- cross-posted to:
- slackware@lemmy.ml
- cross-posted to:
- slackware@lemmy.ml
You must log in or # to comment.
I set my mom up on slackware like 15+ years ago. She wouldn’t have known how to break it if she tried.
I feel out of the loop, what’s Slackware?
The oldest Linux distro that’s still maintained to this day.
With an extreme focus on the KISS principle (simplicity in design) and stability.
It basically still works the same way it did 30 years ago.With fewer floppy disks though.
The linux distro you want to have on a usb stick if the apocalypse breaks out.
deleted by creator
is it more stable than debian?
No, unless stability is very little change.
This is what Debian’s Stable name means: that, once released, the operating system remains relatively unchanging over time.
That’s what it means… A dead distro is the most stable.
but secure, that the sweet spot, stable enough but not sacrificing security
People use OS’ for different things. As an admin I’d love to have an os that’s just there and never needs any attention. I’ll have to investigate if slackware fits the bill :)
I’ll just stick with Debian
This meme reads more like slackware won’t do anything you want it to do…
I really want to try slackware but I’ve only used fedora and hear it’s “difficult.” Is there something you can use that handles dependancies for you? Iirc that was the reason I was holding off.
With Slackware, you install its entire repository (~15GB) upfront. This gives you a system with a lot of software pre-installed for a wide variety of tasks, and makes dependency resolution for the base system pointless - all dependencies are already installed.
Additional software is installed via Slackbuilds or community-maintained additional repos. Those work very similar to Arch’s AUR: officially you are supposed to download, build and install packages manually using preconfigured build scripts with no dependency resolution, but tools that automate the entire process are available. And just like with the AUR, those tools aren’t officially recommended, but they work and almost everyone uses them.
So while it’s true that the default package manager in Slackware has no dependency resolution, that’s irrelevant in practice.
One word of warning: While Slackware does work well out of the box, adjusting it to your needs is a more involved process than with other distros. Everything is done manually but it lacks the awesome documentation Arch has and includes some pitfalls due to lack of automation we’re used to nowadays. For example, if you upgrade your kernel and reboot, it won’t boot. Because you forgot to copy the new kernel into your EFI partition, regenerate the initramfs and point your bootloader to it. Every other distro’s package manager recognizes a kernel upgrade and triggers those things automatically.
Slackware is easiest if you are a bit flexible in what you use and are fine with its default selection. If you want Gnome, best choose another distro. It’s possible to build and set up, but not easily.
But once you’ve set everything up the way you like, it just stays that way forever and there is almost no work needed to maintain it.
