4 ms·
I can't second these statements enough, especially the last one. I'd tried every major distro before settling on Slackware sometime around '99 and that's when
by busterarm 12y ago
I can't second these statements enough, especially the last one.
I'd tried every major distro before settling on Slackware sometime around '99 and that's when I finally learned Linux.
I'm using Arch today and to me it's a very similar philosophy with some bonuses. If it weren't around, I would surely be using Slack.
- mrottenkolber 12y agoThe difference between Arch and Slack tho is, a Slackware system is rock solid and doesn't need to be touched. An Arch system not maintained for a couple months is in pacman hell. :)
- Alupis 12y agoI took a similar approach, although not with Slackware. I was tired of not knowing what was inside my distro, nor how it worked... so one day I decided to build my own distro (following the very good Linux From Scratch book, and then later the Cross-Linux From Scratch book). It's even more bare-bones than a base arch or slackware -- but the best part was knowing exactly how everything worked, and no longer fearing of changing something, because I understood what it was doing now. The experience and knowledge of "rolling my own distro" is very applicable elsewhere -- from understanding kernel panics better, to understanding "dependency hell", to how the entire boot process even works. A linux distro is really a thing of beauty once you understand what is going on under the hood.
- busterarm 12y agoI've done LFS a couple of times and also contributed packages to a few other Linux distributions (GoboLinux mainly) since learning on Slack, but I think the experience was better having learned my way around a Slack system first. LFS was definitely a helpful step to "dive deeper" though.