🚀 go-pugleaf

"Mark Greatrix" <mgreatri@NOSPAM.anasazi.com> writes:

> To change your shell back to bash, edit your /etc/passwd file, go to the
> line corresponding to the user you want to change.  at the end of the line,
> if there is an entry for a shell, change it to
> /bin/bash or if there is no shell specified, add it

*NO*!!! This is why most sys-admins hate Linux users. You use the "chsh"
command to change the shell, because this prevents screwing up the
rest of the password file with accidental typos or selecting a
non-registered shell. All registered shells should be listed in
/etc/shells, so people can change to them at will.

Editing the password file directly without need is foolish. It's even
more foolish to just "edit" it without using the "vipw" command, which
*also* does consistency checks on the password file and edits it in a
temporary file to prevent accidents.


>     If you want to use tcsh, I believe the file to edit is call '.login',
> again in the home dir

You want to edit ".cshrc" for csh, and ".cshrc" or ".tcshrc" for tcsh.


>                 set path=( $HOME/bin   /usr/bin   /pdl/bin  )
> 
>     just add your new one in:-
> 
>                 set path=( $HOME/bin   /usr/bin   /pdl/bin
> /newentry/newentry )

If you are adding modular custom stuff, it is often better to write it
as two separate lines:

                set path=(~/bin /usr/bin /usr/local/bin )
		set path=($path /newentry/newentry )

This makes re-arranging your path to get the correct version of programs
with common names much easier.

-- 
				Nico Garcia
				raoul@tiac.net
<PGP is obviously a good idea: look at who objects to it.>