[627] in SIPB_Linux_Development
Slackware 2.0.0
daemon@ATHENA.MIT.EDU (nocturne@MIT.EDU)
Fri Jul 8 03:25:56 1994
From: nocturne@MIT.EDU
Date: Fri, 8 Jul 1994 03:25:40 -0400
To: ghudson@MIT.EDU, linux-dev@MIT.EDU
I've ftp'd most of Slackware 2.0.0 from ftp.cdrom.com, and have untarred it
in /afs/sipb/project/linux/slackware/Slackware.2.0.0 ...
The fetch of Slackware 2.0.0 is still missing a few important disks, though,
so you shouldn't try to install it anywhere yet, and please don't delete
1.2.0 yet.
There is a large ( ~ 30 MB ) directory full of 'contrib' tarfiles, like
lucid emacs, uucp, perl 5, lynx, and other things, which was not a part of
the Slackware 1.2.0 distribution. These files are not really disk-type
packages like the usual install packages (for example, one is over 7
megabytes in size) ...
Do we want this in the linux locker? I think the answer is "yes", but I
still think that it should be considered.
maze was short on space, so I rm -rf'd the contrib directory which was in
/var/slckware-2.0.0 ... I don't see how it could be very useful to serve
this stuff out via NFS, anyway... it seems to me that maze exports NFS so
that people can install from it, rather than mount it at random times for
hand-installation of random tarfiles; ftp to athena.dialup works just as
well for that.
Does anyone disagree with the above point?
- Eric
