SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
So, just my humble pov: the linux ecosystem evolves too rapidly to ever call it stable. Perhaps since linux has increased in complexity, slackware should do the reverse, and increase in simplicity by reducing the package base it has historically supported.
Why not? And to make the move obvious Slackware could be renamed SlackBSD. it would adopt BSD kernel and utilities, and benefit of the 30000+ packages available for FreeBSD including most Linux desktop and apps (many at their latest versions), still without systemd. So Patrick could concentrate on the distinctive Slackware features. Of course SlackBSD would handle less devices, but for the nostalgic among us this would remind what Linux supported 20 years ago. And SlackBSD could adopt a quarterly upgrade, as GhostBSD, and have KDE plasma as its default desktop, other being easily added by users.
Last edited by Didier Spaier; 10-27-2021 at 06:25 PM.
Slackware philosophy says: KISS. (I heard that too much in military, and prefer just dropping the second S, out of the same principle: KIS is even simpler than KISS).
Just great!
Now then we can expect certain someones calling it Lackware?
Why not? And to make the move obvious Slackware could be renamed SlackBSD. it would adopt BSD kernel and utilities, and benefit of the 30000+ packages available for FreeBSD including most Linux desktop and apps (many at their latest versions), still without systemd. So Patrick could concentrate on the distinctive Slackware features. Of course SlackBSD would handle less devices, but for the nostalgic among us this would remind what Linux supported 20 years ago. And SlackBSD could adopt a quarterly upgrade, as GhostBSD, and have KDE plasma as its default desktop, other being easily added by users.
That would be an interesting switch if that were ever to happen, and SlackBSD would have ZFS made available too.
Never mind BSD. I don't believe plan9 has any package managers. This time P.V. could be first off the block. About time for a fresh start on a new foundation, wouldn't you say?
Then again plan9 people may consider the need for package management a symptom of the disease they're trying to avoid.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.