Bug#389835: [Pkg-cryptsetup-devel] Bug#389835: better out of the box luks root migration support

[maximilian attems]

hello David,

thanks for the quick headup,
was already a bit drunk that night, so i hope i didn't bwarfle too much
;)

On Thu, Sep 28, 2006 at 10:51:56AM +0200, David Härdeman wrote:
> On Thu, September 28, 2006 3:25, maximilian attems said:
> 
> Ah, I see...I'll change the hook to always add the binary and a reasonable
> subset of modules (unless running with MODULES=dep as you said)

great
yes for MODULES=dep faingraining is good,
i thought to call the hook scripts with dep arg if aboves is set,
but until that is implemented, just take a look at aboves setting. :)
 
> > also luks doesn't need an /etc/cryptoroot entry afaik?
> 
> It does require one. And if one had been found, the binaries and modules
> would have been copied to the initramfs. You would also not have had to
> add any cryptopts to the kernel command line.
> 
> In your case, I guess you'd want a line like this:
> croot /dev/sda2 none luks

ok so please add that line to README.initramfs in the LUKS section,,
with a short explanation of which device to list there :)
 
> > the following bootarg worked fine, please add it to the doc
> > root=/dev/sda2 ro cryptopts=target=sda2
> 
> Actually, I'm considering removing support for the "cryptopts" option
> rather than documenting it. The settings should be automatic so the
> cryptopts is just for fixing a messed up installation. However, if the
> crypto is fscked, the user can manually set it up in the initramfs shell
> with about as much effort as writing the proper cryptopts on the command
> line.
> 
> Additionally, I'm going to have to add support for encrypted swap setup
> during boot as well since swsusp won't work otherwise. That would add yet
> another kernel option if "cryptopts" was kept...

ok thanks full ack.

-- 
maks

ps adding Manoj on the cc as the bug report was caused by his trials :)