On 2016-12-28 18:21, Anton Aylward wrote:
On 12/28/2016 11:45 AM, Carlos E. R. wrote:
On 2016-12-28 16:44, Anton Aylward wrote:
So, Carlos, did you eliminate plymouth from your initrd? How did you do that?
Uninstall the package, blacklist it, then run mkinitrd :-)
Well it complained about the the absence, but so what?
The new mkinitrdwhatsthename... ah, dracut, it is way to talkative for my liking. I fail to see what is important. And it writes even more to syslog... tons of pages.
What bothered me was the absence of the following modules
* unix * atkbd * swap * ext2 * LVM2_member
Does that matter?
I don't know. It could also be that they are builtins to the kernel, not modules.
Initrd now down from 12M to 9M
Yes. Not long ago it was big enough so that three kernels would not fit in my separate /boot partition. And you know that during the update of a kernel there are three in existence: the current, the previous, and the new. After the reboot, a process delete the "was previous", leaving again two only. After I replaced my hard disk with a bigger one, I resized the partitions: Telcontar:~ # df -h /boot/ Filesystem Size Used Avail Use% Mounted on /dev/sda5 1011M 44M 917M 5% /boot Telcontar:~ # Way too big, but I thought the same thing on previous iterations... -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)