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.
I have 14.1 installed on several servers. I would like to upgrade to 14.2. In the past, I've always simply installed a clean new distro from scratch, then added my configs and customizations.
I'd rather not do that this time as one of the servers is a Samba4 domain controller with working .ldb database serving the whole office, including Dovecot mail server. Setup for these things, plus DNS, DHCP, etc. is extensive and fraught with peril. Can I just somehow upgrade to 14.2 in-situ without doing a scratch install? If so, can someone give me tips on what I should and should not do? Yes, I'll do a full backup beforehand.
There is a How To file on the install dvd called UPGRADE.TXT. Follow those instructions to do an upgrade. I have used them several times without issues.
I copy off all the config files to some safe locations, and then do the upgrade. Once the upgrade is done, ( about 30 minutes ) use slackpkg to bring the new install up to date, copy the config files back.
It takes me more time to install things from SBO than the upgrade, so look into those packages also.
I have 14.1 installed on several servers. I would like to upgrade to 14.2. In the past, I've always simply installed a clean new distro from scratch, then added my configs and customizations.
I'd rather not do that this time as one of the servers is a Samba4 domain controller with working .ldb database serving the whole office, including Dovecot mail server. Setup for these things, plus DNS, DHCP, etc. is extensive and fraught with peril. Can I just somehow upgrade to 14.2 in-situ without doing a scratch install? If so, can someone give me tips on what I should and should not do? Yes, I'll do a full backup beforehand.
Yes, you can do a live upgrade. It's not exactly a trivial operation, but it's possible. Here's a link to my own notes.
I always have two Linux systems installed, each in its own partition. I dual boot, usually into the newer system. When I want to install a new upgrade or even a completely different distribution I do so by replacing the older system with my latest install. How I do so varies depending on what the distribution's installer is capable of. I prefer upgrade in place if the distribution can handle it.
By using dual boot I don't have to worry about any instability in the new install causing a lot of down time. More importantly I can make all of my custom settings at a leisurely pace and not be rushed because I have to get the new system working as soon as possible.
If you start maintaining two systems at once then you will have to install 14.2 as a second system with a fresh install. After that, then future upgrades can be done either with a fresh install or an upgrade in place at your leisure.
Another advantage of maintaining two systems is that you have an instantly ready backup system if your production system breaks.
There is also a file called CHANGES_AND_HINTS.txt which you should follow: http://mirrors.xmission.com/slackwar..._AND_HINTS.TXT
I would allow for some downtime, and if you have any custom udev rule files in /etc/udev/rules.d/ then I would rename them <filename>_old or you will see alot of errors. I did an upgrade from 14.1 to 14.2 this week and it went smoothly other than the udev files issue, I did mine using the install CD and monting my existing root partition, bind mounting dev, proc and sys, and then following the instructions in UPGRADE.txt, followed by removing the obsolete files (although this was a media pc not a working email/samba server so DO A BACKUP!)
Good luck!
I once perform a live upgrade from Slackware 12.2 to 14.1 (incremental update, 12.2 -> 13.0 -> 13.1, etc) using slackpkg and everything is working just fine. You just need to make sure to install new packages and remove deprecated packages.
Basically, 'current' is ongoing experimental, and not recommended for production. Got it.
Meanwhile, I did successfully upgrade 3 servers from 14.1 to 14.2, remotely w/o going to single user mode. The UPGRADE.TXT instructions were all I needed. The only glitch I ran into was that rc.rpc is required to run on the nfsd server now, whereas it was not before. It took me a while to figure out why I couldn't see nfs exports from client hosts. Also, the rc.rpc.new is definitely needed for 14.2 and nfs usage.
Basically, it worked!
I have not yet done the upgrade to the Samba4 server -- ran out of time this weekend. If I have any issues with that, I'll post.
RPC was required for NFS back in 14.2 as well. The /etc/rc.d/rc.nfsd explicitly called it if it wasn't running.
Code:
# If basic RPC services are not running, start them:
if ! ps axc | grep -q rpc.statd ; then
if [ -r /etc/rc.d/rc.rpc ]; then
sh /etc/rc.d/rc.rpc start
else
# Sure, we tested for rpc.statd, but this is the probable cause:
echo "FATAL: Can't start NFS server without portmap package."
sleep 5
exit 1
fi
fi
This forces /etc/rc.d/rc.rpc to run even if it isn't executable (the -r only tests if it exists and is readable). It is possible that there were changes with rc.rpc and the rc.rpc that was included with 14.1 was no longer compatible in 14.2 (I'm too lazy to diff them).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.