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.
Excuse me, but the ChangeLog is for recording changes to Slackware. There has been no change in a month, which I do not consider to be an outstanding absence. Anybody who has concerns arising from recent vulnerabilities have recourse:
- if you want the latest Firefox then use the excellent script from ruario
- if you want security patches then use the excellent patches provided by mancha
Official Slackware provides a base, the community helps build the scaffold for the erection of the next tier.
As to communication, anybody following Slackware will be well aware from comments made by the hard working developers such as Alien_Bob, rworkman and drmozes, that there has been a lot happening with close involvement with our BDFL. It has been commented on before that Slackware provides an easier path to the developers than other distros. That Patrick Volkerding allows his work to do the talking for him makes for greater esteem on my part. I do not feel that "I have to live with it", but rather feel grateful to take whatever he wants to give.
Neither the qualities of Slackware nor how you can work around common problems (if you want call it that) was the topic of my post. The topic was that, IMHO, if a lack of communication leads to a thread that has to ask if the main developer is alright, then there is something wrong. And yes, the changelog may be the wrong place for that, which is why I wrote in my first post in this thread "in the changelog or somewhere else". Where communication happens is mostly irrelevant, as long it is a public place, and the changelog is where I would expect Slackware users to look first, especially if the lack of updates is the cause for a thread like this.
Just to clarify: I am not criticizing Slackware and it is totally up to Mr. Volkerding how to handle communication with the users of his distro (replace that with customers for those that have a subscription), but I will still point out weaknesses where I see them.
but I will still point out weaknesses where I see them.
I for one, while I'm OK even with the idea that P.V. decided to make a one year trip in Amazon, to study the Brazilian alligators, I believe that something is wrong with those Prophecies and the Prophets of the Big Update Batch. You know something? Say what is it. Something like:
P.V. prepare a huge update batch as KDE to the latest 4.14.3 (or 4.14.6 LTS), which everyone expect, thinking that AlienBOB well tested it. P.V. prepare integration of LinuxPAM, and update the affected packages (half of distro). Sure, even I, I'm a proud Apache warrior, but I uderstand that if we do not learn English and the Pale Faces habits, we risk to speak the Ancestors Language in some Indian Reservation. P.V. rebuild everything and change ARCH into i686. Good to known and bright decision in AD 2015. Then I will wait even until 2017, knowing the task complexity. All above.
BUT, if I believe that the Crypted Prophecies are nice into Church, not in a Linux (Slackware) community.
P.V. prepare a huge update batch as KDE to the latest 4.14.3 (or 4.14.6 LTS), which everyone expect, thinking that AlienBOB well tested it. P.V. prepare integration of LinuxPAM, and update the affected packages (half of distro). Sure, even I, I'm a proud Apache warrior, but I uderstand that if we do not learn English and the Pale Faces habits, we risk to speak the Ancestors Language in some Indian Reservation. P.V. rebuild everything and change ARCH into i686. Good to known and bright decision in AD 2015. Then I will wait even until 2017, knowing the task complexity. All above.
P.V. prepares the inclusion of Slint in Slackware. Whether it be a wishful thinking or a self-fulfilling prophecy remains to be determined.
I for one, while I'm OK even with the idea that P.V. decided to make a one year trip in Amazon, to study the Brazilian alligators
Actually if he comes here to see alligators it's better he go to Pantanal there is much more there, if i see he around i'll ask to take a photo :-) . Joking, i live more than 800 km southeast from there.
I bet that MATE being added to the Slackware tree.
Hmm, what were the time frames between releases in the past..
13.37 to 14 was 15 months! 14 to 14.1 was 14 months! 14.1 released 15 month ago! Seems like average release time is 15 months
13.37 is getting long term support, but 13.37 was release April 2011 4 years ago!
13.37 still works on most desktops and laptops without even a hiccup or burp. I've read here some are still using 12 releases!
The BDFL already has a backup team in place and working with him.
The BDFL and team release updates for security issues within a couple of days for true threats.
This forum is very active with most questions showing [SOLVED] within a few days, due to the tremendous support of everyone.
Problematic questions or quirks are answered by PJV within 48 hours usually when I drop him a question.
There is nothing but solid foundation under our feet with Slackware.
There is slackbuilds.org which allows others to contribute their knowledge and build scripts for those of us who are learning and aren't comfortable building from source only.
There a a number of Slackware spinoffs with other repositories for those who want only packages to install.
Seems like I found a rock solid place to be and stay!
The only concern I have is this, is Patrick getting enough from donations to purchase the health insurance on the open market since Slackware might be his only job? I know as a small business owner with private insurance that it can cost an adult up to $800/mo-$9600/yr plus deductibles of over $4000 just for one person, multiply that by two for spouse and then add children for another $500/month and you are quickly talking about needing $20,000/year just for the mandated health insurance. If we want our BDFL to stay healthy let's make sure he can get the health help he might need without worrying if he can pay for it. Slackware is not free as in beer, but it is free as in free speech.
So HAVE YOU MADE YOUR MONETARY DONATION TO THIS PROJECT YET THIS YEAR?
I just made mine to PJV and Eric! Thank guys.
Distribution: Slackware64-current with "True Multilib" and KDE4Town.
Posts: 9,095
Rep:
Quote:
Originally Posted by bamunds
Hmm, what were the time frames between releases in the past... ....14.1 released 15 month ago!....
17 months, tomorrow.
I'm not concerned with when the next version will be released, but I'm very concerned with the lack of security upgrades over the last 4+ weeks, especially for SeaMonkey.
Odd, health insurance didn't use to cost so much. Wonder why it has gone up so dramatically? Oh, yes, obummercare.
Last edited by cwizardone; 04-06-2015 at 03:38 PM.
So HAVE YOU MADE YOUR MONETARY DONATION TO THIS PROJECT YET THIS YEAR?
Yup. I made a small donation to Slackware a short while ago. I have a subscription to Slackware. I encourage all Slackers to consider buying a subscription as this will ensure a steady revenue stream for Slackware.
Distribution: Slackware 15.0 x64, Slackware Live 15.0 x64
Posts: 618
Rep:
Well, now the those who refused to listen to those who help PV have caused PV himself to break the concentration he had on the project that he couldn't afford to take his eyes off for even a moment, have now caused PV to have to start all over and be gone from sight and sound for another 4 months! Thanks for nothing you guys! (you know who you are!)
What was so hard about taking alien's word that PV was well and good?
1. Handcrafting the world's first SlackBeer to be sold exclusively on the Slackware store.
2. Hiking to the top of the great holy mountain in search of Bob Dobbs' last known location from the all knowing ancient Gurus of all that is Slack.
3. Working on a new T-Shirt design for 14.2 that shall be the awesomeness of awesomesauceness.
4. Playing darts with a photo of he who shall not be named as the bull's eye with Robby and Eric at the Great Slackware Compound located in The Secret Slackware Bunker.
5. Paying homage to Bob Dobbs at the great alter of Subgeniusness by burning the holy Slackware incenses with an offering of handcrafted beer, a CD of The Grateful Dead, wearing the 13.37 robes of enlightenment, chanting "I will get by."
Yup. I made a small donation to Slackware a short while ago. I have a subscription to Slackware. I encourage all Slackers to consider buying a subscription as this will ensure a steady revenue stream for Slackware.
On this note, does the donate button at the slackware store go straight to PV?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.