From owner-freebsd-current  Thu Jan  4 07:44:52 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id HAA11648
          for current-outgoing; Thu, 4 Jan 1996 07:44:52 -0800 (PST)
Received: from jhome.DIALix.COM (root@jhome.DIALix.COM [192.203.228.69])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id HAA11634
          for <current@freebsd.org>; Thu, 4 Jan 1996 07:44:44 -0800 (PST)
Received: (from peter@localhost) by jhome.DIALix.COM (8.7.3/8.7.3) id XAA02956; Thu, 4 Jan 1996 23:42:44 +0800 (WST)
Date: Thu, 4 Jan 1996 23:42:43 +0800 (WST)
From: Peter Wemm <peter@jhome.DIALix.COM>
To: Mark Murray <mark@grondar.za>
cc: current@freebsd.org
Subject: Re: Odd question.. ;-) 
In-Reply-To: <199601041530.RAA02803@grumble.grondar.za>
Message-ID: <Pine.BSF.3.91.960104233435.476B-100000@jhome.DIALix.COM>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-current@freebsd.org
Precedence: bulk

On Thu, 4 Jan 1996, Mark Murray wrote:
> Peter Wemm wrote:
> > How do I update the boot code to -current? :-)
[..]
> 
> I do it by
> disklabel -B -b boot1 -s boot2 sd0
> in the /usr/mdec directory.

OK.. that seems to be the general opinion...  I wonder what went wrong 
last time? :-(  (the docs say that bootsd and sdboot (which are symlinked 
to boot1/2) will be used by default, so all the suggestions have been 
along the same lines).  I vaguely recall "kernel out of reach of bios", 
evne though it had booted from it moments ago.  When I re-ran the install 
program, it read the disk label and/or the fdisk info (I dont remember) 
as "empty".  I vaguely recall the "fixit" option located the missing info..

(..he says, as he cracks open a new dat tape to dump everything in case.. :-)

> I have not newfs'ed my disk sice 2.0-R, so I suspect you may have to
> replace the sd0 with sd0s1 or whatever your  boot partition is.

Umm.. you probably should if it's convenient.. (ha! :-)  You may not be 
getting the benefit from clustering.. Do a "tunefs -p /dev/rsd..." and 
see what the "-a" setting is.

Also, do a "dumpfs /dev/rsd..." and see that it says "no rotational 
position table".. As I understand it, that table causes the blocks to be 
interleaved, defeating any clustering due to "-a".

-Peter


> M
> --
> Mark Murray
> 46 Harvey Rd, Claremont, Cape Town 7700, South Africa
> +27 21 61-3768 GMT+0200
> Finger mark@grondar.za for PGP key
>