From: Chris Smith <smitty_one_each@bigfoot.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: udev not ready for prime time
Date: Wed, 29 Mar 2006 23:22:59 +0000 [thread overview]
Message-ID: <877j6cesz0.fsf@bigfoot.com> (raw)
In-Reply-To: <20060325182838.GA4546@kroah.com>
>>>>> "Greg" = Greg KH <greg@kroah.com> writes:
Greg> is there any specific problems you are having with it that
Greg> we can help you out with?
I feel that Documentation/early-userspace could use a review.
While the material there is certainly interesting, it doesn't seem
sufficient for a reasonably savvy, yet still aspiring, kernel
developer to craft a bootable kernel.
In particular, getting udev integrated into an initramfs seems
under-documented.
Understood, TMTOWTDI, and it's a distro issue, and it's userspace, not
kernel, etc.
Nevertheless, a vanilla example with the minimal guts to support a
boot would be an improvement.
OTOH, masochistic twit that I am, I'm rather enjoying the gum-shoe
aspects of figuring out WTF to get 'er done.
Thanks,
Chris
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid\x110944&bid$1720&dat\x121642
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
prev parent reply other threads:[~2006-03-29 23:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-25 18:28 udev not ready for prime time Greg KH
2006-03-28 20:33 ` Aaron Griffin
2006-03-29 6:12 ` Tobias Powalowski
2006-03-29 23:22 ` Chris Smith [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=877j6cesz0.fsf@bigfoot.com \
--to=smitty_one_each@bigfoot.com \
--cc=linux-hotplug@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;
as well as URLs for NNTP newsgroup(s).