From owner-freebsd-stable  Wed Dec 26 12:37:52 2001
Delivered-To: freebsd-stable@freebsd.org
Received: from clink.schulte.org (clink.schulte.org [209.134.156.193])
	by hub.freebsd.org (Postfix) with ESMTP id B2E7037B417
	for <stable@FreeBSD.ORG>; Wed, 26 Dec 2001 12:37:43 -0800 (PST)
Received: from schulte-laptop.nospam.schulte.org (nb-65.netbriefings.com [209.134.134.65])
	by clink.schulte.org (Postfix) with ESMTP
	id 68E1E2440D; Wed, 26 Dec 2001 14:37:42 -0600 (CST)
Message-Id: <5.1.0.14.0.20011226142742.03c2fde0@pop3s.schulte.org>
X-Sender: 
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Wed, 26 Dec 2001 14:37:16 -0600
To: "Mike Meyer" <mwm-sender-77771d@mired.org>,
	Christopher Schulte <schulte+freebsd@nospam.schulte.org>
From: Christopher Schulte <schulte+freebsd@nospam.schulte.org>
Subject: Re: make buildkernel fails on behalf of config version
Cc: cjclark@alum.mit.edu, Brian Behlendorf <brian@hyperreal.org>,
	stable@FreeBSD.ORG
In-Reply-To: <15402.12857.406331.699967@guru.mired.org>
References: <5.1.0.14.0.20011226135014.03758008@pop3s.schulte.org>
 <20011226105454.Y92442-100000@localhost>
 <20011225153309.C136@gohan.cjclark.org>
 <5.1.0.14.0.20011226135014.03758008@pop3s.schulte.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-stable.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-stable>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-stable>
X-Loop: FreeBSD.ORG

At 02:25 PM 12/26/2001 -0600, Mike Meyer wrote:
>Given a reasonable processor, it's not "many hours", it's more like 15
>minutes even with "best practice" methods. That's because you can do
>the timeconsuming parts of the process with the machine still in
>service.

Not always practical.

If my production server allows interactive login of non-trusted users, 
(shell server for example) I cannot allow these users to have access while 
building of world happens.

I must

1) kill user processes
2) disable remote user login
3) update source
4) build
5) install (install kernel && boot single-user && install world)
6) reboot
7) allow access again

Even on fast CPU and disk this can take hours.

This is a relatively rare (IMHO) circumstance and was included for 
completeness of the thread.

Bottom line is still that kernel and world should be in sync. :)

>         <mike
>--
>Mike Meyer <mwm@mired.org>                      http://www.mired.org/home/mwm/
>Independent WWW/Perforce/FreeBSD/Unix consultant, email for more information.

--c


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message