All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: David VomLehn <dvomlehn@cisco.com>
Cc: stern@rowland.harvard.edu, linux-kernel@vger.kernel.org,
	linux-usb@vger.kernel.org, linux-scsi@cuplxvomd02.corp.sa.net,
	netdev@cuplxvomd02.corp.sa.net
Subject: Re: [PATCH 1/5] KERNEL: Support asynchronously-discovered boot devices, v4 (resend)
Date: Fri, 1 May 2009 13:22:58 -0700	[thread overview]
Message-ID: <20090501132258.672002ee.akpm@linux-foundation.org> (raw)
In-Reply-To: <20090501165803.GA13342@cuplxvomd02.corp.sa.net>

On Fri, 1 May 2009 09:58:03 -0700
David VomLehn <dvomlehn@cisco.com> wrote:

> On Thu, Apr 30, 2009 at 02:54:12PM -0700, Andrew Morton wrote:
> > On Thu, 30 Apr 2009 17:19:34 -0400 (EDT)
> > Alan Stern <stern@rowland.harvard.edu> wrote:
> > 
> > > > I wonder if we can think of something more new ad unique.  startupdev?  yuk.
> > > 
> > > Initdev?  Or does that mean something else also?
> ...
> > initdev sounds good to me.  Given that we're adding a new and distinct
> > concept which will remain with us for a long time, we should name it
> > with care.
> 
> Yes, we do need a good name, so we are now guaranteed to be entering
> the Bike Shed Zone.

Getting the name right is important!  We live with the decision daily,
for years.

> Personally, I'm fine with initdev and will assume this
> is the name going forward. I'll tweak the patches appropriately.

OK.

> > > Really, these are devices that we want to have working before starting
> > > up any userspace processes.  These would be the console device(s) (so
> > > that the first process has open files for its stdin, stdout, and
> > > stderr) and the block device containing the root filesystem (if the
> > > initramfs image doesn't make its own arrangements).
> > 
> > OK, so "initdev" could be viewed as meaning "a device which /sbin/init
> > needs"?  Even I can understand that.
> > 
> > But /sbin/init isn't the first userspace we run, is it?  There's
> > initramfs stuff, firmware loaders, etc.
> > 
> > What's the story here?  Do we intend that all initdevs be up and
> > running before _any_ userspace runs?  Or is /sbin/init the red line?
> 
> I've avoided making any guarantees about this, but /sbin/init is implicitly
> the red line. If we make this explicit, we're probably back in the vicinity
> of the bike shed, but this should help frame any subsequent discussion
> in a concrete manner.

Well, decisions which are made here can make the difference between
"computer boots" and "computer doesn't boot".  That ain't bikeshed
painting.


  parent reply	other threads:[~2009-05-01 20:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-30  1:45 [PATCH 1/5] KERNEL: Support asynchronously-discovered boot devices, v4 (resend) David VomLehn
2009-04-30 21:05 ` Andrew Morton
2009-04-30 21:19   ` Alan Stern
2009-04-30 21:54     ` Andrew Morton
2009-05-01 16:58       ` David VomLehn
2009-05-01 17:20         ` Alan Stern
2009-05-01 20:22         ` Andrew Morton [this message]
2009-05-01 23:11           ` David VomLehn

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=20090501132258.672002ee.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=dvomlehn@cisco.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@cuplxvomd02.corp.sa.net \
    --cc=linux-usb@vger.kernel.org \
    --cc=netdev@cuplxvomd02.corp.sa.net \
    --cc=stern@rowland.harvard.edu \
    /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.