Slackware uses simple packages and expects administrators to understand system changes. Its tools do not generally resolve third-party dependencies for you.
Read the installed version
cat /etc/slackware-version
Use the right privileges
System-wide package operations require root. On a standard Slackware setup you can open a root shell with:
su -
You will be asked for the root password. Do not remain root for everyday browsing.
Basic pkgtools commands
# Inspect these commands before acting
man installpkg
man upgradepkg
man removepkg
installpkg adds a local Slackware package; upgradepkg replaces installed versions; removepkg removes. Prefer packages appropriate for your architecture and Slackware release.
Configure slackpkg
As root, edit /etc/slackpkg/mirrors, enable one suitable official mirror, then review Slackware's changelog and update instructions.
slackpkg update
slackpkg install-new
slackpkg upgrade-all
slackpkg new-config
These are a typical stable-release workflow, not commands to run blindly. new-config can prompt you about important configuration files. Check its choices carefully. Slackware may publish special instructions for certain upgrades and kernel/bootloader changes.
Search for a package
slackpkg search irssi
For applications not in the official release, research SlackBuilds.org. Be sure to track third-party dependencies yourself.
Don't: use Debian
aptor Fedoradnfcommands on Slackware and expect them to work.