RE: Updating world with least downtime

2002-09-04 Thread Sameer R. Manek

I recently rebuilt the world on my pII 400 system, and here is how long it
took me.

/usr/bin/time make installworld
   266.34 real74.23 user43.33 sys
/usr/bin/time make installkernel
   26.11 real 6.89 user 2.38 sys

So it took about 4.8 minutes to install the files, given average consumer
grade disks. Compiling is more cpu dependant, but the install portion is
more a function of disk-io.

Mergemaster is obviously dependent on how quickly it takes the operator to
run that command. But if you budget 10 - 15 minutes, it should be good
enough.

Sameer

 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED]]On Behalf Of Kevin Oberman
 Sent: Friday, August 30, 2002 2:11 PM
 To: Jack L. Stone
 Cc: Brooks Davis; David W. Chapman Jr.; [EMAIL PROTECTED]
 Subject: Re: Updating world with least downtime



 For a modern system and a reasonable disk, this is trivial. I have a
 system which MUST not be down for over 15 minutes and I can do it
 quite easily unless I really fumble something in mergemaster. I do
 always merge a few files later and tend to install most changes very
 quickly, having ode the same upgrade on a non-critical system just
 before I do the critical one so I know what to expect.

 The actual installworld time on my 1GHZ system is about 5 minutes
 (5:34 last time).

 R. Kevin Oberman, Network Engineer
 Energy Sciences Network (ESnet)
 Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab)
 E-mail: [EMAIL PROTECTED]Phone: +1 510 486-8634



To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-stable in the body of the message



Re: Updating world with least downtime

2002-09-01 Thread Kevin Oberman

 Date: Fri, 30 Aug 2002 17:20:24 -0700
 From: David Schultz [EMAIL PROTECTED]
 
 Thus spake Kevin Oberman [EMAIL PROTECTED]:
  For a modern system and a reasonable disk, this is trivial. I have a
  system which MUST not be down for over 15 minutes and I can do it
  quite easily unless I really fumble something in mergemaster. I do
  always merge a few files later and tend to install most changes very
  quickly, having ode the same upgrade on a non-critical system just
  before I do the critical one so I know what to expect.
  
  The actual installworld time on my 1GHZ system is about 5 minutes
  (5:34 last time).
 
 Nice record.  There ought to be a better solution than ``run
 mergemaster really fast and hope nothing goes wrong,'' though.
 For example, you could use mergemaster with -D on a copy of /etc
 and commit the copy in single user mode.

No. I run mergemaster on another system to confirm what needs to be
merged before reboot or can be installed with no complications. Then
plan what I will have to do with any files that require merging. This
is far different from just rushing through things and risking s
disaster. It is, as the subject of the thread states, Updating world
with least downtime.

I like the idea of an early-run using -D, though. I might do that
next time I update a system. Should be even faster than what I do and
less prone to error. Thanks for the suggestion.

R. Kevin Oberman, Network Engineer
Energy Sciences Network (ESnet)
Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab)
E-mail: [EMAIL PROTECTED]  Phone: +1 510 486-8634


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-stable in the body of the message



Re: Updating world with least downtime

2002-08-30 Thread David Schultz

Thus spake Kevin Oberman [EMAIL PROTECTED]:
 For a modern system and a reasonable disk, this is trivial. I have a
 system which MUST not be down for over 15 minutes and I can do it
 quite easily unless I really fumble something in mergemaster. I do
 always merge a few files later and tend to install most changes very
 quickly, having ode the same upgrade on a non-critical system just
 before I do the critical one so I know what to expect.
 
 The actual installworld time on my 1GHZ system is about 5 minutes
 (5:34 last time).

Nice record.  There ought to be a better solution than ``run
mergemaster really fast and hope nothing goes wrong,'' though.
For example, you could use mergemaster with -D on a copy of /etc
and commit the copy in single user mode.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-stable in the body of the message