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.
Hey, Pat! Hope I didn't cause you grief and a full
Inbox over my suggestion to "email you..."
It's amazing to see this gregarious community so
passionate over Slackware Linux! I appreciate what
Really -- a lot of people say that Slackware is pointlessly hard. Really? So is a spoken language. Perhaps we should all go back to grunting and creating cave drawings.
Any time there is a learning curve, there is a proportional reward. Eventually it becomes more straightforward without the training wheels (though the training wheels are great for market share grab).
As someone studying Chinese, it does remind me a lot
of my few years relentlessly "wrestling Slackware to
the blood," as Tinkster said. There is a certain sense
of accomplishment when you can actually use something
that some people tout as "pointlessly hard".
Now that you and Eric and Tinkster and others have been
helping me with Slack for close to 5 years, the knowledge
gained is well worth climbing the learning curve.
Face it -- I would have been burned at the stake for a sudden change to ANY of these proposed new logos. I think it's the nature of the Internet. It is obvious that the Slackware community has grown attached to the traditional Slackware logo, and so have the Slackware developers. I guess it must be a good logo that does reflect the simple, no-nonsense Slackware approach. We don't need a GUI that limits our options, and we don't need a primary logo that is hard to read, either. Really -- a lot of people say that Slackware is pointlessly hard. Really? So is a spoken language. Perhaps we should all go back to grunting and creating cave drawings.
I must say -- out of all of the proposed replacement logos posted here, I like Bruce Hill's logo #1 the best.
I agree, and thank you Mr. Volkerding, it's great to see the old logo back up there
But, which one is Bruce Hill's logo #1 ? He never posted one.
Distribution: Slackware64-current on Thinkpad Carbon X1
Originally Posted by volkerdi
Face it -- It is obvious that the Slackware community has grown attached to the traditional Slackware logo, and so have the Slackware developers. I guess it must be a good logo that does reflect the simple, no-nonsense Slackware approach. We don't need a GUI that limits our options, and we don't need a primary logo that is hard to read, either. :-)
There are a lot of people who thought that from day one. It is always nice to see that change can take place if a group is not happy with something. Most developers would have said "deal with it" etc. Makes me proud to be a slack user.