On Fri, 2015-07-24 at 19:26 +0100, OmegaPhil wrote: > > > > On Monday 25 May 2015 04:55 PM, sf...@users.sourceforge.net wrote: > > > Ritesh Raj Sarraf: > > > > Anyways, in the standalone tree, there are a bunch of patches with no > > > > order defined. Is it to assume that they can all be applied randomly ? > > > No. > > > Please refer to README file in aufs4-standalone.git. > > > > > > Yup. That one explain. Sorry. I completely missed that file. > > > > > > I was hoping if we can have a standalone/dkms tree, which could build a > > > > kernel module out, easily loadable in the respective kernel ?? > > > Patching is neccessary (by either manually or GIT), which means you will > > > need another kernel as long as debian kernel is unpatched. > > > > > > > > > > Then it may not fit in the bill of dkms. Let me check with Ben on how he > > supported it for Jessie. > > > Did this go anywhere? I'm on Debain Testing, the recent upgrade to v4 > kernel completely bricked aufs volumes on the 2 machines I use it on > locally because they removed this (and where was the acceptability of > such a removal discussed? Nothing comes up on a search)...
The aufs patches to the kernel are included in Debian packages again as of Linux 4.1 which will go into unstable soon. You will still have to build the module separately. Ben. -- Ben Hutchings Any sufficiently advanced bug is indistinguishable from a feature.
signature.asc
Description: This is a digitally signed message part
------------------------------------------------------------------------------
