search for: format_ext2

Document what each module does, using *.mli files. Remove the --dtb option, it's obsolete. Rename modules according to their purpose. Rich.

...iance? The simple answer is because we create the appliance image (it's an ext2/3/4 filesystem) using e2fsprogs, and that library wouldn't know how to create anything else since it always assumes it's writing directly to a device. https://github.com/libguestfs/supermin/blob/master/src/format_ext2.mli#L22-L29 HTH, Rich. > I would suggest that choice is related with the performance, so I did > several test runs (./run utils/boot-benchmark/boot-benchmark) > > /appliance/root.raw: > Result: 1342.9ms ±2.9ms > Result: 1370.1ms ±17.3ms > Result: 1365.1ms ±11.0ms > >...

...e the appliance image (it's an > >ext2/3/4 filesystem) using e2fsprogs, and that library wouldn't know > >how to create anything else since it always assumes it's writing > >directly to a device. > > > >https://github.com/libguestfs/supermin/blob/master/src/format_ext2.mli#L22-L29 > > > >HTH, > > Yes, the main point is clear, thanks. > > I asked because we supply the prepared appliance, so would like to use > qcow2. Given that the applaince image is completely controlled, for > supermin and fixed appliance, in both the cases. We co...

...>>>ext2/3/4 filesystem) using e2fsprogs, and that library wouldn't know > >>>how to create anything else since it always assumes it's writing > >>>directly to a device. > >>> > >>>https://github.com/libguestfs/supermin/blob/master/src/format_ext2.mli#L22-L29 > >>> > >>>HTH, > >> > >>Yes, the main point is clear, thanks. > >> > >>I asked because we supply the prepared appliance, so would like to use > >>qcow2. Given that the applaince image is completely controlled, for &gt...

This is an attempt to make supermin check for the existing results of an output when checking whether the appliance must be rebuilt using --if-newer. At the moment it is implemented only for the ext2 output format of the build mode. Changes from v1: - drop empty stub for the prepare mode - add patch to ignore --if-newer on modes different than build - squash patch with stub for the build mode

This is an attempt to make supermin check for the existing results of an output when checking whether the appliance must be rebuilt using --if-newer. At the moment it is implemented only for the build mode, and for its ext2 output format. Pino Toscano (4): build: factor ext2 filenames Tighten Unix_error check for missing outputdir Extend modes with list of outputs build: set