LQWiki - User contributions [en]

Return to Castle Wolfenstein

2006-10-04T04:27:06Z

Evilmrhenry: Mac version on Linux

'''Return to Castle Wolfenstein''' is an [[FPS]] from Id Software ([[Doom]], [[Quake]]) with single/multi-player capabilities. Dark game based in WWII times, you are an Army ranger that must first escape from imprisonment in Castle Wolfenstein, and when you report your findings to your authorities, you are assigned to return and help stop the creation of a genetically enhanced army being raised to level the allied armies.

== Download ==

You need to download a setup binary to create the base RTCW installation. This will not be a complete install...see the directions in the Install section to complete the installation. Here are some download locations (note, you may need to download the GOTY edition setup file...see install section for details):

[http://www.3dgamers.com/games/returnwolfenstein/ 3D Gamers] 
[http://ftp.ipgn.com.au/rtcw/linux/ iPGN] 
[http://titaniclinux.net/mirrors/wolf/Linux/ titaniclinux.net] 
[http://www.sh.nu/download/games/ SH.NU]

== Install ==

You must have the Retail CD to install RTCW. There are 2 ways to install it, depending on which CD you purchased. If you have the GOTY (game of they year) edition, its much easier. Full directions are at [http://zerowing.idsoftware.com/linux/wolf/INSTALL Id's website]

''Installing from Windows retail CD'' 
If you already have it installed in a Windows partition, you will copy some of the files from there to your RTCW folder in Linux. Otherwise, you can use [http://www.winehq.com Wine] to run setup.exe in Linux and then get the files from that installation directory.

''Installing from GOTY edition'' 
Download and run the ''GOTY'' setup file from one of the above links. After you've installed that, you will need to copy some files off of your CD. See above install link for the list of files.

''Installing from Mac edition'' 
The Mac version of RTCW also works. The installation method from the GOTY edition works, but you will need to mount the disk using the '-t hfs' option, and copy the files from the "Wolfenstein/Main" directory.

You may be interested in buying an [http://www.tuxgames.com/details.cgi?gameref=85&id=250552&nc=1021226295 RTCW installer] from Tux Games. This will do all the manual work described in the above install document for you.

==External links==

[http://games.activision.com/games/wolfenstein/ Homepage]

Ncftp

2005-07-24T21:22:28Z

Evilmrhenry: ncftp automation

'''NcFTP''' is a set of [[FTP]] programs that includes the main, [[CLI]], ftp client program '''ncftp''' and the separate [[CLI]] utilities '''ncftpget''', '''ncftpput''', '''ncftpls''', a batch processing daemon '''ncftpbatch''', and a bookmark manager called '''ncftpbookmarks'''.

NcFTP's ftp client supports tab-completion and command line history.

==Automation==

One of ncftp's strengths is its ability to be automated. For example, to do an upload of pictures from the current directory to a server,
ncftpput -u username -p password ftp.server.com www/pictures *.jpg
This can be placed in a batch file with little difficulty, while the equivalent commands in regular [[FTP]] would be more difficult to script.

==External links==

*[http://www.ncftpd.com/ NcFTP homepage]

Lsmod

2005-07-02T05:24:14Z

Evilmrhenry: slight expansion of arguments

'''lsmod''' is a utility which '''l'''i'''s'''ts currently loaded '''mod'''ules.

A Linux [[kernel]] can have [[module]]s for drivers or other functionality. To keep the size of the kernel small, the modules will be loaded only when specified and as opposed to built in modules will not bloat the kernel if e.g. the driver modules hardware isn't present.

This program has only two possible arguments: -V (--version) and -h (--help). Their use should be self-explanatory.

Ulimit

2005-06-29T02:50:00Z

Evilmrhenry: Added options and examples

'''ulimit''' is a shell [[builtin]] [[command]] used to show and set various restrictions on resource usage for a shell. Among the limitations that can be set you find, maximum file size, maximum core file size, maximum size of resident memory. Though the restrictions are shell-independent, the exact syntax depends on what [[shell]] you are running.

It's a good practice to set some of these limitations to prevent for instance a faulty shell script to start unlimited copies of it self or to prevent users on the system to start processes that run forever.

In general, the command ulimit -$ (where $ is some letter) will return the current value of the variable linked with $, while ulimit -$ NUMBER (again, where $ is some letter, and NUMBER is generally an integer, or "unlimited") will set that variable. Of special note is the -a option, which will display all limits for the system.

The -H and -S options are also special. -H will affect the "hard" limit, which is an absolute limit on a resource. -S
will affect the "soft" limit. The major difference between the two is that hard limits can only be increased by root. Since the default for options is to affect both hard and soft limits, adding -S to a command will allow returning the variable to the previous value without root access.

Finally, all limits only apply to the thread in which they are set. For systemwide setting of limits, try /etc/security/limits.conf

==Examples==
* ulimit -S -c 0 (Set the maximum filesize for core files to 0, as a soft limit. This will prevent [[core dump|core dumps]] from forming, while allowing returning to the previous limit.)
* ulimit -f (Return the maximum file size.)
* ulimit -u unlimited (Remove all limits on the number of simultaneous user processes.)

Core dump

2005-06-29T02:21:36Z

Evilmrhenry: How to allow core dumps

'''Core dump''' is an operation of saving current state of a [[process]] and its memory to a file when the program crashes.

The resulting file, usually called ''core'' can be used by a programmer to find out what happend. Usually a [[debugger]] is used in the process.

In most current Linux distributions creating core files is turned off. To check, or to enable, use the "[[ulimit]] -c" command. For example, ulimit -c 0 will turn off core dumps, while ulimit -c 50000 will allow core dumps (that take up to 25000 KB). Finally, ulimit -c will allow you to view the current value for this variable.

==See also==
*[[core]]
*[[gdb]]
*[[debuggers]]

Gaming via Wine or WineX

2005-04-30T06:49:35Z

Evilmrhenry: Updated Transgaming database location

Many Windows games (and applications) can be run in GNU/Linux. This is normally (since there are other Windows [[emulator]]s as well) done with [[Wine]]/[[WineX]]. Wine and WineX are projects that, in a nutshell, try to replace the Windows base so that your Windows apps and games work properly on GNU/Linux.

While Wine is free to use, [http://www.transgaming.com Transgaming] (the company that develops [[WineX]]) does charge a monthly fee ($5 per month, 3 month minimum) for easy-to-install packages and updates. It is possible, though, to use WineX for free, but the process involves downloading and compiling older versions. The advantage is that WineX is more thoroughly tested for games, so you have a much greater chance to play. It is also focused on getting the Direct 3D layer of Windows working on Linux.

== Wine ==

Since there isn't any information here yet, I suggest you go to [http://www.winehq.com WINE's homepage]. There are normally tips and hints on how to make a certain app/game work under GNU/Linux with Wine. Another site to watch is [http://frankscorner.org Frank's Corner]. Frank's Corner provides easy tutorials for the installation and use of common Windows games and apps on Linux.

Since Wine is still in Alpha state (unstable) you should take care to follow the exact instructions you find on how to install each game. Note also that installing new versions (builds) of Wine can make functioning games to stop working. If it ain't broke, don't fix it!

You can find Wine prepackaged and ready to install in most major distributions; if you want newer (or perhaps older) builds, you'll have to [http://www.winehq.org/site/download download] them from the website.

==WineX==

Transgaming maintains a [http://transgaming.org/gamesdb/ database] of the games currently supported, and their actual usability on Linux, varying between 0 (Doesn't install nor work) and 5 (as in Windows). Remember, when you search, to use full names instead of game acronyms (Diablo 2 instead of D2 for instance). Results will link you to pages that have a compatibility rating, screen shots, and a message board for the game you searched for. However, the database is often out of date.

The message board is important, as the compatibility rating is not always accurate. Reading through it can provide a better idea as to the actual compatability.

It's also important to frequently check the TransGaming website (listed above) for WineX as new versions come out regularly that solve older problems. (for example, [http://steampowered.com/ Steam] now works in 3.3).

==Currently supported games==

Games that have been reported to work on [[Wine]]/[[WineX]] include Starcraft, Warcraft III - Reign of Chaos and Warcraft III - The Frozen Throne, GTA 3 - Vice City, Jedi Knight 2 - Jedi Outcast, Half Life and its many modifications, including Counter-Strike, and many more. Note that games coming from [http://www.idsoftware.com ID Software], such as Quake 3 Arena, Return to Castle Wolfenstein and Enemy Territory, run natively on Linux (i.e. without the need for Wine).

==System Requirements==

For 3D games to work on Linux, you must have a supported graphic card with 3D capabilities. At the moment, these include nVIDIA cards (very good drivers) and ATI cards (also good).

Sed

2005-04-30T06:09:02Z

Evilmrhenry: On second thought, plain * doesn't work. Fixed.

'''sed''' ('''s'''tream '''ed'''itor) is an editor used, not interactively on text files (like [[vi]] or [[emacs]]), but on [[stream]]s. This allows it to transform text input from a pipe or the command line or a file (if it is piped to sed or given as an argument to sed).

sed supports [[regular expression]]s which gives it great control over what it can do to the input stream. Common applications of sed include parsing log files, replacing specific words/typos in a stream, and reading [[CSV]] files.

==Substitution==

The Substitute command is quite powerful. In its basic form, it consists of 's/old/new/g', which will replace all occurances of "old" with "new". Of course, the basic form can be changed significantly.

'''Regular Expressions''': [[Regular Expression]]s allow replacement of patterns instead of strings. sed uses the standard [-]*^ regex syntax. For example, 's/[0-9]*//g' will remove all numbers from the input.

'''Remembering the input''': sed can remember parts of the input pattern, and replace that section in the output file. This is done through the &, $, $, and \1-9 commands.

The & command, when used in the replacement pattern, is replaced with the input string. For example 's/[^ ]*/&&/g' will double the input. The commands allow for more precise work; any text between the first $ occurance and the first $ occurance can be placed into the output with \1. The second pair can be recalled with \2, and so on, up to \9. For example, 's/$[0-9]$$[0-9]*$/\2\1/g' will take numbers, and put the first digit of the input on the end of the output.

'''Multiple Substitutions''': Normally, sed can only make one substitution at a time; sed 's/old1/new1/g' 's/old2/new2' will not work. However, the -e option allows multiple commands. Place a "-e" before all commands: sed -e 's/old1/new1/g' -e 's/old2/new2/g'

==Examples==

One of the most common uses of <tt>sed</tt> is to make a quick substitution in a file or data stream. This is done with the following:
$ ''command'' | sed 's/''regexp''/''replacement''/g'
Here, <tt>''command''</tt> generates the input data, <tt>''regexp''</tt> is the text to search for and remove, and <tt>''replacement''</tt> is the new text to insert. The <tt>g</tt> suffix causes <tt>sed</tt> to make more than one replacement per input line as is usually intended.


<tt>sed</tt> is commonly also used as a pre-processing step before handing off to another program. A specific example of this would be to strip out all HTML tags from a file before passing the file to <tt>grep</tt> for the word ''internet''.
$ sed 's/<.*>//g' foobar.html | grep internet

<tt>sed</tt> also works for text editing tasks. For example, the command 
$ sed -e 's/foo $[^ ]*$/foo("\1")/g' -e 's/bar $[0-9]*$ $[^ ]*$/bar(\1, "\2")' < inputfile.txt > outputfile.txt
will search the file <TT>inputfile.txt</TT> for all strings of the form <tt>foo something</tt> and replace them with <tt>foo("something")</tt>. It will also search for strings of the form <TT>bar 543543 something</tt> and replace them with <tt>bar(543543, "something")</tt>. It will then output the resulting file to outputfile.txt.

Examining the above command in more detail: the -e flags specify a new expression, allowing more than one replacement rule in the same command. The escaped-parentheses $ and $ tell sed to remember the string that was enclosed. The \1 and \2 commands tell sed to insert a remembered string; numbers 1-9 all work as expected. The [0-9]* and similar commands are just [[Regular Expression]]s.

==External links==

*[http://man.linuxquestions.org/index.php?query=sed&section=0&type=2 sed man page]
*[http://www.gnu.org/software/sed/manual/sed.html GNU sed online manual]

Sed

2005-04-30T05:00:06Z

Evilmrhenry: Added more examples/doc on the substitute command

'''sed''' ('''s'''tream '''ed'''itor) is an editor used, not interactively on text files (like [[vi]] or [[emacs]]), but on [[stream]]s. This allows it to transform text input from a pipe or the command line or a file (if it is piped to sed or given as an argument to sed).

sed supports [[regular expression]]s which gives it great control over what it can do to the input stream. Common applications of sed include parsing log files, replacing specific words/typos in a stream, and reading [[CSV]] files.

==Substitution==

The Substitute command is quite powerful. In its basic form, it consists of 's/old/new/g', which will replace all occurances of "old" with "new". Of course, the basic form can be changed significantly.

'''Regular Expressions''': [[Regular Expression]]s allow replacement of patterns instead of strings. sed uses the standard [-]*^ regex syntax. For example, 's/[0-9]*//g' will remove all numbers from the input.

'''Remembering the input''': sed can remember parts of the input pattern, and replace that section in the output file. This is done through the &, $, $, and \1-9 commands.

The & command, when used in the replacement pattern, is replaced with the input string. For example 's/*/&&/g' will double the input. The commands allow for more precise work; any text between the first $ occurance and the first $ occurance can be placed into the output with \1. The second pair can be recalled with \2, and so on, up to \9. For example, 's/$[0-9]$$[0-9]*$/\2\1/g' will take numbers, and put the first digit of the input on the end of the output.

'''Multiple Substitutions''': Normally, sed can only make one substitution at a time; sed 's/old1/new1/g' 's/old2/new2' will not work. However, the -e option allows multiple commands. Place a "-e" before all commands: sed -e 's/old1/new1/g' -e 's/old2/new2/g'

==Examples==

One of the most common uses of <tt>sed</tt> is to make a quick substitution in a file or data stream. This is done with the following:
$ ''command'' | sed 's/''regexp''/''replacement''/g'
Here, <tt>''command''</tt> generates the input data, <tt>''regexp''</tt> is the text to search for and remove, and <tt>''replacement''</tt> is the new text to insert. The <tt>g</tt> suffix causes <tt>sed</tt> to make more than one replacement per input line as is usually intended.


<tt>sed</tt> is commonly also used as a pre-processing step before handing off to another program. A specific example of this would be to strip out all HTML tags from a file before passing the file to <tt>grep</tt> for the word ''internet''.
$ sed 's/<.*>//g' foobar.html | grep internet

<tt>sed</tt> also works for text editing tasks. For example, the command 
$ sed -e 's/foo $*$/foo("\1")/g' -e 's/bar $[0-9]*$ $*$/bar(\1, "\2")' < inputfile.txt > outputfile.txt
will search the file <TT>inputfile.txt</TT> for all strings of the form <tt>foo something</tt> and replace them with <tt>foo("something")</tt>. It will also search for strings of the form <TT>bar 543543 something</tt> and replace them with <tt>bar(543543, "something")</tt>. It will then output the resulting file to outputfile.txt.

Examining the above command in more detail: the -e flags specify a new expression, allowing more than one replacement rule in the same command. The escaped-parentheses $ and $ tell sed to remember the string that was enclosed. The \1 and \2 commands tell sed to insert a remembered string; numbers 1-9 all work as expected. The [0-9]* and similar commands are just [[Regular Expression]]s.

==External links==

*[http://man.linuxquestions.org/index.php?query=sed&section=0&type=2 sed man page]
*[http://www.gnu.org/software/sed/manual/sed.html GNU sed online manual]

Regular expression

2005-04-30T04:21:05Z

Evilmrhenry: Added Lazy quantifiers

'''Regular expressions''', also known as "patterns" or simply "regexes" are a notation of describing sets of strings. They are used in many facets of the Unix environment.

Invented by mathematician Stephen Cole Kleene in the mid-1950s as a way to manipulate "regular sets", they are formal descriptions of the behaviour of finite state machines, in regular algebra.

Later adopted by computer science as a way of representing patterns with a combination of symbols and operators.

There are many differing "flavors" of regular expressions, though they all fall into one of three primary types of regular expression engines:
*[[DFA]] - ''Deterministic Finite Automaton'' (used by such things as [[awk]], [[egrep]], and [[lex]])
*[[NFA]] - ''Nondeterministic Finite Automaton''(used by such things as [[Perl]], [[Python]], and [[Tcl]])
*POSIX NFA

==Features==
Irrespective of syntax, the following features are in all widely-used regex engines:
*The ability to match any one of a given set of subexpressions, eg "match Tom '''or''' Dick '''or''' Harry"
**The ability to match any one of a group of characters, eg "match '''any one of''' a, e, i, o and u"
***Within such a group, the ability to include ranges of characters, eg "match '''any one of''' the characters a through f inclusive"
***The ability to invert those groups so that only characters not included may match, eg "match '''any character other than''' z"
***The ability to match any character that is not a newline (or less frequently, any character at all; some syntaxes provide allowance for both)
***The ability to match any character in a certain character class, and inverted instances of each class
****A character class consisting of letters
****A character class consisting of digits
****A character class consisting of whitespace (spaces, tabstops, linefeeds, etc)
****A character class consisting of "word characters" (usually letters, digits and the underscore)
*The ability to match a certain subexpression a variable number of times, eg "match Tom '''at least''' twice" or "match Dick '''between''' three and seven times"
**The ability to make a given subexpression match optionally
**The ability to make a given subexpression match zero or more times
**The ability to make a given subexpression match one or more times
*The ability to store a matched subexpression and match it again later, eg "match Tom '''or''' Dick '''followed by''' Harry '''followed by''' whoever was originally matched"
*The ability to make "zero-width" matches; adding these to a regex which matches strings in group ''x'' will narrow it down to strings in group ''y'', ''y'' being a subset (possibly containing the entiriety) of ''x'', but will not change (except possibly by narrwing down) the matched portions of any of these strings.
**The ability to make these matches at the beginning or end of a string
**The ability to make these matches at the beginning or end of a line
**The ability to make these matches at the boundry between a "word" and a "non-word" character

==Literals & Meta Characters==
Regular expressions, often called patterns, are mainly built up using a combination of literals and meta characters. Let's take it from an example:
*grep -e 'Linux' somedoc
Grep uses regular expressions to search documents for matches to the regular expression. The command above would search the file somedoc for lines containing the characters Linux in that order and print them on the screen. All characters in that pattern are literals, taken literally.
*grep -e '.inux' somedoc
The dot (.) in this pattern is a meta character meaning any character (except new line). This would search the same file for lines with the characters inux that are preceded by any character, for example would it match Linux as well as linux or tinux.

Most characters are taken as literals, and include letter, numbers and space. In certain syntaxes, such as that of grep, this is true even of most metacharacters - they are taken as literals unless they are [[Escaping|escaped]], traditionally with a backslash. In others, such as that of egrep, the meta form of a character is the default, and escaping turns it into a literal.

==Common syntax==
This is the most common syntax for expressions, defined by the [[POSIX]] 1003.2 standard and adopted by just about everything that uses them. There are many differences, such as whether or not certain metacharacters need escaping or not, and extra features have been added, but regexes written for one program in this syntax will be mostly portable to another program.

===Branches===
A pattern will match if one or more of its branches does. A branch consists of several pieces which match next to each other. They are usually separated with the metacharacter |.

===Pieces===
A piece is merely an atom, optionally followed by a quantifier. It matches if the atom matches as many times as required by the quantifier, or once if there is no quantifier.

===Atoms===
An atom is simply anything that will match on its own, and will match if it is there. Atoms include:
*Any character that is not a metacharacter, including metacharacters that match literally by means of escaping (or lack thereof)
*The . (period) character, to match any character that is not a newline
*^ or $, to match the null string at the beginning and end of a string, respectively (sometimes they also or only match at the beginning and end of a line, rather than a string; often however, the distinction is meaningless as witth programs such as grep which only operate on entire lines)
*Bracket expressions
*Subexpresions, which are patterns in their own right and as such can contain branchs, pieces, atoms and quantifiers of their own.

===Quantifiers===
Quantifiers provide us with a possibility to match a certain number of the previous character or meta character. Some of the most common quantifiers are:
* * Match 0 or more times
*+ Match 1 or more times
*? Match 1 or 0 times
The pattern ''Li*nux'' would match any number of i like the following, Lnux Linux Liiiiinux. If we exchange the * for a + Lnux wouldn't be matched.

There are also quantifiers for telling the exact number of times to match or a range.
*{n} Match exactly ''n'' times
*{n,} Match at least ''n'' times
*{x,y} Match at least ''x'' times, but no more than ''y'' times
Often the braces will not be metacharacters by default, requiring \{n\}, \{n,\}, etc. Less often, this will only apply to the opening brace, allowing just \{n}, \{n,}, etc.

===Bracket expressions===
So called because they reside within [ and ], any character between them will match. They can be inverted by placing a caret (^) as the first character. Ranges can be specified using hyphens: [a-d] means the same as [abcd]. Character classes can be specified inside them with another set of bracket enclosing colons and the name of the class: ''[:classname:]''. Class names include ''alnum'' (the same as ''a-zA-Z0-9'') and ''digit'' (the same as ''0-9'').

===Subexpressions===
Surrounded with $ and $ (this is the only instance in which the POSIX standard calls for a metacharacter to be literal by default), these are full patterns in their own right, but treated as atoms by the including pttern. As such, any pattern can be parenthesised and optionally followed by a quantifier to become a piece, which can be included in a branch, which can be part of its own subexpression, ad infinitum.

==Backtracking==
[more]

==Backreferences==
One of the more useful constructs is grouping and back referencing which let us group and reuse matches. Backreferencing comes extra handy when doing substitutions where we can use the matched part in the substitution string.

Grouping can be done with or without capturing. When using capturing the matched text are saved for later use, called backreferencing. The use of non-capturing grouping is useful when you want to use alternation, as in the pattern (apple|banana) for matching ''apple'' or ''banana''.
*( ) Group the text without capturing
* Group the text and capture the result

Let's use [[sed]] as an example:
*sed -e 's/$Linus$/\1 Torvalds/g' somedoc.txt
The substitution command to sed has the syntax, ''s/text to replace/text to insert instead/options''
 
This substitution above searches the somedoc.txt for occurrences of ''Linus'' and puts every match in memory. It replaces it with the first match (\1) and adds a space plus the text ''Torvalds''.

==Greedy==
Standard quantifiers as those described above are greedy, they try to match as many times as possible. The pattern (an)+ would match ''anan'' in the word ''banana''. The greedy quantifiers will only give up matches (called [[#Backtracking|backtracking]]) when it's needed to find an overall match to the pattern.

==Lazy==
Lazy quantifiers are basically the opposite of greedy quantifiers; they match as few times as possible, only taking extra matches when needed to match an overall pattern.

==Positive/Negative lookahead==
[more]

 

==External links==
*http://www.regular-expressions.info/

 
{{msg:stub}}

Sox

2004-12-21T01:41:16Z

Evilmrhenry: fixed spelling: although

'''sox''' is a powerful sound sample converter capable of converting between well over 20 different formats. They include .8svx, .aiff, .au, .avr, .cdr, .cvs, .dat, .gsm, .hcom, .maud, .mp3, .nul, .ogg, ossdsp, .prc, .sf, .sph, .smp, .snd, .sndt, sunau, .txw, .vms, .voc, .vox, .wav, .wve, and .raw, (From sox -h) so the conversion you need should be in there.

Used in its most simple form, sox can be used as "sox input.wav output.ogg".

Sox can also perform some effects, such as fade-in/out, or tasks like turning up/down the volume, or resampling the audio

usage: ''sox OPTIONS input OPTIONS output EFFECTS''

sox is rather picky about that order, effects/filters are at the end, the options are declared 2 times, one for the input data, and the other for the output, although the output can inherit the input options, such as the sample rate, number of channels, etc

read sox's [[man]] page for full info on what it can do, and be sure to read carefully, its not exactly the easiest to understand man page.
{{msg:stub}}

Usleep

2004-12-15T03:12:15Z

Evilmrhenry: closed tag, added space

'''usleep''' suspends execution for microsecond intervals.

wait for 1 microsecond: 
$ usleep 1

wait for 1000 microseconds, which is 1 milli second: 
$ usleep 1000

wait for 1 million microseconds, which is 1 second: 
$ usleep 1000000

<tt>sleep 1</tt> is equivalent to <tt>usleep 1000000</tt>

BUGS : Probably not accurate on many machines down to the microsecond. Count on precision only to -4 or maybe -5.

If you have a fast PC like a 2 GHz P4 or AMD, the accuracy is ok.

==Also see==
*[[sleep]]

Dir

2004-12-15T03:04:57Z

Evilmrhenry: created

The dir command will display the contents of the current [[directory]]. It is equivalent to "[[ls]] -C -b".

Zipsplit

2004-12-15T02:39:46Z

Evilmrhenry: changed formatting from html to wiki

'''zipsplit''' [options] [-n size] [-r room] [-b path] zipfile

Split a zip file into multiple zip files.

"Size" must be larger than the largest compressed file.

==OPTIONS==

*'''-t''': tell how many files would be used, but don't create them
*'''-i''': create index (zipsplit.idx), count size against first zip file
*'''-n''': maximum zip file size (default = 36000 bytes)
*'''-r''': leave room for so many bytes on the first disk (default = 0)
*'''-b''': path for output zip files
*'''-p''': pause between output zip files
*'''-s''': output zip files in sequence, even if it's not optimal

==Examples:==

''See how many zip files it would be, if split into 100,000 bytes each.''

zipsplit -tn 100000 blah.zip

''Perform the split.''

zipsplit -n 100000 blah.zip

==See also:==
* [[zip]]

Exit

2004-12-15T02:34:48Z

Evilmrhenry: Added use with su

'''Exit''' is a built in command for some [[shell]]s, specifically [[bash]].

It causes the shell to exit with a error code that is optionally given to it as a argument.

This command is quite useful when coupled with [[su]]. After switching to another user, the exit command will exit out of that shell, returning to the previous user.

Typing '''help exit''' in a [[terminal]] will give more info on the command.

Whoami

2004-12-15T02:30:14Z

Evilmrhenry: simple > simply

The [[command]] '''whoami''' simply outputs the username of the currently logged in user. For example:

[JRHacker@localhost /]$ whoami
JRHacker

The object of this for human use is quite easily defeated by the fact that most shells display the username in the prompt (as shown above in the [[Bash]] example) but can be used by applications to retrieve the current username through [[piping]].

Ping

2004-12-15T02:29:11Z

Evilmrhenry: Added examples, and means of stopping ping

'''Ping''' is a [[network]] troubleshooting tool that sends [[ICMP]] echo requests that is used for testing connectivity between [[node]]s. It, of course, is named after sonar pings that a submarine uses to detect other ships. It is sometimes said to stand for '''P'''acket '''IN'''ternet '''G'''roper, but this is a [[backronym]].

One difference between the MS-DOS/Windows version of this tool and the Linux version is that, by default, the DOS version quits after 4 pings, the Linux version keeps pinging indefinitely. (Stop it with Ctrl C, or run it with the -c 4 option to stop after 4 pings.)

==Examples==
* ping 127.0.0.1
** Pings your local machine.
** This should work, even with no internet connection.

* ping www.google.com
** Pings Google.
** Note that ping can accept IP addresses or domain names.

==See also==
*[[traceroute]]

Renice

2004-10-22T19:39:57Z

Evilmrhenry: details, permissions, and examples.

'''renice''' is a [[command]] used to change the [[priority]] of running processes.

renice can be used to change the priority of a single [[process]] or a whole process group. It can also change priority for processes owned by a given user or group.

Note, however, that the nice value of a process is not the priority. a nice value of -5 means the process gets priority over processes with greater nice values, such as +5. The allowable nice values usually run from 20 to -20, with 0 being the default.

When renicing processes, [[permissions]] are taken into account. If you do not own the process, you cannot renice it. Also, even for processes you do own, it is still not possible to increase the priority beyond a system-specific level. (Usually 0) Both of these restrictions are ignored by the [[superuser]].

Example renice commands: (Assumes apropriate permissions.)
* renice -2 -p 17055 (Sets the process with the [[PID]] of 17055 to a nice value of -2)
* renice 10 -u user_name (Sets all processes owned by user_name to a nice value of 10, decreasing the priority.)

----
renice is also a system library call, which programmers can use to change the prority of a process.

==See also==
*[[nice]]

Sox

2004-10-22T18:04:13Z

Evilmrhenry: Listed file formats, added example.

Command options

2004-10-22T17:49:35Z

Evilmrhenry: Added -- option.

Command-line options ('''Command options''' or flags) are parameters given to a [[command line]] program to alter the way it runs. One of the most familiar examples of their usage is <tt>ls -l</tt>, where ''-l'' is a flag telling <tt>ls</tt> to use the command's "long" format.

==Types of Options==

* The simplest options are single-letter flags like the <tt>-l</tt> above. They can be combined into a single word, like <tt>ls -la</tt> to use the '''l'''ong format and list '''a'''ll files.

* Some command options take arguments. Then the program knows not only that the option was given, but also gets some additional information. An example is <tt>ssh -l myname myhost.myisp.com</tt>, where the <tt>-l</tt> option is given the parameter <tt>myname</tt> to tell [[ssh]] what username to use when connecting. These options can be combined with the first type, though they must be the last option in the word, like <tt>ssh -Xl myname myhost.myisp.com</tt>, where the <tt>X</tt> tells ssh to try to forward X connections, and the <tt>l</tt> is the same as before.

* long options of the X type use a single <tt>-</tt> and consist of more than one letter. They can take arguments or not. For example, <tt>emacs -geometry +0-0</tt> uses the <tt>geometry</tt> option to tell [[emacs]] to place itself in the corner of the screen.

* long options of the GNU type use the double <tt>--</tt>. <tt>ls --all</tt> is the same as <tt>ls -a</tt>. Long and single-letter arguments can be mixed on the same commandline, but not in the same word. Long options of this type that take arguments sometimes use an equals sign instead of a space to separate the option name from its argument.

* When running a program on a data file that may be mistaken for an option, the -- option can be helpful. This option shows that the option listing is over, and the next input will be a datafile. (Example: rm -- -f would delete the file "-f")

==How to write programs that take options==

* [[C]] programs can use the <tt>getopt()</tt> function to interpret single-letter command options. <tt>getopt_long()</tt> finds long options with '<tt>--</tt>' before them, while <tt>getopt_long_only()</tt> can find long options with either '<tt>--</tt>' or '<tt>-</tt>'. All of these are described in the getopt() man page (see External links below).
* [[Shell scripts]] can use the <tt>getopt</tt> program.
* [[bash]] scripts can use the <tt>getopts</tt> [[builtin]] command.
* [[Perl]] scripts can use the Getopt::Std or Getopt::Long module.

==External links==

* [http://man.linuxquestions.org/index.php?query=getopt&section=1&type=2 getopt man page] - for shell scripts (including bash)
* [http://man.linuxquestions.org/index.php?query=getopt&section=3&type=2 getopt() man page] - for C programs
* [http://man.linuxquestions.org/index.php?query=bash&section=0&type=2 bash man page] - for bash scripts
* [http://man.linuxquestions.org/index.php?query=Getopt%3A%3ALong&section=0&type=2 Getopt::Long] and [http://man.linuxquestions.org/index.php?query=Getopt%3A%3AStd&section=0&type=2 Getopt::Std] - for perl

:''This section is a [[LQWiki:stub articles|stub]] and needs to be finished. [[LQWiki:plunging forward|plunge forward]] and [[LQWiki:How to edit a page|help it grow]]!''

Roguelikes

2004-03-18T04:12:16Z

Evilmrhenry: death in rougelikes

'''Roguelikes''' refers to a genre of [[Gaming|games]] which are similar to the classic computer game '''Rogue'''. These [[role playing games]] are usually formed on a fantasy or sci-fi backdrop, and present the player with a randomly generated dungeon. The dungeon in these games is furthermore represented as an [[ASCII]]-based map, typically with an '''@''' representing the player, '''#''' or equivalent characters for walls, '''^''' representing traps, and various colored letters representing different monsters. Some roguelikes have graphical interfaces available, although die-hard players prefer the [[ASCII]] symbols. A major feature of roguelikes is that death is permanent. Once the character dies, the game will need to be restarted from the beginning. This creates a focus on playing defensively, trying to survive instead of trying to win.

== List of roguelikes ==

The following roguelikes are available for Linux-based systems.
* [[ADoM]] (Ancient Domains of Mystery)
* [[Angband]] (with approximately 50 variants)
** [[ToME]]
* [[Avanor]]
* [[Fargoal]]
* [[IVAN]]
* [[Moria]]
* [[Nethack]]
** [[Slash'EM]]

== External links ==
* [http://en.wikipedia.org/wiki/Roguelike Roguelike] (Wikipedia article)

C/C plus plus tips

2004-03-10T07:48:53Z

Evilmrhenry: quicksort

==Overview==

In a nutshell,..

C is ubiquitous on GNU/Linux and UNIX. Back in frontier times, when computer scientists programmed mostly in [[assembly]], C was considered a high-level language. Nowadays, most folks think of C as a low-level language, and comparatively few people (except compiler writers, OS kernel authors, and their ilk) use assembly language. C is a procedural language and is pretty easy to learn but has many pitfalls for the unwary.

C++ is an object-oriented language, built upon the foundation that is C. C and C++ are not the same language. C++ is not exactly a superset of C, but if you can program in C++, you can program in C. [[Objective-C]] however, ''is'' an object-oriented superset of C. C++ is large, complex, and powerful -- and not for the faint of heart. It takes considerable time to master C++.

Compiled C code runs very fast. Some would say optimized C code can be as fast as hand-written assembly. Compiled C++ code may run just about as fast as C depending on how carefully the code is written. Programs written in interpreted languages like Python and Perl typically won't run nearly as fast as C or C++ programs.

If you are interested in writing system software, device drivers, compilers, operating systems, virtual machines, or graphics-intensive code (or similar software which needs to execute very quickly), you very likely want to learn and use C and/or C++. If you are just interested in GUI application software, C++ might be useful, but [[Python]] might be even better. If you are more interested in system administration, try [[Perl]]. If you want to write GUI software that will also be able to build and run on Mac OS X, have a look at [[GNUstep]] and [[objective-c]]. If you just want to be different, maybe look into [[ruby]], the D programming language, [[lisp]], or any number of other languages that have implementations available for GNU/Linux.

You compile C and C++ code on GNU/Linux using the GNU Compiler Collection ("[[GCC]]"). A C program gets compiled with the <tt>gcc</tt> command, and a C++ program gets compiled with the <tt>g++</tt> command. Note that GCC (the software package) compiles more than just C and C++. It can also build [[objective-c]], [[java]], [[ada]], and [[fortran]] source code.

==Comments: Early and often==

Do comment your code. It rarely hurts to describe what you are doing, and more importantly, why.

Documentation is the most important part. Trying to find out how component X is supposed to be used by looking at the code alone is tedious and error-prone. This is especially important if the code might work anyway on platform Z even when you leave initfoo() out. You can be sure that someone on that platform will do so if it's not there.

Also, if you're about to do some complex task, write your intent briefly down in natural language first. This will both help you organize your thoughts and let someone else later grok what you were trying to do if the code after all doesn't. Sometimes the writing might be more clumsy than the code itself though. Use common sense.

An example of a good comment:
/*
* Insert the values in buckets by their Nth byte. Bucket pointers are
* set up so that they will automatically form a concatenated list this way.
*/
Here we describe a perhaps non-obvious part of an algorithm. Very good.

However, a good code needs less comments than a bad one because it's more readable. Thus, the need to comment is often a sign of another problem:

obscure++; /* this is pointer to the last element */
Renaming the variable does the same.

last_el++; /* increment last element */
Now, that's pretty obvious.

/* last_el points to the first_el+N now */
Otherwise a good one, but we could assert(last_el == first_el+N) instead.

/*
* Insert the values in buckets by their Nth byte. Bucket pointers are
* set up so that they will automatically form a concatenated list this way.
*/
for (i=0; i<cnt; i++) for (j=0; j<i; j++) if (a[i]<a[j]) SWAP(a[i], a[j]);
Uh, that isn't really what we're doing, now is it? ;) Yes, comments get outdated when code gets replaced by better implementations etc. You need to keep them up to date. In this case, a mention that the algorithm was changed because it didn't work for negative values would be helpful.

==Debugging==
===Let the Compiler Nitpick===
When compiling with GCC or G++, always use the <tt>-Wall</tt> command-line argument to tell GCC/G++ to print extra warnings and errors. This can often help you locate potential problems in your code. But it's not enough to let the compiler spit the nitpicks at you; you have to take them seriously. Warnings are often a sign that your code is doing something it shouldn't.

Other useful options of gcc are <tt>-Wstrict-prototypes -Wmissing-prototypes</tt>. These help make sure your function calls have the correct arguments, even <tt>printf()</tt> calls.

[Examples?]

===Remote Debugging with DDD and gdb===

1. Make sure gdbsever and libthread_db.so.1 on the remote machine.

2. run gdbserver on target:
gdbserver host:2345 /path/application

The "host" is ignored, so this can be anything. 2345 is an arbitrary TCP
port not in use. 2345 ususally works, just make sure it does not conflict with other IP ports in use.

The target application on the remote machine does not require symbols (debugging information).

3. On the host (your local PC):
a. ddd program (must have symbols)
b. At the (gdb) prompt
target remote xxx.xxx.xxx.xxx:2345

Where the IP address is that of the remote machine.

That's it, remote debugging is up and running.

==Optimization==

Optimizing a program is often more an art than a science. But even in art, there are some rules that should be carefully followed (especially for new practitioners who aren't quite sure why the rules are important).

===Optimization Rule #1 : DON'T!===
You're coding along, minding your own business, when you notice a simple, quick optimization just begging to be done. Maybe it's as simple as replacing <tt>d = c * 2;</tt> with <tt>d = c << 1;</tt>. Why do an expensive multiply when you could do a cheap right-shift and come up with precisely the same result?

Why indeed? This optimization should do the right thing, but at the expense of a tiny bit of program clarity. Program clarity is a precious commodity, which isn't something that can be said for your computer's processor time. It may be that you'll end up making precisely this optimization later on. But right now, the important thing is to get the program working correctly.

===Optimization Rule #2 : DON'T!===
So now the program runs. It runs like a fifteen year old weiner dog. Sometimes it sits down on its haunches, staring off into space as though it's waiting for a doggie treat. So it's time to go in and replace that multiply with the bitshift, right?

Patience, grasshopper.

Before you decide if it's worth investing even one second in optimizing the program, decide how valuable your effort is going to be. The value derived from the effort is directly linked to the purpose of the program. Is it a tiny app you wrote for your own personal use, that you'll only use once a week? Is it part of a critical, high-performance application or library that will be used by millions, or a scientific number-cruncher which will take years to solve a problem? Most likely, it will be somewhere between these two extrema. To some extent, "fast enough" is a subjective judgment.

===Optimization Rule #3 : DON'T!===
Okay, I see you're getting impatient. You want to go in and make that aged dachshund run like a young rotweiler chasing a mailman smothered in barbecue sauce. But the bad news is, it's still not time to replace that line of code. If you go back in and start "optimizing" right now, you may end up with hundreds of little tweaks, whose overall effect is to make the code difficult to understand and impossible to maintain. Even worse, it may not speed your program up noticeably.

Before you make a single change, take advantage of a profiler ([[gprof]] ([http://www.cs.utah.edu/dept/old/texinfo/as/gprof.html tutorial]), for example). A profiler will tell you exactly where your code is spending all its time. The rationale for this is referred to as [http://en.wikipedia.org/wiki/Amdahls_law Amdahl's law] : The amount of time saved by optimizing a section of code cannot be greater than the time the program spent running that code. For example, if a single for loop comprises 7% of a program's running time, then no optimization you could perform on that loop will cause more than a 7% performance increase.

Most programs spend most of their time executing a few very small areas of code. Find out which areas, and you'll likely get huge boosts from small changes.

===Optimization Rule #4 : Never Assume an Optimization Works===
It is important that you know exactly how the unoptimized version of your program was performing, because many optimizations don't do anything. Some "optimizations" will even slow your program.

Part of this is due to the fact that, without being told, the compiler will try to do whatever optimizations it considers "safe", and a programmer's attempts to optimize the code may interfere with the optimizations the compiler is trying to perform. The best thing is to perform one optimization, compare the new performance to the old performance, decide whether to keep it, and then move on to the next potential improvement.

===Optimization Rule #5 : Three Words: Algorithms===
Very frequently, the best way to speed up a program is to change the way you solve the problem. No amount of pointer arithmetic or loop unwinding is going to give you a thousand-fold improvement in runtime, but changing the algorithm frequently does just that. For example, changing a sorting algorithm from bubble sort to quicksort can make an hour-long sort take just seconds. [Need details, specifics]

[That's really 90% of optimization (sans details), but there are also things to cover like pre-caching, just-in-time calculation, optimizing for space vs. optimizing for time, etc.]

===Save Compiler Optimizations for the End===
Also, don't use any -O flags when debugging, it can compound current errors and make things really weird. They can possibly add new bugs too, due to the way the compiler does low-level optimization. The higher the optimization level, the riskier the optimizations that the compiler will attempt.

Once you know the program works in an unoptimized state, then it may be time to crank the -O flag up a couple of notches. Compare both performance and stability between the unoptimized and optimized versions.

==Memory management==
===Valgrind===
Many new programmers have difficulties with pointers and sudden segmentation faults due to careless usage. [http://valgrind.kde.org/ Valgrind] is an excellent program to get more information about what is causing the problems.

===new and malloc: Arch-nemises===
Don't mix malloc and new; they might work togeather temporarily, but they're bound to cause errors. Pick which one from the start and stay with it. Valgrind will also point out this kind of error.

''Note: The same can be said for <iostream> and <iostream.h>. Don't play mix and match.''

==Use Macros With Care==
Macros are simply precompiler directives that instruct the compiler to replace certain strings of text with others before it attempts to compile. If used carelessly, they can make a program terribly confusing.

For example, if you wanted to be intentionally misleading, you could write:

<tt> #define CLOSE_BLOCK {
#define OPEN_BLOCK }
#define CIN cout
#define COUT cin</tt>

and then write the rest of the program as follows:

<tt> for( int i = 0; i < 100; ++i )
CLOSE_BLOCK
for( int j = 0; j < 100; ++j )
CLOSE_BLOCK
CIN << data[ i ][ j ];
OPEN_BLOCK
OPEN_BLOCK</tt>

But intentional obfuscation isn't the real danger. The real problem comes from accidental obfuscation, as in the following example.

===Example: Proving the Meaning of Life===

The meaning of life is elusive. Here is a prime example of why parentheses are needed around macro definitions.

life.c:
----
<tt> #include <stdio.h>

#define SIX 1+5 /* Should be (1+5) */
#define SEVEN 6+1 /* Should be (6+1) */

int main()
{
printf("The meaning of life: %d x %d = %d\n", SIX, SEVEN, SIX * SEVEN);
return 0;
}</tt>
----
Rather than evaluating (1+5) * (6+1) as we would hope, the compiler will now read the statement as 1+(5*6)+1. Result: 32 rather than 42, and thousands of years of time wasted by the galaxy's biggest supercomputer.

Rm

2004-03-09T21:43:58Z

Evilmrhenry: added examples

==Command rm==
Removes files or directories. Rm removes each specified file. By default, it does not remove directories. If a file is unwritable, the standard input is a tty, and the -f or --force option is not given, rm prompts the user for whether to remove the file. If the response does not begin with `y' or `Y', the file is skipped.

===Syntax===
'''rm ''[OPTION] file'' '''

===Options===
* ''-d'', ''--directory'' - unlink file, even if it is a non-empty directory (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

===Examples===
* rm file1.txt
** removes file1.txt
* rm -r testing
** removes the directory 'testing', including all files it contained.
* rm file*
** removes all files starting with the letters 'file' (eg file1.bin, filed.txt).
* rm -i file1.txt
** asks you for confirmation before deleting file1.txt.

To remove a file whose name starts with a `-', for example `-foobar', use one of these commands:

* rm ./-foobar
* rm -- -foobar

Note that if you use rm to remove a file, it is usually possible to [[recover]] the contents of that file. If you want more assurance that the contents are truly unrecoverable, consider using [[shred]].

===Related Commands===
* [[shred]]
* [[mv]]
* [[mkdir]]

Man

2004-03-09T21:36:45Z

Evilmrhenry: added example

man, short for "[[manual pages]]". The Unix [[Documentation]].

Often refered to when someone interjects [[RTFM]]!! to a new user who asks a question that could easily have been answered had he/she read the [[man page]].

The standard way to use the man pages is to enter 'man command'. 'man ls', for example, will show a large amount of information regarding the [[ls]] command.

Lynx

2004-03-09T21:34:02Z

Evilmrhenry: added commands and examples

Lynx is the classic text based web browsing program. You run it right from the [[CLI]] -- no X Window System required. Also check out [[Links]] if you are interested in this type of application.

Every system should have lynx installed on it, simply so you can browse and get at web pages when you are ssh'd in. Not typically for daily use, though it is quite useful when trying to discover why [[X]] is not working. The main commands are up and down (arrow keys) to move through a page, left and right to follow links, 'g' to go to an arbitrary webpage, and 'q' to quit.

Examples:
* lynx
** starts up Lynx with the default home page.
* lynx file.html
** opens file.html in Lynx.

User:Evilmrhenry

2004-03-07T19:39:36Z

Evilmrhenry:

[[Wiki_markup]]

LyX

2004-03-07T19:35:29Z

Evilmrhenry:

LyX is a graphical frontend to [[LaTeX]], enabling people to use the power of LaTeX while not knowing the actual commands. Although more difficult to learn than most word-proccessors, (reading the help files is recommended) it is simpler than the raw LaTeX files, and can produce very well formatted output. It has versions for Windows, Linux, and MacOS X.

Offical website: http://www.lyx.org/

LyX

2004-03-07T19:35:06Z

Evilmrhenry:

LyX is a graphical frontend to LaTex, enabling people to use the power of LaTeX while not knowing the actual commands. Although more difficult to learn than most word-proccessors, (reading the help files is recommended) it is simpler than the raw LaTeX files, and can produce very well formatted output. It has versions for Windows, Linux, and MacOS X.

Offical website: http://www.lyx.org/

Applications

2004-03-07T19:23:39Z

Evilmrhenry: added LyX

Use this space to collect notes and information on common Linux software!

Do:

* Provide basic descriptive and historical information about the application.
* Add notes or in-depth commentary on usage/common problems/tips.
* Include a concise list of important and distinctive features that will help a potential user decide whether a particular application will meet his or her needs.
* Critically process information you include.
* Link to official project pages and notable community resources.

Don't:

* Hesitate to add what you know, especially to a stub; any information is better than no or incorrect information.
* Simply duplicate the reference manual or uncritically include the project "About" page.
* Clutter the pages with platitudes, personal experience, opinion, or preference.
* Try and list every application in the world. Generally stick to those that are popular or distinctive, and stable or actively maintained/developed.

----
* '''[[3D modeling]]''' - [[Blender]], [[PovRay]]

* '''[[Audio Editor]]''' - [[Audacity]], [[Ardour]]

* '''[[Backup]]''' - [[rdiff-backup]], [[rsync]]

* '''[[CD Burning]]''' - [[K3b]], [[Xcdroast]], [[cdrecord]], [[cdrdao]]

* '''[[Compiler]]''' - [[GCC]], [[Mono]], [[Intel Compiler|Intel C/C++ Fortran]], [[PGI]], [[Pathscale]], [[IBM XLF,VAC]]

* '''[[Database]]''' - [[PostgreSQL]], [[MySQL]], [[Oracle]], [[DB2]], [[FireBirdSQL]]

* '''[[Database Tools]]''' - [[DBVisualizer]], [[DataDino]], [[PGAdmin]], [[PHPMyAdmin]]

* '''[[Desktop Environment]]''' - [[KDE]], [[Gnome]], [[XFce]]

* '''[[Email Client]]''' - [[Evolution]], [[Thunderbird]], [[Kmail]], [[Sylpheed]], [[Sylpheed-claws]], [[mutt]]

* '''[[Emulation]]''' - [[CrossOver]], [[DOSEMU]], [[Dosbox]], [[VMware]], [[Wine]], [[WineX]]

* '''[[File Managers]]''' - [[Midnight Commander]], [[Konqueror]], [[Gentoo File Manager]], [[emelFM]], [[Nautilus]]


* '''[[Image browser]]''' - [[imgSeek]], [[KimDaBa]], [[Gthumb]], [[pixieplus]], [[GQview]]

* '''[[Image manipulation]]''' - [[Gimp]], [[XV]], [[ImageMagick]], [[Sodipodi]], [[Inkscape]], [[Scribus]]

* '''[[Instant Messaging]]''' - [[Gaim]], [[Kopete]], [[Bitlbee]], [[Centericq]]

* '''[[Integrated Development Environment and Web Design]]''' - [[Quanta Plus]], [[KDevelop]], [[Bluefish]], [[Anjuta]]

* '''[[Internet Relay Chat]]''' - [[X-Chat]], [[BitchX]], [[Irssi]], [[ircII]]

* '''[[Music player]]''' - [[XMMS]], [[RhythmBox]]

* '''[[Office Suite]]''' - [[OpenOffice]], [[StarOffice]], [[KOffice]]

* '''[[PVR]]''' - [[MythTV]]

* '''[[Scientific Applications]]''' - [[BioInformatics]], [[Phy/Chem]], [[Molecular Dynamics]]

* '''[[Spreadsheet]]''' - [[Gnumeric]], [[KSpread]]

* '''[[System Statistics]]''' - [[GKrellm2]], [[Dockapps]]

* '''[[Terminal Emulator]]''' - [[aterm]], [[Eterm]], [[rxvt]], [[xterm]], [[wterm]], [[root-tail]], [[pterm]]

* '''[[Editor|Text Editor]]''' - [[Emacs]], [[Vi]] and [[Vim]], [[Joe]], [[Nano]], [[Gedit]], [[Bluefish]], [[Kwrite]], [[Kate]], [[NEdit]]

* '''[[Text Processing]]''' - [[TeX]], [[LaTeX]], [[teTeX]], [[LyX]]

* '''[[Video Capture]]''' - [[Xvidcap]]

* '''[[Video Editor]]''' - [[Cinelerra]], [[Kino]], [[Transcode]], [[DVD::Rip]]

* '''[[Video player]]''' - [[Xine]], [[Totem]], [[MPlayer]], [[vlc]]

* '''[[Web browser]]''' - [[Mozilla]], [[Firefox]], [[Opera]], [[Konqueror]], [[Epiphany]], [[Galeon]]

* '''[[Window Manager]]''' - [[Fluxbox]], [[Blackbox]], [[Window Maker]], [[Sawfish]], [[Enlightenment]], [[Metacity]], [[IceWM]], [[Ion]], [[Openbox]], [[Afterstep]], [[FVWM]]

* '''[[Word Processor]]''' - [[AbiWord]], [[KWord]]

* '''[[X Window System]]'''
**[[General Tips]]
**[[Programming]] 
**[[Configuring]] 

----
* '''[[Useful Sites]]'''

Applications

2004-03-06T21:53:11Z

Evilmrhenry: 3D modeling

Use this space to collect notes and information on common Linux software!

Do:

* Provide basic descriptive and historical information about the application.
* Add notes or in-depth commentary on usage/common problems/tips.
* Include a concise list of important and distinctive features that will help a potential user decide whether a particular application will meet his or her needs.
* Critically process information you include.
* Link to official project pages and notable community resources.

Don't:

* Hesitate to add what you know, especially to a stub; any information is better than no or incorrect information.
* Simply duplicate the reference manual or uncritically include the project "About" page.
* Clutter the pages with platitudes, personal experience, opinion, or preference.
* Try and list every application in the world. Generally stick to those that are popular or distinctive, and stable or actively maintained/developed.

----
* '''[[Desktop Environment]]''' - [[KDE]], [[Gnome]], [[XFce]]

* '''[[Window Manager]]''' - [[Fluxbox]], [[Blackbox]], [[Window Maker]], [[Sawfish]], [[Enlightenment]], [[Metacity]], [[IceWM]], [[Ion]], [[Openbox]], [[Afterstep]], [[FVWM]]

* '''[[X Window System]]''' - [[General Tips]], [[Programming]], [[Configuring]]

* '''[[Terminal Emulator]]''' - [[aterm]], [[Eterm]], [[rxvt]], [[xterm]], [[wterm]], [[root-tail]]

* '''[[Office Suite]]''' - [[OpenOffice]], [[StarOffice]], [[KOffice]]

* '''[[Word Processor]]''' - [[AbiWord]]

* '''[[Spreadsheet]]''' - [[Gnumeric]]

* '''[[Text Editor]]''' - [[Emacs]], [[Vi]] and [[Vim]], [[Joe]], [[Nano]], [[Gedit]], [[Bluefish]], [[Kwrite]], [[Kate]]

* '''[[Web browser]]''' - [[Mozilla]], [[Firefox]], [[Opera]], [[Konqueror]], [[Epiphany]], [[Galeon]]

* '''[[Email Client]]''' - [[Evolution]], [[Thunderbird]], [[Kmail]], [[Sylpheed]], [[Sylpheed-claws]], [[mutt]]

* '''[[Instant Messaging]]''' - [[Gaim]], [[Kopete]], [[Bitlbee]], [[Centericq]]

* '''[[Integrated Development Environment and Web Design]]''' - [[Quanta Plus]], [[KDevelop]], [[Bluefish]], [[Anjuta]]

* '''[[Internet Relay Chat]]''' - [[X-Chat]], [[BitchX]], [[Irssi]], [[ircII]]

* '''[[Video player]]''' - [[Xine]], [[Totem]], [[MPlayer]]

* '''[[Music player]]''' - [[XMMS]], [[RhythmBox]]

* '''[[Audio Editor]]''' - [[Audacity]]

* '''[[Video Editor]]''' - [[Cinelerra]], [[Kino]], [[Transcode]], [[DVD::Rip]]

* '''[[3D modeling]]''' - [[Blender]], [[PovRay]]

* '''[[Video Capture]]''' - [[Xvidcap]]

* '''[[Image manipulation]]''' - [[Gimp]], [[XV]], [[ImageMagick]], [[Sodipodi]], [[Inkscape]], [[Scribus]]

* '''[[Image browser]]''' - [[imgSeek]], [[KimDaBa]], [[Gthumb]], [[pixieplus]], [[GQview]]

* '''[[Emulation]]''' - [[CrossOver]], [[DOSEMU]], [[Dosbox]], [[VMware]], [[Wine]], [[WineX]]

* '''[[Compiler]]''' - [[GCC]], [[Mono]], [[Intel Compiler|Intel C/C++ Fortran]], [[PGI]], [[Pathscale]], [[IBM XLF,VAC]]

* '''[[Database]]''' - [[PostgreSQL]], [[MySQL]], [[Oracle]], [[DB2]], [[FireBirdSQL]]

* '''[[Database Tools]]''' - [[DBVisualizer]], [[DataDino]], [[PGAdmin]], [[PHPMyAdmin]]

* '''[[File Managers]]''' - [[Midnight Commander]], [[Konqueror]], [[Gentoo File Manager]], [[emelFM]], [[Nautilus]]

* '''[[System Statistics]]''' - [[GKrellm2]], [[Dockapps]]

* '''[[CD Burning]]''' - [[K3b]], [[Xcdroast]], [[cdrecord]], [[cdrdao]]

* '''[[Backup]]''' - [[rdiff-backup]]

* '''[[Scientific Applications]]''' - [[BioInformatics]], [[Phy/Chem]], [[Molecular Dynamics]]
----
* '''[[Useful Sites]]'''

Blender

2004-03-06T21:47:21Z

Evilmrhenry: belder->blender

'''Blender''' is a 3D modeling application available for Linux, Windows, and Macintosh. It is a powerful, professional 3D environment, but it has a steep learning curve, and many sometimes obscure shortcut keys. It currently supports animation rendering, radiosity, particle systems, and OpenGL Realtime animation for some (but not all) platforms/OSs.

'''External Links:'''

[http://www.blender3d.org Blender3d.org]

{{msg:stub}}

Dosbox

2004-03-06T21:39:31Z

Evilmrhenry: link to compatability database

Dosbox is a PC emulator with builtin DOS intended for running DOS Games primarily. The latest version 0.61 has already support for most dos games. Dosbox has extensive emulation for different kinds of hardware, such as GUS, Vesa, IPX networking / modem connections over TCP. Dosbox is licensed under GPL.

External link

*[http://dosbox.sourceforge.net/ Dosbox homepage]
*[http://dosbox.sourceforge.net/comp_list.php Compatability database]

Man page

2004-03-06T21:29:55Z

Evilmrhenry:

[[Unix]] [[command]]: view documentation for a given [[command]]. Usually in the format of <code>man command</code>

The man page usually contains information about proper syntax and options, though the contents and quality vary between applications.

See also [[man]], and read the man page: [[man man]]

Grep

2004-03-06T21:25:30Z

Evilmrhenry: added examples

Powerful utility that prints a line matching a given [[pattern]]. Supports [[regexp]].

See also [[egrep]] and [[fgrep]]

Examples:
* grep Something *
** Search all files in the current directory for the word 'Something'.
* grep -i something example.txt
** Search example.txt for all occurances of the word 'something', case-insensitive.
* grep -r something exam*
** search all files that start with 'exam' (ie: example.txt, exam4.txt) both in the current directory, and all subdirectories, for the word 'something'.

Uncompressing files

2004-03-06T21:13:26Z

Evilmrhenry: added explaination for tar

Uncompressing Files

*[[bunzip2]] (.bz2)- Decompresses the specified filename
Example# bunzip2 <filename.bz2>

*[[gunzip]] (.gz)- This utility can decompress files created with the following utilities: [[compress]], [[gzip]] and [[zip]]
Example# gunzip <filename.gz>

*[[unarj]] (.arj)- Decompresses or lists the content of the specified ARJ archive.
Example# ?

*[[uncompress]]- Decompresses the [[compress]] compressed file.
Example# uncompress -d <filename>

*[[unzip]] (.zip)- Decompresses and extracts files created by the Linux [[zip]] utility, PKZIP(MS-DOS) or WinZip(Microsoft Windows).
Example# unzip <filename.zip>

*[[tar]] (.tar) - This command is what is typically used to compress and decompress files in linux.
Example# tar -xvf <filename.tar>
Example# tar -xvzf <filename.tar.gz>
Example# tar -xvjf <filename.tar.bz2>
(x to extract a file, v to show what it's doing, z to run the file through [[gunzip]] first, j to run the file through [[bunzip2]] first, and f to specify the filename.)

*[[unace]] (.ace)- Decompresses ace files
Example# unace x <filename.ace>

*[[unrar]] (.rar)- Decompresses rar files
Example# unrar x <filename.rar>

WineX

2004-03-06T21:02:27Z

Evilmrhenry: link to Gaming via Wine or WineX

WineX is a commercial version of [[wine]] that is geared twoards games. It features a very large database of games, and forums. It comes with excellent support for paying customers, and good support for non-game applications.

It is produced by [http://www.transgaming.com/ Transgaming Technologies] and forked from wine years ago. It currently has a different license which makes porting code between WineX and wine very hard.

Transgaming dose provide support and binary releases to paying customers. Otherwise as with wine what you get is the current CVS.

See the [[wine]] page for further information, or [[Gaming via Wine or WineX]] for information on playing games under WineX.

PySol

2004-03-06T20:47:03Z

Evilmrhenry:

PySol is a Python-based solitare game. It currently includes a little over 200 varieties of solitare, and has versions for Windows, Linux, and Macintosh. The website is at http://www.oberhumer.com/opensource/pysol/

Gaming

2004-03-06T16:11:46Z

Evilmrhenry:

The following is a list of articles related to playing games under Linux. This is a small list; more articles will follow.

* [[First person shooters]]
** [[America's Army]]
** [[Heavy Metal: F.A.K.K.2]]
** [[Parsec]]
** [[Postal Plus]]
** [[Quake 3 Arena]]
** [[Return to Castle Wolfenstein]]
** [[Rune]]
** [[Savage]]
** [[Soldier of Fortune]]
** [[Tribes 2]]
** [[Unreal Tournament]]
** [[Wolfenstein: Enemy Territory]]

* [[Emulators]]
** [[Daphne]]
** [[DarcNES]]
** [[Dosbox|DOSBox]]
** [[ePSXe]]
** [[FakeNES]]
** [[FCE Ultra]]
** [[Generator]]
** [[Gens]]
** [[gngb]]
** [[Handy]] - Atari Lynx
** [[Hatari]] - Atari ST
** [[InfoNES]]
** [[MAME]]
** [[Mupen64]]
** [[NEStra]]
** [[PCSX]]
** [[SNES9X]]
** [[Stella]]
** [[ZSNES]]

* [[Role playing games]]
** [[Crossfire]]
** [[Daimonin]]
** [[FreedroidRPG]]
** [[Neverwinter Nights]]
** [[Roguelikes]]

* Racing
** [[GLTron]]
** [[Tux Racer]]
** [[Tux Kart]]

* Arcade
** [[Chromium]]
** [[Crack Attack]]
** [[Maelstrom]]
** [[XPuyopuyo]]
** [[JumpnBump]]
** [[LiquidWar]]
** [[XScorch]]

* Simulation
** [[Simcity 3000]]
** [[Lincity]]
** [[FreeCiv]]
** [[Alpha Centauri]]

* Other
** [[Persistent online worlds]]
** [[BZFlag]]
** [[Gaming via Wine or WineX]]
** [[Half-Life Server]]
** [[Freedroid]]
** [[Nighthawk]]
** [[Simutrans]]
** [[Dope Wars]]
** [[PySol]]
** [[XQF]] game server browser

Roguelikes

2004-03-06T16:00:15Z

Evilmrhenry: die-hard players don't scorn tile people

'''Roguelikes''' refers to a genre of [[Gaming|games]] which are similar to the classic computer game '''Rogue'''. These [[role playing games]] are usually formed on a fantasy or sci-fi backdrop, and present the player with a randomly generated dungeon. The dungeon in these games is furthermore represented as an [[ASCII]]-based map, typically with an '''@''' representing the player, '''#''' or equivalent characters for walls, '''^''' representing traps, and various colored letters representing different monsters. Some roguelikes have graphical interfaces available, although die-hard players prefer the [[ASCII]] symbols.

== List of roguelikes ==

The following roguelikes are available for Linux-based systems.
* [[ADoM]] (Ancient Domains of Mystery)
* [[Angband]] (with approximately 50 variants)
** [[ToME]]
* [[Fargoal]]
* [[IVAN]]
* [[Moria]]
* [[Nethack]]
** [[Slash'EM]]

== External links ==
* [http://en.wikipedia.org/wiki/Roguelike Roguelike] (Wikipedia article)

Talk:Gaming via WINE or WINEX

2004-03-06T08:59:36Z

Evilmrhenry: moved to "Talk:Gaming_via_Wine_or_WineX"

#REDIRECT [[Talk:Gaming_via_Wine_or_WineX]]

Gaming via WINE or WINEX

2004-03-06T08:59:36Z

Evilmrhenry: moved to "Gaming_via_Wine_or_WineX"

#REDIRECT [[Gaming_via_Wine_or_WineX]]

ToME

2004-03-06T08:56:39Z

Evilmrhenry:

ToME stands for Troubles of Middle Earth, and is one of the more popular [[Angband]] variants. Known as PernAngband in the past, the name and theme were changed due to copyright issues. Currently, ToME strives to closely follow the Middle Earth world.

Features:
* World map based on Middle Earth.
* Numerous classes and races.
* Built-in module support.
* Active development.

The website is http://t-o-m-e.net/

Gaming

2004-03-06T02:49:36Z

Evilmrhenry: WinexX to WineX

The following is a list of articles related to playing games under Linux. This is a small list; more articles will follow.

* [[First person shooters]]
** [[Unreal Tournament]]
** [[Quake 3 Arena]]
** [[Return to Castle Wolfenstein (ET)]]
** [[Half-Life Server]]
** [[America's Army]]
* [[Emulators]]
** [[ZSNES]]
** [[SNES9X]]
** [[MAME]]
** [[DarcNES]]
** [[ePSXe]]
** [[InfoNES]]
** [[FakeNES]]
** [[FCE Ultra]]
** [[PCSX]]
** [[Generator]]

* [[Role playing games]]
** [[FreedroidRPG]]
** [[Roguelikes]]
* Other
** [[Persistent online worlds]]
** [[BZFlag]]
** [[Gaming via Wine or WineX]]
** [[Tux Racer]]
** [[Freedroid]]
** [[Nighthawk]]

Gaming

2004-03-06T02:44:35Z

Evilmrhenry: fixed WINE link

The following is a list of articles related to playing games under Linux. This is a small list; more articles will follow.

* [[First Person Shooters]]
** [[Unreal Tournament]]
** [[Quake 3 Arena]]
** [[Return to Castle Wolfenstein (ET)]]
** [[Half-Life Server]]
** [[America's Army]]
* [[Emulators]]
** [[ZSNES]]
** [[SNES9X]]
** [[MAME]]
** [[DarcNES]]
** [[ePSXe]]
** [[InfoNES]]
** [[FakeNES]]
** [[FCE Ultra]]
** [[PCSX]]
** [[Generator]]

* [[Role Playing Games]]
** [[FreedroidRPG]]
** [[Roguelikes]]
* Other
** [[Persistent Online Worlds]]
** [[BZFlag]]
** [[Gaming via WINE or WINEX | Gaming via WINE or WineX]]
** [[Tux Racer]]
** [[Freedroid]]
** [[Nighthawk]]

Gaming

2004-03-06T02:35:11Z

Evilmrhenry:

Gaming

* '''[[First Person Shooters]]'''
* [[Unreal Tournament]]
* [[Quake 3 Arena]]
* [[Return to Castle Wolfenstein (ET)]]
* [[Half-Life Server]]
* [[America's Army]]

* '''[[Emulators]]'''
* [[ZSNES]]
* [[MAME]]

* '''[[Role Playing Games]]'''
* [[FreedroidRPG]]
* [[Roguelikes]]

* '''Other'''
* [[Persistent Online Worlds]]
* [[BZFlag]]
* [[Gaming via WINE or WineX]]

More to come...

Gaming via Wine or WineX

2004-03-06T01:37:34Z

Evilmrhenry:

Many Windows-games (and applications) can be run in GNU/Linux. This is normally (since there are other Windows [[emulator]]s as well) done with [[WINE]]/[[WINEX]]. WINE and WINEX are projects that, in a nutshell, try to replace the Windows base so that your Windows apps and games work properly on GNU/Linux.

While WINE is free to use, [http://www.transgaming.com Transgaming] (the company that develops [[WINEX]]) does charge a monthly fee ($5 per month, 3 month minimum) for easy-to-install packages and updates. It is possible, though, to use WINEX for free, but the process involves downloading and compiling older versions. The advantage is that WINEX is more thoroughly tested for games, so you have a much greater chance to play. It is also focused on getting the Direct X layer of Windows working on Linux.

==WINE==

Since there isn't any information here yet, I suggest you go to [http://www.winehq.com WINE's homepage], and look at the [http://www.winehq.com/site/supported_applications list of supported applications]. There are normally tips and hints on how to make a certain app/game work under GNU/Linux with WINE. Another site to watch is [http://frankscorner.org Frank's Corner]. Frank's Corner provides easy tutorials for the installation and use of common Windows games and apps on Linux.

Since WINE is still in Alpha state (unstable) you should take care to follow the exact instructions you find on how to install each game. Note also that installing new versions (builds) of WINE can make functioning games to stop working. If it ain't broke, don't fix it!

You can find WINE prepackaged and ready to install in most major distributions; if you want newer (or perhaps older) builds, you'll have to [http://www.winehq.org/site/download download] them from the website.

==WINEX==

Transgaming maintains a [http://www.transgaming.com/searchgame.php database] of the games currently supported, and their actual usability on Linux, varying between 0 (Doesn't install nor work) and 5 (as in Windows). Remember, when you search, to use full names instead of game acronyms (Diablo 2 instead of D2 for instance). Results will link you to pages that have a compatibility rating, screen shots, and a message board for the game you searched for.

The message board is important, as the compatibility rating is not always accurate. Reading through it can provide a better idea as to the actual compatability.

It's also important to frequently check the TransGaming website (listed above) for WineX as new versions come out regularly that solve older problems. (for example, Steam now works in 3.3).

==Currently supported games==

Games that have been reported to work on [[WINE]]/[[WINEX]] include Starcraft, Warcraft III - Reign of Chaos and Warcraft III - The Frozen Throne, GTA 3 - Vice City, Jedi Knight 2 - Jedi Outcast, Half Life and its many modifications, including Counter-Strike, and many more. Note that games coming from [http://www.idsoftware.com ID Software], such as Quake 3 Arena, Return to Castle Wolfenstein and Enemy Territory, run natively on Linux (i.e. without the need for WINE).

==System Requirements==

For 3D games to work on Linux, you must have a supported graphic card with 3D capabilities. At the moment, these include nVIDIA cards (very good drivers) and ATI cards (apparently not so good).