Re: Fix SWSUSP & !SWAP

From: Jamie Lokier <jamie@shareable.org>
To: Nigel Cunningham <ncunningham@clear.net.nz>
Cc: Andreas Dilger <adilger@clusterfs.com>,
	Pavel Machek <pavel@ucw.cz>, Andrew Morton <akpm@digeo.com>,
	cat@zip.com.au, mbligh@aracnet.com, gigerstyle@gmx.ch,
	geert@linux-m68k.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Fix SWSUSP & !SWAP
Date: Fri, 25 Apr 2003 20:32:35 +0100	[thread overview]
Message-ID: <20030425193235.GB1853@mail.jlokier.co.uk> (raw)
In-Reply-To: <1051295327.1722.7.camel@laptop-linux>

Nigel Cunningham wrote:
> Even if we record in the swapfile - while
> suspending - information that gives us the locations of blocks, we still
> need to find the start of the swapfile, or store it somewhere.

If LILO can do it...

The starting block number does not change unless you delete and
recreate the swapfile.  It has the same requirement for location
stability as the kernel image and initrd for LILO.

So, a patched LILO could record the start of the swapfile when it is
run.  Note that you do this as usual when installing a kernel or when
installing a new swapfile.  There's no need to do it when suspending.

If you're booting with Grub or some other fs-aware bootloader, then
the bootloader can presumably find the start of the swapfile just like
it finds the kernel and initrd.

-- Jamie