From owner-freebsd-config  Tue Apr 29 23:38:40 1997
Return-Path: <owner-freebsd-config>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id XAA09550
          for config-outgoing; Tue, 29 Apr 1997 23:38:40 -0700 (PDT)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA09455
          for <config@freebsd.org>; Tue, 29 Apr 1997 23:37:38 -0700 (PDT)
Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id QAA08781; Wed, 30 Apr 1997 16:33:17 +1000
Date: Wed, 30 Apr 1997 16:33:17 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199704300633.QAA08781@godzilla.zeta.org.au>
To: bde@zeta.org.au, msmith@atrad.adelaide.edu.au
Subject: Re: Startup userconfig parsing
Cc: config@freebsd.org
Sender: owner-freebsd-config@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

>> It's squeezed by the 7.5K limit.
>
>Any reason this can't be 8.5K these days?  Who boots from 15spt media 
>anymore?

Yes, only 8K is reserved for the boot blocks, and 15spt media is not
uncommon.

>I think you are misunderstanding what I am suggesting.  The file(s) to
>load can be specified in any fashion; if you want to put the
>instructions as to what to load in a file itself, that's fine.  The

It's overengineerd, not fine.

>> ed(1) certainly won't know about what the commands mean :-).
>
>Huh?  Sorry, I missed that one altogether.

Config files are prepared with a text editor.

Bruce