"Alfred M. Szmidt" <address@hidden> writes:
> > hurd:/home/ams/coreutils/coreutils/src# ./ln -s /ams/foo symlink
> > hurd:/home/ams/coreutils/coreutils/src# ./ln -m /ams/foo firmlink
> > hurd:/home/ams/coreutils/coreutils/src# cd symlink
> > hurd:/home/ams/coreutils/coreutils/src/symlink# ls ..
> > foo hurd.obj lost+found oskit.obj sub-hurd
> > hurd:/home/ams/coreutils/coreutils/src/symlink# cd ../firmlink
> > hurd:/home/ams/coreutils/coreutils/src/firmlink# ls ..
> > CVS
> > Makefile
> > Makefile.am
> > [..snip...]
>
> This looks similar to bind mounts in Linux.
>
> Are those the same thing as union file-systems
I don't know much about union file-systems, but AFAIK they are different
from bind mounts. A bind mount is created by "mount -o bind /foo /bar"
and causes the tree under /foo to be overlayed over /bar, with the former
contents of /bar being hidden. It's like a regular mount, except that the
source is not (a filesystem on) a block device, but a directory.
Andreas.
--
Andreas Schwab, SuSE Labs, address@hidden
SuSE Linux AG, Maxfeldstraße 5, 90409 Nürnberg, Germany
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."