From owner-freebsd-current  Wed Aug  6 16:10:53 1997
Return-Path: <owner-freebsd-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id QAA26559
          for current-outgoing; Wed, 6 Aug 1997 16:10:53 -0700 (PDT)
Received: from broon.off.connect.com.au (broon.off.connect.com.au [203.63.69.1])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA26554
          for <current@freebsd.org>; Wed, 6 Aug 1997 16:10:45 -0700 (PDT)
Received: from connect.com.au (ggm@localhost) by broon.off.connect.com.au with ESMTP id JAA27993
  (8.8.5/IDA-1.6); Thu, 7 Aug 1997 09:09:19 +1000 (EST)
To: Tom Bartol <bartol@salk.edu>, current@freebsd.org
Subject: Re: modifying boot mgrs FROM FREEBSD 
In-reply-to: Your message of "Wed, 06 Aug 1997 16:06:09 MST."
             <Pine.BSF.3.95.970806153805.1888E-100000@pauling.salk.edu> 
Date: Thu, 07 Aug 1997 09:09:18 +1000
Message-ID: <27991.870908958@connect.com.au>
From: George Michaelson <ggm@connect.com.au>
Sender: owner-freebsd-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


[edited down the headers]
  
  Would it be too weird to do the following quick and dirty thing completely
  without the need for any documentation on which boot manager you're using:

I also had this idea. I suspect that for the critical purpose: writing back
that the current opsys is to be rebooted to irrespective of what tunings
the manager has, this would do.

But there are lots of reasons why its a bad move. its another critical path
to go wrong if you change the boot manager in unexpected ways. If the damn
thing is installed and hosted from inside FreeBSD, then changes are likely
to be made in ways which are self-consistent.

I think Jordans comments stand: don't hold your breath.

-George