3 ms·
It was also my first serious Linux distro. I started using it around Slackware 9.0 (wow, it's twenty years already). It was the PERFECT distro for learning beca
by oskarw85 3y ago
It was also my first serious Linux distro. I started using it around Slackware 9.0 (wow, it's twenty years already). It was the PERFECT distro for learning because it was simple (as in uncomplicated) yet workable. I learned a ton about bash scripting, kernel compiling etc. I remember I even "ported" Reiser4 filesystem into the Slackware installer (who remembers that FS today LOL). Slackware did not have ANY dependency mechanism for packages, so often installing them was a lottery. Oh the long hours spent running ldd and strace to find out what's missing.
I switched to Gentoo after Slackware because everything was working just fine and I got bored. After that I learned that my free time is better spent on gaming and I switched to Windows 7. I came back to Linux after few years and damn - systemd took me by surprise. I never learned to use it properly because it's so much more complicated than my beloved Slackware SysV Init.
Congratulations to Patrick Volkerding - managing distro for 30 years is no small feat. Happy hacking.
- hulitu 3y ago> Slackware did not have ANY dependency mechanism for packages, so often installing them was a lottery. That's why i switched from Redhat 5.2 to Slackware and never looked back. In redhat you had circular dependencies: libfoo requires package libbar and libbar requires package libfoo. Solution: use rpm --force Also an RPM package will refuse to install when a dependency was not found (when you compiled and install the library yourself).