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.
i'm using kernels 2.4.24 on slackware 9.1, and i want to start making alias for my bash shell. but when i go to my home directory i can't find that find.
i even did a ls -a command and still no file. does slackware put the bash profiles stuff somewhere else?
Slack (at least as of 9.1) does not create a .bashrc file for you, you have to create it yourself. I'm not too sure that you even need to put #!/bin/bash in the file, but it can't hurt, I'm sure. Good luck.
It doesn't include it because it can use /etc/profile instead. If all users start off with the same default settings, there's no reason to duplicate the settings in a lot of files, so everyone gets /etc/profile to start off with. If they want to customize, that's what .bashrc and .profile are for.
Speaking of which -- djgerbavore -- I may have told you wrong on which file to use. It depends on when you want it to run. If you use .bashrc, when you log in, it apparently won't run, but when you launch an xterm, it will. If you use .profile, when you log in, it will run, but it will not run when you launch an xterm. If you want it to run for both a terminal where you log in AND an xterm, then you need to put the same thing in BOTH .bashrc and .profile. Sorry I wasn't clearer about this earlier.
I've solved this .bashrc and .profile thing by creating an /etc/bashrc file which I source from within /etc/profile. And then I make a symlink from ~/.bashrc to /etc/profile. That way, every user will have the same aliases and stuff, independent on whether it is a login shell or interactive shell, or whatever.