Table of Contents
Upgrading to TLD Linux 2018.02
Note: only upgrade from TLD Linux 2018.01 is supported. If you are running TLD Linux 2016.01 please use this howto.
Please backup at least entire system configuration before proceeding! If possible, backup entire host or take snapshot of its current state if its virtual machine.
First of all update your poldek indexes:
Now get rid of all *.rpmnew files from /etc to be sure you will have newest default configurations for all packages for which old one cannot be adjusted or updated.
TLD Linux 2018.02 is minor update that brings mostly various bugfixes and upgrades for some core packages. Regular poldek upgrade-dist will suffice to update your system, but before doing so you must take care of few system changes.
1. Make sure that elinks package is not installed. It has been removed from TLD Linux.
poldek -ev elinks
2. Stop PostgreSQL server if its running. Check package notes below for details.
service postgresql stop
3. Now perform upgrade:
poldek -v --nohold --upgrade-dist
When upgrade is finished please follow below package notes to get everything running.
Notes for some packages
Default location for configuration has changed. Now dnsmasq loads any file with .conf extension which is located in /etc/dnsmasq.d. Please update your configuration and make sure that you use current version of /etc/sysconfig/dnsmasq file (if your local copy was modified upgrade have saved new one as dnsmasq.rpmnew).
TLD Linux now provides multiple PostgreSQL versions which can be installed in parallel. All currently supported versions are available: 9.3, 9.4, 9.5, 9.6 and 10. Newest version will always be default one which provides all required system libraries.
During upgrade your system has automatically switched to postgresql-10-* packages. However to prevent data loss and/or data migration problems we chose to leave this task to system administrator.
If you were using default database cluster location of /var/lib/pgsql please do following:
1. Prepare new default cluster directory:
mkdir -p /var/lib/postgresql/10/main chown postgres:postgres /var/lib/postgresql/10/main chmod 700 /var/lib/postgresql/10/main
2. Copy or move your existing cluster
cp -rp /var/lib/pgsql/* /var/lib/postgresql/10/main/
mv /var/lib/pgsql/* /var/lib/postgresql/10/main/
3. Start PostgreSQL
service postgresql-10 start
4. If you have double and triple checked that everything works, delete old database cluster
rm -rf /var/lib/pgsql
If you're using non-default database cluster location make sure to modify /etc/sysconfig/postgresql-10 to reflect your configuration
Starting with version 2018.02 TLD Linux has switched from pwdutils package which is no longer maintained to shadow. To receive upgrades for your user/group/password utilities you must install shadow package:
poldek -Uv shadow
This will automatically remove pwdutils package.
Additionaly shadow utils will now by default create separate group for each user added to system for greater flexibility in user and privileges management. In TLD 2018.01 and earlier all users were put to “users” group with GID 1000.
If you wish to use separate “per user” groups it may be a good idea to add groups for existing users and change their primary group from “users” to personal one so they follow current default scheme. Note: UID 1000 is now considered as system ones and shouldn't be used for user accounts.
If you prefer previous behavior please edit /etc/login.defs file and change value of option USERGROUPS_ENAB to no.
Due to switching to personal user groups xrdp now by default allows logins only for members of special xrdp group instead of users group. Please adjust your system configuration or you may not be able to login via xrdp. Also root logins are now not allowed by default. You can enable them again by altering xrdp configuration.