All of lore.kernel.org
 help / color / mirror / Atom feed
From: P@draigBrady.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 10:48:49 +0100	[thread overview]
Message-ID: <40F50181.7070900@draigBrady.com> (raw)
In-Reply-To: <20040713223541.GB7980@taniwha.stupidest.org>

Chris Wedgwood wrote:
> On Tue, Jul 13, 2004 at 12:49:11PM -0400, Jeff Garzik wrote:
> 
> 
>>For LABEL to work on root filesystem, you need an initrd.
> 
> 
> 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.

Something like this?
http://www-124.ibm.com/pipermail/evms/2001-March/000119.html

initrd is awkward but I've found I need the flexibility.
For e.g. I modified nash to support an index as well as
a label so one could have multiple redundant filesystem
images to choose from.

Pádraig.

  reply	other threads:[~2004-07-14  9:50 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 [this message]
2004-07-15  2:44         ` Joel Becker
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=40F50181.7070900@draigBrady.com \
    --to=p@draigbrady.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.