![]() The "-R" makes sure the final ISO file is fully compliant.Īnyways, thanks everyone for your thoughts. The "-o /tmp/new.iso" is the file it will generate, and the last thing "/tmp/iso" specifies the files to put inside it. The "-c isolinux/boot.cat" is a packaging flag. The "-no-emul-boot", "-boot-load-size 4", and "-boot-info-table" all are extra settings for making the disk bootable. The "-b" flag makes the disk bootable, using "isolinux/isolinux.bin" as the boot file. Mkisofs -R -b isolinux/isolinux.bin -c isolinux/boot.cat -no-emul-boot -boot-load-size 4 -boot-info-table -o /tmp/new.iso /tmp/iso ![]() Now take those files and make them into a new ISO (from earlier mentioned link): This method is useful for future planning, although ISO files would still have their uses.Ģ) If I absolutely positively have to modify an ISO, the way to do it is, in general, as follows: ![]() I suppose the payoff is better, thus it's use.Īnyway, it seems that there are two ways for me to go about it:ġ) Don't copy the disk or drive as an ISO originally, instead I could use something like an IMG file. I was not looking for a how, more a fundamental "why I think that is pretty good reasoning, although in the case of modifying an ISO *file* on the drive it makes it difficult and time consuming. So in the case of me having an ISO file on my drive, I would have to mount>copy>edit>mkisofs to do even the smallest bit of Thanks for your response, but I had actually read that very post already, along with about twenty others just like it. It seems that the ISO 9660 format just does not allow for the possibility of read-write. Thank you all for your replies, I think I may understand better. I mean, maybe that's not the norm, or maybe I made an ISO when I should have made an IMG? Am I missing something?Ĭan somebody tell me, from a technical point of view, if I can or why I can't mount an ISO as read-write? However, may I posit that it is *not* a good solution in all cases? E.g., I have a 6GB ISO on the drive, mount it (that makes 12GB), modify, make new ISO (thats 18GB). This is what I eventually did, so you don't need to suggest it. I read around online, found a lot of posts with this same topic, and all of them had a "solution" of copying the ISO content to the hard drive, modifying it, and making a new ISO. Except when I go to modify files, it says it is a read-only file system.ġ) Is it possible to mount an ISO to be read-write?Ģ) If it is not possible, isn't that poor user interface? Shouldn't it tell you something like "You can't do that" instead of running like normal?ģ) Also, if it's not possible, is there any other solution than "mount, copy, modify, mkisofs"? It silently mounts it, so I assume everything is good. Sudo mount -o rw,loop disk.iso /media/disk When I mount it with command line, even specifying read-write and using sudo, like so: When I mount it using GUI commands ("Open with 'Archive Manager'" and "Open with 'Archive Mounter'") it is read-only. I have an ISO and I need to change a small file inside it. This is a more technical question, a fundamental if you will:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |