I'm starting to develop a udev guide which will contain how to setup udev (and hotplug and other things), why devfs isn't as good as people first thought, and how we can have udev and devfs work together on dualboot systems (with both 2.4 and 2.6 kernels) Any pointers to good stories are appreciated
you might appreciate this fairly recent overview in http://kerneltrap.org/node/view/799. Shows some of the new features, including the new (snazzier) kernel build scripts.
No word on udev though :(
http://lwn.net/Articles/28526/ not much but a little bus_drivr
Published today in kerneltrap.org (http://kerneltrap.org/node/view/1031) regarding the release of version 004 of udev. Just so as we keep our collective eyes on the ball ...
Hmm, I wanted to submit it as a new bug, but you might enjoy it more. Attached an ebuild for the latest udev release (which includes two small fixes I took from LKML). The tarball is to be extracted in $PORTDIR_OVERLAY and will create sys-apps/udev have fun.
Created attachment 19641 [details] udev ebuild and patches
Created attachment 19642 [details] ebuild update the previous ebuild version was old and buggy and accidentially uploaded.
Thanks; how does one use udev?
for updates to packages please file new bugs ... 004 is already in portage though :) as for using udev, i just had to emerge the latest baselayout and enable hotplug support in my kernel ... the init.d scripts did the rest ...
so fully disabling devfs in the kernel works on gentoo (i.e. udev takes over the device naming stuff)?
yes and no ... the thread on gentoo-dev sums up the current state of things ... http://article.gmane.org/gmane.linux.gentoo.devel/13148
> as for using udev, i just had to emerge the latest baselayout and enable > hotplug support in my kernel ... the init.d scripts did the rest ... Emerged the latest baselayout, (looks like the only thing left out) see: * Populating /dev with device nodes... Few new devices created in /dev but don't see any new "init.d scripts" that deal with udev. From the tarballs of udev 007 & 008 there is a init.d script for another distro that won't work with Gentoo. Manually created the /sys folder earlier, but don't see anything in baselayout creating it. My /sys folder is working fine, knows when items are plugged in or not. But don't see any changes for example when plug/unplug the scanner in /dev only in /sys. bash-2.05b# lsbus -D usb Bus: usb Drivers: usbscanner microtekX6 Devices: 1-2:1.0 Not seeing any deletion of devices or creation when plug/unplug it though in /dev. So even with the new baselayout this seems either Very Transparent or still not doing anything but within the /sys folder and hotplug. So is the functionality of the init.d scripts still missing?
no, the only change needed with the init.d scripts is that it mounts a ramdisk on /dev, populates it with the previous dev snapshot, and then sets the hotplug manager to the udev binary after that it's a 'bug' in udev ... has nothing to do with init scripts
I've got some forum posts that talk about udev working with gentoo: http://forums.gentoo.org/viewtopic.php?t=114303 http://forums.gentoo.org/viewtopic.php?t=115096 http://forums.gentoo.org/viewtopic.php?t=100173 I'll investigate those later on and see if I can write up something (and if everything works, integrate it in the handbook -- *after* the next gentoo release).
How bout this also: http://forums.gentoo.org/viewtopic.php?t=116093
udev ebuild suggestion: initially backing up /dev on install like its done every reboot would start users off with a working /dev and solve a lot of problems for people losing alsa / nvidia nodes etc.
latest udev supports nvidia/alsa properly (at least it does on all my boxes) next up would seem to be /dev/fb ...
A draft document has been committed and is online at http://www.gentoo.org/doc/en/udev-guide.xml soon. Comment away...
Since baselayout-1.8.6.13-r1 there is no need to alter /sbin/rc or /etc/init.d/halt.sh. Just set RC_DEVICE_TARBALL="no" in /etc/conf.d/rc BTW, what is the point of having two config files for rc scripts (/etc/rc.conf and /etc/conf.d/rc)?
i was actually just updating my baselayout and wondered the samething ... why do we have both /etc/rc.conf and /etc/conf.d/rc ... i'll talk to azarah ;)
I've linked the udev-guide.xml file and am marking this one as FIXED. Regarding the /etc/conf.d/rc and /etc/rc.conf, please file a separate bugreport if necessary.
