Re: DEVTMPFS, DEVTMPFS_MOUNT, custom no initrd kernel, udev 175-7.2 and 204-4
On Thu, Sep 26, 2013 at 7:25 AM, Regid Ichira <regid23@nt1.in> wrote:
The following's what I've understood from #722604...
> 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.
Without an initramfs, you'll need CONFIG_DEVTMPFS_MOUNT=y given the
devtmpfs bug in the udev init script.
> 2. What about
> CONFIG_DEVTMPFS=y
> CONFIG_DEVTMPFS_MOUNT=y
> ? custom, non initrd, linux image. udev 175-7.2.
OK.
> 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.
If you're going to recompile your kernel with CONFIG_DEVTMPFS=y, you
may as well set CONFIG_DEVTMPFS_MOUNT=y and not edit the udev init
script.
> 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?
CONFIG_DEVTMPFS=y
and
CONFIG_DEVTMPFS_MOUNT=y or unset
> 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?
For 204-3, not having CONFIG_DEVTMPFS=y and CONFIG_DEVTMPFS_MOUNT=y
will result in a "problem."
For 204-4, not having CONFIG_DEVTMPFS=y will prevent you from
upgrading from 175-7.2.
(See my answer to your 3rd question for an answer to your last question.)
Reply to: