Re: Tools mkhybrid(8) for mac68k/macppc ISO9660/HFS install ISO images

Izumi Tsutsui <[email protected]>
Newsgroups gmane.os.netbsd.devel.toolchain
Message-ID <[email protected]>
I wrote:
> > > [rationale]
> > >
> > > I believe it's a better strategy to "drop pkgsrc mkisofs(8) and
> > >  use a (dumb and old but) own build tool," even if it isn't perfect.
> > 
> > I would definitely agree. It would ensure all NetBSD mac ISO images
> > were buildable, not just the ones where releng or similar has jumped
> > through specific hoops.
> 
> Thank you for your comment. I'll commit changes this weekend.

Committed:
 https://mail-index.netbsd.org/source-changes/2024/05/31/msg151577.html
 https://mail-index.netbsd.org/source-changes/2024/05/thread3.html#151603 

If there are any problems, please file a PR.


I wrote in the first post:
 https://mail-index.netbsd.org/tech-toolchain/2024/05/25/msg004355.html
>> # Future works
>> 
>> - Currently a special "mapppc_installboot" tool is necessary to
>>   make macppc install CD ISO bootable, in the "old CD method"
>>   described in src/distrib/cdrom directory.
>> 
>>   This old macppc_installboot tool (written by me) should be merged
>>   into MI src/usr.sbin/installboot to build a macppc installcd iso
>>   on "build.sh iso-image" target and to abandon the old method.
>> 
>>   However, it also requires more work and cleanups around Apple
>>   partition map stuff in src/usr.sbin/installboot/arch/macppc.c.

For interim macppc installcd builds, I'll also add
src/tools/macppc_installboot before reorganizing complicated
Apple partition map stuff in src/usr.sbin/installboot/arch/macppc.c.

I've also managed to create a bootable macppc disk using
Apple partition map on my OpenFirmware 2.x Apus2000/200:
 https://gist.github.com/tsutsui/f1f81e194eb2ff1eda6fda4b1bb84d25
so I think we can switch macppc port using Apple partition map
(without BSD disklabel) by default as mac68k, but this is another
macppc specific topic.

---
Izumi Tsutsui
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.