>C. Lastly, the normal user acc't created at installation does not >have sudo permissions. I've rooted, so to speak, around in the >Control Center for user administration while logged in as root. I >did find one panel that seemed to fit the bill and a huge list of >policies and groups, some seemingly overlapping, was presented to me. >I remember checking RPM, adm, floppy, and a couple others but >superuser or su or other obvious abbrev was not there. What >combination of groups/policies would allow me to sudo?
Find out if you have sudo installed 'rpm -qa|grep sudo' Find out what files are installed by the sudo package, and pick out ones in /etc 'rpm -ql sudo|grep etc' That should be the config file 'man sudo' >D. One other lastly, I'd like to run the distributed.net client as a >startup item. Where should I put either the d.net files or alias? >Additionally, I created a folder in my Home directory with the d.net >stuff and when I clicked on the app in KDE, nothing happened so I >opened a terminal window and did the ./dnetc command. I thought I >could just type dnetc and the app would launch. Again, do I need to >relocate the folder/files somewhere else? Put an entry in rc.local, which is where I normally put things like this. The file should be /etc/rc.d/rc.local. Make sure you use the full path to the executable, it is a good practice for _any_ script as you can't always know what the local directory will be when a script is called. As far as where in the filesystem the executable should go, rpm places executables, and if you installed it from source, the 'make install' should have also placed it in a standardized location. I would keep it there unless it is outside your $PATH. If you are issuing './dnetc' that would mean it is in your home directory, which is a non-standard location. I would consult the documentation for that package to find the standard location for the binaries. If the executable is not written to run as a daemon or have a command line switch (-d for example) to put it into deamon mode, use a ampersand (&) after the command to run it in the background. >This is my first experience installing and administering a *NIX--I've >only very loosely had exposure on a college campus with Unix just as >a terminal user. Maybe a couple here know me from the Supermacs >list. I'll do my best not to annoy or irritate the longtime Unix >veterans with two year old toddler questions while I'm learning how >to walk and talk this new language. Thanks for your patience. http://www.tldp.org - The Linux Documentation Project 'man' is your friend, some packages have additional documentation in 'info' format, that is type 'info sudo'. Some packages install documentation in /usr/doc too. Good Luck. -- Charles Dostale System Administrator Silver Oaks Communications http://www.silveroaks.com 824 17th Street Moline IL USA 61265 [EMAIL PROTECTED] 309-797-9898 -- MaX-list is sponsored by <http://lowendmac.com/> and... / Buy books, CDs, videos, and more from Amazon.com \ / <http://www.amazon.com/exec/obidos/redirect-home/lowendmac> \ Support Low End Mac <http://lowendmac.com/lists/support.html> MaX-list info: <http://lowendmac.com/linux/max.shtml> Send list messages to: <mailto:[EMAIL PROTECTED]> To unsubscribe, email: <mailto:[EMAIL PROTECTED]> For digest mode, email: <mailto:[EMAIL PROTECTED]> Subscription questions: <mailto:[EMAIL PROTECTED]> Archive: <http://www.mail-archive.com/max-list%40mail.maclaunch.com/> Using a Macintosh? Get free email and more at Applelinks! <http://www.applelinks.com>
