Re: installing the same file twice using bsd.*.mk
"Michael L. Hitch" <[email protected]>
| Newsgroups | gmane.os.netbsd.devel.general |
|---|---|
| Message-ID | <Pine.ULT.4.05.10204141456140.19862-100000@lightning.msu.montana.edu> |
On Sun, 14 Apr 2002, Klaus Heinz wrote: > [ Klaus Heinz asks about how to install $DESTDIR/boot.amiga with the mechanisms > bsd.*.mk provides ] > > Luke Mewburn wrote: > > > Todd Vierling wrote: > > | Most platforms do this copy as part of "installboot", by passing *two* > > | arguments to installboot (first stage short bootblock and second stage > > | boot > > | program file), not during rolling up of the base sets. (Part of the > > | reason > > | for this is so that doing a build with DESTDIR=/ won't hose bootability if > > | there's bootblock problems unless "installboot" is explicitly run.) As far as I could tell, none of the installboot processes I looked at did this (alpha, pmax, vax). > > I'm curious to as why the base set on the amiga provides /boot; > > I don't think any other port does that. "Whatever" :-) > > Ah, this is a question I did not think about. As far as I know Michael Hitch > has worked at the new boot blocks for NetBSD/Amiga and has probably added > it to the set list for base.tgz. The vax and pmax ports did this, so that's the approach I took. The alpha and pmax sysinst programs do the copy as part of the bootblock install process [so the pmax has /boot.pmax in the base.tgz set as well as copying it when updating bootblocks]. The amiga install/upgrade process could to this easily, I think. > Where else should the second stage bootloader come from if not provided by > the base set or installed by installboot, as Todd proposed? See above. -- Michael L. Hitch [email protected] Computer Consultant Information Technology Center Montana State University Bozeman, MT USA