LQWiki - User contributions [en]

LQWiki:Answering Questions Guide

2007-05-24T12:43:45Z

Titanium geek: /* Answering Questions Guidelines */

== Answering Questions Guidelines ==

As possibly the world's biggest base of linux help, we as members need to work on Answering Questions.

Many [[newbie]]s find it difficult to ask questions, and when they get a bad answer, it could scare them off [[linux]] for good, and gives them a bad impression of the LQ Community.

* '''Always be courteous. '''
Don't flame a newbie for a stupid question, they could be a valuable contributor to the community in the future.

* '''Answer only if you are going to help.'''
(Bad: I have no idea about it, but I think your name is totaly cool. Worse: Stupid Newbie!) Answer the question if you know the answer. Just replying to get rid of a "zero response thread" is not a good idea.

* '''Answer carefully'''
Make sure that you are giving the right answer and explain it carefully, in an easy to understand way.

* '''Be sensitive of newbies. '''
This doesn't mean giving specific steps each time you post an answer (a task many dislike) - but adding "if you need any extra help, just ask" to the end of the post then the newbie will be less likely to freak out. Another helpful thing to do is to link to past threads with similar solutions.

* '''Post links where helpful.'''
Any howto's, tutorials, etc. that might be useful for the asker, and saves you the trouble of typing it all out again.

* '''Read and Re Read the question'''
Sometimes you find the problem hidden in the asker's posts.

* '''Be sensitive of ESL (english as a second language) users'''
The [[internet]] is an international place. Though the [[forum]]'s language is english, be ready to explain things carefully, in an easy to understand way.

* '''Remember you were once a newbie'''

8)

Remember our goal is to encourage and guide people in using linux, not to stop people from using linux.

Slocate

2007-03-15T09:30:31Z

Titanium geek: slocate

'''Slocate'''

[[Slackware]] version of [[bash]] command [[locate]].

About LinuxQuestions

2006-11-23T02:35:49Z

Titanium geek:

[[LQWiki:Answering_Questions_Guide|Answering Questions Guide]]

[[LQWiki:Common_Forum_Responses|Common Forum Responses]]

[[LQRadio]]

[[LQWiki:LQ_Tips_and_Tricks|LQ Tips and Tricks]]

[[LQWiki:What_is_LQ|What is LQ?]]

'''Vocabulary'''

[[Tag]]

[[forum thread]]

[[post]]

[[moderator]]

About LinuxQuestions

2006-11-23T02:33:49Z

Titanium geek:

LQWiki:Answering Questions Guide

2006-05-05T07:49:11Z

Titanium geek: /* Answering Questions Guidelines */

== Answering Questions Guidelines ==

As possibly the world's biggest base of linux help, we as members need to work on Answering Questions.

Many [[newbie]]s find it difficult to ask questions, and when they get a bad answer, it often scares them off [[linux]] for good.

* '''Always be courteous. '''
Don't flame a newbie for a stupid question, they could be a valuable contributor to the community in the future.

* '''Answer only if you are going to help.'''
(Bad: I have no idea about it, but I think your name is totaly cool.) Answer the question if you know the answer. Just replying to get rid of a "zero response thread" is not a good idea.

* '''Answer carefully'''
Make sure that you are giving the right answer and explain it carefully, in an easy to understand way.

* '''Be sensitive of newbies. '''
This doesn't mean giving specific steps each time you post an answer (a task many dislike) - but adding "if you need any extra help, just ask" to the end of the post then the newbie will be less likely to freak out.

* '''Read and Re Read the question'''
Sometimes you find the problem hidden in the asker's posts.

* '''Post links where helpful.'''
Any howto's, tutorials, etc. that might be useful for the asker, and saves you the trouble of typing it all out again.

* '''Be sensitive of ESL (english as a second language) users'''
The [[internet]] is an international place. Though the [[forum]]'s language is english, be ready to explain things carefully, in an easy to understand way.

* '''Remember you were once a newbie'''

8)

Remember our goal is to encourage and guide people in using linux, not to stop people from using linux.

Backwards compatible

2006-02-10T04:29:14Z

Titanium geek:

===Backwards Compatible===

A term to describe software (adjective.)

Usually to describe document handling programs.

Either the ability to open documents from older/earlier versions of the program or the ability of older/earlier versions to open documents created in the new version.

Mirror

2005-10-27T15:16:16Z

Titanium geek: /* Mirror */

== Mirror ==

A place you can download a [[linux]] [[distribution]] [[iso]] or [[software]] from.

The term came from the real world object that is often found in bathrooms, a piece of shiny metal/glass that is used to reflect light and thus images.

In the virtual world, when a [[distro]] or piece of [[software]] is released, it is hosted on a [[server]]- the one that the project maintains. However, especially if the project is popular, the requests to [[download]] can be very taxing on the [[server]]'s resources. So, other people with [[server]]s ''mirror'' (host a copy of) the downloadable file.

It is reccomended that you pick a mirror that is close to you geographically- theoretically this increases speed because there is less cable to travel through.

Linux installation

2005-10-27T15:09:08Z

Titanium geek: /* How to get a Distribution? */

As the method of '''installation of Linux''' varies so much from distribution to distribution, you are best advised to look at the documentation for your chosen distribution.

Some [[Live CD distributions]], such as [[Knoppix]] or [[Morphix]] allow you to test-drive before you install. They also have a very good automatic detection and configuration system and are useful diagnostic tools to help you gather info about your system before installing any chosen distro.

A majority of distributions make a good attempt at autodetecting the target system's hardware, though [[WiFi]] device auto-detection is still more or less non-existent.

A [[Source_distributions|source based distribution]] such as [[Gentoo]] encourages its users to come to grips with Linux system management by making them configure, compile and set up everything from scratch. It's really worth doing if you have the time to learn that way, and the learning method and quality of the documentation set it apart from most other distros.

==System requirements==
There are hardly default hardware requirements. It depends a lot on the used [[Distributions|distribution]] and how much you are willing to tweak it. Most Linux [[distributions]] are rather modest with their hardware requirements so running any of them on a modern computer will not pose any problems.

Of course if you require to run Linux on a pre Pentium machine you might get in trouble using the latest [[Mandrake]], [[Fedora]], etc. because they may not support every processor type and require a certain amount of system memory. On the other hand using the latest technology may confront you with a lack of drivers and propper support.

==Choosing a distribution==
''Always use the same [[distribution]] as the [[guru]] next door!'' This way you have somebody around to question and ask for help.

In general if you don't need special features or have exotic hardware requirements and little or no [[Linux]] knowledge you are on the safe side using one of the major [[distributions]], i.e. [[Fedora]], [[Mandrake]], [[Suse]], [[Red_Hat]]. All them are equipped with a graphical installation, preconfigured desktop and graphical configuration tools.

If you just want to try [[Linux]] your best choice is one of the [[Live_CD_distributions | Live CD distributions]] which run from one CD and don't need to be installed at all.

Special hardware requirements and/or curiosity may lead you to other [[distributions]] like [[VectorLinux]] for sparse hardware which is based on [[Slackware]].

Probably every [[distribution]] would be worth mentioning but believe me as said before: ''The best [[distribution]] is the one your personal [[guru]] has!''

For more information about how to choose a distribution, see [[Choosing a Linux distribution]].

===Distribution specific guides===
A comprehensive list of [[Distributions]].

===How to get a Distribution?===
* Buy a boxed [[Distributions|distribution]] online or in a store. This way you get user guides specific to your distribution and support from the distributor. If you buy an official copy some of the money will help maintain the distribution.
* Download the [[ISO]] files and burn your own CD set. The ISO files can be found at the main [[Distributions|distribution]] site or on countless [[mirror]]s. If the option exists, downloading from a distributed [[P2P]] network such as [[BitTorrent]] is preferable. Using p2p the download is likely to be faster, especially at busy times, and the cost to the distributor is far less than over [[ftp]].
* Download only a small installation CD or floppy image and install your system directly per [[FTP Install]] or [[HTTP Install]]. Only the selected software is downloaded which is in most cases faster than downloading the whole CD set. But not every [[Distributions|distribution]] supports this installation type.
* Sometimes magazines add partial or even complete [[distributions]], occasionally before they are made available online.

===How to solve problems with your distribution===
* Do it yourself, using [[man]] pages, local documents, the web
* Get help. See [[Linux support options]]

===How to keep a distribution up to date===
* Use a package manager like [[apt-get]], [[Synaptic]], [[up2date]], [[Urpmi|urpmi]] ... to download, install, and upgrade applications, and to find applications that will meet your needs. For a cookbook on how to use Synaptic, see [[Fedora, Synaptic Package Manager, finding Repositories, listing RPMs, previously installed]].

==Configuring Linux==
* [[Networking]]
* [[Security]]
* [[Hardware]]
* [[Booting]]
* [[Finding configuration parameters]]

==What next? How to make the most of Linux.==
* List of Linux [[Applications]]
* List of Linux [[Commands]]
* [[Common Tasks]]
* [[Documentation]]
* [[Gaming]]

==Installation Guides==
(guides to install distros at linuxquestions.org)
*[[ipodlinux:documentation|ipodlinux]]
*[[installing_woody|Debian woody on a 100MHz Pentium]]
*[[Installing Slackware and Gentoo]]

==External links==
(links to guides etc.)
* [http://iso.linuxquestions.org/ LQ ISO] - Find and rate fast Linux download mirrors
* [http://www.linuxiso.org LinuxISO.org] - Another great ISO download site.

About LinuxQuestions

2005-10-04T12:30:42Z

Titanium geek:

[[Answering Questions Guide]]

[[LQWiki:Common Forum Responses]]

[[LQRadio]]

[[LQ Tips and Tricks]]

[[What is LQ?]]

Compilation from Source by Hand

2005-10-01T16:36:07Z

Titanium geek: /* What if I get errors? */

== Compilatation From Source ==
you can do it yourself! using your own fingers!

====Formatting used in this document ====

boldface means commands you type at the [[Command line]].
* example: '''su'''

italics are explanations of what you are supposed to do:
* example: Password: ''type your root password''
or related topics to look up
* example: ''check out these links to learn more''

words in between < > characters are keys you press
* example: <enter> you don't type <enter> you hit the enter key (return key)

at the end of a line of commands, you are expected to press enter.
* example: '''cd''' ''name of directory'' ''you are to press enter, do not only press enter when told to do so.''

----
====Let's Go!====

The topic that most people view with FEAR and TREPIDATION is compiling from source by yourself. The reason is the misconception that you must be a [[programmer]] to do so. Actually, compiling by hand is not as bad as it may seem.

first of all, you need your source. So, using [http://www.google.com google], [http://freshmeat.net freshmeat.net] etc, find your program and download it. The file extension should be tar.gz or tar.bz2 or similar.
* '' [[tar]] [[unzip]] [[download]] ''

find where you saved (downloaded) the file. If you have not already done so, now is the time to open your commandline/terminal/CLI. using the change directory command, go to the place where you saved your file. Let's assume that your user name is pengy and you saved the source to your home directory.

'''cd''' /home/pengy

use '''ls''' to see if it is there.
* '' [[directory]] [[cd]] [[ls]] [[CLI]] ''

allright, now you need to unzip and untar the source. this is very easily done-
* for tar.gz: '''tar -zxf''' ''the name of file''.tar.gz
* for tar.bz2: ''tar -jxf''' ''the name of file''.tar.bz2
* '' [[tar]] [[unzip]] ''

now, you need to change to the new directory. the name is usually the same as the tar (minus tar.gz obviously) a useful tool is tab completion-
'''cd''' ''first couple of letters'' <tab>
or just '''ls''' to see what it is.
'''cd''' ''name of directory''
* '' [[cd]] [[tab filename completion]] ''

look for a file named README or something similar- read this.
'''less''' README ''use the right name''
* ''[[less]] [[README]] ''

Now, you must run the configuration file.
'''./configure'''
if this gives you no errors, then
'''make'''
and finally and optionally (though it is a good idea) is as root,
'''su''' <enter> Password: ''type your root password''

'''make install'''
* ''[[configure script]] [[make]] [[su]] [[root]] ''

====What if I get errors?====
most likely you will need to install something else before you can compile the software- the configure and make are good for telling you what the problem is. You don't need to read what they output, just the last couple of lines to see if the compile/configure was succesful.

'''What if I DO have that installed?'''
there are a couple of things that you could check:
the [[path]]
do you have the latest versions of both? If you do, is this the problem? If you compiled the other yourself, did you '''make install'''?

====List of useful Links====
* [[Installing Software]]
* [[gcc]]
* [[configure script]]
* [[make]]
* [[su]]
* [[root]]
* [[unzip]]
* [[tar]]
* [[cd]]
* [[less]]
* [[ls]]

----
may the source be with you.
--[[User:Titanium geek|titanium_geek]] 11:54, Oct 1, 2005 (EDT)

Compilation from Source by Hand

2005-10-01T16:01:43Z

Titanium geek: /* Compilatation by Hand */

== Compilatation From Source ==
you can do it yourself! using your own fingers!

====Formatting used in this document ====

boldface means commands you type at the [[Command line]].
* example: '''su'''

italics are explanations of what you are supposed to do:
* example: Password: ''type your root password''
or related topics to look up
* example: ''check out these links to learn more''

words in between < > characters are keys you press
* example: <enter> you don't type <enter> you hit the enter key (return key)

at the end of a line of commands, you are expected to press enter.
* example: '''cd''' ''name of directory'' ''you are to press enter, do not only press enter when told to do so.''

----
====Let's Go!====

The topic that most people view with FEAR and TREPIDATION is compiling from source by yourself. The reason is the misconception that you must be a [[programmer]] to do so. Actually, compiling by hand is not as bad as it may seem.

first of all, you need your source. So, using [http://www.google.com google], [http://freshmeat.net freshmeat.net] etc, find your program and download it. The file extension should be tar.gz or tar.bz2 or similar.
* '' [[tar]] [[unzip]] [[download]] ''

find where you saved (downloaded) the file. If you have not already done so, now is the time to open your commandline/terminal/CLI. using the change directory command, go to the place where you saved your file. Let's assume that your user name is pengy and you saved the source to your home directory.

'''cd''' /home/pengy

use '''ls''' to see if it is there.
* '' [[directory]] [[cd]] [[ls]] [[CLI]] ''

allright, now you need to unzip and untar the source. this is very easily done-
* for tar.gz: '''tar -zxf''' ''the name of file''.tar.gz
* for tar.bz2: ''tar -jxf''' ''the name of file''.tar.bz2
* '' [[tar]] [[unzip]] ''

now, you need to change to the new directory. the name is usually the same as the tar (minus tar.gz obviously) a useful tool is tab completion-
'''cd''' ''first couple of letters'' <tab>
or just '''ls''' to see what it is.
'''cd''' ''name of directory''
* '' [[cd]] [[tab filename completion]] ''

look for a file named README or something similar- read this.
'''less''' README ''use the right name''
* ''[[less]] [[README]] ''

Now, you must run the configuration file.
'''./configure'''
if this gives you no errors, then
'''make'''
and finally and optionally (though it is a good idea) is as root,
'''su''' <enter> Password: ''type your root password''

'''make install'''
* ''[[configure script]] [[make]] [[su]] [[root]] ''

====What if I get errors?====
most likely you will need to install something else before you can compile the software- the configure and make are good for telling you what the problem is. You don't need to read what they output, just the last couple of lines to see if the compile/configure was succesful.

====List of useful Links====
* [[Installing Software]]
* [[gcc]]
* [[configure script]]
* [[make]]
* [[su]]
* [[root]]
* [[unzip]]
* [[tar]]
* [[cd]]
* [[less]]
* [[ls]]

----
may the source be with you.
--[[User:Titanium geek|titanium_geek]] 11:54, Oct 1, 2005 (EDT)

Compilation from Source by Hand

2005-10-01T15:57:47Z

Titanium geek: /* Compilation by Hand */

== Compilatation by Hand ==

====Formatting used in this document ====

boldface means commands you type at the [[Command line]].
* example: '''su'''

italics are explanations of what you are supposed to do:
* example: Password: ''type your root password''
or related topics to look up
* example: ''check out these links to learn more''

words in between < > characters are keys you press
* example: <enter> you don't type <enter> you hit the enter key (return key)

at the end of a line of commands, you are expected to press enter.
* example: '''cd''' ''name of directory'' ''you are to press enter, do not only press enter when told to do so.''

----
====Let's Go!====

The topic that most people view with FEAR and TREPIDATION is compiling from source by yourself. The reason is the misconception that you must be a [[programmer]] to do so. Actually, compiling by hand is not as bad as it may seem.

first of all, you need your source. So, using [http://www.google.com google], [http://freshmeat.net freshmeat.net] etc, find your program and download it. The file extension should be tar.gz or tar.bz2 or similar.
* '' [[tar]] [[unzip]] [[download]] ''

find where you saved (downloaded) the file. If you have not already done so, now is the time to open your commandline/terminal/CLI. using the change directory command, go to the place where you saved your file. Let's assume that your user name is pengy and you saved the source to your home directory.

'''cd''' /home/pengy

use '''ls''' to see if it is there.
* '' [[directory]] [[cd]] [[ls]] [[CLI]] ''

allright, now you need to unzip and untar the source. this is very easily done-
* for tar.gz: '''tar -zxf''' ''the name of file''.tar.gz
* for tar.bz2: ''tar -jxf''' ''the name of file''.tar.bz2
* '' [[tar]] [[unzip]] ''

now, you need to change to the new directory. the name is usually the same as the tar (minus tar.gz obviously) a useful tool is tab completion-
'''cd''' ''first couple of letters'' <tab>
or just '''ls''' to see what it is.
'''cd''' ''name of directory''
* '' [[cd]] [[tab filename completion]] ''

look for a file named README or something similar- read this.
'''less''' README ''use the right name''
* ''[[less]] [[README]] ''

Now, you must run the configuration file.
'''./configure'''
if this gives you no errors, then
'''make'''
and finally and optionally (though it is a good idea) is as root,
'''su''' <enter> Password: ''type your root password''

'''make install'''
* ''[[configure script]] [[make]] [[su]] [[root]] ''

====What if I get errors?====
most likely you will need to install something else before you can compile the software- the configure and make are good for telling you what the problem is. You don't need to read what they output, just the last couple of lines to see if the compile/configure was succesful.

====List of useful Links====
* [[Installing Software]]
* [[gcc]]
* [[configure script]]
* [[make]]
* [[su]]
* [[root]]
* [[unzip]]
* [[tar]]
* [[cd]]
* [[less]]
* [[ls]]

----
may the source be with you.
--[[User:Titanium geek|titanium_geek]] 11:54, Oct 1, 2005 (EDT)

Compilation from Source by Hand

2005-10-01T15:56:31Z

Titanium geek: /* List of useful Links */

== Compilatation by Hand ==

====Formatting used in this document ====

boldface means commands you type at the [[Command line]].
* example: '''su'''

italics are explanations of what you are supposed to do:
* example: Password: ''type your root password''
or related topics to look up
* example: ''check out these links to learn more''

words in between < > characters are keys you press
* example: <enter> you don't type <enter> you hit the enter key (return key)

at the end of a line of commands, you are expected to press enter.
* example: '''cd''' ''name of directory'' ''you are to press enter, do not only press enter when told to do so.''

----
====Let's Go!====

The topic that most people view with FEAR and TREPIDATION is compiling from source by yourself. The reason is the misconception that you must be a [[programmer]] to do so. Actually, compiling by hand is not as bad as it may seem.

first of all, you need your source. So, using [http://www.google.com google], [http://freshmeat.net freshmeat.net] etc, find your program and download it. The file extension should be tar.gz or tar.bz2 or similar.
* '' [[tar]] [[unzip]] [[download]] ''

find where you saved (downloaded) the file. If you have not already done so, now is the time to open your commandline/terminal/CLI. using the change directory command, go to the place where you saved your file. Let's assume that your user name is pengy and you saved the source to your home directory.

'''cd''' /home/pengy

use '''ls''' to see if it is there.
* '' [[directory]] [[cd]] [[ls]] [[CLI]] ''

allright, now you need to unzip and untar the source. this is very easily done-
* for tar.gz: '''tar -zxf''' ''the name of file''.tar.gz
* for tar.bz2: ''tar -jxf''' ''the name of file''.tar.bz2
* '' [[tar]] [[unzip]] ''

now, you need to change to the new directory. the name is usually the same as the tar (minus tar.gz obviously) a useful tool is tab completion-
'''cd''' ''first couple of letters'' <tab>
or just '''ls''' to see what it is.
'''cd''' ''name of directory''
* '' [[cd]] [[tab filename completion]] ''

look for a file named README or something similar- read this.
'''less''' README ''use the right name''
* ''[[less]] [[README]] ''

Now, you must run the configuration file.
'''./configure'''
if this gives you no errors, then
'''make'''
and finally and optionally (though it is a good idea) is as root,
'''su''' <enter> Password: ''type your root password''

'''make install''
* ''[[configure script]] [[make]] [[su]] [[root]] ''

====What if I get errors?====
most likely you will need to install something else before you can compile the software- the configure and make are good for telling you what the problem is. You don't need to read what they output, just the last couple of lines to see if the compile/configure was succesful.

====List of useful Links====
* [[Installing Software]]
* [[gcc]]
* [[configure script]]
* [[make]]
* [[su]]
* [[root]]
* [[unzip]]
* [[tar]]
* [[cd]]
* [[less]]
* [[ls]]

----
may the source be with you.
--[[User:Titanium geek|titanium_geek]] 11:54, Oct 1, 2005 (EDT)

Compilation from Source by Hand

2005-10-01T15:55:42Z

Titanium geek:

== Compilatation by Hand ==

====Formatting used in this document ====

boldface means commands you type at the [[Command line]].
* example: '''su'''

italics are explanations of what you are supposed to do:
* example: Password: ''type your root password''
or related topics to look up
* example: ''check out these links to learn more''

words in between < > characters are keys you press
* example: <enter> you don't type <enter> you hit the enter key (return key)

at the end of a line of commands, you are expected to press enter.
* example: '''cd''' ''name of directory'' ''you are to press enter, do not only press enter when told to do so.''

----
====Let's Go!====

The topic that most people view with FEAR and TREPIDATION is compiling from source by yourself. The reason is the misconception that you must be a [[programmer]] to do so. Actually, compiling by hand is not as bad as it may seem.

first of all, you need your source. So, using [http://www.google.com google], [http://freshmeat.net freshmeat.net] etc, find your program and download it. The file extension should be tar.gz or tar.bz2 or similar.
* '' [[tar]] [[unzip]] [[download]] ''

find where you saved (downloaded) the file. If you have not already done so, now is the time to open your commandline/terminal/CLI. using the change directory command, go to the place where you saved your file. Let's assume that your user name is pengy and you saved the source to your home directory.

'''cd''' /home/pengy

use '''ls''' to see if it is there.
* '' [[directory]] [[cd]] [[ls]] [[CLI]] ''

allright, now you need to unzip and untar the source. this is very easily done-
* for tar.gz: '''tar -zxf''' ''the name of file''.tar.gz
* for tar.bz2: ''tar -jxf''' ''the name of file''.tar.bz2
* '' [[tar]] [[unzip]] ''

now, you need to change to the new directory. the name is usually the same as the tar (minus tar.gz obviously) a useful tool is tab completion-
'''cd''' ''first couple of letters'' <tab>
or just '''ls''' to see what it is.
'''cd''' ''name of directory''
* '' [[cd]] [[tab filename completion]] ''

look for a file named README or something similar- read this.
'''less''' README ''use the right name''
* ''[[less]] [[README]] ''

Now, you must run the configuration file.
'''./configure'''
if this gives you no errors, then
'''make'''
and finally and optionally (though it is a good idea) is as root,
'''su''' <enter> Password: ''type your root password''

'''make install''
* ''[[configure script]] [[make]] [[su]] [[root]] ''

====What if I get errors?====
most likely you will need to install something else before you can compile the software- the configure and make are good for telling you what the problem is. You don't need to read what they output, just the last couple of lines to see if the compile/configure was succesful.

====List of useful Links====
* [[Installing Software]]
* [[Compiling from source]]
* [[gcc]]
* [[configure script]]
* [[make]]
* [[su]]
* [[root]]
* [[unzip]]
* [[tar]]
* [[cd]]
* [[less]]
* [[ls]]

----
may the source be with you.
--[[User:Titanium geek|titanium_geek]] 11:54, Oct 1, 2005 (EDT)

Compilation from Source by Hand

2005-10-01T15:54:28Z

Titanium geek:

== Compilatation by Hand ==

====Formatting used in this document ====

boldface means commands you type at the [[Command Line]].
* example: '''su'''

italics are explanations of what you are supposed to do:
* example: Password: ''type your root password''
or related topics to look up
* example: ''check out these links to learn more''

words in between < > characters are keys you press
* example: <enter> you don't type <enter> you hit the enter key (return key)

at the end of a line of commands, you are expected to press enter.
* example: '''cd''' ''name of directory'' ''you are to press enter, do not only press enter when told to do so.''

----
====Let's Go!====

The topic that most people view with FEAR and TREPIDATION is compiling from source by yourself. The reason is the misconception that you must be a [[programmer]] to do so. Actually, compiling by hand is not as bad as it may seem.

first of all, you need your source. So, using [http://www.google.com google], [http://freshmeat.net freshmeat.net] etc, find your program and download it. The file extension should be tar.gz or tar.bz2 or similar.
* '' [[tar]] [[unzip]] [[download]] ''

find where you saved (downloaded) the file. If you have not already done so, now is the time to open your commandline/terminal/CLI. using the change directory command, go to the place where you saved your file. Let's assume that your user name is pengy and you saved the source to your home directory.

'''cd''' /home/pengy

use '''ls''' to see if it is there.
* '' [[directory]] [[cd]] [[ls]] [[CLI]] ''

allright, now you need to unzip and untar the source. this is very easily done-
* for tar.gz: '''tar -zxf''' ''the name of file''.tar.gz
* for tar.bz2: ''tar -jxf''' ''the name of file''.tar.bz2
* '' [[tar]] [[unzip]] ''

now, you need to change to the new directory. the name is usually the same as the tar (minus tar.gz obviously) a useful tool is tab completion-
'''cd''' ''first couple of letters'' <tab>
or just '''ls''' to see what it is.
'''cd''' ''name of directory''
* '' [[cd]] [[tab filename completion]] ''

look for a file named README or something similar- read this.
'''less''' README ''use the right name''
* ''[[less]] [[README]] ''

Now, you must run the configuration file.
'''./configure'''
if this gives you no errors, then
'''make'''
and finally and optionally (though it is a good idea) is as root,
'''su''' <enter> Password: ''type your root password''

'''make install''
* ''[[configure script]] [[make]] [[su]] [[root]] ''

====What if I get errors?====
most likely you will need to install something else before you can compile the software- the configure and make are good for telling you what the problem is. You don't need to read what they output, just the last couple of lines to see if the compile/configure was succesful.

====List of useful Links====
* [[Installing Software]]
* [[Compiling from source]]
* [[gcc]]
* [[configure script]]
* [[make]]
* [[su]]
* [[root]]
* [[unzip]]
* [[tar]]
* [[cd]]
* [[less]]
* [[ls]]

----
may the source be with you.
--[[User:Titanium geek|titanium_geek]] 11:54, Oct 1, 2005 (EDT)

Compilation from Source by Hand

2005-10-01T15:52:01Z

Titanium geek:

== Compilatation by Hand ==

====Formatting used in this document ====

boldface means commands you type at the [[Command Line]].
* example: '''su'''

italics are explanations of what you are supposed to do:
* example: Password: ''type your root password''
or related topics to look up
* example: ''check out these links to learn more''

words in between < > characters are keys you press
* example: <enter> you don't type <enter> you hit the enter key (return key)

at the end of a line of commands, you are expected to press enter.
* example: '''cd''' ''name of directory'' ''you are to press enter, do not only press enter when told to do so.''

----
====Let's Go!====

The topic that most people view with FEAR and TREPIDATION is compiling from source by yourself. The reason is the misconception that you must be a [[programmer]] to do so. Actually, compiling by hand is not as bad as it may seem.

first of all, you need your source. So, using [http://www.google.com google], [http://freshmeat.net freshmeat.net] etc, find your program and download it. The file extension should be tar.gz or tar.bz2 or similar.
* '' [[tar]] [[unzip]] [[download]] ''

find where you saved (downloaded) the file. If you have not already done so, now is the time to open your commandline/terminal/CLI. using the change directory command, go to the place where you saved your file. Let's assume that your user name is pengy and you saved the source to your home directory.

'''cd''' /home/pengy

use '''ls''' to see if it is there.
* '' [[directory]] [[cd]] [[ls]] [[CLI]] ''

allright, now you need to unzip and untar the source. this is very easily done-
* for tar.gz: '''tar -zxf''' ''the name of file''.tar.gz
* for tar.bz2: ''tar -jxf''' ''the name of file''.tar.bz2
* '' [[tar]] [[unzip]] ''

now, you need to change to the new directory. the name is usually the same as the tar (minus tar.gz obviously) a useful tool is tab completion-
'''cd''' ''first couple of letters'' <tab>
or just '''ls''' to see what it is.
'''cd''' ''name of directory''
* '' [[cd]] [[tab filename completion]] ''

look for a file named README or something similar- read this.
'''less''' README ''use the right name''
* ''[[less]] [[README]] ''

Now, you must run the configuration file.
'''./configure'''
if this gives you no errors, then
'''make'''
and finally and optionally (though it is a good idea) is as root,
'''su''' <enter> Password: ''type your root password''

'''make install''
* ''[[configure]] [[make]] [[su]] [[root]] ''

====What if I get errors?====
most likely you will need to install something else before you can compile the software- the configure and make are good for telling you what the problem is. You don't need to read what they output, just the last couple of lines to see if the compile/configure was succesful.

====List of useful Links===
* [[Installing Software]]
* [[Compiling from source]]
* [[gcc]]
* [[configure]]
* [[make]]
* [[su]]
* [[root]]
* [[unzip]]
* [[tar]]
* [[cd]]
* [[less]]
* [[ls]]

----
may the source be with you.
--[[User:Titanium geek|titanium_geek]] 11:52, Oct 1, 2005 (EDT)

Compilation from Source by Hand

2005-10-01T15:34:55Z

Titanium geek:

== Compilatation by Hand ==

====Formatting used in this document ====

boldface means commands you type at the [[Command Line]].
* example: '''su'''

italics are explanations of what you are supposed to do:
* example: Password: ''type your root password''
or related topics to look up
* example: ''check out these links to learn more''

words in between < > characters are keys you press
* example: <enter> you don't type <enter> you hit the enter key (return key)

at the end of a line of commands, you are expected to press enter.
* example: '''cd''' ''name of directory'' ''you are to press enter, do not only press enter when told to do so.''

----

The topic that most people view with FEAR and TREPIDATION is compiling from source by yourself. The reason is the misconception that you must be a [[programmer]] to do so. Actually, compiling by hand is not as bad as it may seem.

first of all, you need your source. So, using [http://www.google.com google], [http://freshmeat.net freshmeat.net] etc, find your program and download it. The file extension should be tar.gz or tar.bz2 or similar.
* '' [[tar]] [[unzip]] [[download]] ''

find where you saved (downloaded) the file. If you have not already done so, now is the time to open your commandline/terminal/CLI. using the change directory command, go to the place where you saved your file. Let's assume that your user name is pengy and you saved the source to your home directory.

'''cd''' /home/pengy

use '''ls''' to see if it is there.
* '' [[directory]] [[cd]] [[ls]] [[CLI]] ''

allright, now you need to unzip and untar the source. this is very easily done-
* for tar.gz: '''tar -zxf''' ''the name of file''.tar.gz
* for tar.bz2: ''tar -jxf''' ''the name of file''.tar.bz2
* '' [[tar]] [[unzip]] ''

now, you need to change to the new directory. the name is usually the same as the tar (minus tar.gz obviously) a useful tool is tab completion-
'''cd''' ''first couple of letters'' <tab>
or just '''ls''' to see what it is.
'''cd''' ''name of directory''
* '' [[cd]] [[tab completion]] ''

look for a file named README or something similar- read this.
'''less''' README ''use the right name''
* ''[[less]] [[README]] ''

Now, you must run the configuration file.
'''./configure'''
if this gives you no errors, then
'''make'''
and finally and optionally (though it is a good idea) is as root,
'''su''' <enter> Password: ''type your root password''

'''make install''
* ''[[configure]] [[make]] [[su]] [[root]] ''

====What if I get errors?====

gunzip and tar -xcf the archive.
cd to the directory.
read the readme. (less is good: less readme is the syntax)
unless the readme said otherwise,
./configure
if that gave you no errors, move on to the next step, which is make
else, fix any of the errors that it gave you (you might need to install another program)
the final and slightly optional step is, making sure that you are root (su <enter> password: ) and then make install

may the source be with you.

Compilation from Source by Hand

2005-10-01T15:20:51Z

Titanium geek:

== Compilatation by Hand ==

'''Formatting used in this document'''

boldface means commands you type at the [[Command Line]].
* example: '''su'''

italics are explanations of what you are supposed to do:
* example: Password: ''type your root password''
or related topics to look up
* example: ''check out these links to learn more''

words in between < > characters are keys you press
* example: <enter> you don't type <enter> you hit the enter key (return key)

----

The topic that most people view with FEAR and TREPIDATION is compiling from source by yourself. The reason is the misconception that you must be a [[programmer]] to do so. Actually, compiling by hand is not as bad as it may seem.

first of all, you need your source. So, using [http://www.google.com google], [http://freshmeat.net freshmeat.net] etc, find your program and download it. The file extension should be tar.gz or tar.bz2 or similar.
'' [[tar]] [[unzip]] [[download]] ''

find where you saved (downloaded) the file. If you have not already done so, now is the time to open your commandline/terminal/CLI. using the change directory command, go to the place where you saved your file. Let's assume that your user name is pengy and you saved the source to your home directory.
$ '''cd''' /home/pengy
use '''ls''' to see if it is there.
'' [[directory]] [[cd]] [[ls]] [[CLI]] ''

allright, now you need to unzip and untar the source. this is very easily done-
for tar.gz: '''tar -zxf''' ''the name of file''.tar.gz
for tar.bz2: ''tar -jxf''' ''the name of file''.tar.bz2
'' [[tar]] [[unzip]] ''

now, you need to change to the new directory.

gunzip and tar -xcf the archive.
cd to the directory.
read the readme. (less is good: less readme is the syntax)
unless the readme said otherwise,
./configure
if that gave you no errors, move on to the next step, which is make
else, fix any of the errors that it gave you (you might need to install another program)
the final and slightly optional step is, making sure that you are root (su <enter> password: ) and then make install

may the source be with you.

User talk:Titanium geek

2005-10-01T14:31:04Z

Titanium geek:

Hi. This is where you can find out more about me, titanium_geek.

Installing software

2005-10-01T14:11:26Z

Titanium geek: /* Compilation from source */

A number of Linux [[distributions]] have faced a common problem: <center>'''"how do we distribute software packages and updates to our users?"'''</center>

Though every distribution has particular quirks, most have standardized around one of two approaches, '''binary''' or '''source installation''', each with its own advantages and drawbacks.

Looking for and installing/removing/updating software has been largely automated on Linux through accessible '''graphical frontends''' and powerful underlying tools.

==Installation methods==

===Graphical package managers===

Most distributions come with administration tools to facilitate installation and removal of software packages. These graphical package manager [[frontend]]s also take care of downloading and installation of other neccessary packages, and can perform security updates of your system.

Using one of these tools will greatly '''facilitate software installation and removal''' on your system, as compared to searching on [[rpmfind]] or [[Compilation From Source]]. Power users and developers tend to favour installation from source.

* [[Red Hat]] uses [[RPM]] packages.
** high-level tools: [[up2date]], [[Synaptic]] (See [[Fedora, Synaptic Package Manager, finding Repositories, listing RPMs, previously installed]] for downloading, installation, and use of Synaptic.
** lower-level tools: [[apt-get]], [[Yum]]
** low-level tool: [[rpm]]

* [[SuSE]] uses [[RPM]] packages.
** high-level tool: [[YAST]]
** low-level tool: [[rpm]]

* [[Mandrake]] uses [[RPM]] packages.
** high-level tool: [[rpmdrake]]
** lower-level tool: [[URPMI]]
** low-level tool: [[rpm]]
** read the [http://www.urpmi.org/easyurpmi/index.php EasyURPMI page] to update your installation sources and search and install packages from the web automagically.

* [[Debian]] (and distros built on Debian, such as [[Knoppix]]) uses [[DEB]] packages.
** high-level tools: [[synaptic]], [[gnome-apt]] and [[Kynaptic]]
** lower-level tool: [[apt-get]]
** low-level tool: [[dpkg]]
** see the excellent section on the [[Apt]]-suite for more information on softare installation on Debian systems.

* [[Gentoo]] builds software from source (though binary installation is possible).
** tools: [[portage]] and [[emerge]]

* [[Slackware]] uses [[TGZ]] packages.
** tools: [[pkgtool]], [[slapt-get]], [[swaret]]

===Pre-compiled binaries===

Most Linux distributions today use this method - software packages are built on some conventionally-configured computer, then packaged up for downloading or distribution on CDs. The advantages are speed, standardization, and simplicity - minimal time and tools are required to get a particular piece of software running.

* [[TGZ]] - the longest-lasting form of package management, used by [[Slackware]] and its descendants. Something that confuses many newcomers is the extension. All Slackware packages end in '.tgz' but not all '.tgz' files are Slackware packages. Slackware packages are essentially gzipped tar files of binaries. Ordinarily, non-Slackware gzipped tar files will have the extension '.tar.gz' but sometimes are called '.tgz' as well. Which it is should be clear, based on where you download it but, if not, executing <tt>file</tt> <i>name_of_file.tgz</i> (or just trying to install it) will identify it.

* [[RPM]] - the RedHat Package Manager format, described at [http://www.rpm.org/ www.rpm.org]. This format is used by [[Red Hat]], [[SuSE]], and [[Mandrake]]. You can search for recent RPMs for your system using [[rpmfind]].

* [[DEB]] - the Debian package format. This is used by [[Debian]] and [[Debian]]-based distributions, such as [[Knoppix]].

===[[Compilation from source]]===

Some newer distributions are adopting this method. Rather than compiling a software package, the distributor makes the source available, perhaps with some modifications, along with a "recipe" for configuring it and installing it on an end-user's computer. The advantages of this method are optimization and customization - software is built to take advantage of the hardware you have, rather than falling back on a least common denominator, and you exercise considerable control over how the program is built, what features are included, and so forth.

* [[Portage]] is the [[Gentoo]] distribution's system for handling the downloading, compilation and installation of Gentoo packages.

* [[Compilation from source with checkinstall]]. You can combine the best of both worlds (the easy management of binary packages with the flexibility of compilation from source) by using the program [[checkinstall]]. It generates a [[RPM]] , [[DEB]] or [[TGZ]] binary package from the source compilation, and then installs it. You can manage the resulting package as any other package in your system.

* [[Compilation from Source by Hand]]. This way isn't as hard as it sounds, and it is a really useful skill to have.

Flex

2005-09-19T15:58:43Z

Titanium geek:

http://www.gnu.org/software/flex/

Urpmi

2005-09-09T14:25:00Z

Titanium geek:

The package management tool for [[Mandrake]] / [[Mandriva]]

Uses [[rpm]].

Case

2005-09-09T14:05:22Z

Titanium geek:

'''Case'''

The box that holds the computer bits.

User:Titanium geek

2005-09-09T13:08:18Z

Titanium geek:

'''Who Am I?'''
I am an international citizen, I have lived in southamerica and australia.

'''What Am I Involved In?'''

I enjoy using linux, (slackware) coding using java and designing websites.

more specifically,

* I work part time designing websites- simplicity is the goal.

* I am working on a project called miraMira which will be the next step in an old project- a walkthru of our school- coded by hand. The project attempts to make that easy.
it uses
- imagemaps
- frames
- javascript

Talk:LQRadio

2005-09-09T12:35:52Z

Titanium geek: /* Questions */

== Who will transcript what? ==

== Questions ==

----
[[User:Orkie|Orkie]] 11:46, Sep 7, 2005 (EDT)

Will this be done in American English or British English? I am willing to do some transcripts but somebody may need to quickly read over them and look for any obviously non-American things if we do it in that since our Englishes are actually quite different :) Oh, and if translations do go ahead, I can check for inappropriate content in both French and Spanish.
----
[[User:Titanium_geek|titanium_geek]] Sep 9, 2005
Well, personally I will be spelling in aussie english (coloUr etc) but of course, if any 'americanisms' are used by jeremy and his team- then we'll chuck em in and not translate them to another flavour of english. I will also **** swear words.

User:Titanium geek

2005-09-09T12:34:38Z

Titanium geek:

My name is titanium_geek- and I like linux.

User:Titanium geek

2005-09-09T12:34:17Z

Titanium geek:

My name is Alison- and I like linux.

Talk:LQRadio

2005-09-09T12:31:56Z

Titanium geek: /* Questions */

== Who will transcript what? ==

== Questions ==

----
[[User:Orkie|Orkie]] 11:46, Sep 7, 2005 (EDT)

Will this be done in American English or British English? I am willing to do some transcripts but somebody may need to quickly read over them and look for any obviously non-American things if we do it in that since our Englishes are actually quite different :) Oh, and if translations do go ahead, I can check for inappropriate content in both French and Spanish.
----
[[User:Titanium_geek]] Sep 9, 2005
Well, personally I will be spelling in aussie english (coloUr etc) but of course, if any 'americanisms' are used by jeremy and his team- then we'll chuck em in and not translate them to another flavour of english. I will also **** swear words.

Talk:LQRadio

2005-09-09T12:30:27Z

Titanium geek: /* Questions */

== Who will transcript what? ==

== Questions ==

----
[[User:Orkie|Orkie]] 11:46, Sep 7, 2005 (EDT)

Will this be done in American English or British English? I am willing to do some transcripts but somebody may need to quickly read over them and look for any obviously non-American things if we do it in that since our Englishes are actually quite different :) Oh, and if translations do go ahead, I can check for inappropriate content in both French and Spanish.
----
Well, personally I will be spelling in aussie english (coloUr etc) but of course, if any 'americanisms' are used by jeremy and his team- then we'll chuck em in and not translate them to another flavour of english. I will also **** swear words.

LQRadio

2005-09-04T01:37:11Z

Titanium geek:

this is where the transcripts for the radio should go.

LQWiki:Common Forum Responses

2005-08-24T19:55:55Z

Titanium geek:

This is a stub page to allow members to contribute to common responses for the [http://www.linuxquestions.org/questions/ LQ Forums].

What is a [[Forum]]?

Newbie Shakedown Guide - What's Linux?

2005-08-14T01:57:30Z

Titanium geek:

''originaly posted on the LQ forums by sundialsvcs''
''needs formatting''
My initial experience with Linux is probably typical. Although I've got years of experience with many different OS's, I started with a commercial "distro" (Red Hat) and, I freely admit, didn't really understand it. :confused: ... I installed and used packages, let Red Hat Network install whatever updates it wanted, and slowly began to learn :study: how this system actually worked. I found that probably the hardest thing of all was to grok how the various parts of this system worked together, because it is loosely-connected. In the "hope this helps" department, here goes ... :jawa:

The Linux Kernel:
This what Linus Torvalds started writing. It resides in the /boot directory and gets loaded into memory when you turn on the computer, by means of a "boot loader" such as grub or the older LILO. Once loaded, it always remains in memory (although it also contains "kernel modules" that can be loaded or removed, which is another story).
The Kernel is what IBM likes to call a System Control Program, and that is exactly what it does: it controls the system (hardware), and not much more. It parcels out memory, schedules CPU time, controls hardware devices, and deals with the "interrupts" they produce. All very low-level stuff. The term device driver refers to a part of the kernel (usually a kernel module) that is responsible for recognizing and controlling a particular type of device.

System Libraries (e.g. glibc):
Most programs do not make direct calls to the kernel. Instead, they work with libraries, which are found in /lib. Like Windows .DLL files, they are usually shared by many applications at once. Unlike Windows, there's a well-defined system by which many different versions of the same library can be installed at once. Well-behaved programs request the "latest" version but some applications require specific ones. The system command ldconfig is important here.

Daemons (services):
This fanciful name refers to a program that is (usually) started when the system is booted, remains up all the time, and provides services to other programs. Everything from printing to file-sharing to the act of logging on is handled by them. When the system starts up, one process (process #1) named init is started, and it starts all the other ones as directed by the file /etc/inittab. Different arrangements of daemons can be requested by the mechanism of runlevels. (See the files in /etc/rc.n, where n=0..6, which link to files in /etc/init.d.)

X-windows:
Unlike Microsoft Windows, Linux uses a de-centralized, client-server arrangement for handling graphics. An interesting feature of this system is that you can graphically log-on to a machine that has no graphics card of its own, through the network. Found in /etc/x11, it is an unexpectedly complex but sophisticated subsystem.

Window managers; desktop (e.g. KDE, Gnome):
With Microsoft Windows, your graphical user interface (GUI) only looks and feels one way. With Linux you have a broad choice. The X-windows system mentioned previously relies upon window managers to control the arrangement of windows on the screen and desktops such as KDE, Gnome, FluxBox and AfterStep to specify how things look. The choice is yours.

The Shell (e.g. bash):
You can log-in to Linux using a command-line. You can open a "terminal" window (vdt) and issue commands. The program that accepts and processes these commands is called a shell, and a common one is named "bash."

Commands, Paths:
Most of the commands recognized by a shell aren't built-in to the shell; they're programs. They're usually found in /bin, /usr/bin, /usr/local/bin, and maybe /sbin. The command echo $PATH will tell you where bash knows to look.
Command files can also be located in the current directory, but bash won't automatically look for them there. Commands found in the current directory must be prefixed by ./ (period slash). (Which is why you see people talking about ./configure)

To be sure, a system like this that is loosely-connected, unlike Windows, does take time to "get to know." I hope that this high-level road map might help a little in figuring out just where a particular problem you're having might lie. And instead of calling yourself a :newbie: and feeling somehow embarrassed by it ... you'll start to see that, when you :cry: ... there's a good reason for it! (And I assure you, it happens to us all.)

LQWiki:Answering Questions Guide

2005-07-22T18:06:24Z

Titanium geek:

== Answering Questions Guidelines ==

As possibly the world's biggest base of linux help, we as members need to work on Answering Questions.

Many [[newbie]]s find it dificult to ask questions, and when they get a bad answer, it often scares them off [[linux]] for good.

* '''Always be courteous. '''
Don't flame a newbie for a stupid question, they could be a valuable contributor to the community in the future.

* '''Answer only if you are going to help.'''
(Bad: I have no idea about it, but I think your name is totaly cool.) Answer the question if you know the answer. Just replying to get rid of a "zero response thread" is not a good idea.

* '''Answer carefully'''
make sure that you are giving the right answer and explain it carefully, in an easy to understand way.

* '''Be sensitive of newbies. '''
This doesn't mean giving specific steps each time you post an answer (a task many dislike)- but adding "if you need any extra help, just ask" to the end of the post then the newbie will be less likely to freak out.

* '''Read and Re Read the question'''
sometimes you find the problem hidden in the asker's posts.

* '''Post links where helpful.'''
any howtos, tutorials etc that might be useful for the asker, and saves you the trouble of typing it all out again.

* '''Be sensitive of ESL (english as a second language) users'''
the [[internet]] is an international place. Though the [[forum]]'s language is english, be ready to explain things carefully, in an easy to understand way.

* '''Remember you were once a newbie'''
:)

Remember our goal is to encourage and guide people in using linux, not to stop people from using linux.

Color Codes

2005-07-22T14:27:25Z

Titanium geek:

LQ member druuna posted this list, and I've added it here.

'''Attribute codes'''
* 00=none
* 01=bold
* 04=underscore
* 05=blink
* 07=reverse
* 08=concealed

'''Text color codes'''
* 30=black
* 31=red
* 32=green
* 33=yellow
* 34=blue
* 35=magenta
* 36=cyan
* 37=white

'''Background color codes'''
* 40=black
* 41=red
* 42=green
* 43=yellow
* 44=blue
* 45=magenta
* 46=cyan
* 47=white

Color Codes

2005-07-22T14:26:09Z

Titanium geek: /* terminal colour codes */

LQ member druuna posted this list, and I've added it here.

'''Attribute codes'''
00=none
01=bold
04=underscore
05=blink
07=reverse
08=concealed

'''Text color codes'''
30=black
31=red
32=green
33=yellow
34=blue
35=magenta
36=cyan
37=white

'''Background color codes'''
40=black
41=red
42=green
43=yellow
44=blue
45=magenta
46=cyan
47=white

Common Tasks

2005-07-22T14:24:23Z

Titanium geek: /* Browsing, Burning, Emailing, Office, Scanning, Viewing, Theming */

Desktop Linux is still under heavy development. While we all wish Linux was so intuitive nobody needed instructions, currently that isn't always the case. This section is meant for '''notes and quick guides''' on how to perform common tasks on Linux.

If a section isn't yet written and you are able to write it, please do so!

== General user tasks ==

===Productivity===
====Browsing, Burning, Emailing, Office, Scanning, Viewing, Theming====
* [[Browsing tasks]] - browsing the WWW and downloading safely
* [[Burning a CDROM]] - some pointers on how to write CDs.
* [[Emailing tasks]] - sending and receiving emails, setting up different mail applications
* [[Office tasks]] - word processing, spreadsheet, presentation, image manipulation and other
* [[Scanning]] - use a [[Scanner]] to convert you paper documents or images to an electronic format
* [[Viewing files]] - various ways to view the contents of files
* [[Theming GUIs]] - how to make your computer screen look the way you want it.
* [[Color Codes]] - for the terminal (command line, CLI)

===Fun===
====Gaming, Multimedia, Talking====
* [[Gaming]] - pass some time, ''not'' working
* [[Multimedia tasks]] - listen to music, extract CDs, watch videos and DVDs
* [[Talking to friends online]] - how to access common instant messaging networks, see also [[IM]].
* [[Removing DRM]] - decrypt songs to listen to them anywhere

===Technical===
==== Commands, Connecting, GRUB, LILO ====
* [[Command Line User Interface]] - Techniques for better experience
* [[Accented Characters]] - how to type accented characters
* [[Set up modem]] - using your modem/network connection to get online
* [[GRUB Menu]] - Single Task - Removing old kernel entries from your GRUB Menu boot up selections.
* [[LILO Menu]] - Setting up your own bootscreen in lilo 22.5.9
* [http://home.gagme.com/greg/linux/usbcamera.php How to Connect a Digital Camera to Linux (external link)] - an excellent how-to on connecting digital cameras to Linux.
* [[Installing Software]] - how to find and manage additional software on a running Linux system
* [[File Sharing]] - sharing files between differnt computers
* [[Installing Windows fonts]] - installing your Windows fonts so they work with your Linux install.
* [[screenshots|Taking screenshots]] - You want to show somebody your desktop? There are tools that will help you make a [[screenshots | screenshot]] and [[record your desktop]] so that you can send movie-files of how nice your desktop looks.
* [[Running Windows software]] - for that simply must-have program

== Power user tasks ==
=== Compiling kernel, Configure, IRC help, GRUB, Drivers, Recover, Remote connection ===

* [[Compiling a Kernel]] - here is a guide for compiling a kernel
* [[Configure Storage Devices]] - how to partition a hard drive, add a new hard drive, use software RAID, or use LVM (logical volume management).
* [[Creating startup scripts]] - scripts that automatically run when the computer starts
* [[Getting help from IRC]] - LinuxQuestions is a great forum, but it isn't the only one. If you know how, the IRC chat networks can also be a useful resource.
* [[GRUB boot menu]] - Configuration Guide.
* [[Installing NVIDIA drivers]] - Information on installing the newer (but closed-source) drivers released by NVIDIA. These drivers are sometimes required to run some games, like Unreal or Quake.
* [[Installing ATI drivers]] - How to install the binary ATI Drivers.
* [[Recover a Terminal Session]] - What to do if your screen's garbaged.
* [[Remote Desktop Connection|Access your System Remotely]] - Access your Linux system from another computer (running Linux, or some other OS) or use your Linux box to access another computer (running Linux, or some other OS).

=== Distro specific ===
* [[Distro specific tips & tricks]]

Bug report

2005-07-12T16:56:51Z

Titanium geek:

see: [[bug]]

a '''bug report''' lets the [[user]] tell the [[developer]] or [[maintainer]] that something is wrong with the [[software]].

A good bug report will include:
*what the user was doing with the program when they saw the bug
*a complete list of relevant [[hardware]]
*any changes made to the system (new [[software]] installed or new [[hardware]] added
*the time when the bug was first noted
*a complete description of the bug
*why it's a problem

Before submitting a new bug, the user should check to see if anyone else has posted about the bug. If anything is different (say you use different hardware to the original reporter) then submit the report, including the bug title or number.

Bug report

2005-07-12T16:52:35Z

Titanium geek:

see: [[bug]]

a bug report lets the [[user]] tell the [[developer]] or [[maintainer]] that something is wrong with the [[software]].

A good bug report will include:
*what the user was doing with the program when they saw the bug
*a complete list of relevant [[hardware]]
*any changes made to the system (new [[software]] installed or new [[hardware]] added
*the time when the bug was first noted
*a complete description of the bug
*why it's a problem

Before submitting a new bug, the user should check to see if anyone else has posted about the bug. If anything is different (say you use different hardware to the original reporter) then submit the report, including the bug title or number.

Bug report

2005-07-12T16:52:14Z

Titanium geek: bug report

see: [[bug]]

a bug report lets the [[user]] tell the [[developer]] or [[maintainer]] that something is wrong with the [[software]].

A good bug report will include:
*what the user was doing with the program when they saw the bug
*a complete list of relevant [[hardware]]
*any changes made to the system (new [[software]] installed or new [[hardware added]]
*the time when the bug was first noted
*a complete description of the bug
*why it's a problem

Before submitting a new bug, the user should check to see if anyone else has posted about the bug. If anything is different (say you use different hardware to the original reporter) then submit the report, including the bug title or number.

Distro differences

2005-06-15T23:33:26Z

Titanium geek:

''originally posted by craigevil on the Linux Newbie forum''

Here are some ways the various distros differ:

1) Whether the distro is free or commercial and uses "Free Software".

2) Number of packages available without looking for other sources of software. Debian is the biggy here with over 15000 apps.

3) The way updates are handled.

4) Security policies.

5) Package management systems:( there are advantages and disadvantages to all methods)
The following are some examples of package management systems implemented by Unix-like operating systems:

* [[RPM]], the RPM Package Manager. Invented by [[Red Hat]], but now used by several other Linux distributions. RPM is the Linux Standard Base packaging format. There are many higher level tools that use the RPM packaging format, simplifying the process of finding, downloading and installing packages and their dependencies, including

** [[YUM]], used on [[Fedora Core]].

** [[up2date]], used on [[Red Hat]] Enterprise Linux. Although designed to talk to [[Red Hat]] Network, up2date can also source packages from yum and apt for [[RPM]] repositories, as well as local and directories.

** [[YaST]] , as used on [[SuSE]] Linux distributions.

** [[urpmi]] as used by [[Mandrake]]linux/Mandriva

** [[APT]] for [[RPM]].

* [[dpkg]], used originally by [[Debian]] GNU/Linux and now by other systems. The .deb format used by dpkg was the first to have a widely known dependency resolution tool, called [[APT]].

* Portage/emerge, used by [[Gentoo]] Linux and inspired by the [[BSD]] ports system.

6) Is it going to be around or is it a new distro.

7) "Comparison of Linux distributions"

8) The file system used. "Comparison of file systems"

9) Window manager it uses. Window Managers for X

10) Desktop environment

11) How easy it is to install and use. How are programs installed and updated.

12) Does it have what "you" Need.

13) The documentation and support available.

Distro differences

2005-06-15T23:30:36Z

Titanium geek:

''originally posted by craigevil on the Linux Newbie forum''

Here are some ways the various distros differ:

1) Whether the distro is free or commercial and uses "Free Software".

2) Number of packages available without looking for other sources of software. Debian is the biggy here with over 15000 apps.

3) The way updates are handled.

4) Security policies.

5) Package management systems:( there are advantages and disadvantages to all methods)
The following are some examples of package management systems implemented by Unix-like operating systems:

* RPM, the RPM Package Manager. Invented by Red Hat, but now used by several other Linux distributions. RPM is the Linux Standard Base packaging format.
There are many higher level tools that use the RPM packaging format, simplifying the process of finding, downloading and installing packages and their dependencies, including

o YUM, used on Fedora Core.

o up2date, used on [[Red Hat]] Enterprise Linux. Although designed to talk to [[Red Hat]] Network, up2date can also source packages from yum and apt for [[RPM]] repositories, as well as local and directories.

o [[YaST]] , as used on [[SuSE]] Linux distributions.

o [[urpmi]] as used by [[Mandrake]]linux/Mandriva

o [[APT]] for [[RPM]].

* dpkg, used originally by [[Debian]] GNU/Linux and now by other systems. The .deb format used by dpkg was the first to have a widely known dependency resolution tool, called [[APT]].

* Portage/emerge, used by [[Gentoo]] Linux and inspired by the BSD ports system.

6) Is it going to be around or is it a new distro.

7) "Comparison of Linux distributions"

8) The file system used. "Comparison of file systems"

9) Window manager it uses. Window Managers for X

10) Desktop environment

11) How easy it is to install and use. How are programs installed and updated.

12) Does it have what "you" Need.

13) The documentation and support available.

Distro differences

2005-06-15T23:28:05Z

Titanium geek:

''originally posted by craigevil on the Linux Newbie forum''

Here are some ways the various distros differ:

1) Whether the distro is free or commercial and uses "Free Software".

2) Number of packages available without looking for other sources of software. Debian is the biggy here with over 15000 apps.

3) The way updates are handled.

4) Security policies.

5) Package management systems:( there are advantages and disadvantages to all methods)
The following are some examples of package management systems implemented by Unix-like operating systems:
o RPM, the RPM Package Manager. Invented by Red Hat, but now used by several other Linux distributions. RPM is the Linux Standard Base packaging format.
There are many higher level tools that use the RPM packaging format, simplifying the process of finding, downloading and installing packages and their dependencies, including
o YUM, used on Fedora Core.
o up2date, used on Red Hat Enterprise Linux. Although designed to talk to Red Hat Network, up2date can also source packages from yum and apt for RPM repositories, as well as local and directories.
o YaST , as used on SuSE Linux distributions.
o urpmi as used by Mandrakelinux/Mandriva
o APT for RPM.
o dpkg, used originally by Debian GNU/Linux and now by other systems. The .deb format used by dpkg was the first to have a widely known dependency resolution tool, called APT.
o Portage/emerge, used by Gentoo Linux and inspired by the BSD ports system.

6) Is it going to be around or is it a new distro.

7) "Comparison of Linux distributions"

8) The file system used. "Comparison of file systems"

9) Window manager it uses. Window Managers for X

10) Desktop environment

11) How easy it is to install and use. How are programs installed and updated.

12) Does it have what "you" Need.

13) The documentation and support available.

Distro differences

2005-06-15T23:26:26Z

Titanium geek: how the distros differ

''originally posted by craigevil on the Linux Newbie forum''

Here are some ways the various distros differ:

1) Whether the distro is free or commercial and uses "Free Software".
2) Number of packages available without looking for other sources of software. Debian is the biggy here with over 15000 apps.
3) The way updates are handled.
4) Security policies.
5) Package management systems:( there are advantages and disadvantages to all methods)
The following are some examples of package management systems implemented by Unix-like operating systems:
* RPM, the RPM Package Manager. Invented by Red Hat, but now used by several other Linux distributions. RPM is the Linux Standard Base packaging format.
There are many higher level tools that use the RPM packaging format, simplifying the process of finding, downloading and installing packages and their dependencies, including
o YUM, used on Fedora Core.
o up2date, used on Red Hat Enterprise Linux. Although designed to talk to Red Hat Network, up2date can also source packages from yum and apt for RPM repositories, as well as local and directories.
o YaST , as used on SuSE Linux distributions.
o urpmi as used by Mandrakelinux/Mandriva
o APT for RPM.
* dpkg, used originally by Debian GNU/Linux and now by other systems. The .deb format used by dpkg was the first to have a widely known dependency resolution tool, called APT.
* Portage/emerge, used by Gentoo Linux and inspired by the BSD ports system.
6) Is it going to be around or is it a new distro.
7) "Comparison of Linux distributions"
8) The file system used. "Comparison of file systems"
9) Window manager it uses. Window Managers for X
10) Desktop environment
11) How easy it is to install and use. How are programs installed and updated.
12) Does it have what "you" Need.
13) The documentation and support available.

Choosing a Linux distribution

2005-06-15T23:25:23Z

Titanium geek:

One of the first questions that you probably have about Linux is "What [[distribution]] do I use?" Indeed, this is one of the most frequently asked questions on our [http://www.linuxquestions.org/questions/ forums].

The question is a little harder to answer than it looks. Linux distributions (or ''distros'') come in a wide variety of packages, each with their own quirks and specialties. Some are designed for ease-of-use, some for the power user or [[hacker]], some for powerful computers with lots of [[RAM]] and some for older hardware with slow [[CPU]]s.

Some of the possible answers to this question are:

* Try a few distributions and see what you like
* Use the distribution that the Linux [[guru]] next door uses, so if you have any problems you can ask him or her for help
* [[distro differences]] How distros are different
* (other possible answers?)

==Introductory and general purpose==

=== What distro for just trying Linux out? ===

If you aren't yet prepared to set aside a portion of your hard drive for Linux, or if you just want to take Linux for a spin without any long-term commitments, try one of the [[Live CD distributions]] like [[Knoppix]] or [[DamnSmallLinux]], or the [[Suse]] 9.1 evaluation CD. These can be booted and run directly from a CD, and are a great way to see what Linux can do without affecting any existing operating systems you may have installed. Such distributions tend to run more slowly than a fully-installed Linux, however, so if you are thinking of using Linux regularly, you may want to consider doing a real installation. Many Live CD distributions can be installed to the hard drive if you so choose.

=== What distro for a total newbie? ===

If you are very new to the Linux world and have no interest in learning a lot of technical details just to get it running, you may want to go with one of the mainstream distributions such as [[Linspire]], [[Mandrake]], [[Fedora]] (formerly [[Red Hat]]), [[SuSE]] or [[Debian]]. If you can spare the money, it may be worthwhile to purchase a commercial version, since you may get tech support from the vendor.

=== What distro for the power user? ===

If you consider yourself a power user, and would like to learn a lot of technical details about Linux as you are installing and using it, you would be well served to try out one of the more do-it-yourself distributions. [[Gentoo]], [[Debian]] and [[Slackware]] might be among your choices here. If you are already an experienced Linux user and really want to get your hands dirty, there is [[Linux From Scratch]], which is not really a distribution so much as a set of instructions for building your own distribution (though this isn't recommended unless you already know what you are doing).

==Special purpose==

=== What distribution for a server ===

Many system administrators have come to trust [[Debian]] with their servers. Debian's security policy and strict packaging rules make it an attractive choice for a non-commercial solution. All security fixes are [[backport]]ed ensuring that the production environment remains the same and breakage will not occur. For a commercial solution people tend to lean towards [[Redhat]]'s Advanced Server line.

=== What distro for an old computer? ===

There are a number of minimalistic distributions, such as [[VectorLinux]] and [[Peanut]] that are designed for computers without much hard drive space or CPU speed. It's quite possible to install Linux on an early 386 with 2 to 4 [[megabyte]]s of [[RAM]], though if you hope to install a [[GUI]] you may need a bit more memory or CPU; a 486 with 8MB RAM is probably the lowest you can go with [[XFree86]]. For acting as a [[firewall]], [[e-mail]] client, or basic machine for text editing and scripting, this might be the way to go. However, distributions like Vector and Peanut, while minimal, are not "micro" - they still require 100+ MB hard drives and really need a 586 or fast 486. For even smaller distributions that may run in under 100MB (or even from floppy) on a 386/486, distros like [[BasicLinux]], [[muLinux]], [[Floppix]], and others may be suitable.

''More to be written''

=== What distro for games? ===

Gentoo has modified kernels and other elements that probably make it a good gaming platform. 

''More to be written''

=== Windows/UNIX-Oriented Distro Spectrum ===

If you are a newbie, you will naturally look for a distro that has the look and feel of Windows. On the other hand, if you prefer manual configuration, you will look at a more UNIX-like solution. This spectrum should help you figure out where major distros stand out-of-the-box:

Windows >> Linspire, Xandros >> Fedora, Mandriva >> Debian, Mepis, Ubuntu, (Other Debian Derivatives) >> Arch, Gentoo, Slackware >> BSD (Open, Free, Net, DragonFly), Solaris >> pure UNIX (Unixware, HP-UX, 4.4BSD)

''More to be written''

Smb4k

2005-06-15T21:18:42Z

Titanium geek:

This program helps users set up and access shares on a [[network]].

Mandrake GUI filesharing

2005-06-15T21:12:02Z

Titanium geek:

'''Filesharing''' is when you share files and resources between computers. This can be over the internet, or it can be between computers in a private network. This guide focuses on the second. (see [[File sharing]])

''This guide assumes that you have [[Samba]], [[smb4k]] installed and your [[network]] is running fine.''

''You won't need any special instructions for sharing with computers with different OS's, it should work for all of them.''

1. start smb4k. For me this is under
[ Applications-Internet-File transfer-smb4k ]

2. Start scaning the network. On the left hand side you should see a space with a blue circle and a name. One might be MDKgroup... this is the default workgroup that you are in. The other should be the workgroup of the rest of your network. Let's say this is called workgroup.

3. Click on workgroup. Now you can see some computers and their names. Let's say that the computer you want to share with is called XPbox

4. Click on XPbox. if it asks you for a username and password, and you can't get any further with out it, give it.
:4.5 if smb4k doesn't ask you but you are told you aren't allowed to access the resource, then click on the authentication button.

5. open XPbox by clicking on the plus sign beside it. (+) Now you should see a green folder for the hard drive. it will be of type disk. if you don't see anything, then this is because the other computer doesn't have anything shared.

6. right click on the disk/resource you want to share. Now click Mount.

7. Let's say your user name is sloppy.
Navegate to /home/sloppy/smb4k/XPbox to get stuff and put stuff on the XPbox computer.

8. What about letting XPbox see you? right click on the directory you want to share (lets say home/sloppy) and choose share.

Thats it! 8.5 simple steps.
if you are having problems with the stufff in the first italics, then you really want a tutorial on networking, samba, installing software (such as) smb4k, and/or windows networking, not with filesharing. ;)

File sharing via P2P

2005-06-15T21:10:46Z

Titanium geek:

'''File sharing''' provides a way to give and receive files between individuals without requiring special servers or other complicated configurations. This is particuarly the case with decentralized [[peer to peer]] [[network]]s where, unlike earlier P2P predecessors such as [[Napster]], no centrally controlled systems are required at all in order to establish a vast network upon which people can share music, video and other data via P2P applications. Most free (as in freedom) p2p clients can connect to multiple networks.

File sharing can also refer to traditional [[LAN]] file sharing (not P2P, which works mainly over [[WAN]] networks like the [[Internet]]). Traditional file sharing protocols that work with Linux include [[Samba]] and [[NFS]].

see: [[Mandrake GUI filesharing]]

==Specific applications==

=== FastTrack (KaZaA) ===

*[[giFT]]
*[http://www.lowth.com/p2pwall/ P2Pwall/FTwall - Kazaa blocking with Iptables]

=== Gnutella ===

*[[mutella]]
*[[gtk-gnutella]]
*[[LimeWire]]
*[[qtella]]

=== eDonkey ===

*[[xmule]]
*[[eDonkey]] (official client)
*[[Overnet]] (official client)
*[[MLDonkey]]
*[[ShareDaemon]]
*[[aMule]]

=== BitTorrent ===

*[[BitTorrent]] (official client)
*[[Azureus]]
*[[MLDonkey]]

=== SoulSeek ===

*[[pysoulseek]] (not updated anymore)
*[[Nicotine]]

=== Direct Connect ===

*[[LDCC]]

==External links==
*[http://www.slyck.com/index.php Slyck - File sharing news]
*[http://www.slyck.com/forums/index.php Slyck forums]

Common Tasks

2005-06-15T21:03:37Z

Titanium geek: /* Commands, Connecting, GRUB, LILO */

Desktop Linux is still under heavy development. While we all wish Linux was so intuitive nobody needed instructions, currently that isn't always the case. This section is meant for '''notes and quick guides''' on how to perform common tasks on Linux.

If a section isn't yet written and you are able to write it, please do so!

== General user tasks ==

===Productivity===
====Browsing, Burning, Emailing, Office, Scanning, Viewing, Theming====
* [[Browsing tasks]] - browsing the WWW and downloading safely
* [[Burning a CDROM]] - some pointers on how to write CDs.
* [[Emailing tasks]] - sending and receiving emails, setting up different mail applications
* [[Office tasks]] - word processing, spreadsheet, presentation, image manipulation and other
* [[Scanning]] - use a [[Scanner]] to convert you paper documents or images to an electronic format
* [[Viewing files]] - various ways to view the contents of files
* [[Theming GUIs]] - how to make your computer screen look the way you want it.

===Fun===
====Gaming, Multimedia, Talking====
* [[Gaming]] - pass some time, ''not'' working
* [[Multimedia tasks]] - listen to music, extract CDs, watch videos and DVDs
* [[Talking to friends online]] - how to access common instant messaging networks, see also [[IM]].
* [[Removing DRM]] - decrypt songs to listen to them anywhere

===Technical===
==== Commands, Connecting, GRUB, LILO ====
* [[Command Line User Interface]] - Techniques for better experience
* [[Accented Characters]] - how to type accented characters
* [[Set up modem]] - using your modem/network connection to get online
* [[GRUB Menu]] - Single Task - Removing old kernel entries from your GRUB Menu boot up selections.
* [[LILO Menu]] - Setting up your own bootscreen in lilo 22.5.9
* [http://home.gagme.com/greg/linux/usbcamera.php How to Connect a Digital Camera to Linux (external link)] - an excellent how-to on connecting digital cameras to Linux.
* [[Installing Software]] - how to find and manage additional software on a running Linux system
* [[File Sharing]] - sharing files between differnt computers
* [[Installing Windows fonts]] - installing your Windows fonts so they work with your Linux install.
* [[screenshots|Taking screenshots]] - You want to show somebody your desktop? There are tools that will help you make a [[screenshots | screenshot]] and [[record your desktop]] so that you can send movie-files of how nice your desktop looks.
* [[Running Windows software]] - for that simply must-have program

== Power user tasks ==
=== Compiling kernel, Configure, IRC help, GRUB, Drivers, Recover, Remote connection ===

* [[Compiling a Kernel]] - here is a guide for compiling a kernel
* [[Configure Storage Devices]] - how to partition a hard drive, add a new hard drive, use software RAID, or use LVM (logical volume management).
* [[Creating startup scripts]] - scripts that automatically run when the computer starts
* [[Getting help from IRC]] - LinuxQuestions is a great forum, but it isn't the only one. If you know how, the IRC chat networks can also be a useful resource.
* [[GRUB boot menu]] - Configuration Guide.
* [[Installing NVIDIA drivers]] - Information on installing the newer (but closed-source) drivers released by NVIDIA. These drivers are sometimes required to run some games, like Unreal or Quake.
* [[Installing ATI drivers]] - How to install the binary ATI Drivers.
* [[Recover a Terminal Session]] - What to do if your screen's garbaged.
* [[Remote Desktop Connection|Access your System Remotely]] - Access your Linux system from another computer (running Linux, or some other OS) or use your Linux box to access another computer (running Linux, or some other OS).

=== Distro specific ===
* [[Distro specific tips & tricks]]

Video editor

2005-05-27T01:59:34Z

Titanium geek: /* Category Description */

==Category Description==
So: you have shot all this great footage on your camera. Now what? You know that some of the stuff you shot in the middle really should go at the begining of your movie, and some stuff doesn't belong at all- like the time you forgot to shut off the camera and got 15 minutes of footage about the inside of the camera bag. You also want to add some titles, credits and some fancy disolves.

There are two flavours of editors- linear (which is awful) and nonlinear. Most editors today are nonlinear. (yay!)

You need a video editor- a program that runs on your computer and is the tool you use to participate in the art of editing.

==Specific applications==
*[[LiVES]]
*[[Cinelerra]]
*[[Kino]]
*[[CinePaint]]
*[[Avidemux]]
*[[LVE]]

===Ripping and Capturing Tools, Encoders, Decoders...===
*[[DVD::Rip]]
*[[Transcode]]
*MJPEG tools
*ffmpeg

==External links==
*[http://www.robfisher.net/video/ Linux Video Editing] - Tutorial focused on video capture with [[Kino]] and further editing in [[Cinelerra]].
*[http://www.exploits.org/v4l/ Video for Linux Resources] - Comprehensive list of video and TV [[Linux]] applications.

''This article 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]] !''<br>

Cookies

2005-05-27T01:46:53Z

Titanium geek:

as you travel around the internet, you leave a trail to follow. When hansel and gretel walked through the forrest they left a trail of crumbs. Your four-yearold also leaves a trail of crumbs- especially after eating crackers.

Thus the term cookie- refering to a group of crumbs- came into common usage.

A cookie is used by [[website]] authours to remember you when you come back. This is so you can get the greeting: hello spaz. You last visited our page 01/09/04. Since then there has been 4 new articles posted.
etc etc.

Sometimes a cookie can be malicious, but mostly they are good intentioned. If you get a creepy big brother feeling that somebody is watching you, your browser will have an option about accepting cookies- you also will be able to delete all past cookies from there.

Cookies are simple text files on your hard drive with key words that the website will read to get information. They often have an expiry date, meaning that after a certain time they will erase themselves.