This bug was fixed in the package os-prober - 1.34
---------------
os-prober (1.34) unstable; urgency=low
* Only look for a smart version of mount if we're using busybox mount. In
a normal system, mount probably already handles labels and UUIDs, and
using mount from another filesystem is risky enough that it's worth
avoiding if possible.
* Memoise calls to 'basename $0' in log function.
* Handle escaped special characters in /etc/fstab and /proc/mounts
(LP: #433910).
* dash defines test's -nt operator differently from bash, as it's entitled
to do since this is an extension not defined in POSIX. If file1 exists
and file2 does not, bash returns true but dash returns false. Don't rely
on bash's behaviour when checking whether to use GRUB Legacy or GRUB 2
configuration files, otherwise we end up using neither when only one set
of configuration exists and /bin/sh is dash.
* Try to map LABEL= and UUID= ourselves in linux_mount_boot rather than
relying on mount to do it, to further reduce the chance that we need to
use mount from another filesystem.
* If the filesystem identified by linux-boot-prober as /boot is already
mounted somewhere else, then bind-mount it rather than trying to mount
it again.
-- Colin Watson <cjwat...@canonical.com> Tue, 22 Sep 2009 10:30:45
+0100
** Changed in: os-prober (Ubuntu)
Status: In Progress => Fix Released
--
Fails when mount point has a space
https://bugs.launchpad.net/bugs/433910
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://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
