Description of problem:
/sbin/mount.tmpfs will emit error messages at boot time, and fails to turn
off restricted mode, if two conditions are met:
1. A tmpfs filesystem is used (listed in /etc/fstab).
2. /usr is a separate filesystem, mounted after a tmpfs filesystem.
The problem is simply that /sbin/mount.tmpfs uses 'id', which is in
/usr/bin/id, and hence not yet available.
Version-Release number of selected component (if applicable):
(The error message is emitted by /sbin/mount.tmpfs, but the easy fix is
to coreutils; see "Additional info" below.)
Steps to Reproduce:
A tmpfs filesystem in /etc/fstab, e.g.:
tmpfs /tmp tmpfs defaults 0 0
A separate /usr filesystem, listed after tmpfs in /etc/fstab .
Then boot (single-user will do).
On the system console (also in /var/log/boot.log):
Mounting local filesystems: /sbin/mount.tmpfs: line 22: id: command not found
/sbin/mount.tmpfs: line 23: id: command not found
/sbin/mount.tmpfs: line 25: [: -eq: unary operator expected
No error messages after "Mounting local filesystems".
Two possibilities to fix:
1. Change the location of 'id' from /usr/bin/id to /bin/id, in the coreutils
2. Make all the 'id' code in /sbin/mount.tmpfs be conditional on
'type -t id >/dev/null', and if that fails, assume it's boot time, and
set restricted=0 . (No, I don't like it either.)
It looks like the use of 'id' was introduced with rhbz 616393 .
well... there are several binaries in coreutils which were moved from /usr/bin to /bin ... most recent one was readlink. Solution with keeping symlink in /usr/bin and moving binary into /bin is safe enough, however I don't want to polute /bin with more binaries. Anyway, id doesn't depend on anything from /usr/lib, so it is safe to move it.
Karel, as you are the maintainer of /sbin/mount.tmpfs ... which possibility do you prefer?
oh... I don't need id(1) at all (see bug #620924). The bash provides all necessary information in $UID and $EUID. From my point of view you can close this issue.
Ok, thanks ... closing duplicate...
*** This bug has been marked as a duplicate of bug 620924 ***