Mad Penguin Launches Slackware Handbook Project

An anonymous reader writes "Mad Penguin's Adam Doxtater and Narayan Newton have launched a community-driven site dedicated to bringing the power and depth of the FreeBSD Handbook to Slackware Linux users. The site allows for the community to create and edit its own content. A simple voting system is in place to make sure the content that makes it into the handbook is of the highest quality. This is something that has been needed for some time and the idea of being able to edit our own material is really nice. A very unique project. Read the press release at LinuxPR.com."

link to the handbook

[Anonymous Coward]

why wasn't it in the main article?

http://www.slackersbible.org/

btw. first post

Re:link to the handbook

[Anonymous Coward]

Clicky [slackersbible.org]

why?

[darthpenguin]

There is already an ongoing project updating the official slackware book at http://slackbook.lizella.net/ [lizella.net]. For the most part, this work provides most information about daily admin tasks that anyone would need. Why is there this new project, then?

Good Luck!

[Alan Hicks]

Let me be the first to wish them the best. I've been putting together a little "handbook" of my own (not nearly as ambitious as mimicking the excellent FreeBSD handbook, of which I own a hard copy incidently). Of course, anyone is free to contribute provided they license their writing under the GPL for inclusion. Basically it's a rewrite of the Slackware Linux Essentials book by Chris Lumens, Logan Johnson, and David Cantrell. You can find it here [lizella.net]. I call it "The Unofficial Revised Slackware Book Project". Stop by and take a look, I think you'll enjoy it.

Props to these guys and their project, and I'd like to point out to them that can use anything at the above site provided they do so under the GPL.

OK, I will place my fot in my mouth..

[stephenisu]

OK it is similar to a wiki mixed with slashdot.

So much so that well... they said it best.

"Think of it as a wiki of sorts. All of the contributors are capable of editing and adding to the work of others on the project." said Doxtater, "This will ensure that the documentation is of the highest standard". Mad Penguin says that the new site is currently in operation and ready for the general public.

Re:why?

[MadRaVen]

We started work on this before we knew about that. However, we don't see the two projects as being in conflict. This is more of a community type thing and the goal is to replicate the FreeBSD Handbook, which is quite a bit bigger then the Slackware Book. Our content is all under the BSD license, so the Slackware Book can use it. We arn't trying to steal their thunder or something like that.

And there's the FreeBSD wiki

[Anonymous Coward]

The FreeBSD handbook rules. But there's also the FreeBSD Wiki: FreeBSD wiki [tehinterweb.net] Which certainly needs more members.

Love the FreeBSD Handbook

[CypherXero]

I love the FreeBSD Handbook, it's an amazing guide to help get the system up and running. I got FreeBSD 5.3 + X11 + Xorg + Gnome2 compilled and installed in less than 24 hours. (total work time was around 5-6 hours)

Re:why?

[Alan Hicks]

We started work on this before we knew about that. However, we don't see the two projects as being in conflict.

Of course they're not at conflict. At worst it's only healthy competition, like a sports game.

This is more of a community type thing

Personally I found it very difficult to get the community involved in documentation, and most of the "New Good Book" has been of my doing when my time is available.

the goal is to replicate the FreeBSD Handbook, which is quite a bit bigger then the Slackware Book.

And covers a lot more topics. My project is mainly designed to be a good introduction into Slackware Linux, teach people enough about the system to get it up, running, online, and understand the basics of linux in general and Slackware in particular. It isn't meant to be as indepth as what you're starting. Drop me a line sometime though, as I'd love to work together. Nothing like pooling resources to tackle big problems.

Our content is all under the BSD license, so the Slackware Book can use it.

I wish I could do the same. I typically prefer the BSD license for most things. I spoke with Pat recently about possibly migrating the Slackware Linux Essentials book to the Apple Common Documentation License (which is basically the GPL only tailored for documentation), but as he explained it to me the copyright was never transfered to him, so ATM I'm stuck with the GPL, which is fine by me of course.

We arn't[sic] trying to steal their thunder or something like that.

You gotta watch out for those when you're doing documentation! :^)

CMS...

[xeon4life]

The site allows for the community to create and edit its own content. A simple voting system is in place to make sure the content that makes it into the handbook is of the highest quality. This is something that has been needed for some time and the idea of being able to edit our own material is really nice. A very unique project.

Actually, it's not unique.

The content mangement appears to be Drupal [drupal.org] with a modified Marvin 2k [drupal.org] theme.

Drupal has had these features forever.

Move along now.

Re:slashdotted

[MadRaVen]

Someone set mysql to accept only 100 connections.....should be fine now

Re:Not true..

[todesengel]

This is definately a project I would like to see some press behind, it is far from "unique." Slackwiki [slackwiki.org] has been around for quite a while.