Karel Zak: > It seems that the kernel part (LOOP_SET_CAPACITY) is not restricted > and it supports resizing in both directions (increase/decrease). > Right? Right. The size check is done in userspace, grow only. > Do we really need to hardcode this functionality to losetup(8)? Maybe > users want to use a different way how to resize the file. For example > the latest coreutils contains a nice user-friendly "truncate" utility > that provides all necessary functionality. > > From my point of view everything what we need in losetup(8) is to > call LOOP_SET_CAPACITY ioctl. So you prefer A, do you? A. $ truncate backend_file $ losetup follow_the_size loopdev B. $ losetup --grow size loopdev backend I prefer B. I thought you prefer B too by your mail in last November. There is one more option which is totally a new utility named logrow (the TestApp). Anyway the choice is yours. And I've pulled the latest coreutils. Reading truncate utility, I found it doesn't allocate disk blocks, just calling ftruncate(). That is a major difference. J. R. Okajima -- To unsubscribe from this list: send the line "unsubscribe util-linux-ng" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
