A quick look, makes me think that they are all hardlinks:
Code:
Terry@dixie$ uname -a 3:03
FreeBSD dixie.launchmodem.com 7.0-STABLE FreeBSD 7.0-STABLE #0:
Thu Jul 17 15:17:58 UTC 2008
root@sall1600.launchmodem.com:/usr/obj/usr/src/sys/VIPER i386
Terry@dixie$ stat -Lx /usr/bin/nvi 3:26
File: "/usr/bin/nvi"
Size: 305964 FileType: Regular File
Mode: (0555/-r-xr-xr-x) Uid: ( 0/ root) Gid: ( 0/ wheel)
Device: 0,91 Inode: 6382697 Links: 6
Access: Tue Sep 9 05:44:13 2008
Modify: Thu Jul 17 20:27:57 2008
Change: Thu Jul 17 20:27:58 2008
Terry@dixie$ ls -i1 /usr/bin/n{vi,ex,view} /usr/bin/{vi,ex,view} 3:26
6382697 /usr/bin/ex*
6382697 /usr/bin/nex*
6382697 /usr/bin/nvi*
6382697 /usr/bin/nview*
6382697 /usr/bin/vi*
6382697 /usr/bin/view*
Terry@dixie$ 3:27
The source code for nvi also seems to show that it adopts itself based the name of the executable file.
__________________
My
Journal
Thou shalt check the array bounds of all strings (indeed, all arrays), for surely where thou typest ``foo'' someone someday shall type ``supercalifragilisticexpialidocious''.