I can't think of a way to list all the soft links.
To find the hard links, first run ls -li to find out the inode number of the file. Then do a find from the root of the file system (hard links do not cross mount points) for that inode.
Example from a Solaris 10 box:
Code:
> cd /usr/bin
> ls -li zcat
3262 -r-xr-xr-x 3 root bin 27176 Jan 22 2005 zcat
> find . -inum 3262
./compress
./uncompress
./zcat
>
In this case /usr/bin is the root file system, so I chose not to run the find from / as it would look in other file systems. The 3 between the file permissions and root means there are 3 links to one file.
Hi,
I do not want to violate any rules, so thought to ask before posting any links.
Just to contribute to the forum: through surfing I found a link to download "Unix in a Nutshell" (*.chm) FREE.
I was wondering if I can post that link here.
Thanks
Hemang (5 Replies)
HI,
I would like to ask You about some good books or links where I can find information about shells, theoretical information.
I will be grateful if You can help me
And I have question about zsh loop
trivial script:
#!/bin/zsh
for i in {1..100000}
do
echo $i;
doneexec time is 10... (9 Replies)
Hi,
I have a file with more than 1 layers of soft links for it. For ex.
ls -la .profile
.profile@ -> /home/act/.profile_abc
ls -la
/home/act/.profile_abc@ -> .profile_final
I want to get the name of the last file (i.e. .profile_final) when I refer to .profile using shell script. I... (2 Replies)
Hello.
I have some main directories.
For example :
/main_dir1
/main_dir2In main_dir2, I have a sub dir named sub_dir2-1 with 2 files in it ( file_2-1, file_2-2 )
/main_dir2sub_dir2-1file_2-1
file_2-2From "/main_dir1/A/B/C" I make a soft link
ln -s /main_dir2/sub_dir2-1 ... (6 Replies)
Discussion started by: jcdole
6 Replies
LEARN ABOUT MINIX
link
LINK(2) System Calls Manual LINK(2)NAME
link - make a hard link to a file
SYNOPSIS
#include <unistd.h>
int link(const char *name1, const char *name2)
DESCRIPTION
A hard link to name1 is created; the link has the name name2. Name1 must exist.
With hard links, both name1 and name2 must be in the same file system. Name1 must not be a directory. Both the old and the new link share
equal access and rights to the underlying object.
RETURN VALUE
Upon successful completion, a value of 0 is returned. Otherwise, a value of -1 is returned and errno is set to indicate the error.
ERRORS
Link will fail and no link will be created if one or more of the following are true:
[ENOTDIR] A component of either path prefix is not a directory.
[ENAMETOOLONG] A path name exceeds PATH_MAX characters.
[ENOENT] A component of either path prefix does not exist.
[EACCES] A component of either path prefix denies search permission.
[EACCES] The requested link requires writing in a directory with a mode that denies write permission.
[ELOOP] Too many symbolic links were encountered in translating one of the pathnames. (Minix-vmd)
[ENOENT] The file named by name1 does not exist.
[EEXIST] The link named by name2 does exist.
[EPERM] The file named by name1 is a directory and the effective user ID is not super-user.
[EXDEV] The link named by name2 and the file named by name1 are on different file systems.
[ENOSPC] The directory in which the entry for the new link is being placed cannot be extended because there is no space left on the
file system containing the directory.
[EIO] An I/O error occurred while reading from or writing to the file system to make the directory entry.
[EROFS] The requested link requires writing in a directory on a read-only file system.
[EFAULT] One of the pathnames specified is outside the process's allocated address space.
SEE ALSO symlink(2), unlink(2).
4th Berkeley Distribution August 26, 1985 LINK(2)