Date: Wed, 03 Feb 1999 22:43:21 -0500 From: Mike Tancsa <mike@sentex.net> To: "Jordan K. Hubbard" <jkh@zippy.cdrom.com> Cc: BSD-Stable <freebsd-stable@FreeBSD.ORG> Subject: Re: 3.0 stable Message-ID: <4.1.19990203224002.057d9b60@granite.sentex.ca> In-Reply-To: <37717.918098033@zippy.cdrom.com> References: <Your message of "Thu, 04 Feb 1999 01:03:37 -0200." <36B90E09.D2E22CED@netshell.vicosa.com.br>
next in thread | previous in thread | raw e-mail | index | archive | help
At 10:13 PM 2/3/99 , Jordan K. Hubbard wrote: >> sorry about this stupid question, but i heard that 3.0 stable are not so >> stable as 2.2.8 .... >not made any of my systems less stable, I can say that much, and much >of what has been touted as "instability" lately has more to do with >people upgrading from /usr/src and running over all the bumps of >trying to transition an a.out system to an ELF one in developer mode >with no seat belts. Those that do binary upgrades from, or (more >recommended) clean installations of 3.1 will not suffer from those >problems. Is there an easy way to find out if there are still some a.out libs or binaries on a machine that has been 'transitioned' ? One of my SMP machines during heavy load is rebooting without any warning. In other words, is there a reccomended audit I could do on the machine to make sure the a.out-elf transition was done properly ? It started out as a 3.0 STABLE box from Dec. ---Mike ********************************************************************** Mike Tancsa, Network Admin * mike@sentex.net Sentex Communications Corp, * http://www.sentex.net/mike Cambridge, Ontario * 01.519.651.3400 Canada * To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4.1.19990203224002.057d9b60>