For one, it's pretty poor programming practice to assume path of any
kind.
Second, there are calls to other binaries with full path in this script
as it is, some even in /sbin:
grep bin /usr/sbin/update-grub
[ -x /sbin/mdadm ] || return 1
uuid=$(/sbin/vol_id -u "$dev" || true)
uuid=$(/sbin/vol_id -u "$root" || true)
if [ -x "/usr/bin/makedumpfile" ] && [ -x
"/sbin/kexec"]; then
if test -f "/boot/$name.bin" ; then
kernel="$kernel_dir/$name.bin"
for kern in $(/bin/ls -1vr /boot | grep -v "dpkg-*" | grep "^vmlinuz-") ; do
--
Brandon J. Schwartz
IT Engineer, Sr.
brand...@qualcomm.com
x17208
Steve Langasek wrote:
> Thank you for reporting this issue and helping to improve Ubuntu.
>
> /sbin is in the default path for all users on Ubuntu, and update-grub is
> an admin-only tool which implies only users who already have /sbin in
> their path ought to be running it. Is there some other reason that we
> should regard this as a bug in grub, as opposed to a user configuration
> error?
>
--
update-grub errors out on findfs
https://bugs.launchpad.net/bugs/397548
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
