--- randhir phagura <[EMAIL PROTECTED]> wrote: > > >>I tend to automate my install of most 'sub-systems' such as kde etc and > >>have always been doing configure and make as root. Am I doing something > >>wrong? > > >http://www.linuxfromscratch.org/blfs/view/svn/introduction/unpacking.html > > I will have to learn bash scripting to sufficient degree to be able to > become 'root' in the middle of an automating install script, at the 'make > install' stage for each package. As of now, I don't even know if it is > possible at all.
This sounds like a job for 'sudo'. You can grant superuser priveleges for specific programs. Most of your automated script can be performed by the unpriveleged user (tar -xzf /packages/*; cd package; ./configure; make), and then you do 'sudo make install' and that will let your script install the package. I tried these two lines and now sudo lets the user 'chaotic' run '/usr/bin/make' as root without a password; just type 'sudo make install' to in your install script and it will install as root. You can also add additional commands to allow running as root. Cmnd_Alias MAKE=/usr/bin/make chaotic ALL=(ALL) NOPASSWD:MAKE I had trouble connecting to either of the homepages I found referenced. But sometimes my Internet connection is uncooperative: http://freshmeat.net/projects/sudo/ http://www.sudo.ws/sudo/ http://www.courtesan.com/sudo __________________________________ Yahoo! Mail - PC Magazine Editors' Choice 2005 http://mail.yahoo.com -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
