Making a bootable ISO using 'mkisofs' under Haiku

1

Hello,

I can create a custom bootable ISO of Haiku (with all my own apps, settings, drivers, etc.) within Haiku, but there are some issues.

First I grab a nightly VMware image, fill it with goodies, then grab the nightly ISO with the same revision, and rip the boot floppy image out of it.

Run this command under Haiku:

mkisofs -R -b haiku-boot-floppy.image -c boot.catalog -o /Haiku-Custom.iso /boot

(took me a while to figure the above out, and note, adding the Joilet flag will result in an ISO that doesn’t boot)…

Testing the ISO in Qemu, it loads, fine, boots fine, applications load fine, etc.

The only thing, all the applications don’t have their icons. Didn’t copy the attributes over?

So, does anyone know how I can fix this, what’s happening, if this is a bug in mkisofs?

thx!

2

Ah, I think I see what’s happening. Things are being renamed (how to prevent this?):

Using X_VND000.SVN;1 for /boot/home/config/settings/beos_mime/application/x-vnd.be.url.svn+ssh (x-vnd.be.url.svn)
Using X_VND000.HTT;1 for /boot/home/config/settings/beos_mime/application/x-vnd.be.url.https (x-vnd.be.url.http)
Using X_VND000.PRI;1 for /boot/home/config/settings/beos_mime/application/x-vnd.be.printer-spool (x-vnd.be.printer)
Using X_VND000.BE_;1 for /boot/home/config/settings/beos_mime/application/x-vnd.be-work (x-vnd.be-volume)
Using X_VND001.BE_;1 for /boot/home/config/settings/beos_mime/application/x-vnd.be-volume (x-vnd.be-tskb)
Using X_VND002.BE_;1 for /boot/home/config/settings/beos_mime/application/x-vnd.be-tskb (x-vnd.be-trak)
Using X_VND003.BE_;1 for /boot/home/config/settings/beos_mime/application/x-vnd.be-trak (x-vnd.be-symlink)
Using X_VND004.BE_;1 for /boot/home/config/settings/beos_mime/application/x-vnd.be-symlink (x-vnd.be-scrn)
Using X_VND005.BE_;1 for /boot/home/config/settings/beos_mime/application/x-vnd.be-scrn (x-vnd.be-root)
Using X_VND006.BE_;1 for /boot/home/config/settings/beos_mime/application/x-vnd.be-root (x-vnd.be-querytemplate)
Using X_VND007.BE_;1 for /boot/home/config/settings/beos_mime/application/x-vnd.be-querytemplate (x-vnd.be-query)
Using X_VND008.BE_;1 for /boot/home/config/settings/beos_mime/application/x-vnd.be-query (x-vnd.be-psrv)
Using X_VND009.BE_;1 for /boot/home/config/settings/beos_mime/application/x-vnd.be-psrv (x-vnd.be-prnt)
Using X_VND00A.BE_;1 for /boot/home/config/settings/beos_mime/application/x-vnd.be-prnt (x-vnd.be-pref)
Using X_VND00B.BE_;1 for /boot/home/config/settings/beos_mime/application/x-vnd.be-pref (x-vnd.be-post)
Using X_VND00C.BE_;1 for /boot/home/config/settings/beos_mime/application/x-vnd.be-post (x-vnd.be-pepl)
Using X_VND00D.BE_;1 for /boot/home/config/settings/beos_mime/application/x-vnd.be-pepl (x-vnd.be-mail)
Using X_VND00E.BE_;1 for /boot/home/config/settings/beos_mime/application/x-vnd.be-mail (x-vnd.be-kmap)
Using X_VND00F.BE_;1 for /boot/home/config/settings/beos_mime/application/x-vnd.be-kmap (x-vnd.be-input_server)
Using X_VND00G.BE_;1 for /boot/home/config/settings/beos_mime/application/x-vnd.be-input_server (x-vnd.be-elfexecutable)

*Update:

Added the flag -max-iso9660-filenames, which got rid of those errors above, but didn’t prevent the problem. Most icons for applications/folders are missing, just have the standard binary icon for apps, and the grey icon for directories (although some have the correct ones).

3

[quote=kvdman]
*Update:

Added the flag -max-iso9660-filenames, which got rid of those errors above, but didn’t prevent the problem. Most icons for applications/folders are missing, just have the standard binary icon for apps, and the grey icon for directories (although some have the correct ones).[/quote]

I think that is a sign that attr was not used.

4

This may give you some information:

5

yep, I posted that, think I have it figured out now.