[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#21010: eject fails because of hardcoded path to umount
From: |
Ludovic Courtès |
Subject: |
bug#21010: eject fails because of hardcoded path to umount |
Date: |
Thu, 09 Jul 2015 00:05:11 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux) |
Andreas Enge <address@hidden> skribis:
> On Wed, Jul 08, 2015 at 02:18:21PM +0200, Alex Sassmannshausen wrote:
>> eject: unable to exec /bin/umount of `/mnt/usb'
>
> The culprit is in the source code of util-linux-2.25.2/sys-utils/eject.c:
> 681: execl("/bin/umount", "/bin/umount", name, "-n", NULL);
> 683: execl("/bin/umount", "/bin/umount", name, NULL);
> 685: errx(EXIT_FAILURE, _("unable to exec /bin/umount of `%s'"),
> name);
This should be fixed in core-updates.
> This should be easy to patch, but there are other utilities with the same
> problem. A hopeless case seems to be "whereis": It looks for files in fixed
> lists of locations such as
> static const char *bindirs[] = {
> "/usr/bin",
> "/usr/sbin",
I think we should check what this list is used for, and then prepend
entries accordingly. Volunteering? :-)
Ludo’.