P
Peter0
Guest
Hello alltogether,
I got a script that uses losetup with negative numbers after -o parameter.
The script did a good job under Ubuntu 10.04 system.
After moving to Mint 17, losetup responds like this:
The script calls it the following way:
Apparently, the older system’s losetup accepts negative offsets, while the newer one denies them.
Why?
Is there a way around?
Can I coax a version number out of losetup?
Where is the right place to encourage to getting rid of losetup’s cumbersome constraint?
Thanks for any hints – Peter
If you want to know why and you are able to understand german, take a look at a forum where I explained it. (Sadly I'm hindered to even post anything that might give you any impression of the forum's url.)
In a short: There is a data image file of a CD that contains also music. The image file is only from session 2 of that CD. In order to mount that image file, the script is establishing a loopdevice while giving a negative offset, followed by mounting the loopdevice with a positive offset via mount option "sbsector". The offset depends on the length of audio part on the CD, in other words, it resembles the offset of the second session on the real CD.
Mounting without this double offsetting works with HFS filesystem, but not with ISO-9660 filesystem.
I got a script that uses losetup with negative numbers after -o parameter.
The script did a good job under Ubuntu 10.04 system.
After moving to Mint 17, losetup responds like this:
The script calls it the following way:
Code:
$ sudo losetup -r -o -547622912 -f --show '/media/…/Multimedia_Track.tao'Apparently, the older system’s losetup accepts negative offsets, while the newer one denies them.
Why?
Is there a way around?
Can I coax a version number out of losetup?
Where is the right place to encourage to getting rid of losetup’s cumbersome constraint?
Thanks for any hints – Peter
If you want to know why and you are able to understand german, take a look at a forum where I explained it. (Sadly I'm hindered to even post anything that might give you any impression of the forum's url.)
In a short: There is a data image file of a CD that contains also music. The image file is only from session 2 of that CD. In order to mount that image file, the script is establishing a loopdevice while giving a negative offset, followed by mounting the loopdevice with a positive offset via mount option "sbsector". The offset depends on the length of audio part on the CD, in other words, it resembles the offset of the second session on the real CD.
Mounting without this double offsetting works with HFS filesystem, but not with ISO-9660 filesystem.
