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.
Agree with Didier and Rabelais.
When I was a kid, on trips to Blackpool on the train, I used to wait for the first glimpse of the Tower. Then I knew I was nearly there.
So, can we see the Tower yet?
ReaperX7 Debian?! Oh... You mean CoreOS with apt-get?
How does oneget sound? There's no reason future CoreOS won't include Windows applications is there?
Quote:
Originally Posted by elcore
That's one way to put it. You could call it a brown fedora for example.
There's also green and silver fedora, so I'm not so sure we need another flavor.
It has a vintage package manager, vintage init system, vintage authentication system, vintage mailing system.
Basically nothing changed in the past decade and more. It is far from being a mainstream Linux distro.
My choice of word for Slackware would be classic (2) not vintage(9). Slackware is not the hold your hand Gnu/Linux that most call main stream as things like commercial Red Hat or the wanna be *buntus. So we can continue to have a semantics discussion but I for one finds that Slackware is a classic that provides new additions but remains a stable release that other Gnu/Linux should or would like to produce and to have the reputation that has been earned by PV for the past 20 years. His inclusion of modern efficient packages that are proven to be stable is a plus to me. Not just with on going support beyond what others do not provide via security updates. Slackware does have a great team and support base of users which have helped Slackware grow.
Quote:
Originally Posted by ivandi
And the community around Slackware likes it like this.
It is perfectly suitable for basic setups like home or small business use.
I guess the major users that have Slackware installed are awaiting a downfall from not having a rolling or repeated release cycle. I prefer to have a stable base for my system(s) which Slackware does provide.
Quote:
Originally Posted by ivandi
Unfortunately this vintage simplicity makes Slackware completely unsuitable for enterprise use. But who cares.
Cheers
So say you! You've got numbers to show this stance?
Like most good seasoned Slackware users, I do not need a turn-key enterprise. Slackware does have the tools to utilize by the admin that knows how. Nothing said that we cannot convert other repository packages that do have EAS. Slackware can be used to provide a stable server that implements the business needs for users & admins.
PV does not put any restrictions on how & where Slackware can be targeted for use. So why would I? So any of the Office suites or data bases that are available for Slackware are of no use to the business enterprise from your point of view? What about IDE for houses that need the tools? Impossible to use the IDE packages available for knowledgeable users on Slackware? No!
Slackware users come from varied professions and most will not hinder development or growth with statements(FUD) that would belittle a unique classic Gnu/Linux.
Like most good seasoned Slackware users, I do not need a turn-key enterprise. Slackware does have the tools to utilize by the admin that knows how.
I liked "who cares" fine. As someone whose day job involves writing some so-called enterprise software, I've found, over time, and now that I've heard it, that the only sensible response to the invocation of the e word is Fab's response on the most recent (and one of the final, in case you haven't heard) Linux Outlaws podcast episodes. That is, each and every time someone says enterprise software you must whistle or hum the star trek theme. How to do this in purely textual fora I'll leave up to you.
The fact is, we, on average, simply aren't as good programmers as many who write "for fun" software. Most of what we do could be accomplished by a talented Perl programmer in less than 1/2 the time for less than 1/4 the cost and with better results.
Why do people keep thinking that a new release means that Slackware should decide on a new init first? Did you see any traces of a new init in slackware-current? There is no need for a new init. Don't believe the hype.
Eric
Unfortunately I don't recall, where I read it (your blog, Eric? or here at LQ.org?), but wasn't there a problem with console-kit depending on systemd, meaning that KDE could not be included with Slackware without systemd. Is this still the case?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.