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.
If a rolling release isn't on for a newbie, then slackware-current isn't on! But I used Debian Testing quite successfully for a while in the pre-systemd days. It never broke on me.
I know it isn't the accepted use case, but it is nevertheless very effective to install Current as a "Snapshot System" and never upghrade it or only upgrade that with which one is comfortable.
Current is not technically a rolling release. Actual rolling releases like Arch are apparently fully tested and vetted to be "production ready". One could argue that with so many variations possible and likely with such a minimalist system that they would suffer continual and likely catastrophic breakage if they followed the daily test updates of Current. In my view that speaks volumes about the overall robustness of Slackware, including Current.
BTW if I had to recommend a distro for a rank beginner I might be tempted to promote OpenSuSe. Personally I find both systemd and near daily patches a pita, but it is quite robust and fairly intuitive.
Yo latimro (OP) if you broke your system and got a kernel panic that very likely means you didn't keep your older, working kernel as a failsafe. I actually don't mean to offend you but that is why you look like a newb. That's just a common rank beginner mistake. Always Protect Your Six!
Since you seem to have a bee in your bonnet, let me ask you this: Have you spoken to Patrick about whether or not he has plans to implement Secure Boot support? If not, then how do you know what his plans are? Ranting about it on a forum isn't going to get you anywhere.
Lucky, much like Darth before him, believes that if something isn't working as s/he expects, it's a deliberate choice by Pat and reacts as such. This is instead of thinking/realizing it might be something Pat just hasn't noticed, hasn't decided to tackle yet, or is working it behind the scenes.
I have, and not only with Slackware¹. But I didn’t go online to complain that the system did nothing to prevent me from being foolish.
¹True story: as a teenager back in the 1990s, I got one of my first PCs which was running Windows 3.11. I knew next to nothing about computers back then (as will be obvious by the end of this paragraph). The hard disk was about 100 Mb large, and I was starting to run out of space. When exploring the hard disk, looking for stuff to delete, I came across a folder full of .dll files, which didn’t seem to do anything useful: nothing happened when you clicked on them, and there was no application seemingly able to open them. So, I methodically and conscientiously deleted all those useless .dll files, thereby saving several dozens of Mb of disk space. I felt very proud of myself that day.
The following day, when I tried to boot that computer… It would not boot! Can you believe it? It was working perfectly fine the day before, how can something work one day and not the next one? Surely, the system must be a piece of crap!
(At the time, for some reason the fact that a failure to boot on day n could be the result of something I did on day n−1 seemed completely illogical to me. I understood only much later.)
At least I didn’t have Internet back then, so I couldn’t go online and ridicule myself.
Why not give him the benefit of the doubt until it's proved otherwise? OP sounds like a young guy who discovered his reach exceeded his grasp. It happens. That is a painful experience but the results can go either way. Ideally, in my view, he needs to learn from this experience to improve his current lack of skills. This is either a helpful community or it's not.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.