Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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've searched for a couple of hours on the Internet, but can't seem to find the answer to this... I'm running SUSE 9.2 (first ever Linux system), and am far enough along that I want to customize a few things: alter the path for individual users, start a couple of applications on login, etc, etc.
When a user logs into the system, two personal initialization files are called: .bashrc and .profile. This is no surprise. But neither .bash_profile nor .bash_login seems to be called. At least, if I modify PATH in these files, the modifications never take effect.
My problem is this: .bashrc is called three times, and .profile is called twice. This means that whatever initialization I put into these files is repeated. For aliases and the like, this doesn't matter. But for PATH, starting apps, and other things, it matters a lot.
Two possible solutions, but I don't know how to do either:
- prevent multiple invocations of these files
- find some other file (bash_profile, bash_login) that is only called once. But - as mentioned above - these currently seem *never* to be called.
Thanks for the reply. Yes, I am using KDE. And it does seem likely that the multiple executions of .bashrc are because of KDE starting things. But - as I understand the documentation, ".profile" is really only supposed to be executed once, not twice - and this should not be affected by whatever KDE is up to in its initializaiton process.
Putting things in the KDE-startup files may be a solution, but surely it is not the right one. When one logs into the system, this is (as I understand it) before the window manager has started. I would think that one ought to set PATH, and similar things, at that level - independent of KDE or any other window manager.