![]() ![]() Slackware actually doesn't lack package management. I'm running Slackware 14.0 on an old Thinkpad A31, and it runs pretty alright. I'm by no means an expert, merely a hobbyist, so forgive me if I'm talking out of my ass.Īs for the hardware, I'd be inclined to say it'd be fine. The only area where you may have issues in the in the desktop environment / window manager realm, which will be the case no matter which distro you're using. To find info on what packages you've got installed (and where the files of each package went), consult the /var/log/packages directory.Īnd lastly, to (sort of) answer your first question, I imagine that it would run just fine on that hardware. When I want to upgrade something, I just 'removepkg OLD_PACKAGE' and then 'installpkg NEW_PACKAGE' the new one. I won't claim to be a Slackware expert, though, so you may want to research the various pkg commands before taking any of my advice to heart. There does exist a command for upgrading package (I believe it's just named upgradepkg), but I've never used it. (after gaining superuser privs with 'su -') It more or less just automates the above described process for you. It's similar to 'yaourt' on Arch if you've ever used that. Of course, if the option is available, I tend to opt for the slightly easier route of using sbopkg. This ensures that the package is easy to archive and reinstall should you ever need to, and it also makes removing it simpler as well. Turn the compiled software into a slackware package Here's how I typically install a new piece of software by hand: ![]() Slackware is probably the hardest-to-break Linux distro I've ever used, as long as you do things 'properly'. ![]()
0 Comments
Leave a Reply. |