Ken Moffat wrote: > On Sun, Feb 24, 2013 at 04:59:56PM -0600, Randy McMurchy wrote: >> >> We sure do have opposing opinions on that one, Ken. :-) I use sudo in >> my scripts so that I am certain that nothing gets installed in /usr >> unless I know about it. I always install a package as an unprivileged >> user to DESTDIR if I am unfamiliar with it before doing it for real by >> the root user. sudo works great for me. >> > I don't have a problem with that. But I expect my normal builds to > run unattended, I don't expect to sit there waiting to be asked to > authorise each package's installation. BLFS gave me enough > information or pointers to be able to only type my password on the > first package of the script, and from that I realised that it is no > stronger than running the scripts as root. In the current book we > have: > > One example usage is to allow the system administrator to execute > any program without typing a password each time root privileges are > needed. This can be configured as: > > # User alias specification > User_Alias ADMIN = YourLoginId > > # Allow people in group ADMIN to run all commands without a password > ADMIN ALL = NOPASSWD: ALL
You still need to type 'sudo restricted-command'. The above is convenient but possibly dangerous. Depends on your environment and the value of your data. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
