Date: Wed, 17 Mar 2004 14:37:46 -0500 From: Garance A Drosihn <drosih@rpi.edu> To: Kris Kennaway <kris@obsecurity.org> Cc: freebsd-sparc64@freebsd.org Subject: Re: Reasons for 64-bTT & DHCP import Message-ID: <p06020419bc7e5827e15c@[128.113.24.47]> In-Reply-To: <20040317023908.GA56755@xor.obsecurity.org> References: <20040314210709.GA6482@dhcp01.pn.xcllnt.net> <200403151528.i2FFSe602853@netlx014.civ.utwente.nl> <20040315161833.GA10855@dhcp01.pn.xcllnt.net> <xzp3c8adq8c.fsf@dwp.des.no> <p06020414bc7d6996f710@[128.113.24.47]> <20040317023908.GA56755@xor.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
At 6:39 PM -0800 3/16/04, Kris Kennaway wrote: >On Tue, Mar 16, 2004, Garance A Drosihn wrote: > > >> Hmm. The version in ports seemed to work fairly reliably in > > my limited testing. The version in the base system almost > > never worked for me, so I assumed they were different. > >It's possible the base system version has an incorrect configuration >file; these are typically generated statically by the person who >does the import, so they can sometimes become stale when new >versions are imported, or perhaps a sparc64 version was never >imported in the first place. Dag-Erling Sm=F8rgrav wrote: >I committed a ton of patches to the port last night, including >one that should fix the 64-bit time_t issue. This is excellent to see. Thanks! Hopefully that will go a long way to fixing the problems that people are seeing, and then we can get the same fixes into the base-system version. -- Garance Alistair Drosehn =3D gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?p06020419bc7e5827e15c>