This is actually caused by a design issue between "mountall" and init,
where if a filesystem fails to mount/fsck a shell is started. The
timing for you makes it appear to happen due to lynx. Can you verify
that the spawned shell has init as a parent, rather than lynx? (output
of "pstree -lap" should help.)
** Changed in: lynx-cur (Ubuntu)
Status: New => Incomplete
--
lynx goes to a root shell
https://bugs.launchpad.net/bugs/492745
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
