From: Olaf Hering <olh@suse.de>
To: linux-hotplug@vger.kernel.org
Subject: Re: [PATCH] Enable all events for initramfs
Date: Wed, 14 Jul 2004 06:24:01 +0000 [thread overview]
Message-ID: <20040714062401.GA10304@suse.de> (raw)
In-Reply-To: <40F3C48F.30905@suse.de>
On Wed, Jul 14, Alexander E. Patrakov wrote:
> I see the following application of it. Since no hotplug events are
> dropped any more, the initramfs could save their type and environment in
> files on a ramfs, and then remount that ramfs to some location
> accessible by the main system. The information accumulated in these
> files can be used for re-synthesis of events not handled because e.g.
> /usr was not mounted.
The info as already in sysfs. See how udevstart regenerates each
relevant event.
The whole point of handling these events on the fly is speed. No need to
run udevstart anymore. But you better not drop udevstart. It will
rebuild /dev/ if you toasted its content.
And a hotplug package is really broken if it relies on stuff in /usr
--
USB is for mice, FireWire is for men!
sUse lINUX ag, n√úRNBERG
-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 -
digital self defense, top technical experts, no vendor pitches,
unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
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:[~2004-07-14 6:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-13 11:16 [PATCH] Enable all events for initramfs Hannes Reinecke
2004-07-14 4:01 ` Alexander E. Patrakov
2004-07-14 6:24 ` Olaf Hering [this message]
2004-07-15 16:45 ` Alexander E. Patrakov
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=20040714062401.GA10304@suse.de \
--to=olh@suse.de \
--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).