On Sat, Oct 14, 2006 at 07:12:20PM +0100, Paul LeoNerd Evans wrote: > > In such emergency cases as > > linux init=/bin/sh > > it is useful to have such tools as 'passwd' in /bin, in case /usr isn't > mounted. Having /usr on LVM, for example, requires a number of steps to > make it work. It would be useful if a forgotten root password, say, can > be reset using only tools in the root filing system.
Why do you need passwd when "linux init=/bin/sh"? Are you using "linux init=/bin/sh" to reset users' passwords? I don't think moving tools to /bin is the way to fix unrelated issues. Unless we receive additional arguments, I will close this bug in one or two weeks. Kind Regards, -- Nekral > > -- System Information: > Debian Release: testing/unstable > APT prefers testing > APT policy: (990, 'testing'), (500, 'unstable') > Architecture: i386 (i686) > Shell: /bin/sh linked to /bin/bash > Kernel: Linux 2.6.16-mh3.nim > Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) > > Versions of packages passwd depends on: > ii debianutils 2.17 Miscellaneous utilities specific > t > ii libc6 2.3.6.ds1-4 GNU C Library: Shared libraries > ii libpam-modules 0.79-3.2 Pluggable Authentication Modules > f > ii libpam0g 0.79-3.2 Pluggable Authentication Modules > l > ii libselinux1 1.30.28-2 SELinux shared libraries > ii login 1:4.0.18.1-3 system login tools > > passwd recommends no packages. > > -- debconf information excluded > > > _______________________________________________ > Pkg-shadow-devel mailing list > [EMAIL PROTECTED] > http://lists.alioth.debian.org/mailman/listinfo/pkg-shadow-devel > > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
