SlackwareThis Forum is for the discussion of Slackware Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
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.
Click Here to receive this Complete Guide absolutely free.
There's no compareing Slack to drake, Lyc or other user friendly slick installs you sacrifice power pure unbridled power for that slick install those kind of distros provide (which are built for max compatibility instead of power and tweeking).
package installation is pretty simple I get my packages from www.linuxpackages.net and use $installpkg programname* to install them. Programs that I compile from source usually do so flawlessly.
I'm unable to compare to Debian because attempts to install Debian have always ended in frustration for me.
I have read that Slack is the most "unix like" of the Linux distros which seems to be a good thing so far as all information in my "Running Linux" and "LInux Desk Reference" books have been useful and applicable. (those books tend to call Linux "Unix" in them despite the title).
1) Slackware is the one true distro
2) You will learn more about linux from slackware than from any other distro
3) Slackware is the one true distro
4) There is only one distro
5) Slackware is the one true distro
I'm wonderin why nobody mentioned that Slackware is the 1 true distro?
banana, if you are happy with what you've got, then don't worry about switching. However if you are displeased with something, and are curious if Slack is more of what you want, then load it up. Give it a run for it's money, and see for yourself if there are 5 reasons to use it (or Gentoo).
Distribution: Customised Slackware64-14.1 with multilib
I think "banana2" wants to know specifics about the Slack packaging system. The main point of contention about the Slack packaging system is a lack of dependency checking. It does, however, support "compulsory", "recommended" and "optional" tagging. One could argue that this puts the power in the hands of the user, specifically when one installs in "expert" mode. A new user would have no business installing in "expert" mode, so the issue of dependency checking becomes a moot point. However, after some time that same user will get to know what package requires what. As your knowledge of Slackware grows, so does your knowledge of Linux, not the other way around. This is how things are meant to be (IMHO).
I have had some exposure to Debian, and I have to say it has a sane installation that cushions the user more than Slackware does, PROVIDING the instructions and steps are all followed. Woe betide the user that skips a step in a Debian installation. There are two major drawbacks that counter Debian's stability (which is by no means superior to Slackware): The first is the excessive feature-freeze policy. Since Debian is not tied to the x86 or even the Linux kernel (it can use HURD instead), the feature-freeze applies to packages even if a vulnerability or bug does not affect the x86 platform. The second problem I have with Debian my be due to my own ignorance =-]. Ever tried finding the NAME of a package based on some missing header file when compiling a source package? apt-get has no search functionality, so you have to go through dpkg, which can be a challenge to use when caffeine levels are low ;-p. Certainly, apt-get is a major feature of Debian, and I hope that autopkg will one day rival it.
In summary ;-p, Slackware == Freedom. Freedom to hang yourself, you bet, but if you are not averse to reading some documentation that freedom will spoil you so much that you'll feel limited if you have the misfortune to have to use any other distro (usually to fix a non-Slack distro of a friends).
Hmmm lets see besides the non-Gui Install interface and slack being the one true distro that is most like unix besides FreeBSD (although I have never used FreeBSD).
I am a linux convert who came from the windows enviroment to linux enviroment in the winter of 2000. I started with RH 6.0 then when RH stopped using a 1.44mb boot image and went to a 2.88mb bot image it made installing on older systems like my Toshiba satellite pro 490cdt sorta difficult with out a floppy drive for that system. So I went to Mandrake and was hapy using it till I found out that Mandrake is no better than MS when it comesto monitoring people and their habits(ie. spyware on their website to monitor how people browse their websites.) So I went to www.distrowatch.com and looked at all 96 flavours of linux their and finally came to Slackware.
Now comeing from RH and MDK I never built anything from source every package I ever installed on those 2 systems where RPM which is nice but not true unix like. If you like RPM's and don't want to lose that ability you can still use RPM's with slack but you have to use
to change it to a slackware package format.
also as stated by others the more about slack you learn the more knowledgeable about linux you become.
I have been using slackware since about fall of 2002 and have loved it.
Hope this helps you in decideing to join us and becomeing part of the Slackware community.
1) The oldest distro---very stable---fast but not bleeding edge
2) Assumes NOTHING---you need to configure what you want--it doesnt even start to gui login
3) Has very bsd style configuration---with very good #'s in config files (truely the best)
4) I have very rarely found something that didnt compile
5) For one cd distro, it is exceptionaly complete
6) The best installer --especially for newbies--it gives you an expert install even if you are a newbie
7) Very good package manager---though few use it because of #4 above
slackware is great... why?
because it is vvvveeerrrryyyyyy stable, verrrrrryyyyyyy powerfull... u can run almost anything on it without glitches...
you also learn the most things from it... even if you'r troubleshooting )
i don't considere changing it for nothing in this world )
I'll give you my one and only reason for preferring Slackware to any other Linux:
Other distros: This Administrator tool requires Guile, this tool requires Perl, this one requires Ruby, this one requires Slang, this one requires Python, this one requires Tcl/TK, this one requires Perl/Tk... Oh, and they're all compiled to require X, GTK and Gnome.
Slackware: Administration means a text editor and an ability to read.