Comment 3 for bug 444704

On Wed, 2009-12-23 at 14:37 +0000, Martin Pitt wrote:

> Scott, is there anything which we need to fix in cryptsetup before
> making it acceptable for installing by default? (In terms of slowing
> down boot, plymouth integration, and the like).
>
It must not have any initramfs script, init script or upstart job that
is run in the default case (which isn't true right now).

Having udev rules or upstart jobs only fired as a result of events
signifying the presence of a disk it can handle is fine.

Note that I don't consider having an initramfs script, init script or
upstart job that uses "test" to decide whether to run fine. These cost
a surprisingly significant amount of time, and we don't need them for
things like RAID and LVM.

Also iirc, cryptsetup right now, when installed, forces a framebuffer
and splash screen into the initramfs (so it can ask for a root disk
password); obviously that's incompatible with being installed by
default.

(It's also probably worth noting that cryptsetup is one of those things
that exists on the LiveCD and is removed from the system by ubiquity
when not needed - which makes it more special.)

Scott
--
Scott James Remnant
<email address hidden>