Symlinks are actually very simple pointer files. It's quite easy to end up with links pointing at missing files or the wrong files by creating them incorrectly.
In your case, you asked for a link called "text.txt" (because you only specified a directory as the second arguement) pointing to "text.txt" and to place it in the 'test' directory.
It did what you asked
If you want a relative symlink pointing to text.txt in the test directory, you need to create it from within the target dir. Otherwise, you can use an absolute link instead:
Would I be correct in assuming that find doesn't bother recursivley searching down sim links. (It doesn't seem to so I guess it doesn't!!!) Is there anyway to make it do so? (3 Replies)
I have some crypting functions in object-file - for example,func.o
Main file,from where crypting functions called, named as main.cpp .
"gcc main.cpp -o main func.o" print "undefined reference to ... "
But if I rename main.cpp to main.c and execute
"gcc main.c -o main func.o" - ok. If anybody,... (3 Replies)
Dear linuxers,
I'm a novice in C++ programming.
I wrote a ReadFile class in file ReadFile.cpp.
After that, I wrote a test.cpp, which contains a main function, to test whether my class work well.
I follow the following steps to compile the ReadFile.cpp file.
g++296 -c ReadFile.cpp -o... (4 Replies)
Hi,
I am using Mac X 10.5. It's supporting BSD. I am getting strange problem.
• Launch the terminal.
• Create a directory. Use cd <directory>
• Now create another directory test with command “mkdir test”.
• Create a soft link with command “ln -s text.txt test”
• Go to the test directory... (1 Reply)
Hello,
I have one issue with linking folders.
I have two domains (domain1 and domain2) on one server (centOS). In domain1, I have one folder containing many images which I want to share for domain2. So i have created link for image directory using below command.
ln -s... (1 Reply)
Hello
A new file is created every day with the date appended to the end of a name. We are using Autosys to run jobs which watches for the file and runs jobs. But Autosys does not have the capability to figure out the current date.
I tried creating a symlink like this
ln -s... (1 Reply)
Hi
i need to install a software into a zone, and this kind of software needs to have a file who is linked into /dev.
But it is not possible to create a link into /dev nor create a file into it.
-bash-3.00# ln -s /tmp/testfile /dev/
ln: cannot create /dev//testfile: Permission denied... (2 Replies)
Hi. Can somebody tell me if there's a way of creating a symbolic link from a directory on one filesystem to that on another that will allow a find command that doesn't use the -L param to locate a particular file under that new 'linked' dir. With a normal sym link the find command on that... (6 Replies)
Discussion started by: user052009
6 Replies
LEARN ABOUT SUNOS
ln
ln(1B) SunOS/BSD Compatibility Package Commands ln(1B)NAME
ln - make hard or symbolic links to files
SYNOPSIS
/usr/ucb/ln [-fs] filename [linkname]
/usr/ucb/ln [-fs] pathname... directory
DESCRIPTION
The /usr/ucb/ln utility creates an additional directory entry, called a link, to a file or directory. Any number of links can be assigned
to a file. The number of links does not affect other file attributes such as size, protections, data, etc.
filename is the name of the original file or directory. linkname is the new name to associate with the file or filename. If linkname is
omitted, the last component of filename is used as the name of the link.
If the last argument is the name of a directory, symbolic links are made in that directory for each pathname argument; /usr/ucb/ln uses the
last component of each pathname as the name of each link in the named directory.
A hard link (the default) is a standard directory entry just like the one made when the file was created. Hard links can only be made to
existing files. Hard links cannot be made across file systems (disk partitions, mounted file systems). To remove a file, all hard links
to it must be removed, including the name by which it was first created; removing the last hard link releases the inode associated with the
file.
A symbolic link, made with the -s option, is a special directory entry that points to another named file. Symbolic links can span file sys-
tems and point to directories. In fact, you can create a symbolic link that points to a file that is currently absent from the file sys-
tem; removing the file that it points to does not affect or alter the symbolic link itself.
A symbolic link to a directory behaves differently than you might expect in certain cases. While an ls(1) on such a link displays the
files in the pointed-to directory, an `ls -l' displays information about the link itself:
example% /usr/ucb/ln -s dir link
example% ls link
file1 file2 file3 file4
example% ls -l link
lrwxrwxrwx 1 user 7 Jan 11 23:27 link -> dir
When you use cd(1) to change to a directory through a symbolic link, you wind up in the pointed-to location within the file system. This
means that the parent of the new working directory is not the parent of the symbolic link, but rather, the parent of the pointed-to direc-
tory. For instance, in the following case the final working directory is /usr and not /home/user/linktest.
example% pwd
/home/user/linktest
example% /usr/ucb/ln -s /var/tmp symlink
example% cd symlink
example% cd ..
example% pwd
/usr
C shell user's can avoid any resulting navigation problems by using the pushd and popd built-in commands instead of cd.
OPTIONS -f Force a hard link to a directory. This option is only available to the super-user, and should be used with extreme caution.
-s Create a symbolic link or links.
USAGE
See largefile(5) for the description of the behavior of ln when encountering files greater than or equal to 2 Gbyte ( 2**31 bytes).
EXAMPLES
Example 1: The /usr/ucb/ln command
The commands below illustrate the effects of the different forms of the /usr/ucb/ln command:
example% /usr/ucb/ln file link
example% ls -F file link
file link
example% /usr/ucb/ln -s file symlink
example% ls -F file symlink
file symlink@
example% ls -li file link symlink
10606 -rw-r--r-- 2 user 0 Jan 12 00:06 file
10606 -rw-r--r-- 2 user 0 Jan 12 00:06 link
10607 lrwxrwxrwx 1 user 4 Jan 12 00:06 symlink -> file
example% /usr/ucb/ln -s nonesuch devoid
example% ls -F devoid
devoid@
example% cat devoid
devoid: No such file or directory
example% /usr/ucb/ln -s /proto/bin/* /tmp/bin
example% ls -F /proto/bin /tmp/bin
/proto/bin:
x* y* z*
/tmp/bin:
x@ y@ z@
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWscpu |
+-----------------------------+-----------------------------+
SEE ALSO cp(1), ls(1), mv(1), rm(1), link(2), readlink(2), stat(2), symlink(2), attributes(5), largefile(5)NOTES
When the last argument is a directory, simple basenames should not be used for pathname arguments. If a basename is used, the resulting
symbolic link points to itself:
example% /usr/ucb/ln -s file /tmp
example% ls -l /tmp/file
lrwxrwxrwx 1 user 4 Jan 12 00:16 /tmp/file -> file
example% cat /tmp/file
/tmp/file: Too many levels of symbolic links
To avoid this problem, use full pathnames, or prepend a reference to the PWD variable to files in the working directory:
example% rm /tmp/file
example% /usr/ucb/ln -s $PWD/file /tmp
lrwxrwxrwx 1 user 4 Jan 12 00:16 /tmp/file ->
/home/user/subdir/file
SunOS 5.10 11 Mar 1994 ln(1B)
10-19-2008
