Re: SCCS corruption?

"Melvin P'rez Cedano" wrote: > I think that most of the UNIX vendors fixed the SCCS issues. SCO for example introduced a patch fixing the Y2K problem... And Sun fixed the problems in Solaris 2.5.1 and 2.6 and 7, but not, AFAIK, in Solaris 2.4, nor 2.5. But the person to whom I issued the warning was busy upgrading to SunOS 4.1.3, which does not have those fixes. SunOS 4.1.4 might do; 4.1.3 does not. So this particular person needs to be aware of the issue, as does anybody else who uses SCCS and has not ensured that their system has been made safe. > > -----Original Message----- > From: Info Temp [mailto:inf999@cap-az.com] > Sent: Mi'rcoles 15 de Diciembre de 1999 9:18 AM > > Jonathan Leffler wrote: > > Do not modify SCCS files after the 31 December 1999; you will > > corrupt your files. You are definitely treading on the thinnest of wafer-thin > > ice. > > So, what's the issue with SCCS? I may take a position with the company I'm working > with now. If so, I intended to make source control a priority. No issue if you know that the version of SCCS you are using is Y2K-safe. Old versions are not, in general, and old Sun versions in particular are not safe. I'm glad to see source control is one of your priorities; it is very important. -- Jonathan Leffler (jleffler@informix.com, jleffler@earthlink.net) Guardian of DBD::Informix v0.62 -- see http://www.perl.com/CPAN #include <disclaimer.h>