It is different. Take another look at your printenv example. They are two completely different paths. On BSD, it's exactly the same path. You either get root's environment or you get yours. You don't get a "merging" of the two. that's not how it works.
If you want the functionality of su -c use that. sudo leaves my environment alone so i get a lot of settings that i want but runs apps with an effective uid of root. i happen to like that because it performs as i expect it to. i think i'm missing your argument. you want sudo to perform exactly the same as su? why have sudo, then? bottom line, it sounds like a case of personal preferences. i keep the sbins in my path because i use apps in there regularly. if you don't want to remember where various apps are (as you point out), then maybe you should as well. Ric ----- Original Message ----- From: "William Hubbs" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, April 01, 2003 9:09 AM Subject: Re: [gentoo-user] Re: sudo not setting the path (was sudo not running a shell as a login shell) > I don't see the difference here. On the open bsd system, it appears that the /sbin directories are already in your path, so it isn't an issue. > > With sudo the way it is, you have to type the full path to any command in the > /sbin directories you want to run, but you don't have to with su (even su without the "-"). For example: > > [EMAIL PROTECTED] kc5eiv $ sudo lsmod > sudo: lsmod: command not found > [EMAIL PROTECTED] kc5eiv $ sudo /sbin/lsmod > Module Size Used by Not tainted > [EMAIL PROTECTED] kc5eiv $ su -c lsmod > Password: > Module Size Used by Not tainted > -- [EMAIL PROTECTED] mailing list
