swapping over NFS (fwd)
fuZZy (tjimenez@site.gmu.edu)
Mon, 8 Apr 1996 03:17:56 -0400 (EDT)
Forwarded message:
> From owner-linux-kernel-outgoing@vger.rutgers.edu Sun Apr 7 08:11:19 1996
> Date: Sun, 7 Apr 1996 16:42:37 +1000 (EST)
> From: David Monro <davidm@cs.su.oz.au>
> Reply-To: David Monro <davidm@cs.su.oz.au>
> Subject: swapping over NFS
> To: linux-kernel@vger.rutgers.edu
> Message-ID: <ML-1.3.2.828859377.8565.davidm@fuzzbox.gh.cs.usyd.edu.au>
> MIME-Version: 1.0
> Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
> Sender: owner-linux-kernel@vger.rutgers.edu
> Precedence: bulk
>
> Having played a bit with a diskless setup (using an eprom and the NFSroot
> option) I have discovered that the main obstacle to a really useful diskless
> CPU server is the inability to swap over nfs. Is anybody working on this? How
> hard would it be?
>
> The only other obstacles I can see to creating a setup where multiple sytems
> share the same root filesystem is a modified version of mount that doesn't use
> /etc/mtab but uses /proc/mounts, and could understand some fancy substitutions
> in the fstab, eg
>
> server:/usr/export/var.@HOSTNAME@ /var nfs defaults 0 0
> server:/usr/export/swapfiles/swap.@HOSTNAME@ none swap defaults 0 0
>
> would mount the appropriate things off the server without having a different
> fstab for different clients. This however I can do myself. (I don't believe it
> is possible to share /var, though I may be wrong. /var/log/wtmp at least must
> persist over reboots (so it can't be on a memfs, unlike stuff in /var/run and
> /var/lock) and must be unique to each machine).
mayhaps it would be more usefull to hack the nfs server to remap
paths, based on the client adress. actually, that sounds kina neat...
--
-fuZZy, paramour to the lady mindy
<did they buy it?>
<I don't think they bought it.>
<of course they bought it.>
<shush, they're looking this way, remember to keep a straight face...>