Table of Contents
News from the site admins
Knowledge is power. Scattered and unfocused power is useless. To state it plainly, the vision and the ultimate goal of the Slackware Linux Documentation Project is to become the primary worldwide resource for all Slackware related information. This is a lofty goal, indeed. However, there is confidence that venerable Slackware Linux, the oldest actively maintained distribution of GNU/Linux, has the user base to accomplish this goal. You are invited to join and be a partner in this endeavor.
Who can help? Anyone can, from your uncle Ed who tinkers with Slackware on his old laptop to Linux gurus with development level skill sets. All are welcome. All can contribute something of value to this project. A wiki type resource such as this thrives on community. You've seen for yourselves what the GNU/Linux and Open Source communities have done in the past and are still doing today. Working together, the potential for success is greatly increased.
This project will need article submissions that run the entire gamut of Slackware knowledge. There will be a need for serious technical articles on hardware control, software applications, Slackware Linux implementations in business and personal computing, system administration, etc. Articles will also be needed from the every day Slacker on topics ranging from simple howtos to complicated resolutions and workarounds.
Submitted articles, as with most wiki type resources, will be peer reviewed. Corrections may be needed, amendments added, and so forth. No article should be deemed unimportant. If it has relevance to Slackware Linux and will assist someone somewhere to better utilize this operating system, then it is a worthwhile article. What is being done here is being done for others. This is an archive of knowledge being built for the future. Your participation will be the mortar that holds the bricks in place.
In order to fulfill the goals of this project, a reliance on civil discourse and the presence of a strong spirit of cooperation will be necessary. The rules here are simple. Be kind and considerate in your dealings with others. This project is not about individuals. It's about a community sharing and working together toward a goal. Your ego will not be a part of the Slackware Linux Documentation Project. Please leave it in the coat closet by the front door before you login.
That is the our contract with one another and with the future.
The choice of software
This Wiki runs the DokuWiki software. This choice was made by the initiator of the project, Alien BOB. Basically when setting up a serious wiki there are two choices: MediaWiki and DokuWiki. Alien BOB has extensive experience with both - running DokuWiki for his own Slackware knowledgebase, and running a MediaWiki based knowledgebase for the customer Helpdesk of which he is the teamleader.
The choice for DokuWiki was made for several reasons; its syntax makes it more suitable for writing documentation as opposed to MediaWiki, which is more general-purpose. Also, DokuWiki is self-contained in a single directory and does not require an SQL database, which makes it highly portable (the intention is to make a “daily snapshot” tarball available for download once the Wiki foundation is complete). The DokuWiki also allows the use of Access Control Lists - a quality control measure which will be implemented after the formation of a proper team of editors (those who are going to be responsible for having high-quality texts while you, the authors, are responsible for the technical content).
The Wiki's functionality has been extended with several syntax plugins, which you will find listed at the bottom of the Wiki syntax page. You can follow the links for those plugins if you want to learn what they allow you to do when writing an article.
The artwork used at the moment was created by asteroid who has some more examples of nice graphics on his own user page.
The admins asked (and received permission) from Patrick Volkerding to use these modifications of original Slackware artwork here on the Wiki.
To the left of the page you will find a sidebar with several boxes which can be edited (by the admins). Only the “toolbox” box is part of the wiki's monobook template, and can not be modified. More specifically,modifying the content of that toolbox would make future upgrades a pain.
If you have suggestions about entries which should absolutely be in one of those boxes, let us know (use the discussion page).
Even though this documentation site has a hostname in the slackware.com domain, that does not mean it is a Slackware-controlled or sponsored project. The use of the domain name is a token of approval, rather. Also, the project was bootstrapped by Alien BOB, a Slackware coreteam member.
The content of the Wiki will not be controlled by ”higher powers”. The content on any page in this wiki is determined by its author(s) and contributor(s).
The core structure of the Wiki will be maintained by the site admins. That means: namespaces, visual identity, access controls and the like. It also means that the namespaces ”slackware:”, ”slackdocs:” and ”slackbook:” are read-only for everyone except the editor/admin team.
Ideas for changing the core structure of the Wiki can be submitted through our mailing list ( http://lists.alienbase.nl/mailman/listinfo/slackdocs) or by editing the discussion page. The actual content is all up to you! We are open to good ideas for enhancement of the existing structure and content, and will not refuse any article in the ”howtos:” section.
[Not implemented yet]
Our goal is to give you total creative freedom when writing content for the Wiki. But for the sake of quality assurance, we ask you to co-operate with one of our editors.
He or she may be able to offer suggestions about tags to use in your article so that it gets properly listed in the TOC. We also have tag categories that allow you to indicate your article applies to certain versions of Slackware only. You get the idea? You can also discuss an appropriate namespace to put your article in (consider a namespace as a wiki equivalent of a subdirectory - actually that is how it is implemented in the server's filesystem). The editor's primary role is to advise you on the structure of your article, ensure that it looks good, uses well-formed sentences - essentially that what any book editor would also do for you. You (the author of the article) will remain in control over the technical content! The editor will not enter into discussions about the (technical) content of your article, unless he spotted blatant errors of course. We assume that since you wrote it, you know better what you are talking about than do we…
In order to assist the editor with his work, the Wiki implements a mechanism of “publishing a page”. This means that the creation of a new page, or editing an existing page, will automatically put that page in “Draft” mode. The “Draft” message will be prominently visible on the page. If you are editing an existing page, then the original (approved) page will remain be visible to visitors of our Wiki. Only the registered users of the wiki (i.e. your fellow authors) will be able to see the draft instead of the approved version.
You have to consult one of our editors to get your page revision approved. That action will make it visible to the world.
Respect other people's work
Whenever other people's content is copied into this Wiki, any license and copyright terms which are applicable to the original content will be respected.
The name of the original author(s) as well as the originating URL have to be mentioned in the footer of your (possibly modified) copy of that content.
The content of this wiki is published under a liberal “Creative Commons” license: CC Attribution-Share Alike 3.0 Unported . Take this into consideration if you intended to publish copyrighted information here.