|
|
|
![]() |
![]() |
![]() |
![]() |
IBM : developerWorks : Linux : Education - Tutorials![]() | ![]() ![]() ![]() ![]() |
![]() |
![]() | |||||
![]() | ![]() | ![]() | ![]() | ![]() | ![]() |
![]() | ||||
Symbolic links are generally more flexible than hard links. You can create a symbolic link to any type of filesystem object, including directories. And because the implementation of symbolic links is based on paths (not inodes), it's perfectly fine to create a symbolic link that points to an object on another filesystem. However, this fact can also make symbolic links tricky to understand. |
![]() | ![]() | ![]() | ![]() | ![]() | ![]() |
![]() |
|
|