From: Andrzej Krzysztofowicz <ankry@pg.gda.pl>
To: tigran@veritas.com (Tigran Aivazian)
Cc: torvalds@transmeta.com (Linus Torvalds), linux-kernel@vger.kernel.org
Subject: Re: [patch-2.4.0-test13-pre3] rootfs boot param. support
Date: Mon, 18 Dec 2000 13:11:15 +0100 (MET) [thread overview]
Message-ID: <200012181211.NAA15721@sunrise.pg.gda.pl> (raw)
In-Reply-To: <Pine.LNX.4.21.0012181150060.840-100000@penguin.homenet> from "Tigran Aivazian" at Dec 18, 2000 11:56:47 AM
"Tigran Aivazian wrote:"
> In November last year I wrote support for a new boot parameter called
> "rootfs" implementing functionality similar to UnixWare7, i.e. being
> able to specify the filesystem type to try first in mount_root() and if
> this fails then go on to the usual loop over all registered filesystems.
>
> At the time it was of pure academical interest (i.e. generally useful to
> everybody) but now I realized that it is actually quite critical, i.e.
> there exist filesystems (e.g. ext2) which are not able to detect their
> structural integrity beyond simple damage to the superblock. So, as a
It is more critical now if one wants to use eg. UMSDOS filesystem as root fs.
As the msdos filesystem is linked first system always tries to use it first
when there is a FAT filesystem on the root device.
One way of solving the problem is the "rootfs" parameter.
Changing link sequence to be non-alphabetic is another choice...
However, it is a separate issue that UMSDOS-root is broken in 2.4 at the
moment. But I hope it is not a permanent state.
> diff -urN -X dontdiff linux/Documentation/kernel-parameters.txt rootfs/Documentation/kernel-parameters.txt
> --- linux/Documentation/kernel-parameters.txt Tue Sep 5 21:51:14 2000
> +++ rootfs/Documentation/kernel-parameters.txt Mon Dec 18 09:04:06 2000
> @@ -473,7 +473,10 @@
>
> ro [KNL] Mount root device read-only on boot.
>
> - root= [KNL] root filesystem.
> + root= [KNL] Mount root filesystem on specified (as hex or "/dev/XXX") device.
> +
> + rootfs= [KNL] Use filesystem type specified (e.g. rootfs=ext2) for root.
> +
>
> rw [KNL] Mount root device read-write on boot.
>
Regards
Andrzej
--
=======================================================================
Andrzej M. Krzysztofowicz ankry@mif.pg.gda.pl
phone (48)(58) 347 14 61
Faculty of Applied Phys. & Math., Technical University of Gdansk
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-12-18 12:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.21.0012111102480.801-100000@penguin.homenet>
2000-12-18 11:56 ` Tigran Aivazian
2000-12-18 12:11 ` Andrzej Krzysztofowicz [this message]
2000-12-18 12:45 ` Peter Samuelson
2000-12-18 13:24 ` Tigran Aivazian
2000-12-18 15:12 ` Peter Samuelson
2000-12-18 15:21 ` Tigran Aivazian
2000-12-18 14:17 Andries.Brouwer
2000-12-18 15:22 ` Peter Samuelson
2000-12-18 15:36 ` Tigran Aivazian
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=200012181211.NAA15721@sunrise.pg.gda.pl \
--to=ankry@pg.gda.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=tigran@veritas.com \
--cc=torvalds@transmeta.com \
/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
all inboxes | Powered by JetHome®