On Wed, 23 Oct 2013 01:40, Jan Engelhardt <jengelh@...> wrote:
On Tuesday 2013-10-22 19:08, Yamaban wrote:
As it is, mkinitrd runs every kernel update at least, would it
that bad to run it during system install / update once?
Kernel updates potentially bring in new modules, and you want
thse new modules in the initrd, therefore, on kernel update,
the %post scriptlets will generate the particular initrd
that needs to be regenerated.
Not what I whated to point out, no, my point was:
Instead of leaving the premade 'anyting and all' initrd, that is
brought in during install, as final step for the installation /
distro upgrade (meaning after the first batch of updates),
check if the initrd is still the inital one, if yes call
mkinitrd / dracut to build a smaller, host specific initrd.
That can be done in background, with a nice value.
- smaller initrd, means faster load of initrd by kernel
- less unused modules loaded (what isn't there can't bring errors)
- 'felt' personalised system (it's made for ME, not for the masses)
- made sure the 'theme' the user selects for boot menu is installed.
It's a mix of measureable and just feeling.
No extra work if initrd is build anyway (other than making sure to use
host-specific mode for any call to mkinitrd / dracut).
To unsubscribe, e-mail: opensuse-factory+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-factory+owner(a)opensuse.org