View Single Post
Old 07-02-2012, 09:09 AM   #29
hawhill
Wizard
hawhill ought to be getting tired of karma fortunes by now.hawhill ought to be getting tired of karma fortunes by now.hawhill ought to be getting tired of karma fortunes by now.hawhill ought to be getting tired of karma fortunes by now.hawhill ought to be getting tired of karma fortunes by now.hawhill ought to be getting tired of karma fortunes by now.hawhill ought to be getting tired of karma fortunes by now.hawhill ought to be getting tired of karma fortunes by now.hawhill ought to be getting tired of karma fortunes by now.hawhill ought to be getting tired of karma fortunes by now.hawhill ought to be getting tired of karma fortunes by now.
 
hawhill's Avatar
 
Posts: 1,379
Karma: 2155307
Join Date: Nov 2010
Location: Goettingen, Germany
Device: Kindle Paperwhite, Kobo Mini
Quote:
Originally Posted by knc1 View Post
And a directory need not be empty in any *nix to be used as a mount point. Over-mounting just hides the existing directory contents from new access, which makes it more than a bit hard (as in impossible) to get rid of the previously written contents once the directory is over-mounted.
We're a bit OT here, but *that* is surprisingly easy: You just need to bind-mount the root file system to another place, without recursively binding mounted file systems. I.e. the "bind" mount option, not the "rbind" mount option. Below that bind mount, you will get an accessible mount of the bound file system only. I.e.:
Code:
mkdir rootfs
mount -o bind / rootfs
ls -l rootfs/mnt/us
(untested)
hawhill is offline   Reply With Quote