From owner-freebsd-current  Sun Mar 21 14:30:18 1999
Delivered-To: freebsd-current@freebsd.org
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9])
	by hub.freebsd.org (Postfix) with ESMTP id 633BB15058
	for <current@FreeBSD.ORG>; Sun, 21 Mar 1999 14:30:14 -0800 (PST)
	(envelope-from bde@godzilla.zeta.org.au)
Received: (from bde@localhost)
	by godzilla.zeta.org.au (8.8.7/8.8.7) id JAA27264;
	Mon, 22 Mar 1999 09:29:48 +1100
Date: Mon, 22 Mar 1999 09:29:48 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199903212229.JAA27264@godzilla.zeta.org.au>
To: dcs@newsguy.com, mike@smith.net.au
Subject: Re: How to add a new bootdevice to the new boot code ???
Cc: current@FreeBSD.ORG
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

>Correct.  I was looking for a field in the disklabel that I could spam 
>with a suitable number based on the time from the RTC, and I'd then 

There isn't one.  Especially when there is no disklabel or a read-only
disklabel.

>> Again, same objections... :-)
>
>Same solutions.  Plus we'd be likely to place some metadata somewhere 
>on a FAT filesystem, so it'd be trivial to put such a field there.

Similar objections.  Disks should be write protected to inhibit spam :-).

I pass "foo" from 1:foo(2s1a)kernel in my version of the old boot blocks.

Bruce


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