From: Joel Becker <Joel.Becker@oracle.com>
To: Chris Wedgwood <cw@f00f.org>
Cc: Jeff Garzik <jgarzik@pobox.com>,
Ricky Beam <jfbeam@bluetronic.net>,
"Eric D. Mudama" <edmudama@bounceswoosh.org>,
"Robert M. Stockmann" <stock@stokkie.net>,
linux-kernel@vger.kernel.org
Subject: Re: SATA disk device naming ?
Date: Wed, 14 Jul 2004 19:44:14 -0700 [thread overview]
Message-ID: <20040715024414.GG28239@ca-server1.us.oracle.com> (raw)
In-Reply-To: <20040713223541.GB7980@taniwha.stupidest.org>
On Tue, Jul 13, 2004 at 03:35:41PM -0700, Chris Wedgwood wrote:
> initrd is such a PITA at times, I wondered about something hacky like
> sticking LABEL parsing for rootfs (marked init) into the kernel but
> it's really gross.
>
> Ideally the initrd/initramfs process just needs better (userspace)
> infrastructure to make it more reliable/easier.
I'm waiting for udev to give me consistent device names easily.
Then I can specify root=/dev/disk1 and not have to scan-all-100-disks
for LABEL mounts.
Joel
--
f/8 and be there.
Joel Becker
Senior Member of Technical Staff
Oracle Corporation
E-mail: joel.becker@oracle.com
Phone: (650) 506-8127
next prev parent reply other threads:[~2004-07-15 2:46 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-13 2:25 SATA disk device naming ? Robert M. Stockmann
2004-07-13 3:04 ` Jeff Garzik
2004-07-14 11:20 ` Arnd Bergmann
2004-07-15 17:37 ` Bartlomiej Zolnierkiewicz
2004-07-15 18:07 ` Jeff Garzik
2004-07-13 6:46 ` Eric D. Mudama
2004-07-13 13:24 ` Ian Soboroff
2004-07-13 16:23 ` Ricky Beam
2004-07-13 16:49 ` Jeff Garzik
2004-07-13 17:29 ` Tigran Aivazian
2004-07-13 22:35 ` Chris Wedgwood
2004-07-14 9:48 ` P
2004-07-15 2:44 ` Joel Becker [this message]
2004-07-25 19:05 ` Greg KH
2004-07-13 17:15 ` Tigran Aivazian
2004-07-13 16:58 ` Muli Ben-Yehuda
-- strict thread matches above, loose matches on Subject: below --
2004-07-14 0:09 DaMouse
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=20040715024414.GG28239@ca-server1.us.oracle.com \
--to=joel.becker@oracle.com \
--cc=cw@f00f.org \
--cc=edmudama@bounceswoosh.org \
--cc=jfbeam@bluetronic.net \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stock@stokkie.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.