Path: csiph.com!news.mixmin.net!eternal-september.org!reader01.eternal-september.org!.POSTED!not-for-mail From: Andreas Kohlbach Newsgroups: comp.os.linux.misc Subject: Re: Fwd: Linux on a small memory PC Date: Sun, 10 Jul 2022 17:57:18 -0400 Organization: A noiseless patient Spider Lines: 43 Message-ID: <87sfn8pr5t.fsf@usenet.ankman.de> References: <871quvs7m8.fsf@usenet.ankman.de> MIME-Version: 1.0 Content-Type: text/plain Injection-Info: reader01.eternal-september.org; posting-host="c18144b285b1ecc88e7650e2ad06eaac"; logging-data="1563059"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX197c7+jpnJPPGroJYRUgm7w" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.1 (gnu/linux) Cancel-Lock: sha1:jNz8qL4KQc0+yCsR80nbSzgIxSg= sha1:Gq70A3fxh7WuJK5vBgxWCBgr+lo= Xref: csiph.com comp.os.linux.misc:35010 On Sun, 10 Jul 2022 00:45:42 -0400, 25B.Z959 wrote: > > -------- Forwarded Message -------- Why using "Forwarding" and quote my headers? In other article it was done as it's supposed to. > On Fri, 8 Jul 2022 19:35:33 +0100, The Natural Philosopher wrote: >> >> On 08/07/2022 19:04, Andreas Kohlbach wrote: >>> On Fri, 8 Jul 2022 09:48:30 +0100, The Natural Philosopher wrote: >> >> They weren't. Just some legacy COBOL code was all. > > There was a lot. Starting with MS-DOS before 5.0. which weren't not > Y2K-compliant. > > In 2003 I bought an already old Pentium I (1996-ish). The BIOS would not > allow to set 2003 as year and went back to 19-something (probably 1903, > but I forgot). Subsequently a fairly new Linux did the same. I seem to > remember that I told Linux in a start-script to add 100 years to the > date. I was at that time in a cheap hotel, and WIFI wasn't around there, > so no NTP to access which would have taken care of it. > > There is more. I think early Apple ][ failed Y2K too. > > I had to abandon a whole, rather expensive, database > system because of Y2k issues. Lots of effort put in, > just to be flushed. Which system was it? > Oh well, almost 80 years before we have THAT problem > again ..... 2000 - 80 = 1920 ? 2038 - 80 = 1958 ? The Y2K38 problem sends clocks back about 137 years. I have no idea what you mean. -- Andreas