variable name to output the value, like this:
Click here to view code image
matthew@seymour:~$ echo $TERM
xterm
You can redirect the output of echo into a text file, as is done here to add a
new directory to PATHs:
Click here to view code image
matthew@seymour:~$ echo 'export PATH=$PATH:/usr/local/bin' >>
~/.bashrc
You can change or set a kernel setting ( 1 = on, 0 = off) in /proc, like this:
Click here to view code image
matthew@seymour:~$ sudo sh -c 'echo "1" >
/proc/sys/location/of/setting'
Note that you can read the setting of a kernel value in /proc by using cat.
Finding Files by Searching with find
The find command is one of the darkest and least understood areas of
Linux, but it is also one of the most powerful. Admittedly, the find
command does not help itself by using X-style parameters. The UNIX
standard is -c, -s, and so on, whereas the GNU standard is
—dosomething, —mooby, and so forth. X-style parameters merge the two
by having words preceded by only one dash.
However, the biggest problem with find is that it has more options than
most people can remember; it truly is capable of doing most things you could
want. The most basic usage is as follows:
Click here to view code image
matthew@seymour:~$ find -name "*.txt"
This option searches the current directory and all subdirectories for files that
end in .txt. The previous search finds files ending in .txt but not .TXT,
.Txt, or other case variations. To search without case-sensitivity, use -
iname rather than -name. You can optionally specify where the search
should start before the -name parameter, like this:
Click here to view code image
matthew@seymour:~$ find /home -name "*.txt"