[240] in SIPB_Linux_Development
linux.slackware now linux.slackware.nb
daemon@ATHENA.MIT.EDU (mhpower@MIT.EDU)
Tue Nov 30 23:08:56 1993
From: mhpower@MIT.EDU
To: sipb-afsreq@MIT.EDU
Cc: linux-dev@MIT.EDU
In-Reply-To: "[1180] in SIPB-AFS-requests"
Date: Tue, 30 Nov 93 23:08:42 EST
In response to the following, seemingly authoritative*, remark:
>Sipb/Linux,* Mon Nov 29 1993 21:39:52
>svalente@QUICHE-LORRAINE.MIT.EDU [Gimme some of them cracker thingees.] Unauthentic
>
>There is somewhat less than no reason for linux.slackware to be backed up.
I renamed the linux.slackware volume and mounted linux.slackware.nb on
/afs/sipb/project/linux/slackware. If there were other important
mountpoints for this, then, well, I suppose you just lose, and have to
recreate them yourself. Sorry...
>Sipb/Linux,* Mon Nov 29 1993 21:41:34
>svalente@QUICHE-LORRAINE.MIT.EDU [Gimme some of them cracker thingees.] Unauthentic
>
>linux.sls and linux.tamu also dont need to be backed up. But we should
>possibly get the approval of whoever created the volumes (probably Chad or
>Mark) before changing them to non-backed up.
There isn't a linux.sls.backup (sls is in project.linux-sls.nb). But
there is a linux.tamu.backup ... is this needed?
Matt
* OK, so I did notice it was unauthentic.
