On Wed, 19 Apr 2000, Pavel Machek wrote:
> Yes. I have an userland filesystem, mounted on /overlay. Fs on
> /overlay has all files / filesystem has, plus many more. For example,
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
What for? Why do you want to do it for every bloody file?
> each file.gz has cooresponding file.gz#ugz, which contains its
> uncompressed version. Each file.tar has file file.tar#utar, which
> contains whole tree of that archive.
_Ouch_. OK, first of all you don't want that sort of crap on
creation/removal/etc. of the objects, right? Now, what does your userland
fs do? Details, please.
> I could do chroot /overlay at the bootup, but that would be *very*
> slow (every fs request going through userland... Oh horror). So I
> created that patch...
> Is there better solution?
I hope so. Because it surely sounds like an utterly messy kludge.
Just a question: what happens if you do
chdir("file.tar#untar");
chdir("..");
- where do you end up?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sun Apr 23 2000 - 21:00:15 EST