|
|||||||||||
|
[RFC] No longer create full set of static devices during install
From: Frans Pop <elendil(at)planet.nl>
Date: Fri Nov 09 2007 - 18:41:12 EST
This also ensures that we will no longer "miss" any devices in /target/dev during installations. (We have had bug reports in the past where we were missing e.g. /dev/hdi.) debootstrap is modified to include in the udeb only the minimal tarball of devices currently also included in the regular debootstrap binary package. We still need the udeb to be "arch any" because of the utility pkgdetails and because /usr/lib/debootstrap/arch needs to be included. A minor change in rootskel creates the /dev/.static/dev directory because some packages may try to create static devices during installation. If any static devices are created, these are copied to /target/dev during finish-install (after unmounting the bind mount). I've also removed the creation of /.dev in the D-I environment as that seems obsolete. The create_devices function in base-installer has been simplified a lot because it no longer actually has to create any device nodes anymore. It now takes care of the bind mount to /target/dev and does some apt-install calls for RAID, LVM and crypto installs. (Suggestions for a better name for this function welcome!) I've done successful LVM and LVM-crypto installs using the new udebs. This proofed to be a lot simpler than I had expected, so the question is: what have I missed? Are there still any arches that don't use udev for default installs? If there are, they could be accommodated by calling MAKEDEV during base-installer (using the same set of devices that used to be created by debootstrap).
Cheers,
-- To UNSUBSCRIBE, email to debian-boot-REQUEST@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.orgReceived on Fri Nov 9 18:41:40 2007 This archive was generated by hypermail 2.1.8 : Wed Mar 19 2008 - 03:19:02 EDT |
||||||||||
|
|||||||||||