SlackwareThis Forum is for the discussion of Slackware Linux.
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.
In the initial terminal after booting and before startx, as user and as 'su -', I see the blue directory entries and those light blue files with the ampersands on the end of them and the other white files. And in some directories I see the red files, which appear to be compressed files. And then there are the yellow files in /dev.
If I just do 'su', all the files and directories show up as white, no colors.
Just curious why that is.
Incidentally, this is part of my iniitial foray into slackware and I'm still fairly new to linux in general.
Also, is there a link to some document that describes the different colors used for listing files and directories, or is that just something that you figure out as you go?
its because when you initialy boot up or are a normal user then bash reads profile information from .bashrc or .profile in your home dir and there is probably an alias for ls with color but when you su bash reads the profile info from the /root directory. You can su -m to match profile or -l or somthing else like that to keep your user settings while su'ing.
Oh, ok, I had a similar situation with the PS1 environment variable the other day, but I just today reformatted and reinstalled slackware - because I didn't like the way I had it partitioned.
So, anyway, the initial install of Slackware 9.0 doesn't create any .bashrc files, or .bash_profile files, or .profile files. I will have to create these from scratch.
So, I should be able to put that in my newly created .bash_profile files along with PS1 prompt variable, and then, of course, anything else that comes along as I get the environments set up for su and the user(s).
man dircolors doesn't tell which colors are associated with which file types, but dircolors does apparently set the color.
And I realize that figuring out the colors is just a matter of paying attention.
Distribution: Slackware 10, Fedora Core 3, Mac OS X
the alias thing will need some quote marks in me thinks.
Anyway, the whole colour thing is because of the following fact me thinks. Just using "su" will cause you to hold root priveledges BUT not have root's environment variables. If you login at the login prompt as root, or use su - , then you will have root's environment. This means that you will have the colour thing and certain paths will be there. I found this when I couldn't compile something which you had to be root for. I just su to become root, but this didn't work coz it could never find the right library locations etc. Logged in at the command prompt and tried it and it worked without a hitch.
There are so many nooks and crannies all over the place to explore. Collectively we must know most of them......