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

[Pavel Machek <pavel@suse.cz>]

Hi!

> > > Ah. So it's still valid to have resume= and noresume on the commandline,
> > > and klibc greps /proc/cmdline?
> >
> > Correct.
> >
> > > So, for Suspend2, would I be ok just leaving people to add the echo
> > >
> > >>/proc/suspend2/do_resume, as we currently do for initrds and initramfses?
> >
> > Well, presumably you want to adjust kinit so that it invokes
> > /proc/suspend2/do_resume, instead of or in addition to
> > /sys/power/resume; see usr/kinit/resume.c (the code should be bloody
> > obvious, I hope...)
> 
> It is.
> 
> 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 

Same way as they did it before....? klibc is supposed to be
backward-compatible, as far as userland can tell.
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/