[klibc] [klibc 30/31] Remove in-kernel resume-from-disk invocation code

Nigel Cunningham ncunningham at linuxmail.org
Wed Jul 5 19:18:35 PDT 2006

Hi again.

(Excuse me replying to myself, but this might help someone else).

On Thursday 06 July 2006 11:45, Nigel Cunningham wrote:
> Is there a klibc howto somewhere? I tried googling for 'klibc howto',
> reading the files in Documentation/ and browsing your klibc mailing list
> archive before asking!

> What I'm wondering specifically is: Say a user needs to run some commands
> to set up access to encrypted storage before they can resume. At the
> moment, we'd tell them to put these commands and the echo > do_resume in
> their linuxrc (or init) script prior to mounting their root filesystem.
> Forgive me if I'm asking a stupid question but it's not immediately obvious
> to me how they would now do that. I'd much rather follow a simple howto
> than spend a good amount of time tracing function calls etc. I still see
> init/initramfs.c, and it mentions both CONFIG_BLK_DEV_INITRD and
> CONFIG_BLK_DEV_RAM. Would I be right in surmising that you can still have
> an initrd or ramfs to do such things as the above, after klibc has done its
> work? If not, is there some other way I'm ignorant of?

For the record, I've since discovered that what you really want is an 
initramfs howto. I think I stuck with those old-fangled initrds for too long. 
Better update my desktop from Mandrake 10 too :)... is there a pattern here?

Nigel, Michelle and Alisdair Cunningham
5 Mitchell Street
Cobden 3266
Victoria, Australia
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://www.zytor.com/pipermail/klibc/attachments/20060706/c12619b2/attachment.bin 

More information about the klibc mailing list