Date: Wed, 17 Mar 2004 22:32:25 -0500 From: Garance A Drosihn <drosih@rpi.edu> To: des@des.no (Dag-Erling =?iso-8859-1?Q?Sm=F8rgrav?= ) Cc: freebsd-sparc64@freebsd.org Subject: Re: Check the latest DHCP vs 64-bTT Message-ID: <p06020423bc7ec78afce2@[128.113.24.47]> In-Reply-To: <xzp65d297ic.fsf@dwp.des.no> 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> <p06020419bc7e5827e15c@[128.113.24.47]> <xzp65d297ic.fsf@dwp.des.no>
next in thread | previous in thread | raw e-mail | index | archive | help
At 4:08 AM +0100 3/18/04, Dag-Erling Sm=F8rgrav wrote: >Garance A Drosihn <drosih@rpi.edu> writes: >> 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. > >well... a bunch of those patches were actually taken from the base >system :) the log message contained a fairly detailed list. Well, I'm confused, but then I haven't been paying close attention to the dhcp issues. Everyone who needs dhcp should try the base-system version, I guess, and let me know if it is now working correctly. It certainly wasn't when I last tested it. If it is working right, I'll remove or reword the special blurb about dhcp in UPDATING.64bTT. If it isn't working right, then check the port and let us know if that works any better. -- 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?p06020423bc7ec78afce2>