On 10/14/2012 at 3:13 AM, "Genes MailLists" <li...@sapience.com> wrote: > >I just converted a laptop with encrypted /home and /swap to >systemd - >initscripts has been removed. Luks via standard (new) /etc/crypttab > >Things went swimmingly well (thank you to those who contributed to >the >wiki). > >One thing is a bit less than ideal - at boot - the prompt for luks >password appears - but the screen gets ovrewritten with other >'stuff' - >I can type the password fine its just not directly after the >prompt >where the *** get written - assume its the parallel boot and other >things want to say 'ok'. > >Is there a 'nice' way to handle this? > >Thanks > >gene > > >[testing repo - fully updated]
I'd recommend playing around a bit with the "loglevel" kernel parameter. You might find a level where this output is omitted. I personally just went to booting "quiet" after I finished testing systemd for my systems. mfg narve after my initial testing of systemd was finished.
