Hello Andy, Andy Whitcroft: > The loop.h header has moved private within the drivers/block subsystem. > For now just bodge this by switching to a relative path.
Yes, this is unplesant issue for aufs. But I don't think this approach is good. For instance, - a user wants to rebuild aufs module. - he gets the source files of aufs and the kernel header files. - here "the kernel header files" don't contain drivers/block/loop.h. - finally he cannot rebuild the module. Right? Instead I have released another dirty workaround. See latest aufs3-loopback.patch in aufs3-standalone.git#aufs3.x-rcN branch. J. R. Okajima ------------------------------------------------------------------------------ See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
