Date: Tue, 30 Jul 1996 14:39:37 -0700 (PDT) From: "Rodney W. Grimes" <rgrimes@GndRsh.aac.dev.com> To: dev@trifecta.com (Dev Chanchani) Cc: freebsd-isp@freebsd.org Subject: Re: BSDi --> FreeBSD Message-ID: <199607302139.OAA29439@GndRsh.aac.dev.com> In-Reply-To: <Pine.BSF.3.91.960730153654.195A-100000@www.trifecta.com> from Dev Chanchani at "Jul 30, 96 03:38:15 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
> On Tue, 30 Jul 1996, Rodney W. Grimes wrote: > > > > I have been waiting to upgrade 2.1 -> 2.1.5, however, when the new > > > release came out, many people were having problems. > > > > Can you elaborate on these? I haven't seen many reported 2.1.5 problems. > > Sure, I heard about problems with the 3com 3c509 drivers and such. Just > things like that (i happen to have a 3com 3c509). if_ep has been a sore spot for a long long time, this is nothing new with 2.1.5, though it was broken in the initial release of 2.1.5 and then quickly fixed. > > > Is it safe to do a make world on a running system safely? > > > > Not really, as some things will be in a transitory state for long periods > > of time some programs may core dump. > > Hmm, any recomendations? I'll defer on that one... it is very site specifc as to how to proceded with building things peice meal wise as to not disturb the running system. Read and fully understand the /usr/src/Makefile world: target, most of it can be done while up multiuser, but anything that is going to touch binaries (and that includes /usr/lib) is best done without a load on the system. Those who claim that they have not had problems running ``make world'' on live systems are either very lucky (ie, there load we very light) or they ignored the few programs that dumped core while versions of things where out of sync. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199607302139.OAA29439>