Bug#1010098: xorriso: please allow -cut-out directly from block devices

2022-06-02 Thread Thomas Schmitt
Hi, Ivan Shmakov wrote: > An alternative would be to check if it’s possible to seek to > specified positions rather than to the end of file This should work now, by an attempt of lseek(wanted_size, SEEK_SET) if lseek(0, SEEK_END) yields failure or 0 size. (libisoburn commit 0c0d542, libisofs

Bug#1010098: xorriso: please allow -cut-out directly from block devices

2022-05-26 Thread Thomas Schmitt
Hi, Ivan Shmakov wrote: > An alternative would be to check if it’s possible to seek to > specified positions rather than to the end of file; e. g.: I see at least the problem that the end position of -cut_out (byte_offset + byte_count + 1) is allowed to be unrealisticly high in order to simply

Bug#1010098: xorriso: please allow -cut-out directly from block devices

2022-05-25 Thread Ivan Shmakov
> On 2022-04-26, Thomas Schmitt wrote: > TS == Thomas Schmitt wrote: TS> So if we exclude S_IFSOCK, S_IFLNK, S_IFDIR, S_IFIFO there TS> remain only S_IFREG, S_IFBLK, S_IFCHR with the latter on Linux TS> behaving like S_IFREG with 0 bytes of content. (As said on TS> FreeBSD it could

Bug#1010098: xorriso: please allow -cut-out directly from block devices

2022-04-26 Thread Thomas Schmitt
Hi, i decided to regard a device with 0 lseekable size as not suitable for -cut_out. The test for suitable type rejects S_ISDIR, S_ISLNK, S_ISFIFO, and S_ISSOCK. So if an operating system offers non-POSIX types, it will be possible to test whether they are elsewise suitable. Please give the code

Bug#1010098: xorriso: please allow -cut-out directly from block devices

2022-04-25 Thread Thomas Schmitt
Hi, the plan to allow nearly all file types with -cut_out is dwindeling: - lseek(SEEK_END) on S_IFCHR /dev/zero returns 0, not -1. - open() on S_IFIFO blocks (and i don't want to know what it will do in libisofs). IIRC a successful open() has side effects on the fifo. - S_IFSOCK fails

Bug#1010098: xorriso: please allow -cut-out directly from block devices

2022-04-25 Thread Thomas Schmitt
Hi, i wrote: > > The newest easily compilable and then usable version would be > > http://www.gnu.org/software/xorriso/xorriso-1.5.5.tar.gz Ivan Shmakov wrote: > Not under http://ftp.gnu.org/gnu/xorriso/ , though? 1.5.5 is a development snapshot with potentially later changing new

Bug#1010098: xorriso: please allow -cut-out directly from block devices

2022-04-24 Thread Ivan Shmakov
> On 2022-04-24, Thomas Schmitt wrote: > Ivan Shmakov wrote: >> I’m filing this bug against versions from oldstable and stable, >> for that’s so far the only Debian packages’ versions I’ve tested >> for this issue. > As it is about an upstream wish: > The newest easily compilable

Bug#1010098: xorriso: please allow -cut-out directly from block devices

2022-04-24 Thread Thomas Schmitt
Hi, Ivan Shmakov wrote: > I’m filing this bug against versions from oldstable and > stable, for that’s so far the only Debian packages’ versions > I’ve tested for this issue. As it is about an upstream wish: The newest easily compilable and then usable version would be

Bug#1010098: xorriso: please allow -cut-out directly from block devices

2022-04-24 Thread Ivan Shmakov
Package: xorriso Version: 1.5.0-1 Severity: wishlist Control: found -1 1.5.2-1 [Please do not Cc: me, for I’m “on the list,” so to say, and I try to reserve my inbox for private communication only. I’d have set up Mail-Followup-To:, but there doesn’t seem to be a