From: "Theodore Ts'o" <tytso@mit.edu>
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: Tue, 28 Mar 2006 20:40:48 -0500 [thread overview]
Message-ID: <20060329014048.GA29971@thunk.org> (raw)
In-Reply-To: <4429E050.7080008@soleranetworks.com>
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;
indeed the kernel doesn't do any LABEL= or UUID= searching at all. By
design, it all supposed to be done in userspace.
- Ted
next prev parent reply other threads:[~2006-03-29 1:40 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 [this message]
2006-03-29 2:34 ` Jeff V. Merkey
2006-03-29 19:32 ` Bill Davidsen
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=20060329014048.GA29971@thunk.org \
--to=tytso@mit.edu \
--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