Date: Fri, 20 Nov 1998 10:03:59 -0500 From: Robert Withrow <witr@rwwa.com> To: Robert Withrow <bwithrow@baynetworks.com> Cc: hackers@FreeBSD.ORG, witr@rwwa.com Subject: Re: AMD/NFS problems with 3.0 Message-ID: <199811201503.KAA25644@spooky.rwwa.com> In-Reply-To: Your message of "Wed, 18 Nov 1998 17:29:07 EST." <199811182229.RAA25694@tuva.engeast.baynetworks.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Following up on my posting: All of my *AMD* problems were cured by upgrading to the latest version: am-utils-6.0b2s3. I'd like to suggest that 2.2.8 and 3.next upgrade to, at least, the 6.0 beta stream instead of the alpha code that is in there now. (I still have NFS problems, which I will send to another thread). Also (I know this was discussed before, since I saw a web reference for it in a search I did, but a search of the FreeBSD mailing lists for "am-utils" returns *nothing* related to am-utils, at least for me!) I'd suggest that this should probably be deleted from the BIN distribution. I doubt if more than a small minority of FreeBSD users actually *need* it, and thus it only adds bloat. Also, it builds and runs fine out-of-the-box and it is being actively maintained. It is at least incrementally harder to replace the BIN amd with one you build yourself, since you have to reverse engineer the various paths to issue to the configure script. Another note: for people who build "contrib" code into FreeBSD, it would help if you saved "config.status" when you use a frozen configuration. It saves time and reduces errors when someone else is trying to replace the "contrib" version with a more recent one... Thanks! --------------------------------------------------------------------- Robert Withrow, R.W. Withrow Associates, Swampscott MA, witr@rwwa.COM To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199811201503.KAA25644>