From owner-freebsd-questions Fri May 3 14:51:29 2002 Delivered-To: freebsd-questions@freebsd.org Received: from bsd.alexe.org (slbch-4-m1-19.vnnyca.adelphia.net [24.55.79.19]) by hub.freebsd.org (Postfix) with ESMTP id 7CF2637B420 for ; Fri, 3 May 2002 14:51:15 -0700 (PDT) Received: (from alex@localhost) by bsd.alexe.org (8.12.3/8.12.3) id g43Lswgr024391; Fri, 3 May 2002 14:54:58 -0700 (PDT) (envelope-from alex) Date: Fri, 3 May 2002 14:54:58 -0700 From: Alex Obradovic To: freebsd-questions@freebsd.org, Patrick Soltani Subject: Re: Remote Upgrade Message-ID: <20020503215458.GB16657@montenegro.com> References: <3DBB075EEB95944492E127F2B9A96FAF539525@ultra-exchange.UltraDNS.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3DBB075EEB95944492E127F2B9A96FAF539525@ultra-exchange.UltraDNS.com> User-Agent: Mutt/1.3.27i X-Editor: Vim http://www.vim.org/ X-Info: http://www.alexe.org X-Operating-System: FreeBSD/4.5-STABLE (i386) X-Uptime: 2:50PM up 17:06, 10 users, load averages: 0.03, 0.03, 0.00 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > > I have upgraded my production firewalls, FreeBSD 4.x, over the network with little or no problems. > Here is the recipe, > couple of cvsup for src tree > couple of cvsup for ports tree > make -j 16 buildworld > somefile0 > make buildkernel KERNCONF=MYKERNEL0 > somefile1 > make installkernel KERNCONF=MYKERNEL0 > somefile2 > make installworld > somefile3 > reboot the machine > mergemaster. > My understanding was that we should do mergemaster BEFORE rebooting the machine. I have been updating 3-4 different systems remotely by following this path: cvsup buildworld installworld buildkernel installkernel mergemaster reboot Alex > The last part is kind of tricky, but executed without any options, you get a chance to read the changes and apply the ones you want. > > If the machine is a 7X24 production box and you can not have it downed, then put the lines above into a script, hopefully with some error checking, etc and do a "nice or renice" so it runs in the background and when finished emails you. > > Regards, > Patrick Soltani. > > P.S. Although I have had no problems doing this, I had a console switch with an attached modem hooked up to the serial port so if anything went wrong, still I could get to the machine to revive it. > > > > > -----Original Message----- > > From: Shawn Walker [mailto:shawn@eblend.org] > > Sent: Thursday, May 02, 2002 8:54 PM > > To: freebsd-questions@freebsd.org > > Subject: Remote Upgrade > > > > > > Hello, > > > > I currently have a box running 4.1-RELEASE. It is not > > possible for me > > to gain physical access to the box, so I was wondering if it > > is possible to > > upgrade the box remotely. I have looked at the instructions > > in the handbook > > and in /usr/src/UPDATING, but there is some mention of a few > > steps that > > should be completed in single user mode. Is it possible to do this > > remotely? > > > > Thanks, > > > > -- > > Shawn Walker > > shawn@eblend.org <-----> http://www.eblend.org/ > > > > "In rural areas, we're not going to have full coverage until > > cows talk." > > -- Dan Dan Wilinsky, Sprint PCS > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-questions" in the body of the message > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message