[mk01]

(3rd Jun, 2013 05:43 PM)afrinc Wrote:  I don't know which are realy usefull.
(kernel in testing branch)

I noticed a strange beahiour while installing initramfs, during the dpkg process /boot was unmount.

I don't know how to have splash working.

you know how is it with the non useful packages. "What was I doing last before my pc stopped working? Oh yes, I was removing all the non important stuff"

There was a discussion and consensus at the end, that we better don't mount /boot automatically. it seems that unmounted vfat makes less troubles than mounted and crashed during freeze / too high OC, wrong AC. So in beta1 there is noauto flag in fstab and /boot is mounted according the needs. I was putting check everywhere before /boot mount a check, whether /boot was already mounted. If yes, it should not umount it later ... maybe somewhere (at kernel postinst script is this check missing) so needs to be corrected.

during install of splash, new binaries should be assembled inside initramfs as well to allow early start. during switch_root (from initramfs to real rootfs) the root NameSpace is destroyed and new created and normally running process will not survive this or would not be able to access new root. therefore there is a check for md5sum of splash on initramfs and on rootfs. if not the same (old version would crash or become not controllable), process is killed and after swith root new splash started. but this is fail over, normaly both versions should be the same. Sorry for the details, but with the info you can describe the issue you have more precise ... so what is the issue ?

mk

Quote:I don't know how to have splash working.

the "have" means "get" or "make" or ... ?