Linked by Thom Holwerda on Wed 22nd Nov 2006 22:33 UTC, submitted by Rich Morgan
Slackware, Slax Open Addict reviews Slackware Linux 11.0, and concludes: "The latest Slackware release is more of the same pure Slackware goodness from Patrick and Company. It doesn't drastically diverge from 10.2 but adds some new software packages and includes some newer kernel support. Hardware detection is pretty much as basic as it can be with much of the configuration and tweaking on you - the end user. Thankfully, it isn't hard to configure Slackware through its easy to find textfile-based configuration files, but newbies might be lost."
Permalink for comment 184778
To read all comments associated with this story, please click here.
RE: Slackware package management
by da_Chicken on Thu 23rd Nov 2006 15:42 UTC in reply to "Slackware package management"
Member since:

AFAIK, APT doesn't have a "rollback" feature that would be useful in the kind of problems you describe. APT stores packages in /var/cache/apt/archives/ and you can check if the older version of the package that is causing trouble still exists there. There's also that makes older versions of packages available. Then you can use dpkg to downgrade the troublesome packages.

Dpkg has a log file in /var/log/dpkg.log and if you use aptitude, you can find its log file in /var/log/aptitude. These log files should help you in finding out exactly which packages you upgraded before the problems appeared.

There is also a tool called apt-listbugs that should automatically scan bug reports and show you a warning about packages that have known problems before you install them.

Reply Parent Score: 1