From: Andrey Borzenkov <arvidjaar@mail.ru>
To: linux-hotplug@vger.kernel.org
Subject: Re: Q-udev
Date: Sat, 14 Jan 2006 08:12:42 +0000 [thread overview]
Message-ID: <200601141112.45038.arvidjaar@mail.ru> (raw)
In-Reply-To: <000701c618d8$82c6b160$840429d4@l02>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Saturday 14 January 2006 10:02, Юра Готовко wrote:
> hello
>
> > "we rely on the kernel 'uevent' triggers of kernel 2.6.15 and no
> > longer want to guess event properties from sysfs like udevstart is doing
> > it"
>
> i'm use 2.6.15 and udev-080;
> udevd starts in sysinit after mounts /proc, /sys, /dev (tmpfs)
> with copy to (console, null, zero, tty, tty0) and
> writing '/dev/null' to /proc/sys/kernel/hotplug;
> udevd start with seq's number ~200 (where all prev's events?)
they have been emitted before you started udevd.
> and how without udevstart fill /dev?
>
It was posted just yesterday; look in archive for thread "cold plugging"
- -andrey
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
iD8DBQFDyLJ8R6LMutpd94wRAg4zAJ0Rpbfm6flTp46wbSKW/Mg0S+FEYgCeJvTd
VmPQiEpKwrZBmuuOl1RSnZQ=BUNR
-----END PGP SIGNATURE-----
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37&alloc_id\x16865&op=click
_______________________________________________
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-01-14 8:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-14 7:02 Q-udev Юра Готовко
2006-01-14 8:12 ` Andrey Borzenkov [this message]
2006-01-14 11:23 ` Q-udev Kay Sievers
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=200601141112.45038.arvidjaar@mail.ru \
--to=arvidjaar@mail.ru \
--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).