Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 22 Jul 1997 00:08:53 +0930 (CST)
From:      Michael Smith <msmith@atrad.adelaide.edu.au>
To:        jkh@time.cdrom.com (Jordan K. Hubbard)
Cc:        bde@FreeBSD.ORG, current@FreeBSD.ORG
Subject:   Re: /boot.foo madness
Message-ID:  <199707211438.AAA23834@genesis.atrad.adelaide.edu.au>
In-Reply-To: <27686.869491170@time.cdrom.com> from "Jordan K. Hubbard" at "Jul 21, 97 06:19:30 am"

next in thread | previous in thread | raw e-mail | index | archive | help
Jordan K. Hubbard stands accused of saying:
> 
> One way would be to install these files along with the boot blocks if
> they don't already exist in the targetdir, the "pros" of that approach
> being that you could update your boot blocks and prototype boot
> configuration files in one place, plus it'd wind up in the bindist(s)
> by default.  The #1 con of this idea is that it's truly gross to
> contemplate install rules writing into /, plus you'd have a staleness
> problem as things changed.  Updating /etc is enough of an established
> no-no, now we're talking about installing things straight into the
> root dir?  Surely the beginning of the end, that would be.

The files should be installed into /usr/mdec along with the
prototypical bootblocks, and written to the 'a' partition of the disk
being labelled by 'disklabel -B' and anything that purports to be
compatible with it, if they are not already there.  Possibly an
override option should be supplied which will force the files to be
overwritten when labelling

> Another way would be to artificially create these files in the bin
> dist(s) through the efforts of one of the release building rules in

Yecch.

> that would involve copying another bindist over the old, and that's
> why the 3rd and perhaps least offensive alternative is to put this
> into the "post-install fixup" procedure in sysinstall which puts the
> last few finishing and somewhat kludgy touches on an extracted bin
> dist.  This could then intelligently add the files if they did not
> already exist.

That makes the files second-class citizens.  If they're really meant
to go along with the bootblocks, then they should be managed by the
same tools.

> 					Jordan

-- 
]] Mike Smith, Software Engineer        msmith@gsoft.com.au             [[
]] Genesis Software                     genesis@gsoft.com.au            [[
]] High-speed data acquisition and      (GSM mobile)     0411-222-496   [[
]] realtime instrument control.         (ph)          +61-8-8267-3493   [[
]] Unix hardware collector.             "Where are your PEZ?" The Tick  [[



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199707211438.AAA23834>