From: Bill Davidsen <davidsen@tmr.com>
To: "Nathan G. Grennan" <ngrennan@okcforum.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Unresponiveness of 2.4.16 revisited
Date: Sat, 1 Dec 2001 07:11:02 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.3.96.1011201070846.13057B-100000@gatekeeper.tmr.com> (raw)
In-Reply-To: <1007057769.1528.7.camel@cygnusx-1.okcforum.org>
On Thu, 29 Nov 2001, Nathan G. Grennan wrote:
> On Thu, 2001-11-29 at 12:09, Oktay Akbal wrote:
> > Why do you think that fstab matters for root-fs ? root-fs needs to be
> > mounted to read fstab. So autodetection must be done for root-fs.
> > And if the fs has a journal it is ext3. If you do not want that behaviour
> > you might use a option to lilo, but I don't know of any option to specify
> > the root-fs-tyoe. Or you need to use an initrd to mount explicit as ext2
> > and pivot-root it to / ?
> Actually, I think it should respect fstab. It does mount it, then fsck
> it while mounted read-only, then remounts(key point) read-write. IMHO it
> should remount it with whatever fstab says. I realize this could be a
> little tricky, but I bet doable.
Using the precognition() system call no doubt. It can't read fstab without
mounting, how can kernel use fstab to mount to read fstab? Original
response was correct, you need to learn to use initrd.
--
bill davidsen <davidsen@tmr.com>
CTO, TMR Associates, Inc
Doing interesting things with little computers since 1979.
prev parent reply other threads:[~2001-12-01 12:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-28 6:19 Unresponiveness of 2.4.16 revisited Nathan G. Grennan
2001-11-29 6:30 ` Andrew Morton
2001-11-29 21:12 ` Mike Fedyk
[not found] ` <1007021221.1739.0.camel@cygnusx-1.okcforum.org>
2001-11-29 9:07 ` Nathan G. Grennan
2001-11-29 9:32 ` Oktay Akbal
2001-11-29 16:48 ` Nathan G. Grennan
2001-11-29 18:09 ` Oktay Akbal
2001-11-29 18:16 ` Nathan G. Grennan
2001-11-29 18:36 ` Andreas Dilger
2001-12-01 12:11 ` Bill Davidsen [this message]
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=Pine.LNX.3.96.1011201070846.13057B-100000@gatekeeper.tmr.com \
--to=davidsen@tmr.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ngrennan@okcforum.org \
/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;
as well as URLs for NNTP newsgroup(s).