From: marrandy <marrandy@chaossolutions.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: overview of using hotplug in initrd
Date: Sat, 25 Feb 2006 00:26:29 +0000 [thread overview]
Message-ID: <200602241926.29855.marrandy@chaossolutions.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0602221115450.27382@www.mutagenix.org>
On Wednesday 22 February 2006 17:47, Chris Smith wrote:
> >>>>> "Marco" = Marco d'Itri <md@Linux.IT> writes:
>
> Marco> On Feb 22, Dan Barber <dan@mutagenix.org> wrote:
> >> Can someone point me to an overview or HOWTO in using hotplug
> >> in initrd for discovering hardware on boot up?
>
> Marco> You don't, nowadays you are supposed to use udev and an
> Marco> initramfs.
>
> Is there a reference implementation of how that should be done? I
> used some ancient stuff to traverse /sys and make nodes for my block
> devices, but the resulting boot was very messy. What is Teh 'Right'
> Way To Do It?
> Best,
> Chris
What's up with your clock. It's Friday, not Wednesday. Please fix it.
-------------------------------------------------------
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
next prev parent reply other threads:[~2006-02-25 0:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-22 16:16 overview of using hotplug in initrd Dan Barber
2006-02-22 16:31 ` Marco d'Itri
2006-02-22 22:47 ` Chris Smith
2006-02-25 0:26 ` marrandy [this message]
2006-02-25 1:39 ` David Gómez
2006-02-25 6:31 ` iSteve
2006-02-27 18:06 ` Aaron Griffin
2006-02-27 18:19 ` iSteve
2006-02-27 18:25 ` Aaron Griffin
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=200602241926.29855.marrandy@chaossolutions.org \
--to=marrandy@chaossolutions.org \
--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 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.