home | O'Reilly's CD bookshelfs | FreeBSD | Linux | Cisco | Cisco Exam    

UNIX Power Tools

UNIX Power ToolsSearch this book
Previous: 18.6 Stale Symbolic Links Chapter 18
Linking, Renaming, and Copying Files
Next: 18.8 Showing the Actual Filenames for Symbolic Links
 

18.7 Linking Directories

One feature of symbolic links (18.4 ) (a.k.a. symlinks ) is that unlike hard links, you can use symbolic links to link directories as well as files. Since symbolic links can span between filesystems, this can become enormously useful.

For example, sometimes administrators want to install a package in a directory tree that's different from where users and other programs expect it to be. On our site, we like to keep /usr/bin pure - that is, we like to be sure that all the programs in /usr/bin came with the operating system. That way, when we install a new OS, we know for sure that we can overwrite the entirety of /usr/bin and not lose any "local" programs. We install all local programs in /usr/local .

The X11 (1.31 ) package poses a problem, though. X11 programs are expected to be installed in /usr/bin/X11 . But X isn't distributed as part of our OS, so we'd prefer not to put it there. Instead, we install X programs in /usr/local/X11/bin , and create a symbolic link named /usr/bin/X11 . We do the same for /usr/include/X11 and /usr/lib/X11 :

# ln -s /usr/local/X11/bin /usr/bin/X11


# ln -s /usr/local/X11/lib /usr/lib/X11


# ln -s /usr/local/X11/include /usr/include/X11

By using symlinks, we can have it both ways: we installed the package where we wanted to, but kept it invisible to any users or programs that expected the X programs, libraries, or include files to be in the standard directories.

Directory links can result in some unexpected behavior, however. For example, let's suppose I want to look at files in /usr/bin/X11 . I can just cd to /usr/bin/X11 even though the files are really in /usr/local/X11/bin :


-F
 

% cd /usr/bin/X11


% ls -F


       mkfontdir*      xcalc*          xinit*          xset*
   ...

But when I do a pwd , I see that I'm really in /usr/local/X11/bin . If I didn't know about the symlink, this might be confusing for me:

% pwd


/usr/local/X11/bin

Now suppose I want to look at files in /usr/bin . Since I did a cd to /usr/bin/X11 , I might think I can just go up a level. But that doesn't work:

% cd ..


% ls -F


bin/     include/     lib/
% pwd


/usr/local/X11

What happened? Remember that a symbolic link is just a pointer to another file or directory. So when I went to the /usr/bin/X11 directory, my current working directory became the directory /usr/bin/X11 points to, /usr/local/X11/bin .

lndir
As a solution to this problem and others, the X distribution provides a program called lndir . lndir is also provided on our CD-ROM. lndir makes symlinks between directories by creating links for each individual file. It's cheesy, but it works. We can use lndir instead of ln -s :

# lndir /usr/local/X11/bin /usr/bin/X11


# ls -F /usr/bin/X11


X@       mkfontdir@      xcalc@          xinit@          xset@
   ...

- LM


Previous: 18.6 Stale Symbolic Links UNIX Power Tools Next: 18.8 Showing the Actual Filenames for Symbolic Links
18.6 Stale Symbolic Links Book Index 18.8 Showing the Actual Filenames for Symbolic Links

The UNIX CD Bookshelf NavigationThe UNIX CD BookshelfUNIX Power ToolsUNIX in a NutshellLearning the vi Editorsed & awkLearning the Korn ShellLearning the UNIX Operating System










??????????????@Mail.ru