Date: Thu, 13 Nov 2003 11:41:05 -0800 From: eculp@encontacto.net To: Jesper Skriver <jesper@FreeBSD.org> Cc: freebsd-current@freebsd.org Subject: Re: Unattended reboot was Re: signal 12's everywhere on Current with update this morning. Message-ID: <20031113114105.ee04c4s0kgs8kcc0@mail.encontacto.net> In-Reply-To: <20031113171120.GC73775@FreeBSD.org> References: <20031113064835.qccgccsoowkw0o00@mail.encontacto.net> <20031113145037.GR60410@submonkey.net> <20031113065514.kkcg0ckwsw88okcw@mail.encontacto.net> <20031113073915.yy8s4ooggssk4kw0@mail.encontacto.net> <20031113171120.GC73775@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Mensaje citado por Jesper Skriver <jesper@FreeBSD.org>: | On Thu, Nov 13, 2003 at 07:39:15AM -0800, eculp@encontacto.net wrote: <CUT> | > I'm building new kernels as I write this. My next question is: | > One of the machines I'm building on is remote and was last rebuilt | > just before the change. What would be be better sequence for making | > the change after a fresh cvsup ? | > | > 1. Build and Install a new kernel | > 2. build a new world | > 3. Run mergemaster | > 4. ReBoot (I'm not sure it will come up multiuser with a new | > kernel and a 4 day old userland.) | > 5. Installworld and assess possible problems :-) | | I upgraded a ancient -current last night, I did | | 1) cvsup | 2) build and install new kernel | 3) reboot | 4) build and isntall new world | 5) mergemaster | 6) reboot Jesper, Thanks. I'm already finishing a buildworld but I'm going to reboot after before installworld, I've already installed the kernel. I was afraid it would't go multiuser so I could finish with a ssh. Thanks for confirming that it will, or should :-) ed | | /Jesper | -------------------------------------------------
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20031113114105.ee04c4s0kgs8kcc0>