[Bug 798447] Re: item_in_dir() shell function does not handle missing directory
Launchpad Bug Tracker
798447 at bugs.launchpad.net
Sun Jul 24 10:08:28 UTC 2011
This bug was fixed in the package os-prober - 1.48
---------------
os-prober (1.48) unstable; urgency=low
[ Colin Watson ]
* Depend on grub-mount-udeb (see changelog for 1.45).
* item_in_dir: return 1 immediately if second argument is not a directory
(thanks, Daniel Richard G.; LP: #798447).
[ Otavio Salvador ]
* add MeeGo detection support; thanks to Chengwei Yang
<chengwei.yang at intel.com> for the patch.
* Fix Windows detection when there are more then one boot directories
(e.g boot and Boot). Closes: #634649.
-- Colin Watson <cjwatson at canonical.com> Sun, 24 Jul 2011 10:06:55 +0000
** Changed in: os-prober (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to os-prober in Ubuntu.
https://bugs.launchpad.net/bugs/798447
Title:
item_in_dir() shell function does not handle missing directory
Status in “os-prober” package in Ubuntu:
Fix Released
Bug description:
Binary package hint: os-prober
This concerns os-prober 1.44ubuntu1 in Ubuntu Natty.
When I invoke update-grub(8) in a certain chroot'ed Ubuntu
installation, I see this:
Generating grub.cfg ...
Found linux image: /boot/vmlinuz-2.6.38-8-generic
Found initrd image: /boot/initrd.img-2.6.38-8-generic
Found memtest86+ image: /boot/memtest86+.bin
No volume groups found
ls: cannot access /config: No such file or directory
ls: cannot access /config: No such file or directory
ls: cannot access /config: No such file or directory
ls: cannot access /config: No such file or directory
ls: cannot access /config: No such file or directory
ls: cannot access /config: No such file or directory
ls: cannot access /config: No such file or directory
done
I have a filesystem mounted on /config outside of the chroot. Because
the system /proc directory is bind-mounted inside the chroot,
/proc/mounts shows the /config mount, even though it is not
accessible.
I traced the operation of update-grub(8) to see what was producing the
ls(1) errors, leading me to to the item_in_dir() function in
/usr/share/os-prober/common.sh. Adding the following line to it, in
the appropriate place...
[ -d "$2" ] || return 1
...makes the problem go away.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/os-prober/+bug/798447/+subscriptions
More information about the foundations-bugs
mailing list