Re: swsusp: allow resume from initramfs

From: Nigel Cunningham (ncunningham_at_cyclades.com)
Date: 03/04/05

  • Next message: Pavel Machek: "Re: swsusp: allow resume from initramfs"
    To: Pavel Machek <pavel@suse.cz>
    Date:	Sat, 05 Mar 2005 08:22:07 +1100
    
    

    Hi Pavel et al.

    On Sat, 2005-03-05 at 04:50, Barry K. Nathan wrote:
    > On Fri, Mar 04, 2005 at 03:04:10AM -0800, Andrew Morton wrote:
    > > I don't understand how this can be affected by the modularness of the
    > > kernel. Can you explain a little more?
    > >
    > > Would it not be simpler to just add "resume=03:02" to the boot command line?
    >
    > In addition to what others have mentioned, there's also the situation
    > where swap is on a logical volume. In that case, the initramfs needs to
    > get LVM up and running before you can even think about resuming.
    >
    > Swap on a logical volume is the default Fedora Core 3 partition layout,
    > and I imagine it's the default for Red Hat Enterprise Linux 4 as well.

    You guys are reinventing the wheel a lot at the moment and I'm in the
    middle of doing it for x86_64 lowlevel code :> Can we see if we can work
    a little more closely - perhaps we can get some shared code going that
    will allow us to handle these issues without stepping on each others'
    feet? In particular, shared code for

    - initramfs and initrd support
    - lowlevel suspend & resume

    would be good, wouldn't it?

    I'm tempted to add setting and checking signatures, but I'm also in the
    middle of implementing support for writing the image to a file, so that
    could get messy.

    Regards,

    Nigel

    -- 
    Nigel Cunningham
    Software Engineer, Canberra, Australia
    http://www.cyclades.com
    Bus: +61 (2) 6291 9554; Hme: +61 (2) 6292 8028;  Mob: +61 (417) 100 574
    Maintainer of Suspend2 Kernel Patches http://suspend2.net
    -
    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/
    

  • Next message: Pavel Machek: "Re: swsusp: allow resume from initramfs"

    Relevant Pages

    • Re: 2.4.22 hangs with pcmcia and linux-wlan
      ... If I use the kernel tree's code, I can insmod okay, but my ... >> Regards, ... Nigel Cunningham ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: What does tainting actually mean?
      ... If it's in the kernel itself, ... We could check all the calls the module makes to open source ... Nigel Cunningham ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: What does tainting actually mean?
      ... > There has already been a case mentioned of a binary module that messed ... > proprietary code running in kernel space, and aside from calls to kernel ... Nigel Cunningham ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: [Swsusp-devel] Re: swsusp problems [was Re: Your opinion on the merge?]
      ... On Wed, 24 Mar 2004, Nigel Cunningham wrote: ... > I think it's really important that we have some eye candy. ... > bounds, a small increase in kernel size is worth it, in my opinion. ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: [PATCH 1/3] 2.6.8-rc4-mm1 - Fix UML build
      ... can access them all, and initialized data all before uninitialized, so ... SYMLINKS:= $,$/$f) ... semaphore.c-dir = kernel ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)