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

Nigel Cunningham wrote:

This patch doesn't look right to me. After it is applied, the user will have no way of saying that they don't want to resume (noresume). I assume the removal of resume= isn't a problem because you're expecting them to use that other undocumented way of setting resume= that Pavel mentioned a while ago?

Yes, they have. The handing of resume= and noresume are now done in kinit; resume is invoked from userspace by direct command only.

There is nothing undocumented about it.

	-hpa
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: [klibc] [klibc 30/31] Remove in-kernel resume-from-disk invocation code
    • From: maximilian attems <[email protected]>
  • Re: [klibc 30/31] Remove in-kernel resume-from-disk invocation code
    • From: Nigel Cunningham <[email protected]>

• References:
  • Re: [klibc 30/31] Remove in-kernel resume-from-disk invocation code
    • From: Nigel Cunningham <[email protected]>

• Prev by Date: Re: 2.6.17-mm6
• Next by Date: [patch] i386: early fault handler
• Previous by thread: Re: [klibc 30/31] Remove in-kernel resume-from-disk invocation code
• Next by thread: Re: [klibc 30/31] Remove in-kernel resume-from-disk invocation code
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]