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.
Long time, no see. Thanks for popping by the slack-hood -- don't know if you noticed, but there are official slackware hoodies available: I recall, back-in-the-day, you were pining for one.
Anyhoo, I can see by your neon-green shoulder patch that you're rather short of reps, so I laid one on you. You definitely happened by the right thread.
I also "know" @kikinovak from my participation in the Slackware Documentation Project. He didn't sound as though he was kidding around in the above post. Actually, as others have also done here in this thread, he's made some valid points.
I'm no effin' angel, but this time on this thread, I did NOT post anything ill-mannered toward this OP. However, I did apologize, anyway, once someone pointed out the OP's apology.
I remember the first time I posted a query at the Arch forums (years ago) that was evidently too inane to warrant a decent answer. I remember how it felt to receive those replies. I'm a bit more aged and cynical than many of you younger folks, though. My reply to all of them was to "feck off". That's just me, though.
Anyway, I do think that we of the "Slackware" community, particularly on the "official" Slackware help forum, might try to be just a wee bit less condescending in our replies to folks asking simple questions. I will say this, though... I have seen my share of "Is Slackware Dead" questions in my 15 years as a user of this operating system. Sometimes, it is difficult to differentiate between the legitimately interested poster and the blatant trolls. Maybe we should try to err on the side of kindness. What could it hurt?
I propose this thread to be moved in whatever Debian section, because it have nothing in common with what vaguely I remember about being Slackware but it is a classic sh**hole usually found on the Debian's forums as how they was.
Have some shame, people!
And yes, no wonder that an outsider wonders if the Slackware is dead now, considering that no newb is able to install Slackware 14.2 in a relatively modern box with UEFI (and maybe NVME) and slackware-current isos are a secret known only by those initiated.
It is so complicated to put a sticky thread with frugal instructions from where to download a -current iso and how to use it?
Of course, is easiest to laugh your asses out, worth of 7 pages in the face of a newb...
Last edited by LuckyCyborg; 02-06-2020 at 05:58 PM.
I have seen my share of "Is Slackware Dead" questions in my 15 years as a user of this operating system. Sometimes, it is difficult to differentiate between the legitimately interested poster and the blatant trolls. Maybe we should try to err on the side of kindness. What could it hurt?
Yep. I'm getting damn tired of the "Bring out your Dead" Slackware threads. I started Slacking in 2004 with 10.0.
I will try to be more tolerant of these types of posts.
Slackware Current .iso. --> You don't need a Current .iso. What you do is install 14.2 and then set your choice to a "current" source in your /etc/slackpkg/mirrors set-up. Update and POOF! You have Current installed and running. NOTE: It's recommended that you manually upgrade to the Current kernel.
Sources: UEFI info from docs.slackware.com; Current .iso/installation info from my own experience.
I apologize for nothing. Common sense goes a long way, and if someone doesn't have enough common sense to notice how alive and active the Slackware forum is, (read sticky thread "Requests for -current (14.2-->15.0))", that they had to sign up for, and should have noticed the sticky thread that is almost always the first in the forum, then maybe Windows or Osux is more suited to their computing capabilities.
Don't get me wrong, I would offer help to any "newb" regardless of their experience level. But when your first post is "Is Slackware Dead?", I find it hard to believe that this person would do any investigation into any issues that they may face.
So here's a user who's obviously new to Slackware. He wants to learn a bit more about Slackware, so he checks out the webpage, which sports a news entry that's three and a half years old. No, he didn't click on the ChangeLog link, because nobody does that nowadays.
So he gets back on the forum to ask a legitimate question
First part, totally understandable. No updates on the website for a few years and many don't think to check for a changelog.
But this user came on the extremely active Slackware subforum, registered for an account, then posted the question, without looking at posts or using the search function. Taking 30 seconds of their time looking at some threads would've netted them their answer. Seriously, why would you go through all the effort of registering on the forum and creating the post without looking at the posts on the forum or using the search feature?
Then they "heard" the last update was 2016, but then "saw" it on the slackware.com page?
Quote:
I've heard that the last update was back in 2016
Quote:
Im sorry folks, i thought it was outdated since i saw here: http://www.slackware.com/
that the last post was in 2016-07-01 and its title is Slackware 14.2 is released!, thanks!
And if we want to throw more things OP should've done before creating a post, what about just searching google for "is slackware dead"? There's a post from reddit and one on LQ, both from 2018. Both have the same responses as this thread, stating that development has been ongoing and to check the changelog.
If you can't even search for your question and go straight to posting, then Slackware might be a difficult OS to use and we'd probably see a lot of posts from that person on simple things like how to update their system or setting up their network.
Now, maybe we should have a stickied post titled "Is Slackware dead/dying?" and in there mention that it is not dying and have links to the changelogs, but I expect that will get missed and we'll still end up with posts like these.
Where was it determined to be a "legitimate question"? Perhaps I missed that post. [...]
Well, someone who posts...
Quote:
Im sorry folks, i thought it was outdated since i saw here: http://www.slackware.com/
that the last post was in 2016-07-01 and its title is Slackware 14.2 is released!, thanks!
...(which was the 6th post in this thread) probably isn't a troll and was asking a question they thought was legit.
I have an idea! Maybe next time a moderator would be kind enough to inform the user that Slackware is very much alive and then lock the thread for the greater good. It can be impossible for us to tell if it is a legitimate inquiry or if it is a bot/troll that comes onto the forum ever so often! I looked at the OPs post history to try to gauge their intention.
Maybe it is PC (not computer acronym) or maybe it's thin skins I don't know but seriously guys I didn't see anybody get way overboard and nobody can predict how someone else will react to negative stimulus. A slap in the face may bring one to fisticuffs while another to his senses.
During my first few months on Linux (Mandrake in 1998) I was so green that I didn't yet understand the permissions required to get my modem working except as root, but I knew a lot about electronics and hardware. So I logged in as root and went to IRC Linux channels and started asking questions. One fellow offered to "look around" and asked if I minded if he logged in my box. I was so newb I let him! <facepalm> Thankfully nothing bad happened but I really didn't get anything out of his "visit". Another fellow responded with a disgusted emoji "RTFM Newb" and I responded that I was new to Linux but not computers to which he replied (and let me isolate this convo)
Quote:
Originally Posted by Some Negative 1337 on IRC
"It's not my fault your skills are so shit you own a ghetto box"
Me - My box isn't ghetto I built it with this mobo,CPU, RAM, and Graphics!
Negative 1337 - "I wasn't referring to your hardware. I was referring to you!"
Me - WHAT?
Negative 1337 - "You don't have the faintest clue about administration"
Of course I was quite offended, but by the next day after mulling those words around (The NERVE of that jerk!) until they lost a bit of their sting I realized he was dead on right. So RTFM is what I literally did. I went that day to a CompUSA and bought O'Reilley "Running Linux" and "Linux in a Nutshell" and vowed to never be that clueless ever again.
It seems that slap brought me to my senses. Life just isn't so simple as Good or Bad. Everything is a package deal and people either stick with sour lemons or make lemonade... their/our choice.
And yes, no wonder that an outsider wonders if the Slackware is dead now, considering that no newb is able to install Slackware 14.2 in a relatively modern box with UEFI (and maybe NVME) and slackware-current isos are a secret known only by those initiated.
I can't see what the problem is with UEFI. Slackware 14.2 Set A includes elilo and grub, both of which work with UEFI, as well as lilo for more traditional machines. And elilo comes with a script called eliloconfig which does the installation for you.
I can't see what the problem is with UEFI. Slackware 14.2 Set A includes elilo and grub, both of which work with UEFI, as well as lilo for more traditional machines. And elilo comes with a script called eliloconfig which does the installation for you.
Have you tried installing Slackware 14.2 on a NVMe drive?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.