Is shutil.get_terminal_size useless?
grant.b.edwards at gmail.com
Sun Jan 29 12:27:07 EST 2017
On 2017-01-29, Grant Edwards <grant.b.edwards at gmail.com> wrote:
> On 2017-01-29, Marko Rauhamaa <marko at pacujo.net> wrote:
>> Mount? As a regular user?
> Yes, using a "fuse" use-space filesystem, you can mount things as a
> normal user. There are a couple ISO9660 fuse implemenations. But, you
> can't modify a mounted ISO9660 filesystem. I have read about how to
> use a union mount to simulate a writable ISO9660 filesystem, but
> that's going to require root (I've never tried it).
> 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.
OK, just one more level of pointless digression...
_If_ your ISO image is using syslinux as the bootloader (it probably
isn't, it's almost certainly using isolinux -- usually in hybrid
mode), then the bootloader stuff is actually an image of a bootable
floppy disk. It is sort of "outside" the normal ISO9660 filesystem
with a fixed size in a "well known" location. I'm pretty sure you
could extract that chunk from the ISO using dd, tweak it, and then put
it back into the ISO image without having to mount/extract everything
and then recreate a new ISO9660 image.
But, it's very probably using isolinux, so the bootloader
configuration stuff is actually inside the ISO9660 filesystem tree,
and you'll have to extract the whole tree, modify the files, and
create a new ISO9660 image.
More information about the Python-list