On Mon, Jan 30, 2017 at 4:08 AM, Grant Edwards <grant.b.edwa...@gmail.com> wrote: > As long as you've got the disk space available, the simplest option is > to unpack the .iso into a directory, modify the files, and then use > mkisofs to create the new .iso image. > > I've written scripts like that to build cusotmized bootable ISO images > (usually using systemrescuecd as the starting point). It's not > particulary difficult, but it does burn up a lot of disk space. It's > also rather slow, so when you get into the tweak-build-burn-test cycle > you don't get in a lot of guesses-per-hour.
These days, CD images are a tiny proportion of typical hard disk capacities. Every terabyte of disk can hold over a thousand ISOs, and that's assuming they're using the whole disc (~760MB). Several thousand, if they're only part-full images. But the time factor is considerable. Especially if you then have to boot up a VM or something to test it. ChrisA -- https://mail.python.org/mailman/listinfo/python-list
