Web   ·   Wiki   ·   Activities   ·   Blog   ·   Lists   ·   Chat   ·   Meeting   ·   Bugs   ·   Git   ·   Translate   ·   Archive   ·   People   ·   Donate
summaryrefslogtreecommitdiffstats
path: root/help
diff options
context:
space:
mode:
authorroot <root@ghunt-desktop.(none)>2010-12-19 17:55:02 (GMT)
committer root <root@ghunt-desktop.(none)>2010-12-19 17:55:02 (GMT)
commit16fc1eeb4fb1673d0e12338a5d726185bd72431a (patch)
tree4f31bb9779b8583a36a17ac028fd4970624baa0f /help
parent0b27ac481cdd8695e87908baf538350b28229376 (diff)
version 7,additional help, embeds remembered across invocations
Diffstat (limited to 'help')
-rw-r--r--help/en/PyDebug.htm11
-rw-r--r--help/en/bash/alias.html120
-rw-r--r--help/en/bash/apt-get.html506
-rw-r--r--help/en/bash/aptitude.html857
-rw-r--r--help/en/bash/aspell.html90
-rw-r--r--help/en/bash/awk.html247
-rw-r--r--help/en/bash/basename.html70
-rw-r--r--help/en/bash/bc.html133
-rw-r--r--help/en/bash/bg.html64
-rw-r--r--help/en/bash/break.html75
-rw-r--r--help/en/bash/builtin.html77
-rw-r--r--help/en/bash/cal.html75
-rw-r--r--help/en/bash/case.html85
-rw-r--r--help/en/bash/cat.html97
-rw-r--r--help/en/bash/cd.html98
-rw-r--r--help/en/bash/cfdisk.html540
-rw-r--r--help/en/bash/chgrp.html92
-rw-r--r--help/en/bash/chkconfig.html110
-rw-r--r--help/en/bash/chmod.html373
-rw-r--r--help/en/bash/chown.html131
-rw-r--r--help/en/bash/chroot.html69
-rw-r--r--help/en/bash/cksum.html67
-rw-r--r--help/en/bash/cmp.html124
-rw-r--r--help/en/bash/comm.html92
-rw-r--r--help/en/bash/command.html85
-rw-r--r--help/en/bash/continue.html75
-rw-r--r--help/en/bash/copyright.html169
-rw-r--r--help/en/bash/cp.html124
-rw-r--r--help/en/bash/cron.html94
-rw-r--r--help/en/bash/crontab.html132
-rw-r--r--help/en/bash/csplit.html144
-rw-r--r--help/en/bash/cut.html113
-rw-r--r--help/en/bash/date.html318
-rw-r--r--help/en/bash/dc.html94
-rw-r--r--help/en/bash/dd.html126
-rw-r--r--help/en/bash/ddrescue.html90
-rw-r--r--help/en/bash/declare.html107
-rw-r--r--help/en/bash/df.html170
-rw-r--r--help/en/bash/diff.html438
-rw-r--r--help/en/bash/diff3.html179
-rw-r--r--help/en/bash/dig.html129
-rw-r--r--help/en/bash/dir.html56
-rw-r--r--help/en/bash/dircolours.html82
-rw-r--r--help/en/bash/dirname.html61
-rw-r--r--help/en/bash/dirs.html81
-rw-r--r--help/en/bash/dmesg.html76
-rw-r--r--help/en/bash/du.html161
-rw-r--r--help/en/bash/echo.html121
-rw-r--r--help/en/bash/egrep.html92
-rw-r--r--help/en/bash/eject.html172
-rw-r--r--help/en/bash/enable.html89
-rw-r--r--help/en/bash/env.html92
-rw-r--r--help/en/bash/eval.html65
-rw-r--r--help/en/bash/exec.html85
-rw-r--r--help/en/bash/exit.html57
-rw-r--r--help/en/bash/expand.html81
-rw-r--r--help/en/bash/export.html83
-rw-r--r--help/en/bash/expr.html198
-rw-r--r--help/en/bash/false.html64
-rw-r--r--help/en/bash/fdformat.html87
-rw-r--r--help/en/bash/fdisk.html192
-rw-r--r--help/en/bash/fg.html61
-rw-r--r--help/en/bash/fgrep.html68
-rw-r--r--help/en/bash/find.html514
-rw-r--r--help/en/bash/fmt.html118
-rw-r--r--help/en/bash/fold.html89
-rw-r--r--help/en/bash/for.html99
-rw-r--r--help/en/bash/fsck.html94
-rw-r--r--help/en/bash/function.html91
-rw-r--r--help/en/bash/fuser.html146
-rw-r--r--help/en/bash/getopts.html89
-rw-r--r--help/en/bash/grep.html301
-rw-r--r--help/en/bash/groups.html61
-rw-r--r--help/en/bash/gzip.html170
-rw-r--r--help/en/bash/hash.html73
-rw-r--r--help/en/bash/head.html99
-rw-r--r--help/en/bash/history.html266
-rw-r--r--help/en/bash/hostname.html70
-rw-r--r--help/en/bash/id.html93
-rw-r--r--help/en/bash/if.html81
-rw-r--r--help/en/bash/ifconfig.html142
-rw-r--r--help/en/bash/ifup.html89
-rw-r--r--help/en/bash/import.html212
-rw-r--r--help/en/bash/index.html283
-rw-r--r--help/en/bash/install.html140
-rw-r--r--help/en/bash/jobs.html79
-rw-r--r--help/en/bash/join.html138
-rw-r--r--help/en/bash/kill.html98
-rw-r--r--help/en/bash/killall.html144
-rw-r--r--help/en/bash/less.html276
-rw-r--r--help/en/bash/let.html59
-rw-r--r--help/en/bash/ln.html161
-rw-r--r--help/en/bash/local.html71
-rw-r--r--help/en/bash/locate.html71
-rw-r--r--help/en/bash/logname.html68
-rw-r--r--help/en/bash/logout.html75
-rw-r--r--help/en/bash/look.html68
-rw-r--r--help/en/bash/lpc.html156
-rw-r--r--help/en/bash/lpr.html190
-rw-r--r--help/en/bash/lprm.html122
-rw-r--r--help/en/bash/ls.html212
-rw-r--r--help/en/bash/lsof.html1194
-rw-r--r--help/en/bash/man.html83
-rw-r--r--help/en/bash/mkdir.html68
-rw-r--r--help/en/bash/mkfifo.html66
-rw-r--r--help/en/bash/mknod.html76
-rw-r--r--help/en/bash/mmv.html316
-rw-r--r--help/en/bash/more.html149
-rw-r--r--help/en/bash/mount.html180
-rw-r--r--help/en/bash/mtools.html91
-rw-r--r--help/en/bash/mtr.html129
-rw-r--r--help/en/bash/mv.html118
-rw-r--r--help/en/bash/nice.html81
-rw-r--r--help/en/bash/nl.html156
-rw-r--r--help/en/bash/nohup.html76
-rw-r--r--help/en/bash/nslookup.html128
-rw-r--r--help/en/bash/op.html122
-rw-r--r--help/en/bash/open.html59
-rw-r--r--help/en/bash/passwd.html89
-rw-r--r--help/en/bash/paste.html71
-rw-r--r--help/en/bash/ping.html159
-rw-r--r--help/en/bash/pkill.html126
-rw-r--r--help/en/bash/popd.html72
-rw-r--r--help/en/bash/pr.html166
-rw-r--r--help/en/bash/printf.html148
-rw-r--r--help/en/bash/ps.html288
-rw-r--r--help/en/bash/pushd.html71
-rw-r--r--help/en/bash/pwd.html61
-rw-r--r--help/en/bash/quota.html94
-rw-r--r--help/en/bash/quotacheck.html104
-rw-r--r--help/en/bash/quotactl.html112
-rw-r--r--help/en/bash/ram.html61
-rw-r--r--help/en/bash/rcp.html70
-rw-r--r--help/en/bash/read.html119
-rw-r--r--help/en/bash/readonly.html76
-rw-r--r--help/en/bash/rem.html61
-rw-r--r--help/en/bash/rename.html65
-rw-r--r--help/en/bash/return.html64
-rw-r--r--help/en/bash/rev.html65
-rw-r--r--help/en/bash/rm.html91
-rw-r--r--help/en/bash/rmdir.html71
-rw-r--r--help/en/bash/rsync.html484
-rw-r--r--help/en/bash/scp.html164
-rw-r--r--help/en/bash/screen.html138
-rw-r--r--help/en/bash/sdiff.html170
-rw-r--r--help/en/bash/sed.html161
-rw-r--r--help/en/bash/select.html91
-rw-r--r--help/en/bash/seq.html86
-rw-r--r--help/en/bash/set.html211
-rw-r--r--help/en/bash/shift.html69
-rw-r--r--help/en/bash/shopt.html211
-rw-r--r--help/en/bash/shutdown.html86
-rw-r--r--help/en/bash/sleep.html68
-rw-r--r--help/en/bash/slocate.html103
-rw-r--r--help/en/bash/sort.html345
-rw-r--r--help/en/bash/source.html82
-rw-r--r--help/en/bash/split.html96
-rw-r--r--help/en/bash/ssh.html896
-rw-r--r--help/en/bash/su.html124
-rw-r--r--help/en/bash/sudo.html194
-rw-r--r--help/en/bash/sum.html72
-rw-r--r--help/en/bash/suspend.html60
-rw-r--r--help/en/bash/symlink.html125
-rw-r--r--help/en/bash/sync.html63
-rw-r--r--help/en/bash/syntax.html65
-rw-r--r--help/en/bash/tail.html196
-rw-r--r--help/en/bash/tar.html523
-rw-r--r--help/en/bash/tee.html81
-rw-r--r--help/en/bash/test.html256
-rw-r--r--help/en/bash/time.html228
-rw-r--r--help/en/bash/times.html59
-rw-r--r--help/en/bash/top.html119
-rw-r--r--help/en/bash/touch.html111
-rw-r--r--help/en/bash/tr.html303
-rw-r--r--help/en/bash/traceroute.html132
-rw-r--r--help/en/bash/true.html69
-rw-r--r--help/en/bash/tsort.html96
-rw-r--r--help/en/bash/tty.html78
-rw-r--r--help/en/bash/type.html78
-rw-r--r--help/en/bash/ulimit.html96
-rw-r--r--help/en/bash/umask.html76
-rw-r--r--help/en/bash/uname.html102
-rw-r--r--help/en/bash/unexpand.html83
-rw-r--r--help/en/bash/uniq.html107
-rw-r--r--help/en/bash/units.html308
-rw-r--r--help/en/bash/unset.html70
-rw-r--r--help/en/bash/unshar.html109
-rw-r--r--help/en/bash/until.html58
-rw-r--r--help/en/bash/useradd.html114
-rw-r--r--help/en/bash/usermod.html87
-rw-r--r--help/en/bash/users.html70
-rw-r--r--help/en/bash/uuencode.html97
-rw-r--r--help/en/bash/vi.html301
-rw-r--r--help/en/bash/vmstat.html152
-rw-r--r--help/en/bash/watch.html132
-rw-r--r--help/en/bash/wc.html100
-rw-r--r--help/en/bash/whereis.html101
-rw-r--r--help/en/bash/which.html150
-rw-r--r--help/en/bash/while.html59
-rw-r--r--help/en/bash/who.html125
-rw-r--r--help/en/bash/whoami.html59
-rw-r--r--help/en/bash/write.html69
-rw-r--r--help/en/bash/xargs.html159
-rw-r--r--help/en/bash/xdg-open.html76
-rw-r--r--help/en/bash/yes.html60
-rw-r--r--help/en/term_tools/images/bash-l.gifbin0 -> 1442 bytes
-rw-r--r--help/en/term_tools/images/bash-r.gifbin0 -> 947 bytes
-rw-r--r--help/en/term_tools/images/forum-r.gifbin0 -> 434 bytes
-rw-r--r--help/en/term_tools/images/links-r.gifbin0 -> 1407 bytes
-rw-r--r--help/en/term_tools/images/nt-r.gifbin0 -> 1510 bytes
-rw-r--r--help/en/term_tools/images/oracle-r.gifbin0 -> 1656 bytes
-rw-r--r--help/en/term_tools/images/osx-r.gifbin0 -> 961 bytes
-rw-r--r--help/en/term_tools/images/ps-r.gifbin0 -> 1296 bytes
-rw-r--r--help/en/term_tools/images/roll-left.pngbin0 -> 3601 bytes
-rw-r--r--help/en/term_tools/images/roll-right.pngbin0 -> 3926 bytes
-rw-r--r--help/en/term_tools/images/sql-r.gifbin0 -> 2091 bytes
-rw-r--r--help/en/term_tools/images/ss64.gifbin0 -> 682 bytes
-rw-r--r--help/en/term_tools/images/ss64.pngbin0 -> 1367 bytes
-rw-r--r--help/en/term_tools/images/syntax-r.gifbin0 -> 1563 bytes
-rw-r--r--help/en/term_tools/images/top-4.gifbin0 -> 1327 bytes
-rw-r--r--help/en/term_tools/images/vb-r.gifbin0 -> 678 bytes
-rw-r--r--help/en/term_tools/index.html103
-rw-r--r--help/en/term_tools/library/library.info9
-rw-r--r--help/en/term_tools/links/bash-kier-ubuntu.jpgbin0 -> 2002 bytes
-rw-r--r--help/en/term_tools/links/bash.html161
-rw-r--r--help/en/term_tools/links/linuxnutshell.gifbin0 -> 3494 bytes
-rw-r--r--help/en/term_tools/links/nix_essential.jpgbin0 -> 6455 bytes
-rw-r--r--help/en/term_tools/links/sobell.jpgbin0 -> 4667 bytes
-rw-r--r--help/en/term_tools/links/unixkochan.gifbin0 -> 3819 bytes
-rw-r--r--help/en/term_tools/links/unixpowertools.jpgbin0 -> 3706 bytes
-rw-r--r--help/en/term_tools/main.css33
-rw-r--r--help/en/term_tools/robots.txt15
-rw-r--r--help/en/term_tools/rss.xml50
233 files changed, 29397 insertions, 5 deletions
diff --git a/help/en/PyDebug.htm b/help/en/PyDebug.htm
index ae3a04d..603d601 100644
--- a/help/en/PyDebug.htm
+++ b/help/en/PyDebug.htm
@@ -3,7 +3,7 @@
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
<title>Untitled Document</title>
-<link href="CSS/Georgia.css" rel="stylesheet" type="text/css" />
+<link href="pydebug/CSS/Georgia.css" rel="stylesheet" type="text/css" />
<script type="text/javascript">
function message()
{
@@ -11,13 +11,14 @@ alert("This alert box was called with the onload event");
}
</script></head>
-<body onload="message()">
+<body> <!-- onload="message()"> -->
<script type="text/javascript">
//document.write('width:' + window.screen.width + " height:" + window.screen.height);
</script> <h3 class="header">PyDebug Help System</h3>
-<img class="right" src="images/3080617962_604fcfe2ed.jpg" width="450" height="325" align="top" />
-<p><a href="application.html">Introduction to the Debugger Pages, features</a></p>
- <p> <a href="debugging.html">How to use the Debugger</a> -- set breakpoints, step, examine variables, use <a href="IPython/interactive/index.html">IPython</a> </p>
+<img class="right" src="pydebug/images/3080617962_604fcfe2ed.jpg" width="450" height="325" align="top" />
+<p><a href="pydebug/application.html">Introduction to the Debugger Pages, features</a></p>
+ <p> <a href="pydebug/debugging.html">How to use the Debugger</a> -- set breakpoints, step, examine variables, use <a href="pydebug/IPython/interactive/index.html">IPython.</a></p>
+ <p><a href="pydebug/lessons.html">10 Tutorial Exercises</a> to help learn programming.</p>
<p><a href="ActivityBook/ActivitiesGuideSugar__Introduction.html">Making Sugar Activities</a> by Jim Simmons</p>
<p>Examine the software on your machine using<a href="http://localhost:23432"> PyDoc </a>documentation generator </p>
<p>Learning Python</p>
diff --git a/help/en/bash/alias.html b/help/en/bash/alias.html
new file mode 100644
index 0000000..6513e02
--- /dev/null
+++ b/help/en/bash/alias.html
@@ -0,0 +1,120 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>alias MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> alias</h1>
+<p>Create an alias, aliases allow a string to be substituted for a word when it
+is used as the first word of a simple command. </p>
+<pre>Syntax
+ alias [-p] [<i>name</i>[=<i>value</i>] ...]
+
+ unalias [-a] [<var>name</var> ... ]
+
+Key
+ -p Print the current values
+
+ -a Remove All aliases</pre>
+<p> If arguments are supplied, an alias is defined for each name whose value is
+ given. </p>
+<p>If no value is given, `alias' will print the current value of the alias. <br>
+ <br>
+ Without arguments or with the `-p' option, alias prints the list of aliases
+ on the standard output in a form that allows them to be reused as input. </p>
+<p>name may not be `alias' or `unalias'.</p>
+<p>unalias may be used to remove each <i>name </i>from the list of defined aliases.</p>
+<p><b>Examples</b></p>
+<p> Create an alias 'ls' that will change the default action of ls:<br>
+
+<span class="code">$ alias ls='ls --classify'<br>
+$ ls <br>
+$ unalias ls</span></p>
+<p>More aliases for ls:<span class="code"><br>
+$ alias la='ls -lAXh --color=always' &nbsp;&nbsp;#Show all, sort by extension <br>
+</span>
+<span class="code">$ alias ls-al='ls -al' &nbsp;&nbsp;#fix typo missing space <br>
+</span>
+<span class="code">$ alias l=&quot;ls -l&quot;<br>
+$ alias la=&quot;ls -la&quot;</span></p>
+<p>Use alias to fix missing space typos:<br>
+<span class="code"> $ alias cd..='cd ..'<br>
+$ </span>
+<span class="code">alias ..='cd ..'<br>
+<br>
+</span>Display the working directory<span class="code"> <br>
+$ alias .='echo $PWD'</span></p>
+<p>Prevent accidental deletions by making <a href="rm.html">rm</a> interactive: <br>
+<span class="code">$ alias rm='rm -i'</span></p>
+<p>Shorten apt-get installation commands: <br>
+<span class="code">$ alias canhaz='sudo apt-get install'</span></p>
+<p>Run firefox and open a specific website:<br>
+<span class="code">$ alias fftr='/home/simon/firefox/firefox http://ss64.com'</span><br>
+ <br>
+<b>Make an alias permanent</b></p>
+<p> Use your favorite text editor to create a file called <b><span class="code">~/</span>.bash_aliases</b>, and type
+ the alias commands into the file. <br>
+<b>.bash_aliases</b> will run at login (or you can just execute it with <b>..bash_aliases</b> )</p>
+<p><b>Details</b><br>
+<br>
+The first word of each simple command, if unquoted, is checked to see if it has an alias. If so, that word is replaced by the text of the alias. The alias name and the replacement text may contain any valid shell input, including shell metacharacters, with the exception that the alias name may not contain `='. <br>
+<br>
+The first word of the replacement text is tested for aliases, but a word that is identical to an alias being expanded is not expanded a second time. This means that one may alias ls to "ls -F", for instance, and Bash does not try to recursively expand the replacement text. <br>
+<br>
+If the last character of the alias value is a space or tab character, then the next command word following the alias is also checked for alias expansion. <br>
+<br>
+There is no mechanism for using arguments in the replacement text, as in csh. If arguments are needed, a shell function should be used . Aliases are not expanded when the shell is not interactive, unless the expand_aliases shell option is set using shopt . <br>
+<br>
+The rules concerning the definition and use of aliases are somewhat confusing. Bash always reads at least one complete line of input before executing any of the commands on that line. Aliases are expanded when a command is read, not when it is executed. Therefore, an alias definition appearing on the same line as another command does not take effect until the next line of input is read. The commands following the alias definition on that line are not affected by the new alias. This behavior is also an issue when functions are executed. Aliases are expanded when a function definition is read, not when the function is executed, because a function definition is itself a compound command. As a consequence, aliases defined in a function are not available until after that function is executed. To be safe, always put alias definitions on a separate line, and do not use alias in compound commands. <br>
+<br>
+`alias' and `unalias' are BASH built-ins. For almost every purpose, shell functions are preferred over aliases. <br>
+ <br>
+ <i>“There are many reasons why novelists write, but they all have one thing in common - a need to create an alternative world” - John Fowles</i></p>
+<p><b>Related</b>:<br>
+ <br>
+ <a href="export.html">export</a> - Set an environment variable<br>
+ <a href="env.html">env</a> - Display, set, or remove environment variables<br>
+ <a href="echo.html">echo</a> - Display message on screen <br>
+ <a href="readonly.html">readonly</a> - Mark variables/functions as readonly
+ <br>
+ <a href="shift.html">shift</a> - Shift positional parameters<br>
+ Equivalent Windows command:
+<a href="../term_tools/nt/set.html"></a><a href="../term_tools/nt/set.html">SET</a> - Display, set, or remove Windows environment
+variables.</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/apt-get.html b/help/en/bash/apt-get.html
new file mode 100644
index 0000000..da32763
--- /dev/null
+++ b/help/en/bash/apt-get.html
@@ -0,0 +1,506 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>apt-get MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem -->
+<h1> apt-get</h1>
+<p>Search for and install software packages (Debian/Ubuntu).</p>
+<pre>Syntax
+ apt-get [-sqdyfmubV] [-o= <i>config_string</i> ] [-c= <i>config_file</i> ]
+ [-t= <i>target</i>] <b>update</b>
+
+ apt-get [-sqdyfmubV] [-o= <i>config_string</i> ] [-c= <i>config_file</i> ]
+ [-t= <i>target</i>] <b>upgrade</b>
+
+ apt-get [-sqdyfmubV] [-o= <i>config_string</i> ] [-c= <i>config_file</i> ]
+ [-t= <i>target</i>] <b>dselect-upgrade</b>
+
+ apt-get [-sqdyfmubV] [-o= <i>config_string</i> ] [-c= <i>config_file</i> ]
+ [-t= <i>target</i>] <b>dist-upgrade</b>
+
+ apt-get [-sqdyfmubV] [-o= <i>config_string</i> ] [-c= <i>config_file</i> ]
+ [-t= <i>target</i>] <b>install</b> <i>pkg</i> [ { =<i>pkg_version_number</i> | /<i>target_release_name</i> | /<i>target_release_codename</i> } ] ...
+
+ apt-get [-sqdyfmubV] [-o= <i>config_string</i> ] [-c= <i>config_file</i> ]
+ [-t= <i>target</i>] <b>remove</b> <i>pkg</i>...
+
+ apt-get [-sqdyfmubV] [-o= <i>config_string</i> ] [-c= <i>config_file</i> ]
+ [-t= <i>target</i>] <b>purge</b> <i>pkg</i>...
+
+ apt-get [-sqdyfmubV] [-o= <i>config_string</i> ] [-c= <i>config_file</i> ]
+ [-t= <i>target</i>] <b>source</b> <i>pkg</i> [ { =<i>pkg_version_number</i> | /<i>target_release_name</i> | /<i>target_release_codename</i> } ] ...
+
+ apt-get [-sqdyfmubV] [-o= <i>config_string</i> ] [-c= <i>config_file</i> ]
+ [-t= <i>target</i>] <b>build-dep</b> <i>pkg</i>...
+
+ apt-get [-sqdyfmubV] [-o= <i>config_string</i> ] [-c= <i>config_file</i> ]
+ [-t= <i>target</i>] <b>check</b>
+
+ apt-get [-sqdyfmubV] [-o= <i>config_string</i> ] [-c= <i>config_file</i> ]
+ [-t= <i>target</i>] <b>clean</b>
+
+ apt-get [-sqdyfmubV] [-o= <i>config_string</i> ] [-c= <i>config_file</i> ]
+ [-t= <i>target</i>] <b>autoclean</b>
+
+ apt-get [-sqdyfmubV] [-o= <i>config_string</i> ] [-c= <i>config_file</i> ]
+ [-t= <i>target</i>] <b>autoremove</b>
+
+ apt-get {-v | --version}
+ apt-get {-h | --help}}
+
+ Where <i>Target</i> = {<i>target_release_name</i> | <i>target_release_number_expression</i> | <i>target_release_codename</i>}
+
+Key</pre>
+<p>n.b. Do not switch back and forth between different package managers. If you use apt to install some software, and then try <a href="aptitude.html">aptitude</a>, it will uninstall all the packages you installed using apt. Choose one package manager and stick with it!</p>
+<p>All command line options may be set using the configuration file, the
+descriptions indicate the configuration option to set. For boolean
+options you can override the config file by using something like</p>
+<pre> -f-,--no-f, -f=no or several other variations.
+
+ --no-install-recommends
+ Do not consider recommended packages as a dependency for
+ installing. Configuration Item: APT::Install-Recommends.
+
+ -d, --download-only
+ Download only; package files are only retrieved, not unpacked or
+ installed. Configuration Item: APT::Get::Download-Only.
+
+ -f, --fix-broken
+ Fix; attempt to correct a system with broken dependencies in place.
+ This option, when used with install/remove, can omit any packages
+ to permit APT to deduce a likely solution. If packages are
+ specified, these have to completely correct the problem. The option
+ is sometimes necessary when running APT for the first time; APT
+ itself does not allow broken package dependencies to exist on a
+ system. It is possible that a system's dependency structure can be
+ so corrupt as to require manual intervention (which usually means
+ using dselect(1) or dpkg --remove to eliminate some of the
+ offending packages). Use of this option together with -m may
+ produce an error in some situations. Configuration Item:
+ APT::Get::Fix-Broken.
+
+ -m, --ignore-missing, --fix-missing
+ Ignore missing packages; If packages cannot be retrieved or fail
+ the integrity check after retrieval (corrupted package files), hold
+ back those packages and handle the result. Use of this option
+ together with -f may produce an error in some situations. If a
+ package is selected for installation (particularly if it is
+ mentioned on the command line) and it could not be downloaded then
+ it will be silently held back. Configuration Item:
+ APT::Get::Fix-Missing.
+
+ --no-download
+ Disables downloading of packages. This is best used with
+ --ignore-missing to force APT to use only the .debs it has already
+ downloaded. Configuration Item: APT::Get::Download.
+
+ -q, --quiet
+ Quiet; produces output suitable for logging, omitting progress
+ indicators. More q's will produce more quiet up to a maximum of 2.
+ You can also use -q=# to set the quiet level, overriding the
+ configuration file. Note that quiet level 2 implies -y, you should
+ never use -qq without a no-action modifier such as -d, --print-uris
+ or -s as APT may decided to do something you did not expect.
+ Configuration Item: quiet.
+
+ -s, --simulate, --just-print, --dry-run, --recon, --no-act
+ No action; perform a simulation of events that would occur but do
+ not actually change the system. Configuration Item:
+ APT::Get::Simulate.
+
+ Simulation run as user will deactivate locking (Debug::NoLocking)
+ automatic. Also a notice will be displayed indicating that this is
+ only a simulation, if the option
+ APT::Get::Show-User-Simulation-Note is set (Default: true). Neither
+ NoLocking nor the notice will be triggered if run as root (root
+ should know what he is doing without further warnings by apt-get).
+
+ Simulate prints out a series of lines each one representing a dpkg
+ operation, Configure (Conf), Remove (Remv), Unpack (Inst). Square
+ brackets indicate broken packages and empty set of square brackets
+ meaning breaks that are of no consequence (rare).
+
+ -y, --yes, --assume-yes
+ Automatic yes to prompts; assume "yes" as answer to all prompts and
+ run non-interactively. If an undesirable situation, such as
+ changing a held package, trying to install a unauthenticated
+ package or removing an essential package occurs then apt-get will
+ abort. Configuration Item: APT::Get::Assume-Yes.
+
+ -u, --show-upgraded
+ Show upgraded packages; Print out a list of all packages that are
+ to be upgraded. Configuration Item: APT::Get::Show-Upgraded.
+
+ -V, --verbose-versions
+ Show full versions for upgraded and installed packages.
+ Configuration Item: APT::Get::Show-Versions.
+
+ -b, --compile, --build
+ Compile source packages after downloading them. Configuration Item:
+ APT::Get::Compile.
+
+ --install-recommends
+ Also install recommended packages.
+
+ --no-install-recommends
+ Do not install recommended packages.
+
+ --ignore-hold
+ Ignore package Holds; This causes apt-get to ignore a hold placed
+ on a package. This may be useful in conjunction with dist-upgrade
+ to override a large number of undesired holds. Configuration Item:
+ APT::Ignore-Hold.
+
+ --no-upgrade
+ Do not upgrade packages; When used in conjunction with install,
+ no-upgrade will prevent packages on the command line from being
+ upgraded if they are already installed. Configuration Item:
+ APT::Get::Upgrade.
+
+ --force-yes
+ Force yes; This is a dangerous option that will cause apt to
+ continue without prompting if it is doing something potentially
+ harmful. It should not be used except in very special situations.
+ Using force-yes can potentially destroy your system! Configuration
+ Item: APT::Get::force-yes.
+
+ --print-uris
+ Instead of fetching the files to install their URIs are printed.
+ Each URI will have the path, the destination file name, the size
+ and the expected md5 hash. Note that the file name to write to will
+ not always match the file name on the remote site! This also works
+ with the source and update commands. When used with the update
+ command the MD5 and size are not included, and it is up to the user
+ to decompress any compressed files. Configuration Item:
+ APT::Get::Print-URIs.
+
+ --purge
+ Use purge instead of remove for anything that would be removed. An
+ asterisk ("*") will be displayed next to packages which are
+ scheduled to be purged. remove --purge is equivalent to the purge
+ command. Configuration Item: APT::Get::Purge.
+
+ --reinstall
+ Re-Install packages that are already installed and at the newest
+ version. Configuration Item: APT::Get::ReInstall.
+
+ --list-cleanup
+ This option defaults to on, use --no-list-cleanup to turn it off.
+ When on apt-get will automatically manage the contents of
+ /var/lib/apt/lists to ensure that obsolete files are erased. The
+ only reason to turn it off is if you frequently change your source
+ list. Configuration Item: APT::Get::List-Cleanup.
+
+ -t, --target-release, --default-release
+ This option controls the default input to the policy engine, it
+ creates a default pin at priority 990 using the specified release
+ string. This overrides the general settings in
+ /etc/apt/preferences. Specifically pinned packages are not affected
+ by the value of this option. In short, this option lets you have
+ simple control over which distribution packages will be retrieved
+ from. Some common examples might be -t '2.1*', -t unstable or -t
+ sid. Configuration Item: APT::Default-Release; see also the
+ apt_preferences(5) manual page.
+
+ --trivial-only
+ Only perform operations that are 'trivial'. Logically this can be
+ considered related to --assume-yes, where --assume-yes will answer
+ yes to any prompt, --trivial-only will answer no. Configuration
+ Item: APT::Get::Trivial-Only.
+
+ --no-remove
+ If any packages are to be removed apt-get immediately aborts
+ without prompting. Configuration Item: APT::Get::Remove.
+
+ --auto-remove
+ If the command is either install or remove, then this option acts
+ like running autoremove command, removing the unused dependency
+ packages. Configuration Item: APT::Get::AutomaticRemove.
+
+ --only-source
+ Only has meaning for the source and build-dep commands. Indicates
+ that the given source names are not to be mapped through the binary
+ table. This means that if this option is specified, these commands
+ will only accept source package names as arguments, rather than
+ accepting binary package names and looking up the corresponding
+ source package. Configuration Item: APT::Get::Only-Source.
+
+ --diff-only, --dsc-only, --tar-only
+ Download only the diff, dsc, or tar file of a source archive.
+ Configuration Item: APT::Get::Diff-Only, APT::Get::Dsc-Only, and
+ APT::Get::Tar-Only.
+
+ --arch-only
+ Only process architecture-dependent build-dependencies.
+ Configuration Item: APT::Get::Arch-Only.
+
+ --allow-unauthenticated
+ Ignore if packages can't be authenticated and don't prompt about
+ it. This is useful for tools like pbuilder. Configuration Item:
+ APT::Get::AllowUnauthenticated.
+
+ -h, --help
+ Show a short usage summary.
+
+ -v, --version
+ Show the program version.
+
+ -c, --config-file
+ Configuration File; Specify a configuration file to use. The
+ program will read the default configuration file and then this
+ configuration file. See apt.conf(5) for syntax information.
+
+ -o, --option
+ Set a Configuration Option; This will set an arbitrary
+ configuration option. The syntax is -o Foo::Bar=bar. -o and
+ --option can be used multiple times to set different options.
+</pre>
+<p> update<br>
+update is used to resynchronize the package index files from their
+sources. The indexes of available packages are fetched from the
+location(s) specified in /etc/apt/sources.list. For example, when
+using a Debian archive, this command retrieves and scans the
+Packages.gz files, so that information about new and updated<br>
+packages is available. An update should always be performed before
+an upgrade or dist-upgrade. Please be aware that the overall
+progress meter will be incorrect as the size of the package files
+cannot be known in advance.</p>
+<p> upgrade<br>
+upgrade is used to install the newest versions of all packages
+currently installed on the system from the sources enumerated in
+/etc/apt/sources.list. Packages currently installed with new
+versions available are retrieved and upgraded; under no
+circumstances are currently installed packages removed, or packages
+not already installed retrieved and installed. New versions of
+currently installed packages that cannot be upgraded without
+changing the install status of another package will be left at<br>
+their current version. An update must be performed first so that
+apt-get knows that new versions of packages are available.</p>
+<p> dselect-upgrade<br>
+dselect-upgrade is used in conjunction with the traditional Debian
+packaging front-end, dselect(1). dselect-upgrade follows the
+changes made by dselect(1) to the Status field of available
+packages, and performs the actions necessary to realize that state
+(for instance, the removal of old and the installation of new
+packages).</p>
+<p> dist-upgrade<br>
+dist-upgrade in addition to performing the function of upgrade,
+also intelligently handles changing dependencies with new versions
+of packages; apt-get has a &quot;smart&quot; conflict resolution system, and
+it will attempt to upgrade the most important packages at the
+expense of less important ones if necessary. So, dist-upgrade
+command may remove some packages. The /etc/apt/sources.list file
+contains a list of locations from which to retrieve desired package
+files. See also apt_preferences(5) for a mechanism for overriding
+the general settings for individual packages.</p>
+<p> install<br>
+install is followed by one or more packages desired for
+installation or upgrading. Each package is a package name, not a
+fully qualified filename (for instance, in a Debian GNU/Linux
+system, libc6 would be the argument provided, not
+libc6_1.9.6-2.deb). All packages required by the package(s)
+specified for installation will also be retrieved and installed.
+The /etc/apt/sources.list file is used to locate the desired
+packages. If a hyphen is appended to the package name (with no
+intervening space), the identified package will be removed if it is
+installed. Similarly a plus sign can be used to designate a package
+to install. These latter features may be used to override decisions
+made by apt-get's conflict resolution system.</p>
+<blockquote>
+<p> A specific version of a package can be selected for installation by
+following the package name with an equals and the version of the
+package to select. This will cause that version to be located and
+selected for install. Alternatively a specific distribution can be
+selected by following the package name with a slash and the version<br>
+of the distribution or the Archive name (stable, testing,
+unstable).</p>
+<p> Both of the version selection mechanisms can downgrade packages and
+must be used with care.</p>
+<p> This is also the target to use if you want to upgrade one or more
+already-installed packages without upgrading every package you have
+on your system. Unlike the &quot;upgrade&quot; target, which installs the
+newest version of all currently installed packages, &quot;install&quot; will
+install the newest version of only the package(s) specified. Simply<br>
+provide the name of the package(s) you wish to upgrade, and if a
+newer version is available, it (and its dependencies, as described
+above) will be downloaded and installed.</p>
+<p> Finally, the apt_preferences(5) mechanism allows you to create an
+alternative installation policy for individual packages.</p>
+<p> If no package matches the given expression and the expression
+contains one of '.', '?' or '*' then it is assumed to be a POSIX
+regular expression, and it is applied to all package names in the
+database. Any matches are then installed (or removed). Note that
+matching is done by substring so 'lo.*' matches 'how-lo' and
+'lowest'. If this is undesired, anchor the regular expression with
+a '^' or '$' character, or create a more specific regular
+expression.</p>
+</blockquote>
+<p> remove<br>
+remove is identical to install except that packages are removed
+instead of installed. Note the removing a package leaves its
+configuration files in system. If a plus sign is appended to the
+package name (with no intervening space), the identified package
+will be installed instead of removed.</p>
+<p> purge<br>
+purge is identical to remove except that packages are removed and
+purged (any configuration files are deleted too).</p>
+<p> source<br>
+source causes apt-get to fetch source packages. APT will examine
+the available packages to decide which source package to fetch. It
+will then find and download into the current directory the newest
+available version of that source package while respect the default
+release, set with the option APT::Default-Release, the -t option or<br>
+per package with the pkg/release syntax, if possible.</p>
+<blockquote>
+<p> Source packages are tracked separately from binary packages via
+deb-src type lines in the sources.list(5) file. This means that you
+will need to add such a line for each repository you want to get
+sources from. If you don't do this you will properly get another
+(newer, older or none) source version than the one you have
+installed or could install.</p>
+<p> If the --compile option is specified then the package will be
+compiled to a binary .deb using dpkg-buildpackage, if
+--download-only is specified then the source package will not be
+unpacked.</p>
+<p> A specific source version can be retrieved by postfixing the source
+name with an equals and then the version to fetch, similar to the
+mechanism used for the package files. This enables exact matching
+of the source package name and version, implicitly enabling the
+APT::Get::Only-Source option.</p>
+</blockquote>
+<p> Note that source packages are not tracked like binary packages,
+they exist only in the current directory and are similar to
+downloading source tar balls.</p>
+<p> build-dep<br>
+build-dep causes apt-get to install/remove packages in an attempt
+to satisfy the build dependencies for a source package.</p>
+<p> check<br>
+check is a diagnostic tool; it updates the package cache and checks
+for broken dependencies.</p>
+<p> clean<br>
+clean clears out the local repository of retrieved package files.
+It removes everything but the lock file from
+/var/cache/apt/archives/ and /var/cache/apt/archives/partial/. When
+APT is used as a dselect(1) method, clean is run automatically.
+Those who do not use dselect will likely want to run apt-get clean
+from time to time to free up disk space.</p>
+<p> autoclean<br>
+Like clean, autoclean clears out the local repository of retrieved
+package files. The difference is that it only removes package files
+that can no longer be downloaded, and are largely useless. This
+allows a cache to be maintained over a long period without it
+growing out of control. The configuration option
+APT::Clean-Installed will prevent installed packages from being
+erased if it is set to off.</p>
+<p> autoremove
+<br>
+autoremove is used to remove packages that were automatically
+installed to satisfy dependencies for some package and that are no
+more needed.</p>
+<p>FILES</p>
+<p> <span class="code">/etc/apt/sources.list</span><br>
+Locations to fetch packages from. It takes the following format:<br>deb [web address] [distribution name][maincontribnon-free]<br>
+For example, in Ubuntu, it could be something like:<br>
+<span class="code">deb <a href="http://in.archive.ubuntu.com/ubuntu/">http://in.archive.ubuntu.com/ubuntu</a> lucid main restrcted</span><br>
+or for debian <br>
+<span class="code">deb <a href="http://ftp.de.debian.org/debian">http://ftp.de.debian.org/debian</a> lenny main</span><br>
+Configuration Item:<br>
+Dir::Etc::SourceList.</p>
+<p> <span class="code">/etc/apt/sources.list.d/</span><br>
+File fragments for locations to fetch packages from. Configuration<br>
+Item: Dir::Etc::SourceParts.</p>
+<p> <span class="code">/etc/apt/apt.conf</span><br>
+APT configuration file. Configuration Item: Dir::Etc::Main.</p>
+<p> <span class="code">/etc/apt/apt.conf.d/</span><br>
+APT configuration file fragments. Configuration Item:<br>
+Dir::Etc::Parts.</p>
+<p> <span class="code">/etc/apt/preferences</span><br>
+Version preferences file. This is where you would specify<br>
+&quot;pinning&quot;, i.e. a preference to get certain packages from a<br>
+separate source or from a different version of a distribution.<br>
+Configuration Item: Dir::Etc::Preferences.</p>
+<p> <span class="code">/etc/apt/preferences.d/</span><br>
+File fragments for the version preferences. Configuration Item:<br>
+Dir::Etc::PreferencesParts.</p>
+<p> <span class="code">/var/cache/apt/archives/</span><br>
+Storage area for retrieved package files. Configuration Item:<br>
+Dir::Cache::Archives.</p>
+<p> <span class="code">/var/cache/apt/archives/partial/</span><br>
+Storage area for package files in transit. Configuration Item:<br>
+Dir::Cache::Archives (implicit partial).</p>
+<p> <span class="code">/var/lib/apt/lists/</span><br>
+Storage area for state information for each package resource<br>
+specified in sources.list(5) Configuration Item: Dir::State::Lists.</p>
+<p> <span class="code">/var/lib/apt/lists/partial/</span><br>
+Storage area for state information in transit. Configuration Item:<br>
+Dir::State::Lists (implicit partial).</p>
+<p><b>Examples</b></p>
+<p> These examples assume that <span class="code">/etc/apt/sources.list </span>already includes the web address of at least one software repository.</p>
+<p>Sync the local software database
+with the repository database (build cache):<br>
+
+<span class="code">$ apt-get update</span></p>
+<p><span class="code"></span>Search for a particular program (search the cache) in this case the <i>gimp </i>program:<br>
+<span class="code">$ apt-cache search gimp</span></p>
+<p>If the above succeeds then the software is abailable and can be installed: <br>
+<span class="code">$ apt-get install gimp</span></p>
+<p>To remove the software if you no longer need it: <br>
+<span class="code">$ apt-get remove gimp</span></p>
+<p>Upgrade all the software on your system to the latest versions:<br>
+<span class="code">$ apt-get upgrade</span></p>
+<p>Upgrading the whole linux distribution to a new version: <br>
+<span class="code">$ apt-get dist-upgrade</span><br>
+ <br>
+ <i>“Winners make a habit of manufacturing their own positive expectations in advance of the event” - Brian Tracy</i></p>
+<p><b>Related</b>:</p>
+<p>apt-cache(8), apt-cdrom(8), dselect(1), sources.list(5), apt.conf(5), apt-config(8), apt-secure(8), apt_preferences(5)<br>
+dpkg - Low level Package management<br>
+
+The APT User's guide in
+/usr/share/doc/apt-doc/<br>
+The APT Howto<br>
+<a href="http://www.apt-get.org/">apt-get.org</a> - Unofficial APT repositories for the Debian operating system.<br>
+
+<a href="http://en.wikipedia.org/wiki/Ubuntu_Software_Center"> Ubuntu Software Center</a> - GUI for APT <br>
+<a href="http://www.nongnu.org/synaptic/">Synaptic Package Manager</a> - GUI for APT (In Ubuntu this is under System&gt;Administration)<br>
+<a href="aptitude.html">aptitude</a> - Package manager<br>
+Equivalent Windows command: MSI </p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/aptitude.html b/help/en/bash/aptitude.html
new file mode 100644
index 0000000..63d6d2c
--- /dev/null
+++ b/help/en/bash/aptitude.html
@@ -0,0 +1,857 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>aptitude MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem -->
+<h1> aptitude</h1>
+<p>Package manager (Debian/Ubuntu).</p>
+<pre>Syntax
+ aptitude [<i>options</i>...] autoclean
+ aptitude [<i>options</i>...] clean
+ aptitude [<i>options</i>...] forget-new
+ aptitude [<i>options</i>...] keep-all
+ aptitude [<i>options</i>...] update
+ aptitude [<i>options</i>...] safe-upgrade
+
+ aptitude [<i>options</i>...] changelog <i>packages</i>...
+ aptitude [<i>options</i>...] full-upgrade <i>packages</i>...
+ aptitude [<i>options</i>...] forbid-version <i>packages</i>...
+ aptitude [<i>options</i>...] hold <i>packages</i>...
+ aptitude [<i>options</i>...] install <i>packages</i>...
+ aptitude [<i>options</i>...] markauto <i>packages</i>...
+ aptitude [<i>options</i>...] purge <i>packages</i>...
+ aptitude [<i>options</i>...] reinstall <i>packages</i>...
+ aptitude [<i>options</i>...] remove <i>packages</i>...
+ aptitude [<i>options</i>...] show <i>packages</i>...
+ aptitude [<i>options</i>...] unhold <i>packages</i>...
+ aptitude [<i>options</i>...] unmarkauto <i>packages</i>...
+ aptitude [<i>options</i>...] build-dep <i>packages</i>...
+ aptitude [<i>options</i>...] build-depends <i>packages</i>...
+
+ aptitude extract-cache-subset <i>output-directory packages</i>...
+
+ aptitude [<i>options</i>...] search <i>patterns</i>...
+
+ aptitude [<i>options</i>...] add-user-tag <i>tag</i> <i>packages</i>...
+ aptitude [<i>options</i>...] remove-user-tag <i>tag</i> <i>packages</i>...
+ aptitude [<i>options</i>...] {why | why-not} [<i>patterns</i>...] package
+
+ aptitude [-S <i>fname</i>] [-u | -i]
+
+ aptitude help
+
+Key</pre>
+<p>n.b. Do not switch back and forth between different package managers. If you use <a href="apt-get.html">apt</a> to install some software, and then try aptitude, it will uninstall all the packages you installed using apt. Choose one package manager and stick with it!</p>
+<p>The following actions are available:</p>
+<pre><b> install</b>
+
+ Install one or more packages. The packages should be listed after
+ the “install” command; if a package name contains a tilde character
+ (“<b>~</b>”) or a question mark (“<b>?</b>”), it will be treated as a search
+ pattern and every package matching the pattern will be installed
+ (see the section “Search Patterns” in the <b>aptitude</b> reference
+ manual).
+
+ To select a particular version of the package, append “<b>=&lt;</b><u>version</u>&gt;”
+ to the package name: for instance, “<b>aptitude</b> <b>install</b> <b>apt=0.3.1</b>”.
+ Similarly, to select a package from a particular archive, append
+ “<b>/&lt;</b><u>archive</u>&gt;” to the package name: for instance, “<b>aptitude</b> <b>install</b>
+ <b>apt/experimental</b>”.
+
+ Not every package listed on the command line has to be installed;
+ you can tell <b>aptitude</b> to do something different with a package by
+ appending an “override specifier” to the name of the package. For
+ example, <b>aptitude</b> <b>remove</b> <b>wesnoth+</b> will install <b>wesnoth</b>, not remove
+ it. The following override specifiers are available:
+
+ &lt;<u>package</u>&gt;<b>+</b>
+
+ Install &lt;<u>package</u>&gt;.
+
+ &lt;<u>package</u>&gt;<b>+M</b>
+ Install &lt;<u>package</u>&gt; and immediately mark it as automatically
+ installed (note that if nothing depends on &lt;<u>package</u>&gt;, this will
+ cause it to be immediately removed).
+
+ &lt;<u>package</u>&gt;<b>-</b>
+
+ Remove &lt;<u>package</u>&gt;.
+
+ &lt;<u>package</u>&gt;<b>_</b>
+ Purge &lt;<u>package</u>&gt;: remove it and all its associated configuration
+ and data files.
+
+ &lt;<u>package</u>&gt;<b>=</b>
+ Place &lt;<u>package</u>&gt; on hold: cancel any active installation,
+ upgrade, or removal, and prevent this package from being
+ automatically upgraded in the future.
+
+ &lt;<u>package</u>&gt;<b>:</b>
+
+ Keep &lt;<u>package</u>&gt; at its current version: cancel any installation,
+ removal, or upgrade. Unlike “hold” (above) this does not
+ prevent automatic upgrades in the future.
+
+ &lt;<u>package</u>&gt;<b>&amp;M</b>
+ Mark &lt;<u>package</u>&gt; as having been automatically installed.
+
+ &lt;<u>package</u>&gt;<b>&amp;m</b>
+ Mark &lt;<u>package</u>&gt; as having been manually installed.
+
+ As a special case, “<b>install</b>” with no arguments will act on any
+ stored/pending actions.
+
+ <b>Note</b>
+
+ Once you enter <b>Y</b> at the final confirmation prompt, the
+ “<b>install</b>” command will modify <b>aptitude</b>'s stored information
+ about what actions to perform. Therefore, if you issue (e.g.)
+ the command “<b>aptitude</b> <b>install</b> <b>foo</b> <b>bar</b>” and then abort the
+ installation once <b>aptitude</b> has started downloading and
+ installing packages, you will need to run “<b>aptitude</b> <b>remove</b> <b>foo</b>
+
+ <b>bar</b>” to cancel that order.
+
+ <b>remove</b>, <b>purge</b>, <b>hold</b>, <b>unhold</b>, <b>keep</b>, <b>reinstall</b>
+ These commands are the same as “<b>install</b>”, but apply the named
+ action to all packages given on the command line for which it is
+ not overridden. The difference between <b>hold</b> and <b>keep</b> is that <b>hold</b>
+
+ will cause a package to be ignored by future <b>safe-upgrade</b> or
+ <b>full-upgrade</b> commands, while <b>keep</b> merely cancels any scheduled
+ actions on the package. <b>unhold</b> will allow a package to be upgraded
+ by future <b>safe-upgrade</b> or <b>full-upgrade</b> commands, without otherwise
+ altering its state.
+
+ For instance, “<b>aptitude</b> <b>remove</b> <b>'~ndeity'</b>” will remove all packages
+ whose name contains “<b>deity</b>”.
+
+ <b>markauto</b>, <b>unmarkauto</b>
+
+ Mark packages as automatically installed or manually installed,
+ respectively. Packages are specified in exactly the same way as for
+ the “<b>install</b>” command. For instance, “<b>aptitude</b> <b>markauto</b> <b>'~slibs'</b>”
+ will mark all packages in the “<b>libs</b>” section as having been
+ automatically installed.
+
+ For more information on automatically installed packages, see the
+ section “Managing Automatically Installed Packages” in the <b>aptitude</b>
+ reference manual.
+
+ <b>build-depends</b>, <b>build-dep</b>
+
+ Satisfy the build-dependencies of a package. Each package name may
+ be a source package, in which case the build dependencies of that
+ source package are installed; otherwise, binary packages are found
+ in the same way as for the “<b>install</b>” command, and the
+ build-dependencies of the source packages that build those binary
+ packages are satisfied.
+
+ If the command-line parameter <b>--arch-only</b> is present, only
+ architecture-dependent build dependencies (i.e., not
+ <b>Build-Depends-Indep</b> or <b>Build-Conflicts-Indep</b>) will be obeyed.
+
+ <b>forbid-version</b>
+ Forbid a package from being upgraded to a particular version. This
+ will prevent aptitude from automatically upgrading to this version,
+ but will allow automatic upgrades to future versions. By default,
+ aptitude will select the version to which the package would
+ normally be upgraded; you may override this selection by appending
+ “<b>=&lt;</b><u>version</u>&gt;” to the package name: for instance, “<b>aptitude</b>
+
+ <b>forbid-version</b> <b>vim=1.2.3.broken-4</b>”.
+
+ This command is useful for avoiding broken versions of packages
+ without having to set and clear manual holds. If you decide you
+ really want the forbidden version after all, the “<b>install</b>” command
+ will remove the ban.
+
+ <b>update</b>
+ Updates the list of available packages from the apt sources (this
+ is equivalent to “<b>apt-get</b> <b>update</b>”)
+
+ <b>safe-upgrade</b>
+
+ Upgrades installed packages to their most recent version. Installed
+ packages will not be removed unless they are unused (see the
+ section “Managing Automatically Installed Packages” in the <b>aptitude</b>
+ reference manual). Packages which are not currently installed may
+ be installed to resolve dependencies unless the <b>--no-new-installs</b>
+ command-line option is supplied.
+
+ It is sometimes necessary to remove one package in order to upgrade
+ another; this command is not able to upgrade packages in such
+ situations. Use the <b>full-upgrade</b> command to upgrade as many
+ packages as possible.
+
+ <b>full-upgrade</b>
+ Upgrades installed packages to their most recent version, removing
+ or installing packages as necessary. This command is less
+ conservative than <b>safe-upgrade</b> and thus more likely to perform
+ unwanted actions. However, it is capable of upgrading packages that
+ <b>safe-upgrade</b> cannot upgrade.
+
+ <b>Note</b>
+
+ This command was originally named <b>dist-upgrade</b> for historical
+ reasons, and <b>aptitude</b> still recognizes <b>dist-upgrade</b> as a
+ synonym for <b>full-upgrade</b>.
+
+ <b>keep-all</b>
+ Cancels all scheduled actions on all packages; any packages whose
+ sticky state indicates an installation, removal, or upgrade will
+ have this sticky state cleared.
+
+ <b>forget-new</b>
+
+ Forgets all internal information about what packages are “new”
+ (equivalent to pressing “f” when in visual mode).
+
+ <b>search</b>
+ Searches for packages matching one of the patterns supplied on the
+ command line. All packages which match any of the given patterns
+ will be displayed; for instance, “<b>aptitude</b> <b>search</b> <b>'~N'</b> <b>edit</b>” will
+ list all “new” packages and all packages whose name contains
+ “edit”. For more information on search patterns, see the section
+ “Search Patterns” in the <b>aptitude</b> reference manual.
+
+ Unless you pass the <b>-F</b> option, the output of <b>aptitude</b> <b>search</b> will
+ look something like this:
+
+ i apt - Advanced front-end for dpkg
+ pi apt-build - frontend to apt to build, optimize and in
+ cp apt-file - APT package searching utility -- command-
+ ihA raptor-utils - Raptor RDF Parser utilities
+
+ Each search result is listed on a separate line. The first
+ character of each line indicates the current state of the package:
+ the most common states are <b>p</b>, meaning that no trace of the package
+ exists on the system, <b>c</b>, meaning that the package was deleted but
+ its configuration files remain on the system, <b>i</b>, meaning that the
+ package is installed, and <b>v</b>, meaning that the package is virtual.
+ The second character indicates the stored action (if any; otherwise
+ a blank space is displayed) to be performed on the package, with
+ the most common actions being <b>i</b>, meaning that the package will be
+ installed, <b>d</b>, meaning that the package will be deleted, and <b>p</b>,
+ meaning that the package and its configuration files will be
+ removed. If the third character is <b>A</b>, the package was automatically
+ installed.
+
+ For a complete list of the possible state and action flags, see the
+ section “Accessing Package Information” in the <b>aptitude</b> reference
+ guide. To customize the output of <b>search</b>, see the command-line
+ options <b>-F</b> and <b>--sort</b>.
+
+ <b>show</b>
+
+ Displays detailed information about one or more packages, listed
+ following the search command. If a package name contains a tilde
+ character (“<b>~</b>”) or a question mark (“<b>?</b>”), it will be treated as a
+ search pattern and all matching packages will be displayed (see the
+ section “Search Patterns” in the <b>aptitude</b> reference manual).
+
+ If the verbosity level is 1 or greater (i.e., at least one <b>-v</b> is
+ present on the command-line), information about all versions of the
+ package is displayed. Otherwise, information about the “candidate
+ version” (the version that “<b>aptitude</b> <b>install</b>” would download) is
+ displayed.
+
+ You can display information about a different version of the
+ package by appending <b>=&lt;</b><u>version</u>&gt; to the package name; you can
+ display the version from a particular archive by appending
+ <b>/&lt;</b><u>archive</u>&gt; to the package name. If either of these is present, then
+ only the version you request will be displayed, regardless of the
+ verbosity level.
+
+ If the verbosity level is 1 or greater, the package's architecture,
+ compressed size, filename, and md5sum fields will be displayed. If
+ the verbosity level is 2 or greater, the select version or versions
+ will be displayed once for each archive in which they are found.
+
+ <b>add-user-tag</b>, <b>remove-user-tag</b>
+
+ Adds a user tag to or removes a user tag from the selected group of
+ packages. If a package name contains a tilde (“<b>~</b>”) or question mark
+ (“<b>?</b>”), it is treated as a search pattern and the tag is added to or
+ removed from all the packages that match the pattern (see the
+ section “Search Patterns” in the <b>aptitude</b> reference manual).
+
+ User tags are arbitrary strings associated with a package. They can
+ be used with the <b>?user-tag(&lt;</b><u>tag</u>&gt;<b>)</b> search term, which will select
+ all the packages that have a user tag matching &lt;<u>tag</u>&gt;.
+
+ <b>why</b>, <b>why-not</b>
+
+ Explains the reason that a particular package should or cannot be
+ installed on the system.
+
+ This command searches for packages that require or conflict with
+ the given package. It displays a sequence of dependencies leading
+ to the target package, along with a note indicating the installed
+ state of each package in the dependency chain:
+
+ $ aptitude why kdepim
+ i nautilus-data Recommends nautilus
+ i A nautilus Recommends desktop-base (&gt;= 0.2)
+ i A desktop-base Suggests gnome | kde | xfce4 | wmaker
+ p kde Depends kdepim (&gt;= 4:3.4.3)
+
+ The command <b>why</b> finds a dependency chain that installs the package
+ named on the command line, as above. Note that the dependency that
+ aptitude produced in this case is only a suggestion. This is
+ because no package currently installed on this computer depends on
+ or recommends the kdepim package; if a stronger dependency were
+ available, aptitude would have displayed it.
+
+ In contrast, <b>why-not</b> finds a dependency chain leading to a conflict
+ with the target package:
+
+ $ aptitude why-not textopo
+ i ocaml-core Depends ocamlweb
+ i A ocamlweb Depends tetex-extra | texlive-latex-extra
+ i A texlive-latex-extra Conflicts textopo
+
+ If one or more &lt;<u>pattern</u>&gt;s are present, then aptitude will begin its
+ search at these patterns; that is, the first package in the chain
+ it prints will be a package matching the pattern in question. The
+ patterns are considered to be package names unless they contain a
+ tilde character (“<b>~</b>”) or a question mark (“<b>?</b>”), in which case they
+ are treated as search patterns (see the section “Search Patterns”
+ in the <b>aptitude</b> reference manual).
+
+ If no patterns are present, then <b>aptitude</b> will search for
+ dependency chains beginning at manually installed packages. This
+ effectively shows the packages that have caused or would cause a
+ given package to be installed.
+
+ <b>Note</b>
+
+ <b>aptitude</b> <b>why</b> does not perform full dependency resolution; it
+ only displays direct relationships between packages. For
+ instance, if A requires B, C requires D, and B and C conflict,
+ “<b>aptitude</b> <b>why-not</b> <b>D</b>” will not produce the answer “A depends on
+ B, B conflicts with C, and D depends on C”.
+ By default aptitude outputs only the “most installed, strongest,
+ tightest, shortest” dependency chain. That is, it looks for a chain
+ that only contains packages which are installed or will be
+ installed; it looks for the strongest possible dependencies under
+ that restriction; it looks for chains that avoid ORed dependencies
+ and Provides; and it looks for the shortest dependency chain
+ meeting those criteria. These rules are progressively weakened
+ until a match is found.
+
+ If the verbosity level is 1 or more, then <u>all</u> the explanations
+ aptitude can find will be displayed, in inverse order of relevance.
+ If the verbosity level is 2 or more, a truly excessive amount of
+ debugging information will be printed to standard output.
+
+ This command returns 0 if successful, 1 if no explanation could be
+ constructed, and -1 if an error occured.
+
+ <b>clean</b>
+
+ Removes all previously downloaded <b>.deb</b> files from the package cache
+ directory (usually /var/cache/apt/archives).
+
+ <b>autoclean</b>
+ Removes any cached packages which can no longer be downloaded. This
+ allows you to prevent a cache from growing out of control over time
+ without completely emptying it.
+
+ <b>changelog</b>
+ Downloads and displays the Debian changelog for each of the given
+ source or binary packages.
+
+ By default, the changelog for the version which would be installed
+ with “<b>aptitude</b> <b>install</b>” is downloaded. You can select a particular
+ version of a package by appending <b>=&lt;</b><u>version</u>&gt; to the package name;
+ you can select the version from a particular archive by appending
+ <b>/&lt;</b><u>archive</u>&gt; to the package name.
+
+ <b>download</b>
+
+ Downloads the <b>.deb</b> file for the given package to the current
+ directory. If a package name contains a tilde character (“<b>~</b>”) or a
+ question mark (“<b>?</b>”), it will be treated as a search pattern and all
+ the matching packages will be downloaded (see the section “Search
+ Patterns” in the <b>aptitude</b> reference manual).
+
+ By default, the version which would be installed with “<b>aptitude</b>
+ <b>install</b>” is downloaded. You can select a particular version of a
+ package by appending <b>=&lt;</b><u>version</u>&gt; to the package name; you can select
+ the version from a particular archive by appending <b>/&lt;</b><u>archive</u>&gt; to
+ the package name.
+
+ <b>extract-cache-subset</b>
+
+ Copy the apt configuration directory (<b>/etc/apt</b>) and a subset of the
+ package database to the specified directory. If no packages are
+ listed, the entire package database is copied; otherwise only the
+ entries corresponding to the named packages are copied. Each
+ package name may be a search pattern, and all the packages matching
+ that pattern will be selected (see the section “Search Patterns” in
+ the <b>aptitude</b> reference manual). Any existing package database files
+ in the output directory will be overwritten.
+
+ Dependencies in binary package stanzas will be rewritten to remove
+ references to packages not in the selected set.
+
+ <b>help</b>
+ Displays a brief summary of the available commands and options.</pre>
+<p><b>OPTIONS</b></p>
+<pre> The following options may be used to modify the behavior of the actions
+ described above. Note that while all options will be accepted for all
+ commands, some options don't apply to particular commands and will be
+ ignored by those commands.
+
+ <b>--add-user-tag</b> <b>&lt;</b><u>tag</u>&gt;
+
+ For <b>full-upgrade</b>, <b>safe-upgrade</b>, <b>forbid-version</b>, <b>hold</b>, <b>install</b>,
+ <b>keep-all</b>, <b>markauto</b>, <b>unmarkauto</b>, <b>purge</b>, <b>reinstall</b>, <b>remove</b>, <b>unhold</b>,
+ and <b>unmarkauto</b>: add the user tag &lt;<u>tag</u>&gt; to all packages that are
+ installed, removed, or upgraded by this command as if with the
+ <b>add-user-tag</b> command.
+
+ <b>--add-user-tag-to</b> <b>&lt;</b><u>tag</u>&gt;<b>,&lt;</b><u>pattern</u>&gt;
+
+ For <b>full-upgrade</b>, <b>safe-upgrade</b> <b>forbid-version</b>, <b>hold</b>, <b>install</b>,
+ <b>keep-all</b>, <b>markauto</b>, <b>unmarkauto</b>, <b>purge</b>, <b>reinstall</b>, <b>remove</b>, <b>unhold</b>,
+ and <b>unmarkauto</b>: add the user tag &lt;<u>tag</u>&gt; to all packages that match
+ &lt;<u>pattern</u>&gt; as if with the <b>add-user-tag</b> command. The pattern is a
+ search pattern as described in the section “Search Patterns” in the
+ <b>aptitude</b> reference manual.
+
+ For instance, <b>aptitude</b> <b>safe-upgrade</b> <b>--add-user-tag-to</b>
+
+ <b>"new-installs,?action(install)"</b> will add the tag <b>new-installs</b> to
+ all the packages installed by the <b>safe-upgrade</b> command.
+
+ <b>--allow-new-upgrades</b>
+ When the safe resolver is being used (i.e., <b>--safe-resolver</b> was
+ passed or <b>Aptitude::Always-Use-Safe-Resolver</b> is set to <b>true</b>), allow
+ the dependency resolver to install upgrades for packages regardless
+ of the value of <b>Aptitude::Safe-Resolver::No-New-Upgrades</b>.
+
+ <b>--allow-new-installs</b>
+
+ Allow the <b>safe-upgrade</b> command to install new packages; when the
+ safe resolver is being used (i.e., <b>--safe-resolver</b> was passed or
+ <b>Aptitude::Always-Use-Safe-Resolver</b> is set to <b>true</b>), allow the
+ dependency resolver to install new packages. This option takes
+ effect regardless of the value of
+ <b>Aptitude::Safe-Resolver::No-New-Installs</b>.
+
+ <b>--allow-untrusted</b>
+
+ Install packages from untrusted sources without prompting. You
+ should only use this if you know what you are doing, as it could
+ easily compromise your system's security.
+
+ <b>--disable-columns</b>
+ This option causes <b>aptitude</b> <b>search</b> to output its results without
+ any special formatting. In particular: normally <b>aptitude</b> will add
+ whitespace or truncate search results in an attempt to fit its
+ results into vertical “columns”. With this flag, each line will be
+ formed by replacing any format escapes in the format string with
+ the correponding text; column widths will be ignored.
+
+ For instance, the first few lines of output from “<b>aptitude</b> <b>search</b>
+
+ <b>-F</b> <b>'%p</b> <b>%V'</b> <b>--disable-columns</b> <b>libedataserver</b>” might be:
+
+ disksearch 1.2.1-3
+ hp-search-mac 0.1.3
+ libbsearch-ruby 1.5-5
+ libbsearch-ruby1.8 1.5-5
+ libclass-dbi-abstractsearch-perl 0.07-2
+ libdbix-fulltextsearch-perl 0.73-10
+
+ As in the above example, <b>--disable-columns</b> is often useful in
+ combination with a custom display format set using the command-line
+ option <b>-F</b>.
+
+ This corresponds to the configuration option
+ <b>Aptitude::CmdLine::Disable-Columns</b>.
+
+ <b>-D</b>, <b>--show-deps</b>
+
+ For commands that will install or remove packages (<b>install</b>,
+ <b>full-upgrade</b>, etc), show brief explanations of automatic
+ installations and removals.
+
+ This corresponds to the configuration option
+ <b>Aptitude::CmdLine::Show-Deps</b>.
+
+ <b>-d</b>, <b>--download-only</b>
+ Download packages to the package cache as necessary, but do not
+ install or remove anything. By default, the package cache is stored
+ in /var/cache/apt/archives.
+
+ This corresponds to the configuration option
+ <b>Aptitude::CmdLine::Download-Only</b>.
+
+ <b>-F</b> &lt;<u>format</u>&gt;, <b>--display-format</b> &lt;<u>format</u>&gt;
+
+ Specify the format which should be used to display output from the
+ <b>search</b> command. For instance, passing “<b>%p</b> <b>%V</b> <b>%v</b>” for &lt;<u>format</u>&gt; will
+ display a package's name, followed by its currently installed
+ version and its available version (see the section “Customizing how
+ packages are displayed” in the <b>aptitude</b> reference manual for more
+ information).
+
+ The command-line option <b>--disable-columns</b> is often useful in
+ combination with <b>-F</b>.
+
+ This corresponds to the configuration option
+ <b>Aptitude::CmdLine::Package-Display-Format</b>.
+
+ <b>-f</b>
+
+ Try hard to fix the dependencies of broken packages, even if it
+ means ignoring the actions requested on the command line.
+
+ This corresponds to the configuration item
+ <b>Aptitude::CmdLine::Fix-Broken</b>.
+
+ <b>--full-resolver</b>
+ When package dependency problems are encountered, use the default
+ “full” resolver to solve them. Unlike the “safe” resolver activated
+ by <b>--safe-resolver</b>, the full resolver will happily remove packages
+ to fulfill dependencies. It can resolve more situations than the
+ safe algorithm, but its solutions are more likely to be
+ undesirable.
+
+ This option can be used to force the use of the full resolver even
+ when <b>Aptitude::Always-Use-Safe-Resolver</b> is true. The <b>safe-upgrade</b>
+ command never uses the full resolver and does not accept the
+ <b>--full-resolver</b> option.
+
+ <b>-h</b>, <b>--help</b>
+
+ Display a brief help message. Identical to the <b>help</b> action.
+
+ <b>--no-new-installs</b>
+ Prevent <b>safe-upgrade</b> from installing any new packages; when the
+ safe resolver is being used (i.e., <b>--safe-resolver</b> was passed or
+ <b>Aptitude::Always-Use-Safe-Resolver</b> is set to <b>true</b>), forbid the
+ dependency resolver from installing new packages. This option takes
+ effect regardless of the value of
+ <b>Aptitude::Safe-Resolver::No-New-Installs</b>.
+
+ This mimics the historical behavior of <b>apt-get</b> <b>upgrade</b>.
+
+ This corresponds to the configuration option
+ <b>Aptitude::CmdLine::Safe-Upgrade::No-New-Installs</b>.
+
+ <b>--no-new-upgrades</b>
+
+ When the safe resolver is being used (i.e., <b>--safe-resolver</b> was
+ passed or <b>Aptitude::Always-Use-Safe-Resolver</b> is set to <b>true</b>), allow
+ the dependency resolver to install new packages regardless of the
+ value of <b>Aptitude::Safe-Resolver::No-New-Installs</b>.
+
+ <b>-O</b> &lt;<u>order</u>&gt;, <b>--sort</b> &lt;<u>order</u>&gt;
+
+ Specify the order in which output from the <b>search</b> command should be
+ displayed. For instance, passing “<b>installsize</b>” for &lt;<u>order</u>&gt; will
+ list packages in order according to their size when installed (see
+ the section “Customizing how packages are sorted” in the <b>aptitude</b>
+ reference manual for more information).
+
+ <b>-o</b> &lt;<u>key</u>&gt;<b>=</b>&lt;<u>value</u>&gt;
+
+ Set a configuration file option directly; for instance, use <b>-o</b>
+ <b>Aptitude::Log=/tmp/my-log</b> to log <b>aptitude</b>'s actions to /tmp/my-log.
+ For more information on configuration file options, see the section
+ “Configuration file reference” in the <b>aptitude</b> reference manual.
+
+ <b>-P</b>, <b>--prompt</b>
+
+ Always display a prompt before downloading, installing or removing
+ packages, even when no actions other than those explicitly
+ requested will be performed.
+
+ This corresponds to the configuration option
+ <b>Aptitude::CmdLine::Always-Prompt</b>.
+
+ <b>--purge-unused</b>
+ Purge packages that are no longer required by any installed
+ package. This is equivalent to passing “<b>-o</b>
+ <b>Aptitude::Purge-Unused=true</b>” as a command-line argument.
+
+ <b>-q[=&lt;</b><u>n</u>&gt;], <b>--quiet[=&lt;</b><u>n</u>&gt;]
+ Suppress all incremental progress indicators, thus making the
+ output loggable. This may be supplied multiple times to make the
+ program quieter, but unlike <b>apt-get</b>, <b>aptitude</b> does not enable <b>-y</b>
+
+ when <b>-q</b> is supplied more than once.
+
+ The optional <b>=&lt;</b><u>n</u>&gt; may be used to directly set the amount of
+ quietness (for instance, to override a setting in
+ /etc/apt/apt.conf); it causes the program to behave as if <b>-q</b> had
+ been passed exactly &lt;<u>n</u>&gt; times.
+
+ <b>-R</b>, <b>--without-recommends</b>
+
+ Do <u>not</u> treat recommendations as dependencies when installing new
+ packages (this overrides settings in /etc/apt/apt.conf and
+ ~/.aptitude/config). Packages previously installed due to
+ recommendations will not be removed.
+
+ This corresponds to the pair of configuration options
+ <b>Apt::Install-Recommends</b> and <b>Aptitude::Keep-Recommends</b>.
+
+ <b>-r</b>, <b>--with-recommends</b>
+ Treat recommendations as dependencies when installing new packages
+ (this overrides settings in /etc/apt/apt.conf and
+ ~/.aptitude/config).
+
+ This corresponds to the configuration option
+ <b>Apt::Install-Recommends</b>
+
+ <b>--remove-user-tag</b> <b>&lt;</b><u>tag</u>&gt;
+ For <b>full-upgrade</b>, <b>safe-upgrade</b> <b>forbid-version</b>, <b>hold</b>, <b>install</b>,
+ <b>keep-all</b>, <b>markauto</b>, <b>unmarkauto</b>, <b>purge</b>, <b>reinstall</b>, <b>remove</b>, <b>unhold</b>,
+ and <b>unmarkauto</b>: remove the user tag &lt;<u>tag</u>&gt; from all packages that
+ are installed, removed, or upgraded by this command as if with the
+ <b>add-user-tag</b> command.
+
+ <b>--remove-user-tag-from</b> <b>&lt;</b><u>tag</u>&gt;<b>,&lt;</b><u>pattern</u>&gt;
+
+ For <b>full-upgrade</b>, <b>safe-upgrade</b> <b>forbid-version</b>, <b>hold</b>, <b>install</b>,
+ <b>keep-all</b>, <b>markauto</b>, <b>unmarkauto</b>, <b>purge</b>, <b>reinstall</b>, <b>remove</b>, <b>unhold</b>,
+ and <b>unmarkauto</b>: remove the user tag &lt;<u>tag</u>&gt; from all packages that
+ match &lt;<u>pattern</u>&gt; as if with the <b>remove-user-tag</b> command. The pattern
+ is a search pattern as described in the section “Search Patterns”
+ in the <b>aptitude</b> reference manual.
+
+ For instance, <b>aptitude</b> <b>safe-upgrade</b> <b>--remove-user-tag-from</b>
+
+ <b>"not-upgraded,?action(upgrade)"</b> will remove the <b>not-upgraded</b> tag
+ from all packages that the <b>safe-upgrade</b> command is able to upgrade.
+
+ <b>-s</b>, <b>--simulate</b>
+ In command-line mode, print the actions that would normally be
+ performed, but don't actually perform them. This does not require
+ root privileges. In the visual interface, always open the cache in
+ read-only mode regardless of whether you are root.
+
+ This corresponds to the configuration option <b>Aptitude::Simulate</b>.
+
+ <b>--safe-resolver</b>
+
+ When package dependency problems are encountered, use a “safe”
+ algorithm to solve them. This resolver attempts to preserve as many
+ of your choices as possible; it will never remove a package or
+ install a version of a package other than the package's default
+ candidate version. It is the same algorithm used in <b>safe-upgrade</b>;
+ indeed, <b>aptitude</b> <b>--safe-resolver</b> <b>full-upgrade</b> is equivalent to
+ <b>aptitude</b> <b>safe-upgrade</b>. Because <b>safe-upgrade</b> always uses the safe
+ resolver, it does not accept the <b>--safe-resolver</b> flag.
+
+ This option is equivalent to setting the configuration variable
+ <b>Aptitude::Always-Use-Safe-Resolver</b> to <b>true</b>.
+
+ <b>--schedule-only</b>
+
+ For commands that modify package states, schedule operations to be
+ performed in the future, but don't perform them. You can execute
+ scheduled actions by running <b>aptitude</b> <b>install</b> with no arguments.
+ This is equivalent to making the corresponding selections in visual
+ mode, then exiting the program normally.
+
+ For instance, <b>aptitude</b> <b>--schedule-only</b> <b>install</b> <b>evolution</b> will
+ schedule the <b>evolution</b> package for later installation.
+
+ <b>-t</b> &lt;<u>release</u>&gt;, <b>--target-release</b> &lt;<u>release</u>&gt;
+
+ Set the release from which packages should be installed. For
+ instance, “<b>aptitude</b> <b>-t</b> <b>experimental</b> <b>...</b>” will install packages
+ from the experimental distribution unless you specify otherwise.
+ For the command-line actions “changelog”, “download”, and “show”,
+ this is equivalent to appending <b>/&lt;</b><u>release</u>&gt; to each package named on
+ the command-line; for other commands, this will affect the default
+ candidate version of packages according to the rules described in
+ apt_preferences(5).
+
+ This corresponds to the configuration item <b>APT::Default-Release</b>.
+
+ <b>-V</b>, <b>--show-versions</b>
+
+ Show which versions of packages will be installed.
+
+ This corresponds to the configuration option
+ <b>Aptitude::CmdLine::Show-Versions</b>.
+
+ <b>-v</b>, <b>--verbose</b>
+ Causes some commands (for instance, <b>show</b>) to display extra
+ information. This may be supplied multiple times to get more and
+ more information.
+
+ This corresponds to the configuration option
+ <b>Aptitude::CmdLine::Verbose</b>.
+
+ <b>--version</b>
+ Display the version of <b>aptitude</b> and some information about how it
+ was compiled.
+
+ <b>--visual-preview</b>
+
+ When installing or removing packages from the command line, instead
+ of displaying the usual prompt, start up the visual interface and
+ display its preview screen.
+
+ <b>-W</b>, <b>--show-why</b>
+ In the preview displayed before packages are installed or removed,
+ show which manually installed package requires each automatically
+ installed package. For instance:
+
+ $ aptitude --show-why install mediawiki
+ ...
+ The following NEW packages will be installed:
+ libapache2-mod-php5{a} (for mediawiki) mediawiki php5{a} (for mediawiki)
+ php5-cli{a} (for mediawiki) php5-common{a} (for mediawiki)
+ php5-mysql{a} (for mediawiki)
+
+ When combined with <b>-v</b> or a non-zero value for
+ <b>Aptitude::CmdLine::Verbose</b>, this displays the entire chain of
+ dependencies that lead each package to be installed. For instance:
+
+ $ aptitude -v --show-why install libdb4.2-dev
+ The following NEW packages will be installed:
+ libdb4.2{a} (libdb4.2-dev D: libdb4.2) libdb4.2-dev
+ The following packages will be REMOVED:
+ libdb4.4-dev{a} (libdb4.2-dev C: libdb-dev P&lt;- libdb-dev)
+
+ This option will also describe why packages are being removed, as
+ shown above. In this example, libdb4.2-dev conflicts with
+ libdb-dev, which is provided by libdb-dev.
+
+ This argument corresponds to the configuration option
+ <b>Aptitude::CmdLine::Show-Why</b> and displays the same information that
+ is computed by <b>aptitude</b> <b>why</b> and <b>aptitude</b> <b>why-not</b>.
+
+ <b>-w</b> &lt;<u>width</u>&gt;, <b>--width</b> &lt;<u>width</u>&gt;
+
+ Specify the display width which should be used for output from the
+ <b>search</b> command (by default, the terminal width is used).
+
+ This corresponds to the configuration option
+ <b>Aptitude::CmdLine::Package-Display-Width</b>
+
+ <b>-y</b>, <b>--assume-yes</b>
+ When a yes/no prompt would be presented, assume that the user
+ entered “yes”. In particular, suppresses the prompt that appears
+ when installing, upgrading, or removing packages. Prompts for
+ “dangerous” actions, such as removing essential packages, will
+ still be displayed. This option overrides <b>-P</b>.
+
+ This corresponds to the configuration option
+ <b>Aptitude::CmdLine::Assume-Yes</b>.
+
+ <b>-Z</b>
+
+ Show how much disk space will be used or freed by the individual
+ packages being installed, upgraded, or removed.
+
+ This corresponds to the configuration option
+ <b>Aptitude::CmdLine::Show-Size-Changes</b>.
+
+ The following options apply to the visual mode of the program, but are
+ primarily for internal use; you generally won't need to use them
+ yourself.
+
+ <b>-i</b>
+ Displays a download preview when the program starts (equivalent to
+ starting the program and immediately pressing “g”). You cannot use
+ this option and “<b>-u</b>” at the same time.
+
+ <b>-S</b> &lt;<u>fname</u>&gt;
+ Loads the extended state information from &lt;<u>fname</u>&gt; instead of the
+ standard state file.
+
+ <b>-u</b>
+
+ Begins updating the package lists as soon as the program starts.
+ You cannot use this option and <b>-i</b> at the same time.</pre>
+<p><b>ENVIRONMENT</b></p>
+<pre> <b>HOME</b>
+ If $HOME/.aptitude exists, aptitude will store its configuration
+ file in $HOME/.aptitude/config. Otherwise, it will look up the
+ current user's home directory using <b>getpwuid</b>(2) and place its
+ configuration file there.
+
+ <b>PAGER</b>
+ If this environment variable is set, <b>aptitude</b> will use it to
+ display changelogs when “<b>aptitude</b> <b>changelog</b>” is invoked. If not
+ set, it defaults to <b>more</b>.
+
+ <b>TMP</b>
+
+ If <b>TMPDIR</b> is unset, <b>aptitude</b> will store its temporary files in <b>TMP</b>
+ if that variable is set. Otherwise, it will store them in /tmp.
+
+ <b>TMPDIR</b>
+
+ <b>aptitude</b> will store its temporary files in the directory indicated
+ by this environment variable. If <b>TMPDIR</b> is not set, then <b>TMP</b> will
+ be used; if <b>TMP</b> is also unset, then <b>aptitude</b> will use /tmp.
+</pre>
+<p><b>FILES</b></p><pre> /var/lib/aptitude/pkgstates
+ The file in which stored package states and some package flags are
+ stored.
+
+ /etc/apt/apt.conf, /etc/apt/apt.conf.d/*, ~/.aptitude/config
+ The configuration files for <b>aptitude</b>. ~/.aptitude/config overrides
+ /etc/apt/apt.conf. See <b>apt.conf</b>(5) for documentation of the format
+ and contents of these files.
+</pre>
+<p><i>“Don’t sweat the petty things and don’t pet the sweaty things” - George Carlin</i></p>
+<p><b>Related</b>:</p>
+<p><a href="apt-get.html">apt-get</a> - Package Manager <br>
+dpkg - Low level Package management<br>
+
+
+<a href="http://en.wikipedia.org/wiki/Ubuntu_Software_Center"> Ubuntu Software Center</a> - GUI for APT <br>
+<a href="http://www.nongnu.org/synaptic/">Synaptic Package Manager</a> - GUI for APT (In Ubuntu this is under System&gt;Administration)<br>
+<a href="http://algebraicthunk.net/%7Edburrows/projects/aptitude/">aptitude</a> - Project page <br>
+Equivalent Windows command: MSI </p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/aspell.html b/help/en/bash/aspell.html
new file mode 100644
index 0000000..8c0b809
--- /dev/null
+++ b/help/en/bash/aspell.html
@@ -0,0 +1,90 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>aspell MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem -->
+<h1> aspell</h1>
+<p>Spellcheck a file. </p>
+<pre>Syntax
+ aspell check [<i>options</i>] <i>filename</i>
+
+Key
+ –mode=<i>mode</i>
+ The mode to use when checking files.
+ The available modes are none, <u>url</u>, email, sgml, tex, texinfo, nroff and any
+ others available on your system. <a href="http://aspell.net/man-html/Notes-on-Various-Filters-and-Filter-Modes.html">more..</a>
+
+ –dont-backup
+ Don't create a backup file. Normally, if there are any corrections the Aspell utility
+ will append .bak to the existing file name and then create a new file with corrections
+ made during spell checking.
+
+ –sug-mode=<i>mode</i>
+ The suggestion <i>mode</i> to use where mode is one of ultra, fast, normal, or bad-spellers.
+ For more information on these modes see Notes on the Different Suggestion Modes.
+
+ –lang=<i>name</i>
+ -l <i>name</i>
+ The language the document is written in. The default depends on the current locale.
+
+ –encoding=<i>name</i>
+ Encoding the document is expected to be in. The default depends on the current locale.
+
+ –master=<i>name</i>
+ -d <i>name</i>
+ The main dictionary to use.
+
+ –keymapping=<i>name</i>
+ The keymapping to use. Either aspell for the default mapping or ispell to use the same
+ mapping that the Ispell utility uses.
+
+ <a href="http://aspell.net/man-html/The-Options.html">Further/advanced options</a></pre>
+<p> <b>Examples</b></p>
+<p> Check the file foo.txt:</p>
+<p class="code"> $ aspell check foo.txt</p>
+<p>Check the file foo.txt using the bad-spellers suggestion mode and the American English dictionary:</p>
+<p class="code"> $ aspell check --sug-mode=bad-spellers -d en_US foo.txt</p>
+<p><i> “My spelling is Wobbly. It's good spelling but it Wobbles, and the letters get in the wrong places” - A. A. Milne</i></p>
+<p><b>Related</b>:<br>
+ <br>
+<a href="http://aspell.net/">aspell.net</a><br>
+Equivalent Windows command: <a href="http://discuss.joelonsoftware.com/default.asp?joel.3.731014.6">Word</a> </p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/awk.html b/help/en/bash/awk.html
new file mode 100644
index 0000000..bd3ca1c
--- /dev/null
+++ b/help/en/bash/awk.html
@@ -0,0 +1,247 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>awk gawk MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> awk or gawk (gnu awk)</h1>
+<p>Find and Replace text, database sort/validate/index</p>
+<pre>Syntax
+
+ awk &lt;<em>options</em>&gt; '<em>Program</em>' <em>Input-File1 Input-File2</em> ...
+
+ awk -f <em>PROGRAM-FILE</em> &lt;<em>options</em>&gt; <em>Input-File1 Input-File2</em> ...
+
+Key
+ -F <em>FS</em>
+ --field-separator <em>FS</em>
+ Use FS for the input field separator (the value of the `<em>FS</em>'
+ predefined variable).
+
+ -f <em>PROGRAM-FILE</em>
+ --file <em>PROGRAM-FILE</em>
+ Read the `awk' program source from the file <em>PROGRAM-FILE</em>, instead
+ of from the first command line argument.
+
+ -mf<em> NNN</em>
+ -mr<em> NNN</em>
+ The `f' flag sets the maximum number of fields, and the `r' flag
+ sets the maximum record size. These options are ignored by
+ `gawk', since `gawk' has no predefined limits; they are only for
+ compatibility with the Bell Labs research version of Unix `awk'.
+
+ -v <em>VAR</em>=<em>VAL</em>
+ --assign <em>VAR</em>=<em>VAL</em>
+ Assign the variable <em>VAR</em> the value <em>VAL</em> before program execution
+ begins.
+
+ -W traditional
+ -W compat
+ --traditional
+ --compat
+ Use compatibility mode, in which `gawk' extensions are turned off.
+
+ -W lint
+ --lint
+ Give warnings about dubious or non-portable `awk' constructs.
+
+ -W lint-old
+ --lint-old
+ Warn about constructs that are not available in the original
+ Version 7 Unix version of `awk'.
+
+ -W posix
+ --posix
+ Use POSIX compatibility mode, in which `gawk' extensions are
+ turned off and additional restrictions apply.
+
+ -W re-interval
+ --re-interval
+ Allow interval expressions, in regexps.
+
+ -W source=<em>PROGRAM-TEXT</em>
+ --source <em>PROGRAM-TEXT</em>
+ Use PROGRAM-TEXT as `awk' program source code. This option allows
+ mixing command line source code with source code from files, and is
+ particularly useful for mixing command line programs with library
+ functions.
+
+ --
+ Signal the end of options. This is useful to allow further
+ arguments to the `awk' program itself to start with a `-'. This
+ is mainly for consistency with POSIX argument parsing conventions.
+
+'<em>Program</em>'
+ A series of patterns and actions: see below
+
+<em>Input-File</em>
+ If no Input-File is specified then `awk' applies the <em>Program</em> to
+ "standard input", (piped output of some other command or the terminal.
+ Typed input will continue until end-of-file (typing `Control-d')</pre>
+<p><b>Basic functions</b><br>
+ <br>
+The basic function of awk is to search files for lines (or other units of text) that contain a pattern. When a line matches, awk performs a specific action on that line.</p>
+<p>The <em>Program</em> statement that tells `awk' what to do; consists of a series of "rules".
+ Each rule specifies one pattern to search for, and one action to perform when
+ that pattern is found.<br>
+ <br>
+For ease of reading, each line in an `awk' program is normally a separate <em>Program </em>statement , like this:</p>
+<pre> <em>pattern</em> { <em>action</em> }
+ <em>pattern</em> { <em>action</em> }
+ ...
+</pre>
+<p>e.g. Display lines from my_file containing the string &quot;123&quot; or &quot;abc&quot; or &quot;some text&quot;:</p>
+<pre>awk '/123/ { print $0 }
+ /abc/ { print $0 }
+ /some text/ { print $0 }' my_file</pre>
+<p>A regular expression enclosed in slashes (`/') is an `awk' pattern
+ that matches every input record whose text belongs to that set. e.g. the pattern
+ /foo/ matches any input record containing the three characters `foo', *anywhere*
+ in the record. </p>
+<p>`awk' patterns may be one of the following: </p>
+
+<pre><strong>/</strong>Regular Expression<strong>/</strong> - Match =
+Pattern <strong>&&</strong> Pattern - AND
+Pattern <strong>||</strong> Pattern - OR
+<strong>!</strong> Pattern - NOT
+Pattern <strong>?</strong> Pattern <strong>:</strong> Pattern - If, Then, Else
+Pattern1<strong>,</strong> Pattern2 - Range Start - end
+<strong>BEGIN</strong> - Perform action BEFORE input file is read
+<strong>END</strong> - Perform action AFTER input file is read</pre>
+<p>The special patterns BEGIN and END may be used to capture control before the first input line is read and after the last. BEGIN and END do not combine with other patterns.<br>
+<br>
+Variable names with special meanings:</p>
+<pre>
+ CONVFMT conversion format used when converting numbers
+ (default %.6g)
+
+ FS regular expression used to separate fields; also
+ settable by option -Ffs.
+
+ NF number of fields in the current record
+
+ NR ordinal number of the current record
+
+ FNR ordinal number of the current record in the current
+ file
+
+ FILENAME the name of the current input file
+
+ RS input record separator (default newline)
+
+ OFS output field separator (default blank)
+
+ ORS output record separator (default newline)
+
+ OFMT output format for numbers (default %.6g)
+
+ SUBSEP separates multiple subscripts (default 034)
+
+ ARGC argument count, assignable
+
+ ARGV argument array, assignable; non-null members are
+ taken as filenames
+
+ ENVIRON array of environment variables; subscripts are
+ names.</pre>
+<p>In addition to simple pattern matching `awk' has a huge range
+of text and arithmetic Functions, Variables and Operators. </p>
+<p>`gawk' will ignore newlines after any of the following:</p>
+<pre> , { ? : || &amp;&amp; do else</pre>
+<p> Comments - start with a `#', and continue to the end of the line:</p>
+<pre> # This program prints a nice friendly message</pre>
+<p><strong>Examples</strong></p>
+<p>Print the Row Number (NR), then a dash and space <span class="code">(&quot;- &quot;</span>) and then the first item ($1) from each line in samplefile.txt: </p>
+<p class="code">$ awk '{print NR &quot;- &quot; $1 }' samplefile.txt</p>
+<p>Print the first item ($1) and then the third last item<span class="code"> $(NF-2)</span> from each line in samplefile.txt: </p>
+<p class="code">$ awk '{print $1, $(NF-2) }' samplefile.txt</p>
+<p>Print every line that has at least one field. This is an easy way to delete blank lines from a file (or rather, to<br>
+create a new file similar to the old file but from which the blank lines have been deleted)</p>
+<pre> awk 'NF > 0' data.txt</pre>
+<p>Comparison with <a href="grep.html">grep</a>:</p>
+<blockquote>
+<p>Running <span class="code">grep Dec</span> against the following file listing would return the 3 rows shown in bold as it matches text in different places: </p>
+<p><span class="code">-rw-r--r-- 7 simon simon 12043 Jan 31 09:36 <b>Dec</b>ember.pdf<br>
+-rw-r--r-- 3 simon simon 1024 <b>Dec</b> 01 11:59 README<br>
+-rw-r--r-- 3 simon simon 5096 Nov 14 18:22 <b>Dec</b>ision.txt </span></p>
+<p>Running <span class="code">awk '$6 == &quot;Dec&quot;'</span>against the same file listing, the relational operator $6 matches the exact field (column 6 = Month) so it will list only the December file:</p>
+<p class="code"> $ ls -l /tmp/demo | awk '$6 == &quot;Dec&quot;'</p>
+</blockquote>
+<p>Print the length of the longest input line: </p>
+<pre> awk '{ if (length($0) > max) max = length($0) }
+ END { print max }' data
+</pre>
+<p>Print seven random numbers from zero to 100,
+inclusive:</p>
+<pre> awk 'BEGIN { for (i = 1; i <= 7; i++)
+ print int(101 * rand()) }'
+</pre>
+<p>Print the total number of bytes used by <i>FILES</i>:</p>
+<pre> ls -lg <i>FILES</i> | awk '{ x += $5 } ; END { print "total bytes: " x }'
+</pre>
+<p>Print the average file size of all .PNG files within a directory:</p>
+<pre> ls -l *.png | gawk '{sum += $5; n++;} END {print sum/n;}' </pre>
+<p> Print a sorted list of the login names of all users:</p>
+<pre> awk -F: '{ print $1 }' /etc/passwd | sort</pre>
+<p> Count the lines in a file:</p>
+<pre> awk 'END { print NR }' data</pre>
+<p> Print the even numbered lines in the data file. If you were to use the expression <span class="code">'NR % 2 == 1'</span> instead, it would
+print the odd numbered lines.</p>
+<pre> awk 'NR % 2 == 0' data</pre>
+<p><i>&ldquo;Justice is such a fine thing that we cannot pay too dearly for it&rdquo; - Alain-Rene Lesage </i><br>
+<br>
+<b> Related</b>:<br>
+<br>
+<a href="http://www.gnu.org/software/gawk/manual/gawk.html">GNU Awk User Guide</a> - awk examples<br>
+<a href="http://www.pement.org/awk/awk1line.txt">awk one liners</a> - Eric Pement<br>
+<a href="http://www.catonmat.net/blog/awk-one-liners-explained-part-one/">awk one liners explained</a> &amp; <a href="http://www.catonmat.net/blog/awk-one-liners-explained-part-two/">pt2</a> - Peteris Krumin (CatOnMat.net)<br>
+<a href="http://gregable.com/2010/09/why-you-should-know-just-little-awk.html">Gregable</a> - Why you should know just a little Awk<br>
+<a href="http://sparky.rice.edu/%7Ehartigan/awk.html">Patrick Hartigan</a> - How to use awk<a href="http://www.pement.org/awk/awk1line.txt"></a><br>
+`awk', `oawk', and `nawk' - Alternative, older and newer versions of awk<br>
+<a href="egrep.html">egrep</a> - egrep foo FILES ...is essentially the same as awk '/foo/' FILES ... <br>
+<a href="expr.html">expr</a> - Evaluate expressions<br>
+<a href="eval.html">eval</a> - Evaluate several commands/arguments<br>
+<a href="for.html">for</a> - Expand <var>words</var>, and execute <var>commands</var><br>
+<a href="grep.html">grep</a> - search file(s) for lines that match a given pattern
+<br>
+<a href="../term_tools/bash/m4.html">m4</a> - Macro processor <br>
+<a href="tr.html">tr</a> - Translate, squeeze, and/or delete characters <br>
+Equivalent Windows command:
+<a href="../term_tools/nt/for.html">FOR</a> - Conditionally perform a command several times.</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/basename.html b/help/en/bash/basename.html
new file mode 100644
index 0000000..1597ad8
--- /dev/null
+++ b/help/en/bash/basename.html
@@ -0,0 +1,70 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>basename MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> basename </h1>
+<p>Strip directory and suffix from filenames</p>
+<pre>Syntax
+ basename <i>NAME</i> [<i>SUFFIX</i>]
+
+ basename <i>OPTION
+</i>Key
+ --help
+ Display help
+
+ --version
+ Output version information and exit</pre>
+<p> basename will print <i>NAME</i> with any leading directory components removed. If specified, it will also remove a trailing SUFFIX (typically a file extention). </p>
+<p><b>Examples</b></p>
+<p>A <a href="../term_tools/bash/syntax-script.html">script</a> to rename file extensions:</p>
+<p class="code">#BatchRenameExt<br>
+for file in *.$1; do<br>
+mv $file `basename $file $1`.$2<br>
+done</p>
+<p class="code">$ BatchRenameExt htm html</p>
+<p><i>&ldquo;Then I came up with this crazy idea just to walk out on the stage with no band at all and just start singing whatever came to mind. I actually fought the idea for a while because it seemed almost too radical, but it became obvious what I was supposed to be doing&rdquo; - <a href="http://www.youtube.com/watch?v=PgvJg7D6Qck">Bobby McFerrin</a> </i></p>
+<p><b>Related</b>:<br>
+ <br>
+ <a href="dir.html">dir</a> - Briefly list directory contents<br>
+<a href="dirname.html">dirname</a> - Convert a full pathname to just a path<br>
+ <a href="ls.html">ls</a> - List information about file(s)<br>
+Equivalent Windows command: <a href="http://ss64.com/nt/syntax-substring.html"> Variable Substring </a></p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/bc.html b/help/en/bash/bc.html
new file mode 100644
index 0000000..2766e18
--- /dev/null
+++ b/help/en/bash/bc.html
@@ -0,0 +1,133 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>bc MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1>bc</h1>
+<p>An arbitrary precision calculator language </p>
+<pre>Syntax
+ bc <i>options</i> <i>file</i>...
+
+Options:
+ -h, --help
+ Print the usage and exit.
+
+ <i>file</i> A file containing the calculations/functions to perform.
+ May be piped from standard input
+
+ -i, --interactive
+ Force interactive mode.
+
+ -l, --mathlib
+ Define the standard math library.
+
+ -w, --warn
+ Give warnings for extensions to POSIX bc.
+
+ -s, --standard
+ Process exactly the POSIX bc language.
+
+ -q, --quiet
+ Do not print the normal GNU bc welcome.
+
+ -v, --version
+ Print the version number and copyright and quit.</pre>
+<p>bc is a language that supports arbitrary precision numbers with interactive execution of statements. bc starts by processing code from all the files listed on the command line in the order listed. After all files have been processed, bc reads from the standard input. All code is executed as it is read. (If a file contains a command to halt the processor, bc will never read from the standard input.)</p>
+<p>The most common use of bc is within a shell script, using a &quot;here&quot; document to pass the program details to bc.</p>
+<p><b>Example shell script</b></p>
+<pre>#!/bin/bash
+# bcsample - An example of calculations with bc
+if [ $# != 1 ]
+ then
+ echo "A number argument is required"
+ exit
+fi
+
+bc &lt;&lt;END-OF-INPUT
+ scale=6
+ /* first we define the function */
+ define myfunc(x){
+ return(sqrt(x) + 10);
+ }
+
+ /* then use the function to do the calculation*/
+ x=$1
+ "Processing";x;" result is ";myfunc(x)
+ quit
+END-OF-INPUT
+
+echo &quot;(to 6 decimal places)&quot;</pre>
+<p>Run the script above with:<br>
+<span class="telety">$ chmod a+x bcsample<br>
+$ ./bcsample 125 </span></p>
+<p><b>Standard functions supported by bc</b></p>
+<p><span class="telety">length ( expression )</span><br>
+The value of the length function is the number of significant digits in the expression. <br>
+<span class="telety">read ( )</span><br>
+Read a number from the standard input, regardless of where the function occurs. Beware, this can cause problems with the mixing of data and program in the standard input. The best use for this function is in a previously written program that needs input from the user, but never allows program code to be input from the user. </p>
+<p><span class="telety">scale ( expression )</span><br>
+The number of digits after the decimal point in the expression. </p>
+<p><span class="telety">sqrt ( expression )</span><br>
+The square root of the expression.</p>
+<p> Most standard math expressions are of course supported: <span class="telety"> + - / * % ^ </span></p>
+<p><span class="telety">++ var</span><br>
+increment the variable by one and set the new value as the result of the expression. </p>
+<p><span class="telety">var ++</span><br>
+The result of the expression is the value of the variable and the variable is then incremented by one. </p>
+<p><span class="telety">-- var</span><br>
+decrement the variable by one and set the new value as the result of the expression. <br>
+<br>
+<span class="telety">var --</span><br>
+The result of the expression is the value of the variable and the variable is then decremented by one. <br>
+<br>
+<span class="telety">( expr )</span><br>
+Brackets alter the standard precedence to force the evaluation of an expression. </p>
+<p><span class="telety">var = expr</span><br>
+The variable var is assigned the value of the expression. </p>
+<p>Relational expressions and Boolean operations are also legal, look at the full bc man page for more </p>
+<p><b>Comments</b><br>
+/* In-line comments */<br>
+# single line comment. The end of line character is not part of the comment and is processed normally. </p>
+<p><i>&ldquo;If I were again beginning my studies, I would follow the advice of Plato and start with mathematics&rdquo; - Galileo</i></p>
+<p><b>Related bash commands</b>:<br>
+ <br>
+ <a href="dc.html">dc</a> - Desk Calculator<br>
+</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/bg.html b/help/en/bash/bg.html
new file mode 100644
index 0000000..8f85295
--- /dev/null
+++ b/help/en/bash/bg.html
@@ -0,0 +1,64 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>bg MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1>bg</h1>
+<p>Send job to background</p>
+<pre>Syntax
+ bg [<i>PID</i>...]
+
+Options:
+ If PID is specified, the jobs with the specified group ids are put in the background.</pre>
+<p>Send the specified jobs to the background. A background job is executed simultaneously with fish, and does not have access to the keyboard. If no job is specified, the last job to be used is put in the background.</p>
+<p>The PID of the desired process is usually found by using process expansion.</p>
+<p>Example</p>
+<p>Put the job with job id 0 in the background:<span class="telety"><br>
+bg %0 </span></p>
+<p><i>"I'm not kidding myself,
+my voice is ordinary. If I stand still while
+I'm singing, I might as well go back to
+driving a truck&quot; - Elvis Presley </i></p>
+<p><b>Related bash commands</b>:<br>
+<br>
+<a href="fg.html">fg</a> - Send job to foreground <br>
+<a href="jobs.html">jobs</a> - List active jobs<br>
+<a href="suspend.html">suspend</a> - Suspend execution of this shell</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/break.html b/help/en/bash/break.html
new file mode 100644
index 0000000..06f43ad
--- /dev/null
+++ b/help/en/bash/break.html
@@ -0,0 +1,75 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>break MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> break</h1>
+<p>Exit from a <code>for</code>, <code>while</code>, <code>until</code>,
+or <code>select</code> loop</p>
+<pre>SYNTAX
+ break [<var>n</var>]</pre>
+<p>If <var>n</var> is supplied, the <var>n</var>th enclosing loop is exited. <var>n</var>
+ must be greater than or equal to 1. <br>
+ <br>
+ The return status is zero unless <var>n</var> is not greater than or equal to
+ 1. <br>
+ <br>
+ <b>Example</b></p>
+<pre>for myloop in 1 2 3 4 5
+do
+ echo -n "$myloop"
+ if [ "$myloop" -eq 3 ]
+ then
+ break # This line will break out of the loop
+ fi
+done</pre>
+<p> break is a POSIX `special' builtin</p>
+<p><i>"Don't worry about the world coming to an end today. It's already tomorrow
+ in Australia." - Charles
+Schultz</i></p>
+<p><b>Related</b>:<br>
+ <br>
+ <a href="for.html">for</a> - Expand <var>words</var>, and execute <var>commands</var><br>
+ <a href="select.html">select</a> - Accept keyboard input <br>
+ <a href="until.html">until</a> - Execute commands (until error) <br>
+ <a href="while.html">while</a> - Execute commands <br>
+ <a href="continue.html">continue</a> - Resume the next iteration of a loop <br>
+ Equivalent Windows command: <a href="../term_tools/nt/goto.html">GOTO</a> :eof - Jump to end of file </p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/builtin.html b/help/en/bash/builtin.html
new file mode 100644
index 0000000..a69ad10
--- /dev/null
+++ b/help/en/bash/builtin.html
@@ -0,0 +1,77 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>builtin MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> builtin</h1>
+<p>Run a shell builtin, passing it args, and return its exit status.</p>
+<pre>SYNTAX
+ builtin [<em>shell-builtin</em> [<em>args</em>]]</pre>
+<p>This is useful when defining a shell function with the same name as a shell builtin, retaining the functionality of the builtin within the function. <br>
+</p>
+<pre>For example, to write a function to replace `cd'
+that writes the hostname and current directory
+to an xterm title bar:
+
+ cd()
+
+ {
+
+ builtin cd "$@" && xtitle "$HOST: $PWD"
+
+ }</pre>
+<p> The return status is non-zero if shell-builtin is not a
+shell builtin command. </p>
+<p><i>&quot;More people are killed every year by pigs than by sharks, which shows just how good we are at evaluating risks&quot; - Bruce Schneier</i></p>
+<p><b>Related</b>:<br>
+ <br>
+ <a href="chroot.html">chroot</a> - Run a command with a different root directory<br>
+ <a href="cron.html">cron</a> - Daemon to execute scheduled commands<br>
+ <a href="exec.html">exec</a> - Execute a command<br>
+ <a href="if.html">if</a> - Conditionally perform a command<br>
+ <a href="nohup.html">nohup</a> - Run a command immune to hangups<br>
+ <a href="su.html">su</a> - Run a command with substitute user and group id<br>
+ <a href="shopt.html">shopt</a> - Shell Options<br>
+ <a href="source.html">.source</a>
+ - Run commands from a file <br>
+ <a href="type.html">type</a> - Describe a command <br>
+ <a href="watch.html">watch</a> - Execute/display a program periodically <br>
+Equivalent Windows command: <a href="../term_tools/nt/call.html">CALL</a> - Call one batch program from another </p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/cal.html b/help/en/bash/cal.html
new file mode 100644
index 0000000..4329af3
--- /dev/null
+++ b/help/en/bash/cal.html
@@ -0,0 +1,75 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>cal MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> cal</h1>
+<p>Display a calendar</p>
+<pre>Syntax
+ cal [-mjy] [[<i>month</i>] <i>year</i>]
+
+Options:
+
+ -m Display monday as the first day of the week.
+
+ -j Display julian dates (days one-based, numbered from January 1).
+
+ -y Display a calendar for the current year.
+
+ A single parameter specifies the 4 digit year (1 - 9999) to be displayed.
+
+ Two parameters denote the Month (1 - 12) and Year (1 - 9999).
+
+ If arguments are not specified, the current month is displayed.
+
+ A year starts on 01 Jan.</pre>
+<p><i>"If everything seems under control, then you're not going fast
+ enough&quot; - Mario
+ Andretti</i></p>
+<p><b>Related</b>:<br>
+ <br>
+ <a href="dc.html">dc</a> - Desk Calculator<br>
+ <a href="../term_tools/bash/factor.html">factor</a> - Print prime factors <br>
+ <a href="units.html">units</a> - Convert units from one scale to another<br>
+ <a href="wc.html">wc</a> - Print byte, word, and line counts<br>
+<a href="http://funrei.wordpress.com/2008/01/23/become-a-non-autistic-calendar-counting-genius/">Calculate the day of the week, for any date, in your head</a><br>
+ Equivalent Windows command: <a href="../term_tools/nt/set.html">SET</a> /A command does basic
+arithmetic.</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/case.html b/help/en/bash/case.html
new file mode 100644
index 0000000..34a7d78
--- /dev/null
+++ b/help/en/bash/case.html
@@ -0,0 +1,85 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>case MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> case</h1>
+<p>Conditionally perform a command, <code>case</code> will selectively execute
+ the <var>command-list</var> corresponding to the first <var>pattern</var> that
+ matches <var>word</var>. <br>
+</p>
+<pre>Syntax
+ case <var>word</var> in [ [(] <var>pattern</var> [| <var>pattern</var>]...) <var>command-list</var> ;;]... esac</pre>
+<span class="body">The <samp>`|'</samp> is used to separate multiple patterns,
+and the <samp>`)'</samp> operator terminates a pattern list. A list of patterns
+and an associated command-list is known as a <var>clause</var>. Each clause must
+be terminated with <samp>`;;'</samp>. <br>
+<br>
+The <var>word</var> undergoes tilde expansion, parameter expansion, command substitution,
+arithmetic expansion, and quote removal before matching is attempted. Each <var>pattern</var>
+undergoes tilde expansion, parameter expansion, command substitution, and arithmetic
+expansion. There may be an arbitrary number of <code>case</code> clauses, each
+terminated by a <samp>`;;'</samp>. The first pattern that matches determines the
+command-list that is executed. <br>
+<br>
+Here is an example using <code>case</code> in a script that could be used to describe
+one interesting feature of an animal: </span>
+<pre>echo -n "Enter the name of an animal: "
+read ANIMAL
+echo -n "The $ANIMAL has "
+case $ANIMAL in
+ horse | dog | cat) echo -n "four";;
+ man | kangaroo ) echo -n "two";;
+ *) echo -n "an unknown number of";;
+esac
+echo " legs."</pre>
+<p>The return status is zero if no <var>pattern</var> is matched.
+Otherwise, the return status is the exit status of the <var>command-list</var>
+executed. </p><p><i>I saw a woman wearing a sweatshirt with "Guess" on it. I said, "Thyroid problem?" - Arnold Schwarzenegger </i> </p>
+<p><b>Related</b>:<br>
+ <br>
+ <a href="if.html">if</a> - Conditionally perform a command <br>
+ <a href="for.html">for</a> - Expand <var>words</var>, and execute <var>commands</var>
+ <br>
+ <a href="until.html">until</a> - Execute commands (until error) <br>
+ <a href="while.html">while</a> - Execute commands<br>
+Equivalent Windows command:
+<a href="../term_tools/nt/if.html">IF</a> - Conditionally perform a command</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/cat.html b/help/en/bash/cat.html
new file mode 100644
index 0000000..f18862b
--- /dev/null
+++ b/help/en/bash/cat.html
@@ -0,0 +1,97 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>cat MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> cat</h1>
+<p>Display the contents of a file (concatenate)</p>
+<pre>Syntax
+ cat [<em>Options</em>] [<em>File</em>]...
+
+Concatenate <em>FILE</em>(s), or standard input, to standard output.
+
+ -A, --show-all equivalent to -vET
+
+ -b, --number-nonblank number nonblank output lines
+
+ -e equivalent to -vE
+
+ -E, --show-ends display $ at end of each line
+
+ -n, --number number all output lines
+
+ -s, --squeeze-blank never more than one single blank line
+
+ -t equivalent to -vT
+
+ -T, --show-tabs display TAB characters as ^I
+
+ -u (ignored)
+
+ -v, --show-nonprinting use ^ and M- notation, except for LFD and TAB
+
+ --help display this help and exit
+
+ --version output version information and exit
+
+With no <em>FILE</em>, or when <em>FILE</em> is -, read standard input.</pre>
+<p><b>Examples</b>: <br>
+ <br>
+ Display a file<br>
+ <span class="telety">$ cat myfile.txt </span></p>
+<p>Concatenate two files: <span class="telety"><br>
+$ cat file1.txt file2.txt > union.txt</span></p>
+<p>If you need to combine two files but also eliminate duplicates, this can be done with <a href="sort.html">sort</a> unique: <br>
+<span class="telety">$ sort -u file1.txt file2.txt > unique_union.txt</span></p>
+<p>Put the contents of a file into a variable<br>
+<span class="telety">$ my_variable=`cat $myfile.txt`</span></p>
+<p><i>&quot;To be nobody but yourself - in a world which is doing
+ its best, night and day, to make you like everybody else - means to fight the
+ hardest battle which any human being can fight, and never stop fighting&quot;
+ - E.
+ E. Cummings </i></p>
+<p> <b>Related</b>:<br>
+ <br>
+ <a href="cp.html">cp</a> - Copy one or more files to another location<br>
+ <a href="mv.html">mv</a> - Move or rename files or directories<br>
+<a href="../term_tools/bash/tac.html">tac</a> - Concatenate and write files in reverse <br>
+<a href="http://souptonuts.sourceforge.net/chirico/articles/1/stupidcat.html">Stupid Cat tricks</a> - by Mike Chirico<br>
+Equivalent Windows command: <a href="../term_tools/nt/type.html"> TYPE</a> - Display the contents of a text file</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/cd.html b/help/en/bash/cd.html
new file mode 100644
index 0000000..94eb0f1
--- /dev/null
+++ b/help/en/bash/cd.html
@@ -0,0 +1,98 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>cd MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> cd</h1>
+<p>Change Directory - change the current working
+ directory to a specific Folder.<br>
+</p>
+<pre>Syntax
+ cd [<i>Options</i>] [D<em>irectory</em>]
+
+Key
+ -P Do not follow symbolic links
+ -L Follow symbolic links (default)</pre>
+<p> If <var>directory</var> is not given, the value of the <code>HOME</code>
+shell variable is used. <br>
+<br>
+If the shell variable <code>CDPATH</code> exists, it is used as a search path.
+<br>
+If <var>directory</var> begins with a slash, <code>CDPATH</code> is not used.
+<br>
+<br>
+If <var>directory</var> is <samp>`-'</samp>, this will change to the previous
+directory location (equivalent to <code>$OLDPWD</code> ). <br>
+<br>
+The return status is zero if the directory is successfully changed, non-zero otherwise.
+</p>
+<p><b>Examples</b><br>
+<br>
+Move to the sybase folder<br>
+<span class="telety">$ cd /usr/local/sybase<br>
+$ pwd<br>
+/usr/local/sybase</span><br>
+<br>
+Change to another folder<br>
+<span class="telety">$ cd /var/log<br>
+$ pwd<br>
+/var/log</span><br>
+<br>
+Quickly get back<br>
+<span class="telety">$ cd - <br>
+$ pwd<br>
+/usr/local/sybase</span><br>
+<br>
+move up one folder<br>
+<span class="telety">$ cd ..<br>
+$ pwd<br>
+/usr/local/</span><br>
+<br>
+<span class="telety">$ cd</span> (Back to your home folder)</p>
+<p><i>&quot;I believe entertainment can aspire to be art, and can
+ become art, but if you set out to make art you're an idiot&quot; - <a href="http://www.stevemartin.com/">Steve
+ Martin</a> </i><br>
+ <br>
+ <b> Related</b>:<br>
+ <br>
+ <a href="pwd.html">pwd</a> - Print Working Directory<br>
+ Equivalent Windows command:
+<a href="../term_tools/nt/cd.html">CD</a> - Change Directory </p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/cfdisk.html b/help/en/bash/cfdisk.html
new file mode 100644
index 0000000..f77bb78
--- /dev/null
+++ b/help/en/bash/cfdisk.html
@@ -0,0 +1,540 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>cfdisk MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> cfdisk</h1>
+<p>Curses based disk partition table manipulator for Linux </p>
+<pre>Syntax
+ cfdisk [ -agvz ] [ -c <em>cylinders</em> ] [ -h <em>heads</em> ]
+ [ -s <em>sectors-per-track</em> ] [ -P <em>opt</em> ] [ <em>device</em> ]
+
+Options
+ -a Use an arrow cursor instead of reverse video
+ for highlighting the current partition.
+
+ -g Do not use the geometry given by the disk driver,
+ but try to guess a geometry from the partition table.
+
+ -v Print the version number and copyright.
+
+ -z Start with zeroed partition table.
+ This option is useful when you want to repartition your entire disk.
+ <I>Note:</I> this option does not zero the partition table on the disk;
+ rather, it simply starts the program without reading the existing partition table.
+ -c<I> cylinders</I>
+
+ -h<I> heads</I>
+
+ -s<I> sectors-per-track</I>
+ Override the number of cylinders, heads and sectors per track read from the BIOS.
+ If your BIOS or adapter does not supply this information or if it supplies incorrect
+ information, use these options to set the disk geometry values.
+ -P<I> opt</I>
+ Prints the partition table in specified formats.
+ <I>opt</I> can be one or more of &quot;r&quot;, &quot;s&quot; or &quot;t&quot;.
+ See the <B>p</B>rint command (below) for more information on the print formats.
+
+<i> device
+ </i>Typical values:
+ /dev/hda [<em>default</em>]
+ /dev/hdb
+ /dev/sda
+ /dev/sdb
+ /dev/sdc
+ /dev/sdd</pre>
+<P>In order to write the partition table
+<B>cfdisk </B>needs something called the `geometry' of the disk: the number
+of `heads' and the number of `sectors per track'. Linux does not
+use any geometry, so if the disk will not be accessed by other
+operating systems, you can safely accept the defaults that
+<B>cfdisk</B>
+
+chooses for you. The geometry used by
+<B>cfdisk</B>
+
+is found as follows. First the partition table is examined,
+to see what geometry was used by the previous program that
+changed it. If the partition table is empty, or contains garbage,
+or does not point at a consistent geometry, the kernel is
+asked for advice. If nothing works 255 heads and 63 sectors/track
+is assumed. The geometry can be overridden on the command line
+or by use of the `g' command. When partitioning an empty large modern
+disk, picking 255 heads and 63 sectors/track is always a good idea.
+There is no need to set the number of cylinders, since
+<B>cfdisk</B>
+
+knows the disk size.
+<P>
+Next,
+<B>cfdisk</B>
+
+tries to read the current partition table from the disk drive. If it
+is unable to figure out the partition table, an error is displayed and
+the program will exit. This might also be caused by incorrect
+geometry information, and can be overridden on the command line.
+Another way around this problem is with the
+<B>-z</B>
+
+option. This will ignore the partition table on the disk.
+<P>
+The main display is composed of four sections, from top to bottom: the
+header, the partitions, the command line and a warning line. The
+header contains the program name and version number followed by the
+disk drive and its geometry. The partitions section always displays
+the current partition table. The command line is the place where
+commands and text are entered. The available commands are usually
+displayed in brackets. The warning line is usually empty except when
+there is important information to be displayed. The current partition
+is highlighted with reverse video (or an arrow if the
+<B>-a</B>
+
+option is given). All partition specific commands apply to the
+current partition.
+<P>
+The format of the partition table in the partitions section is, from
+left to right: Name, Flags, Partition Type, Filesystem Type and Size.
+The name is the partition device name. The flags can be
+<I>Boot</I>,
+
+which designates a bootable partition or
+<I>NC</I>,
+
+which stands for &quot;Not Compatible with DOS or OS/2&quot;. DOS, OS/2 and
+possibly other operating systems require the first sector of the first
+partition on the disk and all logical partitions to begin on the
+second head. This wastes the second through the last sector of the
+first track of the first head (the first sector is taken by the
+partition table itself).
+<B>cfdisk</B>
+
+allows you to recover these &quot;lost&quot; sectors with the maximize command
+(<B>m</B>).
+
+
+<I>Note:</I>
+
+<B><a href="fdisk.html">fdisk</a></B>(8)
+
+and some early versions of DOS create all partitions with the number
+of sectors already maximized. For more information, see the maximize
+command below. The partition type can be one of
+<I>Primary</I> or <I>Logical</I>.
+
+For unallocated space on the drive, the partition type can also be
+<I>Pri/Log</I>,
+
+or empty (if the space is unusable). The filesystem type section
+displays the name of the filesystem used on the partition, if known.
+If it is unknown, then
+<I>Unknown</I>
+
+and the hex value of the filesystem type are displayed. A special
+case occurs when there are sections of the disk drive that cannot be
+used (because all of the primary partitions are used). When this is
+detected, the filesystem type is displayed as
+<I>Unusable</I>.
+
+The size field displays the size of the partition in megabytes (by
+default). It can also display the size in sectors and cylinders (see
+the change units command below). If an asterisks
+(<B>*</B>)
+
+appears after the size, this means that the partition is not aligned
+on cylinder boundaries.
+<H2>DOS 6.x WARNING</H2>
+
+<P>
+The DOS 6.x FORMAT command looks for some information in the first
+sector of the data area of the partition, and treats this information
+as more reliable than the information in the partition table. DOS
+FORMAT expects DOS FDISK to clear the first 512 bytes of the data area
+of a partition whenever a size change occurs. DOS FORMAT will look at
+this extra information even if the /U flag is given -- we consider
+this a bug in DOS FORMAT and DOS FDISK.
+<P>
+The bottom line is that if you use cfdisk or fdisk to change the size of a
+DOS partition table entry, then you must also use
+<B>dd</B>
+
+to zero the first 512 bytes of that partition before using DOS FORMAT to
+format the partition. For example, if you were using cfdisk to make a DOS
+partition table entry for /dev/hda1, then (after exiting fdisk or cfdisk
+and rebooting Linux so that the partition table information is valid) you
+would use the command &quot;dd if=/dev/zero of=/dev/hda1 bs=512 count=1&quot; to zero
+the first 512 bytes of the partition. Note:
+<P>
+<B>BE EXTREMELY CAREFUL</B>
+
+if you use the
+<B>dd</B>
+
+command, since a small typo can make all of the data on your disk useless.
+<P>
+For best results, you should always use an OS-specific partition table
+program. For example, you should make DOS partitions with the DOS FDISK
+program and Linux partitions with the Linux fdisk or Linux cfdisk program.
+<P><strong>Commands</strong>
+<B>cfdisk</B>
+
+commands can be entered by pressing the desired key (pressing
+
+<I>Enter</I>
+
+after the command is not necessary). Here is a list of the available
+commands:
+<DL COMPACT>
+<DT><B>b</B>
+
+<DD>
+Toggle bootable flag of the current partition. This allows you to
+select which primary partition is bootable on the drive.
+<DT><B>d</B>
+
+<DD>
+Delete the current partition. This will convert the current partition
+into free space and merge it with any free space immediately
+surrounding the current partition. A partition already marked as free
+space or marked as unusable cannot be deleted.
+<DT><B>g</B>
+
+<DD>
+Change the disk geometry (cylinders, heads, or sectors-per-track).
+<B>WARNING:</B>
+
+This option should only be used by people who know what they are
+doing. A command line option is also available to change the disk
+geometry. While at the change disk geometry command line, you can
+choose to change cylinders
+(<B>c</B>),
+
+heads
+(<B>h</B>),
+
+and sectors per track
+(<B>s</B>).
+
+The default value will be printed at the prompt which you can accept
+by simply pressing the
+<I>Enter</I>
+
+key, or you can exit without changes by pressing the
+
+<I>ESC</I>
+
+key. If you want to change the default value, simply enter the
+desired value and press
+<I>Enter</I>.
+
+The altered disk parameter values do not take effect until you return
+the main menu (by pressing
+<I>Enter</I> or <I>ESC</I>
+
+at the change disk geometry command line. If you change the geometry
+such that the disk appears larger, the extra sectors are added at the
+end of the disk as free space. If the disk appears smaller, the
+partitions that are beyond the new last sector are deleted and the
+last partition on the drive (or the free space at the end of the
+drive) is made to end at the new last sector.
+<DT><B>h</B>
+
+<DD>
+
+Print the help screen.
+<DT><B>m</B>
+
+<DD>
+Maximize disk usage of the current partition. This command will
+recover the the unused space between the partition table and the
+beginning of the partition, but at the cost of making the partition
+incompatible with DOS, OS/2 and possibly other operating systems.
+This option will toggle between maximal disk usage and DOS, OS/2,
+etc. compatible disk usage. The default when creating a partition is
+to create DOS, OS/2, etc. compatible partitions.
+<DT><B>n</B>
+
+<DD>
+Create new partition from free space. If the partition type is
+<I>Primary</I> or <I>Logical</I>,
+
+a partition of that type will be created, but if the partition type is
+<I>Pri/Log</I>,
+
+you will be prompted for the type you want to create. Be aware that
+(1) there are only four slots available for primary partitions and (2)
+since there can be only one extended partition, which contains all of
+the logical drives, all of the logical drives must be contiguous (with
+no intervening primary partition).
+
+<B>cfdisk</B>
+
+next prompts you for the size of the partition you want to create.
+The default size, equal to the entire free space of the current
+partition, is display in megabytes. You can either press the
+<I>Enter</I>
+
+key to accept the default size or enter a different size at the
+prompt.
+<B>cfdisk</B>
+
+accepts size entries in megabytes
+(<B>M</B>)
+
+[default], kilobytes
+(<B>K</B>),
+
+cylinders
+(<B>C</B>)
+
+and sectors
+(<B>S</B>)
+
+by entering the number immediately followed by one of
+(<B>M</B>, <B>K</B>, <B>C</B> or <B>S</B>).
+
+If the partition fills the free space available, the partition is
+created and you are returned to the main command line. Otherwise, the
+partition can be created at the beginning or the end of the free
+space, and
+
+<B>cfdisk</B>
+
+will ask you to choose where to place the partition. After the
+partition is created,
+<B>cfdisk</B>
+
+automatically adjusts the other partition's partition types if all of
+the primary partitions are used.
+<DT><B>p</B>
+
+<DD>
+Print the partition table to the screen or to a file. There are
+several different formats for the partition that you can choose from:
+<P>
+<DL COMPACT>
+ <DD>
+<DL COMPACT>
+<DT><B>r</B>
+
+<DD>
+Raw data format (exactly what would be written to disk)
+<DT><B>s</B>
+
+<DD>
+Partition table in sector order format
+<DT><B>t</B>
+
+<DD>
+Partition table in raw format
+</DL>
+</DL>
+
+<DL COMPACT>
+ <DD>
+ <p>
+ The
+ <I>raw data format</I>
+
+will print the sectors that would be written to disk if a
+ <B>w</B>rite
+
+command is selected. First, the primary partition table is printed,
+ followed by the partition tables associated with each logical
+ partition. The data is printed in hex byte by byte with 16 bytes per
+ line.
+ </p>
+ <DD>
+ <P>
+ The
+ <I>partition table in sector order format</I>
+
+will print the partition table ordered by sector number. The fields,
+ from left to right, are the number of the partition, the partition
+ type, the first sector, the last sector, the offset from the first
+ sector of the partition to the start of the data, the length of the
+ partition, the filesystem type (with the hex value in parenthesis),
+ and the flags (with the hex value in parenthesis). In addition to the
+ primary and logical partitions, free and unusable space is printed and
+ the extended partition is printed before the first logical partition.
+ <P>
+ If a partition does not start or end on a cylinder boundary or if the
+ partition length is not divisible by the cylinder size, an asterisks
+ (<B>*</B>)
+
+is printed after the non-aligned sector number/count. This usually
+ indicates that a partition was created by an operating system that
+ either does not align partitions to cylinder boundaries or that used
+ different disk geometry information. If you know the disk geometry of
+ the other operating system, you could enter the geometry information
+ with the change geometry command
+ (<B>g</B>).
+
+
+ <P>
+ For the first partition on the disk and for all logical partitions, if
+ the offset from the beginning of the partition is not equal to the
+ number of sectors per track (i.e., the data does not start on the
+ first head), a number sign
+ (<B>#</B>)
+
+is printed after the offset. For the remaining partitions, if the
+ offset is not zero, a number sign will be printed after the offset.
+ This corresponds to the
+ <I>NC</I>
+
+flag in the partitions section of the main display.
+ <P>
+ The
+ <I>partition table in raw format</I>
+
+will print the partition table ordered by partition number. It will
+ leave out all free and unusable space. The fields, from left to
+ right, are the number of the partition, the flags (in hex), the
+ starting head, sector and cylinder, the filesystem ID (in hex), the
+ ending head, sector and cylinder, the starting sector in the partition
+ and the number of sectors in the partition. The information in this
+ table can be directly translated to the
+ <I>raw data format</I>.
+
+<P>
+
+The partition table entries only have 10 bits available to represent
+ the starting and ending cylinders. Thus, when the absolute starting
+ (ending) sector number is on a cylinder greater than 1023, the maximal
+ values for starting (ending) head, sector and cylinder are printed.
+ This is the method used by OS/2, and thus fixes the problems
+ associated with OS/2's fdisk rewriting the partition table when it is
+ not in this format. Since Linux and OS/2 use absolute sector counts,
+ the values in the starting and ending head, sector and cylinder are
+ not used.
+</DL>
+<DT><B>q</B>
+
+<DD>
+Quit program. This will exit the program without writing any data to
+disk.
+<DT><B>t</B>
+
+<DD>
+Change the filesystem type. By default, new partitions are created as
+<I>Linux</I>
+
+partitions, but since
+
+<B>cfdisk</B>
+
+can create partitions for other operating systems, change partition
+type allows you to enter the hex value of the filesystem you desire.
+A list of the know filesystem types is displayed. You can type in the
+filesystem type at the prompt or accept the default filesystem type
+[<I>Linux</I>].
+
+<DT><B>u</B>
+
+<DD>
+Change units of the partition size display. It will rotate through
+megabytes, sectors and cylinders.
+<DT><B>W</B>
+
+<DD>
+Write partition table to disk (must enter an upper case W). Since
+this might destroy data on the disk, you must either confirm or deny
+the write by entering `yes' or `no'. If you enter `yes',
+<B>cfdisk</B>
+
+will write the partition table to disk and the tell the kernel to
+re-read the partition table from the disk. The re-reading of the
+partition table works is most cases, but I have seen it fail. Don't
+panic. It will be correct after you reboot the system. In all cases,
+I still recommend rebooting the system--just to be safe.
+<DT><I>Up Arrow</I>
+
+<DT><I>Down Arrow</I>
+
+<DD>
+Move cursor to the previous or next partition. If there are more
+partitions than can be displayed on a screen, you can display the next
+(previous) set of partitions by moving down (up) at the last (first)
+partition displayed on the screen.
+<DT><I>CTRL-L</I>
+
+<DD>
+Redraws the screen. In case something goes wrong and you cannot read
+anything, you can refresh the screen from the main command line.
+<DT><B>?</B>
+
+<DD>
+Print the help screen.
+<P>
+
+All of the commands can be entered with either upper or lower case
+letters (except for
+<B>W</B>rites).
+
+When in a sub-menu or at a prompt to enter a filename, you can hit the
+<I>ESC</I>
+
+key to return to the main command line.
+</DL>
+
+<H2>EXIT STATUS</H2>
+
+
+0: No errors; 1: Invocation error; 2: I/O error;
+3: cannot get geometry; 4: bad partition table on disk.
+
+
+<H2>BUGS</H2>
+
+<p>The current version does not support multiple disks.</p>
+<p><i>"When I'm reading material, if I'm a little bit afraid of a
+ part and I'm willing to admit that to myself, then I'll do it, definitely. If
+ I'm worried about being able to do it, to get it - I absolutely just love it&quot; - Jack
+ Lemmon</i>
+</p>
+<p><b>R</b><b>elated</b>:<br>
+ <br>
+ <a href="fdisk.html">fdisk</a> - disk partition table manipulator<br>
+ <a href="fdformat.html">fdformat</a> - Low-level format a floppy disk<br>
+ mkfs - <br>
+ parted -<br>
+ sfdisk - <br>
+Equivalent Windows command: <a href="../term_tools/nt/format.html">FORMAT</a> - Format a disk</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/chgrp.html b/help/en/bash/chgrp.html
new file mode 100644
index 0000000..ca1672f
--- /dev/null
+++ b/help/en/bash/chgrp.html
@@ -0,0 +1,92 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>chgrp MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> chgrp</h1>
+<p>Change group ownership<br>
+ <br>
+ 'chgrp' changes the group ownership of each given <em>File</em> to <em>Group</em> (which can be
+ either a group name or a numeric group id) or to match the same group as an existing reference
+file. </p>
+<pre>Syntax
+ chgrp [<em>Options</em>]... {<em>Group</em> | --reference=<em>File</em>} <em>File</em>...
+
+Key
+
+ -c
+ --changes
+ Verbosely describe the action for each <em>File</em> whose group actually
+ changes.
+
+ -f
+ --silent
+ --quiet
+ Do not print error messages about files whose group cannot be
+ changed.
+
+ -f
+ --no-dereference
+ Act on symbolic links themselves instead of what they point to.
+ Only available if the `lchown' system call is provided.
+
+ --reference=<em>FILE</em>
+ Use the group of the reference <em>FILE</em> instead of an explicit <em>GROUP</em>.
+
+ -v
+ --verbose
+ Verbosely describe the action or non-action taken for every <em>File</em>.
+
+ -R
+ --recursive
+ Recursively change the group ownership of directories and their
+ contents.</pre>
+<p><b>Example<br>
+ <br>
+ </b> Make Oracle the owner of the database directory<br>
+ <span class="code">$ chgrp oracle /usr/database</span> </p>
+<p><em>Groupthink - Tendency of decision makers to join together around a policy or person without questioning basic assumptions.</em></p>
+<p><b>Related</b>:<br>
+ <a href="chmod.html"><br>
+ chmod</a> - Change access permissions<br>
+ <a href="chown.html">chown</a> - Change file owner and group<br>
+<a href="../term_tools/bash/syntax-permissions.html">bash syntax - Permissions</a><br>
+Equivalent Windows command: <a href="../term_tools/nt/cacls.html">CACLS</a> - Change file permissions</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/chkconfig.html b/help/en/bash/chkconfig.html
new file mode 100644
index 0000000..f1e9777
--- /dev/null
+++ b/help/en/bash/chkconfig.html
@@ -0,0 +1,110 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>chkconfig MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1>chkconfig</h1>
+<p>Update and query runlevel information for system services.</p>
+<pre>Syntax
+ chkconfig --list [<i>name</i>]<br> chkconfig --add <i>name</i><br> chkconfig --del <i>name</i><br> chkconfig [--level <i>levels</i>] <i>name</i> &lt;on|off|reset&gt;<br> chkconfig [--level <i>levels</i>] <i>name</i>
+
+Options:
+ --level <i>levels</i>
+ The run levels an operation should pertain to.
+ Given as a string of numbers from 0 to 7.
+ For example, --level 35 specifies runlevels 3 and 5.
+
+ --add <i>name</i>
+ Add a new service for management by chkconfig.
+ When a new service is added, chkconfig ensures that the
+ service has either a start or a kill entry in every runlevel.
+ If any runlevel is missing such an entry, chkconfig creates
+ the appropriate entry as specified by the default values in
+ the init script. Note that default entries in LSB-delimited
+ 'INIT INFO' sections take precedence over the default runlevels
+ in the initscript.
+ --del <i>name</i>
+ Delete the service from chkconfig management, and remove any
+ links in /etc/rc[0-6].d which pertain to it.
+
+ Note that future package installs for this service may
+ run chkconfig --add, which will re-add such links.
+ To disable a service, run chkconfig name off.
+
+ --list <i>name</i>
+ List all of the services which chkconfig knows about, and
+ whether they are stopped or started in each runlevel.
+ If <i>name </i>is specified, information is only displayed about service <i>name</i>. </pre>
+<p>chkconfig provides a simple command-line tool for maintaining the /etc/rc[0-6].d directory hierarchy by relieving system administrators of the task of directly manipulating the numerous symbolic links in those directories.</p>
+<p>This implementation of chkconfig was inspired by the chkconfig command present in the IRIX operating system. Rather than maintaining configuration information outside of the <span class="code">/etc/rc[0-6].d</span> hierarchy, however, this version directly manages the symlinks in <span class="code">/etc/rc[0-6].d</span>. This leaves all of the configuration information regarding what services init starts in a single location.</p>
+<p>chkconfig has five distinct functions: adding new services for management, removing services from management, listing the current startup information for services, changing the startup information for services, and checking the startup state of a particular service.</p>
+<p>When chkconfig is run without any options, it displays usage information. If only a service name is given, it checks to see if the service is configured to be started in the current runlevel. If it is, chkconfig returns true; otherwise it returns false. The --level option may be used to have chkconfig query an alternative runlevel rather than the current one.</p>
+<p>If one of <b>on, off,</b> or <b>reset</b> is specified after the service name, chkconfig changes the startup information for the specified service. The on and off flags cause the service to be started or stopped, respectively, in the runlevels being changed. The <b>reset</b> flag resets the startup information for the service to whatever is specified in the init script in question.</p>
+<p>By default, the on and off options affect only runlevels 2, 3, 4, and 5, while reset affects all of the runlevels. The --level option may be used to specify which runlevels are affected.</p>
+<p>Note that for every service, each runlevel has either a start script or a stop script. When switching runlevels, init will not re-start an already-started service, and will not re-stop a service that is not running.</p>
+<p>chkconfig also can manage xinetd scripts via the means of xinetd.d configuration files. Note that only the on, off, and --list commands are supported for xinetd.d services. </p>
+<p><b>Runlevel Files</b></p>
+<p>Each service which should be manageable by chkconfig needs two or more commented lines added to its<span class="code"> init.d</span> script. The first line tells <b>chkconfig</b> what runlevels the service should be started in by default, as well as the start and stop priority levels. If the service should not, by default, be started in any runlevels, a - should be used in place of the runlevels list. The second line contains a description for the service, and may be extended across multiple lines with backslash continuation.</p>
+<p>For example, random.init has these three lines:</p>
+<p class="code"># chkconfig: 2345 20 80<br>
+# description: Saves and restores system entropy pool for \<br>
+# higher quality random number generation.</p>
+<p>This says that the random script should be started in levels 2, 3, 4, and 5, that its start priority should be 20, and that its stop priority should be 80. You should be able to figure out what the description says; the \ causes the line to be continued. The extra space in front of the line is ignored. </p>
+<p><b>Examples</b></p>
+<p># List all the startup services, and sort alphabetically:<br>
+<span class="code">$ sudo chkconfig --list | sort | less</span></p>
+<p># List the finger service:<span class="code"><br>
+$ sudo chkconfig --list finger<br>
+<br>
+</span>#
+query a service in /etc/rc.d, and see the service settings for each runlevel<span class="code">:<br>
+$ sudo chkconfig --list anacron<br>
+anacron 0:off 1:off 2:on 3:on 4:on 5:on 6:off</span></p>
+<p># Turn nscd off in runlevels 3, 4, and 5<br>
+<span class="code">$ sudo chkconfig --level 345 nscd off</span></p>
+<p><i>&ldquo;Did you ever stop to think, and forget to start again?&rdquo; - A. A. Milne</i></p>
+<p><b>Related</b>:<br>
+<br>
+init(8) <br>
+lspci - list all PCI devices<br>
+ntsysv(8) <br>
+system-config-services(8) <br>
+Windows Equivalent: <a href="../term_tools/nt/syntax-services.html">Services</a></p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/chmod.html b/help/en/bash/chmod.html
new file mode 100644
index 0000000..83198b5
--- /dev/null
+++ b/help/en/bash/chmod.html
@@ -0,0 +1,373 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>chmod MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<style type="text/css">
+<!--
+.tab1
+{
+ background-color: #ddd;
+ border-collapse: collapse;
+}
+.tab1 td
+{
+ border-bottom: 1px solid #999;
+ padding: 2px 8px;
+}
+.tab1 tbody tr:hover td
+{
+ background-color: #ccc;
+}
+
+-->
+</style>
+
+<script type="text/javascript">
+<!--
+
+/*
+Jeroen's Chmod Calculator- By Jeroen Vermeulen of Alphamega Hosting <jeroen@alphamegahosting.com>
+Visit http://www.javascriptkit.com for this script and more
+This notice must stay intact
+*/
+
+function octalchange()
+{
+ var val = document.chmod.t_total.value;
+ var ownerbin = parseInt(val.charAt(0)).toString(2);
+ while (ownerbin.length<3) { ownerbin="0"+ownerbin; };
+ var groupbin = parseInt(val.charAt(1)).toString(2);
+ while (groupbin.length<3) { groupbin="0"+groupbin; };
+ var otherbin = parseInt(val.charAt(2)).toString(2);
+ while (otherbin.length<3) { otherbin="0"+otherbin; };
+ document.chmod.owner4.checked = parseInt(ownerbin.charAt(0));
+ document.chmod.owner2.checked = parseInt(ownerbin.charAt(1));
+ document.chmod.owner1.checked = parseInt(ownerbin.charAt(2));
+ document.chmod.group4.checked = parseInt(groupbin.charAt(0));
+ document.chmod.group2.checked = parseInt(groupbin.charAt(1));
+ document.chmod.group1.checked = parseInt(groupbin.charAt(2));
+ document.chmod.other4.checked = parseInt(otherbin.charAt(0));
+ document.chmod.other2.checked = parseInt(otherbin.charAt(1));
+ document.chmod.other1.checked = parseInt(otherbin.charAt(2));
+ calc_chmod(1);
+};
+
+function calc_chmod(nototals)
+{
+ var users = new Array("owner", "group", "other");
+ var totals = new Array("","","");
+ var syms = new Array("","","");
+
+ for (var i=0; i<users.length; i++)
+ {
+ var user=users[i];
+ var field4 = user + "4";
+ var field2 = user + "2";
+ var field1 = user + "1";
+ //var total = "t_" + user;
+ var symbolic = "sym_" + user;
+ var number = 0;
+ var sym_string = "";
+
+ if (document.chmod[field4].checked == true) { number += 4; }
+ if (document.chmod[field2].checked == true) { number += 2; }
+ if (document.chmod[field1].checked == true) { number += 1; }
+
+ if (document.chmod[field4].checked == true) {
+ sym_string += "r";
+ } else {
+ sym_string += "-";
+ }
+ if (document.chmod[field2].checked == true) {
+ sym_string += "w";
+ } else {
+ sym_string += "-";
+ }
+ if (document.chmod[field1].checked == true) {
+ sym_string += "x";
+ } else {
+ sym_string += "-";
+ }
+
+ //if (number == 0) { number = ""; }
+ //document.chmod[total].value =
+ totals[i] = totals[i]+number;
+ syms[i] = syms[i]+sym_string;
+
+ };
+ if (!nototals) document.chmod.t_total.value = totals[0] + totals[1] + totals[2];
+ document.chmod.sym_total.value = "-" + syms[0] + syms[1] + syms[2];
+}
+window.onload=octalchange
+//-->
+</script>
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1>chmod</h1>
+<p>Change access permissions, change mode. </p>
+<pre>Syntax
+ chmod [<i>Options</i>]... <i>Mode</i> [,<i>Mode</i>]... <i>file</i>...
+
+ chmod [<i>Options</i>]... <i>Numeric_Mode </i><i>file</i>...
+
+ chmod [<i>Options</i>]... --reference=<i>RFile</i> <i>file</i>...
+
+Options
+ -f, --silent, --quiet suppress most error messages
+
+ -v, --verbose output a diagnostic for every file processed
+ -c, --changes like verbose but report only when a change is made
+
+ --reference=<i>RFile</i> use <i>RFile</i>'s mode instead of MODE values
+
+ -R, --recursive change files and directories recursively
+
+ --help display help and exit
+
+ --version output version information and exit</pre>
+<p> chmod changes the permissions of each given <i>file</i> according
+to <i>mode</i>, where <i>mode</i> describes the permissions to modify. <i>Mode</i> can be specified with octal numbers or with letters. Using letters is easier to understand for most people. </p>
+<form name="chmod">
+<TABLE BORDER="0" CELLSPACING="0" CELLPADDING="0" style="font:normal 12px Verdana";>
+<TR ALIGN="LEFT" VALIGN="MIDDLE">
+<TD>Permissions: </TD>
+<TD><input type="text" name="t_total" value="751" size="4" onKeyUp="octalchange()"> </TD>
+<TD><input type="text" name="sym_total" value="" size="12" READONLY="1" STYLE='border: 0px none; font-family: "Courier New", Courier, mono;'></TD>
+</TR>
+</TABLE>
+<BR>
+<table cellpadding="2" cellspacing="0" border="0" style="font:normal 12px Verdana">
+<tr bgcolor="#333333">
+<td WIDTH="60" align="left"> </td>
+<td WIDTH="55" align="center" style="color:white"><b>owner
+</b></td>
+<td WIDTH="55" align="center" style="color:white"><b>group
+</b></td>
+<td WIDTH="55" align="center" style="color:white"><b>other
+<b></b></b></td>
+</tr>
+<tr bgcolor="#dddddd">
+<td WIDTH="60" align="left" nowrap BGCOLOR="#FFFFFF">read</td>
+<td WIDTH="55" align="center" bgcolor="#EEEEEE">
+<input type="checkbox" name="owner4" value="4" onclick="calc_chmod()">
+</td>
+<td WIDTH="55" align="center" bgcolor="#ffffff"><input type="checkbox" name="group4" value="4" onclick="calc_chmod()">
+</td>
+<td WIDTH="55" align="center" bgcolor="#EEEEEE">
+<input type="checkbox" name="other4" value="4" onclick="calc_chmod()">
+</td>
+</tr>
+<tr bgcolor="#dddddd">
+<td WIDTH="60" align="left" nowrap BGCOLOR="#FFFFFF">write</td>
+<td WIDTH="55" align="center" bgcolor="#EEEEEE">
+<input type="checkbox" name="owner2" value="2" onclick="calc_chmod()"></td>
+<td WIDTH="55" align="center" bgcolor="#ffffff"><input type="checkbox" name="group2" value="2" onclick="calc_chmod()">
+</td>
+<td WIDTH="55" align="center" bgcolor="#EEEEEE">
+<input type="checkbox" name="other2" value="2" onclick="calc_chmod()">
+</td>
+</tr>
+<tr bgcolor="#dddddd">
+<td WIDTH="60" align="left" nowrap BGCOLOR="#FFFFFF">execute</td>
+<td WIDTH="55" align="center" bgcolor="#EEEEEE">
+<input type="checkbox" name="owner1" value="1" onclick="calc_chmod()">
+</td>
+<td WIDTH="55" align="center" bgcolor="#ffffff"><input type="checkbox" name="group1" value="1" onclick="calc_chmod()">
+</td>
+<td WIDTH="55" align="center" bgcolor="#EEEEEE">
+<input type="checkbox" name="other1" value="1" onclick="calc_chmod()">
+</td>
+</tr>
+</table>
+</form>
+<p><b>Numeric mode:</b></p>
+<p>From one to four octal digits<br>
+ Any omitted digits are assumed to be leading zeros. <br>
+ <br>The first digit = selects attributes for the set user
+ ID (4) and set group ID (2) and save text image (1)S<br>
+The second digit = permissions for the user who owns the file: read (4), write
+(2), and execute (1)<br>
+The third digit = permissions for other users in the file's group: read (4),
+write (2), and execute (1)<br>
+The fourth digit = permissions for other users NOT in the file's group: read
+(4), write (2), and execute (1)</p>
+<p> The octal (0-7) value is calculated by adding up the values
+ for each digit<br>
+ User (rwx) = 4+2+1 = <b>7</b><br>
+ Group(rx) = 4+1 = <b>5</b><br>
+ World (rx) = 4+1 =<b> 5</b><br>
+ chmode mode = 0755 </p>
+<p><b>Examples</b><br>
+ <br>
+<span class="code">chmod 400 <i>file</i></span> - Read by owner<br>
+<span class="code">chmod 040 <i>file</i></span> - Read by group<br>
+<span class="code">chmod 004 <i>file</i></span> - Read by world <br>
+<br>
+<span class="code">chmod 200 <i>file</i></span> - Write by owner<br>
+<span class="code">chmod 020 <i>file</i></span> - Write by group<br>
+<span class="code">chmod 002 <i>file</i></span> - Write by world<br>
+<br>
+<span class="code">chmod 100 <i>file</i></span> - execute by owner<br>
+<span class="code">chmod 010 <i>file</i></span> - execute by group<br>
+<span class="code">chmod 001 <i>file</i></span> - execute by world</p>
+<p>To combine these, just add the numbers together:<br>
+<span class="code">chmod 444 <i>file</i></span> - Allow read permission to owner and group and world<br>
+ <span class="code">chmod 777 <i>file</i></span> - Allow everyone to read, write, and execute <i> file</i></p>
+<p><b>Symbolic Mode</b>
+<p> The format of a symbolic mode is a combination of the letters <span class="telety">+-= rwxXstugoa</span><br>
+Multiple symbolic operations can be given, separated by commas. <br>
+The full syntax is <span class="code">[ugoa...][[+-=][rwxXstugo...]...][,...]</span> but this is explained below. <br>
+ <br>
+
+ A combination of the letters <span class="code">ugoa</span> controls which <b>users</b>' access to the
+ file will be changed:</p>
+<blockquote>
+<table class=tab1>
+<tbody><tr> <td><i> User</i></td>
+ <td><i>letter</i></td>
+</tr>
+<tr> <td>The user who owns it</td>
+ <td><tt>u</tt></td>
+</tr>
+<tr> <td>Other users in the file's Group</td>
+ <td><tt>g</tt></td>
+</tr>
+<tr> <td>Other users not in the file's group</td>
+ <td><p><tt>o</tt></p></td>
+</tr>
+<tr>
+<td>All users</td>
+<td>a</td>
+</tr>
+</tbody></table>
+</blockquote>
+<p>If none of these are given, the effect is as if <span class="code">a</span> were
+ given, but bits that are set in the umask are not affected.<br>
+ <br>
+ All users <span class="code">a</span> is effectively
+ user + group + others<br>
+ <br>
+ The operator '<span class="code">+</span>' causes the permissions selected to be added to the existing
+ permissions of each file; '<span class="code">-</span>' causes them to be removed; and '<span class="code">=</span>' causes them
+ to be the only permissions that the file has.<br>
+ <br>
+ The letters '<span class="code">rwxXstugo</span>' select the new <b>permissions</b> for the affected users:
+</p>
+<blockquote>
+<table class=tab1><tbody><tr> <td><i> Permission</i></td>
+ <td><i>letter</i></td>
+</tr>
+<tr> <td>Read</td>
+ <td><tt>r</tt></td>
+</tr>
+<tr> <td>Write</td>
+ <td><tt>w</tt></td>
+</tr>
+<tr> <td>Execute (or access for directories)</td>
+ <td><tt>x</tt></td>
+</tr>
+<tr>
+<td>Execute only if the file is a directory <br>
+(or already has execute permission for some user)</td>
+<td>X</td>
+</tr>
+<tr>
+<td>Set user or group ID on execution</td>
+<td>s</td>
+</tr>
+<tr>
+<td>Save program text on swap device</td>
+<td>t</td>
+</tr>
+<tr>
+<td><br>
+The permissions that the User who owns the file currently has for it</td>
+<td>u</td>
+</tr>
+<tr>
+<td>The permissions that other users in the file's Group have for it</td>
+<td>g</td>
+</tr>
+<tr>
+<td>Permissions that Other users not in the file's group have for it</td>
+<td>o</td>
+</tr>
+</tbody></table>
+</blockquote>
+<p><b>Examples</b><br>
+ Deny execute permission to everyone: <br>
+ <span class="telety">chmod a-x <i>file</i></span><br>
+ <br>
+ Allow read permission to everyone:<br>
+ <span class="telety">chmod a+r <i>file</i></span><br>
+ <br>
+ Make a file readable and writable by the group and others: <br>
+ <span class="telety">chmod go+rw <i>file</i></span></p>
+<p>Make a shell script executable by the user/owner <br>
+<span class="code">$ chmod u+x myscript.sh</span><br>
+ <br>
+ Allow everyone to read, write, and execute the file and turn on the set group-ID:
+ <br>
+ <span class="telety">chmod =rwx,g+s <i>file</i> </span><br>
+ <br>
+ Notes:<br>
+ When chmod is applied to a directory: <br>
+ read = list files in the directory<br>
+ write = add new files to the directory <br>
+ execute = access files in the directory <br>
+ <br>
+ chmod never changes the permissions of symbolic links. This is not a problem
+ since the permissions of symbolic links are never used. However, for each symbolic
+ link listed on the command line, chmod changes the permissions of the pointed-to
+ file. In contrast, chmod ignores symbolic links encountered during recursive
+ directory traversals. </p>
+<p>This page documents the GNU version of chmod.</p>
+<p><i>&quot;Whether a pretty woman grants or withholds her
+ favours, she always likes to be asked for them&quot; - Ovid
+ (Ars Amatoria) </i> </p>
+<p><b>Related</b>:<br>
+ <br>
+ access - Determine whether a file can be accessed <br>
+<a href="ls.html">ls -l</a> - List current permissions: --
+ u (owner) -- g (group) -- O (Other)<br>
+ <a href="chgrp.html">chgrp</a> - Change group ownership<br>
+<a href="chown.html">chown</a> - Change file owner and group<br>
+<a href="../term_tools/bash/syntax-permissions.html">bash syntax - Permissions</a><br>
+Equivalent Windows command: <a href="../term_tools/nt/cacls.html">CACLS</a> - Change file permissions</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/chown.html b/help/en/bash/chown.html
new file mode 100644
index 0000000..7b2dcc4
--- /dev/null
+++ b/help/en/bash/chown.html
@@ -0,0 +1,131 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>chown MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> chown</h1>
+<p>Change owner, change the user and/or group ownership of each given File to a new Owner.<br>
+Chown can also change the ownership of a file to match the user/group of an existing reference file.</p>
+<pre>SYNTAX
+ chown [<em>Options</em>]... <em>NewOwner File</em>...
+
+ chown [<em>Options</em>]... :Group <em>File</em>...
+
+ chown [<em>Options</em>]... --reference=RFILE <em>File</em>...
+
+ If used, NewOwner specifies the new owner and/or group as follows
+ (with no embedded white space):
+
+ [OWNER] [ [:.] [GROUP] ]
+
+ Some examples of how the owner/group can be specified:
+
+ OWNER
+ If only an OWNER (a user name or numeric user id) is given, that
+ user is made the owner of each given file, and the files' group is
+ not changed.
+
+ OWNER.GROUP
+ OWNER:GROUP
+ If the OWNER is followed by a colon or dot and a GROUP (a group
+ name or numeric group id), with no spaces between them, the group
+ ownership of the files is changed as well (to GROUP).
+
+ OWNER.
+ OWNER:
+ If a colon or dot but no group name follows OWNER, that user is
+ made the owner of the files and the group of the files is changed
+ to OWNER's login group.
+
+ .GROUP
+ :GROUP
+ If the colon or dot and following GROUP are given, but the owner
+ is omitted, only the group of the files is changed; in this case,
+ `chown' performs the same function as `<a href="chgrp.html">chgrp</a>'.
+
+OPTIONS:
+
+-c
+--changes
+ Verbosely describe the action for each FILE whose ownership
+ actually changes.
+
+--dereference
+ Do not act on symbolic links themselves but rather on what they
+ point to.
+
+-f
+--silent
+--quiet
+ Do not print error messages about files whose ownership cannot be
+ changed.
+
+-h
+--no-dereference
+ Act on symbolic links themselves instead of what they point to.
+ This is the default. This mode relies on the `lchown' system call.
+ On systems that do not provide the `lchown' system call, `chown'
+ fails when a file specified on the command line is a symbolic link.
+ By default, no diagnostic is issued for symbolic links encountered
+ during a recursive traversal, but see `--verbose'.
+
+--reference=<em>FILE</em>
+ Use the user and group of the reference <em>FILE</em> instead of an explicit
+ <em>NewOwner</em> value.
+
+-R
+--recursive
+ Recursively change ownership of directories and their contents.
+
+-v
+--verbose
+ Verbosely describe the action (or non-action) taken for every FILE.
+ If a symbolic link is encountered during a recursive traversal on
+ a system without the `lchown' system call, and `--no-dereference'
+ is in effect, then issue a diagnostic saying neither the symbolic
+ link nor its referent is being changed.</pre>
+<p><i>&ldquo;It is in men as in soils where sometimes there is a vein of gold which the owner knows not&rdquo; - Jonathan Swift </i></p>
+<p><b>Related</b>:<br>
+ <br>
+ <a href="chgrp.html">chgrp</a> - Change group ownership<br>
+ <a href="chmod.html">chmod</a> - Change access permissions <br>
+<a href="../term_tools/bash/syntax-permissions.html">bash syntax - Permissions</a><br>
+Equivalent Windows command:<a href="../term_tools/nt/xcacls.html"> XCACLS</a> - Change file permissions </p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/chroot.html b/help/en/bash/chroot.html
new file mode 100644
index 0000000..d524ae2
--- /dev/null
+++ b/help/en/bash/chroot.html
@@ -0,0 +1,69 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>chroot MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> chroot</h1>
+<p>Run a command with a different root directory<br>
+ 'chroot' runs a command with a specified root directory. On many systems, only
+ the super-user can do this. <br>
+</p>
+<pre>SYNTAX
+ chroot <i>NEWROOT</i> [<i>COMMAND</i> [<i>ARGS</i>]...]
+
+ chroot OPTION</pre>
+<p>Ordinarily, filenames are looked up starting at the root of the directory structure, i.e. '/' <br>
+<br>'chroot' changes the root to the directory <i>NEWROOT</i> (which must exist) and then runs <i>COMMAND</i> with optional <i>ARGS</i>. <br>
+<br>If COMMAND is not specified, the default is the value of the `SHELL' environment variable or `/bin/sh' if not set, invoked with the `-i' option. <br>
+<br>The only options are `--help' and `--version' </p>
+<p><i>A mission statement is defined as "a long awkward sentence that demonstrates management's inability to think clearly.&quot; All good companies have one. - Scott Adams, The Dilbert Principle, 1996" </i></p>
+<p><b>Related</b>:<br>
+<a href="builtin.html"><br>
+builtin</a> - Run a shell builtin<br>
+<a href="cron.html">cron</a> - Daemon to execute scheduled commands<br>
+<a href="exec.html">exec</a> - Execute a command<br>
+<a href="if.html">if</a> - Conditionally perform a command<br>
+<a href="nohup.html">nohup</a> - Run a command immune to hangups<br>
+<a href="source.html">.source</a> - Run commands from a file <br>
+<a href="su.html">su</a> - Run a command with substitute user and group id<br>
+<a href="watch.html">watch</a> - Execute/display a program periodically<br>
+Equivalent Windows command:
+RUNAS - Run command As</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/cksum.html b/help/en/bash/cksum.html
new file mode 100644
index 0000000..bb57697
--- /dev/null
+++ b/help/en/bash/cksum.html
@@ -0,0 +1,67 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>cksum MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> cksum</h1>
+<p>Print CRC checksum and byte counts<br>
+ <br>
+ Computes a cyclic redundancy check (CRC) checksum for each given <span class="code"><i>File</i></span>, or standard
+input if none are given or for a <span class="code"><i>File</i></span> of <span class="code">-</span></p>
+<pre>Syntax
+ cksum [<em>Option</em>]... [<em>File</em>]...
+</pre>
+<p>
+cksum prints the CRC checksum for each file along with the number
+of bytes in the file, and the filename unless no arguments were given.</p>
+<p>cksum is typically used to ensure that files transferred by
+ unreliable means (e.g., netnews) have not been corrupted, by comparing
+ the cksum output for the received files with the cksum output for
+ the original files (typically given in the distribution).</p>
+<p>The CRC algorithm is specified by the POSIX.2 standard. It is not
+ compatible with the BSD or System V sum algorithms; it is more robust.</p>
+<p>The only options are <span class="code">--help</span> and <span class="code">--version</span>.</p>
+<p><i>&quot;How to be green? consume less, share more, enjoy life&quot; - Penny
+ Kemp </i><br>
+ <br>
+ <b> Related</b>:<br>
+ <br>
+ <a href="sum.html">sum</a> - Print a checksum for a file</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/cmp.html b/help/en/bash/cmp.html
new file mode 100644
index 0000000..c31eb64
--- /dev/null
+++ b/help/en/bash/cmp.html
@@ -0,0 +1,124 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>cmp MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> cmp</h1>
+<p>Compare two files, and if they differ, tells the first byte and
+ line number where they differ.<br>
+ <br>
+ You can use the `cmp' command to show the offsets and line numbers where two
+ files differ. `cmp' can also show all the characters that differ between the
+two files, side by side.</p>
+<pre>Syntax
+ cmp <em>options</em>... <em>FromFile</em> [<em>ToFile</em>]
+
+Options
+ Multiple single letter options (unless they take an argument)
+ can be combined into a single command line word:
+ so `-cl' is equivalent to -c -l.
+
+-c
+ Print the differing characters. Display control characters as a
+ `^' followed by a letter of the alphabet and precede characters
+ that have the high bit set with `M-' (which stands for "meta").
+
+--ignore-initial=<i>BYTES</i>
+ Ignore any differences in the the first <i>BYTES</i> bytes of the input
+ files. Treat files with fewer than <i>BYTES</i> bytes as if they are
+ empty.
+
+-l
+ Print the (decimal) offsets and (octal) values of all differing
+ bytes.
+
+--print-chars
+ Print the differing characters. Display control characters as a
+ `^' followed by a letter of the alphabet and precede characters
+ that have the high bit set with `M-' (which stands for "meta").
+
+--quiet
+-s
+--silent
+ Do not print anything; only return an exit status indicating
+ whether the files differ.
+
+--verbose
+ Print the (decimal) offsets and (octal) values of all differing
+ bytes.
+
+-v
+--version
+ Output the version number of `cmp'.
+
+ The file name `-' is always the standard input. `cmp' also uses the
+ standard input if one file name is omitted.
+
+ An exit status of 0 means no differences were found, 1 means some
+ differences were found, and 2 means trouble.</pre>
+<p>
+ <b>Example</b></p>
+<p class="code">$ cmp tnsnames.ora tnsnames.old</p>
+<p><b>Notes</b><br>
+ `cmp' reports the differences between two files character by character, instead
+ of line by line. As a result, it is more useful than `diff' for comparing binary
+ files. For text files, `cmp' is useful mainly when you want to know only whether
+ two files are identical. <br>
+ <br>
+ For files that are identical, `cmp' produces no output. When the files differ,
+ by default, `cmp' outputs the byte offset and line number where the first difference
+ occurs. You can use the `-s' option to suppress that information, so that `cmp'
+ produces no output and reports whether the files differ using only its exit
+ status. <br>
+ Unlike `diff', `cmp' cannot compare directories; it can only compare two files.<br>
+ <br>
+ <i>"First rate people hire other first rate people. Second rate people hire
+ third rate people. Third rate people hire fifth rate people&quot; - Andr&eacute; Weil</i> </p>
+<p><b>Related</b>:<br>
+ <a href="comm.html"><br>
+ comm</a> - Compare two sorted files line by line<br>
+ <a href="diff.html">diff</a> - Display the differences between two files<br>
+ <a href="diff3.html">diff3</a> - Show differences among three files<br>
+ dircmp - Compare 2 directories <br>
+ <a href="sdiff.html">sdiff</a> - merge two files interactively<br>
+Equivalent Windows commands: <a href="../term_tools/nt/comp.html">COMP</a> / <a href="../term_tools/nt/fc.html">FC</a> - Compare and display Characters/Lines
+which do not match.<br>
+(also the WINDIFF GUI)</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/comm.html b/help/en/bash/comm.html
new file mode 100644
index 0000000..62723f1
--- /dev/null
+++ b/help/en/bash/comm.html
@@ -0,0 +1,92 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>comm MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> comm</h1>
+<p>Common - compare two sorted files line by line and write to standard output:
+ <br>
+the lines that are common, plus the lines that are unique.</p>
+<pre>Syntax
+ comm [<em>options</em>]... <em>File1 File2</em>
+
+Options
+ -1 suppress lines unique to <i>file1</i>
+ -2 suppress lines unique to <i>file2</i>
+ -3 suppress lines that appear in both files
+
+ A file name of `-' means standard input.</pre>
+<p> Before `comm' can be used, the input files must be sorted using
+ the collating sequence specified by the 'LC_COLLATE' locale, with trailing newlines
+ significant. If an input file ends in a non-newline character, a newline is
+ silently appended. The 'sort' command with no options always outputs a file
+ that is suitable input to 'comm'.<br>
+ <br>
+ With no options, `comm' produces three column output. Column one contains lines
+ unique to FILE1, column two contains lines unique to FILE2, and column three
+ contains lines common to both files. Columns are separated by a single TAB character.<br>
+ <br>
+ The options -1, -2, and -3 suppress printing of the corresponding columns.<br>
+ <br>
+ Unlike some other comparison utilities, `comm' has an exit status that does
+ not depend on the result of the comparison. Upon normal completion `comm' produces
+an exit code of zero. If there is an error it exits with nonzero status. </p>
+<p><b>Examples</b></p>
+<p><span class="telety">$ comm -23 &lt;(sort words.txt | uniq) &lt;(sort countries.txt | uniq)</span></p>
+<p>If the file words.txt contains a subset of countries.txt then the above will return nothing.<br>
+If the file words.txt contains items that don't exist in countries.txt then the above will return those unique items. </p>
+<p>To return the lines that are in both words.txt and countries.txt use:</p>
+<p><span class="telety">$ comm -12 &lt;(sort words.txt | uniq) &lt;(sort countries.txt | uniq)</span><br>
+ <i><br>
+ "You don't sew with a fork, so I see no reason to eat with knitting needles&quot;
+ - Miss
+ Piggy, on eating Chinese Food</i><br>
+ <br>
+ <b>Related</b>:<br>
+ <br>
+ <a href="cmp.html">cmp</a> - Compare two files <br>
+ <a href="diff.html">diff</a> - Display the differences between two files<br>
+ <a href="diff3.html">diff3</a> - Show differences among three files<br>
+ <a href="sdiff.html">sdiff</a> - merge two files interactively<br>
+<a href="head.html">head</a> - Output the first part of file(s)<br>
+ <a href="sort.html">sort</a> - Sort text files <br>
+ Equivalent Windows commands: <a href="../term_tools/nt/comp.html">COMP</a> / <a href="../term_tools/nt/fc.html">FC</a> - Compare and display Characters/Lines which do not match.<br>
+(also the WINDIFF GUI)</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/command.html b/help/en/bash/command.html
new file mode 100644
index 0000000..57dbea9
--- /dev/null
+++ b/help/en/bash/command.html
@@ -0,0 +1,85 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>command MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> command</h1>
+<p><span class="body">Run <var>command</var> with <var>arguments</var>
+ignoring any shell function named <var>command</var>. </span></p>
+<pre>SYNTAX
+ command [-pVv] <em>command</em> [<em>arguments</em> ...]
+
+OPTIONS
+ -P Use a default path
+ -v Verbose
+ -V More verbose
+</pre>
+<p><span class="body">Only shell builtin commands or commands found
+ by searching the <code>PATH</code> are executed. If there is a shell function
+ named <code>ls</code>, running <samp>`command ls'</samp> within the function
+ will execute the external command <code>ls</code> instead of calling the function
+ recursively. <br>
+ <br>
+ The <samp>`-p'</samp> option means to use a default value for <code>$PATH</code>
+ that is guaranteed to find all of the standard utilities. The return status
+ in this case is 127 if <var>command</var> cannot be found or an error occurred,
+ and the exit status of <var>command</var> otherwise. <br>
+ <br>
+ If either the <samp>`-V'</samp> or <samp>`-v'</samp> option is supplied, a description
+ of <var>command</var> is printed. The <samp>`-v'</samp> option causes a single
+ word indicating the command or file name used to invoke <var>command</var> to
+ be displayed; the <samp>`-V'</samp> option produces a more verbose description.
+ In this case, the return status is zero if <var>command</var> is found, and
+non-zero if not. </span></p>
+<p><span class="body"><em>If you're not failing every now and again, it's a sign you're not doing anything very innovative. - Woody Allen</em><br>
+ </span><b><br>
+ Related</b>:<br>
+ <br>
+ <a href="builtin.html">builtin</a> - Run a shell builtin<br>
+ <a href="crontab.html">crontab</a> - Schedule a command to run at a later time<br>
+ <a href="chroot.html">chroot</a> - Run a command with a different root directory<br>
+ <a href="exec.html">exec</a> - Execute a command<br>
+ <a href="if.html">if</a> - Conditionally perform a command<br>
+ <a href="nohup.html">nohup</a> - Run a command immune to hangups<br>
+ <a href="source.html">.source</a> - Run commands from a file <br>
+ <a href="su.html">su</a> - Run a command with substitute user and group id<br>
+ <a href="type.html">type</a> - Describe a command <br>
+ <a href="watch.html">watch</a> - Execute/display a program periodically </p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/continue.html b/help/en/bash/continue.html
new file mode 100644
index 0000000..0fcbaa6
--- /dev/null
+++ b/help/en/bash/continue.html
@@ -0,0 +1,75 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>continue MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> continue</h1>
+<p>Resume the next iteration of an enclosing <code>for</code>, <code>while</code>,
+ <code>until</code>, or <code>select</code> loop.<br>
+</p>
+
+
+<pre>SYNTAX
+ continue [<var>n</var>]</pre>
+<p><span class="body">If <var>n</var> is supplied, the execution of the <var>n</var>th
+ enclosing loop is resumed. <var>n</var> must be greater than or equal to 1.
+ The return status is zero unless <var>n</var> is not greater than or equal to
+ 1. </span></p>
+<p><b>Example</b></p>
+<pre>for myloop in 1 2 3 4 5
+do
+ if [ "$myloop" -eq 3 ]
+ then
+ continue # Skip rest of this particular loop iteration.
+ fi
+ echo -n "$myloop"
+done</pre>
+<p><span class="body"> continue is a POSIX `special' builtin<br>
+ <br>
+ <i>&quot;We are American at puberty. We die French&quot; - Evelyn
+ Waugh </i> </span> </p>
+<p><b>Related</b>:<br>
+ <br>
+ <a href="break.html">break</a> - Exit from a loop<a href="for.html"><br>
+ for</a> - Expand <var>words</var>, and execute <var>commands</var><br>
+ <a href="if.html">if</a> - Conditionally perform a command<br>
+ <a href="until.html">until</a> - Execute commands (until error) <br>
+<a href="while.html">while</a> - Execute commands </p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/copyright.html b/help/en/bash/copyright.html
new file mode 100644
index 0000000..aa12daa
--- /dev/null
+++ b/help/en/bash/copyright.html
@@ -0,0 +1,169 @@
+<html>
+<head>
+<link rel="STYLESHEET" href="../../main.css" type="text/css">
+<title>Copyright :: Creative Commons :: Terms of Use</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head>
+<body><!-- #BeginLibraryItem "/Library/head_docs.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../../"><img src="../../images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com">
+</div>
+</form></li>
+</ul>
+</div><!-- #EndLibraryItem -->
+<h2>Terms of Use and Copyright</h2>
+<h2>Creative Commons License:</h2>
+<div align="center">
+<a name="cc"></a><table style="FONT-SIZE: 0.8em; FONT-FAMILY: Verdana, Arial, Helvetica, sans-serif" cellspacing="0" width="530" border="0" bgcolor="#FFFFFF">
+<tbody>
+<tr>
+<td background="../ccimages/deed-head-yellow.png" colspan="2" height="134"><br>
+<br>
+<br>
+<br>
+<center><strong>Attribution-Non-Commercial-Share Alike 2.0 UK: England &amp; Wales</strong>
+</center>
+</td>
+</tr>
+<tr>
+<td width="100">&nbsp;<br>
+</td>
+<td width="430" bgcolor="#FFFFFF">&nbsp;<br>
+</td>
+</tr><tr>
+<td style="PADDING-RIGHT: 10px; PADDING-LEFT: 9px; PADDING-BOTTOM: 9px; PADDING-TOP: 10px;" background="../ccimages/freedoms-header.png" colspan="2"><strong>You are free:</strong></td>
+</tr>
+<tr>
+<td>
+<center><br>
+<img src="../ccimages/share.png" width="50" height="50" /><br>
+<br>
+</center>
+</td>
+<td valign="center" bgcolor="#FFFFFF"><strong>to Share</strong> &mdash; to copy, distribute, display, and perform the work</td>
+</tr>
+<tr>
+<td>
+<center><br>
+<img src="../ccimages/remix.png" width="50" height="50" /><br>
+<br>
+</center>
+</td>
+<td valign="center" bgcolor="#FFFFFF"><strong>to Remix</strong> &mdash; to make derivative works</td>
+</tr>
+<tr>
+<td width="100">&nbsp;</td>
+<td width="430" bgcolor="#FFFFFF">&nbsp;</td>
+</tr>
+<tr>
+<td style="PADDING-RIGHT: 10px; PADDING-LEFT: 10px; PADDING-BOTTOM: 8px; PADDING-TOP: 9px" background="../ccimages/limitations-header.png" colspan="2"><strong>Under the following conditions:</strong></td>
+</tr>
+<tr>
+<td>
+<center><br>
+<img src="../ccimages/by.png" width="50" height="50" /><br>
+<br>
+</center>
+</td>
+<td valign="center" bgcolor="#FFFFFF"><strong>Attribution.</strong> You must attribute the work in the manner specified by the author or licensor (but not in any way that suggests that they endorse you or your use of the work).</td>
+</tr>
+<tr>
+<td>
+<center><br>
+<img src="../ccimages/nc.png" width="50" height="50" /><br>
+<br>
+</center>
+</td>
+<td valign="center" bgcolor="#FFFFFF"><strong>Noncommercial.</strong> You may not use this work for commercial purposes.</td>
+</tr>
+<tr>
+<td>
+<center><br>
+<img src="../ccimages/sa.png" width="50" height="50" /><br>
+<br>
+</center>
+</td>
+<td valign="center" bgcolor="#FFFFFF"><strong>Share Alike.</strong> If you alter, transform, or build upon this work, you may distribute the resulting work only under the same or similar license to this one.</td>
+</tr>
+<tr>
+<td colspan="2">
+<ul style="FONT-SIZE: 1.25em">
+<li>For any reuse or distribution, you must make clear to others the license terms of this work. The best way to do this is with a link to this web page.<br>
+<br>
+</li>
+<li>Any of the above conditions can be waived if you get permission from the copyright holder.<br>
+<br>
+</li>
+<li>Apart from the remix rights granted under this license, nothing in this license impairs or restricts the author's moral rights.</li>
+</ul>
+<br>
+</td>
+</tr>
+<tr>
+<td style="PADDING-RIGHT: 10px; PADDING-LEFT: 10px; PADDING-BOTTOM: 14px; PADDING-TOP: 10px" background="../ccimages/deed-foot-yellow.png" colspan="2"><span style="COLOR: #fff"><span style="FLOAT: right"><a style="COLOR: #ffff00" href="http://creativecommons.org/licenses/by-nc-sa/2.0/uk/">Disclaimer</a></span></span>
+<p clear="both">&nbsp;</p>
+<center><strong><span style="COLOR: #fff">Your fair use and other rights are in no way affected by the above.</span></strong><br><span style="COLOR: #fff">
+This is a human-readable summary of the <a style="COLOR: #ffff00" href="http://creativecommons.org/licenses/by-nc-sa/2.0/uk/">Legal Code (the full license)</a>.</span></center>
+</td>
+</tr>
+</tbody>
+</table></div>
+<p><b>SS64 Interpretation of &ldquo;Non-commercial&rdquo;</b></p>
+
+<p><em>Non-commercial use</em> means that users may not sell, profit from, or commercialize SS64 materials or works derived from them. The guidelines below are intended to help users determine whether or not their use of SS64 materials would be permitted by SS64 under the "non-commercial" restriction. Note that there are additional requirements (attribution and share alike) spelled out in our <a href="#cc">license</a>.</p>
+
+<ol>
+<li><strong>Commercialization is prohibited.</strong> Users may <em>not</em> directly sell or profit from SS64 materials or from works derived from SS64 materials.<br>
+<br>Example: A commercial education or training business may not offer courses based on SS64 materials if students pay a fee for those courses and the business intends to profit as a result.<br>
+<br>
+</li>
+<li><strong>Determination of commercial vs. non-commercial purpose is based on the use, <em>not</em> the user.</strong> Materials may be used by individuals, institutions, governments, corporations, or other business whether for-profit or non-profit so long as the use itself is not a commercialization of the materials or a use that is directly intended to generate sales or profit.<br>
+<br>Example: A corporation may use SS64 materials for internal professional development and training purposes.<br><br></li>
+<li><strong>Incidental charges to recover reasonable reproduction costs may be permitted.</strong> Recovery of nominal actual costs for copying small amounts (under 1000 copies) of SS64 content on paper or CDs is allowed for educational purposes so long as there is no profit motive and so long as the intended use of the copies is in compliance with all license terms. Students must be informed that the materials are freely available on the SS64 Web site and that their purchase of copied materials is optional.<br>
+<br>Example: An institution in a remote area has limited Internet access and limited network infrastructure on campus, and a professor offers to create CDs of SS64 materials relevant to her course. The professor may recover the costs of creating the CDs.</li>
+</ol>
+
+<p><b>Attribution</b></p>
+<p>For short extracts use the format: <span class="code">(c) Copyright 2010, SS64.com </span>[ hyperlinked where possible to http://ss64.com ]</p>
+<p>For entire pages and hard copies, just ensure the existing copyright notice (bottom right) remains in place. </p>
+<p>For use within a software application with limited screen estate, the attribution may be moved to the Help/About or general credits screen.</p>
+<p>If you have questions about acceptable use of SS64 materials, please
+<script type="text/javascript">
+
+<!--
+// SpamProof Spambait email Script 1.0 by Joseph McLean <flux@thecentre.com> - freeware
+// Linktext is the text you want folks to see and click upon.
+// email1 & email2 are the text on either side of your email address's @ sign.
+
+var linktext = "contact";
+var email1 = "Website";
+var email2 = "SS64.com";
+
+document.write("<a href=" + "mail" + "to:" + email1 + "@" + email2 + ">" + linktext + "<\/a>")
+//-->
+ </script>
+us.</p>
+<p><b>Mirror Sites</b></p>
+<p>While not expressly forbidden, mirror sites are not encouraged because duplicate pages on the internet tend to lower the google ranking of both sites. Of course if SS64.com were to disappear completely at some point in the future, then do 'mirror away'. </p>
+<p>Something a number of people have done which works well (and stays up-to-date) is to save the main command list (in any web browser - File, Save as) that gives you an HTML page with all the links back to ss64.com. You can then copy the HTML into your own blog or forum. Here's an example: <a href="http://pc.de/pages/nt-be">SS64 in Belorussian</a> from <a href="http://pc.de/">PC</a>. </p>
+<p><b>Terms of Use </b></p>
+<p>Your use of the SS64 website is subject to our Creative Commons License and other terms of use.<br>
+<span class="code"><br>
+</span>All information on this site is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. </p>
+<p>Except for purposes of attribution as required by our Creative Commons License, you may not use the SS64.com name in any way that claims or suggests a relationship with or endorsement by SS64.<br>
+All trademarks are for identification purposes only and are the property of
+their respective owners. </p>
+<p><a href="../../privacy.html">Privacy Policy </a></p>
+<!-- #BeginLibraryItem "/Library/foot_menu.lbi" --><div align="center"><hr size="1">
+<p id="top"><a href="#"><img src="../../images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+<p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/cp.html b/help/en/bash/cp.html
new file mode 100644
index 0000000..a20139c
--- /dev/null
+++ b/help/en/bash/cp.html
@@ -0,0 +1,124 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>cp MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> cp</h1>
+<p>Copy one or more files to another location<br>
+ <br>
+Copy SOURCE to DEST, or multiple SOURCE(s) to DIRECTORY. </p>
+<pre>Syntax
+ cp [<em>options</em>]... <em>Source</em> <em>Dest</em>
+ cp [<em>options</em>]... <em>Source</em>... <em>Directory</em>
+
+Key
+
+ -a, --archive same as -dpR
+
+ -b, --backup make backup before removal
+
+ -d, --no-dereference preserve links
+
+ -f, --force remove existing destinations, never prompt
+
+ -i, --interactive prompt before overwrite
+
+ -l, --link link files instead of copying
+
+ -p, --preserve preserve file attributes if possible
+
+ -P, --parents append source path to DIRECTORY
+
+ -r copy recursively, non-directories as files
+
+ --sparse=WHEN control creation of sparse files
+
+ -R, --recursive copy directories recursively
+
+ -s, --symbolic-link make symbolic links instead of copying
+
+ -S, --suffix=SUFFIX override the usual backup suffix
+
+ -u, --update copy only when the SOURCE file is newer
+ than the destination file or when the
+ destination file is missing
+
+ -v, --verbose explain what is being done
+
+ -V, --version-control=WORD override the usual version control
+
+ -x, --one-file-system stay on this file system
+ --help display this help and exit
+ --version output version information and exit.</pre>
+<p>By default, sparse SOURCE files are detected by a crude heuristic and the corresponding DEST file is made sparse as well. <br>
+
+That is the behavior selected by --sparse=auto. </p>
+<p>Specify --sparse=always to create a sparse DEST file whenever the SOURCE file contains a long enough sequence of zero bytes. <br>
+<br>
+Use --sparse=never to inhibit creation of sparse files. <br>
+<br>
+The backup suffix is ~, unless set with SIMPLE_BACKUP_SUFFIX. <br>
+<br>
+The version control may be set with VERSION_CONTROL, values are: t, numbered make numbered backups nil, existing numbered if numbered backups exist, simple otherwise never, simple always make simple backups <br>
+<br>
+As a special case, cp makes a backup of SOURCE when the force and backup options are given and SOURCE and DEST are the same name for an existing, regular file. </p>
+<p><b>Examples</b></p>
+<p>Copy demofile to demofile.bak : </p>
+<p><span class="code">$ cp demofile demofile.bak<br>
+</span>or<span class="code"><br>
+$ cp demofile{,.bak}</span></p>
+<p>Copy demofile.txt to demofile.bak : </p>
+<p class="code">$ file=&quot;demofile.txt&quot;<br>
+$ cp $file ${file%.*}.bak</p>
+<p>Copy floppy to home directory:</p>
+<p class="code">$ cp -f /mnt/floppy/* ~ </p>
+<p><i>“Thank you for sending me a copy of your book; I'll waste no time reading it” - Moses Hadas</i></p>
+<p><b>Related:</b><br>
+ <br>
+ <a href="dd.html">dd</a> - Data Dump - convert and copy a file (use for RAW
+ storage)<br>
+ copy - Copy groups of files in directories<br>
+ <a href="install.html">install</a> - Copy files and set attributes<br>
+ <a href="mv.html">mv</a> - Move files<br>
+ <a href="rsync.html">rsync</a> - Remote file copy (Synchronize file trees) <br>
+ <a href="tar.html">tar</a> - store or extract files to an archive (allows symbolic
+ links to be copied as links)<br>
+Equivalent Windows command: <a href="../term_tools/nt/copy.html">COPY</a> - Copy one or more files to another location</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/cron.html b/help/en/bash/cron.html
new file mode 100644
index 0000000..44c5c0e
--- /dev/null
+++ b/help/en/bash/cron.html
@@ -0,0 +1,94 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>cron MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> cron</h1>
+<p>daemon to execute scheduled commands</p>
+<pre>Syntax
+ cron</pre>
+<p> How to run the cron daemon: Cron should be started from /etc/rc
+ or /etc/rc.local. It will return immediately, so you don't need to start it
+ with '&'.<br>
+ <br>
+ What cron does<br>
+ Cron searches<span class="telety"> /var/spool/cron</span> for <a href="crontab.html">crontab</a> files which are named after accounts
+ in /etc/passwd; crontabs found are loaded into memory. Cron also searches for
+ /etc/crontab and the files in the /etc/cron.d/ directory, which are in a different
+ format. </p>
+<p>Cron then wakes up every minute, examining all stored <a href="crontab.html">crontabs</a>,
+ checking each command to see if it should be run in the current minute.<br>
+ <br>
+ <strong>Modifying a cron job</strong><br>
+ To edit a users crontab entry, log into your system for that particular user and type crontab -e.<br>
+ The default editor for the 'crontab -e' command is vi.<br>
+ Change the default editor by running: <span class="telety">export VISUAL='<em>editor</em>'</span><br>
+ <br>
+ cron checks each minute to see if its spool directory's modtime
+ (or the modtime on /etc/crontab) has changed, and if it has, cron will then
+ examine the modtime on all crontabs and reload those which have changed. Thus
+ cron need not be restarted whenever a crontab file is modfied. Note that
+ the <a href="crontab.html">crontab</a> command updates the modtime of the
+spool directory whenever it changes a crontab. </p>
+<p><strong>Mailing output</strong><br>
+ Cron will email to the <span class="telety">user</span> all output of the commands it runs, to silence this, redirect the output to a log file or to /dev/null<br>
+ You can also redirect email to the user named in the MAILTO environment variable in the crontab, if such exists. </p>
+<p>Cron comes from the word chronos, the Greek word for time.<br>
+ <br>
+ <i>&quot;If you do not love your job, change
+ it. Instead of pushing paper, push ideas. Instead of sitting down, stand
+ up and be heard. Instead of complaining, contribute. Don't get stuck in a job
+ description&quot; - <a href="http://www.socresonline.org.uk/1/4/1.html">Microsoft
+ job advert</a> </i><br>
+ <br>
+ <b> Related</b>:<br>
+ <a href="builtin.html"><br>
+ </a> <a href="crontab.html">crontab</a> - Schedule a command to run at a later
+ time<br>
+ <a href="chroot.html">chroot</a> - Run a command with a different root directory<br>
+ <a href="exec.html">exec</a> - Execute a command<br>
+ <a href="if.html">if</a> - Conditionally perform a command<br>
+ <a href="nohup.html">nohup</a> - Run a command immune to hangups<br>
+ <a href="su.html">su</a> - Run a command with substitute user and group id<br>
+ <a href="watch.html">watch</a> - Execute/display a program periodically<br>
+ <a href="source.html">.period</a> - Run commands from a file <br>
+Equivalent Windows commands:
+ <a href="../term_tools/nt/schtasks.html">schtasks</a> - Schedule a command to run at a later time</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/crontab.html b/help/en/bash/crontab.html
new file mode 100644
index 0000000..dea250b
--- /dev/null
+++ b/help/en/bash/crontab.html
@@ -0,0 +1,132 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>crontab MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> crontab (cron table)</h1>
+<p>Schedule a command to run at a later time</p>
+<pre>SYNTAX
+ crontab [ -u <em>user</em> ] <em>file</em>
+ crontab [ -u <em>user</em> ] { -l | -r | -e }
+
+Key
+ -l List - display the current crontab entries.
+
+ -r Remove the current crontab.
+
+ -e Edit the current crontab using the editor specified by the
+ VISUAL or EDITOR environment variables.
+ After you exit from the editor, the modified crontab will be installed automatically.
+</pre>
+<p> <span class="body">Crontab is the program used to install, deinstall or list
+ the tables used to drive the <a href="cron.html">cron</a> daemon in Vixie Cron.<br>
+ Each user can have their own crontab, and though these are
+ files in /var, they are not intended to be edited
+ directly.<br>
+ <br>
+
+ If the -u option is given, it specifies the name of the
+ user whose crontab is to be tweaked. If this option is
+ not given, crontab examines "your" crontab, i.e., the
+ crontab of the person executing the command. Note that <a href="su.html">su</a> can confuse crontab and that if you are running
+ inside of <a href="su.html">su</a> you should always use the -u option for
+ safety's sake.</span><br>
+ <br>
+ <span class="telety">cron <em>file</em> </span>is used to install a new
+ crontab from some named file or standard input if the
+pseudo-filename `-' is given.</p>
+<p>Each line in the cron table follows the following format: 7 fields left to right </p>
+<table border="1" bordercolor="#333333" cellpadding="5" cellspacing="0">
+<tbody><tr><th align="left" class="body">Field</th><th align="left" class="body">Meaning</th>
+</tr><tr>
+<td width="30" align="center" class="body">1</td><td class="body">Minute (0-59)</td>
+</tr>
+<tr>
+<td align="center" class="body">2</td><td class="body">Hour (2-24)</td>
+
+</tr>
+<tr>
+<td align="center" class="body">3</td><td class="body">Day of month (1-31)</td>
+</tr>
+<tr>
+<td align="center" class="body">4</td>
+<td class="body">Month (1-12, Jan, Feb, ...)</td>
+</tr>
+<tr>
+<td align="center" class="body">5</td>
+<td class="body">Day of week (0-6) 0=Sunday, 1=Monday ... <br>
+ or Sun, Mon, Tue, Wed, Thur, Fri </td>
+</tr>
+<tr>
+
+<td align="center" class="body">6</td><td class="body">User that the command will run as</td>
+</tr>
+<tr>
+<td align="center" class="body">7</td><td class="body">Command to execute</td>
+</tr>
+</tbody></table>
+<p>There are several ways of specifying multiple values in a field:</p>
+<p> <span class="body">&#8226; The comma (',') operator specifies a list of values, for example: &quot;1,3,4,7,8&quot;<br>
+&#8226; The dash ('-') operator specifies a range of values, for example: &quot;1-6&quot;, which is equivalent to &quot;1,2,3,4,5,6&quot;<br>
+&#8226; The asterisk ('*') operator specifies all possible values for a field. e.g. every hour or every day.</span></p>
+<p>There is also an operator which some extended versions of cron support, the slash ('/') operator, which can be used to skip a given number of values. For example, &quot;*/3&quot; in the hour time field is equivalent to &quot;0,3,6,9,12,15,18,21&quot;; &quot;*&quot; specifies 'every hour' but the &quot;/3&quot; means that only the first, fourth, seventh...and such values given by &quot;*&quot; are used.</p>
+<p>Cron will email to the <span class="telety">user</span> all output of the commands it runs, to silence this, redirect the output to a log file or to /dev/null</p>
+<p><strong>Example</strong></p>
+<p>Run <span class="telety">/usr/bin/somecommand</span> at 12.59 every day and supress the output (redirect to null) <br>
+ <br>
+ <span class="telety">59 12 * * * simon /usr/bin/somecommand &gt;&gt; /dev/null 2&gt;&amp;1</span></p>
+<p><strong>Permissions</strong><br>
+If the <span class="telety">allow</span> file exists, then you must be listed therein in order to be allowed to use this command. If the allow file does not exist but the deny file does exist, then you must not be listed in the deny file in order to use this command. If neither of these files exists, then depending on site-dependent configuration parameters, only the super user will be allowed to use this command, or all users will be able to use this command.</p>
+<p><i>"Wisdom is the power to put our time and our knowledge to the
+ proper use" - Thomas
+ J. Watson </i></p>
+<p><b>Related</b>:<br>
+ <br>
+ <a href="cron.html">cron</a> - daemon to execute scheduled commands<br>
+ <a href="nice.html">nice</a> - Change job scheduling priority<br>
+ <a href="builtin.html">builtin</a> - Run a shell builtin<br>
+ <a href="chroot.html">chroot</a> - Run a command with a different root directory<br>
+ <a href="exec.html">exec</a> - Execute a command<br>
+ <a href="nohup.html">nohup</a> - Run a command immune to hangups<br>
+ <a href="source.html">.source</a> - Run commands from a file <br>
+ <a href="su.html">su</a> - Run a command with substitute user and group id<br>
+ <a href="watch.html">watch</a> - Execute/display a program periodically<br>
+Equivalent Windows command: <a href="../term_tools/nt/schtasks.html">schtasks</a> - Schedule a command to run at a later time</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/csplit.html b/help/en/bash/csplit.html
new file mode 100644
index 0000000..c00c4cd
--- /dev/null
+++ b/help/en/bash/csplit.html
@@ -0,0 +1,144 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>csplit MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> csplit</h1>
+<p>Split a file into context-determined pieces.</p>
+<pre>SYNTAX
+ csplit [<em>options</em>]... <em>INPUT</em> <em>PATTERN</em>...
+</pre>
+<p>Creates zero or more output files containing sections of
+<i>INPUT</i> (standard input if <i>INPUT</i> is - ).</p>
+<p>The contents of the output files are determined by the <i>PATTERN</i>arguments, as detailed below. An error occurs if a <i>PATTERN</i> argument
+refers to a nonexistent line of the input file (e.g., if no remaining
+line matches a given regular expression). After every <i>PATTERN</i> has been
+matched, any remaining input is copied into one last output file.<br>
+<br>
+By default, `csplit' prints the number of bytes written to each
+output file after it has been created.</p>
+<pre> The types of pattern arguments are:
+
+<i>N</i>
+ Create an output file containing the input up to but not including
+ line <i>N</i> (a positive integer). If followed by a repeat count, also
+ create an output file containing the next LINE lines of the input
+ file once for each repeat.
+
+/<i>REGEXP</i>/[<i>OFFSET</i>]
+ Create an output file containing the current line up to (but not
+ including) the next line of the input file that contains a match
+ for <i>REGEXP</i>. The optional <i>OFFSET</i> is a `+' or `-' followed by a
+ positive integer. If it is given, the input up to the matching
+ line plus or minus <i>OFFSET</i> is put into the output file, and the
+ line after that begins the next section of input.
+
+%<i>REGEXP</i>%[<i>OFFSET</i>]
+ Like the previous type, except that it does not create an output
+ file, so that section of the input file is effectively ignored.
+
+{<i>REPEAT-COUNT</i>}
+ Repeat the previous pattern <i>REPEAT-COUNT</i> additional times.
+ <i>REPEAT-COUNT</i> can either be a positive integer or an asterisk,
+ meaning repeat as many times as necessary until the input is
+ exhausted.
+</pre>
+<p>The output files' names consist of a prefix (`xx' by default)
+followed by a suffix. By default, the suffix is an ascending sequence
+of two-digit decimal numbers from `00' and up to `99'. In any case,
+concatenating the output files in sorted order by filename produces the
+original input file.<br>
+<br>
+By default, if `csplit' encounters an error or receives a hangup,
+interrupt, quit, or terminate signal, it removes any output files that
+it has created so far before it exits.</p>
+<pre> The program accepts the following options.
+
+-f <i>PREFIX</i>
+--prefix=<i>PREFIX</i>
+ Use <i>PREFIX</i> as the output file name prefix.
+
+-b <i>SUFFIX</i>
+--suffix=<i>SUFFIX</i>
+ Use <i>SUFFIX</i> as the output file name suffix. When this option is
+ specified, the suffix string must include exactly one
+ `printf(3)'-style conversion specification, possibly including
+ format specification flags, a field width, a precision
+ specifications, or all of these kinds of modifiers. The format
+ letter must convert a binary integer argument to readable form;
+ thus, only `d', `i', `u', `o', `x', and `X' conversions are
+ allowed. The entire SUFFIX is given (with the current output file
+ number) to `sprintf(3)' to form the file name suffixes for each of
+ the individual output files in turn. If this option is used, the
+ `--digits' option is ignored.
+
+-n <i>DIGITS</i>
+--digits=<i>DIGITS</i>
+ Use output file names containing numbers that are DIGITS digits
+ long instead of the default 2.
+
+-k
+--keep-files
+ Do not remove output files when errors are encountered.
+
+-z
+--elide-empty-files
+ Suppress the generation of zero-length output files. (In cases
+ where the section delimiters of the input file are supposed to
+ mark the first lines of each of the sections, the first output
+ file will generally be a zero-length file unless you use this
+ option.) The output file sequence numbers always run
+ consecutively starting from 0, even when this option is specified.
+
+-s
+-q
+--silent
+--quiet
+ Do not print counts of output file sizes.</pre>
+<p><b>Related</b>:<br>
+ <br>
+ <a href="cut.html">cut</a> - Divide a file into several parts<br>
+ <a href="fmt.html">fmt</a> - Reformat paragraph text<br>
+ <a href="fold.html">fold</a> - Wrap input lines to fit in specified width<br>
+ <a href="join.html">join</a> - Join lines on a common field <br>
+ <a href="paste.html">paste</a> - Merge lines of files<br>
+ <a href="split.html">split</a> - Split a file into fixed-size pieces<br>
+<a href="tail.html">tail</a> - Output the last part of files </p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/cut.html b/help/en/bash/cut.html
new file mode 100644
index 0000000..a3ac59e
--- /dev/null
+++ b/help/en/bash/cut.html
@@ -0,0 +1,113 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>cut MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> cut</h1>
+<p>Divide a file into several parts (columns)<br>
+ Writes to standard output selected parts of each line of each input file, or
+standard input if no files are given or for a file name of `-'.</p>
+<pre>Syntax
+ cut [<i>OPTION</i>]... [<i>FILE</i>]...
+</pre>
+<p>In the options below, BYTE-LIST, CHARACTER-LIST, and FIELD-LIST are one or more
+numbers or ranges (two numbers separated by a dash)<br>
+<br>
+Bytes, characters, and fields are are numbered starting at 1 and
+separated by commas. <br>
+Incomplete ranges may be given: <span class="code">-M </span>means <span class="code">1-M</span> &nbsp;; <span class="code">&nbsp;N-</span> means <span class="code">N</span> through end of line or last field.</p>
+<pre>Options
+
+-b <i>BYTE-LIST</i>
+--bytes=<i>BYTE-LIST</i>
+ Print only the bytes in positions listed in <i>BYTE-LIST</i>. Tabs and
+ backspaces are treated like any other character; they take up 1
+ byte.
+
+-c <i>CHARACTER-LIST</i>
+--characters=<i>CHARACTER-LIST</i>
+ Print only characters in positions listed in <i>CHARACTER-LIST</i>. The
+ same as `-b' for now, but internationalization will change that.
+ Tabs and backspaces are treated like any other character; they
+ take up 1 character.
+
+-f <i>FIELD-LIST</i>
+--fields=<i>FIELD-LIST
+</i> Print only the fields listed in <i>FIELD-LIST</i>. Fields are separated
+ by a TAB character by default.
+
+-d <i>INPUT_DELIM_BYTE</i>
+--delimiter=<i>INPUT_DELIM_BYTE</i>
+ For `-f', fields are separated in the input by the first character
+ in INPUT_DELIM_BYTE (default is TAB).
+
+-n
+ Do not split multi-byte characters (no-op for now).
+
+-s
+--only-delimited
+ For `-f', do not print lines that do not contain the field
+ separator character.
+
+--output-delimiter=<i>OUTPUT_DELIM_STRING</i>
+ For `-f', output fields are separated by <i>OUTPUT_DELIM_STRING</i> The
+ default is to use the input delimiter.</pre>
+<p><b> Example</b></p>
+<p>Parse out column 2 from a semicolon (;) delimited file:</p>
+<p class="code">$ cat myfile.txt | cut -d \; -f 2 &gt; output.txt </p>
+<p><i>&quot;It seemed the world was divided into good and bad people. The
+ good ones slept better... while the bad ones seemed to enjoy the waking hours
+ much more&quot; - Woody
+ Allen</i><br>
+ <br>
+ <b> Related</b>:<br>
+ <br>
+ <a href="csplit.html">csplit</a> - Split a file into context-determined pieces<br>
+ <a href="fmt.html">fmt</a> - Reformat paragraph text <br>
+ <a href="fold.html">fold</a> - Wrap input lines to fit in specified width<br>
+ <a href="head.html">head</a> - Output the first part of file(s) <br>
+ <a href="join.html">join</a> - Join lines on a common field <br>
+ <a href="paste.html">paste</a> - Merge lines of files<br>
+ <a href="split.html">split</a> - Split a file into fixed-size pieces<br>
+ <a href="tail.html">tail</a> - Output the last part of files <br>
+Equivalent Windows command:
+ <a href="../term_tools/nt/for_f.html">FOR</a> /F - Conditionally perform a command on items
+in a text file</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/date.html b/help/en/bash/date.html
new file mode 100644
index 0000000..8a56d9a
--- /dev/null
+++ b/help/en/bash/date.html
@@ -0,0 +1,318 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>date MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> date</h1>
+<p>Display or change the date.</p>
+<pre>Syntax
+ date [<i>option</i>]... [+<i>Format</i>]
+
+ date [<i>option</i>] [MMDDhhmm[[CC]YY][.ss]]
+</pre>
+<p>`date' with no arguments prints the current time and date, in the
+format of the <span class="code">%c</span> directive (described below).<br>
+<br>
+If given an argument that starts with a <span class="code">+</span>, <span class="code">date</span> prints the
+current time and date (or the time and date specified by the<span class="code"> --date</span> option, see below) in the format defined by that argument, which is the
+same as in the <span class="code">strftime</span> function. </p>
+<p>Except for directives, which start
+with <span class="code">%</span>, characters in the format string are printed unchanged. The
+directives are described below.</p>
+<pre>
+Options:
+ -d, --date=<i>String</i> Display time described by <i>String</i>, instead of `now'
+ this can be in almost any common format.
+ It can contain month names, timezones, `am' and `pm',
+ `yesterday', `ago', `next', etc.
+
+ -f, --file=<i>DateFile</i> like --date once for each line of <i>DateFile</i>
+ If <i>DateFile</i> is `-', use standard input. This is
+ useful when you have many dates to process,
+ because the system overhead of starting up the
+ `date' executable many times can be considerable.
+
+ -I, --iso-8601[=<i>Timespec</i>] Output an ISO-8601 compliant date/time string., `%Y-%m-%d'.
+ <i>Timespec</i>=`date' (or missing) for date only,
+ `hours', `minutes', or `seconds' for date and
+ time to the indicated precision.
+ If showing any time terms, then include the time zone
+ using the format `%z'. If `--utc' is also specified,
+ use `%Z' in place of `%z'.
+
+ -r, --reference=<i>File</i> Display the last modification time of <i>File</i>
+
+ -R, --rfc-822 Output RFC-822 compliant date string
+
+ -s, --set=<i>String</i> Set time described by <i>String</i> (see -d above)
+
+ -u, --utc, --universal Print or set Coordinated Universal Time
+
+ --help Display this help and exit
+ --version output version information and exit
+ </pre><p><i><a name="format"></a>Format</i> controls the output as follows. The only valid option for the second form <span class="code">(MMDDhhmm[[CC]YY][.ss])</span>will specify Coordinated Universal Time. </p>
+<p> Interpreted sequences are:</p>
+<pre>
+ Date:
+ D Date in mm/dd/yy format (06/14/06)
+ x Date in standard format for locale (09/12/07 for English-US)
+
+ Year:
+ C Century (20 for 2006)
+ Y Year in 4-digit format (2006)
+ y Year in 2-digit format (06)
+ G Same as 'Y'
+ g Same as 'y'
+
+ Month:
+ b Month name - abbreviated (Jan)
+ B Month name - full (January)
+ h Same as 'b'
+ m Month number (06)
+
+ Week:
+ W Week of the year (00-52)
+ V Week of the year (01-53)
+ U Same as 'W'
+
+ Day:
+ a Day of the week - abbreviated name (Mon)
+ A Day of the week - full name (Monday)
+ u Day of the week - number (Monday = 1)
+ d Day of the month - 2 digits (05)
+ e Day of the month - digit preceded by a space ( 5)
+ j Day of the year - (1-366)
+ w Same as 'u'
+
+ Time:
+ p AM or PM
+ r Time in 12-hour format (09:15:36 AM)
+ R Time in 24-hour format - no seconds (17:45)
+ T Time in 24 hour format (17:45:52)
+ X Same as 'T'
+ Z Time zone offset from UTC (-07)
+
+ Hour:
+ H Hour in 24-hour format (17)
+ I Hour in 12 hour format (05)
+ k Same as 'H'
+ l Same as 'I' (Upper-case I = Lower-case L)
+
+ Minutes & Seconds:
+ M Minutes (35)
+ S Seconds (05)
+ s Seconds elapsed since January 1, 1970 00:00:00 (1150451174.95705)
+</pre>
+<p>Here are the same format codes in alphabetical order:</p>
+<pre>
+ %% a literal %
+ %a locale's abbreviated weekday name (Sun..Sat)
+ %A locale's full weekday name, variable length (Sunday..Saturday)
+ %b locale's abbreviated month name (Jan..Dec)
+ %B locale's full month name, variable length (January..December)
+ %c locale's date and time (Sat Nov 04 12:02:33 EST 1989)
+ %d day of month (01..31)
+ %D date (mm/dd/yy)
+ %e day of month, blank padded ( 1..31)
+ %h same as %b, locale's abbreviated month name (Jan..Dec)
+ %H hour :24 hour(00..23)
+ %I hour :12 hour(01..12)
+ %j day of year (001..366)
+ %k hour :24 hour(00..23)
+ %l hour :12 hour(01..12)
+ %m month (01..12)
+ %M minute (00..59)
+ %n a newline
+ %p locale's AM or PM
+ %r time, 12-hour (hh:mm:ss [AP]M)
+ %s seconds since 00:00:00, Jan 1, 1970 (a GNU extension)
+ Note that this value is defined by the localtime system
+ call. It isn't changed by the `--date' option.
+ %S second (00..60)
+ %t a horizontal tab
+ %T time, 24-hour (hh:mm:ss)
+ %U week number of year with Sunday as first day of week (00..53)
+ %V week number of year with Monday as first day of week (01..53)
+ If the week containing January 1 has four or
+ more days in the new year, then it is considered week 1;
+ otherwise, it is week 53 of the previous year, and the next week
+ is week 1. (See the ISO 8601: 1988 standard.)
+
+ %w day of week (0..6); 0 represents Sunday
+ %W week number of year with Monday as first day of week (00..53)
+ %x locale's date representation (mm/dd/yy)
+ %X locale's time representation (%H:%M:%S)
+ %y last two digits of year (00..99)
+ %Y year (1970...)
+ %z RFC-822 style numeric timezone (-0500) (a nonstandard extension)
+ This value reflects the _current_ time zone.
+ It isn't changed by the `--date' option.
+ %Z time zone (e.g., EDT), or nothing if no time zone is determinable
+ This value reflects the _current_ time zone.
+ It isn't changed by the `--date' option.
+</pre>
+<p>By default, date pads numeric fields with zeroes. GNU date recognizes
+the following modifiers between <span class="code">%</span> and a numeric directive.<br>
+<br>
+<span class="code">-</span> (hyphen) do not pad the field; useful if the output is intended for
+human consumption.<br>
+
+<span class="code">_</span> (underscore) pad the field with spaces; useful if you need a fixed
+number of characters in the output, but zeroes are too distracting.</p>
+<p>The - and _ are GNU extensions.
+Here is an example illustrating the differences:</p>
+<pre>
+ date +%d/%m -d "Feb 1"
+ => 01/02
+ date +%-d/%-m -d "Feb 1"
+ => 1/2
+ date +%_d/%_m -d "Feb 1"
+ => 1/ 2
+</pre>
+<p>Setting the time</p>
+<p>If given an argument that does not start with <span class="code">+</span>, <span class="code">date</span> sets the
+system clock to the time and date specified by that argument (as
+described below). You must have appropriate privileges to set the
+system clock. The <span class="code">--date</span> and <span class="code">--set</span> options may not be used with
+such an argument. The <span class="code">--universal</span> option may be used with such an
+argument to indicate that the specified time and date are relative to
+Coordinated Universal Time rather than to the local time zone.<br>
+<br>
+The argument must consist entirely of digits, which have the
+following meaning:</p>
+<pre> MM month
+ DD day within month
+ HH hour
+ MM minute
+ CC first two digits of year (optional)
+ YY last two digits of year (optional)
+ SS second (optional)
+
+ The `--set' option also sets the system clock; see the examples below.</pre>
+<p><b>Examples</b><br>
+<br>
+Print the date of the day before yesterday:<br>
+ <span class="code">$ date --date='2 days ago'</span><br>
+<br>
+Rename a file with the current date and time <br>
+<span class="code">$ STAMPME=$HOME/demo_file_$(date +%Y%m%d-%H%M).txt<br>
+$ mv $HOME/demo_file</span> <span class="code">$STAMPME</span><br>
+<br>
+Print the date of the day three months and one day hence:<br>
+<span class="code">$ date --date='3 months 1 day'</span><br>
+<br>
+Print the day of year of Christmas in the current year:<br>
+<span class="code">$ date --date='25 Dec' +%j</span><br>
+<br>
+Print the current full month name and the day of the month:<br>
+<span class="code">$ date '+%B %d'</span><br>
+<br>
+But this may not be what you want because for the first nine days
+of the month, the `%d' expands to a zero-padded two-digit field,
+for example <span class="code">date -d 1may '+%B %d'</span> will print `May 01'.<br>
+<br>
+* Print a date without the leading zero for one-digit days of the
+month, you can use the (GNU extension) `-' modifier to suppress
+the padding altogether.<br>
+<span class="code">$ date -d=1may '+%B %-d'</span><br>
+<br>
+Print the current date and time in the format required by many
+non-GNU versions of `date' when setting the system clock:<br>
+<span class="code">$ date +%m%d%H%M%Y.%S</span><br>
+<br>
+Set the system date and time<br>
+<span class="code">$ date --set=&quot;2002-6-29 11:59 AM&quot; </span><br>
+<br>
+Set the system clock forward by two minutes:<br>
+<span class="code">$ date --set='+2 minutes'</span><br>
+<br>
+Print the date in the format specified by RFC-822, use <span class="code">date
+--rfc</span><br>
+I just did and saw this:<br>
+
+Mon, 25 Mar 1996 23:34:17 -0600<br>
+<br>
+To convert a date string to the number of seconds since the epoch
+(which is 1970-01-01 00:00:00 UTC), use the `--date' option with
+the `%s' format. That can be useful in sorting and/or graphing
+and/or comparing data by date. The following command outputs the
+number of the seconds since the epoch for the time one second later
+than the epoch, but in time zone five hours later (Cambridge,
+Massachusetts), thus a total of five hours and one second after
+the epoch:<br>
+<br>
+<span class="code">$ date --date='1970-01-01 00:00:01 UTC +5 hours' +%s<br>
+18001</span><br>
+<br>
+Suppose you had _not_ specified time zone information in the
+example above. Then, date would have used your computer's idea of<br>
+the time zone when interpreting the string. Here's what you would
+get if you were in Greenwich, England:<br>
+<br>
+# local time zone used<br>
+<span class="code">$ date --date='1970-01-01 00:00:01' +%s<br>
+1</span><br>
+<br>
+ If you're sorting or graphing dated data, your raw date values may
+be represented as seconds since the epoch. But few people can<br>
+look at the date `946684800' and casually note "Oh, that's the
+first second of the year 2000."<br>
+<br>
+<span class="code">$ date --date='2000-01-01 UTC' +%s<br>
+946684800</span><br>
+<br>
+To convert such an unwieldy number of seconds back to a more
+readable form, use a command like this:<br>
+<br>
+<span class="code">$ date -d '1970-01-01 946684800 sec' +"%Y-%m-%d %T %z"<br>
+2000-01-01 00:00:00 +0000</span><br>
+</p>
+<p><b> </b><i>&quot;Carpe Diem - Seize the day&quot; - Horace
+ </i><br>
+ <b><br>
+ Related</b>:<br>
+ <br>
+ <a href="cal.html">cal</a> - Display a calendar<br>
+ <a href="crontab.html">crontab</a> - Schedule a command to run at a later time<br>
+ <a href="time.html">time</a> - Measure Program Resource Use<br>
+ <a href="times.html">times</a> - User and system times <br>
+ <a href="touch.html">touch</a> - Change file timestamps <br>
+Equivalent Windows command: <a href="../term_tools/nt/date.html">DATE</a> - Display or set the date</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/dc.html b/help/en/bash/dc.html
new file mode 100644
index 0000000..cfa7e6e
--- /dev/null
+++ b/help/en/bash/dc.html
@@ -0,0 +1,94 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>dc MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> dc</h1>
+<p>Desk calculator</p>
+<pre>SYNTAX
+ dc &lt;options&gt;
+
+OPTIONS
+
+-e EXPR
+--expression=EXPR
+ Evaluate EXPR as DC commands.
+
+-f FILE
+--file=FILE
+ Read and evaluate DC commands from FILE.
+
+-h
+--help
+ Print a usage message summarizing the command-line options, then
+ exit.
+
+-V
+--version
+ Print the version information for this program, then exit.
+
+To exit, use `q'.</pre>
+<p>DESCRIPTION <br>
+ The desk calculator works with postfix notation; rather like many HP Calculators.<br>
+ Basic arithmetic uses the standard + - / * symbols but entered <b>after</b>
+ the digits<br>
+ <br>
+ so entering:<br>
+ <br>
+ 100<br>
+ 0.5<br>
+ *<br>
+ p<br>
+ <br>
+ will return 50<br>
+ <br>
+ <i>"The best way to destroy the capitalist system is to debauch the currency"
+ - John
+Keynes </i> </p>
+<p><b>Related</b>:<br>
+ <br>
+ <a href="cal.html">cal</a> - Display a calendar<br>
+ <a href="expr.html">expr</a> - Evaluate expressions<br>
+ <a href="../term_tools/bash/factor.html">factor</a> - Print prime factors <br>
+ <a href="units.html">units</a> - Convert units from one scale to another<br>
+ <a href="wc.html">wc</a> - Print byte, word, and line counts <br>
+ Equivalent Windows command: <a href="../term_tools/nt/set.html">SET</a> /A Display, set, or remove Windows environment
+variables</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/dd.html b/help/en/bash/dd.html
new file mode 100644
index 0000000..e9f5c58
--- /dev/null
+++ b/help/en/bash/dd.html
@@ -0,0 +1,126 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>dd MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> dd</h1>
+<p>Convert and copy a file, write disk headers, boot records, create a boot floppy. dd can make an exact clone of an (unmounted) disk, this will include all blank space so the output destination must be at least as large as the input. </p>
+<pre>Syntax
+ dd [<em>Options</em>]
+
+Key
+ if=<i>FILE</i>
+ Input file : Read from FILE instead of standard input.
+
+ of=<i>FILE</i>
+ Output file : Write to FILE instead of standard output. Unless `conv=notrunc'
+ is given, `dd' truncates FILE to zero bytes (or the size specified
+ with `seek=').
+
+ ibs=<em>BYTES</em>
+ Read BYTES bytes at a time.
+
+ obs=<em>BYTES</em>
+ Write BYTES bytes at a time.
+
+ bs=<em>BYTES</em>
+ Block size, both read and write <i>BYTES</i> bytes at a time. This overrides `ibs'
+ and `obs'.
+
+ cbs=<em>BYTES</em>
+ Convert BYTES bytes at a time.
+
+ skip=<em>BLOCKS</em>
+ Skip BLOCKS `ibs'-byte blocks in the input file before copying.
+
+ seek=<em>BLOCKS</em>
+ Skip BLOCKS `obs'-byte blocks in the output file before copying.
+
+ count=<em>BLOCKS</em>
+ Copy BLOCKS `ibs'-byte blocks from the input file, instead of
+ everything until the end of the file.
+
+ conv=<em>CONVERSION</em>[,<em>CONVERSION</em>]...
+ Convert the file as specified by the CONVERSION argument(s).
+ (No spaces around any comma)
+
+ Conversions:
+ `ascii' Convert EBCDIC to ASCII.
+ `ebcdic' Convert ASCII to EBCDIC.
+ `ibm' Convert ASCII to alternate EBCDIC.
+ `block' For each line in the input, output `cbs' bytes, replacing the
+ input newline with a space and padding with spaces as
+ necessary.
+ `unblock' Replace trailing spaces in each `cbs'-sized input block with a newline.
+ `lcase' Change uppercase letters to lowercase.
+ `ucase' Change lowercase letters to uppercase.
+ `swab' Swap every pair of input bytes. GNU `dd', unlike others,
+ works when an odd number of bytes are read--the last byte is
+ simply copied (since there is nothing to swap it with).
+ `noerror' Continue after read errors.
+ `notrunc' Do not truncate the output file.
+ `sync' Pad every input block to size of `ibs' with trailing zero bytes.
+ </pre>
+<p> The numeric-valued options (BYTES and BLOCKS) can be followed by a multiplier: `b'=512, `c'=1, `w'=2, `xM'=M, or any of the standard block size suffixes like `k'=1024.</p>
+<p><strong>Examples:</strong></p>
+<p>Clone one hard drive onto another<span class="code"> <br>
+$ dd if=/dev/sda of=/dev/sdb</span></p>
+<p>Clone a hard drive<span class="code"> </span>to an image file <br>
+<span class="code">$ dd if=/dev/hda of=/image.img</span></p>
+<p>Clone a hard drive to a zipped image file in 100Mb blocks <span class="code"><br>
+$ dd if=/dev/hda bs=100M | gzip -c &gt; /image.img</span></p>
+<p>Create a boot floppy:<br>
+<span class="code">$ dd if=boot.img of=/dev/fd0 bs=1440</span></p>
+<p><i> &quot;Success isn't something you chase. It's something you have
+ to put forth the effort for constantly. Then maybe it'll come when you least
+ expect it. Most people don't understand that&quot; - Michael
+ Jordan </i><br>
+ <br>
+ <b> Related</b>:<br>
+<a href="http://www.codecoffee.com/tipsforlinux/articles/036.html">CodeCoffee.com</a> - dd examples<br>
+ <a href="cp.html">cp</a> - Copy one or more files to another location<br>
+<a href="ddrescue.html">ddrescue</a> - Data recovery tool
+<br>
+ <a href="install.html">install</a> - Copy files and set attributes<br>
+ <a href="mtools.html">mtools</a> - Manipulate MS-DOS files<br>
+
+ <a href="sum.html">sum</a> - Print a checksum for a file<br>
+Equivalent Windows command: <a href="../term_tools/nt/fsutil.html">FSUTIL</a> file setzerodata</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/ddrescue.html b/help/en/bash/ddrescue.html
new file mode 100644
index 0000000..31a4d54
--- /dev/null
+++ b/help/en/bash/ddrescue.html
@@ -0,0 +1,90 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>ddrescue MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> ddrescue</h1>
+<p>Data recovery tool, save data from a crashed partition. </p>
+<pre>Syntax
+ ddrescue [<i>options</i>] <i>infile outfile</i> [<i>logfile</i>]
+
+Options:<br> -b=<i>bytes</i> Hardware block size of input device [512]
+ --block-size=<i>bytes</i><br><br> -B Show binary multipliers in numbers [default SI]
+ --binary-prefixes<br><br> -c=<i>blocks</i> Hardware blocks to copy at a time [128]
+ --cluster-size=<i>blocks</i><br><br> -C Do not read new data beyond logfile limits
+ --complete-only<br><br> -d Use direct disc access for input file
+ --direct<br><br> -e=<i>n</i> Maximum number of error areas allowed
+ --max-errors=<i>n</i><br><br> -i=<i>pos</i> Starting position in input file [0]
+ --input-position=<i>pos</i><br><br> -n Do not try to split error areas
+ --no-split<br><br> -o=<i>pos</i> Starting position in output file [ipos]
+ --output-position=<i>pos</i><br><br> -q Quiet operation
+ --quiet<br><br> -r=<i>n</i> Exit after given retries (-1=infinity) [0]
+ --max-retries=<i>n</i><br><br> -s=<i>bytes</i> Maximum size of data to be copied
+ --max-size=<i>bytes</i><br><br> -t Truncate output file
+ --truncate<br><br> -v Verbose operation
+ --verbose<br>
+ -V Output version information and exit
+ --version</pre>
+<p>Numbers may be followed by a multiplier: b = blocks, k = kB = 10^3 = 1000, Ki = KiB = 2^10 = 1024, M = 10^6, Mi = 2^20, G = 10^9, Gi = 2^30, etc...</p>
+<p><b> Installation</b></p>
+<p>Debian / Ubuntu Linux:<br>
+<span class="telety"># apt-get install ddrescue</span></p>
+<p>RedHat /Fedora /CentOS Linux:<br>
+<span class="telety"># yum -y install ddrescue</span></p>
+<p>ddrescue written by Antonio Diaz Diaz, download from the <a href="http://www.gnu.org/software/ddrescue/ddrescue.html">GNU</a> web site.<br>
+Installs as /usr/bin/ddrescue</p>
+<p><strong>Example:</strong></p>
+<p>To copy /dev/sda (damaged \device\harddisk0) to another drive /dev/sdb (empty \device\harddisk1)</p>
+<p class="telety"># ddrescue /dev/sda /dev/sdb</p>
+<p>To recover the partition data run <a href="fsck.html">fsck</a>, for example if /home (user data) is on /dev/sd<b>a</b>2, run fsck on partition /dev/sd<b>b</b>2:<br>
+<span class="telety"># fsck /dev/sdb2</span></p>
+<p>This avoids touching the damaged /dev/sda, if the procedure fails you can send the original disk to a professional data recovery service. </p>
+<p>Lastly mount the partition somewhere and see if you can access the data:<br>
+<span class="telety"># mount /dev/sdb2 /mnt/data</span></p>
+<p><i>&quot;Rescue me,
+Oh take me in your arms, Rescue me&quot; - Aretha Franklin</i><br>
+ <br>
+ <b> Related</b>:<br>
+<br>
+ info ddrescue - full ddrescue manual<br>
+dd_rescue - written by Kurt Garloff for Debian <br>
+<a href="http://www.macosxhints.com/article.php?story=20050720092514388">ddrescue for OS X</a> - macosxhints<br>
+<a href="dd.html">dd</a> - Data Dump - Convert and copy a file</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/declare.html b/help/en/bash/declare.html
new file mode 100644
index 0000000..def5fa6
--- /dev/null
+++ b/help/en/bash/declare.html
@@ -0,0 +1,107 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>declare MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> declare</h1>
+<p>Declare variables and give them attributes.</p>
+<pre>SYNTAX
+ declare [-afFrxi] [-p] [<var>name</var>[=<var>value</var>]]
+
+OPTIONS
+
+ -a Each name is an array variable.
+
+ -f Use function names only.
+<br> -F Inhibit the display of function definitions;
+ only the function name and attributes are printed.
+ (implies -f)
+
+ -i The variable is to be treated as an integer;
+ arithmetic evaluation is performed when the
+ variable is assigned a value.<br>
+ -p Display the attributes and values of each <var>name</var>.
+ When `-p' is used, additional options are ignored.
+
+ -r Make <i>name</i>s readonly. These names cannot then <br> be assigned values by subsequent assignment statements
+ or unset.
+<br> -x Mark each <i>name</i> for export to subsequent commands <br> via the environment.</pre>
+<p><span class="body">If no <var>name</var>s are given, then `declare' will display
+ the values of variables instead.</span> </p>
+<dl compact>
+ <dt><span class="body"> </span>
+ <dt><span class="body">Using <samp>`+'</samp> instead of <samp>`-'</samp> turns
+ off the attribute instead. <br>
+ <br>
+ When used in a function, <code>declare</code> makes each <var>name</var> local,
+ as with the <code>local</code> command. <br>
+ <br>
+ The <code>typeset</code> command is supplied for compatibility with the Korn
+ shell; however, it has been deprecated in favor of the <code>declare</code>
+ builtin command. <br>
+ <br>
+ The return status is zero unless an invalid option is encountered, an attempt
+ is made to define a function using <samp>`-f foo=bar'</samp>, an attempt is
+ made to assign a value to a readonly variable, an attempt is made to assign
+ a value to an array variable without using the compound assignment syntax
+ , one of the <var>names</var> is not a valid shell variable name, an attempt
+ is made to turn off readonly status for a readonly variable, an attempt is
+ made to turn off array status for an array variable, or an attempt is made
+ to display a non-existent function with <samp>`-f'</samp>. <br>
+ <br>
+ <i>"My mother never saw the irony in calling me a son-of-a-bitch." - Jack
+ Nicholson </i> </span>
+</dl>
+<p><b> Related</b>:<br>
+ <br>
+ <a href="alias.html">alias</a> - Create an alias<br>
+ <a href="env.html">env</a> - Display, set, or remove environment variables<br>
+ <a href="echo.html">echo</a> - Display message on screen <br>
+ <a href="export.html"> export</a> - Set an environment variable<br>
+ <a href="hostname.html">hostname</a> - Print or set system name<br>
+ <a href="local.html">local</a> - Create variables <br>
+ printenv - Print environment variables <br>
+ <a href="readonly.html">readonly</a> - Mark variables/functions as readonly
+ <br>
+ <a href="shift.html">shift</a> - Shift positional parameters <br>
+ Equivalent Windows command:
+ <a href="../term_tools/nt/set.html">SET</a> - Display, set, or remove Windows environment
+ variables</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/df.html b/help/en/bash/df.html
new file mode 100644
index 0000000..00a61c4
--- /dev/null
+++ b/help/en/bash/df.html
@@ -0,0 +1,170 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>df MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> df</h1>
+<p>Disk Free - display free disk space.<br>
+ With no arguments, `df' reports the space used and available on all currently
+ mounted filesystems (of all types). Otherwise, `df' reports on the filesystem
+containing each argument <i>file</i>. </p>
+<pre>SYNTAX
+ df [<i>option</i>]... [<i>file</i>]...
+
+Normally the disk space is printed in units of 1024 bytes, but this
+can be overridden.
+
+OPTIONS
+
+`-a'
+`--all'
+ Include in the listing filesystems that have a size of 0 blocks,
+ which are omitted by default. Such filesystems are typically
+ special-purpose pseudo-filesystems, such as automounter entries.
+ Also, filesystems of type "ignore" or "auto", supported by some
+ operating systems, are only included if this option is specified.
+
+`-h'
+`--human-readable'
+ Append a size letter such as `M' for megabytes to each size.
+ Powers of 1024 are used, not 1000; `M' stands for 1,048,576 bytes.
+ Use the `-H' or `--si' option if you prefer powers of 1000.
+
+`-H'
+`--si'
+ Append a size letter such as `M' for megabytes to each size. (SI
+ is the International System of Units, which defines these letters
+ as prefixes.) Powers of 1000 are used, not 1024; `M' stands for
+ 1,000,000 bytes. Use the `-h' or `--human-readable' option if you
+ prefer powers of 1024.
+
+`-i'
+`--inodes'
+ List inode usage information instead of block usage. An inode
+ (short for index node) is contains information about a file such
+ as its owner, permissions, timestamps, and location on the disk.
+
+`-k'
+`--kilobytes'
+ Print sizes in 1024-byte blocks, overriding the default block size.
+
+`-l'
+`--local'
+ Limit the listing to local filesystems. By default, remote
+ filesystems are also listed.
+
+`-m'
+`--megabytes'
+ Print sizes in megabyte (that is, 1,048,576-byte) blocks.
+
+`--no-sync'
+ Do not invoke the `sync' system call before getting any usage data.
+ This may make `df' run significantly faster on systems with many
+ disks, but on some systems (notably SunOS) the results may be
+ slightly out of date. This is the default.
+
+`-P'
+`--portability'
+ Use the POSIX output format. This is like the default format
+ except that the information about each filesystem is always
+ printed on exactly one line; a mount device is never put on a line
+ by itself. This means that if the mount device name is more than
+ 20 characters long (e.g., for some network mounts), the columns
+ are misaligned.
+
+`--sync'
+ Invoke the `sync' system call before getting any usage data. On
+ some systems (notably SunOS), doing this yields more up to date
+ results, but in general this option makes `df' much slower,
+ especially when there are many or very busy filesystems.
+
+`-t FSTYPE'
+`--type=FSTYPE'
+ Limit the listing to filesystems of type FSTYPE. Multiple
+ filesystem types can be specified by giving multiple `-t' options.
+ By default, nothing is omitted.
+
+`-T'
+`--print-type'
+ Print each filesystem's type. The types printed here are the same
+ ones you can include or exclude with `-t' and `-x'. The particular
+ types printed are whatever is supported by the system. Here are
+ some of the common names (this list is certainly not exhaustive):
+
+ `nfs'
+ An NFS filesystem, i.e., one mounted over a network from
+ another machine. This is the one type name which seems to be
+ used uniformly by all systems.
+
+ `4.2, ufs, efs...'
+ A filesystem on a locally-mounted hard disk. (The system
+ might even support more than one type here; Linux does.)
+
+ `hsfs, cdfs'
+ A filesystem on a CD-ROM drive. HP-UX uses `cdfs', most other
+ systems use `hsfs' (`hs' for `High Sierra').
+
+ `pcfs'
+ An MS-DOS filesystem, usually on a diskette.
+
+`-x FSTYPE'
+`--exclude-type=FSTYPE'
+ Limit the listing to filesystems not of type FSTYPE. Multiple
+ filesystem types can be eliminated by giving multiple `-x'
+ options. By default, no filesystem types are omitted.
+
+`-v'
+ Ignored; for compatibility with System V versions of `df'.</pre>
+<p><span class="body"> If an argument FILE is a disk device file
+ containing a mounted filesystem, `df' shows the space available on that filesystem
+ rather than on the filesystem containing the device node (i.e., the root filesystem).
+ GNU `df' does not attempt to determine the disk usage on unmounted filesystems,
+ because on most kinds of systems doing so requires extremely nonportable intimate
+ knowledge of filesystem structures.</span><br>
+ <i><br>
+ "A prediction is worth twenty explanations" - K.
+ Brecher</i><b><br>
+ <br>
+ Related</b>:<br>
+ <br>
+ <a href="du.html">du</a> - Estimate file space usage<br>
+ quot(1M), tunefs(1M), mnttab(4), attributes(5) <br>
+ Equivalent Windows command: DIRUSE - resource kit utility to show size of multiple subfolders</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/diff.html b/help/en/bash/diff.html
new file mode 100644
index 0000000..5da2b1e
--- /dev/null
+++ b/help/en/bash/diff.html
@@ -0,0 +1,438 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>diff MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> diff</h1>
+<p>Display the differences between two files, or each corresponding
+ file in two directories. <br>
+ Each set of differences is called a "diff" or "patch". For files that are identical,
+ diff normally produces no output; for binary (non-text) files, diff normally
+reports only that they are different.</p>
+<pre>Syntax
+ diff [<i>options</i>] <i>from-file to-file</i></pre>
+<pre>Options</pre><p>Multiple single letter options (unless they take an argument) can be combined into a single command line word: so `-ac' is equivalent to `-a -c'.</p>
+<pre>
+ -<i>lines</i> Show <i>lines</i> lines of context. This option is obsolete.
+
+ -a Treat all files as text and compare them line-by-
+ line, even if they do not seem to be text.
+
+ -b Ignore changes in amount of white space.
+
+ -B Ignore changes that just insert or delete blank
+ lines.
+
+ --brief
+ Report only whether the files differ, not the
+ details of the differences.
+
+ -c Use the context output format.
+
+ -C <i>lines</i>
+ --context[=<i>lines</i>]
+ Use the context output format, showing <i>lines</i> (an
+ integer) lines of context, or three if lines is not
+ given. For proper operation, patch typically needs
+ at least two lines of context.
+
+ --changed-group-format=<i>format</i>
+ Use <i>format</i> to output a line group containing dif-
+ fering lines from both files in if-then-else for-
+ mat.
+
+ -d Change the algorithm to perhaps find a smaller set
+ of changes. This makes diff slower (sometimes much
+ slower).
+
+ -D <i>name</i>
+ Make merged if-then-else format output, conditional
+ on the preprocessor macro name.
+
+ -e
+ --ed Make output that is a valid ed script.
+
+ --exclude=<i>pattern</i>
+ When comparing directories, ignore files and subdi-
+ rectories whose basenames match <i>pattern</i>.
+
+ --exclude-from=<i>file</i>
+ When comparing directories, ignore files and subdi-
+ rectories whose basenames match any pattern con-
+ tained in <i>file</i>.
+
+ --expand-tabs
+ Expand tabs to spaces in the output, to preserve
+ the alignment of tabs in the input files.
+
+ -f Make output that looks vaguely like an ed script
+ but has changes in the order they appear in the
+ file.
+
+ -F <i>regexp</i>
+ In context and unified format, for each hunk of
+ differences, show some of the last preceding line
+ that matches <i>regexp</i>.
+
+ --forward-ed
+ Make output that looks vaguely like an ed script
+ but has changes in the order they appear in the
+ file.
+
+ -h This option currently has no effect; it is present
+ for Unix compatibility.
+
+ -H Use heuristics to speed handling of large files
+ that have numerous scattered small changes.
+
+ --horizon-lines=<i>lines</i>
+ Do not discard the last <i>lines</i> lines of the common
+ prefix and the first lines lines of the common suf-
+ fix.
+
+ -i Ignore changes in case; consider upper- and lower-
+ case letters equivalent.
+
+ -I <i>regexp</i>
+ Ignore changes that just insert or delete lines
+ that match <i>regexp</i>.
+
+ --ifdef=<i>name</i>
+ Make merged if-then-else format output, conditional
+ on the preprocessor macro <i>name</i>.
+
+ --ignore-all-space
+ Ignore white space when comparing lines.
+
+ --ignore-blank-lines
+ Ignore changes that just insert or delete blank
+ lines.
+
+ --ignore-case
+ Ignore changes in case; consider upper- and lower-
+ case to be the same.
+
+ --ignore-matching-lines=<i>regexp</i>
+ Ignore changes that just insert or delete lines
+ that match <i>regexp</i>.
+
+ --ignore-space-change
+ Ignore changes in amount of white space.
+
+ --initial-tab
+ Output a tab rather than a space before the text of
+ a line in normal or context format. This causes
+ the alignment of tabs in the line to look normal.
+
+ -l Pass the output through pr to paginate it.
+
+ -L <i>label</i>
+ --label=<i>label</i>
+ Use <i>label</i> instead of the file name in the context
+ format and unified format headers.
+
+ --left-column
+ Print only the left column of two common lines in
+ side by side format.
+
+ --line-format=<i>format</i>
+ Use <i>format</i> to output all input lines in in-then-
+ else format.
+
+ --minimal
+ Change the algorithm to perhaps find a smaller set
+ of changes. This makes diff slower (sometimes much
+ slower).
+
+ -n Output RCS-format diffs; like -f except that each
+ command specifies the number of lines affected.
+
+ -N
+ --new-file
+ In directory comparison, if a file is found in only
+ one directory, treat it as present but empty in the
+ other directory.
+
+ --new-group-format=<i>format</i>
+ Use <i>format</i> to output a group of lines taken from
+ just the second file in if-then-else format.
+
+ --new-line-format=<i>format</i>
+ Use <i>format</i> to output a line taken from just the
+ second file in if-then-else format.
+
+ --old-group-format=<i>format</i>
+ Use <i>format</i> to output a group of lines taken from
+ just the first file in if-then-else format.
+
+ --old-line-format=<i>format</i>
+ Use <i>format</i> to output a line taken from just the
+ first file in if-then-else format.
+
+ -p Show which C function each change is in.
+
+ -P When comparing directories, if a file appears only
+ in the second directory of the two, treat it as
+ present but empty in the other.
+
+ --paginate
+ Pass the output through pr to paginate it.
+
+ -q Report only whether the files differ, not the
+ details of the differences.
+
+ -r When comparing directories, recursively compare any
+ subdirectories found.
+
+ --rcs Output RCS-format diffs; like -f except that each
+ command specifies the number of lines affected.
+
+ --recursive
+ When comparing directories, recursively compare any
+ subdirectories found.
+
+ --report-identical-files
+ -s Report when two files are the same.
+
+ -S <i>file</i>
+ When comparing directories, start with the file
+ <i>file</i>. This is used for resuming an aborted compar-
+ ison.
+
+ --sdiff-merge-assist
+ Print extra information to help <a href="sdiff.html">sdiff</a>. sdiff uses
+ this option when it runs diff. This option is not
+ intended for users to use directly.
+
+ --show-c-function
+ Show which C function each change is in.
+
+ --show-function-line=<i>regexp</i>
+ In context and unified format, for each hunk of
+ differences, show some of the last preceding line
+ that matches <i>regexp</i>.
+
+ --side-by-side
+ Use the side by side output format.
+
+ --speed-large-files
+ Use heuristics to speed handling of large files
+ that have numerous scattered small changes.
+
+ --starting-file=<i>file</i>
+ When comparing directories, start with the file
+ <i>file</i>. This is used for resuming an aborted compar-
+ ison.
+
+ --suppress-common-lines
+ Do not print common lines in side by side format.
+
+ -t Expand tabs to spaces in the output, to preserve
+ the alignment of tabs in the input files.
+
+ -T Output a tab rather than a space before the text of
+ a line in normal or context format. This causes
+ the alignment of tabs in the line to look normal.
+
+ --text Treat all files as text and compare them line-by-
+ line, even if they do not appear to be text.
+
+ -u Use the unified output format.
+
+ --unchanged-group-format=<i>format</i>
+ Use <i>format</i> to output a group of common lines taken
+ from both files in if-then-else format.
+
+ --unchanged-line-format=<i>format</i>
+ Use <i>format</i> to output a line common to both files in
+ if-then-else format.
+
+ --unidirectional-new-file
+ When comparing directories, if a file appears only
+ in the second directory of the two, treat it as
+ present but empty in the other.
+
+ -U <i>lines</i>
+ --unified[=<i>lines</i>]
+ Use the unified output format, showing <i>lines</i> (an
+ integer) lines of context, or three if lines is not
+ given. For proper operation, patch typically needs
+ at least two lines of context.
+
+ -v
+ --version
+ Output the version number of diff.
+
+ -w Ignore white space when comparing lines.
+
+ -W <i>columns</i>
+ --width=<i>columns</i>
+ Use an output width of <i>columns</i> in side by side for-
+ mat.
+
+ -x <i>pattern</i>
+ When comparing directories, ignore files and subdi-
+ rectories whose basenames match <i>pattern</i>.
+
+ -X <i>file</i>
+ When comparing directories, ignore files and subdi-
+ rectories whose basenames match any pattern con-
+ tained in <i>file</i>.
+
+ -y Use the side by side output format.</pre>
+<p>In the simplest case, diff compares the contents of the two files <i>from-file
+ </i>and <i>to-file</i>. A file name of - stands for text read from the standard
+ input. </p>
+<p>If <i>from-file</i> is a directory and <i>to-file </i>is not,
+ diff compares the file in <i>from-file</i> whose file name is that of <i>to-file</i>,
+ and vice versa. The non-directory file must not be -. </p>
+<p>If both <i>from-file</i> and <i>to-file </i>are directories, diff
+ compares corresponding files in both directories, in alphabetical order; this
+ comparison is not recursive unless the -r or --recursive option is given. </p>
+<p>GNU `diff' can show whether files are different without detailing the differences.
+ <br>
+ It also provides ways to suppress certain kinds of differences that are not
+ important to you. <br>
+ <br>
+ Most commonly, such differences are changes in the amount of white space between
+ words or lines. `diff' also provides ways to suppress differences in alphabetic
+ case or in lines that match a regular expression that you provide. <br>
+ <br>
+ These options can accumulate; for example, you can ignore changes in both white
+ space and alphabetic case.<b><br>
+ <br>
+ End -of-Line markers</b><br>
+ In operating systems that distinguish between text and binary files, `diff'
+ normally reads and writes all data as text. <br>
+ <br>
+ Use the `--binary' option to force `diff' to read and write binary data instead.
+ This option has no effect on a Posix-compliant system like GNU or traditional
+ Unix. However, many personal computer operating systems represent the end of
+ a line with a carriage return followed by a newline. <br>
+ <br>
+ On such systems, `diff' normally ignores these carriage returns on input and
+ generates them at the end of each output line, but with the `--binary' option
+ `diff' treats each carriage return as just another input character, and does
+ not generate a carriage return at the end of each output line. <br>
+ <br>
+ This can be useful when dealing with non-text files that are meant to be interchanged
+ with Posix-compliant systems.<b><br>
+ <br>
+Suppress differences in Blank and Tab Spacing</b></p>
+<p> The `-b' and `--ignore-space-change' options ignore white space at line end,
+ and considers all other sequences of one or more white space characters to be
+ equivalent. <br>
+ <br>
+ The `-w' and `--ignore-all-space' options are stronger than `-b'. They ignore
+ difference even if one file has white space where the other file has none. "White
+ space" characters include tab, newline, vertical tab, form feed, carriage return,
+ and space; some locales may define additional characters to be white space.<br>
+ <br>
+ <b><br>
+Ignore Case</b></p>
+<p>GNU `diff' can treat lowercase letters as equivalent to their uppercase counterparts,
+ so that, for example, it considers `Funky Stuff', `funky STUFF', and `fUNKy
+ stuFf' to all be the same. <br>
+ To request this, use the `-i' or `--ignore-case' option.<br>
+ <br>
+ <b>Suppressing Lines Matching a Regular Expression</b><br>
+ To ignore insertions and deletions of lines that match a regular expression,
+ use the `-I REGEXP' or `--ignore-matching-lines=REGEXP' option. <br>
+ You should escape regular expressions that contain shell metacharacters to prevent
+ the shell from expanding them. <br>
+ <br>
+ For example, `diff -I '^[0-9]'' ignores all changes to lines beginning with
+ a digit. <br>
+ <br>
+ However, `-I' only ignores the insertion or deletion of lines that contain the
+ regular expression if every changed line in the hunk--every insertion and every
+ deletion--matches the regular expression. <br>
+ <br>
+ In other words, for each nonignorable change, `diff' prints the complete set
+ of changes in its vicinity, including the ignorable ones. You can specify more
+ than one regular expression for lines to ignore by using more than one `-I'
+ option. `diff' tries to match each line against each regular expression, starting
+ with the last one given.<br>
+ <br>
+ <b>Summarizing Which Files Differ</b><br>
+ When you only want to find out whether files are different, and you don't care
+ what the differences are, you can use the summary output format. <br>
+ In this format, instead of showing the differences between the files, `diff'
+ simply reports whether files differ. <br>
+ The `-q' and `--brief' options select this output format. <br>
+ This format is especially useful when comparing the contents of two directories.
+ It is also much faster than doing the normal line by line comparisons, because
+ `diff' can stop analyzing the files as soon as it knows that there are any differences.
+ <br>
+ You can also get a brief indication of whether two files differ by using `cmp'.
+ <br>
+ <br>
+ <b>Using diff to patch a file</b><br>
+ To show context around the differing lines GNU `diff' provides these output
+ formats <br>
+ <br>
+ Normal Format: An output format that shows each hunk of differences without
+ any surrounding context<br>
+ Context Format:: An output format that shows surrounding lines. <br>
+ Unified Format:: A more compact output format that shows context.<br>
+ <br>
+ `patch' can apply diffs by searching in the files for the lines of context around
+ the differing lines; if those lines are actually a few lines away from where
+ the diff says they are, `patch' can adjust the line numbers accordingly and
+still apply the diff correctly.</p>
+<p><b>Example</b></p>
+<p><span class="telety">$ diff -q &lt;(sort file1.txt | uniq) &lt;(sort file2.txt | uniq)</span><br>
+ <br>
+The command above will return 0 if <span class="telety">file1.txt = file2.txt </span>and will return 1 if <span class="telety">file1.txt &ne; file2.txt</span><br>Note the files have to be sorted first (the order matters) and if the files could contain duplicate values, then the output of sort has to be run through the uniq command to eliminate any duplicate elements. </p>
+<p>For more on patching files and producing commands that direct the `ed' text
+ editor to edit a file - see `info diff'<br>
+ <br>
+ <i># Oh lord won't you buy me a Mercedes Benz, my friends all drive Porsches,
+ I must make amends # - Janice
+Joplin </i> </p>
+<p><b>Related</b>:<br>
+ <br>
+ <a href="cmp.html">cmp</a> - Compare two files<br>
+ dircmp - Compare 2 directories<br>
+ <a href="diff3.html">diff3</a> - Show differences among three files<br>
+ <a href="sdiff.html">sdiff</a> - Merge two files interactively<br>
+ Equivalent Windows commands: <a href="../term_tools/nt/comp.html">COMP</a> / <a href="../term_tools/nt/fc.html">FC</a> - Compare and display Characters/Lines which do not match.<br>
+(also the WINDIFF GUI)</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/diff3.html b/help/en/bash/diff3.html
new file mode 100644
index 0000000..2daa924
--- /dev/null
+++ b/help/en/bash/diff3.html
@@ -0,0 +1,179 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>diff3 MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1>diff3</h1>
+<p>Show differences among three files.<br>
+ When two people have made independent changes to a common original, `diff3'
+ can report the differences between the original and the two changed versions,
+ and can produce a merged file that contains both persons' changes together with
+ warnings about conflicts.<br>
+ The files to compare are MINE, OLDER, and YOURS. At most one of these three
+ file names may be `-', which tells `diff3' to read the standard input for that
+ file.<br>
+</p>
+<pre>SYNTAX
+ diff3 [<i>options</i>] <i>mine older yours</i>
+
+OPTIONS
+`-a'
+ Treat all files as text and compare them line-by-line, even if they
+ do not appear to be text.
+
+`-A'
+ Incorporate all changes from OLDER to YOURS into MINE, surrounding
+ all conflicts with bracket lines. *Note Marking Conflicts::.
+
+`-e'
+ Generate an `ed' script that incorporates all the changes from
+ OLDER to YOURS into MINE. *Note Which Changes::.
+
+`-E'
+ Like `-e', except bracket lines from overlapping changes' first
+ and third files. *Note Marking Conflicts::. With `-e', an
+ overlapping change looks like this:
+
+ <<<<<<< MINE
+ lines from MINE
+ =======
+ lines from YOURS
+ >>>>>>> YOURS
+
+`--ed'
+ Generate an `ed' script that incorporates all the changes from
+ OLDER to YOURS into MINE. *Note Which Changes::.
+
+`--easy-only'
+ Like `-e', except output only the nonoverlapping changes. *Note
+ Which Changes::.
+
+`-i'
+ Generate `w' and `q' commands at the end of the `ed' script for
+ System V compatibility. This option must be combined with one of
+ the `-AeExX3' options, and may not be combined with `-m'. *Note
+ Saving the Changed File::.
+
+`--initial-tab'
+ Output a tab rather than two spaces before the text of a line in
+ normal format. This causes the alignment of tabs in the line to
+ look normal. *Note Tabs::.
+
+`-L LABEL'
+`--label=LABEL'
+ Use the label LABEL for the brackets output by the `-A', `-E' and
+ `-X' options. This option may be given up to three times, one for
+ each input file. The default labels are the names of the input
+ files. Thus `diff3 -L X -L Y -L Z -m A B C' acts like `diff3 -m A
+ B C', except that the output looks like it came from files named
+ `X', `Y' and `Z' rather than from files named `A', `B' and `C'.
+ *Note Marking Conflicts::.
+
+`-m'
+`--merge'
+ Apply the edit script to the first file and send the result to
+ standard output. Unlike piping the output from `diff3' to `ed',
+ this works even for binary files and incomplete lines. `-A' is
+ assumed if no edit script option is specified. *Note Bypassing
+ ed::.
+
+`--overlap-only'
+ Like `-e', except output only the overlapping changes. *Note
+ Which Changes::.
+
+`--show-all'
+ Incorporate all unmerged changes from OLDER to YOURS into MINE,
+ surrounding all overlapping changes with bracket lines. *Note
+ Marking Conflicts::.
+
+`--show-overlap'
+ Like `-e', except bracket lines from overlapping changes' first
+ and third files. *Note Marking Conflicts::.
+
+`-T'
+ Output a tab rather than two spaces before the text of a line in
+ normal format. This causes the alignment of tabs in the line to
+ look normal. *Note Tabs::.
+
+`--text'
+ Treat all files as text and compare them line-by-line, even if they
+ do not appear to be text. *Note Binary::.
+
+`-v'
+`--version'
+ Output the version number of `diff3'.
+
+`-x'
+ Like `-e', except output only the overlapping changes. *Note
+ Which Changes::.
+
+`-X'
+ Like `-E', except output only the overlapping changes. In other
+ words, like `-x', except bracket changes as in `-E'. *Note
+ Marking Conflicts::.
+
+`-3'
+ Like `-e', except output only the nonoverlapping changes. </pre>
+<p> <b>Notes</b><br>
+ `diff3' normally compares three input files line
+ by line, finds groups of lines that differ, and reports each group of differing
+ lines. Its output is designed to make it easy to inspect two different sets
+ of changes to the same file. <br>
+ <br>
+ If `diff3' thinks that any of the files it is comparing is binary (a non-text
+ file), it normally reports an error, because such comparisons are usually not
+ useful. As with `diff', you can force `diff3' to consider all files to be text
+ files and compare them line by line by using the `-a' or `--text' options. <br>
+ <b><br>
+ </b>Multiple single letter options (unless they take an argument) can be combined
+ into a single command line argument.</p>
+<p>An exit status of 0 means diff3 was successful, 1 means some conflicts
+ were found, and 2 means trouble.</p>
+<p> <i>"One person can make a difference and every person must try"
+ ~ John
+ F. Kennedy</i></p>
+<p><b>Related bash commands</b>:<br>
+ <br>
+ <a href="cmp.html">cmp</a> - Compare two files<br>
+ <a href="diff.html">diff</a> - Display the differences between two files <br>
+ <a href="sdiff.html">sdiff</a> - merge two files interactively<br>
+Equivalent Windows commands: <a href="../term_tools/nt/comp.html">COMP</a> / <a href="../term_tools/nt/fc.html">FC</a> - Compare and display Characters/Lines which do not match.<br>
+(also the WINDIFF GUI)</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/dig.html b/help/en/bash/dig.html
new file mode 100644
index 0000000..fb423bc
--- /dev/null
+++ b/help/en/bash/dig.html
@@ -0,0 +1,129 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>dig MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> dig (domain information groper)</h1>
+<p>A flexible tool for interrogating DNS name servers. It performs DNS lookups and displays the answers that are returned from the name server(s) that were queried. Most DNS administrators use dig to troubleshoot DNS problems because of its flexibility, ease of use and clarity of output. Other lookup tools tend to have less functionality than dig.</p>
+<pre>Syntax:
+ dig [@<i>server</i>] [-b <i>address</i>] [-c <i>class</i>] [-f <i>filename</i>] [-k <i>filename</i>]
+ [-p <i>port#</i>] [-t <i>type</i>] [-x <i>addr</i>] [-y <i>name</i>:<i>key</i>] [-4] [-6]
+ [<i>name</i>] [<i>type</i>] [<i>class</i>] [<i>queryopt</i>...]<br> dig [-h]
+<br> dig [<i><a href="../term_tools/bash/dig-queryopt.html">global-queryopt</a></i>...] [<i>query</i>...]
+
+Options:
+
+ -b <i>address</i>
+ Set the source IP address of the query to address.
+ This must be a valid address on one of the host's network interfaces or "0.0.0.0" or "::".
+ An optional port may be specified by appending "#<port>"
+
+ -c <i>class</i>
+ Over-ride the default query class (IN for internet).
+ class is any valid class, such as HS for Hesiod records or CH for CHAOSNET records.
+
+ -f <i>filename</i>
+ Operate in batch mode by reading a list of lookup requests to process from a file.
+ The file contains a number of queries, one per line.
+ Each entry in the file should be organised in the same way they would be presented
+ as queries to dig using the command-line interface.
+
+ -p <i>port#</i>
+ Specify a non-standard port number to be queried,
+ default = the standard DNS port number 53.
+ This option would be used to test a name server that has been configured
+ to listen for queries on a non-standard port number.
+
+ -4 Force dig to only use IPv4 query transport.
+
+ -6 Force dig to only use IPv6 query transport.
+
+ -t <i>type</i>
+ Set the query type to <i>type</i>, any valid query type which is supported in BIND9.
+ The default query type "A", unless the -x option is supplied to indicate a reverse lookup.
+ A zone transfer can be requested by specifying a type of AXFR.
+ When an incremental zone transfer (IXFR) is required, type is set to ixfr=N.
+ The incremental zone transfer will contain the changes made to the zone since the
+ serial number in the zone's SOA record was N.
+
+ -x <i>addr
+ </i> Reverse lookups - mapping addresses to names: <i>addr</i> is an IPv4 address in dotted-
+ decimal notation, or a colon-delimited IPv6 address. When this option is used,
+ there is no need to provide the name, class and type arguments. dig automatically
+ performs a lookup for a name like 11.12.13.10.in-addr.arpa and sets the query type
+ and class to PTR and IN respectively. By default, IPv6 addresses are looked up using
+ nibble format under the IP6.ARPA domain. To use the older RFC1886 method using the
+ IP6.INT domain specify the -i option. Bit string labels (RFC2874) are now experimental
+ and are not attempted.
+
+ -k <i>filename</i>
+ Sign the DNS queries sent by dig and their responses using transaction signatures
+ (TSIG key file). You can also specify the TSIG key itself on the command line
+ using the -y option; <i>name</i> is the name of the TSIG key and <i>key</i> is the actual key.
+ The key is a base-64 encoded string, typically generated by dnssec-keygen(8).
+ Caution should be taken when using the -y option on multi-user systems as the key
+ can be visible in the output from ps(1 ) or in the shell's history file.
+ When using TSIG authentication with dig, the name server that is queried needs to
+ know the key and algorithm that is being used. In BIND, this is done by providing
+ appropriate key and server statements in named.conf.
+
+ -h Print a brief summary of the command-line arguments and options.
+</pre>
+<p><span class="body"> Although dig is normally used with command-line arguments, it also has a batch mode of operation for reading lookup requests from a file. Unlike earlier versions, the BIND9 implementation of dig allows multiple lookups to be issued from the command line.</span></p>
+<p>Unless it is told to query a specific name server, dig will try each of the servers listed in <span class="telety">/etc/resolv.conf</span></p>
+<p>When no command line arguments or options are given, will perform an NS query for &quot;.&quot; (the root).</p>
+<p>It is possible to set per-user defaults for dig via <span class="telety">${HOME}/.digrc</span>. This file is read and any options in it are applied before the command line arguments. </p>
+<p><b>Examples</b></p>
+<p class="telety">dig ss64.com<br>dig ss64.com SIG <br>
+dig ss64.com MX <br>
+dig ss64.com A </p>
+<p>Test your DNS resolver's source port behavior:<span class="telety"><br>
+dig +short porttest.<a href="https://www.dns-oarc.net/oarc/services/porttest">dns-oarc.net</a> TXT</span></p>
+<p><i> "A prediction is worth twenty explanations" - K.
+ Brecher</i><b><br>
+ <br>
+ Related</b>:<br>
+ <br>
+ host<br>
+named<br>
+dnssec-keygen<br>
+ Equivalent Windows command:
+ <a href="http://members.shaw.ca/nicholas.fong/dig/">dig</a> - Unofficial port from debian to Win32</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/dir.html b/help/en/bash/dir.html
new file mode 100644
index 0000000..96fe97c
--- /dev/null
+++ b/help/en/bash/dir.html
@@ -0,0 +1,56 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>dir MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> dir</h1>
+<p>Briefly list directory contents<br>
+</p>
+<pre>SYNTAX
+ `dir' (also installed as `d')</pre>
+<p>Equivalent to `ls -C -b'; that is,by default files are listed
+ in columns, sorted vertically, and special characters are represented by backslash
+ escape sequences. </p>
+<p><b>Related</b>:<br>
+ <br>
+ <a href="ls.html">ls</a> - List information about files <br>
+Equivalent Windows command:
+<a href="../term_tools/nt/dir.html">DIR</a> - Display a list of files and folders</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/dircolours.html b/help/en/bash/dircolours.html
new file mode 100644
index 0000000..fd9a8a0
--- /dev/null
+++ b/help/en/bash/dircolours.html
@@ -0,0 +1,82 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>dircolors MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> dircolors</h1>
+<p>Color setup for `ls', outputs a sequence of shell commands to
+set up the terminal for color output from `ls' (and `dir', etc.).</p>
+<pre>Syntax
+
+ eval `dircolors [<em>options</em>]... [<em>file</em>]`
+</pre>
+<p><span class="body"> If FILE is specified, `dircolors' reads it to determine which colors
+ to use for which file types and extensions. Otherwise, a precompiled<br>
+ database is used. For details on the format of these files, run
+ `dircolors --print-database'.<br>
+ <br>
+ The output is a shell command to set the `LS_COLORS' environment
+ variable. You can specify the shell syntax to use on the command line,
+ or `dircolors' will guess it from the value of the `SHELL' environment
+ variable.</span></p>
+<pre>Options
+
+ -b
+ --sh
+ --bourne-shell
+ Output Bourne shell commands. This is the default if the `SHELL'
+ environment variable is set and does not end with `csh' or `tcsh'.
+
+ -c
+ --csh
+ --c-shell
+ Output C shell commands. This is the default if `SHELL' ends with
+ `csh' or `tcsh'.
+
+ -p
+ --print-database
+ Print the (compiled-in) default color configuration database. This
+ output is itself a valid configuration file, and is fairly
+ descriptive of the possibilities.</pre>
+<p><b>Related</b>:<br>
+ <br>
+ <a href="ls.html">ls</a> - List information about FILEs<br>
+Equivalent Windows command:<a href="../term_tools/nt/color.html"> COLOR</a> - Change colour of the CMD window</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/dirname.html b/help/en/bash/dirname.html
new file mode 100644
index 0000000..0bedfee
--- /dev/null
+++ b/help/en/bash/dirname.html
@@ -0,0 +1,61 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>dirname MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> dirname</h1>
+<p>Convert a full pathname to just a path</p>
+<pre>Syntax
+ dirname <em>pathname</em>
+</pre>
+<p>Prints all but the final slash-delimited component of a
+string (presumably a filename).<br>
+If PATHNAME is a single component, `dirname' prints `.'
+(meaning the current directory)</p>
+<p><b>Related</b>:<br>
+ <br>
+ <a href="hash.html">hash</a> - Remember the full pathname of a name argument
+ <br>
+ <a href="ls.html">ls</a> - List information about File(s)<br>
+ <a href="which.html">which</a> - Show full path of commands <br>
+Equivalent Windows commands:
+ <a href="../term_tools/nt/syntax-args.html">SET Parameters</a> - get a full or partial
+pathname from a variable. </p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/dirs.html b/help/en/bash/dirs.html
new file mode 100644
index 0000000..4167639
--- /dev/null
+++ b/help/en/bash/dirs.html
@@ -0,0 +1,81 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>dirs MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> dirs</h1>
+<p>Display the list of currently remembered directories. </p>
+<pre>Syntax
+ dirs [+N | -N] [-clpv]
+
+Options
+ +N Displays the Nth directory (counting from the left of the list
+ printed by dirs when invoked without options), starting with
+ zero.
+
+ -N Displays the Nth directory (counting from the right of the list
+ printed by dirs when invoked without options), starting with
+ zero.
+
+ -c Clears the directory stack by deleting all of the elements.
+
+ -l Produces a longer listing; the default listing format uses a tilde to denote
+ the home directory.
+
+ -p Causes dirs to print the directory stack with one entry per
+ line.
+ -v Causes dirs to print the directory stack with one entry per
+ line, prefixing each entry with its index in the stack.</pre>
+<span class="body"><b>Description</b></span>
+<p>Equivalent to `ls -C -b'; that is,by default files are listed
+ in columns, sorted vertically, and special characters are represented by backslash
+ escape sequences. </p>
+<p><i>"After all, what is your hosts' purpose in having a party?
+ Surely not for you to enjoy yourself; if that were their sole purpose, they'd
+ have simply sent champagne and women over to your place by taxi" - P.J.
+ O'Rourke </i></p>
+<p><i></i><b>Related</b>:<br>
+ <a href="popd.html"><br>
+ popd</a> - Restore the previous value of the current directory saved by `pushd'<a href="pushd.html"><br>
+ pushd</a> - Save and then change the current directory<br>
+Equivalent Windows commands: <a href="../term_tools/nt/pushd.html">
+ PUSHD</a>/
+<a href="../term_tools/nt/popd.html">POPD</a> </p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/dmesg.html b/help/en/bash/dmesg.html
new file mode 100644
index 0000000..bb12347
--- /dev/null
+++ b/help/en/bash/dmesg.html
@@ -0,0 +1,76 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>dmesg MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> dmesg </h1>
+<p>Print kernel (and driver) messages, control the kernel ring buffer.</p>
+<pre>Syntax
+ dmesg [ -c ] [ -n <i>level</i> ] [ -s <i>bufsize</i> ]</pre>
+<p> The dmesg program allows you to print system messages from the buffer (mostly kernel and drivers loading at bootup) and can also be used to configure the kernel ring buffer. </p>
+
+<pre>Options</pre>
+<pre> -c Clear the ring buffer contents after printing.
+
+ -s <i>bufsize</i> Use a buffer of size <i>bufsize</i> to query the kernel ring buffer.
+ This is 16392 by default. (The default kernel syslog buffer
+ size was 4096 at first, 8192 since 1.3.54, 16384 since 2.1.113.)
+ If you have set the kernel buffer to be larger than the default
+ then this option can be used to view the entire buffer.
+
+ -n<i> level</i> Set the level at which logging of messages is done to the console.
+ For example, -n 1 prevents all messages, expect panic messages,
+ from appearing on the console. All levels of messages are still
+ written to /proc/kmsg, so syslogd(8) can still be used to control exactly
+ where kernel messages appear. When the -n option is used, dmesg will not
+ print or clear the kernel ring buffer.</pre>
+<p> When both options are used, only the last option on the command line will have an effect.<br>
+As it's a ring-buffer, it will automatically cycle out old information when the buffer is full.</p>
+<p><b>Examples</b></p>
+<p>Print all the bootup messages to a file: </p>
+<p class="code">$ sudo dmesg &gt; messages.txt</p>
+<p>Print recent messages: </p>
+<p class="code">$ sudo dmesg | tail -f</p>
+<p><i>&ldquo;If we want a love message to be heard, it has got to be sent out. To keep a lamp burning, we have to keep putting oil in it&rdquo; - Mother Teresa</i></p>
+<p><b>Related</b>:<br>
+ chkconfig - updates and queries runlevel information for system services<br>
+syslogd - Linux system logging utilities.<br>
+/var/log/dmesg</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/du.html b/help/en/bash/du.html
new file mode 100644
index 0000000..494d84f
--- /dev/null
+++ b/help/en/bash/du.html
@@ -0,0 +1,161 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>du MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> du</h1>
+<p>Disk Usage - report the amount of disk space used
+by the specified files and for each subdirectory.</p>
+<pre>Syntax
+ du [<em>options</em>]... [<em>file</em>]...
+</pre>
+<p><span class="body"> With no arguments, `du' reports the disk space for the current
+ directory. Normally the disk space is printed in units of 1024 bytes,
+ but this can be overridden</span></p>
+<pre>
+OPTIONS
+
+`-a'
+`--all'
+ Show counts for all files, not just directories.
+
+`-b'
+`--bytes'
+ Print sizes in bytes, overriding the default block size (*note
+ Block size::).
+
+`-c'
+`--total'
+ Print a grand total of all arguments after all arguments have been
+ processed. This can be used to find out the total disk usage of a
+ given set of files or directories.
+
+`-D'
+`--dereference-args'
+ Dereference symbolic links that are command line arguments. Does
+ not affect other symbolic links. This is helpful for finding out
+ the disk usage of directories, such as `/usr/tmp', which are often
+ symbolic links.
+
+`-h'
+`--human-readable'
+ Append a size letter such as `M' for megabytes to each size.
+ Powers of 1024 are used, not 1000; `M' stands for 1,048,576 bytes.
+ Use the `-H' or `--si' option if you prefer powers of 1000.
+
+`-H'
+`--si'
+ Append a size letter such as `M' for megabytes to each size. (SI
+ is the International System of Units, which defines these letters
+ as prefixes.) Powers of 1000 are used, not 1024; `M' stands for
+ 1,000,000 bytes. Use the `-h' or `--human-readable' option if you
+ prefer powers of 1024.
+
+`-k'
+`--kilobytes'
+ Print sizes in 1024-byte blocks, overriding the default block size
+ (*note Block size::).
+
+`-l'
+`--count-links'
+ Count the size of all files, even if they have appeared already
+ (as a hard link).
+
+`-L'
+`--dereference'
+ Dereference symbolic links (show the disk space used by the file
+ or directory that the link points to instead of the space used by
+ the link).
+
+`--max-depth=DEPTH'
+ Show the total for each directory (and file if -all) that is at
+ most MAX_DEPTH levels down from the root of the hierarchy. The
+ root is at level 0, so `du --max-depth=0' is equivalent to `du -s'.
+
+`-m'
+`--megabytes'
+ Print sizes in megabyte (that is, 1,048,576-byte) blocks.
+
+`-s'
+`--summarize'
+ Display only a total for each argument.
+
+`-S'
+`--separate-dirs'
+ Report the size of each directory separately, not including the
+ sizes of subdirectories.
+
+`-x'
+`--one-file-system'
+ Skip directories that are on different filesystems from the one
+ that the argument being processed is on.
+
+`--exclude=PAT'
+ When recursing, skip subdirectories or files matching PAT. For
+ example, `du --exclude='*.o'' excludes files whose names end in
+ `.o'.
+
+`-X FILE'
+`--exclude-from=FILE'
+ Like `--exclude', except take the patterns to exclude from FILE,
+ one per line. If FILE is `-', take the patterns from standard
+ input.
+
+On BSD systems, `du' reports sizes that are half the correct values
+for files that are NFS-mounted from HP-UX systems. On HP-UX systems,
+it reports sizes that are twice the correct values for files that are
+NFS-mounted from BSD systems. This is due to a flaw in HP-UX; it also
+affects the HP-UX `du' program.</pre>
+<p><b>Example</b></p>
+<p>List the total files sizes for everything 1 directory (or less) below the currrent directory ( . ) </p>
+<p>[simon@testserver]$<span class="telety"> du -hc --max-depth=1 .</span><br>
+400M ./data1<br>
+1.0G ./data2<br>
+
+1.3G .<br>
+1.3G total</p>
+<p><i>"Never go to a doctor whose office plants have died" - Erma
+ Bombeck</i></p>
+<p><b>Related</b>:<br>
+ <br>
+ <a href="ls.html">ls</a> - List information about FILEs<br>
+Equivalent Windows command:
+ DIRUSE - resource kit utility to show size of multiple subfolders.</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/echo.html b/help/en/bash/echo.html
new file mode 100644
index 0000000..9b012bb
--- /dev/null
+++ b/help/en/bash/echo.html
@@ -0,0 +1,121 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>echo MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> echo</h1>
+<p>Display message on screen, writes each given STRING to standard
+output, with a space between each and a newline after the last one.</p>
+<pre>Syntax
+ echo [<em>options</em>]... [<em>string</em>]...
+
+Options
+
+ -n
+ Do not output the trailing newline.
+
+ -E
+ Disable the interpretation of the following backslash-escaped characters
+
+ -e
+ Enable interpretation of the following backslash-escaped
+ characters in each STRING:
+
+ \a alert (bell)
+
+ \b backspace
+
+ \c suppress trailing newline
+
+ \e escape <br> <br> \f form feed
+
+ \n new line
+
+ \r carriage return
+
+ \t horizontal tab
+
+ \v vertical tab
+
+ \\ backslash
+
+ \<i>NNN</i>
+ the character whose ASCII code is NNN (octal); if NNN is not
+ a valid octal number, it is printed literally.
+
+ \x<i>nnn</i><br> the character whose ASCII code is the hexadecimal value <br> nnn (one to three digits)</pre>
+<p>echo is a BASH built-in command</p>
+<p><b>Examples</b></p>
+<p>Echo can also display in color by using Escape sequences for foreground (30..37) and background (40..47) colours.</p>
+<p class="code">$ COL_BLUE=&quot;\x1b[34;01m&quot;<br>
+$ COL_RESET=&quot;\x1b[39;49;00m&quot;<br>
+$ echo -e $COL_BLUE&quot;Important Message: &quot;$COL_RESET&quot;This is a message&quot;</p>
+<p>Here is a shell script to display all the color combinations: </p>
+<pre> #!/bin/bash
+ #
+ echo ---Bg---40---41---42---43---44---45---46---47
+ for i in {30..37} # foreground
+ do
+ echo -n -e fg$i-
+ for j in {40..47} # background
+ do
+ echo -n -e '\E['$i';'$j'm SS64'
+ tput sgr0 # Reset text attributes to normal without clear
+ done
+ echo # newline
+ done
+
+ echo -- Clear BG --
+ for n in {30..37} # foreground
+ do
+ echo -e fg$n '\E['$n';'01'm SS64'
+ tput sgr0 # Reset text attributes to normal without clear
+ done</pre>
+<p><em>&quot;The only thing that helps me pass the time away; is knowing I'll be back at Echo Beach some day&quot; - Martha and the Muffins</em><b></b><b><br>
+ <br>
+ Related</b>:<br>
+ <br>
+ <a href="head.html">head</a> - Output the first part of file(s)<a href="less.html"><br>
+ less</a> - Display output one screen at a time<br>
+ <a href="more.html">more</a> - Display output one screen at a time <br>
+ pg - Display one page at a time<br>
+ <a href="tee.html">tee</a> - Redirect output to multiple files <br>
+Equivalent Windows command: <a href="echo.html">ECHO</a> - Display message on screen</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/egrep.html b/help/en/bash/egrep.html
new file mode 100644
index 0000000..9419e15
--- /dev/null
+++ b/help/en/bash/egrep.html
@@ -0,0 +1,92 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>egrep MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> egrep</h1>
+<p>Search file(s) for lines that match an extended expression (extended grep) </p>
+<pre>Syntax
+ egrep [ <em>options</em> ] '<em>PATTERN</em>' <em>files</em> ...
+
+egrep is the same as `grep <a href="../term_tools/bash/grep2.html">-E</a>'
+
+all other <em>options</em> are the same as <a href="grep.html">grep</a>
+
+The <em>PATTERN</em> is a regexp. In typical usage, the regexp is quoted to
+prevent the shell from expanding any of the special characters as file
+name wildcards. Normally, `egrep' prints the lines that matched. If
+multiple file names are provided on the command line, each output line
+is preceded by the name of the file and a colon.
+
+OPTIONS
+
+`-c'
+ Print out a count of the lines that matched the pattern, instead
+ of the lines themselves.
+
+`-s'
+ Be silent. No output is produced, and the exit value indicates
+ whether or not the pattern was matched.
+
+`-v'
+ Invert the sense of the test. `egrep' prints the lines that do
+ *not* match the pattern, and exits successfully if the pattern was
+ not matched.
+
+`-i'
+ Ignore case distinctions in both the pattern and the input data.
+
+`-l'
+ Only print the names of the files that matched, not the lines that
+ matched.
+
+`-e PATTERN'
+ Use PATTERN as the regexp to match. The purpose of the `-e'
+ option is to allow patterns that start with a `-'.</pre>
+<p><i>&quot;I've never had a humble opinion in my life. If you're going to have one, why bother to be humble about it&quot; - Joan Baez </i> </p>
+<p><b>Related</b>:<br>
+ <br>
+ <a href="fgrep.html">fgrep</a> - Search file(s) for lines that match a fixed
+ string<br>
+ <a href="awk.html">gawk</a> - Find and Replace text within file(s) <br>
+ <a href="grep.html">grep</a> - Search file(s) for lines that match a given pattern
+ <br>
+Equivalent Windows commands: <a href="../term_tools/nt/findstr.html">FINDSTR</a> - Search for strings in files </p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/eject.html b/help/en/bash/eject.html
new file mode 100644
index 0000000..81b9362
--- /dev/null
+++ b/help/en/bash/eject.html
@@ -0,0 +1,172 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>eject MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1>eject</h1>
+<p>Eject removable media </p>
+<pre>Syntax
+ eject -h
+ eject [-vnrsfmqp] [&lt;name&gt;]
+ eject [-vn] -d
+ eject [-vn] -a on|off|1|0 [&lt;name&gt;]
+ eject [-vn] -c slot [&lt;name&gt;]
+ eject [-vn] -t [&lt;name&gt;]
+ eject [-vn] -T [&lt;name&gt;]
+ eject [-vn] -x &lt;speed&gt; [&lt;name&gt;]
+ eject [-vn] -X [&lt;name&gt;]
+ eject -V
+</pre>
+
+<p>Description
+</p>
+<p>Eject allows removable media (typically a CD-ROM, floppy disk, tape, or JAZ or ZIP disk) to be ejected under software control. The command can also control some multi-disc CD-ROM changers, the auto-eject feature supported by some devices, and close the disc tray of some CD-ROM drives.</p>
+<p>The device corresponding to &lt;name&gt; is ejected. The name can be a device file or mount point, either a full path or with the leading &quot;/dev&quot;, &quot;/media&quot; or &quot;/mnt&quot; omitted. If no name is specified, the default name &quot;cdrom&quot; is used.</p>
+<p>There are four different methods of ejecting, depending on whether the device is a CD-ROM, SCSI device, removable floppy, or tape. By default eject tries all four methods in order until it succeeds.</p>
+<p>If the device is currently mounted, it is unmounted before ejecting.<br>
+Command-line Options</p>
+<p>-h<br>
+Help - displays a brief description of the command options. <br>
+<br>
+-v<br>
+This makes eject run in verbose mode; more information is displayed about what the command is doing. <br>
+<br>
+-d<br>
+If invoked with this option, eject lists the default device name. <br>
+<br>
+-a on|1|off|0<br>
+This option controls the auto-eject mode, supported by some devices. When enabled, the drive automatically ejects when the device is closed. <br>
+<br>
+-c &lt;slot&gt;<br>
+With this option a CD slot can be selected from an ATAPI/IDE CD-ROM changer. Linux 2.0 or higher is required to use this feature. The CD-ROM drive can not be in use (mounted data CD or playing a music CD) for a change request to work. Please also note that the first slot of the changer is referred to as 0, not 1. <br>
+<br>
+-t<br>
+With this option the drive is given a CD-ROM tray close command. Not all devices support this command. <br>
+<br>
+-T<br>
+With this option the drive is given a CD-ROM tray close command if it's opened, and a CD-ROM tray eject command if it's closed. Not all devices support this command, because it uses the above CD-ROM tray close command. <br>
+<br>
+-x &lt;speed&gt;<br>
+With this option the drive is given a CD-ROM select speed command. The speed argument is a number indicating the desired speed (e.g. 8 for 8X speed), or 0 for maximum data rate. Not all devices support this command and you can only specify speeds that the drive is capable of. Every time the media is changed this option is cleared. This option can be used alone, or with the -t and -c options. <br>
+<br>
+-X<br>
+With this option the CD-ROM drive will be probed to detect the available speeds. The output is a list of speeds which can be used as an argument of the -x option. This only works with Linux 2.6.13 or higher, on previous versions solely the maximum speed will be reported. Also note that some drive may not correctly report the speed and therefore this option does not work with them. <br>
+<br>
+-n<br>
+With this option the selected device is displayed but no action is performed. <br>
+<br>
+-r<br>
+This option specifies that the drive should be ejected using a CDROM eject command. <br>
+<br>
+-s<br>
+This option specifies that the drive should be ejected using SCSI commands. <br>
+<br>
+-f<br>
+This option specifies that the drive should be ejected using a removable floppy disk eject command. <br>
+<br>
+-q<br>
+This option specifies that the drive should be ejected using a tape drive offline command. <br>
+<br>
+-p<br>
+This option allow you to use /proc/mounts instead /etc/mtab. It also passes the -n option to umount(1). <br>
+<br>
+-m<br>
+This option allows eject to work with device drivers which automatically mount removable media and therefore must be always mount()ed. The option tells eject <br>
+to not try to unmount the given device, even if it is mounted according to /etc/mtab or /proc/mounts. <br>
+<br>
+-V<br>
+This option causes eject to display the program version and exit.</p>
+<p>Long Options<br>
+All options have corresponding long names, as listed below. The long names can be abbreviated as long as they are unique.</p>
+<p>-h --help<br>
+-v --verbose<br>
+-d --default<br>
+-a --auto<br>
+-c --changerslot<br>
+-t --trayclose<br>
+-T --traytoggle<br>
+-x --cdspeed<br>
+-X --listspeed<br>
+-n --noop<br>
+-r --cdrom<br>
+-s --scsi<br>
+-f --floppy<br>
+-q --tape<br>
+-V --version<br>
+-p --proc<br>
+-m --no-unmount</p>
+<p><b>Examples</b></p>
+<p>Eject the default device:</p>
+<p class="code">eject</p>
+<p>Eject a device or mount point named cdrom:</p>
+<p class="code">eject cdrom</p>
+<p>Eject using device name:</p>
+<p class="code">eject /dev/cdrom</p>
+<p>Eject using mount point:</p>
+<p class="code">eject /mnt/cdrom/</p>
+<p>Eject 4th IDE device:</p>
+<p class="code">eject hdd</p>
+<p>Eject first SCSI device:</p>
+<p class="code">eject sda</p>
+<p>Eject using SCSI partition name (e.g. a ZIP drive):</p>
+<p class="code">eject sda4</p>
+<p>Select 5th disc on multi-disc changer:</p>
+<p class="code">eject -v -c4 /dev/cdrom</p>
+<p>Turn on auto-eject on a SoundBlaster CD-ROM drive:</p>
+<p class="code">eject -a on /dev/sbpcd</p>
+<p><b>Exit Status</b></p>
+<p>Returns 0 if operation was successful, 1 if operation failed or command syntax was not valid.</p>
+<p><b>Notes</b></p>
+<p>Eject only works with devices that support one or more of the four methods of ejecting. This includes most CD-ROM drives (IDE, SCSI, and proprietary), some SCSI tape drives, JAZ drives, ZIP drives (parallel port, SCSI, and IDE versions), and LS120 removable floppies. Users have also reported success with floppy drives on Sun SPARC and Apple Macintosh systems. If eject does not work, it is most likely a limitation of the kernel driver for the device and not the eject program itself.</p>
+<p>The -r, -s, -f, and -q options allow controlling which methods are used to eject. More than one method can be specified. If none of these options are specified, it tries all four (this works fine in most cases).</p>
+<p>Eject may not always be able to determine if the device is mounted (e.g. if it has several names). If the device name is a symbolic link, eject will follow the link and use the device that it points to.</p>
+<p>If eject determines that the device can have multiple partitions, it will attempt to unmount all mounted partitions of the device before ejecting. If an unmount fails, the program will not attempt to eject the media.</p>
+<p>You can eject an audio CD. Some CD-ROM drives will refuse to open the tray if the drive is empty. Some devices do not support the tray close command.</p>
+<p>If the auto-eject feature is enabled, then the drive will always be ejected after running this command. Not all Linux kernel CD-ROM drivers support the auto-eject mode. There is no way to find out the state of the auto-eject mode.</p>
+<p>You need appropriate privileges to access the device files. Running as root or setuid root is required to eject some devices (e.g. SCSI devices).</p>
+<p>The heuristic used to find a device, given a name, is as follows. If the name ends in a trailing slash, it is removed (this is to support filenames generated using shell file name completion). If the name starts with '.' or '/', it tries to open it as a device file or mount point. If that fails, it tries prepending '/dev/', '/media/' ,'/mnt/', '/dev/cdroms', '/dev/rdsk/', '/dev/dsk/', and finally './' to the name, until a device file or mount point is found that can be opened. The program checks /etc/mtab for mounted devices. If that fails, it also checks /etc/fstab for mount points of currently unmounted devices.</p>
+<p>Creating symbolic links such as /dev/cdrom or /dev/zip is recommended so that eject can determine the appropriate devices using easily remembered names.</p>
+<p>To save typing you can create a shell alias for the eject options that work for your particular setup. </p>
+<p><i>"I discovered that rejections are not altogether a bad thing. They teach a writer to rely on his own judgment and to say in his heart of hearts, 'To hell with you' - Saul Bellow</i></p>
+<p><b>Related bash commands</b>:<br>
+<br>
+<a href="mount.html">mount</a> - Mount a file system<br>
+umount - Unmount a device</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/enable.html b/help/en/bash/enable.html
new file mode 100644
index 0000000..b22357f
--- /dev/null
+++ b/help/en/bash/enable.html
@@ -0,0 +1,89 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>enable MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> enable</h1>
+<p>Enable and disable builtin shell commands.</p>
+<pre>Syntax
+ enable [-n] [-p] [-f <var>filename</var>] [-ads] [<var>name</var> ...]
+
+Options
+ -a list each builtin with an indication of whether or not
+ it is enabled.
+
+ <samp>-d</samp> Delete a builtin loaded with <samp>`-f'</samp>.
+
+ -f load the new builtin command <i>name</i> from shared object <var>filename</var>,
+ on systems that support dynamic loading.
+
+ -n Disable the <i>name</i>s listed, otherwise names are enabled.
+
+ -p Print a list of shell builtins, default if no <var>name</var> arguments appear
+ With no other arguments, the list consists of all enabled shell builtins.
+
+ -s Restrict to enable only POSIX special builtins</pre>
+<p> Disabling a builtin allows a disk command which has the same
+ name as a shell builtin to be executed without specifying a full pathname, even
+ though the shell normally searches for builtins before disk commands. <br>
+ <br>
+ For example, to use the <code>test</code> binary found via <code>$PATH</code>
+ instead of the shell builtin version, type <samp>`enable -n test'</samp>. <br>
+ <br>
+ If there are no options, a list of the shell builtins is displayed. <br>
+ <br>
+ If `-s' is used with `-f', the new builtin becomes a special builtin. <br>
+ <br>
+ The return status is zero unless a <i>name</i> is not a shell builtin or there
+ is an error loading a new builtin from a shared object. <br>
+ <br>
+ <i>You see things; and you say 'Why?' But I dream things that never were; and
+ I say 'why not?' - George
+ Bernard Shaw </i> </p>
+<p><b>Related</b>:<br>
+ <a href="builtin.html"><br>
+ builtin</a> - Run a shell builtin<br>
+ <a href="chroot.html">chroot</a> - Run a command with a different root directory<br>
+ <a href="exec.html">exec</a> - Execute a command<br>
+ <a href="nohup.html">nohup</a> - Run a command immune to hangups<br>
+ <a href="su.html">su</a> - Run a command with substitute user and group id<br>
+ <a href="watch.html">watch</a> - Execute/display a program periodically<br>
+<a href="source.html">.source</a> - Run commands from a file </p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/env.html b/help/en/bash/env.html
new file mode 100644
index 0000000..15a9481
--- /dev/null
+++ b/help/en/bash/env.html
@@ -0,0 +1,92 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>env MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> env</h1>
+<p>Display, set, or remove environment variables, Run a command in
+a modified environment.</p>
+<pre><i>Syntax</i>
+ env [OPTION]... [NAME=VALUE]... [COMMAND [ARGS]...]
+
+Options
+
+ -u NAME
+ --unset=NAME
+ Remove variable NAME from the environment, if it was in the
+ environment.
+
+ -
+ -i
+ --ignore-environment
+ Start with an empty environment, ignoring the inherited
+ environment.</pre>
+<p><span class="body"> Arguments of the form `VARIABLE=VALUE' set the environment
+ variable VARIABLE to value VALUE. <br>
+ <br>
+ VALUE may be empty (`VARIABLE='). Setting a variable to an empty value is different
+ from unsetting it.<br>
+ <br>
+ The first remaining argument specifies the program name to invoke; it is searched
+ for according to the `PATH' environment variable. Any remaining arguments are
+ passed as arguments to that program.<br>
+ <br>
+ If no command name is specified following the environment specifications, the
+ resulting environment is printed. This is like specifying a command name of
+ `printenv'.</span> </p>
+<p><em>&quot;It isn't the pollution that is harming the environment, it's the
+impurities in the air and water&quot; - Dan Quayle</em></p>
+<p><b>Related</b>:<br>
+ <br>
+ <a href="hostname.html">hostname</a> - Print or set system name<br>
+ <a href="local.html">local</a> - Create variables <br>
+ <a href="logname.html">logname</a> - Print current login name<br>
+ printenv - Print environment variables <br>
+ <a href="readonly.html">readonly</a> - Mark variables/functions as readonly<br>
+ <a href="set.html">set</a> - Manipulate shell variables and functions<br>
+ <a href="shift.html">shift</a> - Shift positional parameters<br>
+ <a href="shopt.html">shopt</a> - Shell Options <br>
+ <a href="uname.html">uname</a> - Print system information<br>
+ <a href="unset.html">unset</a> - Remove variable or function names<br>
+ <a href="who.html">who</a> - Print who is currently logged in<br>
+Equivalent Windows command:
+ <a href="../term_tools/nt/set.html">SET</a> / <a href="../term_tools/nt/setx.html">SETX</a> - Display, set, or remove environment
+ variables</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/eval.html b/help/en/bash/eval.html
new file mode 100644
index 0000000..ed8dd1c
--- /dev/null
+++ b/help/en/bash/eval.html
@@ -0,0 +1,65 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>eval MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> eval</h1>
+<p>Evaluate several commands/arguments</p>
+<pre>Syntax
+ eval [<var>arguments</var>]</pre>
+<p><span class="body">The arguments are concatenated together into a single command,
+ which is then read and executed, and its exit status returned as the exit status
+ of <code>eval</code>. If there are no arguments or only empty arguments, the
+ return status is zero. <br>
+ <br>
+ eval is a POSIX `special' builtin </span></p>
+<p><em>&quot;If you get to the edge of the penalty area with the ball and don't know
+ what to do next, just stick the ball in the net for now. We can evaluate the other options later&quot; - Bill Shankley </em></p>
+<p><b>Related</b>:<br>
+ <br>
+ <a href="case.html">case</a> - Conditionally perform a command<br>
+ <a href="expr.html">expr</a> - Evaluate expressions<br>
+ <a href="for.html">for</a> - Expand <var>words</var>, and execute <var>commands</var>
+ <br>
+ <a href="awk.html">gawk</a> - Find and Replace text within file(s)<br>
+<a href="test.html">test</a> - Evaluate a conditional expression <br>
+Equivalent Windows command:
+<a href="../term_tools/nt/call.html">CALL</a> - Call one batch program from another</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/exec.html b/help/en/bash/exec.html
new file mode 100644
index 0000000..8a40cf2
--- /dev/null
+++ b/help/en/bash/exec.html
@@ -0,0 +1,85 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>exec MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> exec</h1>
+<p>Execute a command</p>
+<pre>Syntax
+ exec [-cl] [-a <var>name</var>] [<var>command</var> [<var>arguments</var>]]
+
+Options
+ -l Place a dash at the beginning of the zeroth arg passed to <var>command</var>.
+ (This is what the <code>login</code> program does.)
+ -c Causes <var>command</var> to be executed with an empty environment.
+ <samp>-a </samp> The shell passes <var>name</var> as the zeroth argument to <var>command</var>.
+</pre>
+<p> If <var>command</var> is supplied, it replaces the shell without
+ creating a new process. If no <var>command</var> is specified, redirections
+ may be used to affect the current shell environment. <br>
+ <br>
+ If there are no redirection errors, the return status is zero; otherwise the
+ return status is non-zero.</p>
+<p>exec is a BOURNE shell command and a POSIX `special' builtin</p>
+<p>To run an executable file or a shell script from the command line it is often not necessary to use <span class="code">exec</span> at all, just prefix the filename with .<span class="code">/ </span><br>
+bash will only search the <b>path </b>not the current working directory for the file. </p>
+<p>To execute a program/script in the current working directory use:</p>
+<p><span class="code">./<i>file_name</i></span><br>
+<span class="code">or<br>
+./<i>ScriptName</i> </span><br>
+<br>
+ You may be tempted to 'fix' this by adding '.' to $PATH but this is widely considered to be a bad idea for security reasons.</p>
+<p><em> &quot;In art the hand can never execute anything higher than the heart can inspire&quot; - Ralph Waldo Emerson</em></p>
+<p><b>Related</b>:<br>
+ <br>
+ exit - Exit the shell<br>
+ <a href="builtin.html">builtin</a> - Run a shell builtin<br>
+ <a href="crontab.html">crontab</a> - Schedule a command to run at a later time<br>
+ <a href="chroot.html">chroot</a> - Run a command with a different root directory<br>
+ <a href="if.html">if</a> - Conditionally perform a command<br>
+ <a href="nohup.html">nohup</a> - Run a command immune to hangups<br>
+ <a href="source.html">.source</a>
+ - Run commands from a file <br>
+ <a href="su.html">su</a> - Run a command with substitute user and group id<br>
+ <a href="type.html">type</a> - Describe a command <br>
+ <a href="watch.html">watch</a> - Execute/display a program periodically<br>
+Equivalent Windows command: <a href="../term_tools/nt/start.html">START</a> / <a href="../term_tools/nt/cmd.html">
+ CMD</a> - Start a new CMD shell</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/exit.html b/help/en/bash/exit.html
new file mode 100644
index 0000000..fa4062d
--- /dev/null
+++ b/help/en/bash/exit.html
@@ -0,0 +1,57 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>exit MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1>exit</h1>
+<p>Exit from a program, shell or log out of a Unix network.</p>
+<pre>Syntax
+ exit
+</pre>
+<p>If supported will exit you from the program, shell or log you out of network.</p>
+<p> If exit does not log you out you can also do logout, lo, bye, quit, also Ctrl-D may work. </p>
+<p><br>
+<i>&quot;Either I'm dead or my watch has stopped&quot; - Groucho Marx's last words</i></p>
+
+<p><b>Related:</b><br>
+ <br>
+ <a href="logout.html">logout</a> - Exit a login shell<br>
+Equivalent Windows commands: EXIT</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/expand.html b/help/en/bash/expand.html
new file mode 100644
index 0000000..e69d001
--- /dev/null
+++ b/help/en/bash/expand.html
@@ -0,0 +1,81 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>expand MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> expand</h1>
+<p>Convert tabs to spaces, write the contents of each given <em>file</em>,
+ to standard output, with tab characters converted to the appropriate number
+ of spaces. If no <em>file</em> is given, or for a <em>file</em> of `-', write to standard input</p>
+<pre>Syntax
+ expand [<em>options</em>]... [<em>file</em>]...
+
+Options
+`-TAB1[,TAB2]...'
+`-t TAB1[,TAB2]...'
+`--tabs=TAB1[,TAB2]...'
+ If only one tab stop is given, set the tabs TAB1 spaces apart
+ (default is 8). Otherwise, set the tabs at columns TAB1, TAB2,
+ ... (numbered from 0), and replace any tabs beyond the last
+ tabstop given with single spaces. If the tabstops are specified
+ with the `-t' or `--tabs' option, they can be separated by blanks
+ as well as by commas.
+
+`-i'
+`--initial'
+ Only convert initial tabs (those that precede all non-space or
+ non-tab characters) on each line to spaces.</pre>
+<p>By default, expand converts all tabs to spaces. It preserves backspace characters in the output; they decrement the column count for tab calculations. The default action is equivalent to `-8' (set tabs every 8 columns).</p>
+<p><i>&quot;Apply yourself. Get all the education you can, but then,
+ by God, do something. Don't just stand there, make it happen." - Lee
+ Iacocca, Chairman, Chrysler Motors</i></p>
+<p><b>Related</b>:<br>
+ <br>
+ <a href="cut.html">cut</a> - Divide a file into several parts<br>
+ <a href="expr.html">expr</a> - Evaluate expressions <br>
+ <a href="fmt.html">fmt</a> - Reformat paragraph text <br>
+ <a href="grep.html">grep</a> - Search file(s) for lines that match a given pattern
+ <br>
+ <a href="tr.html">tr</a> - Translate, squeeze, and/or delete characters <br>
+ <a href="unexpand.html">unexpand</a> - Convert spaces to tabs <br>
+<a href="uuencode.html">uuencode</a> - Encode a binary file <br>
+Equivalent Windows command: <a href="../term_tools/nt/syntax-replace.html">SET variable</a> - change part of a
+variable</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/export.html b/help/en/bash/export.html
new file mode 100644
index 0000000..e92a5e7
--- /dev/null
+++ b/help/en/bash/export.html
@@ -0,0 +1,83 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>export MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1>export</h1>
+<p>Set an environment variable. Mark each <var>name</var> to be passed to child processes in the environment.</p>
+<pre>Syntax
+ export [-fn] [-p] [<var>name</var>[=<var>value</var>]]
+
+Options
+ -f The <var>name</var>s refer to shell functions;
+ otherwise the names refer to shell variables
+ -n No longer mark each <var>name</var> for export.
+ -p Display output in a form that may be reused as input.
+</pre>
+<p> If no <var>names</var> are supplied, or if the `-p' option is given, a list
+ of exported names is displayed. </p>
+<p>The return status is zero unless an invalid option is supplied, one of the
+ names is not a valid shell variable name, or `-f' is supplied with a name that
+ is not a shell function.</p>
+<p>export is a BOURNE shell command and a POSIX `special' builtin.<br>
+ <br>
+ Example - local variables</p>
+<pre>old_file=export.csv
+new_file=last.csv
+mv $old_file $new_file</pre>
+<p>Example - global variables</p>
+<pre>mydepartment=Sales ; export mydepartment
+mycustomer='Brown Brothers' ; export mycustomer</pre>
+<p><em>&quot;An average user will saturate their cognitive capacity
+ if
+they have more than seven things to remember&quot;</em></p>
+<p><b>Related:</b><br>
+ <br>
+ <a href="env.html">env</a> - Display, set, or remove environment variables<br>
+ <a href="echo.html">echo</a> - Display message on screen <br>
+ <a href="hostname.html">hostname</a> - Print or set system name<br>
+ <a href="local.html">local</a> - Create variables <br>
+ printenv - Print environment variables <br>
+ <a href="readonly.html">readonly</a> - Mark variables/functions as readonly
+ <br>
+ <a href="shift.html">shift</a> - Shift positional parameters<br>
+ <a href="unset.html">unset</a> - Remove variable or function names <br>
+Equivalent Windows command: <a href="../term_tools/nt/setx.html">SETX</a> - Set environment variables permanently</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/expr.html b/help/en/bash/expr.html
new file mode 100644
index 0000000..eacab83
--- /dev/null
+++ b/help/en/bash/expr.html
@@ -0,0 +1,198 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>expr MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> expr</h1>
+<p>Evaluate expressions, evaluates an expression and writes the result
+on standard output.</p>
+<pre>Syntax
+ expr <em>expression</em>...
+
+Description:
+Each token of the expression must be a separate argument.
+
+Operands are either numbers or strings. `expr' coerces anything
+appearing in an operand position to an integer or a string depending on
+the operation being applied to it.
+
+Strings are not quoted for `expr' itself, though you may need to
+quote them to protect characters with special meaning to the shell,
+e.g., spaces.
+
+Operators may given as infix symbols or prefix keywords. Parentheses
+may be used for grouping in the usual manner (you must quote parentheses
+to avoid the shell evaluating them, however).
+
+String expressions
+------------------
+
+ `expr' supports pattern matching and other string operators. These
+have lower precedence than both the numeric and relational operators (in
+the next sections).
+
+`STRING : REGEX'
+ Perform pattern matching. The arguments are coerced to strings
+ and the second is considered to be a (basic, a la GNU `grep')
+ regular expression, with a `^' implicitly prepended. The first
+ argument is then matched against this regular expression.
+
+ If the match succeeds and REGEX uses `\(' and `\)', the `:'
+ expression returns the part of STRING that matched the
+ subexpression; otherwise, it returns the number of characters
+ matched.
+
+ If the match fails, the `:' operator returns the null string if
+ `\(' and `\)' are used in REGEX, otherwise 0.
+
+ Only the first `\( ... \)' pair is relevant to the return value;
+ additional pairs are meaningful only for grouping the regular
+ expression operators.
+
+ In the regular expression, `\+', `\?', and `\|' are operators
+ which respectively match one or more, zero or one, or separate
+ alternatives. SunOS and other `expr''s treat these as regular
+ characters. (POSIX allows either behavior.)
+
+`match STRING REGEX'
+ An alternative way to do pattern matching. This is the same as
+ `STRING : REGEX'.
+
+`substr STRING POSITION LENGTH'
+ Returns the substring of STRING beginning at POSITION with length
+ at most LENGTH. If either POSITION or LENGTH is negative, zero,
+ or non-numeric, returns the null string.
+
+`index STRING CHARSET'
+ Returns the first position in STRING where the first character in
+ CHARSET was found. If no character in CHARSET is found in STRING,
+ return 0.
+
+`length STRING'
+ Returns the length of STRING.
+
+`quote TOKEN'
+ Interpret TOKEN as a string, even if it is a keyword like MATCH or
+ an operator like `/'. This makes it possible to test `expr length
+ quote "$x"' or `expr quote "$x" : '.*/\(.\)'' and have it do the
+ right thing even if the value of $X happens to be (for example)
+ `/' or `index'. This operator is a GNU extension. It is disabled
+ when the environment variable `POSIXLY_CORRECT' is set.
+
+To make `expr' interpret keywords as strings, you must use the
+`quote' operator.
+
+Numeric expressions
+-------------------
+
+ `expr' supports the usual numeric operators, in order of increasing
+precedence. The string operators (previous section) have lower
+precedence, the connectives (next section) have higher.
+
+`+ -'
+ Addition and subtraction. Both arguments are coerced to numbers;
+ an error occurs if this cannot be done.
+
+`* / %'
+ Multiplication, division, remainder. Both arguments are coerced to
+ numbers; an error occurs if this cannot be done.
+
+Relations for `expr'
+--------------------
+
+`expr' supports the usual logical connectives and relations. These
+are higher precedence than either the string or numeric operators
+(previous sections). Here is the list, lowest-precedence operator
+first.
+
+`|' Returns its first argument if that is neither null nor 0,
+ otherwise its second argument.
+
+`&' Return its first argument if neither argument is null or 0,
+ otherwise 0.
+
+`< <= = == != >= >'
+ Compare the arguments and return 1 if the relation is true, 0
+ otherwise. `==' is a synonym for `='. `expr' first tries to
+ coerce both arguments to numbers and do a numeric comparison; if
+ either coercion fails, it does a lexicographic comparison.
+
+Exit status:
+------------
+
+ 0 if the expression is neither null nor 0,
+ 1 if the expression is null or 0,
+ 2 for invalid expressions.
+
+<strong>Examples</strong>
+
+ Here are a few examples, including quoting for shell metacharacters.
+
+ To add 1 to the shell variable `foo', in Bourne-compatible shells:
+ foo=`expr $foo + 1`
+
+ To print the non-directory part of the file name stored in `$fname',
+ which need not contain a `/'.
+ expr $fname : '.*/\(^.*\)' '^|' $fname
+
+ An example showing that `\+' is an operator:
+ expr aaa : 'a\+'
+ => 3
+
+ expr abc : 'a\(.\)c'
+ => b
+ expr index abcdef cz
+ => 3
+ expr index index a
+ error--> expr: syntax error
+ expr index quote index a
+ => 0</pre>
+<p><em>&quot;Art is man's expression of his joy in labor&quot; - William Morris</em></p>
+<p><b>Related</b>:<br>
+ <br>
+ <a href="eval.html">eval</a> - Evaluate several commands/arguments<br>
+ <a href="for.html">for</a> - Expand <var>words</var>, and execute <var>commands</var>
+ <br>
+ <a href="function.html">function</a> - Define Function Macros <br>
+ <a href="awk.html">gawk</a> - Find and Replace text within file(s) <br>
+ <a href="test.html">test</a> - Evaluate a conditional expression <br>
+Equivalent Windows commands:
+ <a href="../term_tools/nt/set.html">SET</a> /A - environment variable arithmetic </p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/false.html b/help/en/bash/false.html
new file mode 100644
index 0000000..799e7a3
--- /dev/null
+++ b/help/en/bash/false.html
@@ -0,0 +1,64 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>false MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> false</h1>
+<p>Do nothing, returning a non-zero (false) exit status</p>
+<pre>Syntax
+ false</pre>
+<p> `false' does nothing except return an exit status of 1, meaning
+ "failure". It can be used as a place holder in shell scripts where an<br>
+ unsuccessful command is needed.<br>
+ <br>
+ `false' ignores <strong>all</strong> command line arguments, even `--help' and
+ `--version', since to do otherwise would change expected behavior that
+some programmers may be relying on.</p>
+<p> This version of `false' is implemented as a C program, and is thus
+ more secure and faster than a shell script implementation, and may
+ safely be used as a dummy shell for the purpose of disabling accounts.</p>
+<p><em>&quot;False in one thing, false in everything&quot; - Legal maxim </em></p>
+<p><b>Related</b>:<br>
+ <br>
+ <a href="true.html">true</a> - Do nothing, successfully<br>
+ <a href="yes.html">yes</a> - Print a string until interrupted<br>
+Equivalent Windows commands:
+The <a href="../term_tools/nt/color.html">COLOR</a> command can be used to set an %errorlevel%</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/fdformat.html b/help/en/bash/fdformat.html
new file mode 100644
index 0000000..30b72be
--- /dev/null
+++ b/help/en/bash/fdformat.html
@@ -0,0 +1,87 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>fdformat MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> fdformat</h1>
+<p>Low-level format a floppy disk</p>
+<pre>Syntax
+ fdformat [ -n ] <em>device
+
+</em>Options
+ -n No verify. This will disable the verification
+ that is performed after the format.</pre>
+<p> fdformat does a low level format on a floppy disk. </p>
+<p>device
+ is usually one of the following (for floppy devices, the major =2, and the minor is shown for informational purposes only):</p>
+<pre>
+ /dev/fd0d360 (minor = 4)
+ /dev/fd0h1200 (minor = 8)
+ /dev/fd0D360 (minor = 12)
+ /dev/fd0H360 (minor = 12)
+ /dev/fd0D720 (minor = 16)
+ /dev/fd0H720 (minor = 16)
+ /dev/fd0h360 (minor = 20)
+ /dev/fd0h720 (minor = 24)
+ /dev/fd0H1440 (minor = 28)
+
+ /dev/fd1d360 (minor = 5)
+ /dev/fd1h1200 (minor = 9)
+ /dev/fd1D360 (minor = 13)
+ /dev/fd1H360 (minor = 13)
+ /dev/fd1D720 (minor = 17)
+ /dev/fd1H720 (minor = 17)
+ /dev/fd1h360 (minor = 21)
+ /dev/fd1h720 (minor = 25)
+ /dev/fd1H1440 (minor = 29)</pre>
+<p> The generic floppy devices, /dev/fd0 and /dev/fd1, will
+ fail to work with fdformat when a non-standard format is<br>
+ being used, or if the format has not been autodetected
+ earlier. In this case, use setfdprm(8) to load the disk
+parameters.</p>
+<p><i>&ldquo;Meetings are a symptom of bad organization. The fewer meetings the better&rdquo; - Peter F. Drucker</i></p>
+<p><b>Related</b>:<br>
+ <br>
+ format - Format disks or tapes<br>
+ <a href="mtools.html">mtools</a> - Manipulate MS-DOS files<br>
+ fd(4), setfdprm(8), mkfs(8), emkfs(8)<br>
+Equivalent Windows commands:
+ <a href="../term_tools/nt/format.html">FORMAT</a> - Format a disk</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/fdisk.html b/help/en/bash/fdisk.html
new file mode 100644
index 0000000..6bb0919
--- /dev/null
+++ b/help/en/bash/fdisk.html
@@ -0,0 +1,192 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>fdisk MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> fdisk</h1>
+<p>Partition table manipulator for Linux</p>
+<pre>Syntax
+ fdisk [-u] <em>device</em>
+
+ fdisk -l [-u] <em>device</em> ...
+
+ fdisk -s <em>partition</em> ...
+
+ fdisk -v
+
+Options
+ -u When listing partition tables, give sizes in sectors instead of cylinders.
+
+ -l List the partition tables for /dev/hd[a-d], /dev/sd[a-h], /dev/ed[a-d], and then exit.
+
+ -s <em>partition</em>
+ The size of the partition (in blocks) is printed on the standard output.
+
+ -v Print version number of fdisk program and exit.
+
+Description</pre>
+<p>Hard disks can be divided into one or more logical disks called partitions. This division is described in the partition table found in sector 0 of the disk.<br>
+<br>
+In the BSD world one talks about `disk slices' and a `disklabel'.<br>
+<br>
+Linux needs at least one partition, namely for its root
+file system. It can use swap files and/or swap partitions, but the latter are more efficient. So, usually one<br>
+will want a second Linux partition dedicated as swap partition. On Intel compatible hardware, the BIOS that boots
+the system can often only access the first 1024 cylinders of the disk. For this reason people with large disks often create a third partition, just a few MB large, typically mounted on /boot, to store the kernel image and a
+few auxiliary files needed at boot time, so as to make sure that this stuff is accessible to the BIOS. There may be reasons of security, ease of administration and backup,or testing, to use more than the minimum number of partitions.<br>
+<br>
+fdisk (in the first form of invocation) is a menu driven program for creation and manipulation of partition tables.<br>
+It understands DOS type partition tables and BSD or SUN type disklabels.</p>
+<pre>
+ The device is usually one of the following:
+ /dev/hda
+ /dev/hdb
+ /dev/sda
+ /dev/sdb
+ (/dev/hd[a-h] for IDE disks, /dev/sd[a-p] for SCSI disks,
+ /dev/ed[a-d] for ESDI disks, /dev/xd[ab] for XT disks). A
+ device name refers to the entire disk.
+
+ The partition is a device name followed by a partition
+ number. For example, /dev/hda1 is the first partition on
+ the first IDE hard disk in the system. IDE disks can have
+ up to 63 partitions, SCSI disks up to 15. See also
+ /usr/src/linux/Documentation/devices.txt.
+
+ A BSD/SUN type disklabel can describe 8 partitions, the
+ third of which should be a `whole disk' partition. Do not
+ start a partition that actually uses its first sector
+ (like a swap partition) at cylinder 0, since that will
+ destroy the disklabel.
+
+ An IRIX/SGI type disklabel can describe 16 partitions, the
+ eleventh of which should be an entire `volume' partition,
+ while the ninth should be labeled `volume header'. The
+ volume header will also cover the partition table, i.e.,
+ it starts at block zero and extends by default over five
+ cylinders. The remaining space in the volume header may
+ be used by header directory entries. No partitions may
+ overlap with the volume header. Also do not change its
+ type and make some file system on it, since you will lose
+ the partition table. Use this type of label only when
+ working with Linux on IRIX/SGI machines or IRIX/SGI disks
+ under Linux.</pre>
+<p>A DOS type partition table can describe an unlimited number of partitions. In sector 0 there is room for the
+description of 4 partitions (called `primary'). One of these may be an extended partition; this is a box holding
+logical partitions, with descriptors found in a linked list of sectors, each preceding the corresponding logical
+partitions. The four primary partitions, present or not, get numbers 1-4. Logical partitions start numbering from
+5.<br>
+<br>
+In a DOS type partition table the starting offset and the size of each partition is stored in two ways: as an absoute number of sectors (given in 32 bits) and as a Cylinders/Heads/Sectors triple (given in 10+8+6 bits). The former is OK - with 512-byte sectors this will work up to 2 TB. The latter has two different problems. First of all, these C/H/S fields can be filled only when the number of heads and the number of sectors per track are known. Secondly, even if we know what these numbers should be, the 24 bits that are available do not suffice. DOS uses C/H/S only, Windows uses both, Linux never uses C/H/S.<br>
+<br>
+If possible, fdisk will obtain the disk geometry automatically. This is not necessarily the physical disk geometry
+(indeed, modern disks do not really have anything like a physical geometry, certainly not something that can be
+described in simplistic Cylinders/Heads/Sectors form), but is the disk geometry that MS-DOS uses for the partition
+table.<br>
+<br>
+Usually all goes well by default, and there are no problems if Linux is the only system on the disk. However, if
+the disk has to be shared with other operating systems, it is often a good idea to let an fdisk from another operating system make at least one partition. When Linux boots<br>
+<br>
+it looks at the partition table, and tries to deduce what(fake) geometry is required for good cooperation with
+other systems.<br>
+<br>
+Whenever a partition table is printed out, a consistency check is performed on the partition table entries. This
+check verifies that the physical and logical start and end points are identical, and that the partition starts and
+ends on a cylinder boundary (except for the first partition).<br>
+<br>
+Some versions of MS-DOS create a first partition which does not begin on a cylinder boundary, but on sector 2 of
+the first cylinder. Partitions beginning in cylinder 1 cannot begin on a cylinder boundary, but this is unlikely
+to cause difficulty unless you have OS/2 on your machine.<br>
+<br>
+A sync() and a BLKRRPART ioctl() (reread partition table from disk) are performed before exiting when the partition
+table has been updated. Long ago it used to be necessary to reboot after the use of fdisk. I do not think this is
+the case anymore - indeed, rebooting too quickly might cause loss of not-yet-written data. Note that both the
+kernel and the disk hardware may buffer data.</p>
+<p> DOS 6.x WARNING<br>
+ The DOS 6.x FORMAT command looks for some information in
+ the first sector of the data area of the partition, and
+ treats this information as more reliable than the information in the partition table. DOS FORMAT expects DOS FDISK
+ to clear the first 512 bytes of the data area of a partition whenever a size change occurs. DOS FORMAT will look
+ at this extra information even if the /U flag is given,
+ we consider this a bug in DOS FORMAT and DOS FDISK.<br>
+ <br>
+ The bottom line is that if you use cfdisk or fdisk to
+ change the size of a DOS partition table entry, then you
+ must also use dd to zero the first 512 bytes of that partition before using DOS FORMAT to format the partition.<br>
+ For example, if you were using cfdisk to make a DOS partition table entry for /dev/hda1, then (after exiting fdisk
+ or cfdisk and rebooting Linux so that the partition table
+ information is valid) you would use the command "dd
+ if=/dev/zero of=/dev/hda1 bs=512 count=1" to zero the
+ first 512 bytes of the partition.<br>
+ <br>
+ BE EXTREMELY CAREFUL if you use the dd command, since a
+ small typo can make all of the data on your disk useless.<br>
+ <br>
+ For best results, you should always use an OS-specific
+ partition table program. For example, you should make DOS
+ partitions with the DOS FDISK program and Linux partitions
+with the Linux fdisk or Linux cfdisk program.</p>
+<p> BUGS<br>
+ There are several *fdisk programs around. Each has its
+problems and strengths. </p>
+<p>Try them in the order <strong>cfdisk,
+ fdisk, sfdisk</strong>. (Indeed, <span class="body"><a href="cfdisk.html">cfdisk</a></span> is a beautiful program
+ that has strict requirements on the partition tables it
+ accepts, and produces high quality partition tables. Use
+it if you can. </p>
+<p>fdisk is a buggy program that does fuzzy things - usually it happens to produce reasonable results.<br>
+ Its single advantage is that it has some support for BSD
+ disk labels and other non-DOS partition tables. Avoid it
+ if you can. sfdisk is for hackers only - the user interface is terrible, but it is more correct than fdisk and
+ more powerful than both fdisk and cfdisk. Moreover, it
+can be used noninteractively.)</p>
+<p> The IRIX/SGI type disklabel is currently not supported by the kernel. Moreover, IRIX/SGI header directories are not
+ fully supported yet.<br>
+ <br>
+The option `dump partition table to file' is missing.</p>
+<p><i>&ldquo;When I'm reading material, if I'm a little bit afraid of a part and I'm willing to admit that to myself, then I'll do it, definitely. If
+ I'm worried about being able to do it, to get it - I absolutely just love it&rdquo; - Jack
+ Lemmon</i></p>
+<p><b>R</b><b>elated</b>:<br>
+ <br>
+ <a href="cfdisk.html">cfdisk</a> - Partition table manipulator for Linux <br>
+ <a href="fdformat.html">fdformat</a> - Low-level format a floppy disk<br>
+Equivalent Windows commands: <a href="../term_tools/nt/diskpart.html">DISKPART</a> Disk Administration</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/fg.html b/help/en/bash/fg.html
new file mode 100644
index 0000000..e64a2ef
--- /dev/null
+++ b/help/en/bash/fg.html
@@ -0,0 +1,61 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>fg MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1>fg</h1>
+<p>Send job to foreground </p>
+<pre>Syntax
+ fg [<i>PID</i>...]
+
+Options:
+ If PID is specified, the job with the specified group id is put in the foreground.</pre>
+<p>Send the specified job to the foreground. While a foreground job is executed, fish is suspended. If no job is specified, the last job to be used is put in the foreground.</p>
+<p>The PID of the desired process is usually found by using process expansion.</p>
+<p>Example</p>
+<p>Put the job with job id 0 in the foreground:<span class="telety"><br>
+fg %0 </span></p>
+<p><i>&ldquo;A true friend stabs you in the front&rdquo; - Oscar Wilde</i></p>
+<p><b>Related bash commands</b>:<br>
+ <br>
+<a href="bg.html">bg</a> - Send to background<br>
+<a href="jobs.html">jobs</a> - List active jobs<br>
+<a href="suspend.html">suspend</a> - Suspend execution of this shell</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/fgrep.html b/help/en/bash/fgrep.html
new file mode 100644
index 0000000..c088dab
--- /dev/null
+++ b/help/en/bash/fgrep.html
@@ -0,0 +1,68 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>fgrep MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> fgrep</h1>
+<p>Search file(s) for lines that match a fixed string</p>
+<pre>Syntax
+ fgrep &lt;<em>options</em>&gt; ...
+
+fgrep is the same as `grep <a href="../term_tools/bash/grep2.html">-F</a>'
+
+all other <em>options</em> are the same as <a href="grep.html">grep</a> </pre>
+<p>It's a popular fallacy that <span class="code">fgrep</span> stands for fast-grep,
+ in fact <span class="code">fgrep</span> means fixed-string grep<b>.</b></p>
+<p>fgrep implements the <a href="http://en.wikipedia.org/wiki/Aho%E2%80%93Corasick_string_matching_algorithm">Aho–Corasick string matching algorithm</a> which is very fast at matching multiple strings in the input stream/file. So if fgrep is used like this:</p>
+<p class="code">fgrep -f patternlist.txt largetextfile.txt</p>
+<p>it is much faster than</p>
+<p class="code">grep -f patternlist.txt largetextfile.txt</p>
+<p>Matching a single pattern with fgrep is not significantly faster than grep.</p>
+<p><em>&quot;The knowledge imposes a pattern, and falsifies, For the pattern is new in
+ every moment...&quot; - T. S. Eliot</em><b><br>
+ <br>
+ Related</b>:<br>
+ <br>
+ <a href="egrep.html">egrep</a> - Search file(s) for lines that match an extended
+ expression<br>
+ <a href="awk.html">gawk</a> - Find and Replace text within file(s) <br>
+ <a href="grep.html">grep</a> - Search file(s) for lines that match a given pattern <br>
+Equivalent Windows command: <a href="../term_tools/nt/findstr.html">FINDSTR</a> - Search for strings in files </p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/find.html b/help/en/bash/find.html
new file mode 100644
index 0000000..d7165ed
--- /dev/null
+++ b/help/en/bash/find.html
@@ -0,0 +1,514 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>find MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> find</h1>
+<p>Search a folder hierarchy for filename(s) that meet a desired
+criteria: Name, Size, File Type - see <a href="#examples">examples</a>.</p>
+<pre>Syntax
+ find [-H] [-L] [-P] [<em>path</em>...] [<i>expression</i>]</pre>
+<p> GNU find searches the directory tree rooted at each given file name by evaluating the given <i>expression</i> from left to right, according to the rules of precedence (<a href="#operators">see Operators</a>), until the outcome is known (the left hand side is
+false for <b>AND</b> operations, true for <b>OR</b>), at which point find moves on to the next file name. </p>
+<p><b>Options</b></p>
+<p>The '-H', '-L' and '-P' options control the treatment of symbolic links. Command-line arguments following these are taken to be names of files or directories to be examined, up to the first argument that begins with <span class="code">'-', '(', ')', ',', or '!'</span>. That argument and any following arguments are taken to be the expression describing what is to be searched for. If no paths are given, the current directory is used. If no expression is given, the expression '-print' is used (but you should probably consider using '-print0' instead, anyway).</p>
+<p>This manual page talks about 'options' within the expression list. These options control the behaviour of find but are specified immediately after the last path name. The three 'real' options '-H', '-L' and '-P' must appear before the first path name, if at all.</p>
+<blockquote>
+<p class="code">-P</p>
+<p>Never follow symbolic links. This is the default behaviour. When find examines or prints information a file, and the file is a symbolic link, the information used shall be taken from the properties of the symbolic link itself.</p>
+<p class="code">-L</p>
+<p>Follow symbolic links. When find examines or prints information about files, the information used shall be taken from the properties of the file to which the link points, not from the link itself (unless it is a broken symbolic link or find is unable to examine the file to which the link points). Use of this option implies -noleaf. If you later use the -P option, -noleaf will still be in effect. If -L is in effect and finddiscovers a symbolic link to a subdirectory during its search, the subdirectory pointed to by the symbolic link will be searched.<br>
+When the -L option is in effect, the -type predicate will always match against the type of the file that a symbolic link points to rather than the link itself (unless the symbolic link is broken). Using -L causes the -lname and -ilname predicates always to return false. </p>
+<p class="code">-H</p>
+<p>Do not follow symbolic links, except while processing the command line arguments. When find examines or prints information about files, the information used shall be taken from the properties of the symbolic link itself. The only exception to this behaviour is when a file specified on the command line is a symbolic link, and the link can be resolved. For that situation, the information used is taken from whatever the link points to (that is, the link is followed). The information about the link itself is used as a fallback if the file pointed to by the symbolic link cannot be examined. If -H is in effect and one of the paths specified on the command line is a symbolic link to a directory, the contents of that directory will be examined (though of course -maxdepth 0 would prevent this).<br>
+If more than one of -H, -L and -P is specified, each overrides the others; the last one appearing on the command line takes effect. Since it is the default, the -P option should be considered to be in effect unless either -H or -L is specified.</p>
+</blockquote>
+<p>GNU find frequently stats files during the processing of the command line itself, before any searching has begun. These options also affect how those arguments are processed. Specifically, there are a number of tests that compare files listed on the command line against a file we are currently considering. In each case, the file specified on the command line will have been examined and some of its properties will have been saved. If the named file is in fact a symbolic link, and the -P option is in effect (or if neither -H nor -L were specified), the information used for the comparison will be taken from the properties of the symbolic link. Otherwise, it will be taken from the properties of the file the link points to. If find cannot follow the link (for example because it has insufficient privileges or the link points to a nonexistent file) the properties of the link itself will be used.</p>
+<p>When the -H or -L options are in effect, any symbolic links listed as the argument of -newer will be dereferenced, and the timestamp will be taken from the file to which the symbolic link points. The same consideration applies to -anewer and -cnewer.</p>
+<p>The -follow option has a similar effect to -L, though it takes effect at the point where it appears (that is, if -L is not used but -follow is, any symbolic links appearing after -follow on the command line will be dereferenced, and those before it will not).</p>
+<p>Expressions</p>
+<p>The expression is made up of <b>options</b> (which affect overall operation rather than the processing of a specific file, and always return true), <b>tests</b> (which return a true or false value), and <b>actions</b> (which have side effects and return a true or false value), all separated by operators. -and is assumed where the operator is omitted.</p>
+<p>If the expression contains no actions other than -prune, -print is performed on all files for which the expression is true.</p>
+<p><b><a name="options"></a>OPTIONS</b></p>
+<p>All options always return true. Except for -follow and -daystart, they always take effect, rather than being processed only when their place in the expression is reached. Therefore, for clarity, it is best to place them at the beginning of the expression. A warning is issued if you don't do this.</p>
+<p><span class="code">-daystart</span><br>
+Measure times (for -amin, -atime, -cmin, -ctime, -mmin, and -mtime) from the beginning of today rather than from 24 hours ago. This option only affects tests which appear later on the command line. </p>
+<p><span class="code">-depth<br>
+</span>Process each directory's contents before the directory itself.</p>
+<p><span class="code">-d<br>
+</span>A synonym for -depth, for compatibility with FreeBSD, NetBSD, MacOS X and OpenBSD.</p>
+<p><span class="code">-follow</span><br>
+Deprecated; use the -L option instead. Dereference symbolic links. Implies -noleaf. The -follow option affects only those tests which appear after it on the command line. Unless the -H or -L option has been specified, the position of the -follow option changes the behaviour of the -newer predicate; any files listed as the argument of -newer will be dereferenced if they are symbolic links. The same consideration applies to -anewer and -cnewer. Similarly, the -type predicate will always match against the type of the file that a symbolic link points to rather than the link itself. Using -follow causes the -lname and -ilname predicates always to return false. </p>
+<p><span class="code">-help, --help</span><br>
+Print a summary of the command-line usage of find and exit. </p>
+<p><span class="code">-ignore_readdir_race</span><br>
+Normally, find will emit an error message when it fails to stat a file. If you give this option and a file is deleted between the time findreads the name of the file from the directory and the time it tries to stat the file, no error message will be issued. This also applies to files or directories whose names are given on the command line. This option takes effect at the time the command line is read, which means that you cannot search one part of the filesystem with this option on and part of it with this option off (if you need to do that, you will need to issue two find commands instead, one with the option and one without it). </p>
+<p><span class="code">-maxdepth <i>levels</i></span><br>
+Descend at most levels (a non-negative integer) levels of directories below the command line arguments. '-maxdepth 0' means only apply the tests and actions to the command line arguments. </p>
+<p><span class="code">-mindepth <i>levels</i></span><br>
+Do not apply any tests or actions at levels less than levels (a non-negative integer). '-mindepth 1' means process all files except the command line arguments. </p>
+<p><span class="code">-mount</span><br>
+Don't descend directories on other filesystems. An alternate name for -xdev, for compatibility with some other versions of find.</p>
+<p><span class="code">-noignore_readdir_race</span><br>
+Turns off the effect of -ignore_readdir_race. <br>
+<br>
+<span class="code">-noleaf</span><br>
+Do not optimize by assuming that directories contain 2 fewer subdirectories than their hard link count. This option is needed when searching filesystems that do not follow the Unix directory-link convention, such as CD-ROM or MS-DOS filesystems or AFS volume mount points. Each directory on a normal Unix filesystem has at least 2 hard links: its name and its '.' entry. Additionally, its subdirectories (if any) each have a '..' entry linked to that directory. When find is examining a directory, after it has statted 2 fewer subdirectories than the directory's link count, it knows that the rest of the entries in the directory are non-directories ('leaf' files in the directory tree). If only the files' names need to be examined, there is no need to stat them; this gives a significant increase in search speed. </p>
+<p><span class="code">-regextype <i>type</i></span><br>
+Changes the regular expression syntax understood by <b>-regex</b> and <b>-iregex</b> tests which occur later on the command line. Currently-implemented types are emacs (this is the default), posix-awk, posix-basic, posix-egrep and posix-extended.</p>
+<p><span class="code">-version, --version</span><br>
+Print the find version number and exit. </p>
+<p><span class="code">-warn, -nowarn</span><br>
+Turn warning messages on or off. These warnings apply only to the command line usage, not to any conditions that find might encounter when it searches directories. The default behaviour corresponds to -warn if standard input is a tty, and to -nowarn otherwise. </p>
+<p><span class="code">-xdev</span><br>
+Don't descend directories on other filesystems.</p>
+<p><b><a name="tests"></a>TESTS</b></p>
+<p>Numeric arguments can be specified as</p>
+<blockquote>
+<p><span class="code">+n
+</span>for greater than n,<br>
+<span class="code">-n
+</span>for less than n,<br>
+<span class="code">n</span>
+for exactly n.</p>
+</blockquote>
+<p><span class="code">-amin <i>n</i></span> File was last accessed n minutes ago. <br>
+<span class="code">-anewer <i>file</i></span> File was last accessed more recently than file was modified. If file is a symbolic link and the -H option or the -L option is in effect, the access time of the file it points to is always used. <br>
+<br>
+<span class="code">-atime <i>n</i></span> File was last accessed n*24 hours ago. When find figures out how many 24-hour periods ago the file was last accessed, any fractional part is ignored:</p>
+<blockquote>
+<p>+7 = more than 7 days ago<br>
+
+2 = between 2 and 3 days ago<br>
+-2 = within the past 2 days<br>
++1 = more than 1 day old<br>
+1 = between 1 and 2 days ago<br>
+
+-1 = within the past 1 day <br>
+0 = within the past 1 day</p>
+<p>A file 47.99 hours old will round down to 1 day, for this to have matched <b>-atime +1</b>, the file would have to have been accessed <b> more </b>than one <b>day </b>ago i.e two days ago or longer. To match a date range you can specify more than one test. </p>
+</blockquote>
+<p><span class="code">-cmin <i>n</i></span>
+File's status was last changed n minutes ago. </p>
+<p><span class="code">-cnewer <i>file</i></span>
+File's status was last changed more recently than file was modified. If file is a symbolic link and the -H option or the -L option is in effect, the status-change time of the file it points to is always used. </p>
+<p><span class="code">-ctime n</span>
+File's status was last changed n*24 hours ago. See the comments for -atime to understand how rounding affects the interpretation of file status change times. </p>
+<p><span class="code">-empty</span> File is empty and is either a regular file or a directory.</p>
+<p><span class="code">-false</span>
+Always false.</p>
+<p><span class="code">-fstype <i>type</i></span>
+File is on a filesystem of type type. The valid filesystem types vary among different versions of Unix; an incomplete list of filesystem types that are accepted on some version of Unix or another is: ufs, 4.2, 4.3, nfs, tmp, mfs, S51K, S52K. You can use -printf with the %F directive to see the types of your filesystems. </p>
+<p><span class="code">-gid n</span> File's numeric group ID is n.</p>
+<p><span class="code">-group <i>gname</i></span>
+File belongs to group gname (numeric group ID allowed). </p>
+<p><span class="code">-ilname <i>pattern</i></span>
+Like -lname, but the match is case insensitive. If the -L option or the -follow option is in effect, this test returns false unless the symbolic link is broken. </p>
+<p><span class="code">-iname <i>pattern</i></span>
+Like -name, but the match is case insensitive. For example, the patterns 'fo*' and 'F??' match the file names 'Foo', 'FOO', 'foo', 'fOo', etc. In these patterns, unlike filename expansion by the shell, an initial '.' can be matched by '*'. That is, find -name *bar will match the file '.foobar'. Please note that you should quotepatterns as a matter of course, otherwise the shell will expand any wildcard characters in them. </p>
+<p><span class="code">-inum <i>n</i></span>
+File has inode number <i>n</i>. It is normally easier to use the -<b>samefile</b> test instead. </p>
+<p><span class="code">-ipath <i>pattern</i></span>
+Behaves in the same way as -iwholename. This option is deprecated, so please do not use it. </p>
+<p><span class="code">-iregex <i>pattern</i></span>
+Like -regex, but the match is case insensitive. </p>
+<p><span class="code">-iwholename <i>pattern</i></span>
+Like -wholename, but the match is case insensitive. </p>
+<p><span class="code">-links n</span>
+File has n links. </p>
+<p><span class="code">-lname <i>pattern</i></span>
+File is a symbolic link whose contents match shell pattern pattern. The metacharacters do not treat '/' or '.' specially. If the -L option or the -follow option is in effect, this test returns false unless the symbolic link is broken. </p>
+<p><span class="code">-mmin <i>n</i></span>
+File's data was last modified <i>n</i> minutes ago. e.g. <span class="code">find . -mmin +5 -mmin -10</span> # find files modifed between 5 and 10 minutes ago</p>
+<p><span class="code">-mtime <i>n</i></span>
+File's data was last modified n*24 hours ago. See the comments for -atime to understand how rounding affects the interpretation of file modification times. </p>
+<p><span class="code"><i>-</i>name<i> pattern</i></span><br>
+Base of file name (the path with the leading directories removed) matches shell pattern pattern. The metacharacters ('*', '?', and '[]') match a '.' at the start of the base name (this is a change in findutils-4.2.2; see section <a href="#standards">STANDARDS CONFORMANCE</a> below). To ignore a directory and the files under it, use -prune; see an example in the description of -wholename. Braces are not recognised as being special, despite the fact that some shells including Bash imbue braces with a special meaning in shell patterns. The filename matching is performed with the use of the <b>fnmatch</b>(3) library function. Don't forget to enclose the pattern in quotes in order to protect it from expansion by the shell. </p>
+<p><span class="code">-newer <i>file</i></span>
+File was modified more recently than file. If file is a symbolic link and the -H option or the -L option is in effect, the modification time of the file it points to is always used. </p>
+<p><span class="code">-nouser</span>
+No user corresponds to file's numeric user ID. </p>
+<p><span class="code">-nogroup</span>
+No group corresponds to file's numeric group ID. </p>
+<p><span class="code">-path <i>pattern</i></span>
+See -wholename. The predicate -path is also supported by HP-UX find. </p>
+<p><span class="code">-perm <i>mode</i></span><br>
+File's permission bits are exactly mode (octal or symbolic). Since an exact match is required, if you want to use this form for symbolic modes, you may have to specify a rather complex mode string. For example '-perm g=w' will only match files which have mode 0020 (that is, ones for which group write permission is the only permission set). It is more likely that you will want to use the '/' or '-' forms, for example '-perm -g=w', which matches any file with group write permission. See the <a href="#examples">EXAMPLES</a> section for some illustrative examples. </p>
+<p><span class="code">-perm -<i>mode</i></span><br>
+All of the permission bits mode are set for the file. Symbolic modes are accepted in this form, and this is usually the way in which would want to use them. You must specify 'u', 'g' or 'o' if you use a symbolic mode. See the <a href="#examples">EXAMPLES</a> section for some illustrative examples. </p>
+<p><span class="code">-perm /<i>mode</i></span><br>
+Any of the permission bits mode are set for the file. Symbolic modes are accepted in this form. You must specify 'u', 'g' or 'o' if you use a symbolic mode. See the <a href="#examples">EXAMPLES</a> section for some illustrative examples. If no permission bits in mode are set, this test currently matches no files. However, it will soon be changed to match any file (the idea is to be more consistent with the behaviour of <b>perm -000</b>). </p>
+<p><span class="code">-perm +<i>mode</i></span><br>
+Deprecated, old way of searching for files with any of the permission bits in mode set. You should use <b>-perm </b>/mode instead. Trying to use the '+' syntax with symbolic modes will yield surprising results. For example, '+u+x' is a valid symbolic mode (equivalent to +u,+x, i.e. 0111) and will therefore not be evaluated as <b>-perm</b> +mode but instead as the exact mode specifier <b>-perm</b> mode and so it matches files with exact permissions 0111 instead of files with any execute bit set. If you found this paragraph confusing, you're not alone - just use -perm /mode. This form of the <b>-perm</b> test is deprecated because the POSIX specification requires the interpretation of a leading '+' as being part of a symbolic mode, and so we switched to using '/' instead. </p>
+<p><span class="code">-regex <i>pattern</i></span><br>
+File name matches regular expression pattern. This is a match on the whole path, not a search. For example, to match a file named './fubar3', you can use the regular expression '.*bar.' or '.*b.*3', but not 'f.*r3'. The regular expressions understood by <b>find</b> are by default Emacs Regular Expressions, but this can be changed with the <b>-regextype</b> option. </p>
+<p><span class="code">-samefile <i>name</i></span><br>
+File refers to the same inode as name. When -L is in effect, this can include symbolic links. </p>
+<p><span class="code">-size n[cwbkMG]</span>
+File uses n units of space. The following suffixes can be used: </p>
+<blockquote>
+<p><span class="code">'b'</span>
+for 512-byte blocks (this is the default if no suffix is used)<br>
+<span class="code">'c'</span>
+for bytes<br>
+<span class="code">'w'</span>
+for two-byte words<br>
+<span class="code">'k'</span>
+for Kilobytes (units of 1024 bytes)<br>
+<span class="code">'M'</span>
+for Megabytes (units of 1048576 bytes)<br>
+<span class="code">'G'</span>
+for Gigabytes (units of 1073741824 bytes) <br>
+The size does not count indirect blocks, but it does count blocks in sparse files that are not actually allocated. Bear in mind that the '%k' and '%b' format specifiers of -printf handle sparse files differently. The 'b' suffix always denotes 512-byte blocks and never 1 Kilobyte blocks, which is different to the behaviour of -ls. </p>
+</blockquote>
+<p><span class="code">-true</span>
+Always true.</p>
+<p><span class="code">-type c</span>
+File is of type c: </p>
+<p><span class="code">b</span>
+block (buffered) special</p>
+<p><span class="code">c</span>
+character (unbuffered) special</p>
+<p><span class="code">d</span>
+directory</p>
+<p><span class="code">p</span>
+named pipe (FIFO)</p>
+<p><span class="code">f</span>
+regular file</p>
+<p><span class="code">l</span>
+symbolic link; this is never true if the -L option or the -follow option is in effect, unless the symbolic link is broken. If you want to search for symbolic links when -L is in effect, use -xtype.</p>
+<p><span class="code">s</span>
+socket</p>
+<p><span class="code">D</span>
+door (Solaris)</p>
+<p><span class="code">-uid <i>n</i></span>
+File's numeric user ID is n.</p>
+<p><span class="code">-used <i>n </i></span>
+File was last accessed n days after its status was last changed. </p>
+<p><span class="code">-user <i>uname</i></span>
+File is owned by user uname (numeric user ID allowed). </p>
+<p><span class="code">-wholename <i>pattern</i></span><br>
+File name matches shell pattern pattern. The metacharacters do not treat '/' or '.' specially; so, for example,<br>
+<span class="code"> find . -wholename './sr*sc'</span><br>
+will print an entry for a directory called './src/misc' (if one exists). To ignore a whole directory tree, use -prune rather than checking every file in the tree. For example, to skip the directory 'src/emacs' and all files and directories under it, and print the names of the other files found, do something like this: <br>
+<span class="code">find . -wholename './src/emacs' -prune -o -print</span></p>
+<p><span class="code">-xtype c</span><br>
+The same as -type unless the file is a symbolic link. For symbolic links: if the -H or -P option was specified, true if the file is a link to a file of type c; if the -L option has been given, true if c is 'l'. In other words, for symbolic links, -xtype checks the type of the file that -type does not check. </p>
+<p><span class="code">-context pattern</span><br>
+(SELinux only) Security context of the file matches glob pattern. </p>
+<p><b><a name="actions"></a>ACTIONS</b></p>
+<p>Use <a href="#operators">operators</a> to separate multiple actions. If the operator is omitted, -<b>and</b> is assumed.<br>
+The default action is to -print all files for which the expression is true.</p>
+<p><span class="code">-delete</span><br>
+Delete files; true if removal succeeded. If the removal failed, an error message is issued. Use of this action automatically turns on the '-depth' option. </p>
+<p><span class="code">-exec <i>command</i> ;</span><br>
+Execute command; true if 0 status is returned. All following arguments to <b>find</b> are taken to be arguments to the command until an argument consisting of ';' is encountered. The string '{}' is replaced by the current file name being processed everywhere it occurs in the arguments to the command, not just in arguments where it is alone, as in some versions of <b>find</b>. Both of these constructions might need to be escaped (with a '\') or quoted to protect them from expansion by the shell. See the <a href="#examples">EXAMPLES</a> section for examples of the use of the '-exec' option. The specified command is run once for each matched file. The command is executed in the starting directory. There are unavoidable security problems surrounding use of the -exec option; you should use the -execdir option instead. </p>
+<p><span class="code">-exec <i>command</i> {} +</span><br>
+This variant of the -exec option runs the specified command on the selected files, but the command line is built by appending each selected file name at the end; the total number of invocations of the command will be much less than the number of matched files. The command line is built in much the same way that xargs builds its command lines. Only one instance of '{}' is allowed within the command. The command is executed in the starting directory. </p>
+<p><span class="code">-execdir <i>command</i> ;<br>
+-execdir <i>command</i> {} +</span><br>
+Like -exec, but the specified command is run from the subdirectory containing the matched file, which is not normally the directory in which you started find. This a much more secure method for invoking commands, as it avoids race conditions during resolution of the paths to the matched files. As with the -exec option, the '+' form of -execdir will build a command line to process more than one matched file, but any given invocation of command will only list files that exist in the same subdirectory. If you use this option, you must ensure that your <b>$PATH</b> environment variable does not reference the current directory; otherwise, an attacker can run any commands they like by leaving an appropriately-named file in a directory in which you will run -execdir. </p>
+<p><span class="code">-fls <i>file</i></span><br>
+True; like -ls but write to file like -fprint. The output file is always created, even if the predicate is never matched. See the <a href="#unusual">UNUSUAL FILENAMES</a> section for information about how unusual characters in filenames are handled. </p>
+<p><span class="code">-fprint <i>file</i></span><br>
+True; print the full file name into file file. If file does not exist when find is run, it is created; if it does exist, it is truncated. The file names ''/dev/stdout'' and ''/dev/stderr'' are handled specially; they refer to the standard output and standard error output, respectively. The output file is always created, even if the predicate is never matched. See the <a href="#unusual">UNUSUAL FILENAMES</a> section for information about how unusual characters in filenames are handled. </p>
+<p><span class="code">-fprint0 <i>file</i></span><br>
+True; like -print0 but write to file like -fprint. The output file is always created, even if the predicate is never matched. See the <a href="#unusual">UNUSUAL FILENAMES</a> section for information about how unusual characters in filenames are handled. </p>
+<p><span class="code">-fprintf <i>file format</i></span><br>
+True; like -printf but write to file like -fprint. The output file is always created, even if the predicate is never matched. See the <a href="#unusual">UNUSUAL FILENAMES</a> section for information about how unusual characters in filenames are handled. </p>
+<p><span class="code">-ok <i>command</i> ;</span><br>
+Like -exec but ask the user first (on the standard input); if the response does not start with 'y' or 'Y', do not run the command, and return false. If the command is run, its standard input is redirected from <b>/dev/null</b>. </p>
+<p class="code">-print</p>
+<p><span class="code">True;</span> print the full file name on the standard output, followed by a newline. If you are piping the output of find into another program and there is the faintest possibility that the files which you are searching for might contain a newline, then you should seriously consider using the '-print0' option instead of '-print'. See the UNUSUAL FILENAMES section for information about how unusual characters in filenames are handled.</p>
+<p><span class="code">-okdir <i>command</i> ;</span><br>
+Like -execdir but ask the user first (on the standard input); if the response does not start with 'y' or 'Y', do not run the command, and return false. If the command is run, its standard input is redirected from /dev/null. </p>
+<p><span class="code">-print0</span><br>
+<span class="code">True; </span>print the full file name on the standard output, followed by a null character (instead of the newline character that '-print' uses). This allows file names that contain newlines or other types of white space to be correctly interpreted by programs that process the find output. This option corresponds to the '-0' option of xargs. </p>
+<p><span class="code">-printf <i>format</i></span><br>
+<span class="code">True; </span>print format on the standard output, interpreting '<span class="code">\</span>' escapes and '<span class="code">%</span>' directives. Field widths and precisions can be specified as with the 'printf' C function. Please note that many of the fields are printed as %s rather than %d, and this may mean that flags don't work as you might expect. This also means that the '<span class="code">-</span>' flag does work (it forces fields to be left-aligned). Unlike -print, -printf does not add a newline at the end of the string. <br>
+The escapes and directives are: <br>
+<span class="code">\a </span>Alarm bell.<br>
+<span class="code">\b </span>Backspace.<br>
+<span class="code">\c </span>Stop printing from this format immediately and flush the output.<br>
+<span class="code">\f </span>Form feed.<br>
+<span class="code">\n </span>Newline.<br>
+<span class="code">\r </span>Carriage return.<br>
+<span class="code">\t </span>Horizontal tab.<br>
+<span class="code">\v </span>Vertical tab.<br>
+<span class="code">\&nbsp;&nbsp;</span>ASCII NUL.<br>
+<span class="code">\\ </span>A literal backslash ('\').<br>
+<span class="code">\NNN </span>The character whose ASCII code is NNN (octal). <br>
+A '<span class="code">\</span>' character followed by any other character is treated as an ordinary character, so they both are printed. <br>
+<span class="code">%% </span>A literal percent sign.<br>
+<span class="code">%a </span>File's last access time in the format returned by the C 'ctime' function.<br>
+<span class="code">%A<i>k</i> </span>File's last access time in the format specified by k, which is either '@' or a directive for the C 'strftime' function. </p>
+<blockquote>
+<p>The possible values for <i>k</i> are listed below; some of them might not be available on all systems, due to differences in 'strftime' between systems. </p>
+<p>Time fields:<br>
+<span class="code">@ </span>seconds since Jan. 1, 1970, 00:00 GMT.<br>
+<span class="code">H </span>hour (00..23)<br>
+<span class="code">I </span>hour (01..12)<br>
+<span class="code">k </span>hour ( 0..23)<br>
+<span class="code">l </span>hour ( 1..12)<br>
+<span class="code">M </span>minute (00..59)<br>
+<span class="code">p</span> locale's AM or PM<br>
+<span class="code">r </span>time, 12-hour (hh:mm:ss [AP]M)<br>
+<span class="code">S </span>second (00..61)<br>
+<span class="code">T </span>time, 24-hour (hh:mm:ss)<br>
+<span class="code">+ </span>Date and time, separated by '+', for example '2004-04-28+22:22:05'. The time is given in the current timezone (which may be affected by setting the TZ environment variable). This is a GNU extension.<br>
+<span class="code">X</span> locale's time representation (H:M:S)<br>
+<span class="code">Z</span> time zone (e.g., EDT), or nothing if no time zone is determinable</p>
+<p>Date fields:<br>
+<span class="code">a </span>locale's abbreviated weekday name (Sun..Sat)<br>
+<span class="code">A </span>locale's full weekday name, variable length (Sunday..Saturday)<br>
+<span class="code">b </span>locale's abbreviated month name (Jan..Dec)<br>
+<span class="code">B </span>locale's full month name, variable length (January..December)<br>
+<span class="code">c </span>locale's date and time (Sat Nov 04 12:02:33 EST 1989)<br>
+<span class="code">d </span>day of month (01..31)<br>
+<span class="code">D </span>date (mm/dd/yy)<br>
+<span class="code">h </span>same as b<br>
+<span class="code">j </span>day of year (001..366)<br>
+<span class="code">m </span>month (01..12)<br>
+<span class="code">U </span>week number of year with Sunday as first day of week (00..53)<br>
+<span class="code">w </span>day of week (0..6)<br>
+<span class="code">W </span>week number of year with Monday as first day of week (00..53)<br>
+<span class="code">x </span>locale's date representation (mm/dd/yy)<br>
+<span class="code">y </span>last two digits of year (00..99)<br>
+<span class="code">Y </span>year (1970...)</p>
+</blockquote>
+<p><span class="code">%b </span>The amount of disk space used for this file in
+512-byte blocks. Since disk space is allocated in multiples of the filesystem block size this is usually greater than %s/1024, but it can also be smaller if the file is a sparse file. <br>
+<span class="code">%c </span>File's last status change time in the format returned by the C 'ctime' function.<br>
+<span class="code">%C<i>k</i> </span>File's last status change time in the format specified by k, which is the same as for %A.<br>
+<span class="code">%d </span>File's depth in the directory tree; 0 means the file is a command line argument.<br>
+<span class="code">%D </span>The device number on which the file exists (the st_dev field of struct stat), in decimal.<br>
+<span class="code">%f </span>File's name with any leading directories removed (only the last element).<br>
+<span class="code">%F </span>Type of the filesystem the file is on; this value can be used for -fstype.<br>
+<span class="code">%g </span>File's group name, or numeric group ID if the group has no name.<br>
+<span class="code">%G </span>File's numeric group ID.<br>
+<span class="code">%h </span>Leading directories of file's name (all but the last element). If the file name contains no slashes (since it is in the current directory) the %h specifier expands to &quot;.&quot;.<br>
+<span class="code">%H </span>Command line argument under which file was found.<br>
+<span class="code">%i </span>File's inode number (in decimal).<br>
+<span class="code">%k </span>The amount of disk space used for this file in 1K blocks. Since disk space is allocated in multiples of the filesystem block size this is usually greater than %s/1024, but it can also be smaller if the file is a sparse file.<br>
+<span class="code">%l </span>Object of symbolic link (empty string if file is not a symbolic link).<br>
+<span class="code">%m </span>File's permission bits (in octal). This option uses the 'traditional' numbers which most Unix implementations use, but if your particular implementation uses an unusual ordering of octal permissions bits, you will see a difference between the actual value of the file's mode and the output of %m. Normally you will want to have a leading zero on this number, and to do this, you should use the # flag (as in, for example, '%#m').<br>
+<span class="code">%M </span>File's permissions (in symbolic form, as for ls). This directive is supported in findutils 4.2.5 and later.<br>
+<span class="code">%n </span>Number of hard links to file.<br>
+<span class="code">%p </span>File's name.<br>
+<span class="code">%P </span>File's name with the name of the command line argument under which it was found removed.<br>
+<span class="code">%s </span>File's size in bytes.<br>
+<span class="code">%t </span>File's last modification time in the format returned by the C 'ctime' function.<br>
+<span class="code">%T<i>k</i> </span>File's last modification time in the format specified by k, which is the same as for %A.<br>
+<span class="code">%u </span>File's user name, or numeric user ID if the user has no name.<br>
+<span class="code">%U </span>File's numeric user ID.<br>
+<span class="code">%y </span>File's type (like in ls -l), U=unknown type (shouldn't happen)<br>
+<span class="code">%Y </span>File's type (like %y), plus follow symlinks: L=loop, N=nonexistent<br>
+<span class="code">%Z </span>(SELinux only) file's security context. <br>
+A '<span class="code">%</span>' character followed by any other character is discarded (but the other character is printed).</p>
+<blockquote>
+<p> The %m and %d directives support the # , 0 and + flags, but the other directives do not, even if they print numbers. Numeric directives that do not support these flags include G, U, b, D, k and n. The '-' format flag is supported and changes the alignment of a field from right-justified (which is the default) to left-justified.<br>
+See the <a href="#unusual">UNUSUAL FILENAMES</a> section for information about how unusual characters in filenames are handled. </p>
+</blockquote>
+<p><span class="code">-prune </span>If -depth is not given, true; if the file is a directory, do not descend into it.
+If <b>-depth</b> is given, false; no effect. <br>
+<span class="code">-quit </span>Exit immediately. No child processes will be left running, but no more paths specified on the command line will be processed. For example, find /tmp/foo /tmp/bar -print -quit will print only /tmp/foo. Any command lines which have been built up with -execdir ... {} + will be invoked before find exits. The exit status may or may not be zero, depending on whether an error has already occurred.<br>
+<span class="code">-ls </span>True; list current file in 'ls -dils' format on standard output. The block counts are of 1K blocks, unless the environment variable POSIXLY_CORRECT is set, in which case 512-byte blocks are used. See the <a href="#unusual">UNUSUAL FILENAMES</a> section for information about how unusual characters in filenames are handled.</p>
+<p><a name="unusual"></a><b>UNUSUAL FILENAMES</b></p>
+<p>Many of the actions of <b>find</b> result in the printing of data which is under the control of other users. This includes file names, sizes, modification times and so forth. File names are a potential problem since they can contain any character except '\0' and '/'. </p>
+<p>Unusual characters in file names can do unexpected and often undesirable things to your terminal (for example, changing the settings of your function keys on some terminals). Unusual characters are handled differently by various actions, as described below.</p>
+<p><span class="code">-print0, -fprint0</span></p>
+<blockquote>
+<p>Always print the exact filename, unchanged, even if the output is going to a terminal. </p>
+</blockquote>
+<p><span class="code">-ls, -fls </span></p>
+<blockquote>
+<p>Unusual characters are always escaped. White space, backslash, and double quote characters are printed using C-style escaping (for example '\f', '\&quot;'). Other unusual characters are printed using an octal escape. Other printable characters (for -ls and -fls these are the characters between octal 041 and 0176) are printed as-is. </p>
+</blockquote>
+<p><span class="code">-printf, -fprintf</span></p>
+<blockquote>
+<p> If the output is not going to a terminal, it is printed as-is. Otherwise, the result depends on which directive is in use. The directives %D, %F, %g, %G, %H, %Y, and %y expand to values which are not under control of files' owners, and so are printed as-is. The directives %a, %b, %c, %d, %i, %k, %m, %M, %n, %s, %t, %u and %U have values which are under the control of files' owners but which cannot be used to send arbitrary data to the terminal, and so these are printed as-is. The directives %f, %h, %l, %p and %P are quoted. This quoting is performed in the same way as for GNU ls. This is not the same quoting mechanism as the one used for -ls and -fls. If you are able to decide what format to use for the output of find then it is normally better to use '\0' as a terminator than to use newline, as file names can contain white space and newline characters. </p>
+</blockquote>
+<p><span class="code">-print, -fprint </span></p>
+<blockquote>
+<p>Quoting is handled in the same way as for -printf and -fprintf. If you are using find in a script or in a situation where the matched files might have arbitrary names, you should consider using -print0 instead of -print. </p>
+</blockquote>
+<p><br>
+The -ok and -okdir actions print the current filename as-is. This may change in a future release.</p>
+<p><a name="operators"></a><b>OPERATORS</b></p>
+<p>Listed in order of decreasing precedence:<br>
+<span class="code">( expr )</span>
+Force precedence. <br>
+<span class="code"><b>!</b> expr </span>True if expr is false.<br>
+<span class="code"><b>-not</b> expr</span>
+Same as ! expr, but not POSIX compliant. <br>
+<span class="code">expr1 expr2 </span>Two expressions in a row are taken to be joined with an implied &quot;<b>and</b>&quot;; expr2 is not evaluated if expr1 is false. <br>
+<span class="code">expr1 <b>-a</b> expr2</span>
+Same as expr1 expr2. <br>
+<span class="code">expr1 <b>-and</b> expr2 </span>Same as expr1 expr2, but not POSIX compliant. <br>
+<span class="code">expr1 <b>-o</b> expr2 </span>Or; expr2 is not evaluated if expr1 is true. <br>
+<span class="code">expr1 <b>-or</b> expr2 </span>Same as expr1 -o expr2, but not POSIX compliant. <br>
+<span class="code">expr1 <b>,</b> expr2 </span>List; both expr1 and expr2 are always evaluated. The value of expr1 is discarded; the value of the list is the value of expr2.</p>
+<p> The comma operator can be useful for searching for several different types of thing, but traversing the filesystem hierarchy only once. The -fprintf action can be used to list the various matched items into several different output files. </p>
+<p><b><a name="standards"></a>Standards Conformance</b></p>
+<p>The following options are specified in the POSIX standard (IEEE Std 1003.1, 2003 Edition):</p>
+<p><span class="code">-H </span>This option is supported.<br>
+<span class="code">-L </span>This option is supported.<br>
+<span class="code">-name </span>This option is supported, but POSIX conformance depends on the POSIX conformance of the system's fnmatch(3) library function. As of findutils-4.2.2, shell metacharacters ('*'. '?' or '[]' for example) will match a leading '.', because IEEE PASC interpretation 126 requires this. This is a change from previous versions of findutils.<br>
+<span class="code">-type</span> Supported. POSIX specifies 'b', 'c', 'd', 'l', 'p', 'f' and 's'. GNU find also supports 'D', representing a Door, where the OS provides these.<br>
+<span class="code">-ok </span>Supported. Interpretation of the response is not locale-dependent (see <a href="#variables">ENVIRONMENT VARIABLES</a>).<br>
+<span class="code">-newer </span>Supported. If the file specified is a symbolic link, it is always dereferenced. This is a change from previous behaviour, which used to take the relevant time from the symbolic link; see the HISTORY section below.</p>
+<p>Other predicates -
+the predicates '-atime', '-ctime', '-depth', '-group', '-links', '-mtime', '-nogroup', '-nouser', '-perm', '-print', '-prune', '-size', '-user' and '-xdev', are all supported.
+The POSIX standard specifies parentheses '(', ')', negation '!' and the 'and' and 'or' operators ('-a', '-o').</p>
+<p>All other options, predicates, expressions and so forth are extensions beyond the POSIX standard. Many of these extensions are not unique to GNU find, however.</p>
+<p>The POSIX standard requires that
+the find utility shall detect infinite loops; that is, entering a previously visited directory that is an ancestor of the last file encountered. When it detects an infinite loop, find shall write a diagnostic message to standard error and shall either recover its position in the hierarchy or terminate. <br>
+The link count of directories which contain entries which are hard links to an ancestor will often be lower than they otherwise should be. This can mean that GNU find will sometimes optimise away the visiting of a subdirectory which is actually a link to an ancestor. Since find does not actually enter such a subdirectory, it is allowed to avoid emitting a diagnostic message. Although this behaviour may be somewhat confusing, it is unlikely that anybody actually depends on this behaviour. If the leaf optimisation has been turned off with -noleaf, the directory entry will always be examined and the diagnostic message will be issued where it is appropriate. Symbolic links cannot be used to create filesystem cycles as such, but if the -L option or the -follow option is in use, a diagnostic message is issued when find encounters a loop of symbolic links. As with loops containing hard links, the leaf optimisation will often mean that find knows that it doesn't need to call stat() or chdir() on the symbolic link, so this diagnostic is frequently not necessary.</p>
+<p>The -d option is supported for compatibility with various BSD systems, but you should use the POSIX-compliant option -depth instead.</p>
+<p>The POSIXLY_CORRECT environment variable does not affect the behaviour of the -regex or -iregex tests because those tests aren't specified in the POSIX standard.</p>
+<p><b><a name="variables"></a>Environment Variables</b></p>
+<p><span class="code">LANG </span>Provides a default value for the internationalization variables that are unset or null.<br>
+<span class="code">LC_ALL</span> If set to a non-empty string value, override the values of all the other internationalization variables.<br>
+<span class="code">LC_COLLATE </span>The POSIX standard specifies that this variable affects the pattern matching to be used for the '-name' option. GNU find uses the fnmatch(3) library function, and so support for 'LC_COLLATE' depends on the system library. <br>
+POSIX also specifies that the 'LC_COLLATE' environment variable affects the interpretation of the user's response to the query issued by '-ok', but this is not the case for GNU find. <br>
+<span class="code">LC_CTYPE </span>This variable affects the treatment of character classes used with the '-name' test, if the system's fnmatch(3) library function supports this. It has no effect on the behaviour of the '-ok' expression. <br>
+<span class="code">LC_MESSAGES </span>Determines the locale to be used for internationalised messages. <br>
+<span class="code">NLSPATH </span>Determines the location of the internationalisation message catalogues. <br>
+<span class="code">PATH </span>Affects the directories which are searched to find the executables invoked by '-exec', '-execdir', '-ok' and '-okdir'.<br>
+<span class="code">POSIXLY_CORRECT </span>Determines the block size used by '-ls' and '-fls'. If 'POSIXLY_CORRECT' is set, blocks are units of 512 bytes. Otherwise they are units of 1024 bytes. <br>
+<span class="code">TZ </span>Affects the time zone used for some of the time-related format directives of -printf and -fprintf.</p>
+<p><b><a name="examples"></a>Examples</b></p>
+<p>List all filenames ending in .mp3, searching in the current folder and all subfolders: <br>
+<span class="code">$ find . -name &quot;*.mp3&quot; </span></p>
+<p>List all filenames ending in .mp3, searching in the music folder and subfolders: <br>
+<span class="code">$ find ./music -name &quot;*.mp3&quot; </span></p>
+<p>List files with the exact name: Sales_document.doc in ./work and subfolders: <br>
+<span class="code">$ find ./work -name Sales_document.doc </span></p>
+<p>List all files that belong to the user Maude: <br>
+<span class="code">$ find . -user Maude </span></p>
+<p>List all the directory and sub-directory names: <br>
+<span class="code">$ find . -type d </span></p>
+<p>List all files in those sub-directories (but not the directory names) <br>
+<span class="code">$ find . -type f </span></p>
+<p>List all the file links: <br>
+<span class="code">$ find . -type l </span></p>
+<p>List all files (and subdirectories) in your home directory: <br>
+<span class="code">$ find $HOME</span> </p>
+<p>Find files that are over a gigabyte in size:<br>
+<span class="code">$ find ~/Movies -size +1024M </span></p>
+<p>Find files have been modified within the last day: <br>
+<span class="code">$ find ~/Movies -mtime -1 </span></p>
+<p>Find files have been modified within the last 30 minutes: <br>
+<span class="code">$ find ~/Movies -mmin -30 </span></p>
+<p>Find .doc files that also start with 'questionnaire' (AND) <br>
+<span class="code">$
+find . -name '*.doc' -name questionnaire*</span> </p>
+<p>List all files beginning with 'memo' and owned by Maude (AND) <br>
+<span class="code">$ find . -name 'memo*' -user Maude </span></p>
+<p> Find .doc files that do NOT start with 'Accounts' (NOT)<br>
+<span class="code">$
+find . -name '*.doc' ! -name Accounts*</span></p>
+<p>Find files named 'secrets' in or below the directory /tmp and delete them. Note that this will work incorrectly if there are any filenames containing newlines, single or double quotes, or spaces:<br>
+<span class="code">$ find /tmp -name secrets -type f -print | xargs /bin/rm -f</span></p>
+<p>Find files named 'secrets' in or below the directory /tmp and delete them, processing filenames in such a way that file or directory names containing single or double quotes, spaces or newlines are correctly handled. The -name test comes before the -type test in order to avoid having to call stat(2) on every file.
+<br>
+<span class="code">$ find /tmp -name secrets -type f -print0 | xargs -0 /bin/rm -f</span>
+<p>Run 'myapp' on every file in or below the current directory. Notice that the braces are enclosed in single quote marks to protect them from interpretation as shell script punctuation. The semicolon is similarly protected by the use of a backslash, though ';' could have been used in that case also.</p>
+<p class="code">find . -type f -exec myapp '{}' \;</p>
+<p> Traverse the filesystem just once, listing setuid files and directories into /root/suid.txt and large files into /root/big.txt.</p>
+<p><span class="code">find / \( -perm -4000 -fprintf /root/suid.txt '%#m %u %p\n' \) , \<br>
+\( -size +100M -fprintf /root/big.txt '%-10s %p\n' \)</span></p>
+<p>Search for files in your home directory which have been modified in the last twenty-four hours. This command works this way because the time since each file was last modified is divided by 24 hours and any remainder is discarded. That means that to match -mtime 0, a file will have to have a modification in the past which is less than 24 hours ago.</p>
+<p class="code">find $HOME -mtime 0</p>
+<p>Search for files which have read and write permission for their owner, and group, but which other users can read but not write to (<a href="chmod.html">664</a>). Files which meet these criteria but have other permissions bits set (for example if someone can execute the file) will not be matched.</p>
+<p><span class="code">find . -perm 664</span></p>
+<p>Search for files which have read and write permission for their owner and group, and which other users can read, without regard to the presence of any extra permission bits (for example the executable bit). This will match a file which has mode 0777, for example.</p>
+<p><span class="code">find . -perm -664</span></p>
+<p>Search for files which are writable by somebody (their owner, or their group, or anybody else).</p>
+<p><span class="code">find . -perm /222</span></p>
+<p>All three of these commands do the same thing, but the first one uses the octal representation of the file mode, and the other two use the symbolic form. These commands all search for files which are writable by either their owner or their group. The files don't have to be writable by both the owner and group to be matched; either will do.</p>
+<p><span class="code">find . -perm /220<br>
+find . -perm /u+w,g+w<br>
+find . -perm /u=w,g=w</span></p>
+<p>Both these commands do the same thing; search for files which are writable by both their owner and their group.</p>
+<p><span class="code">find . -perm -220<br>
+find . -perm -g+w,u+w</span></p>
+<p>These two commands both search for files that are readable for everybody (-perm -444 or -perm -a+r), have at least on write bit set (-perm /222 or -perm /a+w) but are not executable for anybody (! -perm /111 and ! -perm /a+x respectively)</p>
+<p><span class="code">find . -perm -444 -perm /222 ! -perm /111<br>
+find . -perm -a+r -perm /a+w ! -perm /a+x</span></p>
+<p><b><a name="performance"></a>Performance</b></p>
+<p>If you need to run an action against a large quantity of files, an alternative and often much faster method is to execute the command by simply piping <span class="telety">find</span> into <a href="xargs.html">xargs</a> rather than specifying a <b>find <a href="#actions">action</a></b> against each file.<br>
+<br>
+<span class="telety">xargs</span>, will bundle up the files and (almost always) run them through a single instance of the called program<br>
+<span class="telety">find -exec</span>, will run a separate instance of the called program for each file.</p>
+<p><b><a name="exit"></a>Exit Status</b></p>
+<p>find exits with status 0 if all files are processed successfully, greater than 0 if errors occur. This is deliberately a very broad description, but if the return value is non-zero, you should not rely on the correctness of the results of find.<br>
+</p>
+<p>As of findutils-4.2.2, shell metacharacters ('*'. '?' or '[]' for example) used in filename patterns will match a leading '.', because IEEE POSIX interpretation 126 requires this.</p>
+<p><b><a name="nonbugs"></a>Non-bugs</b></p>
+<p class="code">$ find . -name *.c -print<br>
+find: paths must precede expression<br>
+Usage: find [-H] [-L] [-P] [path...] [expression]</p>
+<p>This happens because *.c has been expanded by the shell resulting in find actually receiving a command line like this:</p>
+<p><span class="code">find . -name bigram.c code.c frcode.c locate.c -print</span></p>
+<p>That command is of course not going to work. Instead of doing things this way, you should enclose the pattern in quotes:</p>
+<p class="code">$ find . -name &acute;*.c&acute; -print</p>
+<p><b><a name="bugs"></a>Bugs</b></p>
+<p>The test -perm /000 currently matches no files, but for greater consistency with -perm -000, this will be changed to match all files; this change will probably be made in early 2006. Meanwhile, a warning message is given if you do this.</p>
+<p>There are security problems inherent in the behaviour that the POSIX standard specifies for find, which therefore cannot be fixed. For example, the -exec action is inherently insecure, and -execdir should be used instead. Please see Finding Files for more information.</p>
+<p>The best way to report a bug is to use the form at http://savannah.gnu.org/bugs/?group=findutils. The reason for this is that you will then be able to track progress in fixing the problem. Other comments about find(1) and about the findutils package in general can be sent to the bug-findutils mailing list. To join the list, send email to bug-findutils-request@gnu.org. </p>
+<p>This page documents the GNU version of find. If you are using find in an environment where security is important (for example if you are using it to seach directories that are writable by other users), you should read the &quot;Security Considerations&quot; chapter of the findutils documentation, which is called Finding Files and comes with findutils. </p>
+<p><i>"Instead of getting married again, I'm going to <b>find</b> a woman I don't like and just give her a house." - Lewis Grizzard </i><br>
+ <br>
+<b> Related</b>:</p>
+<p><a href="awk.html">awk</a> - Find and Replace text within file(s)<br>
+<a href="chmod.html">chmod</a> - Change access permissions<br>
+fnmatch - Filename match <br>
+findutils documentation - 'Finding Files' doc with more detail on security considerations<br>
+<a href="grep.html">grep</a> - Search file(s) for lines that match a given pattern<br>
+<a href="history.html">history</a> - Command History<br>
+<a href="locate.html">locate</a> - Find files - simple but fast <br>
+<a href="ls.html">ls</a> - List information about file(s)<br>
+<a href="printf.html">printf</a> - Format and print data<br>
+<a href="xargs.html">xargs</a> - <span class="body">Execute utility, passing constructed argument list(s)</span><br>
+regex(7), stat(2), lstat(2), strftime(3), ctime(3)<br>
+
+Equivalent Windows command: <a href="../term_tools/nt/forfiles.html">FORFILES</a> - Batch process multiple files</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/fmt.html b/help/en/bash/fmt.html
new file mode 100644
index 0000000..ac69ca9
--- /dev/null
+++ b/help/en/bash/fmt.html
@@ -0,0 +1,118 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>fmt MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> fmt</h1>
+<p>Reformat paragraph text, fill and join lines to produce output
+ lines of a given width (75 characters by default).<br>
+</p>
+<pre>SYNTAX
+ fmt [<i>option(s)</i>]... [<i>file</i>]...
+
+OPTIONS
+
+-c
+--crown-margin
+ "Crown margin" mode: preserve the indentation of the first two
+ lines within a paragraph, and align the left margin of each
+ subsequent line with that of the second line.
+
+-t
+--tagged-paragraph
+ "Tagged paragraph" mode: like crown margin mode, except that if
+ indentation of the first line of a paragraph is the same as the
+ indentation of the second, the first line is treated as a one-line
+ paragraph.
+
+-s
+--split-only
+ Split lines only. Do not join short lines to form longer ones.
+ This prevents sample lines of code, and other such "formatted"
+ text from being unduly combined.
+
+-u
+--uniform-spacing
+ Uniform spacing. Reduce spacing between words to one space, and
+ spacing between sentences to two spaces.
+
+-<i>WIDTH</i>
+-w <i>WIDTH</i>
+--width=<i>WIDTH</i>
+ Fill output lines up to WIDTH characters (default 75). `fmt'
+ initially tries to make lines about 7% shorter than this, to give
+ it room to balance line lengths.
+
+-p <i>PREFIX</i>
+--prefix=<i>PREFIX</i>
+ Only lines beginning with PREFIX (possibly preceded by whitespace)
+ are subject to formatting. The prefix and any preceding whitespace
+ are stripped for the formatting and then re-attached to each
+ formatted output line. One use is to format certain kinds of
+ program comments, while leaving the code unchanged.</pre>
+<p><b>Notes<br>
+ </b>`fmt' reads from the specified FILE arguments (or standard input if none
+ are given), and writes to standard output.</p>
+<p>The fmt utility is meant to format mail messages prior to sending,
+ but may also be useful for other simple tasks. </p>
+<p>By default, blank lines, spaces between words, and indentation
+ are preserved in the output; successive input lines with different indentation
+ are not joined; tabs are expanded on input and introduced on output. </p>
+<p>`fmt' prefers breaking lines at the end of a sentence, and tries
+ to avoid line breaks after the first word of a sentence or before the last word
+ of a sentence. A "sentence break" is defined as either the end of a paragraph
+ or a word ending in any of `.?!', followed by two spaces or end of line, ignoring
+ any intervening parentheses or quotes.</p>
+<p><i>"Everything flows and nothing abides; everything gives way
+ and nothing stays fixed&quot; - Heraclitus
+ </i><br>
+ <br>
+ <b> Related</b>:<br>
+ <br>
+ mail(1), nroff(1)<br>
+ <a href="csplit.html">csplit</a> - Split a file into context-determined pieces<br>
+ <a href="cut.html">cut</a> - Divide a file into several parts<br>
+ <a href="fold.html">fold</a> - Wrap input lines to fit in specified width<br>
+ <a href="join.html">join</a> - Join lines on a common field <br>
+ <a href="paste.html">paste</a> - Merge lines of files<br>
+ <a href="split.html">split</a> - Split a file into fixed-size pieces<br>
+ <a href="tr.html">tr</a> - Translate, squeeze, and/or delete characters <br>
+<a href="tail.html">tail</a> - Output the last part of files </p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/fold.html b/help/en/bash/fold.html
new file mode 100644
index 0000000..e222a57
--- /dev/null
+++ b/help/en/bash/fold.html
@@ -0,0 +1,89 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>fold MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> fold</h1>
+<p>Wrap input lines to fit in specified width, writes each FILE (`-'
+ means standard input), or standard input if none are given, to standard output,
+breaking long lines.</p>
+<pre>Syntax
+ fold [<em>options</em>]... [FILE]...
+</pre>
+<p> By default, `fold' breaks lines wider than 80 columns. The output
+ is split into as many lines as necessary.<br>
+ <br>
+ `fold' counts screen columns by default; thus, a tab may count more
+ than one column, backspace decreases the column count, and carriage
+return sets the column to zero.</p>
+<pre>Options
+
+ -b
+ --bytes
+ Count bytes rather than columns, so that tabs, backspaces, and
+ carriage returns are each counted as taking up one column, just
+ like other characters.
+
+ -s
+ --spaces
+ Break at word boundaries: the line is broken after the last blank
+ before the maximum line length. If the line contains no such
+ blanks, the line is broken at the maximum line length as usual.
+
+ -w <i>WIDTH</i>
+ --width=<i>WIDTH</i>
+ Use a maximum line length of <i>WIDTH</i> columns instead of 80.</pre>
+<p><i>"The general attitude seems to be that people should wear square
+ shoes, because squares are easier to design and manufacture than foot shaped
+ shoes. If the shoe industry has gone the way of the computer industry it would
+ now be running a $200-a-day course on how to walk, run and jump in square shoes."
+ - Alan
+ Kay</i></p>
+<p><b>Related</b>:<br>
+ <br>
+ <a href="csplit.html">csplit</a> - Split a file into context-determined pieces<br>
+ <a href="cut.html">cut</a> - Divide a file into several parts<br>
+ <a href="expand.html">expand</a> - Convert tabs to spaces <br>
+ <a href="fmt.html">fmt</a> - Reformat paragraph text<br>
+ <a href="head.html">head</a> - Output the first part of file(s) <br>
+ <a href="paste.html">paste</a> - Merge lines of files<br>
+ <a href="split.html">split</a> - Split a file into fixed-size pieces<br>
+<a href="tail.html">tail</a> - Output the last part of files</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/for.html b/help/en/bash/for.html
new file mode 100644
index 0000000..68ea87c
--- /dev/null
+++ b/help/en/bash/for.html
@@ -0,0 +1,99 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>for MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> for</h1>
+<p>Expand <var>words</var>, and execute <var>commands</var> once
+ for each member in the resultant list, with <var>name</var> bound to the current
+member.</p>
+<pre>Syntax
+ for <var>name</var> [in <var>words</var> ...]; do <var>commands</var>; done
+
+ for (( <var>expr1</var> ; <var>expr2</var> ; <var>expr3</var> )) ; do <var>commands</var> ; done</pre>
+<span class="body">If <samp>`in <var>words</var>'</samp> is not present, the <code>for</code>
+command executes the <var>commands</var> once for each positional parameter that
+is set, as if <samp>`in "$@"'</samp> had been specified (see Positional Parameters below.) <br>
+</span>
+<p>The second form of the <span class="body"><span class="telety">for</span></span> command is evaluated thus: </p>
+<blockquote>
+<p>First, the arithmetic expression <var>expr1</var> is evaluated
+ according to <a href="../term_tools/bash/syntax-math.html">shell arithmetic expression rules</a>. The arithmetic expression <var>expr2</var>
+ is then evaluated repeatedly until it evaluates to zero. <br>
+ <br>
+ Each time <var>expr2</var> evaluates to a non-zero value, <var>commands</var>
+ are executed and the arithmetic expression <var>expr3</var> is evaluated. If any
+expression is omitted, it behaves as if it evaluates to 1. </p>
+</blockquote>
+<p> <b>Return Status</b> <br>
+The Return Status of <span class="telety">for</span> will be the exit status of the last command that executes, (if there are multiple expressions then the last command in <var>list</var> .) <br>
+If there are no items in the expansion of <var>words</var>, no commands are executed, and the return status is zero. The return status is false if any of the expressions is invalid. </p>
+<p><strong>Positional Parameters</strong><br>
+These are assigned from the shell's arguments when the shell is invoked, they can be reassigned using the <a href="../term_tools/osx/set.html">set </a>builtin command.<br>
+Positional parameter N may be referenced as ${N}, or as $N when N consists of a single digit. $1, $2 etc </p>
+<p><strong>Examples</strong></p>
+<pre># Loop through a set of strings:
+for m in Apple Sony Panasonic &quot;Hewlett Packard&quot; Nokia<br>do<br> echo &quot;Manufacturer is:&quot; $m<br>done
+
+# or as a single line...
+for <strong>m</strong> in Apple Sony Panasonic &quot;Hewlett Packard&quot; Nokia; do echo &quot;Manufacturer is:&quot; $<strong>m</strong>;done
+
+
+# Loop 100 times:
+for i in $(seq 1 100); do echo -n &quot;Hello World${i} &quot;; done
+
+
+# Loop through the arguments passed to a function:
+foo ()<br>{<br> for ARG in &quot;$@&quot;;do echo $ARG; done<br>}
+# try it<br>foo abc 123 &quot;Hello World&quot; 'bash rules'</pre>
+<p><i>&quot;In expanding the field of knowledge, we but increase the horizon of ignorance&quot; - Henry Miller </i>
+</p>
+<p><b>Related</b>:<br>
+ <a href="case.html"><br>
+ case</a> - Conditionally perform a command<br>
+ <a href="eval.html">eval</a> - Evaluate several commands/arguments<br>
+ <var> </var> <a href="if.html">if</a> - Conditionally perform a command<br>
+ <a href="awk.html">gawk</a> - Find and Replace text within file(s)<br>
+ <a href="../term_tools/bash/m4.html">m4</a> - Macro processor<br>
+ <a href="until.html">until</a> - Execute commands (until error) <br>
+ <a href="while.html">while</a> - Execute commands<br>
+Equivalent Windows commands:
+ <a href="../term_tools/nt/for.html">FOR</a> - Conditionally perform a command several times </p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/fsck.html b/help/en/bash/fsck.html
new file mode 100644
index 0000000..efc2934
--- /dev/null
+++ b/help/en/bash/fsck.html
@@ -0,0 +1,94 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>fsck MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> fsck</h1>
+<p>Filesystem consistency check and interactive repair. Journaling file systems avoid the need to run fsck.</p>
+<pre>Syntax
+ fsck [<em>options</em>] [<em>filesystem</em>] ...
+
+Options
+ -- Pass all subsequent options to filesystem-specific checker.
+ All options that fsck doesn't recognize will also be passed.
+
+ -r Interactive mode; prompt before making any repairs.
+
+ -s Serial mode.
+
+ -t <i>fstype
+</i> Specify the filesystem type. Do not check filesystems of any other type.
+
+ -A Check all filesystems listed in /etc/fstab.
+
+ -N Suppress normal execution; just display what would be done.
+
+ -R Meaningful only with -A: check all filesystems listed in /etc/fstab except the root filesystem.
+
+ -T Suppress printing of title.
+
+ -V Verbose mode.
+
+EXIT CODES
+
+ 1 Errors were found and corrected.
+ 2 Reboot suggested.
+ 4 Errors were found but not corrected.
+ 8 fsck encountered an operational error.
+ 16 fsck was called incorrectly.
+ 128 A shared library error was detected.</pre>
+<p><span class="body">The return status is the exit status of the last command
+ executed in <var>consequent-commands</var>, or zero if none were executed. </span></p>
+<p><i>"Politics is the art of looking for trouble, finding it, misdiagnosing it,
+ and then misapplying the wrong remedies." - Groucho
+ Marx</i> </p>
+<p><b>Related b<b><b><b><b><b>ash </b></b></b></b></b>commands</b>:<a href="for.html"><br>
+ </a><br>
+ reboot - Reboot the machine<br>
+
+ <a href="http://e2fsprogs.sourceforge.net/ext2.html">ext2</a> File System (non journaling)<br>
+ <a href="http://www.redhat.com/support/wpapers/redhat/ext3/index.html">ext3
+ File System</a> - Red Hat Journaling File System<br>
+<a href="ddrescue.html">ddrescue</a> - Data recovery tool<br>
+ <a href="http://oss.sgi.com/projects/xfs/">XFS File System</a> - journaling filesystem, SuSE, Mandrake, Gentoo.<br>
+Equivalent Windows command:
+ <a href="../term_tools/nt/chkdsk.html">CHKDSK</a> - Check Disk - check and repair disk
+problems</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/function.html b/help/en/bash/function.html
new file mode 100644
index 0000000..69e320b
--- /dev/null
+++ b/help/en/bash/function.html
@@ -0,0 +1,91 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>function MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> function</h1>
+<p>Shell functions are a way to group commands for later execution using a single
+ name for the group. They are executed just like a "regular" command. When the
+ name of a shell function is used as a simple command name, the list of commands
+ associated with that function name is executed. Shell functions are executed
+ in the current shell context; no new process is created to interpret them. </p>
+<p>Functions are declared using this syntax:
+<pre>[ <code>function</code> ] <var>name</var> () { <var>command-list</var>; }</pre>
+<p>This defines a shell function named <var>name</var>. The reserved word <code>function</code>
+ is optional. If the <code>function</code> reserved word is supplied, the parentheses
+ are optional. The <var>body</var> of the function is the <var>command-list</var>
+ between { and }. This list is executed whenever <var>name</var> is specified
+ as the name of a command. The exit status of a function is the exit status of
+ the last command executed in the body. </p>
+<p>Note that for historical reasons, the curly braces that surround the body of
+ the function must be separated from the body by <code>blank</code>s or newlines.
+ This is because the braces are reserved words and are only recognized as such
+ when they are separated by whitespace. Also, the <var>command-list</var> must
+ be terminated with a semicolon or a newline. </p>
+<p>When a function is executed, the arguments to the function become the positional
+ parameters during its execution.<br>
+ The special parameter <samp>`#'</samp> that expands to the number of positional
+ parameters is updated to reflect the change. <br>
+ Positional parameter <code>0</code> is unchanged. <br>
+ The <code>FUNCNAME</code> variable is set to the name of the function while
+ the function is executing. </p>
+<p>If the builtin command <code>return</code> is executed in a function, the function
+ completes and execution resumes with the next command after the function call.
+ When a function completes, the values of the positional parameters and the special
+ parameter <samp>`#'</samp> are restored to the values they had prior to the
+ function's execution. If a numeric argument is given to <code>return</code>,
+ that is the function's return status; otherwise the functions's return status
+ is the exit status of the last command executed before the <code>return</code>.
+</p>
+<p>Variables local to the function may be declared with the <code>local</code>
+ builtin. These variables are visible only to the function and the commands it
+ invokes. </p>
+<p>Functions may be recursive. No limit is placed on the number of recursive calls.</p>
+<p><b>Related</b>:<br>
+ <br>
+ <a href="expr.html">expr</a> - Evaluate expressions<br>
+ <a href="eval.html">eval</a> - Evaluate several commands/arguments<br>
+ <a href="for.html">for</a> - Expand <var>words</var>, and execute <var>commands</var>
+ <br>
+ <a href="awk.html">gawk</a> - Find and Replace text within file(s) <br>
+ <a href="set.html">set</a> - Manipulate shell variables and functions <br>
+Equivalent Windows command: <a href="../term_tools/nt/doskey.html">DOSKEY</a> - Edit command line, recall commands,
+and create macros</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/fuser.html b/help/en/bash/fuser.html
new file mode 100644
index 0000000..6737cf9
--- /dev/null
+++ b/help/en/bash/fuser.html
@@ -0,0 +1,146 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>fuser MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> fuser </h1>
+<p>Identify processes using files or sockets, optionally: Kill the process that is accessing the file.</p>
+<pre>Syntax
+ fuser [-a|-s|-c] [-4|-6] [-n <i>space</i> ] [-k [-i] [-<i>signal</i> ] ] [-muvf] <i>name</i>
+
+ fuser -l
+
+ fuser -V
+
+Options:
+
+ -a Show all files specified on the command line.
+ By default, only files that are accessed by at least one process are shown.
+
+ -c Same as -m option, used for POSIX compatibility.
+
+ -f Silently ignored, used for POSIX compatibility.
+
+ -k Kill processes accessing the file.
+ Unless changed with -signal, SIGKILL is sent.
+ An fuser process never kills itself, but may kill other fuser processes.
+ The effective user ID of the process executing fuser is set to its real
+ user ID before attempting to kill.
+
+ -i Ask the user for confirmation before killing a process.
+ This option is silently ignored if -k (kill) is not present too.
+
+ -l List all known signal names.
+
+ -m <i>name</i> Specifies a file on a mounted file system or a block device that is mounted.
+ All processes accessing files on that file system are listed.
+ If a directory file is specified, it is automatically changed to name/.
+ to use any file system that might be mounted on that directory.
+
+ -n <i>space</i> Select a different name space.
+ The name spaces file (file names, the default), udp (local UDP ports),
+ and tcp (local TCP ports) are supported. For ports, either the port number or
+ the symbolic name can be specified.
+ If there is no ambiguity, the shortcut notation name/Ispace (e.g. 80/tcp ) can be used.
+
+ -s Silent operation. -u and -v are ignored in this mode.
+ -a must not be used with -s.
+
+ -signal Use the specified signal instead of SIGKILL when killing processes.
+ Signals can be specified either by name (e.g. -HUP) or by number (e.g. -1).
+ This option is silently ignored if the -k (kill)option is not used.
+
+ -u Append the user name of the process owner to each PID.
+
+ -v Verbose mode. Processes are shown in a ps-like style.
+ The fields PID, USER and COMMAND are similar to ps.
+ ACCESS shows how the process accesses the file. If the access is by the kernel
+ (e.g. in the case of a mount point, a swap file, etc.), kernel is shown instead of the PID.
+
+ -V Display version information.
+
+ -4 Search only for IPv4 sockets.
+ This option must not be used with the -6 option and only has an effect with the tcp and udp namespaces.
+
+ -6 Search only for IPv6 sockets.
+ This option must not be used with the -4 option and only has an effect with the tcp and udp namespaces.
+
+ - Reset all options and set the signal back to SIGKILL. </pre>
+<p>fuser returns a non-zero return code if none of the specified files is accessed or in case of a fatal error. If at least one access has been found, fuser returns zero.</p>
+<p>In order to look up processes using TCP and UDP sockets, the corresponding name space has to be selected with the -n option. By default fuser will look in both IPv6 and IPv4 sockets. To change the default, behavior, use the -4 and -6 options. The socket(s) can be specified by the local and remote port, and the remote address. All fields are optional, but commas in front of missing fields must be present:</p>
+<p class="code">[lcl_port][,[rmt_host][,[rmt_port]]]</p>
+<p>Either symbolic or numeric values can be used for IP addresses and port numbers.</p>
+<p>fuser outputs only the PIDs to stdout, everything else is sent to stderr. </p>
+<p>fuser displays the PIDs of processes using the specified files or file systems. In the default display mode, each file name is followed by a letter denoting the type of access:</p>
+<pre> c current directory.</pre>
+<pre> e executable being run.</pre>
+<pre> f open file. f is omitted in default display mode.</pre>
+<pre> F open file for writing. F is omitted in default display mode.</pre>
+<pre> r root directory.</pre>
+<pre> m mmap'ed file or shared library. </pre>
+<p><b>Examples</b></p>
+<p><span class="code">fuser -km /home</span> kill all processes accessing the file system /home in any way.</p>
+<p><span class="code">if fuser -s /dev/ttyS1; then :; else something; fi </span>invoke something if no other process is using /dev/ttyS1.</p>
+<p><span class="code">fuser telnet/tcp</span> shows all processes at the (local) TELNET port.</p>
+<p><b>Restrictions</b></p>
+<p>Processes accessing the same file or file system several times in the same way are only shown once.</p>
+<p>If the same object is specified several times on the command line, some of those entries may be ignored.</p>
+<p>fuser may only be able to gather partial information unless run with privileges. As a consequence, files opened by processes belonging to other users may not be listed and executables may be classified as mapped only.</p>
+<p>Installing fuser SUID root will avoid problems associated with partial information, but may be undesirable for security and privacy reasons.</p>
+<p>udp and tcp name spaces, and UNIX domain sockets can't be searched with kernels older than 1.3.78.</p>
+<p>udp and tcp currently work with IPv6 and IPv4, but the address fields can only be IPv4 addresses.</p>
+<p>Accesses by the kernel are only shown with the <span class="code">-v</span> option.</p>
+<p>The<span class="code"> -k</span> option only works on processes. If the user is the kernel, fuser will print an advice, but take no action beyond that.</p>
+<p><b>Files</b></p>
+<p>/proc</p>
+<p>location of the proc file system</p>
+<p><b>Bugs</b></p>
+<p><span class="code">fuser -m /dev/sgX</span> will show (or kill with the -k flag) all processes, even if you don't have that device configured. There may be other devices it does this for too.</p>
+<p>fuser cannot report on any processes that it doesn't have permission to look at the file descriptor table for. The most common time this problem occurs is when looking for TCP or UDP sockets when running fuser as a non-root user. In this case fuser will report no access.</p>
+<p><i>"A bank is a place where they lend you an umbrella in fair weather and ask for it back when it begins to rain&quot; - Robert Frost</i></p>
+<p><b>Related</b>:<br>
+<br>
+<a href="ps.html">ps</a> - List running processes (returns PID)<br>
+<a href="kill.html">kill</a> - Stop a process from running<br>
+killall - Kill processes by name<br>
+<a href="lsof.html">lsof</a> - List open files<br>
+top - display Linux tasks <br>
+Equivalent Windows command: OPENFILES - List or disconnect open files</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/getopts.html b/help/en/bash/getopts.html
new file mode 100644
index 0000000..f87e2b6
--- /dev/null
+++ b/help/en/bash/getopts.html
@@ -0,0 +1,89 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>getopts MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> getopts</h1>
+<span class="body">getopts is used by shell scripts to parse positional parameters.</span><br>
+<pre>Syntax
+ getopts <em>optstring</em> <em>name</em> [<em>args</em>]
+
+Options
+ optstring : The option characters to be recognized
+
+ If a character is followed by a colon, the option is expected to
+ have an argument, which should be separated from it by white space.
+ The colon (`:') and question mark (`?') may not be used as option characters.</pre>
+<p>Each time it is invoked, getopts places the next option in the shell variable
+ name, initializing name if it does not exist, and the index of the next argument
+ to be processed into the variable OPTIND. OPTIND is initialized to 1 each time
+ the shell or a shell script is invoked. </p>
+<p>When an option requires an argument, getopts places that argument into the
+ variable OPTARG. The shell does not reset OPTIND automatically; it must be manually
+ reset between multiple calls to getopts within the same shell invocation if
+ a new set of parameters is to be used. </p>
+<p>When the end of options is encountered, getopts exits with a return value greater
+ than zero. </p>
+<p>OPTIND is set to the index of the first non-option argument, and name is set
+ to `?'. getopts normally parses the positional parameters, but if more arguments
+ are given in args, getopts parses those instead. </p>
+<p>getopts can report errors in two ways. If the first character of optstring
+ is a colon, silent error reporting is used. In normal operation diagnostic messages
+ are printed when invalid options or missing option arguments are encountered.
+ <br>
+ <br>
+ If the variable OPTERR is set to 0, no error messages will be displayed, even
+ if the first character of optstring is not a colon. <br>
+ If an invalid option is seen, getopts places `?' into name and, if not silent,
+ prints an error message and unsets OPTARG. <br>
+ If getopts is silent, the option character found is placed in OPTARG and no
+ diagnostic message is printed. If a required argument is not found, and getopts
+ is not silent, a question mark (`?') is placed in name, OPTARG is unset, and
+ a diagnostic message is printed. <br>
+ If getopts is silent, then a colon (`:') is placed in name and OPTARG is set
+ to the option character found. </p>
+<p>This is a BOURNE shell command</p>
+<p><b>Related</b>:<br>
+ <br>
+ <a href="export.html">export</a> - Set an environment variable<br>
+ <a href="shift.html">shift</a> - Shift positional parameters <br>
+Equivalent Windows commands:
+<a href="for.html">FOR</a> - Conditionally perform a command several times</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/grep.html b/help/en/bash/grep.html
new file mode 100644
index 0000000..22785fa
--- /dev/null
+++ b/help/en/bash/grep.html
@@ -0,0 +1,301 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>grep MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> grep</h1>
+<p>Search file(s) for specific text. </p>
+<pre>SYNTAX
+ grep &lt;<em>options</em>&gt; &quot;<em>Search String</em>&quot; [<em>filename</em>]
+
+ grep &lt;<em>options</em>&gt; [-e <em>pattern</em>] [<em>file</em>...]
+
+ grep &lt;<em>options</em>&gt; [-f <em>file</em>] [<em>file</em>...]
+
+A simple example:
+$grep "Needle in a Haystack" /etc/*
+
+OPTIONS
+
+-A <em>NUM</em>
+--after-context=<em>NUM</em>
+ (GNU Extension)
+ Print <em>NUM</em> lines of trailing context after matching lines.
+
+-a
+--text
+ (GNU Extension)
+ Do not suppress output lines that contain binary data. Normally,
+ if the first few bytes of a file indicate that the file contains
+ binary data, grep outputs only a message saying that the file
+ matches the pattern. This option causes grep to act as if the
+ file is a text file, even if it would otherwise be treated as
+ binary. _Warning:_ the result might be binary garbage printed to
+ the terminal, which can have nasty side-effects if the terminal
+ driver interprets some of it as commands.
+
+-B <em>NUM</em>
+--before-context=<em>NUM</em>
+ (GNU Extension)
+ Print NUM lines of leading context before matching lines.
+
+-b
+--byte-offset
+ (GNU Extension)
+ Print the byte offset within the input file before each line of
+ output. When `grep' runs on MS-DOS or MS-Windows, the printed
+ byte offsets depend on whether the `-u' (`--unix-byte-offsets')
+ option is used; see below.
+
+-C <em>NUM</em>
+--context=[<em>NUM</em>]
+ (GNU Extension)
+ Print NUM lines (default 2) of output context.
+
+-c
+--count
+ Suppress normal output; instead print a count of matching lines
+ for each input file. With the `-v', `--invert-match' option,
+ count non-matching lines.
+
+-d <em>ACTION</em>
+--directories=<em>ACTION</em>
+ (GNU Extension)
+ If an input file is a directory, use ACTION to process it. By
+ default, ACTION is `read', which means that directories are read
+ just as if they were ordinary files (some operating systems and
+ filesystems disallow this, and will cause `grep' to print error
+ messages for every directory). If ACTION is `skip', directories
+ are silently skipped. If ACTION is `recurse', `grep' reads all
+ files under each directory, recursively; this is equivalent to the
+ `-r' option.
+
+-e <em>PATTERN</em>
+--regexp=<em>PATTERN</em>
+ Use <em>PATTERN</em> as the <a href="../term_tools/bash/grep2.html">pattern</a>; useful to protect patterns beginning
+ with a -
+
+-f <em>FILE</em>
+--file=<em>FILE</em>
+ Obtain <a href="../term_tools/bash/grep2.html">patterns</a> from <em>FILE</em>, one per line. The empty file contains
+ zero patterns, and therefore matches nothing.
+
+-H
+--with-filename
+ (GNU Extension)
+ Print the filename for each match.
+
+-h
+--no-filename
+ (GNU Extension)
+ Suppress the prefixing of filenames on output when multiple files
+ are searched.
+
+--help
+ (GNU Extension)
+ Print a usage message briefly summarizing these command-line
+ options and the bug-reporting address, then exit.
+
+-i
+--ignore-case
+ Ignore case distinctions in both the pattern and the input files.
+
+-L
+--files-without-match
+ (GNU Extension)
+ Suppress normal output; instead print the name of each input file
+ from which no output would normally have been printed. The
+ scanning of every file will stop on the first match.
+
+-l
+--files-with-matches
+ Suppress normal output; instead print the name of each input file
+ from which output would normally have been printed. The scanning
+ of every file will stop on the first match.
+
+--mmap
+ (GNU Extension)
+ If possible, ue the `mmap' system call to read input, instead of
+ the default `read' system call. In some situations, `--mmap'
+ yields better performance. However, `--mmap' can cause undefined
+ behavior (including core dumps) if an input file shrinks while
+ `grep' is operating, or if an I/O error occurs.
+
+-n
+--line-number
+ Prefix each line of output with the line number within its input
+ file.
+
+-<em>NUM</em>
+ (GNU Extension)
+ Same as `--context=<em>NUM</em>' lines of leading and trailing context.
+ However, grep will never print any given line more than once.
+
+-q
+--quiet
+--silent
+ Quiet; suppress normal output. The scanning of every file will
+ stop on the first match. Also see the `-s' or `--no-messages'
+ option.
+
+-r
+--recursive
+ (GNU Extension)
+ For each directory mentioned in the command line, read and process
+ all files in that directory, recursively. This is the same as the
+ `-d recurse' option.
+
+-s
+--no-messages
+ Suppress error messages about nonexistent or unreadable files.
+ Portability note: unlike GNU `grep', traditional `grep' did not
+ conform to POSIX.2, because traditional `grep' lacked a `-q'
+ option and its `-s' option behaved like GNU `grep''s `-q' option.
+ Shell scripts intended to be portable to traditional `grep' should
+ avoid both `-q' and `-s' and should redirect output to `/dev/null'
+ instead.
+
+-U
+--binary
+ (GNU Extension)
+ Treat the file(s) as binary. By default, under MS-DOS and
+ MS-Windows, `grep' guesses the file type by looking at the
+ contents of the first 32kB read from the file. If `grep' decides
+ the file is a text file, it strips the `CR' characters from the
+ original file contents (to make regular expressions with `^' and
+ `$' work correctly). Specifying `-U' overrules this guesswork,
+ causing all files to be read and passed to the matching mechanism
+ verbatim; if the file is a text file with `CR/LF' pairs at the end
+ of each line, this will cause some regular expressions to fail.
+ This option has no effect on platforms other than MS-DOS and
+ MS-Windows.
+
+-u
+--unix-byte-offsets
+ (GNU Extension)
+ Report Unix-style byte offsets. This switch causes `grep' to
+ report byte offsets as if the file were Unix style text file,
+ i.e., the byte offsets ignore the `CR' characters which were
+ stripped. This will produce results identical to running `grep' on
+ a Unix machine. This option has no effect unless `-b' option is
+ also used; it has no effect on platforms other than MS-DOS and
+ MS-Windows.
+
+-v
+--invert-match
+ Invert the sense of matching, to select non-matching lines.
+
+-V
+--version
+ (GNU Extension)
+ Print the version number of `grep' to the standard output stream.
+ This version number should be included in all bug reports.
+
+-w
+--word-regexp
+ (GNU Extension)
+ Select only those lines containing matches that form whole words.
+ The test is that the matching substring must either be at the
+ beginning of the line, or preceded by a non-word constituent
+ character. Similarly, it must be either at the end of the line or
+ followed by a non-word constituent character. Word-constituent
+ characters are letters, digits, and the underscore.
+
+-x
+--line-regexp
+ Select only those matches that exactly match the whole line.
+
+-Z
+--null
+ (GNU Extension)
+ Output a zero byte (the ASCII `NUL' character) instead of the
+ character that normally follows a file name. For example, `grep
+ -lZ' outputs a zero byte after each file name instead of the usual
+ newline. This option makes the output unambiguous, even in the
+ presence of file names containing unusual characters like
+ newlines. This option can be used with commands like `find
+ -print0', `perl -0', `sort -z', and `xargs -0' to process
+ arbitrary file names, even those that contain newline characters.
+
+-z
+--null-data
+ (GNU Extension)
+ Treat the input as a set of lines, each terminated by a zero byte
+ (the ASCII `NUL' character) instead of a newline. Like the `-Z'
+ or `--null' option, this option can be used with commands like
+ `sort -z' to process arbitrary file names.
+
+<b>Environment variables</b>
+
+Grep's behavior can be affected by setting the following environment variables
+
+GREP_OPTIONS - default options
+LANG - language for messages
+POSIXLY_CORRECT - Posix behaviour
+_N_GNU_nonoption_argv_flags_ - ignore an operand
+
+see `info' for more on these
+</pre>
+<p><span class="body">Grep stands for: Global Regular Expression Print.</span></p>
+<p> <b>Diagnostics</b><br>
+ <br>
+ Normally, exit status is 0 if matches were found, and 1 if no matches
+ were found (the `-v' option inverts the sense of the exit status).<br> Exit status is 2 if there were syntax errors in the pattern,
+inaccessible input files, or other system errors.</p>
+<p><b>Examples</b></p>
+<p>Search the file example.txt, including binary data (-a) for the string 'hunting the snark':</p>
+<p>$ <span class="code">sudo grep -a 'hunting the snark' example.txt</span></p>
+<p>Search the whole partition (/sda1), including binary data(-a) for the string 'hunting the snark' return all the lines starting 25 <b>B</b>efore the text found and 50 lines <b>A</b>fter the matching text found, this can be a way to discover fragments of deleted files but is very slow:</p>
+<p>$ <span class="code">grep -a -B 25 -A 50 'hunting the snark' /dev/sda1</span> &gt; results.txt</p>
+<p><i>&quot;I understand that change is frightening for people, especially
+ if there's nothing to go to. It's best to stay where you are. I understand that.&quot; - <a href="http://www.bbc.co.uk/politics97/diana/panorama.html">Princess
+ Diana</a> </i><br>
+ <br>
+ <b> Related</b>:<br>
+ <br>
+ <a href="egrep.html">egrep</a> - Search file(s) for lines that match an extended
+ expression<br>
+ <a href="fgrep.html">fgrep</a> - Search file(s) for lines that match a fixed
+ string<br>
+ <a href="awk.html">gawk</a> - Find and Replace text within file(s)<br>
+ <a href="sed.html">sed</a> - Stream Editor - Find and Replace text within file(s) <br>
+ <a href="tr.html">tr</a> - Translate, squeeze, and/or delete characters <br>
+Equivalent Windows commands: <a href="../term_tools/nt/qgrep.html">QGREP</a> / <a href="../term_tools/nt/findstr.html">FINDSTR</a> - Search for strings in files </p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/groups.html b/help/en/bash/groups.html
new file mode 100644
index 0000000..9277af4
--- /dev/null
+++ b/help/en/bash/groups.html
@@ -0,0 +1,61 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>groups MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> groups</h1>
+<p>Print group names a user is in.</p>
+<pre>Syntax
+ groups [<em>username</em>]...</pre>
+<p> Prints the names of the primary and any supplementary groups for each given
+<em>username</em>, or the current process if no names are given. </p>
+<p>If names are given,
+the name of each user is printed before the list of that user's groups.</p>
+<p><b>Related</b>:<br>
+ <a href="env.html"><br>
+ env</a> - Display, set, or remove environment variables<br>
+ <a href="id.html">id</a> - Print user and group id's<br>
+ <a href="logname.html">logname</a> - Print current login name<br>
+ printenv - Print environment variables. <a href="users.html"><br>
+ users</a> - Print login names of users currently logged in <br>
+ <a href="uname.html">uname</a> - Print system information <br>
+ <a href="who.html">who</a> - Print who is currently logged in <br>
+ whoami - Print the current user id and name (`id -un') <br>
+Equivalent Windows command: <a href="../term_tools/nt/dsmod.html">DSMOD</a> user - Modify active directory object.</p><!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/gzip.html b/help/en/bash/gzip.html
new file mode 100644
index 0000000..6775984
--- /dev/null
+++ b/help/en/bash/gzip.html
@@ -0,0 +1,170 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>gzip MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> gzip</h1>
+<p>Compress or decompress named file(s)</p>
+<pre>SYNTAX
+ gzip <em>options</em> ...
+
+OPTIONS
+
+--stdout
+--to-stdout
+-c
+ Write output on standard output; keep original files unchanged.
+ If there are several input files, the output consists of a
+ sequence of independently compressed members. To obtain better
+ compression, concatenate all input files before compressing them.
+
+--decompress
+--uncompress
+-d
+ Decompress.
+
+--force
+-f
+ Force compression or decompression even if the file has multiple
+ links or the corresponding file already exists, or if the
+ compressed data is read from or written to a terminal. If the
+ input data is not in a format recognized by `gzip', and if the
+ option --stdout is also given, copy the input data without change
+ to the standard ouput: let `zcat' behave as `cat'. If `-f' is not
+ given, and when not running in the background, `gzip' prompts to
+ verify whether an existing file should be overwritten.
+
+--help
+-h
+ Print a help message describing the options, then quit.
+
+--list
+-l
+ For each compressed file, list the following fields:
+
+ compressed size: size of the compressed file
+ uncompressed size: size of the uncompressed file
+ ratio: compression ratio (0.0% if unknown)
+ uncompressed_name: name of the uncompressed file
+
+ The uncompressed size is given as `-1' for files not
+ in `gzip' format.
+
+--license
+-L
+ Display the `gzip' license then quit.
+
+--no-name
+-n
+ When compressing, do not save the original file name and time
+ stamp by default. (The original name is always saved if the name
+ had to be truncated.) When decompressing, do not restore the
+ original file name if present (remove only the `gzip' suffix from
+ the compressed file name) and do not restore the original time
+ stamp if present (copy it from the compressed file). This option
+ is the default when decompressing.
+
+--name
+-N
+ When compressing, always save the original file name and time
+ stamp; this is the default. When decompressing, restore the
+ original file name and time stamp if present. This option is
+ useful on systems which have a limit on file name length or when
+ the time stamp has been lost after a file transfer.
+
+--quiet
+-q
+ Suppress all warning messages.
+
+--recursive
+-r
+ Travel the directory structure recursively. If any of the file
+ names specified on the command line are directories, `gzip' will
+ descend into the directory and compress all the files it finds
+ there (or decompress them in the case of `gunzip').
+
+--suffix SUF
+-S SUF
+ Use suffix `SUF' instead of `.gz'. Any suffix can be given, but
+ suffixes other than `.z' and `.gz' should be avoided to avoid
+ confusion when files are transferred to other systems. A null
+ suffix forces gunzip to try decompression on all given files
+ regardless of suffix, as in:
+
+ gunzip -S "" * (*.* for MSDOS)
+
+ Previous versions of gzip used the `.z' suffix. This was changed
+ to avoid a conflict with `pack'.
+
+--test
+-t
+ Test. Check the compressed file integrity.
+
+--verbose
+-v
+ Verbose. Display the name and percentage reduction for each file
+ compressed.
+
+--version
+-V
+ Version. Display the version number and compilation options, then
+ quit.
+
+--fast
+--best
+-N
+ Regulate the speed of compression using the specified digit N,
+ where `-1' or `--fast' indicates the fastest compression method
+ (less compression) and `--best' or `-9' indicates the slowest
+ compression method (optimal compression). The default
+ compression level is `-6' (that is, biased towards high
+ compression at expense of speed).</pre>
+<p>`gunzip' can currently decompress files created by `gzip', `zip',
+ `compress' or `pack'. The detection of the input format is automatic. <br>
+ <br>
+ `gzip' is designed as a complement to `tar', not as a replacement. </p>
+<p><b>Related</b>:<br>
+ <br>
+ <a href="sum.html">sum</a> - Print a checksum for a file <br>
+ <a href="tar.html">tar</a> - Tape ARchiver<br>
+ <a href="unshar.html">unshar</a> - Unpack shell archive scripts <br>
+Equivalent Windows command:
+ <a href="../term_tools/nt/expand.html">EXPAND</a> - Uncompress files</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/hash.html b/help/en/bash/hash.html
new file mode 100644
index 0000000..bce2498
--- /dev/null
+++ b/help/en/bash/hash.html
@@ -0,0 +1,73 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>hash MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> hash</h1>
+<p>Remember the full pathnames of commands specified as name arguments,
+so they need not be searched for on subsequent invocations.</p>
+<pre>SYNTAX
+ hash [-r] [-p <em>filename</em>] [<em>name</em>]
+
+OPTIONS
+ -r Reset (causes the shell to forget all remembered locations)
+ -p Use filename as the location of name (don't search $PATH)</pre>
+<p> The commands are found by searching through the directories listed in $PATH.
+ <br>
+ <br>
+ If no arguments are given, information about remembered commands is printed.
+ <br>
+ <br>
+ The return status is zero unless a name is not found or an invalid option is
+ supplied. </p>
+<p>This is a BOURNE shell command.<br>
+ <br>
+ <i>&quot;I spent most of the eighties, most of my life, riding around in somebody
+ else's car, in possession of, or ingested of, something illegal, on my way from
+ something illegal to something illegal with many illegal things happening all
+ around me&quot; - Iggy Pop
+ </i> </p>
+<p><b>Related</b>:<br>
+ <br>
+ <a href="dirname.html">dirname</a> - Convert a full pathname to just a path<br>
+ <a href="which.html">which</a> - Show full path of commands <br>
+Equivalent Windows command: <a href="../term_tools/nt/set.html">
+SET</a> - Display, set, or remove Windows environment variables</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/head.html b/help/en/bash/head.html
new file mode 100644
index 0000000..242b81f
--- /dev/null
+++ b/help/en/bash/head.html
@@ -0,0 +1,99 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>head MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> head</h1>
+<p>Output the first part of files, prints the first part (10 lines
+by default) of each file.</p>
+<pre>SYNTAX
+ head [<i>options</i>]... [<i>file</i>]...
+
+Options:
+
+ -<i>NUMBER</i>
+ Return the first <i>NUMBER</i> of lines from the file. (must be the first option specified)
+
+ -<i>Count</i>Options</pre>
+<blockquote>
+<p>This option is only recognized if it is specified first. <span class="telety">Count</span> is
+a decimal number optionally followed by a size letter ('b', 'k',<br>
+'m' for bytes, Kilobytes or Megabytes) , or 'l' to mean count by lines, or other option
+letters ('cqv').</p>
+</blockquote>
+<pre> -c <i>BYTES</i>
+ --bytes=<i>BYTES</i>
+ Print the first <i>BYTES</i> bytes, instead of initial lines. Appending
+ 'b' multiplies <i>BYTES</i> by 512, 'k' by 1024, and 'm' by 1048576.
+
+ -n <i>N</i>
+ --lines=<i>N</i>
+ Output the first <i>N</i> lines.
+
+ -q
+ --quiet
+ --silent
+ Never print file name headers.
+
+ -v
+ --verbose
+ Always print file name headers.</pre>
+<p>If no files are given (or if given a <i>FILE </i>of '-') head will read from standard input.</p>
+<p>If more than one <i>FILE</i> is specified, 'head' will print a one-line header consisting of <span class="telety">==> FILE NAME <==</span> before the output for each <i>FILE</i>.<br>
+<br>
+Two option formats are accepted: the new one, in which numbers are arguments to the options ('-q -n 1'), and the old one, in which the number precedes any option letters ('-1q')</p>
+<p><b>Examples</b></p>
+<p>Extract the first 85 lines from a file: </p>
+<p class="telety"> head -85 file,txt </p>
+<p>Extract lines 40-50 from a file, first using head to get the first 50 lines then <a href="tail.html">tail</a> to get the last 10: </p>
+<p class="telety"> head -50 file.txt | tail -10 </p>
+<p><i>"If you can keep your head when all about you are losing theirs and blaming it on you...&quot; - Rudyard Kipling</i></p>
+<p><b>Related bash commands</b>:<br>
+ <a href="csplit.html"><br>
+ csplit</a> - Split a file into context-determined pieces<br>
+ <a href="cut.html">cut</a> - Divide a file into several parts<br>
+ <a href="fmt.html">fmt</a> - Reformat paragraph text<br>
+ <a href="paste.html">paste</a> - Merge lines of files<br>
+ <a href="split.html">split</a> - Split a file into fixed-size pieces<br>
+ <a href="tail.html">tail</a> - Output the last part of files<br>
+ Equivalent Windows command:
+ <a href="../term_tools/nt/for.html">FOR</a> /F &quot;skip=nlines&quot; - Loop through items
+ in a text file</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/history.html b/help/en/bash/history.html
new file mode 100644
index 0000000..0a7430e
--- /dev/null
+++ b/help/en/bash/history.html
@@ -0,0 +1,266 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>history MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> history</h1>
+<p>Command Line history</p>
+<pre>SYNTAX
+ history
+ history [n]
+ history -c
+ history -d <em>offset</em>
+ history [-anrw] [<em>filename</em>]
+ history -ps <em>arg</em>
+
+KEY
+ -c Clear the history list. This may be combined with
+ the other options to replace the history list completely.
+
+ -d offset
+ Delete the history entry at position offset.
+ offset should be specified as it appears when the history is displayed.
+
+ -a Append the new history lines (history lines entered since
+ the beginning of the current Bash session) to the history file.
+
+ -n Append the history lines not already read from the history file
+ to the current history list. These are lines appended to the
+ history file since the beginning of the current Bash session.
+
+ -r Read the current history file and append its contents to the history list.
+
+ -w Write out the current history to the history file.
+
+ -p Perform history substitution on the args and display the result
+ on the standard output, without storing the results in the history list.
+
+ -s The args are added to the end of the history list as a single entry.
+ </pre>
+<p>With no options, display the history list with line numbers. Lines
+ prefixed with with a `*' have been modified. An argument of n lists only the
+ last n lines. <br>
+ When any of the `-w', `-r', `-a', or `-n' options are used, if filename is given,
+ then it is used as the history file. If not, then the value of the HISTFILE
+ variable is used.
+<p><b>Recalling a previous command</b>
+<p> Pressing the UP arrow will return to previous commands.<br>
+ <br>
+ To return to a previously entered command, type ctrl-r and then begin typing
+ the command. This will finish the command for you as you type. If you can remember
+ to use ctrl-r, it will become invaluable for repeating longer commands. <br>
+ <br>
+ To find a specific command among many previous commands; pipe history through
+ grep:<br>
+ history|<a href="grep.html">grep</a> -i <i>first few letters of command</i><br>
+ <br>
+ <b>History Expansion </b><br>
+ <br>
+ History expansions introduce words from the history list into the input stream,
+ making it easy to repeat commands, insert the arguments to a previous command
+ into the current input line, or fix errors in previous commands quickly. <br>
+ <br>
+ History expansion takes place in two parts. The first is to determine which
+ line from the history list should be used during substitution. The second is
+ to select portions of that line for inclusion into the current one. <br>
+ <br>
+ The line selected from the history is called the event, and the portions of
+ that line that are acted upon are called words. Various modifiers are available
+ to manipulate the selected words. The line is broken into words (several words
+ surrounded by quotes are considered one word). <br>
+ <br>
+ History expansions are introduced by the appearance of the history expansion
+ character, which is `!' by default. Only `\' and `'' may be used to escape the
+ history expansion character. <br>
+ <br>
+ Several shell options settable with the <a href="shopt.html">shopt</a> builtin
+ may be used to tailor the behavior of history expansion. <br>
+ <br>
+ The `-p' option to the history builtin command may be used to see what a history
+ expansion will do before using it. <br>
+ <br>
+ The `-s' option to the history builtin may be used to add commands to the end
+ of the history list without actually executing them, so that they are available
+ for subsequent recall.<br>
+ <br>
+ <b>Event Designators</b> <br>
+ An event designator is a reference to a command line entry in the history list.
+ <br>
+<pre>
+! Start a history substitution, except when followed by a space,
+ tab, the end of the line, `=' or `('.
+
+!n Refer to command line n.
+
+!-n Refer to the command n lines back.
+
+!! Refer to the previous command. This is a synonym for `!-1'.
+
+!string Refer to the most recent command starting with string.
+
+!?string[?] Refer to the most recent command containing string.
+ The trailing `?' may be omitted if the string is followed
+ immediately by a newline.
+
+^string1^string2^ Quick Substitution. Repeat the last command, replacing string1
+ with string2. Equivalent to !!:s/string1/string2/.
+
+!# The entire command line typed so far. </pre>
+<p> <b>Word Designators </b><br>
+ <br>
+ Word designators are used to select desired words from the event. A `:' separates
+ the event specification from the word designator. It may be omitted if the word
+ designator begins with a `^', `$', `*', `-', or `%'. Words are numbered from
+ the beginning of the line, with the first word being denoted by 0 (zero). Words
+ are inserted into the current line separated by single spaces. </p>
+<pre>For example,
+
+!! designates the preceding command. When you type this, the
+ preceding command is repeated in toto.
+
+!!:$ designates the last argument of the preceding command.
+ This may be shortened to !$.
+
+!fi:2 designates the second argument of the most recent command
+ starting with the letters fi.
+
+Here are the word designators:
+
+0 (zero) The 0th word. For many applications, this is the command word.
+
+<em>n</em> The <em>n</em>th word.
+
+^ The first argument; that is, word 1.
+
+$ The last argument.
+
+% The word matched by the most recent `?string?' search.
+
+x-y A range of words; `-y' abbreviates `0-y'.
+
+* All of the words, except the 0th. This is a synonym for `1-$'.
+ It is not an error to use `*' if there is just one word in the event;
+ the empty string is returned in that case.
+
+x* Abbreviates `x-$'
+
+x- Abbreviates `x-$' like `x*', but omits the last word.
+
+If a word designator is supplied without an event specification,
+the previous command is used as the event.</pre>
+<b><span class="body">Modifiers</span></b><span class="body"><br>
+<br>
+After the optional word designator, you can add a sequence of one or more of the
+following modifiers, each preceded by a `:'. </span><br>
+
+<pre>h Remove a trailing pathname component, leaving only the head.
+
+t Remove all leading pathname components, leaving the tail.
+
+r Remove a trailing suffix of the form `.suffix', leaving the basename.
+
+e Remove all but the trailing suffix.
+
+p Print the new command but do not execute it.
+
+q Quote the substituted words, escaping further substitutions.
+
+x Quote the substituted words as with `q', but break into words at
+ spaces, tabs, and newlines.
+
+s/old/new/
+ Substitute new for the first occurrence of old in the event line.
+ Any delimiter may be used in place of `/'. The delimiter may be
+ quoted in old and new with a single backslash.
+ If `&' appears in new, it is replaced by old.
+ A single backslash will quote the `&'.
+ The final delimiter is optional if it is the last character on the input line.
+
+& Repeat the previous substitution.
+
+g Cause changes to be applied over the entire event line.
+ Used in conjunction with `s', as in gs/old/new/, or with `&'.</pre>
+<p><b>History Configuration</b></p>
+<p><span class="code">export HISTCONTROL=erasedups<br>
+export HISTSIZE=10000<br>
+shopt -s histappend</span></p>
+<p># Remove duplicates from history (when a new item is added).<br>
+# Increase the history size.<br>
+# Append history to ~/.bash_history. when you exit a shell<br>
+From Allan Odgaard&rsquo;s excellent <a href="http://blog.macromates.com/2008/working-with-history-in-bash/">Working With History in Bash</a></p>
+<p><b>Examples (bang commands) </b></p>
+<p>The following bang commands work in not just bash but also tcsh and zsh too.<br>
+Not every
+bang command will work in every shell, but these are pretty universal . </p>
+<p>assume these are the last
+ three commands you ran:</p>
+<p class="telety"> % which firefox<br>
+ % make<br>
+ % ./foo -f foo.conf<br>
+% vi foo.c bar.c</p>
+<p>Getting stuff from the last command:</p>
+<pre> Full line: % !! becomes: % vi foo.c bar.c
+ Last arg : % svn ci !$ becomes: % svn ci bar.c
+ All args : % svn ci !* becomes: % svn ci foo.c bar.c
+ First arg: % svn ci !!:1 becomes: % svn ci foo.c</pre>
+<p>Accessing commandlines by pattern:</p>
+<pre> Full line: % !./f becomes: % ./foo -f foo.conf
+ Full line: % vi `!whi` becomes: % vi `which firefox`
+ Last arg : % vi !./f:$ becomes: % vi foo.conf
+ All args : % ./bar !./f:* becomes: % ./bar -f foo.conf
+ First arg: % svn ci !vi:1 becomes: % svn ci foo.c</pre>
+<p>Example from <a href="http://mail.linux.ie/pipermail/ilug/2006-May/087799.html">Kevin Lyda </a>(Irish Linux Users' Group)<br>
+ Various shells have options that can affect this. Be careful with
+ shells that let you share history among instances. Some shells also<br>
+ allow bang commands to be expanded with tabs or expanded and reloaded
+on the command line for further editing when you press return.</p>
+<p><i>&quot;I never cared for fashion much, amusing little seams
+ and witty little pleats: it was the girls I liked.&quot; - David
+ Bailey </i><br>
+ <br>
+ <b> Related</b>:<br>
+ <a href="env.html"> </a> <a href="set.html">set -o history</a> - Enable/Disable history<br>
+ set history = 8 - Set the size of the history list.<br>
+ fc - Fix History Command<a href="hash.html"><br>
+ hash</a> - Remember the full pathname of a name argument<br>
+ <a href="time.html">time</a> - Measure Program Resource Use <br>
+ Equivalent Windows Powershell command:
+ <a href="../term_tools/ps/get-history.html">Get-History</a> - Get commands entered during the current session.</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/hostname.html b/help/en/bash/hostname.html
new file mode 100644
index 0000000..d15f2a3
--- /dev/null
+++ b/help/en/bash/hostname.html
@@ -0,0 +1,70 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>hostname MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> hostname</h1>
+<p>Print or set system name</p>
+<pre>SYNTAX
+ hostname [<em>name</em>]
+</pre>
+<p> With no arguments, `hostname' prints the name of the current host
+ system. With one argument, it sets the current host name to the
+ specified string. You must have appropriate privileges to set the host
+ name.</p>
+<p>&quot;<i>After all, what is your hosts' purpose in having a party?
+ Surely not for you to enjoy yourself; if that were their sole purpose, they'd
+ have simply sent champagne and women over to your place by taxi.&quot; - P.J.
+ O'Rourke</i></p>
+<p><b>Related</b>:<br>
+ <br>
+ <a href="env.html">env</a> - Display, set, or remove environment variables <br>
+ <a href="groups.html">groups</a> - Print group names a user is in<br>
+ <a href="id.html">id</a> - Print user and group id's <br>
+ <a href="logname.html">logname</a> - Print current login name<br>
+ <a href="tty.html">tty</a> - Print filename of terminal on stdin <br>
+ <a href="uname.html">uname</a> - Print system information <br>
+ <a href="users.html">users</a> - Print login names of users currently logged
+ in <br>
+ <a href="who.html">who</a> - Print who is currently logged in <br>
+ whoami - Print the current user id and name (`id -un') <br>
+Equivalent Windows command: <a href="../term_tools/nt/echo.html"> ECHO
+</a> %COMPUTERNAME%</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/id.html b/help/en/bash/id.html
new file mode 100644
index 0000000..87b0501
--- /dev/null
+++ b/help/en/bash/id.html
@@ -0,0 +1,93 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>id MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> id</h1>
+<p>Print real and effective user id (uid) and group id (gid), prints
+ identity information about the given user, or if no user is specified the current process.</p>
+<pre>SYNTAX
+ id [<em>options</em>]... [<em>username</em>]
+</pre>
+<p><span class="body"> By default, it prints the real user id, real group id, effective
+ user id if different from the real user id, effective group id if
+ different from the real group id, and supplemental group ids.<br>
+ <br>
+ Each of these numeric values is preceded by an identifying string and
+ followed by the corresponding user or group name in parentheses.</span></p>
+<pre>
+OPTIONS
+ The options cause `id' to print only part of the above information.
+
+-g
+--group
+ Print only the group id.
+
+-G
+--groups
+ Print only the supplementary groups.
+
+-n
+--name
+ Print the user or group name instead of the ID number.
+ Requires -u, -g, or -G
+
+-r
+--real
+ Print the real, instead of effective, user or group id.
+ Requires -u, -g, or -G
+
+-u
+--user
+ Print only the user id.</pre>
+<p><b>Related</b>:<br>
+ <br>
+ <a href="echo.html">echo</a> - Display message on screen <br>
+ <a href="env.html">env</a> - Display, set, or remove environment variables <br>
+ <a href="groups.html">groups</a> - Print group names a user is in <br>
+ <a href="hostname.html">hostname</a> - Print or set system name <br>
+ <a href="logname.html">logname</a> - Print current login name <br>
+ <a href="uname.html">uname</a> - Print system information<br>
+ <a href="users.html">users</a> - Print login names of users currently logged
+ in <br>
+ <a href="who.html">who</a> - Print who is currently logged in <br>
+ whoami - Print the current user id and name (`id -un') <br>
+Equivalent Windows command: <a href="../term_tools/nt/echo.html"> ECHO </a> %USERNAME%</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/if.html b/help/en/bash/if.html
new file mode 100644
index 0000000..84728ed
--- /dev/null
+++ b/help/en/bash/if.html
@@ -0,0 +1,81 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>if MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> if</h1>
+<p>Conditionally perform a command. </p>
+<pre>SYNTAX
+ <b>if</b> <var>test-commands</var>; <b>then</b>
+ <var> consequent-commands</var>;
+ [<b>elif</b> <var>more-test-commands</var>; <b>then</b>
+ <var> more-consequents</var>;]
+ [<b>else</b> <var>alternate-consequents</var>;]
+ <b>fi</b></pre>
+<p> The <var>test-commands</var> list is executed, and if its return status is
+ zero, the <var>consequent-commands</var> list is executed.</p>
+<p>If <var>test-commands</var> returns a non-zero status, each <code>elif</code>
+ list is executed in turn, and if its exit status is zero, the corresponding
+ <var>more-consequents</var> is executed and the command completes.<br>
+ <br>
+ If <samp>`else <var>alternate-consequents</var>'</samp> is present, and the
+ final command in the final <code>if</code> or <code>elif</code> clause has a
+ non-zero exit status, then <var>alternate-consequents</var> is executed.<br>
+ <br>
+ The return status is the exit status of the last command executed, or zero if
+ no condition tested true. </p>
+<p><i>"Then you admit confirming not denying you ever said that?" <br>
+ "NO! ... I mean Yes! WHAT?" <br>
+ I'll put `maybe.' - Bloom
+ County </i></p>
+
+<p><b>Related</b>:<br>
+ <br>
+ <a href="case.html">case</a> - Conditionally perform a command<br>
+ <a href="eval.html">eval</a> - Evaluate several commands/arguments <br>
+ <a href="expr.html">expr</a> - Evaluate expressions <br>
+ <a href="for.html">for</a> - Expand <var>words</var>, and execute <var>commands</var><br>
+ <a href="test.html">test</a> -
+ Evaluate a conditional expression<br>
+ <a href="until.html">until</a> - Execute commands (until error) <br>
+ <a href="while.html">while</a> - Execute commands<br>
+Equivalent Windows command:
+<a href="../term_tools/nt/if.html">IF</a> - Conditionally perform a command</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/ifconfig.html b/help/en/bash/ifconfig.html
new file mode 100644
index 0000000..7b94157
--- /dev/null
+++ b/help/en/bash/ifconfig.html
@@ -0,0 +1,142 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>ifconfig MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> ifconfig</h1>
+
+
+<p><b>I</b>nter<b>f</b>ace <b>config</b>urator - display your ip address, network interfaces, transferred and received data information, configure a network interface.</p>
+<pre>Syntax
+ ifconfig [<i>interface</i>]
+
+ ifconfig <i>interface</i> [<i>aftype</i>] <i>options</i> | <i>address </i>...
+
+Options
+ interface The name of the interface.
+ Usually a driver name followed by a unit number, eth0 = 1st Ethernet interface.
+
+ up This flag causes the interface to be activated.
+ It is implicitly specified if an address is assigned to the interface.
+
+ down This flag causes the driver for this interface to be shut down.
+
+ [-]arp Enable or disable the use of the ARP protocol on this interface.
+
+ [-]promisc Enable or disable the promiscuous mode of the interface.
+ If selected, all packets on the network will be received by the interface.
+
+ [-]allmulti Enable or disable all-multicast mode.
+ If selected, all multicast packets on the network will be received by the interface.
+
+ metric N Set the interface metric.
+
+ mtu N Set the Maximum Transfer Unit (MTU) of an interface.
+
+ dstaddr addr Set the remote IP address for a point-to-point (PPP)link (obsolete; use pointopoint instead)
+
+ netmask addr Set the IP network mask for this interface.
+ This value defaults to the usual class A, B or C network mask
+ (as derived from the interface IP address), but it can be set to any value.
+
+ add addr/prefixlen Add an IPv6 address to an interface.
+
+ del addr/prefixlen Remove an IPv6 address from an interface.
+
+ tunnel aa.bb.cc.dd Create a new SIT (IPv6-in-IPv4) device, tunnelling to the given destination.
+
+ irq addr Set the interrupt line used by this device.
+ Not all devices can dynamically change their IRQ setting.
+
+ io_addr addr Set the start address in I/O space for this device.
+
+ mem_start addr Set the start address for shared memory used by this device.
+ Only a few devices need this.
+
+ media type Set the physical port or medium type to be used by the device.
+ Not all devices can change this setting, and those that can vary
+ in what values they support. Typical values for type are 10base2 (thin Ethernet),
+ 10baseT (twisted-pair 10Mbps Ethernet), AUI (external transceiver) and so on.
+ The special medium type of auto can be used to tell the driver to auto-sense the
+ media. Again, not all drivers can do this.
+
+ [-]broadcast [addr] If the address argument is given, set the protocol broadcast address
+ for this interface. Otherwise, set (or clear) the IFF_BROADCAST flag for
+ the interface.
+
+ [-]pointopoint [addr] This keyword enables the point-to-point mode of an interface,meaning that
+ it is a direct link between two machines with nobody else listening on it.
+ If the address argument is also given, set the protocol address of the other
+ side of the link, just like the obsolete dstaddr keyword does.
+ Otherwise, set or clear the IFF_POINTOPOINT flag for the interface.
+
+ hw class address Set the hardware address of this interface, if the device driver supports
+ this operation. The keyword must be followed by the name of the hardware class
+ and the printable ASCII equivalent of the hardware address. Hardware classes
+ currently supported include ether (Ethernet), ax25 (AMPR AX.25), ARCnet and
+ netrom (AMPR NET/ROM).
+
+ multicast Set the multicast flag on the interface. Not normally be needed as
+ the drivers set the flag correctly themselves.
+
+ address The IP address to be assigned to this interface.
+
+ txqueuelen length Set the length of the transmit queue of the device.
+ It is useful to set this to small values for slower devices with a high
+ latency (modem links, ISDN) to prevent fast bulk transfers from disturbing
+ interactive traffic like telnet too much.</pre>
+<p> ifconfig is used at boot time to set up interfaces as necessary. After that, it is usually only needed when debugging or when system tuning is needed.</p>
+<p>If no arguments are given, ifconfig displays the status of the currently active interfaces. If a single interface argument is given, it displays the status of the given interface only; if a single -a argument is given, it displays the status of all interfaces, even those that are down. Otherwise, it configures an interface.</p>
+<p>If the first argument after the interface name is recognized as the name of a supported address family, that address family is used for decoding and displaying all protocol addresses. Currently supported address families include <b>inet</b> (TCP/IP, default), <b>inet6</b> (IPv6), <b>ax25</b> (AMPR Packet Radio), <b>ddp</b> (Appletalk Phase 2), <b>ipx</b> (Novell IPX) and <b>netrom</b> (AMPR Packet radio). </p>
+<p>All numbers supplied as parts in IPv4 dotted decimal notation may be decimal, octal, or hexadecimal, as specified in the ISO C standard (that is, a leading 0x or 0X implies hexadecimal; otherwise, a leading '0' implies octal; otherwise, the number is interpreted as decimal). Use of hexamedial and octal numbers is not RFC-compliant and therefore its use is discouraged and may go away.</p>
+<p><i>"A Connection Manager connection does not connect
+after being disconnected&quot; - Title of Microsoft <a href="http://support.microsoft.com/default.aspx?scid=kb;en-us;325331">KnowledgeBase</a> article</i></p>
+
+<p><b>Related</b>:<br>
+ <br>
+route(8)<br>
+netstat - Networking information<br>
+arp(8)<br>
+rarp(8)<br>
+ipchains(8)<br>
+<a href="http://www.ipchicken.com/">www.ipchicken.com</a><br>
+Equivalent Windows command:
+<a href="../term_tools/nt/netsh.html">NETSH</a> - Configure Interfaces</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/ifup.html b/help/en/bash/ifup.html
new file mode 100644
index 0000000..9c0a7b7
--- /dev/null
+++ b/help/en/bash/ifup.html
@@ -0,0 +1,89 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>ifup ifdown MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1>ifup / ifdown</h1>
+<p>Bring a network interface up or down </p>
+<pre>Syntax
+ ifup [<i>options</i>] -a | <i>IFACE</i>...
+
+ ifdown [<i>options</i>] -a|IFACE...
+
+Options
+ -a, --all If given to ifup, affect all interfaces marked auto.
+ Interfaces are brought up in the order in which they are defined in /etc/network/interfaces.
+
+ If given to ifdown, affect all defined interfaces.
+ Interfaces are brought down in the order in which they are currently listed in the state file.
+ Only interfaces defined in /etc/network/interfaces will be brought down.
+
+ --force Force configuration or deconfiguration of the interface.
+
+ --allow=<i>CLASS</i> Only allow interfaces listed in an allow-CLASS line in /etc/network/interfaces
+ to be acted upon.
+ -i <i>FILE</i>
+ --interfaces=<i>FILE
+ </i> Read interface definitions from FILE instead of from /etc/network/interfaces.
+
+ -n, --no-act Don't configure any interfaces or run any "up" or "down" commands.
+
+ --no-mappings Don't run any mappings. See interfaces for more information about the mapping feature.
+
+ -v, --verbose Show commands as they are executed.
+
+ -h, --help Display help for ifup
+
+ -V, --version Show copyright and version information.
+</pre>
+<p><b>Examples</b></p>
+<p>Bring up all the interfaces defined with auto in /etc/network/interfaces</p>
+<p class="telety">ifup -a</p>
+<p>Bring up interface eth0</p>
+<p class="telety">ifup eth0</p>
+<p>Bring down all interfaces that are currently up.</p>
+<p class="telety">ifdown -a</p>
+<p><br>
+<i>&quot;Either I'm dead or my watch has stopped&quot; - Groucho Marx's last words</i></p>
+
+<p><b>Related:</b></p>
+<p>ifplugd - A link detection daemon for ethernet devices <br>
+ <a href="logout.html">logout</a> - Exit a login shell</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/import.html b/help/en/bash/import.html
new file mode 100644
index 0000000..07029c9
--- /dev/null
+++ b/help/en/bash/import.html
@@ -0,0 +1,212 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>import MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> import</h1>
+<p>Capture some or all of an X server screen and save the image to
+file.</p>
+<pre>SYNTAX
+ import [ <em>options</em> ... ] [ file ]
+</pre>
+<p><span class="body"> import reads an image from any visible window on an X server
+ and outputs it as an image file. <br>
+ You can capture a single window, the entire screen, or any rectangular portion
+ of the screen. <br>
+ <br>
+ The target window can be specified by id, name, or may be selected by clicking
+ the mouse in the desired window. <br>
+ <br>
+ If you press a button and then drag, a rectangle will form which expands and
+ contracts as the mouse moves. To save the portion of the screen defined by the
+ rectangle, just release the button. The keyboard bell is rung once at the beginning
+ of the screen capture and twice when it completes.</span></p>
+<p>Examples</p>
+<blockquote>
+ <p>To select an X window with the mouse and save it in the MIFF image format
+ to a file titled MyTest.miff, use: <br>
+ <br>
+ import MyTest.miff <br>
+ <br>
+ To save the desktop to a jpeg file, use: </p>
+ <p><span class="body"> </span>import -window root MyTest.jpg<br>
+ </p>
+</blockquote>
+<p><span class="body">Although not strictly speaking part of the shell `import'
+ seems to be present on most linux distributions.</span> </p>
+<pre>OPTIONS
+<br>-border </pre>
+<p><span class="body"> include image borders in the output image.</span></p>
+<pre>-colors value</pre>
+<p><span class="body"> preferred number of colours in the image. The actual number
+ of colours in the image may be less than your request, but never more.<br>
+ </span> </p>
+<pre>-colorspace <em>value</em></pre>
+<p><span class="body"> The type of colorspace: GRAY, OHTA, RGB, Transpar*ent,
+ XYZ, YCbCr, YIQ, YPbPr, YUV, or CMYK.<br>
+ colour reduction, by default, takes place in the RGB colour space.<br>
+ <br>
+ The Transparent colour space behaves uniquely in that it preserves the matte
+ channel of the image if it exists.<br>
+ The -colors or -monochrome option is required for this option to take effect.
+ </span> </p>
+<pre>-comment <em>string</em></pre>
+<p><span class="body"> annotate an image with a comment.</span> </p>
+<pre>-compress <em>type</em></pre>
+<p><span class="body"> The type of image compression: None, BZip, Fax, Group4,
+ JPEG, LZW, RunlengthEncoded, or Zip.<br>
+ Specify +compress to store the binary image in an uncompressed format. The default
+ is the compression type of the specified image file. </span> </p>
+<pre>-delay <1/100ths of a second>x<seconds> </pre>
+<p><span class="body"> display the next image after pausing.<br>
+ This option is useful for regulating the display of the sequence of images.
+ 1/100ths of a second must expire before the display of the next image. The default
+ is 6/100 of a second between each frame of the image sequence. The second value
+ is optional. It specifies the number of seconds to pause before repeating your
+ animation sequence. </span> </p>
+<pre>-density <width><em>x<height></em>
+vertical and horizontal resolution in pixels of the image.
+
+-frame
+include window manager frame.
+
+-geometry <width><em>x</em><height>{+-}<x offset>{+-}<y off-
+set>{%}{!}{<}{>}
+the width and height of the image.
+
+-interlace <em>type</em></pre>
+<p><span class="body"> The type of interlacing scheme: <tt>None, Line, Plane, or Partition</tt>.
+ The default is <tt>None</tt>.<br>
+ This option is used to specify the type of interlacing scheme for raw image
+ formats such as RGB or YUV.<br>
+ <br>
+ No - means do not interlace (RGBRGBRGBRGBRGBRGB...)<br>
+ Line - uses scanline interlacing (RRR...GGG...BBB...RRR...GGG...BBB...)<br>
+ Plane - uses plane interlacing (RRRRRR...GGGGGG...BBBBBB...)<br>
+ Partition - is like plane except the different planes are saved to individual
+ files (e.g. image.R, image.G, and image.B)<br>
+ <br>
+ Use Line, or Plane to create an interlaced GIF or progressive JPEG image.</span></p>
+<pre>-label name assign a label to an image.</pre>
+<p><span class="body"> Use this option to assign a specific label to the image.
+ </span> </p>
+<pre>-monochrome
+transform image to black and white.
+
+-negate
+replace every pixel with its complementary colour (white becomes black, yellow becomes blue, etc.)
+Use +negate to only negate the grayscale pixels of the image.
+
+-quality value</pre>
+<p> JPEG/MIFF/PNG compression level.<br>
+ For the JPEG image format, quality is 0 (worst) to 100 (best). The default quality
+ is 75.<br>
+ Quality for the MIFF and PNG image format sets the amount of image compression
+ (quality / 10) and filter-type (quality % 10). Compression quality values range
+ from 0 (worst) to 100 (best).</p>
+<pre>-rotate <em>degrees</em>{<}{>}</pre>
+<p><span class="body"> apply Paeth image rotation to the image.<br>
+ <br>
+ Use > to rotate the image only if its width exceeds the height. < rotates the
+ image only if its width is less than the height. For example, if you specify
+ -90> and the image size is 480x640, the image is not rotated by the specified
+ angle. However, if the image is 640x480, it is rotated by-90 degrees. Empty
+ triangles left over from rotating the image are filled with the colour defined
+ as bordercolor (class borderColor). </span><br>
+</p>
+<pre>-scene <em>value</em> </pre>
+<p><span class="body"> Number of screen snapshots.<br>
+ Use this option to grab more than one image from the X server screen to create
+ an animation sequence. </span><br>
+</p>
+<pre>-screen </pre>
+<p><span class="body"> This option indicates that the GetImage request used to
+ obtain the image should be done on the root window, rather than directly on
+ the specified window. In this way, you can obtain pieces of other windows that
+ overlap the specified window, and more importantly, you can capture menus or
+ other popups that are independent windows but appear over the specified window.
+ </span><br>
+</p>
+<pre>-silent
+operate silently, i.e. don't ring any bells.
+
+-transparency color
+make this colour transparent within the image.
+
+-treedepth value </pre>
+<p><span class="body"> Normally, this integer value is zero or one. A zero or
+ one tells convert to choose a optimal tree depth for the colour reduction algorithm.
+ <br>
+ Try values between 2 and 8 for this parameter. </span><br>
+</p>
+<pre>-verbose </pre>
+<p><span class="body"> print detailed information about the image. This information
+ is printed: image scene number; image name; image size; the image class (Direct-
+ Class or PseudoClass); the total number of unique colours; and the number of
+ seconds to read and write the image. </span> </p>
+<pre>-window <em>id</em> </pre>
+<p><span class="body"> select window with this id or name. With this option you
+ can specify the target window by id or name rather than using the mouse. Specify
+ `root' to select X's root window as the target window. </span></p>
+<p><span class="body"> All Options are processed in command line order. Any option
+ you specify on the command line remains in effect until it is explicitly changed
+ by specifying the option again with a different effect. <br>
+ <br>
+ file specifies the image filename. If file is omitted, it defaults to magick.miff.
+ The default image format is MIFF. To specify a particular image format, precede
+ the filename with an image format name and a colon (i.e. gif:image) or specify
+ the image type as the filename suffix (i.e. image.jpg). See convert(1) for a
+ list of valid image formats. <br>
+ <br>
+ Specify file as - for standard output. If file has the extension .Z or .gz,
+ the file size is compressed using with compress or gzip respectively. Precede
+ the image file name | to pipe to a system command. If file already exists, you
+ will be prompted as to whether it should be overwritten. <br>
+ <br>
+ <i>&quot;We can now manipulate images to such an extrodinary extent that there's
+ no lie you cannot tell&quot; - Sir
+ David Attenborough </i> </span></p>
+<p><b>Related</b>:<br>
+ <a href="cat.html"><br>
+ cat</a> - Display the contents of a file<br>
+ <a href="echo.html">echo</a> - Display message on screen<a href="more.html"><br>
+ more</a> - Display output one screen at a time<br>
+Equivalent Windows command: Print Scrn - Copy screen to clipboard</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/index.html b/help/en/bash/index.html
new file mode 100644
index 0000000..578c4bc
--- /dev/null
+++ b/help/en/bash/index.html
@@ -0,0 +1,283 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>bash commands - Linux MAN Pages</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<link rel="alternate" type="application/rss+xml" title="RSS" href="../term_tools/rss.xml">
+<style type="text/css">
+<!--
+.grn { color: #339900; text-decoration: none; }
+-->
+</style>
+</head>
+<body>
+
+<h1>An A-Z Index of the <span class="grn">Bash</span> command line for Linux.</h1>
+<pre> adduser Add a user to the system
+ addgroup Add a group to the system
+ <a href="alias.html">alias</a> Create an alias •
+ apropos Search Help manual pages (man -k)
+ <a href="apt-get.html">apt-get</a> Search for and install software packages (Debian/Ubuntu)
+ <a href="aptitude.html">aptitude</a> Search for and install software packages (Debian/Ubuntu)
+ <a href="aspell.html">aspell</a> Spell Checker
+ <a href="awk.html">awk</a> Find and Replace text, database sort/validate/index
+b
+ <a href="basename.html">basename</a> Strip directory and suffix from filenames
+ bash GNU Bourne-Again SHell
+ <a href="bc.html">bc</a> Arbitrary precision calculator language
+ <a href="bg.html">bg</a> Send to background
+ <a href="break.html">break</a> Exit from a loop •
+ <a href="builtin.html">builtin</a> Run a shell builtin
+ <a href="http://www.bzip.org/">bzip2</a> Compress or decompress named file(s)
+c
+ <a href="cal.html">cal</a> Display a calendar
+ <a href="case.html">case</a> Conditionally perform a command
+ <a href="cat.html">cat</a> Display the contents of a file
+ <a href="cd.html">cd</a> Change Directory
+ <a href="cfdisk.html">cfdisk</a> Partition table manipulator for Linux
+ <a href="chgrp.html">chgrp</a> Change group ownership
+ <a href="chmod.html">chmod</a> Change access permissions
+ <a href="chown.html">chown</a> Change file owner and group
+ <a href="chroot.html">chroot</a> Run a command with a different root directory
+ <a href="chkconfig.html">chkconfig</a> System services (runlevel)
+ <a href="cksum.html">cksum</a> Print CRC checksum and byte counts
+ clear Clear terminal screen
+ <a href="cmp.html">cmp</a> Compare two files
+ <a href="comm.html">comm</a> Compare two sorted files line by line
+ <a href="command.html">command</a> Run a command - ignoring shell functions •
+ <a href="continue.html">continue</a> Resume the next iteration of a loop •
+ <a href="cp.html">cp</a> Copy one or more files to another location
+ <a href="cron.html">cron</a> Daemon to execute scheduled commands
+ <a href="crontab.html">crontab</a> Schedule a command to run at a later time
+ <a href="csplit.html">csplit</a> Split a file into context-determined pieces
+ <a href="cut.html">cut</a> Divide a file into several parts
+d
+ <a href="date.html">date</a> Display or change the date &amp; time
+ <a href="dc.html">dc</a> Desk Calculator
+ <a href="dd.html">dd</a> Convert and copy a file, write disk headers, boot records
+ <a href="ddrescue.html">ddrescue</a> Data recovery tool
+ <a href="declare.html">declare</a> Declare variables and give them attributes •
+ <a href="df.html">df</a> Display free disk space
+ <a href="diff.html">diff</a> Display the differences between two files
+ <a href="diff3.html">diff3</a> Show differences among three files
+ <a href="dig.html">dig</a> DNS lookup
+ <a href="dir.html">dir</a> Briefly list directory contents
+ <a href="dircolours.html">dircolors</a> Colour setup for `ls'
+ <a href="dirname.html">dirname</a> Convert a full pathname to just a path
+ <a href="dirs.html">dirs</a> Display list of remembered directories
+ <a href="dmesg.html">dmesg</a> Print kernel &amp; driver messages
+ <a href="du.html">du</a> Estimate file space usage
+e
+ <a href="echo.html">echo</a> Display message on screen •
+ <a href="egrep.html">egrep</a> Search file(s) for lines that match an extended expression
+ <a href="eject.html">eject</a> Eject removable media
+ <a href="enable.html">enable</a> Enable and disable builtin shell commands •
+ <a href="env.html">env</a> Environment variables
+ ethtool Ethernet card settings
+ <a href="eval.html">eval</a> Evaluate several commands/arguments
+ <a href="exec.html">exec</a> Execute a command
+ <a href="exit.html">exit</a> Exit the shell
+ <a href="http://en.wikipedia.org/wiki/Expect">expect</a> Automate arbitrary applications accessed over a terminal
+ <a href="expand.html">expand</a> Convert tabs to spaces
+ <a href="export.html">export</a> Set an environment variable
+ <a href="expr.html">expr</a> Evaluate expressions
+f
+ <a href="false.html">false</a> Do nothing, unsuccessfully
+ <a href="fdformat.html">fdformat</a> Low-level format a floppy disk
+ <a href="fdisk.html">fdisk</a> Partition table manipulator for Linux
+ <a href="fg.html">fg</a> Send job to foreground
+ <a href="fgrep.html">fgrep</a> Search file(s) for lines that match a fixed string
+ file Determine file type
+ <a href="find.html">find</a> Search for files that meet a desired criteria
+ <a href="fmt.html">fmt</a> Reformat paragraph text
+ <a href="fold.html">fold</a> Wrap text to fit a specified width.
+ <a href="for.html">for</a> Expand <var>words</var>, and execute <var>commands</var>
+ format Format disks or tapes
+ free Display memory usage
+ <a href="fsck.html">fsck</a> File system consistency check and repair
+ ftp File Transfer Protocol
+ <a href="function.html">function</a> Define Function Macros
+ <a href="fuser.html">fuser</a> Identify/kill the process that is accessing a file
+g
+ <a href="awk.html">gawk</a> Find and Replace text within file(s)
+ <a href="getopts.html">getopts</a> Parse positional parameters
+ <a href="grep.html">grep</a> Search file(s) for lines that match a given pattern
+ <a href="groups.html">groups</a> Print group names a user is in
+ <a href="gzip.html">gzip</a> Compress or decompress named file(s)
+h
+ <a href="hash.html">hash</a> Remember the full pathname of a name argument
+ <a href="head.html">head</a> Output the first part of file(s)
+ help Display help for a built-in command •
+ <a href="history.html">history</a> Command History
+ <a href="hostname.html">hostname</a> Print or set system name
+i
+ <a href="id.html">id</a> Print user and group id's
+ <a href="if.html">if</a> Conditionally perform a command
+ <a href="ifconfig.html">ifconfig</a> Configure a network interface
+ <a href="ifup.html">ifdown</a> Stop a network interface
+ <a href="ifup.html">ifup</a> Start a network interface up
+ <a href="import.html">import</a> Capture an X server screen and save the image to file
+ <a href="install.html">install</a> Copy files and set attributes
+j
+ <a href="jobs.html">jobs</a> List active jobs &bull;
+ <a href="join.html">join</a> Join lines on a common field
+k
+ <a href="kill.html">kill</a> Stop a process from running
+ <a href="killall.html">killall</a> Kill processes by name
+l
+ <a href="less.html">less</a> Display output one screen at a time
+ <a href="let.html">let</a> Perform arithmetic on shell variables •
+ <a href="ln.html">ln</a> Make links between files
+ <a href="local.html">local</a> Create variables •
+ <a href="locate.html">locate</a> Find files
+ <a href="logname.html">logname</a> Print current login name
+ <a href="logout.html">logout</a> Exit a login shell •
+ <a href="look.html">look</a> Display lines beginning with a given string
+ <a href="lpc.html">lpc</a> Line printer control program
+ <a href="lpr.html">lpr</a> Off line print
+ lprint Print a file
+ lprintd Abort a print job
+ lprintq List the print queue
+ <a href="lprm.html">lprm</a> Remove jobs from the print queue
+ <a href="ls.html">ls</a> List information about file(s)
+ <a href="lsof.html">lsof</a> List open files
+m
+ make Recompile a group of programs
+ <a href="man.html">man</a> Help manual
+ <a href="mkdir.html">mkdir</a> Create new folder(s)
+ <a href="mkfifo.html">mkfifo</a> Make FIFOs (named pipes)
+ mkisofs Create an hybrid ISO9660/JOLIET/HFS filesystem
+ <a href="mknod.html">mknod</a> Make block or character special files
+ <a href="more.html">more</a> Display output one screen at a time
+ <a href="mount.html">mount</a> Mount a file system
+ <a href="mtools.html">mtools</a> Manipulate MS-DOS files
+ <a href="mtr.html">mtr</a> Network diagnostics (traceroute/ping)
+ <a href="mv.html">mv</a> Move or rename files or directories
+ <a href="mmv.html">mmv</a> Mass Move and rename (files)
+n
+ netstat Networking information
+ <a href="nice.html">nice</a> Set the priority of a command or job
+ <a href="nl.html">nl</a> Number lines and write files
+ <a href="nohup.html">nohup</a> Run a command immune to hangups
+ <a href="../term_tools/bash/notify-send.html">notify-send</a> Send desktop notifications
+ <a href="nslookup.html">nslookup</a> Query Internet name servers interactively
+o
+ <a href="open.html">open</a> Open a file in its default application
+ <a href="op.html">op</a> Operator access
+p
+ <a href="passwd.html">passwd</a> Modify a user password
+ <a href="paste.html">paste</a> Merge lines of files
+ pathchk Check file name portability
+ <a href="ping.html">ping</a> Test a network connection
+ <a href="pkill.html">pkill</a> Stop processes from running
+ <a href="popd.html">popd</a> Restore the previous value of the current directory
+ <a href="pr.html">pr</a> Prepare files for printing
+ printcap Printer capability database
+ printenv Print environment variables
+ <a href="printf.html">printf</a> Format and print data •
+ <a href="ps.html">ps</a> Process status
+ <a href="pushd.html">pushd</a> Save and then change the current directory
+ <a href="pwd.html">pwd</a> Print Working Directory
+q
+ <a href="quota.html">quota</a> Display disk usage and limits
+ <a href="quotacheck.html">quotacheck</a> Scan a file system for disk usage
+ <a href="quotactl.html">quotactl</a> Set disk quotas
+r
+ <a href="ram.html">ram</a> ram disk device
+ <a href="rcp.html">rcp</a> Copy files between two machines
+ <a href="read.html">read</a> Read a line from standard input •
+ readarray Read from stdin into an array variable •
+ <a href="readonly.html">readonly</a> Mark variables/functions as readonly
+ reboot Reboot the system
+ <a href="rename.html">rename</a> Rename files
+ renice Alter priority of running processes
+ remsync Synchronize remote files via email
+ <a href="return.html">return</a> Exit a shell function
+ <a href="rev.html">rev</a> Reverse lines of a file
+ <a href="rm.html">rm</a> Remove files
+ <a href="rmdir.html">rmdir</a> Remove folder(s)
+ <a href="rsync.html">rsync</a> Remote file copy (Synchronize file trees)
+s
+ <a href="screen.html">screen</a> Multiplex terminal, run remote shells via ssh
+ <a href="scp.html">scp</a> Secure copy (remote file copy)
+ <a href="sdiff.html">sdiff</a> Merge two files interactively
+ <a href="sed.html">sed</a> Stream Editor
+ <a href="select.html">select</a> Accept keyboard input
+ <a href="seq.html">seq</a> Print numeric sequences
+ <a href="set.html">set</a> Manipulate shell variables and functions
+ sftp Secure File Transfer Program
+ <a href="shift.html">shift</a> Shift positional parameters
+ <a href="shopt.html">shopt</a> Shell Options
+ <a href="shutdown.html">shutdown</a> Shutdown or restart linux
+ <a href="sleep.html">sleep</a> Delay for a specified time
+ <a href="slocate.html">slocate</a> Find files
+ <a href="sort.html">sort</a> Sort text files
+ <a href="source.html">source</a> Run commands from a file `.'
+ <a href="split.html">split</a> Split a file into fixed-size pieces
+ <a href="ssh.html">ssh</a> Secure Shell client (remote login program)
+ strace Trace system calls and signals
+ <a href="su.html">su</a> Substitute user identity
+ <a href="sudo.html">sudo</a> Execute a command as another user
+ <a href="sum.html">sum</a> Print a checksum for a file
+ <a href="suspend.html">suspend</a> Suspend execution of this shell &bull;
+ <a href="symlink.html">symlink</a> Make a new name for a file
+ <a href="sync.html">sync</a> Synchronize data on disk with memory
+t
+ <a href="tail.html">tail</a> Output the last part of files
+ <a href="tar.html">tar</a> Tape ARchiver
+ <a href="tee.html">tee</a> Redirect output to multiple files
+ <a href="test.html">test</a> Evaluate a conditional expression
+ <a href="time.html">time</a> Measure Program running time
+ <a href="times.html">times</a> User and system times
+ <a href="touch.html">touch</a> Change file timestamps
+ <a href="top.html">top</a> List processes running on the system
+ <a href="traceroute.html">traceroute</a> Trace Route to Host
+ trap Run a command when a signal is set(bourne)
+ <a href="tr.html">tr</a> Translate, squeeze, and/or delete characters
+ <a href="true.html">true</a> Do nothing, successfully
+ <a href="tsort.html">tsort</a> Topological sort
+ <a href="tty.html">tty</a> Print filename of terminal on stdin
+ <a href="type.html">type</a> Describe a command •
+u
+ <a href="ulimit.html">ulimit</a> Limit user resources •
+ <a href="umask.html">umask</a> Users file creation mask
+ umount Unmount a device
+ <a href="alias.html">unalias</a> Remove an alias •
+ <a href="uname.html">uname</a> Print system information
+ <a href="unexpand.html">unexpand</a> Convert spaces to tabs
+ <a href="uniq.html">uniq</a> Uniquify files
+ <a href="units.html">units</a> Convert units from one scale to another
+ <a href="unset.html">unset</a> Remove variable or function names
+ <a href="unshar.html">unshar</a> Unpack shell archive scripts
+ <a href="until.html">until</a> Execute commands (until error)
+ <a href="useradd.html">useradd</a> Create new user account
+ <a href="usermod.html">usermod</a> Modify user account
+ <a href="users.html">users</a> List users currently logged in
+ <a href="uuencode.html">uuencode</a> Encode a binary file
+ <a href="uuencode.html">uudecode</a> Decode a file created by uuencode
+v
+ v Verbosely list directory contents (`ls -l -b')
+ vdir Verbosely list directory contents (`ls -l -b')
+ <a href="vi.html">vi</a> Text Editor
+ <a href="vmstat.html">vmstat</a> Report virtual memory statistics
+w
+ <a href="watch.html">watch</a> Execute/display a program periodically
+ <a href="wc.html">wc</a> Print byte, word, and line counts
+ <a href="whereis.html">whereis</a> Search the user's $path, man pages and source files for a program
+ <a href="which.html">which</a> Search the user's $path for a program file
+ <a href="while.html">while</a> Execute commands
+ <a href="who.html">who</a> Print all usernames currently logged in
+ <a href="whoami.html">whoami</a> Print the current user id and name (`id -un')
+ Wget Retrieve web pages or files via HTTP, HTTPS or FTP
+ <a href="write.html">write</a> Send a message to another user
+x
+ <a href="xargs.html">xargs</a> Execute utility, passing constructed argument list(s)
+ <a href="xdg-open.html">xdg-open</a> Open a file or URL in the user's preferred application.
+ <a href="yes.html">yes</a> Print a string until interrupted
+ <a href="source.html">.</a> Run a command script in the current shell
+ <a href="rem.html">###</a> Comment / Remark
+</pre>
+<p> Commands marked • are bash <i>built-ins</i>, these are available under all shells. </p>
+<a href="http://ss64.com/docs/copyright.html">Some rights reserved</a><br>
+</html>
diff --git a/help/en/bash/install.html b/help/en/bash/install.html
new file mode 100644
index 0000000..6fc14f7
--- /dev/null
+++ b/help/en/bash/install.html
@@ -0,0 +1,140 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>install MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> install</h1>
+<p>Copy files and set attributes, copies files while setting their
+permission modes and, if possible, their owner and group.</p>
+<pre>SYNTAX
+ install [<i>options</i>]... <em>SOURCE DEST</em>
+
+ install [<i>options</i>]... <em>SOURCE</em>... <em>DIRECTORY</em>
+
+ install -d [<i>options</i>]... <em>DIRECTORY</em>...
+
+DESCRIPTION
+The 3 variants above install either a single SOURCE file to DEST target
+or copy multiple SOURCE files to the destination. In the last variant,
+each DIRECTORY (and any missing parent directories) is created.
+
+`install' is similar to `cp', but allows you to control the
+attributes of destination files. It is typically used in Makefiles to
+copy programs into their destination directories. It refuses to copy
+files onto themselves.
+
+OPTIONS
+
+-b
+--backup
+ Make a backup of each file that would otherwise be overwritten or
+ removed. *Note Backup options::.
+
+-C
+ Install file, unless target already exists and is the same file,
+ in which case the modification time is not changed.
+
+-c
+ Ignored; for compatibility with old Unix versions of `install'.
+
+-d
+--directory
+ Create each given directory and any missing parent directories,
+ setting the owner, group and mode as given on the command line or
+ to the defaults. It also gives any parent directories it creates
+ those attributes. (This is different from the SunOS 4.x
+ `install', which gives directories that it creates the default
+ attributes.)
+
+-g <em>GROUP</em>
+--group=<em>GROUP</em>
+ Set the group ownership of installed files or directories to
+ GROUP. The default is the process's current group. GROUP may be
+ either a group name or a numeric group id.
+
+-m <em>MODE</em>
+--mode=<em>MODE</em>
+ Set the permissions for the installed file or directory to MODE,
+ which can be either an octal number, or a symbolic mode as in
+ `chmod', with 0 as the point of departure (*note File
+ permissions::). The default mode is 0755--read, write, and execute
+ for the owner, and read and execute for group and other.
+
+-o <em>OWNER</em>
+--owner=<em>OWNER</em>
+ If `install' has appropriate privileges (is run as root), set the
+ ownership of installed files or directories to OWNER. The default
+ is `root'. OWNER may be either a user name or a numeric user ID.
+
+-p
+--preserve-timestamps
+ Set the time of last access and the time of last modification of
+ each installed file to match those of each corresponding original
+ file. When a file is installed without this option, its last
+ access and last modification times are both set to the time of
+ installation. This option is useful if you want to use the last
+ modification times of installed files to keep track of when they
+ were last built as opposed to when they were last installed.
+
+-s
+--strip
+ Strip the symbol tables from installed binary executables.
+
+-S <em>SUFFIX</em>
+--suffix=<em>SUFFIX</em>
+ Append SUFFIX to each backup file made with `-b'.
+
+-v
+--verbose
+ Print the name of each file before copying it.
+
+-V <em>METHOD</em>
+--version-control=<em>METHOD</em>
+ Change the type of backups made with `-b'. The METHOD argument
+ can be `numbered' (or `t'), `existing' (or `nil'), or `never' (or
+ `simple').</pre>
+<p><i>SysAdmins can't be sued for malpractice but surgeons don't
+ have to deal with patients who install new versions of their own innards.</i><br>
+ <br>
+ <b> Related</b>:<br>
+ <br>
+ <a href="cp.html">cp</a> - Copy one or more files to another location<br>
+Equivalent Windows command: <a href="../term_tools/nt/robocopy.html">ROBOCOPY</a> - Robust File and Folder Copy </p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/jobs.html b/help/en/bash/jobs.html
new file mode 100644
index 0000000..736bad0
--- /dev/null
+++ b/help/en/bash/jobs.html
@@ -0,0 +1,79 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>jobs MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem -->
+<h1>jobs</h1>
+<p>Print currently running jobs and their status. </p>
+<pre>Syntax
+ jobs [<i>OPTIONS</i>] [<i>PID</i>]
+
+
+Options:
+ -c
+ --command Print the command name for each process in jobs
+
+ -g
+ --group Only print the group id of each job
+
+ -h
+ --help Display a help message and exit
+
+ -l
+ --last Only the last job to be started is printed
+
+ -p
+ --pid Print the process id for each process in all jobs </pre>
+<p>On systems that supports this feature, jobs will print the CPU usage of each job since the last command was executed. The CPU usage is expressed as a percentage of full CPU activity. Note that on multiprocessor systems, the total activity may be more than 100%. </p>
+<p>Example<br>
+<br>
+<span class="code">$ jobs</span></p>
+<p><i>"I'm not kidding myself,
+my voice is ordinary. If I stand still while
+I'm singing, I might as well go back to
+driving a truck&quot; - Elvis Presley </i></p>
+<p><b>Related bash commands</b>:<br>
+<br>
+<a href="fg.html">fg</a> - Send job to foreground <br>
+<a href="bg.html">bg</a> - Send to background<br>
+
+<a href="suspend.html">suspend</a> - Suspend execution of this shell</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/join.html b/help/en/bash/join.html
new file mode 100644
index 0000000..38f9b67
--- /dev/null
+++ b/help/en/bash/join.html
@@ -0,0 +1,138 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>join MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> join</h1>
+<p>Join lines on a common field, writes to standard output a line
+for each pair of input lines that have identical join fields.</p>
+<pre>SYNTAX
+ join [<em>Options</em>]... <em>File</em>1 <em>File</em>2</pre>
+<p><span class="body"> Description<br>
+ <br>
+ Either FILE1 or FILE2 (but not both) can be `-', meaning standard input. FILE1
+ and FILE2 should be already sorted in increasing textual order on the join fields,
+ using the collating sequence specified by the `LC_COLLATE' locale. <br>
+ <br>
+ Unless the `-t' option is given, the input should be sorted ignoring blanks
+ at the start of the join field, as in `sort -b'. If the `--ignore-case' option
+ is given, lines should be sorted without regard to the case of characters in
+ the join field, as in `sort<br>
+ -f'.<br>
+ <br>
+ The defaults are:<br>
+ </span><span class="body">The join field is the first field in each line; <br>
+ Fields in the input are separated by one or more blanks, with leading blanks
+ on the line ignored; <br>
+ Fields in the output are separated by a space; <br>
+ Each output line consists of the join field, the remaining fields from FILE1,
+ then the remaining fields from FILE2.</span></p>
+
+<pre>OPTIONS
+
+`-a <em>FILE-NUMBER</em>'
+ Print a line for each unpairable line in file <em>FILE-NUMBER</em> (either
+ `1' or `2'), in addition to the normal output.
+
+`-e <em>STRING</em>'
+ Replace those output fields that are missing in the input with
+ <em>STRING</em>.
+
+`-i'
+`--ignore-case'
+ Ignore differences in case when comparing keys. With this option,
+ the lines of the input files must be ordered in the same way. Use
+ `sort -f' to produce this ordering.
+
+`-1 <em>FIELD</em>'
+`-j1 <em>FIELD</em>'
+ Join on field <em>FIELD</em> (a positive integer) of file 1.
+
+`-2 <em>FIELD</em>'
+`-j2 <em>FIELD</em>'
+ Join on field <em>FIELD</em> (a positive integer) of file 2.
+
+`-j <em>FIELD</em>'
+ Equivalent to `-1 <em>FIELD</em> -2 <em>FIELD'</em>.
+
+`-o <em>FIELD-LIST</em>...'
+ Construct each output line according to the format in <em>FIELD-LIST</em>.
+ Each element in <em>FIELD-LIST</em> is either the single character `0' or
+ has the form M.N where the file number, M, is `1' or `2' and N is
+ a positive field number.
+
+ A field specification of `0' denotes the join field. In most
+ cases, the functionality of the `0' field spec may be reproduced
+ using the explicit M.N that corresponds to the join field.
+ However, when printing unpairable lines (using either of the `-a'
+ or `-v' options), there is no way to specify the join field using
+ M.N in FIELD-LIST if there are unpairable lines in both files. To
+ give `join' that functionality, POSIX invented the `0' field
+ specification notation.
+
+ The elements in <em>FIELD-LIST</em> are separated by commas or blanks.
+ Multiple <em>FIELD-LIST</em> arguments can be given after a single `-o'
+ option; the values of all lists given with `-o' are concatenated
+ together. All output lines - including those printed because of
+ any -a or -v option - are subject to the specified <em>FIELD-LIST</em>.
+
+`-t <em>CHAR</em>'
+ Use character <em>CHAR</em> as the input and output field separator.
+
+`-v <em>FILE-NUMBER</em>'
+ Print a line for each unpairable line in file <em>FILE-NUMBER </em>(either
+ `1' or `2'), instead of the normal output.</pre>
+<p><b><i><br>
+ </i></b><i>A nation is not in danger of financial disaster merely because it
+ owes itself money&quot; - Andrew William Mellon</i><br>
+ <br>
+ <b> Related commands</b>:<br>
+ <br>
+ <a href="csplit.html">csplit</a> - Split a file into context-determined pieces<br>
+ <a href="cut.html">cut</a> - Divide a file into several parts <br>
+ <a href="fmt.html">fmt</a> - Reformat paragraph text <br>
+ <a href="fold.html">fold</a> - Wrap input lines to fit in specified width<br>
+ <a href="head.html">head</a> - Output the first part of file(s) <br>
+ <a href="paste.html">paste</a> - Merge lines of files<br>
+ <a href="split.html">split</a> - Split a file into fixed-size pieces<br>
+ <a href="tail.html">tail</a> - Output the last part of files <br>
+Equivalent Windows command:
+<a href="../term_tools/nt/fc.html">FC</a> - Compare two files</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/kill.html b/help/en/bash/kill.html
new file mode 100644
index 0000000..904ffa4
--- /dev/null
+++ b/help/en/bash/kill.html
@@ -0,0 +1,98 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>kill MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> kill</h1>
+<p>Stop a process from running, either via a signal or forced termination.</p>
+<pre>Syntax
+ kill [-s <var>sigspec</var>] [-n <var>signum</var>] [-<var>sigspec</var>] <var>jobspec</var> or <var>pid</var>
+ kill -l [<var>exit_status</var>]
+ kill -l [<var>sigspec</var>]
+
+Key
+ -l List the signal names
+ -s Send a specific signal
+ -n Send a specific signal number</pre>
+<p>Send a signal specified by <var>sigspec</var> or <var>signum</var>
+ to the process named by job specification <var>jobspec</var> or process ID <var>pid</var>.
+ <var><br>
+ <br>
+ sigspec</var> is either a case-insensitive signal name such as <code>SIGINT</code> (with or without
+ the <code>SIG</code> prefix) or a signal number; <var>signum</var> is a signal
+ number.<br>
+ <br>
+ If <var>sigspec</var> is not present, <code>SIGTERM</code>
+ is used (Terminate). <br>
+ <br>
+ If any arguments are supplied when <samp>`-l'</samp> is given, the names of
+ the signals corresponding to the arguments are listed, and the return status
+ is zero. <var>exit_status</var> is a number specifying a signal number or the
+ exit status of a process terminated by a signal.<br>
+ <br>
+ The return status is true if at least one signal was successfully sent, or false
+if an error occurs or an invalid option is encountered.</p>
+<p><b>Examples</b></p>
+<p>List the running process</p>
+<pre>$ <b>ps</b>
+PID TTY TIME CMD
+1293 pts/5 00:00:00 MyProgram
+</pre>
+<p>Then Kill it</p>
+<pre>$ <b>kill 1293</b>
+[2]+ Terminated MyProgram
+</pre>
+<p><b><i> </i></b>To run a command and then kill it after 5 seconds:</p>
+<p class="code"> <span class="code">$ my_command &amp; sleep 5 <br>
+</span> $ kill -0 $! &amp;&amp; kill $!</p>
+<p>kill is a bash built in command: <span class="code"> $ help kill </span></p>
+<p><i>&quot;Whom the gods love dies young&quot; - Menander 300 BC </i><br>
+ <br>
+<b> Related</b>:</p>
+<p>ctrl+z - Suspend a program<br>
+ctrl+c - Interrupt a program<br>
+ <a href="ps.html">ps</a> - List running processes (returns PID)<br>
+ jobs - List your own processes (returns Job No.)<br>
+ <a href="bg.html">bg</a> - Put a process in the background<br>
+ <a href="fg.html">fg</a> - Put a process in the foreground<br>
+killall - kill processes by name <br>
+<a href="pkill.html">pkill</a> - Stop processes from running<br>
+Windows equivalent command: <a href="../term_tools/nt/pskill.html">pskill</a>- Stop a process from running</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/killall.html b/help/en/bash/killall.html
new file mode 100644
index 0000000..57dcc57
--- /dev/null
+++ b/help/en/bash/killall.html
@@ -0,0 +1,144 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>killall MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem -->
+<h1> killall</h1>
+<p>kill processes by name .</p>
+<pre>Syntax
+ killall [<i>option(s)</i>] [--] <i>name</i> ...
+
+ killall -l
+
+ killall -V,--version
+
+Options
+
+ -e
+ --exact
+ Require an exact match for very long names.
+ If a command name is longer than 15 characters, the full name may be
+ unavailable (i.e. it is swapped out). In this case, killall will kill everything
+ that matches within the first 15 characters. With -e, such entries are skipped.
+ killall prints a message for each skipped entry if -v is specified in addition to -e,
+
+ -g
+ --process-group
+ Kill the process group to which the process belongs.
+ The kill signal is only sent once per group, even if multiple processes belonging
+ to the same process group were found.
+
+ -I Do case insensitive process name match.
+ --ignore-case
+
+ -i Interactively ask for confirmation before killing.
+ --interactive
+
+ -l List all known signal names.
+ --list
+
+ <i>name</i> The command/process to be killed
+
+ -q Do not complain if no processes were killed.
+ --quiet
+
+ -r Interpret process name pattern as an extended regular expression.
+ --regexp
+
+ -<i>s</i> <i>signal</i>
+ --signal <i>signal</i>
+ Send this signal instead of SIGTERM. e.g. -9 = SIGKILL
+
+ -u <i>user</i>
+ --user <i>user</i>
+ Kill only processes the specified user owns. Command names are optional.
+
+ -v Report if the signal was successfully sent.
+ --verbose
+
+ -V Display version information.
+ --version
+
+ -w
+ --wait
+ Wait for all killed processes to die. killall checks once per second if any
+ of the killed processes still exist and only returns if none are left.
+ Note that killall may wait forever if the signal was ignored, had no effect, or
+ if the process stays in zombie state.
+
+ -Z <i>pattern</i>
+ --context <i>pattern</i>
+ Specify security context: kill only processes having security context that match
+ with given expended regular expression pattern. Must precede other arguments on
+ the command line. Command names are optional. (SELinux Only)
+
+ -- Each parameter after a '--' parameter is always interpreted as a non-option parameter.</pre>
+<p>killall sends a signal to all processes running any of the specified commands. If no signal name is specified, SIGTERM is sent.</p>
+<p>Signals can be specified either by name (e.g. -HUP) or by number (e.g. -1) or by option -s.</p>
+<p>If the command name is not regular expression (option -r) and contains a slash (/), processes executing that particular file will be selected for killing, independent of their name.</p>
+<p>killall returns a zero return code if at least one process has been killed for each listed command, or no commands were listed and at least one process matched the -u and -Z search criteria. killall returns non-zero otherwise.</p>
+<p>A killall process never kills itself (but may kill other killall processes). </p>
+<p><b>Common kill signals</b></p>
+<table border="1"><thead><tr><th align="LEFT" valign="MIDDLE">Signal name</th><th align="LEFT" valign="MIDDLE">Signal value</th><th align="LEFT" valign="MIDDLE">Effect</th></tr></thead><tbody><tr><td align="LEFT" valign="MIDDLE">SIGHUP</td><td align="LEFT" valign="MIDDLE">1</td><td align="LEFT" valign="MIDDLE">Hangup</td></tr><tr><td align="LEFT" valign="MIDDLE">SIGINT</td><td align="LEFT" valign="MIDDLE">2</td><td align="LEFT" valign="MIDDLE">Interrupt from keyboard</td></tr><tr><td align="LEFT" valign="MIDDLE">SIGKILL</td><td align="LEFT" valign="MIDDLE">9</td><td align="LEFT" valign="MIDDLE">Kill signal</td></tr><tr><td align="LEFT" valign="MIDDLE">SIGTERM</td><td align="LEFT" valign="MIDDLE">15</td><td align="LEFT" valign="MIDDLE">Termination signal</td></tr><tr><td align="LEFT" valign="MIDDLE">SIGSTOP</td><td align="LEFT" valign="MIDDLE">17,19,23</td><td align="LEFT" valign="MIDDLE">Stop the process</td></tr></tbody></table>
+<tbody><tr><th align="LEFT" valign="CENTER"><p><b>Files<br>
+</b>/proc<br>
+location of the proc file system</p>
+<p><b>Known Bugs</b></p>
+<p>Typing<span class="code"> killall <i>name</i></span> may not have the desired effect on non-Linux systems, especially when done by a privileged user. e.g. on Solaris it will kill all active processes.</p>
+<p>Killing by file only works for executables that are kept open during execution, i.e. impure executables can't be killed this way.</p>
+<p>killall -w doesn't detect if a process disappears and is replaced by a new process with the same PID between scans.</p>
+<p>If processes change their name, killall may not be able to match them correctly. </p>
+<p><b>Examples</b></p>
+<p>Kill firefox:</p>
+<p class="code">$ killall -9 mozilla-bin</p>
+<p><b>Related</b>:</p>
+
+<p>ctrl+z - Suspend a program<br>
+ctrl+c - Interrupt a program<br>
+ <a href="ps.html">ps</a> - List running processes (returns PID)<br>
+pgrep - look up or signal processes based on name and other attributes<br>
+<a href="pkill.html">pkill</a> - Signal a process to stop running<br>
+fuser - identify processes using files or sockets<br>
+ jobs - List your own processes (returns Job No.)<br>
+ <a href="bg.html">bg</a> - Put a process in the background<br>
+ <a href="fg.html">fg</a> - Put a process in the foreground<br>
+<a href="kill.html">kill</a> - kill processes</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/less.html b/help/en/bash/less.html
new file mode 100644
index 0000000..0dfa4a3
--- /dev/null
+++ b/help/en/bash/less.html
@@ -0,0 +1,276 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>less MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> less</h1>
+<p>Display output one screen at a time, Search through output, Edit
+the command line.</p>
+<pre>SYNTAX
+ <strong>less</strong> [<em>options</em>]
+
+ &lt;command&gt; | <strong>less</strong> [<em>options</em>]
+
+Moving Commands:
+
+Commands marked with * may be preceded by a number, N.
+Notes in parentheses indicate the behavior if N is given.
+
+ e ^E j ^N CR * Forward one line (or N lines).
+ y ^Y k ^K ^P * Backward one line (or N lines).
+ f ^F ^V SPACE * Forward one window (or N lines).
+ b ^B ESC-v * Backward one window (or N lines).
+ z * Forward one window (and set window to N).
+ w * Backward one window (and set window to N).
+ ESC-SPACE * Forward one window, but don't stop at end-of-file.
+ d ^D * Forward one half-window (and set half-window to N).
+ u ^U * Backward one half-window (and set half-window to N).
+ ESC-( RightArrow * Left 8 character positions (or N positions).
+ ESC-) LeftArrow * Right 8 character positions (or N positions).
+ F Forward forever; like "tail -f".
+ r ^R ^L Repaint screen.
+ R Repaint screen, discarding buffered input.
+
+ h H Display this help.
+ q :q Q :Q ZZ Exit.
+ ---------------------------------------------------
+ Default "window" is the screen height.
+ Default "half-window" is half of the screen height.
+
+ ---------------------------------------------------------------------------
+
+Searching Commands:
+
+ /pattern * Search forward for (N-th) matching line.
+ ?pattern * Search backward for (N-th) matching line.
+ n * Repeat previous search (for N-th occurrence).
+ N * Repeat previous search in reverse direction.
+ ESC-n * Repeat previous search, spanning files.
+ ESC-N * Repeat previous search, reverse dir. & spanning files.
+ ESC-u Undo (toggle) search highlighting.
+ ---------------------------------------------------
+ Search patterns may be modified by one or more of:
+ ^N or ! Search for NON-matching lines.
+ ^E or * Search multiple files (pass thru END OF FILE).
+ ^F or @ Start search at FIRST file (for /) or last file (for ?).
+ ^K Highlight matches, but don't move (KEEP position).
+ ^R Don't use REGULAR EXPRESSIONS.
+ ---------------------------------------------------------------------------
+
+Jumping commands:
+
+ g < ESC-< * Go to first line in file (or line N).
+ G > ESC-> * Go to last line in file (or line N).
+ p % * Go to beginning of file (or N percent into file).
+ { ( [ * Find close bracket } ) ].
+ } ) ] * Find open bracket { ( [.
+ ESC-^F <c1> <c2> * Find close bracket <c2>.
+ ESC-^B <c1> <c2> * Find open bracket <c1>
+ ---------------------------------------------------
+ Each "find close bracket" command goes forward to the close bracket
+ matching the (N-th) open bracket in the top line.
+ Each "find open bracket" command goes backward to the open bracket
+ matching the (N-th) close bracket in the bottom line.
+
+ m<letter> Mark the current position with <letter>.
+ '<letter> Go to a previously marked position.
+ '' Go to the previous position.
+ ^X^X Same as '.
+ ---------------------------------------------------
+ A mark is any upper-case or lower-case letter.
+ Certain marks are predefined:
+ ^ means beginning of the file
+ $ means end of the file
+ ---------------------------------------------------------------------------
+
+Changing files:
+
+ :e [file] Examine a new file.
+ ^X^V Same as :e.
+ :n * Examine the (N-th) next file from the command line.
+ :p * Examine the (N-th) previous file from the command line.
+ :x * Examine the first (or N-th) file from the command line.
+ :d Delete the current file from the command line list.
+ = ^G :f Print current file name.
+ ---------------------------------------------------------------------------
+
+Miscellaneous Commands:
+
+ -<flag> Toggle a command line option [see OPTIONS below].
+ --<name> Toggle a command line option, by name.
+ _<flag> Display the setting of a command line option.
+ __<name> Display the setting of an option, by name.
+ +cmd Execute the less cmd each time a new file is examined.
+
+ !command Execute the shell command with $SHELL.
+ |<b>X</b>command Pipe file between current pos & mark <b>X</b> to shell command.
+ v Edit the current file with $VISUAL or $EDITOR.
+ V Print version number of "less".
+ ---------------------------------------------------------------------------
+
+OPTIONS:
+</pre>
+<p><span class="body"> Most options may be changed either on the command line,
+ or from within less by using the - or -- command.<br>
+ Options may be given in one of two forms: either a single
+ character preceded by a -, or a name preceeded by --.</span></p>
+<pre>
+FINDING:
+
+ -a ........ --search-skip-screen
+ Forward search, skips current screen.
+ -g ........ --hilite-search
+ Highlight only last match for searches.
+ -G ........ --HILITE-SEARCH
+ Don't highlight any matches for searches.
+ -h [N] .... --max-back-scroll=[N]
+ Backward scroll limit.
+ -i ........ --ignore-case
+ Ignore case in searches.
+ -I ........ --IGNORE-CASE
+ Ignore case in searches and in search patterns.
+ -j [N] .... --jump-target=[N]
+ Screen position of target lines.
+ -p [pattern] --pattern=[<em>pattern</em>]
+ Start at pattern (from command line).
+ -t [tag] .. --tag=[tag]
+ Find a tag.
+ -T [tagsfile] --tag-file=[<em>tagsfile</em>]
+ Use an alternate tags file.
+ -y [N] .... --max-forw-scroll=[<em>N</em>]
+ Forward scroll limit.
+
+DISPLAY OPTIONS:
+
+ -D [<em>xn.n</em>] . --color=<em>xn.n</em>
+ Set screen colors. (MS-DOS only)
+ -c -C .... --clear-screen --CLEAR-SCREEN
+ Repaint by scrolling/clearing.
+ -P [<em>prompt</em>] --prompt=[<em>prompt</em>]
+ Define new prompt.
+ -m -M .... --long-prompt --LONG-PROMPT
+ Set prompt style.
+ -n -N .... --line-numbers --LINE-NUMBERS
+ Use line numbers.
+ -r ........ --raw-control-chars
+ Output "raw" control characters.
+ -s ........ --squeeze-blank-lines
+ Squeeze multiple blank lines.
+ -S ........ --chop-long-lines
+ Chop long lines.
+ -w ........ --hilite-unread
+ Highlight first new line after forward-screen.
+ -W ........ --HILITE-UNREAD
+ Highlight first new line after any forward movement.
+ -~ ........ --tilde
+ Don't display tildes after end of file.
+ -z [<em>N</em>] .... --window=[<em>N</em>]
+ Set size of window.
+
+FILE OPTIONS:
+
+ -b [<em>N</em>] .... --buffers=[<em>N</em>]
+ Number of buffers.
+ -B ........ --auto-buffers
+ Don't automatically allocate buffers for pipes.
+ -f ........ --force
+ Force open non-regular files.
+ -k [<em>file</em>] . --lesskey-file=[<em>file</em>]
+ Use a lesskey file.
+ -o [<em>file</em>] . --log-file=[<em>file</em>]
+ Copy to log file (standard input only).
+ -O [<em>file</em>] . --LOG-FILE=[<em>file</em>]
+ Copy to log file (unconditionally overwrite).
+
+MISC OPTIONS:
+
+ -d ........ --dumb
+ Dumb terminal.
+ -e -E .... --quit-at-eof --QUIT-AT-EOF
+ Quit at end of file.
+ -q -Q .... --quiet --QUIET --silent --SILENT
+ Quiet the terminal bell.
+ -u -U .... --underline-special --UNDERLINE-SPECIAL
+ Change handling of backspaces.
+ -x [<em>N</em>] .... --tabs=[<em>N</em>]
+ Set tab stops.
+ -X ........ --no-init
+ Don't use termcap init/deinit strings.
+ -" [<em>c</em>[<em>c</em>]] . --quotes=[<em>c</em>[<em>c</em>]]
+ Set shell quote characters.
+ -? ........ --help
+ Display help (from command line).
+ -V ........ --version
+ Display the version number of "less".
+ ---------------------------------------------------------------------------
+
+Line Editing:
+
+ These keys can be used to edit text being entered
+ on the "command line" at the bottom of the screen.
+
+ RightArrow ESC-l Move cursor right one character.
+ LeftArrow ESC-h Move cursor left one character.
+ CNTL-RightArrow ESC-RightArrow ESC-w Move cursor right one word.
+ CNTL-LeftArrow ESC-LeftArrow ESC-b Move cursor left one word.
+ HOME ESC-0 Move cursor to start of line.
+ END ESC-$ Move cursor to end of line.
+ BACKSPACE Delete char to left of cursor.
+ DELETE ESC-x Delete char under cursor.
+ CNTL-BACKSPACE ESC-BACKSPACE Delete word to left of cursor.
+ CNTL-DELETE ESC-DELETE ESC-X Delete word under cursor.
+ CNTL-U ESC (MS-DOS only) Delete entire line.
+ UpArrow ESC-k Retrieve previous command line.
+ DownArrow ESC-j Retrieve next command line.
+ TAB Complete filename & cycle.
+ SHIFT-TAB ESC-TAB Complete filename & reverse cycle.
+ CNTL-L Complete filename, list all.</pre>
+<p><i>&ldquo;Counter to the widely held belief that industrial agriculture is more efficient and productive, small farms produce far more per acre than large farms&rdquo; - <a href="http://www.cnr.berkeley.edu/%7Echristos/articles/cv_organic_farming.html">Christos Vasilikiotis</a></i><a href="http://www.cnr.berkeley.edu/%7Echristos/articles/cv_organic_farming.html"><br>
+ </a><br>
+ <b> Related</b>:<br>
+ <br>
+ <a href="echo.html">echo</a> - Display message on screen<br>
+ <a href="head.html">head</a> - Output the first part of file(s)<br>
+ <a href="more.html">more</a> - Display output one screen at a time <br>
+ pg - Display one page at a time<br>
+ <a href="tee.html">tee</a> - Redirect output to multiple files <br>
+Equivalent Windows command:
+<a href="../term_tools/nt/more.html">MORE</a> - Display output one screen at a time.</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/let.html b/help/en/bash/let.html
new file mode 100644
index 0000000..410404f
--- /dev/null
+++ b/help/en/bash/let.html
@@ -0,0 +1,59 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>let MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> let</h1>
+<p> Perform arithmetic on shell variables.</p>
+<pre>Syntax
+ let <var>expression</var> [<var>expression</var>]</pre>
+<p> Each <var>expression</var> is an arithmetic expression to be evaluated. If the last <var>expression</var> evaluates to 0, <code>let</code>
+ returns 1; otherwise 0 is returned.<br>
+ <br>
+ `let' is a bash builtin command.</p>
+<p><i>&quot;Arithmetic is being able to count up to twenty without
+ taking off your shoes.&quot; - Mickey
+Mouse</i></p>
+<p><b>Related</b>:<br>
+ <br>
+ <a href="expr.html">expr</a> - Evaluate expressions <a href="eval.html"><br>
+ eval</a> - Evaluate several commands/arguments<br>
+<a href="test.html">test</a> - Evaluate a conditional expression </p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/ln.html b/help/en/bash/ln.html
new file mode 100644
index 0000000..053a307
--- /dev/null
+++ b/help/en/bash/ln.html
@@ -0,0 +1,161 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>ln MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> ln</h1>
+<p>Make links between files, by default, it makes hard links; with
+the `-s' option, it makes symbolic (or "soft") links.</p>
+<pre>Syntax
+ ln [<em>Options</em>]... <em>target</em> [<em>Linkname</em>]
+
+ ln [<em>Options</em>]... <em>target</em>... <em>Directory</em>
+
+Options
+ -b
+ --backup
+ Make a backup of each file that would otherwise be overwritten or
+ removed. *Note Backup options::.
+
+ -d
+ -F
+ --directory
+ Allow the super-user to make hard links to directories.
+
+ -f
+ --force
+ Remove existing destination files.
+
+ -i
+ --interactive
+ Prompt whether to remove existing destination files.
+
+ -n
+ --no-dereference
+ When given an explicit destination that is a symlink to a
+ directory, treat that destination as if it were a normal file.
+
+ When the destination is an actual directory (not a symlink to one),
+ there is no ambiguity. The link is created in that directory.
+ But when the specified destination is a symlink to a directory,
+ there are two ways to treat the user's request. `ln' can treat
+ the destination just as it would a normal directory and create the
+ link in it. On the other hand, the destination can be viewed as a
+ non-directory--as the symlink itself. In that case, `ln' must
+ delete or backup that symlink before creating the new link. The
+ default is to treat a destination that is a symlink to a directory
+ just like a directory.
+
+ -s
+ --symbolic
+ Make symbolic links instead of hard links. This option merely
+ produces an error message on systems that do not support symbolic
+ links.
+
+ -S SUFFIX
+ --suffix=SUFFIX
+ Append SUFFIX to each backup file made with `-b'. *Note Backup
+ options::.
+
+ -v
+ --verbose
+ Print the name of each file before linking it.
+
+ -V METHOD
+ --version-control=METHOD
+ Change the type of backups made with `-b'. The METHOD argument
+ can be `numbered' (or `t'), `existing' (or `nil'), or `never' (or
+ `simple').
+</pre>
+<p><span class="body"> * If the last argument names an existing directory, `ln' creates a
+ link to each TARGET file in that directory, using the TARGETs'<br>
+ names. (But see the description of the `--no-dereference' option
+ below.)<br>
+ <br>
+ * If two filenames are given, `ln' creates a link from the second to
+ the first.<br>
+ <br>
+ * If one TARGET is given, `ln' creates a link to that file in the
+ current directory.<br>
+ <br>
+ * It is an error if the last argument is not a directory and more
+ than two files are given. Without `-f' or `-i' (see below), `ln'
+ will not remove an existing file. Use the `--backup' option to
+ make `ln' rename existing files.<br>
+ <br>
+ A "hard link" is another name for an existing file; the link and the
+ original are indistinguishable. Technically speaking, they share the
+ same inode, and the inode contains all the information about a
+ file--indeed, it is not incorrect to say that the inode _is_ the file.<br>
+ On all existing implementations, you cannot make a hard link to a
+ directory, and hard links cannot cross filesystem boundaries. (These
+ restrictions are not mandated by POSIX, however.)<br>
+ <br>
+"Symbolic links" ("symlinks" for short), on the other hand, are a
+ special file type (which not all kernels support: System V release 3
+ (and older) systems lack symlinks) in which the link file actually
+ refers to a different file, by name. When most operations (opening,
+ reading, writing, and so on) are passed the symbolic link file, the
+ kernel automatically "dereferences" the link and operates on the target
+ of the link. But some operations (e.g., removing) work on the link
+file itself, rather than on its target.</span></p>
+<p><b>Examples</b></p>
+<pre>$ ln file1.txt link1
+$ rm file1.txt #The file cannot be deleted until the link is removed.
+
+$ ln -s /some/name # create a link ./name pointing to /some/name
+$ ln -s /some/name mylink2 # or give the link a name
+
+$ ln -s /home/simon/demo /home/jules/mylink3 #Create mylink3 pointing to demo
+
+$ ln -s item1 item2 .. # creates links ../item1 and ../item2 pointing to ./item1 and ./item2</pre>
+<p>If you delete a file for which a symbolic link still exists, the <span class="telety">rm</span> will succeed but the symbolic link would remain and any attempt to reference it will return a 'file not found' error. </p>
+<p><i>&quot;Arithmetic is being able to count up to twenty without
+ taking off your shoes.&quot; - Mickey
+ Mouse</i><br>
+ <br>
+ <b> Related</b>:<br>
+ <br>
+ pathchk - Check file name portability<br>
+ <a href="symlink.html">symlink</a> - Make a new name for a file <br>
+Equivalent Windows commands:
+ <a href="../term_tools/nt/shortcut.html">SHORTCUT</a> - Create a windows shortcut (.LNK
+file)</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/local.html b/help/en/bash/local.html
new file mode 100644
index 0000000..948b9c5
--- /dev/null
+++ b/help/en/bash/local.html
@@ -0,0 +1,71 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>local MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> local</h1>
+<p>Create variables</p>
+<pre>SYNTAX
+ local [<var>option</var>] <var>name</var>[=<var>value</var>]</pre>
+<p> For each argument, a local variable named <var>name</var> is created, and
+ assigned <var>value</var>. <br>
+ <br>
+ The <var>option</var> can be any of the options accepted by <a href="declare.html">declare</a>.
+ <code><br>
+ <br>
+ local</code> can only be used within a function; it makes the variable <var>name</var>
+ have a visible scope restricted to that function and its children. <br>
+ <br>
+ The return status is zero unless <code>local</code> is used outside a function,
+ an invalid <var>name</var> is supplied, or <var>name</var> is a readonly variable.
+</p>
+<p>`local' is a BASH builtin command.</p>
+<p><i>&quot;A local shop for local people&quot; - The
+ League Of Gentlemen</i></p>
+<p><b>Related</b>:<br>
+ <a href="declare.html">declare</a> - Declare variables and give them attributes<a href="env.html"><br>
+ env</a> - Display, set, or remove environment variables<br>
+ <a href="export.html">export</a> - Set an environment variable<br>
+ <a href="function.html">function</a> - Define Function Macros <br>
+ <a href="readonly.html">readonly</a> - Mark variables/functions as readonly<br>
+ <a href="set.html">set</a> - Manipulate shell variables and functions <br>
+ Equivalent Windows commands: <a href="../term_tools/nt/set.html">SET</a> - Display, set, or remove environment
+ variable</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/locate.html b/help/en/bash/locate.html
new file mode 100644
index 0000000..e47b235
--- /dev/null
+++ b/help/en/bash/locate.html
@@ -0,0 +1,71 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>Locate - find files MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1>locate</h1>
+<p>Find files. </p>
+<pre>Syntax
+ locate [<i>options</i>]<i> pattern</i>
+
+Options
+
+ -d path, --database=path
+ Search databases in path.
+ path must be a colon- separated list.
+
+ -h, --help Print a help message and exit.
+
+ --version Print version information and then exit.
+</pre>
+<p>Search database(s) of filenames and print matches. *, ?, [, and
+ ] are treated specially; / and . are not. </p>
+<p>Matches include all files that contain pattern, unless pattern
+ includes metacharacters, in which case locate requires an exact match.</p>
+<p> If locate does not work, run the command: <a href="slocate.html">slocate -u</a> to rebuild the index </p>
+<p><b>Related</b>:</p>
+<p>udpatedb - Update the database for locate (usually run daily by <a href="cron.html">cron</a> to update the default database.)<br>
+ <a href="slocate.html">slocate</a> - Security Enhanced version of GNU Locate
+ (users won't see files they don't have access to.)<br>
+ <a href="find.html"> find</a> - Search for files that meet a desired criteria<br>
+ fnmatch<br>
+ weekly.conf<br>
+Equivalent Windows command: <a href="dir.html">DIR</a> /S - Display a list of files and folders</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/logname.html b/help/en/bash/logname.html
new file mode 100644
index 0000000..1dacfa8
--- /dev/null
+++ b/help/en/bash/logname.html
@@ -0,0 +1,68 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>logname MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> logname</h1>
+<p>Print current login name</p>
+<pre>SYNTAX
+ logname
+</pre>
+<p>Prints the calling user's name, as found in the file`/var/run/utmp', and exits with a status of 0.<br>
+ <br>
+ If there is no `/var/run/utmp' entry for the calling process, `logname' prints an error message and exits with a status of 1.<br>
+ <br>
+ The only options are `--help' and `--version'.</p>
+<p><i>&quot;What passes for identity in America is a series of myths
+ about one's heroic ancestors&quot; - James
+ Baldwin</i></p>
+<p><b>Related</b>:<br>
+ <a href="env.html"><br>
+ env</a> - Display, set, or remove environment variables <br>
+ <a href="groups.html">groups</a> - Print group names a user is in<br>
+ <a href="hostname.html">hostname</a> - Print or set system name <br>
+ <a href="id.html">id</a> - Print user and group id's<br>
+ <a href="uname.html">uname</a> - Print system information <br>
+ <a href="users.html">users</a> - Print login names of users currently logged
+ in <br>
+ <a href="who.html">who</a> - Print who is currently logged in <br>
+ whoami - Print the current user id and name (`id -un') <br>
+Equivalent Windows command: <a href="../term_tools/nt/echo.html">ECHO</a> %username% </p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/logout.html b/help/en/bash/logout.html
new file mode 100644
index 0000000..182f0ab
--- /dev/null
+++ b/help/en/bash/logout.html
@@ -0,0 +1,75 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>logout MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> logout</h1>
+<p>Exit a login shell.</p>
+<pre>SYNTAX
+ logout [<var>n</var>]</pre>
+<p>Returns a status of <var>n</var> to the shell's parent. </p>
+<p>A login shell, is your topmost shell, and is started when
+you log in. </p>
+<p>When you terminate a login shell (via the commands `exit', `logout,' or the end of file [^D]), you are logged out completely. </p>
+<p>Sub-Shells</p>
+<p>A
+ `sub-shell' is a shell created after login, either by loading a new shell or opening a window with a graphics interface. A sub-shell usually will not
+ accept the command `logout' to terminate, you must use `exit' or ^D.<br>
+ When you terminate a sub-shell, you are returned to the process or shell
+that created it. </p>
+<p>Example (starting from a bash shell) <br>
+ $ tcsh<br>
+ % # now in the tcsh shell <br>
+ % exit<br>
+ $
+ # now back in the bash shell <br>
+ $ logout
+ <br>
+ <br>
+ <i>&quot;We want the finest wines available to humanity. And we want them here
+ and we want them now&quot; - Bruce
+ Robinson / Withnail and I </i> </p>
+<p><b> Related</b>:</p>
+<p>exit - Exit session<br>
+&lt;ctrl&gt;&lt;d&gt; - End of File <br>
+ <a href="logname.html"> logname</a> - Print current login name<br>
+Equivalent Windows command:
+EXIT - Quit the CMD shell</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/look.html b/help/en/bash/look.html
new file mode 100644
index 0000000..56c1d18
--- /dev/null
+++ b/help/en/bash/look.html
@@ -0,0 +1,68 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>look MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1>look</h1>
+<p>Display any lines in file which contain <i>string</i> as a prefix. </p>
+<pre>Syntax
+ look [-df] [-t <i>termchar</i>] <i>string</i> [<i>file</i>]
+
+ As look performs a binary search, the lines in <i>file</i> must be sorted.
+
+Options:
+
+ -d Dictionary character set and order, i.e. only alphanumeric characters are compared.
+
+ -f Ignore the case of alphabetic characters (UPPER/lower).
+
+ -t Specify a string termination character, i.e. only the characters
+ in <i>string </i>up to and including the first occurrence of <i>termchar</i> are compared.
+</pre>
+<p> If <i>file</i> is not specified, the dictionary file <span class="telety">/usr/share/dict/words</span> is used, only alphanumeric characters are compared and the case of alphabetic characters is ignored.</p>
+<p>Exits 0 if one or more lines were found and displayed, 1 if no lines were found, and >1 if an error occurred.</p>
+<p>The return status is the exit status of the last command executed
+in <var>consequent-commands</var>, or zero if none were executed. </p>
+<p><em>&quot;One's destination is never a place but rather a new way of looking at things&quot; - Henry Miller</em></p>
+<p><b>Related</b>:</p>
+<p><a href="for.html"> </a><a href="grep.html">grep</a> Search file(s) for lines that match a given pattern<a href="case.html"><br>
+ </a><a href="sort.html">sort</a> Sort text files<br>
+ Equivalent Windows command: <a href="../term_tools/nt/find.html">FIND</a> - Search for a text string in a file</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/lpc.html b/help/en/bash/lpc.html
new file mode 100644
index 0000000..79e23c5
--- /dev/null
+++ b/help/en/bash/lpc.html
@@ -0,0 +1,156 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>lpc MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> lpc</h1>
+<p>line printer control program</p>
+<pre>SYNTAX
+ lpc [<em>command</em> [<em>argument</em> ...]]
+
+DESCRIPTION
+ Lpc is used by the system administrator to control the operation of the
+ line printer system. For each line printer configured in /etc/printcap,
+ lpc may be used to:
+
+ · Disable or enable a printer,
+
+ · Disable or enable a printer's spooling queue,
+
+ · Rearrange the order of jobs in a spooling queue,
+
+ · Find the status of printers, and their associated spooling
+ queues and printer dameons.
+</pre>
+<p>Without any arguments, lpc will prompt for commands from the standard input. If arguments are supplied, lpc interprets the first argument as a
+command and the remaining arguments as parameters to the command. The
+standard input may be redirected causing lpc to read commands from file.<br>
+Commands may be abreviated; </p>
+<pre>
+COMMANDS
+
+ ? [command ...]
+ help [command ...]
+ Print a short description of each command specified in the argument list, or,
+ if no arguments are given, a list of the recognized commands.
+
+ abort { all | printer }
+ Terminate an active spooling daemon on the local host immediately
+ and then disable printing (preventing new daemons from being
+ started by lpr) for the specified printers.
+
+ clean { all | printer }
+ Remove any temporary files, data files, and control files that
+ cannot be printed (i.e., do not form a complete printer job) from
+ the specified printer queue(s) on the local machine.
+
+ disable { all | printer }
+ Turn the specified printer queues off. This prevents new printer
+ jobs from being entered into the queue by lpr.
+
+ down { all | printer } message ...
+ Turn the specified printer queue off, disable printing and put
+ message in the printer status file. The message doesn't need to
+ be quoted, the remaining arguments are treated like echo(1).
+ This is normally used to take a printer down and let others know
+ why lpq(1) will indicate the printer is down and print the status
+ message).
+
+ enablee { all | printer }
+ Enable spooling on the local queue for the listed printers. This
+ will allow lpr(1) to put new jobs in the spool queue.
+
+ exit
+ quit Exit from lpc.
+
+
+ restart { all | printer }
+ Attempt to start a new printer daemon. This is useful when some
+ abnormal condition causes the daemon to die unexpectedly leaving
+ jobs in the queue. Lpq will report that there is no daemon present
+ when this condition occurs. If the user is the super-user,
+ try to abort the current daemon first (i.e., kill and restart a
+ stuck daemon).
+
+ start { all | printer }
+ Enable printing and start a spooling daemon for the listed printers.
+
+ status { all | printer }
+ Display the status of daemons and queues on the local machine.
+
+ stop { all | printer }
+ Stop a spooling daemon after the current job completes and disable
+ printing.
+
+ topq printer [ jobnum ... ] [ user ... ]
+ Place the jobs in the order listed at the top of the printer
+ queue.
+
+ up { all | printer }
+ Enable everything and start a new printer daemon. Undoes the effects
+ of down.
+
+FILES
+ /etc/printcap printer description file
+ /var/spool/* spool directories
+ /var/spool/*/lock lock file for queue control
+
+ERROR Messages
+
+ ?Ambiguous command
+ abbreviation matches more than one command
+
+ ?Invalid command
+ no match was found
+
+ ?Privileged command
+ command can be executed by root only</pre>
+<p><em>&quot;There's a thin line between being committed and being committed&quot;
+- ComputerBob, 1992 </em></p>
+<p><b>Related</b>:<br>
+ <br>
+ <a href="lpr.html">lpr</a> - Off line print <br>
+ lprint - Print a file<br>
+ lprintd / lpd(8) - Abort a print job<br>
+ lprintq / lpq(1) - List the print queue<br>
+ <a href="lprm.html">lprm</a> - Remove jobs from the print queue <br>
+ printcap(5) - Printer Capability database<br>
+Equivalent Windows command: <a href="../term_tools/nt/prncnfg.html">PRNCNFG</a> - Display, configure or rename a printer</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/lpr.html b/help/en/bash/lpr.html
new file mode 100644
index 0000000..e66b6a8
--- /dev/null
+++ b/help/en/bash/lpr.html
@@ -0,0 +1,190 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>lpr MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> lpr</h1>
+<p>off line print - sends a print job to the default system queue.</p>
+<pre>SYNTAX
+ lpr [-P<em>printer</em>] [-#<em>num</em>] [-C <em>class</em>] [-J <em>job</em>] [-T <em>title</em>] [-U <em>user</em>] [-i [<em>numcols</em>]]
+ [-1234 <em>font</em>] [-w<em>num</em>] [-cdfghlnmprstv] [name ...]
+
+DESCRIPTION
+ Lpr uses a spooling daemon to print the named files when facilities become
+ available. If no names appear, the standard input is assumed.
+
+ The following single letter options are used to notify the line printer
+ spooler that the files are not standard text files. The spooling daemon
+ will use the appropriate filters to print the data accordingly.
+
+ -c The files are assumed to contain data produced by cifplot(1)
+
+ -d The files are assumed to contain data from tex (DVI format from
+ Stanford).
+
+ -f Use a filter which interprets the first character of each line as
+ a standard FORTRAN carriage control character.
+
+ -g The files are assumed to contain standard plot data as produced
+ by the plot routines (see also plot for the filters used by the
+ printer spooler).
+
+ -l Use a filter which allows control characters to be printed and
+ suppresses page breaks.
+
+ -n The files are assumed to contain data from ditroff (device independent
+ troff).
+
+ -p Use pr(1) to format the files (equivalent to print).
+
+ -t The files are assumed to contain data from troff(1) (cat photo-
+ typesetter commands).
+
+ -v The files are assumed to contain a raster image for devices like
+ the Benson Varian.
+
+ These options apply to the handling of the print job:
+
+ -P Force output to a specific printer. Normally, the default printer
+ is used (site dependent), or the value of the environment
+ variable PRINTER is used.
+
+ -h Suppress the printing of the burst page.
+
+ -m Send mail upon completion.
+
+ -r Remove the file upon completion of spooling. Can not be used with
+ the -s option, due to security concerns.
+
+ -s Use symbolic links. Usually files are copied to the spool directory.
+ The -s option will use symlink(2) to link data files
+ rather than trying to copy them so large files can be printed.
+ This means the files should not be modified or removed until they
+ have been printed.
+
+ The remaining options apply to copies, the page display, and headers:
+
+ -#<em>num</em> The quantity num is the number of copies desired of each file
+ named. For example,
+
+ lpr -#3 foo.c bar.c more.c
+
+ would result in 3 copies of the file foo.c, followed by 3 copies
+ of the file bar.c, etc. On the other hand,
+
+ cat foo.c bar.c more.c | lpr -#3
+
+ will give three copies of the concatenation of the files. Often a
+ site will disable this feature to encourage use of a photocopier
+ instead.
+
+ -[1234]<em>font</em>
+ Specifies a font to be mounted on font position i. The daemon
+ will construct a .railmag file referencing the font pathname.
+
+ -C <em>class</em>
+ Job classification to use on the burst page. For example,
+
+ lpr -C EECS foo.c
+
+ causes the system name (the name returned by hostname(1)) to be
+ replaced on the burst page by EECS, and the file foo.c to be
+ printed.
+
+ -J <em>job</em> Job name to print on the burst page. Normally, the first file's
+ name is used.
+
+ -T <em>title</em>
+ Title name for pr(1), instead of the file name.
+
+ -U <em>user</em>
+ User name to print on the burst page, also for accounting purposes.
+ This option is only honored if the real user-id is daemon
+ (or that specified in the printcap file instead of daemon), and
+ is intended for those instances where print filters wish to requeue
+ jobs.
+
+ -i [<em>numcols</em>]
+ The output is indented. If the next argument is numeric
+ (<em>numcols</em>), it is used as the number of blanks to be printed before
+ each line; otherwise, 8 characters are printed.
+
+ -w<em>num</em> Uses <em>num</em> as the page width for pr(1).
+
+Environment
+ If the following environment variable exists, it is used by lpr:
+
+ PRINTER Specifies an alternate default printer.
+
+Files
+ /etc/passwd Personal identification.
+ /etc/printcap Printer capabilities data base.
+ /usr/sbin/lpd* Line printer daemons.
+ /var/spool/output/* Directories used for spooling.
+ /var/spool/output/*/cf* Daemon control files.
+ /var/spool/output/*/df* Data files specified in "cf" files.
+ /var/spool/output/*/tf* Temporary copies of "cf" files.
+
+Diagnostics
+ If you try to spool too large a file, it will be truncated. Lpr will object
+ to printing binary files. If a user other than root prints a file
+ and spooling is disabled, lpr will print a message saying so and will not
+ put jobs in the queue. If a connection to lpd(1) on the local machine
+ cannot be made, lpr will say that the daemon cannot be started. Diagnostics
+ may be printed in the daemon's log file regarding missing spool
+ files by lpd(1).
+
+Bugs
+ Fonts for troff(1) and tex reside on the host with the printer. It is
+ currently not possible to use local font libraries.</pre>
+<p><b>Related</b>:<br>
+ <br>
+ banner - Print a line of text in extra large (poster size)<br>
+ cancel - Cancel request to printer<br>
+ <a href="lpc.html">lpc</a> - Line printer control program<br>
+ lprint - Print a file<br>
+ lprintd / lpd(8) - Abort a print job<br>
+ lprintq / lpq(1) - List the print queue<br>
+ <a href="lprm.html">lprm</a> - Remove jobs from the print queue <br>
+ pr(1) - Convert text files for printing <br>
+ printcap(5) - Printer Capability database<br>
+ <a href="symlink.html">symlink</a> - Make a new name for a file <br>
+ Equivalent Windows commands: <a href="../term_tools/nt/prncnfg.html">PRNCNFG</a> - Display, configure or rename a printer</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/lprm.html b/help/en/bash/lprm.html
new file mode 100644
index 0000000..2494437
--- /dev/null
+++ b/help/en/bash/lprm.html
@@ -0,0 +1,122 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>lprm MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> lprm</h1>
+<p>Remove jobs from the line printer spooling queue</p>
+<pre>Syntax
+ lprm [-P<em>printer</em>] [-] [<em>job# </em>...] [<em>user</em> ...]
+
+Options and arguments:
+
+ -P<em>printer</em>
+ Specify the queue associated with a specific printer (otherwise
+ the default printer is used).
+
+ - If a single `-' is given, lprm will remove all jobs which a user
+ owns. If the super-user employs this flag, the spool queue will
+ be emptied entirely.
+
+ <em>user</em> Causes lprm to attempt to remove any jobs queued belonging to
+ that user (or users). This form of invoking lprm is useful only
+ to the super-user.
+
+ <em>job#</em> A user may dequeue an individual job by specifying its job number.
+ This number may be obtained from the lpq(1) program, e.g.
+
+ % lpq -l
+
+ 1st:ken [job #013ucbarpa]
+ (standard input) 100 bytes
+ % lprm 13
+
+ If neither arguments or options are given, lprm will delete the currently
+ active job if it is owned by the user who invoked lprm.
+
+ lprm announces the names of any files it removes and is silent if there
+ are no jobs in the queue which match the request list.
+
+ lprm will kill off an active daemon, if necessary, before removing any
+ spooling files. If a daemon is killed, a new one is automatically
+ restarted upon completion of file removals.
+
+Environment
+ If the following environment variable exists, it is utilized by lprm.
+
+ PRINTER If the environment variable PRINTER exists, and a printer has
+ not been specified with the -P option, the default printer is
+ assumed from PRINTER.
+
+Files
+ /etc/printcap Printer characteristics file.
+ /var/spool/* Spooling directories.
+ /var/spool/*/lock Lock file used to obtain the pid of the current daemon
+ and the job number of the currently active job.
+</pre>
+<p><span class="body"> Lprm will remove a job, or jobs, from a printer's spool queue. </span></p>
+<p><span class="body">Since the
+ spooling directory is protected from users, using Lprm is normally the
+ only method by which a user may remove a job. </span></p>
+<p><span class="body">The owner of a job is determined by the user's login name and host name on the machine where the
+ lpr command was invoked.</span></p>
+<p><span class="body">Bug:
+since there are race conditions possible in the update of the lock file,
+the currently active job may be incorrectly identified.<br>
+ <br>
+ ERROR Messages:
+ `Permission denied' if the user tries to remove files other than their own.</span></p>
+<p><i>"Because I could not stop for Death - <br>
+ He kindly stopped for me<br>
+ The carriage held but just ourselves - <br>
+ And Immortality...&quot; - Emily
+ Dickinson</i></p>
+<p><b>Related</b>:<br>
+ <br>
+ <a href="lpc.html">lpc</a> - Line printer control program<br>
+ <a href="lpr.html">lpr</a> - Off line print <br>
+ lprint - Print a file<br>
+ lprintd / lpd(8) - Abort a print job<br>
+ lprintq / lpq(1) - List the print queue<br>
+ pr(1) - Convert text files for printing <br>
+ printcap(5) - Printer Capability database<br>
+ <a href="symlink.html">symlink</a> - Make a new name for a file <br>
+Equivalent Windows command: <a href="../term_tools/nt/net.html">NET</a> PRINT - Manage print jobs</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/ls.html b/help/en/bash/ls.html
new file mode 100644
index 0000000..8f5d7f0
--- /dev/null
+++ b/help/en/bash/ls.html
@@ -0,0 +1,212 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>ls MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> ls</h1>
+<p>List information about files.</p>
+<pre>Syntax
+ ls [<em>Options</em>]... [<em>File</em>]...
+
+Key
+ Sort entries alphabetically if none of -cftuSUX nor --sort.
+
+ -a, --all Do not hide entries starting with .
+
+ -A, --almost-all Do not list implied . and ..
+
+ -b, --escape Print octal escapes for nongraphic characters
+
+ --block-size=<em>SIZE</em> Use <em>SIZE</em>-byte blocks
+
+ -B, --ignore-backups Do not list implied entries ending with ~
+
+ -c Sort by change time; with -l: show ctime
+
+ -C List entries by columns
+
+ --color[=<em>WHEN</em>] Control whether color is used to distinguish file
+ types. WHEN may be `never', `always', or `auto'
+
+ -d, --directory List directory entries instead of contents
+
+ -D, --dired Generate output designed for Emacs' dired mode
+
+ -f Do not sort, enable -aU, disable -lst
+
+ -F, --classify Append indicator (one of */=@|) to entries
+
+ --format=<em>WORD</em> Across -x, commas -m, horizontal -x, long -l,
+ single-column -1, verbose -l, vertical -C
+
+ --full-time List both full date and full time
+
+ -g (ignored)
+
+ -G, --no-group Inhibit display of group information
+
+ -h, --human-readable Print sizes in human readable format (e.g., 1K 234M 2G)
+ -H, --si Likewise, but use powers of 1000 not 1024
+
+ --indicator-style=<em>WORD</em> Append indicator with style <em>WORD</em> to entry names:
+ none (default), classify (-F), file-type (-p)
+
+ -i, --inode Print index number of each file
+
+ -I, --ignore=<em>PATTERN</em> Do not list implied entries matching shell <em>PATTERN</em>
+
+ -k, --kilobytes Like --block-size=1024
+
+ -l Use a long listing format
+
+ -L, --dereference List entries pointed to by symbolic links
+
+ -m Fill width with a comma separated list of entries
+
+ -n, --numeric-uid-gid List numeric UIDs and GIDs instead of names
+
+ -N, --literal Print raw entry names (don't treat e.g. control
+ characters specially)
+
+ -o Use long listing format without group info
+
+ -p, --file-type Append indicator (one of /=@|) to entries
+
+ -q, --hide-control-chars Print ? instead of non graphic characters
+
+ --show-control-chars Show non graphic characters as-is (default)
+
+ -Q, --quote-name Enclose entry names in double quotes
+ --quoting-style=<em>WORD</em> Use quoting style <em>WORD</em> for entry names:
+ literal, shell, shell-always, c, escape
+
+ -r, --reverse Reverse order while sorting
+
+ -R, --recursive List subdirectories recursively
+
+ -s, --size Print size of each file, in blocks
+
+ -S Sort by file size
+
+ --sort=<em>WORD</em> time -t, version -v, status -c
+ size -S, extension -X, none -U
+ atime -u, access -u, use -u
+
+ --time=<em>WORD</em> Show time as <em>WORD</em> instead of modification time:
+ atime, access, use, ctime or status;
+ also use this as a sort key if --sort=time
+
+ -t sort by modification time
+
+ -T, --tabsize=<em>COLS</em> assume tab stops at each <em>COLS</em> instead of 8
+
+ -u sort by last access time; with -l: show atime
+
+ -U do not sort; list entries in directory order
+
+ -v sort by version
+
+ -w, --width=<em>COLS</em> assume screen width instead of current value
+
+ -x list entries by lines instead of by columns
+
+ -X sort alphabetically by entry extension
+
+ -1 list one file per line
+
+ --help display help and exit
+
+ --version output version information and exit</pre>
+<p><span class="body"> The most common options are -a (all files) and -l (long
+ or details)<br>
+ <br>
+ When output to file the files are listed one per line. <br>
+ <br>
+ By default, colour is not used to distinguish types of files. That is equivalent
+ to using --color=none. <br>
+ Using the --color option without the optional WHEN argument is equivalent to
+ using --color=always. <br>
+ With --color=auto, color codes are output only if standard output is connected
+to a terminal (tty).</span></p>
+<p><b>Examples</b></p>
+<pre># List the contents of your home directory
+<b>$ ls ~</b>
+
+# list everything in a vertical list:
+<b>$ ls -al</b>
+
+total 109
+drwxr-xr-x 18 root root 4096 Jun 9 21:12 ./
+drwxr-xr-x 18 root root 4096 Jun 9 21:12 ../
+drwxr-xr-x 2 root root 4096 Jun 9 21:14 bin/
+drwxr-xr-x 3 root root 1024 Jun 9 20:32 boot/
+drwxr-xr-x 6 root root 36864 Jul 12 10:26 dev/
+drwxr-xr-x 34 root root 4096 Jul 12 10:25 etc/
+^
+the first column is the file type
+d = directory
+f = file
+
+# List the directories in the current directory:
+<b>$ ls -d */</b>
+
+# list ALL subdirectories
+<b>$ ls *</b></pre>
+<p>The default behaviour of <span class="telety">ls</span> is to only pass color control codes to tty output <span class="telety">--color=auto</span>.<br>
+To pipe the output to a second command complete with color codes then set <span class="body"><span class="telety">--color=always</span></span></p>
+<p class="telety"><b>$ ls -lAXh --color=auto</b>|less -R</p>
+<p>A list of <a href="../term_tools/bash/lsenv.html">environment variables that affect ls</a> (colour, column width, blocksize etc) </p>
+<p><i> &quot;If the doors of perception were cleansed every thing
+ would appear to man as it is, infinite&quot; - William
+ Blake</i></p>
+<p><b>Related</b>:<br>
+ <br>
+ <a href="dir.html">dir</a> - Briefly list directory contents<br>
+ <a href="dircolours.html">dircolors</a> - Colour setup for `ls' <br>
+ <a href="dirname.html">dirname</a> - Convert a full pathname to just a path<br>
+ lspci - List PCI devices
+ <br>
+ <a href="quota.html">quota</a> - Display disk usage and limits <br>
+ <a href="rm.html">rm</a> - Remove files <a href="rmdir.html"><br>
+ rmdir</a> - Remove folder(s) <br>
+ <a href="wc.html">wc</a> - Print byte, word, and line counts <br>
+Equivalent Windows command: <a href="../term_tools/nt/dir.html">
+ DIR</a> - Display a list of files and folders</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/lsof.html b/help/en/bash/lsof.html
new file mode 100644
index 0000000..bfa1e12
--- /dev/null
+++ b/help/en/bash/lsof.html
@@ -0,0 +1,1194 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>lsof MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> lsof</h1>
+<p>List open files.</p>
+<pre>Syntax
+ lsof [ -?abChlnNOPRstUvVX ] [ -A A ] [ -c c ] [ +c c ] [ +|-d d ]
+ [ +|-D D ] [ +|-f [cfgGn] ] [ -F [f] ] [ -g [s] ] [ -i[i] ]
+ [ -k k ] [ +|-L [l] ] [ +|-m m ] [ +|-M ] [ -o [o] ] [ -p s ]
+ [ +|-r [t] ] [ -S [t] ] [ -T [t] ] [ -u s ] [ +|-w ]
+ [ -x [fl] ] [ -z [z] ] [ -Z [Z] ] [ -- ] [<i>filenames</i>] </pre>
+<p><span class="body"> Jump to <a href="#examples">examples</a> <br>
+An open file may be a regular file, a directory, a block special file, a character special file, an executing text reference, a library, a stream or a network file (Internet socket, NFS file or UNIX domain socket.) A specific file or all the files in a file system may be selected by path.</span></p>
+<p>Instead of a formatted display, lsof will produce output that can be parsed by other programs. See the -F, option description, and the OUTPUT FOR OTHER PROGRAMS section for more information.</p>
+<p>In addition to producing a single output list, lsof will run in repeat mode. In repeat mode it will produce output, delay, then repeat the output operation until stopped with an interrupt or quit signal. See the +|-r [t] option description for more information.<br>
+<br>
+In the absence of any options, lsof lists <b>all open files</b> belonging to all active processes.</p>
+<pre>Options
+ -? -h
+<dd>These two equivalent options select a usage (help) output list. <i>Lsof</i> displays a shortened form of this output when it detects an error in the
+options supplied to it, after it has displayed messages explaining each error. (Escape the '?' character as your shell requires.)
+</dd><dt> -a
+</dt><dd>This option causes list selection options to be ANDed, as described below.<br>
+</dd><dt> -A <i>A</i></dt><dd>This option is available on systems configured for AFS whose AFS kernel code is implemented via dynamic modules. It allows the <i>lsof</i> user to
+specify <i>A</i> as an alternate name list file where the kernel addresses of the dynamic modules might be found. See the <i>lsof</i> FAQ (The Related
+section gives its location.) for more information about dynamic modules, their symbols, and how they affect <i>lsof</i>.
+</dd><dt><b>-b</b></dt><dd>This option causes <i>lsof</i> to avoid kernel functions that might block - <i><b>lstat</b>(2)</i>, <i><b>readlink</b>(2)</i>, and <i><b>stat</b>(2)</i>. <br>See the BLOCKS AND TIMEOUTS and AVOIDING KERNEL BLOCKS sections for information on using this option.
+
+</dd><dt><b>-c</b> <i>c</i>
+</dt><dd>This option selects the listing of files for processes executing the command that begins with the characters of <i>c</i>. Multiple commands may be
+specified, using multiple <b>-c</b> options. They are joined in a single ORed set before participating in AND option selection.<br>If <i>c</i> begins and ends with a slash ('/'), the characters between the slashes are interpreted as a regular expression. <br>Shell meta-characters in the regular expression must be quoted to prevent their interpretation by the shell. <br>The closing slash may be followed by these modifiers:<br> b the regular expression is a basic one. i ignore the case of letters. x the regular expression is an extended one (default).
+
+</dd><dd>See the <i>lsof</i> FAQ (The FAQ section gives its location.) for more information on basic and extended regular expressions.<br>The simple command specification is tested first. If that test fails, the command regular expression is applied.<br> If the simple command test succeeds, the command regular expression test isn't made. This
+may result in ''no command found for regex:'' messages when lsof's <b>-V</b> option is specified.
+</dd><dt><b>+c</b> <i>w</i>
+</dt><dd>This option defines the maximum number of initial characters of the name, supplied by the UNIX dialect, of the UNIX command associated with a process to be
+printed in the COMMAND column. (The <i>lsof</i> default is nine.)
+<br>Note that many UNIX dialects do not supply all command name characters to <i>lsof</i> in the files and structures from<br> which <i>lsof</i> obtains command name. Often dialects limit the number of characters supplied in those
+sources. For example, Linux 2.4.27 and Solaris 9 both limit command name length to 16 characters.<br>If <i>w</i> is zero ('0'), all command characters supplied to <i>lsof</i> by the UNIX dialect will be printed.<br>If <i>w</i> is less than the length of the column title, ''COMMAND'', it will be raised to that length.
+
+</dd><dt><b>-C</b>
+</dt><dd>This option disables the reporting of any path name components from the kernel's name cache. <br>See the KERNEL NAME CACHE section for more information.
+</dd><dt><b>+d</b> <i>s</i>
+</dt><dd>This option causes <i>lsof</i> to search for all open instances of directory <i>s</i> and the files and directories it contains at its top level.<br>This option does NOT descend the directory tree, rooted at <i>s</i>. <br>The <b>+D</b> <i>D</i> option may be used to request a full-descent directory tree search,rooted at directory <i>D</i>. <br><br>Processing of the <b>+d</b> option does not follow symbolic links within <i>s</i> unless the <b>-x</b> or <b>-x " l"</b> option is also specified.<br>Nor does it search for open files on file system mount points on subdirectories of <i>s</i> unless the <b>-x</b> or <b>-x " f"</b> option is also specified.<br>Note: the authority of the user of this option limits it to searching for files that the user has permission to examine with the system <i><b>stat</b>(2)</i> function.
+</dd><dt><b>-d</b> <i>s</i>
+</dt><dd>This option specifies a list of file descriptors (FDs) to exclude from or include in the output listing. The file descriptors are specified in the
+comma-separated set <i>s</i> - e.g., ''cwd,1,3'', ''^6,^2''. (There should be no spaces in the set.)<br>The list is an exclusion list if all entries of the set begin with '^'. It is an inclusion list if no entry begins with '^'. Mixed lists are not permitted.<br>A file descriptor number range may be in the set as long as neither member is empty, both members are numbers, and<br>the ending member is larger than the starting one - e.g., ''0-7'' or ''3-10''. Ranges may be specified for exclusion if they<br>have the '^' prefix - e.g., ''^0-7'' excludes all file descriptors 0 through 7. <br>Multiple file descriptor numbers are joined in a single ORed set before participating in AND option selection.<br>When there are exclusion and inclusion members in the set, <i>lsof</i> reports them as errors and exits with a non-zero return code.<br>See the description of File Descriptor (FD) output values in the <b>OUTPUT</b> section for more information on file descriptor names.<br>
+</dd><dt><b>+D</b> <i>D</i>
+</dt><dd>This option causes <i>lsof</i> to search for all open instances of directory <i>D</i> and all the files and directories it contains to its complete depth.<br>Processing of the <b>+D</b> option does not follow symbolic links within <i>D</i> unless the <b>-x</b> or <b>-x " l"</b> option is also specified. <br>Nor does it search for open files on file system mount points on subdirectories of <i>D</i> unless the <b>-x</b> or <b>-x " f"</b> option is also specified.<br>Note: the authority of the user of this option limits it to searching for files that the user has permission to examine with the system <i><b>stat</b>(2)</i> function.<br><br>Further note: <i>lsof</i> may process this option slowly and require a large amount of dynamic memory to do it. This is because it must descend the entire directory
+tree, rooted at <i>D</i>, calling <i><b>stat</b>(2)</i> for each file and directory, building a list of all the files it finds, and searching that list for a match
+with every open file. When directory <i>D</i> is large, these steps can take a long time, so use this option prudently.
+
+</dd><dt><b>-D</b> <i>D</i>
+</dt><dd>This option directs <i>lsof's</i> use of the device cache file. The use of this option is sometimes restricted.<br> See the <b>DEVICE CACHE FILE</b> section and the sections that follow it for more information on this option.
+</dd><dt><b>-D</b>
+</dt><dd>must be followed by a function letter; the function letter may optionally be followed by a path name. <i><br><br>Lsof</i> recognizes these function letters:<br><br><b>?</b> - report device cache file paths<br><b>b</b> - build the device cache file<br><b>i</b> - ignore the device cache file<br><b>r</b> - read the device cache file<br><b>u</b> - read and update the device cache file
+
+</dd><dd>The <b>b</b>, <b>r</b>, and <b>u</b> functions, accompanied by a path name, are sometimes restricted.<br>When these functions are restricted, they will not appear in the description of the <b>-D</b> option that <br>accompanies <b>-h</b> or <b>-?</b> option output. See the DEVICE CACHE FILE section and the
+sections that follow it for more information on these functions and when they're restricted.
+<br>The <b>?</b> function reports the read-only and write paths that lsof can use for the device cache file,<br>the names of any environment variables whose values <i>lsof</i> will examine when forming the<br>device cache file path, and the format for the personal device cache file path. <br>(Escape the '?' character as your shell requires.)<br>When available, the <b>b</b>, <b>r</b>, and <b>u</b> functions may be followed by the device cache file's path.<br>The standard default is <i>.lsof_hostname</i> in the home directory of the real user ID that executes <i>lsof</i>, <br>but this could have been changed when <i>lsof</i> was configured and compiled. <br>(The output of the <b>-h</b> and <b>-?</b> options show the current default prefix - e.g., ''.lsof''.) <br>The suffix, <i>hostname</i>, is the first component of the host's name returned by <i><b>gethostname</b>(2).</i> <br>When available, the <b>b</b> function directs <i>lsof</i> to build a new device cache file at the default or specified path.
+The <b>i</b> function directs <i>lsof</i> to ignore the default device cache file and obtain its information about devices via direct calls to the kernel.<br><br>The <b>r</b> function directs <i>lsof</i> to read the device cache at the default or specified path, but <br>prevents it from creating a new device cache file when none exists or the existing one is<br>improperly structured. The <b>r</b> function, when specified without a path name, prevents <i>lsof</i> <br>from updating an incorrect or outdated device cache file, or creating a new one in its place.<br><br>The <b>r</b> function is always available when it is specified without a path name
+argument; it may be restricted by the permissions of the <i>lsof</i> process.
+<br>When available, the <b>u</b> function directs <i>lsof</i> to read the device cache file at the default or specified path,<br>if possible, and to rebuild it, if necessary. This is the default device cache file function when no <b>-D</b> option has been specified.<br>
+</dd><dt><b>+|-f [cfgGn]</b>
+</dt><dd><b>f</b> by itself clarifies how path name arguments are to be interpreted. When followed by <b>c</b>, <b>f</b>, <b>g</b>, <b>G</b>, or <b>n</b> in any
+combination it specifies that the listing of kernel file structure information is to be enabled ('+') or inhibited ('-').
+<br>Normally a path name argument is taken to be a file system name if it matches a mounted-on directory<br>name reported by <i><b>mount</b>(8)</i>, or if it represents a block device, named in the <i>mount</i> output and associated
+with a mounted directory name. When <b>+f</b> is specified, all path name arguments will be taken to be<br>file system names, and <i>lsof</i> will complain if any are not. This can be useful, for example, when the <br>file system name (mounted-on device) isn't a block device. This happens for some CD-ROM file systems.<br><br>When <b>-f</b> is specified by itself, all path name arguments will be taken to be simple files. <br>Thus, for example, the ''<b>-f</b> -- /'' arguments direct lsof to search for open files with a '/' path name, <br>not all open files in the '/' (root) file system.
+<br>Be careful to make sure <b>+f</b> and <b>-f</b> are properly terminated and aren't followed by a character<br> (e.g., of the file or file system name) that might be taken as a parameter. <br>For example, use ''--'' after <b>+f</b> and <b>-f</b> as in these examples.<br><br>$ lsof +f -- /file/system/name $ lsof -f -- /file/name
+
+</dd><dd>The listing of information from kernel file structures, requested with the <b>+f [cfgGn]</b> option form,<br>is normally inhibited, and is not available for some dialects - e.g., /proc-based Linux.<br>When the prefix to <b>f</b> is a plus sign ('+'), these characters request file structure information:</dd><dt> <b>c</b> file structure use count <br> <b>f</b> file structure address <br> <b>g</b> file flag abbreviations<br> <b>G</b> file flags in hexadecimal<br> <b>n</b> file structure node address
+</dt><dd>When the prefix is minus ('-') the same characters disable the listing of the indicated values.<br><br>File structure addresses, use counts, flags, and node addresses may be used to detect more <br>readily identical files inherited by child processes and identical files in use by different processes.<br><i>Lsof</i> column output can be sorted by output columns holding the values and listed to identify identical file use,<br> or <i>lsof</i> field output can be parsed by an AWK or Perl post-filter script, or by a C program.<br>
+</dd><dt><b>-F</b> <i>f</i>
+</dt><dd>This option specifies a character list, <i>f</i>, that selects the fields to be output for processing by another program, and the character that terminates
+each output field. Each field to be output is specified with a single character in <i>f</i>. The field terminator defaults to NL, but may be changed to NUL
+(000). See the OUTPUT FOR OTHER PROGRAMS section for a description of the field identification characters and the field output process.
+<br>When the field selection character list is empty, all standard fields are selected <br>(except the raw device field, security context and zone field for compatibility reasons) and the NL field terminator is used.<br>When the field selection character list contains only a zero ('0'), all fields are selected <br>(except the raw device field for compatibility reasons) and the NUL terminator character is used.<br>Other combinations of fields and their associated field terminator character must be set with explicit entries in <i>f</i>, <br>as described in the OUTPUT FOR OTHER PROGRAMS section.<br><br>When a field selection character identifies an item <i>lsof</i> does not normally list - <br>e.g., PPID, selected with <b>-R</b> - specification of the field character - e.g., ''<b>-FR</b>'' - also selects the listing of the item.<br><br>
+When the field selection character list contains the single character '?', <i>lsof</i> will display a help list <br>of the field identification characters. (Escape the '?' character as your shell requires.)<br>
+</dd><dt><b>-g</b> <i>[s]</i>
+</dt><dd>This option excludes or selects the listing of files for the processes whose optional process group IDentification (PGID) numbers are in the
+comma-separated set <i>s</i> - e.g., ''123'' or ''123,^456''. (There should be no spaces in the set.) <br>PGID numbers that begin with '^' (negation) represent exclusions.<br>Multiple PGID numbers are joined in a single ORed set before participating in AND option selection. <br>However, PGID exclusions are applied without ORing or ANDing and take effect before other selection criteria are applied.<br>The <b>-g</b> option also enables the output display of PGID numbers. When specified without a PGID set that's all it does.<br>
+</dd><dt><b>-i</b> <i>[i]</i>
+</dt><dd>This option selects the listing of files any of whose Internet address matches the address specified in <i>i</i>. If no address is specified, this option
+selects the listing of all Internet and x.25 (HP-UX) network files.<br>If <b>-i</b><i>4</i> or <b>-i</b><i>6</i> is specified with no following address, only files of the indicated IP version, IPv4 or IPv6, are displayed. (An
+IPv6 specification may be used only if the dialects supports IPv6, as indicated by ''[46]'' and ''IPv[46]'' in <i>lsof's</i> <b>-h</b> or <b>-?</b> output.)
+Sequentially specifying <b>-i</b>4, followed by <b>-i</b>6 is the same as specifying <b>-i</b>, and vice-versa. <br>Specifying <b>-i</b>4, or <b>-i</b>6 after <b>-i</b> is the same as specifying <b>-i</b>4 or <b>-i</b>6 by itself.<br>Multiple addresses (up to a limit of 100) may be specified with multiple <b>-i</b> options. <br>(A port number or service name range is counted as one address.) They are joined in a single ORed set before participating in AND option
+selection. <br>An Internet address is specified in the form (Items in square brackets are optional.):<span class="code"> [<i>46</i>][<i>protocol</i>][@<i>hostname</i>|<i>hostaddr</i>][:<i>service</i>|<i>port</i>]</span>
+where:</dd></pre>
+<dd><p> <span class="code">46</span> specifies the IP version, IPv4 or IPv6 that applies to the following address.<br>
+ '6' may be be specified only if the UNIX
+ dialect supports IPv6. <br>
+If neither '4' nor
+ '6' is specified, the following address applies to all IP versions.<br>
+ <span class="code">protocol</span> is a protocol name - TCP or UDP.<br>
+ <span class="code">hostname</span> is an Internet host name. Unless a
+ specific IP version is specified, open
+ network files associated with host names
+ of all versions will be selected.<br>
+ <span class="code">hostaddr</span> is a numeric Internet IPv4 address in
+ dot form; or an IPv6 numeric address in
+ colon form, enclosed in brackets, if the
+ UNIX dialect supports IPv6. <br>
+When an IP
+ version is selected, only its numeric
+ addresses may be specified.<br>
+ <span class="code">service</span> is an /etc/services name - e.g., smtp -
+ or a list of them.<br>
+ <span class="code">port</span> is a port number, or a list of them.</p>
+IPv6 options may be used only if the UNIX dialect supports IPv6.
+</dd>
+<dd>To see if the dialect supports IPv6, run <i>lsof</i> and specify the <b>-h</b> or <b>-?</b> (help) option. If the displayed description of the <b>-i</b>
+
+option contains ''[46]'' and ''IPv[46]'', IPv6 is supported.
+<br>IPv4 host names and addresses may not be specified if network file selection
+is limited to IPv6 with <b>-i</b> 6. <br>
+IPv6 host names and addresses may not be specified if network file selection is limited to IPv4 with <b>-i</b> 4. <br>
+When
+an open IPv4 network file's address is mapped in an IPv6 address, the open file's type will be IPv6, not IPv4, and its display will be selected by '6', not
+'4'.
+<br>
+<br>At least one address component -
+</dd><dd><b>4, 6,</b> <i>protocol</i>, ,IR hostname , <i>hostaddr</i>, or <i>service</i> - must be supplied. The '@' character, leading the host
+specification, is always required; as is the ':', leading the port specification. Specify either <i>hostname</i> or <i>hostaddr</i>. Specify either
+
+<i>service</i> name list or <i>port</i> number list. If a <i>service</i> name list is specified, the <i>protocol</i> may also need to be specified if the TCP
+and UDP port numbers for the service name are different. Use any case - lower or upper - for <i>protocol</i>.
+<br>
+</dd><dt><i>Service</i>
+</dt><dd>names and <i>port</i> numbers may be combined in a list whose entries are separated by commas and whose numeric range entries are separated by minus signs.
+There may be no embedded spaces, and all service names must belong to the specified <i>protocol</i>. Since service names may contain embedded minus signs, the
+starting entry of a range can't be a service name; it can be a port number, however.
+<br>
+</dd>
+<dt>Here are some sample addresses:
+</dt><dd>
+<pre class="code"> -i6 - IPv6 only
+
+ TCP:25 - TCP and port 25
+
+ @1.2.3.4 - Internet IPv4 host address 1.2.3.4
+
+ @[3ffe:1ebc::1]:1234 - Internet IPv6 host address
+ 3ffe:1ebc::1, port 1234
+
+ UDP:who - UDP who service port
+
+
+ TCP@lsof.itap:513 - TCP, port 513 and host name lsof.itap<br> tcp@foo:1-10,smtp,99 - TCP, ports 1 through 10,
+ service name smtp, port 99, host name foo
+
+ tcp@bar:1-smtp - TCP, ports 1 through smtp, host bar<br> :time - either TCP or UDP time service port</pre>
+</dd><dt><b>-k</b> <i>k</i>
+
+</dt><dd>This option specifies a kernel name list file, <i>k</i>, in place of /vmunix, /mach, etc. This option is not available under AIX on the IBM RISC/System
+6000.
+</dd><dt><b>-l</b>
+</dt><dd>This option inhibits the conversion of user ID numbers to login names. It is also useful when login name lookup is working improperly or slowly.
+</dd><dt><b>+|-L</b> <i>[l]</i>
+</dt>
+<dd>This option enables ('+') or disables ('-') the listing of file link counts, where they are available - <br>
+e.g., they aren't available for sockets, or most
+FIFOs and pipes.
+When
+<b>+L</b> is specified without a <br>
+following number, all link counts will be listed. When <b>-L</b> is specified (the default), no link counts will be
+listed.
+<br>
+When <b>+L</b> is followed by a number, only files having a link count less than that number will be listed. <br>
+(No number may follow <b>-L</b>.) A specification
+of the form ''<b>+L1</b>'' will select open files that have been unlinked.<br>
+A specification of the form ''<b>+aL1 <i>&lt;file_system&gt;</i></b>'' will select
+unlinked open files on the specified file system.
+<br>
+For other link count comparisons, use field output (<b>-F</b>) and a post-processing script or program.
+<br>
+</dd>
+<dt><b>+|-m</b> <i>m</i>
+
+</dt>
+<dd>This option specifies an alternate kernel memory file or activates mount table supplement processing.
+<br>The option form
+<b>-m</b> <i>m</i> specifies a kernel memory file, <i>m</i>, in place of <i>/dev/kmem</i> or <i>/dev/mem</i> - e.g., a crash dump file.
+<br>
+The option form <b>+m</b> requests that a mount supplement file be written to the standard output file. All other options are silently ignored.
+<br>
+<br>
+There will be a line in the mount supplement file for each mounted file system, containing the mounted file system directory, followed by a single space, followed by the device number in hexadecimal "0x" format - <br>
+e.g.,<br>
+/ 0x801 <br>
+<i>Lsof</i> can use the mount supplement file to get device numbers for file systems when it can't get them via <i><b>stat</b>(2)</i> or <i><b>lstat</b>(2)</i>.
+<br>
+The option form <b>+m</b> <i>m</i> identifies <i>m</i> as a mount supplement file.
+<br>
+Note: the <b>+m</b> and <b>+m</b> <i>m</i> options are not available for all supported dialects. <br>
+Check the output of <i>lsof's</i> <b>-h</b> or <b>-?</b> options to
+see if the <b>+m</b> and <b>+m</b> <i>m</i> options are available.
+<br>
+</dd>
+<dt><b>+|-M</b>
+</dt>
+<dd>Enables (<b>+</b>) or disables (<b>-</b>) the reporting of portmapper registrations for local TCP and UDP ports. <br>
+The default reporting mode is set by the
+<i>lsof</i> builder with the HASPMAPENABLED #define in the dialect's machine.h header file;<br>
+<i>lsof</i> is distributed with the HASPMAPENABLED #define
+deactivated, so portmapper reporting is disabled by default<br>
+and must be requested with <b>+M</b>. Specifying <i>lsof's</i> <b>-h</b> or <b>-?</b> option will
+report the default mode. <br>
+Disabling portmapper registration when it is already disabled or enabling it when already enabled is acceptable.
+<br>
+<br>When portmapper registration reporting is enabled,
+<i>lsof</i> displays the portmapper registration (if any) for local TCP or UDP ports in square brackets immediately following the port numbers or service
+names - e.g., '':1234[name]'' or '':name[100083]''. The registration information may be a name or number, depending on what the registering program supplied to
+the portmapper when it registered the port.
+<br>
+<br>
+When portmapper registration reporting is enabled, <i>lsof</i> may run a little more slowly or even become blocked <br>
+when access to the portmapper becomes congested or stopped. Reverse the reporting mode to
+determine <br>
+if portmapper registration reporting is slowing or blocking <i>lsof</i>.
+<br>
+For purposes of portmapper registration reporting
+<i>lsof</i> considers a TCP or UDP port local if: it is found in the<br>
+local part of its containing kernel structure; or if it is located in the foreign part
+of its containing kernel structure <br>
+and the local and foreign Internet addresses are the same; or if it is located in the foreign part of its containing <br>
+kernel
+structure and the foreign Internet address is INADDR_LOOPBACK (127.0.0.1). <br>
+This rule may make <i>lsof</i> ignore some foreign ports on machines with multiple
+interfaces when the foreign<br>
+Internet address is on a different interface from the local one.
+<br>
+See the <i>lsof</i> FAQ (The <b>FAQ</b> section gives its location.) for further discussion of portmapper registration reporting issues.
+</dd>
+<dt><b>-n</b>
+</dt><dd>This option inhibits the conversion of network numbers to host names for network files. <br>
+Inhibiting conversion may make <i>lsof</i> run faster. It is also
+useful when host name lookup is not working properly.
+</dd>
+<dt><b>-N</b>
+</dt><dd>This option selects the listing of NFS files.
+</dd><dt><b>-o</b>
+
+</dt>
+<dd>This option directs <i>lsof</i> to display file offset at all times. It causes the SIZE/OFF output column title to be changed to OFFSET. Note: on some UNIX
+dialects <i>lsof</i> can't obtain accurate or consistent file offset information from its kernel data sources, sometimes just for particular kinds of files
+(e.g., socket files.) Consult the <i>lsof</i> FAQ (The <b>FAQ</b> section gives its location.) for more information.
+<br>The
+<b>-o</b> and <b>-s</b> options are mutually exclusive; they can't both be specified. <br>
+When neither is specified, <i>lsof</i> displays whatever value - size
+or offset - is appropriate and available for the type of the file.
+<br>
+</dd>
+<dt><b>-o</b> <i>o</i>
+</dt>
+<dd>This option defines the number of decimal <i>digits (</i>o) to be printed after the ''0t'' for a file offset before the form is switched to ''0x...''. <br>
+An
+<i>o</i> value of zero (unlimited) directs <i>lsof</i> to use the ''0t'' form for all offset output.
+<br>
+<br>This option does NOT direct
+<i>lsof</i> to display offset at all times; specify <b>-o</b> (without a trailing number) to do that. <br>
+This option only specifies the number of digits after
+''0t'' in either mixed size and offset or offset-only output. <br>
+Thus, for example, to direct <i>lsof</i> to display offset at all times with a decimal digit
+count of 10, use:<br>
+
+</dd>
+<dt> -o -o 10or -oo10
+</dt><dd>The default number of digits allowed after ''0t'' is normally 8, but may have been changed by the lsof builder. <br>
+Consult the description of the <b>-o</b>
+<i>o</i> option in the output of the <b>-h</b> or <b>-?</b> option to determine the default that is in effect.
+</dd>
+<dt><b>-O</b>
+
+</dt>
+<dd>This option directs <i>lsof</i> to bypass the strategy it uses to avoid being blocked by some kernel operations - <br>
+i.e., doing them in forked child
+processes. See the BLOCKS AND TIMEOUTS and AVOIDING KERNEL BLOCKS sections<br>
+for more information on kernel operations that may block <i>lsof</i>.
+<br>While use of this option will reduce
+<i>lsof</i> startup overhead, it may also cause <i>lsof</i> to hang when the kernel doesn't respond to a function.<br>
+Use this option cautiously.
+
+</dd>
+<dt><b>-p</b> <i>s</i>
+</dt>
+<dd>This option excludes or selects the listing of files for the processes whose optional process IDentification (PID) <br>
+numbers are in the comma-separated set
+<i>s</i> - e.g., ''123'' or ''123,^456''. (There should be no spaces in the set.)
+<br>PID numbers that begin with '^' (negation) represent exclusions.
+<br>Multiple process ID numbers are joined in a single ORed set before
+participating in AND option selection. <br>
+However, PID exclusions are applied without ORing or ANDing and take effect before other selection criteria are
+applied.
+</dd>
+<dt><b>-P</b>
+</dt><dd>This option inhibits the conversion of port numbers to port names for network files.<br>
+Inhibiting the conversion may make <i>lsof</i> run a little faster. It
+is also useful when port name lookup is not working properly.
+<br>
+</dd>
+<dt><b>+|-r</b> <i>[t]</i>
+</dt>
+<dd>This option puts <i>lsof</i> in repeat mode. There <i>lsof</i> lists open files as selected by other options, delays <i>t</i> seconds (default fifteen),
+then repeats the listing, delaying and listing repetitively until stopped by a condition defined by the prefix to the option.
+<br>If the prefix is a '-', repeat mode is endless.
+<i>Lsof</i> must be terminated with an interrupt or quit signal.
+<br>
+If the prefix is '+', repeat mode will end the first cycle no open files are listed - and of course when <i>lsof</i> is stopped<br>
+with an interrupt or quit signal. When repeat mode ends because no files are listed,<br>
+the process
+exit code will be zero if any open files were ever listed; one, if none were ever listed.<br>
+<i><br>
+Lsof</i>
+marks the end of each listing: if field output is in progress (the <b>-F</b>, option has been specified), <br>
+the marker is 'm'; otherwise the marker is
+''========''. The marker is followed by a NL character.
+<br>
+<br>Repeat mode reduces
+<i>lsof</i> startup overhead, so it is more efficient to use this mode than to call <i>lsof</i> repetitively from a shell script, for example.
+<br>
+To use repeat mode most efficiently, accompany <b>+|-r</b> with specification of other <i>lsof</i> selection options, <br>
+so the amount of kernel memory access <i>lsof</i> does will be kept to a minimum.
+<br>
+Options that filter at the process level - e.g., <b>-c</b>, <b>-g</b>, <b>-p</b>, <b>-u</b> - are the most efficient selectors.
+<br>
+Repeat mode is useful when coupled with field output (see the
+<b>-F</b>, option description) and a supervising <i>awk</i> or <i>Perl</i> script, or a C program.
+<br>
+</dd>
+
+<dt><b>-R</b>
+</dt><dd>This option directs lsof to list the Parent Process IDentification number in the PPID column.
+</dd><dt><b>-s</b>
+</dt>
+<dd>This option directs <i>lsof</i> to display file size at all times. It causes the SIZE/OFF output column title to be changed to SIZE. If the file does not
+have a size, nothing is displayed.
+<br>The
+<b>-o</b> (without a following decimal digit count) and <b>-s</b> options are mutually exclusive; they can't both be specified. When neither is specified,
+<i>lsof</i> displays whatever value - size or offset - is appropriate and available for the type of file.
+<br>Since some types of files don't have true sizes - sockets, FIFOs,pipes, etc.<br>
+- lsof displays for their sizes the content amounts in their associated kernel buffers, if possible.
+<br>
+</dd>
+<dt><b>-S</b> <i>[t]</i>
+</dt>
+<dd>This option specifies an optional time-out seconds value for kernel functions - <i><b>lstat</b>(2)</i>, <i><b>readlink</b>(2)</i>, and <i><b>stat</b>(2)</i> - that might
+otherwise deadlock. <br>
+The minimum for <i>t</i> is two; the default, fifteen; when no value is specified, the default is used.
+<br>
+See the
+BLOCKS AND TIMEOUTS section for more information.
+<br>
+</dd>
+<dt><b>-T</b> <i>[t]</i>
+</dt><dd>This option controls the reporting of some TCP/TPI information, also reported by <i><b>netstat</b>(1)</i>, following the network addresses. In normal output the
+information appears in parentheses, each item except state identified by a keyword, followed by '=', separated from others by a single space:<br>
+<br>
+<span class="code">&lt;TCP or TPI state name&gt; QR=&lt;read queue length&gt; QS=&lt;send queue length&gt; SO=&lt;socket options and values&gt; SS=&lt;socket
+states&gt; TF=&lt;TCP flags and values&gt; WR=&lt;window read length&gt; WW=&lt;window write length&gt;
+</span><br>
+</dd>
+<dd>Not all values are reported for all UNIX dialects. Items values (when available) are reported after the item name and '='.
+<br>
+When the field output mode is in effect (See OUTPUT FOR OTHER PROGRAMS.) each item appears as a field with a 'T' leading character.
+<br>
+</dd>
+<dt><b>-T</b>
+</dt><dd>with no following key characters disables TCP/TPI information reporting.
+</dd><dt><b>-T</b>
+</dt><dd>with following characters selects the reporting of specific TCP/TPI information:<br>
+<b>f</b> selects reporting of socket options, states and values, and TCP flags and values.<br>
+<b>q</b> selects queue length
+reporting. <b><br>
+s</b> selects connection state reporting. <b><br>
+w</b> selects window size reporting.
+
+</dd>
+<dd>Not all selections are enabled for some UNIX dialects. State may be selected for all dialects and is reported by default. <br>
+The <b>-h</b> or <b>-?</b> help
+output for the <b>-T</b> option will show what selections may be used with the UNIX dialect.
+<br>
+<br>
+When <b>-T</b> is used to select information - i.e., it is followed by one or more selection characters - the displaying of state is disabled by default, and it
+must be explicitly selected again in the characters following <b>-T</b>. (In effect, then, the default is equivalent to <b>-Ts</b>.) <br>
+<br>
+For example, if queue
+lengths and state are desired, use <b>-Tqs</b>.
+<br>
+Socket options, socket states, some socket values, TCP flags and
+one TCP value may be reported (when available in the UNIX dialect) in the form of the names that commonly appear after SO_, so_, SS_, TCP_ and TF_ in the
+dialect's header files - most often &lt;sys/socket.h&gt;, &lt;sys/socketvar.h&gt; and &lt;netinet/tcp_var.h&gt;. <br>
+<br>
+Consult those header files for the meaning of
+the flags, options, states and values.
+''SO='' precedes socket options and values; ''SS='', socket states;
+and ''TF='', TCP flags and values.
+If a flag or option has a value, the value will follow an '=' and
+the name -- e.g., ''SO=LINGER=5'', ''SO=QLIM=5'', ''TF=MSS=512''. <br>
+<br>
+The following values may be reported:<br>
+<br>
+ <i>Name Reported Description (Common Symbol) </i><br>
+KEEPALIVE keep alive time (SO_KEEPALIVE) <br>
+LINGER linger time (SO_LINGER) <br>
+MSS
+maximum segment size (TCP_MAXSEG) <br>
+PQLEN partial listen queue connections <br>
+QLEN established listen queue connections <br>
+QLIM established
+listen queue limit <br>
+RCVBUF receive buffer length (SO_RCVBUF) <br>
+SNDBUF send buffer length (SO_SNDBUF)
+<br>
+</dd>
+<dd>Details on what socket options and values, socket states, and TCP flags and values may be displayed for particular UNIX dialects may be found in the answer
+to the ''Why doesn't lsof report socket options, socket states, and TCP flags and values for my dialect?'' and ''Why doesn't lsof report the partial listen
+queue connection count for my dialect?'' questions in the <i>lsof</i> FAQ (The <b>FAQ</b> section gives its location.)
+</dd><dt><b>-t</b>
+</dt><dd>This option specifies that <i>lsof</i> should produce terse output with process identifiers only and no header - e.g., so that the output may be piped to
+<i><b>kill</b>(1)</i>. This option selects the <b>-w</b> option.
+
+</dd><dt><b>-u</b> <i>s</i>
+</dt>
+<dd>This option selects the listing of files for the user whose login names or user ID numbers are in the comma-separated set <i>s</i> - e.g., ''abe'', or
+''548,root''. (There should be no spaces in the set.)
+<br>Multiple login names or user ID numbers are joined in a single ORed set
+before participating in AND option selection.
+<br>If a login name or user ID is preceded by a '^', it becomes a negation -</dd><dd>i.e., files of processes owned by the login name or user ID will never be listed. <br>
+A negated login name or user ID selection is neither ANDed nor ORed with
+other selections;<br>
+it is applied before all other selections and absolutely excludes the listing of the files of the process. <br>
+For example, to direct <i>lsof</i>
+to exclude the listing of files belonging to root processes, specify ''-u^root'' or ''-u^0''.
+</dd><dt><b>-U</b>
+
+</dt><dd>This option selects the listing of UNIX domain socket files.
+</dd><dt><b>-v</b>
+</dt><dd>This option selects the listing of <i>lsof</i> version information, including: revision number; <br>
+when the <i>lsof</i> binary was constructed; <br>
+who
+constructed the binary and where; <br>
+the name of the compiler used to construct the <i>lsof</i> binary;<br>
+the version number of the compiler when readily available;
+<br>
+the compiler and loader flags used to construct the <i>lsof</i> binary; <br>
+and system information, typically the output of <i>uname</i>'s <b>-a</b> option.
+
+</dd><dt><b>-V</b>
+</dt>
+<dd>This option directs <i>lsof</i> to indicate the items it was asked to list and failed to find - command names, file names, Internet addresses or files,
+login names, NFS files, PIDs, PGIDs, and UIDs.
+<br>When other options are ANDed to search options, or compile-time
+options restrict the listing of some files, <i>lsof</i> may not report that it failed to find a search item when an ANDed option or compile-time option
+prevents the listing of the open file containing the located search item.
+<br>
+For example, ''lsof -V -iTCP@foobar -a -d 999'' may not report a failure to locate open files at ''TCP@foobar'' and may not list any, if none have a file descriptor number of 999. A similar situation arises when
+HASSECURITY and HASNOSOCKSECURITY are defined at compile time and they prevent the listing of open files.
+</dd><dt><b>+|-w</b>
+</dt>
+<dd>Enables (<b>+</b>) or disables (<b>-</b>) the suppression of warning messages.
+<br>
+The
+<i>lsof</i> builder may choose to have warning messages disabled or enabled by default. The default warning message state is indicated in the output of the
+<b>-h</b> or <b>-?</b> option. Disabling warning messages when they are already disabled or enabling them when already enabled is acceptable.
+<br>
+The <b>-t</b> option selects the <b>-w</b> option.
+<br>
+</dd><dt><b>-x " [fl]"</b>
+</dt>
+<dd>This option may accompany the <b>+d</b> and <b>+D</b> options to direct their processing to cross over symbolic links and|or file system mount points
+encountered when scanning the directory (<b>+d</b>) or directory tree (<b>+D</b>).
+<br>If
+<b>-x</b> is specified by itself without a following parameter, cross-over processing of both symbolic links and file system mount points is enabled. Note
+that when <b>-x</b> is specified without a parameter, the next argument must begin with '-' or '+'.
+<br>
+The optional 'f' parameter enables file system mount point cross-over processing; 'l', symbolic link cross-over processing.
+<br>
+The <b>-x</b> option may not be supplied without also supplying a <b>+d</b> or <b>+D</b> option.
+<br>
+</dd><dt><b>-X</b>
+</dt><dd>This is a dialect-specific option.
+<br>
+<br>
+AIX:
+
+</dd><dd>This IBM AIX RISC/System 6000 option requests the reporting of executed text file and shared library references.
+<br>
+<b>WARNING:</b>
+</dd><dd>because this option uses the kernel readx() function, its use on a busy AIX system might cause an application process to hang so completely that it can
+neither be killed nor stopped. I have never seen this happen or had a report of its happening, but I think there is a remote possibility it could happen.
+<br>By default use of readx() is disabled.
+</dd>
+<dd>On AIX 5L and above <i>lsof</i> may need setuid-root permission to perform the actions this option requests.
+<br>
+The
+<i>lsof</i> builder may specify that the <b>-X</b> option be restricted to processes whose real UID is root. If that has been done, the <b>-X</b> option
+will not appear in the <b>-h</b> or <b>-?</b> help output unless the real UID of the <i>lsof</i> process is root. The default <i>lsof</i> distribution allows
+any UID to specify <b>-X,</b> so by default it will appear in the help output.
+<br>
+When AIX readx() use is disabled, <i>lsof</i> may not be able to report information for all text and loader file references, but it may also avoid exacerbating an AIX kernel
+directory search kernel error, known as the Stale Segment ID bug.
+<br>
+The readx() function, used by <i>lsof</i> or any other program to access some sections of kernel virtual memory, can trigger the Stale Segment ID bug. It can cause the kernel's
+dir_search() function to believe erroneously that part of an in-memory copy of a file system directory has been zeroed. Another application process, distinct
+from <i>lsof</i>, asking the kernel to search the directory - e.g., by using <i><b>open</b>(2)</i> - can cause dir_search() to loop forever, thus hanging the
+application process.
+<br>
+Consult the <i>lsof</i> FAQ (The <b>FAQ</b> section gives its location.) and the <i>00README</i> file of the <i>lsof</i> distribution for a more complete description
+of the Stale Segment ID bug, its APAR, and methods for defining readx() use when compiling <i>lsof</i>.
+<br>
+<br>
+Linux:<br>
+This Linux option requests that <i>lsof</i> skip the reporting of information on all open TCP and UDP IPv4 and IPv6 files.
+<br>This Linux option is most useful when the system has an extremely</dd><dd>large number of open TCP and UDP files, the processing of whose information in the <i>/proc/net/tcp*</i> and <i>/proc/net/udp*</i> files would take
+<i>lsof</i> a long time, and whose reporting is not of interest.
+<br>Use this option with care and only when you are sure that the
+</dd><dd>information you want <i>lsof</i> to display isn't associated with open TCP or UDP socket files.
+<br>
+<br>
+Solaris 10 and above:
+</dd>
+<dd>This Solaris 10 and above option requests the reporting of cached paths for files that have been deleted - i.e., removed with <i><b><a href="/bash/rm.html">rm</a></b></i> or <i><b>unlink</b>(2)</i>.
+<br>The cached path is followed by the string '' (deleted)'' to indicate
+that the path by which the file was opened has been deleted.
+<br>
+Because intervening changes made to the path - i.e., renames with <i><b><a href="/bash/mv.html">mv</a></b>(1)</i> or <i><b>rename</b>(2)</i> - are not recorded in the cached path, what <i>lsof</i> reports is only the path by which the file was opened, not its
+possibly different final path.
+<br>
+</dd><dt><b>-z</b> <i>[z]</i>
+
+</dt>
+<dd>specifies how Solaris 10 and higher zone information is to be handled.
+<br>Without a following argument - e.g., NO
+<i>z</i> - the option specifies that zone names are to be listed in the ZONE output column.
+<br>
+The <b>-z</b> option may be followed by a zone name, <b>z</b><i>.</i> That causes lsof to list only open files for processes in that zone. Multiple <b>-z</b>
+<i>z</i> option and argument pairs may be specified to form a list of named zones. Any open file of any process in any of the zones will be listed, subject to
+other conditions specified by other options and arguments.
+<br>
+</dd><dt><b>-Z</b><i>[Z]</i>
+</dt>
+<dd>specifies how SELinux security contexts are to be handled.
+<br>Without a following argument - e.g., NO
+<i>Z</i> - the option specifies that security contexts are to be listed in the SECURITY-CONTEXT output column.
+<br>
+The <b>-Z</b> option may be followed by a wildcard security context name, <b>Z</b><i>.</i> That causes lsof to list only open files for processes in that
+security context. Multiple <b>-Z</b><i>Z</i> option and argument pairs may be specified to form a list of security contexts. Any open file of any process in
+any of the security contexts will be listed, subject to other conditions specified by other options and arguments. Note that <i>Z</i> can be A:B:C or *:B:C or
+A:B:* or *:*:C to match against the A:B:C context.
+<br>
+</dd><dt><b>--</b>
+</dt><dd>The double minus sign option is a marker that signals the end of the keyed options. It may be used, for example, when the first file name begins with a
+minus sign. It may also be used when the absence of a value for the last keyed option must be signified by the presence of a minus sign in the following option
+and before the start of the file names.
+<br>
+</dd>
+<dt><i>filenames</i>
+</dt>
+<dd>These are path names of specific files to list. <br>
+Symbolic links are resolved before use. <br>
+The first name may be separated from the preceding options with the
+''--'' option.
+<br>
+If a
+<i>filename</i> is the mounted-on directory of a file system or the device of the file system, <i>lsof</i> will list all the files open on the file system. <br>
+To
+be considered a file system, the <i>filename</i> must match a mounted-on directory name in <i><b><a href="mount.html" rel="nofollow">mount</a></b></i> output, or match the name of a block device associated
+with a mounted-on directory name. The <b>+|-f</b> option may be used to force <i>lsof</i> to consider a <i>name</i> a file system identifier (<b>+f</b>) or a
+simple file (<b>-f</b>).
+<br>
+<br>
+If <i>name</i> is a path to a directory that is not the mounted-on directory name of a file system, it is treated just as a regular file is treated - i.e.,
+its listing is restricted to processes that have it open as a file or as a process-specific directory, such as the root or current working directory. To
+request that <i>lsof</i> look for open files inside a directory name, use the <b>+d</b> <i>s</i> and <b>+D</b> <i>D</i> options.
+<br>
+<br>
+If a <i>name</i> is the base name of a family of multiplexed files - e. g, AIX's <i>/dev/pt[cs]</i> - <i>lsof</i> will list all the associated multiplexed files
+on the device that are open - e.g., <i>/dev/pt[cs]/1</i>, <i>/dev/pt[cs]/2</i>, etc.
+<br>
+<br>
+If a
+<i>name</i> is a UNIX domain socket name, <i>lsof</i> will usually search for it by the characters of the name alone - exactly as it is specified and is
+recorded in the kernel socket structure. (See the next paragraph for an exception to that rule for Linux.) Specifying a relative path - e.g., <i>./file</i> -
+in place of the file's absolute path - e.g., <i>/tmp/file</i> - won't work because <i>lsof</i> must match the characters you specify with what it finds in the
+kernel UNIX domain socket structures.<br>
+<br>If a
+<i>name</i> is a Linux UNIX domain socket name, in one case <i>lsof</i> is able to search for it by its device and inode number, allowing <i>name</i> to be
+a relative path. The case requires that the absolute path -- i.e., one beginning with a slash ('/') be used by the process that created the socket, and hence
+be stored in the <i>/proc/net/unix</i> file; and it requires that <i>lsof</i> be able to obtain the device and node numbers of both the absolute path in
+<i>/proc/net/unix</i> and <i>name</i> via successful <i><b>stat</b>(2)</i> system calls. When those conditions are met, <i>lsof</i> will be able to search for the
+UNIX domain socket when some path to it is is specified in <i>name</i>. Thus, for example, if the path is <i>/dev/log</i>, and an <i>lsof</i> search is
+initiated when the working directory is <i>/dev</i>, then <i>name</i> could be <i>./log</i>.<br>
+<br>
+If a <i>name</i> is none of the above, <i>lsof</i> will list any open files whose device and inode match that of the specified path <i>name</i>.
+<br>
+<br>
+If you have also specified the <b>-b</b> option, the only <i>names</i> you may safely specify are file systems for which your mount table supplies alternate device numbers. See the
+AVOIDING KERNEL BLOCKS and ALTERNATE DEVICE NUMBERS sections for more information. <br>
+Multiple file names are joined in a single ORed set before participating in AND option selection.</dd>
+<p><b>Notes</b></p>
+<p>If any list request option is specified, other list requests must be specifically requested - e.g., if -U is specified for the listing of UNIX socket files, NFS files won't be listed unless -N is also specified; or if a user list is specified with the -u option, UNIX domain socket files, belonging to users not in the list, won't be listed unless the -U option is also specified.</p>
+<p>Normally list options that are specifically stated are ORed - i.e., specifying the -i option without an address and the -ufoo option produces a listing of all network files OR files belonging to processes owned by user ''foo''. Three exceptions are: 1) the '^' (negated) login name or user ID (UID), specified with the -u option; 2) the '^' (negated) process ID (PID), specified with the -p option; and 3) the '^' (negated) process group ID (PGID), specified with the -g option. Since they represent exclusions, they are applied without ORing or ANDing and take effect before any other selection criteria are applied.</p>
+<p>The -a option may be used to AND the selections. For example, specifying -a, -U, and -ufoo produces a listing of only UNIX socket files that belong to processes owned by user ''foo''.</p>
+<p>Caution: the -a option causes all list selection options to be ANDed; it can't be used to cause ANDing of selected pairs of selection options by placing it between them, even though its placement there is acceptable. Wherever -a is placed, it causes the ANDing of all selection options.</p>
+<p>Items of the same selection set - command names, file descriptors, network addresses, process identifiers, user identifiers, zone names, security contexts - are joined in a single ORed set and applied before the result participates in ANDing. Thus, for example, specifying -i@aaa.bbb, -i@ccc.ddd, -a, and -ufff,ggg will select the listing of files that belong to either login ''fff'' OR ''ggg'' AND have network connections to either host aaa.bbb OR ccc.ddd.</p>
+<p>Options may be grouped together following a single prefix -- e.g., the option set ''-a -b -C'' may be stated as -abC. However, since values are optional following +|-f, -F, -g, -i, +|-L, -o, +|-r, -S, -T, -x and -z. when you have no values for them be careful that the following character isn't ambiguous. For example, -Fn might represent the -F and -n options, or it might represent the n field identifier character following the -F option. When ambiguity is possible, start a new option with a '-' character - e.g., ''-F -n''. If the next option is a file name, follow the possibly ambiguous option with ''--'' - e.g., ''-F -- name''.</p>
+<p>Either the '+' or the '-' prefix may be applied to a group of options. Options that don't take on separate meanings for each prefix - e.g., -i - may be grouped under either prefix. Thus, for example, ''+M -i'' may be stated as ''+Mi'' and the group means the same as the separate options. Be careful of prefix grouping when one or more options in the group does take on separate meanings under different prefixes - e.g., +|-M; ''-iM'' is not the same request as ''-i +M''. When in doubt, use separate options with appropriate prefixes. </p>
+<p><b>Security</b></p>
+<blockquote>
+<p>Lsof has three features that may cause security concerns. First, its default compilation mode allows anyone to list all open files with it. Second, by default it creates a user-readable and user-writable device cache file in the home directory of the real user ID that executes lsof. (The list-all-open-files and device cache features may be disabled when lsof is compiled.) Third, its -k and -m options name alternate kernel name list or memory files.</p>
+<p>Restricting the listing of all open files is controlled by the compile-time HASSECURITY and HASNOSOCKSECURITY options. When HASSECURITY is defined, lsof will allow only the root user to list all open files. The non-root user may list only open files of processes with the same user IDentification number as the real user ID number of the lsof process (the one that its user logged on with).</p>
+<p>However, if HASSECURITY and HASNOSOCKSECURITY are both defined, anyone may list open socket files, provided they are selected with the -i option.</p>
+<p>When HASSECURITY is not defined, anyone may list all open files.</p>
+<p>Help output, presented in response to the -h or -? option, gives the status of the HASSECURITY and HASNOSOCKSECURITY definitions.</p>
+<p>See the Security section of the 00README file of the lsof distribution for information on building lsof with the HASSECURITY and HASNOSOCKSECURITY options enabled.</p>
+<p>Creation and use of a user-readable and user-writable device cache file is controlled by the compile-time HASDCACHE option. See the DEVICE CACHE FILE section and the sections that follow it for details on how its path is formed. For security considerations it is important to note that in the default lsof distribution, if the real user ID under which lsof is executed is root, the device cache file will be written in root's home directory - e.g., / or /root. When HASDCACHE is not defined, lsof does not write or attempt to read a device cache file.</p>
+<p>When HASDCACHE is defined, the lsof help output, presented in response to the -h, -D?, or -? options, will provide device cache file handling information. When HASDCACHE is not defined, the -h or -? output will have no -D option description.</p>
+<p>Before you decide to disable the device cache file feature - enabling it improves the performance of lsof by reducing the startup overhead of examining all the nodes in /dev (or /devices) - read the discussion of it in the 00DCACHE file of the lsof distribution and the lsof FAQ (The FAQ section gives its location.)</p>
+<p>WHEN IN DOUBT, YOU CAN TEMPORARILY DISABLE THE USE OF THE DEVICE CACHE FILE WITH THE -Di OPTION.</p>
+<p>When lsof user declares alternate kernel name list or memory files with the -k and -m options, lsof checks the user's authority to read them with access(2). This is intended to prevent whatever special power lsof's modes might confer on it from letting it read files not normally accessible via the authority of the real user ID. </p>
+</blockquote>
+<p><b>Output</b></p>
+<blockquote>
+<p>This section describes the information lsof lists for each open file. See the OUTPUT FOR OTHER PROGRAMS section for additional information on output that can be processed by another program.</p>
+<p>Lsof only outputs printable (declared so by isprint(3)) 8 bit characters. Non-printable characters are printed in one of three forms: the C ''\[bfrnt]'' form; the control character '^' form (e.g., ''^@''); or hexadecimal leading ''\x'' form (e.g., ''\xab''). Space is non-printable in the COMMAND column (''\x20'') and printable elsewhere.</p>
+<p>For some dialects - if HASSETLOCALE is defined in the dialect's machine.h header file - lsof will print the extended 8 bit characters of a language locale. The lsof process must be supplied a language locale environment variable (e.g., LANG) whose value represents a known language locale in which the extended characters are considered printable by isprint(3). Otherwise lsof considers the extended characters non-printable and prints them according to its rules for non-printable characters, stated above. Consult your dialect's setlocale(3) man page for the names of other environment variables that may be used in place of LANG - e.g., LC_ALL, LC_CTYPE, etc.</p>
+<p>Lsof's language locale support for a dialect also covers wide characters - e.g., UTF-8 - when HASSETLOCALE and HASWIDECHAR are defined in the dialect's machine.h header file, and when a suitable language locale has been defined in the appropriate environment variable for the lsof process. Wide characters are printable under those conditions if iswprint(3) reports them to be. If HASSETLOCALE, HASWIDECHAR and a suitable language locale aren't defined, or if iswprint(3) reports wide characters that aren't printable, lsof considers the wide characters non-printable and prints each of their 8 bits according to its rules for non-printable characters, stated above.</p>
+<p>Consult the answers to the &quot;Language locale support&quot; questions in the lsof FAQ (The FAQ section gives its location.) for more information.</p>
+<p>Lsof dynamically sizes the output columns each time it runs, guaranteeing that each column is a minimum size. It also guarantees that each column is separated from its predecessor by at least one space.</p>
+</blockquote>
+<p>COMMAND</p>
+<p>contains the first nine characters of the name of the UNIX command associated with the process. If a non-zero w value is specified to the +cw option, the column contains the first w characters of the name of the UNIX command associated with the process up to the limit of characters supplied to lsof by the UNIX dialect. (See the description of the +c w command or the lsof FAQ for more information. The FAQ section gives its location.) <br>
+If<br>
+w is less than the length of the column title, ''COMMAND'', it will be raised to that length. <br>
+If a zero<br>
+w value is specified to the +c w option, the column contains all the characters of the name of the UNIX command associated with the process. <br>
+All command name characters maintained by the kernel in its structures<br>
+are displayed in field output when the command name descriptor ('c') is specified. See the OUTPUT FOR OTHER COMMANDS section for information on selecting field output and the associated command name descriptor. <br>
+<br>
+PID<br>
+is the Process IDentification number of the process. <br>
+ZONE<br>
+is the Solaris 10 and higher zone name. This column must be selected with the -z option. <br>
+SECURITY-CONTEXT<br>
+is the SELinux security context. This column must be selected with the -Z option. <br>
+PPID<br>
+is the Parent Process IDentification number of the process. It is only displayed when the -R option has been specified. <br>
+PGID<br>
+is the process group IDentification number associated with the process. It is only displayed when the -g option has been specified. <br>
+USER<br>
+is the user ID number or login name of the user to whom the process belongs, usually the same as reported by ps(1). However, on Linux USER is the user ID number or login that owns the directory in /proc where lsof finds information about the process. Usually that is the same value reported by ps(1), but may differ when the process has changed its effective user ID. (See the -l option description for information on when a user ID number or login name is displayed.) <br>
+FD<br>
+is the File Descriptor number of the file or:<br>
+cwd current working directory; Lnn library references (AIX); err FD information error (see NAME column); jld jail directory (FreeBSD); ltx shared library text (code and data); Mxx hex memory-mapped type number xx. m86 DOS Merge mapped file; mem memory-mapped file; mmap memory-mapped device; pd parent directory; rtd root directory; tr kernel trace file (OpenBSD); txt program text (code and data); v86 VP/ix mapped file;<br>
+FD is followed by one of these characters, describing the <b>mode</b> under which the file is open:</p>
+<blockquote>
+<p>r for read access;<br>
+w for write access;<br>
+u for read and write access;<br>
+space if mode unknown and no lock
+character follows;<br>
+'-' if mode unknown and lock character follows</p>
+</blockquote>
+<p>The mode character is followed by one of these <b>lock</b> characters, describing
+the type of lock applied to the file:<br>
+N for a Solaris NFS lock of unknown type;</p>
+<blockquote>
+<p>r for read lock on part of the file;<br>
+R for a read lock on the entire file;<br>
+w for a write lock on part of the file;<br>
+W for a write lock on the entire file;<br>
+u for a read and write lock of any length;<br>
+U for a lock of unknown type;<br>
+x for an SCO OpenServer Xenix lock on part
+of the file;<br>
+X for an SCO OpenServer Xenix lock on the
+entire file;<br>
+space if there is no lock.</p>
+</blockquote>
+<p><br>
+See the
+LOCKS section for more information on the lock information character. <br>
+The FD column contents constitutes a single field for parsing in
+post-processing scripts. <br>
+<br>
+TYPE
+is the type of the node associated with the file - e.g., GDIR, GREG, VDIR, VREG, etc. <br>
+or ''IPv4'' for an IPv4 socket;<br>
+or ''IPv6'' for an open IPv6 network file - even if its address is<br>
+IPv4, mapped in an IPv6 address; <br>
+or ''ax25'' for a Linux AX.25 socket;<br>
+or ''inet'' for an Internet domain socket;<br>
+or ''sock'' for a socket of unknown domain;<br>
+or ''unix'' for a UNIX domain socket;<br>
+or ''BLK'' for a block special file;<br>
+or ''CHR'' for a character special file;<br>
+or ''DEL'' for a Linux map file that has been deleted;<br>
+or ''DIR'' for a directory;<br>
+or ''DOOR'' for a VDOOR file;<br>
+or ''FIFO'' for a FIFO special file;<br>
+or ''KQUEUE'' for a BSD style kernel event queue file;<br>
+or ''LINK'' for a symbolic link file;<br>
+or ''MPB'' for a multiplexed block file;<br>
+or ''MPC'' for a multiplexed character file;<br>
+or ''NOFD'' for a Linux /proc/&lt;PID&gt;/fd directory that can't be opened --<br>
+the directory path appears in the NAME column, followed by an error message; <br>
+or ''PAS'' for a<br>
+/proc/as file; <br>
+or ''PAXV'' for a<br>
+/proc/auxv file; <br>
+or ''PXMP'' for a<br>
+/proc/xmap file; <br>
+or ''REG'' for a regular file;<br>
+or ''SMT'' for a shared memory transport file;<br>
+or ''STSO'' for a stream socket;<br>
+or ''UNNM'' for an unnamed type file;<br>
+<br>
+or the four type number octets if the corresponding name isn't known.<br>
+FILE-ADDR<br>
+contains the kernel file structure address when f has been specified to +f; <br>
+FCT<br>
+contains the file reference count from the kernel file structure when c has been specified to +f; <br>
+FILE-FLAG<br>
+when g or G has been specified to +f, this field contains the contents of the f_flag[s] member of the kernel file structure and the kernel's per-process open file flags (if available); 'G' causes them to be displayed in hexadecimal; 'g', as short-hand names; two lists may be displayed with entries separated by commas, the lists separated by a semicolon (';'); the first list may contain short-hand names for f_flag[s] values from the following table:<br>
+</p>
+<blockquote>
+<p>AIO asynchronous I/O (e.g., FAIO) <br>
+AP append <br>
+ASYN asynchronous I/O (e.g., FASYNC) <br>
+BAS block, test, and set in use <br>
+BKIU block if in use BL use block offsets <br>
+BSK block seek <br>
+CA copy avoid <br>
+CIO concurrent I/O <br>
+CLON clone <br>
+CLRD <br>
+CL read <br>
+CR create <br>
+DF defer <br>
+DFI defer IND <br>
+DFLU data flush <br>
+DIR direct <br>
+DLY delay <br>
+DOCL do clone <br>
+DSYN data-only integrity <br>
+EVO event only EX open for exec <br>
+EXCL exclusive open <br>
+FSYN synchronous writes <br>
+GCDF defer during unp_gc() (AIX) <br>
+GCMK mark during unp_gc() (AIX) <br>
+GTTY accessed via /dev/tty <br>
+HUP HUP in progress <br>
+KERN kernel <br>
+KIOC kernel-issued ioctl <br>
+LCK has lock LG large file <br>
+MBLK stream message block <br>
+MK mark <br>
+MNT mount <br>
+MSYN multiplex synchronization <br>
+NB non-blocking I/O <br>
+NBDR no BDRM check <br>
+NBIO SYSV non-blocking I/O NBF n-buffering in effect <br>
+NC no cache <br>
+ND no delay <br>
+NDSY no data synchronization <br>
+NET network <br>
+NMFS NM file system <br>
+NOTO disable background stop <br>
+NSH no share NTTY no controlling TTY <br>
+OLRM OLR mirror <br>
+PAIO POSIX asynchronous I/O <br>
+PP POSIX pipe R read RC file and record locking cache <br>
+REV revoked <br>
+RSH shared read <br>
+RSYN read synchronization <br>
+SL shared lock <br>
+SNAP cooked snapshot <br>
+SOCK socket <br>
+SQSH Sequent shared set on open <br>
+SQSV Sequent <br>
+SVM set on open <br>
+SQR Sequent set repair on open <br>
+SQS1 Sequent full shared open <br>
+SQS2 Sequent partial shared open <br>
+STPI stop I/O <br>
+SWR synchronous read <br>
+SYN file integrity while writing <br>
+TCPM avoid TCP collision <br>
+TR truncate W write <br>
+WKUP parallel I/O synchronization <br>
+WTG parallel I/O synchronization <br>
+VH vhangup pending <br>
+VTXT virtual text <br>
+XL exclusive lock</p>
+</blockquote>
+<p><br>
+This list of names was derived from F* #define's in dialect header files <span class="code">&lt;fcntl.h&gt;, &lt;linux&lt;/fs.h&gt;, &lt;sys/fcntl.c&gt;, &lt;sys/fcntlcom.h&gt;</span>, and <span class="code">&lt;sys/file.h&gt;</span>; <br>
+see the lsof.h header file for a list showing the correspondence between the above short-hand names and the header file definitions; <br>
+the second list (after the semicolon) may contain short-hand names
+for kernel per-process open file flags from this table:</p>
+<blockquote>
+<p>ALLC allocated BR the file has been read BHUP activity stopped by SIGHUP BW the file has been written CLSG closing CX close-on-exec (see fcntl(F_SETFD)) LCK lock was applied MP memory-mapped OPIP open pending - in progress RSVW reserved wait SHMT UF_FSHMAT set (AIX) USE in use (multi-threaded)NODE-ID<br>
+(or INODE-ADDR for some dialects) contains a unique identifier for the file node (usually the kernel vnode or inode address, but also occasionally a concatenation of device and node number) when n has been specified to +f; <br>
+<br>
+DEVICE<br>
+contains the device numbers, separated by commas, for a character special, block special, regular, directory or NFS file; <br>
+or ''memory'' for a memory file system node under Tru64 UNIX;<br>
+or the address of the private data area of a Solaris socket<br>
+stream; <br>
+or a kernel reference address that identifies the file<br>
+(The kernel reference address may be used for FIFO's, for example.); <br>
+or<br>
+the base address or device name of a Linux AX.25 socket device. <br>
+Usually only the lower thirty two bits of Tru64 UNIX kernel addresses<br>
+are displayed. <br>
+<br>
+SIZE, SIZE/OFF, or OFFSET<br>
+is the size of the file or the file offset in bytes. A value is displayed in this column only if it is available. Lsof displays whatever value - size or offset - is appropriate for the type of the file and the version of lsof. <br>
+On some UNIX dialects
+lsof can't obtain accurate or consistent file offset information from its kernel data sources, sometimes just for particular kinds of files (e.g., socket files.) In other cases, files don't have true sizes - e.g., sockets, FIFOs, pipes - so lsof displays for their sizes the content amounts it finds in their kernel buffer descriptors (e.g., socket buffer size counts or TCP/IP window sizes.) Consult the lsof FAQ (The FAQ section gives its location.) for more information. <br>
+The file size is displayed in decimal;<br>
+the offset is normally displayed in decimal with a leading ''0t'' if it contains 8 digits or less; in hexadecimal with a leading ''0x'' if it is longer than 8 digits. (Consult the -o o option description for information on when 8 might default to some other value.) <br>
+Thus the leading ''0t'' and ''0x'' identify an offset when the column<br>
+may contain both a size and an offset (i.e., its title is SIZE/OFF). <br>
+If the
+-o option is specified, lsof always displays the file offset (or nothing if no offset is available) and labels the column OFFSET. The offset always begins with ''0t'' or ''0x'' as described above. <br>
+The lsof user can control the switch from ''0t'' to ''0x'' with the -o o option. Consult its description for more information. <br>
+If the -s option is specified, lsof always displays the file size (or nothing if no size is available) and labels the column SIZE. The -o and -s options are mutually exclusive; they can't both be specified. <br>
+For files that don't have a fixed size - e.g., don't reside<br>
+on a disk device - lsof will display appropriate information about the current size or position of the file if it is available in the kernel structures that define the file. <br>
+<br>
+NLINK<br>
+contains the file link count when +L has been specified; <br>
+<br>
+NODE<br>
+is the node number of a local file; <br>
+or the inode number of an NFS file in the server host;<br>
+or the Internet protocol type - e. g, ''TCP'';<br>
+or ''STR'' for a stream;<br>
+or ''CCITT'' for an HP-UX x.25 socket;<br>
+or the IRQ or inode number of a Linux AX.25 socket device.<br>
+<br>
+NAME<br>
+is the name of the mount point and file system on which the file resides; <br>
+or the name of a file specified in the<br>
+names option (after any symbolic links have been resolved); <br>
+or the name of a character special or block special device;<br>
+or the local and remote Internet addresses of a network file;<br>
+the local host name or IP number is followed by a colon (':'), the port, ''-&gt;'', and the two-part remote address; IP addresses may be reported as numbers or names, depending on the +|-M, -n, and -P options; colon-separated IPv6 numbers are enclosed in square brackets; IPv4 INADDR_ANY and IPv6 IN6_IS_ADDR_UNSPECIFIED addresses, and zero port numbers are represented by an asterisk ('*'); a UDP destination address may be followed by the amount of time elapsed since the last packet was sent to the destination; TCP and UDP remote addresses may be followed by TCP/TPI information in parentheses - state (e.g., ''(ESTABLISHED)'', ''(Unbound)''), queue sizes, and window sizes (not all dialects) - in a fashion similar to what netstat(1) reports; see the -T option description or the description of the TCP/TPI field in OUTPUT FOR OTHER PROGRAMS for more information on state, queue size, and window size; <br>
+or the address or name of a UNIX domain socket, possibly including<br>
+a stream clone device name, a file system object's path name, local and foreign kernel addresses, socket pair information, and a bound vnode address; <br>
+or the local and remote mount point names of an NFS file;<br>
+or ''STR'', followed by the stream name;<br>
+or a stream character device name, followed by ''-&gt;'' and the stream name<br>
+or a list of stream module names, separated by ''-&gt;''; <br>
+or ''STR:'' followed by the SCO OpenServer stream device and module<br>
+names, separated by ''-&gt;''; <br>
+or system directory name, '' -- '', and as many components of the path<br>
+name as lsof can find in the kernel's name cache for selected dialects (See the KERNEL NAME CACHE section for more information.); <br>
+or ''PIPE-&gt;'', followed by a Solaris kernel pipe destination address;<br>
+or ''COMMON:'', followed by the vnode device information structure's<br>
+device name, for a Solaris common vnode; <br>
+or the address family, followed by a slash ('/'), followed by fourteen<br>
+comma-separated bytes of a non-Internet raw socket address; <br>
+or the HP-UX x.25 local address, followed by the virtual connection<br>
+number (if any), followed by the remote address (if any); <br>
+or ''(dead)'' for disassociated Tru64 UNIX files - typically terminal files<br>
+that have been flagged with the TIOCNOTTY ioctl and closed by daemons; <br>
+or ''rd=&lt;offset&gt;'' and ''wr=&lt;offset&gt;'' for the values of the<br>
+read and write offsets of a FIFO; <br>
+or ''clone n:/dev/event'' for SCO OpenServer file clones of the<br>
+/dev/event device, where n is the minor device number of the file; <br>
+or ''(socketpair: n)'' for a Solaris 2.6, 8, 9 or 10
+UNIX domain socket, created by the socketpair(3N) network function; <br>
+or ''no PCB'' for socket files that do not have a protocol block<br>
+associated with them, optionally followed by '', CANTSENDMORE'' if sending on the socket has been disabled, or '', CANTRCVMORE'' if receiving on the socket has been disabled (e.g., by the shutdown(2) function); <br>
+or the local and remote addresses of a Linux IPX socket file<br>
+in the form &lt;net&gt;:[&lt;node&gt;:]&lt;port&gt;, followed in parentheses by the transmit and receive queue sizes, and the connection state; <br>
+or ''dgram'' or ''stream'' for the type UnixWare 7.1.1 and above in-kernel<br>
+UNIX domain sockets, followed by a colon (':') and the local path name when available, followed by ''-&gt;'' and the remote path name or kernel socket address in hexadecimal when available.</p>
+</blockquote>
+<p>For dialects that support a ''namefs'' file system, allowing one file to be attached to another with fattach(3C), lsof will add ''(FA:&lt;address1&gt;&lt;direction&gt;&lt;address2&gt;)'' to the NAME column. &lt;address1&gt; and &lt;address2&gt; are hexadecimal vnode addresses. &lt;direction&gt; will be ''&lt;-'' if &lt;address2&gt; has been fattach'ed to this vnode whose address is &lt;address1&gt;; and ''-&gt;'' if &lt;address1&gt;, the vnode address of this vnode, has been fattach'ed to &lt;address2&gt;. &lt;address1&gt; may be omitted if it already appears in the DEVICE column.</p>
+<p>Lsof may add two parenthetical notes to the NAME column for open Solaris 10 files: ''(?)'' if lsof considers the path name of questionable accuracy; and ''(deleted)'' if the -X option has been specified and lsof detects the open file's path name has been deleted. Consult the lsof FAQ (The FAQ section gives its location.) for more information on these NAME column additions.</p>
+<p><b>Locks</b><br>
+Lsof can't adequately report the wide variety of UNIX dialect file locks in a single character. What it reports in a single character is a compromise between the information it finds in the kernel and the limitations of the reporting format.</p>
+<p>Moreover, when a process holds several byte level locks on a file, lsof only reports the status of the first lock it encounters. If it is a byte level lock, then the lock character will be reported in lower case - i.e., 'r', 'w', or 'x' - rather than the upper case equivalent reported for a full file lock.</p>
+<p>Generally lsof can only report on locks held by local processes on local files. When a local process sets a lock on a remotely mounted (e.g., NFS) file, the remote server host usually records the lock state. One exception is Solaris - at some patch levels of 2.3, and in all versions above 2.4, the Solaris kernel records information on remote locks in local structures.</p>
+<p>Lsof has trouble reporting locks for some UNIX dialects. Consult the BUGS section of this manual page or the lsof FAQ (The FAQ section gives its location.) for more information.<br>
+<br>
+<b>Output for Other Programs</b><br>
+When the -F option is specified, lsof produces output that is suitable for processing by another program - e.g, an awk or Perl script, or a C program.</p>
+<p>Each unit of information is output in a field that is identified with a leading character and terminated by a NL (012) (or a NUL (000) if the 0 (zero) field identifier character is specified.) The data of the field follows immediately after the field identification character and extends to the field terminator.</p>
+<p>It is possible to think of field output as process and file sets. A process set begins with a field whose identifier is 'p' (for process IDentifier (PID)). It extends to the beginning of the next PID field or the beginning of the first file set of the process, whichever comes first. Included in the process set are fields that identify the command, the process group IDentification (PGID) number, and the user ID (UID) number or login name.</p>
+<p>A file set begins with a field whose identifier is 'f' (for file descriptor). It is followed by lines that describe the file's access mode, lock state, type, device, size, offset, inode, protocol, name and stream module names. It extends to the beginning of the next file or process set, whichever comes first.</p>
+<p>When the NUL (000) field terminator has been selected with the 0 (zero) field identifier character, lsof ends each process and file set with a NL (012) character.</p>
+<p>Lsof always produces one field, the PID ('p') field. All other fields may be declared optionally in the field identifier character list that follows the -F option. When a field selection character identifies an item lsof does not normally list - e.g., PPID, selected with -R - specification of the field character - e.g., ''-FR'' - also selects the listing of the item.</p>
+<p>It is entirely possible to select a set of fields that cannot easily be parsed - e.g., if the field descriptor field is not selected, it may be difficult to identify file sets. To help you avoid this difficulty, lsof supports the -F option; it selects the output of all fields with NL terminators (the -F0 option pair selects the output of all fields with NUL terminators). For compatibility reasons neither -F nor -F0 select the raw device field.</p>
+<p>These are the fields that lsof will produce. The single character listed first is the field identifier.</p>
+<blockquote>
+<p>a file access mode<br>
+c process command name (all characters from proc or<br>
+user structure)<br>
+C file structure share count<br>
+d file's device character code<br>
+D file's major/minor device number (0x&lt;hexadecimal&gt;)<br>
+f file descriptor<br>
+F file structure address (0x&lt;hexadecimal&gt;)<br>
+G file flaGs (0x&lt;hexadecimal&gt;; names if +fg follows)<br>
+i file's inode number<br>
+k link count<br>
+l file's lock status<br>
+L process login name<br>
+m marker between repeated output<br>
+n file name, comment, Internet address<br>
+N node identifier (ox&lt;hexadecimal&gt;<br>
+o file's offset (decimal)<br>
+p process ID (always selected)<br>
+g process group ID<br>
+P protocol name<br>
+r raw device number (0x&lt;hexadecimal&gt;)<br>
+R parent process ID<br>
+s file's size (decimal)<br>
+S file's stream identification<br>
+t file's type<br>
+T TCP/TPI information, identified by prefixes (the<br>
+'=' is part of the prefix):<br>
+QR=&lt;read queue size&gt;<br>
+QS=&lt;send queue size&gt;<br>
+SO=&lt;socket options and values&gt; (not all dialects)<br>
+SS=&lt;socket states&gt; (not all dialects)<br>
+ST=&lt;connection state&gt;<br>
+TF=&lt;TCP flags and values&gt; (not all dialects)<br>
+WR=&lt;window read size&gt; (not all dialects)<br>
+WW=&lt;window write size&gt; (not all dialects)<br>
+(TCP/TPI information isn't reported for all supported<br>
+UNIX dialects. The -h or -? help output for the<br>
+-T option will show what TCP/TPI reporting can be<br>
+requested.)<br>
+u process user ID<br>
+z Solaris 10 and higher zone name<br>
+0 use NUL field terminator character in place of NL<br>
+1-9 dialect-specific field identifiers (The output<br>
+of -F? identifies the information to be found<br>
+in dialect-specific fields.)</p>
+</blockquote>
+<p>You can get on-line help information on these characters and their descriptions by specifying the -F? option pair. (Escape the '?' character as your shell requires.) Additional information on field content can be found in the OUTPUT section.</p>
+<p>As an example, ''-F pcfn'' will select the process ID ('p'), command name ('c'), file descriptor ('f') and file name ('n') fields with an NL field terminator character; ''-F pcfn0'' selects the same output with a NUL (000) field terminator character.</p>
+<p>Lsof doesn't produce all fields for every process or file set, only those that are available. Some fields are mutually exclusive: file device characters and file major/minor device numbers; file inode number and protocol name; file name and stream identification; file size and offset. One or the other member of these mutually exclusive sets will appear in field output, but not both.</p>
+<p>Normally lsof ends each field with a NL (012) character. The 0 (zero) field identifier character may be specified to change the field terminator character to a NUL (000). A NUL terminator may be easier to process with xargs (1), for example, or with programs whose quoting mechanisms may not easily cope with the range of characters in the field output. When the NUL field terminator is in use, lsof ends each process and file set with a NL (012).</p>
+<p>Three aids to producing programs that can process lsof field output are included in the lsof distribution. The first is a C header file, lsof_fields.h, that contains symbols for the field identification characters, indexes for storing them in a table, and explanation strings that may be compiled into programs. Lsof uses this header file.</p>
+<p>The second aid is a set of sample scripts that process field output, written in awk, Perl 4, and Perl 5. They're located in the scripts subdirectory of the lsof distribution.</p>
+<p>The third aid is the C library used for the lsof test suite. The test suite is written in C and uses field output to validate the correct operation of lsof. The library can be found in the tests/LTlib.c file of the lsof distribution. The library uses the first aid, the lsof_fields.h header file.<br>
+Blocks and Timeouts<br>
+Lsof can be blocked by some kernel functions that it uses - lstat(2), readlink(2), and stat(2). These functions are stalled in the kernel, for example, when the hosts where mounted NFS file systems reside become inaccessible.</p>
+<p>Lsof attempts to break these blocks with timers and child processes, but the techniques are not wholly reliable. When lsof does manage to break a block, it will report the break with an error message. The messages may be suppressed with the -t and -w options.</p>
+<p>The default timeout value may be displayed with the -h or -? option, and it may be changed with the -S [t] option. The minimum for t is two seconds, but you should avoid small values, since slow system responsiveness can cause short timeouts to expire unexpectedly and perhaps stop lsof before it can produce any output.</p>
+<p>When lsof has to break a block during its access of mounted file system information, it normally continues, although with less information available to display about open files.</p>
+<p>Lsof can also be directed to avoid the protection of timers and child processes when using the kernel functions that might block by specifying the -O option. While this will allow lsof to start up with less overhead, it exposes lsof completely to the kernel situations that might block it. Use this option cautiously.<br>
+Avoiding Kernel Blocks</p>
+<p>You can use the -b option to tell lsof to avoid using kernel functions that would block. Some cautions apply.</p>
+<p>First, using this option usually requires that your system supply alternate device numbers in place of the device numbers that lsof would normally obtain with the lstat(2) and stat(2) kernel functions. See the ALTERNATE DEVICE NUMBERS section for more information on alternate device numbers.</p>
+<p>Second, you can't specify names for lsof to locate unless they're file system names. This is because lsof needs to know the device and inode numbers of files listed with names in the lsof options, and the -b option prevents lsof from obtaining them. Moreover, since lsof only has device numbers for the file systems that have alternates, its ability to locate files on file systems depends completely on the availability and accuracy of the alternates. If no alternates are available, or if they're incorrect, lsof won't be able to locate files on the named file systems.</p>
+<p>Third, if the names of your file system directories that lsof obtains from your system's mount table are symbolic links, lsof won't be able to resolve the links. This is because the -b option causes lsof to avoid the kernel readlink(2) function it uses to resolve symbolic links.</p>
+<p>Finally, using the -b option causes lsof to issue warning messages when it needs to use the kernel functions that the -b option directs it to avoid. You can suppress these messages by specifying the -w option, but if you do, you won't see the alternate device numbers reported in the warning messages.<br>
+Alternate Device Numbers</p>
+<p>On some dialects, when lsof has to break a block because it can't get information about a mounted file system via the lstat(2) and stat(2) kernel functions, or because you specified the -b option, lsof can obtain some of the information it needs - the device number and possibly the file system type - from the system mount table. When that is possible, lsof will report the device number it obtained. (You can suppress the report by specifying the -w option.)</p>
+<p>You can assist this process if your mount table is supported with an /etc/mtab or /etc/mnttab file that contains an options field by adding a ''dev=xxxx'' field for mount points that do not have one in their options strings. Note: you must be able to edit the file - i.e., some mount tables like recent Solaris /etc/mnttab or Linux /proc/mounts are read-only and can't be modified.</p>
+<p>You may also be able to supply device numbers using the +m and +m m options, provided they are supported by your dialect. Check the output of lsof's -h or -? options to see if the +m and +m m options are available.</p>
+<p>The ''xxxx'' portion of the field is the hexadecimal value of the file system's device number. (Consult the st_dev field of the output of the lstat(2) and stat(2) functions for the appropriate values for your file systems.) Here's an example from a Sun Solaris 2.6 /etc/mnttab for a file system remotely mounted via NFS:</p>
+<p> nfs ignore,noquota,dev=2a40001</p>
+<p>There's an advantage to having ''dev=xxxx'' entries in your mount table file, especially for file systems that are mounted from remote NFS servers. When a remote server crashes and you want to identify its users by running lsof on one of its clients, lsof probably won't be able to get output from the lstat(2) and stat(2) functions for the file system. If it can obtain the file system's device number from the mount table, it will be able to display the files open on the crashed NFS server.</p>
+<p>Some dialects that do not use an ASCII /etc/mtab or /etc/mnttab file for the mount table may still provide an alternative device number in their internal mount tables. This includes AIX, Apple Darwin, FreeBSD, NetBSD, OpenBSD, and Tru64 UNIX. Lsof knows how to obtain the alternative device number for these dialects and uses it when its attempt to lstat(2) or stat(2) the file system is blocked.</p>
+<p>If you're not sure your dialect supplies alternate device numbers for file systems from its mount table, use this lsof incantation to see if it reports any alternate device numbers:</p>
+<p>lsof -b</p>
+<p>Look for standard error file warning messages that begin ''assuming &quot;dev=xxxx&quot; from ...''.<br>
+Kernel Name Cache</p>
+<p>Lsof is able to examine the kernel's name cache or use other kernel facilities (e.g., the ADVFS 4.x tag_to_path() function under Tru64 UNIX) on some dialects for most file system types, excluding AFS, and extract recently used path name components from it. (AFS file system path lookups don't use the kernel's name cache; some Solaris VxFS file system operations apparently don't use it, either.)</p>
+<p>Lsof reports the complete paths it finds in the NAME column. If lsof can't report all components in a path, it reports in the NAME column the file system name, followed by a space, two '-' characters, another space, and the name components it has located, separated by the '/' character.</p>
+<p>When lsof is run in repeat mode - i.e., with the -r option specified - the extent to which it can report path name components for the same file may vary from cycle to cycle. That's because other running processes can cause the kernel to remove entries from its name cache and replace them with others.</p>
+<p>Lsof's use of the kernel name cache to identify the paths of files can lead it to report incorrect components under some circumstances. This can happen when the kernel name cache uses device and node number as a key (e.g., SCO OpenServer) and a key on a rapidly changing file system is reused. If the UNIX dialect's kernel doesn't purge the name cache entry for a file when it is unlinked, lsof may find a reference to the wrong entry in the cache. The lsof FAQ (The FAQ section gives its location.) has more information on this situation.</p>
+<p>Lsof can report path name components for these dialects:</p>
+<p> FreeBSD<br>
+HP-UX<br>
+Linux<br>
+NetBSD<br>
+NEXTSTEP<br>
+OpenBSD<br>
+OPENSTEP<br>
+SCO OpenServer<br>
+SCO|Caldera UnixWare<br>
+Solaris<br>
+Tru64 UNIX</p>
+<p>Lsof can't report path name components for these dialects:AIX</p>
+<p>If you want to know why lsof can't report path name components for some dialects, see the lsof FAQ (The FAQ section gives its location.)<br>
+Device Cache File</p>
+<p>Examining all members of the /dev (or /devices) node tree with stat(2) functions can be time consuming. What's more, the information that lsof needs - device number, inode number, and path - rarely changes.</p>
+<p>Consequently, lsof normally maintains an ASCII text file of cached /dev (or /devices) information (exception: the /proc-based Linux lsof where it's not needed.) The local system administrator who builds lsof can control the way the device cache file path is formed, selecting from these options:</p>
+<p> Path from the -D option;<br>
+Path from an environment variable;<br>
+System-wide path;<br>
+Personal path (the default);<br>
+Personal path, modified by an environment variable.</p>
+<p>Consult the output of the -h, -D? , or -? help options for the current state of device cache support. The help output lists the default read-mode device cache file path that is in effect for the current invocation of lsof. The -D? option output lists the read-only and write device cache file paths, the names of any applicable environment variables, and the personal device cache path format.</p>
+<p>Lsof can detect that the current device cache file has been accidentally or maliciously modified by integrity checks, including the computation and verification of a sixteen bit Cyclic Redundancy Check (CRC) sum on the file's contents. When lsof senses something wrong with the file, it issues a warning and attempts to remove the current cache file and create a new copy, but only to a path that the process can legitimately write.</p>
+<p>The path from which a lsof process may attempt to read a device cache file may not be the same as the path to which it can legitimately write. Thus when lsof senses that it needs to update the device cache file, it may choose a different path for writing it from the path from which it read an incorrect or outdated version.</p>
+<p>If available, the -Dr option will inhibit the writing of a new device cache file. (It's always available when specified without a path name argument.)</p>
+<p>When a new device is added to the system, the device cache file may need to be recreated. Since lsof compares the mtime of the device cache file with the mtime and ctime of the /dev (or /devices) directory, it usually detects that a new device has been added; in that case lsof issues a warning message and attempts to rebuild the device cache file.</p>
+<p>Whenever lsof writes a device cache file, it sets its ownership to the real UID of the executing process, and its permission modes to 0600, this restricting its reading and writing to the file's owner.<br>
+Lsof Permissions that Affect Device Cache File Access</p>
+<p>Two permissions of the lsof executable affect its ability to access device cache files. The permissions are set by the local system administrator when lsof is installed.</p>
+<p>The first and rarer permission is setuid-root. It comes into effect when lsof is executed; its effective UID is then root, while its real (i.e., that of the logged-on user) UID is not. The lsof distribution recommends that versions for these dialects run setuid-root.</p>
+<p> HP-UX 11.11 and 11.23<br>
+Linux</p>
+<p>The second and more common permission is setgid. It comes into effect when the effective group IDentification number (GID) of the lsof process is set to one that can access kernel memory devices - e.g., ''kmem'', ''sys'', or ''system''.</p>
+<p>An lsof process that has setgid permission usually surrenders the permission after it has accessed the kernel memory devices. When it does that, lsof can allow more liberal device cache path formations. The lsof distribution recommends that versions for these dialects run setgid and be allowed to surrender setgid permission.</p>
+<p> AIX 5.[123]<br>
+Apple Darwin 7.x Power Macintosh systems<br>
+FreeBSD 4.x, 4.1x, 5.x and [67].x for x86-based systems<br>
+FreeBSD 5.x and [67].x for Alpha, AMD64 and Sparc64-based<br>
+systems<br>
+HP-UX 11.00<br>
+NetBSD 1.[456], 2.x and 3.x for Alpha, x86, and SPARC-based<br>
+systems<br>
+NEXTSTEP 3.[13] for NEXTSTEP architectures<br>
+OpenBSD 2.[89] and 3.[0-9] for x86-based systems<br>
+OPENSTEP 4.x<br>
+SCO OpenServer Release 5.0.6 for x86-based systems<br>
+SCO|Caldera UnixWare 7.1.4 for x86-based systems<br>
+Solaris 2.6, 8, 9 and 10<br>
+Tru64 UNIX 5.1</p>
+<p>(Note: lsof for AIX 5L and above needs setuid-root permission if its -X option is used.)</p>
+<p>Lsof for these dialects does not support a device cache, so the permissions given to the executable don't apply to the device cache file.</p>
+<p> Linux</p>
+<p>Device Cache File Path from the -d Option</p>
+<p>The -D option provides limited means for specifying the device cache file path. Its ? function will report the read-only and write device cache file paths that lsof will use.</p>
+<p>When the -D b, r, and u functions are available, you can use them to request that the cache file be built in a specific location (b[path]); read but not rebuilt (r[path]); or read and rebuilt (u[path]). The b, r, and u functions are restricted under some conditions. They are restricted when the lsof process is setuid-root. The path specified with the r function is always read-only, even when it is available.</p>
+<p>The b, r, and u functions are also restricted when the lsof process runs setgid and lsof doesn't surrender the setgid permission. (See the LSOF PERMISSIONS THAT AFFECT DEVICE CACHE FILE ACCESS section for a list of implementations that normally don't surrender their setgid permission.)</p>
+<p>A further -D function, i (for ignore), is always available.</p>
+<p>When available, the b function tells lsof to read device information from the kernel with the stat(2) function and build a device cache file at the indicated path.</p>
+<p>When available, the r function tells lsof to read the device cache file, but not update it. When a path argument accompanies -Dr, it names the device cache file path. The r function is always available when it is specified without a path name argument. If lsof is not running setuid-root and surrenders its setgid permission, a path name argument may accompany the r function.</p>
+<p>When available, the u function tells lsof to attempt to read and use the device cache file. If it can't read the file, or if it finds the contents of the file incorrect or outdated, it will read information from the kernel, and attempt to write an updated version of the device cache file, but only to a path it considers legitimate for the lsof process effective and real UIDs.<br>
+Device Cache Path from an Environment Variable</p>
+<p>Lsof's second choice for the device cache file is the contents of the LSOFDEVCACHE environment variable. It avoids this choice if the lsof process is setuid-root, or the real UID of the process is root.</p>
+<p>A further restriction applies to a device cache file path taken from the LSOFDEVCACHE environment variable: lsof will not write a device cache file to the path if the lsof process doesn't surrender its setgid permission. (See the LSOF PERMISSIONS THAT AFFECT DEVICE CACHE FILE ACCESS section for information on implementations that don't surrender their setgid permission.)</p>
+<p>The local system administrator can disable the use of the LSOFDEVCACHE environment variable or change its name when building lsof. Consult the output of -D? for the environment variable's name.<br>
+System-wide Device Cache Path</p>
+<p>The local system administrator may choose to have a system-wide device cache file when building lsof. That file will generally be constructed by a special system administration procedure when the system is booted or when the contents of /dev or /devices) changes. If defined, it is lsof's third device cache file path choice.</p>
+<p>You can tell that a system-wide device cache file is in effect for your local installation by examining the lsof help option output - i.e., the output from the -h or -? option.</p>
+<p>Lsof will never write to the system-wide device cache file path by default. It must be explicitly named with a -D function in a root-owned procedure. Once the file has been written, the procedure must change its permission modes to 0644 (owner-read and owner-write, group-read, and other-read).<br>
+Personal Device Cache Path (default)</p>
+<p>The default device cache file path of the lsof distribution is one recorded in the home directory of the real UID that executes lsof. Added to the home directory is a second path component of the form .lsof_hostname.</p>
+<p>This is lsof's fourth device cache file path choice, and is usually the default. If a system-wide device cache file path was defined when lsof was built, this fourth choice will be applied when lsof can't find the system-wide device cache file. This is the only time lsof uses two paths when reading the device cache file.</p>
+<p>The hostname part of the second component is the base name of the executing host, as returned by gethostname(2). The base name is defined to be the characters preceding the first '.' in the gethostname(2) output, or all the gethostname(2) output if it contains no '.'.</p>
+<p>The device cache file belongs to the user ID and is readable and writable by the user ID alone - i.e., its modes are 0600. Each distinct real user ID on a given host that executes lsof has a distinct device cache file. The hostname part of the path distinguishes device cache files in an NFS-mounted home directory into which device cache files are written from several different hosts.</p>
+<p>The personal device cache file path formed by this method represents a device cache file that lsof will attempt to read, and will attempt to write should it not exist or should its contents be incorrect or outdated.</p>
+<p>The -Dr option without a path name argument will inhibit the writing of a new device cache file.</p>
+<p>The -D? option will list the format specification for constructing the personal device cache file. The conversions used in the format specification are described in the 00DCACHE file of the lsof distribution.<br>
+Modified Personal Device Cache Path</p>
+<p>If this option is defined by the local system administrator when lsof is built, the LSOFPERSDCPATH environment variable contents may be used to add a component of the personal device cache file path.</p>
+<p>The LSOFPERSDCPATH variable contents are inserted in the path at the place marked by the local system administrator with the ''%p'' conversion in the HASPERSDC format specification of the dialect's machine.h header file. (It's placed right after the home directory in the default lsof distribution.)</p>
+<p>Thus, for example, if LSOFPERSDCPATH contains ''LSOF'', the home directory is ''/Homes/abe'', the host name is ''lsof.itap.purdue.edu'', and the HASPERSDC format is the default (''%h/%p.lsof_%L''), the modified personal device cache file path is:</p>
+<p> /Homes/abe/LSOF/.lsof_vic</p>
+<p>The LSOFPERSDCPATH environment variable is ignored when the lsof process is setuid-root or when the real UID of the process is root.</p>
+<p>Lsof will not write to a modified personal device cache file path if the lsof process doesn't surrender setgid permission. (See the LSOF PERMISSIONS THAT AFFECT DEVICE CACHE FILE ACCESS section for a list of implementations that normally don't surrender their setgid permission.)</p>
+<p>If, for example, you want to create a sub-directory of personal device cache file paths by using the LSOFPERSDCPATH environment variable to name it, and lsof doesn't surrender its setgid permission, you will have to allow lsof to create device cache files at the standard personal path and move them to your subdirectory with shell commands.</p>
+<p>The local system administrator may: disable this option when lsof is built; change the name of the environment variable from LSOFPERSDCPATH to something else; change the HASPERSDC format to include the personal path component in another place; or exclude the personal path component entirely. Consult the output of the -D? option for the environment variable's name and the HASPERSDC format specification.<br>
+Diagnostics<br>
+Errors are identified with messages on the standard error file.</p>
+<p>Lsof returns a one (1) if any error was detected, including the failure to locate command names, file names, Internet addresses or files, login names, NFS files, PIDs, PGIDs, or UIDs it was asked to list. If the -V option is specified, lsof will indicate the search items it failed to list.</p>
+<p>It returns a zero (0) if no errors were detected and if it was able to list some information about all the specified search arguments.</p>
+<p>When lsof cannot open access to /dev (or /devices) or one of its subdirectories, or get information on a file in them with stat(2), it issues a warning message and continues. That lsof will issue warning messages about inaccessible files in /dev (or /devices) is indicated in its help output - requested with the -h or &gt;B -? options - with the message:</p>
+<p> Inaccessible /dev warnings are enabled.</p>
+<p>The warning message may be suppressed with the -w option. It may also have been suppressed by the system administrator when lsof was compiled by the setting of the WARNDEVACCESS definition. In this case, the output from the help options will include the message:</p>
+<p> Inaccessible /dev warnings are disabled.</p>
+<p>Inaccessible device warning messages usually disappear after lsof has created a working device cache file.<br>
+<br>
+<b><a name="examples"></a>Examples</b><br>
+For a more extensive set of examples, documented more fully, see the 00QUICKSTART file of the lsof distribution.</p>
+<p>To list all open files, use:</p>
+<p class="code">lsof</p>
+<p>To list all open Internet, x.25 (HP-UX), and UNIX domain files, use:</p>
+<p class="code">lsof -i -U</p>
+<p>To list all open IPv4 network files in use by the process whose PID is 1234, use:</p>
+<p class="code">lsof -i 4 -a -p 1234</p>
+<p>Presuming the UNIX dialect supports IPv6, to list only open IPv6 network files, use:</p>
+<p class="code">lsof -i 6</p>
+<p>To list all files using any protocol on ports 513, 514, or 515 of host wonderland.cc.purdue.edu, use:</p>
+<p class="code">lsof -i @wonderland.cc.purdue.edu:513-515</p>
+<p>To list all files using any protocol on any port of mace.cc.purdue.edu (cc.purdue.edu is the default domain), use:</p>
+<p class="code">lsof -i @mace</p>
+<p>To list all open files for login name ''abe'', or user ID 1234, or process 456, or process 123, or process 789, use:</p>
+<p class="code">lsof -p 456,123,789 -u 1234,abe</p>
+<p>To list all open files on device /dev/hd4, use:</p>
+<p class="code">lsof /dev/hd4</p>
+<p>To find the process that has /u/abe/foo open, use:</p>
+<p class="code">lsof /u/abe/foo</p>
+<p>To send a SIGHUP to the processes that have /u/abe/bar open, use:</p>
+<p class="code">kill -HUP 'lsof -t /u/abe/bar'</p>
+<p>To find any open file, including an open UNIX domain socket file, with the name /dev/log, use:</p>
+<p class="code">lsof /dev/log</p>
+<p>To find processes with open files on the NFS file system named /nfs/mount/point whose server is inaccessible, and presuming your mount table supplies the device number for /nfs/mount/point, use:</p>
+<p class="code">lsof -b /nfs/mount/point</p>
+<p>To do the preceding search with warning messages suppressed, use:</p>
+<p class="code">lsof -bw /nfs/mount/point</p>
+<p>To ignore the device cache file, use:</p>
+<p class="code">lsof -Di</p>
+<p>To obtain PID and command name field output for each process, file descriptor, file device number, and file inode number for each file of each process, use:</p>
+<p class="code">lsof -FpcfDi</p>
+<p>To list the files at descriptors 1 and 3 of every process running the lsof command for login ID ''abe'' every 10 seconds, use:</p>
+<p class="code">lsof -c lsof -a -d 1 -d 3 -u abe -r10</p>
+<p>To list the current working directory of processes running a command that is exactly four characters long and has an 'o' or 'O' in character three, use this regular expression form of the -c c option:</p>
+<p class="code">lsof -c /^..o.$/i -a -d cwd</p>
+<p>To find an IP version 4 socket file by its associated numeric dot-form address, use:</p>
+<p class="code">lsof -i@128.210.15.17</p>
+<p>To find an IP version 6 socket file (when the UNIX dialect supports IPv6) by its associated numeric colon-form address, use:</p>
+<p class="code">lsof -i@[0:1:2:3:4:5:6:7]</p>
+<p>To find an IP version 6 socket file (when the UNIX dialect supports IPv6) by an associated numeric colon-form address that has a run of zeroes in it - e.g., the loop-back address - use:</p>
+<p class="code">lsof -i@[::1]</p>
+<p><b>Bugs</b><br>
+Since lsof reads kernel memory in its search for open files, rapid changes in kernel memory may produce unpredictable results.</p>
+<p>When a file has multiple record locks, the lock status character (following the file descriptor) is derived from a test of the first lock structure, not from any combination of the individual record locks that might be described by multiple lock structures.</p>
+<p>Lsof can't search for files with restrictive access permissions by name unless it is installed with root set-UID permission. Otherwise it is limited to searching for files to which its user or its set-GID group (if any) has access permission.</p>
+<p>The display of the destination address of a raw socket (e.g., for ping) depends on the UNIX operating system. Some dialects store the destination address in the raw socket's protocol control block, some do not.</p>
+<p>Lsof can't always represent Solaris device numbers in the same way that <a href="ls.html">ls</a>(1) does. For example, the major and minor device numbers that the lstat(2) and stat(2) functions report for the directory on which CD-ROM files are mounted (typically /cdrom) are not the same as the ones that it reports for the device on which CD-ROM files are mounted (typically /dev/sr0). (Lsof reports the directory numbers.)</p>
+<p>The support for /proc file systems is available only for BSD and Tru64 UNIX dialects, Linux, and dialects derived from SYSV R4 - e.g., FreeBSD, NetBSD, OpenBSD, Solaris, UnixWare.</p>
+<p>Some /proc file items - device number, inode number, and file size - are unavailable in some dialects. Searching for files in a /proc file system may require that the full path name be specified.</p>
+<p>No text (txt) file descriptors are displayed for Linux processes. All entries for files other than the current working directory, the root directory, and numerical file descriptors are labeled mem descriptors.</p>
+<p>Lsof can't search for Tru64 UNIX named pipes by name, because their kernel implementation of lstat(2) returns an improper device number for a named pipe.</p>
+<p>Lsof can't report fully or correctly on HP-UX 9.01, 10.20, and 11.00 locks because of insufficient access to kernel data or errors in the kernel data. See the lsof FAQ (The FAQ section gives its location.) for details.</p>
+<p>The AIX SMT file type is a fabrication. It's made up for file structures whose type (15) isn't defined in the AIX /usr/include/sys/file.h header file. One way to create such file structures is to run X clients with the DISPLAY variable set to '':0.0''.</p>
+<p>The +|-f[cfgGn] option is not supported under /proc-based Linux lsof, because it doesn't read kernel structures from kernel memory.<br>
+<br>
+<b>Environment</b> <b>variables.</b></p>
+<p>LANG
+defines a language locale. See setlocale(3) for the names of other variables that can be used in place of LANG - e.g., LC_ALL, LC_TYPE, etc. <br>
+LSOFDEVCACHE
+defines the path to a device cache file. See the DEVICE CACHE PATH FROM AN ENVIRONMENT VARIABLE section for more information. <br>
+LSOFPERSDCPATH
+defines the middle component of a modified personal device cache file path. See the MODIFIED PERSONAL DEVICE CACHE PATH section for more information.</p>
+<p><b>Related</b>:<br>
+ <br>
+<a href="ftp://lsof.itap.purdue.edu/pub/tools/unix/lsof/FAQ">lsof FAQ </a>(FTP)
+<br>
+
+<a href="awk.html">awk</a> - Find and Replace text<br>
+<a href="fuser.html">fuser</a> - Identify/kill the process that is accessing a file<br>
+
+ <a href="kill.html">kill</a> - Stop a process from running<br>
+<a href="mount.html">mount</a> - Mount a file system<br>
+<a href="ps.html">ps</a> - Process status<br>
+<a href="uname.html">uname</a> - Print system information<br>
+access(2), crash(1), fattach(3C), ff(1), fstat(8),
+gethostname(2), isprint(3), lstat(2), netstat(1), readlink(2)<br>
+Equivalent Windows command: <a href="../term_tools/nt/psfile.html"> psFILE</a></p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/man.html b/help/en/bash/man.html
new file mode 100644
index 0000000..b91d955
--- /dev/null
+++ b/help/en/bash/man.html
@@ -0,0 +1,83 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>man MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> man / info / help </h1>
+<p>Display helpful information about commands.</p>
+<pre>Syntax
+ man [-k] [<var>command</var>]
+
+ man intro
+
+ man bash
+
+ info [<var>command</var>]
+
+ help [-s] [<var>command</var>]
+
+Options
+
+ -s Short usage synopsis, restricts the information displayed.
+
+ -k Search by command description rather than command name.
+
+ intro An overview of basic commands
+
+Press &lt;Space bar&gt; to view the next page
+Press &lt;return&gt; to view next line
+Press &lt;ctrl-C&gt; to exit</pre>
+<p>For simplicity, this website includes both <b>internal</b> GNU bash commands and <b>external</b> unix commands in a single list. Many more commands are available and the <span class="telety">man</span> command will list the full details of these. </p>
+<p><b>Internal</b> means a command built into the shell, it's the shell that performs the action. <br>
+ <b>External</b> means the shell will fork and execute an external program as a new subprocess. External commands are available when running any shell.</p>
+<p>For example, the <span class="telety">cd</span> command is built-in. The <span class="telety">ls</span> command, is external. </p>
+<p>The <span class="telety">man</span> command lists all the internal commands for bash under <span class="telety">man bash</span></p>
+<p><i> &quot;Education is not the filling of a pail, but the lighting of a fire&quot;
+ - W. B. Yeats
+ </i><br>
+ <br>
+ <b> Related</b>:<br>
+ <a href="env.html"><br>
+ </a><a href="more.html">more</a>
+ - Display output one screen at a time<br>
+ <a href="less.html">less</a> - Display output one screen at a time<br>
+ <b> </b>Equivalent Windows command:
+<a href="../term_tools/nt/help.html">HELP</a> <i>command</i></p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/mkdir.html b/help/en/bash/mkdir.html
new file mode 100644
index 0000000..a3b2eb4
--- /dev/null
+++ b/help/en/bash/mkdir.html
@@ -0,0 +1,68 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>mkdir MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> mkdir</h1>
+<p>Create new folder(s), if they do not already exist.</p>
+<pre>SYNTAX
+ mkdir [<em>Options</em>] <em>folder</em>...
+
+ mkdir "<em>Name with spaces</em>"
+
+OPTIONS
+ -m, --mode=<em>MODE</em> set permission mode (as in <a href="chmod.html">chmod</a>), not rwxrwxrwx - umask
+ -p, --parents no error if existing, make parent directories as needed
+ --verbose print a message for each created directory
+</pre>
+<p><br>
+ mkdir creates the standard entries . (dot) for the current folder <br>
+ and .. (dot dot) for its parent<br>
+ <br>
+ Any folder name that includes spaces may appear in some applications<br>
+ as "Name%20with%20spaces"</p>
+<p><b>Related</b>:<br>
+ <br>
+ <a href="cd.html">cd</a> - Change Directory<br>
+ <a href="rm.html">rm</a> - Remove files<br>
+ <a href="rmdir.html">rmdir</a> - Remove folder(s)<br>
+Equivalent Windows commands:
+<a href="../term_tools/nt/md.html">MD</a> - Create new folders </p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/mkfifo.html b/help/en/bash/mkfifo.html
new file mode 100644
index 0000000..4ef71a6
--- /dev/null
+++ b/help/en/bash/mkfifo.html
@@ -0,0 +1,66 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>mkfifo MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> mkfifo</h1>
+<p>Make FIFOs (named pipes) with the specified names.</p>
+<pre>Syntax
+ mkfifo [<em>options</em>] NAME...
+
+Options
+
+ -m <em>MODE</em>
+ --mode=<em>MODE</em>
+ Set the mode of created FIFOs to <em>MODE</em>, which is symbolic as in
+ `chmod' and uses 0666 (read and write allowed for everyone) minus
+ the bits set in the umask for the point of departure.</pre>
+<p>A "FIFO" is a special file type that permits independent processes
+ to communicate. One process opens the FIFO file for writing, and another for
+ reading, after which data can flow as with the usual anonymous pipe in shells
+ or elsewhere.</p>
+<p><i>"Ceci n'est pas une pipe" (This is not a pipe) - Magritte
+ </i></p>
+<p><b>Related</b>:<br>
+ <br>
+ <a href="mknod.html">mknod</a> - Make block or character special files <br>
+ <a href="sed.html">sed</a> - Stream Editor<br>
+<a href="umask.html">umask</a> - Users file creation mask</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/mknod.html b/help/en/bash/mknod.html
new file mode 100644
index 0000000..1d963c8
--- /dev/null
+++ b/help/en/bash/mknod.html
@@ -0,0 +1,76 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>mknod MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> mknod</h1>
+<p> creates a FIFO, character special file, or block special file
+with the specified name.</p>
+<pre>Syntax
+ mknod [<em>options</em>]... <em>NAME </em><em>Type</em> [<em>Major Minor</em>]
+
+Options
+
+ -m <em>MODE</em>
+ --mode=<em>MODE</em>
+ Set the mode of created files to <em>MODE</em>, which is symbolic as in
+ `chmod' and uses 0666 minus the bits set in the umask as the point
+ of departure.
+<em>
+Type</em> The type of file to make:
+ `p' for a FIFO
+ `b' for a block special file
+ `c' for a character special file
+<em>
+Major/Minor</em> When making a block or character special file, the major and minor
+ device numbers must be given after the file type.</pre>
+<p>Unlike the phrase "special file type" above, the term "special
+ file" has a technical meaning on Unix: something that can generate or receive
+ data. Usually this corresponds to a physical piece of hardware, e.g., a printer
+ or a disk. (These files are typically created at system-configuration time.)
+ The `mknod' command is what creates files of this type. Such devices can be
+ read either a character at a time or a "block" (many characters) at a time,
+ hence we say there are "block special" files and "character special" files.
+</p>
+<p><b>Related</b>:<br>
+ <br>
+ <a href="mkfifo.html">mkfifo</a> - Make FIFOs (named pipes)<br>
+<a href="sed.html">sed</a> - Stream Editor</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/mmv.html b/help/en/bash/mmv.html
new file mode 100644
index 0000000..8299791
--- /dev/null
+++ b/help/en/bash/mmv.html
@@ -0,0 +1,316 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>mmv MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1>mmv</h1>
+<p>Mass Move and rename - Move, copy, append or link Multiple <b>files</b> using wildcard patterns.</p>
+<pre>Syntax
+ mmv [<i>Source_Option</i>] [-h] [-d|p] [-g|t] [-v|n] [--] [<i>from</i> <i>to</i>]
+
+Options:
+ -h help
+
+ -d Delete
+ -p Protect (don't delete or overwrite)
+ -g Go
+ -t Terminate
+ -v verbose mode
+ -n no-execute mode (display messages about what would have been done)
+
+Source_Options:
+
+ -m <b>Move</b> source file to target name.
+ Both must be on the same device. Will not move directories.
+ If the source file is a symbolic link, moves the link without checking
+ if the link's target from the new directory is different than the old.
+
+ -x same as -m, except cross-device moves are done by copying, then deleting source.
+ When copying, sets the permission bits and file modification time of the target
+ file to that of the source file.
+
+ -r <b>Rename</b> source file or directory to target name.
+ The target name must not include a path: the file remains in the same directory
+ in all cases. This option is the only way of renaming directories under mmv.
+
+ -c <b>Copy</b> source file to target name.
+ Sets the file modification time and permission bits of the target file to that
+ of the source file, regardless of whether the target file already exists.
+ Chains and cycles (to be explained below) are not allowed.
+
+ -o <b>Overwrite</b> target name with source file.
+ If target file exists, it is overwritten, keeping its original owner and
+ permission bits. If it does not exist, it is created, with read-write permission
+ bits set according to <a href="umask.html">umask</a>, and the execute permission bits copied from the
+ source file. In either case, the file modification time is set to the current time.
+
+ -a <b>Append</b> contents of source file to target name.
+ Target file modification time is set to the current time. If target file does not
+ exist, it is created with permission bits set as under -o.
+ Unlike all other options, -a allows multiple source files to have the same target name,
+ e.g. "mmv -a \*.c big" will append all ".c" files to "big".
+ Chains and cycles are also allowed, so "mmv -a f f" will double up "f".
+
+ -l <b>Link</b> target name to source file.
+ Both must be on the same device, and the source must not be a directory.
+ Chains and cycles are not allowed.
+
+ -s Same as -l, but use symbolic links instead of hard links.
+ For the resulting link to aim back at the source, either the source name
+ must begin with a '/', or the target must reside in either the current or the
+ source directory. If none of these conditions are met, the link is refused.
+ However, source and target can reside on different devices, and the source can be a directory.
+
+ If no <i>source_option</i> is specified, the task is given by the command name under which mmv was invoked (argv[0]):
+
+ command_name default task
+
+ mmv -x (Move except cross device)
+ mcp -c (Copy)
+ mad -a (Append)
+ mln -l (Link)
+
+Options need not be given separately, i.e. &quot;mmv -mk&quot; is allowed.</pre>
+<p>Mmv moves (or copies, appends, or links, as specified) each source file
+matching a <b>from</b> pattern to the target name specified by the <b>to</b> pattern.</p>
+<p>This multiple action is performed safely, i.e. without any unexpected
+deletion of files due to collisions of target names with existing filenames or with other target names. Furthermore, before doing anything,
+mmv attempts to detect any errors that would result from the entire set
+of actions specified and gives the user the choice of either proceeding
+by avoiding the offending parts or aborting. </p>
+<p>mmv does support large
+files (LFS) but it does *NOT* support sparse files (i.e. it explodes
+them).</p>
+<p><b>Multiple Pattern Pairs</b><br>
+<br>
+Multiple<span class="code"> from -- to</span> pattern pairs may be specified by omitting the pattern pair on the command line, and entering them on the standard input,
+one pair per line. (If a pattern pair is given on the command line,
+the standard input is not read.) Thus,<br>
+<br>
+<span class="code">mmv<br>
+a b<br>
+c d</span><br>
+<br>
+would rename &quot;a&quot; to &quot;b&quot; and &quot;c&quot; to &quot;d&quot;. </p>
+<p>If a file can be matched to
+several of the given from patterns, the to pattern of the first matching pair is used. Thus,<br>
+<br>
+<span class="code">mmv<br>
+a b<br>
+a c</span><br>
+<br>
+would give the error message &quot;a -&gt; c : no match&quot; because file &quot;a&quot; (even
+if it exists) was already matched by the first pattern pair.<br>
+<br>
+<b>The From Pattern</b><br>
+<br>
+The <span class="code">from</span> pattern is a filename with embedded wildcards: &rsquo;<span class="code">*</span>&rsquo;, &rsquo;<span class="code">?</span>&rsquo;,
+&rsquo;<span class="code">[</span>&rsquo;...&rsquo;<span class="code">]</span>&rsquo;, and &rsquo;<span class="code">;</span>&rsquo;. The first three have their usual sh(1) meanings
+of, respectively, matching any string of characters, matching any single character, and matching any one of a set of characters.<br>
+<br>
+Between the &rsquo;[&rsquo; and &rsquo;]&rsquo;, a range from character &rsquo;a&rsquo; through character &rsquo;z&rsquo; is specified with &quot;a-z&quot;. The set of matching characters can be
+negated by inserting a &rsquo;<span class="code">^</span>&rsquo; after the &rsquo;[&rsquo;. Thus, <span class="code">&quot;[^b-e2-5_]&quot;</span> will
+match any character but &rsquo;b&rsquo; through &rsquo;e&rsquo;, &rsquo;2&rsquo; through &rsquo;5&rsquo;, and &rsquo;_&rsquo;.<br>
+<br>
+Note that paths are allowed in the patterns, and wildcards may be
+intermingled with slashes arbitrarily. The &rsquo;;&rsquo; wildcard is useful for
+matching files at any depth in the directory tree. It matches the same
+as &quot;*/&quot; repeated any number of times, including zero, and can only
+occur either at the beginning of the pattern or following a &rsquo;/&rsquo;. Thus<span class="code"> &quot;;*.c&quot;</span> will match all &quot;.c&quot; files in or below the current directory,
+while &quot;/;*.c&quot; will match them anywhere on the file system.<br>
+<br>
+In addition, if the from pattern (or the to pattern) begins with &quot;~/&quot;,
+the &rsquo;~&rsquo; is replaced with the home directory name. (Note that the &quot;~user&quot; feature of csh(1) is not implemented.) However, the &rsquo;~&rsquo; is not
+treated as a wildcard, in the sense that it is not assigned a wildcard
+index (see below).<br>
+<br>
+Since matching a directory under a task option other than -r or -s
+would result in an error, tasks other than -r and -s match directories
+only against completely explicit from patterns (i.e. not containing
+wildcards). Under -r and -s, this applies only to &quot;.&quot; and &quot;..&quot;.<br>
+<br>
+Files beginning with &rsquo;.&rsquo; are only matched against from patterns that
+begin with an explicit &rsquo;.&rsquo;. However, if -h is specified, they are
+matched normally.<br>
+<br>
+Warning: since the shell normally expands wildcards before passing the
+command-line arguments to mmv, it is usually necessary to enclose the
+command-line from and to patterns in quotes.<br>
+<b><br>
+The To Pattern</b><br>
+<br>
+The <span class="code">to</span> pattern is a filename with embedded wildcard indexes, where an
+index consists of the character &rsquo;<span class="code">#</span>&rsquo; followed by a string of digits.</p>
+<p>When a source file matches a <span class="code">from</span> pattern, a target name for the file
+is constructed out of the <span class="code">to</span> pattern by replacing the wildcard indexes
+by the actual characters that matched the referenced wildcards in the
+source name. Thus, if the from pattern is <span class="code">&quot;abc*.*&quot;</span> and the to pattern
+is <span class="code">&quot;xyz#2.#1&quot;</span>, then &quot;abc.txt&quot; is targeted to &quot;xyztxt.&quot;. (The first &rsquo;<span class="code">*</span>&rsquo;
+matched <span class="code">&quot;&quot;</span>, and the second matched &quot;txt&quot;.) Similarly, for the pattern
+pair <span class="code">&quot;;*.[clp]&quot; -&gt; &quot;#1#3/#2&quot;</span>, &quot;foo1/foo2/prog.c&quot; is targeted to &quot;foo1/foo2/c/prog&quot;. Note that there is no &rsquo;/&rsquo; following the &quot;#1&quot; in
+the to pattern, since the string matched by any &rsquo;;&rsquo; is always either
+empty or ends in a &rsquo;/&rsquo;. In this case, it matches &quot;foo1/foo2/&quot;.<br>
+<br>
+To convert the string matched by a wildcard to either lowercase or
+uppercase before embedding it in the target name, insert &rsquo;<span class="code">l</span>&rsquo; or &rsquo;<span class="code">u</span>&rsquo;,
+respectively, between the &rsquo;#&rsquo; and the string of digits.<br>
+<br>
+The <span class="code">to</span> pattern, like the <span class="code">from</span> pattern, can begin with a &quot;~/&quot; (see
+above). This does not necessitate enclosing the <span class="code">to</span> pattern in quotes
+on the command line since csh(1) expands the &rsquo;~&rsquo; in the exact same manner as mmv (or, in the case of sh(1), does not expand it at all).<br>
+<br>
+For all task options other than -r, if the target name is a directory,
+the real target name is formed by appending a &rsquo;/&rsquo; followed by the last
+component of the source file name. For example, <span class="code">&quot;mmv dir1/a dir2&quot;</span>
+will, if &quot;dir2&quot; is indeed a directory, actually move &quot;dir1/a&quot; to &quot;dir2/a&quot;. However, if &quot;dir2/a&quot; already exists and is itself a directory, this is considered an error.<br>
+<br>
+To strip any character (e.g. &rsquo;*&rsquo;, &rsquo;?&rsquo;, or &rsquo;#&rsquo;) of its special meaning
+to mmv, as when the actual replacement name must contain the character &rsquo;<span class="code">#</span>&rsquo;, precede the special character with a &acute;<span class="code">\</span>&rsquo; (and enclose the argument
+in quotes because of the shell). This also works to terminate a wildcard index when it has to be followed by a digit in the filename, e.g.
+<span class="code">&quot;a#1\1&quot;</span>.<br>
+<br>
+<b>Chains and Cycles</b><br>
+<br>
+A chain is a sequence of specified actions where the target name of one
+action refers to the source file of another action. For example,<br>
+<br>
+<span class="code">mmv<br>
+a b<br>
+b c</span><br>
+<br>
+specifies the chain &quot;a&quot; -&gt; &quot;b&quot; -&gt; &quot;c&quot;. A cycle is a chain where the
+last target name refers back to the first source file, e.g. &quot;mmv a a&quot;.</p>
+<p> Mmv detects chains and cycles regardless of the order in which their
+constituent actions are actually given. Where allowed, i.e. in moving,
+renaming, and appending files, chains and cycles are handled gracefully, by performing them in the proper order. Cycles are broken by
+first renaming one of the files to a temporary name (or just remembering its original size when doing appends).<br>
+<br>
+<b>Collisions and Deletions</b><br>
+<br>
+When any two or more matching files would have to be moved, copied, or
+linked to the same target filename, mmv detects the condition as an
+error before performing any actions. Furthermore, mmv checks if any of
+its actions will result in the destruction of existing files. </p>
+<p>If the
+<span class="code">-d (delete)</span> option is specified, all file deletions or overwrites are
+done silently. </p>
+<p>Under <span class="code">-p (protect)</span>, all deletions or overwrites (except
+those specified with &quot;(*)&quot; on the standard input, see below) are
+treated as errors. And if neither option is specified, the user is
+queried about each deletion or overwrite separately. (A new stream to &quot;/dev/tty&quot; is used for all interactive queries, not the standard
+input.)<br>
+<b><br>
+Error Handling</b><br>
+<br>
+Whenever any error in the user&rsquo;s action specifications is detected, an
+error message is given on the standard output, and mmv proceeds to
+check the rest of the specified actions. Once all errors are detected,
+mmv queries the user whether he wishes to continue by avoiding the
+erroneous actions or to abort altogether. This and all other queries
+may be avoided by specifying either the <span class="code">-g (go) or -t (terminate)</span><br>
+option. The former will resolve all difficulties by avoiding the erroneous actions; the latter will abort mmv if any errors are detected.<br>
+Specifying either of them defaults mmv to -p, unless -d is specified
+(see above). Thus, -g and -t are most useful when running mmv in the
+background or in a shell script, when interactive queries are undesirable.<br>
+<b><br>
+Reports</b><br>
+<br>
+Once the actions to be performed are determined, mmv performs them
+silently, unless either the -v (verbose) or -n (no-execute) option is
+specified. The former causes mmv to report each performed action on
+the standard output as<br>
+<br>
+<span class="code">a -&gt; b : done.</span><br>
+<br>
+Here, &quot;a&quot; and &quot;b&quot; would be replaced by the source and target names,
+respectively. If the action deletes the old target, a &quot;(*)&quot; is
+inserted after the the target name. Also, the &quot;-&gt;&quot; symbol is modified
+when a cycle has to be broken: the &rsquo;&gt;&rsquo; is changed to a &rsquo;^&rsquo; on the
+action prior to which the old target is renamed to a temporary, and the&rsquo;-&rsquo; is changed to a &rsquo;=&rsquo; on the action where the temporary is used.<br>
+<br>
+Under <span class="code">-n</span>, none of the actions are performed, but messages like the
+above are printed on the standard output with the &quot;: done.&quot; omitted.<br>
+<br>
+The output generated by <span class="code">-n</span> can (after editing, if desired) be fed back
+to mmv on the standard input (by omitting the <span class="code">from -- to </span>pair on the
+mmv command line). To facilitate this, mmv ignores lines on the standard input that look like its own error and &quot;done&quot; messages, as well as
+all lines beginning with white space, and will accept pattern pairs<br>
+with or without the intervening &quot;-&gt;&quot; (or &quot;-^&quot;, &quot;=&gt;&quot;, or &quot;=^&quot;). Lines
+with &quot;(*)&quot; after the target pattern have the effect of enabling <span class="code">-d</span> for
+the files matching this pattern only, so that such deletions are done
+silently. When feeding mmv its own output, one must remember to specify again the task option (if any) originally used to generate it.<br>
+<br>
+Although mmv attempts to predict all mishaps prior to performing any
+specified actions, accidents may happen. For example, mmv does not
+check for adequate free space when copying. Thus, despite all efforts,
+it is still possible for an action to fail after some others have
+already been done. To make recovery as easy as possible, mmv reports
+which actions have already been done and which are still to be performed after such a failure occurs. It then aborts, not attempting to
+do anything else. Once the user has cleared up the problem, he can
+feed this report back to mmv on the standard input to have it complete
+the task. (The user is queried for a file name to dump this report if
+the standard output has not been redirected.)</p>
+<p>Mmv exits with status 1 if it aborts before doing anything, with status
+2 if it aborts due to failure after completing some of the actions, and
+with status 0 otherwise.<br>
+Example</p>
+<p><b>BUGS</b></p>
+<p> If the search pattern is not quoted, the shell expands the wildcards.
+Mmv then (usually) gives some error message, but can not determine that
+the lack of quotes is the cause.<br>
+<br>
+To avoid difficulties in semantics and error checking, mmv refuses to
+move or create directories.</p>
+<p>If the mmv tool is not installed on your distro, get it with: <span class="code">apt-get install mmv</span></p>
+<p><b><a name="examples"></a>Examples</b></p>
+<p>Rename the file extension of all .csv files in the current directory to .xls</p>
+<p class="code">mmv &quot;<b>*</b>.csv&quot; &quot;<b>#1</b>.xls&quot;</p>
+<p>Copy <span class="code">report6part4.txt</span> to <span class="code">./french/rapport6partie4.txt</span> along with all similarly named files: </p>
+<p class="code">mmv -c &quot;report<b>*</b>part<b>*</b>.txt&quot; &quot;./french/rapport<b>#1</b>partie<b>#2</b>.txt&quot;</p>
+<p>Append the contents of all .txt files into one file:</p>
+<p class="code">mmv -a &quot;*.txt&quot; &quot;all.txt&quot; </p>
+<p><i>&ldquo;All things change, nothing is extinguished. There is nothing in the whole world which is permanent. Everything flows onward; all things are brought into being with a changing nature; the ages themselves glide by in constant movement&rdquo; - Ovid</i></p>
+<p><b>Related bash commands</b>:<br>
+<br>
+<a href="mv.html">mv</a> - Move or rename files or directories<br>
+<a href="cp.html">cp</a> - Copy one or more files to another location<br>
+<a href="ln.html">ln</a> - Make links between files<br>
+<a href="umask.html">umask</a> - Users file creation mask</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/more.html b/help/en/bash/more.html
new file mode 100644
index 0000000..10beed2
--- /dev/null
+++ b/help/en/bash/more.html
@@ -0,0 +1,149 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>more MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> more</h1>
+<p>Display output one screen at a time, <a href="less.html">less</a>
+provides <i>more</i> emulation and extensive enhancements.</p>
+<pre>SYNTAX
+ more [-dlfpcsu] [-<em>num</em>] [+/ <em>pattern</em>] [+ <em>linenum</em>] [<em>file</em> ...]
+
+OPTIONS
+ Command line options are described below. Options are also taken from
+ the environment variable MORE (make sure to precede them with a dash
+ (``-'')) but command line options will override them.
+
+ -<em>num</em> This option specifies an integer which is the screen size (in
+ lines).
+
+ -d more will prompt the user with the message "[Press space to continue,
+ 'q' to quit.]" and will display "[Press 'h' for instructions.]"
+ instead of ringing the bell when an illegal key is pressed.
+
+ -l more usually treats ^L (form feed) as a special character, and will
+ pause after any line that contains a form feed. The -l option will
+ prevent this behavior.
+
+ -f Causes more to count logical, rather than screen lines (i.e., long
+ lines are not folded).
+
+ -p Do not scroll. Instead, clear the whole screen and then display
+ the text.
+ -c Do not scroll. Instead, paint each screen from the top, clearing
+ the remainder of each line as it is displayed.
+
+ -s Squeeze multiple blank lines into one.
+
+ -u Suppress underlining.
+
+ +/ The +/ option specifies a string that will be searched for before
+ each file is displayed.
+
+ +<em>num</em> Start at line number num.
+
+COMMANDS
+ Interactive commands for more are based on vi(1). Some commands may be
+ preceeded by a decimal number, called k in the descriptions below. In
+ the following descriptions, ^X means control-X.
+
+ h or ? Help: display a summary of these commands. If you forget all
+ the other commands, remember this one.
+
+ SPACE Display next k lines of text. Defaults to current screen
+ size.
+
+ z Display next k lines of text. Defaults to current screen
+ size. Argument becomes new default.
+
+ RETURN Display next k lines of text. Defaults to 1.
+ Argument becomes new default.
+
+ d or ^D Scroll k lines. Default is current scroll size, initially
+ 11. Argument becomes new default.
+
+ q or Q or INTERRUPT Exits the more command.
+
+ s Skip forward k lines of text. Defaults to 1.
+
+ f Skip forward k screenfuls of text. Defaults to 1.
+
+ b or ^B Skip backwards k screenfuls of text. Defaults to 1.
+
+ ' Go to place where previous search started.
+
+ = Display current line number.
+
+ /<em>pattern</em> Search for kth occurrence of regular expression. Defaults to 1.
+
+ n Search for kth occurrence of last r.e. Defaults to 1.
+
+ !<cmd> or :!<cmd> Execute <cmd> in a subshell
+
+ v Start up /usr/bin/vi at current line
+
+ ^L Redraw screen
+
+ :n Go to kth next file. Defaults to 1.
+
+ :p Go to kth previous file. Defaults to 1.
+
+ :f Display current file name and line number
+
+ . Repeat previous command
+
+ENVIRONMENT
+ More utilizes the following environment variables, if they exist:
+
+ MORE This variable may be set with favored options to more.
+ SHELL Current shell in use (normally set by the shell at login</pre>
+<p><i>&quot;There are few more impressive sights than a Scotsman
+ on the make&quot; - Sir
+ James Barrie </i><br>
+ <br>
+ <b> Related bash commands</b>:<br>
+ <a href="echo.html"><br>
+ echo</a> - Display message on screen<br>
+ <a href="less.html">less</a> - Display output one screen at a time<br>
+<a href="tee.html">tee</a> - Redirect output to multiple files <br>
+<a href="http://www.jedsoft.org/most/">most</a> - A paging program for Unix, VMS, MSDOS, and win32 systems (allows scrolling left and right).<br>
+Equivalent Windows command:
+<a href="../term_tools/nt/more.html">MORE</a> - Display output one screen at a time</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/mount.html b/help/en/bash/mount.html
new file mode 100644
index 0000000..4e5a6f6
--- /dev/null
+++ b/help/en/bash/mount.html
@@ -0,0 +1,180 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>mount MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> mount</h1>
+<p>mount a file system<span class="body"><br>
+ All files accessible in a Unix system are arranged in one big tree, the file
+ hierarchy, rooted at /. These files can be spread out over several devices.
+ The mount command serves to attach the file system found on some device to the
+ big file tree.</span></p>
+<pre>SYNTAX
+ mount -a [-fFnrsvw] [-t vfstype]
+
+ mount [-fnrsvw] [-o <i>options</i> [,...]] device | dir
+
+ mount [-fnrsvw] [-t vfstype] [-o <i>options</i>] device dir
+
+ mount [-hV]<span class="body"> </span> </pre>
+<pre>OPTIONS
+
+ -a Mount all filesystems (of the given types) mentioned
+ in fstab.
+
+ -F (Used in conjunction with -a.) Fork off a new
+ incarnation of mount for each device. This will do
+ the mounts on different devices or different NFS
+ servers in parallel. This has the advantage that
+ it is faster; also NFS timeouts go in parallel. A
+ disadvantage is that the mounts are done in unde-
+ fined order. Thus, you cannot use this option if
+ you want to mount both /usr and /usr/spool.
+
+ -f Causes everything to be done except for the actual
+ system call; if it's not obvious, this ``fakes''
+ mounting the file system. This option is useful in
+ conjunction with the -v flag to determine what the
+ mount command is trying to do. It can also be used
+ to add entries for devices that were mounted ear-
+ lier with the -n option.
+
+ -n Mount without writing in /etc/mtab. This is necessary for example
+ when /etc is on a read-only file system.
+
+ -s Tolerate sloppy mount options rather than failing.
+ This option exists for support of the Linux
+ autofs-based automounter.
+
+ -r Mount the file system read-only. A synonym is -o ro
+
+ -w Mount the file system read/write. This is the
+ default. A synonym is -o rw.
+
+ -L <i>label</i>
+ Mount the partition that has the specified label.
+
+ -U <i>uuid</i>
+ Mount the partition that has the specified uuid.
+
+ -o Several -o options can be specified in a comma separated
+ string ... see info for more
+
+ async All I/O to the file system should be done
+ asynchronously.
+
+ atime Update inode access time for each access.
+ This is the default.
+
+ noatime
+ Do not update inode access times on this
+ file system (e.g, for faster access on the
+ news spool to speed up news servers).
+
+ auto Can be mounted with the -a option.
+
+ noauto Can only be mounted explicitly (i.e., the -a
+ option will not cause the file system to be
+ mounted).
+
+ ro Mount the file system read-only.
+
+ rw Mount the file system read-write.
+
+ suid Allow set-user-identifier or set-group-identifier bits to take effect.
+
+ sync All I/O to the file system should be done synchronously.
+
+ -t <i>vfstype</i>
+ The argument following the -t is used to indicate
+ the file system type.
+
+ -h Print a help message.
+
+ -V Output version.
+
+ -v Verbose mode.
+
+File system specific MOUNT options
+ see <b>info mount</b> for these</pre>
+<p><span class="body">The standard form of the mount command, is
+ mount -t type device dir This tells the kernel to attach the file system found
+ on device (which is of type type) at the directory dir. The previous contents
+ (if any) and owner and mode of dir become invisible, and as long as this file
+ system remains mounted, the pathname dir refers to the root of the file system
+ on device.<br>
+ <br>
+ Three forms of invocation do not actually mount anything:<br>
+ <br>
+ print a help message:<br>
+ mount -h<br>
+ <br>
+ print a version string:<br>
+ mount -V<br>
+ <br>
+ list all mounted file systems of type 'type'<br>
+ mount [-t type]<br>
+ <br>
+ The proc file system is not associated with a special device, and when mounting
+ it, an arbitrary keyword, such as proc can be used instead of a device specification.
+ (The customary choice none is less fortunate: the error message `none busy'
+ from umount can be confusing.)<br>
+ <br>
+ Most devices are indicated by a file name (of a block special device), like
+ /dev/sda1, but there are other possibilities. For example, in the case of an
+ NFS mount, device may look like knuth.cwi.nl:/dir. It is possible to indicate
+ a block special device using its volume label or UUID (see the -L and -U options
+ below).<br>
+ <br>
+ The file /etc/fstab (see fstab), may contain lines describing what devices are
+ usually mounted where, using which options.</span></p>
+<p><i>"The Ten Commandments and the Sermon on the Mount contain my
+ religion&quot; - John
+ Adams</i><br>
+ <br>
+ <b> Related</b>:<br>
+ <br>
+ <a href="df.html">df</a> - Report filesystem disk space usage<br>
+ <a href="fdformat.html">fdformat</a> - Low-level format a floppy disk<br>
+ <a href="fdisk.html">fdisk</a> - Partition table manipulator for Linux<br>
+ <a href="ram.html">ram</a> - ram disk device <br>
+ <span class="body">umount(8) - detach/u</span>nmount a device<br>
+Equivalent Windows commands: Disk Administrator GUI</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/mtools.html b/help/en/bash/mtools.html
new file mode 100644
index 0000000..ee1d810
--- /dev/null
+++ b/help/en/bash/mtools.html
@@ -0,0 +1,91 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>mtools MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> mtools</h1>
+<p>Mtools is a public domain collection of tools to allow Unix systems
+ to manipulate MS-DOS files: read, write, and move around files on an MS-DOS
+ filesystem <br>
+ <br>
+ Mtools are typically used to manipulate FAT formatted floppy disks. Each program
+ attempts to emulate the MS-DOS equivalent command, these are different from
+ Windows NT/2000 commands.<br>
+ <br>
+ Mtools is sufficient to give access to MS-DOS filesystems. For instance, commands
+ such as `mdir a:' work on the `a:' floppy without any preliminary mounting or
+ initialization (assuming the default `/etc/mtools.conf' works on your machine).
+With mtools, one can change floppies too without unmounting and mounting.</p>
+<pre>MTOOLS Programs
+
+floppyd floppy daemon to run on your X server box
+floppyd_installtest small utility to check for the presence of floppyd
+mattrib change MS-DOS file attribute flags
+<a href="../term_tools/bash/mbadblocks.html">mbadblocks</a> tests a floppy disk, and marks the bad blocks in the FAT
+mcat same as cat. Only useful with floppyd.
+mcd change MS-DOS directory
+mcopy copy MS-DOS files to/from Unix
+mdel delete an MS-DOS file
+mdeltree recursively delete an MS-DOS directory
+mdir display an MS-DOS directory
+mdu list space occupied by directory and its contents
+mformat add an MS-DOS filesystem to a low-level formatted floppy disk
+minfo get information about an MS-DOS filesystem.
+mlabel make an MS-DOS volume label
+mkmanifest makes a list of short name equivalents
+mmd make an MS-DOS subdirectory
+mmount mount an MS-DOS disk
+mpartition create an MS-DOS as a partition
+mrd remove an MS-DOS subdirectory
+mmove move or rename an MS-DOS file or subdirectory
+mren rename an existing MS-DOS file
+mshowfat shows the FAT map of a file
+mtoolstest tests and displays the configuration
+mtype display contents of an MS-DOS file
+mzip zip disk specific commands
+xcopy recursively copy a dos directory into another</pre>
+<p> Equivalent Windows commands:<br>
+ <br>
+ In the same way that `mtools' are DOS/Windows commands ported to run under UNIX,
+ most UNIX commands have been ported to run under NT.<br>
+ A very limited selection of POSIX tools are included in the NT resource kits,
+ more can be found on the net.<br>
+Be aware that most UNIX commands running on Windows are case sensitive. </p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/mtr.html b/help/en/bash/mtr.html
new file mode 100644
index 0000000..bd5eb22
--- /dev/null
+++ b/help/en/bash/mtr.html
@@ -0,0 +1,129 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>mtr MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem -->
+<h1> mtr </h1>
+<p>Network diagnostics (traceroute/ping.)</p>
+<pre>Syntax
+ mtr [-hvrctglspni46] [--help] [--version] [--report] [--report-cycles <i>COUNT</i>]
+ [--curses] [--split] [--raw] [--no-dns] [--gtk] [--address <i>IP.ADD.RE.SS</i>]
+ [--interval <i>SECONDS</i>] [--psize <i>BYTES</i> | -s <i>BYTES</i>] <i>HOSTNAME</i> [<i>PACKETSIZE</i>]
+
+Key
+ -c <i>COUNT</i>
+ --report-cycles <i>COUNT</i>
+ Use this option to set the number of pings sent to determine both the machines on the network and
+ the reliability of those machines. Each cycle lasts one second.
+
+ -s <i>BYTES</i>
+ --psize <i>BYTES</i>
+ <i>PACKETSIZE</i>
+ These options or a trailing PACKETSIZE on the commandline set the packet size (in Bytes inclusive IP and ICMP headers) used for probing.
+ If set to a negative number, every iteration will use a different, random packetsize up to that number.
+
+ -g
+ --gtk
+ Force mtr to use the GTK+ based X11 window interface (if available). GTK+ must have
+ been available on the system when mtr was built for this to work. See <a href="http://www.gtk.org/">GTK+</a>
+
+ -p
+ --split
+ Set mtr to spit out a format that is suitable for a split-user interface.
+
+ -h
+ --help
+ Print a summary of command line argument options.
+
+ -l
+ --raw
+ Tell mtr to use the raw output format. This format is better suited for archival of the
+ measurement results. It could be parsed to be presented into any of the other display methods.
+
+ -a <i>IP.ADD.RE.SS</i>
+ --address<i> IP.ADD.RE.SS</i>
+ Bind outgoing packets' socket to a specific interface, so that any packet will be sent
+ through this interface. NOTE that this option doesn't apply to DNS requests (which
+ could be and could not be what you want).
+
+ -i <i>SECONDS</i>
+ --interval <i>SECONDS</i>
+ Use this option to specify the positive number of seconds between ICMP ECHO requests. The default value for this parameter is one second.
+
+ -t
+ --curses
+ Force mtr to use the curses based terminal interface (if available).
+
+ -n
+ --no-dns
+ Force mtr to display numeric IP numbers and not try to resolve the host names.
+
+ -r
+ --report
+ Put mtr into report mode. When in this mode, mtr will run for the number of cycles specified by
+ the -c option, and then print statistics and exit.
+ This mode is useful for generating statistics about network quality.
+ Note that each running instance of mtr generates a significant amount of network traffic.
+ Using mtr to measure the quality of your network may result in decreased network performance.
+
+ -v
+ --version
+ Print the installed version of mtr.
+
+ -4 Use IPv4 only.
+
+ -6 Use IPv6 only.</pre>
+<p>mtr combines the functionality of the traceroute and ping programs in a single network diagnostic tool.</p>
+<p>As mtr starts, it investigates the network connection between the host mtr runs on and HOSTNAME. by sending packets with purposly low TTLs. It continues to send packets with low TTL, noting the response time of the intervening routers. This allows mtr to print the response percentage and response times of the internet route to HOSTNAME. A sudden increase in packetloss or response time is often an indication of a bad (or simply overloaded) link. </p>
+<p>Some modern routers give a lower priority to ICMP ECHO packets than to other network traffic. Consequently, the reliability of these routers reported by mtr will be significantly lower than the actual reliability of these routers.</p>
+<p><b>Examples</b></p>
+<p class="code">$ mtr 192.168.12.34<br>
+$ mtr google.com</p>
+<p><br>
+MTR (Matt's traceroute) was written by Matt Kimball, with contributions by many people.</p>
+<p><i>“I don’t measure a man’s success by how high he climbs but how high he bounces when he hits bottom” - General George S. Patton </i></p>
+<p><b>Related</b>:</p>
+<p><a href="http://www.bitwizard.nl/mtr/">The mtr web page</a> - download the latest version<br>
+<a href="ping.html">ping</a> - Test a network connection<br>
+ <a href="traceroute.html">traceroute</a> - Trace Route to Host<br>
+ Equivalent Windows command: <a href="../term_tools/nt/set.html"></a><a href="../term_tools/nt/pathping.html">PATHPING</a> - Display, set, or remove Windows environment
+variables.</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/mv.html b/help/en/bash/mv.html
new file mode 100644
index 0000000..fdb1945
--- /dev/null
+++ b/help/en/bash/mv.html
@@ -0,0 +1,118 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>mv MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> mv</h1>
+<p>Move or rename files or directories.</p>
+<pre>SYNTAX
+ mv [<em>options</em>]... <em>Source</em> <em>Dest</em>
+
+ mv [<em>options</em>]... <em>Source</em>... <em>Directory</em></pre>
+<p><span class="body">
+ If the last argument names an existing directory, `mv' moves each other given
+ file into a file with the same name in that directory. Otherwise, if only two
+ files are given, it renames the first as the second. It is an error if the last
+argument is not a directory and more than two files are given.</span></p>
+<pre>OPTIONS
+
+-b
+--backup
+ Make a backup of each file that would otherwise be overwritten or
+ removed.
+
+-f
+--force
+ Remove existing destination files and never prompt the user.
+
+-i
+--interactive
+ Prompt whether to overwrite each existing destination file,
+ regardless of its permissions. If the response does not begin
+ with `y' or `Y', the file is skipped.
+
+-S <em>SUFFIX</em>
+--suffix=<em>SUFFIX</em>
+ Append <em>SUFFIX</em> to each backup file made with `-b'.
+ The backup suffix is ~, unless set with SIMPLE_BACKUP_SUFFIX.
+
+-u
+--update
+ Do not move a nondirectory that has an existing destination with
+ the same or newer modification time.
+
+-v
+--verbose
+ Print the name of each file before moving it.
+
+-V <em>METHOD</em>
+--version-control=<em>METHOD</em>'
+ Change the type of backups made with `-b'. METHOD can be:
+
+ t, numbered make numbered backups
+ nil, existing numbered if numbered backups exist, simple otherwise
+ never, simple always make simple backups
+
+ --help display help and exit
+ --version output version information and exit
+
+<strong>Examples</strong>
+
+Rename the file apple as orange.doc:
+mv apple orange.doc
+
+Move orange.doc to the Documents folder:
+mv orange.doc ~/Documents/orange.doc
+
+Rename a bunch of file extensions
+e.g. change *.txt into *.htm
+ for f in *.txt; do mv ./&quot;$f&quot; &quot;${f%txt}htm&quot;; done</pre>
+<p>`mv' can move only regular files across filesystems.<br>
+<br>
+If a destination file exists but is normally unwritable, standard input is a terminal, and the `-f' or `--force' option is not given, `mv' prompts the user for whether to replace the file. (You might own the file, or have write permission on its directory.) If the response does not begin with `y' or `Y', the file is skipped.</p>
+<p><i>&ldquo;Any intelligent fool can make things bigger and more complex... It takes a touch of genius - and a lot of courage to move in the opposite direction&rdquo; -
+Albert Einstein </i></p>
+<p><b>Related</b>:<br>
+ <br>
+ <a href="cp.html">cp</a> - Copy one or more files to another location<br>
+<a href="mmv.html">mmv</a> - Mass Move and rename<br>
+Equivalent Windows command:
+ <a href="../term_tools/nt/move.html">MOVE</a> - Move files from one folder to another</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/nice.html b/help/en/bash/nice.html
new file mode 100644
index 0000000..5686369
--- /dev/null
+++ b/help/en/bash/nice.html
@@ -0,0 +1,81 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>nice MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> nice</h1>
+<p>Run a command with modified scheduling priority, print or modify
+the scheduling priority of a job.</p>
+<pre>SYNTAX
+ nice [<i>Option</i>]... [<i>Command</i> [<i>Arg</i>]...]
+
+OPTION
+ -n <i>MyADJUSTMENT</i>
+ -<i>MyADJUSTMENT</i>
+ --adjustment=<i>MyADJUSTMENT</i>
+
+ Priority can be adjusted by `nice' over the range
+ of -20 (the highest priority)
+ to 19 (the lowest)</pre>
+<p> If no arguments are given, `nice' prints the current scheduling
+ priority, which it inherited. </p>
+<p>Otherwise, `nice' runs the given <i>Command</i> with its scheduling
+ priority adjusted. <br>
+ <br>
+ If no option for <i>MyADJUSTMENT</i> is given, the priority of the command is
+ incremented by 10. You must have appropriate privileges to specify a negative
+ adjustment. <br>
+ <br>
+ Because most shells have a built-in command by the same name, using the unadorned
+ command name in a script or interactively may get you different functionality
+ than that described here.<br>
+ <br>
+ <i>&quot;Work is achieved by those employees who have not yet reached their
+ level of incompetence&quot; - Laurence J. Peter (The
+ Peter Principle)</i> </p>
+<p><b>Related</b>:<br>
+ <br>
+ <a href="nohup.html">nohup</a> - Run a command immune to hangups<br>
+ <a href="sync.html">sync</a> - Synchronize data on disk with memory<br>
+ <a href="sleep.html">sleep</a> - Delay for a specified time <br>
+Equivalent Windows commands:
+ <a href="../term_tools/nt/start.html">START</a> /HIGH - Start a program with `high' scheduling
+ priority</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/nl.html b/help/en/bash/nl.html
new file mode 100644
index 0000000..fd1d6d9
--- /dev/null
+++ b/help/en/bash/nl.html
@@ -0,0 +1,156 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>nl MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> nl</h1>
+<p>Number lines and write files, writes each FILE to standard output,
+ with line numbers added to some or all of the lines. <br>
+If no input file (or `-' ) is given nl will read from standard input.</p>
+<pre>SYNTAX
+ nl [<em>options</em>]... [<em>File</em>]...
+
+OPTIONS
+
+`-b <em>STYLE</em>'
+`--body-numbering=<em>STYLE</em>'
+ Select the numbering style for lines in the body section of each
+ logical page. When a line is not numbered, the current line number
+ is not incremented, but the line number separator character is
+ still prepended to the line.
+ The styles are:
+
+ `a' number all lines,
+
+ `t' number only nonempty lines (default for body),
+
+ `n' do not number lines (default for header and footer),
+
+ `pREGEXP' number only lines that contain a match for REGEXP.
+
+`-d <em>CD</em>'
+`--section-delimiter=<em>CD</em>'
+ Set the section delimiter characters to CD; default is `\:'. If
+ only C is given, the second remains `:'. (Remember to protect `\'
+ or other metacharacters from shell expansion with quotes or extra
+ backslashes.)
+
+`-f <em>STYLE</em>'
+`--footer-numbering=<em>STYLE</em>'
+ Analogous to `--body-numbering'.
+
+`-h <em>STYLE</em>'
+`--header-numbering=<em>STYLE</em>'
+ Analogous to `--body-numbering'.
+
+`-i <em>NUMBER</em>'
+`--page-increment=<em>NUMBER</em>'
+ Increment line numbers by <em>NUMBER</em> (default 1).
+
+`-l <em>NUMBER</em>'
+`--join-blank-lines=<em>NUMBER</em>'
+ Consider <em>NUMBER</em> (default 1) consecutive empty lines to be one
+ logical line for numbering, and only number the last one. Where
+ fewer than <em>NUMBER</em> consecutive empty lines occur, do not number
+ them. An empty line is one that contains no characters, not even
+ spaces or tabs.
+
+`-n <em>FORMAT</em>'
+`--number-format=<em>FORMAT</em>'
+ Select the line numbering format (default is `rn'):
+
+ `ln'
+ left justified, no leading zeros;
+
+ `rn'
+ right justified, no leading zeros;
+
+ `rz'
+ right justified, leading zeros.
+
+`-p'
+`--no-renumber'
+ Do not reset the line number at the start of a logical page.
+
+`-s <em>STRING</em>'
+`--number-separator=<em>STRING</em>'
+ Separate the line number from the text line in the output with
+ STRING (default is the TAB character).
+
+`-v <em>NUMBER</em>'
+`--starting-line-number=<em>NUMBER</em>'
+ Set the initial line number on each logical page to NUMBER
+ (default 1).
+
+`-w <em>NUMBER</em>'
+`--number-width=<em>NUMBER</em>'
+ Use NUMBER characters for line numbers (default 6).</pre>
+<p>`nl' decomposes its input into (logical) pages; by default, the
+ line number is reset to 1 at the top of each logical page.<br>
+ <br>
+ `nl' treats all of the input files as a single document; it does not reset line
+ numbers or logical pages between files. <br>
+ <br>
+ A logical page consists of three sections: header, body, and footer. Any of
+ the sections can be empty. Each can be numbered in a different style from the
+ others. <br>
+ <br>
+ The beginnings of the sections of logical pages are indicated in the input file
+ by a line containing exactly one of these delimiter strings:<br>
+ `\:\:\:' start of header;<br>
+ `\:\:' start of body;<br>
+ `\:' start of footer. <br>
+ The two characters from which these strings are made can be changed from `\'
+ and `:' via options (see above), but the pattern and length of each string cannot
+ be changed. A section delimiter is replaced by an empty line on output. <br>
+ <br>
+ Any text that comes before the first section delimiter string in the input file
+ is considered to be part of a body section, so `nl' treats a file that contains
+ no section delimiters as a single body section. </p>
+<p><b>Related</b>:<br>
+ <br>
+ <a href="comm.html">comm</a> - Compare two sorted files line by line<br>
+ <a href="csplit.html">csplit</a> - Split a file into context-determined pieces<br>
+ <a href="expand.html">expand</a> - Convert tabs to spaces<br>
+ <a href="seq.html">seq</a> - Print numeric sequences <br>
+Equivalent Windows commands:
+ <a href="../term_tools/nt/for.html">FOR</a> /F &quot;skip=nlines&quot; - Loop through items
+ in a text file</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/nohup.html b/help/en/bash/nohup.html
new file mode 100644
index 0000000..60a8d02
--- /dev/null
+++ b/help/en/bash/nohup.html
@@ -0,0 +1,76 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>nohup MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><mv><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> nohup</h1>
+<p>No Hang Up. Run a command immune to hangups, runs the given <i>command</i> with hangup
+ signals ignored, so that the command can continue running in the background
+after you log out.</p>
+<pre>SYNTAX
+ nohup <i>Command</i> [<i>Arg</i>]...</pre>
+<p>`nohup' increases the scheduling priority of COMMAND by 5, this
+ gives a slightly lower priority. <br>
+ <br>
+ If standard output is a terminal, it and standard error are redirected so that
+ they are appended to the file `nohup.out'; if that cannot be written to, they
+ are appended to the file `$HOME/nohup.out'. If that cannot be written to, the
+ command is not run.<br>
+ <br>
+ If `nohup' creates either `nohup.out' or `$HOME/nohup.out', it creates it with
+ no "group" or "other" access permissions. It does not change the permissions
+ if the output file already existed. <br>
+ <br>
+ `nohup' does not automatically put the command it runs in the background; you
+ must do that explicitly, by ending the command line with an `&'. </p>
+<p><i>"Love is a perky elf dancing a merry little jig and then suddenly
+ he turns on you with a miniature machine gun" - Matt
+ Groening</i></p>
+<p><b>Related</b>:<br>
+ <br>
+ <a href="builtin.html">builtin</a> - Run a shell builtin <br>
+ <a href="chroot.html">chroot</a> - Run a command with a different root directory<br>
+ <a href="exec.html">exec</a> - Execute a command<br>
+ <a href="if.html">if</a> - Conditionally perform a command<br>
+ <a href="nice.html">nice</a> - Change job scheduling priority <br>
+<a href="screen.html">screen</a> - Multiplex terminal, run remote shells via ssh<br>
+ <a href="source.html">.source</a> - Run commands from a file <br>
+ <a href="su.html">su</a> - Run a command with substitute user and group id</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/nslookup.html b/help/en/bash/nslookup.html
new file mode 100644
index 0000000..c7db81e
--- /dev/null
+++ b/help/en/bash/nslookup.html
@@ -0,0 +1,128 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>nslookup MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1>nslookup</h1>
+<p>Query Internet name servers </p>
+<pre>Syntax:
+ nslookup
+
+ nslookup <i>host-to-find</i>
+
+ nslookup <i>server</i>
+
+interactive mode:
+
+ nslookup -<i>server</i>
+
+ nslookup [-<i>options</i>] [<i>host-to-find</i> ]
+
+Options:
+
+ host [<i>server</i> ]
+ Look up information for host using the current default server or using server,
+ if specified. If <i>host </i>is an Internet address and the query type is A or PTR ,
+ the name of the host is returned. If host is a name and does not have a trailing
+ period, the default domain name is appended to the name. (This behavior depends
+ on the state of the set options domain , srchlist , defname , and search.
+
+ To look up a host not in the current domain, append a period to the name.
+
+ server <i>domain
+</i> lserver <i>domain</i>
+ Change the default server to <i>domain</i> ; lserver uses the initial server to look up
+ information about <i>domain</i> while server uses the current default server.
+ If an authoritative answer can't be found, the names of servers that might have
+ the answer are returned.
+ root
+ Change the default server to the server for the root of the domain name space.
+ Currently, the host ns.internic.net is used. (This command is a synonym for
+ `lserver ns.internic.net' The name of the root server can be changed with
+ the `set root ' command.
+
+ finger [name ] [> filename ]
+ finger [name ] [>> filename ]
+ Connects with the finger server on the current host. The current host is
+ defined when a previous lookup for a host was successful and returned address
+ information (see the `set querytype=A ' command). The name is optional. > and
+ >> can be used to redirect output in the usual manner.
+
+ ls [option ] domain [> filename ]
+ ls [option ] domain [>> filename ]
+ List the information available for domain , optionally creating or appending
+ to <i>filename</i> The default output contains host names and their Internet addresses.
+ <i>Option</i> can be one of the following:
+
+ -t <i>querytype</i> list all records of the specified type (see querytype below).
+ -a list aliases of hosts in the domain; synonym for `-t CNAME '
+ -d list all records for the domain; synonym for `-t ANY'
+ -h list CPU and operating system information for the domain; synonym for `-t HINFO'
+ -s list well-known services of hosts in the domain; synonym for `-t WKS'
+
+ When output is directed to a file, hash marks are printed for every 50 records
+ received from the server.
+
+ view <i>filename</i>
+ Sort and lists the output of previous ls command(s) with more(1).
+
+ set <i>keyword</i> [= <i>value</i> ]<br> This command is used to change state information that affects the lookups.
+ run <b>man nslookup</b> for a full list of valid keywords.
+
+ set all Print the current value of the frequently-used options
+ to set Information about the current default server and host is also printed.
+
+ help
+ ? Print a brief summary of commands.
+
+ exit Exit the program.
+</pre>
+<p>Nslookup has two modes: interactive and non-interactive.</p>
+<p> Interactive mode allows the user to query name servers for information about various hosts and domains or to print a list of hosts in a domain. </p>
+<p>Non-interactive mode is used to print just the name and requested information for a host or domain.</p>
+<p>The options listed under the `set ' command can be specified in the .nslookuprc file in the user's home directory (listed one per line). Options can also be specified on the command line if they precede the arguments and are prefixed with a hyphen. </p>
+<p> <i>&quot;He who listens to truth is not less
+than he who utters truth&quot; - Kahlil Gibran</i></p>
+<p><b>Related</b>:<br>
+ <a href="env.html"><br>
+ </a> named(8), resolver(3), resolver(5)<br>
+Equivalent Windows command:
+ <a href="../term_tools/nt/nslookup.html">NSLOOKUP</a> - Lookup IP addresses on a NameServer.</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/op.html b/help/en/bash/op.html
new file mode 100644
index 0000000..277dd15
--- /dev/null
+++ b/help/en/bash/op.html
@@ -0,0 +1,122 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>op MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1>op</h1>
+<p>Operator access. A flexible means for system administrators to grant trusted users access to certain root operations without having to give them full superuser privileges.</p>
+<pre>Syntax
+ op <i>mnemonic</i> [arg]
+
+Key
+ -V Show version number.
+
+ -l List available commands.
+ Note that this will only display commands you are permitted to run.
+</pre>
+<p><b> Configuration</b></p>
+<p>Configuration entries are read from <span class="telety">/etc/op.conf</span> and all files in lexical order from <span class="telety">/etc/op.d</span> with the extension .conf. Files must be owned by root and not have group or other permissions set.</p>
+<p>The fields of the entries in the configuration files are separated by white space. Each entry may span several lines and continues until the next alphanumeric string is found at the beginning of a lines (which is taken to be the next mnemonic or variable definition, and thus the beginning of a new entry). Comments may be embedded beginning with a # character. Each entry in the configuration files has the following form:</p>
+<blockquote>
+<p> <span class="telety">mnemonic</span></p>
+<p><span class="telety"> command [ arg ... ] ; [ option ... ]</span></p>
+<p>or</p>
+<p><span class="telety">var=value </span></p>
+</blockquote>
+<p>Key:<br>
+<span class="telety">var</span> a variable name, which must be an upper case alphanumeric identifier. Variables are expanded when reading options.</p>
+<p><span class="telety">value</span> the remainder of the line is taken to be the value of the variable.</p>
+<p><span class="telety">mnemonic</span> a unique, alphanumeric identifier for each operator function. </p>
+<p><span class="telety">command</span> the full pathname of the executable to be run by op when the associated mnemonic is chosen. </p>
+<p><span class="telety">arg(s) </span>any arguments, either literal or variable, needed by command. Literal arguments are simply specified directly, like specific command options (0Gun) or files (/dev/rmt20). Variable arguments are specified here as $1, $2 ... $n; <br>
+For a full list look in the options section of the op man page( <span class="telety">man op</span> ).</p>
+<p> <span class="telety">$*</span> indicates any number trailing arguments. </p>
+<p><b>Examples</b><br>
+Example /etc/op.conf:</p>
+<blockquote>
+<p> <span class="telety"># Define some users<br>
+OPERATORS=(fred|barry)<br>
+# Define hosts that Fred is restricted to<br>
+FRED_HOSTS=(alpha|beta)<br>
+# Define hosts that Barry is restricted to<br>
+BARRY_HOSTS=(theta|gamma)<br>
+# Define user/host access list<br>
+ACCESS_LIST=fred@FRED_HOSTS|barry@BARRY_HOSTS</span></p>
+<p class="telety"> # 'op shell' - gives user a root shell<br>
+shell<br>
+/bin/su -; <br>
+users=ACCESS_LIST</p>
+<p class="telety"> environment</p>
+<p class="telety"> password <br>
+help=&quot;Root shell&quot;</p>
+<p class="telety"> # 'op reboot' - reboot system<br>
+reboot<br>
+/sbin/reboot; <br>
+users=ACCESS_LIST</p>
+<p class="telety"> password <br>
+help=&quot;Reboot system&quot;</p>
+<p class="telety"> # 'op shutdown &lt;time&gt;' - shutdown at a<br>
+# certain time. Restricts argument to<br>
+# valid values only<br>
+shutdown<br>
+/sbin/shutdown -h $1;<br>
+users=ACCESS_LIST<br>
+$1=(now|[0-1]?[0-9]:[0-9][0-9]|2[0-3]:[0-5][0-9]|+[0-9]+)<br>
+help=&quot;Shutdown system&quot;</p>
+<p class="telety"> # Switch inetd on and off, shows complex<br>
+# shell example and 'string' arguments. $1<br>
+# in this example is expanded by op<br>
+inetd /bin/sh -c '<br>
+case $1 in<br>
+on) /usr/sbin/inetd -s ;;<br>
+off) /usr/bin/pkill inetd ;;<br>
+esac<br>
+';<br>
+users=ACCESS_LIST<br>
+$1=on|off </p>
+</blockquote>
+<p> <i>&ldquo;He who reigns within himself, and rules passions, desires, and fears, is more than a king&rdquo; - Milton </i><br>
+ <br>
+ <b> Related</b>:</p>
+<p><a href="chroot.html">chroot</a> - Run a command with a different root directory<br>
+ <a href="sudo.html">sudo</a> - Execute a command as another user<br>
+<a href="su.html">su</a> - Substitute user identity<br>
+Equivalent Windows command: <a href="../term_tools/nt/runas.html">runas</a> - Execute a program under a different user account.</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/open.html b/help/en/bash/open.html
new file mode 100644
index 0000000..f56d608
--- /dev/null
+++ b/help/en/bash/open.html
@@ -0,0 +1,59 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>open MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1>open</h1>
+<p>Open a file in its default application, using virtual terminal (VT).</p>
+<pre>Syntax
+ open <i>Files</i>...
+
+Options:
+ files The filename(s) to open, wildcards are accepted.</pre>
+<p>Example</p>
+<p>Open all the text files in the current directory using your default text editor:</p>
+<p><span class="telety">open *.txt </span></p>
+<p><i>&ldquo;Do not run; scorn running with thy heels&rdquo; - Shakespeare</i></p>
+<p><b>Related</b>:<br>
+ <br>
+<a href="kill.html">kill</a> - Stop a process from running<br>
+<a href="xdg-open.html">xdg-open</a> - Open a file in its default application<br>
+Equivalent Windows command: <a href="../term_tools/nt/start.html">START</a> - Start a program or command.</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/passwd.html b/help/en/bash/passwd.html
new file mode 100644
index 0000000..2e4230d
--- /dev/null
+++ b/help/en/bash/passwd.html
@@ -0,0 +1,89 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>passwd MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> passwd</h1>
+<p>Modify a user password.</p>
+<pre>SYNTAX
+ passwd [<em>options</em>...] <accountname>
+
+OPTIONS
+ -d, --delete delete the password for the named account (root only)
+
+ -f, --force force operation (effectively calls `chfn'?)
+
+ -k, --keep-tokens keep non-expired authentication tokens
+
+ -l, --lock lock the named account (root only)
+
+ -S, --status report password status on the named account (root only)
+
+ --stdin read new tokens from stdin (root only)
+
+ -u, --unlock unlock the named account (root only)
+
+ -?, --help Show this help message
+
+ --usage Display brief usage message</pre>
+<p>If no options are specified - passwd will change the password
+ of the currently logged in user - will prompt for the old and new passwords.</p>
+<p>Password aging (for new accounts) can be set to
+enforce a limited lifetime for each password: <i>/etc/login.defs<br>
+</i> parameters: PASS_MAX_DAYS, PASS_MIN_DAYS, PASS_WARN_AGE</p>
+<p><i>"Chico : you can't come in unless you give the password... <br>
+ Well, what is the password?... I got it! Haddock! - Groucho
+ Marx</i><b><br>
+ <br>
+ Related</b>:<br>
+<a href="chgrp.html"><br>
+chgrp</a> - Change group ownership<br>
+chage -
+Set password age<br>
+ <a href="chmod.html">chmod</a> - Change access permissions<br>
+ <a href="chown.html">chown</a> - Change file owner and group<br>
+ <a href="quotactl.html">quotactl</a> - Set disk quotas<br>
+ <a href="who.html">who</a> - Print who is currently logged in<br>
+<i>/etc/default/useradd</i><br>
+<i>/etc/login.defs</i><br>
+<a href="http://punchcast.com/">Punchcast password generator </a><br>
+Equivalent Windows command:
+<a href="../term_tools/nt/net_useradmin.html">NET USER</a> <i>username</i> * /domain</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/paste.html b/help/en/bash/paste.html
new file mode 100644
index 0000000..6376ad2
--- /dev/null
+++ b/help/en/bash/paste.html
@@ -0,0 +1,71 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>paste MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> paste</h1>
+<p>Merge lines of files, write to standard output lines consisting
+ of sequentially corresponding lines of each given file, separated by a TAB character.</p>
+<pre>SYNTAX
+ paste [<em>options</em>]... [<em>file</em>]...
+
+OPTIONS
+ -s
+ --serial
+ Paste the lines of one file at a time rather than one line from
+ each file.
+
+ -d <em>DELIM-LIST</em>
+ --delimiters <em>DELIM-LIST</em>
+ Consecutively use the characters in <em>DELIM-LIST</em> instead of TAB to
+ separate merged lines. When <em>DELIM-LIST</em> is exhausted, start again
+ at its beginning.
+
+Standard input is used for a file name of `-' or if no input files are given.</pre>
+<p><b>Related</b>:<br>
+ <br>
+ <a href="csplit.html">csplit</a> - Split a file into context-determined pieces<br>
+ <a href="cut.html">cut</a> - Divide a file into several parts<br>
+ <a href="fold.html">fold</a> - Wrap input lines to fit in specified width <br>
+ <a href="fmt.html">fmt</a> - Reformat paragraph text<br>
+ <a href="join.html">join</a> - Join lines on a common field <br>
+ <a href="split.html">split</a> - Split a file into fixed-size pieces<br>
+<a href="tail.html">tail</a> - Output the last part of files </p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/ping.html b/help/en/bash/ping.html
new file mode 100644
index 0000000..92fec30
--- /dev/null
+++ b/help/en/bash/ping.html
@@ -0,0 +1,159 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>ping MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1>ping</h1>
+<p>Test a network connection. When using ping for fault isolation, it should first be run on the local host, to verify that the local network interface is up and running.
+Then, hosts and gateways further and further away should be `pinged'.</p>
+<pre>Syntax<br> ping [<i>options</i>] <i>destination_host</i>
+
+Options
+
+ -a Audible ping.
+
+ -A Adaptive ping. Interpacket interval adapts to round-trip time,
+ so that effectively not more than one (or more, if preload is set) unanswered probes
+ present in the network. Minimal interval is 200msec for not super-user.
+ On networks with low rtt this mode is essentially equivalent to flood mode.
+
+ -b Allow pinging a broadcast address.
+
+ -B Do not allow ping to change source address of probes. The address is bound to one selected when ping starts.
+
+ -c <i>count</i> Stop after sending (and receiving) <i>count</i> ECHO_RESPONSE packets.
+
+ -d Debug, Set the SO_DEBUG option on the socket being used.
+
+ -F <i>flow_label</i> Allocate and set 20 bit flow label on echo request packets. (Only ping6).
+ If value is zero, kernel allocates random flow label.
+
+ -f Flood ping, output packets as fast as they come back or 100 times per second.
+
+ -i <i>wait</i> Set an interval of <i>wait </i>seconds between sending each packet. default=one second.
+ Only super-user may set <i>wait</i> to values less 0.2 seconds.
+ (incompatible with -f)
+
+ -I <i>interface address<br></i> Set source address to specified <i>interface_address</i>.
+ Argument may be numeric IP address or name of device.
+ Required when pinging an IPv6 link-local address.
+
+ -l <i>preload</i> If preload is specified, ping sends that many packets as fast as
+ possible before falling into its normal mode of behavior.
+ Only the super-user may select preload more than 3.
+
+ -L Suppress loopback of multicast packets.
+ only applies if the ping destination is a multicast address.
+
+ -n Numeric output only. No attempt will be made to lookup symbolic
+ names for host addresses.
+ -p <i>pattern</i>
+ Specify up to 16 `pad' bytes to fill out the packet sent.
+ This is useful for diagnosing data-dependent problems in a
+ network. eg, `-p ff' will fill the packet sent with all ones.
+
+ -q Quiet output. Only display the summary lines at startup time and when finished.
+
+ -Q <i>tos </i> Set Quality of Service -related bits in ICMP datagrams. <i>tos</i> can be a decimal or hex number.
+ Multiple TOS bits should not be set simultaneously. For detail see RFC1349 and RFC2474
+
+ -R Record route(IPv4 only). Includes the RECORD_ROUTE option in the ECHO_REQUEST packet and
+ display the route buffer on returned packets.
+ Note that the IP header is only large enough for nine such routes.
+ Many hosts ignore or discard this option.
+
+ -r Bypass the normal routing tables and send directly to a host on an attached network.
+ If the host is not on a directly-attached network, an error is returned.
+ This option can be used to ping a local host through an interface that has no route through it
+ (e.g., after the interface was dropped by routed(8)).
+
+ -s <i>packetsize
+ </i> The number of data bytes to be sent. The default is 56, which translates into
+ 64 ICMP data bytes when combined with the 8 bytes of ICMP header data.
+
+ -S <i>sndbuf</i> Set socket <i>sndbuf</i>. If not specified, it is selected to buffer not more than one packet. <br>
+ -t <i>ttl</i> Set the IP Time to Live. <br>
+ -T <i>timestamp_option</i><br> Set special IP timestamp options, either 'tsonly' (only timestamps),
+ 'tsandaddr' (timestamps and addresses)
+ or 'tsprespec host1 [host2 [host3 [host4]]]' (timestamp prespecified hops). <br>
+ -M <i>hint</i> Select Path MTU Discovery strategy. <i>hint</i> may be either 'do' (prohibit fragmentation,
+ even local one), 'want' (do PMTU discovery, fragment locally when packet size is large),
+ or 'dont' (do not set DF flag). <br>
+ -U Print full user-to-user latency (the old behaviour).
+ Normally ping prints network round trip time, which can be different f.e. due to DNS failures.
+
+ -v Verbose output. ICMP packets other than ECHO_RESPONSE that are received are listed.
+
+</pre>
+<p>
+Ping is intended for use in network testing, measurement and management. Because of the load it can impose on the network, it is unwise to use ping during normal operations or from automated scripts. </p>
+<p>If ping does not receive any reply packets at all it will exit with code 1. If a packet <i>count</i> and <i>deadline</i> are both specified, and fewer than <i>count</i> packets are received by the time the <i>deadline</i> has arrived, it will also exit with code 1. On other error it exits with code 2. Otherwise it exits with code 0. This makes it possible to use the exit code to see if a host is alive or not.</p>
+<p><b>Flood Ping</b><br>
+For every ECHO_REQUEST sent a period `.' is printed, while for every ECHO_REPLY received a backspace is printed. This provides a rapid display of how many packets are being dropped. Only the super-user may use this option. This can be very hard on a network and should be used with caution.</p>
+<p>Round-trip times and packet loss statistics are computed. If duplicate packets are received, they are not included in the packet loss calculation, although the round trip time of these packets is used in calculating the minimum/average/maximum round-trip time numbers. When the specified number of packets have been sent (and received) or if the program is terminated with a SIGINT, a brief summary is displayed.</p>
+<p>Flood pinging is not recommended in general, and flood pinging the broadcast address should only be done under very controlled conditions.</p>
+<p><b>ICMP Packet Details</b><br>
+An IP header without options is 20 bytes. An ICMP ECHO_REQUEST packet contains an additional 8 bytes worth of ICMP header followed by an arbitrary amount of data. When a packetsize is given, this indicated the size of this extra piece of data (the default is 56). Thus the amount of data received inside of an IP packet of type ICMP ECHO_REPLY will always be 8 bytes more than the requested data space (the ICMP header).</p>
+<p> If the data space is at least eight bytes large, ping uses the first eight bytes of this space to include a timestamp which it uses in the computation of round trip times. If less than eight bytes of pad are specified, no round trip times are given.</p>
+<p><b>Duplicate and Damaged Packets</b><br>
+Ping will report duplicate and damaged packets. <br>
+Duplicate packets are rarely; if ever; a good sign, although the presence of low levels of duplicates may not always be cause for alarm.<br>
+Damaged packets are a serious cause for alarm and often indicate broken hardware somewhere in the ping packet's path (in the network or in the hosts).</p>
+<p><b>Different Data Patterns</b><br>
+The (inter)network layer should never treat packets differently depending on the data contained in the data portion. Unfortunately, data-dependent<br>
+problems have been known to sneak into networks and remain undetected for long periods of time. If you have a data-dependent problem you will probably have to do a lot of testing to find it. If you are lucky, you may manage to find a file that either can't be sent across your network or that takes much longer to transfer than other similar length files. You can then examine this file for repeated patterns that you can test using the -p option of ping.
+<p><b>TTL Details</b><br>
+The <a href="http://en.wikipedia.org/wiki/Time_to_live">Time To Live</a>, (TTL) value of an IP packet represents the maximum number of IP routers that the packet can go through before being thrown away. In current practice you can expect each router in the Internet to decrement the TTL field by exactly one.</p>
+<p> The TCP/IP specification states that the TTL field for TCP packets should be set to 60, but many systems use smaller values (4.3 BSD uses 30, 4.2 used 15).</p>
+<p> The maximum possible value of this field is 255, and most Unix systems set the TTL field of ICMP ECHO_REQUEST packets to 255. This is why you will find you can `ping' some hosts, but not reach them with telnet(1) or <a href="../term_tools/bash/ftp.html">ftp</a>.</p>
+<p> In normal operation ping prints the ttl value from the packet it receives. When a remote system receives a ping packet, it can do one of three things with the TTL field in its response:</p>
+<ul>
+<li> Not change it; this is what Berkeley Unix systems did before the 4.3BSD-Tahoe release. In this case the TTL value in the received packet will be 255 minus the number of routers in the round-trip path.</li>
+<li> Set it to 255; this is what current Berkeley Unix systems do. In this case the TTL value in the received packet will be 255 minus the number of routers in the path from the remote system to the pinging host.</li>
+<li> Set it to some other value. Some machines use the same value for ICMP packets that they use for TCP packets, for example either 30 or 60. Others may use completely wild values.</li>
+</ul>
+<p> <i>&quot;There's a Nong Nang Ning, Where the trees go Ping! &quot; ~ Spike Milligan </i> </p>
+<p><b> Related</b>:</p>
+<p>netstat(1)<br>
+ifconfig(8)<br>
+routed(8)<br>
+Equivalent Windows command:
+<a href="../term_tools/nt/ping.html">Ping</a> - Test a network connection</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/pkill.html b/help/en/bash/pkill.html
new file mode 100644
index 0000000..e57777c
--- /dev/null
+++ b/help/en/bash/pkill.html
@@ -0,0 +1,126 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>pkill MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> pgrep / pkill</h1>
+<p>pgrep searches through the currently running processes, pkill will send the specified signal (by default SIGTERM) to each process instead of listing them on stdout.</p>
+<pre>Syntax
+ pgrep [-flvx] [-d <i>delimiter</i>] [-n|-o] [-P <i>ppid</i>,...] [-g <i>pgrp</i>,...]
+ [-s <i>sid</i>,...] [-u <i>euid</i>,...] [-U <i>uid</i>,...] [-G gid,...]
+ [-t <i>term</i>,...] [<i>pattern</i>]
+
+ pkill [-signal] [-fvx] [-n|-o] [-P <i>ppid</i>,...] [-g <i>pgrp</i>,...]
+ [-s <i>sid</i>,...] [-u <i>euid</i>,...] [-U <i>uid</i>,...] [-G <i>gid</i>,...]
+ [-t <i>term</i>,...] [<i>pattern</i>]
+
+Key
+ <i>pattern</i><br> An Extended Regular Expression to match process names or command lines.
+
+ -d <i>delimiter</i>
+ Set the string used to delimit each process ID in the output
+ (by default a newline). (pgrep only.)
+ -f
+ The pattern is normally only matched against the process name.
+ When -f is set, the full command line is used.
+ -g <i>pgrp</i>,...
+ Only match processes in the process group IDs listed.
+ Process group 0 is translated into pgrep's or pkill's own process group.
+ -G <i>gid</i>,...
+ Only match processes whose real group ID is listed.
+ Either the numerical or symbolical value may be used.
+ -l
+ List the process name as well as the process ID. (pgrep only.)
+ -n
+ Select only the newest (most recently started) of the matching processes.
+ -o
+ Select only the oldest (least recently started) of the matching processes.
+ -P <i>ppid</i>,...
+ Only match processes whose parent process ID is listed.
+ -s <i>sid</i>,...
+ Only match processes whose process session ID is listed.
+ Session ID 0 is translated into pgrep's or pkill's own session ID.
+ -t <i>term</i>,...
+ Only match processes whose controlling terminal is listed.
+ The terminal name should be specified without the "/dev/" prefix.
+ -u <i>euid</i>,...
+ Only match processes whose effective user ID is listed.
+ Either the numerical or symbolical value may be used.
+ -U <i>uid</i>,...
+ Only match processes whose real user ID is listed.
+ Either the numerical or symbolical value may be used.
+ -v
+ Negates the matching.
+ -x
+ Only match processes whose name (or command line if -f is specified)
+ exactly match the pattern.
+ -signal
+ Defines the signal to send to each matched process.
+ Either the numeric or the symbolic signal name can be used. (pkill only.)
+</pre>
+<p>All the criteria have to match. </p>
+<p>For example, <span class="code">pgrep -u root sshd</span> will only list the processes called sshd AND owned by root. </p>
+<p>On the other hand, <span class="code">pgrep -u root,daemon</span> will list the processes owned by root OR daemon. </p>
+<p><b>Examples</b></p>
+<p>Example 1: Find the process ID of the named daemon:</p>
+<p class="code">$ pgrep -u root named</p>
+<p>Example 2: Make syslog reread its configuration file:</p>
+<p class="code">$ pkill -HUP syslogd</p>
+<p>Example 3: Give detailed information on all xterm processes:</p>
+<p class="code">$ ps -fp $(pgrep -d, -x xterm)</p>
+<p>Example 4: Make all netscape processes run nicer:</p>
+<p class="code">$ renice +4 'pgrep netscape'</p>
+<p><b>Exit Status</b></p>
+<p> 1. One or more processes matched the criteria.<br>
+2. No processes matched.<br>
+3. Syntax error in the command line.<br>
+4. Fatal error: out of memory etc.</p>
+<p><i>&ldquo;Somebody should tell us, right at the start of our lives, that we are dying. Then we might live life to the limit, every minute of every day. Do it! I say. Whatever you want to do, do it now! There are only so many tomorrows&rdquo; - Pope Paul VI</i></p>
+<p><b> Related</b>:<br>
+<br>
+<a href="ps.html">ps</a> - List running processes (returns PID)<br>
+<a href="kill.html">kill</a> - Stop a process from running <br>
+killall - Kill processes by name<br>
+skill(1)<br>
+<a href="bg.html">bg</a> - Put a process in the background<br>
+<a href="fg.html">fg</a> - Put a process in the foreground<br>
+regex(7) signal(7)<br>
+Equivalent Windows command: <a href="../term_tools/nt/kill.html">KILL</a> - Remove a program from memory</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/popd.html b/help/en/bash/popd.html
new file mode 100644
index 0000000..ca9d3a6
--- /dev/null
+++ b/help/en/bash/popd.html
@@ -0,0 +1,72 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>popd MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> popd</h1>
+<p>Remove the top entry from the directory stack, and <code>cd</code>
+to the new top directory.</p>
+<pre>SYNTAX
+ popd [+<em>N</em> | -<em>N</em>] [-n]
+
+Key
+ +<em>N</em> Remove the <em>N</em>th directory (counting from the left of the list
+ printed by dirs), starting with zero.
+
+ -<em>N</em> Remove the <em>N</em>th directory (counting from the right of the list
+ printed by dirs), starting with zero.
+
+ -n Suppress the normal change of directory when removing directories from
+ the stack, so that only the stack is manipulated. </pre>
+<p>When no arguments are given, popd removes the top directory from
+ the stack and performs a cd to the new top directory. <br>
+ <br>
+ The elements are numbered from 0 starting at the first directory listed with
+dirs; i.e., popd is equivalent to popd +0.</p>
+<p><i>&quot;It's amazing how low you go to get high&quot; - John Lennon </i><br>
+ <b><br>
+ Related</b>:<br>
+ <a href="dirs.html"><br>
+ dirs</a> - Display list of remembered directories<br>
+ <a href="pushd.html">pushd</a> - Save and then change the current directory <br>
+ Equivalent Windows command:
+ <a href="../term_tools/nt/popd.html">POPD</a> - Restore the previous value of the current
+directory</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/pr.html b/help/en/bash/pr.html
new file mode 100644
index 0000000..b0dfe34
--- /dev/null
+++ b/help/en/bash/pr.html
@@ -0,0 +1,166 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>pr MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> pr</h1>
+<p>Prepare files for printing, printing and pagination filter for text files.<br>
+ When multiple input files are specified, each is read, formatted, and written
+to standard output.</p>
+<pre>SYNTAX
+ pr [<i>options</i>] [<i>file</i> ...]
+
+OPTIONS
+
+ +<i>beg_pag</i>[:<i>end-pag</i>],
+ --pages=[<i>beg_pag</i>[:<i>end-pag</i>]
+ Begin printing on page <i>beg_pag </i>and end on <i>end-pag </i>if specified.
+
+ -<i>num_cols</i>
+ --columns=<i>num_cols</i>
+ Print in <i>num_cols</i> number of columns, balancing the number of lines
+ in the columns on each page.
+
+ -a
+ --across
+ Print columns horizontally, not vertically.
+
+ -c
+ --show-control-chars
+ Convert control characters to hat notation (such as ^C) and other unprintable characters to octal backslash format.
+ -d
+ --double-space
+ Double space.
+
+ -e[<i>tab-char[width</i>]]
+ --expand-tabs=[<i>tab-char[width</i>]]
+ Convert tabs (or tab-chars) to spaces.
+ If <i>width</i> is specified, convert tabs to <i>width</i> characters (default is 8).
+
+ -f
+ -F
+ --form-feed
+ Separate pages with form feeds, not newlines.
+
+ -h <i>header</i>
+ --header=header
+ Use header for the header instead of the filename.
+
+ -i[<i>out-tab-char[out-tab-width</i>]]
+ --output-tabs[=<i>out-tab-char[out-tab-width</i>]]
+ Replace spaces with tabs on output. Can specify alternative tab character (default is tab) and width (default is 8).
+
+ -J
+ --join-lines
+ Merge full lines; ignore -W if set.
+
+ -l <i>lines</i>
+ --length=<i>lines</i>
+ Set page length to <i>lines</i> (default 66). If lines is less than 10, omit headers and footers.
+
+ -m
+ --merge
+ Print all files, one file per column.
+
+ -n[<i>delimiter</i>[<i>digits</i>]]
+ --number-lines[=<i>delimiter</i>[<i>digits</i>]]
+ Number columns, or, with the -m option, number lines.
+ Append delimiter to each number (default is a tab) and limit
+ the size of numbers to digits (default is 5).
+
+ -o <i>width</i>
+ --indent=<i>width</i>
+ Set left margin to width.
+
+ -r
+ --no-file-warnings
+ Continue silently when unable to open an input file.
+
+ -s[<i>delimiter</i>]
+ --separator[=<i>delimiter</i>]
+ Separate columns with delimiter (default is a tab) instead of spaces.
+
+ -S[<i>string</i>]
+ --sep-string[=<i>string</i>]
+ Separate columns with string. Default is a tab with -J and a space otherwise.
+
+ -t
+ --omit-header
+ Suppress headers, footers, and fills at end of pages.
+
+ -T
+ --omit-pagination
+ Like -t but also suppress form feeds.
+
+ -v
+ --show-non-printing
+ Convert unprintable characters to octal backslash format.
+
+ -w <i>page_width</i>
+ --width=<i>page_width</i>
+ Set the page width to <i>page_width </i>characters for multi-column output.
+ Default is 72.
+
+ -W <i>page_width</i>
+ --page-width=<i>page_width</i>
+ Set the page width to always be page_width characters.
+ Default is 72.
+
+ <i>file</i>
+ A pathname of a file to be printed.
+ If no <i>file</i> operands are specified, or if a <i>file</i> operand is `<b>-</b>',
+ the standard input is used.
+
+ --help
+ Print a help message and then exit.
+
+ --version
+ Print version information and then exit.
+</pre>
+<p> <i>"And bring me a hard copy of the Internet so I can do some
+ serious surfing&quot; - Dilbert
+ comic strip</i></p>
+<p><b>Related commands</b>:<br>
+ <br>
+ <a href="cat.html">cat</a> - Display the contents of a file<br>
+ <a href="more.html">more</a> - Display output one screen at a time <br>
+Equivalent Windows commands:
+<a href="../term_tools/nt/print.html">PRINT</a> - Print a file </p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/printf.html b/help/en/bash/printf.html
new file mode 100644
index 0000000..912d4aa
--- /dev/null
+++ b/help/en/bash/printf.html
@@ -0,0 +1,148 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>printf MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> printf</h1>
+<p>Format and print data.<br>
+ Write the formatted <var>arguments</var> to the standard output under the control
+of the <var>format</var>. </p>
+<pre>SYNTAX
+ printf <i>format</i> [<i>argument</i>]...
+
+ printf --help
+
+ printf --version
+
+OPTIONS
+
+ The <i>format</i> characters and their meanings are:
+
+ \" double quote
+
+ \0NNN character with octal value NNN (0 to 3 digits)
+
+ \\ backslash
+
+ \a alert (BEL)
+
+ \b backspace
+
+ \c produce no further output
+
+ \f form feed
+
+ \n new line
+
+ \r carriage return
+
+ \t horizontal tab
+
+ \v vertical tab
+
+ \xNNN byte with hexadecimal value NNN (1 to 3 digits)
+
+ \uNNNN character with hexadecimal value NNNN (4 digits)
+
+ \UNNNNNNNN
+ character with hexadecimal value NNNNNNNN (8 digits)
+
+ %% a single %
+
+ %<b>b</b> ARGUMENT as a string with `\' escapes interpreted
+
+ %<i>W</i><b>d</b> Integer `<i>W</i>' digits wide xxxx
+
+ %<i>W.D</i><b>e</b> Scientific notation x.xxxx e nnn. float, double
+
+ %<i>W.D<b>f</b></i> Fixed format xx.xxxx. float, double
+
+ %<i>W.D</i><b>g</b> Variable `<i>W</i>' digits wide,`<i>D</i>' decimals xxxx.xx
+
+ %<b>q</b> Output the corresponding <var>argument</var> in a format that can be
+ reused as shell input
+
+ %<b>s</b> Character string char
+
+ and all C format specifications ending with one of diouxXfeEgGcs, with
+ ARGUMENTs converted to proper type first. Variable widths are handled.
+ e.g. `\0ooo' = an octal number, `\xhhh' = a hex number</pre>
+<p>The <var>format</var> is a character string which contains three
+ types of objects: </p>
+<ul>
+ <li>Plain characters, which are simply copied to standard output, </li>
+ <li>Character escape sequences, which are converted and copied to standard output,
+ </li>
+ <li>Format specifications, each of which causes printing of the next successive
+ <var>argument</var>. </li>
+</ul>
+<p>The <var>format</var> is reused as necessary to consume all of the <var>arguments</var>.
+ If the <var>format</var> requires more <var>arguments</var> than are supplied,
+ the extra format specifications behave as if a zero value or null string, as
+ appropriate, had been supplied. </p>
+<p>The return value is zero on success, non-zero on failure. </p>
+<p><b>Examples</b></p>
+<pre> # Use \n to start a new line
+$ printf "Two separate\nlines\n"
+Two separate
+lines
+
+# Echo a list of numbers from 1 to 100, adding 3 digits of Zero padding
+# so they appear as 001, 002, 003 etc:
+$ for ((num=1;num&lt;=100;num+=1)); do echo `printf &quot;%03d&quot; $num`; done
+
+# Print text followed by variable $USER
+$ printf "Hello, $USER.\n\n"
+
+# Display an integer variable
+$ printf "Distance = %5d Miles" $distance
+Distance = 27 Miles
+
+# Print text interspersed with command results
+$ printf "This is `uname -s` running on a `uname -m` processor.\n\n"</pre>
+<p><i>&ldquo;I really look with commiseration over the great body of my fellow citizens who, reading newspapers, live and die in the belief that they have known something of what has been passing in their time&rdquo; - Thomas Jefferson</i></p>
+<p> <b>Related</b>:<br>
+ <a href="cat.html"><br>
+ cat</a> - Display the contents of a file<br>
+ <a href="less.html">less</a> - Display output one screen at a time <br>
+ <a href="more.html">more</a> - Display output one screen at a time<br>
+Equivalent Windows commands:
+<a href="../term_tools/nt/echo.html">ECHO</a> - Display message on screen</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/ps.html b/help/en/bash/ps.html
new file mode 100644
index 0000000..5905069
--- /dev/null
+++ b/help/en/bash/ps.html
@@ -0,0 +1,288 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>ps MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> ps</h1>
+<p>Process status, information about processes running in memory.
+If you want a repetitive update of this status, use top.</p>
+<pre>Syntax
+
+ ps <i>option(s)</i>
+ ps [-L]
+
+Options
+ -L List all the <a href="../term_tools/bash/ps_keywords.html">keyword</a> options</pre>
+<p>This version of ps accepts 3 kinds of option:<br>
+<br>
+-Unix98 options may be grouped and must be preceeded by a dash.<br>
+
+BSD options may be grouped and must not be used with a dash.<br>
+--GNU long options are preceeded by two dashes.<br>
+<br>
+Options of different types may be freely mixed. The <a href="../term_tools/bash/ps_keywords.html">PS_PERSONALITY</a> environment variable provides more detailed control of ps behavior.<br>
+<br>
+The Options below are listed side-by-side (unless there are differences).</p>
+<pre>Simple Process Selection:
+ -A a select all processes (including those of other users)
+ -a select all with a tty except session leaders
+ -d select all, but omit session leaders
+ -e select all processes
+ g really all, even group leaders (does nothing w/o SunOS settings)
+ -N negate selection
+ r restrict output to running processes
+ T select all processes on this terminal
+ x select processes without controlling ttys
+ --deselect negate selection
+
+Process Selection by List:
+
+ -C select by command name
+ -G select by RGID (supports names)
+ -g select by session leader OR by group name
+ --Group select by real group name or ID
+ --group select by effective group name or ID
+ -p p --pid select by process ID (PID)
+ -s --sid select by session ID
+ -t --tty select by terminal (tty)
+ -u U select by effective user ID (supports names)
+ -U select by RUID (supports names)
+ --User select by real user name or ID
+ --user select by effective user name or ID
+
+ -<i>123</i> implied --sid
+ <i>123</i> implied --pid
+
+Output Format Control:
+
+ -c Different scheduler info for -l option
+ -f Full listing
+ -j j Jobs format
+ -l l Long format
+ -O O Add the information associated with the space or comma separated
+ list of <a href="../term_tools/bash/ps_keywords.html">keywords</a> specified, after the <b>process ID</b>, in the default
+ information display.
+
+ -o o Display information associated with the space or comma separated
+ list of <a href="../term_tools/bash/ps_keywords.html">keywords</a> specified.
+ --format <a href="../term_tools/bash/ps_keywords.html">user-defined format</a>
+ s display signal format
+ u display user-oriented format
+ v display virtual memory format
+ X old Linux i386 register format
+ -y do not show flags; show rss in place of addr
+
+Output Modifiers:
+ C use raw CPU time for %CPU instead of decaying average
+ c true command name
+ e show environment after the command
+ f ASCII-art process hierarchy (forest)
+ -H show process hierarchy (forest)
+ h do not print header lines (repeat header lines in BSD personality)
+ -m m show all threads
+ -n set namelist file
+ n numeric output for WCHAN and USER
+ N specify namelist file
+ O <a href="../term_tools/bash/ps_keywords.html">sorting</a> order (overloaded)
+ S include some dead child process data (as a sum with the parent)
+ -w w wide output
+ --cols set screen width
+ --columns set screen width
+ --forest ASCII art process tree
+ --html HTML escaped output
+ --headers repeat header lines
+ --no-headers print no header line at all
+ --lines set screen height
+ --nul unjustified output with NULs
+ --null unjustified output with NULs
+ --rows set screen height
+ --sort specify <a href="../term_tools/bash/ps_keywords.html">sorting</a> order
+ --width set screen width
+ --zero unjustified output with NULs
+
+Information:
+ -V V print version
+ L list all format specifiers
+ --help print help message
+ --info print debugging info
+ --version print version
+
+Obsolete:
+ A increase the argument space (DecUnix)
+ M use alternate core (try -n or N instead)
+ W get swap info from ... not /dev/drum (try -n or N instead)
+ k use /vmcore as c-dumpfile (try -n or N instead)
+</pre>
+<p><span class="body"> NOTES<br>
+ The "-g" option can select by session leader OR by group
+ name. Selection by session leader is specified by many
+ standards, but selection by group is the logical behavior
+ that several other operating systems use. This ps will
+ select by session leader when the list is completely
+ numeric (as sessions are). Group ID numbers will work only
+ when some group names are also specified.<br>
+ <br>
+ The "m" option should not be used. Use "-m" or "-o" with a
+ list. ("m" displays memory info, shows threads, or sorts
+ by memory use)<br>
+ <br>
+ The "h" option varies between BSD personality and Linux usage
+ (not printing the header) Regardless of the current personality,
+ you can use the long options --headers and --no-headers<br>
+ <br>
+ Terminals (ttys, or screens of text output) can be specified in several forms: /dev/ttyS1, ttyS1, S1.
+ Obsolete "ps t" (your own terminal) and "ps t?" (processes without a terminal)
+ syntax is supported, but modern options ("T","-t" with list, "x", "t" with list)
+ should be used instead.<br>
+ <br>
+ The BSD "O" option can act like "-O" (user-defined output
+ format with some common fields predefined) or can be used
+ to specify sort order. Heuristics are used to determine
+ the behavior of this option. To ensure that the desired
+ behavior is obtained, specify the other option (sorting or
+ formatting) in some other way.<br>
+ <br>
+ For sorting, BSD "O" option syntax is
+ O[+|-]k1[,[+|-]k2[,...]] Order the process listing
+ according to the multilevel sort specified by the sequence
+ of short keys from SORT KEYS, k1, k2, ... The `+' is quite
+ optional, merely re-iterating the default direction on a
+ key. `-' reverses direction only on the key it precedes.<br>
+ The O option must be the last option in a single command
+ argument, but specifications in successive arguments are
+ catenated.<br>
+ <br>
+ GNU sorting syntax is --sortX[+|-]key[,[+|-]key[,...]]<br>
+ Choose a multi-letter key from the SORT KEYS section. X
+ may be any convenient separator character. To be GNU-ish
+ use `='. The `+' is really optional since default direction is increasing numerical or lexicographic order. For
+ example, ps jax --sort=uid,-ppid,+pid<br>
+ <br>
+ This ps works by reading the virtual files in /proc. This
+ ps does not need to be suid kmem or have any privileges to
+ run. Do not give this ps any special permissions.<br>
+ <br>
+ This ps needs access to a namelist file for proper WCHAN
+ display. The namelist file must match the current Linux
+ kernel exactly for correct output.<br>
+ <br>
+ To produce the WCHAN field, ps needs to read the System.map file created when the kernel is compiled. The search path is:</span></p>
+<pre> $PS_SYSTEM_MAP
+ /boot/System.map-`uname -r`
+ /boot/System.map
+ /lib/modules/`uname -r`/System.map
+ /usr/src/linux/System.map
+ /System.map</pre>
+<p> The member <span class="code">used_math of task_struct</span> is not shown, since
+ crt0.s checks to see if math is present. This causes the math flag to be set for all processes, and so it is Programs swapped out to disk will be shown without command line arguments, and unless the c option is given, in
+ brackets.<br>
+ <br>
+ %CPU shows the cputime/realtime percentage. It will not add up to 100% unless you are lucky. It is time used divided by the time the process has been running.<br>
+ <br>
+ The SIZE and RSS fields don't count the page tables and the task_struct of a proc; this is at least 12k of memory that is always resident. SIZE is the virtual size of the
+ proc (code+data+stack).<br>
+ <br>
+ Processes marked <i>defunct</i> are dead processes (so-called"zombies") that remain because their parent has not
+destroyed them properly. These processes will be destroyed by init(8) if the parent process exits.</p>
+<pre>
+ PROCESS FLAGS
+ ALIGNWARN 001 print alignment warning msgs
+ STARTING 002 being created
+ EXITING 004 getting shut down
+ PTRACED 010 set if ptrace (0) has been called
+ TRACESYS 020 tracing system calls
+ FORKNOEXEC 040 forked but didn't exec
+ SUPERPRIV 100 used super-user privileges
+ DUMPCORE 200 dumped core
+ SIGNALED 400 killed by a signal
+
+ PROCESS STATE CODES
+ D uninterruptible sleep (usually IO)
+ R runnable (on run queue)
+ S sleeping
+ T traced or stopped
+ Z a defunct ("zombie") process
+
+ For BSD formats and when the "stat" keyword is used,
+ additional letters may be displayed:
+ W has no resident pages
+ < high-priority process
+ N low-priority task
+ L has pages locked into memory (for real-time and custom IO)
+
+<a href="../term_tools/bash/ps_keywords.html">ENVIRONMENT VARIABLES and PERSONALITY</a> (posix,linux,bsd,sun)
+</pre>
+<p>Examples:</p>
+<p>List every process on the system using standard syntax:<br>
+<span class="telety">ps -e</span><br>
+<br>
+List every process on the system using BSD syntax:<br>
+<span class="telety">ps ax</span></p>
+<p>List the top 10 CPU users.<br>
+<span class="telety">ps -e -o pcpu -o pid -o user -o args | sort -k 1 | tail -21r</span><br>
+<br>
+
+List every process except those running as root (real & effective ID)<br>
+<span class="telety">ps -U root -u root -N</span><br>
+<br>
+List every process with a user-defined format:<br>
+<span class="telety">ps -eo pid,tt,user,fname,tmout,f,wchan</span><br>
+<br>
+Odd display with AIX field descriptors:<br>
+<span class="telety">ps -o "%u : %U : %p : %a"</span><br>
+<br>
+Print only the process IDs of syslogd:<br>
+<span class="telety">ps -C syslogd -o pid=</span></p>
+<span class="body"> </span>
+<p>When displaying multiple fields, part of the output may be truncated, to avoid this supply a width to the arguments: </p>
+<pre>ps -e -o user:20,args.</pre>
+<p>Since ps cannot run faster than the system and is run as any other
+ scheduled process, the information it displays can never be exact.</p>
+<p><i>"Life is a process of becoming, a combination of states we have to go through. Where people fail is that they wish to elect a state and remain in it. This is a kind of death" - Ana&iuml;s Nin</i></p>
+<p><b>Related</b>:<a href="for.html"><br>
+ </a><br>
+ <a href="top.html">top</a> - List running processes on the system<br>
+ pstree(1) <br>
+ proc(5)<br>
+Performance monitoring tools: <a href="http://freshmeat.net/projects/atop/">atop</a>, <a href="http://freshmeat.net/projects/bmon/">bmon</a>, <a href="http://dag.wieers.com/home-made/dstat/">dstat</a>, <a href="http://htop.sourceforge.net/">htop</a>,
+<a href="http://gael.roualland.free.fr/ifstat/">ifstat</a>, <a href="http://www.ex-parrot.com/pdw/iftop/">iftop</a>, <a href="http://htop.sourceforge.net/"></a><a href="http://pagesperso-orange.fr/sebastien.godard/">sysstat</a><br>
+Equivalent Windows command:
+<a href="../term_tools/nt/pslist.html">pslist</a> - List detailed information about processes</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/pushd.html b/help/en/bash/pushd.html
new file mode 100644
index 0000000..fdf0f60
--- /dev/null
+++ b/help/en/bash/pushd.html
@@ -0,0 +1,71 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>pushd MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> pushd</h1>
+<p>Save and then change the current directory. With no arguments,
+<code>pushd</code> exchanges the top two directories.</p>
+<pre>SYNTAX
+ pushd [<var>dir</var> | <var>+N</var> | <var>-N</var>] [-n]
+KEY
+ +N Brings the Nth directory (counting from the left of the list
+ printed by dirs, starting with zero) to the top of the list by
+ rotating the stack.
+
+ -N Brings the Nth directory (counting from the right of the list
+ printed by dirs, starting with zero) to the top of the list by
+ rotating the stack.
+
+ -n Suppresses the normal change of directory when adding directories to the
+ stack, so that only the stack is manipulated.
+
+ dir Makes the current working directory be the top of the stack, and then executes
+ the equivalent of `cd dir'. cds to dir.</pre>
+<p><i>#Ah, push it - push it good<br>
+Ah, push it - p-push it real good# - Salt 'N' Pepa</i></p>
+<p><b>Related</b>:<br>
+ <br>
+ <a href="dirs.html">dirs</a> - Display list of remembered directories <br>
+ <a href="popd.html">popd</a> - Restore the previous value of the current directory
+ saved by PUSHD<a href="pushd.html"></a> <br>
+Equivalent Windows command:
+<a href="../term_tools/nt/pushd.html">PUSHD</a> - Save and then change the current directory</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/pwd.html b/help/en/bash/pwd.html
new file mode 100644
index 0000000..8e58874
--- /dev/null
+++ b/help/en/bash/pwd.html
@@ -0,0 +1,61 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>pwd MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> pwd</h1>
+<p>Print Working Directory (shell builtin) </p>
+<pre>Syntax
+ pwd [-LP]
+
+Options
+ -P : The pathname printed will not contain symbolic links.
+ -L : The pathname printed may contain symbolic links</pre>
+<p>The default action is to show the current folder as an absolute
+ path.<br>
+ All components of the path will be actual folder names - none will be symbolic
+ links. </p>
+<p><b>Related </b>:<br>
+ <br>
+ <a href="cd.html">cd</a> - Change Directory<br>
+Equivalent Windows command:
+ <a href="../term_tools/nt/cd.html">CD</a> - Change Directory / describe current folder
+</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/quota.html b/help/en/bash/quota.html
new file mode 100644
index 0000000..5b247df
--- /dev/null
+++ b/help/en/bash/quota.html
@@ -0,0 +1,94 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>quota MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> quota</h1>
+<p>Display disk usage and limits, by default only the user quotas
+are printed.</p>
+<pre>SYNTAX
+ quota [ -guv | q ]
+ quota [ -uv | q ] <em>user</em>
+ quota [ -gv | q ] <em>group</em>
+
+OPTIONS
+ -g Print <b>group</b> quotas for the group of which the user
+ is a member.
+
+ -u Print <b>user</b> quotas (this is the default)
+
+ -v Verbose, will display quotas on filesystems where no
+ storage is allocated.
+
+ -q Print a more terse message, containing only information
+ on filesystems where usage is over quota.</pre>
+<p> Specifying both -g and -u displays both the user quotas and the
+ group quotas (for the user). <br>
+ <br>
+ Only the super-user may use the -u flag and the optional user argument to view
+ the limits of other users. Non- super-users can use the the -g flag and optional
+ group argument to view only the limits of groups of which they are members.
+ <br>
+ <br>
+ The -q flag takes precedence over the -v flag. <br>
+ <br>
+ Quota reports the quotas of all the filesystems listed in /etc/fstab. For filesystems
+ that are NFS-mounted a call to the rpc.rquotad on the server machine is performed
+ to get the information. If quota exits with a non-zero status, one or more filesystems
+ are over quota. <br>
+ <br>
+ <b>Files </b><br>
+ quota.user located at the filesystem root with user quotas <br>
+ quota.group located at the filesystem root with group quotas <br>
+ /etc/fstab to find filesystem names and locations<br>
+ <br>
+ <i>&quot;We don't wake up for less than $10,000 a day&quot; - Linda
+Evangelista </i> </p>
+<p><b>Related</b>:<br>
+ <br>
+ <a href="quotactl.html">quotactl</a> - Manipulate disk quotas <br>
+ fstab<br>
+ edquota<br>
+ <a href="quotacheck.html">quotacheck</a> - Scan a file system for disk usage<br>
+ quotaon<br>
+ repquota<br>
+ <a href="ulimit.html">ulimit</a> - Limit user resources <br>
+Equivalent Windows command: <a href="../term_tools/nt/fsutil.html">FSUTIL</a> quota - File and Volume utilities </p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/quotacheck.html b/help/en/bash/quotacheck.html
new file mode 100644
index 0000000..80bcf10
--- /dev/null
+++ b/help/en/bash/quotacheck.html
@@ -0,0 +1,104 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>quotacheck MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> quotacheck</h1>
+<p>Scan a file system for disk usage</p>
+<pre>Syntax
+ quotacheck [-g] [-u] [-v] -a
+ quotacheck [-g] [-u] [-v] filesys ...</pre>
+<p><span class="body">
+ Quotacheck performs a filesystems scan for usage of files and directories, used
+ by either user or group. The output is the quota file for the corresponding
+ filesystem. By default the names for these files are:<br>
+ - A user scan: quota.user<br>
+ - A group scan: quota.group<br>
+ <br>
+ The resulting file consist of a struct dqblk for each possible id up to the
+ highest existing uid or gid and contains the values for the disk file and block
+ usage and possibly excess time for these values. ( for definitions of struct
+ dqblk see )<br>
+ <br>
+ Quotacheck should be run each time the system boots and mounts non-valid file
+ systems. This is most likely to happen after a system crash.<br>
+ <br>
+ The speed of the scan is proportional to the number of directories/files. </span>
+</p>
+<pre>OPTIONS
+ -v This way the program will give some useful information
+ about what it is doing, plus some fancy
+ stuff.
+
+ -d This means debug. It will result in a lot of information
+ which can be used in debugging the program.
+ The output is very verbose and the scan will not be
+ fast.
+
+ -u This flag tells the program to scan the disk and to
+ count the files and directories used by a certain
+ uid. This is the default action.
+
+ -g This flag forces the program to count the the files
+ and directories used by a certain gid.
+
+ -a Check all of the quotas for the filesystems mentioned
+ in /etc/fstab. Both user and group quotas
+ are checked as indictated by the /etc/fstab
+ options.
+
+ -R When used in conjunction with -a, all filesystems
+ except the root filesystem are checked for quotas.</pre>
+<p> NOTE Quotacheck should only be run as Super User. Non-priviliged
+ users are presumably not allowed to read all the directories on the given file
+ system.<br>
+ <br>
+ <b>Files </b><br>
+quota.user, quota.group, /etc/fstab</p>
+<p><em>&quot;In the factory we make cosmetics. In the store we sell hope&quot;
+ - Charles Revson</em></p>
+<p><b>Related</b>:<br>
+ <br>
+ <a href="quota.html">quota</a> - Display disk usage and limits <br>
+ <a href="quotactl.html">quotactl</a> - Manipulate disk quotas <br>
+ fstab, quotaon, quotaoff, edquota, repquota, fsck, efsck, e2fsck, xfsck<br>
+ <a href="ulimit.html">ulimit</a> - Limit user resources <br>
+Equivalent Windows command: <a href="../term_tools/nt/fsutil.html">FSUTIL</a> quota - File and Volume utilities </p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/quotactl.html b/help/en/bash/quotactl.html
new file mode 100644
index 0000000..2fa07e5
--- /dev/null
+++ b/help/en/bash/quotactl.html
@@ -0,0 +1,112 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>quotactl MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> quotactl</h1>
+<p>Set disk quotas </p>
+<pre>SYNTAX
+ #include &lt;linux/quota.h&gt;
+
+ int quotactl(cmd, special, uid, addr)
+ int cmd;
+ char *special;
+ int uid;
+ caddr_t addr;
+
+DESCRIPTION</pre>
+<p>The quotactl() call manipulates disk quotas. cmd indicates
+a command to be applied to UID id or GID id. To set the type
+of quota use the QCMD(cmd,type) macro. special is a pointer
+to a null-terminated string containing the
+path name of the block special device for the file system
+being manipulated. addr is the address of an optional,
+command specific, data structure which is copied in or out
+of the system. The interpretation of addr is given with
+each command below.</p>
+<pre>
+ Q_QUOTAON Turn on quotas for a file system. addr
+ points to the path name of file containing
+ the quotas for the file system. The quota
+ file must exist; it is normally created
+ with the <a href="quotacheck.html">quotacheck</a> program. This call
+ is restricted to the super-user.
+
+ Q_QUOTAOFF Turn off quotas for a file system. addr
+ and uid are ignored. This call is
+ restricted to the super-user.
+
+ Q_GETQUOTA Get disk quota limits and current usage for
+ user or group id. addr is a pointer to a
+ dqblk structure (defined in
+ &lt;linux/quota.h&gt;). Only the super-user may
+ get the quotas of a user other than himself.
+
+
+ Q_SETQUOTA Set disk quota limits and current usage for
+ user or group id. addr is a pointer to a
+ dqblk structure (defined in
+ &lt;linux/quota.h&gt;). This call is restricted
+ to the super-user.
+
+ Q_SETQLIM Set disk quota limits for user or group id.
+ addr is a pointer to a dqblk structure
+ (defined in &lt;linux/quota.h&gt;). This call is
+ restricted to the super-user.
+
+ Q_SYNC Update the on-disk copy of quota usages for
+ a file system. If special is null then all
+ file systems with active quotas are
+ sync'ed. addr and uid are ignored.
+
+RETURN VALUES
+
+ 0 on success.
+
+ -1 on failure and sets errno to indicate the error.</pre>
+<p> <b>Related</b>:<br>
+ <br>
+ <a href="quota.html">quota</a> - Display disk usage and limits <br>
+ getrlimit - <br>
+ <a href="quotacheck.html">quotacheck</a> - Scan a file system for disk usage<br>
+ quotaon - <br>
+ <a href="ulimit.html">ulimit</a> - Limit user resources <br>
+Equivalent Windows command: <a href="../term_tools/nt/fsutil.html">FSUTIL</a> quota - File and Volume utilities </p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/ram.html b/help/en/bash/ram.html
new file mode 100644
index 0000000..14f3bd1
--- /dev/null
+++ b/help/en/bash/ram.html
@@ -0,0 +1,61 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>ram MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> ram</h1>
+<p>ram disk device</p>
+<p> Ram is a block device to access the ram disk in raw mode.<br>
+It is typically created by:</p>
+<pre> mknod -m 660 /dev/ram b 1 1
+ chown root:disk /dev/ram</pre>
+<p>Files</p>
+<pre> /dev/ram</pre>
+<p><b><i> </i></b><i>&quot;All your life you live so close to truth it becomes a permanent
+ blur in the corner of your eye. And when something nudges it into outline, it's
+ like being ambushed by a grotesque.&quot; Tom
+ Stoppard, Rosencrantz and Guildenstern are Dead </i><br>
+ <br>
+ <b> Related</b>:<br>
+ <br>
+ <a href="mknod.html">mknod</a> - Make block or character special files<br>
+ <a href="chown.html">chown</a> - Change file owner and group<br>
+<a href="mount.html">mount</a> - Mount a file system</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/rcp.html b/help/en/bash/rcp.html
new file mode 100644
index 0000000..e703c19
--- /dev/null
+++ b/help/en/bash/rcp.html
@@ -0,0 +1,70 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>rcp MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> rcp</h1>
+<p>Remote Copy - move files between machines. <br>
+ Each file or directory is either a remote filename of the form rname@rhost:path
+or a local filename.</p>
+<pre>Syntax
+ rcp [<i>options</i>] <i>file1 file2</i>
+
+ rcp [<i>options</i>] <i>file</i> ... <i>directory</i>
+
+Options
+ -k Attempt to get tickets for remote host; query krb_realmofhost to determine realm.
+
+ -p Preserve modification times and modes of the source files.
+
+ -r If any of the source files are directories, rcp copies each subtree rooted at that name.
+ The destination must be a directory.
+
+ -x Turns on DES encryption for all data passed by rcp.</pre>
+<p><i>&quot;Worms are now able to propagate much faster than humans
+ can react to install patches. In short, the patch-and-pray model can't prevent
+ massive-scale attacks from succeeding&quot; - icir.org
+ (2002) </i></p>
+<p><b>Related</b>:<br>
+ <br>
+ <a href="rsync.html">rsync</a> - Remote file copy (Synchronize file trees) <br>
+Equivalent Windows command:
+<a href="../term_tools/nt/robocopy.html">ROBOCOPY</a> - Robust File and Folder Copy</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/read.html b/help/en/bash/read.html
new file mode 100644
index 0000000..3f4f7ef
--- /dev/null
+++ b/help/en/bash/read.html
@@ -0,0 +1,119 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>read MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> read</h1>
+<p><span class="body">Read a line from standard input</span></p>
+<pre>Syntax
+ read [-ers] [-a <var>aname</var>] [-p <var>prompt</var>] [-t <var>timeout</var>]
+ [-n <var>nchars</var>] [-d <var>delim</var>] [<var>name</var>...]
+
+Options
+
+ -a <i>aname</i>
+ The words are assigned to sequential indices of the array variable aname,
+ starting at 0. All elements are removed from aname before the assignment.
+ Other name arguments are ignored.
+
+ -d <i>delim</i>
+ The first character of delim is used to terminate the input line,
+ rather than newline.
+
+ -e
+ If the standard input is coming from a terminal, Readline is used
+ to obtain the line.
+
+ -n <i>nchars</i>
+ read returns after reading nchars characters rather
+ than waiting for a complete line of input.
+
+ -p <i>prompt</i>
+ Display prompt, without a trailing newline, before attempting
+ to read any input. The prompt is displayed only if input is coming from a
+ terminal.
+
+ -r
+ If this option is given, backslash does not act as an escape character.
+ The backslash is considered to be part of the line. In particular, a backslash-newline
+ pair may not be used as a line continuation.
+
+ -s
+ Silent mode. If input is coming from a terminal, characters are not echoed.
+
+ -t <i>timeout</i>
+ Cause read to time out and return failure if a complete line
+ of input is not read within timeout seconds. This option has no
+ effect if read is not reading input from the terminal or a pipe.</pre>
+
+
+<p>This is a BASH shell builtin.<br>
+ <br>
+ One line is read from the standard input, and the first word is assigned to
+ the first <var>name</var>, the second word to the second <var>name</var>, and
+ so on, with leftover words and their intervening separators assigned to the
+ last <var>name</var>. <br>
+ <br>
+ If there are fewer words read from the standard input than names, the remaining
+ names are assigned empty values. <br>
+ <br>
+ The characters in the value of the <code>IFS</code> variable are used to split
+ the line into words. <br>
+ <br>
+ The backslash character <samp>`\'</samp> may be used to remove any special meaning
+ for the next character read and for line continuation. <br>
+ <br>
+ If no names are supplied, the line read is assigned to the variable <code>REPLY</code>.
+ The return code is zero, unless end-of-file is encountered or <code>read</code>
+ times out. </p>
+<p><b>Examples</b></p>
+<p>#!/bin/bash<br>
+ read var_year <br>
+ echo "The year is: $var_year"</p>
+<p>echo -n "Enter your name and press [ENTER]: " <br>
+ read var_name<br>
+ echo "Your name is: $var_name"</p>
+<p><em>"Formal education will make you a living; self-education will make you a fortune" - Jim Rohn</em></p>
+<p><b>Related</b>:<br>
+ <a href="select.html"><br>
+ select</a> - Accept keyboard input<br>
+Equivalent Windows commands: <a href="../term_tools/nt/set.html">
+ SET /P</a> - Prompt for user input</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/readonly.html b/help/en/bash/readonly.html
new file mode 100644
index 0000000..5c655be
--- /dev/null
+++ b/help/en/bash/readonly.html
@@ -0,0 +1,76 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>readonly MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> readonly</h1>
+<span class="body">Mark variables/functions as readonly. </span><br>
+<pre>Syntax
+ readonly [-apf] [<em>name</em>] ...
+
+Options
+ -f Each name refers to a shell function
+ -a Each name refers to an array variable
+ -p Print a list of all readonly names (This is the default)</pre>
+<p> The values of these names may not be changed by subsequent assignment.<br>
+ <br>
+ The `-p' option causes output to be displayed in a format that may be reused
+ as input. <br>
+ <br>
+ The return status is zero unless an invalid option is supplied, one of the name
+ arguments is not a valid shell variable or function name, or the `-f' option
+ is supplied with a name that is not a shell function. </p>
+<p>readonly is a BOURNE shell command and a POSIX `special' builtin.<br>
+ <br>
+ <i>&quot;The stupid neither forgive nor forget, the naive forgive and forget,
+ the wise forgive but do not forget&quot; - Thomas
+ Szasz (The second sin)</i> </p>
+<p><b>Related</b>:<br>
+ <br>
+ <a href="chmod.html">chmod</a> - Change access permissions<br>
+ <a href="env.html">env</a> - Display, set, or remove environment variables <br>
+ <a href="export.html"> export</a> - Set an environment variable <br>
+ <a href="function.html">function</a> - Define Function Macros <br>
+ <a href="hostname.html">hostname</a> - Print or set system name<br>
+ <a href="local.html">local</a> - Create variables<br>
+ printenv - Print environment variables <br>
+ <a href="shift.html">shift</a> - Shift positional parameters <br>
+Equivalent Powershell command: <a href="../term_tools/ps/set-variable.html">Set-Variable</a> -option:ReadOnly </p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/rem.html b/help/en/bash/rem.html
new file mode 100644
index 0000000..d7f6e1a
--- /dev/null
+++ b/help/en/bash/rem.html
@@ -0,0 +1,61 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>comments MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> #</h1>
+<p>A comment or remark is indicated by starting the line with the # character</p>
+<pre> # This is a description
+ # Another remark
+ command
+ # Another remark</pre>
+<p><b>Related commands</b>:<br>
+ <br>
+ <code>: (a colon)</code> </p>
+<dl>
+ <dd>
+<pre>: [<var>arguments</var>]</pre>
+<dd>
+<p>Do nothing beyond expanding <var>arguments</var> and performing redirections.
+ The return status is zero.
+</p>
+</dl>
+<p> <b>Equivalent Windows command</b>: <a href="../term_tools/nt/rem.html">REM</a> - comment </p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/rename.html b/help/en/bash/rename.html
new file mode 100644
index 0000000..f0ce1a0
--- /dev/null
+++ b/help/en/bash/rename.html
@@ -0,0 +1,65 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>rename MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> rename (linux only, not ubuntu) </h1>
+<p>Rename files. </p>
+<pre>Syntax
+ rename <i>from to file...</i></pre>
+<p>rename will rename the specified files by replacing the first occurrence of <i>from</i> in their name by <i>to</i>.</p>
+<p><b>Examples</b></p>
+<p>Given the files foo1, ..., foo9, foo10, ..., foo278, the commands</p>
+<p class="code"> $ rename foo foo0 foo?<br>
+$ rename foo foo0 foo??</p>
+<p>will turn them into foo001, ..., foo009, foo010, ..., foo278.</p>
+<p>Fix the extension of your .htm files so they become .html :</p>
+<p class="code"> $ rename .htm .html *.htm</p>
+<p>Rename all files (<span class="code">*</span>) to be lowercase:</p>
+<p class="code">$ rename 'y/A-Z/a-z/' *</p>
+<p>An alternative is to use a <a href="for.html">for</a> loop, for example to change a bunch of .txt files to have the extension .html </p>
+<p class="code">$ for i in *.txt; do mv &quot;$i&quot; &quot;`<a href="basename.html">basename</a> $i .txt`.html&quot;; done </p>
+<p> <i>&ldquo;Never doubt that a small group of thoughtful, committed citizens can change the world; indeed, it is the only thing that ever has&rdquo; - Margaret Mead</i><br>
+ <b><br>
+ Related</b>:<br>
+ <br>
+ <a href="mv.html">mv</a> - Move or rename files or directories.<br>
+Equivalent Windows command: <a href="../term_tools/nt/ren.html">REN</a> - Rename files. </p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/return.html b/help/en/bash/return.html
new file mode 100644
index 0000000..013ab9a
--- /dev/null
+++ b/help/en/bash/return.html
@@ -0,0 +1,64 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>return MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> return</h1>
+<span class="body">Cause a shell function to exit with the return value n. </span><br>
+<pre>Syntax
+ return [<em>n</em>]
+
+Options
+ <em>n</em> Return value i.e. an errorlevel</pre>
+<p> If n is not supplied, the return value is the exit status of the last command
+ executed in the function. This may also be used to terminate execution of a
+ script being executed with the . (or source) builtin, returning either n or
+ the exit status of the last command executed within the script as the exit status
+ of the script. <br>
+ <br>
+ The return status is false if return is used outside a function and not during
+ the execution of a script by . or source. </p>
+<p>return is a BOURNE shell command and a POSIX `special' builtin.</p>
+<p><b>Related</b>:<br>
+ <br>
+ <a href="source.html">. period</a> - Run commands from a file<br>
+Equivalent Windows command: <a href="../term_tools/nt/set.html">
+</a>EXIT - Exit a windows <a href="../term_tools/nt/cmd.html">CMD</a> shell</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/rev.html b/help/en/bash/rev.html
new file mode 100644
index 0000000..1fcd00b
--- /dev/null
+++ b/help/en/bash/rev.html
@@ -0,0 +1,65 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>rev MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> rev</h1>
+<p>Reverse lines of a file.</p>
+<pre>Syntax:
+
+ rev [<i>file</i>]</pre>
+<p>The rev utility copies the specified files to the standard output, reversing the order of characters in every line.</p>
+<p>If no <i>file </i>is specified, the standard input is read (type CTRL-D to end). </p>
+<p>The most common use of rev is to reverse the lines, apply a <a href="sort.html">sort</a> to the result and then pipe through rev a second time to restore the original.</p>
+<p><b>Example</b></p>
+<p>Given the input of:</p>
+<p> The quick brown fox <br>
+jumps over the lazy dog</p>
+<p>Rev will output:</p>
+<p>xof mworb kciuq ehT <br>
+god yzal eht revo spmuj </p>
+<p><i>&quot;The weirder you're going to behave, the more normal you should
+look. It works in reverse, too. When I see a kid with three or four
+rings in his nose, I know there is absolutely nothing extraordinary
+about that person&quot;
+- P. J. O'Rourke </i></p>
+<p><b>Related</b>:</p>
+<p><a href="sort.html">sort</a> - Sort text files (sort - k will sort on a key) </p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/rm.html b/help/en/bash/rm.html
new file mode 100644
index 0000000..084b546
--- /dev/null
+++ b/help/en/bash/rm.html
@@ -0,0 +1,91 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>rm MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> rm</h1>
+<p>Remove files (delete/unlink) </p>
+<pre>Syntax
+ rm [<em>options</em>]... <em>file</em>...
+
+Options
+ -d, --directory unlink directory, even if non-empty (super-user only)
+
+ -f, --force ignore nonexistent files, never prompt
+
+ -i, --interactive prompt before any removal
+
+ -r, -R, --recursive remove the contents of directories recursively
+
+ -v, --verbose explain what is being done
+
+ --help display this help and exit
+
+ --version output version information and exit</pre>
+<p>To remove a file you must have write permission on the file and
+ the folder where it is stored. <br>
+ <br>
+ rm -rf will recursively remove folders and their contents <br>
+ <br>
+ The OWNER of a file does not need rw permissions in order to rm it. </p>
+<p><b>Undeletable files</b></p>
+<p> The rm command
+accepts the `--' option which will cause it to stop processing flag
+options from that point forward. This allows the removal of file names that
+begin with a dash (`-'). <br>
+<span class="telety">rm -- -filename</span><br>
+Alternatively use an absolute or relative path reference. <br>
+<span class="telety">rm /home/user/-filename<br>
+rm ./-filename </span></p>
+<p>To delete a file with non-printable characters in the name: `bad file name' Use the shell wildcard &quot;?&quot; for each character</p>
+<p class="telety">rm bad?file?name</p>
+<p>Older file systems such as ext2fs, perform badly for massive bulk deletes. The newer ext3fs doesn't have this performance problem.<br>
+To remove a very large number of files from a directory it can be quicker to rm them one at a time in a loop:</p>
+<p class="telety">find my_dir -type f | while read -r; do rm -v &quot;$REPLY&quot;; sleep 0.2; done</p>
+<p><i>"It devoured my paper, it was a really good paper" - <a href="http://en.wikipedia.org/wiki/Ellen_Feiss">Ellen Feiss</a></i></p>
+<p><b>Related</b>:<br>
+ <br>
+ <a href="ls.html">ls</a> - List information about files<br>
+ <a href="rmdir.html">rmdir</a> - Remove folder(s) <br>
+Equivalent Windows command:
+ <a href="../term_tools/nt/del.html">DEL</a> - Delete one or more files</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --><p align="center"><br>
+</p>
+</body>
+</html>
diff --git a/help/en/bash/rmdir.html b/help/en/bash/rmdir.html
new file mode 100644
index 0000000..fd999e8
--- /dev/null
+++ b/help/en/bash/rmdir.html
@@ -0,0 +1,71 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>rmdir MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> rmdir</h1>
+<p>Remove directory, this command will only work if the folders are empty.</p>
+<pre>Syntax
+ rmdir [<em>options</em>]... <i>folder(s)</i>...
+
+Options
+ --ignore-fail-on-non-empty
+ Ignore each failure that is solely because the
+ directory is non-empty.
+
+ -p, --parents Remove explicit parent directories if being emptied
+
+ --verbose Output a diagnostic for every directory processed
+
+ --help Display help and exit
+
+ --version Output version information and exit</pre>
+<p><b>Example</b></p>
+<p class="telety">$ rmdir myfolder </p>
+<p>Before removing directories with a wildcard, it's wise to list them first:</p>
+<p class="telety">$ ls -d britney*/</p>
+<p><i>"</i><i>It devoured my paper, it was a really good paper" - <a href="http://en.wikipedia.org/wiki/Ellen_Feiss">Ellen Feiss</a></i></p>
+<p><b>Related</b>:<br>
+ <br>
+ <a href="rm.html">rm</a> - Remove files (rm -rf will recursively remove folders
+ and their contents)<br>
+<a href="ls.html">ls -al</a> - List information about files<br>
+Equivalent Windows commands: <a href="../term_tools/nt/rd.html">RD</a> - Delete folders or entire folder trees (DELTREE)</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/rsync.html b/help/en/bash/rsync.html
new file mode 100644
index 0000000..4579acc
--- /dev/null
+++ b/help/en/bash/rsync.html
@@ -0,0 +1,484 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>rsync MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> rsync (<a href="http://rsync.samba.org/">download</a>) </h1>
+<p>Remote file copy - Synchronize file trees across local disks,
+directories or across a network.</p>
+<pre>Syntax
+
+# Local file to Local file
+ rsync [<i>option</i>]... <em>Source</em> [<em>Source</em>]... <em>Dest</em>
+
+# Local to Remote
+ rsync [<i>option</i>]... <em>Source</em> [<em>Source</em>]... [<em>user</em>@]<em>host</em>:<em>Dest</em>
+
+ rsync [<i>option</i>]... <em>Source</em> [<em>Source</em>]... [<em>user</em>@]<em>host</em>::<em>Dest</em>
+
+# Remote to Local
+ rsync [<i>option</i>]... [<em>user</em>@]<em>host</em>::<em>Source</em> [<em>Dest</em>]
+
+ rsync [<i>option</i>]... [<em>user</em>@]<em>host</em>:<em>Source</em><em>Dest</em>
+
+ rsync [<i>option</i>]... rsync://[<em>user</em>@]<em>host</em>[:PORT]/<em>Source</em> [<em>Dest</em>]</pre>
+<p><span class="body"> rsync is a program that behaves in much the same way that <a href="rcp.html">rcp</a> does, but has
+ many more options and uses the rsync remote-update protocol to greatly
+ speed up file transfers when the destination file already exists.<br>
+ <br>
+ The rsync remote-update protocol allows rsync to transfer just the
+ differences between two sets of files across the network link, using
+ an efficient checksum-search algorithm described in the technical report
+ that accompanies this package.<br>
+ <br>
+ Some of the additional features of rsync are:<br>
+ <br>
+ # support for copying links, devices, owners, groups and permissions<br>
+ # exclude and exclude-from options similar to GNU tar<br>
+ # a CVS exclude mode for ignoring the same files that CVS would ignore<br>
+ # can use any transparent remote shell, including rsh or ssh<br>
+ # does not require root privileges<br>
+ # pipelining of file transfers to minimize latency costs<br>
+# support for anonymous or authenticated rsync servers (ideal for mirroring)</span></p>
+<p><span class="body"> <b>General</b><br>
+ <br>
+ There are six different ways of using rsync. They are:<br>
+ <br>
+ . Copy <strong>local</strong> files. This is invoked when neither source nor
+ destination path contains a : separator<br>
+ <br>
+ : Copying from the <strong>local</strong> machine to a <strong>remote</strong> machine using a remote
+ shell program as the transport (such as rsh or ssh).
+ This is invoked when the destination path contains a single : separator.<br>
+ <br>
+ : Copy from a <strong>remote</strong> machine to the <strong>local</strong> machine using a remote
+ shell program. This is invoked when the source contains a : separator.<br>
+ <br>
+ :: Copy from a <strong>remote rsync</strong> server to the <strong>local</strong> machine.
+ This is invoked when the source path contains a :: separator or a rsync:// URL.<br>
+ <br>
+ :: Copy from the <strong>local</strong> machine to a <strong>remote rsync</strong> server.
+ This is invoked when the destination path contains a :: separator.<br>
+ <br>
+ # <b>L</b><strong>ist</strong> files on a remote machine. This is done the same way as rsync
+ transfers except that you leave off the local destination.<br>
+ <br>
+ Note that in all cases (other than listing) at least one of the source and
+ destination paths must be local.</span></p>
+<pre><b>Usage</b>
+
+You use rsync in the same way you use rcp.
+You must specify a source and a destination, one of which may be remote.
+
+Perhaps the best way to explain the syntax is some examples:
+
+ rsync *.c foo:src/
+
+this would transfer all files matching the pattern *.c from the current directory
+to the directory src on the machine foo.
+If any of the files already exist on the remote system then the
+rsync remote-update protocol is used to update the file by sending only the differences.
+See the tech report for details.
+
+ rsync -avz foo:src/bar /data/tmp
+
+this would recursively transfer all files from the directory src/bar
+on the machine foo into the /data/tmp/bar directory on the local machine.
+The files are transferred in "archive" mode, which ensures that symbolic links,
+devices, attributes, permissions, ownerships etc are preserved in the transfer.
+Additionally, compression will be used to reduce the size of data portions of the transfer.
+
+ rsync -avz foo:src/bar/ /data/tmp
+
+a trailing slash on the source changes this behavior to transfer all files
+from the directory src/bar on the machine foo into the /data/tmp/.
+A trailing / on a source name means "copy the contents of this directory".
+Without a trailing slash it means "copy the directory".
+This difference becomes particularly important when using the --delete option.
+
+You can also use rsync in local-only mode, where both the source and destination
+don't have a ':' in the name.
+In this case it behaves like an improved copy command.
+
+ rsync somehost.mydomain.com::
+
+this would list all the anonymous rsync modules available on
+the host somehost.mydomain.com. (See the following section for more details.)
+
+<b>CONNECTING TO AN RSYNC SERVER</b>
+
+It is also possible to use rsync without using rsh or ssh as the transport.
+In this case you will connect to a remote rsync server running on TCP port 873.
+
+You may establish the connection via a web proxy by setting the environment variable
+ RSYNC_PROXY to a hostname:port pair pointing to your web proxy.
+Note that your web proxy's configuration must allow proxying to port 873.
+
+Using rsync in this way is the same as using it with rsh or ssh except that:
+
+# you use a double colon :: instead of a single colon to separate the hostname
+from the path.
+
+# the remote server may print a message of the day when you connect.
+
+# if you specify no path name on the remote server then the list of accessible
+paths on the server will be shown.
+
+# if you specify no local destination then a listing of the specified files on
+the remote server is provided.
+
+Some paths on the remote server may require authentication.
+If so then you will receive a password prompt when you connect.
+You can avoid the password prompt by setting the environment variable
+RSYNC_PASSWORD to the password you want to use or using the --password-file option.
+This may be useful when scripting rsync.
+
+WARNING: On some systems environment variables are visible to all users.
+On those systems using --password-file is recommended.
+
+<b>RUNNING AN RSYNC SERVER</b>
+
+An rsync server is configured using a config file which by default is
+called /etc/rsyncd.conf. Please see the rsyncd.conf(5) man page for more information.
+
+<b>EXAMPLES</b>
+
+To Backup the home directory using a cron job:
+
+ rsync -Cavz . ss64:backup
+
+Run the above over a PPP link to a duplicate directory on machine "ss64".
+
+To synchronize samba source trees use the following Makefile targets:
+
+ get:
+ rsync -avuzb --exclude '*~' samba:samba/ .
+
+ put:
+ rsync -Cavuzb . samba:samba/
+
+ sync: get put
+
+this allows me to sync with a CVS directory at the other end of the link.
+I then do cvs operations on the remote machine, which saves a lot of time
+as the remote cvs protocol isn't very efficient.
+
+I mirror a directory between my "old" and "new" ftp sites with the command
+
+ rsync -az -e ssh --delete ~ftp/pub/samba/ nimbus:"~ftp/pub/tridge/samba"
+
+this is launched from cron every few hours.
+
+<b>OPTIONS SUMMARY</b>
+
+Here is a short summary of the options available in rsync.
+Please refer to the <a href="../term_tools/bash/rsync_options.html">FULL List of OPTIONS</a> for a complete description.
+
+<i>What to copy:</i>
+ -r, --recursive recurse into directories
+ -R, --relative use relative path names
+ --exclude=PATTERN exclude files matching PATTERN
+ --exclude-from=FILE exclude patterns listed in FILE
+ -I, --ignore-times don't exclude files that match length and time
+ --size-only only use file size when determining if a file should be transferred
+ --modify-window=NUM Timestamp window (seconds) for file match (default=0)
+ --include=PATTERN don't exclude files matching PATTERN
+ --include-from=FILE don't exclude patterns listed in FILE
+
+<i>How to copy it:
+</i> -n, --dry-run show what would have been transferred
+ -l, --links copy symlinks as symlinks
+ -L, --copy-links copy the referent of symlinks
+ --copy-unsafe-links copy links outside the source tree
+ --safe-links ignore links outside the destination tree
+ -H, --hard-links preserve hard links
+ -D, --devices preserve devices (root only)
+ -g, --group preserve group
+ -o, --owner preserve owner (root only)
+ -p, --perms preserve permissions
+ -t, --times preserve times
+ -S, --sparse handle sparse files efficiently
+ -x, --one-file-system don't cross filesystem boundaries
+ -B, --block-size=SIZE checksum blocking size (default 700)
+ -e, --rsh=COMMAND specify rsh replacement
+ --rsync-path=PATH specify path to rsync on the remote machine
+ --numeric-ids don't map uid/gid values by user/group name
+ --timeout=TIME set IO timeout in seconds
+ -W, --whole-file copy whole files, no incremental checks
+
+<i>Destination options:
+</i> -a, --archive archive mode
+ -b, --backup make backups (default ~ suffix)
+ --backup-dir make backups into this directory
+ --suffix=SUFFIX override backup suffix
+ -z, --compress compress file data
+ -c, --checksum always checksum
+ -C, --cvs-exclude auto ignore files in the same way CVS does
+ --existing only update files that already exist
+ --delete delete files that don't exist on the sending side
+ --delete-excluded also delete excluded files on the receiving side
+ --delete-after delete after transferring, not before
+ --force force deletion of directories even if not empty
+ --ignore-errors delete even if there are IO errors
+ --max-delete=NUM don't delete more than NUM files
+ --log-format=FORMAT log file transfers using specified format
+ --partial keep partially transferred files
+ --progress show progress during transfer
+ -P equivalent to --partial --progress
+ --stats give some file transfer stats
+ -T --temp-dir=DIR create temporary files in directory DIR
+ --compare-dest=DIR also compare destination files relative to DIR
+ -u, --update update only (don't overwrite newer files)
+
+<i>Misc Others:
+</i> --address=ADDRESS bind to the specified address
+ --blocking-io use blocking IO for the remote shell
+ --bwlimit=KBPS limit I/O bandwidth, KBytes per second
+ --config=FILE specify alternate rsyncd.conf file
+ --daemon run as a rsync daemon
+ --no-detach do not detach from the parent
+ --password-file=FILE get password from FILE
+ --port=PORT specify alternate rsyncd port number
+ -f, --read-batch=FILE read batch file
+ -F, --write-batch write batch file
+ --version print version number
+ -v, --verbose increase verbosity
+ -q, --quiet decrease verbosity
+ -h, --help show this help screen
+
+Tips on how to use each of the options above can be found in the
+<a href="../term_tools/bash/rsync_options.html">FULL List of OPTIONS and Exit Values</a>
+
+<b><a name="exclude"></a>EXCLUDE PATTERNS</b>
+
+The exclude and include patterns specified to rsync allow for flexible selection of
+which files to transfer and which files to skip.
+
+rsync builds an ordered list of include/exclude options as specified on the
+command line. When a filename is encountered, rsync checks the name against each
+ exclude/include pattern in turn. The first matching pattern is acted on.
+If it is an exclude pattern, then that file is skipped.
+If it is an include pattern then that filename is not skipped.
+If no matching include/exclude pattern is found then the filename is not skipped.
+
+Note that when used with -r (which is implied by -a), every subcomponent of
+every path is visited from top down, so include/exclude patterns get applied
+recursively to each subcomponent.
+
+Note also that the --include and --exclude options take one pattern each.
+To add multiple patterns use the --include-from and --exclude-from options
+ or multiple --include and --exclude options.
+
+The patterns can take several forms. The rules are:
+
+# if the pattern starts with a / then it is matched against the start of the filename,
+ otherwise it is matched against the end of the filename.
+ Thus "/foo" would match a file called "foo" at the base of the tree.
+ On the other hand, "foo" would match any file called "foo" anywhere in the tree
+ because the algorithm is applied recursively from top down; it behaves as if each
+ path component gets a turn at being the end of the file name.
+
+# if the pattern ends with a / then it will only match a directory, not a file,
+ link or device.
+
+# if the pattern contains a wildcard character from the set *?[ then expression
+ matching is applied using the shell filename matching rules.
+ Otherwise a simple string match is used.
+
+# if the pattern includes a double asterisk "**" then all wildcards in the pattern
+ will match slashes, otherwise they will stop at slashes.
+
+# if the pattern contains a / (not counting a trailing /) then it is matched
+ against the full filename, including any leading directory.
+ If the pattern doesn't contain a / then it is matched only against the final
+ component of the filename. Again, remember that the algorithm is applied recursively
+ so "full filename" can actually be any portion of a path.
+
+# if the pattern starts with "+ " (a plus followed by a space) then it is always
+ considered an include pattern, even if specified as part of an exclude option.
+ The "+ " part is discarded before matching.
+
+# if the pattern starts with "- " (a minus followed by a space) then it is always
+ considered an exclude pattern, even if specified as part of an include option.
+ The "- " part is discarded before matching.
+
+# if the pattern is a single exclamation mark ! then the current include/exclude list
+ is reset, removing all previously defined patterns.
+
+The +/- rules are most useful in exclude lists, allowing you to have a single
+ exclude list that contains both include and exclude options.
+
+If you end an exclude list with --exclude '*', note that since the algorithm is applied recursively that unless you explicitly include parent directories of files you want to include then the algorithm will stop at the parent directories and never see the files below them. To include all directories, use --include '*/' before the --exclude '*'.
+
+Here are some exclude/include examples:
+
+# --exclude "*.o" would exclude all filenames matching *.o
+# --exclude "/foo" would exclude a file in the base directory called foo
+# --exclude "foo/" would exclude any directory called foo.
+# --exclude "/foo/*/bar" would exclude any file called bar two levels below a
+ base directory called foo.
+# --exclude "/foo/**/bar" would exclude any file called bar two or more levels below
+ a base directory called foo.
+# --include "*/" --include "*.c" --exclude "*"
+ would include all directories
+ and C source files
+# --include "foo/" --include "foo/bar.c" --exclude "*"
+ would include only foo/bar.c (the foo/ directory must be
+ explicitly included or it would be excluded by the "*")
+
+<b>BATCH MODE</b>
+
+The following call generates 4 files that encapsulate the information for
+synchronizing the contents of target_dir with the updates found in src_dir
+
+$ rsync -F [other rsync options here] \
+/somewhere/src_dir /somewhere/target_dir
+
+The generated files are labeled with a common timestamp:
+
+# rsync_argvs.<timestamp> command-line arguments
+# rsync_flist.<timestamp> rsync internal file metadata
+# rsync_csums.<timestamp> rsync checksums
+# rsync_delta.<timestamp> data blocks for file update & change
+
+See http://www.ils.unc.edu/i2dsi/unc_rsync+.html for papers and technical reports.
+
+<b>SYMBOLIC LINKS</b>
+
+Three basic behaviours are possible when rsync encounters a symbolic link in
+the source directory.
+
+By default, symbolic links are not transferred at all.
+A message "skipping non-regular" file is emitted for any symlinks that exist.
+
+If --links is specified, then symlinks are recreated with the same target
+on the destination. Note that --archive implies --links.
+
+If --copy-links is specified, then symlinks are "collapsed" by copying their referent,
+rather than the symlink.
+
+rsync also distinguishes "safe" and "unsafe" symbolic links.
+An example where this might be used is a web site mirror that wishes ensure the
+rsync module they copy does not include symbolic links to /etc/passwd in the public
+section of the site. Using --copy-unsafe-links will cause any links to be copied
+as the file they point to on the destination.
+Using --safe-links will cause unsafe links to be ommitted altogether.
+
+<b>DIAGNOSTICS</b>
+
+rsync occasionally produces error messages that may seem a little cryptic.
+The one that seems to cause the most confusion is
+"protocol version mismatch - is your shell clean?".
+
+This message is usually caused by your startup scripts or remote shell facility
+producing unwanted garbage on the stream that rsync is using for its transport.
+The way to diagnose this problem is to run your remote shell like this:
+
+ rsh remotehost /bin/true > out.dat
+
+then look at out.dat. If everything is working correctly then out.dat should be
+a zero length file. If you are getting the above error from rsync then you will
+probably find that out.dat contains some text or data.
+Look at the contents and try to work out what is producing it.
+The most common cause is incorrectly configured shell startup scripts
+ (such as .cshrc or .profile) that contain output statements for non-interactive logins.
+
+If you are having trouble debugging include and exclude patterns,
+then try specifying the -vv option.
+At this level of verbosity rsync will show why each individual file is included or
+excluded.
+
+<b>SETUP</b>
+See the file README for installation instructions.
+
+Once installed you can use rsync to any machine that you can use rsh to.
+rsync uses rsh for its communications, unless both the source and destination are local.
+
+You can also specify an alternative to rsh, either by using the -e command line
+option, or by setting the RSYNC_RSH environment variable.
+
+One common substitute is to use ssh, which offers a high degree of security.
+
+Note that rsync must be installed on both the source and destination machines.
+
+<b>ENVIRONMENT VARIABLES</b>
+
+CVSIGNORE
+ The CVSIGNORE environment variable supplements any ignore patterns in .cvsignore files.
+ See the --cvs-exclude option for more details.
+
+RSYNC_RSH
+ The RSYNC_RSH environment variable allows you to override the default shell used as
+ the transport for rsync. This can be used instead of the -e option.
+
+RSYNC_PROXY
+ The RSYNC_PROXY environment variable allows you to redirect your rsync client to
+ use a web proxy when connecting to a rsync daemon.
+ You should set RSYNC_PROXY to a hostname:port pair.
+
+RSYNC_PASSWORD
+ Setting RSYNC_PASSWORD to the required password allows you to run authenticated
+ rsync connections to a rsync daemon without user intervention.
+ Note that this does not supply a password to a shell transport such as ssh.
+
+USER or LOGNAME
+ The USER or LOGNAME environment variables are used to determine the default
+ username sent to a rsync server.
+
+HOME
+ The HOME environment variable is used to find the user's default .cvsignore file.
+
+<b>FILES</b>
+
+/etc/rsyncd.conf
+</pre>
+<p><b>Related:</b><br>
+ <br>
+<a href="http://www.opbyte.it/grsync/">Grsync</a> - GUI for rsync (<a href="http://ubuntuforums.org/showthread.php?t=795668">how to install</a>) <br>rsyncd.conf(5)<br>
+<a href="http://rsnapshot.org/">rsnapshot</a> - Save multiple backups with rsync <br>
+ <a href="rcp.html">rcp</a> - Copy files between two machines.<br>
+ <a href="cp.html">cp</a> - Copy one or more files to another location <br>
+ <a href="install.html">install</a> - Copy files and set attributes<br>
+ <a href="dd.html">dd</a> - Data Dump - convert and copy a file (use for RAW
+ storage) <br>
+ remsync - Synchronize remote files via email <br>
+Equivalent Windows command:
+<a href="../term_tools/nt/robocopy.html">ROBOCOPY</a> - Robust File and Folder Copy </p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/scp.html b/help/en/bash/scp.html
new file mode 100644
index 0000000..8b0c18e
--- /dev/null
+++ b/help/en/bash/scp.html
@@ -0,0 +1,164 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>scp MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1>scp</h1>
+<p>Secure copy (remote file copy program) </p>
+<pre>Syntax
+ scp [-1246BCpqrv] [-c <i>cipher</i>] [-F <i>ssh_config</i>] [-i <i>identity_file</i>]
+ [-l <i>limit</i>] [-o <i>ssh_option</i>] [-P <i>port</i>] [-S <i>program</i>]
+ <b>[</b> [<i>user</i>@]<i>host1</i>:<b>]</b><i>file1</i> [...] <b>[</b> [<i>user</i>@]<i>host2</i>:<b>]</b><i>file2</i></pre>
+<p>scp copies files between hosts on a network. It uses ssh(1) for data transfer, and uses the same authentication and provides the same security as ssh(1). Unlike <a href="rcp.html">rcp</a>, scp will ask for passwords or passphrases if they are needed for authentication.</p>
+<p>Any file name may contain a host and user specification to indicate that the file is to be copied to/from that host. <br>
+Copies between two remote hosts are permitted.</p>
+<pre><i>Options</i>:
+ -1' Force scp to use protocol 1.
+
+ -2' Force scp to use protocol 2.
+
+ -4' Force scp to use IPv4 addresses only.
+
+ -6' Force scp to use IPv6 addresses only.
+
+ -B' Select batch mode (dont ask for passwords or passphrases).
+
+ -C' Compression, passes the -C flag to ssh(1) to enable compression.
+
+ -c <i>cipher</i>
+ Select the cipher to use for encrypting the data transfer.
+ This option is directly passed to ssh(1).
+
+ -F <i>ssh_config</i>
+ Specifies an alternative per-user configuration file for ssh.
+ This option is directly passed to ssh(1).
+
+ -i <i>identity_file</i>
+ Select the file from which the identity (private key) for RSA
+ authentication is read. This option is directly passed to ssh(1).
+
+ -l <i>limit</i>
+ Limit the used bandwidth, specified in Kbit/s.
+
+ -o <i>ssh_option</i>
+ Can be used to pass options to ssh in the format used in ssh_config(5).
+ This is useful for specifying options for which there is no separate
+ scp command-line flag.
+
+ For full details of the options listed below, and their possible values,
+ see ssh_config(5).
+
+ AddressFamily
+ BatchMode
+ BindAddress
+ ChallengeResponseAuthentication
+ CheckHostIP
+ Cipher
+ Ciphers
+ Compression
+ CompressionLevel
+ ConnectionAttempts
+ ConnectTimeout
+ ControlMaster
+ ControlPath
+ GlobalKnownHostsFile
+ GSSAPIAuthentication
+ GSSAPIDelegateCredentials
+ HashKnownHosts
+ Host'
+ HostbasedAuthentication
+ HostKeyAlgorithms
+ HostKeyAlias
+ HostName
+ IdentityFile
+ IdentitiesOnly
+ KbdInteractiveDevices
+ LogLevel
+ MACs'
+ NoHostAuthenticationForLocalhost
+ NumberOfPasswordPrompts
+ PasswordAuthentication
+ Port'
+ PreferredAuthentications
+ Protocol
+ ProxyCommand
+ PubkeyAuthentication
+ RekeyLimit
+ RhostsRSAAuthentication
+ RSAAuthentication
+ SendEnv
+ ServerAliveInterval
+ ServerAliveCountMax
+ SmartcardDevice
+ StrictHostKeyChecking
+ TCPKeepAlive
+ UsePrivilegedPort
+ User'
+ UserKnownHostsFile
+ VerifyHostKeyDNS
+
+ -P <i>port</i>
+ The port to connect to on the remote host.
+ Note that this option is written with a capital 'P', because -p is
+ already reserved for preserving the times and modes of the file in rcp(1).
+
+ -p' Preserves modification times, access times, and modes from the original file.
+
+ -q' Disables the progress meter.
+
+ -r' Recursively copy entire directories.
+
+ -S <i>program</i>
+ Name of program to use for the encrypted connection.
+ The program must understand ssh(1) options.
+
+ -v' Verbose mode.
+ Causes scp and ssh(1) to print debugging messages about their progress.
+ This is helpful in debugging connection, authentication, and configuration problems.
+</pre>
+<p>scp exits with 0 on success or &gt;0 if an error occurred. </p>
+<p><b>Example</b></p>
+<p>Copy file1 to a remote host:<span class="telety"><br>
+scp /home/simon/file1 kate@ss64.com:/home/kate</span></p>
+<p><i>&ldquo;Nothing is secure but life, transition, the energizing spirit&rdquo; - Ralph Waldo Emerson</i></p>
+<p><b>Related</b>:<br>
+<br>
+<a href="rcp.html">rcp</a> - Copy files between two machines<br> sftp(1), ssh(1), ssh-add(1), ssh-agent(1), ssh-keygen(1), ssh_config(5), sshd(8) </p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/screen.html b/help/en/bash/screen.html
new file mode 100644
index 0000000..abb8feb
--- /dev/null
+++ b/help/en/bash/screen.html
@@ -0,0 +1,138 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>screen MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> screen </h1>
+<p>Multiplex a physical terminal between several processes (typically interactive shells).</p>
+<pre>Syntax:
+
+ Start a <i>screen</i> session:
+
+ screen [ -<i>options</i> ] [ <i>cmd</i> [<i>args</i>] ]
+
+ Resume a detached screen session:
+
+ screen -r [[<i>pid</i>.]<i>tty</i>[.<i>host</i>]]
+
+ screen -r <i>sessionowner</i>/[[<i>pid</i>.]<i>tty</i>[.<i>host</i>]]
+
+Options:
+
+ -A -[r|R] Adapt all windows to the new display width & height.
+ -c <i>file</i> Read configuration file instead of .screenrc
+ -d (-r) Detach the elsewhere running screen (and reattach here).
+ -dmS <i>name</i> Start as daemon: Screen session in detached mode.
+ -D (-r) Detach and logout remote (and reattach here).
+ -D -RR Do whatever is needed to Reattach a screen session.
+ -d -m Start in "detached" mode. Useful for system startup scripts.
+ -D -m Start in "detached" mode, &amp; don't fork a new process.
+ -list List our SockDir and do nothing else (-ls)
+ -r Reattach to a detached screen process.
+ -R Reattach if possible, otherwise start a new session.
+ -t <i>title</i> Set title. (window's name).
+ -U Tell screen to use UTF-8 encoding.
+ -x Attach to a not detached screen. (Multi display mode).
+ -X Execute <i>cmd</i> as a screen command in the specified session.
+
+Interactive commands:
+
+ Control-a ? Display brief help
+ <b>Control-a &quot;</b> List all windows for selection
+ Control-a ' Prompt for a window name or number to switch to.
+ Control-a 0 Select window 0
+ Control-a 1 Select window 1
+ ... ...
+ Control-a 9 Select window 9
+ Control-a A Accept a title name for the current window.
+ Control-a b Send a break to window
+ <b>Control-a c</b> Create new window running a shell
+ Control-a C Clear the screen
+ Control-a d Detach screen from this terminal.
+ Control-a D D Detach and logout.
+ Control-a f Toggle flow on, off or auto.
+ Control-a F Resize the window to the current region size.
+ Control-a h Write a hardcopy of the current window to file &quot;hardcopy.n&quot;<br> Control-a H Begin/end logging of the current window to file &quot;screenlog.n&quot;
+ Control-a i Show info about this window.
+ <b>Control-a k</b> Kill (Destroy) the current window.
+ Control-a l Fully refresh current window
+ Control-a M Monitor the current window for activity {toggle on/off}
+ <b>Control-a n</b> Switch to the Next window
+ Control-a N Show the Number and Title of window
+ <b>Control-a p</b> Switch to the Previous window
+ Control-a q Send a control-q to the current window(xon)
+ Control-a Q Delete all regions but the current one.(only)
+ Control-a r Toggle the current window's line-wrap setting(wrap)
+ Control-a s Send a control-s to the current window(xoff)
+ Control-a w Show a list of windows (windows)
+ Control-a x Lock this terminal (lockscreen)
+ Control-a X Kill the current region(remove)
+ Control-a Z Reset the virtual terminal to its &quot;power-on&quot; values
+ Control-a Control-\ Kill all windows and terminate screen(quit)
+ Control-a : Enter command line mode(colon)
+ Control-a [ Enter copy/scrollback mode(copy)
+ Control-a ] Write the contents of the paste buffer to stdin(paste)
+ Control-a _ Monitor the current window for inactivity {toggle on/off}
+ Control-a * Show a listing of all currently attached displays.</pre>
+<p>When screen is called, it creates a single window with a shell in it (or the specified command) and then gets out of your way so that you can use the program as you normally would. </p>
+<p>Then, at any time, you can:</p>
+<blockquote>
+<p>Create new (full-screen) windows with other programs in them (including more shells)</p>
+<p>Kill existing windows</p>
+<p>View a list of windows</p>
+<p>Switch between windows - all windows run their programs completely independent of each other. Programs continue to run when their window is currently not visible and even when the whole screen session is detached from the user's terminal. </p>
+</blockquote>
+<p>The interactive commands above assume the default key bindings. You can modify screen&rsquo;s settings by creating a <a href="http://www.google.co.uk/search?q=.screenrc">~/.screenrc</a> file in your home directory. This can change the default keystrokes, bind function keys F11, F12 or even set a load of programs/windows to run as soon as you start screen.</p>
+<p><b>Attaching and Detaching</b></p>
+<p>Once you have screen running, switch to any of the running windows and type <span class="telety">Control-a d</span>. this will detach screen from this terminal. Now, go to a different machine, open a shell, ssh to the machine running screen (the one you just detached from), and type:
+<span class="telety">% screen -r</span></p>
+<p>This will reattach to the session. Just like magic, your session is back up and running, just like you never left it. </p>
+<p><b>Exiting screen completely</b></p>
+<p>Screen will exit automatically when all of its windows have been killed. </p>
+<p>Close whatever program is running or type `Exit ' to exit the shell, and the window that contained it will be killed by screen. (If this window was in the foreground, the display will switch to the previous window)</p>
+<p>When none are left, screen exits.</p>
+<p>This page is just a summary of the options available, type <span class="telety">man screen</span> for more.</p>
+<p><i>&quot;Growing old is mandatory, but growing up is optional&quot; - Motto of the Silver Screen Saddle Pals</i></p>
+<p> <b> Related</b>:</p>
+<p><a href="nohup.html">nohup</a> - Run a command immune to hangups<br>
+tset - Select your terminal type <br>
+exit - Exit the shell<br>
+<a href="http://www4.informatik.uni-erlangen.de/%7Ejnweiger/screen-faq.html">screen FAQ</a> - J&uuml;rgen Weigert</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/sdiff.html b/help/en/bash/sdiff.html
new file mode 100644
index 0000000..9d2fd8d
--- /dev/null
+++ b/help/en/bash/sdiff.html
@@ -0,0 +1,170 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>sdiff MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> sdiff</h1>
+<p>Merge two files interactively. (Show differences) with output
+to <i>outfile</i>.</p>
+<pre>SYNTAX
+ sdiff -o <i>outfile</i> [<i>options</i>] <i>from-file to-file</i>
+
+OPTIONS
+
+ Multiple single letter options (unless they take an argument)
+ can be combined into a single command line argument.
+
+ <b>-a</b> Treat all files as text and compare them line-by-line,
+ even if they do not appear to be text.
+
+ <b>-b</b> Ignore changes in amount of white space.
+
+ <b>-B</b> Ignore changes that just insert or delete blank
+ lines.
+
+ <b>-d</b> Change the algorithm to perhaps find a smaller set
+ of changes. This makes <i>sdiff</i> slower (sometimes
+ much slower).
+
+ <b>-H</b> Use heuristics to speed handling of large files
+ that have numerous scattered small changes.
+
+ <b>--expand-tabs</b>
+
+ Expand tabs to spaces in the output, to preserve
+ the alignment of tabs in the input files.
+
+ <b>-i</b> Ignore changes in case; consider upper- and lower-
+ case to be the same.
+
+ <b>-I</b> <i>regexp</i>
+ Ignore changes that just insert or delete lines
+ that match <i>regexp</i>.
+
+ <b>--ignore-all-space</b>
+ Ignore white space when comparing lines.
+
+ <b>--ignore-blank-lines</b>
+
+ Ignore changes that just insert or delete blank
+ lines.
+
+ <b>--ignore-case</b>
+ Ignore changes in case; consider upper- and lower-
+ case to be the same.
+
+ <b>--ignore-matching-lines=</b><i>regexp</i>
+ Ignore changes that just insert or delete lines
+ that match <i>regexp</i>.
+
+ <b>--ignore-space-change</b>
+ Ignore changes in amount of white space.
+
+ <b>-l</b>
+
+ <b>--left-column</b>
+ Print only the left column of two common lines.
+
+ <b>--minimal</b>
+ Change the algorithm to perhaps find a smaller set
+ of changes. This makes <i>sdiff</i> slower (sometimes
+ much slower).
+
+ <b>-o</b> <i>file</i>
+ <b>--output=</b><i>file</i>
+
+ Put merged output into <i>file</i>. This option is
+ required for merging.
+
+ <b>-s</b>
+ <b>--suppress-common-lines</b>
+ Do not print common lines.
+
+ <b>--speed-large-files</b>
+ Use heuristics to speed handling of large files
+ that have numerous scattered small changes.
+
+ <b>-t</b> Expand tabs to spaces in the output, to preserve
+ the alignment of tabs in the input files.
+
+ <b>--text</b> Treat all files as text and compare them line-by-
+ line, even if they do not appear to be text.
+
+ <b>-v</b>
+
+ <b>--version</b>
+ Output the version number of <i>sdiff</i>.
+
+ <b>-w</b> <i>columns</i>
+ <b>--width=</b><i>columns</i>
+ Use an output width of <i>columns</i>. Note that for his-
+ torical reasons, this option is <b>-W</b> in <i>diff</i>, <b>-w</b> in
+ <i>sdiff</i>.
+
+ <b>-W</b> Ignore horizontal white space when comparing lines.
+ Note that for historical reasons, this option is <b>-w</b>
+
+ in <i>diff</i>, <b>-W</b> in <i>sdiff</i>.</pre>
+<p>Long named options can be abbreviated to any unique prefix of
+ their name.</p>
+<p> If <i>from-file</i> is a directory and <i>to-file</i> is not,
+ <i>sdiff</i> compares the file in <i>from-file</i> whose file name is that of
+ <i>to-file</i>, and vice versa. <i>from-file</i> and <i>to-file</i> may not
+ both be directories.</p>
+<p> <i>sdiff</i> options begin with <b>-</b>, so normally <i>from-file</i>
+ and <i>to-</i><i>file</i> may not begin with <b>-</b>. However, <b>--</b> as
+ an argument by itself treats the remaining arguments as file names even if they
+ begin with <b>-</b>. </p>
+<p>You may not use <b>-</b> as an input file. </p>
+<p><i>sdiff</i> without <b>-o</b> (or <b>--output</b>) produces a
+ side-by-side difference. This usage is obsolete; use <b>diff</b> <b>--side-by-side</b>
+ instead.</p>
+<p>An exit status of 0 means no differences were found, 1 means some
+ differences were found, and 2 means trouble.</p>
+<p><i>"Eventually, all things merge into one, and a river runs through it&quot; - Norman Maclean</i></p>
+<p><b>Related</b>:<br>
+ <br>
+ <a href="cmp.html">cmp</a> - Compare two files<br>
+ comm(1) <br>
+ <a href="diff.html">diff</a> - Display the differences between two files<br>
+ <a href="diff3.html">diff3</a> - Show differences among three files <br>
+Equivalent Windows commands: <a href="../term_tools/nt/comp.html">COMP</a> / <a href="../term_tools/nt/fc.html">FC</a> - Compare and display Characters/Lines which do not match.<br>
+(also the WINDIFF GUI)</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/sed.html b/help/en/bash/sed.html
new file mode 100644
index 0000000..79ac9da
--- /dev/null
+++ b/help/en/bash/sed.html
@@ -0,0 +1,161 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>sed MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> sed</h1>
+<p>SED is a stream editor. A stream editor is used to perform basic
+ text transformations on an input stream (a file or input from a pipeline). <br>
+ While in some ways similar to an editor which permits scripted edits, SED works
+ by making only one pass over the input(s), and is consequently more efficient.
+ But it is SED's ability to filter text in a pipeline which particularly distinguishes
+it from other types of editors.</p>
+<pre>SYNTAX
+ sed [<i>options</i>]...
+
+OPTIONS</pre>
+<p> <span class="body">A single command may be specified as the first argument
+ to sed. Multiple commands may be specified by using the -e or -f options. All
+ commands are applied to the input in the order they are specified regardless
+of their origin.</span> </p>
+<pre>`-e SCRIPT'
+`--expression=SCRIPT'
+ Add the commands in SCRIPT to the set of commands to be run while
+ processing the input.
+
+`-f SCRIPT-FILE'
+`--file=SCRIPT-FILE'
+ Add the commands contained in the file SCRIPT-FILE to the set of
+ commands to be run while processing the input.
+
+`-n'
+`--quiet'
+`--silent'
+ By default, SED will print out the pattern space at then end of
+ each cycle through the script. These options disable this
+ automatic printing, and SED will only produce output when
+ explicitly told to via the `p' command.
+
+`-h'
+`--help'
+ Print a usage message and then exit.
+
+`-V'
+`--version'
+ Print out version info and exit.</pre>
+<p> If no `-e', `-f', `--expression', or `--file' options are given
+ on the command-line, then the first non-option argument on the command line
+ is taken to be the SCRIPT to be executed. If any command-line parameters remain
+ after processing the above, these parameters are interpreted as the names of
+ input files to be processed. A file name of `-' refers to the standard input
+ stream. The standard input will processed if no file names are specified.<br>
+ <br>
+ sed supports regular expressions (like <a href="awk.html">awk</a>), and can
+ select whole lines or patterns of text.<br>
+ e.g. </p>
+<pre>`/REGEXP/'
+ This will select any line which matches the regular expression
+ REGEXP. If REGEXP itself includes any `/' characters, each must
+ be escaped by a backslash (`\').
+
+`/REGEXP/I'
+`\%REGEXP%I'
+ The `I' modifier to regular-expression matching is a GNU extension
+ which causes the REGEXP to be matched in a case-insensitive manner.</pre>
+<p> Having selected a pattern you can either delete or replace it...</p>
+<pre>`d'
+ Delete the pattern space; immediately start next cycle.
+
+`s/REGEXP/REPLACEMENT/FLAGS'
+ (The `/' characters may be uniformly replaced by any other single
+ character within any given `s' command.)</pre>
+<blockquote>
+ <p><span class="body"> The `/' character (or whatever other character is used
+ in its stead) can appear in the REGEXP or REPLACEMENT only if it is preceded
+ by a `\' character. Also newlines may appear in the REGEXP using the two character
+ sequence `\n'.<br>
+ <br>
+ The `s' command attempts to match the pattern space against the supplied REGEXP.
+ If the match is successful, then that portion of the pattern space which was
+ matched is replaced with REPLACEMENT.<br>
+ <br>
+ The REPLACEMENT can contain `\N' (N being a number from 1 to 9, inclusive)
+ references, which refer to the portion of the match which is contained between
+ the Nth `\(' and its matching `\)'.<br>
+ Also, the REPLACEMENT can contain unescaped `&' characters which will reference
+ the whole matched portion of the pattern space. To include a literal `\',
+ `&', or newline in the final replacement, be sure to precede the desired `\',
+ `&', or newline in the REPLACEMENT with a `\'.</span> </p>
+</blockquote>
+<pre> The `s' command can be followed with zero or more of the following
+ FLAGS:
+
+ `g'
+ Apply the replacement to *all* matches to the REGEXP, not
+ just the first.
+
+ `p'
+ If the substitution was made, then print the new pattern
+ space.
+
+ `NUMBER'
+ Only replace the NUMBERth match of the REGEXP.
+
+ `w FILE-NAME'
+ If the substitution was made, then write out the result to
+ the named file.
+
+ `I'
+ Match REGEXP in a case-insensitive manner.
+ (This is a GNU extension.)</pre>
+<p> More (much more) detail is available from `info sed'</p>
+<p><i>&quot;life is 10% what happens to me and 90% how I react to
+ it&quot; - Charles
+ Swindoll </i><b><br>
+ <br>
+ Related</b>:<br>
+ <br>
+ <a href="awk.html">awk</a> - Find and Replace text within file(s)<a href="cal.html"></a><br>
+ <a href="grep.html">grep</a> - Search file(s) for lines that match a given pattern<br>
+ regex(3)<br>
+ re_format(7) <br>
+Equivalent Windows commands:<a href="../term_tools/nt/findstr.html">
+FINDSTR</a> - Search for strings in files</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/select.html b/help/en/bash/select.html
new file mode 100644
index 0000000..d946185
--- /dev/null
+++ b/help/en/bash/select.html
@@ -0,0 +1,91 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>select MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> select</h1>
+<p>The <code>select</code> construct allows the easy generation of
+ menus. It has almost the same syntax as the <code>for</code> command.</p>
+
+<pre>Syntax
+ select <var>name</var> [in <var>words</var> ...]; do <var>commands</var>; done</pre>
+<p>The list of words following <code>in</code> is expanded, generating a list
+ of items. The set of expanded words is printed on the standard error output
+ stream, each preceded by a number.<br>
+ <br>
+ If the <samp>`in <var>words</var>'</samp> is omitted, the positional parameters
+ are printed, as if <samp>`in "$@"'</samp> had been specifed. The <code>PS3</code>
+ prompt is then displayed and a line is read from the standard input. If the
+ line consists of a number corresponding to one of the displayed words, then
+ the value of <var>name</var> is set to that word. If the line is empty, the
+ words and prompt are displayed again. If <code>EOF</code> is read, the <code>select</code>
+ command completes. Any other value read causes <var>name</var> to be set to
+ null. The line read is saved in the variable <code>REPLY</code>.<br>
+ <br>
+ The <var>commands</var> are executed after each selection until a <code>break</code>
+ or <code>return</code> command is executed, at which point the <code>select</code>
+ command completes. <br>
+ <br>
+ Here is an example that allows the user to pick a filename from the current
+ directory, and displays the name and index of the file selected. </p>
+<pre>select fname in *;
+do
+ echo you picked $fname \($REPLY\)
+ break;
+done
+</pre>
+<p><code>((...))</code> </p>
+<pre>(( <var>expression</var> ))
+</pre>
+<p> If the value of the expression is non-zero, the return status is 0; otherwise
+ the return status is 1. This is exactly equivalent to </p>
+<pre>let "<var>expression</var>"</pre>
+<p><em>The truly successful businessman is essentially a dissenter, a rebel who is seldom if ever satisfied with the <a href="http://www.statusquo.co.uk/">status quo</a>&quot; -
+J. Paul Getty</em></p>
+<p><b>Related</b>:<a href="for.html"><br>
+ <br>
+ </a><a href="read.html">read</a> - read a line from standard input<a href="for.html">
+ <br>
+ for</a> - Expand <var>words</var>, and execute <var>commands</var><br>
+ <a href="if.html">if</a> - Conditionally perform a command<br>
+ <a href="until.html">until</a> - Execute commands (until error)<br>
+Equivalent Windows command:
+<a href="../term_tools/nt/choice.html">CHOICE</a> - Accept keyboard input to a batch file</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/seq.html b/help/en/bash/seq.html
new file mode 100644
index 0000000..46ee936
--- /dev/null
+++ b/help/en/bash/seq.html
@@ -0,0 +1,86 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>seq MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> seq</h1>
+<p>Print a sequence of numbers to standard output</p>
+<pre>Syntax
+ seq [<em>options</em>]... [<em>FIRST</em> [<em>STEP</em>]] <em>LAST</em>...
+
+Options
+
+ -f <em>FORMAT</em>
+ --format=<em>FORMAT</em>
+ Print all numbers using FORMAT; default `%g'. FORMAT must contain
+ exactly one of the standarding float output formats `%e', `%f', or
+ `%g'.
+
+ -s <em>STRING</em>
+ --separator=<em>STRING</em>
+ Separate numbers with <em>STRING</em>; default is a newline. The output
+ always terminates with a newline.
+
+ -w
+ --equal-width
+ Print all numbers with the same width, by padding with leading
+ zeroes. (To have other kinds of padding, use `--format').</pre>
+<p>`seq' prints the numbers from <em>FIRST</em> to <em>LAST</em> by <em>STEP</em>. <br>
+ <br>
+ By default, FIRST and STEP are both 1, and each number is printed on its own
+ line. All numbers can be reals, not just integers.</p>
+<p><b>Examples</b></p>
+<p>Produce a sequence of numbers from 1 to 100</p>
+<p class="code">$ seq 100</p>
+<p>You can also produce a sequence with the <a href="for.html">for</a> command </p>
+<p><span class="code">for ((myseq=0; myseq&lt;50; myseq++))<br>
+do<br>
+echo The sequence is ${myseq}<br>
+done <br>
+fi</span><br>
+ <br>
+ <i>&ldquo;The idea of a Being who interferes with the sequence of events in the world is absolutely impossible&rdquo; - Albert Einstein</i></p>
+<p><b>Related</b>:<br>
+ <br>
+ <a href="expr.html">expr</a> - Evaluate expressions<br>
+ <a href="for.html">for</a> - Expand <var>words</var>, and execute <var>commands</var><br>
+ <a href="nl.html">nl</a> - Number lines and write files <br>
+ Equivalent Windows commands: <a href="../term_tools/nt/for_l.html">FOR</a> /L - Numeric loop. </p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/set.html b/help/en/bash/set.html
new file mode 100644
index 0000000..1f5a7b3
--- /dev/null
+++ b/help/en/bash/set.html
@@ -0,0 +1,211 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>set MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1>set</h1>
+<p>Manipulate shell variables and functions.</p>
+<pre>Syntax
+ set [--abBCefhHkmnpPtuvx] [-o <var>option</var>] [<var>argument</var> ...]</pre>
+<p>If no options or arguments are supplied, set displays the
+ names and values of all shell variables and functions, sorted according to the
+ current locale, in a format that may be reused as input. When options are supplied, they set or unset shell attributes. </p>
+<pre>Options
+
+Using `+' rather than `-' will cause the option to be turned off.
+
+-a <i>allexport</i>
+ Mark variables which are modified or created for export.
+
+-b <i>notify</i><br>
+ Cause the status of terminated background jobs to be
+ reported immediately, rather than before printing the
+ next primary prompt.
+&nbsp;
+-B <i>braceexpand
+</i> The shell will perform brace expansion.
+ This option is on by default.
+
+-C <i>noclobber</i>
+ Prevent output redirection using `&gt;', `&gt;&amp;',
+ and `&lt;&gt;' from overwriting existing files.
+
+-e <i>errexit</i>
+ Exit immediately if a simple command exits with a non-zero
+ status, unless the command that fails is part of an until or
+ while loop, part of an if statement, part of a &amp;&amp; or || list,
+ or if the command's return status is being inverted using !.
+
+-f <i>noglob
+</i> Disable file name generation (globbing).
+
+-h <i>hashall
+</i> Locate and remember (hash) commands as they are looked
+ up for execution. This option is enabled by default.
+
+-H <i>histexpand</i>
+ Enable `!' style history substitution
+ This option is on by default for interactive shells.
+
+-k <i>keyword</i>
+ All arguments in the form of assignment statements are
+ placed in the environment for a command, not just those that
+ precede the command name.
+
+-m <i>monitor
+</i> Job control is enabled.
+
+-n <i>noexec
+</i> Read commands but do not execute them; this may be used
+ to check a script for syntax errors.
+ This option is ignored by interactive shells.
+
+-o option-name
+ Set the option corresponding to `option-name'
+ The `option-names' are listed above and below (in <i>ITALICS</i>)
+
+ <i>emacs</i> : Use an emacs-style line editing interface .
+ <i>history</i> : Enable command history,
+ this option is on by default in interactive shells.
+ <i>ignoreeof</i> : An interactive shell will not exit upon reading EOF.
+ <i>posix</i> : Change the behavior of Bash to match the POSIX 1003.2 standard.
+ <i>vi</i> : Use a vi-style line editing interface.
+
+-p <i>privileged</i>
+ Turn on privileged mode. In this mode,
+ the $BASH_ENV and $ENV files are not processed,
+ shell functions are not inherited from the environment,
+ and the SHELLOPTS variable, if it appears in the environment,
+ is ignored.
+ If the shell is started with the effective user (group) id
+ not equal to the real user (group) id, and the -p option
+ is not supplied, these actions are taken and the effective
+ user id is set to the real user id.
+ If the -p option is supplied at startup, the effective user
+ id is not reset. Turning this option off causes the effective
+ user and group ids to be set to the real user and group ids.
+
+-P <i>physical</i>
+ If set, do not follow symbolic links when performing
+ commands. The physical directory is used instead.
+
+-t <i>onecmd
+</i> Exit after reading and executing one command.
+
+-u <i>nounset</i>
+ Treat unset variables as an error when performing
+ parameter expansion. An error message will be written
+ to the standard error, and a non-interactive shell will exit.
+
+-v <i>verbose</i>
+ Print shell input lines as they are read.
+
+-x <i>xtrace</i>
+ Print a trace of simple commands and their arguments
+ after they are expanded and before they are executed.
+&nbsp;
+--
+ If no arguments follow this option, then the positional parameters are unset.
+ Otherwise, the positional parameters are set to the arguments,
+ even if some of them begin with a `-'.
+
+-
+ Signal the end of options, cause all remaining arguments to be
+ assigned to the positional parameters. The `-x' and `-v'
+ options are turned off. If there are no arguments, the positional parameters
+ remain unchanged.</pre>
+<p><span class="body"> <strong>Examples</strong></span></p>
+<p>Set the variable 'mydept' equal to 'Sales' :</p>
+
+<pre> mydept=Sales
+
+To make the change permanent:
+
+ export mydept</pre>
+<p><strong>Symbolic Links</strong></p>
+<p>By default, Bash follows the logical chain
+ of directories when performing commands which change the current directory.
+ e.g.</p>
+<pre>If `/usr/sys' is a symbolic link to `/usr/local/sys' then:
+
+$ cd /usr/sys; echo $PWD
+/usr/sys
+$ cd ..; pwd
+/usr
+
+ If <b>set -P</b> is on (do not follow symbolic links), then:
+
+$ cd /usr/sys; echo $PWD
+/usr/local/sys
+$ cd ..; pwd
+/usr/local
+</pre>
+<p>Debugging part of a script:</p>
+<pre>set -x # activate debugging <br># your commands go here...<br>set +x # stop debugging </pre>
+<p>The options can also be used upon invocation of the shell.
+ The current set of options may be found in <code>$-</code>. The remaining N <var>arguments</var>
+ are positional parameters and are assigned, in order, to <code>$1</code>, <code>$2</code>,
+ ... <code>$N</code>. The special parameter <code>#</code> is set to N. <br>
+ <br>
+ set is a POSIX `special' builtin. The return status is always zero unless an invalid
+option is supplied. </p>
+<p><em>&quot;Never memorize what you can look up in books&quot; - Einstein
+</em></p>
+<p><b>Related bash commands</b>:<br>
+ <a href="env.html"><br>
+ env</a> - Display, set, or remove environment variables <br>
+ <a href="groups.html">groups</a> - Print group names a user is in<br>
+ <a href="hostname.html">hostname</a> - Print or set system name <br>
+ <a href="id.html">id</a> - Print user and group id's<br>
+ <a href="logname.html">logname</a> - Print current login name <br>
+ printenv - Print environment variables <br>
+ <a href="readonly.html">readonly</a> - Mark variables/functions as readonly
+ <br>
+ <a href="shift.html">shift</a> - Shift positional parameters<br>
+ <a href="shopt.html">shopt</a> - Shell Options <br>
+ <a href="uname.html">uname</a> - Print system information<br>
+ <a href="users.html">users</a> - Print login names of users currently logged
+ in <br>
+ <a href="unset.html">unset</a> - Remove variable or function names<br>
+ <a href="who.html">who</a> - Print who is currently logged in <br>
+Equivalent Windows commands:
+ <a href="set.html">SET</a> - Display, set, or remove Windows NT environment
+variables</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/shift.html b/help/en/bash/shift.html
new file mode 100644
index 0000000..b9537cb
--- /dev/null
+++ b/help/en/bash/shift.html
@@ -0,0 +1,69 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>shift MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> shift</h1>
+<span class="body">Shift positional parameters to the left by n.</span><br>
+<pre>Syntax
+ shift [<em>n</em>]
+
+Options
+
+ <em>n</em> : The number of parameters to shift (default = 1)</pre>
+<p> The positional parameters from <br>
+ n+1 ... $# <br>
+ are renamed to <br>
+ $1 ... $#-n+1<br>
+ <br>
+ Parameters represented by the numbers $# to n+1 are unset. <br>
+ <br>
+ n must be a positive number less than or equal to $#.<br>
+ <br>
+ The return status is zero unless n is greater than $# or less than zero. </p>
+<p>shift is a BOURNE shell command and a POSIX `special' builtin.</p>
+<p><em>&ldquo;Here lies Colonel Chinstrap, drowned, From the inside&rdquo; - Shifting sands, The Goon Show </em></p>
+<p><b>Related</b>:<br>
+ <br>
+ <a href="getopts.html">getopts</a> - Parse positional parameters<br>
+Equivalent Windows command:
+ <a href="../term_tools/nt/shift.html">SHIFT</a> - Shift parameters
+in a batch file</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/shopt.html b/help/en/bash/shopt.html
new file mode 100644
index 0000000..c84b767
--- /dev/null
+++ b/help/en/bash/shopt.html
@@ -0,0 +1,211 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>shopt MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> shopt</h1>
+<p>Shell Options</p>
+<pre>Syntax
+ shopt [-pqsu] [-o] [<var>optname</var> ...]
+
+Options
+ -s Enable (set) each optname
+
+ -u Disable (unset) each optname.
+
+ -p Display a list of all settable options, with an indication of
+ whether or not each is set. The output is displayed in a form
+ that may be reused as input. (-p is the default action)
+
+ -q Suppresses normal output; the return status indicates whether the optname
+ is set or unset. If multiple optname arguments are given with `-q',
+ the return status is zero if all optnames are enabled; non-zero otherwise.
+
+ -o Restricts the values of optname to be those defined for the `-o' option to
+ the set builtin.</pre>
+<p><span class="body"> If either `-s' or `-u' is used with no optname arguments,
+ the display is limited to those options which are set or unset, respectively.
+ Unless otherwise noted, the shopt options are disabled (off) by default. <br>
+ <br>
+ The return status is zero unless an optname was *not* enabled or was not a valid
+ shell option. </span><br>
+</p>
+<pre>The list of <code>shopt</code> options is:
+
+cdable_vars
+ If this is set, an argument to the <code>cd</code> builtin command that
+ is not a directory is assumed to be the name of a variable whose value is
+ the directory to change to.
+
+cdspell
+ If set, minor errors in the spelling of a directory component in a <code>cd</code>
+ command will be corrected. The errors checked for are transposed characters,
+ a missing character, and a character too many. If a correction is found, the
+ corrected path is printed, and the command proceeds. This option is only used
+ by interactive shells.
+
+checkhash
+ If this is set, Bash checks that a command found in the hash table exists
+ before trying to execute it. If a hashed command no longer exists, a normal
+ path search is performed.
+
+checkwinsize
+ If set, Bash checks the window size after each command and, if necessary,
+ updates the values of <code>LINES</code> and <code>COLUMNS</code>.
+
+cmdhist
+ If set, Bash attempts to save all lines of a multiple-line command in the
+ same history entry. This allows easy re-editing of multi-line commands.
+
+dotglob
+ If set, Bash includes filenames beginning with a `.' in the results of filename
+ expansion.
+
+execfail
+ If this is set, a non-interactive shell will not exit if it cannot execute
+ the file specified as an argument to the <code>exec</code> builtin command.
+ An interactive shell does not exit if <code>exec</code> fails.
+
+expand_aliases
+ If set, aliases are expanded. This option is enabled by default for interactive
+ shells.
+
+extglob
+ If set, the extended pattern matching features described above are enabled.
+
+histappend
+ If set, the history list is appended to the history file when the shell exits,
+ rather than overwriting the history file.
+ shopt -s histappend
+ To append every line to history individually set:
+ PROMPT_COMMAND='history -a'
+ With these two settings, a new shell will get the history lines from all previous
+ shells instead of the default 'last window closed'&gt;history
+ (the history file is named by the value of the <code>HISTFILE</code> variable)
+
+histreedit
+ If set, and Readline is being used, a user is given the opportunity to re-edit
+ a failed history substitution.
+
+histverify
+ If set, and Readline is being used, the results of history substitution
+ are not immediately passed to the shell parser. Instead, the resulting line
+ is loaded into the Readline editing buffer, allowing further modification.
+
+hostcomplete
+ If set, and Readline is being used, Bash will attempt to perform hostname
+ completion when a word containing a <samp>`@'</samp> is being completed.
+ This option is enabled by default.
+
+huponexit
+ If set, Bash will send <code>SIGHUP</code> to all jobs when an interactive
+ login shell exits.
+
+interactive_comments
+ Allow a word beginning with <samp>`#'</samp> to cause that word and all
+ remaining characters on that line to be ignored in an interactive shell. This
+ option is enabled by default.
+
+lithist
+ If enabled, and the <code>cmdhist</code> option is enabled, multi-line commands
+ are saved to the history with embedded newlines rather than using semicolon
+ separators where possible.
+
+mailwarn
+ If set, and a file that Bash is checking for mail has been accessed since
+ the last time it was checked, the message <code>"The mail in <var>mailfile</var>
+ has been read"</code> is displayed.
+
+no_empty_cmd_completion
+ If set, and Readline is being used, Bash will not attempt to search the
+ <code>PATH</code> for possible completions when completion is attempted on
+ an empty line.
+
+nocaseglob
+ If set, Bash matches filenames in a case-insensitive fashion when performing
+ filename expansion.
+
+nullglob
+ If set, Bash allows filename patterns which match no files to expand to
+ a null string, rather than themselves.
+
+progcomp
+ If set, the programmable completion facilities are enabled. This option
+ is enabled by default.
+
+promptvars
+ If set, prompt strings undergo variable and parameter expansion after being
+ expanded. This option is enabled by default.
+
+restricted_shell
+ The shell sets this option if it is started in restricted mode. The value
+ may not be changed. This is not reset when the startup files are executed,
+ allowing the startup files to discover whether or not a shell is restricted.
+
+shift_verbose
+ If this is set, the <code>shift</code> builtin prints an error message when
+ the shift count exceeds the number of positional parameters.
+
+sourcepath
+ If set, the <code>source</code> builtin uses the value of <code>PATH</code>
+ to find the directory containing the file supplied as an argument. This option
+ is enabled by default.
+
+xpg_echo
+ If set, the <code>echo</code> builtin expands backslash-escape sequences
+ by default.</pre>
+<p>`shopt' is a BASH builtin command.<br>
+ <br>
+ <i>&quot;The dogma of the ghost in the machine&quot; - Gilbert
+ Ryle </i> </p>
+<p><b>Related</b>:<br>
+ <a href="env.html"><br>
+ env</a> - Display, set, or remove environment variables<br>
+ <a href="function.html">function</a> - Define Function Macros<br>
+ <a href="local.html">local</a> - Create variables <br>
+ <a href="logname.html">logname</a> - Print current login name<br>
+ <a href="set.html">set</a> - Manipulate shell variables and functions<br>
+ <a href="uname.html">uname</a> - Print system information<br>
+ <a href="users.html">users</a> - Print login names of users currently logged
+ in<br>
+ <a href="who.html">who</a> - Print who is currently logged in <br>
+Equivalent Windows commands: <a href="../term_tools/nt/setlocal.html">SETLOCAL</a> - Set options to control the visibility of variables<br>
+</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/shutdown.html b/help/en/bash/shutdown.html
new file mode 100644
index 0000000..b8c5360
--- /dev/null
+++ b/help/en/bash/shutdown.html
@@ -0,0 +1,86 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>shutdown MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> shutdown</h1>
+<p> Shutdown or restart linux</p>
+<pre>Syntax
+ shutdown [<em>options</em>] <em>when</em> [<em>message</em>]
+
+Options
+ -c Cancel a shutdown that is in progress.
+
+ -f Reboot fast, by suppressing the normal call to fsck
+ when rebooting.
+ -h Halt the system when shutdown is complete.
+
+ -k Print the warning message, but suppress actual shutdown.
+
+ -n Perform shutdown without a call to init.
+
+ -r Reboot the system when shutdown is complete.
+
+ -t <em>sec</em>
+ Ensure a sec-second delay between killing processes
+ and changing the runlevel.
+
+<b>Examples
+</b> Shutdown immediately:
+ shutdown -h now
+
+ Reboot immediately:
+ shutdown -r now
+
+ Shutdown at 8 pm:
+ shutdown -h 20:00
+
+ Shutdown in 10 minutes:
+ shutdown -h +10 </pre>
+<p><i>&quot;The illegal we do immediately. The unconstitutional takes
+ a little longer&quot; - Henry
+ Kissinger </i><br>
+ <br>
+ <b> Related</b>:<br>
+ <br>
+ <a href="logout.html">logout</a> - Exit a login shell<br>
+Equivalent Windows command:
+<a href="../term_tools/nt/shutdown.html">SHUTDOWN</a></p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/sleep.html b/help/en/bash/sleep.html
new file mode 100644
index 0000000..542a25a
--- /dev/null
+++ b/help/en/bash/sleep.html
@@ -0,0 +1,68 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>sleep MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> sleep</h1>
+<p>Delay for a specified time, pause for an amount of time specified
+by the sum of the values of the command line arguments</p>
+<pre>Syntax
+ sleep [<em>NUMBER</em> [smhd]]...
+
+Key:
+
+ s : seconds (default)
+
+ m : minutes
+
+ h : hours
+
+ d : days</pre>
+<p><i>&quot;I think men talk to women so they can sleep with them
+ and women sleep with men so they can talk to them&quot; - Jay
+ McInerney </i><br>
+ <br>
+ <b> Related</b>:<br>
+ <br>
+ <a href="nice.html">nice</a> - Change job scheduling priority<br>
+ at(1) - <br>
+Equivalent Windows commands:
+ <a href="../term_tools/nt/sleep.html">SLEEP</a> - Wait for x seconds</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/slocate.html b/help/en/bash/slocate.html
new file mode 100644
index 0000000..760e9e0
--- /dev/null
+++ b/help/en/bash/slocate.html
@@ -0,0 +1,103 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>sLocate - find files MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1>slocate</h1>
+<p>Security Enhanced version of GNU Locate. Secure Locate provides a secure way to index and quickly search for files on your system. It uses incremental encoding just like GNU locate to compress its database to make searching faster, but it will also store file permissions and ownership so that users will not see files they do not have access to. </p>
+<pre>Syntax
+ slocate [-qi] [-d <i>path</i>] [--database=<i>path</i>] <i>search string</i>
+
+ slocate [-i] [-r <i>regexp</i>] [--regexp=<i>regexp</i>]
+
+ slocate [-qv] [-o <i>file</i>] [--output=<i>file</i>]
+
+ slocate [-e <i>dir1</i>,<i>dir2</i>,...] [-f <i>fstype1</i>,...] &lt;[-l <i>level</i>] [-c] &lt;[-U <i>path</i>] [-u]>
+
+ slocate [-Vh] [--version] [--help]
+
+Options
+
+ -u Create slocate database starting at path /.
+
+ -U <i>dir</i> Create slocate database starting at path <i>dir</i>.
+
+ -e <i>dir1,dir2</i>,...
+ Exclude directories from the slocate database.
+
+ -f <i>fstype1</i>,...
+ Exclude files on specific file systems from the slocate database.
+
+ -c Parse '/etc/updatedb.conf' when updating the slocate database.
+
+ -l <i>level</i>
+ Security level. 0 turns security checks off.
+ This will make search faster. 1 turns security checks on. This is the default.
+
+ -i Do a case insensitive search.
+
+ -q Quiet mode. Error messages are suppressed.
+
+ -n <i>num</i> Limit the amount of results shown to <i>num</i>.
+
+ -r <i>regexp</i>
+ --regexp=<i>regexp</i> Search the database using a basic POSIX regular expression.
+
+ -o <i>file</i>
+ --output=<i>file</i> The database to create.
+
+ -d <i>path</i>
+ --database=<i>path</i> The path of databases to search in.
+ -h
+ --help Display this help.
+ -v
+ --verbose Verbose mode. Display files when creating database.
+ -V
+ --version Display version. </pre>
+<p>slocate enables system users to search entire filesystems without displaying unauthorized files.</p>
+<p><b>Related</b>:<br>
+ <br>
+ <a href="locate.html">locate</a> - GNU Locate <br>
+ <a href="find.html"> find</a> - Search for files that meet a desired criteria<br>
+ fnmatch<br>
+ weekly.conf<br>
+Equivalent Windows command:
+<a href="dir.html">DIR</a> /S - Display a list of files and folders</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/sort.html b/help/en/bash/sort.html
new file mode 100644
index 0000000..0aaacb6
--- /dev/null
+++ b/help/en/bash/sort.html
@@ -0,0 +1,345 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>sort MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> sort</h1>
+<p>Sort text files.<br>
+ Sort, merge, or compare all the lines from the files given (or standard input.)</p>
+<pre>Syntax
+ sort [<i>options</i>] [<em>file</em>...]
+ sort --help
+ sort --version
+
+Options
+ sort has three modes of operation:
+ Sort (the default), Merge (-m), and Check(-c)
+
+ -c Check whether the given files are already sorted: if they are
+ not all sorted, print an error message and exit with a status of 1.
+
+ -m Merge the given files by sorting them as a group. Each input
+ file should already be individually sorted. It always works to
+ sort instead of merge; merging is provided because it is faster,
+ in the case where it works.
+</pre>
+<p>The following options affect the <b>ordering</b> of output lines. They may be
+specified globally or as part of a specific key field. If no key<br>
+fields are specified, global options apply to comparison of entire lines;
+otherwise the global options are inherited by key fields that do not<br>
+specify any special options of their own.
+The `-b', `-d', `-f' and `-i' options classify characters according to
+the `LC_CTYPE' locale.</p>
+<pre>
+`-b'
+ Ignore leading blanks when finding sort keys in each line.
+
+`-d'
+ Sort in "phone directory" order: ignore all characters except
+ letters, digits and blanks when sorting.
+
+`-f'
+ Fold lowercase characters into the equivalent uppercase characters
+ when sorting so that, for example, `b' and `B' sort as equal.
+
+`-g'
+ Sort numerically, using the standard C function `strtod' to convert
+ a prefix of each line to a double-precision floating point number.
+ This allows floating point numbers to be specified in scientific
+ notation, like `1.0e-34' and `10e100'. Do not report overflow,
+ underflow, or conversion errors. Use the following collating
+ sequence:
+
+ * Lines that do not start with numbers (all considered to be
+ equal).
+
+ * NaNs ("Not a Number" values, in IEEE floating point
+ arithmetic) in a consistent but machine-dependent order.
+
+ * Minus infinity.
+
+ * Finite numbers in ascending numeric order (with -0 and +0
+ equal).
+
+ * Plus infinity.
+
+ Use this option only if there is no alternative; it is much slower
+ than `-n' and it can lose information when converting to floating
+ point.
+
+`-i'
+ Ignore unprintable characters.
+
+`-M'
+ An initial string, consisting of any amount of whitespace, followed
+ by a month name abbreviation, is folded to UPPER case and compared
+ in the order `JAN' < `FEB' < ... < `DEC'. Invalid names compare
+ low to valid names. The `LC_TIME' locale determines the month
+ spellings.
+
+`-n'
+ Sort numerically: the number begins each line; specifically, it
+ consists of optional whitespace, an optional `-' sign, and zero or
+ more digits possibly separated by thousands separators, optionally
+ followed by a radix character and zero or more digits. The
+ `LC_NUMERIC' locale specifies the radix character and thousands
+ separator.
+
+ `sort -n' uses what might be considered an unconventional method
+ to compare strings representing floating point numbers. Rather
+ than first converting each string to the C `double' type and then
+ comparing those values, sort aligns the radix characters in the two
+ strings and compares the strings a character at a time. One
+ benefit of using this approach is its speed. In practice this is
+ much more efficient than performing the two corresponding
+ string-to-double (or even string-to-integer) conversions and then
+ comparing doubles. In addition, there is no corresponding loss of
+ precision. Converting each string to `double' before comparison
+ would limit precision to about 16 digits on most systems.
+
+ Neither a leading `+' nor exponential notation is recognized. To
+ compare such strings numerically, use the `-g' option.
+
+`-r'
+ Reverse the result of comparison, so that lines with greater key
+ values appear earlier in the output instead of later.
+
+<b>Other options</b>:
+
+`-o <i>OUTPUT-FILE</i>'
+ Write output to <i>OUTPUT-FILE</i> instead of standard output. If
+ <i>OUTPUT-FILE</i> is one of the input files, `sort' copies it to a
+ temporary file before sorting and writing the output to
+ <i>OUTPUT-FILE</i>.
+
+`-t <i>SEPARATOR</i>'
+ Use character <i>SEPARATOR</i> as the field separator when finding the
+ sort keys in each line. By default, fields are separated by the
+ empty string between a non-whitespace character and a whitespace
+ character. That is, given the input line ` foo bar', `sort'
+ breaks it into fields ` foo' and ` bar'. The field separator is
+ not considered to be part of either the field preceding or the
+ field following.
+
+`-u'
+ For the default case or the `-m' option, only output the first of
+ a sequence of lines that compare equal. For the `-c' option,
+ check that no pair of consecutive lines compares equal.
+
+`-k <i>POS1</i>[,<i>POS2</i>]'
+ The recommended, POSIX, option for specifying a sort field. The
+ field consists of the part of the line between POS1 and POS2 (or
+ the end of the line, if POS2 is omitted), _inclusive_. Fields and
+ character positions are numbered starting with 1. So to sort on
+ the second field, you'd use `-k 2,2' See below for more examples.
+
+`-z'
+ Treat the input as a set of lines, each terminated by a zero byte
+ (ASCII NUL (Null) character) instead of an ASCII LF (Line Feed).
+ This option can be useful in conjunction with `perl -0' or `find
+ -print0' and `xargs -0' which do the same in order to reliably
+ handle arbitrary pathnames (even those which contain Line Feed
+ characters.)
+
+`+<i>POS1</i>[-<i>POS2</i>]'
+ The obsolete, traditional option for specifying a sort field.
+ The field consists of the line between POS1 and up to but _not
+ including_ POS2 (or the end of the line if POS2 is omitted).
+ Fields and character positions are numbered starting with 0.
+ See below.
+
+`--help'
+
+`--version'
+</pre>
+<p><b>HOW LINES ARE COMPARED</b><br>
+<br>
+A pair of lines is compared as follows: if any key fields have been
+specified, `sort' compares each pair of fields, in the order specified
+on the command line, according to the associated ordering options,
+until a difference is found or no fields are left. Unless otherwise
+specified, all comparisons use the character collating sequence
+specified by the `LC_COLLATE' locale.<br>
+<br>
+If any of the global options `Mbdfinr' are given but no key fields
+are specified, `sort' compares the entire lines according to the global
+options.<br>
+<br>
+Finally, as a last resort when all keys compare equal (or if no
+ordering options were specified at all), `sort' compares the entire
+lines. The last resort comparison honors the `-r' global option. The
+`-s' (stable) option disables this last-resort comparison so that lines
+in which all fields compare equal are left in their original relative
+order. If no fields or global options are specified, `-s' has no
+effect.<br>
+<br>
+GNU `sort' (as specified for all GNU utilities) has no limits on
+input line length or restrictions on bytes allowed within lines. In
+addition, if the final byte of an input file is not a newline, GNU
+`sort' silently supplies one. A line's trailing newline is part of the
+line for comparison purposes; for example, with no options in an ASCII
+locale, a line starting with a tab sorts before an empty line because
+tab precedes newline in the ASCII collating sequence.<br>
+<br>
+Upon any error, `sort' exits with a status of `2'.<br>
+<br>
+If the environment variable `TMPDIR' is set, `sort' uses its value
+as the directory for temporary files instead of `/tmp'. The `-T
+TEMPDIR' option in turn overrides the environment variable.<br>
+<br>
+<b>NOTES</b><br>
+<br>
+Historical (BSD and System V) implementations of `sort' have
+differed in their interpretation of some options, particularly `-b',
+`-f', and `-n'. GNU sort follows the POSIX behavior, which is usually
+(but not always!) like the System V behavior. According to POSIX, `-n'
+no longer implies `-b'. For consistency, `-M' has been changed in the
+same way. This may affect the meaning of character positions in field
+specifications in obscure cases. The only fix is to add an explicit
+`-b'.<br>
+<br>
+A position in a sort field specified with the `-k' or `+' option has
+the form `F.C', where F is the number of the field to use and C is the
+number of the first character from the beginning of the field (for
+`+POS') or from the end of the previous field (for `-POS'). If the `.C'
+is omitted, it is taken to be the first character in the field. If the
+`-b' option was specified, the `.C' part of a field specification is
+counted from the first nonblank character of the field (for `+POS') or
+from the first nonblank character following the previous field (for
+`-POS').<br>
+<br>
+A sort key option may also have any of the option letters `Mbdfinr'
+appended to it, in which case the global ordering options are not used
+for that particular field. The `-b' option may be independently
+attached to either or both of the `+POS' and `-POS' parts of a field
+specification, and if it is inherited from the global options it will
+be attached to both. Keys may span multiple fields.</p>
+<p><b>Examples</b></p>
+<pre>Character Sort:
+
+<span class="telety">$ sort countries.txt <br>
+Numeric sort:
+
+$ sort -n numbers.txt</span>
+
+To sort the file below on the third field (area code):</pre>
+<p>Jim Alchin 212121 Seattle<br>
+Bill Gates 404404 Seattle<br>
+Steve Jobs 246810 Nevada <br>
+Scott Neally 212277 Los Angeles </p>
+<pre>$ sort -k 3,3 people.txt&gt; sorted.txt
+
+or using the 'old' syntax:
+$ sort +2 -3 people.txt&gt; sorted2.txt
+
+To sort the same file on the 4th column and supress duplicates: (should return 3 rows)
+$ sort -u -k 4,4 people.txt&gt; sorted3.txt
+</pre>
+<p><br>
+In the remaining examples, the POSIX `-k' option is used to specify sort keys rather than
+the obsolete `+POS1-POS2' syntax.</p>
+<pre>Sort in descending (reverse) numeric order:
+
+$ sort -nr
+
+Sort alphabetically, omitting the first and second fields. This
+uses a single key composed of the characters beginning at the
+start of field three and extending to the end of each line:
+
+$ sort -k3
+
+Sort numerically on the second field and resolve ties by sorting
+alphabetically on the third and fourth characters of field five.
+Use `:' as the field delimiter:
+
+$ sort -t : -k 2,2n -k 5.3,5.4</pre>
+<p>
+Note that if you had written `-k 2' instead of `-k 2,2' `sort'
+would have used all characters beginning in the second field and
+extending to the end of the line as the primary _numeric_ key.
+For the large majority of applications, treating keys spanning
+more than one field as numeric will not do what you expect.<br>
+<br>
+Also note that the `n' modifier was applied to the field-end
+specifier for the first key. It would have been equivalent to
+specify `-k 2n,2' or `-k 2n,2n'. All modifiers except `b' apply
+to the associated _field_, regardless of whether the modifier
+character is attached to the field-start and/or the field-end part<br>
+of the key specifier.</p>
+<pre>Sort the password file on the fifth field and ignore any leading
+white space. Sort lines with equal values in field five on the
+numeric user ID in field three:
+
+$ sort -t : -k 5b,5 -k 3,3n /etc/passwd
+
+An alternative is to use the global numeric modifier `-n':
+
+$ sort -t : -n -k 5b,5 -k 3,3 /etc/passwd
+
+Generate a tags file in case insensitive sorted order:
+
+$ find src -type f -print0 | sort -t / -z -f | xargs -0 etags --append</pre>
+<p>The use of `-print0', `-z', and `-0' in this case mean that
+pathnames that contain Line Feed characters will not get broken up
+by the sort operation.<br>
+<br>
+Finally, to ignore both leading and trailing white space, you
+could have applied the `b' modifier to the field-end specifier for
+the first key,</p>
+<pre>$ sort -t : -n -k 5b,5b -k 3,3 /etc/passwd
+
+or by using the global `-b' modifier instead of `-n' and an
+explicit `n' with the second key specifier:
+
+$ sort -t : -b -k 5,5 -k 3,3n /etc/passwd</pre>
+<p>A file name of `-' means standard input. </p>
+<p>By default, sort writes the results to the standard output.</p>
+<p><i>"We never sit anything out. We are cups, constantly and quietly
+ being filled. The trick is, knowing how to tip ourselves over and let the Beautiful
+ Stuff out" - Ray
+Bradbury</i></p>
+<p><b>Related</b>:<br>
+ <a href="head.html"><br>
+ head</a> - Output the first part of file(s) <br>
+ <a href="nl.html">nl</a> - Number lines and write files<br>
+ <a href="printf.html">printf</a> - Format and print data<br>
+Equivalent Windows commands:
+<a href="../term_tools/nt/sort.html">SORT</a> - Sort input</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/source.html b/help/en/bash/source.html
new file mode 100644
index 0000000..0162276
--- /dev/null
+++ b/help/en/bash/source.html
@@ -0,0 +1,82 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>source or dot operator MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> . (source or dot operator) </h1>
+<p>Run a command script in the current shell context. </p>
+<pre>Syntax
+ . <var>filename</var> [<var>arguments</var>]
+
+ source <var>filename</var> [<var>arguments</var>]</pre>
+<p>
+ A dot/period '<span class="code">.</span>' is a synonym for '<span class="code">source</span>' </p>
+<p>When a script is run using <span class="code">source</span> it runs within the existing shell, any variables created or modified by the script will remain available after the script completes. In contrast if the script is run just as <span class="telety"><i>filename</i></span>, then a separate subshell (with a completely separate set of variables) would be spawned to run the script. </p>
+<p>There is a subtle difference between executing a script by running<span class="telety"> .ss64script </span>(dot ss64script) and<span class="telety"> . ss64script </span>(dot space ss64script)<br>
+the first is running a file thats been hidden from the 'ls' command, (although <a href="ls.html">ls</a> -a will show hidden files) the second option will execute ss64script even if it has not been set as an executable with chmod.</p>
+<p>Unless you provide an exact path to <span class="telety"><i>filename</i></span> then bash will look first via the <code>PATH</code> variable
+ and then in the current directory (only if <span class="telety"><i>filename</i></span> is not found in <code>$PATH</code>.)
+ If any <var>arguments</var> are supplied, they become the positional parameters
+ when <span class="telety"><i>filename</i></span> is executed. Otherwise the positional parameters are
+ unchanged. </p>
+<p>Other ways that the bash shell may interpret a dot/period:
+<br>
+A dot can represent the current <a href="cd.html">directory</a> (&quot;<span class="code">./filename</span>&quot;) <br>
+In a regular expression, &quot;.&quot; will match any single character, (not zero or more characters.)<br>
+ <br>
+ The return status is the exit status of the last command executed, or zero if
+ no commands are executed. If <span class="telety"><i>filename</i></span> is not found, or cannot be
+read, the return status is non-zero. `source' is a bourne shell builtin and a POSIX `special' builtin</p>
+<p><b>Related</b>:<a href="for.html"><br>
+ <br>
+ </a><a href="command.html">command</a> - Run a command - ignoring shell functions<a href="for.html">
+ <br>
+ </a> <a href="builtin.html">builtin</a> - Run a shell builtin<br>
+ <a href="crontab.html">crontab</a> - Schedule a command to run at a later time<br>
+ <a href="chroot.html">chroot</a> - Run a command with a different root directory<br>
+ <a href="exec.html">exec</a> - Execute a command<br>
+ <a href="if.html">if</a> - Conditionally perform a command<br>
+ <a href="nohup.html">nohup</a> - Run a command immune to hangups<br>
+ <a href="su.html">su</a> - Run a command with substitute user and group id<br>
+ <a href="type.html">type</a> - Describe a command <br>
+ <a href="watch.html">watch</a> - Execute/display a program periodically <br>
+
+Equivalent Windows command: <a href="../term_tools/nt/setlocal.html">SETLOCAL</a> - Set options to control the visibility of variables</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/split.html b/help/en/bash/split.html
new file mode 100644
index 0000000..c9485a3
--- /dev/null
+++ b/help/en/bash/split.html
@@ -0,0 +1,96 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>split MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> split</h1>
+<p>Split a file into fixed-size pieces, creates output files containing
+consecutive sections of <em>INPUT</em> (standard input if none is given or INPUT is `-')</p>
+<pre>Syntax
+ split [<em>options</em>] [<em>INPUT</em> [<em>PREFIX</em>]]
+
+Options
+
+ -<em>LINES</em>
+ -l <em>LINES</em>
+ --lines=<em>LINES</em>
+ Put <em>LINES</em> lines of <em>INPUT</em> into each output file.
+
+ -b <em>BYTES</em>
+ --bytes=<em>BYTES</em>
+ Put the first <em>BYTES</em> bytes of <em>INPUT</em> into each output file.
+ Appending `b' multiplies <em>BYTES</em> by 512, `k' by 1024, and `m' by
+ 1048576.
+
+ -C <em>BYTES</em>
+ --line-bytes=<em>BYTES</em>
+ Put into each output file as many complete lines of INPUT as
+ possible without exceeding BYTES bytes. For lines longer than
+ BYTES bytes, put BYTES bytes into each output file until less than
+ BYTES bytes of the line are left, then continue normally. BYTES
+ has the same format as for the `--bytes' option.
+
+ --verbose
+ Write a diagnostic to standard error just before each output file
+ is opened.</pre>
+<p> By default, `split' puts 1000 lines of <em>INPUT</em> (or whatever is
+ left over for the last section), into each output file. <br>
+ <br>
+ The output files' names consist of <em>PREFIX</em> (`x' by default) followed by a group
+ of letters `aa', `ab', and so on, such that concatenating the output files in
+ sorted order by file name produces the original input file. <br>
+ <br>
+ If more than 676 output files are required, `split' uses `zaa', `zab', etc.<br>
+ <br>
+ <i>&quot;The man who is tired of London is tired of looking for a parking space&quot;
+ - Paul
+Theroux </i> </p>
+<p><b>Related</b>:<br>
+ <br>
+ <a href="csplit.html">csplit</a> - Split a file into context-determined pieces<br>
+ <a href="cut.html">cut</a> - Divide a file into several parts<br>
+ <a href="fmt.html">fmt</a> - Reformat paragraph text <br>
+ <a href="fold.html">fold</a> - Wrap input lines to fit in specified width<br>
+ <a href="head.html">head</a> - Output the first part of file(s) <br>
+ <a href="join.html">join</a> - Join lines on a common field<br>
+ <a href="paste.html">paste</a> - Merge lines of files <br>
+Equivalent Windows commands:
+<a href="../term_tools/nt/fc.html">FC</a> /lb - Compare two files</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/ssh.html b/help/en/bash/ssh.html
new file mode 100644
index 0000000..3c276b1
--- /dev/null
+++ b/help/en/bash/ssh.html
@@ -0,0 +1,896 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>ssh MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem -->
+<h1> ssh </h1>
+<p>OpenSSH SSH client (remote login program)</p>
+<pre>Syntax
+ ssh [-1246AaCfgKkMNnqsTtVvXxYy] [-b <i>bind_address</i>] [-c <i>cipher_spec</i>]
+ [-D [<i>bind_address</i>:]<i>port</i>] [-e <i>escape_char</i>] [-F <i>configfile</i>]
+ [-i <i>identity_file</i>] [-L [<i>bind_address</i>:]<i>port</i>:<i>host</i>:<i>hostport</i>]
+ [-l <i>login_name</i>] [-m <i>mac_spec</i>] [-O <i>ctl_cmd</i>] [-o <i>option</i>]
+ [-p <i>port</i>] [-R [<i>bind_address</i>:]<i>port</i>:<i>host</i>:<i>hostport</i>]
+ [-S ctl_path] [-w <i>local_tun</i>[:<i>remote_tun</i>]]
+ [user@]hostname [<i>command</i>]
+</pre>
+<p><br>
+ssh (SSH client) is a program for logging into a remote machine and for
+executing commands on a remote machine. It is intended to replace rlogin
+and rsh, and provide secure encrypted communications between two
+untrusted hosts over an insecure network. X11 connections and arbitrary
+TCP ports can also be forwarded over the secure channel.</p>
+<p> ssh connects and logs into the specified hostname (with optional user
+name). The user must prove his/her identity to the remote machine using
+one of several methods depending on the protocol version used (see
+below).</p>
+<p> If <i>command</i> is specified, it is executed on the remote host instead of a
+login shell.</p>
+<pre>The options are as follows:
+
+ <b>-1</b> Forces <b>ssh</b> to try protocol version 1 only.
+
+ <b>-2</b> Forces <b>ssh</b> to try protocol version 2 only.
+
+ <b>-4</b> Forces <b>ssh</b> to use IPv4 addresses only.
+
+ <b>-6</b> Forces <b>ssh</b> to use IPv6 addresses only.
+
+ <b>-A</b> Enables forwarding of the authentication agent connection. This
+ can also be specified on a per-host basis in a configuration
+ file.
+
+ Agent forwarding should be enabled with caution. Users with the
+ ability to bypass file permissions on the remote host (for the
+ agent’s Unix-domain socket) can access the local agent through
+ the forwarded connection. An attacker cannot obtain key material
+ from the agent, however they can perform operations on the keys
+ that enable them to authenticate using the identities loaded into
+ the agent.
+
+ <b>-a</b> Disables forwarding of the authentication agent connection.
+
+ <b>-b</b> <u>bind_address</u>
+
+ Use <u>bind_address</u> on the local machine as the source address of
+ the connection. Only useful on systems with more than one
+ address.
+
+ <b>-C</b> Requests compression of all data (including stdin, stdout,
+ stderr, and data for forwarded X11 and TCP connections). The
+ compression algorithm is the same used by gzip(1), and the
+ “level” can be controlled by the <b>CompressionLevel</b> option for
+ protocol version 1. Compression is desirable on modem lines and
+ other slow connections, but will only slow down things on fast
+ networks. The default value can be set on a host-by-host basis
+ in the configuration files; see the <b>Compression</b> option.
+
+ <b>-c</b> <u>cipher_spec</u>
+
+ Selects the cipher specification for encrypting the session.
+
+ Protocol version 1 allows specification of a single cipher. The
+ supported values are “3des”, “blowfish”, and “des”. <u>3des</u>
+ (triple-des) is an encrypt-decrypt-encrypt triple with three
+ different keys. It is believed to be secure. <u>blowfish</u> is a fast
+ block cipher; it appears very secure and is much faster than
+ <u>3des</u>. <u>des</u> is only supported in the <b>ssh</b> client for
+ interoperability with legacy protocol 1 implementations that do
+ not support the <u>3des</u> cipher. Its use is strongly discouraged due
+ to cryptographic weaknesses. The default is “3des”.
+
+ For protocol version 2, <u>cipher_spec</u> is a comma-separated list of
+ ciphers listed in order of preference. See the <b>Ciphers</b> keyword
+ for more information.
+
+ <b>-D</b> [<u>bind_address</u>:]<u>port</u>
+
+ Specifies a local “dynamic” application-level port forwarding.
+ This works by allocating a socket to listen to <u>port</u> on the local
+ side, optionally bound to the specified <u>bind_address</u>. Whenever a
+ connection is made to this port, the connection is forwarded over
+ the secure channel, and the application protocol is then used to
+ determine where to connect to from the remote machine. Currently
+ the SOCKS4 and SOCKS5 protocols are supported, and <b>ssh</b> will act
+ as a SOCKS server. Only root can forward privileged ports.
+ Dynamic port forwardings can also be specified in the
+ configuration file.
+
+ IPv6 addresses can be specified with an alternative syntax:
+ [<u>bind_address</u>/]<u>port</u> or by enclosing the address in square
+ brackets. Only the superuser can forward privileged ports. By
+ default, the local port is bound in accordance with the
+ <b>GatewayPorts</b> setting. However, an explicit <u>bind_address</u> may be
+ used to bind the connection to a specific address. The
+ <u>bind_address</u> of “localhost” indicates that the listening port be
+ bound for local use only, while an empty address or ‘*’ indicates
+ that the port should be available from all interfaces.
+
+ <b>-e</b> <u>escape_char</u>
+
+ Sets the escape character for sessions with a pty (default: ‘~’).
+ The escape character is only recognized at the beginning of a
+ line. The escape character followed by a dot (‘.’) closes the
+ connection; followed by control-Z suspends the connection; and
+ followed by itself sends the escape character once. Setting the
+ character to “none” disables any escapes and makes the session
+ fully transparent.
+
+ <b>-F</b> <u>configfile</u>
+ Specifies an alternative per-user configuration file. If a
+ configuration file is given on the command line, the system-wide
+ configuration file (<u>/etc/ssh/ssh_config</u>) will be ignored. The
+ default for the per-user configuration file is <u>~/.ssh/config</u>.
+
+ <b>-f</b> Requests <b>ssh</b> to go to background just before command execution.
+ This is useful if <b>ssh</b> is going to ask for passwords or
+ passphrases, but the user wants it in the background. This
+ implies <b>-n</b>. The recommended way to start X11 programs at a
+ remote site is with something like <b>ssh</b> <b>-f</b> <b>host</b> <b>xterm</b>.
+
+ If the <b>ExitOnForwardFailure</b> configuration option is set to “yes”,
+ then a client started with <b>-f</b> will wait for all remote port
+ forwards to be successfully established before placing itself in
+ the background.
+
+ <b>-g</b> Allows remote hosts to connect to local forwarded ports.
+
+ <b>-I</b> <u>smartcard_device</u>
+
+ Specify the device <b>ssh</b> should use to communicate with a smartcard
+ used for storing the user’s private RSA key. This option is only
+ available if support for smartcard devices is compiled in
+ (default is no support).
+
+ <b>-i</b> <u>identity_file</u>
+ Selects a file from which the identity (private key) for RSA or
+ DSA authentication is read. The default is <u>~/.ssh/identity</u> for
+ protocol version 1, and <u>~/.ssh/id_rsa</u> and <u>~/.ssh/id_dsa</u> for
+ protocol version 2. Identity files may also be specified on a
+ per-host basis in the configuration file. It is possible to have
+ multiple <b>-i</b> options (and multiple identities specified in
+ configuration files).
+
+ <b>-K</b> Enables GSSAPI-based authentication and forwarding (delegation)
+ of GSSAPI credentials to the server.
+
+ <b>-k</b> Disables forwarding (delegation) of GSSAPI credentials to the
+ server.
+
+ <b>-L</b> [<u>bind_address</u>:]<u>port</u>:<u>host</u>:<u>hostport</u>
+
+ Specifies that the given port on the local (client) host is to be
+ forwarded to the given host and port on the remote side. This
+ works by allocating a socket to listen to <u>port</u> on the local side,
+ optionally bound to the specified <u>bind_address</u>. Whenever a
+ connection is made to this port, the connection is forwarded over
+ the secure channel, and a connection is made to <u>host</u> port
+ <u>hostport</u> from the remote machine. Port forwardings can also be
+ specified in the configuration file. IPv6 addresses can be
+ specified with an alternative syntax:
+ [<u>bind_address</u>/]<u>port</u>/<u>host</u>/<u>hostport</u> or by enclosing the address in
+ square brackets. Only the superuser can forward privileged
+ ports. By default, the local port is bound in accordance with
+ the <b>GatewayPorts</b> setting. However, an explicit <u>bind_address</u> may
+ be used to bind the connection to a specific address. The
+ <u>bind_address</u> of “localhost” indicates that the listening port be
+ bound for local use only, while an empty address or ‘*’ indicates
+ that the port should be available from all interfaces.
+
+ <b>-l</b> <u>login_name</u>
+
+ Specifies the user to log in as on the remote machine. This also
+ may be specified on a per-host basis in the configuration file.
+
+ <b>-M</b> Places the <b>ssh</b> client into “master” mode for connection sharing.
+ Multiple <b>-M</b> options places <b>ssh</b> into “master” mode with
+ confirmation required before slave connections are accepted.
+ Refer to the description of <b>ControlMaster</b> in ssh_config(5) for
+ details.
+
+ <b>-m</b> <u>mac_spec</u>
+
+ Additionally, for protocol version 2 a comma-separated list of
+ MAC (message authentication code) algorithms can be specified in
+ order of preference. See the <b>MACs</b> keyword for more information.
+
+ <b>-N</b> Do not execute a remote command. This is useful for just
+ forwarding ports (protocol version 2 only).
+
+ <b>-n</b> Redirects stdin from <u>/dev/null</u> (actually, prevents reading from
+ stdin). This must be used when <b>ssh</b> is run in the background. A
+ common trick is to use this to run X11 programs on a remote
+ machine. For example, <b>ssh</b> <b>-n</b> <b>shadows.cs.hut.fi</b> <b>emacs</b> <b>&amp;</b> will
+ start an emacs on shadows.cs.hut.fi, and the X11 connection will
+ be automatically forwarded over an encrypted channel. The <b>ssh</b>
+
+ program will be put in the background. (This does not work if
+ <b>ssh</b> needs to ask for a password or passphrase; see also the <b>-f</b>
+ option.)
+
+ <b>-O</b> <u>ctl_cmd</u>
+ Control an active connection multiplexing master process. When
+ the <b>-O</b> option is specified, the <u>ctl_cmd</u> argument is interpreted
+ and passed to the master process. Valid commands are: “check”
+ (check that the master process is running) and “exit” (request
+ the master to exit).
+
+ <b>-o</b> <u>option</u>
+
+ Can be used to give options in the format used in the
+ configuration file. This is useful for specifying options for
+ which there is no separate command-line flag. For full details
+ of the options listed below, and their possible values, see
+ ssh_config(5).
+
+ AddressFamily
+ BatchMode
+ BindAddress
+ ChallengeResponseAuthentication
+ CheckHostIP
+ Cipher
+ Ciphers
+ ClearAllForwardings
+ Compression
+ CompressionLevel
+ ConnectionAttempts
+ ConnectTimeout
+ ControlMaster
+ ControlPath
+ DynamicForward
+ EscapeChar
+ ExitOnForwardFailure
+ ForwardAgent
+ ForwardX11
+ ForwardX11Trusted
+ GatewayPorts
+ GlobalKnownHostsFile
+ GSSAPIAuthentication
+ GSSAPIDelegateCredentials
+ HashKnownHosts
+ Host
+ HostbasedAuthentication
+ HostKeyAlgorithms
+ HostKeyAlias
+ HostName
+ IdentityFile
+ IdentitiesOnly
+ KbdInteractiveDevices
+ LocalCommand
+ LocalForward
+ LogLevel
+ MACs
+ NoHostAuthenticationForLocalhost
+ NumberOfPasswordPrompts
+ PasswordAuthentication
+ PermitLocalCommand
+ Port
+ PreferredAuthentications
+ Protocol
+ ProxyCommand
+ PubkeyAuthentication
+ RekeyLimit
+ RemoteForward
+ RhostsRSAAuthentication
+ RSAAuthentication
+ SendEnv
+ ServerAliveInterval
+ ServerAliveCountMax
+ SmartcardDevice
+ StrictHostKeyChecking
+ TCPKeepAlive
+ Tunnel
+ TunnelDevice
+ UsePrivilegedPort
+ User
+ UserKnownHostsFile
+ VerifyHostKeyDNS
+ VisualHostKey
+ XAuthLocation
+
+ <b>-p</b> <u>port</u>
+ Port to connect to on the remote host. This can be specified on
+ a per-host basis in the configuration file.
+
+ <b>-q</b> Quiet mode. Causes most warning and diagnostic messages to be
+ suppressed. Only fatal errors are displayed. If a second <b>-q</b> is
+ given then even fatal errors are suppressed, except for those
+ produced due solely to bad arguments.
+
+ <b>-R</b> [<u>bind_address</u>:]<u>port</u>:<u>host</u>:<u>hostport</u>
+
+ Specifies that the given port on the remote (server) host is to
+ be forwarded to the given host and port on the local side. This
+ works by allocating a socket to listen to <u>port</u> on the remote
+ side, and whenever a connection is made to this port, the
+ connection is forwarded over the secure channel, and a connection
+ is made to <u>host</u> port <u>hostport</u> from the local machine.
+
+ Port forwardings can also be specified in the configuration file.
+ Privileged ports can be forwarded only when logging in as root on
+ the remote machine. IPv6 addresses can be specified by enclosing
+ the address in square braces or using an alternative syntax:
+ [<u>bind_address</u>/]<u>host</u>/<u>port</u>/<u>hostport</u>.
+
+ By default, the listening socket on the server will be bound to
+ the loopback interface only. This may be overridden by
+ specifying a <u>bind_address</u>. An empty <u>bind_address</u>, or the address
+ ‘*’, indicates that the remote socket should listen on all
+ interfaces. Specifying a remote <u>bind_address</u> will only succeed
+ if the server’s <b>GatewayPorts</b> option is enabled (see
+ sshd_config(5)).
+
+ If the <u>port</u> argument is ‘0’, the listen port will be dynamically
+ allocated on the server and reported to the client at run time.
+
+ <b>-S</b> <u>ctl_path</u>
+
+ Specifies the location of a control socket for connection
+ sharing, or the string “none” to disable connection sharing.
+ Refer to the description of <b>ControlPath</b> and <b>ControlMaster</b> in
+ ssh_config(5) for details.
+
+ <b>-s</b> May be used to request invocation of a subsystem on the remote
+ system. Subsystems are a feature of the SSH2 protocol which
+ facilitate the use of SSH as a secure transport for other
+ applications (eg. sftp(1)). The subsystem is specified as the
+ remote command.
+
+ <b>-T</b> Disable pseudo-tty allocation.
+
+ <b>-t</b> Force pseudo-tty allocation. This can be used to execute
+ arbitrary screen-based programs on a remote machine, which can be
+ very useful, e.g. when implementing menu services. Multiple <b>-t</b>
+
+ options force tty allocation, even if <b>ssh</b> has no local tty.
+
+ <b>-V</b> Display the version number and exit.
+
+ <b>-v</b> Verbose mode. Causes <b>ssh</b> to print debugging messages about its
+ progress. This is helpful in debugging connection,
+ authentication, and configuration problems. Multiple <b>-v</b> options
+ increase the verbosity. The maximum is 3.
+
+ <b>-w</b> <u>local_tun</u>[:<u>remote_tun</u>]
+ Requests tunnel device forwarding with the specified tun(4)
+ devices between the client (<u>local_tun</u>) and the server
+ (<u>remote_tun</u>).
+
+ The devices may be specified by numerical ID or the keyword
+ “any”, which uses the next available tunnel device. If
+ <u>remote_tun</u> is not specified, it defaults to “any”. See also the
+ <b>Tunnel</b> and <b>TunnelDevice</b> directives in ssh_config(5). If the
+ <b>Tunnel</b> directive is unset, it is set to the default tunnel mode,
+ which is “point-to-point”.
+
+ <b>-X</b> Enables X11 forwarding. This can also be specified on a per-host
+ basis in a configuration file.
+
+ X11 forwarding should be enabled with caution. Users with the
+ ability to bypass file permissions on the remote host (for the
+ user’s X authorization database) can access the local X11 display
+ through the forwarded connection. An attacker may then be able
+ to perform activities such as keystroke monitoring.
+
+ For this reason, X11 forwarding is subjected to X11 SECURITY
+ extension restrictions by default. Please refer to the <b>ssh</b> <b>-Y</b>
+
+ option and the <b>ForwardX11Trusted</b> directive in ssh_config(5) for
+ more information.
+
+ <b>-x</b> Disables X11 forwarding.
+
+ <b>-Y</b> Enables trusted X11 forwarding. Trusted X11 forwardings are not
+ subjected to the X11 SECURITY extension controls.
+
+ <b>-y</b> Send log information using the syslog(3) system module. By
+ default this information is sent to stderr.
+
+ <b>ssh</b> may additionally obtain configuration data from a per-user
+ configuration file and a system-wide configuration file. The file format
+ and configuration options are described in ssh_config(5).
+
+ <b>ssh</b> exits with the exit status of the remote command or with 255 if an
+ error occurred.</pre>
+<p><b>AUTHENTICATION</b></p>
+<pre> The OpenSSH SSH client supports SSH protocols 1 and 2. Protocol 2 is the
+ default, with <b>ssh</b> falling back to protocol 1 if it detects protocol 2 is
+ unsupported. These settings may be altered using the <b>Protocol</b> option in
+ ssh_config(5), or enforced using the <b>-1</b> and <b>-2</b> options (see above). Both
+ protocols support similar authentication methods, but protocol 2 is
+ preferred since it provides additional mechanisms for confidentiality
+ (the traffic is encrypted using AES, 3DES, Blowfish, CAST128, or Arcfour)
+ and integrity (hmac-md5, hmac-sha1, umac-64, hmac-ripemd160). Protocol 1
+ lacks a strong mechanism for ensuring the integrity of the connection.
+
+ The methods available for authentication are: GSSAPI-based
+ authentication, host-based authentication, public key authentication,
+ challenge-response authentication, and password authentication.
+ Authentication methods are tried in the order specified above, though
+ protocol 2 has a configuration option to change the default order:
+ <b>PreferredAuthentications</b>.
+
+ Host-based authentication works as follows: If the machine the user logs
+ in from is listed in <u>/etc/hosts.equiv</u> or <u>/etc/ssh/shosts.equiv</u> on the
+ remote machine, and the user names are the same on both sides, or if the
+ files <u>~/.rhosts</u> or <u>~/.shosts</u> exist in the user’s home directory on the
+ remote machine and contain a line containing the name of the client
+ machine and the name of the user on that machine, the user is considered
+ for login. Additionally, the server <u>must</u> be able to verify the client’s
+ host key (see the description of <u>/etc/ssh/ssh_known_hosts</u> and
+ <u>~/.ssh/known_hosts</u>, below) for login to be permitted. This
+ authentication method closes security holes due to IP spoofing, DNS
+ spoofing, and routing spoofing. [Note to the administrator:
+ <u>/etc/hosts.equiv</u>, <u>~/.rhosts</u>, and the rlogin/rsh protocol in general, are
+ inherently insecure and should be disabled if security is desired.]
+
+ Public key authentication works as follows: The scheme is based on
+ public-key cryptography, using cryptosystems where encryption and
+ decryption are done using separate keys, and it is unfeasible to derive
+ the decryption key from the encryption key. The idea is that each user
+ creates a public/private key pair for authentication purposes. The
+ server knows the public key, and only the user knows the private key.
+ <b>ssh</b> implements public key authentication protocol automatically, using
+ either the RSA or DSA algorithms. Protocol 1 is restricted to using only
+ RSA keys, but protocol 2 may use either. The <u>HISTORY</u> section of ssl(8)
+ (on non-OpenBSD systems, <a href="http://www.openbsd.org/cgi-bin/man.cgi?query=ssl&sektion=8#HISTORY">see</a>)
+ contains a brief discussion of the two algorithms.
+
+ The file <u>~/.ssh/authorized_keys</u> lists the public keys that are permitted
+ for logging in. When the user logs in, the <b>ssh</b> program tells the server
+ which key pair it would like to use for authentication. The client
+ proves that it has access to the private key and the server checks that
+ the corresponding public key is authorized to accept the account.
+
+ The user creates his/her key pair by running ssh-keygen(1). This stores
+ the private key in <u>~/.ssh/identity</u> (protocol 1), <u>~/.ssh/id_dsa</u> (protocol
+ 2 DSA), or <u>~/.ssh/id_rsa</u> (protocol 2 RSA) and stores the public key in
+ <u>~/.ssh/identity.pub</u> (protocol 1), <u>~/.ssh/id_dsa.pub</u> (protocol 2 DSA), or
+ <u>~/.ssh/id_rsa.pub</u> (protocol 2 RSA) in the user’s home directory. The
+ user should then copy the public key to <u>~/.ssh/authorized_keys</u> in his/her
+ home directory on the remote machine. The <u>authorized_keys</u> file
+ corresponds to the conventional <u>~/.rhosts</u> file, and has one key per line,
+ though the lines can be very long. After this, the user can log in
+ without giving the password.
+
+ The most convenient way to use public key authentication may be with an
+ authentication agent. See ssh-agent(1) for more information.
+
+ Challenge-response authentication works as follows: The server sends an
+ arbitrary "challenge" text, and prompts for a response. Protocol 2
+ allows multiple challenges and responses; protocol 1 is restricted to
+ just one challenge/response. Examples of challenge-response
+ authentication include BSD Authentication (see login.conf(5)) and PAM
+ (some non-OpenBSD systems).
+
+ Finally, if other authentication methods fail, <b>ssh</b> prompts the user for a
+ password. The password is sent to the remote host for checking; however,
+ since all communications are encrypted, the password cannot be seen by
+ someone listening on the network.
+
+ <b>ssh</b> automatically maintains and checks a database containing
+ identification for all hosts it has ever been used with. Host keys are
+ stored in <u>~/.ssh/known_hosts</u> in the user’s home directory. Additionally,
+ the file <u>/etc/ssh/ssh_known_hosts</u> is automatically checked for known
+ hosts. Any new hosts are automatically added to the user’s file. If a
+ host’s identification ever changes, <b>ssh</b> warns about this and disables
+ password authentication to prevent server spoofing or man-in-the-middle
+ attacks, which could otherwise be used to circumvent the encryption. The
+ <b>StrictHostKeyChecking</b> option can be used to control logins to machines
+ whose host key is not known or has changed.
+
+ When the user’s identity has been accepted by the server, the server
+ either executes the given command, or logs into the machine and gives the
+ user a normal shell on the remote machine. All communication with the
+ remote command or shell will be automatically encrypted.
+
+ If a pseudo-terminal has been allocated (normal login session), the user
+ may use the escape characters noted below.
+
+ If no pseudo-tty has been allocated, the session is transparent and can
+ be used to reliably transfer binary data. On most systems, setting the
+ escape character to “none” will also make the session transparent even if
+ a tty is used.
+
+ The session terminates when the command or shell on the remote machine
+ exits and all X11 and TCP connections have been closed.</pre>
+<p><b>ESCAPE</b> <b>CHARACTERS</b></p>
+<pre> When a pseudo-terminal has been requested, <b>ssh</b> supports a number of
+ functions through the use of an escape character.
+
+ A single tilde character can be sent as <b>~~</b> or by following the tilde by a
+ character other than those described below. The escape character must
+ always follow a newline to be interpreted as special. The escape
+ character can be changed in configuration files using the <b>EscapeChar</b>
+ configuration directive or on the command line by the <b>-e</b> option.
+
+ The supported escapes (assuming the default ‘~’) are:
+
+ <b>~.</b> Disconnect.
+
+ <b>~^Z</b> Background <b>ssh</b>.
+
+ <b>~#</b> List forwarded connections.
+
+ <b>~&amp;</b> Background <b>ssh</b> at logout when waiting for forwarded connection /
+ X11 sessions to terminate.
+
+ <b>~?</b> Display a list of escape characters.
+
+ <b>~B</b> Send a BREAK to the remote system (only useful for SSH protocol
+ version 2 and if the peer supports it).
+
+ <b>~C</b> Open command line. Currently this allows the addition of port
+ forwardings using the <b>-L</b>, <b>-R</b> and <b>-D</b> options (see above). It also
+ allows the cancellation of existing remote port-forwardings using
+ <b>-KR</b>[<u>bind_address</u>:]<u>port</u>. <b>!</b><u>command</u> allows the user to execute a
+ local command if the <b>PermitLocalCommand</b> option is enabled in
+ ssh_config(5). Basic help is available, using the <b>-h</b> option.
+
+ <b>~R</b> Request rekeying of the connection (only useful for SSH protocol
+ version 2 and if the peer supports it).
+</pre>
+<p><b>TCP</b> <b>FORWARDING</b></p>
+<pre> Forwarding of arbitrary TCP connections over the secure channel can be
+ specified either on the command line or in a configuration file. One
+ possible application of TCP forwarding is a secure connection to a mail
+ server; another is going through firewalls.
+
+ In the example below, we look at encrypting communication between an IRC
+ client and server, even though the IRC server does not directly support
+ encrypted communications. This works as follows: the user connects to
+ the remote host using <b>ssh</b>, specifying a port to be used to forward
+ connections to the remote server. After that it is possible to start the
+ service which is to be encrypted on the client machine, connecting to the
+ same local port, and <b>ssh</b> will encrypt and forward the connection.
+
+ The following example tunnels an IRC session from client machine
+ “127.0.0.1” (localhost) to remote server “server.example.com”:
+
+ $ ssh -f -L 1234:localhost:6667 server.example.com sleep 10
+ $ irc -c ’#users’ -p 1234 pinky 127.0.0.1
+
+ This tunnels a connection to IRC server “server.example.com”, joining
+ channel “#users”, nickname “pinky”, using port 1234. It doesn’t matter
+ which port is used, as long as it’s greater than 1023 (remember, only
+ root can open sockets on privileged ports) and doesn’t conflict with any
+ ports already in use. The connection is forwarded to port 6667 on the
+ remote server, since that’s the standard port for IRC services.
+
+ The <b>-f</b> option backgrounds <b>ssh</b> and the remote command “sleep 10” is
+ specified to allow an amount of time (10 seconds, in the example) to
+ start the service which is to be tunnelled. If no connections are made
+ within the time specified, <b>ssh</b> will exit.
+</pre>
+<p><b>X11</b> <b>FORWARDING</b></p>
+<pre> If the <b>ForwardX11</b> variable is set to “yes” (or see the description of the
+ <b>-X</b>, <b>-x</b>, and <b>-Y</b> options above) and the user is using X11 (the DISPLAY
+ environment variable is set), the connection to the X11 display is
+ automatically forwarded to the remote side in such a way that any X11
+ programs started from the shell (or command) will go through the
+ encrypted channel, and the connection to the real X server will be made
+ from the local machine. The user should not manually set DISPLAY.
+ Forwarding of X11 connections can be configured on the command line or in
+ configuration files.
+
+ The DISPLAY value set by <b>ssh</b> will point to the server machine, but with a
+ display number greater than zero. This is normal, and happens because
+ <b>ssh</b> creates a “proxy” X server on the server machine for forwarding the
+ connections over the encrypted channel.
+
+ <b>ssh</b> will also automatically set up Xauthority data on the server machine.
+ For this purpose, it will generate a random authorization cookie, store
+ it in Xauthority on the server, and verify that any forwarded connections
+ carry this cookie and replace it by the real cookie when the connection
+ is opened. The real authentication cookie is never sent to the server
+ machine (and no cookies are sent in the plain).
+
+ If the <b>ForwardAgent</b> variable is set to “yes” (or see the description of
+ the <b>-A</b> and <b>-a</b> options above) and the user is using an authentication
+ agent, the connection to the agent is automatically forwarded to the
+ remote side.
+</pre><p id="toptoc7"><b>VERIFYING</b> <b>HOST</b> <b>KEYS</b></p>
+<pre> When connecting to a server for the first time, a fingerprint of the
+ server’s public key is presented to the user (unless the option
+ <b>StrictHostKeyChecking</b> has been disabled). Fingerprints can be determined
+ using ssh-keygen(1):
+
+ $ ssh-keygen -l -f /etc/ssh/ssh_host_rsa_key
+
+ If the fingerprint is already known, it can be matched and the key can be
+ accepted or rejected. Because of the difficulty of comparing host keys
+ just by looking at hex strings, there is also support to compare host
+ keys visually, using <u>random</u> <u>art</u>. By setting the <b>VisualHostKey</b> option to
+ “yes”, a small ASCII graphic gets displayed on every login to a server,
+ no matter if the session itself is interactive or not. By learning the
+ pattern a known server produces, a user can easily find out that the host
+ key has changed when a completely different pattern is displayed.
+ Because these patterns are not unambiguous however, a pattern that looks
+ similar to the pattern remembered only gives a good probability that the
+ host key is the same, not guaranteed proof.
+
+ To get a listing of the fingerprints along with their random art for all
+ known hosts, the following command line can be used:
+
+ $ ssh-keygen -lv -f ~/.ssh/known_hosts
+
+ If the fingerprint is unknown, an alternative method of verification is
+ available: SSH fingerprints verified by DNS. An additional resource
+ record (RR), SSHFP, is added to a zonefile and the connecting client is
+ able to match the fingerprint with that of the key presented.
+
+ In this example, we are connecting a client to a server,
+ “host.example.com”. The SSHFP resource records should first be added to
+ the zonefile for host.example.com:
+
+ $ ssh-keygen -r host.example.com.
+
+ The output lines will have to be added to the zonefile. To check that
+ the zone is answering fingerprint queries:
+
+ $ dig -t SSHFP host.example.com
+
+ Finally the client connects:
+
+ $ ssh -o "VerifyHostKeyDNS ask" host.example.com
+ [...]
+ Matching host key fingerprint found in DNS.
+ Are you sure you want to continue connecting (yes/no)?
+
+ See the <b>VerifyHostKeyDNS</b> option in ssh_config(5) for more information.</pre>
+<p><b>SSH-BASED</b> <b>VIRTUAL</b> <b>PRIVATE</b> <b>NETWORKS</b></p>
+<pre> <b>ssh</b> contains support for Virtual Private Network (VPN) tunnelling using
+ the tun(4) network pseudo-device, allowing two networks to be joined
+ securely. The sshd_config(5) configuration option <b>PermitTunnel</b> controls
+ whether the server supports this, and at what level (layer 2 or 3
+ traffic).
+
+ The following example would connect client network 10.0.50.0/24 with
+ remote network 10.0.99.0/24 using a point-to-point connection from
+ 10.1.1.1 to 10.1.1.2, provided that the SSH server running on the gateway
+ to the remote network, at 192.168.1.15, allows it.
+
+ On the client:
+
+ # ssh -f -w 0:1 192.168.1.15 true
+ # ifconfig tun0 10.1.1.1 10.1.1.2 netmask 255.255.255.252
+ # route add 10.0.99.0/24 10.1.1.2
+
+ On the server:
+
+ # ifconfig tun1 10.1.1.2 10.1.1.1 netmask 255.255.255.252
+ # route add 10.0.50.0/24 10.1.1.1
+
+ Client access may be more finely tuned via the <u>/root/.ssh/authorized_keys</u>
+
+ file (see below) and the <b>PermitRootLogin</b> server option. The following
+ entry would permit connections on tun(4) device 1 from user “jane” and on
+ tun device 2 from user “john”, if <b>PermitRootLogin</b> is set to
+ “forced-commands-only”:
+
+ tunnel="1",command="sh /etc/netstart tun1" ssh-rsa ... jane
+ tunnel="2",command="sh /etc/netstart tun2" ssh-rsa ... john
+
+ Since an SSH-based setup entails a fair amount of overhead, it may be
+ more suited to temporary setups, such as for wireless VPNs. More
+ permanent VPNs are better provided by tools such as ipsecctl(8) and
+ isakmpd(8).</pre>
+<p><b>ENVIRONMENT</b></p><pre> <b>ssh</b> will normally set the following environment variables:
+
+ DISPLAY The DISPLAY variable indicates the location of the
+ X11 server. It is automatically set by <b>ssh</b> to
+ point to a value of the form “hostname:n”, where
+ “hostname” indicates the host where the shell runs,
+ and ‘n’ is an integer ≥ 1. <b>ssh</b> uses this special
+ value to forward X11 connections over the secure
+ channel. The user should normally not set DISPLAY
+ explicitly, as that will render the X11 connection
+ insecure (and will require the user to manually
+ copy any required authorization cookies).
+
+ HOME Set to the path of the user’s home directory.
+
+ LOGNAME Synonym for USER; set for compatibility with
+ systems that use this variable.
+
+ MAIL Set to the path of the user’s mailbox.
+
+ PATH Set to the default PATH, as specified when
+ compiling <b>ssh</b>.
+
+ SSH_ASKPASS If <b>ssh</b> needs a passphrase, it will read the
+ passphrase from the current terminal if it was run
+ from a terminal. If <b>ssh</b> does not have a terminal
+ associated with it but DISPLAY and SSH_ASKPASS are
+ set, it will execute the program specified by
+ SSH_ASKPASS and open an X11 window to read the
+ passphrase. This is particularly useful when
+ calling <b>ssh</b> from a <u>.xsession</u> or related script.
+ (Note that on some machines it may be necessary to
+ redirect the input from <u>/dev/null</u> to make this
+ work.)
+
+ SSH_AUTH_SOCK Identifies the path of a UNIX-domain socket used to
+ communicate with the agent.
+
+ SSH_CONNECTION Identifies the client and server ends of the
+ connection. The variable contains four space-
+ separated values: client IP address, client port
+ number, server IP address, and server port number.
+
+ SSH_ORIGINAL_COMMAND This variable contains the original command line if
+ a forced command is executed. It can be used to
+ extract the original arguments.
+
+ SSH_TTY This is set to the name of the tty (path to the
+ device) associated with the current shell or
+ command. If the current session has no tty, this
+ variable is not set.
+
+ TZ This variable is set to indicate the present time
+ zone if it was set when the daemon was started
+ (i.e. the daemon passes the value on to new
+ connections).
+
+ USER Set to the name of the user logging in.
+
+ Additionally, <b>ssh</b> reads <u>~/.ssh/environment</u>, and adds lines of the format
+ “VARNAME=value” to the environment if the file exists and users are
+ allowed to change their environment. For more information, see the
+ <b>PermitUserEnvironment</b> option in sshd_config(5).
+
+
+</pre>
+<h4 id="toptoc10"><b>FILES</b></h4><pre> ~/.rhosts
+ This file is used for host-based authentication (see above). On
+ some machines this file may need to be world-readable if the
+ user’s home directory is on an NFS partition, because sshd(8)
+ reads it as root. Additionally, this file must be owned by the
+ user, and must not have write permissions for anyone else. The
+ recommended permission for most machines is read/write for the
+ user, and not accessible by others.
+
+ ~/.shosts
+ This file is used in exactly the same way as <u>.rhosts</u>, but allows
+ host-based authentication without permitting login with
+ rlogin/rsh.
+
+ ~/.ssh/
+ This directory is the default location for all user-specific
+ configuration and authentication information. There is no
+ general requirement to keep the entire contents of this directory
+ secret, but the recommended permissions are read/write/execute
+ for the user, and not accessible by others.
+
+ ~/.ssh/authorized_keys
+
+ Lists the public keys (RSA/DSA) that can be used for logging in
+ as this user. The format of this file is described in the
+ sshd(8) manual page. This file is not highly sensitive, but the
+ recommended permissions are read/write for the user, and not
+ accessible by others.
+
+ ~/.ssh/config
+ This is the per-user configuration file. The file format and
+ configuration options are described in ssh_config(5). Because of
+ the potential for abuse, this file must have strict permissions:
+ read/write for the user, and not accessible by others. It may be
+ group-writable provided that the group in question contains only
+ the user.
+
+ ~/.ssh/environment
+ Contains additional definitions for environment variables; see
+ <u>ENVIRONMENT</u>, above.
+
+ ~/.ssh/identity
+
+ ~/.ssh/id_dsa
+ ~/.ssh/id_rsa
+ Contains the private key for authentication. These files contain
+ sensitive data and should be readable by the user but not
+ accessible by others (read/write/execute). <b>ssh</b> will simply
+ ignore a private key file if it is accessible by others. It is
+ possible to specify a passphrase when generating the key which
+ will be used to encrypt the sensitive part of this file using
+ 3DES.
+
+ ~/.ssh/identity.pub
+ ~/.ssh/id_dsa.pub
+ ~/.ssh/id_rsa.pub
+
+ Contains the public key for authentication. These files are not
+ sensitive and can (but need not) be readable by anyone.
+
+ ~/.ssh/known_hosts
+ Contains a list of host keys for all hosts the user has logged
+ into that are not already in the systemwide list of known host
+ keys. See sshd(8) for further details of the format of this
+ file.
+
+ ~/.ssh/rc
+ Commands in this file are executed by <b>ssh</b> when the user logs in,
+ just before the user’s shell (or command) is started. See the
+ sshd(8) manual page for more information.
+
+ /etc/hosts.equiv
+ This file is for host-based authentication (see above). It
+ should only be writable by root.
+
+ /etc/ssh/shosts.equiv
+ This file is used in exactly the same way as <u>hosts.equiv</u>, but
+ allows host-based authentication without permitting login with
+ rlogin/rsh.
+
+ /etc/ssh/ssh_config
+
+ Systemwide configuration file. The file format and configuration
+ options are described in ssh_config(5).
+
+ /etc/ssh/ssh_host_key
+ /etc/ssh/ssh_host_dsa_key
+ /etc/ssh/ssh_host_rsa_key
+ These three files contain the private parts of the host keys and
+ are used for host-based authentication. If protocol version 1 is
+ used, <b>ssh</b> must be setuid root, since the host key is readable
+ only by root. For protocol version 2, <b>ssh</b> uses ssh-keysign(8) to
+ access the host keys, eliminating the requirement that <b>ssh</b> be
+ setuid root when host-based authentication is used. By default
+ <b>ssh</b> is not setuid root.
+
+ /etc/ssh/ssh_known_hosts
+
+ Systemwide list of known host keys. This file should be prepared
+ by the system administrator to contain the public host keys of
+ all machines in the organization. It should be world-readable.
+ See sshd(8) for further details of the format of this file.
+
+ /etc/ssh/sshrc
+ Commands in this file are executed by <b>ssh</b> when the user logs in,
+ just before the user’s shell (or command) is started. See the
+ sshd(8) manual page for more information.</pre>
+<p><i>&ldquo;Talent is hitting a target no-one else can hit, genius is hitting a target no-one else can see&rdquo; - Schopenhauer</i><br>
+ <br>
+ <b> Related</b>:<br>
+ <br>
+scp(1), sftp(1), ssh-add(1), ssh-agent(1), ssh-argv0(1), ssh-keygen(1),
+ssh-keyscan(1), ssh-vulnkey(1), tun(4), hosts.equiv(5), ssh_config(5),
+ssh-keysign(8), sshd(8)</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/su.html b/help/en/bash/su.html
new file mode 100644
index 0000000..c6d9d14
--- /dev/null
+++ b/help/en/bash/su.html
@@ -0,0 +1,124 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>su MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> su</h1>
+<p>Substitute user identity<br>
+ Run a command with substitute user and
+ group id, allow one user to temporarily become another user. It runs a command
+ (often an interactive shell) with the real and effective user id, group id,
+and supplemental groups of a given <i>user</i>. </p>
+<pre>Syntax
+ su [<em>options</em>]... [<em>user</em> [<em>arg</em>]...]
+
+Options
+
+-c <em>COMMAND</em>
+--command=<em>COMMAND</em>
+ Pass <em>COMMAND</em>, a single command line to run, to the shell with a
+ -c option instead of starting an interactive shell.
+
+-f
+--fast
+ Pass the `-f' option to the shell. This probably only makes sense
+ if the shell run is `csh' or `tcsh', for which the `-f' option
+ prevents reading the startup file (`.cshrc'). With Bourne-like
+ shells, the `-f' option disables file name pattern expansion
+ (globbing), which is not likely to be useful.
+
+-
+-l
+--login
+ Make the shell a login shell. This means the following. Unset all
+ environment variables except `TERM', `HOME', and `SHELL' (which
+ are set as described above), and `USER' and `LOGNAME' (which are
+ set, even for the super-user, as described above), and set `PATH'
+ to a compiled-in default value. Change to USER's home directory.
+ Prepend `-' to the shell's name, intended to make it read its
+ login startup file(s).
+
+-m
+-p
+--preserve-environment
+ Do not change the environment variables `HOME', `USER', `LOGNAME',
+ or `SHELL'. Run the shell given in the environment variable
+ `SHELL' instead of the shell from USER's passwd entry, unless the
+ user running `su' is not the superuser and USER's shell is
+ restricted. A "restricted shell" is one that is not listed in the
+ file `/etc/shells', or in a compiled-in list if that file does not
+ exist. Parts of what this option does can be overridden by
+ `--login' and `--shell'.
+
+-s <em>SHELL</em>
+--shell=<em>SHELL</em>
+ Run <em>SHELL</em> instead of the shell from USER's passwd entry, unless
+ the user running `su' is not the superuser and USER's shell is
+ restricted (see `-m' just above).</pre>
+<p> If no <i>user</i> is given, the default is 'root', the super-user. <br>
+ <br>
+ The shell to use is taken from user's 'passwd' entry, or /bin/sh if none is
+ specified there.<br>
+ <br>
+ If USER has a password, `su' prompts for the password unless run by a user with
+ effective user id of zero (the super-user). <br>
+ <br>
+ By default, su does not change the current directory. It sets the environment
+ variables `HOME' and `SHELL' from the password entry for USER, and if USER is
+ not the super-user, sets `USER' and `LOGNAME' to USER. <br>
+ <br>
+ By default, the shell is not a login shell. Any additional ARGs are passed as
+ additional arguments to the shell. <br>
+ <br>
+ GNU su does not treat `/bin/sh' or any other shells specially (e.g., by setting
+ `argv[0]' to -su, passing `-c' only to certain shells, etc.). su can optionally
+ be compiled to use syslog to report failed, and optionally successful, su
+ attempts. (If the system supports syslog.) However, GNU su does not check
+ if the user is a member of the `wheel' group; see options above. </p>
+<p><i>"It was just like Romeo and Juliet, only it ended in tragedy"
+ - Milhouse</i><br>
+ <br>
+ <b> Related</b>:<br>
+ <br>
+ <a href="chroot.html">chroot</a> - Run a command with a different root directory<br>
+ <a href="id.html">id</a> - Print user and group id's <br>
+ <a href="logname.html">logname</a> - Print current login name<br>
+Equivalent Windows command: <a href="../term_tools/nt/runas.html">RUNAS</a> /user</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/sudo.html b/help/en/bash/sudo.html
new file mode 100644
index 0000000..5853345
--- /dev/null
+++ b/help/en/bash/sudo.html
@@ -0,0 +1,194 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>sudo MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> sudo, sudoedit - execute a command as another user </h1>
+<p>sudo allows a permitted user to execute a command as the superuser or another user, as specified in the sudoers file.</p>
+<pre>Syntax
+ sudo -K | -L | -V | -h | -k | -l | -v
+
+ sudo [-HPSb] [-a <i>auth_type</i>] [-c <i>class</i>|-] [-p <i>prompt</i>]
+ [-u username|#<i>uid</i>] {-e <i>file</i> [...] | -i | -s | <i>command</i>}
+
+ sudoedit [-S] [-a <i>auth_type</i>] [-p <i>prompt</i>] [-u <i>username</i>|#<i>uid</i>] <i>file</i> [...]
+
+Options
+ -H Set the HOME environment variable to the homedir of the target user
+ (root by default) as specified in passwd(5). By default, sudo does
+ not modify HOME (see set_home and always_set_home in sudoers(5)).
+
+ -K (sure kill) like kill (-k) except that it removes the user's timestamp
+ entirely. Like -k, this option does not require a password.
+
+ -L list defaults, list out the parameters that may be set in a Defaults
+ line along with a short description for each. This option is useful
+ in conjunction with grep(1).
+
+ -P Preserve group vector, causes sudo to preserve the invoking user's
+ group vector unaltered. By default, sudo will initialize the group
+ vector to the list of groups the target user is in. The real and
+ effective group IDs, however, are still set to match the target user.
+
+ -S stdin, read the password from the standard input instead of the terminal.
+
+ -V Version, print the version number and exit.
+ If the invoking user is already root the -V option will print out a
+ list of the defaults sudo was compiled with as well as the machine's
+ local network addresses.
+
+ -a Authentication type, use the specified authentication type when
+ validating the user, as allowed by /etc/login.conf. The system
+ administrator may specify a list of sudo-specific authentication
+ methods by adding an "auth-sudo" entry in /etc/login.conf.
+ This option is only available on systems that support BSD
+ authentication where sudo has been configured with the
+ --with-bsdauth option.
+
+ -b Background, run the given command in the background.
+ Note that if you use the -b option you cannot use shell
+ job control to manipulate the process.
+
+ -c Class, run the specified command with resources limited by
+ the specified login class. The class argument can be either a
+ class name as defined in /etc/login.conf, or a single '-' character.
+ Specifying a class of -indicates that the command should be run
+ restricted by the default login capabilities for the user the
+ command is run as. If the class argument specifies an existing user
+ class, the command must be run as root, or the sudo command must be
+ run from a shell that is already root.
+ This option is only available on systems with BSD login classes
+ where sudo has been configured with the --with-logincap option.
+
+ -e Edit, instead of running a command, the user wishes to edit one
+ or more files. In lieu of a command, the string "sudoedit" is
+ used when consulting the sudoers file. If the user is authorized
+ by sudoers the following steps are taken:
+ 1. Temporary copies are made of the files to be edited with the
+ owner set to the invoking user.
+ 2. The editor specified by the VISUAL or EDITOR environment variables
+ is run to edit the temporary files. If neither VISUAL nor EDITOR
+ are set, the program listed in the editor sudoers variable is used.
+ 3. If they have been modified, the temporary files are copied back
+ to their original location and the temporary versions are removed.
+ If the specified file does not exist, it will be created.
+ Note that unlike most commands run by sudo, the editor is run with the
+ invoking user's environment unmodified. If, for some reason, sudo is
+ unable to update a file with its edited version, the user will receive
+ a warning and the edited copy will remain in a temporary file.
+
+ -h Help, print a usage message and exit.
+
+ -i Simulate initial login, run the shell specified in the passwd(5) entry
+ of the user that the command is being run as. The command name argument
+ given to the shell begins with a - to tell the shell to run as a login shell.
+ sudo attempts to change to that user's home directory before running the shell.
+ It also initializes the environment, leaving TERM unchanged, setting HOME ,
+ SHELL , USER , LOGNAME , and PATH , and unsetting all other environment variables.
+ Note that because the shell to use is determined before the sudoers file is
+ parsed, a runas_default setting in sudoers will specify the user to run the
+ shell as but will not affect which shell is actually run.
+
+ -k Kill, invalidates the user's timestamp by setting the time on it to the epoch.
+ The next time sudo is run a password will be required.
+ This option does not require a password and was added to allow a user to
+ revoke sudo permissions from a .logout file.
+
+ -l List, list out the allowed (and forbidden) commands for the user on the current host.
+
+ -p Prompt, allows you to override the default password prompt and use a custom one.
+ The following percent ('%') escapes are supported:
+ %u expanded to the invoking user's login name
+ %U expanded to the login name of the user the command will be run as (defaults to root)
+ %h expanded to the local hostname without the domain name
+ %H expanded to the local hostname including the domain name
+ (on if the machine's hostname is fully qualified or the fqdn sudoers option is set)
+ %% two consecutive % characters are collapsed into a single % character
+
+ -s Shell, runs the shell specified by the SHELL environment variable if it is
+ set or the shell as specified in passwd(5).
+
+ -u User, causes sudo to run the specified command as a user other than root.
+ To specify a uid instead of a username, use #uid.
+ Note that if the targetpw Defaults option is set (see sudoers(5)) it is
+ not possible to run commands with a uid not listed in the password database.
+
+ -v Validate, sudo will update the user's timestamp, prompting for the user's password
+ if necessary. This extends the sudo timeout for another 5 minutes (or whatever
+ the timeout is set to in sudoers) but does not run a command.
+
+ -- Indicates that sudo should stop processing command line arguments.
+ It is most useful in conjunction with the -s flag. </pre>
+<p><b> Return Values<br>
+</b>Upon successful execution of a program, the return value from sudo will simply be the return value of the program that was executed.</p>
+<p>Otherwise, sudo quits with an exit value of 1 if there is a configuration/permission problem or if sudo cannot execute the given command. In the latter case the error string is printed to stderr. If sudo cannot stat(2) one or more entries in the user's PATH an error is printed on stderr. (If the directory does not exist or if it is not really a directory, the entry is ignored and no error is printed.) This should not happen under normal circumstances. The most common reason for stat(2) to return &quot;permission denied&quot; is if you are running an automounter and one of the directories in your PATH is on a machine that is currently unreachable. </p>
+<p>sudo utilizes the following environment variables: EDITOR, HOME, PATH,SHELL,SUDO_PROMPT, SUDO_COMMAND, SUDO_USER, SUDO_UID, SUDO_GID, SUDO_PS1, USER, VISUAL. </p>
+<p><b>Files<br>
+</b>List of who can run what<span class="telety">:
+/etc/sudoers</span> <br>
+Directory containing timestamps:<span class="telety"> /var/run/sudo</span> </p>
+<p><b>Examples</b></p>
+<p>Note: the following examples assume suitable sudoers(5) entries.</p>
+<p>To get a file listing of an unreadable directory:</p>
+<p class="code">$ sudo ls /usr/local/protected</p>
+<p>To run the last command as root, useful when you forget to use sudo for a command. <span class="code">!!</span> grabs the last run command.</p>
+<p class="code">sudo !!</p>
+<p>To list the home directory of user yazza on a machine where the file system holding ~yazza is not exported as root:</p>
+<p class="code">$ sudo -u yazza ls ~yazza</p>
+<p>To edit the index.html file as user JDoe:</p>
+<p class="code">$ sudo -u JDoe vi ~www/htdocs/index.html</p>
+<p>To shutdown a machine:</p>
+<p class="code">$ sudo shutdown -r +15 &quot;quick reboot&quot;</p>
+<p>To make a usage listing of the directories in the /home partition. Note that this runs the commands in a sub-shell to make the cd and file redirection work.</p>
+<p class="code">$ sudo sh -c &quot;cd /home ; du -s * | sort -rn &gt; USAGE&quot;</p>
+<p><i>"It was just like Romeo and Juliet, only it ended in tragedy" - Milhouse</i><br>
+ <br>
+ <b> Related</b>:<br>
+ <br>
+ <a href="grep.html">grep</a> - Search file(s) for lines that match a given pattern<br>
+<a href="su.html">su</a> - Substitute user identity<br>
+stat(2)<br>
+login_cap(3)<br>
+sudoers(5)<br>
+<a href="passwd.html">passwd</a> - Modify a user password<br>
+visudo(8) <br>
+<a href="http://www.sudo.ws/">www.sudo.ws</a> - Todd Miller, sudo maintainer<br>
+Equivalent Windows command: <a href="../term_tools/nt/runas.html">RUNAS</a> /user</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/sum.html b/help/en/bash/sum.html
new file mode 100644
index 0000000..cae356e
--- /dev/null
+++ b/help/en/bash/sum.html
@@ -0,0 +1,72 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>sum MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> sum</h1>
+<p>Print a checksum for a file.<br>
+ <br>
+ `sum' is provided for compatibility; `<a href="cksum.html">cksum</a>' is preferable
+in new applications. </p>
+<pre>Syntax
+ sum [<em>options</em>]... [file]...
+
+Options
+
+ -r
+ Use the default (BSD compatible) algorithm. This option is
+ included for compatibility with the System V `sum'. Unless `-s'
+ was also given, it has no effect.
+
+ -s
+ --sysv
+ Compute checksums using an algorithm compatible with System V
+ `sum''s default, and print file sizes in units of 512-byte blocks.</pre>
+<p>`sum' prints the checksum for each FILE followed by the number
+ of blocks in the file (rounded up). If more than one FILE is given, file names
+ are also printed (by default). (With the `--sysv' option, corresponding file
+ name are printed when there is at least one file argument.) <br>
+ <br>
+ By default, GNU `sum' computes checksums using an algorithm compatible with
+ BSD `sum' and prints file sizes in units of 1024-byte blocks.</p>
+<p><b>Related</b>:<br>
+ <br>
+<a href="cksum.html">cksum</a> - Print CRC checksum and byte counts</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/suspend.html b/help/en/bash/suspend.html
new file mode 100644
index 0000000..06275ec
--- /dev/null
+++ b/help/en/bash/suspend.html
@@ -0,0 +1,60 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>suspend MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem -->
+<h1>suspend</h1>
+<p>Suspend the execution of this shell until it receives a SIGCONT signal.</p>
+<pre>Syntax
+ suspend [-f]<br>
+Key<br> -f Do not complain if this is a login shell; just suspend anyway.</pre>
+<p> The return status is 0 unless
+the shell is a login shell and -f is not supplied, or if job control is not enabled.</p>
+<p>suspend is a bash built in command.</p>
+<p><i>&ldquo;Suspense is worse than disappointment&rdquo; - Robert Burns</i></p>
+<p><b>Related bash commands</b>:<br>
+<br>
+<a href="fg.html">fg</a> - Send job to foreground <br>
+<a href="bg.html">bg</a> - Send to background<br>
+
+<a href="jobs.html">jobs</a> - List active jobs<br>
+logout - Exit a login shell</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/symlink.html b/help/en/bash/symlink.html
new file mode 100644
index 0000000..8c15592
--- /dev/null
+++ b/help/en/bash/symlink.html
@@ -0,0 +1,125 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>symlink MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> symlink</h1>
+<p>make a new name for a file</p>
+<pre>Syntax
+ #include <unistd.h>
+
+ int symlink(const char *OldPath, const char *NewPath);</pre>
+<p><span class="body">
+ symlink creates a symbolic link named NewPath which contains the string OldPath.<br>
+ <br>
+ Symbolic links are interpreted at run-time as if the contents of the link had
+ been substituted into the path being followed to find a file or directory.<br>
+ <br>
+ Symbolic links may contain .. path components, which (if used at the start of
+ the link) refer to the parent directories of that in which the link resides.<br>
+ <br>
+ A symbolic link (also known as a soft link) may point to an existing file or
+ to a nonexistent one; the latter case is known as a dangling link.<br>
+ <br>
+ The permissions of a symbolic link are irrelevant; the ownership is ignored
+ when following the link, but is checked when removal or renaming of the link
+ is requested and the link is in a directory with the sticky bit set.<br>
+ <br>
+ If NewPath exists it will NOT be overwritten.</span><br>
+</p>
+<pre>
+RETURN VALUE
+ On success, zero is returned. On error, -1 is returned,
+ and errno is set appropriately.
+
+ERRORS
+ EPERM The filesystem containing NewPath does not support
+ the creation of symbolic links.
+
+ EFAULT OldPath or NewPath points outside your accessible
+ address space.
+
+ EACCES Write access to the directory containing NewPath is
+ not allowed for the process's effective uid, or one
+ of the directories in NewPath did not allow search
+ (execute) permission.
+
+ ENAMETOOLONG
+ OldPath or NewPath was too long.
+
+ ENOENT A directory component in NewPath does not exist or
+ is a dangling symbolic link, or OldPath is the
+ empty string.
+
+ ENOTDIR
+ A component used as a directory in NewPath is not,
+ in fact, a directory.
+
+ ENOMEM Insufficient kernel memory was available.
+
+ EROFS NewPath is on a read-only filesystem.
+
+ EEXIST NewPath already exists.
+
+ ELOOP Too many symbolic links were encountered in resolving
+ NewPath.
+
+ ENOSPC The device containing the file has no room for the
+ new directory entry.
+
+ EIO An I/O error occurred.</pre>
+<p>NOTES <br>
+ No checking of OldPath is done. <br>
+ Deleting the name referred to by a symlink will actually delete the file (unless
+ it also has other hard links). If this behaviour is not desired, use link.<br>
+ <br>
+ <i>&quot;Women might be able to fake orgasms. But men can fake whole relationships."
+ - Sharon Stone
+ </i> </p>
+<p><b>Related</b>:<br>
+ <br>
+ readlink(2)<br>
+link(2), <br>
+unlink(2), rename(2), open(2), lstat(2), <br>
+ <a href="ln.html">ln</a> - Make links between files<br>
+Equivalent Windows command:
+ <a href="../term_tools/nt/shortcut.html">SHORTCUT</a> - Create a windows shortcut (.LNK
+file)</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/sync.html b/help/en/bash/sync.html
new file mode 100644
index 0000000..f8162b8
--- /dev/null
+++ b/help/en/bash/sync.html
@@ -0,0 +1,63 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>sync MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> sync</h1>
+<p>Synchronize data on disk with memory</p>
+<pre>Syntax
+ sync</pre>
+<p>Writes any data buffered in memory out to disk. This can include
+ (but is not limited to) modified superblocks, modified inodes, and delayed reads
+ and writes. <br>
+ This must be implemented by the kernel; The `sync' program does nothing but
+ exercise the `sync' system call. The kernel keeps data in memory to avoid doing
+ (relatively slow) disk reads and writes. This improves performance, but if the
+ computer crashes, data may be lost or the filesystem corrupted as a result.
+ `sync' ensures everything in memory is written to disk. <br>
+ <br>
+ Any arguments are ignored, except for a lone `--help' or `--version'<br>
+ <br>
+ <i>&quot;The way to a mans heart is through his stomach&quot; - Fanny
+ Fern (writer) </i> </p>
+<p><b>Related</b>:<br>
+ <br>
+<a href="mount.html">mount</a> - Mount a file system</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/syntax.html b/help/en/bash/syntax.html
new file mode 100644
index 0000000..cd44393
--- /dev/null
+++ b/help/en/bash/syntax.html
@@ -0,0 +1,65 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>bash syntax</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head>
+<body>
+<div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com">
+</div>
+</form></li>
+<li><a class="rr" href="../term_tools/links/bash.html"><img src="../term_tools/images/links-r.gif" title="Linux Books, Websites etc" alt="Linux Books, Websites etc"></a></li>
+</ul>
+</div>
+<h1> bash syntax</h1>
+<pre> <a href="../term_tools/bash/syntax-parameters.html">Parameters</a> Shell parameters
+ <a href="../term_tools/bash/syntax-env.html">Variables</a> Environment variables
+ <a href="../term_tools/bash/syntax-arrays.html">Arrays</a> Array Variables
+ <a href="../term_tools/bash/syntax-permissions.html">Permissions</a> Allow or Deny actions
+ <a href="../term_tools/bash/syntax-redirection.html">Redirection</a> Spooling to and from files
+ <a href="../term_tools/bash/syntax-pipe.html">Pipes</a> Redirect the output from one command as input for another</pre>
+<p>Looping constructs:</p>
+<pre> <a href="if.html">if-then-else</a> Conditionally perform a command
+ <a href="for.html">for</a> Expand <var>words</var>, and execute commands
+ <a href="until.html">until</a> Execute commands (until error)
+ <a href="while.html">while</a> Execute commands</pre>
+<blockquote>
+<p>The <a href="break.html">break</a> and <a href="continue.html">continue</a>
+ builtins may be used to control loop execution.</p>
+</blockquote>
+<p> Evaluating expressions:</p>
+<pre> <a href="../term_tools/bash/syntax-brackets.html">Using brackets</a> to Group and expand expressions
+ <a href="../term_tools/bash/syntax-execute.html">Conditional Execution</a> Chain commands to run one after another (AND/OR)
+ <a href="../term_tools/bash/syntax-condition.html">Conditional</a> expressions
+ <a href="../term_tools/bash/syntax-math.html">Arithmetic</a> expressions
+ <a href="../term_tools/bash/syntax-expand.html">Shell expansion</a> and Pattern matching (Wildcards)
+ <a href="../term_tools/bash/syntax-quoting.html">Escape Chars, delimiters and Quotes</a>
+ <a href="../term_tools/bash/syntax-substitution.html">Command Substitution</a></pre>
+<p>Working with the bash Shell: </p>
+<pre> <a href="../term_tools/bash/syntax-script.html">Run a bash shell script</a>
+<a href="vi.html"> vi editor</a> A one page reference to the vi editor
+ <a href="../term_tools/bash/syntax-here.html">Here docs</a> Here documents
+ <a href="../term_tools/bash/syntax-keyboard.html">Keyboard</a> Cursor control - Cut &amp; paste
+ <a href="../term_tools/bash/syntax-jobs.html">Job Control</a> Suspend and resume a process
+ <a href="../term_tools/bash/syntax-prompt.html">Prompt</a> Prompt variable
+ <a href="rem.html">###</a> Comment / Remark
+ <a href="../term_tools/bash/syntax-pronounce.html">BashBangSplat</a> Pronunciation guide for unix</pre>
+<p>Note that wherever a <samp>`;'</samp> appears in the description of a command's syntax, it may be replaced with one or more newlines. </p>
+<p>For examples of all the above see my <a href="../term_tools/links/bash.html">recommended Linux books</a> </p>
+<!-- #BeginLibraryItem "/Library/foot_menu.lbi" --><div align="center"><hr size="1">
+<p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+<p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/tail.html b/help/en/bash/tail.html
new file mode 100644
index 0000000..e892ece
--- /dev/null
+++ b/help/en/bash/tail.html
@@ -0,0 +1,196 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>tail MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> tail</h1>
+<p>Output the last part of files, print the last part (10 lines by
+ default) of each FILE; <br>
+ tail reads from standard input if no files are given or when given a FILE of
+`-'.</p>
+<pre>Syntax
+ tail [<em>options</em>]... [<em>file</em>]...
+
+ tail -<em>Number</em> [<em>options</em>]... [<em>file</em>]...
+
+ tail +<em>Number</em> [<em>options</em>]... [<em>file</em>]...
+
+Options
+
+-<em>COUNT</em>
++<em>COUNT</em>
+ This option is only recognized if it is specified first. COUNT is
+ a decimal number optionally followed by a size letter (`b', `k',
+ `m') as in `-c', or `l' to mean count by lines, or other option
+ letters (`cfqv').
+
+-c <em>BYTES</em>
+--bytes=<em>BYTES</em>
+ Output the last BYTES bytes, instead of final lines. Appending
+ `b' multiplies BYTES by 512, `k' by 1024, and `m' by 1048576.
+
+-f
+--follow[=<em>HOW</em>]
+ Loop forever trying to read more characters at the end of the file,
+ presumably because the file is growing. This option is ignored
+ when reading from a pipe. If more than one file is given, `tail'
+ prints a header whenever it gets output from a different file, to
+ indicate which file that output is from.
+
+ There are two ways to specify how you'd like to track files with
+ this option, but that difference is noticeable only when a
+ followed file is removed or renamed. If you'd like to continue to
+ track the end of a growing file even after it has been unlinked,
+ use `--follow=descriptor'. This is the default behavior, but it
+ is not useful if you're tracking a log file that may be rotated
+ (removed or renamed, then reopened). In that case, use
+ `--follow=name' to track the named file by reopening it
+ periodically to see if it has been removed and recreated by some
+ other program.
+
+ No matter which method you use, if the tracked file is determined
+ to have shrunk, `tail' prints a message saying the file has been
+ truncated and resumes tracking the end of the file from the
+ newly-determined endpoint.
+
+ When a file is removed, `tail''s behavior depends on whether it is
+ following the name or the descriptor. When following by name,
+ tail can detect that a file has been removed and gives a message
+ to that effect, and if `--retry' has been specified it will
+ continue checking periodically to see if the file reappears. When
+ following a descriptor, tail does not detect that the file has
+ been unlinked or renamed and issues no message; even though the
+ file may no longer be accessible via its original name, it may
+ still be growing.
+
+ The option values `descriptor' and `name' may be specified only
+ with the long form of the option, not with `-f'.
+
+--retry
+ This option is meaningful only when following by name. Without
+ this option, when tail encounters a file that doesn't exist or is
+ otherwise inaccessible, it reports that fact and never checks it
+ again.
+
+--sleep-interval=<em>N</em>
+ Change the number of seconds to wait between iterations (the
+ default is 1). During one iteration, every specified file is
+ checked to see if it has changed size.
+
+--pid=<em>PID</em>
+ When following by name or by descriptor, you may specify the
+ process ID, PID, of the sole writer of all FILE arguments. Then,
+ shortly after that process terminates, tail will also terminate.
+ This will work properly only if the writer and the tailing process
+ are running on the same machine. For example, to save the output
+ of a build in a file and to watch the file grow, if you invoke
+ `make' and `tail' like this then the tail process will stop when
+ your build completes. Without this option, you would have had to
+ kill the `tail -f' process yourself.
+ $ make >& makerr & tail --pid=$! -f makerr
+ If you specify a PID that is not in use or that does not correspond
+ to the process that is writing to the tailed files, then `tail'
+ may terminate long before any FILEs stop growing or it may not
+ terminate until long after the real writer has terminated.
+
+--max-consecutive-size-changes=<em>N</em>
+ This option is meaningful only when following by name. Use it to
+ control how long `tail' follows the descriptor of a file that
+ continues growing at a rapid pace even after it is deleted or
+ renamed. After detecting <em>N</em> consecutive size changes for a file,
+ `open'/`fstat' the file to determine if that file name is still
+ associated with the same device/inode-number pair as before. See
+ the output of `tail --help' for the default value.
+
+--max-unchanged-stats=<em>N</em>
+ When tailing a file by name, if there have been this many
+ consecutive iterations for which the size has remained the same,
+ then `open'/`fstat' the file to determine if that file name is
+ still associated with the same device/inode-number pair as before.
+ When following a log file that is rotated this is approximately the
+ number of seconds between when tail prints the last pre-rotation
+ lines and when it prints the lines that have accumulated in the
+ new log file. See the output of `tail --help' for the default
+ value. This option is meaningful only when following by name.
+
+-n <em>N</em>
+--lines=<em>N</em>
+ Output the last N lines.
+
+-q
+-quiet
+--silent
+ Never print file name headers.
+
+-v
+--verbose
+ Always print file name headers.</pre>
+<p> If more than one FILE is specified, `tail' prints a one-line
+ header consisting of ==> FILE NAME <== before the output for each FILE. <br>
+ <br>
+ GNU `tail' can output any amount of data (some other versions of `tail' cannot).
+ It also has no `-r' option (print in reverse), since reversing a file is really
+ a different job from printing the end of a file; BSD `tail' (which is the one
+ with `-r') can only reverse files that are at most as large as its buffer, which
+ is typically 32k. A more reliable and versatile way to reverse files is the
+ GNU `<a href="../term_tools/bash/tac.html">tac</a>' command. <br>
+ <br>
+ `tail' accepts two option formats: the new one, in which numbers are arguments
+ to the options (`-n 1'), and the old one, in which the number precedes any option
+ letters (`-1' or `+1'). If any option-argument is a number N starting with a
+ `+', `tail' begins printing with the Nth item from the start of each file, instead
+ of from the end. </p>
+<p><b>Examples</b></p>
+<p>Extract the last 85 lines from a file: </p>
+<p class="telety"> tail -85 file,txt </p>
+<p>Extract lines 40-50 from a file, first using <span class="body"><a href="head.html">head</a></span> to get the first 50 lines then tail to get the last 10: </p>
+<p class="telety"> head -50 file.txt | tail -10 </p>
+<p><i>"Money will buy a pretty good dog, but it won't buy the wag
+of his tail" - Henry Wheeler Shaw</i></p>
+<p><b>Related</b>:<br>
+ <br>
+ <a href="csplit.html">csplit</a> - Split a file into context-determined pieces<br>
+ <a href="cut.html">cut</a> - Divide a file into several parts<br>
+ <a href="fmt.html">fmt</a> - Reformat paragraph text<br>
+ <a href="head.html">head</a> - Output the first part of file(s)<br>
+ <a href="join.html">join</a> - Join lines on a common field <br>
+ <a href="paste.html">paste</a> - Merge lines of files<br>
+<a href="split.html">split</a> - Split a file into fixed-size pieces </p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/tar.html b/help/en/bash/tar.html
new file mode 100644
index 0000000..59d1586
--- /dev/null
+++ b/help/en/bash/tar.html
@@ -0,0 +1,523 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>tar MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> tar</h1>
+<p>Tape ARchiver, store, list or extract files in an archive.</p>
+<pre>Syntax
+ tar [[-]<i>function</i>] [<i>options</i>] <i>filenames</i>...
+
+ tar [[-]<i>function</i>] [<i>options</i>] -C <i>directory-name</i>...
+
+ Command-line arguments that specify files to add to, extract from,
+ or list from an archive may be given as shell pattern matching strings.
+
+Functions:<i>
+</i> Exactly one of the following functions (shown in bold) must be specified:
+ <b>-A</b>
+ <b>--catenate</b>
+ <b>--concatenate</b> Append the contents of named file, which must itself be a
+ gnutar archive, to the end of the archive (erasing the old
+ end-of-archive block). This has the effect of adding the
+ files contained in the named file to the first archive,
+ rather than adding the second archive as an element of the
+ first. <i>Note</i>: This option requires a rewritable <i>tarfile</i>,
+ and therefore does not work on quarter-inch cartridge
+ tapes. (see notes below)
+ <b>-c</b>
+ <b>--create</b> Create a new archive (or truncate an old one) and write
+ the named files to it.
+ <b>-d</b>
+ <b>--diff</b>
+ <b>--compare</b> Find differences between files in the archive and
+ corresponding files in the file system.
+
+ <b>--delete</b> Delete named files from the archive.
+ (Does not work on quarter-inch tapes).
+ <b>-r</b>
+ <b>--append</b> Append files to the end of an archive.
+ (Does not work on quarter-inch tapes).
+ <b>-t</b>
+ <b>--list</b> List the contents of an archive; if <i>filename</i> arguments are
+ given, only those files are listed, otherwise the entire
+ table of contents is listed.
+ <b>-u</b>
+ <b>--update</b> Append the named files if the on-disk version has a
+ modification date more recent than their copy in the
+ archive(if any). Does not work on quarter-inch tapes.
+ <b>-x</b>
+ <b>--extract</b>
+ <b>--get</b> Extract files from an archive. The owner, modification
+ time, and file permissions are restored, if possible. If
+ no <i>file</i> arguments are given, extract all the files in the
+ archive. If a <i>filename</i> argument matches the name of a
+ directory on the tape, that directory and its contents are
+ extracted (as well as all directories under that direc-
+ tory). If the archive contains multiple entries corre-
+ sponding to the same file (see the <b>--append</b> command
+ above), the last one extracted will overwrite all earlier
+ versions.</pre>
+<blockquote>
+ <p> You can specify an argument for `<span class="telety">--file</span> (or <span class="telety">-f</span> ) whenever you use tar; this option determines
+ the name of the archive file that `tar' will work on.<br>
+ <br>
+ If you don't specify this argument, then `tar' will use a default, usually
+ some physical tape drive attached to your machine. If there is no tape drive
+ attached, or the default is not meaningful, then `tar' will print an error
+ message like one of the following:</p>
+</blockquote>
+<pre> tar: can't open /dev/rmt8 : No such device or address
+ tar: can't open /dev/rsmt0 : I/O error</pre>
+<blockquote>
+ <p><span class="body"> To avoid confusion, we recommend that you always specify
+ an archive file name by using `--file=ARCHIVE-NAME' (or `-f ARCHIVE-NAME') when
+ writing your `tar' commands. </span> </p>
+</blockquote>
+<pre> --verbose' (`-v') shows details about the results of running `tar'.</pre>
+<blockquote>
+ <p><span class="body"> This can be especially useful when the results might
+ not be obvious. For example, if you want to see the progress of `tar' as it
+ writes files into the archive, you can use the `--verbose' option. In the
+ beginning, you may find it useful to use `--verbose' at all times; when you
+ are more accustomed to `tar', you will likely want to use it at certain times
+ but not at others. <br>
+ <br>
+ Sometimes, a single instance of `--verbose' on the command line will show
+ a full, `ls' style listing of an archive or files, giving sizes, owners, and
+ similar information. Other times, `--verbose' will only show files or members
+ that the particular operation is operating on at the time. In the latter case,
+ you can use `--verbose' twice in a command to get a listing such as that in
+ the former case.</span> </p>
+</blockquote>
+<p><b>Options</b></p>
+<pre>--absolute-names
+-P
+ Normally when creating an archive, `tar' strips an initial `/' from
+ member names. This option disables that behavior.
+
+--after-date
+ (See --newer.)
+
+--atime-preserve
+ Tells `tar' to preserve the access time field in a file's inode
+ when dumping it.
+
+--backup=<em>BACKUP-TYPE</em>
+ Rather than deleting files from the file system, `tar' will back
+ them up using simple or numbered backups, depending upon
+ BACKUP-TYPE.
+
+--block-number
+-R
+ With this option present, `tar' prints error messages for read
+ errors with the block number in the archive file.
+
+--blocking-factor=<em>BLOCKING</em>
+-b <em>BLOCKING</em>
+ Sets the blocking factor `tar' uses to BLOCKING x 512 bytes per
+ record.
+
+--bzip2
+-I
+ This option tells `tar' to read or write archives through `bzip2'.
+
+--checkpoint
+ This option directs `tar' to print periodic checkpoint messages as
+ it reads through the archive. Its intended for when you want a
+ visual indication that `tar' is still running, but don't want to
+ see --verbose' output.
+
+--compress
+--uncompress
+-Z
+ `tar' will use the `compress' program when reading or writing the
+ archive. This allows you to directly act on archives while saving
+ space.
+
+--confirmation
+ (See --interactive.)
+
+--dereference
+-h
+ When creating a `tar' archive, `tar' will archive the file that a
+ symbolic link points to, rather than archiving the symlink.
+
+--directory=<em>DIR</em>
+-C <em>DIR</em>
+ When this option is specified, `tar' will change its current
+ directory to DIR before performing any operations. When this
+ option is used during archive creation, it is order sensitive.
+
+--exclude=<em>PATTERN</em>
+ When performing operations, `tar' will skip files that match
+ PATTERN.
+
+--exclude-from=<em>FILE</em>
+-X <em>FILE</em>
+ Similar to --exclude, except `tar' will use the list of patterns
+ in the file <em>FILE</em>.
+
+--file=<em>ARCHIVE</em>
+-f <em>ARCHIVE</em>
+ `tar' will use the file ARCHIVE as the `tar' archive it performs
+ operations on, rather than `tar''s compilation dependent default.
+
+--files-from=<em>FILE</em>
+-T <em>FILE</em>
+ `tar' will use the contents of FILE as a list of archive members
+ or files to operate on, in addition to those specified on the
+ command-line.
+
+--force-local
+ Forces `tar' to interpret the filename given to --file as a local
+ file, even if it looks like a remote tape drive name.
+
+--group=<em>GROUP</em>
+ Files added to the `tar' archive will have a group id of GROUP,
+ rather than the group from the source file. GROUP is first decoded
+ as a group symbolic name, but if this interpretation fails, it has
+ to be a decimal numeric group ID.
+
+ Also see the comments for the --owner=USER option.
+
+--gzip
+--gunzip
+--ungzip
+-z
+ This option tells `tar' to read or write archives through `gzip',
+ allowing `tar' to directly operate on several kinds of compressed
+ archives transparently.
+
+--help
+ `tar' will print out a short message summarizing the operations and
+ options to `tar' and exit.
+
+--ignore-failed-read
+ Instructs `tar' to exit successfully if it encounters an
+ unreadable file.
+
+--ignore-umask
+ (See --preserve-permissions'; *note Writing::..)
+
+--ignore-zeros
+-i
+ With this option, `tar' will ignore zeroed blocks in the archive,
+ which normally signals EOF. *Note Reading::.
+
+--incremental
+-G
+ Used to inform `tar' that it is working with an old GNU-format
+ incremental backup archive. It is intended primarily for backwards
+ compatibility only.
+
+--info-script=<em>SCRIPT-FILE</em>
+--new-volume-script=<em>SCRIPT-FILE</em>
+-F <em>SCRIPT-FILE</em>
+ When `tar' is performing multi-tape backups, <em>SCRIPT-FILE</em> is run at
+ the end of each tape.
+
+--interactive
+--confirmation
+-w
+ Specifies that `tar' should ask the user for confirmation before
+ performing potentially destructive options, such as overwriting
+ files.
+
+--keep-old-files
+-k
+ When extracting files from an archive, `tar' will not overwrite
+ existing files if this option is present. *Note Writing::.
+
+--label=<em>NAME</em>
+-V <em>NAME</em>
+ When creating an archive, instructs `tar' to write NAME as a name
+ record in the archive. When extracting or listing archives, `tar'
+ will only operate on archives that have a label matching the
+ pattern specified in NAME.
+
+--listed-incremental=<em>SNAPSHOT-FILE</em>
+-g <em>SNAPSHOT-FILE</em>
+ During a --create' operation, specifies that the archive that
+ `tar' creates is a new GNU-format incremental backup, using
+ SNAPSHOT-FILE to determine which files to backup. With other
+ operations, informs `tar' that the archive is in incremental
+ format.
+
+--mode=<em>PERMISSIONS</em>
+ When adding files to an archive, `tar' will use <em>PERMISSIONS</em> for
+ the archive members, rather than the permissions from the files.
+ The program `chmod' and this `tar' option share the same syntax
+ for what <em>PERMISSIONS</em> might be. *Note Permissions: (fileutils)File
+ permissions. This reference also has useful information for those
+ not being overly familiar with the Unix permission system.
+
+ Of course, <em>PERMISSIONS</em> might be plainly specified as an octal
+ number. However, by using generic symbolic modifications to mode
+ bits, this allows more flexibility. For example, the value `a+rw'
+ adds read and write permissions for everybody, while retaining
+ executable bits on directories or on any other file already marked
+ as executable.
+
+--multi-volume
+-M
+ Informs `tar' that it should create or otherwise operate on a
+ multi-volume `tar' archive.
+
+--new-volume-script
+ (see -info-script)
+
+--newer=<em>DATE</em>
+--after-date=<em>DATE</em>
+-N
+ When creating an archive, `tar' will only add files that have
+ changed since <em>DATE</em>.
+
+--newer-mtime
+ In conjunction with --newer', `tar' will only add files whose
+ contents have changed (as opposed to just --newer', which will
+ also back up files for which any status information has changed).
+
+--no-recursion
+ With this option, `tar' will not recurse into directories unless a
+ directory is explicitly named as an argument to `tar'.
+
+--null
+ When `tar' is using the --files-from' option, this option
+ instructs `tar' to expect filenames terminated with `NUL', so
+ `tar' can correctly work with file names that contain newlines.
+
+--numeric-owner
+ This option will notify `tar' that it should use numeric user and
+ group IDs when creating a `tar' file, rather than names.
+
+--old-archive
+ (See --portability.)
+
+--one-file-system
+-l
+ Used when creating an archive. Prevents `tar' from recursing into
+ directories that are on different file systems from the current
+ directory.
+
+--owner=<em>USER</em>
+ Specifies that `tar' should use USER as the owner of members when
+ creating archives, instead of the user associated with the source
+ file. USER is first decoded as a user symbolic name, but if this
+ interpretation fails, it has to be a decimal numeric user ID.
+
+ There is no value indicating a missing number, and `0' usually
+ means `root'. Some people like to force `0' as the value to offer
+ in their distributions for the owner of files, because the `root'
+ user is anonymous anyway, so that might as well be the owner of
+ anonymous archives.
+
+--portability
+--old-archive
+-o
+ Tells `tar' to create an archive that is compatible with Unix V7
+ `tar'.
+
+--posix
+ Instructs `tar' to create a POSIX compliant `tar' archive.
+
+--preserve
+ Synonymous with specifying both --preserve-permissions' and
+ --same-order.
+
+--preserve-order
+ (See --same-order; *note Reading::..)
+
+--preserve-permissions
+--same-permissions
+-p
+ When `tar' is extracting an archive, it normally subtracts the
+ users' umask from the permissions specified in the archive and
+ uses that number as the permissions to create the destination
+ file. Specifying this option instructs `tar' that it should use
+ the permissions directly from the archive. *Note Writing::.
+
+--read-full-records
+-B
+ Specifies that `tar' should reblock its input, for reading from
+ pipes on systems with buggy implementations. *Note Reading::.
+
+--record-size=<em>SIZE</em>
+ Instructs `tar' to use SIZE bytes per record when accessing the
+ archive.
+
+--recursive-unlink
+ Similar to the --unlink-first option, removing existing
+ directory hierarchies before extracting directories of the same
+ name from the archive. *Note Writing::.
+
+--remove-files
+ Directs `tar' to remove the source file from the file system after
+ appending it to an archive.
+
+--rsh-command=<em>CMD</em>
+ Notifies `tar' that is should use CMD to communicate with remote
+ devices.
+
+--same-order
+--preserve-order
+-s
+ This option is an optimization for `tar' when running on machines
+ with small amounts of memory. It informs `tar' that the list of
+ file arguments has already been sorted to match the order of files
+ in the archive. *Note Reading::.
+
+--same-owner
+ When extracting an archive, `tar' will attempt to preserve the
+ owner specified in the `tar' archive with this option present.
+
+--same-permissions
+ (See --preserve-permissions; *note Writing::..)
+
+--show-omitted-dirs
+ Instructs `tar' to mention directories its skipping over when
+ operating on a `tar' archive.
+
+--sparse
+-S
+ Invokes a GNU extension when adding files to an archive that
+ handles sparse files efficiently.
+
+--starting-file=<em>NAME</em>
+-K NAME
+ This option affects extraction only; `tar' will skip extracting
+ files in the archive until it finds one that matches NAME. *Note
+ Scarce::.
+
+--suffix=<em>SUFFIX</em>
+ Alters the suffix `tar' uses when backing up files from the default
+ `~'.
+
+--tape-length=<em>NUM</em>
+-L <em>NUM</em>
+ Specifies the length of tapes that `tar' is writing as being
+ NUM x 1024 bytes long.
+
+--to-stdout
+-O
+ During extraction, `tar' will extract files to stdout rather than
+ to the file system. *Note Writing::.
+
+--totals
+ Displays the total number of bytes written after creating an
+ archive.
+
+--touch
+-m
+ Sets the modification time of extracted files to the extraction
+ time, rather than the modification time stored in the archive.
+ *Note Writing::.
+
+--uncompress
+ (See --compress.)
+
+--ungzip
+ (See --gzip.)
+
+--unlink-first
+-U
+ Direct `tar' to remove the corresponding file from the file system
+ before extracting it from the archive. *Note Writing::.
+
+--use-compress-program=<i>PROG</i>
+ Instruct `tar' to access the archive through <i>PROG</i>, which is
+ presumed to be a compression program of some sort.
+
+--verbose
+-v
+ Be more verbose about the operation.
+ This option can be specified multiple times (for some operations)
+ to increase the amount of information displayed.
+
+--verify
+-W
+ Verify that the archive was correctly written.
+
+--version
+ `tar' will print an informational message about what version it is
+ and a copyright message, some credits, and then exit.
+
+--volno-file=FILE
+ Used in conjunction with --multi-volume'. `tar' will keep track
+ of which volume of a multi-volume archive its working in FILE.</pre>
+<p><b>Examples</b></p>
+<p>Create a tar and zip the file (using the <i>create function</i>)</p>
+<pre> tar -czvf MyArchive Source_file
+or
+ tar --<b>c</b>reate --g<b>z</b>ip --<b>v</b>erbose --<b>f</b>ile=MyArchive Source_file</pre>
+<p>Extract the zip file created above:</p>
+<pre> tar <b>-x</b>zvf MyArchive Source_file
+or
+ tar --e<b>x</b>tract --gun<b>z</b>ip --<b>v</b>erbose --<b>f</b>ile=MyArchive Source_file</pre>
+<p>Create a tar in zip format with the file named as todays date/time:</p>
+<pre>tar czvf my_backup.$(date +%Y%m%d-%H%M%S).tgz /users/simon
+</pre>
+<p>A simple shell script for the above:</p>
+<pre>
+#!/bin/bash<br>tar czvf $1.$(date +%Y%m%d-%H%M%S).tgz $1<br>exit $?</pre>
+<p>Save the script as 'arc', use chmod to make it executable and then run it passing a single file or foldername:</p>
+<pre>chmod 700 arc
+./arc /users/simon</pre>
+<p><b>Notes</b></p>
+<p>Always <b>tar -t </b>before<b> tar -x </b>to check if the archive contents have been placed inside one subdirectory or will just spill all over the current directory.</p>
+<p>The -C feature does not work like historical gnutar programs, and is probably
+ untrustworthy.</p>
+<p> The -A command should work to join an arbitrary number of gnutar
+ archives together, but it does not; attempting to do so leaves the end-of-archive
+ blocks in place for the second and subsequent archives. </p>
+<p>The gnutar file format is a semi fixed width field format, and
+ the field for device numbers were designed for 16 bit (8 major, 8 minor) and
+ can not absorb our 32 bit (8 major, 16+8 minor) numbers. </p>
+<p><i>&quot;Of all forms of caution, caution in love is perhaps the
+ most fatal to true happiness&quot; - Bertrand
+ Russell </i></p>
+<p> <b> Related</b>:<br>
+ <br>
+ <a href="gzip.html">gzip</a> - Compress or decompress named file(s)<br>
+ <a href="sum.html">sum</a> - Print a checksum for a file <br>
+ <a href="unshar.html">unshar</a> - Unpack shell archive scripts <br>
+Equivalent Windows command:
+ZIP - compress files</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/tee.html b/help/en/bash/tee.html
new file mode 100644
index 0000000..e2db377
--- /dev/null
+++ b/help/en/bash/tee.html
@@ -0,0 +1,81 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>tee MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> tee</h1>
+<p>Redirect output to multiple files, copies standard input to standard
+ output and also to any files given as arguments. This is useful when you want
+not only to send some data down a pipe, but also to save a copy.</p>
+<pre>Syntax
+ tee [<em>options</em>]... [<em>file</em>]...
+
+Options
+ -a
+ --append
+ Append standard input to the given files rather than overwriting
+ them.
+
+ -i
+ --ignore-interrupts'
+ Ignore interrupt signals.
+
+Example:
+
+ ps -ax | tee processes.txt | more</pre>
+<p>If a file being written to does not already exist, it is created.
+ <br>
+ If a file being written to already exists, the data it previously contained
+ is overwritten unless the `-a' option is used.<br>
+ <br>
+ <i>"Twenty years from now, you will be more disappointed by the things you didn't
+ do than by the ones you did do. So throw off the bowlines, sail away from the
+ safe harbour. Catch the trade winds in your sails. Explore. Dream. Discover."
+ Mark
+Twain</i> </p>
+<p><b>Related</b>:<br>
+ <br>
+ <a href="echo.html">echo</a> - Display message on screen<br>
+ <a href="head.html">head</a>
+ - Output the first part of file(s)<a href="less.html"><br>
+ less</a> - Display output one screen at a time<br>
+ <a href="more.html">more</a> - Display output one screen at a time <br>
+pg - Display one page at a time</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/test.html b/help/en/bash/test.html
new file mode 100644
index 0000000..99b6a8e
--- /dev/null
+++ b/help/en/bash/test.html
@@ -0,0 +1,256 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>test MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> test</h1>
+<span class="body">Evaluate a conditional expression <var>expr</var>. </span><br>
+<pre>Syntax
+ test <i>expr</i><br> [ <i>expr</i>
+
+Options</pre>
+<p>Each operator and operand must be a separate argument. When the <code>[</code>
+ form is used, the last argument to the command must be a <code>]</code>. Expressions
+ may be combined using the following operators, listed in decreasing order of
+ precedence. </p>
+<dl>
+ <dd>
+ <dl compact>
+ <dt><code>! <var>expr</var></code>
+ </dl>
+ <dd>
+ <pre>True if <var>expr</var> is <strong>false</strong>.</pre>
+ </dd>
+ <dt><code>( <var>expr</var> )</code> </dt>
+ <dd>
+ <pre>Returns the value of <var>expr</var>. This may be used to override the
+normal precedence of operators. </pre>
+ </dd>
+ <dt><code><var>expr1</var> -a <var>expr2</var></code> </dt>
+ <dd>
+ <pre>True if both <var>expr1</var> <strong>and</strong> <var>expr2</var> are true.</pre>
+ </dd>
+ <dt><code><var>expr1</var> -o <var>expr2</var></code> </dt>
+ <dd>
+ <pre>True if either <var>expr1</var> <strong>or</strong> <var>expr2</var> is true.</pre>
+ </dd>
+</dl>
+<p><span class="body">The <code>test</code> and <code>[</code> builtins evaluate
+ conditional expressions using a set of rules based on the number of arguments.</span>
+</p>
+<dl>
+ <dd>
+ <dl compact>
+ <dt><span class="body">0 arguments </span>
+ <dd>
+ <p><span class="body">The expression is false. </span></p>
+ <dt><span class="body">1 argument </span>
+ <dd>
+ <p><span class="body">The expression is true if and only if the argument
+ is not null. </span></p>
+ <dt><span class="body">2 arguments </span>
+ <dd>
+ <p><span class="body">If the first argument is <samp>`!'</samp>, the expression
+ is true if and only if the second argument is null. If the first argument
+ is one of the unary conditional operators, the expression is true if
+ the unary test is true. If the first argument is not a valid unary operator,
+ the expression is false. </span></p>
+ <dt><span class="body">3 arguments </span>
+ <dd>
+ <p><span class="body">If the second argument is one of the binary conditional
+ operators, the result of the expression is the result of the binary
+ test using the first and third arguments as operands. If the first argument
+ is <samp>`!'</samp>, the value is the negation of the two-argument test
+ using the second and third arguments. If the first argument is exactly
+ <samp>`('</samp> and the third argument is exactly <samp>`)'</samp>,
+ the result is the one-argument test of the second argument. Otherwise,
+ the expression is false. The <samp>`-a'</samp> and <samp>`-o'</samp>
+ operators are considered binary operators in this case. </span></p>
+ <dt><span class="body">4 arguments </span>
+ <dd>
+ <p><span class="body">If the first argument is <samp>`!'</samp>, the result
+ is the negation of the three-argument expression composed of the remaining
+ arguments. Otherwise, the expression is parsed and evaluated according
+ to precedence using the rules listed above. </span></p>
+ <dt><span class="body">5 or more arguments </span>
+ <dd>
+ <p><span class="body">The expression is parsed and evaluated according
+ to precedence using the rules listed above.</span></p>
+ </dd>
+ </dl>
+</dl>
+<p>The above applies to the BOURNE shell built-in, the BASH `test'
+ command has the following additional options:</p>
+<p><span class="body"><b>File type tests </b><br>
+ <br>
+ These options test for particular types of files. All cases will only return
+ True (0) if the file exists.</span></p>
+<pre>`-b <em>file</em>'
+ True if <em>file</em> is a Block special device.
+
+`-c <em>file</em>'
+ True if <em>file</em> is a Character special device.
+
+`-d <em>file</em>'
+ True if <em>file</em> is a Directory.
+
+`-e <em>file</em>'
+ True if <em>file</em> Exists.
+
+`-f <em>file</em>'
+ True if <em>file</em> is a regular File.
+
+`-g <em>file</em>'
+ True if <em>file</em> has its set-group-id bit set.
+
+`-G <em>file</em>'
+ True if <em>file</em> is owned by the current effective group id.
+
+`-k <em>file</em>'
+ True if <em>file</em> has its "sticky" bit set.
+
+`-h <em>file</em>'
+`-L <em>file</em>'
+ True if <em>file</em> is a symbolic Link.
+
+`-O <em>file</em>'
+ True if <em>file</em> is owned by the current effective user id.
+
+`-p <em>file</em>'
+ True if <em>file</em> is a named Pipe.
+
+`-r <em>file</em>'
+ True if <em>file</em> is readable.
+
+`-S <em>file</em>'
+ True if <em>file</em> is a Socket.
+
+`-s <em>file</em>'
+ True if <em>file</em> has a Size greater than zero.
+
+`-t [FD]'
+ True if FD is opened on a terminal. If FD is omitted, it defaults
+ to 1 (standard output).
+
+`-u <em>file</em>'
+ True if <em>file</em> has its set-user-id bit set.
+
+`-w <em>file</em>'
+ True if <em>file</em> is writable.
+
+`-x <em>file</em>'
+ True if <em>file</em> is executable.
+
+`<em>file</em>1 -ef <em>file</em>2'
+ True if <em>file</em>1 and <em>file</em>2 have the same device and inode numbers,
+ i.e., if they are hard links to each other.</pre>
+<p><span class="body"><b>File Age</b><br>
+These options test the file modification date.</span></p>
+<pre>
+`<em>file</em>1 -nt <em>file</em>2'
+ True if <em>file</em>1 is newer than <em>file</em>2.
+
+`<em>file</em>1 -ot <em>file</em>2'
+ True if <em>file</em>1 is older than <em>file</em>2.</pre>
+<p><span class="body"> <b>String tests</b><br>
+ These options test string characteristics. Strings are not quoted for `test',
+ though you may need to quote them to protect characters with special meaning
+ to the shell, e.g., spaces.</span> </p>
+<pre>`-z <em>String</em>'
+ True if the length of <em>String</em> is zero.
+
+`-n <em>String</em>'
+`<em>String</em>'
+ True if the length of <em>String</em> is nonzero.
+
+`<em>String</em>1 = <em>String</em>2'
+ True if the strings are equal.
+
+`<em>String</em>1 != <em>String</em>2'
+ True if the strings are not equal.</pre>
+<p><span class="body"> <b>Numeric tests</b><br>
+ Numeric relationals. The arguments must be entirely numeric (possibly negative),
+ or the special expression `-l STRING', which evaluates to the length of STRING.</span>
+</p>
+<pre>`ARG1 -eq ARG2'
+`ARG1 -ne ARG2'
+`ARG1 -lt ARG2'
+`ARG1 -le ARG2'
+`ARG1 -gt ARG2'
+`ARG1 -ge ARG2'
+ These arithmetic binary operators return true if ARG1 is equal,
+ not-equal, less-than, less-than-or-equal, greater-than, or
+ greater-than-or-equal than ARG2, respectively.
+
+ For example:
+
+ test -1 -gt -2 && echo yes
+ => yes
+ test -l abc -gt 1 && echo yes
+ => yes
+ test 0x100 -eq 1
+ error--> test: integer expression expected before -eq</pre>
+<p><strong><span class="body"> Examples</span></strong></p>
+<pre>$ ls -al<br>total 67
+
+drwxr-xr-x 18 root root 4096 Jun 9 21:12 ./<br>drwxr-xr-x 18 root root 4096 Jun 9 21:12 ../<br>-rw-rw-rw- 1 simon users 4096 Jun 9 07:30 london<br>-rwsrwsrwx 1 simon users 4096 Jun 9 07:32 aberdeen<br>-rw------- 1 simon users 4096 Jun 9 07:29 bristol<br>-rw-r--r-- 1 simon users 4096 Jun 9 07:29 bath<br>$</pre>
+<p>$ test -r paris<br>
+ $ echo $?<br>
+ 1<br>
+$</p>
+<p>Because the file `paris' is not Readable, the value returned
+is false (non zero)<br>
+</p>
+<pre>if [ &quot;$LOGNAME&quot; <strong>=</strong> &quot;scott&quot; ]<br>then<br> echo &quot;Logged in as Scott&quot;<br>else<br> echo &quot;incorrect user&quot;<br>fi</pre>
+<p>If the logname variable = scott then the test returns TRUE (0)</p>
+<p><em>&quot;The test of a vocation is the love of the drudgery it involves&quot; - Logan Pearsall</em></p>
+<p><b>Related</b>:<br>
+ <br>
+ <a href="case.html">case</a> - Conditionally perform a command<br>
+ <a href="cmp.html">cmp</a> - Compare two files<br>
+ <a href="expr.html">expr</a> - Evaluate expressions<br>
+ <a href="eval.html">eval</a> - Evaluate several commands/arguments <br>
+ <a href="for.html">for</a> - Expand <var>words</var>, and execute <var>commands</var>
+ <br>
+ <a href="if.html">if</a> - Conditionally perform a command <br>
+ pathchk - Check file name portability<br>
+Equivalent Windows command: <a href="../term_tools/nt/set.html">
+</a><a href="../term_tools/nt/if.html">IF</a> - Conditionally perform a command</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/time.html b/help/en/bash/time.html
new file mode 100644
index 0000000..f0d477d
--- /dev/null
+++ b/help/en/bash/time.html
@@ -0,0 +1,228 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>time MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> time</h1>
+<p>Measure the running time of a program. </p>
+<p> The `time' command will run another
+ program, and record the elapsed time or CPU Resource Used time used by that program. <br>
+The information mmay be displayed on screen or saved in a file. </p>
+<pre>Syntax
+ time [<em>option</em>...] <em>command</em> [<em>arg</em>...]
+
+Options
+
+ -o <em>FILE</em>
+ --output=<em>FILE</em>
+ Write the resource use statistics to FILE.
+
+ -a
+ --append
+ *Append* the resource use information to the output file instead
+ of overwriting it.
+
+ -f <em>FORMAT</em>
+ --format=<em>FORMAT</em>
+ Use <em>FORMAT</em> as the format string, see below for formatting options.
+
+ --help
+ Summary of the command line options.
+
+ -o <em>FILE</em>
+ --output=<em>FILE</em>
+ Write the resource use statistics to FILE. By default, this
+ *overwrites* the file, destroying the file's previous contents.
+
+ -a
+ --append
+ *Append* the resource use information to the output file instead
+ of overwriting it. This option is only useful with the `-o' or
+ `--output' option.
+
+ -p
+ --portability
+ Use the POSIX format.
+
+ -v
+ --verbose
+ Use the built-in verbose format, which displays each available
+ piece of information on the program's resource use on its own
+ line, with an English description of its meaning.
+
+-V
+--version
+ Print the version number of `time' and exit.
+
+Options to `time' must appear on the command line before COMMAND.
+Anything on the command line after COMMAND is passed as arguments to
+COMMAND.</pre>
+<p>Setting the Output Format<br>
+ `time' uses a "format string" to determine which information to display about
+ the resources used by the command it runs. You can specify a format string with
+ the options listed above. <br>
+ If no format is specified on the command line, but the `TIME' environment variable
+ is set, its value is used as the format string. Otherwise, the default format
+ built into `time' is used:</p>
+<pre> %Uuser %Ssystem %Eelapsed %PCPU (%Xtext+%Ddata %Mmax)k
+ %Iinputs+%Ooutputs (%Fmajor+%Rminor)pagefaults %Wswaps</pre>
+<p><b>The Format String</b><br>
+<br>
+The "format string" controls the contents of the `time' output. It
+consists of "resource specifiers" and "escapes", interspersed with<br>
+plain text.<br>
+<br>
+A backslash introduces an "escape", which is translated into a
+single printing character upon output. The valid escapes are listed<br>
+below. An invalid escape is output as a question mark followed by a
+backslash.</p>
+<pre> \t a tab character
+ \n a newline
+ \\ a literal backslash</pre>
+<p>`time' always prints a newline after printing the resource use
+information, so normally format strings do not end with a newline<br>
+character (or `\n').<br>
+<br>
+A resource specifier consists of a percent sign followed by another
+character. An invalid resource specifier is output as a question mark<br>
+followed by the invalid character. Use `%%' to output a literal
+percent sign.<br>
+<br>
+<b>Time Resources</b></p>
+<pre> %E Elapsed real (wall clock) time used by the process, in [hours:]minutes:seconds.
+
+ %e Elapsed real (wall clock) time used by the process, in seconds.
+
+ %S Total number of CPU-seconds used by the system on behalf of the
+ process (in kernel mode), in seconds.
+
+ %U Total number of CPU-seconds that the process used directly (in user
+ mode), in seconds.
+
+ %P Percentage of the CPU that this job got. This is just user +
+ system times divied by the total running time.
+
+<b>Memory Resources</b>
+
+ %M Maximum resident set size of the process during its lifetime, in
+ Kilobytes.
+
+ %t Average resident set size of the process, in Kilobytes.
+
+ %K Average total (data+stack+text) memory use of the process, in
+ Kilobytes.
+
+ %D Average size of the process's unshared data area, in Kilobytes.
+
+ %p Average size of the process's unshared stack, in Kilobytes.
+
+ %X Average size of the process's shared text, in Kilobytes.
+
+ %Z System's page size, in bytes. This is a per-system constant, but
+ varies between systems.
+
+<b>I/O Resources</b>
+
+ %F Number of major, or I/O-requiring, page faults that occurred while
+ the process was running. These are faults where the page has
+ actually migrated out of primary memory.
+
+ %R Number of minor, or recoverable, page faults. These are pages
+ that are not valid (so they fault) but which have not yet been
+ claimed by other virtual pages. Thus the data in the page is
+ still valid but the system tables must be updated.
+
+ %W Number of times the process was swapped out of main memory.
+
+ %c Number of times the process was context-switched involuntarily
+ (because the time slice expired).
+
+ %w Number of times that the program was context-switched voluntarily,
+ for instance while waiting for an I/O operation to complete.
+
+ %I Number of file system inputs by the process.
+
+ %O Number of file system outputs by the process.
+
+ %r Number of socket messages received by the process.
+
+ %s Number of socket messages sent by the process.
+
+ %k Number of signals delivered to the process.
+
+<b>Command Info</b>
+
+ %C Name and command line arguments of the command being timed.
+
+ %x Exit status of the command.
+
+
+<b>Examples</b>
+
+Run the command `wc /etc/hosts' and show the default information:
+
+$ time wc /etc/hosts
+ 35 111 1134 /etc/hosts
+ 0.00user 0.01system 0:00.04elapsed 25%CPU (0avgtext+0avgdata 0maxresident)k
+ 1inputs+1outputs (0major+0minor)pagefaults 0swaps
+
+Run the command `ls -Fs' and show the user, system, and wall-clock time:
+
+$ time -f "\t%E real,\t%U user,\t%S sys" ls -Fs
+ total 16
+ 1 account/ 1 db/ 1 mail/ 1 run/
+ 1 backups/ 1 emacs/ 1 msgs/ 1 rwho/
+ 1 crash/ 1 games/ 1 preserve/ 1 spool/
+ 1 cron/ 1 log/ 1 quotas/ 1 tmp/
+ 0:00.03 real, 0.00 user, 0.01 sys
+
+Run the command `cat' and record the elapsed time (stopwatch) until `cat' is closed with Ctrl-D
+
+$ time cat
+^d
+ 0:16.55, 726</pre>
+<p><i>&quot;There is no monument dedicated to the memory of a committee.&quot;
+ - Lester J. Pourciau</i></p>
+<p><b>Related</b>:<br>
+ <br>
+ <a href="times.html">times</a> - User and system times<br>
+Equivalent Windows command:
+PERFMTR - Performance Monitor</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/times.html b/help/en/bash/times.html
new file mode 100644
index 0000000..02892eb
--- /dev/null
+++ b/help/en/bash/times.html
@@ -0,0 +1,59 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>times MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> times</h1>
+<p>Print out the user and system times used by the shell and its
+ children. </p>
+<pre>Syntax
+ times</pre>
+<p> The return status is zero. </p>
+<p>This is a BOURNE shell command.<br>
+ <br>
+ <i>&quot;Youth has no age&quot; - Pablo
+ Picasso </i> </p>
+<p><b>Related</b>:<br>
+ <br>
+ <a href="time.html">time</a> - Measure Program Resource Use<br>
+<br>
+Equivalent Windows command: <a href="../term_tools/nt/set.html">
+ </a>PERFMTR - Performance Monitor</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/top.html b/help/en/bash/top.html
new file mode 100644
index 0000000..167a153
--- /dev/null
+++ b/help/en/bash/top.html
@@ -0,0 +1,119 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>top MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> top</h1>
+<p>Process viewer, find the CPU-intensive
+ programs currently running. See <a href="ps.html">ps</a> for explanations of
+the field descriptors.</p>
+<pre>Syntax
+ top <i>options</i>
+
+Options
+ -b Run in batch mode; don't accept command-line input.
+ Useful for sending output to another command or to a file.
+ -c Show command line in display instead of just command name.
+ -d <i>delay</i>
+ Specify delay between refreshes.
+ -i Suppress display of idle and zombie processes.
+ -n <i>num</i>
+ Update display num times, then exit.
+ -p <i>pid
+</i> Monitor only processes with the specified process ID.
+ -q Refresh without any delay.
+ If user is privileged, run with highest priority.
+ -s Secure mode. Disable some (dangerous) interactive commands.
+ -S Cumulative mode. Print total CPU time of each process,
+ including dead child processes.
+
+Interactive commands
+
+space Update display immediately.
+ A Sort by age, with newest first.
+ c Toggle display of command name or full command line.
+ f, F Add fields to display or remove fields from the display.
+ h, ? Display help about commands and the status of secure and cumulative modes.
+ k Prompt for process ID to kill and signal to send (default is 15) to kill it.
+ i Toggle suppression of idle and zombie processes.
+ l Toggle display of load average and uptime information.
+ ^L Redraw screen.
+ m Toggle display of memory information.
+ M Sort tasks by resident memory usage.
+ n, # Prompt for number of processes to show.
+ If 0 is entered, show as many as will fit on the screen
+ (default).
+ N Sort numerically by process ID.
+ o, O Change order of displayed fields.
+ P Sort tasks by CPU usage (default).
+ q Exit.
+ r Apply renice to a process. Prompt for PID and renice value. Suppressed in secure mode.
+ s Change delay between refreshes.
+ Prompt for new delay time, which should be in seconds.
+ (Suppressed in secure mode.)
+ S Toggle cumulative mode. (See the -S option.)
+ t Toggle display of processes and CPU states information.
+ T Sort tasks by time/cumulative time.
+ W Write current setup to ~/.toprc. This is the recommended way to write a top configuration file.</pre>
+<p>Top displays per-process
+CPU usage (not total server load) it is useful for seeing how much
+work the machine is doing now compared to some point in the past.</p>
+<p>At the top
+ of the display output there are three numbers representing the number
+ of processes waiting for the CPU now, an average for the past
+ five minutes, and an average for the past fifteen minutes. These three numbers
+are the &quot;load average&quot;</p>
+<p>Top should only be used to compare the load average on two different machines
+if they have an identical configuration (both hardware and software.)</p>
+<p><strong>Example <br>
+ </strong><br>
+ To display processes sorted by CPU useage, updating every 5
+seconds:<br>
+top -Ps5</p>
+<p><i>&quot;Venice is
+ like eating an entire box of chocolate liqueurs at one go&quot; - Truman
+ Capote </i></p>
+<p><b>Related</b>:</p>
+<p><a href="http://htop.sourceforge.net/">htop</a> - text mode, interactive process viewer (easy alternative to top) <br>
+ <a href="kill.html">kill</a> - Stop a process from running<br>
+ signal(3) - software signal facilities<br>
+Equivalent Windows command: <a href="../term_tools/nt/tasklist.html">TaskList</a> - Display all running applications
+ and services </p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/touch.html b/help/en/bash/touch.html
new file mode 100644
index 0000000..6d1d0a1
--- /dev/null
+++ b/help/en/bash/touch.html
@@ -0,0 +1,111 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>touch MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> touch</h1>
+<p>Change file timestamps, change the access and/or modification
+times of the specified files.</p>
+<pre>Syntax
+ touch [<i>options</i>]... <i>File</i>...
+
+Options
+
+-a
+--time=atime
+--time=access
+--time=use
+ Change the access time only.
+
+-c
+--no-create
+ Do not create files that do not exist.
+
+-d
+--date=<em>time</em>
+ Use <em>time</em> instead of the current time. It can contain month names,
+ timezones, `am' and `pm', etc.
+
+-f Ignored; for compatibility with BSD versions of `touch'.
+
+-m
+--time=mtime
+--time=modify
+ Change the modification time only.
+
+-r <em>FILE</em>
+--reference=<em>FILE</em>
+ Use the times of the reference <em>FILE</em> instead of the current time.
+
+-t [[CC]YY]MMDDhhmm[.ss]
+ Set to a specific time.</pre>
+<p>The -t argument will accept four-digit or two-digit years, specifying the seconds is optional. If no digits of the year are specified, the argument is
+interpreted as a date in the current year. </p>
+<p>If two-digit year is specified, then CC
+is 20 for years in the range 0 ... 68, and 19 for year in 69 ...
+99. </p>
+<p>If the first <i>FILE</i> would be a valid argument to the `-t'
+ option and no timestamp is given with any of the `-d', `-r', or `-t' options
+ and the `--' argument is not given, that argument is interpreted as the time
+ for the other files instead of as a file name. </p>
+<p>Any <i>FILE</i> that does not exist is created empty. </p>
+<p>If changing both the access and modification times to the current
+ time, `touch' can change the timestamps for files that the user running it does
+ not own but has write permission for. Otherwise, the user must own the files.</p>
+<p><b>Examples</b></p>
+<p>Create/datestamp one file called sample.txt:</p>
+<p class="telety">touch sample.txt</p>
+<p>Create/datestamp 10 files called file1, file2 etc:</p>
+<p class="telety">touch file{1,2,3,4,5,6,7,8,9,10}</p>
+<p class="telety"><span class="body">Create/datestamp 100 files called file1, file2 etc:</span></p>
+<p class="telety">for i in $(seq 1 100); do echo -n &quot;file${i} &quot;; touch file${i} 2&gt;&amp;1; done</p>
+<p><i>"If you play it safe you stagnate is this league. Maybe we'll
+ bust, but if we hit it, we'll hit it big." - Jimmy
+ Johnson, coach of the Miami Dolphins</i></p>
+<p><b>Related</b>:<br>
+ <br>
+ <a href="chgrp.html">chgrp</a> - Change group ownership<br>
+ <a href="chmod.html">chmod</a> - Change access permissions<br>
+ <a href="chown.html">chown</a> - Change file owner and group<br>
+ <a href="date.html">date</a> - Display or change the date <br>
+ <a href="which.html">which</a> - Show full path of commands<br>
+Equivalent Windows commands:
+<a href="../term_tools/nt/touch.html">TOUCH</a> - Change file timestamps</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/tr.html b/help/en/bash/tr.html
new file mode 100644
index 0000000..7512162
--- /dev/null
+++ b/help/en/bash/tr.html
@@ -0,0 +1,303 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>tr MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> tr</h1>
+<p> Translate, squeeze, and/or delete characters</p>
+<pre>Syntax
+ tr [<em>options</em>]... <em>SET1</em> [<em>SET2</em>]
+</pre>
+<p><span class="body"> `tr' copies standard input to standard output, performing one of the
+ following operations:</span></p>
+<blockquote>
+ <p><span class="body"> * translate, and optionally squeeze repeated characters in the
+ result,<br>
+ <br>
+ * squeeze repeated characters,<br>
+ <br>
+ * delete characters,<br>
+ <br>
+ * delete characters, then squeeze repeated characters from the
+ result.</span></p>
+</blockquote>
+<p> The SET1 and (if given) SET2 arguments define ordered sets of
+characters, referred to below as SET1 and SET2. These sets are the
+characters of the input that `tr' operates on. The `--complement'
+(`-c') option replaces SET1 with its complement (all of the characters
+that are not in SET1).</p>
+<p><b>Specifying sets of characters</b><br>
+<br>
+ The format of the SET1 and SET2 arguments resembles the format of
+ regular expressions; however, they are not regular expressions, only
+ lists of characters. Most characters simply represent themselves in
+ these strings, but the strings can contain the shorthands listed below,
+ for convenience. Some of them can be used only in SET1 or SET2, as
+noted below.</p>
+<pre>
+Backslash escapes
+ A backslash followed by a character not listed below causes an
+ error message.
+
+ \a
+ Control-G.
+
+ \b
+ Control-H.
+
+ \f
+ Control-L.
+
+ \n
+ Control-J.
+
+ \r
+ Control-M.
+
+ \t
+ Control-I.
+
+ \v
+ Control-K.
+
+ \OOO
+ The character with the value given by OOO, which is 1 to 3
+ octal digits,
+
+ \\
+ A backslash.
+
+Ranges</pre>
+<p>The notation `M-N' expands to all of the characters from M through
+N, in ascending order. M should collate before N; if it doesn't,
+an error results. As an example, `0-9' is the same as
+`0123456789'. Although GNU `tr' does not support the System V
+syntax that uses square brackets to enclose ranges, translations<br>
+specified in that format will still work as long as the brackets
+in STRING1 correspond to identical brackets in STRING2.</p>
+<pre>
+Repeated characters</pre>
+<p>The notation `[C*N]' in SET2 expands to N copies of character C.
+Thus, `[y*6]' is the same as `yyyyyy'. The notation `[C*]' in
+STRING2 expands to as many copies of C as are needed to make SET2
+as long as SET1. If N begins with `0', it is interpreted in
+octal, otherwise in decimal.</p>
+<pre>
+Character classes</pre>
+<p>The notation `[:CLASS:]' expands to all of the characters in the
+(predefined) class CLASS. The characters expand in no particular<br>
+order, except for the `upper' and `lower' classes, which expand in
+ascending order. When the `--delete' (`-d') and
+`--squeeze-repeats' (`-s') options are both given, any character
+class can be used in SET2. Otherwise, only the character classes
+`lower' and `upper' are accepted in SET2, and then only if the<br>
+corresponding character class (`upper' and `lower', respectively)
+is specified in the same relative position in SET1. Doing this
+specifies case conversion. The class names are given below; an
+error results when an invalid class name is given.</p>
+<pre>
+ `alnum'
+ Letters and digits.
+
+ `alpha'
+ Letters.
+
+ `blank'
+ Horizontal whitespace.
+
+ `cntrl'
+ Control characters.
+
+ `digit'
+ Digits.
+
+ `graph'
+ Printable characters, not including space.
+
+ `lower'
+ Lowercase letters.
+
+ `print'
+ Printable characters, including space.
+
+ `punct'
+ Punctuation characters.
+
+ `space'
+ Horizontal or vertical whitespace.
+
+ `upper'
+ Uppercase letters.
+
+ `xdigit'
+ Hexadecimal digits.
+</pre>
+<p><br>
+ <span class="code">Equivalence classes</span></p>
+<p> The syntax `<span class="code">[=C=]</span>' expands to all of the characters that are
+ equivalent to C, in no particular order. Equivalence classes are
+ a relatively recent invention intended to support non-English
+ alphabets. But there seems to be no standard way to define them
+ or determine their contents. Therefore, they are not fully
+ implemented in GNU `tr'; each character's equivalence class
+ consists only of that character, which is of no particular use.</p>
+<p><b>Translating</b><br>
+
+<br>
+`tr' performs translation when SET1 and SET2 are both given and the
+`--delete' (`-d') option is not given. `tr' translates each character<br>
+of its input that is in SET1 to the corresponding character in SET2.<br>
+Characters not in SET1 are passed through unchanged. When a character
+appears more than once in SET1 and the corresponding characters in SET2<br>
+are not all the same, only the final one is used. <br>
+For example, these
+two commands are equivalent:</p>
+<pre>
+ tr aaa xyz
+ tr a z</pre>
+<p>A common use of `tr' is to convert lowercase characters to
+uppercase. This can be done in many ways. Here are three of them:</p>
+<pre> tr abcdefghijklmnopqrstuvwxyz ABCDEFGHIJKLMNOPQRSTUVWXYZ
+ tr a-z A-Z
+ tr '[:lower:]' '[:upper:]'</pre>
+<p>When `tr' is performing translation, SET1 and SET2 typically have
+the same length. If SET1 is shorter than SET2, the extra characters at<br>
+the end of SET2 are ignored.<br>
+<br>
+On the other hand, making SET1 longer than SET2 is not portable;
+POSIX.2 says that the result is undefined. In this situation, BSD `tr'<br>
+pads SET2 to the length of SET1 by repeating the last character of SET2
+as many times as necessary. System V `tr' truncates SET1 to the length<br>
+of SET2.<br>
+<br>
+By default, GNU `tr' handles this case like BSD `tr'. When the
+`--truncate-set1' (`-t') option is given, GNU `tr' handles this case
+like the System V `tr' instead. This option is ignored for operations
+other than translation.<br>
+<br>
+Acting like System V `tr' in this case breaks the relatively common
+BSD idiom:<br>
+<br>
+<span class="code">tr -cs A-Za-z0-9 '\012'</span><br>
+<br>
+because it converts only zero bytes (the first element in the
+complement of SET1), rather than all non-alphanumerics, to newlines.<br>
+<br>
+<b>Squeezing repeats and deleting</b><br>
+<br>
+When given just the `--delete' (`-d') option, `tr' removes any input
+characters that are in SET1.<br>
+<br>
+When given just the `--squeeze-repeats' (`-s') option, `tr' replaces
+each input sequence of a repeated character that is in SET1 with a<br>
+single occurrence of that character.<br>
+<br>
+When given both `--delete' and `--squeeze-repeats', `tr' first
+performs any deletions using SET1, then squeezes repeats from any<br>
+remaining characters using SET2.<br>
+<br>
+The `--squeeze-repeats' option may also be used when translating, in
+which case `tr' first performs translation, then squeezes repeats from<br>
+any remaining characters using SET2.</p>
+<p> Here are some examples to illustrate various combinations of options:</p>
+<pre> * Remove all zero bytes:
+
+ tr -d '\000'
+
+ * Put all words on lines by themselves. This converts all
+ non-alphanumeric characters to newlines, then squeezes each string
+ of repeated newlines into a single newline:
+
+ tr -cs 'a-zA-Z0-9' '[\n*]'
+
+ * Convert each sequence of repeated newlines to a single newline:
+
+ tr -s '\n'
+
+ * Find doubled occurrences of words in a document. For example,
+ people often write "the the" with the duplicated words separated
+ by a newline. The bourne shell script below works first by
+ converting each sequence of punctuation and blank characters to a
+ single newline. That puts each "word" on a line by itself. Next
+ it maps all uppercase characters to lower case, and finally it
+ runs `uniq' with the `-d' option to print out only the words that
+ were adjacent duplicates.
+
+ #!/bin/sh
+ cat "$@" \
+ | tr -s '[:punct:][:blank:]' '\n' \
+ | tr '[:upper:]' '[:lower:]' \
+ | uniq -d</pre>
+<p>Warning messages<br>
+<br>
+Setting the environment variable `POSIXLY_CORRECT' turns off the
+following warning and error messages, for strict compliance with
+POSIX.2. Otherwise, the following diagnostics are issued:<br>
+<br>
+1. When the `--delete' option is given but `--squeeze-repeats' is
+not, and SET2 is given, GNU `tr' by default prints a usage message
+and exits, because SET2 would not be used. The POSIX
+specification says that SET2 must be ignored in this case.
+Silently ignoring arguments is a bad idea.<br>
+<br>
+2. When an ambiguous octal escape is given. For example, `\400' is
+actually `\40' followed by the digit `0', because the value 400
+octal does not fit into a single byte.<br>
+<br>
+<br>
+GNU `tr' does not provide complete BSD or System V compatibility.
+For example, it is impossible to disable interpretation of the POSIX
+constructs `[:alpha:]', `[=c=]', and `[c*10]'. Also, GNU `tr' does not
+delete zero bytes automatically, unlike traditional Unix versions,
+which provide no way to preserve zero bytes.</p>
+<p><b>Example</b></p>
+<p class="code">$ toLower() {<br>
+echo $1 | tr &quot;[:upper:]&quot; &quot;[:lower:]&quot; <br>
+} </p>
+<p class="code">$ toLower SomeMixEDCaseText<br>
+Somemixedcasetext</p>
+<p><b></b><i>"Chance is always powerful. - Let your hook be always cast;
+ in the pool where you least expect it, there will be a fish&quot; - Ovid </i></p>
+<p><b>Related</b>:<br>
+ <br>
+ <a href="awk.html">gawk</a> - Find and Replace text within file(s)<br>
+ <a href="grep.html">grep</a> - Search file(s) for lines that match a given pattern<br>
+Equivalent Windows command: <a href="../term_tools/nt/findstr.html">FINDSTR</a> - Search for strings in files</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/traceroute.html b/help/en/bash/traceroute.html
new file mode 100644
index 0000000..8178326
--- /dev/null
+++ b/help/en/bash/traceroute.html
@@ -0,0 +1,132 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>traceroute MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> traceroute</h1>
+<p> Print the route packets take to network host.</p>
+<pre>Syntax
+ traceroute [<i>options</i>] host [<i>packetsize</i>]
+
+Options:
+
+ -I Use ICMP ECHO for probes
+ -T Use TCP SYN for probes
+ -U Use UDP datagrams for probes (default). Only UDP is allowed for unprivileged users.
+ -d Enable socket level debugging (when the Linux kernel supports it)
+
+ -F Set the "Don't Fragment" bit. This tells intermediate routers not to fragment
+ the packet when they find it's too big for a network hop's MTU.
+
+ -f <i>first_ttl</i>
+ With what TTL to start. Default = 1
+
+ -g <i>gateway</i>
+ Adds an IP source route gateway to the outgoing packet. Not useful, as
+ most routers have disabled this for security reasons.
+
+ -i <i>interface</i>
+ The interface through which traceroute should send packets.
+ Default = select according to the routing table.
+
+ -m <i>max_ttl</i>
+ The max no. of hops (max time-to-live value) traceroute will probe. Default=30 hops
+
+ -N <i>squeries</i>
+ The number of probe packets sent out simultaneously. Sending several probes
+ concurrently can speed up traceroute considerably. Default = 16
+ Note that some routers and hosts can use ICMP rate throttling. In such a situation
+ specifying too large number can lead to loss of some responses.
+
+ -n Show numerical addresses; do not look up hostnames.
+ (Useful if DNS is not functioning properly.)
+
+ -p <i>port</i>
+ For UDP tracing: the destination port base traceroute will use
+ (the destination port number will be incremented by each probe).
+ For ICMP tracing: the initial icmp sequence value (incremented by each probe).
+ For TCP tracing: the (constant) destination port to connect.
+ -t <i>tos</i>
+ For IPv4, set the Type of Service (TOS) and Precedence value.
+ Useful values are 16 (low delay) and 8 (high throughput).
+ Note that in order to use some TOS precendence values, you have to be super user.
+ For IPv6, set the Traffic Control value.
+
+ -w <i>waittime
+</i> Set the time (in seconds) to wait for a response to a probe (default 5.0 sec).
+
+ -q <i>nqueries
+</i> Set the number of probe packets per hop. Default = 3
+
+ -r Bypass the normal routing tables and send directly to a host on an attached network.
+ If the host is not on a directly-attached network, an error is returned.
+ This option can be used to ping a local host through an interface that has no route through it.
+
+ -s <i>source_addr</i>
+ Choose an alternative source address. You must select the address of one of the interfaces.
+ Default = address of the outgoing interface.
+
+ -z sendwait
+ Minimal time interval between probes (default 0). If the value is more than 10,
+ then it specifies a number in milliseconds, else it is a number of seconds
+ (float point values allowed too). Useful when some routers use rate-limit for icmp messages.
+
+ -A Perform AS path lookups in routing registries and print results directly after
+ the corresponding addresses
+
+ -V Print the version and exit.
+
+ --help Print help info and exit.
+
+ -4, -6 Explicitly force IPv4 or IPv6 traceouting. By default, the program will try
+ to resolve the name given, and choose the appropriate protocol automatically.
+ If resolving a host name returns both IPv4 and IPv6 addresses, traceroute will use IPv4.
+
+</pre>
+<p> <i>"The Net interprets censorship as damage and routes around
+ it" - John
+Gilmore</i></p>
+<p><b>Related</b>:</p>
+<p> <a href="mtr.html">mtr</a> - Network diagnostics (traceroute/ping)<br>
+ netstat(1)<br>
+ ping(8)<br>
+ route - manipulate routing tables<br>
+Equivalent Windows commands: <a href="../term_tools/nt/tracert.html">tracert</a> - Trace Route</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/true.html b/help/en/bash/true.html
new file mode 100644
index 0000000..e4241e5
--- /dev/null
+++ b/help/en/bash/true.html
@@ -0,0 +1,69 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>true MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> true</h1>
+<p>Do nothing, returning a zero (true) exit status</p>
+<pre> `true' does nothing except return an exit status of 0, meaning
+"success". It can be used as a place holder in shell scripts where a
+successful command is needed, although the shell built-in command `:'
+(colon) does the same thing faster.
+
+ `true' ignores _all_ command line arguments, even `--help' and
+`--version', since to do otherwise would change expected behavior that
+some programmers may be relying on.
+
+ This version of `true' is implemented as a C program, and is thus
+more secure and faster than a shell script implementation, and may
+safely be used as a dummy shell for the purpose of disabling accounts.</pre>
+<p><i>&quot;You are never dedicated to something you have complete
+ confidence in. No-one is fanatically shouting that the sun is going to rise
+ tomorrow. When people are fanatically devoted to political or religious faiths
+ or any other kind of dogmas or goals, its always because these dogmas or goals
+ are in doubt&quot; - <i><a href="http://en.wikipedia.org/wiki/Robert_M._Pirsig">Robert M Pirsig</a></i></i><br>
+ <br>
+ <b> Related</b>:<br>
+ <br>
+ <a href="false.html">false</a> - Do nothing, unsuccessfully<br>
+ <a href="yes.html">yes</a> - Print a string until interrupted <br>
+Equivalent Windows command:
+The <a href="../term_tools/nt/color.html">COLOR</a> command can be used be used to set an %errorlevel%</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/tsort.html b/help/en/bash/tsort.html
new file mode 100644
index 0000000..2e80ba3
--- /dev/null
+++ b/help/en/bash/tsort.html
@@ -0,0 +1,96 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>tsort MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> tsort</h1>
+<p>Topological sort, perform a topological sort on the given FILE,
+or standard input if no input file is given or for a FILE of `-'.</p>
+<pre>Syntax
+ tsort [<em>options</em>] [<em>file</em>]
+
+Options
+
+--help
+--version
+
+`tsort' reads its input as pairs of strings, separated by blanks,
+indicating a partial ordering. The output is a total ordering that
+corresponds to the given partial ordering.
+
+ For example
+
+ tsort <&lt;EOF
+ a b c
+ d
+ e f
+ b c d e
+ EOF
+
+will produce the output
+
+ a
+ b
+ c
+ d
+ e
+ f
+
+`tsort' will detect cycles in the input and writes the first cycle
+encountered to standard error.<eof a
+ b
+ c
+ d
+ e
+ f
+ eof will produce the output detect cycles in input and writes first cycle
+encountered to standard error.
+
+ note that for given partial ordering generally there is no unique
+total ordering.></pre>
+<p><i>&quot;There is always room at the top&quot; - Daniel
+ Webster </i><br>
+ <br>
+ <b> Related</b>:<br>
+ <br>
+ <a href="sort.html">sort</a> - Sort text files<br>
+Equivalent Windows commands:
+<a href="sort.html">SORT</a> - Sort input</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/tty.html b/help/en/bash/tty.html
new file mode 100644
index 0000000..c58b5d2
--- /dev/null
+++ b/help/en/bash/tty.html
@@ -0,0 +1,78 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>tty MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> tty</h1>
+<p>Print file name of terminal on standard input, print the file
+ name of the terminal connected to standard input. It prints `not a tty' if standard
+input is not a terminal.</p>
+<pre>SYNTAX
+ tty [<i>option</i>]...
+
+OPTIONS
+
+ -s
+ --silent
+ --quiet
+ Print nothing; only return an exit status.
+
+ Exit status:
+
+ 0 if standard input is a terminal
+ 1 if standard input is not a terminal
+ 2 if given incorrect arguments
+ 3 if a write error occurs</pre>
+<p><i>"Behind every great fortune there is a crime" - Honore
+ de Balzac </i></p>
+<p><b>Related</b>:<br>
+ <br>
+ <a href="env.html">env</a> - Display, set, or remove environment variables <br>
+ <a href="hostname.html">hostname</a> - Print or set system name <br>
+ <a href="id.html">id</a> - Print user and group id's <br>
+ <a href="logname.html">logname</a> - Print current login name<br>
+ <a href="uname.html">uname</a> - Print system information <br>
+ <a href="users.html">users</a> - Print login names of users currently logged
+ in <br>
+ <a href="who.html">who</a> - Print who is currently logged in <br>
+ whoami - Print the current user id and name (`id -un') <br>
+Equivalent Windows command:
+<a href="../term_tools/nt/set.html">SET</a> %COMPUTERNAME%</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/type.html b/help/en/bash/type.html
new file mode 100644
index 0000000..c9309ac
--- /dev/null
+++ b/help/en/bash/type.html
@@ -0,0 +1,78 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>type MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> type</h1>
+<p>Describe a command, for each <i>name</i>, indicate how it would be interpreted
+ if used as <br>
+a command name. </p>
+<pre>Syntax
+ type [-atp] [<var>name</var> ...]
+
+Options
+ If the `-t' option is used, type prints a single word which is one of:
+ `alias' (shell alias)
+ `function' (shell function)
+ `builtin' (shell builtin)
+ `file' (disk file)
+ `keyword' (shell reserved word)
+
+ If the `-p' option is used, type either returns the name of the disk file that
+ would be executed, or nothing if `-t' would not return `file'.
+
+ If the `-a' option is used, type returns all of the places that contain an
+ executable named file. This includes aliases and functions, if and only if the
+ `-p' option is not also used.</pre>
+<p> The return status is zero if any of the <i>names</i> are found, non-zero otherwise.</p>
+<p>`type' is a BASH builtin command.</p>
+<p><em>&quot;In his errors a man is true to type. Observe the errors and you will
+know the man&quot; - Analects</em></p>
+<p><b>Related</b>:<br>
+ <a href="builtin.html"><br>
+ builtin</a> - Run a shell builtin<a href="env.html"><br>
+ env</a> - Display, set, or remove environment variables<br>
+ <a href="echo.html">echo</a> - Display message on screen <br>
+ <a href="export.html">export</a> - Set an environment variable<br>
+ <a href="function.html">function</a> - Define Function Macros <br>
+ <a href="readonly.html">readonly</a> - Mark variables/functions as readonly<br>
+ <a href="set.html">set</a> - Manipulate shell variables and functions <br>
+<a href="whereis.html">whereis</a> - Report all known instances of a command</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/ulimit.html b/help/en/bash/ulimit.html
new file mode 100644
index 0000000..34994c7
--- /dev/null
+++ b/help/en/bash/ulimit.html
@@ -0,0 +1,96 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>ulimit MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> ulimit</h1>
+<p>User limits - limit the use of system-wide resources.</p>
+<pre>Syntax
+ ulimit [-acdfHlmnpsStuv] [<var>limit</var>]
+
+Options
+
+ -S Change and report the soft limit associated with a resource.
+ -H Change and report the hard limit associated with a resource.
+
+ -a All current limits are reported.
+ -c The maximum size of core files created.
+ -d The maximum size of a process's data segment.
+ -f The maximum size of files created by the shell(default option)
+ -l The maximum size that may be locked into memory.
+ -m The maximum resident set size.
+ -n The maximum number of open file descriptors.
+ -p The pipe buffer size.
+ -s The maximum stack size.
+ -t The maximum amount of cpu time in seconds.
+ -u The maximum number of processes available to a single user.
+ -v The maximum amount of virtual memory available to the process. </pre>
+<p>ulimit provides control over the resources available to the shell and to processes started by it, on systems that allow such control. </p>
+<p>The soft limit is the value that the kernel enforces for
+the corresponding resource. The hard limit acts as a
+ceiling for the soft limit.</p>
+<p>An unprivileged process may
+only set its soft limit to a value in the range from 0 up
+to the hard limit, and (irreversibly) lower its hard
+limit. A privileged process may make arbitrary changes to
+either limit value.</p>
+<p>If <i>limit</i> is given, it is the new value of the specified
+ resource. Otherwise, the current value of the soft limit for the specified resource
+ is printed, unless the `-H' option is supplied. </p>
+<p>When setting new limits, if neither `-H' nor `-S' is supplied, both the hard
+ and soft limits are set.<br>
+ <br>
+ Values are in 1024-byte increments, except for `-t', which is in seconds, `-p',
+ which is in units of 512-byte blocks, and `-n' and `-u', which are unscaled
+ values.
+<p>The return status is zero unless an invalid option is supplied,
+ a non-numeric argument other than <span class="code">unlimited</span> is supplied as a <i>limit</i>, or
+ an error occurs while setting a new limit.</p>
+<p>ulimit is a bash built in command.<br>
+ <br>
+ <i>&ldquo;Every man is a damn fool for at least five minutes every day; wisdom consists of not exceeding that limit&rdquo; - Elbert Hubbard</i> </p>
+<p><b>Related</b>:</p>
+<p> <a href="../term_tools/bash/limits.conf.html">limits.conf - configuration file<br>
+ </a><a href="quota.html">quota</a> - Display disk usage and limits<br>
+setrlimit - Set resource limit <br>
+<a href="http://en.wikipedia.org/wiki/Fork_bomb">Fork bomb</a> - Wikipedia<br>
+Equivalent Windows command: <a href="../term_tools/nt/set.html">
+</a><a href="../term_tools/nt/diruse.html">DIRUSE</a> - Display disk usage</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/umask.html b/help/en/bash/umask.html
new file mode 100644
index 0000000..d7c8370
--- /dev/null
+++ b/help/en/bash/umask.html
@@ -0,0 +1,76 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>umask MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> umask</h1>
+<p><span class="body">User's file creation mask</span>. umask sets an environment variable which automatically sets file permissions on newly created files. i.e. it will set the shell process's
+file creation mask to <var>mode</var>.</p>
+<pre>Syntax
+ umask [-p] [-S] [<var>mode</var>]
+
+Key
+ mode File creation mask
+ -S Print the mask in symbolic format
+ -p Output in a form that may be reused as input</pre>
+<p> The mode specified works as a mask, if <var>mode</var> is omitted, the current value of the mask will be printed.</p>
+<p>You can set umask in <span class="telety">/etc/bashrc</span> or <span class="telety">/etc/profile</span> for all users. By default most Linux distros will set it to 0022 (022) or 0002 (002).</p>
+<p>So the file will contain<br>
+<span class="telety">umask 022</span></p>
+<p>If <var>mode</var> begins with a digit, it is interpreted as an octal number;
+ if not, it is interpreted as a symbolic mode mask similar to that accepted by
+ the <code>chmod</code> command. <br>
+ <br>
+ The return status is zero if the mode is successfully changed or if no <var>mode</var>
+ argument is supplied, and non-zero otherwise. <br>
+ <br>
+ Note that when the <i>mode</i> is interpreted as an octal number, each number of the
+ umask is subtracted from <code>7</code>. Thus, a umask of <code>022</code> results
+ in permissions of <code>755</code>. </p>
+<p>umask is a bash built in command.<br>
+ <br>
+ <i>&quot;Woe to him who doesn't know how to wear his mask, be he king or Pope!&quot;
+ - Luigi Pirandello</i></p>
+<p><b>Related</b>:<br>
+ <a href="export.html">export</a> - Set an environment variable<br>
+ <a href="chmod.html">chmod</a> - Change access permissions<br>
+ <a href="chown.html">chown</a> - Change file owner and group<br>
+<a href="readonly.html">readonly</a> - Mark variables/functions as readonly</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/uname.html b/help/en/bash/uname.html
new file mode 100644
index 0000000..984fd57
--- /dev/null
+++ b/help/en/bash/uname.html
@@ -0,0 +1,102 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>uname MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> uname</h1>
+<p>Print system information, print information about the machine
+ and operating system it is run on. If no options are given, `uname' acts as
+if the `-s' option were given.</p>
+<pre>Syntax
+ uname [<em>options</em>]...
+
+Options
+
+ -a
+ --all
+ Print all of the below information.
+
+ -m
+ --machine
+ Print the machine (hardware) type.
+
+ -n
+ --nodename
+ Print the machine's network node hostname.
+
+ -p
+ --processor
+ Print the machine's processor type
+
+ -r
+ --release
+ Print the operating system release.
+
+ -s
+ --sysname
+ Print the operating system name.
+
+ -v
+ Print the operating system version.</pre>
+<p> If multiple options or `-a' are given, the selected information
+ is printed in this order: <br>
+ <br>
+ SYSNAME NODENAME RELEASE OSVERSION MACHINE<br>
+ <br>
+ The OSVERSION, at least, may well be multiple words. <br>
+ For example: <br>
+ <span class="telety">$uname -a <br>
+ => Linux hayley 1.0.4 #3 Thu May 12 18:06:34 1994 i486 </span></p>
+<p><b>Related</b>:<br>
+ <br>
+ <a href="tty.html"> </a><a href="env.html">env</a> - Display, set, or remove
+ environment variables <br>
+ <a href="groups.html">groups</a> - Print group names a user is in<br>
+ <a href="hostname.html">hostname</a> - Print or set system name <br>
+ <a href="id.html">id</a> - Print user and group id's<br>
+ <a href="logname.html">logname</a> - Print current login name<br>
+ ps - list processes<br>
+ <a href="tty.html">tty</a> - Print filename of terminal on stdin<br>
+ <a href="users.html">users</a> - Print login names of users currently logged
+ in <br>
+ <a href="who.html">who</a> - Print who is currently logged in <br>
+ whoami - Print the current user id and name (`id -un') <br>
+ Equivalent Windows command: <a href="../term_tools/nt/echo.html"> ECHO </a> %USERNAME%</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/unexpand.html b/help/en/bash/unexpand.html
new file mode 100644
index 0000000..98c3a7a
--- /dev/null
+++ b/help/en/bash/unexpand.html
@@ -0,0 +1,83 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>unexpand MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> unexpand</h1>
+<p> Convert spaces to tabs, write the contents of each given FILE,
+ or standard input if none are given or for a FILE of `-', to standard output.
+ Strings of two or more space or tab characters are converted to as many tabs
+as possible followed by as many spaces as are needed.</p>
+<pre>Syntax
+ unexpand [<em>options</em>]... [<em>file</em>]...
+
+Options
+
+ -<em>TAB1</em>[,<em>TAB2</em>]...
+ -t <em>TAB1</em>[,<em>TAB2</em>]...
+ --tabs=<em>TAB1</em>[,<em>TAB2</em>]...
+ If only one tab stop is given, set the tabs TAB1 spaces apart
+ instead of the default 8. Otherwise, set the tabs at columns
+ TAB1, TAB2, ... (numbered from 0), and leave spaces and tabs
+ beyond the tabstops given unchanged. If the tabstops are specified
+ with the `-t' or `--tabs' option, they can be separated by blanks
+ as well as by commas. This option implies the `-a' option.
+
+ -a
+ --all
+ Convert all strings of two or more spaces or tabs, not just initial
+ ones, to tabs.</pre>
+<p>By default, `unexpand' converts only initial spaces and tabs (those
+ that precede all non space or tab characters) on each line. <br>
+ It preserves backspace characters in the output; they decrement the column count
+ for tab calculations. <br>
+ By default, tabs are set at every 8th column. </p>
+<p><b>Related</b>:<br>
+ <br>
+ <a href="cut.html">
+ cut</a> - Divide a file into several parts<br>
+ <a href="expand.html">expand</a> - Convert tabs to spaces<br>
+ <a href="expr.html">expr</a> - Evaluate expressions <br>
+ <a href="fmt.html">fmt</a> - Reformat paragraph text <br>
+ <a href="grep.html">grep</a> - Search file(s) for lines that match a given pattern<br>
+ <a href="seq.html">seq</a> - Print numeric sequences <br>
+ <a href="tr.html">tr</a> - Translate, squeeze, and/or delete characters <br>
+ <a href="uuencode.html">uuencode</a> - Encode a binary file </p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/uniq.html b/help/en/bash/uniq.html
new file mode 100644
index 0000000..cc9f035
--- /dev/null
+++ b/help/en/bash/uniq.html
@@ -0,0 +1,107 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>uniq MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> uniq</h1>
+<p> Uniquify files, write out the unique lines from the given InputFile.<br>
+If an InputFile of `<span class="telety">-</span>' (or nothing) is given, then uniq will read from standard input.</p>
+<pre>Syntax
+ uniq [<em>options</em>]... [<em>InputFile</em> [<em>OutputFile</em>]]
+
+Options
+
+-<em>N</em>
+-f <em>N</em>
+--skip-fields=<em>N</em>
+ Skip <em>N</em> fields on each line before checking for uniqueness. Fields
+ are sequences of non-space non-tab characters that are separated
+ from each other by at least one spaces or tabs.
+
++<em>N</em>
+-s N
+--skip-chars=<em>N</em>
+ Skip N characters before checking for uniqueness. If you use both
+ the field and character skipping options, fields are skipped over
+ first.
+
+-c
+--count
+ Print the number of times each line occurred along with the line.
+
+-i
+--ignore-case
+ Ignore differences in case when comparing lines.
+
+-d
+--repeated
+ Print only duplicate lines.
+
+-D
+--all-repeated
+ Print all duplicate lines and only duplicate lines. This option
+ is useful mainly in conjunction with other options e.g., to ignore
+ case or to compare only selected fields. This is a GNU extension.
+
+-u
+--unique
+ Print only unique lines.
+
+-w <em>N</em>
+--check-chars=<em>N</em>
+ Compare <em>N</em> characters on each line (after skipping any specified
+ fields and characters). By default the entire rest of the lines
+ are compared.</pre>
+<p>By default, `uniq' prints the unique lines in a sorted file, i.e.,
+ discards all but one of identical successive lines. Optionally, it can instead
+ show only lines that appear exactly once, or lines that appear more than once.
+ <br>
+ <br>
+ The input must be sorted. If your input is not sorted, perhaps you want to use
+ `sort -u'.<br>
+ <br>
+ If no <em>OutputFile</em> file is specified, `uniq' writes to standard output.</p>
+<p><em>&quot;The unique the complex, the extraordinary and
+ irreplaceable Diana, whose beauty, both internal and external, will never
+be extinguished from our minds&quot; - Earl Spencer</em></p>
+<p><b>Related</b>:<br>
+ <br>
+<a href="sort.html">sort</a> - Sort text files</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/units.html b/help/en/bash/units.html
new file mode 100644
index 0000000..2729e63
--- /dev/null
+++ b/help/en/bash/units.html
@@ -0,0 +1,308 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>units MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> units</h1>
+<p>Convert units from one scale to another. The units are defined
+ in an external data file. You can use the extensive data file that comes with
+ this program, or you can provide your own data file to suit your needs. You
+ can use the program interactively with prompts, or you can use it from the command
+line.</p>
+<pre>Syntax
+ units <em>options</em> [<em>FROM-UNIT</em> [<em>TO-UNIT</em>]]
+
+Options
+
+ -c
+ --check
+ Check that all units and prefixes defined in the units file reduce
+ to primitive units. The program will print a list of all units
+ that cannot be reduced.
+
+ --check-verbose
+ Like the `-check' option, this option prints a list of units that
+ cannot be reduced. But to help find unit definitions that cause
+ endless loops, it lists the units as they are checked. If `units'
+ hangs, then the last unit to be printed has a bad definition.
+
+ -o <em>format</em>
+ --output-format format
+ Use the specified format for numeric output. Format is the same
+ as that for the printf function in the ANSI C standard. For
+ example, if you want more precision you might use `-o %.15g'.
+
+ -f <em>filename</em>
+ --file <em>filename</em>
+ Use filename as the units data file rather than the default units
+ data file `units.dat'.
+
+ -h
+ --help
+ Print out a summary of the options for `units'.
+
+ -q
+ --quiet
+ --silent
+ Suppress prompting of the user for units and the display of
+ statistics about the number of units loaded.
+
+ -s
+ --strict
+ Suppress conversion of units to their reciprocal units.
+
+ -v
+ --verbose
+ Give slightly more verbose output when converting units. When
+ combined with the `-c' option this gives the same effect as
+ `--check-verbose'.
+
+ -V
+ --version
+ Print program version number, tell whether the readline library
+ has been included, and give the location of the default units data
+ file.</pre>
+<p>To invoke units for interactive use, type `units' at your shell
+ prompt. The program will print something like this: <br>
+ <span class="telety"><br>
+ 1161 units, 53 prefixes <br>
+ You have: </span><br>
+ <br>
+ At the `You have:' prompt, type the quantity and units that you are converting
+ *from*. For example, if you want to convert ten meters to feet, type `10 meters'.
+ Next, `units' will print `You want:'. You should type the type of units you
+ want to convert *to*. To convert to feet, you would type `feet'. <br>
+ <br>
+ The answer will be displayed in two ways. The first line of output, which is
+ marked with a `*' to indicate multiplication, gives the result of the conversion
+ you have asked for. The second line of output, which is marked with a `/' to
+ indicate division, gives the inverse of the conversion factor. If you convert
+ 10 meters to feet, `units' will print <br>
+ <br>
+ <span class="telety">* 32.808399 <br>
+ / 0.03048 </span><br>
+ <br>
+ which tells you that 10 meters equals about 32.8 feet. The second number gives
+ the conversion in the reverse direction.<br>
+ <br>
+ The `units' program can perform units conversions non-interactively from the
+ command line. To do this, type the command, type the original units expression,
+ and type the new units you want. You will probably need to protect the units
+ expressions from interpretation by the shell using single quote characters.<br>
+ If you type <br>
+ <br>
+ <span class="telety">units '2 liters' 'quarts' </span><br>
+ <br>
+ then `units' will print <br>
+ <br>
+ * 2.1133764 <br>
+ / 0.47317647 <br>
+ <br>
+ and then exit. The output tells you that 2 liters is about 2.1 quarts, or alternatively
+ that a quart is about 0.47 times 2 liters.</p>
+<p><b>Unit expressions</b><br>
+<br>
+In order to enter more complicated units or fractions, you will need
+to use operations such as powers, products and division. Powers of
+units can be specified using the `^' character as shown in the
+following example, or by simple concatenation: `cm3' is equivalent to
+`cm^3'. If the exponent is more than one digit, the `^' is required.<br>
+</p>
+<pre>
+ You have: cm^3
+ You want: gallons
+ * 0.00026417205
+ / 3785.4118
+
+ You have: arabicfoot-arabictradepound-force
+ You want: ft lbf
+ * 0.7296
+ / 1.370614
+
+ Multiplication of units can be specified by using spaces, a hyphen
+(`-') or an asterisk (`*'). Division of units is indicated by the
+slash (`/').
+
+ You have: furlongs/fortnight
+ You want: m/s
+ * 0.00016630986
+ / 6012.8727
+</pre>
+<p>Multiplication has a higher precedence than division and is evaluated
+left to right, so `m/s * s/day' is equivalent to `m / s s day' and has
+dimensions of length per time cubed. In effect, the first `/'
+character marks the beginning of the denominator of your unit. In
+particular, this means that writing `1/2 meter' refers to a unit of
+reciprocal length equivalent to .5/meter, which is probably not what
+you would intend if you entered that expression. To indicate division
+of numbers, use the vertical dash (`|'). No spaces area permitted on
+either side of the vertical dash character.</p>
+<pre>
+ You have: 1|2 inch
+ You want: cm
+ * 1.27
+ / 0.78740157</pre>
+<p>Prefixes are defined separately from base units. In order to get
+centimeters, the units database defines `centi-' and `c-' as prefixes.<br>
+Prefixes can appear alone with no unit following them. An exponent
+applies only to the immediately preceding unit and its prefix so that
+`cm^3' or `centimeter^3' refer to cubic centimeters but `centi-meter^3'
+refers to hundredths of cubic meters. Only one prefix is permitted per
+unit, so `micromicrofarad' will fail, but `micro-microfarad' will work.<br>
+<br>
+For `units', numbers are just another kind of unit. They can appear
+as many times as you like and in any order in a unit expression. For
+example, to find the volume of a box which is 2 ft by 3 ft by 12 ft in
+steres, you could do the following:</p>
+<pre> You have: 2 ft 3 ft 12 ft
+ You want: stere
+ * 2.038813
+ / 0.49048148
+
+ You have: $ 5 / yard
+ You want: cents / inch
+ * 13.888889
+ / 0.072</pre>
+<p>And the second example shows how the dollar sign in the units conversion
+can precede the five. Be careful: `units' will interpret `$5' with no
+space as equivalent to dollars^5.<br>
+<br>
+Outside of the SI system, it is often desirable to add values of
+different units together. Sums of conformable units are written with
+the `+' character.</p>
+<pre> You have: 2 hours + 23 minutes + 32 seconds
+ You want: seconds
+ * 8612
+ / 0.00011611705
+
+ You have: 12 ft + 3 in
+ You want: cm
+ * 373.38
+ / 0.0026782366
+
+ You have: 2 btu + 450 ft-lbf
+ You want: btu
+ * 2.5782804
+ / 0.38785542</pre>
+<p>
+The expressions which are added together must reduce to identical
+expressions in primitive units, or an error message will be displayed:</p>
+<pre> You have: 12 printerspoint + 4 heredium
+ Illegal sum of non-conformable units:
+ 12 printerspoint reduces to 0.0042175176 m
+ 4 heredium reduces to 20145.828 m^2</pre>
+<p>Because `-' is used for products, it cannot also be used to form
+differences of units. If a `-' appears before numerical digits as the
+very first character on the input line or if it appears immediately
+after a `+' then the number will be evaluated as a negative number. So
+you can compute 20 degrees minus 12 minutes by entering `20 degrees+-12<br>
+arcmin'. The `+' character is sometimes used in exponents like
+`3.43e+8'. Exponents of this form cannot be used when forming sums of
+units, but they may be used otherwise.<br>
+<br>
+<b>Unit definitions</b><br>
+<br>
+The conversion information is read from a units data file which is
+called `units.dat' and is probably located in the `/usr/local/share'
+directory. If you invoke `units' with the `-V' option, it will print
+the location of this file. The default file includes definitions for
+all familiar units, abbreviations and metric prefixes. It also
+includes many obscure or archaic units.</p>
+<pre> Many constants of nature are defined, including these:
+
+ pi ratio of circumference to diameter
+ c speed of light
+ e charge on an electron
+ force acceleration of gravity
+ mole Avogadro's number
+ water pressure per unit height of water
+ Hg pressure per unit height of mercury
+ au astronomical unit
+ k Boltzman's constant
+ mu0 permeability of vacuum
+ epsilon0 permitivity of vacuum
+ G Gravitational constant
+ mach speed of sound</pre>
+<p>The database includes atomic masses for all of the elements and numerous
+other constants. Also included are the densities of various ingredients
+used in baking so that `2 cups flour_sifted' can be converted to<br>
+`grams'. This is not an exhaustive list. Consult the units data file
+to see the complete list, or to see the definitions that are used.<br>
+<br>
+The unit `pound' is a unit of mass. To get force, multiply by the
+force conversion unit `force' or use the shorthand `lbf'. (Note that
+`g' is already taken as the standard abbreviation for the gram.) The
+unit `ounce' is also a unit of mass. The fluid ounce is `fluidounce'
+or `floz'. British capacity units that differ from their US
+counterparts, such as the British Imperial gallon, are prefixed with
+`br'. Currency is prefixed with its country name: `belgiumfranc',
+`britainpound'.<br>
+<br>
+The US Survey foot, yard, and mile can be obtained by using the `US'
+prefix. These units differ slightly from the international length
+units. They were in use until 1959, but for geographic surveys, they
+are still used. The acre is officially defined in terms of the US
+Survey foot. If you want an acre defined according to the
+international foot, use `intacre'. The difference between these units
+is about 4 parts per million. The British also used a slightly
+different length measure before 1959. These can be obtained with the
+prefix `UK'.<br>
+<br>
+When searching for a unit, if the specified string does not appear
+exactly as a unit name, then the `units' program will try to remove a
+trailing `s' or a trailing `es'. If that fails, `units' will check for
+a prefix. All of the standard metric prefixes are defined.<br>
+<br>
+To find out what units and prefixes are available, read the standard
+units data file.<br>
+<br>
+All of the units and prefixes that `units' can convert are defined
+in the units data file. <br>
+To add your own units data file - see the man pages for the file layout.</p>
+<p><i>"You have not converted a man because you have silenced him&quot;
+ - John
+ Morley</i></p>
+<p><b>Related</b>:<br>
+ <br>
+ <a href="cal.html">cal</a> - Display a calendar<br>
+ <a href="dc.html">dc</a> - Desk Calculator<br>
+ <a href="../term_tools/bash/factor.html">factor</a> - Print prime factors <br>
+<a href="wc.html">wc</a> - Print byte, word, and line counts</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/unset.html b/help/en/bash/unset.html
new file mode 100644
index 0000000..993db2a
--- /dev/null
+++ b/help/en/bash/unset.html
@@ -0,0 +1,70 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>unset MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> unset</h1>
+<p>Remove variable or function names</p>
+<pre>Syntax
+ unset [-fv] [<var>name</var>]
+
+Options
+ -f The <var>name</var>s refer to shell Functions,
+ and the function definition is removed.
+ Readonly variables and functions may not be unset.
+
+ -v Each <var>name</var> refers to a shell Variable (default)</pre>
+<p> The return status is zero unless a <var>name</var> does not exist or is readonly.
+</p>
+<p>uset is a BOURNE shell command and a POSIX `special' builtin.</p>
+<p><em>&quot;A good trader has to have three things: a chronic inability to accept things at face value, to feel continuously unsettled, and to have humility&quot;
+- Michael Steinhardt</em></p>
+<p><b>Related</b>:<br>
+ <a href="env.html"><br>
+ env</a> - Display, set, or remove environment variables<br>
+ <a href="echo.html">echo</a> - Display message on screen <br>
+ <a href="export.html">export</a> - Set an environment variable<br>
+ <a href="function.html">function</a> - Define Function Macros <br>
+ <a href="readonly.html">readonly</a> - Mark variables/functions as readonly<br>
+ <a href="set.html">set</a> - Manipulate shell variables and functions <br>
+Equivalent Windows commands: <a href="../term_tools/nt/set.html">
+ </a><a href="../term_tools/nt/set.html">SET</a> - Display, set, or remove Windows environment
+ variables</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/unshar.html b/help/en/bash/unshar.html
new file mode 100644
index 0000000..598c017
--- /dev/null
+++ b/help/en/bash/unshar.html
@@ -0,0 +1,109 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>unshar MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> unshar</h1>
+<p>Unpack shell archive scripts. Each <i>file</i> is processed in turn,
+ as a shell archive or a collection of shell archives. If no files are given,
+then standard input is processed instead.</p>
+<pre>Syntax
+ unshar [<em>options</em>] ... [<em>file</em>... ]
+
+Options
+
+ -d <em>DIRECTORY</em>
+ --directory=<em>DIRECTORY</em>
+ Change directory to <em>DIRECTORY</em> before unpacking any files.
+
+ -c
+ --overwrite
+ -f
+ --force
+ Passed as an option to the shar file. Many shell archive scripts
+ (including those produced by `shar' 3.40 and newer) accepts a `-c'
+ argument to indicate that existing files should be overwritten.
+
+ The option `-f' is provided for a more unique interface. Many
+ programs (such as `cp' and `mv') use this option to trigger the
+ very same action.
+
+ -e
+ --exit-0
+ This option exists mainly for people who collect many shell
+ archives into a single mail folder. With this option, `unshar'
+ isolates each different shell archive from the others which have
+ been put in the same file, unpacking each in turn, from the
+ beginning of the file towards its end. Its proper operation
+ relies on the fact that many shar files are terminated by a
+ `exit 0' at the beginning of a line.
+
+ Option `-e' is internally equivalent to `-E "exit 0"'.
+
+ -E <em>STRING</em>
+ --split-at=<em>STRING</em>
+ This option works like `-e', but it allows you to specify the
+ string that separates archives if `exit 0' isn't appropriate.
+
+ For example, noticing that most `.signatures' have a `--' on a
+ line right before them, one can sometimes use `--split-at=--' for
+ splitting shell archives which lack the `exit 0' line at end. The
+ signature will then be skipped altogether with the headers of the
+ following message.
+
+ --version
+ Print the version number of the program on standard output, then
+ immediately exits.
+
+ --help
+ Print a help summary on standard output, then immediately exits.</pre>
+<p><i>&quot;I've never had a humble opinion in my life. If you're
+ going to have one, why bother to be humble about it&quot; - Joan
+ Baez </i><br>
+ <br>
+ <b> Related</b>:<br>
+ <br>
+ <a href="cksum.html">cksum</a> - Print CRC checksum and byte counts<br>
+ pr - Convert text files for printing<br>
+ <a href="tar.html"> tar</a> - Tape ARchiver<br>
+ <a href="uuencode.html">uudecode</a> - Decode a file created by uuencode<br>
+Equivalent Windows commands:
+EXTRACT, UNZIP</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/until.html b/help/en/bash/until.html
new file mode 100644
index 0000000..9c76911
--- /dev/null
+++ b/help/en/bash/until.html
@@ -0,0 +1,58 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>until MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> until</h1>
+<p>Execute <var>consequent-commands</var> as long as <var>test-commands</var>
+has an exit status which is not zero.</p>
+<pre>Syntax
+ until <var>test-commands</var>; do <var>consequent-commands</var>; done</pre>
+<p>The return status is the exit status of the last command executed in <var>consequent-commands</var>,
+ or zero if none was executed.</p>
+<p><b>Related</b>:<br>
+ <a href="case.html"><br>
+ case</a> - Conditionally perform a command<br>
+ <a href="for.html">for</a> - Expand <var>words</var>, and execute <var>commands</var><br>
+ <a href="if.html">if</a> - Conditionally perform a command<br>
+ <a href="while.html">while</a> - Execute commands<br>
+Equivalent Windows command:
+ <a href="../term_tools/nt/if.html">IF</a> - Conditionally perform a command</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/useradd.html b/help/en/bash/useradd.html
new file mode 100644
index 0000000..d54c976
--- /dev/null
+++ b/help/en/bash/useradd.html
@@ -0,0 +1,114 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>useradd MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> useradd</h1>
+<p>Create new user accounts or update default account information.
+ <br>
+ Unless invoked with the -D option, <i>user </i>must be given. useradd will create
+ new entries in system files. Home directories and initial files may also be
+created as needed.</p>
+<pre>Syntax
+ useradd [<i>options</i>] [<i>user</i>]
+
+Options
+ -c <i>comment</i> Comment field.
+
+ -d <i>dir</i> Home directory.
+ The default is to use <i>user </i>as the directory name
+ under the home directory specified with the -D option.
+
+ -e <i>date </i>Account expiration date.
+ date is in the format MM/DD/YYYY.
+ Two-digit year fields are also accepted.
+ The value is stored as the number of days since January 1, 1970.
+ This option requires the use of shadow passwords.
+
+ -f <i>days </i> Permanently disable account this many days after the
+ password has expired. A value of -1 disables this feature.
+ This option requires the use of shadow passwords.
+
+ -g <i>group</i> Initial group name or ID number.
+ If a different default group has not been specified using the -D option,
+ the default group is 1.
+ -G <i>groups</i> Supplementary groups given by name or number in a comma-separated
+ list with no whitespace.
+
+ -k [<i>dir</i>] Copy default files to user's home directory.
+ Meaningful only when used with the -m option.
+ Default files are copied from /etc/skel/ unless an alternate dir is specified.
+
+ -m Make user's home directory if it does not exist.
+ The default is not to make the home directory.
+
+ -o Override. Accept a nonunique uid with the -u option. (Probably a bad idea.)
+
+ -s <i>shell</i> Login shell.
+
+ -u <i>uid </i> Numerical user ID. The value must be unique unless the -o option is used.
+ The default value is the smallest ID value greater than 99 and greater
+ than every other uid.
+
+ -D [<i>options</i>] Set or display <b>defaults</b>. If options are specified, set them.
+ If no options are specified, display current defaults. The options are:
+
+ -b <i>dir </i>Home directory prefix to be used in creating home directories.
+ If the -d option is not used when creating an account, the
+ user name will be appended to dir.
+
+ -e <i>date</i> Expire date. Requires the use of shadow passwords.
+
+ -f <i>days</i> Number of days after a password expires to disable an account.
+ Requires the use of shadow passwords.
+
+ -g <i>group</i> Initial group name or ID number.
+
+ -s <i>shell</i> Default login shell.
+</pre>
+<p><em>&quot;As living spies we must recruit men who are intelligent but appear to be stupid&quot; - Tu Mu (803-825) </em></p>
+<p><b>Related</b>:<br>
+ <br>
+ userdel [-r] <i>user</i> - Remove user and optionally the user's home directory (
+ /home and mailspool)<br>
+ usermod - modify user account<br>
+Equivalent Windows command:
+<a href="../term_tools/nt/dsadd.html">dsadd</a> - Add active directory object.</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/usermod.html b/help/en/bash/usermod.html
new file mode 100644
index 0000000..7ea9a6f
--- /dev/null
+++ b/help/en/bash/usermod.html
@@ -0,0 +1,87 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>usermod MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> usermod</h1>
+<p>Modify user account information. </p>
+<pre>Syntax
+ usermod [<i>options</i>] [<i>user</i>]
+
+Options
+ -c <i>comment</i> Comment field.
+
+ -d <i>dir</i> Home directory.
+
+ -e <i>date </i>Account expiration date.
+ date is in the format MM/DD/YYYY.
+ Two-digit year fields are also accepted.
+ The value is stored as the number of days since January 1, 1970.
+ This option requires the use of shadow passwords.
+
+ -f <i>days </i> Permanently disable account this many days after the
+ password has expired. A value of -1 disables this feature.
+ This option requires the use of shadow passwords.
+
+ -g <i>group</i> Initial group name or ID number.
+ If a different default group has not been specified using the -D option,
+
+ -G <i>groups</i> Supplementary groups given by name or number in a comma-separated
+ list with no whitespace. The <i>user </i>will be removed from any groups to
+ which they currently belong that are not included in <i>groups</i>.
+
+ -l <i>name</i> Login name. This cannot be changed while the user is logged in.
+
+ -o Override. Accept a nonunique uid with the -u option. (Probably a bad idea.)
+
+ -s <i>shell</i> Login shell.
+
+ -u <i>uid </i> Numerical user ID. The value must be unique unless the -o option is used.
+ The default value is the smallest ID value greater than 99 and greater
+ than every other uid.
+</pre>
+<p><em>&quot;They have rights who dare maintain them.&quot; - James Russell Lowell </em></p>
+<p><b>Related bash commands</b>:<br>
+ <br>
+ userdel [-r] <i>user</i> - Remove user and (optionally) the user's home directory<br>
+ <a href="useradd.html">useradd</a> - add user account<br>
+ Equivalent Windows command:
+<a href="../term_tools/nt/dsmod.html">dsmod</a> - Modify active directory object.</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/users.html b/help/en/bash/users.html
new file mode 100644
index 0000000..a99c69a
--- /dev/null
+++ b/help/en/bash/users.html
@@ -0,0 +1,70 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>users MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> users</h1>
+<p>Print login names of users currently logged in, print on a single
+ line a blank-separated list of user names of users currently logged in to the
+current host.</p>
+<pre>Syntax
+ users [<em>file</em>]
+</pre>
+<p><span class="body"> With no <em>file</em> argument, `users' extracts its information from the
+file `/var/run/utmp'. </span></p>
+<p><span class="body">If a <em>file</em> argument is given, `users' uses that
+file instead. A common choice is `/var/run/wtmp'.</span></p>
+<pre>
+The only options are `--help' and `--version'. </pre>
+<p>Each user name corresponds to a login session, so if a user has
+ more than one login session, that user's name will appear the same number of
+ times in the output. </p>
+<p><b>Related</b>:<br>
+ <br>
+ <a href="groups.html">groups</a> - Print group names a user is in<br>
+ <a href="hostname.html">hostname</a> - Print or set system name <br>
+ <a href="id.html">id</a> - Print user and group id's<br>
+ <a href="logname.html">logname</a> - Print current login name<br>
+ printenv - Print environment variables. <a href="users.html"></a> <br>
+ <a href="uname.html">uname</a> - Print system information <br>
+ <a href="who.html">who</a> - Print who is currently logged in <br>
+ whoami - Print the current user id and name (`id -un') <br>
+Equivalent Windows commands: usrstat (resource kit) </p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/uuencode.html b/help/en/bash/uuencode.html
new file mode 100644
index 0000000..f8b4692
--- /dev/null
+++ b/help/en/bash/uuencode.html
@@ -0,0 +1,97 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>uuencode MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> uuencode / uudecode</h1>
+<p> uuencode - encode a binary file <br>
+ <br>
+uudecode - decode a file created by uuencode</p>
+<pre>Syntax
+ uuencode [-m] [ <i>file</i> ] <i>name</i>
+
+ uudecode [-o <i>outfile</i>] [ <i>file</i> ]...
+</pre>
+<p> Uuencode and uudecode are used to transmit binary files over transmission mediums that do not support other than
+simple ASCII data.</p>
+<p>Debian/Ubuntu users can install uuencode as part of the &rsquo;<a href="http://packages.ubuntu.com/search?keywords=sharutils">sharutils</a>&rsquo; group of Unix utilities with <span class="telety">apt-get install sharutils</span><span class="body"><br>
+ <br>
+ Uuencode reads file (or by default the standard input) and
+ writes an encoded version to the standard output. The
+ encoding uses only printing ASCII characters and includes
+ the mode of the file and the operand name for use by uude
+code.</span></p><span class="body">
+<p>If name is /dev/stdout the result will be written
+to standard output. </p>
+<p>By default the standard UU encoding
+ format will be used. If the option -m is given on the
+ command line base64 encoding is used instead.
+
+</p>
+<p>Uudecode transforms uuencoded files (or by default, the
+ standard input) into the original form. The resulting
+ file is named <i>name</i> (or outfile if the -o option is given)
+ and will have the mode of the original file except that
+setuid and execute bits are not retained. </p>
+<p>If outfile or
+ <i>name</i> is /dev/stdout the result will be written to standard
+ output. Uudecode ignores any leading and trailing lines.
+ The program can automatically decide which of the both
+ supported encoding schemes are used.</p>
+<p><b>Examples</b><br>
+The following example packages up a source tree, compresses it, uuencodes it and mails it to a user on another
+system. When uudecode is run on the target system, the file `src_tree.tar.Z' will be created which may then be
+uncompressed and extracted into the original tree.</p>
+<pre>
+ tar cf - src_tree | compress | uuencode
+ src_tree.tar.Z | mail sys1!sys2!user</pre>
+<p><i>"One of the main causes of the fall of the Roman Empire was
+ that, lacking zero, they had no way to indicate successful termination of their
+ C programs" - Robert
+ Firth</i><br>
+ <br>
+ <b> Related</b>:<br>
+ <br>
+ compress(1) - <br>
+ mail(1) - <br>
+ uucp(1) - <br>
+Equivalent Windows command:
+NTUUCODE.EXE - UUEncode/Decode utility</p>
+</span><!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/vi.html b/help/en/bash/vi.html
new file mode 100644
index 0000000..2d4fc66
--- /dev/null
+++ b/help/en/bash/vi.html
@@ -0,0 +1,301 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>VI MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<style type="text/css">
+<!--
+.grn {color: #006633}
+-->
+</style>
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> VI Editor Commands</h1>
+<p>Vi has two modes <i>insertion</i> mode and <i>command</i> mode. <br>
+The editor begins in command mode, where cursor movement and copy/paste editing occur. <br>
+
+Most commands execute as soon as typed except for &quot;colon&quot; commands which execute when you press the return key. </p>
+<p><b>Switch to Text or Insert mode:</b></p>
+<table border="1" width="80%" cellspacing="0" cellpadding="3">
+ <tr>
+ <td>&nbsp;</td>
+ <td>&nbsp;</td>
+ <td><div align="right">Open line above cursor </div></td>
+ <td><strong>O</strong></td>
+ <td>&nbsp;</td>
+ <td>&nbsp;</td>
+ <td>&nbsp;</td>
+ <td>&nbsp;</td>
+ </tr>
+ <tr>
+ <td><div align="right">Insert text at beginning of line</div></td>
+ <td><strong>I </strong></td>
+ <td><div align="right">Insert text at cursor</div></td>
+ <td><strong>i</strong></td>
+ <td><div align="right">Insert text after cursor</div></td>
+ <td><strong>a</strong></td>
+ <td><div align="right">Append text at line end</div></td>
+ <td><strong>A</strong></td>
+ </tr>
+ <tr>
+ <td>&nbsp;</td>
+ <td>&nbsp;</td>
+ <td><div align="right">Open line below cursor</div></td>
+ <td><strong>o</strong></td>
+ <td>&nbsp;</td>
+ <td>&nbsp;</td>
+ <td>&nbsp;</td>
+ <td>&nbsp;</td>
+ </tr>
+</table>
+<p><b>Switch to Command mode:</b></p>
+<table border="0" width="28%" cellspacing="0" cellpadding="3">
+ <tr>
+ <td width="75%"><div align="right">Switch to command mode</div></td>
+ <td width="25%"><b>&lt;ESC&gt;</b></td>
+ </tr>
+</table>
+<p><strong>Cursor Movement (command mode):</strong></p>
+<table border="1" width="80%" cellspacing="0" cellpadding="3">
+ <tr>
+ <td height="15">&nbsp;</td>
+ <td height="15">&nbsp;</td>
+ <td height="15"><div align="right">Scroll <u>B</u>ackward 1 screen</div></td>
+ <td height="15"><strong>&lt;ctrl&gt;b</strong></td>
+ <td height="15">&nbsp;</td>
+ <td height="15">&nbsp;</td>
+ </tr>
+ <tr>
+ <td height="15">&nbsp;</td>
+ <td height="15">&nbsp;</td>
+ <td height="15"><div align="right">Scroll <u>U</u>p 1/2 screen</div></td>
+ <td height="15"><strong>&lt;ctrl&gt;u</strong></td>
+ <td height="15">&nbsp;</td>
+ <td height="15">&nbsp;</td>
+ </tr>
+ <tr>
+ <td><div align="right">Go to beginning of line</div></td>
+ <td><strong>0</strong></td>
+ <td><div align="right">Go to line <span class="grn"><var>n</var></span></div></td>
+ <td><strong><var class="grn">n</var>G</strong></td>
+ <td><div align="right">Go to end of line</div></td>
+ <td><strong>$</strong></td>
+ </tr>
+ <tr>
+ <td>&nbsp;</td>
+ <td>&nbsp;</td>
+ <td><div align="right">Scroll <u>D</u>own 1/2 screen</div></td>
+ <td><strong>&lt;ctrl&gt;d</strong></td>
+ <td><div align="right">Go to line number <span class="grn">##</span></div></td>
+ <td><b>:<span class="grn">##</span></b></td>
+ </tr>
+ <tr>
+ <td>&nbsp;</td>
+ <td>&nbsp;</td>
+ <td><div align="right">Scroll <u>F</u>orward 1 screen</div></td>
+ <td><strong>&lt;ctrl&gt;f</strong></td>
+ <td>&nbsp;</td>
+ <td>&nbsp;</td>
+ </tr>
+ <tr>
+ <td>&nbsp;</td>
+ <td>&nbsp;</td>
+ <td><div align="right">Go to last line</div></td>
+ <td><strong>G</strong></td>
+ <td>&nbsp;</td>
+ <td>&nbsp;</td>
+ </tr>
+ <tr>
+ <td>Scroll by sentence f/b</td>
+ <td><strong>( )</strong></td>
+ <td>&nbsp;</td>
+ <td>&nbsp;</td>
+ <td>&nbsp;</td>
+ <td>&nbsp;</td>
+ </tr>
+ <tr>
+ <td>Scroll by word f/b</td>
+ <td><strong>w b</strong></td>
+ <td>Move left, down, up, right</td>
+ <td><strong>h j k l</strong></td>
+ <td><div align="right">Left <span class="grn">6</span> chars</div></td>
+ <td><span class="grn"><b>6</b></span><b>h</b></td>
+ </tr>
+ <tr>
+ <td>Scroll by paragraph f/b</td>
+ <td><b>{ } </b></td>
+ <td>Directional Movement</td>
+ <td><strong>Arrow Keys</strong></td>
+ <td><div align="right">Go to line #<span class="grn">6</span></div></td>
+ <td><span class="grn"><b>6</b></span><b>G</b></td>
+ </tr>
+</table>
+<p><b>Deleting text <strong>(command mode)</strong>:</b></p>
+<table border="1" width="80%" cellpadding="3" cellspacing="0">
+ <tr>
+ <td><div align="right">Change word </div></td>
+ <td><strong>cw</strong></td>
+ <td><div align="right">Replace one character</div></td>
+ <td><strong>r</strong></td>
+ <td>&nbsp;</td>
+ <td>&nbsp;</td>
+ </tr>
+ <tr>
+ <td><div align="right">Delete word</div></td>
+ <td><strong>dw</strong></td>
+ <td><div align="right">Delete text at cursor</div></td>
+ <td><strong>x</strong></td>
+ <td><div align="right">Delete entire line (to buffer)</div></td>
+ <td><strong>dd</strong></td>
+ </tr>
+ <tr>
+ <td>&nbsp;</td>
+ <td>&nbsp;</td>
+ <td><div align="right">Delete (backspace) text at cursor</div></td>
+ <td><b>X</b></td>
+ <td><div align="right">Delete <span class="grn">5</span> lines (to buffer)</div></td>
+ <td><span class="grn"><b>5</b></span><b>dd</b></td>
+ </tr>
+ <tr>
+ <td>&nbsp;</td>
+ <td>&nbsp;</td>
+ <td>Delete current to end of line</td>
+ <td><b>D</b></td>
+ <td><div align="right">Delete lines <span class="grn">5-10</span></div></td>
+ <td><strong>:<span class="grn">5,10</span>d </strong></td>
+ </tr>
+</table>
+<p><b>Editing <strong>(command mode)</strong>:</b></p>
+<table border="1" width="80%" cellpadding="3" cellspacing="0">
+ <tr>
+ <td><div align="right">Copy line</div></td>
+ <td><strong>yy </strong></td>
+ <td><div align="right">Copy <var class="grn">n</var> lines</div></td>
+ <td><strong><var class="grn">n</var>yy</strong></td>
+ <td><div align="right">Copy lines <span class="grn">1-2</span>/paste after&nbsp;<span class="grn">3</span></div></td>
+ <td><strong>:<span class="grn">1,2</span>t <span class="grn">3</span></strong></td>
+ </tr>
+ <tr>
+ <td><div align="right">Paste above current line</div></td>
+ <td><strong>P</strong></td>
+ <td><div> </div></td>
+ <td>&nbsp;</td>
+ <td>&nbsp;</td>
+ <td>&nbsp;</td>
+ </tr>
+ <tr>
+ <td><div align="right">Paste below current line</div></td>
+ <td><strong>p</strong></td>
+ <td>&nbsp;</td>
+ <td>&nbsp;</td>
+ <td><div align="right">Move lines <span class="grn">4-5</span>/paste after&nbsp;<span class="grn">6</span></div></td>
+ <td><strong>:<span class="grn">4,5</span>m <span class="grn">6</span></strong></td>
+ </tr>
+ <tr>
+ <td>&nbsp;</td>
+ <td>&nbsp;</td>
+ <td>&nbsp;</td>
+ <td>&nbsp;</td>
+ <td><div align="right">Join previous line</div></td>
+ <td><strong>J</strong></td>
+ </tr>
+ <tr>
+ <td><div align="right">Search backward for <var>string</var></div></td>
+ <td><strong>?<var>string</var></strong></td>
+ <td><div align="right">Search forward for <var>string</var></div></td>
+ <td><strong>/<var>string</var></strong></td>
+ <td>Find next <var>string</var> occurrence</td>
+ <td><strong>n</strong></td>
+ </tr>
+ <tr>
+ <td><div align="right">% (entire file)<b> s </b>(search and replace) /old text with new/ <b>c</b> (confirm) <b>g</b> (global - all)</div></td>
+ <td><strong>:%s/oldstring/newstring/cg</strong></td>
+ <td>&nbsp;</td>
+ <td>&nbsp;</td>
+ <td><div align="right">Ignore case during search</div></td>
+ <td><strong>:set ic</strong></td>
+ </tr>
+ <tr>
+ <td><div align="right">Repeat last command</div></td>
+ <td><b>.</b></td>
+ <td><div align="right">Undo previous command</div></td>
+ <td><strong>u</strong></td>
+ <td><div align="right">Undo all changes to line</div></td>
+ <td><strong>U</strong></td>
+ </tr>
+</table>
+<p><b>Save and Quit <strong>(command mode)</strong>:</b></p>
+<table border="1" width="80%" cellspacing="0" cellpadding="3">
+ <tr>
+ <td><div align="right">Save changes to buffer</div></td>
+ <td><strong>:w</strong></td>
+ <td><div align="right">Save changes and quit vi</div></td>
+ <td><strong>:wq</strong></td>
+ <td><div align="right">Save file to new file</div></td>
+ <td><strong>:w <i>file</i></strong></td>
+ </tr>
+ <tr>
+ <td>&nbsp;</td>
+ <td>&nbsp;</td>
+ <td><div align="right">Quit without saving</div></td>
+ <td><strong>:q!</strong></td>
+ <td><div align="right">Save lines to new file</div></td>
+ <td><strong>:<span class="grn">10,15</span>w <i>file</i></strong></td>
+ </tr>
+</table>
+<p><span class="code">:syntax on</span> Turn on syntax highlighting<br>
+<span class="code">:syntax off </span>Turn off syntax highlighting<br>
+<span class="code">:set number</span> Turn on Line numbering (shorthand :set nu) <br>
+<span class="code">:set nonumber</span> Turn off Line numbering (shorthand :set nonu) </p>
+<p><span class="code">:set ignorecase</span> Ignore case sensitivity when searching<br>
+<span class="code">:set noignorecase</span> Restore case sensitivity (default) <br>
+<br>
+<span class="code">:set autoindent </span>Turn on Auto-indentation <br>
+Use the command<span class="code"> &gt;&gt;</span> to indent and the <span class="code">&lt;&lt;</span> command to outdent <br>
+<span class="code">:set shiftwidth=4</span> Set indentation to four spaces<br>
+<span class="code">:set noautoindent</span> Turn off Auto-indentation</p>
+<p><i>&ldquo;vi was written for a world that doesn't exist anymore - unless you decide to get a satellite phone and use it to connect to the Net at 2400 baud&rdquo; - Bill Joy</i></p>
+<p><b></b><b>Related</b>:</p>
+<p> <a href="http://www.amazon.com/exec/obidos/ASIN/059652983X/ss64">Book - Learning the vi &amp; vim Editor</a><br>
+<a href="http://sshmenu.sourceforge.net/articles/bcvi/">bcvi</a> - Remote file editing with SSH<br>
+
+<a href="http://www.ungerhu.com/jxh/vi.html">Full list of VI commands</a> <br>
+<a href="http://www.vim.org/scripts/script.php?script_id=1658">NerdTree</a> - A VIM plugin for navigating the filesystem<br>
+<a href="http://www.eng.hawaii.edu/Tutor/vi.html">vi Tutorial</a><br>
+<a href="http://www.nano-editor.org/">nano-editor.org</a> - simple text editor </p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/vmstat.html b/help/en/bash/vmstat.html
new file mode 100644
index 0000000..d04b000
--- /dev/null
+++ b/help/en/bash/vmstat.html
@@ -0,0 +1,152 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>vmstat MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> vmstat </h1>
+<p> Report virtual memory statistics: processes, memory, paging, block IO, traps, and cpu activity.</p>
+<pre>Syntax
+ vmstat [-a] [-n] [<i>delay</i> [ <i>count</i>]]
+ vmstat [-f] [-s] [-m]
+ vmstat [-S unit]
+ vmstat [-d]
+ vmstat [-p disk partition]
+ vmstat [-V]
+
+Options
+
+ -a Display active/inactive memory, given a 2.5.41 kernel or better.
+
+ -f Display the number of forks since boot.
+ This includes the fork, vfork, and clone system calls, and is
+ equivalent to the total number of tasks created.
+ Each process is represented by one or more tasks, depending on
+ thread usage. This display does not repeat.
+
+ -m Displays slabinfo.
+
+ -n Cause the header to be displayed only once rather than periodically.
+
+ -s Display a table of various event counters and memory statistics.
+ This display does not repeat.
+
+ <i>delay</i> The delay between updates in seconds.
+ If no delay is specified, only one report is printed with the average values since boot.
+
+ <i>count</i> The number of updates. If no count is specified and delay is defined, count defaults to infinity.
+
+ -d Report disk statistics (2.5.70 or above required)
+
+ -p followed by some partition name for detailed statistics (2.5.70 or above required)
+
+ -S followed by k or K or m or M switches outputs between 1000, 1024, 1000000, or 1048576 bytes
+
+ -V Display version information. </pre>
+<p><b> Field Description For Vm Mode</b></p>
+<p>Procs</p>
+<p>r: The number of processes waiting for run time.<br>
+b: The number of processes in uninterruptible sleep.</p>
+<p>Memory</p>
+<p>swpd: the amount of virtual memory used.<br>
+free: the amount of idle memory.<br>
+buff: the amount of memory used as buffers.<br>
+cache: the amount of memory used as cache.<br>
+inact: the amount of inactive memory. (-a option)<br>
+active: the amount of active memory. (-a option)</p>
+<p>Swap</p>
+<p>si: Amount of memory swapped in from disk (/s).<br>
+so: Amount of memory swapped to disk (/s).</p>
+<p>IO</p>
+<p>bi: Blocks received from a block device (blocks/s).<br>
+bo: Blocks sent to a block device (blocks/s).</p>
+<p>System</p>
+<p>in: The number of interrupts per second, including the clock.<br>
+cs: The number of context switches per second.</p>
+<p>CPU</p>
+<p>These are percentages of total CPU time.</p>
+<p>us: Time spent running non-kernel code. (user time, including nice time)<br>
+sy: Time spent running kernel code. (system time)<br>
+id: Time spent idle. Prior to Linux 2.5.41, this includes IO-wait time.<br>
+wa: Time spent waiting for IO. Prior to Linux 2.5.41, included in idle.<br>
+st: Time stolen from a virtual machine. Prior to Linux 2.6.11, unknown.</p>
+<p><b>Field Description For Disk Mode</b></p>
+<p>Reads</p>
+<p>total: Total reads completed successfully<br>
+merged: grouped reads (resulting in one I/O)<br>
+sectors: Sectors read successfully<br>
+ms: milliseconds spent reading</p>
+<p>Writes</p>
+<p>total: Total writes completed successfully<br>
+merged: grouped writes (resulting in one I/O)<br>
+sectors: Sectors written successfully<br>
+ms: milliseconds spent writing</p>
+<p>IO</p>
+<p>cur: I/O in progress<br>
+s: seconds spent for I/O</p>
+<p><b>Field Description For Disk Partition Mode</b></p>
+<p>reads: Total number of reads issued to this partition<br>
+read sectors: Total read sectors for partition<br>
+writes : Total number of writes issued to this partition<br>
+requested writes: Total number of write requests made for partition</p>
+<p><b>Field Description For Slab Mode</b></p>
+<p>cache: Cache name<br>
+num: Number of currently active objects<br>
+total: Total number of available objects<br>
+size: Size of each object<br>
+pages: Number of pages with at least one active object<br>
+totpages: Total number of allocated pages<br>
+pslab: Number of pages per slab</p>
+<p><b>Notes</b></p>
+<p>vmstat does not require special permissions.</p>
+<p>These reports are intended to help identify system bottlenecks. Linux vmstat does not count itself as a running process.</p>
+<p>All linux blocks are currently 1024 bytes. Old kernels may report blocks as 512 bytes, 2048 bytes, or 4096 bytes.</p>
+<p>Since procps 3.1.9, vmstat lets you choose units (k, K, m, M) default is K (1024 bytes) in the default mode</p>
+<p>vmstat uses slabinfo 1.1 FIXME</p>
+<p>Files</p>
+<p>/proc/meminfo<br>
+/proc/stat<br>
+/proc/*/stat</p>
+<p><i> "The moment one definitely commits oneself then Providence moves too. All sorts of things occur to help one that would never otherwise have occurred&quot; - W.H. Murray</i></p>
+<p><b>Related</b>:</p>
+<p>iostat(1), sar(1), mpstat(1)<br>
+free - Display memory usage<br>
+<a href="ps.html">ps</a> - Process status<br>
+<a href="top.html">top</a> - List processes running on the system</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/watch.html b/help/en/bash/watch.html
new file mode 100644
index 0000000..85b3926
--- /dev/null
+++ b/help/en/bash/watch.html
@@ -0,0 +1,132 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>watch MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> watch</h1>
+<p>Execute a program periodically, showing output full screen</p>
+<pre>Syntax
+ watch [<em>options</em>] <em>command</em> <em>command_options</em>
+
+Options
+
+ -<em>n
+</em> --interval=n<seconds>
+ Specify an interval to run <em>command</em>
+
+ -d
+ --differences[=cumulative]]
+ Highlight the differences between successive updates
+
+ -h
+ --help Display Help
+
+ -v
+ --version Display version</pre>
+<p><span class="body"> watch runs command repeatedly, displaying its output (the
+ first screenfull). This allows you to watch the program<br>
+output change over time. </span><span class="body">By default, the program is run
+ every 2 seconds.<br>
+ <br>
+ The --cumulative option
+ makes highlighting "sticky", presenting a running display
+ of all positions that have ever changed.<br>
+ <br>
+ watch will run until interrupted.<br>
+ <br>
+ Note that <em>command</em> is given to "sh -c" which means that you
+ may need to use extra quoting to get the desired effect.<br>
+ <br>
+ POSIX option processing is used (i.e., option
+ processing stops at the first non-option argument). This
+ means that <em>command_options</em> don't get interpreted by
+ watch itself.</span></p>
+<p><b>Examples:</b></p>
+<pre> To watch for mail, you might do
+
+ watch -n 60 from
+
+ To watch the contents of a directory change, you could use
+
+ watch -d ls -l
+
+ If you're only interested in files owned by user joe, you
+ might use
+
+ watch -d 'ls -l | fgrep joe'
+
+ To see the effects of quoting, try these out
+
+ watch echo $$
+
+ watch echo '$$'
+
+ watch echo "'"'$$'"'"
+
+ You can watch for your administrator to install the latest
+ kernel with
+
+ watch uname -r
+
+ (Just kidding.)
+</pre>
+<p> Bugs<br>
+ Upon terminal resize, the screen will not be correctly
+ repainted until the next scheduled update. All differences highlighting is lost on that update as well.<br>
+ Non-printing characters are stripped from program output.
+ Use "cat -v" as part of the command pipeline if you want
+ to see them.</p>
+<p><i>&quot;Advertising may be described as the science of arresting
+ the human intelligence long enough to get money from it.&quot; - Stephen
+ Leacock </i><br>
+ <br>
+ <b> Related</b>:<br>
+ <br>
+ <a href="builtin.html">builtin</a> - Run a shell builtin<br>
+ <a href="crontab.html">crontab</a> - Schedule a command to run at a later time<br>
+ <a href="chroot.html">chroot</a> - Run a command with a different root directory<br>
+ <a href="exec.html">exec</a> - Execute a command<br>
+ <a href="if.html">if</a> - Conditionally perform a command<br>
+ <a href="nohup.html">nohup</a> - Run a command immune to hangups<br>
+ <a href="su.html">su</a> - Run a command with substitute user and group id<br>
+ <a href="watch.html">watch</a> - Execute/display a program periodically<br>
+ <a href="source.html">.period</a> - Run commands from a file<br>
+Equivalent Windows command: <a href="../term_tools/nt/schtasks.html">SCHTASKS</a> - Manage scheduled tasks.</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/wc.html b/help/en/bash/wc.html
new file mode 100644
index 0000000..56f1366
--- /dev/null
+++ b/help/en/bash/wc.html
@@ -0,0 +1,100 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>wc MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> wc</h1>
+<p> Print byte, word, and line counts, count the number of bytes,
+ whitespace-separated words, and newlines in each given FILE, or standard input
+if none are given or for a FILE of `-'.</p>
+<pre>Syntax
+ wc [<i>options</i>]... [<i>file</i>]...
+
+Options
+
+ -c
+ --bytes
+ --chars
+ Print only the byte counts.
+
+ -w
+ --words
+ Print only the word counts.
+
+ -l
+ --lines
+ Print only the newline counts.
+
+ -L
+ --max-line-length
+ Print only the length of the longest line per file,
+ and if there is more than one file it prints the
+ maximum (not the sum) of those lengths. </pre>
+<p> `wc' prints one line of counts for each file, and if the file
+ was given as an argument, it prints the file name following the counts. <br>
+ <br>
+ If more than one FILE is given, `wc' prints a final line containing the cumulative
+ counts, with the file name `total'. The counts are printed in this order: newlines,
+ words, bytes. <br>
+ <br>
+ By default, each count is output right-justified in a 7-byte field with one
+ space between fields so that the numbers and file names line up nicely in columns.
+ However, POSIX requires that there be exactly one space separating columns.
+ You can make `wc' use the POSIX-mandated output format by setting the `POSIXLY_CORRECT'
+ environment variable. <br>
+ <br>
+ By default, `wc' prints all three counts. Options can specify that only certain
+ counts be printed. Options do not undo others previously given, so <span class="telety">wc --bytes --words</span>will print both the byte counts and the word counts. </p>
+<p><b>Examples</b></p>
+<p>Count the number of lines in file1.txt </p>
+<p><span class="telety">$ wc -l &lt; file1.txt </span></p>
+<p>Count the number of words in file2.txt </p>
+<p><span class="telety">$ wc -w file2.txt </span></p>
+<p>Count the number of words by pasting from the clipboard: </p>
+<p><span class="telety">$ wc -l<br>
+(paste the list into the window and then type CTRL-D)</span></p>
+<p> <i>"One look is worth a thousand words" - Fred
+ R. Barnard</i> </p>
+<p><b>Related</b>:</p>
+<p><a href="http://www.linuxjournal.com/article/1327">wc examples</a> - Linux Journal <br>
+ <a href="cat.html">cat</a> - Display the contents of a file<br>
+ <a href="cal.html">cal</a> - Display a calendar<br>
+<a href="units.html"> units</a> - Convert units from one scale to another </p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/whereis.html b/help/en/bash/whereis.html
new file mode 100644
index 0000000..77fb19b
--- /dev/null
+++ b/help/en/bash/whereis.html
@@ -0,0 +1,101 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>whereis MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> whereis</h1>
+<p>Search $path, man pages and source files for an application file.</p>
+<p>The supplied filenames are first stripped of leading pathname
+ components and any (single) trailing extension of the form .ext (for example,
+ .c). Prefixes of s. resulting from use of source code control are also dealt
+ with. whereis then attempts to locate the desired program in a list of standard
+Linux directories (e.g., /bin, /etc, /usr/bin, /usr/local/bin/, etc.).</p>
+<pre>Syntax
+ whereis [<i>options</i>] <i>files</i>
+
+Options
+ -b Search only for binaries.
+
+ -B <i>directories</i>
+ Change or otherwise limit the <i>directories</i> to search for
+ binaries.
+
+ -f Terminate the last directory list and signal the
+ start of filenames;
+ Required when any of the -B, -M, or -S options are used.
+
+ -m Search only for manual sections.
+
+ -M <i>directory</i>
+ Change or otherwise limit the directories to search for
+ manual sections.
+
+ -s Search only for sources.
+
+ -S <i>directory</i>
+ Change or otherwise limit the directories to search for
+ sources.
+
+ -u Search for unusual entries, that is, files that do <b>not</b>
+ have one entry of each requested type.
+ Thus, the command whereis -m -u * asks for those files
+ in the current directory that have no documentation.
+
+Example
+Find all files in /usr/bin that are not documented in /usr/man/man1
+but that have source in /usr/src:
+
+% cd /usr/bin
+% whereis -u -M /usr/man/man1 -S /usr/src -f *
+</pre>
+<p><i>"If I am not for myself, Who will be for me? <br>
+ And if I am only for myself, What am I? <br>
+ And if not now, When?" - Rabbi Hillel</i><br>
+ <br>
+ <b> Related</b>:<br>
+ <br>
+ <a href="pwd.html">pwd</a> - Print Working Directory <br>
+ <a href="hash.html">hash</a> - Remember the full pathname of a name argument
+ <br>
+ <a href="type.html">type</a> - Describe a command <br>
+ <a href="which.html">which</a> - Search the user's $path for a program file<br>
+Equivalent Windows commands: <a href="../term_tools/nt/where.html">WHERE</a> - Locate and display files in a directory
+tree. </p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/which.html b/help/en/bash/which.html
new file mode 100644
index 0000000..2ea1a61
--- /dev/null
+++ b/help/en/bash/which.html
@@ -0,0 +1,150 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>which MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> which</h1>
+<p>Locate a program file in the user's path. </p>
+<p>For each of its arguments which prints to stdout the full path
+ of the executable(s). It does this by searching the directories listed in the
+environment variable PATH.</p>
+<pre>Syntax
+ which [<em>options</em>] [--] <em>program_name</em> [...]
+
+Options
+ --all, -a
+ Print all matching executables in PATH, not just the
+ first.
+
+ --read-alias, -i
+ Read aliases from stdin, reporting matching ones on
+ stdout. This is useful in combination with using an
+ alias for which itself. For example
+ alias which='alias | which -i'.
+
+ --skip-alias
+ Ignore option --read-alias, if any. This is useful to
+ explicity search for normal binaries, while using the
+ --read-alias option in an alias for which.
+
+ --skip-dot
+ Skip directories in PATH that start with a dot.
+
+ --skip-tilde
+ Skip directories in PATH that start with a tilde and
+ executables which reside in the HOME directory.
+
+ --show-dot
+ If a directory in PATH starts with a dot and a matching
+ executable was found for that path, then print
+ "./program_name" rather than the full path.
+
+ --show-tilde
+ Output a tilde when a directory matches the HOME
+ directory. This option is ignored when which is
+ invoked as root.
+
+ --tty-only
+ Stop processing options on the right if not on tty.
+
+ --version, -v, -V
+ Print version information on standard output then exit
+ successfully.
+
+ --help
+ Print usage information on standard output then exit
+ successfully.
+
+RETURN VALUE
+ Which returns the number of failed arguments, or -1 when
+ no programname was given.
+
+EXAMPLE
+ A useful way to use this utility is by adding an alias for
+ which like the following:
+
+ alias which='which --tty-only --show-tilde --show-dot'
+
+ This will print the readable ~/ and ./ when starting which
+ from your prompt, while still printing the full path when
+ used from a script:
+
+ > which q2
+ ~/bin/q2
+ > echo `which q2`
+ /home/carlo/bin/q2
+
+ Aliases are also supported, through the use of an alias
+ for which itself. An example alias for which that is
+ using this feature is as follows:
+
+ alias which='alias | which --tty-only --read-alias --show-tilde --show-dot'
+
+ This will print the output of alias for each alias that
+ matches one of the given arguments. For example, using
+ this alias on itself in a tcsh:
+
+ $ alias which alias \| /usr/bin/which -i !\*
+ $ which which
+ which (alias | ./which -i !*)
+ /usr/bin/which
+
+BUGS
+ The HOME directory is determined by looking for the HOME
+ environment variable, which aborts when this variable
+ doesn't exist. Which will consider two equivalent directories
+ to be different when one of them contains a path
+ with a symbolic link.</pre>
+<p><i>&quot;A man should never be ashamed to own he has been in the
+ wrong, which is saying in other words, that he is wiser today than he was yesterday&quot;
+ - Alexander
+ Pope (thoughts on various subjects) </i><br>
+ <br>
+ <b> Related</b>:<br>
+ <br>
+ bash(1)<br>
+ <a href="pwd.html">pwd</a> - Print Working Directory <br>
+ <a href="hash.html">hash</a> - Remember the full pathname of a name argument
+ <br>
+ pathchk - Check file name portability <br>
+<a href="whereis.html">whereis</a> - Search the user's $path, man pages and source files for a program<br>
+Equivalent Windows commands: <a href="../term_tools/nt/where.html">WHERE</a> - Locate and display files in a directory
+tree. </p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/while.html b/help/en/bash/while.html
new file mode 100644
index 0000000..4f9abee
--- /dev/null
+++ b/help/en/bash/while.html
@@ -0,0 +1,59 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>while MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> while</h1>
+<p>Execute <var>consequent-commands</var> as long as <var>test-commands</var>
+has an exit status of zero</p>
+<pre>Syntax
+ while <var>test-commands</var>; do <var>consequent-commands</var>; done</pre>
+<p>The return status is the exit status of the last command executed
+in <var>consequent-commands</var>, or zero if none were executed. </p>
+<p><em>&ldquo;Men talk of killing time, while time quietly kills them.&rdquo; - Dion Boucicault
+</em></p>
+<p><b>Related</b>:<a href="for.html"><br>
+ </a><a href="case.html"><br>
+ case</a> - Conditionally perform a command<a href="for.html"><br>
+ for</a> - Expand <var>words</var>, and execute <var>commands</var><br>
+ <a href="if.html">if</a> - Conditionally perform a command<br>
+ <a href="until.html">until</a> - Execute commands (until error)<br>
+Equivalent Windows commands: <a href="../term_tools/nt/if.html">IF</a> - Conditionally perform a command.</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/who.html b/help/en/bash/who.html
new file mode 100644
index 0000000..bed148c
--- /dev/null
+++ b/help/en/bash/who.html
@@ -0,0 +1,125 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>who MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> who</h1>
+<p>Print who is currently logged in</p>
+<pre>Syntax
+ who [<em>options</em>] [<em>file</em>] [am i]
+
+Options
+
+ -m
+ Print the current user id, name and domain
+ (Same as `who am i')
+
+ -q
+ --count
+ Print only the login names and the number of users logged on.
+ Overrides all other options.
+
+ -s
+ Ignored; for compatibility with other versions of `who'.
+
+ -i
+ -u
+ --idle
+ After the login time, print the number of hours and minutes that
+ the user has been idle. `.' means the user was active in last
+ minute. `old' means the user was idle for more than 24 hours.
+
+ -l
+ --lookup
+ Attempt to canonicalize hostnames found in utmp through a DNS
+ lookup. This is not the default because it can cause significant
+ delays on systems with automatic dial-up internet access.
+
+ -H
+ --heading
+ Print a line of column headings.
+
+ -w
+ -T
+ --mesg
+ --message
+ --writable
+ After each login name print a character indicating the user's
+ message status:
+
+ + allowing `write' messages
+ - disallowing `write' messages
+ ? cannot find terminal device
+
+</pre>
+<p>The who command differs from whoami in that it provides a list of all users currently logged into the system as well as additional information about each of those users (including login times and terminal numbers). It also differs in that, in the event of a change in ownership of a login session through the use of the su command, it reports the original owner of the session, whereas whoami provides the user name of the effective (i.e., current) owner of the session. </p>
+<p>If given no non-option arguments, `who' prints the following information
+ for each user currently logged on:<br>
+ <br>
+ <span class="telety">login name,<br>
+ terminal line,<br>
+ login time,<br>
+ remote hostname or X display. </span><br>
+ <br>
+ If given one non-option argument, `who' uses that instead of `/var/run/utmp'
+ as the name of the file containing the record of users logged on. `/var/run/wtmp'
+ is commonly given as an argument to `who' to look at who has previously logged
+ on. <br>
+ <br>
+ If given two non-option arguments, `who' prints only the entry for the user
+ running it (determined from its standard input), preceded by the hostname. Traditionally,
+ the two arguments given are `am i', as in `who am i'.<br>
+ <br>
+ <i>&quot;It is awful work this love and prevents all a mans projects of good
+ or glory&quot; - Lord
+ Byron </i> </p>
+<p><b>Related</b>:<br>
+ <a href="env.html"><br>
+ </a> <a href="groups.html">groups</a> - Print group names a user is in<br>
+ <a href="hostname.html">hostname</a> - Print or set system name <br>
+ <a href="id.html">id</a> - Print user and group id's <br>
+ <a href="uname.html">uname</a> - Print system information<br>
+ <a href="logname.html">logname</a> - Print current login name<br>
+ <a href="users.html">users</a> - Print login names of users currently logged
+ in <br>
+w - Show who is logged on and what they are doing.<br>
+ whoami - Print the current user id and name (`id -un') <br>
+Equivalent Windows command: <a href="../term_tools/nt/echo.html"> ECHO </a> %USERNAME%</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/whoami.html b/help/en/bash/whoami.html
new file mode 100644
index 0000000..b6326bd
--- /dev/null
+++ b/help/en/bash/whoami.html
@@ -0,0 +1,59 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>whoami MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1>whoami</h1>
+<p>Print the current user id and name.</p>
+<pre>Syntax
+ whoami [<i>options</i>]
+
+Options
+ --help Display Help
+ --version Display program version info
+</pre>
+<p>whoami produces the same result as the <span class="telety">id -un</span> command (the <span class="telety">id</span> command by default provides more detailed information)</p>
+<p><i>&quot;He travels the fastest who travels alone&quot; - Rudyard Kipling</i></p>
+
+<p><b>Related:</b></p>
+<p> <a href="id.html">id</a> - Print user and group id's<br>
+ <a href="who.html">who</a> -Print all usernames currently logged in<br>
+Equivalent Windows command: %username% </p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/write.html b/help/en/bash/write.html
new file mode 100644
index 0000000..3dd3826
--- /dev/null
+++ b/help/en/bash/write.html
@@ -0,0 +1,69 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>write MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> write</h1>
+<p>Send a message to another user </p>
+<pre>Syntax:
+
+ write <i>user</i> [<i>ttyname</i>]</pre>
+<p>
+Write allows you to communicate with other users, by copying lines from your terminal to theirs.</p>
+<p>When you run the write command, the user you are writing to gets a message of the form:</p>
+<p> Message from yourname@yourhost on yourtty at hh:mm ...</p>
+<p>Any further lines you enter will be copied to the specified user's terminal. If the other user wants to reply, they must run write as well.</p>
+<p>When you are done, type an end-of-file or interrupt character. The other user will see the message EOF indicating that the conversation is over.</p>
+<p>You can prevent people (other than the super-user) from writing to you with the mesg(1) command. Some commands, for example nroff(1) and pr(1), may disallow writing automatically, so that your output isn't overwritten.</p>
+<p>If the user you want to write to is logged in on more than one terminal, you can specify which terminal to write to by specifying the terminal name as the second operand to the write command. Alternatively, you can let write select one of the terminals - it will pick the one with the shortest idle time. This is so that if the user is logged in at work and also dialed up from home, the message will go to the right place.</p>
+<p>The traditional protocol for writing to someone is that the string '-o', either at the end of a line or on a line by itself, means that it's the other person's turn to talk. The string 'oo' means that the person believes the conversation to be over. </p>
+<p><b>Example</b></p>
+<p class="telety">$ Write maude <br>
+This is a test message
+<span class="telety"> &lt;CTRL-D&gt; </span> </p>
+<p><i>&quot;We do not write because we want to; we write because we have to&quot; - W. Somerset Maugham</i></p>
+<p><b>Related</b>:</p>
+<p>mesg y - Allow
+write access to your terminal <br>
+mesg n - Disallow
+write access to your terminal <br>
+talk - Talk to another user <br>
+<a href="who.html">who</a> - Print all usernames currently logged in</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/xargs.html b/help/en/bash/xargs.html
new file mode 100644
index 0000000..bec567a
--- /dev/null
+++ b/help/en/bash/xargs.html
@@ -0,0 +1,159 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>xargs MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> xargs</h1>
+<p> Execute a command, passing constructed argument list(s).
+ The arguments are typically
+ a long list of filenames (generated by ls or find) that are passed
+to xargs via a pipe. </p>
+<pre>Syntax
+ xargs [<i>options</i>] [<i>command</i>]
+
+Options
+ -0
+ --null
+ Expect filenames to be terminated by NULL instead of whitespace.
+ Do not treat quotes or backslashes specially.
+
+ -e[<em>string</em>]
+ -E[<em>string</em>]
+ --eof[=<em>string</em>]
+ Set EOF to _ or, if specified, to string.
+
+ --help
+ Print a summary of the options to xargs and then exit.
+
+ -i[<em>string</em>]
+ -I[<em>string</em>]
+ --replace[=<em>string</em>]
+ Edit all occurrences of , or string, to the names read in
+ on standard input. Unquoted blanks are not considered argument terminators.
+ Implies -x and -l 1.
+
+ -l[<em>lines</em>]
+ -L[<em>lines</em>]
+ --max-lines[=<em>lines</em>]
+ Allow no more than 1, or lines, nonblank input lines on the command line.
+ Implies -x.
+
+ -n <em>args</em>
+ --max-args=<em>args</em>
+ Allow no more than args arguments on the command line.
+ May be overridden by -s.
+
+ -p
+ --interactive
+ Prompt for confirmation before running each command line. Implies -t.
+
+ -P <em>max</em>
+ --max-procs=<em>max</em>
+ Allow no more than max processes to run at once.
+ The default is 1. A maximum of 0 allows as many as possible to run at once.
+
+ -r
+ --no-run-if-empty
+ Do not run command if standard input contains only blanks.
+
+ -s <em>max</em>
+ --max-chars=<em>max</em>
+ Allow no more than <i>max</i> characters per command line.
+
+ -t
+ --verbose
+ Print the command line (on standard error) before executing.
+
+ -x
+ --exit
+ If the maximum size (as specified by -s) is exceeded, exit.
+
+ --version
+ Print the version number of xargs and then exit.
+</pre>
+<p>xargs can execute the <i>command</i> supplying some initial arguments directly, and reading the remaining arguments from
+standard input (or piped input). </p>
+<p>xargs passes arguments
+to <i>command </i>in several bundles, this allows <i>command</i> to process more
+arguments than it could normally handle at once. </p>
+<p>Arguments in the standard input must be separated by unquoted blank characters, or unescaped blank characters or newline characters.<br>
+Characters can be quoted by enclosing them in &quot;double-quotes&quot; (non-double-quote and non-newline chars only).<br>
+Characters can be quoted by enclosing them in 'apostrophes' (non-apostrophe and non-newline chars only).<br>
+Any unquoted character can be escaped by preceding it with a backslash.</p>
+<p>e.g. file1 file2 &quot;file three&quot; 'file four' file\ five</p>
+<p>If <i>command</i> is omitted then the equivalent of /bin/echo is used.</p>
+<p>If all invocations of <i>command </i>return exit status 0 then xargs will return 0, an error of 127=<i>command</i> not found.</p>
+<p><b>Examples
+</b>
+</p>
+<p>Find all the .mp3 files in the music folder and pass to the ls command, <span class="code">-print0</span> is required if any filenames contain whitespace.:</p>
+<pre>
+ find ./music -name &quot;*.mp3&quot; -print0 | xargs -0 ls
+</pre>
+<p>Find all files in the work folder, pass to grep and search for profit:</p>
+<pre>
+ find ./work -print | xargs grep &quot;profit&quot;
+</pre>
+<p>Find and delete files which have been modified in the last 30 minutes:</p>
+<pre>
+ find ./work -mmin -30 | xargs -0 rm
+</pre>
+<p>Delete all files from the work directory:</p>
+<pre>
+ find ./work -print0 | xargs -0 rm</pre>
+<p>
+(Use this when rm on a large directory gives: Argument list too long)<br>
+
+Run diff on file pairs (e.g., f1.a and f1.b, f2.a and f2.b ...):</p>
+<pre>
+ echo $* | xargs -n2 diff</pre>
+<p>
+The previous line would be invoked as a shell script, specifying filenames as arguments.<br>
+<br>
+Display file, one word per line (same as deroff -w):</p>
+<pre> cat <i>file</i> | xargs -n1
+</pre>
+<p>Move files in <i>olddir</i> to <i>newdir</i>, showing each command:</p>
+<pre>
+ ls olddir | xargs -i -t mv olddir/ newdir/</pre>
+<p> <b>Related</b>:<br>
+ <br>
+<a href="env.html">env</a> - Display, set, or remove environment variables</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/xdg-open.html b/help/en/bash/xdg-open.html
new file mode 100644
index 0000000..57c9bb0
--- /dev/null
+++ b/help/en/bash/xdg-open.html
@@ -0,0 +1,76 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>xdg-open MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem -->
+<h1>xdg-open</h1>
+<p>Open a file or URL in the user's preferred application.</p>
+<pre>Syntax
+ xdg-open <i>file
+
+ </i>xdg-open<i> URL</i>
+
+ xdg-open --help
+
+ xdg-open --manual
+
+ xdg-open --version
+
+Options:
+ files The filename(s) to open, wildcards are accepted.</pre>
+<p> If a URL is provided the URL will be opened in the user's preferred web browser. If a file is provided the file will be opened in the preferred application for files of that type. xdg-open supports file, ftp, http and https URLs.</p>
+<p>xdg-open is for use inside a desktop session only. It is not recommended to use xdg-open as root. </p>
+<p><b>Exit Codes
+</b></p>
+<p>A non-zero exit code indicates failure:</p>
+<p>0 Success<br>1 Error in command line syntax.<br>2 One of the files passed on the command line did not exist.<br>3 A required tool could not be found.<br>4 The action failed.</p>
+<p><b>Examples</b></p>
+<p class="code">$ xdg-open 'http://www.ss64.com/'</p>
+<p>Opens the SS64.com website in the user's default browser</p>
+<p class="code">$ xdg-open /tmp/foxtrot_the_cat.png</p>
+<p>Opens a cat picture in the user's default image viewing application. </p>
+<p><i>&ldquo;Do not run; scorn running with thy heels&rdquo; - Shakespeare</i></p>
+<p><b>Related</b>:<br>
+ <br>
+<a href="kill.html">kill</a> - Stop a process from running<br>
+<a href="open.html">open</a> - Open a file in its default application<br>
+Equivalent Windows command: <a href="../term_tools/nt/start.html">START</a> - Start a program or command.</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/bash/yes.html b/help/en/bash/yes.html
new file mode 100644
index 0000000..e7b6a81
--- /dev/null
+++ b/help/en/bash/yes.html
@@ -0,0 +1,60 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+<link rel="STYLESHEET" href="../term_tools/main.css" type="text/css">
+<title>yes MAN Page</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><!-- #BeginLibraryItem "/Library/head_bash.lbi" --><div id="nav-menu">
+<ul>
+<li><a class="rl" href="../term_tools/index.html"><img src="../term_tools/images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../term_tools/bash"><img src="../term_tools/images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li><!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com/bash/">
+</div>
+</form></li>
+<li><a class="rr" href="syntax.html"><img src="../term_tools/images/syntax-r.gif" title="Bash Syntax"></a></li>
+</ul>
+</div> <!-- #EndLibraryItem --><h1> yes</h1>
+<p>`yes' prints the command line arguments, separated by spaces and
+followed by a newline, forever until it is killed.</p>
+<pre> If no arguments are given, it prints `y' followed by
+ a newline forever until killed.
+
+ The only options are a lone `--help' or `--version'.</pre>
+<p><b>Related</b>:<br>
+ <br>
+ <a href="false.html">false</a> - Do nothing, unsuccessfully<br>
+ <a href="true.html">true</a>
+ - Do nothing, successfully<br>
+
+ Equivalent Windows command:
+ <span class="telety">ECHO Y | <i>command</i></span><br>
+ <br>
+</p>
+<!-- #BeginLibraryItem "/Library/foot_bash.lbi" --><p align="left"><script type="text/javascript"><!--
+google_ad_client = "pub-6140977852749469";
+google_ad_width = 300;
+google_ad_height = 250;
+google_ad_format = "300x250_as";
+google_ad_type = "text_image";
+google_ad_channel ="1984328893";
+google_color_border = "CCCCCC";
+google_color_bg = "CCCCCC";
+google_color_link = "000000";
+google_color_text = "333333";
+google_color_url = "0000FF";
+//--></script>
+<script type="text/javascript"
+ src="http://pagead2.googlesyndication.com/pagead/show_ads.js">
+</script><br>
+</p>
+<div align="center"><hr size="1">
+ <p id="top"><a href="#"><img src="../term_tools/images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+ <p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html>
diff --git a/help/en/term_tools/images/bash-l.gif b/help/en/term_tools/images/bash-l.gif
new file mode 100644
index 0000000..2b4ef64
--- /dev/null
+++ b/help/en/term_tools/images/bash-l.gif
Binary files differ
diff --git a/help/en/term_tools/images/bash-r.gif b/help/en/term_tools/images/bash-r.gif
new file mode 100644
index 0000000..77ae9e0
--- /dev/null
+++ b/help/en/term_tools/images/bash-r.gif
Binary files differ
diff --git a/help/en/term_tools/images/forum-r.gif b/help/en/term_tools/images/forum-r.gif
new file mode 100644
index 0000000..750e5fe
--- /dev/null
+++ b/help/en/term_tools/images/forum-r.gif
Binary files differ
diff --git a/help/en/term_tools/images/links-r.gif b/help/en/term_tools/images/links-r.gif
new file mode 100644
index 0000000..41c9667
--- /dev/null
+++ b/help/en/term_tools/images/links-r.gif
Binary files differ
diff --git a/help/en/term_tools/images/nt-r.gif b/help/en/term_tools/images/nt-r.gif
new file mode 100644
index 0000000..96003df
--- /dev/null
+++ b/help/en/term_tools/images/nt-r.gif
Binary files differ
diff --git a/help/en/term_tools/images/oracle-r.gif b/help/en/term_tools/images/oracle-r.gif
new file mode 100644
index 0000000..31a73be
--- /dev/null
+++ b/help/en/term_tools/images/oracle-r.gif
Binary files differ
diff --git a/help/en/term_tools/images/osx-r.gif b/help/en/term_tools/images/osx-r.gif
new file mode 100644
index 0000000..c151780
--- /dev/null
+++ b/help/en/term_tools/images/osx-r.gif
Binary files differ
diff --git a/help/en/term_tools/images/ps-r.gif b/help/en/term_tools/images/ps-r.gif
new file mode 100644
index 0000000..7f2e04c
--- /dev/null
+++ b/help/en/term_tools/images/ps-r.gif
Binary files differ
diff --git a/help/en/term_tools/images/roll-left.png b/help/en/term_tools/images/roll-left.png
new file mode 100644
index 0000000..5565cd4
--- /dev/null
+++ b/help/en/term_tools/images/roll-left.png
Binary files differ
diff --git a/help/en/term_tools/images/roll-right.png b/help/en/term_tools/images/roll-right.png
new file mode 100644
index 0000000..dea4f8a
--- /dev/null
+++ b/help/en/term_tools/images/roll-right.png
Binary files differ
diff --git a/help/en/term_tools/images/sql-r.gif b/help/en/term_tools/images/sql-r.gif
new file mode 100644
index 0000000..1250e91
--- /dev/null
+++ b/help/en/term_tools/images/sql-r.gif
Binary files differ
diff --git a/help/en/term_tools/images/ss64.gif b/help/en/term_tools/images/ss64.gif
new file mode 100644
index 0000000..e602c72
--- /dev/null
+++ b/help/en/term_tools/images/ss64.gif
Binary files differ
diff --git a/help/en/term_tools/images/ss64.png b/help/en/term_tools/images/ss64.png
new file mode 100644
index 0000000..51ffb00
--- /dev/null
+++ b/help/en/term_tools/images/ss64.png
Binary files differ
diff --git a/help/en/term_tools/images/syntax-r.gif b/help/en/term_tools/images/syntax-r.gif
new file mode 100644
index 0000000..7950c05
--- /dev/null
+++ b/help/en/term_tools/images/syntax-r.gif
Binary files differ
diff --git a/help/en/term_tools/images/top-4.gif b/help/en/term_tools/images/top-4.gif
new file mode 100644
index 0000000..8207d36
--- /dev/null
+++ b/help/en/term_tools/images/top-4.gif
Binary files differ
diff --git a/help/en/term_tools/images/vb-r.gif b/help/en/term_tools/images/vb-r.gif
new file mode 100644
index 0000000..b863372
--- /dev/null
+++ b/help/en/term_tools/images/vb-r.gif
Binary files differ
diff --git a/help/en/term_tools/index.html b/help/en/term_tools/index.html
new file mode 100644
index 0000000..b6d9ee3
--- /dev/null
+++ b/help/en/term_tools/index.html
@@ -0,0 +1,103 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
+<html>
+<head>
+<link rel="STYLESHEET" href="main.css" type="text/css">
+<title>SS64.com Command line reference</title>
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+<META NAME="Author" CONTENT="Simon Sheppard">
+<META NAME="Description" CONTENT="A Command line reference for Windows, Powershell, vbscript, bash, OSX, Oracle and SQL Server">
+<META NAME="Keywords" CONTENT="Command line, Windows XP, Linux, Oracle, OS X, Bash, Batch file, Robocopy, for, grep, vi">
+<link rel="alternate" type="application/rss+xml" title="RSS" href="rss.xml">
+<link rel="search" href="http://ss64.com/opensearchdescription.xml" type="application/opensearchdescription+xml" title="SS64.com">
+<style type="text/css">
+<!--
+#goog
+{
+position:absolute;
+top:17px;
+left:141px;
+width: 350px;
+}
+#goog input{height: 20px;vertical-align: middle;margin-right:7px;}
+#goog .submit{height: 30px; width: 89px;}
+
+td a{outline:none;}
+.logo {margin:0 0.15em}
+
+.menu a{height:47px; line-height:47px; width:115px; display:block; color:#0d2474; border-width: 0px; text-decoration:none; text-align:center;outline:none;}
+.menu img{border-width: 0px;}
+.menu a:hover { background-position: 0 -47px;}
+.menu a:active { background-position: 0 -94px;}
+-->
+</style>
+</head>
+<body><img class="logo" src="images/ss64.png" alt="SS64.com" width="115" height="47">
+<p>Command line reference: Database and Operating&nbsp;Systems.</p>
+<div id="goog">
+<!-- Search Google -->
+<form action="http://www.google.com/search" method="get">
+<input name="q" type="text" class="body" size="20">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com">
+</form>
+</div>
+
+<table border="0" width="100%" cellspacing="0" class="body">
+ <tr>
+<td width="11%">&nbsp;</td>
+<td width="12%"><p align="left"><b><a href="ora/">Oracle database</a></b><br>
++
+<a href="orad/" title="Oracle data dictionary"> dict.</a></p></td>
+ <td width="10%">
+ <div class="menu"><a class="rr" href="ora/"><img src="images/oracle-r.gif" alt="Oracle" ></a></div></td>
+ <td width="16%" align="left">&nbsp;</td>
+ <td width="27%" align="left">
+ <div align="left"><p align="left"><b><a href="nt/">Windows XP</a></b> <br>
++ Resource Kits, <a href="nt/robocopy.html" title="Robust File and Folder Copy">Robocopy</a></p></div></td>
+ <td width="24%"><div class="menu"><a class="rr" href="nt/"><img src="images/nt-r.gif" alt="CMD Commands" ></a></div></td>
+ </tr>
+<tr>
+<td>&nbsp;</td>
+<td><p align="left"><b><a href="bash/">BASH</a></b><br>
+GNU Linux </p></td>
+<td><div class="menu"><a class="rr" href="bash/"><img src="images/bash-r.gif" alt="Bash"></a></div></td>
+<td align="left">&nbsp;</td>
+<td align="left"><p align="left"><b><a href="vb/">VBScript Commands</a></b></p></td>
+<td width="24%"><div class="menu"><a class="rr" href="vb/"><img src="images/vb-r.gif" alt="VBScript" ></a></div> </td>
+</tr>
+<tr>
+<td>&nbsp;</td>
+<td><p align="left"><b><a href="osx/">OS X commands</a></b><br>
+Leopard 10.5
+</p></td>
+ <td> <div class="menu"><a class="rr" href="osx/"><img src="images/osx-r.gif" alt="OS X Commands" ></a></div></td>
+ <td align="left">&nbsp;</td>
+ <td align="left"><p align="left"><b><a href="ps/">Windows PowerShell</a></b></p></td>
+ <td width="24%"><div class="menu"><a class="rr" href="ps/"><img src="images/ps-r.gif" alt="Powershell" ></a></div></td>
+</tr>
+ <tr>
+<td><p><FONT size="-1"><br>
+</FONT><font size="-1"> </font></p></td>
+<td><p><b><a href="http://ss64.org/">Discussion <br>Forums </a></b></p></td>
+ <td><div class="menu"><a class="rr" href="http://ss64.org/"><img src="images/forum-r.gif" alt="Forum" width="115" height="47" border="0" ></a></div></td>
+ <td align="left">&nbsp;</td>
+ <td align="left"><p align="left"><b><a href="sql/">SQL Server database</a></b></p></td>
+ <td width="24%"> <div class="menu"><a class="rr" href="sql/"><img src="images/sql-r.gif" alt="SQL Server" ></a></div> </td>
+ </tr>
+</table>
+<br>
+<div align="center">
+<hr size="1">
+<p class="tagline">&copy; Copyright SS64.com 1999-2010<br>
+<a href="docs/copyright.html">Some rights reserved</a><br>
+<a href="docs/">Last update</a>: 7th December 2010<br>
+</p>
+</div>
+
+<div style=" display:none;">
+<img src="images/roll-left.png"
+alt="p" height="115" width="141" >
+</div>
+
+</body>
+</html>
diff --git a/help/en/term_tools/library/library.info b/help/en/term_tools/library/library.info
new file mode 100644
index 0000000..5d7f44d
--- /dev/null
+++ b/help/en/term_tools/library/library.info
@@ -0,0 +1,9 @@
+[Library]
+name = cmnd_tools
+global_name = cmnd_tools
+long_name = cmnd_tools
+category = media
+library_version = 1
+host_version = 1
+l10n = false
+locale = en
diff --git a/help/en/term_tools/links/bash-kier-ubuntu.jpg b/help/en/term_tools/links/bash-kier-ubuntu.jpg
new file mode 100644
index 0000000..d9afca5
--- /dev/null
+++ b/help/en/term_tools/links/bash-kier-ubuntu.jpg
Binary files differ
diff --git a/help/en/term_tools/links/bash.html b/help/en/term_tools/links/bash.html
new file mode 100644
index 0000000..c466558
--- /dev/null
+++ b/help/en/term_tools/links/bash.html
@@ -0,0 +1,161 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"><html>
+<head>
+ <link rel="STYLESHEET" href="../main.css" type="text/css">
+ <title>Linux Books, Software and websites</title>
+ <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
+</head><body>
+<div id="nav-menu">
+<ul>
+<li><a class="rl" href="../index.html"><img src="../images/ss64.gif" title="Home" alt="Home"></a></li>
+<li><a class="rl" href="../bash/"><img src="../images/bash-l.gif" title="bash" alt="bash"></a></li>
+<li>
+<!-- Search Google -->
+<form action="http://www.google.com/search" method="get" style="margin:0px;padding:0px;">
+<div align="right">
+<input name="q" type="text" class="body" size="25">
+<input class="submit" type="submit" value="Search">
+<input type="hidden" name="q" value="site:ss64.com">
+</div>
+</form>
+</li>
+</ul>
+</div>
+<h1>Links to GNU/Linux Websites and Books</h1>
+<p><b><a name="news"></a></b><b class="head">Man Pages</b></p>
+<blockquote>
+<p><a href="http://www.oreillynet.com/linux/cmd/">Alphabetical Directory of Linux Commands</a> - O`Reilly<br>
+<a href="http://www.linuxcommand.org/superman_pages.php">LinuxCommand.org</a> - SuperMan pages<br>
+<a href="http://techpubs.sgi.com/library/tpl/cgi-bin/browse.cgi?db=man&amp;coll=linux&amp;pth=/man1">Linux Man pages</a> - Searchable<br>
+<a href="http://www.gnu.org/manual/"> GNU Bash Manual</a> - gzip archives<br>
+<a href="http://en.wikipedia.org/wiki/List_of_TCP_and_UDP_port_numbers">TCP and UDP port numbers </a>- wikipedia </p>
+</blockquote>
+<p class="head"> <b>Tutorials</b></p>
+<blockquote>
+ <p> <a href="http://tldp.org/LDP/Bash-Beginners-Guide/html/index.html">Bash Guide for beginners</a> - Machtelt Garrels<br>
+<a href="http://mywiki.wooledge.org/BashFAQ">Greg Wooledge Bash FAQ</a><br>
+<a href="http://www.tldp.org/">The Linix Documentation Project </a><br>
+<a href="http://www.dsl.org/cookbook/cookbook_toc.html">The Linux Cookbook</a> - Tips and Techniques<br>
+<a href="http://www.justlinux.com/nhf/">Justlinux.com</a> - Newbie help pages<br>
+<a href="http://www.ukuug.org/events/linux2003/papers/bash_tips/">bash tips</a> -
+Configure the bash terminal<br>
+
+<a href="http://wooledge.org/mywiki/BashPitfalls">Bash pitfalls</a> -
+GreyCat's wiki<br>
+<a href="http://www.ibm.com/developerworks/views/linux/libraryview.jsp">IBM DeveloperWorks</a> -
+Linux Technical library<br>
+<a href="http://www.xminc.com/linux/linuxcheatsheet.pdf">Linux cheat sheet</a> (PDF) - Anthony Barker<br>
+<a href="http://bash.cyberciti.biz/guide/Main_Page">Linux Shell Scripting Tutorial</a> - LSST<br>
+<a href="http://cb.vu/unixtoolbox.xhtml">Unix/Linux/BSD Toolbox</a> - concise summary of commands <br>
+<a href="http://en.tldp.org/LDP/abs/html/index.html">Advanced Bash-Scripting Guide </a>- Mendel Cooper <br>
+<a href="http://www.comp.eonworks.com/scripts/scripts.html">Administration shell scripts</a> - Dawid Michalczyk<br>
+<a href="http://www.grymoire.com/Unix/">grymoire.com</a> - Advanced stuff<br>
+
+<a href="http://www-128.ibm.com/developerworks/views/aix/libraryview.jsp?search_by=speaking+UNIX+Part">Speaking UNIX</a> - Tutorials from IBM<br>
+<a href="http://www.shell-fu.org/lister.php">Shell-fu</a> - Daily tips <br>
+<a href="http://linuxcommand.org/learning_the_shell.php"> LinuxCommand</a> - Shell Scripting tutorial<br>
+<a href="http://ubuntuforums.org/forumdisplay.php?f=100">UbuntuForums</a> - HowTo guides and forum <br>
+<a href="https://help.ubuntu.com/9.04/basic-commands/C/">Using the Ubuntu command line</a> - Simple introduction <br>
+<a href="http://ubuntuguide.org/wiki/Main_Page">UbuntuGuide</a> - In depth guide to Ubuntu <br>
+<a href="http://www.faqs.org/faqs/unix-faq/shell/">UNIX FAQ</a> </p>
+</blockquote>
+<p class="head"> Recommended Books</p>
+<blockquote>
+ <p><a href="http://www.amazon.com/dp/0596154488?tag=ss64"><img src="linuxnutshell.gif" width="72" height="110"> <b>Linux in a Nutshell</b> </a> 6th Edition, Sept 2009 <br>
+ A command reference for Linux, find the command syntax you need. Also <b><a href="http://www.amazon.com/dp/0596100299?tag=ss64">UNIX in a Nutshell</a></b>, Fourth edition (2008) <i>by Arnold Robbins</i><br>
+<i>the </i>standard desktop reference.</p>
+<p><a href="http://www.amazon.com/dp/0596003439?tag=ss64"><img src="nix_essential.jpg" width="120" height="160"> <b>Essential System Administration</b></a>, Third Edition Aug 2002 <i>by &AElig;leen Frisch</i><br>
+Describes Unix tools in the context of a system administrator's job. More than just covering syntax, tools and concepts, this book shows how to use administrative tools intelligently and efficiently.</p>
+<p><a href="http://www.amazon.com/dp/0131478230?tag=ss64"><strong><img src="sobell.jpg" width="87" height="110"> Linux Commands, Editors, and Shell Programming</strong></a> <br>
+ <em>by Mark G. Sobell</em><br>
+Effectively two books in one - a tutorial on concepts and techniques, plus a command reference. <br>
+Clear explanations and useful knowledge.<br>
+965 pages </p>
+<p><b><a href="http://www.amazon.com/dp/1934356220?tag=ss64"><img src="bash-kier-ubuntu.jpg" width="75" height="75"> Ubuntu Kung Fu: Tips, Tricks, Hints, and Hacks</a> </b>by Kier Thomas<br>
+Entertaining and readable with hundreds of concise tips. Enhance productivity, tweak Ubuntu performance, enhance security, and lots more.</p>
+<p><b><a href="http://www.amazon.com/dp/0596003307?tag=ss64"><img src="unixpowertools.jpg" width="68" height="90" border="1"> UNIX Power Tools</a></b> <i>by <a href="http://www.jpeek.com/">Jerry D Peak</a>, <a href="http://radar.oreilly.com/tim/">Tim O'Reilly</a> et al</i><br>
+Useful tricks and techniques, each chapter describes the different ways of performing a task. e.g. the page on 'Wildcards' has 10 ways to select a group of files - only two of which involve the grep command. [<a href="ftp://ftp.ora.com/published/oreilly/power_tools/unix/upt9707.tgz">Archive of shell scripts</a>] <br>
+1200 pages </p>
+<p><a href="http://www.amazon.com/dp/0672324903?tag=ss64"><b><img src="unixkochan.gif" width="89" height="110"> Unix Shell Programming</b></a>, Third Edition (Paperback)<br>
+<i>by Stephen Kochan, Patrick Wood </i><br>
+Detailed coverage of shell programming: regular expressions, the kernel and utilities.</p>
+</blockquote>
+<p><b>OS Downloads</b></p>
+<blockquote>
+<p><a href="http://directory.fsf.org/project/bash/">Bash V3.0</a> <a href="http://groups.google.com/groups?dq=&group=comp.unix.shell&c2coff=1&selm=ce69oa$sev$1@eeyore.INS.cwru.edu">released</a> July 2004<br>
+<a href="http://wubi-installer.org/">wubi</a> - Ubuntu installer for Windows <br>
+<a href="http://www.sun.com/software/solaris/get.jsp">Solaris 10</a> from Sun (free)<br>
+<a href="http://www.gentoo.org/">Gentoo.org</a> <br>
+<a href="https://www.redhat.com/apps/download/">RedHat Linux</a> <br>
+<a href="http://linux.dell.com/">Linux.Dell.com</a> (Red Hat) <br>
+<a href="http://www.novell.com/linux/">Novell linux</a> <br>
+<a href="http://www.livecdlist.com/">Live CDs</a> &amp; <a href="http://en.wikipedia.org/wiki/List_of_LiveCDs">Wikipedia Live CDs</a><br>
+<a href="http://www.ubuntu.com/">Ubuntu.com</a><br>
+<a href="https://wiki.ubuntu.com/Artwork/Incoming/DustTheme?action=show">Ubuntu Dust Theme</a> - a new, look for Ubuntu Lucid Lynx. </p>
+</blockquote>
+<p class="head">Apps &amp; Utilities</p>
+<blockquote>
+<p><a href="http://freshmeat.net/">Freshmeat.net</a> - Huge open source download
+site <br>
+<a href="http://www.gnu.org/prep/ftp.html">GNU FTP Sites</a> - GNU programs
+and Manuals<br>
+<br>
+<a href="http://www.pc-tools.net/unix/">pc-tools.net</a> - Utilities (Linux/BSD) <br>
+
+<a href="http://betterthangrep.com/">Ack - better than grep</a>- a grep-like tool, aimed at programmers.<br>
+<a href="http://audacity.sourceforge.net/">Audacity</a> - CD Ripper, Sound editor<br>
+<a href="https://wiki.ubuntu.com/AutoFsck">AutoFsck</a> - Configure boot disc checks (Ubuntu)<br>
+<a href="http://beagle-project.org/">Beagle</a> - Desktop Search
+<br>
+<a href="http://dar.linux.free.fr/">Dar</a> - Disk Archive/backup
+<br>
+<a href="http://www.novell.com/products/desktop/features/evolution.html">Evolution</a> - email with Exchange compatibility<br>
+<a href="http://www.winfield.demon.nl/">AntiWord</a> - Cross-platform MS Word reader.<br>
+<a href="http://www.acme.com/software/thttpd/">thttpd</a> - HTTP Web Server<br>
+<a href="http://www.imgseek.net/">ImgSeek</a> - Photo collection manager and viewer<br>
+<a href="http://easytag.sourceforge.net/">Easy Tag</a> - Tag editor for MP3, Ogg Vorbis files<br>
+<a href="http://www.methylblue.com/filelight/">Filelight</a> - Graphical view of the filesystem <br>
+<a href="http://www.stearns.org/fanout/README.html">Fanout</a> - Run a command on multiple machines<br>
+
+<a href="http://www.gnu.org/software/parted/parted.html">GNU Parted</a> | <a href="http://www.partimage.org/">Partimage</a> - partition managers<br>
+<a href="http://do.davebsd.com/">Gnome Do</a> -
+App launcher (inspired by Quicksilver) includes <a href="http://do.davebsd.com/wiki/Docky">Docky</a> <br>
+<a href="http://code.google.com/p/googlecl/wiki/ExampleScripts">Google command line</a> - Script Youtube, Cal, docs, picasa etc <br>
+<a href="http://www.nostatic.org/grip/">Grip</a> - CD Ripper (Gnome)<br>
+<a href="http://gftp.seul.org/">Gftp multithreaded ftp</a> <br>
+<a href="http://htop.sourceforge.net/">htop</a> - an interactive process viewer<br>
+<a href="http://www.k3b.org/">k3b.org</a> - The CD/DVD Kreator<br>
+<a href="http://userbase.kde.org/Kontact">KNode newsreader</a> - for K desktop<br>
+<a href="http://www.inkscape.org/">Inkscape</a> - Vector Graphics (Illustrator)<br>
+<a href="http://lame.sourceforge.net/links.php">Lame</a> - audio apps <br>
+<a href="http://www.adobe.com/shockwave/download/download.cgi?P1_Prod_Version=ShockwaveFlash">Macromedia Flash Player</a><br>
+<a href="http://pan.rebelbase.com/">Pan </a>- Newsreader <br>
+<a href="http://www.partimage.org/">Partition Image</a> - Ghost <br>
+Performance monitoring tools: <a href="http://freshmeat.net/projects/atop/">atop</a>, <a href="http://freshmeat.net/projects/bmon/">bmon</a>, <a href="http://dag.wieers.com/home-made/dstat/">dstat</a>, <a href="http://htop.sourceforge.net/">htop</a>, <a href="http://gael.roualland.free.fr/ifstat/">ifstat</a>, <a href="http://www.ex-parrot.com/pdw/iftop/">iftop</a>, <a href="http://htop.sourceforge.net/"></a><a href="http://pagesperso-orange.fr/sebastien.godard/">sysstat</a><br>
+<a href="http://www.kmyfirewall.org/">KMyFirewall</a> <a href="http://easyfwgen.morizot.net/">Easy Firewall</a> | <a href="http://www.fwbuilder.org/">Firewall Builder</a> | <a href="http://www.shorewall.net/">Shoreline Firewall</a> | <a href="http://www.simonzone.com/software/guarddog/">GuardDog</a> | <a href="http://www.fs-security.com/">Firestarter</a> <br>
+<a href="http://usat.sourceforge.net/">Linux Security Auditing Tool </a><br>
+<a href="http://ocsinventory.sourceforge.net/index.php?page=English">OCS Inventory</a> - Open Source System Management<br>
+<a href="http://www.rdesktop.org/">rDesktop</a> -
+RDP client for Windows (Terminal Services)<br>
+<a href="http://www.dtek.chalmers.se/%7Ed3august/xt/">xTraceroute</a> - graphical version of traceroute<br>
+<a href="http://e2undel.sourceforge.net/">e2Undel</a> - Undelete <br>
+<a href="http://www.videolan.org/vlc/">VLC Media Player</a> <br>
+<a href="http://www.mplayerhq.hu/">MPlayer</a> - DVD and media player <br>
+<a href="http://www.realvnc.com/products/download.html">VNC</a> <br>
+<a href="http://www.xfce.org">Xfce</a> - Lightweight window manager <br>
+<a href="http://www.xmms.org/">xmms</a> - Winamp clone</blockquote>
+<p class="head">Discussion &amp; Newsgroups</p>
+<blockquote><p>
+<a href="http://groups.google.com/group/comp.unix.shell/topics">comp.unix.shell</a> - Shell scripting<br>
+<a href="http://groups.google.com/groups/dir?sel=usenet%3Dcomp.os.linux%2C&"> comp.os.linux.*</a> - General linux<br>
+<a href="http://www.linuxquestions.org/questions/index.php">Linux Questions.org</a><br>
+SS64 <a href="http://ss64.org/"> Discussion Forum</a>
+</p>
+</blockquote>
+<p><i>&ldquo;Talk is cheap. Show me the code&rdquo; - <a href="http://lkml.org/lkml/2000/8/25/132">Linus Torvalds</a></i></p>
+<!-- #BeginLibraryItem "/Library/foot_menu.lbi" --><div align="center"><hr size="1">
+<p id="top"><a href="#"><img src="../images/top-4.gif" width="47" height="53" border="0" alt="Back to the Top" title="Back to the Top"></a></p>
+<p class="tagline">&copy; Copyright <a href="http://ss64.com/">SS64.com</a> 1999-2010<br>
+Some rights reserved<br>
+</p>
+</div><!-- #EndLibraryItem --></body>
+</html> \ No newline at end of file
diff --git a/help/en/term_tools/links/linuxnutshell.gif b/help/en/term_tools/links/linuxnutshell.gif
new file mode 100644
index 0000000..3620251
--- /dev/null
+++ b/help/en/term_tools/links/linuxnutshell.gif
Binary files differ
diff --git a/help/en/term_tools/links/nix_essential.jpg b/help/en/term_tools/links/nix_essential.jpg
new file mode 100644
index 0000000..4e28b15
--- /dev/null
+++ b/help/en/term_tools/links/nix_essential.jpg
Binary files differ
diff --git a/help/en/term_tools/links/sobell.jpg b/help/en/term_tools/links/sobell.jpg
new file mode 100644
index 0000000..eb66358
--- /dev/null
+++ b/help/en/term_tools/links/sobell.jpg
Binary files differ
diff --git a/help/en/term_tools/links/unixkochan.gif b/help/en/term_tools/links/unixkochan.gif
new file mode 100644
index 0000000..6d7c098
--- /dev/null
+++ b/help/en/term_tools/links/unixkochan.gif
Binary files differ
diff --git a/help/en/term_tools/links/unixpowertools.jpg b/help/en/term_tools/links/unixpowertools.jpg
new file mode 100644
index 0000000..30231d1
--- /dev/null
+++ b/help/en/term_tools/links/unixpowertools.jpg
Binary files differ
diff --git a/help/en/term_tools/main.css b/help/en/term_tools/main.css
new file mode 100644
index 0000000..939f0fd
--- /dev/null
+++ b/help/en/term_tools/main.css
@@ -0,0 +1,33 @@
+/* elements */
+body{font-weight:normal; color:#000; background-color:#CCC;}
+p, ol, ul, h1, h2, dt, dd, table{font-family:Helvetica,Arial,sans-serif; font-weight:normal; font-size:100%;}
+pre{font-family:"courier new","Andale Mono",courier,monospace; font-size:100%;}
+h1{clear:both; font-size:140%;}
+h2{font-weight:bold; color:#000;}
+tr, td{font-family:helvetica,Arial,Sans-Serif; font-weight:normal; font-size:100%;}
+/* classes */
+.head{font-family:Helvetica,Arial,sans-serif; font-size:large;}
+.body{font-family:Helvetica,Arial,sans-serif; font-size:100%;}
+.blu{color:#09F; text-decoration:none;}
+.tagline{font-family:Helvetica,Arial,sans-serif; font-size:75%; text-align:right;}
+.telety, .code{font-family:"courier new",courier,"Andale Mono",monospace; font-size:100%;}
+.menu{font-family:Helvetica,Arial,sans-serif; font-size:100%;}
+a.rl {background: url("images/roll-left.png") 0 0 no-repeat; text-decoration: none;}
+a.rr {background: url("images/roll-right.png") 0 0 no-repeat; text-decoration: none;}
+a:link{color:#00F; text-decoration:none;}
+a:visited{text-decoration:none;}
+a:visited:hover{color:#00F; text-decoration:underline;}
+a:hover{color:#00F; text-decoration:underline;}
+a:active{color:#00F;}
+/* IDs */
+#nav-menu{width:60em; height:50px;}
+#nav-menu ul{list-style:none; padding:0; margin:0;}
+#nav-menu li{float:left; margin:0 0.15em;}
+#nav-menu li a{height:47px; line-height:47px; width:115px; display:block; text-decoration:none; text-align:center;outline:none;}
+#nav-menu input{margin-top:0.6em; margin-left:0.7em;height: 20px;}
+#nav-menu .submit{margin-right:0.7em;height: 30px; width: 89px;}
+#nav-menu a:hover {background-position: 0 -47px;}
+#nav-menu a:active { background-position: 0 -94px;}
+#nav-menu img {border-width: 0px;}
+#top{float:left; margin:0 0 1em 1.5em;}
+#top a{outline:none;} \ No newline at end of file
diff --git a/help/en/term_tools/robots.txt b/help/en/term_tools/robots.txt
new file mode 100644
index 0000000..9999f47
--- /dev/null
+++ b/help/en/term_tools/robots.txt
@@ -0,0 +1,15 @@
+# ss64.com robots
+User-agent: *
+Disallow:
+
+User-agent: Charlotte
+Disallow: /
+
+User-agent: R6_FeedFetcher(www.radian6.com/crawler)
+Disallow: /
+
+User-agent: R6_FeedFetcher
+Disallow: /
+
+User-agent: 008
+Disallow: /
diff --git a/help/en/term_tools/rss.xml b/help/en/term_tools/rss.xml
new file mode 100644
index 0000000..eb369c4
--- /dev/null
+++ b/help/en/term_tools/rss.xml
@@ -0,0 +1,50 @@
+<?xml version="1.0"?>
+<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
+<channel>
+<title>SS64 RSS Feed</title>
+<link>http://ss64.com</link>
+<description>Command Line Reference</description>
+<language>en-gb</language>
+<pubDate>Fri, 08 Aug 2008 17:00:00 GMT</pubDate>
+<lastBuildDate>Fri, 12 Jun 2009 14:27:34 GMT</lastBuildDate>
+<atom:link href="http://ss64.com/rss.xml" rel="self" type="application/rss+xml" />
+<docs>http://ss64.com/rssinfo.html</docs>
+ <item>
+ <title>Oracle commands</title>
+ <link>http://ss64.com/ora/</link>
+ <description>Including PL/SQL and Data dictionary views</description>
+ <pubDate>Fri, 13 Jan 2006 00:00:01 GMT</pubDate>
+ </item>
+ <item>
+ <title>SQL Server commands</title>
+ <link>http://ss64.com/sql/</link>
+ <description>SQL Server command reference</description>
+ <pubDate>Sun, 16 Jul 2006 00:00:01 GMT</pubDate>
+ </item>
+
+ <item>
+ <title>Windows XP commands</title>
+ <link>http://ss64.com/nt/</link>
+ <description>Including Resource Kits</description>
+ <pubDate>Thu, 12 Jan 2006 10:31:51 GMT</pubDate>
+ </item>
+ <item>
+ <title>PowerShell commands</title>
+ <link>http://ss64.com/ps/</link>
+ <description>Including functions and sample scripts</description>
+ <pubDate>Fri, 08 Aug 2008 17:00:00 GMT</pubDate>
+ </item>
+ <item>
+ <title>Linux BASH commands</title>
+ <link>http://ss64.com/bash/</link>
+ <description>Built-in and Shell tools</description>
+ <pubDate>Thu, 12 Jan 2006 00:00:52 GMT</pubDate>
+ </item>
+ <item>
+ <title>Apple OS X commands</title>
+ <link>http://ss64.com/osx/</link>
+ <description>Built-in and Shell tools</description>
+ <pubDate>Fri, 12 Jun 2009 14:27:34 GMT</pubDate>
+ </item>
+ </channel>
+ </rss> \ No newline at end of file