Date: Fri, 2 Mar 2001 13:59:48 -0600 From: Mike Meyer <mwm@mired.org> To: Brooks Davis <brooks@one-eyed-alien.net> Cc: Bob Johnson <bob@eng.ufl.edu>, dcs@newsguy.com, nickhead@folino.com, stable@FreeBSD.ORG Subject: Re: KERNCONF instead of KERNEL? Message-ID: <15007.64436.475064.323404@guru.mired.org> In-Reply-To: <20010302105521.A29174@Odin.AC.HMC.Edu> References: <3A9FEBF1.8C1A5AC4@eng.ufl.edu> <20010302105521.A29174@Odin.AC.HMC.Edu>
next in thread | previous in thread | raw e-mail | index | archive | help
Brooks Davis <brooks@one-eyed-alien.net> types: > On Fri, Mar 02, 2001 at 01:52:33PM -0500, Bob Johnson wrote: > > You can't reboot to single user mode when you are doing a remote > > update. He is specifically asking about the best way to do > > a remote update. You have to do everything multiuser and accept > > the risk, but there is still the question of what order minimizes > > the risk. > The give one is it. It's going to be pretty easy to talk a NOC monkey > through booting the system on the old kernel, but damn near impossiable > to get them through recovering a system with a busted kernel and a > userland that won't work with the old one. How well does setting the serial console help in this case? I've not used it, as my remote admin experience is with hardware that lets you talk to the mobo rom via a serial line. If the appropriate serial flags will let you work in single user mode over a serial line, then you can do the installworld in single user mode. If they let you boot an alternate kernel over a serial line, then you're set, aren't you? <mike -- Mike Meyer <mwm@mired.org> http://www.mired.org/home/mwm/ Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information. 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?15007.64436.475064.323404>