From: David van Hoose <david.vanhoose@comcast.net>
To: Christoph Hellwig <hch@infradead.org>
Cc: Helge Hafting <helge.hafting@hist.no>,
John Richard Moser <nigelenki@comcast.net>,
linux-kernel@vger.kernel.org
Subject: Re: Collapse ext2 and 3 please
Date: Fri, 25 Jun 2004 07:50:42 -0400 [thread overview]
Message-ID: <40DC1192.7030006@comcast.net> (raw)
In-Reply-To: <20040625114105.GA28892@infradead.org>
yeah.. Really. Here's what I do.
I have ext3 partitions, so I decided if they are different partitions,
then I can compile my kernel with ext2 as a module and ext3 builtin.
So I do it and reboot. Panic! Reason? Cannot find filesystem for the
root partition.
The error is in the kernel itself either way. Pick your reason.
1) ext3 is identified as ext2 on bootup.
2) There is no fallback to ext3 if ext2 is not found.
I'll check this again to be sure on a 2.6 kernel later today, but as far
as 2.4 is concerned my kernel panics.
Regards,
David
PS. Shut up with the cheap insults. I have empirical evidence supporting
my claim. Meaning there exists a bug somewhere.
Christoph Hellwig wrote:
> On Fri, Jun 25, 2004 at 07:30:40AM -0400, David van Hoose wrote:
>
>>If ext2 and ext3 are different filesystems, why does my kernel panic if
>>I include ext3 in the kernel make ext2 a module?
>
>
> My kernel doesn't, must be a problem in front of the computer.
>
>
next prev parent reply other threads:[~2004-06-25 11:50 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-24 23:14 Collapse ext2 and 3 please John Richard Moser
2004-06-25 9:16 ` Helge Hafting
2004-06-25 11:30 ` David van Hoose
2004-06-25 11:41 ` Christoph Hellwig
2004-06-25 11:50 ` David van Hoose [this message]
2004-06-25 12:01 ` Matthew Garrett
[not found] ` <1088165028.16286.59.camel@imp.csi.cam.ac.uk>
2004-06-25 12:05 ` David van Hoose
2004-06-25 12:13 ` Matthew Garrett
[not found] ` <1088165426.16286.67.camel@imp.csi.cam.ac.uk>
2004-06-25 12:18 ` David van Hoose
2004-06-25 13:03 ` Tigran Aivazian
2004-06-25 12:40 ` David van Hoose
2004-06-25 14:03 ` Rik van Riel
2004-06-25 12:10 ` Christoph Hellwig
2004-06-25 12:15 ` David van Hoose
2004-06-25 12:26 ` Richard B. Johnson
2004-06-25 12:48 ` Philip R. Auld
2004-06-25 12:53 ` David van Hoose
2004-06-25 13:39 ` Tigran Aivazian
2004-06-25 18:55 ` David van Hoose
2004-06-25 22:26 ` John Richard Moser
2004-06-25 12:25 ` Sean Neakums
2004-06-25 18:01 ` Timothy Miller
2004-06-25 18:04 ` Sean Neakums
2004-06-25 18:41 ` Timothy Miller
2004-06-25 20:52 ` R. J. Wysocki
2004-06-25 20:50 ` Sean Neakums
2004-06-25 21:36 ` R. J. Wysocki
2004-06-25 22:00 ` Andrew Morton
2004-06-25 23:48 ` John Richard Moser
[not found] <2aZfF-3es-5@gated-at.bofh.it>
[not found] ` <2b45V-6tl-39@gated-at.bofh.it>
2004-06-25 22:28 ` Pascal Schmidt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=40DC1192.7030006@comcast.net \
--to=david.vanhoose@comcast.net \
--cc=hch@infradead.org \
--cc=helge.hafting@hist.no \
--cc=linux-kernel@vger.kernel.org \
--cc=nigelenki@comcast.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox