You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!

Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.

If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.

Having a problem logging in? Please visit this page to clear all LQ-related cookies.

Introduction to Linux - A Hands on Guide

This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.

I agree with previous comments about the documentation, wikis, etc being too spread out over the internet. It would be nice to have an updated slackbook/slackwiki directly on slackware.com. This seems much more like our responsibility than the official Slackware team as they have plenty on their hands.

Personally, I would agree to help if this won't be another slackwarehowto.something.net, but the conglomeration of all sources and officialy approved by Pat or Slackware Team (whoever it consists of).

I hope you all know freebsd handbook. One of the greatest manuals ever (and not only for freebsd, but for whole *bsd oses and more). I wish Slackware could have smth similar. Because Slackware is the most Unix like system there (please don't argue with me), it should have such type of handbook just because lots of things written here also applies to other distros most often without problems. Once RedHat was thought as the classic and the only one reliable GNU/Linux (I still have some of those old manuals), but these times are over. Constant patching doesn't increase system compatibility.

What I wanted to say, that Slackware book would/should apply to most GNU/Linux distros.

I hope you all know freebsd handbook. One of the greatest manuals ever (and not only for freebsd, but for whole *bsd oses and more). I wish Slackware could have smth similar. Because Slackware is the most Unix like system there (please don't argue with me), it should have such type of handbook just because lots of things written here also applies to other distros most often without problems. Once RedHat was thought as the classic and the only one reliable GNU/Linux (I still have some of those old manuals), but these times are over. Constant patching doesn't increase system compatibility.

What I wanted to say, that Slackware book would/should apply to most GNU/Linux distros.

End of rant...

Even though this isn't the case I still refer some linux newbies to the slackbook because it does offer some good linux basics.

As a newbie in the linux world, I've been facing some tough time finding information in a reliable and structured way.
Thanks to:

Many folks in this forum

Hours in front of the computer

tons of creativity in finding excuses to "dodge" angry wife...

, my "slack life" became a lot easier.

The idea of creating a centralized (reliable, oficial, constantly updated) pool of knowledge (be it a book, bible, wiki or whatever) would definitely help bringing in more and more users, and I would think that popularity won't really hurt in this case. Having such knowledge available in one place would make Slackware less scary to the average user.

I would also like to see an "official" port to AMD64 architecture. Last time I checked, SLAMD64 was still on v11...

If this idea moves forward, I would also like to somehow contribute to the project(even being a newbie - but that won't last forever!)

The idea of creating a centralized (reliable, oficial, constantly updated) pool of knowledge (be it a book, bible, wiki or whatever) would definitely help bringing in more and more users, and I would think that popularity won't really hurt in this case. Having such knowledge available in one place would make Slackware less scary to the average user.

If this idea moves forward, I would also like to somehow contribute to the project(even being a newbie - but that won't last forever!)

Hey, already on the third page and no-one has suggested suspend to ram/disk? I'm a laptop user, and I'd like to see both suspend and networkmanager in Slackware. I haven't tried using (k)networkmanager, as the compile seems quite some work, but I did compile s2disk and friends, and it works quite nicely.

I concur, with updating the Slackbook. I personally don't have the time or the knowledge to help that project all that much... but I would gladly buy a copy of it and/or donate to the project. I have a copy of the slackbook sitting right next to me and it is a great read, but it would be nice for it to be updated for v12.

Agreed. Some things are better left out. Fancy that, we have a package manager and can install them on our own with a whole whoppin' one line command! Much appreciation goes out to people who manage these packages so this is possible.

As far as the documentation, what would be the first step to get it moving in the right direction- towards having a centralized Slackware Bible similar to the BSD manual mentioned earlier?

There's not much that I'd like to see in Slackware that's not there already. If there's a particular application that I really want, I typically build it myself using a SlackBuild script from SlackBuilds.org, or use src2pkg.

I'd like to see src2pkg officially included in the distribution, replacing checkinstall if necessary. I'd also like to see Emacs 22 instead of Emacs 21.

Other than that, an update and expansion to the Slackbook would be helpful. I'll see what I can do to help.