What features/changes would you like to see in future Slackware?
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.
Add OO? Oh god no. Slackware is getting too big already. I'd like to see some stuff removed rather than new stuff added.
A reworking/rationalisation of the disksets probably wouldn't hurt either. Especially so, if it could be done in such a way as to provide an easy way to do a minimal install. Getting rid of the 'n' set and putting the stuff in there in either 'a' or 'ap' as appropriate, would probably be a good start.
The IT guy installs what he is told, or he is not the IT guy for very long.
It is irrelevant anyway because 99% of people use Microsoft Word, we in the Linux world actually have a Word beater, yet a number of people are against it because it weighs in at a compressed 130-150mb that seems to me to be a fatuous argument for not including a piece of software.
The only reasons a bit of software should be included is because it works, it is stable, and it improves Slackware. Given a choice between Koffice and Openoffice I know what I would choose. However this is again irrelevant as the only person who's opinion matters is Patrick Volkerdings.
However I would suggest that he does actually read, and probably laughs, at these threads and if enough people say they want the Slackware logo to be pink then it will be pink, or maybe even readable upside down when rotated.
yet a number of people are against it because it weighs in at a compressed 130-150mb that seems to me to be a fatuous argument for not including a piece of software.
putting it in the distribution means that the people who take care of the distribution will start fielding questions about it, keeping it up to date, handling CVEs, etc. It's a lot of work for a small team. I'd rather that team spend their time figuring out how to get glibc 19.29.21 working and I'll put openoffice on myself, since its trivial to do.
However I would suggest that he does actually read, and probably laughs, at these threads and if enough people say they want...
I'd agree with the above. Pat has been known to make infrequent guest appearances on LQ and I figure he reads a LOT of what's posted re Slackware. It's sheer speculation on my part, but it isn't unreasonable that ANY developer, artist, programmer, or whatever, wants and likes to know what <fans/users/whatever> are thinking about his/her work, and possibly trying to appeal to their desires sometimes.
But, I dunno, it'd take a whole lot of demand IMO before the Slack logo goes pink and can be read from any angle or perspective-- (prove me wrong, Pat!)