Showing posts with label Shell. Show all posts
Showing posts with label Shell. Show all posts

Wednesday, January 09, 2008

No More Beeping

*NIX Quick Tip

Beep, beep, beep,
If your like me and don't like auditory reminders, you can turning off the beeping quickly and easily:

X Windows
If you want to disable beeps in X11 (X Windows), you can turn them off with the command:
# xset b off
*Note: you will need to login as root or use sudo.

csh and tcsh
You can disable csh and tcsh shell terminal beep if you put `set nobeep' (no quotes) in your ~/.cshrc file.

This options will work on most *nix systems (using csh/tcsh or X windows), including Ubuntu, FreeBSD, and OpenBSD, however I tested this solution using FreeBSD.

Wednesday, December 12, 2007

Changing Environmental Variables

It's really handy to be able to change the way your shell works for you. Being able to add aliases, and other options makes the shell a much more powerful tool. Changing or setting environmental variables is done differently for each shell.

To change an environment variable in csh or tcsh use:$ setenv NAME "value"where NAME is the name of the variable and "value" its new value.

To change an environment variable in /bin/sh use:
$ VARIABLE="value"
$ export VARIABLE

You can permanently set environment variables for your shell by putting them in a startup file for the shell. The name of the startup file varies depending on the shell;
csh and tcsh uses .login,
bash, sh, ksh and zsh use .profile.
When using bash, sh, ksh or zsh, don't forget to export the variable.

*Note:
.login and .profile are to set conditions which apply to the whole session and to perform actions that are relevant only at login.

.cshrc and .shrc are used to set conditions and perform actions specific to the shell and to each invocation of it.
The guidelines are to set ENVIRONMENT variables in the .login, .profile file and SHELL variables in the .cshrc, .shrc files.