mountpoint does not exist (securityfs, fuse/connections)
Bug #447525 reported by
Michael Marley
This bug affects 8 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
mountall (Ubuntu) |
Fix Released
|
Medium
|
Unassigned |
Bug Description
Binary package hint: mountall
I just updated my Karmic AMD64 system to the latest version of mountall, but it causes it to fail to boot when running a custom-compiled kernel without the initramfs. The error message says that mountall died because it could not remove the /forcefsck file because the file system is read only. The standard Ubuntu kernel works fine, and rolling back to version 0.1.8 of mountall works around my problem.
To post a comment you must log in.
And I know why... security probably with apparmor filesystem
mountall now tries to mount /sys/kernel/
I don't have one in my kernel.
I think that mountall should never return a failure, as this results in complete lack of ability to boot because lets face it upstart is nice, but less robust/ configurable.