LQWiki - User contributions [en]

Client-server

2004-04-19T20:20:23Z

Ugen64: moved peer to peer into see also

'''Client-server''' communication models involve a [[client]] or clients accessing resources from a [[server]].

See also [[dumb terminal]], [[thin client]], [[peer to peer]]

X Window Server

2004-04-19T20:19:55Z

Ugen64: made into redirect

#REDIRECT [[X Window System]].

Windows

2004-04-19T20:18:38Z

Ugen64: sp

'''Microsoft Windows''' is a term for a family of operating systems produced by [[Microsoft]], and these are the only serious competition for [[Linux]] on desktop machines ([[MacOS]] is limited to proprietary hardware and as such doesn't really compete).

Windows has a large user base - over 95% of the world's desktop computers use some form of it. Being compatible with Windows takes a significant amount of manpower from the open source movement. However, the majority of servers use [[UNIX]] or Linux, and with Microsoft's questionable practices, the open source movement is undoubtedly growing.

The [[Samba]] suite of software enables [[UNIX]] and [[Linux]] systems to both act as clients accessing Windows PCs and as servers for them. [[WINE]] and its commercial variants enable Windows software to be run on Linux machines, whilst [[DOSEMU]] allows DOS programs to be used. The [[Mono]] project is developing a Linux implementation of [[.NET]] and ASP.NET.

Sub Categories:

[[Windows Replacement]] -- list of programs that have equivalent functionality

[[Windows Interoperability]] -- samba and ldap and exchange

[[Windows Compatability]] -- wine

FAT

2004-04-19T20:18:14Z

Ugen64: wordage

'''FAT''' stands for ''File Allocation Table''. It is the [[filesystem]] used and/or supported by versions of [[Microsoft]] [[Microsoft Windows|Windows]], but has been superseded by the [[VFAT]] and [[NTFS]] filesystems.

There are several versions of this filesystem, with varying cluster sizes: [[FAT12]], [[FAT16]], and [[FAT32]]. Each allows for successively larger files and directories to be stored.

FAT is often still used in certain devices, because it is very easy to implement.

Music player

2004-04-07T21:47:10Z

Ugen64: aded noatun

Various programs exist to play music under Linux: audio CDs, [[MP3]] files or [[Ogg Vorbis]] audio. The most well-known is [[XMMS]], a WinAmp-alike music player.

Though the MP3 format still reigns supreme, Ogg support is growing quickly, and even some hardware "MP3 players" can handle Ogg audio.

==Specific applications==

===GUI/X===
* [[XMMS]] -- Media player modeled after Winamp
* [[RhythmBox]] -- A music player and manager for the [[GNOME]] desktop
* [[JuK]] -- an audio jukebox that supports collections of files for [[KDE]]
* [[grip]] -- can be used for playing and ripping audio CDs with ease
* [[Beep media player]] -- XMMS based media player, uses [[GTK]]2
* [[GQmpeg]] -- [[GTK]]1 based player
* [[Noatun]] - A [[KDE]] music player, although not as elaborate as some of the others

===Console/text-based===
*[[mpg123]] -- Command line MP3 player
*[[mpg321]] -- [[free]] mpg123 clone
*[[ogg123]] -- [[Ogg vorbis]] command line player

==See also==
* [[Multimedia tasks]]
* [[FreeDB]]

Image manipulation

2004-04-07T21:46:18Z

Ugen64: fmt

'''Image manipulation''' [[application]]s are used to manipulate pictures, such as removing red eye, and other more sophisticated tools.

==Specific applications==

*[[ImageMagick]] is great for the command-line user. It also has some GUI capabilities, but is wonderful for scripting activity.
*[[Inkscape]]
*[[Gimp]] is the classic Linux image manipulator. It isn't strictly image manipulation, though. There are a large variety of tutorials regarding the program.
*[[Scribus]]
*[[Sodipodi]]
*[[XV]]

==External link==
*[http://www.steidler.net/uptime/archives/000560.html Making Magick - an ImageMagick Tutorial]

''This article is a [[LinuxQuestions.org_Wiki:stub_articles|stub]] and needs to be finished. [[LinuxQuestions.org_Wiki:plunging_forward|Plunge forward]] and [[LinuxQuestions.org_Wiki:How_to_edit_a_page|help it grow]] !''

3D modeling

2004-04-07T21:45:02Z

Ugen64: 2 words

'''3D modeling''' software is used to create 3D images and animations.

==Specific applications==

*[[Blender]]
*[[PovRay]]
*[[Wings 3d]]

''This article is a [[LinuxQuestions.org_Wiki:stub_articles|stub]] and needs to be finished. [[LinuxQuestions.org_Wiki:plunging_forward|Plunge forward]] and [[LinuxQuestions.org_Wiki:How_to_edit_a_page|help it grow]] !''

Unreal

2004-04-07T21:43:20Z

Ugen64: created

'''Unreal''' refers both to a [[Windows]] first person shooter and the engine that debuted on that game. It is currently used in a variety of [[Linux]]-enabled video games, including [[America's Army]] and [[Unreal Tournament]].

ClamAV

2004-04-07T21:40:32Z

Ugen64: elaborated

'''ClamAV''' is a virus scanner under the [[GPL]]. On its official website, it is stated that ClamAV can detect over 20,000 viruses, and it can also recognize many different data types (including a variety of [[compressed file]]s).

==External links==
* http://www.clamav.net

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

Red Hat

2004-04-07T21:38:35Z

Ugen64: grammar

'''Red Hat''' Linux was an [[RPM]]-based, [[user friendly]] Linux [[distribution]] that gained some degree of corporate acceptance as a viable [[server]] [[operating system]] and has a small degree of market share in the corporate [[enterprise]]. Red Hat was one of the first Linux distributions to feature a graphical installer. In 2003 Red Hat announced their plan to abandon their legacy as a user friendly, desktop distribution and to focus their efforts on their enterprise server products and paid support programs under a brand new name. Thus, Red Hat will no longer exist as a Linux distribution name. [[Fedora]] is now aimed at the desktop market while Red Hat Enterprise Linux is aimed at the coporate market and the latter has become its primary product.

==History of Red Hat Linux==
1993:
Young incorporates ACC Corporation, was a catalog business that sold Linux and Unix software accessories and books and distributed a magazine called New York UNIX.

1994:
Marc Ewing created his own distribution of Linux which he named Red Hat Linux, which was released in October. It becomes known as the Halloween release.

1995:
Young later bought Ewing's business, merged it with ACC Corporation, and named the new company Red Hat Software.

Red Hat Linux 2.0 marked the official release of the new package management system called [[RPM]].

Feburary 1999:
[[IBM]] and Red Hat announce Linux Alliance.

This is how one of the most popular distributions came into existence.

In 2003 Red Hat announced the creation of the [[Fedora]] project. Red Hat now only provides support for its enterprise edition, while Fedora is the free testing distribution, the next in the series after Red Hat 9. Fedora can be found at http://fedora.redhat.com.

==See also==
*[[Fedora]]
*[[up2date]]

==External links==
*[http://www.redhat.com Official website]
*[http://www.redhat.com/mktg/rh10year/ Red Hat history]

List of Linux distributions

2004-04-07T21:37:53Z

Ugen64: caps

[http://kernel.org Linux] is a [[kernel]], in itself not an extremely useful piece of software, but very important: it provides hardware resources management, and access to the hardware is necessary to get anything done, of course. To have a fully functional [[operating system]], some basic software is needed as well. A [[GNU/Linux]] [[distribution]] is the complete package. Most modern distributions also come with graphical installers to help with the initial setup.

===Special categories===
*[[Live CD distributions]]
*[[Source distributions]]
*[[Firewall distributions]]
*[[Embedded Linux]]

===Alphabetical distribution listing===
*[[Arch Linux]]
*[[Ark]]
*[[Aurox]]
*[[BioKnoppix]]
*[[BLAG]]
*[[Buffalo]]
*[[cAos]]
*[[ClusterKnoppix]]
*[[CollegeLinux]]
*[[Conectiva]]
*[[DamnSmallLinux]]
*[[Debian]]
*[[Devil-Linux]]
*[[Feather]]
*[[Fedora]]
*[[Gentoo]]
*[[Gnoppix]]
*[[IPCop]]
*[[Kanotix]]
*[[KnopILS]]
*[[Knoppix]]
*[[Kurumin]]
*[[Libranet]]
*[[LindowsOS]]
*[[Linux From Scratch]]
*[[LNX-BBC]]
*[[Lorma]]
*[[Lunar Linux]]
*[[Lycoris]]
*[[Mandrake]]
*[[Mandows]]
*[[MEPIS]]
*[[Morphix]]
*[[Peanut]]
*[[PCLinuxOS]]
*[[PHLAK]]
*[[Red Hat]]
*[[ROCK Linux]]
*[[Rubyx]]
*[[Slackware]]
*[[Slax]]
*[[SmoothWall]]
*[[SOL (Server Optimized Linux)]]
*[[SOT Linux]]
*[[Source Mage]]
*[[SPB-Linux]]
*[[Sun JDS]]
*[[SuSE]]
*[[SystemRescue]]
*[[Thiz]]
*[[Trustix Secure Linux]]
*[[TurboLinux]]
*[[VectorLinux]]
*[[Whitebox Linux]]
*[[Yellow Dog Linux]]
*[[Xandros]]

Suse

2004-04-07T21:36:38Z

Ugen64: moved to "SuSE"

#REDIRECT [[SuSE]]

User:Ugen64

2004-03-26T20:48:38Z

Ugen64:

I'm '''ugen64''', a [[Mandrake]] user and an administrator (sysop) at [http://www.wikipedia.org Wikipedia, the free encyclopedia]. I am also an administrator at this website.

User:Ugen64

2004-03-26T20:48:32Z

Ugen64: diff distro

I'm '''Ugen64''', a [[Mandrake]] user and an administrator (sysop) at [http://www.wikipedia.org Wikipedia, the free encyclopedia]. I am also an administrator at this website.

Tarball

2004-03-21T23:44:31Z

Ugen64: copyedits

A '''tarball''' is the long name of a '''tar''' file, almost always compressed using either [[bzip2]] or [[gzip]]. As its name suggests, the format was originally used for storage on a tape drive. The actual result of running a directory or a bunch of files through tar is one file composed of all those files (like a ZIP archive in DOS or Windows, but uncompressed). It is worthwhile to note that while one will usually find a compressed tarball, a tarball consisting of individually compressed files is much less susceptible to damage (damage to the former results in everything following the damage becoming unreadable, while damage to the latter results in the damaged archive becoming unreadable). Tarballs are often used to distribute Linux [[software]] and [[source code]] for compiling.

First Person Shooter

2004-03-21T23:43:04Z

Ugen64: better definition

The term '''First Person Shooter''' (sometimes abbreviated '''FPS''') is used to describe the genre of shooting games (or action games, to be broader) that gives the player a first-person perspective.

Examples include:
* [[Doom]]
* [[Quake]]
* [[Half-Life]]
* [[Counter-Strike]]
* [[Unreal Tournament]]

Localhost

2004-03-21T23:41:47Z

Ugen64:

'''127.0.0.1''' is a computer's ''loopback'' [[IP address]]. Actually the whole 127.0.0.1/8 range is allocated for this, but only 127.0.0.1 is normally used. It is usually configured in ''/etc/hosts'' to the host name [[localhost]].

If you're troubleshooting local [[TCP/IP]] networking issues you can issue a <tt>ping 127.0.0.1</tt> or <tt>ping localhost</tt> command to see if the [[TCP/IP stack]] is installed and working on your local machine. If the ping replies, then you have eliminated a missing TCP/IP configuration on the local machine as a possible cause.
----
''This article is a [[LinuxQuestions.org_Wiki:stub_articles|stub]] and needs to be finished. [[LinuxQuestions.org_Wiki:plunging_forward|Plunge forward]] and [[LinuxQuestions.org_Wiki:How_to_edit_a_page|help it grow]]!''

LQWiki:Manual of Style

2004-03-21T23:40:19Z

Ugen64: small edits

This '''manual of style''' is meant to serve as a guideline to help ensure that LQ Wiki articles have a consistent look and feel. It is just a guideline, but consistency will make the wiki easier to read, easier to use and easier to contribute to. Clear, informative and unbiased writing is always more important than presentation and formatting. Remember, one of the great things about a wiki is that perfection is not required. Don't let this article stop you from [[LinuxQuestions.org_Wiki:plunging forward|plunging forward]]. Other wiki users will find your article when [[LinuxQuestions.org:weeding|weeding]] and all
articles should gradually reflect this guide.

The emphasis of this manual is more on explaining what to do, and less on how to do it. For instructions explaining how to markup your contributions, see the [[LinuxQuestions.org_Wiki:Wiki_markup|markup]] guide.

==Mechanics==

===Use Good Spelling and Grammar===

*Spelling and grammar, partly due to the spellchecking defaults and partly due to prevalence, is standardized in the American form. Regarding the spelling of links, redirects may be necessary.
*Spell words correctly. This site includes a spellchecker. Various editors and word processors contain or utilize spellcheckers. Various utilities such as aspell or ispell are available. However, do not let concerns regarding spelling errors prevent you from contributing.
*Use good grammar. Use a grammar-checking program or take other steps to ensure correctness. Again, do not let concerns regarding correctness prevent you from contributing.

===Titles===

*The first instance of the title of the page should be bold. Note the bold "manual of style" at the beginning of this page.

===Links===

*Before creating a new link, first search for it and likely variants. This avoids redundant material, redundant links, or conflicts.
*Link only relevant keywords. Not every possible linkable word needs to be so linked; rather, link to only those articles that the reader would most likely desire to follow for further pertinent information.
*Articles and links should be on '''Linux''' or general computer topics relevant to Linux, though brief digressions on specifically non-Linux topics may be appropriate.
*Make links in the singular form. Consistency promotes ease of editing. If it is necessary to use the plural form, plural <nowiki>[[link]]s</nowiki> can easily be made and will render as a single highlighted word.
*As of this writing, links are case sensitive. Title/link applications and entities according to their official names (MPlayer, IBM) and, otherwise, the case should be as if it were The Title of a Book. If necessary, in the circumstance of a wrongly or confusingly cased title, supply a redirect.

====External and 'See also' links====

*External links should be formatted as normal when in the body of the text. Additional external links for further research should be placed at the end in a section entitled "External links", using a heading (i.e. <nowiki>==External links==</nowiki>).
*If internal links do not fall within the body of the article, they should be listed in a section entitled "See also" which should come immediately before "External links" (if it exists) or at the end.
*These lists should be bulleted, using single asterisks.
*Short descriptive text should be supplied to replace long or ugly URLs and to simply be more informative. This is done with brackets (i.e. <nowiki>[http://www.kde.org KDE]</nowiki> comes out as [http://www.kde.org KDE]). Additional descriptive text, if truly necessary, can be added to the right of the link (outside the right bracket).



===Markup===

*Use as little HTML (i.e. <nowiki>, , etc.</nowiki>) as possible. A few cases where HTML may be necessary include block quotes, single line breaks, and underlining.
*Do ''not'' indent in order to separate paragraphs or create leading whitespace. It will misformat paragraphs as a single long line in fixed font. To separate paragraphs, simply leave a single blank line between each; to create leading whitespace, use the ':' markup.
* When first expanding acronyms, format it as usual except for bold initial letters. For example: '''GNU''' is a recursive acronym for '''G'''NU's '''N'''ot '''U'''NIX.

===Command Syntax Markup===

*Prefix all commands meant to be performed by an ordinary user with '$' and all command meant to be performed by the super-user/root with '#'.
*Format the names of commands in fixed font with <nowiki><tt></tt></nowiki>


==Style==

===Be Objective===

*First, if in doubt, use ''facts'', not ''opinions''.
**Good: "KDE is one of the most popular desktop managers for Linux." (a fact)
**Okay: John Smith states that "KDE is an awesome desktop manager." (not as good)
**Bad: KDE is the best desktop manager out, everyone should get it! (opinion)
*Second, use what ''specific'' people say, not a general group that you make up.
**Okay: John Smith states that "KDE is an awesome desktop manager." (not as good)
**Bad: Critics say that KDE is a horrible desktop manager. (it's too general: who are critics, why do they say this, do they really say this, etc.)
**Bad: Lots of people think that KDE sucks (how can we tell this is right or wrong? define lots of people)
*People on kde.org are probably going to say that KDE is better than GNOME, and vice versa. Therefore, if you are writing an article about desktop managers, you should attempt to get all points of view (those who like KDE, those who like GNOME, etc.).

===Paragraphs===

*Generally, the first paragraph should contain a few sentences introducing the topic in a general sense prior to expanding on the topic in detail. For example:

::A '''game''' is an object generally used to have fun. Currently, games are one of the most popular forms of entertainment, and have been around for thousands of years.

:However, let your content dictate your presentation.

==Material from External Sources==

*Do not copy and paste material from sources, as most sources are generally copyright (and the use of copy and paste is not recommended, anyway). Also, do not copy from the Wikipedia, as the GFDL and the CC licenses (the latter being the license of this site) are incompatible.
*Incorporate license-compatible material where necessary and appropriate. Edit such material to make it correct and up to date rather than blindly copying and pasting.
*You should always cite your sources. Make a little section at the bottom (something like <nowiki>==Sources==</nowiki>) and put sources at the bottom (using bullets, i.e. <nowiki>*source</nowiki>).

LQWiki:Manual of Style

2004-03-21T23:38:53Z

Ugen64: edits

This '''manual of style''' is meant to serve as a guideline to help ensure that LQ Wiki articles have a consistent look and feel. It is just a guideline, but consistency will make the wiki easier to read, easier to use and easier to contribute to. Clear, informative and unbiased writing is always more important than presentation and formatting. Remember, one of the great things about a wiki is that perfection is not required. Don't let this article stop you from [[LinuxQuestions.org_Wiki:plunging forward|plunging forward]]. Other wiki users will find your article when [[LinuxQuestions.org:weeding|weeding]] and all
articles should gradually reflect this guide.

The emphasis of this manual is more on explaining what to do, and less on how to do it. For instructions explaining how to markup your contributions, see the [[LinuxQuestions.org_Wiki:Wiki_markup|markup]] guide.

==Mechanics==

===Use Good Spelling and Grammar===

*Spelling and grammar, partly due to the spellchecking defaults and partly due to prevalence, is standardized in the American form. Regarding the spelling of links, redirects may be necessary.
*Spell words correctly. This site includes a spellchecker. Various editors and word processors contain or utilize spellcheckers. Various utilities such as aspell or ispell are available. However, do not let concerns regarding spelling errors prevent you from contributing.
*Use good grammar. Use a grammar-checking program or take other steps to ensure correctness. Again, do not let concerns regarding correctness prevent you from contributing.

===Titles===

*The first instance of the title of the page should be bold. Note the bold "manual of style" at the beginning of this page.

===Links===

*Before creating a new link, first search for it and likely variants. This avoids redundant material, redundant links, or conflicts.
*Link only relevant keywords. Not every possible linkable word needs to be so linked; only those the reader would most likely desire to follow for further pertinent information.
*Links should be on '''Linux''' or general computer topics relevant to Linux, though brief digressions on specifically non-Linux topics may be appropriate.
*Make links in the singular form. Consistency promotes ease of editing. If it is necessary to use the plural form, plural <nowiki>[[link]]s</nowiki> can easily be made and will render as a single highlighted word.
*As of this writing, links are case sensitive. Title/link applications and entities according to their official names (MPlayer, IBM) and, otherwise, the case should be as if it were The Title of a Book. If necessary, in the circumstance of a wrongly or confusingly cased title, supply a redirect.

====External and 'See also' links====

*External links should be formatted as normal when in the body of the text. Additional external links for further research should be placed at the end in a section entitled "External links", using a heading (i.e. <nowiki>==External links==</nowiki>).
*If internal links do not fall within the body of the article, they should be listed in a section entitled "See also" which should come immediately before "External links" (if it exists) or at the end.
*These lists should be bulleted, using single asterisks.
*Short descriptive text should be supplied to replace long or ugly URLs and to simply be more informative. This is done with brackets (i.e. <nowiki>[http://www.kde.org KDE]</nowiki> comes out as [http://www.kde.org KDE]). Additional descriptive text, if truly necessary, can be added to the right of the link (outside the right bracket).



===Markup===

*Use as little HTML (i.e. <nowiki>, , etc.</nowiki>) as possible. A few cases where HTML may be necessary include block quotes, single line breaks, and underlining.
*Do ''not'' indent in order to separate paragraphs or create leading whitespace. It will misformat paragraphs as a single long line in fixed font. To separate paragraphs, simply leave a single blank line between each; to create leading whitespace, use the ':' markup.
* When first expanding acronyms, format it as usual except for bold initial letters. For example: '''GNU''' is a recursive acronym for '''G'''NU's '''N'''ot '''U'''NIX.

===Command Syntax Markup===

*Prefix all commands meant to be performed by an ordinary user with '$' and all command meant to be performed by the super-user/root with '#'.
*Format the names of commands in fixed font with <nowiki><tt></tt></nowiki>


==Style==

===Be Objective===

*First, if in doubt, use ''facts'', not ''opinions''.
**Good: "KDE is one of the most popular desktop managers for Linux." (a fact)
**Okay: John Smith states that "KDE is an awesome desktop manager." (not as good)
**Bad: KDE is the best desktop manager out, everyone should get it! (opinion)
*Second, use what ''specific'' people say, not a general group that you make up.
**Okay: John Smith states that "KDE is an awesome desktop manager." (not as good)
**Bad: Critics say that KDE is a horrible desktop manager. (it's too general: who are critics, why do they say this, do they really say this, etc.)
**Bad: Lots of people think that KDE sucks (how can we tell this is right or wrong? define lots of people)
*People on kde.org are probably going to say that KDE is better than GNOME, and vice versa. Therefore, if you are writing an article about desktop managers, you should attempt to get all points of view (those who like KDE, those who like GNOME, etc.).

===Paragraphs===

*Generally, the first paragraph should contain a few sentences introducing the topic in a general sense prior to expanding on the topic in detail. For example:

::A '''game''' is an object generally used to have fun. Currently, games are one of the most popular forms of entertainment, and have been around for thousands of years.

:However, let your content dictate your presentation.

==Material from External Sources==

*Do not copy and paste material from sources, as most sources are generally copyright (and the use of copy and paste is not recommended, anyway). Also, do not copy from the Wikipedia, as the GFDL and the CC licenses (the latter being the license of this site) are incompatible.
*Incorporate license-compatible material where necessary and appropriate. Edit such material to make it correct and up to date rather than blindly copying and pasting.
*You should always cite your sources. Make a little section at the bottom (something like <nowiki>==Sources==</nowiki>) and put sources at the bottom (using bullets, i.e. <nowiki>*source</nowiki>).

LQWiki:How to edit a page

2004-03-13T02:14:19Z

Ugen64: four quotes dont do anything

You can edit any article in the LinuxQuestions.org Wiki by clicking the '''Edit this page''' link. You'll get a text box with the current contents of the page formatted in [[LinuxQuestions.org_Wiki:Wiki markup|Wiki markup]]. If the page does not exist yet you will be able to create it and the text box will be empty.

You can modify the page ''however you want'', but anything you add ''must'' be compatible with the LinuxQuestions.org [[LinuxQuestions.org_Wiki:Copyrights|copyleft]]. It helps the rest of us if you follow our [[LinuxQuestions.org_Wiki:policies and guidelines|policies and guidelines]] and [[LinuxQuestions.org_Wiki:manual of style|manual of style]], but don't let that stop you from [[LinuxQuestions.org_Wiki:plunging forward|plunging forward]]. It's more important that you add ''something'' than that you do it ''perfectly''.

To see what your changes will look like, hit the '''Show preview''' button, which ''will not save the page''. Do a preview just before saving the page, to make sure your changes look right. When you're happy with the changes, hit the '''Save page''' button to save the page.

You can cancel your edits by clicking the '''Cancel''' link, and of course '''Editing help''' brings you here.

Beneath the article editing text box is a short field labelled '''Summary'''. This is for putting a short note about what you've done to an article, such as "added correct compiler flag" or "spelling 'miserible' -> 'miserable'" or "updated instructions to include new kernel options". It can be helpful for people who are looking at the [[Special:Recentchanges|Recent changes]] or Page history pages to quickly see what you did.

You must be [[Special:userlogin|logged in]] to a [[LinuxQuestions.org_Wiki:How to create a user account|user account]] to edit a page. There will be a '''This is a minor edit''' checkbox for marking your changes as "minor". The idea with this is that people reviewing page history or recent changes can filter out unimportant changes. It's up to you to determine what makes your changes "minor" -- usually, spelling corrections, grammar, or formatting changes are "minor", and changes to the real information on a page are not.

The '''Watch this article''' checkbox puts this article on your watchlist. Any changes to the article, or to the article's talk page, by you or anyone else will show up in your watchlist, so you can keep an eye on the article.

The default setting -- whether these checkboxes are checked or not by default -- can be set in your [[Special:Preferences|user preferences]].

==Some Helpful Commands==

*Repeated single quotes provide emphasis. To end emphasis, use the same number of quotes at the end of whatever you are emphasizing. From least to most: ''Two Quotes'', '''Three Quotes''', '''''Five Quotes'''''.
*Bullets are created by using asterisks (press enter at the end of each bulleted phrase)
*Numbered lists are created by using the # sign (same as above)
*Indentations (should only be necessary in discussions) are created using colons; see above
*Headings are created by using equals signs: 2 equals signs (before and after) creates the largest headings, five equals signs (and possibly more) creates the smallest.

LQWiki:How to edit a page

2004-03-13T02:13:54Z

Ugen64: some helpful commands

You can edit any article in the LinuxQuestions.org Wiki by clicking the '''Edit this page''' link. You'll get a text box with the current contents of the page formatted in [[LinuxQuestions.org_Wiki:Wiki markup|Wiki markup]]. If the page does not exist yet you will be able to create it and the text box will be empty.

You can modify the page ''however you want'', but anything you add ''must'' be compatible with the LinuxQuestions.org [[LinuxQuestions.org_Wiki:Copyrights|copyleft]]. It helps the rest of us if you follow our [[LinuxQuestions.org_Wiki:policies and guidelines|policies and guidelines]] and [[LinuxQuestions.org_Wiki:manual of style|manual of style]], but don't let that stop you from [[LinuxQuestions.org_Wiki:plunging forward|plunging forward]]. It's more important that you add ''something'' than that you do it ''perfectly''.

To see what your changes will look like, hit the '''Show preview''' button, which ''will not save the page''. Do a preview just before saving the page, to make sure your changes look right. When you're happy with the changes, hit the '''Save page''' button to save the page.

You can cancel your edits by clicking the '''Cancel''' link, and of course '''Editing help''' brings you here.

Beneath the article editing text box is a short field labelled '''Summary'''. This is for putting a short note about what you've done to an article, such as "added correct compiler flag" or "spelling 'miserible' -> 'miserable'" or "updated instructions to include new kernel options". It can be helpful for people who are looking at the [[Special:Recentchanges|Recent changes]] or Page history pages to quickly see what you did.

You must be [[Special:userlogin|logged in]] to a [[LinuxQuestions.org_Wiki:How to create a user account|user account]] to edit a page. There will be a '''This is a minor edit''' checkbox for marking your changes as "minor". The idea with this is that people reviewing page history or recent changes can filter out unimportant changes. It's up to you to determine what makes your changes "minor" -- usually, spelling corrections, grammar, or formatting changes are "minor", and changes to the real information on a page are not.

The '''Watch this article''' checkbox puts this article on your watchlist. Any changes to the article, or to the article's talk page, by you or anyone else will show up in your watchlist, so you can keep an eye on the article.

The default setting -- whether these checkboxes are checked or not by default -- can be set in your [[Special:Preferences|user preferences]].

==Some Helpful Commands==

*Repeated single quotes provide emphasis. To end emphasis, use the same number of quotes at the end of whatever you are emphasizing. From least to most: ''Two Quotes'', '''Three Quotes''', ''''Four Quotes'''', '''''Five Quotes'''''.
*Bullets are created by using asterisks (press enter at the end of each bulleted phrase)
*Numbered lists are created by using the # sign (same as above)
*Indentations (should only be necessary in discussions) are created using colons; see above
*Headings are created by using equals signs: 2 equals signs (before and after) creates the largest headings, five equals signs (and possibly more) creates the smallest.

LQWiki:Manual of Style

2004-03-13T02:10:14Z

Ugen64: some formatting tips

GCC

2004-03-13T02:07:51Z

Ugen64: fmt

The '''GNU Compiler Collection''' (formerly the '''GNU C Compiler''') contains a [[compiler]] for the most popular languages: [[C]], [[C plus plus|C++]], [[Objective-C]], [[Java]], and [[FORTRAN]], among others. By default it installs front-ends for all of the languages, however, if you only want to install some of the front-ends use the configure option:

--with-languages=languages.

===See also:===
*[[ld]]
*[[Library-related Commands and Files]]

===External links===
*[http://www.gnu.org/directory/gcc.html Official Website]

User talk:AaronPeterson

2004-03-13T02:05:13Z

Ugen64: oops wrong word

how the heck does this work?

it doesn't refresh!

It doesn't notifiy me that somebody has sent me a message!

:What exactly are your problems? I don't really understand what you meant on my userpage... [[User:Ugen64|ugen64]] 21:04, Mar 12, 2004 (EST) (sign your name with 4 tildes, i.e. <nowiki>~~~~</nowiki>)

User talk:AaronPeterson

2004-03-13T02:04:58Z

Ugen64: hmm?

LQWiki:Manual of Style

2004-03-12T22:26:03Z

Ugen64: grr... stupid equals signs

LQWiki:Manual of Style

2004-03-12T22:25:49Z

Ugen64: wow, i can't even make proper headings

LQWiki:Manual of Style

2004-03-12T22:25:17Z

Ugen64: added links

LQWiki talk:Manual of Style

2004-03-12T22:20:53Z

Ugen64:

== Create or Die ==
OK, that's a little extreme, but... We need more than exists here. Someone '''must''' come up with guidelines for this page, and it must be featured prominently somewhere! I reccomend importing one based on Wikipedia's Manual of Style, or something to that effect. (stuff like Explain Jargon, sensible article naming conventions... stuff to that effect. - [[User:Fennec|Fennec]] 22:46, Mar 6, 2004 (EST)
----
Well?! *cries*

[[User:EvilSporkMan|EvilSporkMan]] 21:58, Mar 6, 2004 (EST)

----
The style manual is definitely a top priority. I am looking for suggestions on the mailing list and wouldn't mind a few volunteers to help!

--jeremy

:Well, I decided to be bold and made a few sections :-). Hope you don't mind. [[User:Ugen64|ugen64]] 17:20, Mar 12, 2004 (EST)

LQWiki:Manual of Style

2004-03-12T22:19:14Z

Ugen64: gee, fixed my headers

LQWiki:Manual of Style

2004-03-12T22:18:51Z

Ugen64: started

User:Ugen64

2004-03-12T22:03:20Z

Ugen64: edited

I'm '''Ugen64''', a [[Fedora Linux]] user and an administrator (sysop) at [http://www.wikipedia.org Wikipedia, the free encyclopedia]. I am also an administrator at this website.

Talk:C plus plus

2004-03-12T03:42:26Z

Ugen64:

re: having the page ''actually'' called '''C++''', <tt>%2B</tt> doesn't seem to work.

what about just making a link to [[C++]] and clicking on it?

answered my own question...

[[User:Marcel|Marcel]] 21:22, Mar 6, 2004 (EST)

:Yeah, there's apparently some thing in the Wiki code that doesn't allow pluses in article titles. It's rather annoying. [[User:Ugen64|ugen64]] 22:42, Mar 11, 2004 (EST)

C plus plus

2004-03-12T03:41:45Z

Ugen64: added some stuff

==Introduction==

'''C++''' is a very popular programming tool (an extension of the original [[C]]) that is almost exclusively used to program many of [[Linux]]'s core programs. [[Perl]], [[Java]], and [[Python]] are some of the other popular programs. It is object-oriented.

==History==

(Feed me)

==Language Features==

(Feed me)

==Examples==

(from [[Wikipedia:Hello world program]])

#include <iostream>

int main() {
std::cout << "Hello, world!" << std::endl;
}

This displays the phrase "Hello, world!" on the screen, similar to the simpler shell command "echo Hello, world!" used in the Linux console.

==Further Reading==

===Wiki pages===
*[[C plus plus tutorial|Tutorial]]
*[[C/C plus plus tips|Tips and Tricks]]
*[[C plus plus practices|Good Programming Practices]]
*[[C plus plus tools|Linux C++ tools]]

===Books===
*''The C++ Programming Language'', Bjarne Stroustrup 
*''Effective C++: 50 Specific Ways to Improve Your Programs and Design'', [http://www.aristeia.com/ Scott Meyers] 
*''Code Complete'', Steve McConnell

===External links===

''This article is a [[LinuxQuestions.org_Wiki:stub_articles|stub]] and needs to be finished. [[LinuxQuestions.org_Wiki:plunging_forward|Plunge forward]] and [[LinuxQuestions.org_Wiki:How_to_edit_a_page|help it grow]] !''
 

See also: [[C]], [[C/C_plus_plus tips|C and C++ tips]]

Tux

2004-03-12T03:38:45Z

Ugen64: made the link into its own section

'''Tux''', a penguin, is the official mascot of [[Linux]]. It was originally thought of by [[Linus Torvalds]], the programmer of the Linux kernel, who was bitten by a pygmy penguin in [[Australia]] and developed penguinitis. He dreamed of a penguin stuffed on herring (as opposed to a randy penguin), and this ubiquitous mascot lives on.

==External links==
*[http://www.isc.tamu.edu/~lewing/linux/ Some pictures of Tux]

Spreadsheet

2004-03-12T03:35:08Z

Ugen64: edits

A '''spreadsheet''' program is used to facilitate the presentation and computation of data that contains numbers. Normally, spreadsheets are created for financial statements, budgets, report cards, etc. where the numbers can be edited with the formulae (such as averages and totals) in the spreadsheet recomputing automatically each time changes are made.

The earliest successfull spreadsheet software was Visicalc, followed by the venerable Lotus 123. Borland also joined the fray with its Quattro Pro. Microsoft Excel is now by far the most advanced spreadsheet program (but available mainly on [[Windows]]) but open source efforts such as [[OpenOffice.org]] and [[KOffice]] are catching up. OpenOffice's spreadsheet program, OpenOffice Calc, is one of the most popular spreadsheet programs on [[Linux]] distributions.

Nowadays, spreadsheet programs are usually bundled into [[Office_Suite]]s.

User:Ugen64

2004-03-12T03:33:37Z

Ugen64: added

I'm '''Ugen64''', a [[Fedora Linux]] user and an administrator (sysop) at [http://www.wikipedia.org Wikipedia, the free encyclopedia]. I have also been recently contacted and (probably) been made an administrator at this website.

Cdrecord

2004-03-12T03:31:23Z

Ugen64: created stub

'''cdrecord''' is a cd burning console command and arguably the most popular tool used to burn CDs (with the possible exception of some user-friendlier, front-end tools). However, a certain amount of knowledge is generally required in order to burn CDs (generally using [[ISO]]s).

Burning a CD

2004-03-06T15:51:49Z

Ugen64:

In [[Linux]], the easiest way to burn a CD is through the command line:

cdrecord

with some additional lines will burn one effectively. For a complete guide, see [http://www.troubleshooters.com/linux/coasterless.htm Coasterless CD Burning].

Microsoft Windows

2004-03-06T15:48:31Z

Ugen64: redirect

#REDIRECT [[Windows]]

Opera

2004-03-06T15:48:15Z

Ugen64: edits

'''Opera''' is a light-weight but fully featured web browser available for multiple platforms including: [[GNU/Linux]], [[MacOS]], [[Microsoft Windows]], [[QNX]], [[FreeBSD]], [[Solaris]], and [[BeOS]]. It features tabbed browsing, integrated pop-up blocking, advanced cookie management, support for Netscape plug-ins, Java, etc. Although it is not open source like Mozilla, Opera has an excellent track record for security and support.

*[http://www.opera.com Opera official website]

Fedora Linux

2004-03-06T03:53:46Z

Ugen64: redirect

#REDIRECT [[Fedora]]

Fedora

2004-03-06T03:51:33Z

Ugen64: links

'''Fedora Core''' is the new name for the Red Hat Linux (RHL) series of distributions. Once RHL reached version 9, [[Red Hat]] decided that it was time to split their core product into two directions:

* ''Fedora'', which would become a community-developed cutting edge R&D distro where the latest and greatest Linux technologies would appear first. It focuses on the hobbyist and developer desktop (ie desktop Linux). An operating system built exclusively from free software and is available for free download.
* ''Red Hat Enterprise Linux'', which is a less cutting-edge, more stable, better supported version of Linux based on snapshots of Fedora taken every so often (typically once every year or so). An operating system that is not free but is available at a cost of over $150.

Fedora continues Red Hat's tradition of building a super-modern, if slightly unstable, Linux desktop, and it is extremely popular. An excellent distro for newbies, as long as they're willing to rough and tumble it with the Linux developers.

*[http://www.fedora.us Fedora Linux Home Page]
*[http://fedora.redhat.com Fedora Core download page]
*[http://www.fedoranews.org FedoraNEWS.org].

Mac OS X

2004-03-06T03:50:41Z

Ugen64:

'''Mac OS X''' is the latest iteration of the [[Mac]] [[Operating system]] by [[Apple]]. It is derived from [[BSD UNIX]], and as such is much closer to [[Linux]] than [[Windows]]. In fact, lots of Linux software will compile and run on Mac OS X, including the X Window Server.

GNU

2004-03-06T03:49:36Z

Ugen64: quotes, link

'''GNU''' is a recursive acronym that stands for '''GNU's Not [[Unix]]'''. It is a project to develop a feature-complete implementation of a Unix system, whose source code would be completely [[Free]]. Many of the GNU system's core tools are used by Linux; this has led some people (notably [[RMS|Richard Stallman]] and the [[Debian]] project) to refer to the system as "GNU/Linux".

One of the most important contributions of the GNU project is not software, but a license for distributing free software, the GNU [[GPL]] or General Public License. The Linux kernel is released under this license, as is much of the crucial software in any Linux distribution.

*[http://www.gnu.org Official website]

User talk:Ugen64

2004-03-06T03:48:14Z

Ugen64:

This is [[User:Ugen64|ugen64's]] talk page!

Tux

2004-03-06T03:47:03Z

Ugen64: created

Linux

2004-03-06T03:44:50Z

Ugen64: edits

'''Linux''' is a [[kernel]], the heart of the [[operating system]] sometimes called [[GNU/Linux]]. It was initially programmed by the famous Finnish programmer, [[Linus Torvalds]] and was first released in 1991. Nowadays the kernel is being developed by a mass of developers all over the world.

*[http://www.kernel.org The Linux Kernel Project]

Windows

2004-03-06T03:43:37Z

Ugen64: edits

'''Microsoft Windows''' is an operating system, and the only serious competition for [[Linux]] on desktop machines ([[MacOS]] is limited to proprietary hardware and as such doesn't really compete).

Windows has a large user base - over 95% of the worlds desktop computers use some form of it. Being compatible with Windows takes a significant amount of manpower from the open source movement. However, a large minority of servers use UNIX and/or Linux, and with Microsoft's questionable practices, the open source movement is undoubtedly growing.

OpenOffice

2004-03-06T03:42:12Z

Ugen64: edits

'''OpenOffice.org''' is both an Open Source product and a project. The product is a multi-platform office productivity suite. It combines the key desktop applications, such as a word processor, spreadsheet, presentation manager, and drawing program, with a user interface and feature set similar to other office suites. Sophisticated and flexible, OpenOffice.org also works transparently with a variety of file formats, including those of Microsoft Office.

Available in 25 languages with more being constantly added by the community, OpenOffice.org runs stably and natively on [[Solaris]], [[Common_Questions_and_Misconceptions#Q:_What_is_Linux?|Linux]] (including PPC Linux), and [[Windows]]. Additional ports, such as for FreeBSD, IRIX, and Mac OS X, are in various stages of completion.

Written in C++ and with documented APIs licensed under the LGPL and SISSL Open Source licenses, OpenOffice.org allows any knowledgeable developer to benefit from the source. And, because the file format for OpenOffice.org is XML, interoperability is easy, making future development and adoption more certain.

*[http://www.openoffice.org/ The OpenOffice.org homepage]