>> >> Is this a known issue and is there a solution or workaround by any >> >> chance? >> > >> >until unionfs supports mmap, it will be a problem. There's no good >> >workaround, beyond modifying the applications to know to prune the path. >> >> On the contrary. There are a LOT of workarounds, ranging from "multimount >> networks and pivot_root whoppings" down to a simple "modify the >> kernel source" to strip the unwanted parts. > >what the heck is the first thing? the 2nd thing is what I mentioned >(pruning).
Right. The first thing is, if expanded, a serious pivoting I could not understand as long as I had it in the inbox. It was a privately sent one, so there is no record in the archives. I think it was like this solution http://www.fsl.cs.sunysb.edu/pipermail/unionfs/2005-October/001305.html the unexplainable part being the pivot_root /ram/union /ram/union Jan Engelhardt -- | Alphagate Systems, http://alphagate.hopto.org/ | jengelh's site, http://jengelh.hopto.org/ _______________________________________________ unionfs mailing list [email protected] http://www.fsl.cs.sunysb.edu/mailman/listinfo/unionfs
