In summary. Two or more files within the same filesystem with the same inode number are "hard linked".
Scrutinizer has pointed to the link count for an ordinary file in "ls -l". Value 2 or more shows hard links.
"radolouv" has the right idea by using "find -xdev" because inode numbers are only unique within a filesystem. However to find all files hard linked to a given filename the find must be from the mountpoint.
One way of testing whether a file is a "hard link" and then listing all the files with the same inode. This script contains code to find out the mountpoint containing a file under HP-UX. Will need changing for other O/S which don't have this layout of "bdf".
Hi all!
I'd like to know the differences between hard links and soft links. I've already read the ln manpage, but i'm not quite sure of what i understood.
Does a hard link sort of copy the file to a new name, give it the same inode number and same rights?
What exactly should I do to do this:... (3 Replies)
Someone asked me a question today about the difference between a hard link and a soft link. That got me thinking and maybe someone can answer.
Why would I ever use a hard link if I can use a soft link instead? (2 Replies)
hello folks
how y'all doin
well i have some questions about symbolic link and hard link
hope some one answer me
i open terminal and join as root
and i wrote ln -s blah blah
then i wrote ls
i see red file called blah blah
but didn't understand what is this can some one explain and... (2 Replies)
Hello,
In unix, the normal user can't create a hardlink for a directory. why..?
Is there any difference between creating a hard link for a file and directory?
The super user can create a hard link for directories.
Why we cannot create and super user can create.?
Please, can anyone help... (1 Reply)
Hi
PLease let me know the usage of Hard Link vs Soft Link
i.e what is the basic difference and what happens when one file is changed or deleted in both the cases???
thanks (3 Replies)
Hi Experts,
Please help me out to find out difference between a hard link and a soft link.
I am new in unix plz help me with some example commands ( for creating such links).
Regards
S.Kamakshi :) (2 Replies)
Hello,
Please move this if I chose the wrong forum category. This question pertains to Unix and Linux I believe. I google the difference between hard and symbolic/soft links and I understand the difference. What I am trying to find is a real example of a hard link being used in a Operating... (11 Replies)
Is it possible to Hard link a directory? Some people on google say it is possible and some say it is not possible. I haven't seen a working solution though. (3 Replies)
How can I create a hard link to a file, then rename the hard link to a different name? (2 Replies)
Discussion started by: fhill2
2 Replies
LEARN ABOUT NETBSD
info
INFO(1) User Commands INFO(1)NAME
info - read Info documents
SYNOPSIS
info [OPTION]... [MENU-ITEM...]
DESCRIPTION
Read documentation in Info format.
OPTIONS --apropos=STRING
look up STRING in all indices of all manuals.
-d, --directory=DIR
add DIR to INFOPATH.
--dribble=FILENAME
remember user keystrokes in FILENAME.
-f, --file=FILENAME
specify Info file to visit.
-h, --help
display this help and exit.
--index-search=STRING
go to node pointed by index entry STRING.
-n, --node=NODENAME
specify nodes in first visited Info file.
-o, --output=FILENAME
output selected nodes to FILENAME.
-R, --raw-escapes
output "raw" ANSI escapes (default).
--no-raw-escapes
output escapes as literal text.
--restore=FILENAME
read initial keystrokes from FILENAME.
-O, --show-options, --usage
go to command-line options node.
--subnodes
recursively output menu items.
-w, --where, --location
print physical location of Info file.
--vi-keys
use vi-like and less-like key bindings.
--version
display version information and exit.
The first non-option argument, if present, is the menu entry to start from; it is searched for in all `dir' files along INFOPATH. If it is
not present, info merges all `dir' files and shows the result. Any remaining arguments are treated as the names of menu items relative to
the initial node visited.
EXAMPLES
info show top-level dir menu
info emacs
start at emacs node from top-level dir
info emacs buffers
start at buffers node within emacs manual
info --show-options emacs
start at node with emacs' command line options
info -f ./foo.info
show file ./foo.info, not searching dir
REPORTING BUGS
Email bug reports to bug-texinfo@gnu.org, general questions and discussion to help-texinfo@gnu.org. Texinfo home page:
http://www.gnu.org/software/texinfo/
COPYRIGHT
Copyright (C) 2004 Free Software Foundation, Inc. There is NO warranty. You may redistribute this software under the terms of the GNU
General Public License. For more information about these matters, see the files named COPYING.
info 4.8 December 2004 INFO(1)