LQWiki - User contributions [en]

FIFO

2011-05-23T23:59:20Z

Hda7: Linked "named pipe" to new named pipe page

'''FIFO''' ('''F'''irst '''I'''n '''F'''irst '''O'''ut) generally refers to a special [[file]] known as a "[[named pipe]]".

==See also==
*[[mkfifo]]

Talk:Named pipe

2011-05-17T14:09:29Z

Hda7:

Can you give an example how this could be useful? --[[User:ThorstenStaerk|ThorstenStaerk]] 12:59, May 15, 2011 (UTC)
:Now in the process of doing so. Plan to finish later. [[User:Hda7|Hda7]] 13:14, May 15, 2011 (UTC)

Should the comparison section come after the usage section?
: Most important for the typical reader is how to use it, right? If he wants to know what it is, he or she will look it up on wikipedia. Why do you want a comparison section? --[[User:ThorstenStaerk|ThorstenStaerk]] 12:15, May 17, 2011 (UTC)
By the way, this is my first page. Any help with style, convention, etc. would be appreciated.

[[User:Hda7|Hda7]] 17:38, May 15, 2011 (UTC)
: The first sentences should make clear if it is worth reading on. What is it and what problems can you solve. This is still not clear to me. You should not compare it e.g. with anonymous pipes because if you are a newbie you do not know what anonymous pipes are and if you are an expert you do not need to read this article. If you write the article like this you are my hero :) --[[User:ThorstenStaerk|ThorstenStaerk]] 12:15, May 17, 2011 (UTC)
:: Any better now? [[User:Hda7|Hda7]] 14:09, May 17, 2011 (UTC)

Talk:Named pipe

2011-05-17T14:07:42Z

Hda7:

Can you give an example how this could be useful? --[[User:ThorstenStaerk|ThorstenStaerk]] 12:59, May 15, 2011 (UTC)
:Now in the process of doing so. Plan to finish later.
[[User:Hda7|Hda7]] 13:14, May 15, 2011 (UTC)

Should the comparison section come after the usage section?
: Most important for the typical reader is how to use it, right? If he wants to know what it is, he or she will look it up on wikipedia. Why do you want a comparison section? --[[User:ThorstenStaerk|ThorstenStaerk]] 12:15, May 17, 2011 (UTC)
By the way, this is my first page. Any help with style, convention, etc. would be appreciated.

[[User:Hda7|Hda7]] 17:38, May 15, 2011 (UTC)
: The first sentences should make clear if it is worth reading on. What is it and what problems can you solve. This is still not clear to me. You should not compare it e.g. with anonymous pipes because if you are a newbie you do not know what anonymous pipes are and if you are an expert you do not need to read this article. If you write the article like this you are my hero :) --[[User:ThorstenStaerk|ThorstenStaerk]] 12:15, May 17, 2011 (UTC)

Named pipe

2011-05-17T14:07:00Z

Hda7:

A '''named pipe''' is special type of file used to provide one-way communications between two processes.

==Typical use==
A named pipe is generally created with [[mkfifo]] or [[mknod]]. One process opens the file read-only, while another opens it write-only. By default, the first open will block until the second process opens the pipe. The process that opened the pipe write-only can then write data into the pipe with standard file functions such as [[fwrite]]. The other process will receive this data when it reads from the pipe.

Named pipe

2011-05-17T14:06:26Z

Hda7: Removed comparison section and tweaked first sentence

A '''named pipe''' is special type of file which is used to provide one-way communications between two processes.

==Typical use==
A named pipe is generally created with [[mkfifo]] or [[mknod]]. One process opens the file read-only, while another opens it write-only. By default, the first open will block until the second process opens the pipe. The process that opened the pipe write-only can then write data into the pipe with standard file functions such as [[fwrite]]. The other process will receive this data when it reads from the pipe.

Talk:Named pipe

2011-05-15T17:38:45Z

Hda7:

Can you give an example how this could be useful? --[[User:ThorstenStaerk|ThorstenStaerk]] 12:59, May 15, 2011 (UTC)

Now in the process of doing so. Plan to finish later.
[[User:Hda7|Hda7]] 13:14, May 15, 2011 (UTC)

Should the comparison section come after the usage section?

By the way, this is my first page. Any help with style, convention, etc. would be appreciated.

[[User:Hda7|Hda7]] 17:38, May 15, 2011 (UTC)

Named pipe

2011-05-15T17:37:27Z

Hda7:

A '''named pipe''' is a type of file used for one-way [[inter-process communication]]. It is similar to [[anonymous pipes]] such as those used in [[shell pipelines]].
==Comparison with other [[inter-process communication|IPC]] methods==
This relatively simple method of inter-process data transfer is more flexible than an anonymous pipe for two main reasons:
# the processes do not need to be descended from one another, and
# the second process may open the pipe any length of time after the first.
However, there is no guarantee that only the intended processes will open the pipe, whereas an anonymous pipe can only be accessed by the process that created it and its child processes.

Pipes have the restriction of only offering one-way communication. If bi-directional communication is needed, two pipes could be used (one in each direction) or a [[socket]] could be used instead.

Compared to [[shared memory]], pipes are generally easier to use (they use standard file read/write commands) and safer (if both processes write to the same location at the same time using shared memory, one process's data will be overwritten).

==Typical use==
A named pipe is generally created with [[mkfifo]] or [[mknod]]. One process opens the file read-only, while another opens it write-only. By default, the first open will block until the second process opens the pipe. The process that opened the pipe write-only can then write data into the pipe with standard file functions such as [[fwrite]]. The other process will receive this data when it reads from the pipe.

Talk:Named pipe

2011-05-15T13:14:23Z

Hda7:

Named pipe

2011-05-15T13:13:18Z

Hda7:

A '''named pipe''' is a type of file used for one-way [[inter-process communication]]. It is similar to [[anonymous pipes]] such as those used in [[shell pipelines]].
==Comparison with other [[inter-process communication|IPC]] methods==
This relatively simple method of inter-process data transfer is more flexible than an anonymous pipe for two main reasons:
# the processes do not need to be descended from one another, and
# the second process may open the pipe any length of time after the first.
However, there is no guarantee that only the intended processes will open the pipe, whereas an anonymous pipe can only be accessed by the process that created it and its child processes.
==Typical use==
A named pipe is generally created with [[mkfifo]] or [[mknod]]. One process opens the file read-only, while another opens it write-only. By default, the first open will block until the second process opens the pipe. The process that opened the pipe write-only can then write data into the pipe with standard file functions such as [[fwrite]]. The other process will receive this data when it reads from the pipe.

Named pipe

2011-05-14T20:27:12Z

Hda7:

A '''named pipe''' is a type of file used for one-way [[inter-process communication]]. It is similar to [[anonymous pipes]] such as those used in [[shell pipelines]].
==Typical use==
A named pipe is generally created with [[mkfifo]] or [[mknod]]. One process opens the file read-only, while another opens it write-only. By default, the first open will block until the second process opens the pipe. The process that opened the pipe write-only can then write data into the pipe with standard file functions such as [[fwrite]]. The other process will receive this data when it reads from the pipe.

Named pipe

2011-05-14T16:26:13Z

Hda7: Created page with 'A '''named pipe''' is a type of file used for one-way inter-process communication. It is similar to anonymous pipes such as those used in shell pipelines. ==Typical …'

A '''named pipe''' is a type of file used for one-way [[inter-process communication]]. It is similar to [[anonymous pipes]] such as those used in [[shell pipelines]].
==Typical use==
A named pipe is generally created with [[mkfifo]] or [[mknod]]. One process opens the file read-only, while another opens it write-only. By default, the first open will block until the second process opens the pipe. The process that opened the pipe write-only can then write data into the pipe with standard file functions such as [[write]]. The other process will receive this data when it reads from the pipe.

Text editor

2010-06-30T19:09:14Z

Hda7: Condensed both emacs records into one. Changed emacs unicode status to yes.

A '''text editor''' is an [[application]] that is used to write and edit plain text.
You can categorize editors by being able to provide a comfortable [http://en.wikipedia.org/wiki/GUI gui] and by their ability to process [[unicode]].

== Specific applications ==

{| class="wikitable sortable" border=1
! [[Application]] !! [[CLI]] or GUI !! [[Unicode]] support
|-
| [[ed]] || cli || ?
|-
| [[ex]] || cli || ?
|-
| [[emacs]] || both || yes
|-
| [[joe]] || cli || ?
|-
| [[yudit]] || gui || yes
|-
| [[Minimum Profit]] || cli || ?
|-
| [[nano]] || cli || ?
|-
| [[pico]] || cli || ?
|-
| [[vi]] and its derivatives || cli || ?
|-
| [[bluefish]] || gui || ?
|-
| [[jEdit]] || gui || ?
|-
| [[kate]] || gui || ?
|-
| [[kwrite]] || gui || ?
|-
| [[Gedit]] || gui || ?
|-
| [[gvim]] || gui || ?
|-
| [[NEdit]] || gui || ?
|}

== See also ==
* [[Text Processing]]
* [[Word Processor]]
* [[WYSIWYG]]
* [[EditOr]]

[[category:Editors]]

Emacs

2010-04-17T16:56:19Z

Hda7:

'''Emacs'''; ('''E'''diting '''MAC'''ro'''S''') The non plus ultra of hacker editors, a programmable [[text editor]] with an entire [http://en.wikipedia.org/wiki/Lisp_(programming_language) LISP] system inside it. It was originally written by [http://en.wikipedia.org/wiki/Richard_stallman Richard Stallman] in [[TECO]] under [http://en.wikipedia.org/wiki/Incompatible_Timesharing_System ITS] at the [http://en.wikipedia.org/wiki/MIT_AI_lab MIT AI lab]; AI Memo 554 described it as "an advanced, self-documenting, customizable, extensible real-time display editor". It has since been reimplemented any number of times, by various hackers, and versions exist that run under most major [[operating system]]s. Perhaps the most widely used version, also written by Stallman and now called "[[GNU]] EMACS" or GNUMACS, runs principally under Unix. (Its close relative [http://en.wikipedia.org/wiki/Xemacs XEmacs] is the second most popular version.) It includes facilities to run compilation subprocesses and send and receive [[email]] or news; many hackers, before the time of [http://en.wikipedia.org/wiki/GUI GUIs], spent up to 80% of their tube time inside it. Other variants include GOSMACS, CCA EMACS, UniPress EMACS, Montgomery EMACS, jove, epsilon, and MicroEMACS. Some EMACS versions running under window managers iconify as an overflowing kitchen sink, perhaps to suggest the one feature the editor does not (yet) include.

The latest stable release of GNU EMACS, 21.3, was released on March 24, 2003.

=== Vi vs. Emacs ===
Emacs vs [[vi]] is the subject of a holy war, but this has largely been settled by the rise of [[WYSIWYG]] editors, which have tended to displace both options, and faster hardware, which renders the baroque nature of emacs irrelevant. The Emacs camp is sometimes jokingly referred to as the "Church of Emacs".

=== Buckies ===
The [http://en.wikipedia.org/wiki/Space_cadet_keyboard space-cadet keyboard] was an inspiration for emacs. This is where all the C-''x'' (That's emacs notation for pressing the Control key while hitting the ''x'' key) and M-''x'' (same thing, only with the Alt key instead of the Control key) commands came from. These chorded keystrokes make use of "buckies", or special function keys like Control, Alt, and Shift. The name bucky comes from the early days of keyboards, before they standardized on [http://en.wikipedia.org/wiki/ASCII ASCII]. In those days, characters used 7 [http://en.wikipedia.org/wiki/Bit bits], and bucky keys turned on extra bits, which were called bucky bits, meta bits, or high bits, to the top of the character's [http://en.wikipedia.org/wiki/Byte byte]. This changed the value of the character's byte, and produced a different character.

The use of buckies means that an experienced emacs user has a wide range of commands available in just a few keystrokes, and doesn't have to take their hands off the main keyboard to use the arrow keys or the mouse. On the downside, there are a lot of commands to memorize (although you can usually muddle along with the arrow keys or the menu). Also, some key chords are hard to pull off. But at least emacs is better than the space-cadet keyboard. There are occasionally double bucky|double buckies (where you press Ctrl, Alt, and another key) but triple or even quadruple buckies are very rare. (A triple bucky would require the use of the Shift key. Quadruple or quintuple bucky would need super and hyper modifier keys, which can be defined using [[xmodmap]].)

=== Features ===
Emacs supports syntax highlighting, [[CVS]], [[diff]]/[[patch]] and many other features, which draw on Emacs' built-in LISP extensibility.

Around version 19 a fork of the GNU Emacs project resulted in an alternate version [http://en.wikipedia.org/wiki/Xemacs XEmacs]. Both versions are now actively developed. The reasons for the fork are detailed on http://www.xemacs.org, but in short you could say that GNU Emacs is [[Free Software]] while XEmacs is more [[Open Source]] Software. XEmacs readily adopts changes from Emacs into its code base, so XEmacs arguably has more features. In practice the editors a much alike, so most you read about Emacs should apply to XEmacs and vice versa.

ELSE, the Emacs Language Sensitive Editor is an installable mode of the editor.

A primary attraction of Emacs is its excellent syntax highlighting (called font-locking) and indentation support, as well as a lot of advanced editing tricks. Functions such as indent-function, hungry delete and other advanced tricks makes Emacs users incredibly productive. The flip side of the coin is that this enormous functionality has to be mastered, which takes some time.

Emacs comes with an excellent tutorial and auto-generated documentation. To access the tutorial, press h while holding down the Control key, release the control key and press t.

== See also ==
* [[Emacs keystrokes]]
* [[Emacs modes]]
* [[Keyboard shortcuts at a glance]]
* [[LQWiki:Emacs_tips_and_tricks| Emacs tips and tricks to play well with LQWiki]]

== External links ==
* [http://www.gnu.org/software/emacs/ Homepage] (''www.gnu.org'')
* [http://www.emacswiki.org/ Wiki] (''www.emacswiki.org'')
* [http://www.nabble.com/Emacs-f1569.html Mailing lists] (''www.nabble.com'')
* [http://www.xemacs.org/ XEmacs homepage] (''www.xemacs.org'')

{{Jargon File/Attribution}}

[[category:Editors]]

Vim

2010-04-17T16:48:02Z

Hda7:

'''vim''' ('''vi''' i'''m'''proved) is a contemporary version of the classic [[vi]] editor, with additional capabilites.

== Introduction ==
All [[UNIX]] machines typically come with the [[vi]] [[text editor]]. However, vi lacks some more contemporary features (for example, syntax highlighting). This is where '''vim''' comes in. If you know how to use vi, you'll find vim to be the same except it has a number of useful features added to make editing easier. If you don't yet know how to use vi or vim, and you didn't come from using [[ed]], you'll find the learning curve quite steep (which means, it might take you a while to learn to achieve maximum proficiency).

Vim was originally written by (and is still primarily maintained by) Bram Moolenaar. It started as a personal desire to have a useful vi-clone for the Amiga, but eventually grew as more features were added. It now runs on a variety of platforms (including Unix work-a-likes, e.g. GNU/Linux, Mac OS X, and *BSD; Amiga; Windows; Mac "Classic"; and OS/2) and supports a variety of graphical toolkits (including GTK, QT, and Carbon) in addition to the command-line interface. VIM is also the latin word for "power" or "force".

Vim has a compatibility mode which produces an almost vi-compatible experience (the version of vi used seems to be one released with Sun OS 4.x, from Version 3.7 dated on 6/7/85). This is enabled by using the ":set compatible" ex-command or by running Vim with the -C option.

== Tips ==

=== learning ===
To learn [[vim]], [[open a console]] and call
[http://linuxcommand.org/man_pages/vimtutor1.html vimtutor]

=== ~/.vimrc ===
To make a config file for vim, create a file in your home directory called .vimrc, and fill it with stuff that you'd normally type into vim's "ex" mode. For example, if you regularly do ":syntax on" from inside vim, put "syntax on" (no colon or quotes) on a line by itself in your ~/.vimrc file.

Here's the contents of a useful .vimrc file:
<pre>
syntax on
set number
set expandtab
set tabstop=4
set shiftwidth=4
set autoindent
</pre>

Where:
* "syntax on" turns on syntax highlighting
* "set number" turns on line numbers
* "set expandtab" makes vim insert spaces (instead of tabs) whenever you hit the tab key
* "set tabstop=4" sets tabs to equal 4 spaces
* "set shiftwidth=4" makes it so when you use the text shifting command, it shifts over using 4-space indents.
* "set autoindent" has vim use "smart indenting", ie. when you are tabbed out to, say, the 8th column, and you type something then hit enter, the cursor is helpfully placed at the 8th column again for you.

(You can shut off line numbering from command mode by typing <tt>:set nonumber</tt>.)

=== syntax highlighting ===

You can turn syntax highlighting on/off with:
:syntax off
:syntax on

If you have syntax highlighting on, but are using a dark background and the colors don't show up well, you can use this command:
:set background=dark

==External links==
*[http://www.vim.org Vim Homepage] (''www.vim.org'')
*[http://vi-improved.org/wiki/index.php #vim wiki] (''vi-improved.org'')

[[Category:Editors]]

CVS

2010-04-16T13:04:32Z

Hda7:

'''Concurrent Versioning System (CVS)''', is a [[client-server]] version control (aka [[revision control]]) system. It enables teams to write together on books, documentation - or software projects. CVS's client tools are available on most platforms.

It works like this: There is a central storage for the files, called the ''Repository''. Every participant can ''check out'' the project's files to their local ''[[Sandbox]]'' and change them. Typically, less participants can ''commit'' (submit) their changes afterwords so next checkouts will deliver the files with their changes.
The technical excellence of CVS is, first, that for every file in the repository, there is every version available. This is not because every version is stored, but because every ''change'' is stored. See [[revision control]]. Second, it is totally transparent whether your repository lives on a remote [[server]] or on your local [[desktop]].

CVS is in many aspects outperformed by [[subversion]], but CVS is still easier to set up.

==Usage==

===Building up a server===

To build up a CVS Server, best use [[webmin]] that has an own module for that.

===Creating a repository===

To create and initialize a repository /cvstest, do a
cvs -d /cvstest init

===Accessing a repository===

Before you can do anything, you must tell CVS the location of the repository you'll be accessing. This is done with the -d global option. For example, assuming the repository is on the local machine in /usr/local/cvs (a fairly standard location):
$ cvs -d /usr/local/cvs ''cvs-command''

You can also use the variable CVSROOT to avoid the -d option. E.g. You can check out the files from the very same repository by:
$ export CVSROOT=/usr/local
$ cvs co cvs
In many cases, however, the repository is on another machine and must therefore be reached over the network. CVS provides a choice of network access methods; which one you'll use depends mostly on the security needs of the repository machine.

To specify a remote repository as opposed to a local one, you just use a longer repository path. You first name the access method, delimited on each side by colons, followed by the username and the server name (joined with an @ sign), another separator colon, and finally the path to the repository directory on the server.

An example of the pserver access method, which stands for "password-authenticated server":

$ cvs -d :pserver:jrandom@cvs.foobar.com:/usr/local/cvs login
(Logging in to jrandom@cvs.foobar.com)
CVS password: (enter your CVS password here)
$

The command to check out a project is exactly what you think it is:

$ cvs checkout myproj
cvs checkout: Updating myproj
U myproj/README.txt
U myproj/hello.c
cvs checkout: Updating myproj/a-subdir
U myproj/a-subdir/whatever.c
cvs checkout: Updating myproj/a-subdir/subsubdir
U myproj/a-subdir/subsubdir/fish.c
cvs checkout: Updating myproj/b-subdir
U myproj/b-subdir/random.c

$ ls
myproj/ was_myproj/
$ cd myproj
$ ls
CVS/ README.txt a-subdir/ b-subdir/ hello.c
$

source: http://cvsbook.red-bean.com/cvsbook.html

== See also ==
* [[Subversion]]
* [[gIt]]
* [[GNU Arch]]

== External links ==
* [http://linuxjournal.com/article.php?sid=5976 how to make your home directory a CVS sandbox.] (''linuxjournal.com'')
* [http://www.cvshome.org/ CVS homepage] (''www.cvshome.org'')

[[Category:Command]]

Command

2010-04-16T12:58:55Z

Hda7:

A '''command''', in the most general sense, is an executable file or a [[shell]] [[builtin]]. For example, <tt>[[cd]]</tt>, <tt>[[ls]]</tt>, <tt>[[echo]]</tt> and <tt>[[firefox]]</tt> are commands.

'''''Note:''' details of commands vary from version to version and available commands vary from [[distribution]] to distribution.''

= General notes on commands =
Commands may be invoked as ''simple'' commands.
''In these examples, the '''$''' that starts each line is a [[shell prompt]] and not meant to be typed''
$ ls
Or they may be invoked as ''complex'' commands.
$ ls -l /bin
Here "-l /bin" are a pair of '''arguments''' (separated from each other and the command by whitespace) and "-l" is specifically an '''option''', since it modifies the behavior of ls (it produces a '''l'''ong listing), while "/bin" simply specifies a target for <tt>ls</tt> to act on.

They may also be invoked in multiples where the semi-colon is a '''command separator'''.
$ cd /bin; ls
That's two commands on one line. You may also execute one long command on two lines by escaping the carriage return with a backslash. (See [[shell script|scripting]] for further details on [[metacharacter]]s and escaping and quoting.)
$ cd really long command line \
that we would like to finish here
Another way to invoke multiple commands is conditionally, where (in [[bash]]) "&&" means to execute the second command only if the first returns with an exit code of 0 (i.e., it succeeds).
$ cd /bin && ls
With the semicolon command separator, had the change of directory failed, <tt>ls</tt> would still have been invoked and simply listed the contents of the current directory. With the conditional operator, <tt>ls</tt> would not be invoked if <tt>cd</tt> had failed.

Similarly, "||" means to execute the second command only if the first returns a non-zero exit code (i.e., it fails).
$ cd /bing [[Redirect |2>]]/dev/null || echo 'I kinna do it, Cap'\<nowiki>''</nowiki>n!'
This will <tt>cd</tt> to the directory named "bing" if it in fact exists and the command will exit. Since it probably doesn't, being a typo, the second command will execute and print a somewhat more entertaining error message than is usual.

= Learning about commands with local documentation =

A Linux system should have [[documentation]] in the form of [[man pages]] and possibly [[GNU]] [[info]] pages (see also [[texinfo]]). In a manner similar to this page's alphabetical list, if you know the command you wish to learn more about,
$ man ''command''
will show you the manual page of ''command''.

If you do not know the command but would like to see commands relevant to a topic, use
$ [[apropos]] ''subject''
or
$ man -k ''subject''
to find suitable commands.

Unfortunately, while most man pages will be informative and complete, many GNU utilities distribute very sketchy man pages whose primary purpose is to redirect the user to the info system. In that case,

$ info ''command''

will invoke that system of documentation.

Many commands have an "-h", "-H", "-help", "--help" option or some combination thereof. Unfortunately, some commands understand other things by "-h" or "-H" so unexpected and possibly unpleasant results may occur.

There are also extensive miscellaneous files usually found in /usr/doc, /usr/local/doc, /usr/src/linux/Documentation (kernel docs), and elsewhere.

= Lists of commands =

In our [[:Category:Command|Category Command]] you will find all commands in this wiki, but without explanation. The next chapter lists the most relevant ones with a short explanation so you can decide if the respective command is right for you. If you add to this list, your contribution should be didactic, understandable for newcomers, focused on the "real world" and contain sensible examples.

== By name ==
This is a list of [[command]]s that gives you just enough information to decide what command you want to use.

=== A ===
* [[alias]] - allows you to create shorter or more familiar names for commonly used commands
* [[apropos]] - search the manual page names and descriptions
* [[at]] - execute a command-line task at a specified future time
* [[awk]] - print only the n<sup>th</sup> word of an input line and more

=== B ===
* [[badblocks]] - a [[command]] disk utility
* [[bash]] - a [[shell]]
* [[beep]] - customized audible alerts
* [[bunzip2]] - [[unpack]] [[file]]s [[pack]]ed with [[bzip2]]
* [[bzip2]] - a [[pack]] utility

=== C ===
* [[cat]] - receive strings from [[stdin]] or a [[file]] and output them to [[stdout]] or a [[file]]
* [[chgrp]] - change the group ownership of a file
* [[chmod]] - change the permission mode of a [[file]]
* [[chown]] - change the owner of a [[file]]
* [[chroot]] - change the position of a root directory in filesystem
* [[chsh]] - change the shell of a [[user]]
* [[cp]] - copy a [[file]]
* [[cpio]] - [[pack]] or unpack [[files]] in cpio archives or [[tarballs]]
* [[cron]] - [[schedule tasks]] to be executed regularly at a specific [[time]]
* [[crontab]] - control the cron service
* [[cut]] - display specific coloumns of a file delimited by a character
* [[cvs]] - a version management system

=== D ===
* [[date]] - output or set date and time
* [[dd]] - dump a disk to/from a [[file]] and more
* [[df]] - show how much free disk space there is
* [[diff]] - show the difference between two files and more
* [[dig]] - show answer of DNS lookup of queried name server
* [[disown]] - disowns a job (removes the pid of the job). Even when the shell exits, the job won't stop running
* [[du]] - show how much disc space is used up

=== E ===
* [[echo]] - echo a string/value to [[stdout]]
* [[env]] - show all [[environment variable]]s
* [[exit]] - exit most [[shell]]s
* [[export]] - set an [[environment variable]] in the [[bash]] or [[zsh]]

=== F ===
* [[fdisk]] - [[partition]] a disc
* [[fg]] - fetch a [[process]] from the [[background]] to the foreground
* [[file (command)]] - determine a [[file]]'s type
* [[find]] - find a file depending on its name, size, change date or other attributes
* [[ftp]] - get files from the internet

=== G ===
* [[g++]] - compile [[C++]] code
* [[gcc]] - compile [[C]] code
* [[grep]] - grab for patterns in a [[file]] and more
* [[groups]] - show what groups your user is in
* [[gzip|gunzip]] - [[unpack]] [[file]]s from a special format
* [[gzip]] - [[pack]] [[files]] in a special format

=== H ===
* [[halt]] - shut down your computer
* [[head]] - show only the first n lines of a [[file]] and more
* [[hexdump]] - show a [[file]]'s content in hexadecimal numbers and more
* [[history (command)]] - show a [[command]] history in the [[bash]] [[shell]]
* [[hostname]] - show your computer's name
* [[hwinfo]] - show your available [[hardware]]

=== I ===
* [[id]] - show your user and groups ids
* [[ifconfig]] - show your ip address and more
* [[info]] - show info about a given command
* [[init]] - reboot or change runlevel
* [[iptables]] - show your [[firewall]] configuration
* [[iptraf]] - Interactive IP LAN monitor

=== J ===
* [[jobs]] - gives a list of current [[background]] jobs ([[process]]es)

=== K ===
* [[kill]] - kill a [[process]]
* [[killall]] - kill all processes with a given name

=== L ===
* [[ldd]] - show dynamic libraries needed by an executable
* [[less]] - show output in a viewer where you can scroll and search
* [[ln]] - link a file
* [[ls]] - list a file
* [[lsmod]] - list loaded kernel modules
* [[lsof]] - list open files and listening sockets
* [[lspci]] - list all pci devices
* [[lsusb]] - list usb devices

=== M ===
* [[make]] - [[compile]] [[software]] and more
* [[man]] - get help on questions that you never wanted to ask
* [[md5sum]] - compute the md5 sum of a [[file]] and more
* [[mkdir]] - make a [[directory]]
* [[mkfs]] - format a [[device]]
* [[minicom]] - communicate over your RS232 interface
* [[more]] - show input in a searchable pager
* [[mount]] - prepare a [[device]] for [[read]]ing and writing
* [[mv]] - move a file (can also be renaming)

=== N ===
* [[netcat]] - Send some bytes to the [[network]]
* [[netstat]] - get information on listening [[socket]]s, open [[port]]s and [[more]]
* [[nice]] - set a [[process]]' priority
* [[nm]] - list the names of functions in an object file
* [[nmap]] - [[network]] and [[port]] scanner tool

=== O ===
* [[objdump]] - show information about object [[file]]s
* [[openssl]] - create cryptographic [[server]] certificates and more

=== P ===
* [[passwd]] - change your and other's password
* [[ping]] - show if a given computer is up and running
* [[ps]] - show running [[process]]es
* [[pwd]] - show your current working [[directory]]

=== Q ===
* [[quota]] - manage how much resources the user is allowed to consume

=== R ===
* [[rar]] - rar files/directories
* [[read]] - read a string from your [[keyboard]] and more
* [[reboot]] - reboot the computer
* [[rename]] - rename a [[file]]
* [[rm]] - delete a [[file]]
* [[route]] - manage your network routing table
* [[rpm]] - a [[package management]] [[backend]] for [[Redhat]] and [[Fedora]]
* [[rsync]] - synchronize your folders over the [[network]]

=== S ===
* [[scp]] - ([[secure]] copy) over a [[network]]
* [[screen]] - a terminal multiplexer
* [[sed]] - manipulate a stream of characters (scripting language)
* [[setenv]] - change the value of an [[environment variable]] in the [[csh]]
* [[shuf]] - generate random permutations
* [[shutdown]] - shutdowns/reboots the system
* [[sleep]] - wait/delay some time
* [[ssh]] - login into / execute [[commands]] in a remote [[host]]
* [[su]] - change user
* [[sudo]] - execute the command as another user (usually root- /etc/sudoers)

=== T ===
* [[tail]] - show only the last ''n'' lines of a [[file]] and more
* [[tar]] - [[pack]] [[file]]s in a special format
* [[tcpdump]] - dump the tcp network traffic
* [[tee]] - multiplex [[cli]] output
* [[time]] - show the time needed by a command to finish
* [[top]] - show the top CPU consuming processes and more
* [[touch]] - create a file or update its time stamp
* [[traceroute]] - show the route a [[package]] takes over the [[network]]
* [[tac]] - print the [[file]] in reverse. (opposite of cat) (cat X tac)

=== U ===
* [[ulimit]] - show the limits of your user
* [[umount]] - unmount a [[device]] (Often requires sudo permissions)
* [[uname]] - show the running kernel's version and more
* [[uniq]] - remove repeated lines in a sorted file
* [[unzip]] - [[unpack]] files
* [[uptime]] - show the time since your computer was last switched on
* [[useradd]] - add a user
* [[userdel]] - delete a user
* [[usermod]] - modify a user

=== V ===
* [[Vgcreate]] - create [[lvm]] volume groups
* [[Vgdisplay]] - display [[lvm]] volume groups
* [[Vgs]] - show information about [[lvm]] volume groups
* [[Vgscan]] - scan for [[lvm]] volume groups
* [[vim]] - its not a text editor like Notepad, it is an [[IDE]]
* [[Vmstat]] - show input/output values, [[swap]], [[memory]] consumption and more

=== W ===
* [[w]] - print who is logged in to your system
* [[wc]] - [[word count]] (word,line,char)
* [[which]] - print the path where you find an executable [[file]]
* [[whoami]] - print your effective user name

=== X ===
* [[xargs]] - hand over [[stdin]] as a parameter
* [[xev]] - show information about your keystrokes and more
* [[xkill]] - kill a window that is in your way
* [[xosview]] - show [[CPU]]/[[memory]]/[[hard Drive]] activity and [[more]]

=== Y ===
* [[yacc]] - A [[C]] parser generator
* [[yes]] - repeatedly output a string
* [[yum]] - a [[package management]] [[frontend]] for [[Redhat]] & [[Fedora]]
* [[yast]] - a [[package management]] [[frontend]] for [[SUSE]]

=== Z ===
* [[zip]] - [[pack]] a [[file]]

== By category ==
* [[Cryptography Commands]]
* [[Directory Commands]]
* [[Disk and Tape Drive Commands]]
* [[File Commands]]
* [[Internet and Network Commands]]
* [[Kernel-commands]]
* [[Managing Sessions]]
* [[Packing and Unpacking files]]
* [[Programming-related Commands]]
* [[Scripting]]
* [[Shells]]
* [[System Information]]
* [[Startup/Shutdown Commands]]
* [[Text Viewing and Processing Tools]]
* [[User Commands]]

= External links =
* [http://www.debianhelp.co.uk/commands.htm Complete Basic Linux Commands List] (''www.debianhelp.co.uk'')
* [http://www.debianadmin.com/basic-linux-commands-with-man-pages.html Complete List of Linux Commands With man pages] (''www.debianadmin.com'')
* [http://man-wiki.net/ Linux Man Pages Online] (''man-wiki.net'')
* [http://www.examplenow.com Searchable Linux command examples] (''http://www.examplenow.com'')

LQWiki:Sandbox

2010-03-15T02:01:55Z

Hda7:

{{sandbox}} 

== Welcome to the sandbox! ==
<div style="position: fixed; z-index: 1000000; top: 35%; left: 30%; bottom: 25%; right: 30%; font-size: 200pt; background: #aaffaa; text-align: center;">Hello, this is an attempt to see if plain html with embedded styles will render correctly!
</div>
[[Main Page|Home]]
'''BOLD?'''
''Italic?''

LQWiki:Sandbox

2010-03-15T02:01:05Z

Hda7:

LQWiki:Sandbox

2010-03-15T02:00:45Z

Hda7:

{{sandbox}} 

== Welcome to the sandbox! ==
<div style="position: fixed; z-index: 1000000; top: 30%; left: 30%; bottom: 30%; right: 30%; font-size: 200pt; background: #aaffaa; text-align: center;">Hello, this is an attempt to see if plain html with embedded styles will render correctly!
[[Main Page|Home]]
'''BOLD?'''
''Italic?''
</div>

LQWiki:Sandbox

2010-03-15T01:58:50Z

Hda7:

{{sandbox}} 

== Welcome to the sandbox! ==
<div style="position: fixed; z-index: 1000000; top: 30%; left: 30%; bottom: 30%; right: 30%; font-size: 200pt; background: #aaffaa; text-align: center;">Hello, this is an attempt to see if plain html will render correctly!
[[Main Page|Home]]
'''BOLD?'''
''Italic?''
</div>

LQWiki:Sandbox

2010-03-15T01:58:22Z

Hda7:

{{sandbox}} 

== Welcome to the sandbox! ==
<div style="position: fixed; z-index: 1000000; top: 30%; left: 30%; bottom: 30%; right: 30%; font-size: 200pt; background: #aaffaa; text-align: center;"><br /><br /><br /><br /><br /><br /><br />Hello, this is an attempt to see if plain html will render correctly!
[[Main Page|Home]]
'''BOLD?'''
''Italic?''
</div>

LQWiki:Sandbox

2010-03-15T01:55:41Z

Hda7:

{{sandbox}} 

== Welcome to the sandbox! ==
<div style="position: fixed; z-index: 1000000; top: 10%; left: 10%; bottom: 10%; right: 10%; font-size: 200pt; background: #aaffaa;">Hello, this is an attempt to see if plain html will render correctly!</div>
<See green insert>

LQWiki:Sandbox

2010-03-15T01:54:33Z

Hda7:

{{sandbox}} 

== Welcome to the sandbox! ==
<div style="position: fixed; z-index: 1000000; top: 40%; left: 40%; width: 100px; height: 100px; background: #aaffaa;">Hello, this is an attempt to see if plain html will render correctly!</div>

LQWiki:Sandbox

2010-03-15T01:53:56Z

Hda7:

{{sandbox}} 

== Welcome to the sandbox! ==
<div style="position: fixed; z-index: 1000; top: 5%; left: 5%; width: 100px; height: 100px; background: #aaffaa;">Hello, this is an attempt to see if plain html will render correctly!</div>

LQWiki:Sandbox

2010-03-15T01:53:07Z

Hda7:

{{sandbox}} 

== Welcome to the sandbox! ==
<div style="position: fixed; z-index: 1000; top: 5%; left: 5%; width: 100px; height: 100px;">Hello, thi is an attempt to see if plain html will render correctly!</div>