Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I was wondering if there is a SU File Manager out there that I can use in RedHat-9. When I was using ManDrake one was installed with the OS. I got used to using it but now that I have RH if I want to use a graphical file manager with root permissions I have to login to my root account. Of course there is always the terminal but its nice to have both options. Any recommendations?
wicked... thanx man. I'll be memorizing that one for sure. After I tried the command it changed my desktop wallpaper to the one I use with my root login. Not sure if that is whats supposed to happen but its no big deal I can just switch the one in my root account. Thanks again.
I'll keep that in mind Satriani if I ever decide to use KDE as my default desktop. Currently I use Gnome which has certain features that I enjoy. But thanx for the tip.
>Remember that it can be dangerous using a gui with root privilages - it is MUCH easier to delete files<
While we are on the subject.. where does Linux keep all of the critical system data? Microsoft for instance has the c:\windows as a main directory. Does linux have a similar directory or is it more complex then that?
You can also do "kdesu konqueror" (or other File Manager such as nautilus of Midnight Commander) if you have KDE installed. You can do this from Gnome, Window Maker, etc.
As for critical files... They are scattered about, depending on what you consider critical. Most binaries are in:
and /sbin <-- where most "dangerous" binaries live like mkfs, fdisk, killall5, etc. They are only dangerous like a nail gun is dangerous. Perfectly safe if you know what you are doing and pay attention. That's not to say you couldn't reek havoc with other utilities. nice, mail, chown, mount, umount all live in /bin but can cause problems if misused. Like a hammer.
/dev contains "devices" like ports, drives, etc. Deleting these can also screw you up pretty good.
Check out your environment variables by running env in a bash shell and you will see your path.
Originally posted by JZL240I-U Won't kdesu <program> work only with KDE?
Also, as I use KDE, I usually type kdesu <program> & to be rid of one window, or, using a terminal, so as not to freeze the prompt.
If KDE is installed, you can use kdesu in any desktop (at least all of those I have tried; gnome, WM, Sawfish, etc). True, the & will not freeze the prompt, I was thinking of right clicking in Window Maker (my primary desktop), select run from the menu and enter kdesu [whatever] which doesn't spawn a (visible) shell and hang the prompt.
Not sure why they are scattered. That would be a good question for Linus... Probably because UNIX is based that way.
To find where a binary lives, from a shell, type which [command-goes-here]. IE: which chown will return /bin/chown (at least in RH anyway). Of course you have to have rights to the file and it has to be in your path (either explicit or inherited).