Am 18.09.2013 19:01, schrieb Andrew Chant:
Reopening this bug report is correct. I won't play re-open tag with
you, though I hope you will consider re-opening the bug.
Just checking for devtmpfs in /proc/filesystems is not enough. The
Why not?
update caused my system to stop booting, which
Reopening this bug report is correct. I won't play re-open tag with
you, though I hope you will consider re-opening the bug.
Just checking for devtmpfs in /proc/filesystems is not enough. The
update caused my system to stop booting, which no update should ever
do. You are correct that I have no
As-mentioned,
using the kernel from which I ran this:
chant@zbz:~$ zcat /proc/config.gz | grep DEVTMP
CONFIG_DEVTMPFS=y
# CONFIG_DEVTMPFS_MOUNT is not set
I got a system which didn't load any modules and which failed to boot,
same symptoms as the initial bug.
I would hope you would be more
Woops, CC'd the wrong bug. sorry for the noise.
On Wed, Sep 18, 2013 at 11:17 AM, Andrew Chant
andrew.chant+deb...@gmail.com wrote:
As-mentioned,
using the kernel from which I ran this:
chant@zbz:~$ zcat /proc/config.gz | grep DEVTMP
CONFIG_DEVTMPFS=y
# CONFIG_DEVTMPFS_MOUNT is not set
I
+722580 -722850, woops.
As-mentioned, I am using the kernel from which I ran this:
chant@zbz:~$ zcat /proc/config.gz | grep DEVTMP
CONFIG_DEVTMPFS=y
# CONFIG_DEVTMPFS_MOUNT is not set
I got a system which didn't load any modules and which failed to boot,
same symptoms as the initial bug.
I would
This update made my system unbootable due to no devices being created
by udev. However, I believe your fix won't work on my system.
chant@zbz:~$ zcat /proc/config.gz | grep DEVTMP
CONFIG_DEVTMPFS=y
# CONFIG_DEVTMPFS_MOUNT is not set
this configuration was enough to cause the problem.
--
To
6 matches
Mail list logo
