On 5/9/2005 4:17 AM Neil Bothwick wrote:
On Sun, 08 May 2005 17:53:26 -0700, Drew Tomlinson wrote:
OK, I've done some more reading and found that the reason I couldn't
use 'su' as myself was because /bin/su didn't have the setuid bit set.
So in all my fooling around, I have file ownership and modes screwed up from the default. What user:group should own all (or most) of the
files after a install? What files should be setuid? Is there a list somewhere? Or will some incantation of 'emerge' fix all of this for
me?
# qpkg -f /bin/su sys-apps/shadow
So "emerge --oneshot shadow" should restore things to their defaults.
Setting the setuid bit on /bin/su and /bin/login fixed my login problems. I'm tried this suggestion and it worked. However I don't quite understand exactly what the "oneshot" option does. The man page says:
Emerge as normal, but do not add the packages to the world profile for later updating.
So it rebuilds it but we don't add it to the world profile because it's part of the "base system" and we wouldn't want it upgraded unless we rebuilt everything else? I'm brand spankin' new to both Linux and Gentoo but I have experience with FreeBSD. In FreeBSD, I know one doesn't want to get his "kernel" and "world" out of sync. Is the idea behind "oneshot" similar to this?
A big THANK YOU to all for helping this "noob" get up to speed.
Drew
-- Visit The Alchemist's Warehouse Magic Tricks, DVDs, Videos, Books, & More!
http://www.alchemistswarehouse.com
-- gentoo-user@gentoo.org mailing list
