Date: Tue, 16 Mar 2004 21:34:30 -0500 From: Garance A Drosihn <drosih@rpi.edu> To: freebsd-sparc64@freebsd.org Subject: Re: Reasons for 64-bTT & DHCP import Message-ID: <p06020414bc7d6996f710@[128.113.24.47]> In-Reply-To: <xzp3c8adq8c.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>
next in thread | previous in thread | raw e-mail | index | archive | help
At 5:33 PM +0100 3/15/04, Dag-Erling Sm=F8rgrav wrote: >Marcel Moolenaar <marcel@xcllnt.net> writes: >> I don't think there are specific reasons not to upgrade. > >I have one: the version in the base system is the exact same as >that in the ports tree, and it's broken beyond belief on 64-bit >systems. I posted a patch to this list a few weeks ago for this >specific issue, but there are probably other, more deeply hidden >ones. 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. Reminder: I have not been looking into the problems with dhcp vs 64-bTT. I hope someone else is... -- 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?p06020414bc7d6996f710>