public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: "Jeff V. Merkey" <jmerkey@soleranetworks.com>
Cc: Jeff Garzik <jeff@garzik.org>,
	"Jeff V. Merkey" <jmerkey@wolfmountaingroup.com>,
	Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: e2label suggestions
Date: Wed, 29 Mar 2006 14:32:29 -0500	[thread overview]
Message-ID: <442AE0CD.1090707@tmr.com> (raw)
In-Reply-To: <4429F247.90209@soleranetworks.com>

Jeff V. Merkey wrote:
> Theodore Ts'o wrote:
> 
>> On Tue, Mar 28, 2006 at 06:18:08PM -0700, Jeff V. Merkey wrote:
>>  
>>
>>> Thanks for verifying it is passed through the kernel to initrd, 
>>> another kernel component.    It's also stored as EXT meta data
>>> (also in the kernel).  and retrieved from there.  And its not 
>>> accessible from normal user space applications (except in raw mode).
>>>   
>>
>> No, the contents of initrd/initramfs is not shipped as part of a
>> standard kernel.org kernel.  It is the responsibility of each
>> distribution to set up their initrd or initramfs initial boot scripts
>> themselves.  One could argue that it would be better if there were a
>> standard set of initrd scripts (and udev binaries) paired with
>> specific kernel.org kernels and used by all distro's, but that's not
>> where we are right now.
>>
>>  
>>
> ????????
> 
>> The data is most certainly accessible from normal userspace
>> applications.  All they have to do is link against blkid library;  
>>
> All you need is a degree from MIT in advanced Fusion mechanics. :-)
> 
>> indeed the kernel doesn't do any LABEL= or UUID= searching at all.  By
>> design, it all supposed to be done in userspace.
>>  
>>
> ?????????
> 
> Ted,
> 
> I give up on this one. I also agree a standardized initrd with built in 
> init is a great idea.

It's a great idea until you ask which init script will be used and 
forced on all the other vendors. Or all the vendors, let's standardize 
on my script, or your script, or Linus' script.

Better yet, let's leave it alone, because even if there were a script 
with the kernel, it would not be a standard ir would only be a default. 
All the vendors do their own thing because they feel it's best, and 
that's not going to change (not probably should it).

-- 
    -bill davidsen (davidsen@tmr.com)
"The secret to procrastination is to put things off until the
  last possible moment - but no longer"  -me


      reply	other threads:[~2006-03-30 20:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-28 21:48 e2label suggestions Jeff V. Merkey
2006-03-28 23:29 ` Theodore Ts'o
2006-03-29  0:25   ` Jeff V. Merkey
2006-03-29  0:13     ` Jeff Garzik
2006-03-29  1:18       ` Jeff V. Merkey
2006-03-29  1:40         ` Theodore Ts'o
2006-03-29  2:34           ` Jeff V. Merkey
2006-03-29 19:32             ` Bill Davidsen [this message]

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=442AE0CD.1090707@tmr.com \
    --to=davidsen@tmr.com \
    --cc=jeff@garzik.org \
    --cc=jmerkey@soleranetworks.com \
    --cc=jmerkey@wolfmountaingroup.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