Am 03.10.2013 16:23, schrieb sf...@users.sourceforge.net:
> Florian Klink:
>> I wanted to say that it's a little bit strange that aufs needs to load
>> loop module as soon as it mounts anything (even not loop).
>
> I understand.
>
>
>> bool check_if_loopback_overlap(){
>> if(!kernel_has_loop_already_loaded_or_compiled_in()) {
>> //kernel doesn't know anything about loop, so branch
>> //can't be a loopback one
>> return false
>> }
>> //kernel currently has support for loop
>> else {
>> symbol_request();...
>> return really_check_overlap_now();
>> }
>> }
>
> Hmm... You are convincing me...
> How about this patch?
>
Nice :-)
With missing loop module file, now I'm still able to union mount my two
"regular" file systems, thanks a lot!
Florian
------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60134791&iu=/4140/ostg.clktrk
