SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Answer is - I don't really know, but it sure would be a lot easier just to install from scratch again.
I have had the experience allready, and quite honestly, to install Slackware from scratch is about the easiest thing in the wild-west of distros.
I had to do this on my laptop due to missing driver support from AMD.
IIRC, do it this way:
1. Make sure that you have set DOWNLOAD_ALL to on in your slackpkg.conf
2. Set your mirror to a 14.0 repository
You have to replace slackware with slackware64 in the second slackpkg command when you run a 64 bit installation.
At the time I had to do this -current was not so far away from 14.0, so it may be possible that it doesn't work anymore.
Further to TobiSGD's excellent post. Downgrading may work, but 14.0 and the upcoming 14.1 are very far apart now (I have no idea if this will work). As mentioned prior to attempting a downgrade ensure that you back-up everything that you cannot afford to lose. If the downgrade fails you can always do a clean install of 14.0 and bring over your stuff from the back-up.
Location: Northeastern Michigan, where Carhartt is a Designer Label
Distribution: Slackware 32- & 64-bit Stable
This sort of situation is where partitioning comes in handy.
When you think about it, your stuff goes in /home, /usr/local, /opt, /var/lib/mysql, /var/lib/psql, /var/lib/virtual, maybe a couple of other places. Everything else goes in root; i.e., everything that's on the distribution CD-ROM/DVD goes in root. So, I create partitions for each of those; in some cases they're separate drives altogether -- my data base servers are separate drives, but on my working systems they're partitions on the system drive. In either case, they "look" the same when mounted.
I always do a clean install when a new Slackware release comes along. First, I copy /etc to one of the partitions. Then I stick the DVD in and go through set up. I format the root partition (so it's "clean") but do not format the partitions that will be mounted (you choose not to format during set up when you're adding partitions to /etc/fstab).
Once the installation is complete, I copy or merge some configuration files in /etc from the backed up copy. You know, things like /etc/ntp.conf, /etc/fonts/local.conf (I keep font files in /usr/local/share/fonts -- I have Adobe Type Libary (large!) plus other add-on fonts). All that sort of fine tuning.
The net result is that an install takes about 20 minutes, maybe 30 minutes. Software installed in /opt is still there (like LibreOffice plus a lot of GIS, Google-Earth), the data bases are there, virtual machines are there (I do have to run Win7 every patch Tuesday, you know).
All you have to do is remember which partition is what (and df -h or mount will tell you that before you start) and don't format them during installation (well, you do want to format the root partition) -- I'm not kidding, 20 or so minutes from start to up and running.
You may, if you use a lot of SlackBuilds.org packages, need to make your root "large;" they seem to want to be installed in the root tree (I prefer that anything I add go in /usr/local but, OK, deal with it and make the root tree 20G instead of 10G, dammit).
Works for me, might just work for you when you need to go back to square one.
I actually did what you want to do, I upgraded my wife's to current, and when I checked it with "slackpkg update" it had
written a new mirror. I accidentally marked a Slackpkg mirror to 14 instead of current and proceeded to update/upgrade,
well it upgraded/downgraded me back to 14 with no problems. She used it for a couple of weeks before
I took it back to current.