Re: Generic boot image support in makefs(8)

[jnemeth%victoria.tc.ca@localhost (John Nemeth)]

On Jun 12, 12:46pm, David Young wrote:
} On Sun, Jan 20, 2008 at 04:01:26PM -0800, John Nemeth wrote:
} > On Jun 12,  9:41am, David Young wrote:
} > } On Sun, Jan 20, 2008 at 11:20:11AM -0800, John Nemeth wrote:
} > } >      BTW, while on this subject, I'm wondering why hp700 can't use the
} > } > makefs -o bootimage=sysid:filename syntax that other systems use?
} > } 
} > } AFAIK, there are not magic numbers defined for hp700.
} > 
} >      "sysid" here isn't to have a magic number, but to tell makefs what
} > type of bootcode it is setting up so that it puts the code in the right
} > place on the CD and does whatever else may be needed to make the disk
} > bootable on that platform.
} 
} Ah.  I see what you mean.  I just brought it up because -o bootimage
} presently uses a particular mechanism that is defined by an ISO9660
} extension which provides for only a few architectures.  There is no

     Ah, okay.  I didn't realise that the -o bootimage referred to a
particular mechanism.  I assume that means that all the systems that
are supported by it conflict in such a way that only a CD can only boot
on one of them?

} reason the mechanism should not be chosen based on the sysid.

     Yeah, no reason why the tool has to have numerous options.  It
would certainly make things simpler for people building CD images if
the tool hid the gory details.

}-- End of excerpt from David Young