Chris Angelico <ros...@gmail.com> writes: > On Wed, May 28, 2014 at 3:21 PM, Kushal Kumaran > <kushal.kumaran+deb...@gmail.com> wrote: >> Chris Angelico <ros...@gmail.com> writes: >> >>> On Wed, May 28, 2014 at 5:47 AM, Joe Pfeiffer <pfeif...@cs.nmsu.edu> wrote: >>>> Well, I don't want to keep two separate files (that's what I'm trying to >>>> get away from). It seems like the overlay filesystem would be a bit >>>> cleaner if it can work, but symbolic links elsewhere would be my second >>>> choice. >>>> >>> >>> As a variant of Kushal's suggestion of two symlinks to the same file, >>> you could have the real file in one place (preferably where it's >>> written to) and a symlink to it from the other place. >>> >> >> If I understand the situation correctly, only one of the locations will >> be accessible at any time. When the user logs in, the original files >> will be hidden under the files provided by the encrypted filesystem. >> So, both files are actually ~/.bogofilter (say), just at different >> times. So you cannot have a symlink from one location to the other. > > Ah! Gotcha. Then, yes; symlinks from both to the same destination. Not > sure what a suitable destination is, though. > > ChrisA
For the moment, I have /home/acct/file, /home.unenc/acct/file, and /home.enc/acct/file. The real file is in /home.unenc/acct/file, and there are symbolic links to it from both home/acct/file and /home.enc/acct/file. When I'm not logged in, the daemon sees /home/acct/file (and hence really sees /home.unenc/acct/file); when I log in, /home.enc/acct is unencrypted and laid on top of /home/acct, so the daemon still sees /home.unenc/acct/file. Inelegant (so I'd really like to find a way for a union or overlay filesystem to do it!) but it seems to work... -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1bfvju8234....@snowball.wb.pfeifferfamily.net