SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Like others here it seems I had problems with the latest -current. I can't startx, no sound, etc. I put back the video drivers and such from the 13 CD but now have a bunch of other issues, video will flash every now and then and sometimes go blank so I can only reboot as exiting xwindows and going back in its still blank. I tried booting from the 13 cd and reinstalling without formatting my root partition but that dies in the kde games for some reason and setup won't start again. I was trying to not format and loose all the updates just put back 13 but that doesn't seem to be working.
Distribution: slackware64 13.37 and -current, Dragonfly BSD
Posts: 1,810
Rep:
Personally I wouldn't advise mixing things from any stable version and current and I can't see any point in running a version of current that is not "current". I would just try and find out what was the problem in current (that's the point of running current after all) or revert to 13 stable in which case you can format your root directory again - hopefully you have /home on a separate partition which you can use to save stuff on should you wish. However,again mixing things from current and stable is not recommended so anything built on a current system should be rebuilt on the stable. Just install afresh and "slackpkg update && slackpkg install-new && slackpkg upgrade-all" to get any updates to 13 stable after adjusting your mirror version. At least this way you know your reverting to a clean system.
looks like I'll have to reformat. My problem was there were multiple issues with the latest current. But I like to have some of the stuff up to date like kde.
I don't think slackpkg and whatever other package managers can do "roll-back" because Slackware don't keep old packages. When they are removed from the remote server, they are gone forever. So you will have nowhere to found the packages you need. There are some slow mirrors will keep the old packages for some time but how about if you want to roll back to a year ago?
So, I think the solution is solute the problems you have encountered. If one want a solid system, go -stable.
If you can boot to the command line just change the mirror in slackpkg to a 13.0 mirror, and run slackpkg. you will have to update, clean, install new and upgrade. but this should give you a cleanish install of Slackware 13.0.
Distribution: Slackware64 current multilib, Gentoo
Posts: 43
Rep:
Quote:
Originally Posted by grissiom
I don't think slackpkg and whatever other package managers can do "roll-back" because Slackware don't keep old packages. .
That is true, and : if you want a stable system, don't use current.
HOWEVER: if you are using current; and are using slackpkg for the task; then there's one thing you can do; so that you can make a 'step backwards':
Standard slackpkg will remove all downloaded files after upgrade; but if you edit /etc/slackpkg/slackpkg.conf this way:
Code:
...
# If DELALL is "on", all downloaded files will be removed after install.
DELALL=off
...
then the downloaded packages are still in /var/cache/packages.
When you move these packages after every update you make to a safe place, then you can always reinstall the versions before the last update. You can use this to make one step back and stay there till a new stable release is out, but don't mix older and newer versions from packages!
Thats what I should be doing then. I want the latest Firefox, Thunderbird and KDE4 that I installed in Feb without the broken Xorg, power management, etc in March.
Looks like some of the repos are pulling March's off, I'm back on 13 but can't even get the new firefox and thunderbird, every time I try slackpkg errors out with a not found even though the update list says they are there, been through like 10 different reps now.
Great practice I'm considering that the ultimate back up of a system is ZFS. Maybe btrfs in the future Linux.
ZFS and its like are great storage tools and i'm looking forward to playing with them too, but you can't beat the simplicity of a set of archive files as a safety net when the shit hits the fan.
Ok, I see where the issue is. The install of 13 doesn't support txz's, I seem to remember that being in a -current update a while back. But it seems that its not in -current so anything slackpkg tries to install fails due to it not being a .tgz. So unless I can find the packagetools from earlier -current I can't install anything new.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.