Date: Mon, 09 Oct 2000 02:25:43 -0700 From: Kent Stewart <kstewart@urx.com> To: Warner Losh <imp@village.org> Cc: Scott Dodson <sdodson@beoclu-01.phy.gasou.edu>, Jon Paterson <jpaterson@itchannel.net>, "'freebsd-stable@freebsd.org'" <freebsd-stable@FreeBSD.ORG> Subject: Re: Correct sequence for keeping a 4.1 system stable. Message-ID: <39E18F17.2D013442@urx.com> References: <Pine.BSF.4.21.0010090243500.8019-100000@beoclu-01.phy.gasou.edu> <200010090647.AAA09610@harmony.village.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Warner Losh wrote: > > In message <Pine.BSF.4.21.0010090243500.8019-100000@beoclu-01.phy.gasou.edu> Scott Dodson writes: > : Hmm, I don't know why. Those problems were going from 4.0 -> 4.1.1 and > : going from 4.1 -> 4.1.1 on another machine. If it happened on just one > : machine i wouldn't rase a question. But his is happening on both, however > : of course I'm the one that's done both the machines. But i don't think > : i've screwd anything else up. > > OK. I'll setup a system and give it a try. I thought that I had no > problems when I had done it. But maybe there's some autopilot effects > going on here. I am following a 4.0-release system that is being upgraded to 4.1.1 stable. It is a training exercise and I'm doing a tail -f and following the upgrade output, which is being redirected to a text file, remotely. The only upgrade problems I've seen lately are those occasional strange ones with perl, i.e., the chmod of libdbsm.a. The upgrade I'm following won't be finished until they get off from work tonight at the earliest. Kent -- Kent Stewart Richland, WA mailto:kbstew99@hotmail.com http://kstewart.urx.com/kstewart/index.html FreeBSD News http://daily.daemonnews.org/ 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?39E18F17.2D013442>