On Monday 02 April 2012 14.14:34 Raymond Wooninck wrote:
Hi Ludwig,
On Monday, April 02, 2012, Ludwig Nussel
wrote: Frederic Crozat wrote:
[...] Don't bother supporting text for cryptsetup in initrd plymouth : it won't work because you would need to pull pango and so on in initrd, which make it huge. Best would be to have a different splash (usually with a lock before the text field).
Uhm, how does the user know which volume the prompt refers to then? Maybe the text could be pre-rendered at mkinitrd time?
The current setup will show messages as soon as /usr has been mounted. I have made a small script that asks for a truecrypt password to mount an encrypted partition. This works fine with the plymouth display-text functionality.
It also show which volume on the text-mode, and so I assume all necessary informations are around. volume by volume.
I am wondering if all information regarding the LUKS disks is present at the moment that the initrd file is generated. Also the system has to be able to generate png files for this. An alternative could be is to somehow force that the LUKS passwords are asked before plymouth is started. This can then be done on a normal console which can display text. My question would be how many users of openSUSE do we have that are using LUKS ?
bilions for sure, nobody using a laptop use an unencrypted / did they? :D
Regards
Raymond
One crazy idea, can't plymouth reuse the font needed by grub/grub2 ? those are available before any unlocking
-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch openSUSE Member & Ambassador GPG KEY : D5C9B751C4653227 irc: tigerfoot -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org