From mboxrd@z Thu Jan 1 00:00:00 1970 From: Greg KH Date: Thu, 18 Aug 2005 20:14:36 +0000 Subject: Re: general hotplug/udev questions Message-Id: <20050818201436.GA31814@kroah.com> List-Id: References: <1124394814.4483.46.camel@rich> In-Reply-To: <1124394814.4483.46.camel@rich> MIME-Version: 1.0 Content-Type: text/plain; charset="windows-1252" Content-Transfer-Encoding: quoted-printable To: linux-hotplug@vger.kernel.org On Thu, Aug 18, 2005 at 12:53:34PM -0700, rich turner wrote: > because my linuxrc does not create events or mount /lib/klibc/events in > the initrd, then boot.coldplug does not load the network modules. That is correct. > i realize i can load the network modules in the initrd and everything > would be golden, but that is not the purpose of the initrd. in my > opinion we already do to much in the initrd because the distributions > dont do enough (or do it correctly) in their init scripts. we try to > keep the initrd's purpose to do only enough to mount the root > filesystem. Sorry, but that's not the way we are all moving toward. With initramfs and kinit we are pushing more and more of the early boot stuff into a initramfs/initrd image to get it out of the kernel itself. > it is important that our process remain generic across all distributions > because we need to support many other distributions. I wish you the best of luck. Providing custom kernel images for different distros, while ignoring how they do their initrd/initramfs boot sequence seems like a futile way to go. Not to mention breaking your customer's service contracts with their distro :) > does anyone have an opinion as to whether suse's current method will > become the standard? Is there ever a "standard" for Linux? :) Seriously, I think something like this will become more common as it solves a lot of problems people have with early boot processes. Look at how Red Hat solves it (in a different way, but with the same results.) > it appears that udevstart.static creates events but /sbin/udevstart does > not. why is that? >=20 > is /sbin/hotplugevenrecorder an executable being distributed by suse or > is it something that will be coming in the maintained udev? http://www.kernel.org/git/?p=3Dlinux/hotplug/udev.git;a=3Dblob;h=9A3c3e197c= 6cf3972c0f9d910ac206aed3df66e7;hb=8C11a2f0ff27264513033691bb818262f009fe4e;= f=3Dudeveventrecorder.c look like what you are looking for? > even though we use udevstart in the initrd, is there any real purpose to > echoing something (/sbin/udev, /sbin/udevsend, /bin/true) out > to /proc/sys/kernel/hotplug while in the initrd? Depends on how you want to catch hotplug events. Note, a lot of this has changed recently in suse's kernel. Take a look at opensuse beta 2 for examples of this. > it is my experience that udev only handles devices that you would expect > to find in /dev. how could it have any effect on network interfaces? is > this a product of hotplug or udev? Both. udev can handle network devices just fine, has for years. thanks, greg k-h ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ 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