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!
Notices
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.
If I understand your question this would do it for the bash shell.
Code:
readonly PATH=$PATH
That readonly directive makes the PATH variable permanent at whatever you set it to. The example is making the PATH variable permanently set to whatever it was already set to.
Last edited by stress_junkie; 07-09-2007 at 06:47 PM.
If I understand your question this would do it for the bash shell.
Code:
readonly PATH=$PATH
That readonly directive makes the PATH variable permanent at whatever you set it to. The example is making the PATH variable permanently set to whatever it was already set to.
and how can I edit mean to say delete something from path??
You edit the file with a text editor. If you want to edit /etc/bash.bashrc (the file may be /etc/bashrc or something different though), you'll need to be root. Obviously if you want to edit the .bashrc in your home directory, you won't need root priviliges.
Unless for specific need, this should not been put in bashrc.
.bashrc is executed for each subshells.
So you login, /etc/profile is executed only once
->PATH=/bin
You open a terminal in your wm for example, bashrc is executed
->PATH=/bin:/your/new/path
In this terminal you open an subshell (like running any script would do) :
$bash
->PATH=/bin:/your/new/path:/your/new/path
Solution is to put it in a profile file (/etc/profile for example)
There are many editors avail on Linux.
Pls add your distribution ie Linux name eg Rh Fedora Core, Suse, Debain, whatever to your profile info (info under your name on posts).
Aslo, add your dektop environment ie KDE or Gnome (probably one of those).
anyway, some editores include:
vi, vim, kedit, gedit, kate, nano, pico etc ....
You'll need to learn at least one of those.
The editor that's avail on all Unix style systems is vi, and a lot these days have the option of vim (means vi improved).
Others may or may not be available.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.