On Mon, Oct 05, 2020 at 10:58:02PM +, Alexander Prada wrote:
> Here is the updated libguestfs-test-tool output after the command below:
>
> echo /usr/lib/x86_64-linux-gnu/libtsk.so.19 >
> /usr/lib/x86_64-linux-gnu/guestfs
> /supermin.d/zz-libtsk
...
> supermin: if-newer: output does not
On Mon, Sep 07, 2020 at 10:41:20AM +0100, Richard W.M. Jones wrote:
For BitLocker disks cryptsetup does not (yet? ever?) support reading
UUIDs and this function will fail. This does not matter here so just
ignore the error.
Note there is no error message, cryptsetup simply returns with a bad
On Thu, Sep 17, 2020 at 01:39:56PM +0100, Richard W.M. Jones wrote:
As discussed in the emails today, this is the third version addressing
most points from the v1/v2 review.
You will need to pair this with the changes in libguestfs-common from
this series:
On Tue, Oct 06, 2020 at 03:25:20PM +0200, Martin Kletzander wrote:
> On Mon, Sep 07, 2020 at 10:41:20AM +0100, Richard W.M. Jones wrote:
> >For BitLocker disks cryptsetup does not (yet? ever?) support reading
> >UUIDs and this function will fail. This does not matter here so just
> >ignore the
On Tue, Oct 06, 2020 at 03:29:33PM +0200, Martin Kletzander wrote:
> On Thu, Sep 17, 2020 at 01:39:56PM +0100, Richard W.M. Jones wrote:
> >As discussed in the emails today, this is the third version addressing
> >most points from the v1/v2 review.
> >
> >You will need to pair this with the
On Tue, Oct 06, 2020 at 01:01:49PM -0500, Eric Blake wrote:
> On 10/6/20 11:54 AM, Richard W.M. Jones wrote:
> > If the server fails, nbdinfo can write partial output before the error
> > message (albeit on different channels). Here is an example:
> >
> > $ nbdkit eval open='echo EIO fail >&2;
If the server fails, nbdinfo can write partial output before the error
message (albeit on different channels). Here is an example:
$ nbdkit eval open='echo EIO fail >&2; exit 1' --run 'nbdinfo --json "$uri"'
{
"protocol": "newstyle-fixed",
"TLS": false,
nbdkit: eval[1]: error:
On 10/6/20 11:54 AM, Richard W.M. Jones wrote:
> If the server fails, nbdinfo can write partial output before the error
> message (albeit on different channels). Here is an example:
>
> $ nbdkit eval open='echo EIO fail >&2; exit 1' --run 'nbdinfo --json "$uri"'
> {
> "protocol":
