From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kay Sievers Date: Sat, 14 Jan 2006 11:23:10 +0000 Subject: Re: Q-udev Message-Id: <20060114112310.GA11605@vrfy.org> List-Id: References: <000701c618d8$82c6b160$840429d4@l02> In-Reply-To: <000701c618d8$82c6b160$840429d4@l02> MIME-Version: 1.0 Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: quoted-printable To: linux-hotplug@vger.kernel.org On Sat, Jan 14, 2006 at 02:02:03PM +0700, =D0=AE=D1=80=D0=B0 =D0=93=D0=BE= =D1=82=D0=BE=D0=B2=D0=BA=D0=BE wrote: > > "we rely on the kernel 'uevent' triggers of kernel 2.6.15 and no lon= ger > > want to guess event properties from sysfs like udevstart is doing it" >=20 > 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; Huh, hell, what does a device node at a program execution path? > udevd start with seq's number ~200 (where all prev's events?) > and how without udevstart fill /dev? Rerequest the events from sysfs. Good luck, Kay ------------------------------------------------------- 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=16865&op=CCk _______________________________________________ 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