Date: Fri, 19 Mar 2004 00:57:26 +0200 From: "Wafa M. Hadidi" <wmmh@identd.net> To: Garance A Drosihn <drosih@rpi.edu> Cc: freebsd-current@freebsd.org Subject: Re: Updating sparc64 time_t, hostname not found Message-ID: <200403190057.36638.wmmh@identd.net> In-Reply-To: <p0602043bbc7fce6c9a52@[128.113.24.47]> References: <40594A35.6060303@exeter.ac.uk> <200403190005.22811.wmmh@identd.net> <p0602043bbc7fce6c9a52@[128.113.24.47]>
next in thread | previous in thread | raw e-mail | index | archive | help
=2D----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Friday 19 March 2004 00:28, Garance A Drosihn wrote: > > Okay. Hmm. Well, that indicates that it is not the 64-bTT > change itself which is the problem. Unfortunately, knowing that > does not actually help you. Given your answer, I am also then > at a loss to explain the times you are seeing from 'ls' output. > Its not only an ls problem, using ntpdate for an example to sync my clock i= s also resetting it to the zero. > > The other thing this tells me is that your problem looks the same > as Daniel's problem, but it must be slightly different. He got > all the way to step 17, while you are seeing the problem before > you have changed anything to be 64-bit time_t's. > It was my fault not to mention that early, sorry :) > The fact that you are seeing this at the earlier stage is probably > very significant, but I am not sure what it means... > Though I am not sure, but here is what I think: some files used 32_bTT and = have been updated to use 64_bTT instead. These files lack the ability to de= tect my installation type (32 or 64) and they preassume that 64 is the defa= ult during the makeworld phase. > If you are failing that early in the installworld step, then it > should be true that very little was actually changed. What happens > if you reboot into your previous kernel? Do you still get the odd > time-stamp results from 'ls'? What do you get for the output of > the 'date' command? Something reasonable? Or is it just that > your machine-clock is getting reset to zero? (you might want > to boot up in single-user mode to check that, perhaps your normal > startup process will do things that fix your system's clock). > Rebooting to the old kernel solves everything, ls shows correct time-stamps= and ntpdate syncs to the right time. > Also, if you are upgrading to the latest files in /usr/src, when > did you do your *previous* system upgrade? That might help us > figure out what's happening. My last system upgrade was in Mon Jan 12 09:04:03 EET 2004. =2D --=20 Wafa M. Hadidi | ITUniversity - Jordan Technical Lead | Phone: +962-6-5693251 RHCE, RHCX, SCSA, SCNA | Fax:+962-6-5655266 PGP Key: 0xD4CE9796 fpr: 1D5B C0DB 7055 FC7F 0315 BD72 5C2A 6326 D4CE 9796 =2D----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFAWilXXCpjJtTOl5YRAsCTAKCcak5Qu5IjZyk76YBQDUEla1V3GQCfROv0 coc93qlKLeOFpLDoABWwBkY=3D =3DMV0M =2D----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200403190057.36638.wmmh>