jassi brar wrote:
quoted text
> Hi,
> 
>   Lately a question has been bugging me: Why do we keep complicated(specific ioctls to set up and set free) LOOP driver to emulate a data file as block-device, for it to be mounted/formated.
> 
>  Wouldn't it be nice if we didnt have to specify '-o loop' or use losetup -d etc?
> 
>  With inspiration from UMS-Gadget and LOOP driver itself, I implemented a proof of concept: A kernel module which creats a node in /sys/devices/ and un/loads files to be emulated as block devices. The interface doesn't implement any new ioctls or a syscall.
> 
This seems like a really interesting idea, but will it interface with 
crypto applications like LUKS? Crypto seems to be a vital feature for 
anything related to devices and/or filesystems if an approach is going 
to be more than a niche slution.

-- 
Bill Davidsen <davidsen@tmr.com>
   "We have more to fear from the bungling of the incompetent than from
the machinations of the wicked."  - from Slashdot
--
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/