In view of http://bugs.debian.org/722580 and http://bugs.debian.org/722604:
A machine with: - a custom, non initrd, linux image - udev 175-7.2 - no DEVTMPFS in the kernel configuration is able to boot. 1. Will the machine boot with CONFIG_DEVTMPFS=y # CONFIG_DEVTMPFS_MOUNT is not set ? Again, custom, non initrd, linux image. udev 175-7.2. 2. What about CONFIG_DEVTMPFS=y CONFIG_DEVTMPFS_MOUNT=y ? custom, non initrd, linux image. udev 175-7.2. 3. Will it boot when /etc/init.d/udev from udev 175-7.2 is edtited by hand? If so, what modifications, by hand, are required to /etc/init.d/udev? Are there more files to edit? Again, custom, non initrd, linux image. 4. When udev 204-4 is installed, what should be the settings of CONFIG_DEVTMPFS and CONFIG_DEVTMPFS_MOUNT for a custom, non initrd, linux image? Isn't there an upgrade path problem for people with a custom, non initrd, linux image that have DEVTMPFS unset? I mean, newer udev can't be installed without CONFIG_DEVTMPFS=y. So one has to boot into a CONFIG_DEVTMPFS=y kernel before upgrading udev. But will a custom, non initrd, linux image with CONFIG_DEVTMPFS=y boot with udev 175-7.2? -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130926112533.ga21...@nt1.in