On Wednesday 08 February 2006 00:50, Pavel Machek wrote:
>
> > > > themselves
> > > > (and then have their patches rejected by you) is no way to maintain a part
> > > > of the kernel. Stop being a liability instead of an asset!
> > >
> > > Ugh?
> > >
> > > Lee is a programmer. He wants faster swsusp, and improving uswsusp is
> > > currently best way to get that. It may be alpha/beta quality, but
> > > someone has to start testing, and Lee should be good for that (played
> > > with realtime kernels etc...). Actually it is in good enough state
> > > that I'd like non-programmers to test it, too.
> >
> > I'd rather like to wait with that until there's a howto. :-)
>
> Attached, now Lee or anyone can start hacking.
>
> Suspend-to-disk HOWTO
> ~~~~~~~~~~~~~~~~~~~~
> Copyright (C) 2006 Pavel Machek <[email protected]>
>
>
> You'll need /dev/snapshot for these to work:
>
> crw-r--r-- 1 root root 10, 231 Jan 13 21:21 /dev/snapshot
>
> Then compile userspace tools in usual way. You'll need an -mm kernel
> for now. To suspend-to-disk, run
>
> ./suspend /dev/<your_swap_partition>
>
> . (There should be just one, for now.) Suspend is easy, resume is
> slightly harder. Resume application has to be ran without any
> filesystems mounted rw, and without any journalling filesystems
> mounted at all, preferably from initrd (but read-only ext2 should do
> the trick, too). Resume is then as easy as running
>
> ./resume /dev/<your_swap_partition>
>
> . You probably want to create script that attempts to resume with
> above command, and if that fails, fall back to init.
If it's run fron an initrd, it'll fall back automatically. Also you can set
the name of the resume partition in the header file swsusp.h and
you'll be able to use the tools without any command line
parameters (useful if you want to start resume from an initrd).
Besides, an -mm kernel is needed for this to work (preferrably
2.6.16-rc1-mm5, for now), and the CVS changes on a daily basis.
Greetings,
Rafael
-
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/
[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]
