Ln - Revision history

68.106.247.149: /* Physical Path */

2011-01-29T22:56:43Z

Physical Path

68.106.247.149: /* Moving Files */

2011-01-29T22:54:19Z

Moving Files

Jimbo: Reverted edits by 80.78.41.16 (Talk); changed back to last version by Jimbo

2010-01-11T19:29:17Z

Reverted edits by 80.78.41.16 (Talk); changed back to last version by Jimbo

80.78.41.16 at 18:04, 11 January 2010

2010-01-11T18:04:11Z

Jimbo: Reverted edits by 201.217.54.113 (Talk); changed back to last version by Jimbo

2010-01-10T17:58:48Z

Reverted edits by 201.217.54.113 (Talk); changed back to last version by Jimbo

201.217.54.113 at 03:44, 10 January 2010

2010-01-10T03:44:33Z

Jimbo: Reverted edits by 69.246.149.141 (Talk); changed back to last version by Jimbo

2010-01-04T23:10:33Z

Reverted edits by 69.246.149.141 (Talk); changed back to last version by Jimbo

69.246.149.141 at 21:32, 4 January 2010

2010-01-04T21:32:03Z

Jimbo: Reverted edits by 98.193.122.73 (Talk); changed back to last version by Jimbo

2009-12-26T20:51:54Z

Reverted edits by 98.193.122.73 (Talk); changed back to last version by Jimbo

98.193.122.73 at 19:56, 26 December 2009

2009-12-26T19:56:52Z

@@ Line 132: / Line 132: @@
   %ln -s /server/www/looknfeel.css physical_path
-This establishes a symbolic link using the physical path, that is, the entire directory path from the [[root]] to the file itself.  Therefore the file 'physuical_path' contains '/server/www/liiknfeel.css'.
+This establishes a symbolic link using the physical path, that is, the entire directory path from the [[root]] to the file itself.  Therefore the file 'physical_path' contains '/server/www/liiknfeel.css'.
 This is how Microsoft's shortcut concept works, for example, 'C:\Program Files\Application\App.exe'.

@@ Line 96: / Line 96: @@
 === Moving Files ===
-Moving files using the '[[mv]]' command on hard-linked files is possible because the inode remains the same, regardless of wether the original file name was used or one of it's linked file names.  Therefore editing a moved file will affect the contents of the original file.
+Moving files using the '[[mv]]' command on hard-linked files is possible because the inode remains the same, regardless of whether the original file name was used or one of it's linked file names.  Therefore editing a moved file will affect the contents of the original file.
 === Copying Files ===

@@ Line 170: / Line 170: @@
 The version of perl installed was 5.8.8, and forms part of the original file name 'perl5.8.8'.  This is hard linked with file names 'perl5' and simply 'perl', as seen by the common inode.
-The reason for these links is for application compatibility.  It is possible ion number (which would be 'perl5.8.8' in this example).  If two versions were installed only one could be hard linked to the simple 'perl' name.
+The reason for these links is for application compatibility.  It is possible a piece of perl script to be executed with the command 'perl', 'perl5' or even 'perl5.8.8' though most typically the first one would be used.  Therefore regardless of the version installed a programmer knows that executing simply 'perl' will start which-ever version it happens to be.  Moving up one level the same programmer could have a version of perl from the 4.x.x release and from the 5.x.x release on the same system.  They then have the ability to just call 'perl4' or 'perl5' without needing to know the actual file name that application takes from the version number (which would be 'perl5.8.8' in this example).  If two versions were installed only one could be hard linked to the simple 'perl' name.
 There are other commands present within the same directory that are linked as the following example illustrates:

@@ Line 170: / Line 170: @@
 The version of perl installed was 5.8.8, and forms part of the original file name 'perl5.8.8'.  This is hard linked with file names 'perl5' and simply 'perl', as seen by the common inode.
-The reason for these links is for application compatibility.  It is possible a piece of perl script to be executed with the command 'perl', 'perl5' or even 'perl5.8.8' though most typically the first one would be used.  Therefore regardless of the version installed a programmer knows that executing simply 'perl' will start which-ever version it happens to be.  Moving up one level the same programmer could have a version of perl from the 4.x.x release and from the 5.x.x release on the same system.  They then have the ability to just call 'perl4' or 'perl5' without needing to know the actual file name that application takes from the version number (which would be 'perl5.8.8' in this example).  If two versions were installed only one could be hard linked to the simple 'perl' name.
+The reason for these links is for application compatibility.  It is possible ion number (which would be 'perl5.8.8' in this example).  If two versions were installed only one could be hard linked to the simple 'perl' name.
 There are other commands present within the same directory that are linked as the following example illustrates:

@@ Line 170: / Line 170: @@
 The version of perl installed was 5.8.8, and forms part of the original file name 'perl5.8.8'.  This is hard linked with file names 'perl5' and simply 'perl', as seen by the common inode.
-The reason for these links isrelease on the same system.  They then have the ability to just call 'perl4' or 'perl5' without needing to know the actual file name that application takes from the version number (which would be 'perl5.8.8' in this example).  If two versions were installed only one could be hard linked to the simple 'perl' name.
+The reason for these links is for application compatibility.  It is possible a piece of perl script to be executed with the command 'perl', 'perl5' or even 'perl5.8.8' though most typically the first one would be used.  Therefore regardless of the version installed a programmer knows that executing simply 'perl' will start which-ever version it happens to be.  Moving up one level the same programmer could have a version of perl from the 4.x.x release and from the 5.x.x release on the same system.  They then have the ability to just call 'perl4' or 'perl5' without needing to know the actual file name that application takes from the version number (which would be 'perl5.8.8' in this example).  If two versions were installed only one could be hard linked to the simple 'perl' name.
 There are other commands present within the same directory that are linked as the following example illustrates:

← Older revision		Revision as of 23:10, 4 January 2010
Line 170:		Line 170:
	The version of perl installed was 5.8.8, and forms part of the original file name 'perl5.8.8'. This is hard linked with file names 'perl5' and simply 'perl', as seen by the common inode.		The version of perl installed was 5.8.8, and forms part of the original file name 'perl5.8.8'. This is hard linked with file names 'perl5' and simply 'perl', as seen by the common inode.

−	The reason for these links is for application compatibility. It is possible	+	The reason for these links is for application compatibility. It is possible a piece of perl script to be executed with the command 'perl', 'perl5' or even 'perl5.8.8' though most typically the first one would be used. Therefore regardless of the version installed a programmer knows that executing simply 'perl' will start which-ever version it happens to be. Moving up one level the same programmer could have a version of perl from the 4.x.x release and from the 5.x.x release on the same system. They then have the ability to just call 'perl4' or 'perl5' without needing to know the actual file name that application takes from the version number (which would be 'perl5.8.8' in this example). If two versions were installed only one could be hard linked to the simple 'perl' name.
		+
		+	There are other commands present within the same directory that are linked as the following example illustrates:
		+
		+	%cd /usr/local/bin
		+	%ls -l
		+	lrwxr-xr-x 1 root wheel 16 Nov 14 17:05 autoconf -> autoconf-wrapper
		+	lrwxr-xr-x 1 root wheel 16 Nov 14 17:05 autoheader -> autoconf-wrapper
		+	lrwxr-xr-x 1 root wheel 16 Nov 14 17:05 autom4te -> autoconf-wrapper
		+	lrwxr-xr-x 1 root wheel 16 Nov 14 17:05 autoreconf -> autoconf-wrapper
		+	lrwxr-xr-x 1 root wheel 16 Nov 14 17:05 autoscan -> autoconf-wrapper
		+	lrwxr-xr-x 1 root wheel 16 Nov 14 17:05 autoupdates -> autoconf-wrapper
		+	lrwxr-xr-x 1 root wheel 16 Nov 14 17:05 ifnames -> autoconf-wrapper
		+	lrwxr-xr-x 1 root wheel 10 Nov 19 13:02 '''ldapadd''' -> '''ldapmodify'''
		+	lrwxr-xr-x 1 root wheel 13 Nov 14 16:39 libpng12-config -> libpng-config
		+	lrwxr-xr-x 1 root wheel 24 Nov 14 16:36 perl5 -> /usr/local/bin/perl5.8.8
		+	lrwxr-xr-x 1 root wheel 5 Nov 19 13:26 zipinfo -> unzip
		+
		+	''This list is filtered to show only the linked file names.''
		+
		+	The file name on the left is the linked name for the file name on the right, as denoted by the textual arrow '->'. The majority of the symbolic links here link to autoconf-wrapper. If a system administrator called the command 'ldapadd' the operating system would really run the command 'ldapmodify' (highlighted above). Like the 'perl' example above, these links exist for compatibility.
		+
		+	[[Category:System Commands]]

@@ Line 170: / Line 170: @@
 The version of perl installed was 5.8.8, and forms part of the original file name 'perl5.8.8'.  This is hard linked with file names 'perl5' and simply 'perl', as seen by the common inode.
-The reason for these links is for application compatibility.  It is possible a piece of perl script to be executed with the command 'perl', 'perl5' or even 'perl5.8.8' though most typically the first one would be used.  Therefore regardless of the version installed a programmer knows that executing simply 'perl' will start which-ever version it happens to be.  Moving up one level the same programmer could have a version of perl from the 4.x.x release and from the 5.x.x release on the same system.  They then have the ability to just call 'perl4' or 'perl5' without needing to know the actual file name that application takes from the version number (which would be 'perl5.8.8' in this example).  If two versions were installed only one could be hard linked to the simple 'perl' name.
+The reason for these links is for application compatibility.  It is possible
-−
-There are other commands present within the same directory that are linked as the following example illustrates:
-−
- %cd /usr/local/bin
- %ls -l
- lrwxr-xr-x  1 root  wheel       16 Nov 14 17:05 autoconf -> autoconf-wrapper
- lrwxr-xr-x  1 root  wheel       16 Nov 14 17:05 autoheader -> autoconf-wrapper
- lrwxr-xr-x  1 root  wheel       16 Nov 14 17:05 autom4te -> autoconf-wrapper
- lrwxr-xr-x  1 root  wheel       16 Nov 14 17:05 autoreconf -> autoconf-wrapper
- lrwxr-xr-x  1 root  wheel       16 Nov 14 17:05 autoscan -> autoconf-wrapper
- lrwxr-xr-x  1 root  wheel       16 Nov 14 17:05 autoupdates -> autoconf-wrapper
- lrwxr-xr-x  1 root  wheel       16 Nov 14 17:05 ifnames -> autoconf-wrapper
- lrwxr-xr-x  1 root  wheel       10 Nov 19 13:02 '''ldapadd''' -> '''ldapmodify'''
- lrwxr-xr-x  1 root  wheel       13 Nov 14 16:39 libpng12-config -> libpng-config
- lrwxr-xr-x  1 root  wheel       24 Nov 14 16:36 perl5 -> /usr/local/bin/perl5.8.8
- lrwxr-xr-x  1 root  wheel        5 Nov 19 13:26 zipinfo -> unzip
-−
-''This list is filtered to show only the linked file names.''
-−
-The file name on the left is the linked name for the file name on the right, as denoted by the textual arrow '->'.  The majority of the symbolic links here link to autoconf-wrapper.  If a system administrator called the command 'ldapadd' the operating system would really run the command 'ldapmodify' (highlighted above).  Like the 'perl' example above, these links exist for compatibility.
-−
-[[Category:System Commands]]

← Older revision		Revision as of 20:51, 26 December 2009
Line 170:		Line 170:
	The version of perl installed was 5.8.8, and forms part of the original file name 'perl5.8.8'. This is hard linked with file names 'perl5' and simply 'perl', as seen by the common inode.		The version of perl installed was 5.8.8, and forms part of the original file name 'perl5.8.8'. This is hard linked with file names 'perl5' and simply 'perl', as seen by the common inode.

−	The reason for these links is for application compatibility. It is possible	+	The reason for these links is for application compatibility. It is possible a piece of perl script to be executed with the command 'perl', 'perl5' or even 'perl5.8.8' though most typically the first one would be used. Therefore regardless of the version installed a programmer knows that executing simply 'perl' will start which-ever version it happens to be. Moving up one level the same programmer could have a version of perl from the 4.x.x release and from the 5.x.x release on the same system. They then have the ability to just call 'perl4' or 'perl5' without needing to know the actual file name that application takes from the version number (which would be 'perl5.8.8' in this example). If two versions were installed only one could be hard linked to the simple 'perl' name.
		+
		+	There are other commands present within the same directory that are linked as the following example illustrates:
		+
		+	%cd /usr/local/bin
		+	%ls -l
		+	lrwxr-xr-x 1 root wheel 16 Nov 14 17:05 autoconf -> autoconf-wrapper
		+	lrwxr-xr-x 1 root wheel 16 Nov 14 17:05 autoheader -> autoconf-wrapper
		+	lrwxr-xr-x 1 root wheel 16 Nov 14 17:05 autom4te -> autoconf-wrapper
		+	lrwxr-xr-x 1 root wheel 16 Nov 14 17:05 autoreconf -> autoconf-wrapper
		+	lrwxr-xr-x 1 root wheel 16 Nov 14 17:05 autoscan -> autoconf-wrapper
		+	lrwxr-xr-x 1 root wheel 16 Nov 14 17:05 autoupdates -> autoconf-wrapper
		+	lrwxr-xr-x 1 root wheel 16 Nov 14 17:05 ifnames -> autoconf-wrapper
		+	lrwxr-xr-x 1 root wheel 10 Nov 19 13:02 '''ldapadd''' -> '''ldapmodify'''
		+	lrwxr-xr-x 1 root wheel 13 Nov 14 16:39 libpng12-config -> libpng-config
		+	lrwxr-xr-x 1 root wheel 24 Nov 14 16:36 perl5 -> /usr/local/bin/perl5.8.8
		+	lrwxr-xr-x 1 root wheel 5 Nov 19 13:26 zipinfo -> unzip
		+
		+	''This list is filtered to show only the linked file names.''
		+
		+	The file name on the left is the linked name for the file name on the right, as denoted by the textual arrow '->'. The majority of the symbolic links here link to autoconf-wrapper. If a system administrator called the command 'ldapadd' the operating system would really run the command 'ldapmodify' (highlighted above). Like the 'perl' example above, these links exist for compatibility.
		+
		+	[[Category:System Commands]]