My karmic linode.com machine (xen hosting) is also back up with this
package, thanks!
--
mountpoint does not exist (securityfs, fuse/connections)
https://bugs.launchpad.net/bugs/447525
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
And my DomU is starting again. Great work. Thank you!
--
mountpoint does not exist (securityfs, fuse/connections)
https://bugs.launchpad.net/bugs/447525
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-
Mine, too. Thanks!
--
mountpoint does not exist (securityfs, fuse/connections)
https://bugs.launchpad.net/bugs/447525
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://list
Ok. Now my custom kernel boots fine. Thank you Scott. Bye!
--
mountpoint does not exist (securityfs, fuse/connections)
https://bugs.launchpad.net/bugs/447525
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ub
This bug was fixed in the package mountall - 0.2.2
---
mountall (0.2.2) karmic; urgency=low
[ Steve Langasek ]
* Don't emit the local-filesystem signal until after virtual filesystems
are also done mounting. LP: #448981.
[ Robert Gerlach ]
* Fix segfault when root filesy
** Branch linked: lp:~ubuntu-core-dev/ubuntu/karmic/mountall/ubuntu
--
mountpoint does not exist (securityfs, fuse/connections)
https://bugs.launchpad.net/bugs/447525
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailin
I'll check to see whether something makes that directory
--
mountpoint does not exist (securityfs, fuse/connections)
https://bugs.launchpad.net/bugs/447525
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubun
Tell me if I have to update to the faulty version of mountall and give it a
try, as i said I'm allowed to break my system whenever i want.
See ya soon, going out for the saturday night. Bye all.
--
mountpoint does not exist (securityfs, fuse/connections)
https://bugs.launchpad.net/bugs/447525
Y
Here is mine, from a normal boot with mountall v. 0.1.8
on the other hand, I don't have a /sys/kernel/security directory.
** Attachment added: "filesistems"
http://launchpadlibrarian.net/33420232/filesistems
--
mountpoint does not exist (securityfs, fuse/connections)
https://bugs.launchpad.n
Yes, the directory exists, and it is empty.
--
mountpoint does not exist (securityfs, fuse/connections)
https://bugs.launchpad.net/bugs/447525
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists
That's odd, you have securityfs but no /sys/kernel/security
After you boot normally does that directory exist?
--
mountpoint does not exist (securityfs, fuse/connections)
https://bugs.launchpad.net/bugs/447525
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
mich...@mamarley-laptop:~$ cat /proc/filesystems
nodev sysfs
nodev rootfs
nodev bdev
nodev proc
nodev cgroup
nodev cpuset
nodev tmpfs
nodev binfmt_misc
nodev debugfs
nodev securityfs
nodev sockfs
nodev pipefs
nodev anon_inodefs
nodev inotifyfs
nodev devpts
nodev ramf
Thanks for confirming, Michael.
So we have a set of symptoms here that are all the same underlying bug,
missing directories for virtual filesystems that mountall wants to try
and mount. That's a condition that should be dealt with.
I wonder, could you all attach the /proc/filesystems file for me
13 matches
Mail list logo
