From owner-freebsd-stable Tue Mar 12 11:36: 1 2002 Delivered-To: freebsd-stable@freebsd.org Received: from pc3-cove5-0-cust178.bir.cable.ntl.com (pc3-cove5-0-cust178.bir.cable.ntl.com [213.105.113.178]) by hub.freebsd.org (Postfix) with ESMTP id 6F48337B402 for ; Tue, 12 Mar 2002 11:35:53 -0800 (PST) Received: from alpha.private.lan (alpha.private.lan [192.168.0.2]) by pc3-cove5-0-cust178.bir.cable.ntl.com (8.11.6/8.11.6) with ESMTP id g2CJZnP50720 for ; Tue, 12 Mar 2002 19:35:49 GMT (envelope-from ianjhart@ntlworld.com) Received: from ntlworld.com (alpha.private.lan [192.168.0.2]) (authenticated bits=0) by alpha.private.lan (8.12.2/8.12.2) with ESMTP id g2CJZlDl041281 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT) for ; Tue, 12 Mar 2002 19:35:47 GMT (envelope-from ianjhart@ntlworld.com) X-Authentication-Warning: alpha.private.lan: Host alpha.private.lan [192.168.0.2] claimed to be ntlworld.com Message-ID: <3C8E5893.6802DEE5@ntlworld.com> Date: Tue, 12 Mar 2002 19:35:47 +0000 From: ian j hart X-Mailer: Mozilla 4.79 [en] (X11; U; Linux 2.4.2 i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-stable@FreeBSD.ORG Subject: Re: Remote upgrading (was: /etc/make.conf question) References: <200203121201050707.044E239E@luna.affordablehost.com> <20020312074349.A91204@blackhelicopters.org> <20020312155618.GA9463@raggedclown.net> <20020312114158.A92910@blackhelicopters.org> <5.1.0.14.0.20020312113310.05cd6028@pop3s.schulte.org> <15502.19126.331274.336789@guru.mired.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-milter (http://amavis.org/) X-Filter-Version: 1.8 (alpha.private.lan) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Mike Meyer wrote: > > Christopher Schulte types: > > At 06:19 PM 3/12/2002 +0100, Erik Trulsson wrote: > > >Now, if you can ensure that the machine is "quiet" in some other way, > > >for example by not running any applications yourself and making sure > > >nobody else is logged in, and are confident that the new kernel will > > >work then there is no reason you can't do a remote upgrade. > > > > Ideally, > > > > Log out all users but yourself. > > > > Unmount all network drives. > > Unfortunately, that includes /usr/src and /usr/obj on some of my > machines :-). > > > Stop all inet services. > > See above. > > > Kill all processes not critical to the running system such as cron, > > syslogd, inetd, sshd ( just the master listening process ). I just run a > > ps until I feel I've killed everything I can. > > > > I've done a ton of these remote installs. They've been safe for me. > > On msvhines that I install with an nfs-mounted /usr/src and /usr/obj, > I reboot to multiuser, then shutdown to single user. That hasn't > casued me a problem yet either. I think you've been lucky. If you reboot after installkernel you may not be able to mount your source. This has bitten me more than once. This is doubly important if you can't easily get to the console to boot kernel.old. If the machine is really remote, a dry run on an identical local machine is probably a good idea. I do all my upgrades (bar 1) remote with nfs mounted source. The only times I've had problems were occasions when I've accidently rebooted. I suspect a similar caveat may apply to the vinum userland stuff. I once had "vinum start" fail, but this could have been pilot error. > > The trick is to make sure that all the kernel modules are updated as > well as the kernel, and not to let them get to far out of sync. And, > of course, to be prepared for the worst. -- ian j hart To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message