https://bugzilla.novell.com/show_bug.cgi?id=433395 Summary: mkinitrd after su uses ~user/bin/umount instead of /bin/umount Product: openSUSE 10.3 Version: Final Platform: x86-64 OS/Version: Linux Status: NEW Severity: Major Priority: P5 - None Component: Installation AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: 7eggert@gmx.de QAContact: jsrain@novell.com Found By: Community User I created a wrapper for umount, since I don't like to remember if I have to use /bin/umount, /sbin/umount.cifs or "for a in list; do fusermount -u "$a"; done". This creates some amount of bogus error messages when unmounting, but it works better than all alternatives I can think of - except for /bin/umount doing the right thing in the first place. Unfortunately, mkinitrd does not use /bin/umount when creating the initrd, but it copies my wrapper script (being first in the path) to initrd:/bin/umount. This turns out to be a very bad idea. I did not use "su -" because I wanted to stay in the current directory. Obviously I changed pest for cholera. My umount script (In case you're interested) #!/bin/sh for a in "$@" do fusermount -u "$a" || /bin/umount "$a" || /sbin/umount.cifs "$a" done -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.