home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.linux
- Path: sparky!uunet!bcstec!aw108!vds7789
- From: vds7789@aw2.fsl.ca.boeing.com (Vincent D. Skahan)
- Subject: Re: SLS bug: a4 updates
- Message-ID: <1993Jan21.154421.13949@aw2.fsl.ca.boeing.com>
- Organization: none
- References: <1993Jan19.080611.21485@sol.UVic.CA>
- Date: Thu, 21 Jan 1993 15:44:21 GMT
- Lines: 33
-
- pmacdona@sanjuan (Peter MacDonald) writes:
-
- >Well I am writing this from the console after doing a minimal
- >install of SLS, which kind of eliminates the possibility that
- >SLS is broke.
-
- 'broke' is a relative term.
-
- if you mean your master copies of everything install and run ok,
- then I understand.
-
- >Anyways, I have fixed them all except bin.tpz, which I will
- >do tomorrow (tuesday) morning (to big to do tonite).
-
- >Look for them there, then download the whole a4 disk again.
- >I guess this goes to show, to many changes in to little time
- >is not a good thing.
-
- it also goes to show that there is a DEFINITE need for some
- method of identifying a version number for each and every kit
- and doc file in SLS, so that we can positively identify where
- our local configurations have drifted out of synch from your
- master ('not broke') configuration.
-
- please...please...please...
-
- Come up with something to help us not get this frustrated
- forever...
-
- --
- --------- Vince Skahan ----- vds7789@aw101.iasl.ca.boeing.com -------
- Hypocrisoda - the diet soda you drink so you can have an extra piece of
- fudge without fear of gaining weight.
-