This is one example of a broken symlink.
By contrast, in the lib64 directory, the "libp" symlink is missing.
The process of creating this single symlink is called tree folding.
There is no create operation; mknod will be called for creation of all non-directory, non-symlink nodes.
With this symlink in place and each deployment in a separate directory, it is easy to roll back to previous versions of the application.
Symlinks do not prevent a file from being deleted; if the target file is moved or deleted, then the symlink will be broken.
To do this, devfsd actually performs a dynamic call to the libc function you specify, in this case symlink() and unlink().
A symlink is somewhat similar to Windows shortcuts or MacOS aliases, which can represent an image of an application that resides in another location, perhaps a different drive or directory.
