From: Andreas Dilger <adilger@turbolinux.com>
To: Jeff Garzik <jgarzik@mandrakesoft.com>
Cc: David Woodhouse <dwmw2@infradead.org>,
Andreas Dilger <adilger@turbolinux.com>,
Venkatesh Ramamurthy <Venkateshr@ami.com>,
"'Bryan Henderson'" <hbryan@us.ibm.com>,
linux-kernel@vger.kernel.org
Subject: Re: Linux not adhering to BIOS Drive boot order?
Date: Wed, 17 Jan 2001 03:19:28 -0700 (MST) [thread overview]
Message-ID: <200101171019.f0HAJSM04596@webber.adilger.net> (raw)
In-Reply-To: <3A656C09.4A40BBF5@mandrakesoft.com> "from Jeff Garzik at Jan 17, 2001 04:55:21 am"
Jeff writes:
> David Woodhouse wrote:
> >
> > adilger@turbolinux.com said:
> > > One reason why this may NOT ever make it into the kernel is that I
> > > know "kernel poking at devices" is really frowned upon.
> >
> > A possible alternative is to specify drives by serial number.
>
> Currently mount(8) supports mounting by '-L <label>' and '-U <UUID>'.
> Most modern mke2fs proggies will assign a UUID to each newly created
> filesystem. For /etc/fstab, you can specify LABEL=xxx or UUID=xxx
> instead of a device name.
> The one thing I don't know is... can the kernel mount the root fs if
> only given the uuid?
You missed the context. I was referring to the 2.2.5? patch that allowed
you to do exactly that - specify a kernel parameter "root=UUID:foo" or
"root=LABEL:bar". I've re-worked it and will post after testing a bit.
My only hesitation was that kernel probing is frowned upon. When UUID/LABEL
support for devfs came up at the Miami Linux Storage Workshop, it was
given the thumbs down.
If I get a chance I will also fix LILO to allow UUID/LABEL for root as well.
Cheers, Andreas
--
Andreas Dilger \ "If a man ate a pound of pasta and a pound of antipasto,
\ would they cancel out, leaving him still hungry?"
http://www-mddsp.enel.ucalgary.ca/People/adilger/ -- Dogbert
-
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:[~2001-01-17 10:20 UTC|newest]
Thread overview: 89+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-16 17:39 Linux not adhering to BIOS Drive boot order? Venkatesh Ramamurthy
2001-01-16 17:58 ` David Woodhouse
2001-01-16 21:11 ` Andreas Dilger
2001-01-17 9:38 ` David Woodhouse
2001-01-17 9:55 ` Jeff Garzik
2001-01-17 10:19 ` Andreas Dilger [this message]
2001-01-17 10:02 ` David Woodhouse
2001-01-19 1:17 ` H. Peter Anvin
2001-01-17 10:12 ` Andreas Dilger
2001-01-17 23:19 ` Russell King
2001-01-17 19:50 ` Werner Almesberger
2001-01-17 20:43 ` Andreas Dilger
2001-01-18 0:14 ` Tim Fletcher
2001-01-18 0:39 ` Andreas Dilger
2001-01-18 0:59 ` Tim Fletcher
2001-01-18 9:41 ` Helge Hafting
-- strict thread matches above, loose matches on Subject: below --
2001-01-18 16:55 David Balazic
2001-01-18 19:49 ` Tim Fletcher
2001-01-18 16:36 Andries.Brouwer
2001-01-18 11:01 David Balazic
2001-01-18 11:35 ` Tim Fletcher
2001-01-18 13:01 ` Xavier Bestel
2001-01-18 14:03 ` Tim Fletcher
2001-01-17 11:04 David Balazic
2001-01-17 10:56 David Balazic
2001-01-17 10:48 David Balazic
2001-01-17 23:23 ` Andreas Dilger
2001-01-18 10:14 ` David Balazic
2001-01-17 10:21 David Balazic
2001-01-17 10:28 ` Boszormenyi Zoltan
2001-01-16 22:54 Venkatesh Ramamurthy
2001-01-16 20:35 Venkatesh Ramamurthy
2001-01-16 20:14 Venkatesh Ramamurthy
2001-01-16 20:30 ` Dr. Kelsey Hudson
2001-01-16 21:18 ` Andreas Dilger
2001-01-17 15:33 ` Mike Porter
2001-01-17 16:16 ` James Bottomley
2001-01-17 17:07 ` Craig Ruff
2001-01-18 12:50 ` Peter Samuelson
2001-01-18 17:59 ` idalton
2001-01-18 18:14 ` Peter Samuelson
2001-01-18 20:53 ` Matti Aarnio
2001-01-18 22:55 ` David Weinehall
2001-01-16 17:30 Bryan Henderson
2001-01-16 17:04 David Balazic
[not found] <Venkateshr@ami.com>
2001-01-16 16:56 ` Venkatesh Ramamurthy
2001-01-16 19:52 ` John Summerfield
2001-01-16 16:51 Venkatesh Ramamurthy
2001-01-16 17:09 ` Honza Pazdziora
2001-01-16 16:46 Venkatesh Ramamurthy
2001-01-16 16:43 Venkatesh Ramamurthy
2001-01-16 20:01 ` Dr. Kelsey Hudson
2001-01-16 20:37 ` Michael Meissner
2001-01-16 21:01 ` Andi Kleen
2001-01-16 21:23 ` Michael Meissner
2001-01-16 23:32 ` J . A . Magallon
2001-01-17 0:05 ` Dr. Kelsey Hudson
2001-01-17 0:42 ` Michael Meissner
2001-01-17 2:14 ` Peter Samuelson
2001-01-17 17:22 ` Michael Meissner
2001-01-17 18:41 ` Douglas Gilbert
2001-01-17 9:45 ` Ishikawa
2001-01-17 15:45 ` J . A . Magallon
2001-01-16 23:51 ` Dr. Kelsey Hudson
2001-01-17 19:22 ` Werner Almesberger
2001-01-17 20:32 ` Matti Aarnio
2001-01-17 20:46 ` Werner Almesberger
2001-01-17 21:26 ` Dr. Kelsey Hudson
2001-01-16 16:35 Venkatesh Ramamurthy
2001-01-16 17:04 ` Brian Gerst
2001-01-16 17:24 ` Eddie Williams
2001-01-16 18:22 ` Timur Tabi
2001-01-16 19:18 ` Matthew D. Pitts
2001-01-16 19:54 ` Christopher Friesen
2001-01-16 21:04 ` Timur Tabi
2001-01-16 22:51 ` Peter Samuelson
2001-01-16 16:31 Venkatesh Ramamurthy
2001-01-16 16:53 ` Eddie Williams
2001-01-16 19:48 ` John Summerfield
2001-01-16 16:19 Venkatesh Ramamurthy
2001-01-16 16:23 ` Florent Cueto
2001-01-16 16:31 ` Brian Gerst
2001-01-16 16:40 ` Dominik Kubla
2001-01-16 15:49 Venkatesh Ramamurthy
2001-01-16 16:06 ` David Woodhouse
2001-01-16 16:27 ` Arjan van de Ven
2001-01-16 16:40 ` Matthias Andree
2001-01-16 16:45 ` Douglas Gilbert
2001-01-16 17:38 ` Malahal Rao Naineni
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=200101171019.f0HAJSM04596@webber.adilger.net \
--to=adilger@turbolinux.com \
--cc=Venkateshr@ami.com \
--cc=dwmw2@infradead.org \
--cc=hbryan@us.ibm.com \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.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