When the dir pointed by a symlink changes its name or ancestral dir(s), the symlink will not work. This happens often. Is there some more or less automatic way to make a symlink keep track of that?
I use symlinks to organize my directories. One topic is represented as a directory. A topic can have several subtopics, in the sense that a directory can have several subdirs. My topics are constantly under reorganization, so I often rename dirs, and change ancestral dirs.
--bind
mounting them. You can maintain the entire tree in/etc/fstab
. – mikeserv Aug 16 '14 at 16:18mount --bind
become not working if I change the mounted dir's ancestral dirs or its names? Is it different from hard links? How does it work? Feel free to post a reply. I always upvote replies. – Tim Aug 16 '14 at 17:19mount
s - such asprivate
(the regular kind),shared
,bind
, andslave
. When deployed correctly, they can completely surmount any need for links of any kind. You can--bind
mount a file over another file, for instance, and you can assign a mount to a namespace - like one process will see a mount tree in one way, while another will see it in another. These are fully filesystem independent. You'll want to do some googling if interested. Tryecho hey >txt.file; sudo mount --bind /dev/null ./txt.file; cat ./txt.file
– mikeserv Aug 16 '14 at 20:32unbindable
mount type (as I did above) or you'll wind up with infinitely recursing mount trees. – mikeserv Aug 17 '14 at 21:59