Bug#247054: Crypto-root patch updated to initrd-tools 0.1.70
On Mon, Jun 07, 2004 at 08:07:16PM +1000, Herbert Xu wrote:
> On Mon, Jun 07, 2004 at 12:02:15PM +0200, Wesley W. Terpstra wrote:
> >
> > It looks to me like the initrd doesn't even need to setup root, right?
> > The boot process will replace the entire kernel, it's modules, it's idea of
> > root, everything. This means we just have to get the linux kernel to the
> > point where it can read the saved image.
> >
> > Am I right about this so far?
>
> Exactly. In fact, it would be advantageous to not touch root at all
> since modifying root before resuming may lead to serious data
> corruption.
>
> > If you agree with me so far, then what we really want to do in the initrd is
> > to either find root or find the swap device. Setting up encryption for one
> > is enough. Swsusp is controlled by a kernel-command-line option, so we
> > should check for the option and only if it is set, configure root.
> >
> > Agreed?
>
> Yep that sounds good.
Ok, so in the process of trying to get this to work, I was talking with a
coworker who actually used swsusp once upon a time. He said that the kernel
should ALWAYS be given this "resume" option. If there is nothing to resume,
then the kernel boots from root normally.
This ... sucks. It means that we have to setup both in case the system is
sometimes resumed, but other times rebooted properly. Have you used swsusp?
> > If so, I will update my patch and setup swsusp on my machine to test it.
My stock debian 2.6.6 kernel blew oopses all over the place when I ran
hibernate. Does this even work with 2.6? Crypto root is only supported by
>= 2.6.4, so maybe trying to get this to work doesn't make sense.
--
Wesley W. Terpstra
Reply to: