From owner-freebsd-current Sun Mar 21 15:36:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles212.castles.com [208.214.165.212]) by hub.freebsd.org (Postfix) with ESMTP id 6B2E214D48 for ; Sun, 21 Mar 1999 15:36:24 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id PAA01548; Sun, 21 Mar 1999 15:29:53 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199903212329.PAA01548@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Bruce Evans Cc: dcs@newsguy.com, mike@smith.net.au, current@FreeBSD.ORG Subject: Re: How to add a new bootdevice to the new boot code ??? In-reply-to: Your message of "Mon, 22 Mar 1999 09:29:48 +1100." <199903212229.JAA27264@godzilla.zeta.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 21 Mar 1999 15:29:52 -0800 From: Mike Smith 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'm happy to entertain any alternate solutions. > I pass "foo" from 1:foo(2s1a)kernel in my version of the old boot blocks. And you determine "foo" how? -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message