Date: Thu, 19 Feb 2004 08:38:38 -0600 From: Tillman Hodgson <tillman@seekingfire.com> To: sparc64@freebsd.org Subject: Re: Back to the Future - 64-bit time_t on sparc64 Message-ID: <20040219143838.GL68388@seekingfire.com> In-Reply-To: <20040217040616.GL12181@seekingfire.com> References: <p06020407bc533f0ae9d2@[128.113.24.47]> <40306CE7.6080104@mindspring.com> <20040216193108.GE12181@seekingfire.com> <p0602041ebc56dd660908@[128.113.24.47]> <20040217040616.GL12181@seekingfire.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Feb 16, 2004 at 10:06:16PM -0600, Tillman Hodgson wrote: > I'm currently upgrading to the latest -CURRENT in > 32-bTT mode. I'm also going through my ports to see if I can weed out > any that I don't need anymore in order to save time reocmpiling later. The upgrade to 64bTT went smoothly, with /usr/src being NFS mounted and /usr/obj being local (I skipped the mount_nfs step for /usr/obj). The kadmin daemon out of security/krb5 signal 11's repeatedly (it's launched by inetd) until it's upgraded. Postfix (and thus mailman) don't seem happy until they're recompiled. Apache+modssl, openvpn and quagga seemed to work correctly without recompiling (though I did anyway). All in all, it's a pretty smooth upgrade. The worst part of it is how slowly the Ultra 5 compiles due to the slow IDE interface ;-) I haven't tried a cvsup yet -- cvsup-without-gui is still recompiling. Is there a rough timeline for when the 64bTT change might go into src? If it's in the next month or so I won't worry about applying the patch by hand as I only rebuild world occassionally. -T -- Page 41: Two of the most important Unix traditions are to share and to help people. - Harley Hahn, _The Unix Companion_
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040219143838.GL68388>