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.
I admit I do that too, from time to time. It's a bit like driving my super-robust-and-reliable 750 BMW motorcycle every day... and then from time to time there's this shiny Kawasaki 750 GPZ Turbo in my pal's garage, almost unusable for everyday work, but hey what a feeling when you drive this thing at night on a South French motorway and the exhaust is so hot it begins to glow.
I just hope Slack continues to offer a non-systemd version. While I don't buy into all the conspiracy nonsense, I do in fact dislike it & don't want it for both ideological and technical reasons. I don't like having my arm twisted into using something, be that Metro OR by creating platform API inter-dependencies. I'm not 100% sure if abandoning POSIX is a good idea when some compatibility is there between things like OSX & Linux. I don't want a PID1 that carries the whole system on it's shoulders. Imagine, "Linux updates have been installed, you must restart your computer for them to take effect."
Anyway, I'm not mad or hateful or anything. I think the systemd guys might be trying to make things better in their own way, but I just don't agree with their direction. At least their stuff is GPL and sooner or later someone will come along and tear it apart to make it more modular.
I've used FreeBSD, and tried OpenBSD and NetBSD time to time. I've seen technical differences that could be worth at time to choose depending on the use you want to give to the OS.
I've tried Fedora, Suse a few times. I've tried Ubuntu time to time (just to evaluate the "converting friends" issue). I've used Mandriva, Gentoo, Debian, Slackware, Crux. The only difference between Linux distributions I've observed has been how their maintainers complicate things trying to help. The less the better.
By the way. I'd really thank someone here to write a complete tutorial about successfully converting Windows users to Linux. Taking in care the effect of "popularity" over all, include please a careful explanation of why that could mean a real benefit for everyone in the long term.
Distribution: Slackware has beern Main OpSys for decades while testing others to keep up
Originally Posted by tronayne
I've converted a few Windows Weenies to Linux (yeah, Slackware) and they're all happy campers.
I can see no reason whatsoever to dabble with other distributions.
I stopped converting Windows users unless they ask about Linux first and then I qualify them carefully. Some drivers will never also be mechanics.
However I dabble in other distros for various reasons. Early on, when we had to setup most hardware manually, it was instructive to see how "automatic" distros did it on my box. These days I do it so I can speak intelligently to other Linux users who grew on and use auto dependency resolving distros and who think Slackware is "old and too much time-consuming work". I'm vastly more interested in converting other distro users to Slack than Windows user to Linux.
I was rooting through some old stuff and found a Slackware 7.x CD. I never actually used it, I didn't really get into Slackware until version 9 came out, which was about ten years ago. Love at first sight. I no longer use windows for anything except for a few games. I'm a software developer, and I do everything on Slackware. Our app servers and web servers and fax servers are all Slackware. We did have Ubuntu servers, and I won't get into a this-is-better-than-that debate, but switching from Ubuntu to Slackware solved several problems.
I used KDE until version 4.x came out. IMNSHO they ruined KDE, and I switched to xfce. Never looked back. If I wanted bloat and eye candy, I would use Windows. I don't, and I don't.