Differences between revisions 8 and 9
Revision 8 as of 2005-11-03 21:48:46
Size: 3289
Editor: 156_220_103_66-WIFI_HOTSPOTS
Comment: Update
Revision 9 as of 2005-11-03 21:54:19
Size: 3405
Editor: 156_220_103_66-WIFI_HOTSPOTS
Comment: Add note about klibc, add another modutils note
Deletions are marked like this. Additions are marked like this.
Line 31: Line 31:

 * modutils
Line 69: Line 71:
=== klibc ===

 * udev should be compiled against a recent version of klibc for tiny initramfs'


Upgrading from udev 060 to 071 is a major change that affects initramfs, udev, hotplug, hal, and many other pieces. The 2.6.15 kernel will require udev 071. Because these changes are invasive, this spec is split out from HardwareDetection to make sure that it can be reviewed and implemented independantly.



This is an implementation for Dapper.

Newer versions of udev affect the following packages:

  • initramfs-tools
  • hotplug
  • klibc
  • hal
  • linux-image-*
  • modutils



Update the initramfs startup sequence to reflect the following:

  • Create base device nodes
  • Start udevd
  • Load modules from /etc/mkinitramfs/modules (and other force_load calls)

Note: without udevstart, something needs to correct permissions, or we need to provide the rules.

  • Walk the sysfs tree for harddrive devices and tickle uevents for those.

Some of the code for this exists in the current

  • Walk the ide, scsi, and i2o busses
  • Attempt hibernate recovery
  • Walk the pci sysfs tree for usb controllers


  • Upgrade to udev-071 plus current git patches.

Git patches after 071 cause the rules to be cached. It's best to just accomidate this now. Current git patches also add more man pages, and some extra needed UUID support.


  • Ask the ftpmasters to remove from the archive.


  • Upgrade modutils to recent version to get blacklisting support.


  • udev should be compiled against a recent version of klibc for tiny initramfs'

full userspace init scripts

  • As soon as full userspace has started, need to tell udev to reread all of the rulesets.
  • Where udevstart and coldplugging routines are currently run, ensure that udevd is running (in case of custom kernels), and pass over entire sysfs tree to cause events to be rerun. This will ensure that device nodes are created with correct permissions and according to the rules of the running system.

Data preservation and migration

Custom written hotplug rules will need to be migrated to be udev rules. There is no way to do this in an automated fashion.

Outstanding issues

Rebooting the system shortly after the upgrade is critical. It is quite likely that hal will stop working, and the rules that are on the harddrive may then be completely incompatible. The cute little lightbulb "Please click on me for a message" in the corner is probably insufficiently invasive to make sure this happens. That notification applet should be refered to mpt for a case of the mean-and-ugly treatment. This is out of scope for this spec.

UdevRoadmap (last edited 2008-08-06 16:16:48 by localhost)