creating a readable iso? #228
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Hi,
I saw in a Tupfile.lua:
'mkisofs -U -J -pad -b cdboot.bin -no-emul-boot -c boot.catalog'
.. ' -hide-joliet boot.catalog -hide-joliet cdboot.bin'
.. ' -hide-joliet kernel.mnt -graft-points'
.. ' -A "KolibriOS AutoBuilder" -p "CleverMouse"'
.. ' -publisher "KolibriOS Team" -V "' .. volume_id .. '" -sysid "KOLIBRI"'
.. ' -iso-level 3 -o %o ' .. iso_files_list .. ' 2>&1',
so tried to do similar to create an iso mounted by vmware, for example:
mkisofs -U -J -pad -graft-points -A "KolibriOS AutoBuilder" -p "CleverMouse" -publisher "KolibriOS Team" -V "01" -sysid "KOLIBRI" -iso-level 3 -o myfiles.iso afilename
nothing i've tried worked, in Kolibri it lists no files, or sometimes eolite would crash/close as soon as CD clicked.
maybe you could document the procedure.
Sorry if I get your issue wrong but for which mkisofs option you need documentation?
i just want the ISO to work, in this case mounted by vmware. do you spot anything wrong in my mkisofs example?
I'm not sure you are using the -graft-points option correctly.
fantastic! removing -graft-points fixed the problem! so ya maybe just add that to a doc, like the mkisofs parms reqd etc.
you can close if you like.
thanks a bunch!
/data/Tupfile.lua has the mkisofs command that builds valid nightbuild iso images. What do you expect to be added and to what doc?
it's up to you, if you don't want that's fine, but as you saw i used that Tupfile.lua myself and didn't get it right, never used mkisofs in my life. actually tried ultraiso, imgburn etc first, all failed. Where to put it is entirely up to you, if at all. i even asked chatgpt who also didnt get it right ha