Newsgroups: comp.sys.next
Path: utzoo!utgpu!watserv1!vlsi!ccng!tgoldtho
From: tgoldtho@ccng.waterloo.edu (Thomas A. Goldthorpe)
Subject: Re: A few minor prob left...
Message-ID: <1990Oct17.231958.10800@ccng.waterloo.edu>
Organization: University of Waterloo
References: <9102@milton.u.washington.edu> <1990Oct15.050058.27579@ccng.waterloo.edu> <53614@brunix.UUCP>
Date: Wed, 17 Oct 90 23:19:58 GMT
Lines: 36

In article <53614@brunix.UUCP> rca@cs.brown.edu (Ronald C.F. Antony) writes:
>a) As NeXT has a swapfile and not a swap disk, the second partition should NOT
>be used as swappartition at all.

Did I say to use the second partition of his main disk as swap?  No.

>The point of having a swapfile is that it 
>can grow and shrink (after a reboot) according to the demand and within the
>bounds of the size of the filesystem. By using a swap partition, you get rid
>of this advantage.

What advantage?  You can place your swapfile anywhere.  It will still have
that dynamic characteristic.  If it runs out of space, swapon allows for other
swap files in other partitions to be used anyway.  On a single hard disk
system, of course the only swapfile will be the one created.  On a multiple
hard disk system, there are advantages to having the primary swapfile on
another disk along with /tmp.

>b) The second partition you usually find on bigger NeXT hard drives is there
>to mount network clients. If you have a standalone system, get rid of it and
>make your main file system bigger. This saves a lot of trouble with allocating
>files to filesytems and such 

I agree with making one large partiton, but you are forgetting that you are
suggesting this to some people on the net who haven't the slightest idea how to
go about doing this (or for that matter the amount of time involved in the
backup).  

>c) Don't modify the scripts written by NeXT. They do everything automatically.
>They look for a swapdisk, and if they don't find it, create the standard swap
>file we want to have.

I thought I already said this.