Oleg Goldshmidt wrote:
Shachar Shemesh <[EMAIL PROTECTED]> writes:
Going over the kernel source reveals that the LOOP_SET_STATUS64
does,
I suspect you meant struct loop_info64...
loop_info64 is the structure, LOOP_SET_STATUS64 is the ioctl.
If anyone can shed any light, it would be useful.
If you look at the kernel code in loop.{h,c} and fs/compat_ioctl.c you
will see that there is a compatibility layer between old (loop_info)
and new (loop_info64), and that a part of the difference is the
lo_sizelimit field.
Except that if you look at the losetup source code you will see that it
uses the new API, not the compatibility one.
I don't know but I suspect that this "upgrade" has not yet propagated
into the user level code, at least not everywhere. Try looking into
/usr/include/linux/loop.h on your system. Do you see loop_info64
defined there or lo_sizelimit as a field of loop_info? If you do, it
is very likely conditional on something.
Actually, it is not.
If I am (and it appears that I am) to write my own program, I know how
to do that. I am just a little disappointed that the program I wanted to
do as a shell script I will now have to do as a C compiled program. I
may do it in perl, if I feel up to scaling the ioctl conversions required.
Thanks,
Shachar
Check that preprocessor
condition against your system.
Hope it helps,
=================================================================
To unsubscribe, send mail to [EMAIL PROTECTED] with
the word "unsubscribe" in the message body, e.g., run the command
echo unsubscribe | mail [EMAIL PROTECTED]
