Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!elroy.jpl.nasa.gov!usc!wuarchive!zaphod.mps.ohio-state.edu!mips!pacbell.com!att!ucbvax!unisoft!greywolf From: greywolf@unisoft.UUCP (The Grey Wolf) Newsgroups: comp.unix.questions Subject: Re: hiding files under a mount point. Message-ID: <3479@unisoft.UUCP> Date: 11 Apr 91 01:54:01 GMT References: <1991Mar18.045734.5114@brolga.cc.uq.oz.au> <1991Apr3.140229.3474@athena.mit.edu> Reply-To: greywolf@unisoft.UUCP (The Grey Wolf) Organization: Foo Bar and Grill Lines: 24 /* <1991Apr3.140229.3474@athena.mit.edu> by jik@athena.mit.edu (Jonathan I. Kamens) * In article , mitch@hq.af.mil (Mitch Wright) writes: * |> Just write your own library routines that quickly unmount the fs, open the * |> file, and then remount. * * This will only work if no process has any files open on the filesystem * you're trying to unmount. In the case of a filesystem like /usr, it is very * unlikely that no one will have any open files on it when you go to unmount it. Not to mention that if you manage to nfs-mount the parent fs of the fs in question, you can get to the file anyway (though permissions can take care of that if you use the extreme fascistic permission scheme for your precious files...). It's kind of like sweeping things under the rug on the main system and then using some other system to turn 2-dimensional and make your way under the rug... It's a side effect which is better avoided. * * -- * Jonathan Kamens USnail: * MIT Project Athena 11 Ashford Terrace * jik@Athena.MIT.EDU Allston, MA 02134 * Office: 617-253-8085 Home: 617-782-0710