From owner-freebsd-alpha Thu Feb 22 21:42:33 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from grafin.fujimori.cache.waseda.ac.jp (grafin.fujimori.cache.waseda.ac.jp [133.9.152.154]) by hub.freebsd.org (Postfix) with ESMTP id 79F9937B4EC for ; Thu, 22 Feb 2001 21:42:30 -0800 (PST) (envelope-from fujimori@grafin.fujimori.cache.waseda.ac.jp) Received: from grafin.fujimori.cache.waseda.ac.jp (fujimori@localhost [127.0.0.1]) by grafin.fujimori.cache.waseda.ac.jp (8.9.3/3.7W) with ESMTP id OAA26957 for ; Fri, 23 Feb 2001 14:42:29 +0900 Message-Id: <200102230542.OAA26957@grafin.fujimori.cache.waseda.ac.jp> To: freebsd-alpha@freebsd.org Subject: funny clock on some alphas Date: Fri, 23 Feb 2001 14:42:29 +0000 From: Yoriaki FUJIMORI Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Folks, At the beginining of January, I asked about a possible y2k problem on some alpha boxes. The problem is that the machie date is set to year 2000 and not year 2001 after shutdown. I first experienced this on old alphapc164. I thought that SRM of that box is not good. # I remember someone from Germany wrote the same complaint here. These few days I have been playing around a new up1100 based alpha box with FreeBSD 4.2R. UP1100 has got a new SRM, that has got a command `date' in SRM itself---we can set the date as >>> date 200102231430.40 When I rebooted the system I noticed that the date is reset to 2000! When I ran SuSE7.0(Linux) on that beast, no problem like that. The problem seems to be solely specific to FreeBSD/Alpha. Now, I come to believe that some of codes related to shutdown process may not be y2k compliant. Yoriaki FUJIMORI To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message