public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@digeo.com>
To: Mohamed El Ayouty <melayout@umich.edu>
Cc: Rusty Russell <rusty@rustcorp.com.au>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [2.5.51] Failure to mount ext3 root when ext2 compiled in
Date: Sat, 14 Dec 2002 02:11:52 -0800	[thread overview]
Message-ID: <3DFB03E8.C7AB1271@digeo.com> (raw)
In-Reply-To: 1039790158.25215.48.camel@syKr0n.mine.nu

Mohamed El Ayouty wrote:
> 
> Hi,
> 
> This sounds more like the bug I have opened:
> 
> http://bugme.osdl.org/show_bug.cgi?id=110
> 
> where if CONFIG_DEVFS_FS = Y and CONFIG_DEVFS_MOUNT = Y, you will get:
> 
> VFS: Cannot open root device "hda2" or 03:02
> Please append a correct "root=" boot option
> Kernel panic: VFS: Unable to mount root fs on 03:02
> 
> I worked around it by enabling CONFIG_UNIX98_PTYS = Y under the
> character devices.
> 
> But, a recent update to the bug shows that a patch was posted but nobody
> cared.
> 
> Personally, I think the patch should be merged.

You mean this one?

	http://www.lkml.org/archive/2002/12/13/50/index.html

It appears to simply disable internal mounting of devfs.

In which kernel did this problem first appear?   There were
devfs changes in 2.5.51.

  reply	other threads:[~2002-12-14 10:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-13 14:35 [2.5.51] Failure to mount ext3 root when ext2 compiled in Mohamed El Ayouty
2002-12-14 10:11 ` Andrew Morton [this message]
2002-12-14 14:22   ` Mohamed El Ayouty
2002-12-14 18:48     ` Andrew Morton
2002-12-14 19:06       ` Mohamed El Ayouty
  -- strict thread matches above, loose matches on Subject: below --
2002-12-13  3:48 Rusty Russell
2002-12-13  4:09 ` Andrew Morton
2002-12-16 21:42   ` Rusty Russell
2002-12-13 14:31 ` Wayne Willson

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=3DFB03E8.C7AB1271@digeo.com \
    --to=akpm@digeo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=melayout@umich.edu \
    --cc=rusty@rustcorp.com.au \
    /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