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.
What the heck is the rush? System crashing? Slackware is not the sort of distro that needs constant updating. This frenzy for constant updates is just nuts. If a slack user gets nervous about all the "security flaws" just freaking update that package yourself. If I had my wish, PV would only release once a year with only monthly updates.
Let PV take a breather and/or hang with his family.
Yeah, agreed. I see no problem with any of this, my system is stable and as someone mentioned earlier, I use it for mostly hobby stuff.... there are currently no 'cure-for-cancer' projects on my laptop. I was just reading this thread for entertainment, and bonixavier said exactly what I was thinking.
But I guess IF the distro was de-commissioned, I would go with something else in active development. It wouldn't be any of the other major Linux distro's though, at least I doubt it. I've tried a few and none came close to this one.
Click here to see the post LQ members have rated as the most helpful post in this thread.
If Slack is decommissioned I still ani't jumping ship.
Pat has blessed us with a distro that allows us to be dependent on ourselves if we choose. Were not dependent on package managers or “ready rolled” updated packages from some repo. There are many who don't have time to screw with building there own sec updates but there are also many who do. If Slack is decommissioned I think I'll hang in there and try to learn some new tricks.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,039
Rep:
Quote:
Originally Posted by Richard Cranium
Too bad they removed the "no" option to the "Was this post helpful?" question.
Oh, I absolutely agree!
Many just don't seem to get it, so here it is one more time, SLACKWARE IS A BUSINESS. Unfortunately, regardless of past
history, it is NOT currently being ran like a business. This is not a national security hush-hush weapons project, it is just software, an operating system.
Put it this way, and it doesn't matter what kind of business it is, from your local barber or baker to your neighborhood "rocket scientist." If every time you go to the shop or office door the place is closed and locked and there is not a sign on the door saying, "Gone Fishing," or even, "Gone to the Bank. Be Back in 15 minutes," pretty soon you will stop wasting you time and energy and find another vendor.
Simple. Human nature. Nothing more. Nothing less.
I've refrained from saying this for several weeks now, in the hope things would change, but they haven't so hold you nose, suck it up, take off the rose coloured glasses and realized the word for such a lack of communication from a business is, irresponsibility.
Last edited by cwizardone; 01-30-2012 at 09:07 AM.
I don't really care that -current isn't moving, but it is unsettling that stable isn't receiving security updates. Pat has always taken a pretty relaxed approach to security updates, but at least the major ones were covered. At this point in time, that can no longer be said. It's not enough of a worry to me (yet) to move on, but if the situation remains as it is 3 or 6 months from now...then using Slackware may no longer be the responsible choice. At *this* point though, I'm OK with riding it out, as long as Slackware isn't in limbo indefinitely.
I am hopeful that the present situation will not continue for 3-6 months. I suspect that the updates in the pipe will be made available in the near future.
If every time you go to the shop or office door the place is closed and locked and there is not a sign on the door saying, "Gone Fishing," or even, "Gone to the Bank. Be Back in 15 minutes," pretty soon you will stop wasting you time and energy and find another vendor.
Last time I checked, slackware.com was still open and the product could still be freely downloaded or purchased from the store. Nonetheless, if you don't feel the proprietor of Slackware is supporting your needs then you certainly have the right to complain or take your business elsewhere.
As for myself, I imagine Mr Volkerding is monitoring the status of upstreams and, if he is not working on the next Slackware (which I doubt to be the case), planning what updates of what packages are worth consideration for inclusion (and what adaptations will have to be made).
To be honest, I don't see very much in the upstream landscape that is at a stage in development where I am interested in dealing with the problems. KDE has been refactoring things for a more simplified distribution model; XFCE is still chasing problems caused by their adoption of FreeDesktop guidelines; and many GTK-based applications are in a state of transition to GTK3. Personally, I would not be interested in a new Slackware that incorporated this less than fully-baked software.
Pat has more than proven to me that he knows what he is doing (to say the least), and even if he has "gone fishing" for a few months in my view he has chosen a good time to do so.
Pat has more than proven to me that he knows what he is doing (to say the least), and even if he has "gone fishing" for a few months in my view he has chosen a good time to do so.
Agreed. I have been Slacking since 2004 and will continue to do so. Praise Bob.
My own thoughts are that maybe we need to take a deep breath.
If Slack was on the rocks, Eric would know. And then why would he continue to maintain kde?
He just updated 4.80 two days ago...
I am also just a personal Slack user, and I see no reason for alarm yet. If I need to update something, the Slackbuilds system gives me everything I need. If I were running a production server, I would be following upstream patches for every mission-critical package on my system. Again, Slackbuilds would give me everything I need.
If you conclude that from what I read, you are way off. I was referring to the fact that I have been maintaining KDE releases outside of Slackware for a year now and I'd like to see my updates folded back into slackware-current. Robby Workman has the same feeling about his XFCE. But that has nothing to do with the lack of updates everybody is discussing with so much vigor.
I know (most of) what's going on behind the scenes and I have already explained earlier in the thread. I am not going to repeat myself.
If Pat is taking time off, well, Praise Bob the man has earned it. If he decides to quit there is always C.U.S.S. or the Horned One (BSD). Personally I'll start worrying sometime next year.
Many just don't seem to get it, so here it is one more time, SLACKWARE IS A BUSINESS.
Well, yes, but the business of the Slackware business is the sale by mail order of geek artefacts (teeshirts, bottle openers, discs). There is a software distribution coincidentally branded Slackware, but that is an occasional *gift* from a small group of people (one of whom has a mail order geek artefact business).
In other news, Slackware isn't affected by today's sudo vulnerability). Don't upgrade. Stay in bed.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.