Kernel firmware packages consume a lot of disk space on a Linux system, both on the installed system and in an installation environment (inst-sys). In some cases (e.g. RAM disk for a minimal NET ISO), that also means a lot of RAM usage.
The installed kernel-firmware packages on a Leap 15.5 (screenshot of qdirstat pkg:/kernel-firmware)
sudo zypper in libqt5-qtwebengine-examples
Taken from my GitHub profile / history; omitting duplicate PRs due to merging to SLE-15-SP4, then merging to master.
| The workaround for this was to set LD_PRELOAD if libsuseconnect.so was | |
| found, but that causes new problems: This is inherited by child | |
| processes, and now every binary started from YaST also gets this | |
| LD_PRELOAD, so they are now also force linked to libsuseconnect.so. | |
| YaST uses external programs extensively; among lots of other things, | |
| for storage probing. That means that in many cases, storage probing | |
| now fails because of this; mostly due to out of memory because | |
| libsuseconnect.so (and the Go runtime libs that it uses?) consumes a | |
| lot more RAM. |
This document moved to a new location; this Gist is now a mirror.
This is the method to use since about 2018. Don't use SCR .target.bash in new code.
Author: Stefan Hundhammer shundhammer@suse.com
The YaST installer is a very powerful, but also very complex tool; it is designed to cover a large variety of Linux installation scenarios. The user is asked a lot of questions in a lot of workflow steps; but in many of these, you can simply click "Next" and rely on the defaults.
In regular intervals, somebody tries to come up with something drastically simpler; an installer that is so dumbed down that it is borderline useless for all but the most trivial cases.
