You're the one whoIt's titled it a megathread... they always go off topic. But the original question was asked in here, so I responded in here. I don't have the ability to break off discussions into new topics. If you feel that is needed, feel free to report the posts and a mod can take it from there.

EDIT: Sorry, I realize now that it came off as attacking. It wasn't meant that way!

1 members found this post helpful.

I was kind of thinking the same thing. However, SSD storage is a lot more common now than it was when 14.2 was released 4 years and 7 months ago. So perhaps it is on-topic after all.

@upnort

This huge update will change almost everything in the root partition. On my main computer 40% of the partition is used, but on a laptop it is almost 80%. This is why I asked if there is something to do during the update (fstrim in my message) to improve the health or performance of this partition, or if the hardware of the filesystem are able to manage this.
In the same way, the size of kde is 1/3 of the packages. To update everything in kde I 'upgradepkg' every package in kde/. Maybe it is better (for fragmentation) to 'removepkg' the old versions of everything, and then 'installpkg' the new ones.

If you're not running KDE at the time of upgrading (which you shouldn't really be running any GUI and ideally should be in init 1), it shouldn't be an issue to removepkg everything from kde/ first and then installpkg the new stuff, but if you do that for any other directories, it could break system packages that are needed to properly upgrade the system (however, if you installed aaa_glibc and aaa_libraries, the chances of that should be slim to none).

I have tested first removing all packages. Doing so removes the important system packages and hangs the system. Let upgradepkg --install-new handle the bulk of the load. Then remove the stale packages.

And you didn't record the display as you did this? I'm so disappointed. I guess I'll just have to wreck one of my own Slackware systems to see what it looks like. I'm pretty sure I have a laptop around here somewhere...

I wasn't interested in "show and tell." I just wanted to get my shell script wrapper to function correctly. All work and no play makes me a dull person.

1 members found this post helpful.

Looks like the difference is a new monitorLVDS-1 entry in ~/.config/xfce4/xfconf/xfce-perchannel-xml/xfce4-desktop.xml. I think the entry replaces the monitor0 entry but I haven't yet tested with a simple text edit.

Looks like this is resolved with editing /etc/profile.d/freetype.sh to use classic hinting version=35.

you can use e4defrag -c to get a defragmentation status (ext4 only), and use the same binary to defrag if necessary. e4defrag is part of e2fsprogs and has a man page.

you can issue a manual fstrim -v -all if worried about trimming, before and after the upgrade.

In Current, spoof protection in /etc/host.conf will create stderr spew. Easy to fix by removing the spoof options. Some details here.

Updating causes stderr spew when using alsactl. The remedy might be deleting /var/lib/alsa/asound.state.lock. Not yet tested though.