### <a name="3.07 Which TCP/IP ports and pro"></a> 3.07 Which TCP/IP ports and protocols do I need to enable in order to operate AFS through my Internet firewall?
-Assuming you have already taken care of nameserving, you may wish to use an Internet timeserver for Network Time Protocol [[[NTP|Main/FurtherReading#NTP]]] and the question about [[timed|Main/WebHome#NTP]]:
+Assuming you have already taken care of nameserving, you may wish to use an Internet timeserver for Network Time Protocol [[[NTP|FurtherReading#NTP]]] and the question about [[timed|WebHome#NTP]]:
ntp 123/udp
No.
-<a name="NTP"></a> The AFS Servers make use of NTP [[[NTP|Main/FurtherReading#NTP]]] to synchronise time each other and typically with one or more external NTP servers. By default, clients synchronize their time with one of the servers in the local cell. Thus all the machines participating in the AFS cell have an accurate view of the time.
+<a name="NTP"></a> The AFS Servers make use of NTP [[[NTP|FurtherReading#NTP]]] to synchronise time each other and typically with one or more external NTP servers. By default, clients synchronize their time with one of the servers in the local cell. Thus all the machines participating in the AFS cell have an accurate view of the time.
For further details on NTP see: <http://www.eecis.udel.edu/~ntp/>. The latest version is 4.1, dated August 2001, which is **much** more recent that the version packaged with Transarc AFS.
</tr>
<tr>
<td> 1983 </td>
- <td>[[AndrewProject]] started at [[Main/CarnegieMellonUniversity]]</td>
+ <td>[[AndrewProject]] started at [[CarnegieMellonUniversity]]</td>
</tr>
<tr>
<td> 1987 </td>
[[LeoShyhWeiLuan]] has proposed a [[JavaAPI]] to simplify writing and sharing tools.
-There is also a Perl API, written by Roland Schemers and now maintained and developed by [[Norbert E. Gr�ner|Main/NorbertGruener]] and described on his [AFS Perl Kwiki](http://www.mpa-garching.mpg.de/kwiki/nog/afsperl/), which provides access to most of the AFS programming API. It comes with extensive [documentation](http://www.mpa-garching.mpg.de/~nog/doc/afsperl.html).
+There is also a Perl API, written by Roland Schemers and now maintained and developed by [[Norbert E. Gr�ner|NorbertGruener]] and described on his [AFS Perl Kwiki](http://www.mpa-garching.mpg.de/kwiki/nog/afsperl/), which provides access to most of the AFS programming API. It comes with extensive [documentation](http://www.mpa-garching.mpg.de/~nog/doc/afsperl.html).
----
</tr>
</table>
-Arguments controlling the [[VLRU:|Main/WebHome#VolumeLeastRecentlyUsed]]
+Arguments controlling the [[VLRU:|WebHome#VolumeLeastRecentlyUsed]]
<table border="1" cellpadding="0" cellspacing="0">
<tr>
- encrypted passwords no longer need to be visible
- You don't have to use NIS, aka yellow pages, to distribute /etc/passwd - thus "ypcat passwd" can be eliminated.
- - If you do choose to use NIS, you can replace the password field with "X" so the encrypted password is not visible. (These issues are discussed in detail in [[[AdminGuide|Main/FurtherReading#AdminGuide]]]).
+ - If you do choose to use NIS, you can replace the password field with "X" so the encrypted password is not visible. (These issues are discussed in detail in [[[AdminGuide|FurtherReading#AdminGuide]]]).
- AFS uses mutual authentication - both the service provider and service requester prove their identities
#### <a name="1.05.i Communications protocol"></a> 1.05.i Communications protocol
-AFS communications protocol is optimized for Wide Area Networks. Retransmitting only the single bad packet in a batch of packets and allowing the number of unacknowledged packets to be higher (than in other protocols, see [[[Johnson90|Main/FurtherReading#Johnson90]]]).
+AFS communications protocol is optimized for Wide Area Networks. Retransmitting only the single bad packet in a batch of packets and allowing the number of unacknowledged packets to be higher (than in other protocols, see [[[Johnson90|FurtherReading#Johnson90]]]).
#### <a name="1.05.j Improved system manageme"></a> 1.05.j Improved system management capability
Originally AFS shipped with it's own version of a Kerberos, called "KAS." KAS still ships at this time (1.4.2 release) but is depricated in favor of using a true Kerberos 5 implimentation. [[OpenAFS]] does not currently ship with a K5 install; it is up to the administrator(s) to choose a version (either MIT's or KTH's "Heimdal") and install it. [[OpenAFS]] will happily work with either.
-For more detail on this and other Kerberos issues see the faq for Kerberos (posted to news.answers and comp.protocols.kerberos) [[[Jaspan|Main/FurtherReading#Jaspan]]]. (Also, see [[[Miller87|Main/FurtherReading#Miller87]]], [[[Bryant88|Main/FurtherReading#Bryant88]]], [[[Bellovin90|Main/FurtherReading#Bellovin90]]], [[[Steiner88|Main/FurtherReading#Steiner88]]])
+For more detail on this and other Kerberos issues see the faq for Kerberos (posted to news.answers and comp.protocols.kerberos) [[[Jaspan|FurtherReading#Jaspan]]]. (Also, see [[[Miller87|FurtherReading#Miller87]]], [[[Bryant88|FurtherReading#Bryant88]]], [[[Bellovin90|FurtherReading#Bellovin90]]], [[[Steiner88|FurtherReading#Steiner88]]])
### <a name="1.09 Does AFS work over protoco"></a> 1.09 Does AFS work over protocols other than TCP/IP?
## <a name="What to do next?"></a> What to do next?
- [[InstallOpenAFSClient]]
-- [[AFS Quick Start Guide for UNIX|Main/AFSQuickStartGuideForUNIX]]
-- [[Example USS Templates|Main/ExampleUSSTemplates]]
+- [[AFS Quick Start Guide for UNIX|AFSQuickStartGuideForUNIX]]
+- [[Example USS Templates|ExampleUSSTemplates]]
- [AFS intro doc at Stanford](http://www.stanford.edu/services/afs/intro/)
- [AFS into at IBM developerworks](http://www.ibm.com/developerworks/opensource/library/os-openafs-kerberos5/index.html)
# <a name="Git and gerrit for gatekeepers"></a> Git and gerrit for gatekeepers
-Firstly, please read the [[Git and gerrit for developers|Main/GitDevelopers]] document. This document only details gatekeeper specific workflow - it's worth reading the git basics first!
+Firstly, please read the [[Git and gerrit for developers|GitDevelopers]] document. This document only details gatekeeper specific workflow - it's worth reading the git basics first!
## <a name="Getting started"></a> Getting started
# /etc/rc.afs
-[[Confirm Cache Manager Initialization|Main/ConfirmCacheManagerInitialization]]
+[[Confirm Cache Manager Initialization|ConfirmCacheManagerInitialization]]
## <a name="Automatically Start AFS on Syste"></a> Automatically Start AFS on System Boot
# /sbin/init.d/afs start
-[[Confirm Cache Manager Initialization|Main/ConfirmCacheManagerInitialization]]
+[[Confirm Cache Manager Initialization|ConfirmCacheManagerInitialization]]
## <a name="Automatically Start AFS on Syste"></a> Automatically Start AFS on System Boot
# /sbin/init.d/afs start
-[[Confirm Cache Manager Initialization|Main/ConfirmCacheManagerInitialization]]
+[[Confirm Cache Manager Initialization|ConfirmCacheManagerInitialization]]
## <a name="Automatically Start AFS on Syste"></a> Automatically Start AFS on System Boot
# /etc/init.d/afs start
-[[Confirm Cache Manager Initialization|Main/ConfirmCacheManagerInitialization]]
+[[Confirm Cache Manager Initialization|ConfirmCacheManagerInitialization]]
## <a name="Automatically Start AFS on Syste"></a> Automatically Start AFS on System Boot
# /etc/rc.d/init.d/afs start
-[[Confirm Cache Manager Initialization|Main/ConfirmCacheManagerInitialization]]
+[[Confirm Cache Manager Initialization|ConfirmCacheManagerInitialization]]
## <a name="Automatically Start AFS on Syste"></a> Automatically Start AFS on System Boot
# /etc/init.d/afs start
-[[Confirm Cache Manager Initialization|Main/ConfirmCacheManagerInitialization]]
+[[Confirm Cache Manager Initialization|ConfirmCacheManagerInitialization]]
## <a name="Automatically Start AFS on Syste"></a> Automatically Start AFS on System Boot
## <a name="Loading AFS into the AIX Kernel"></a> Loading AFS into the AIX Kernel
-[[Loading AFS into the AIX Kernel|Main/LoadingAFSIntoTheAIXKernel]]
+[[Loading AFS into the AIX Kernel|LoadingAFSIntoTheAIXKernel]]
## <a name="Enabling AFS Login on AIX System"></a> Enabling AFS Login on AIX Systems
-[[Enabling AFS Login on AIX Systems|Main/EnablingAFSLoginOnAIXSystems]]
+[[Enabling AFS Login on AIX Systems|EnablingAFSLoginOnAIXSystems]]
Proceed to Loading and Creating Client Files.
## <a name="Building AFS into the Digital UN"></a> Building AFS into the Digital UNIX Kernel
-[[Building AFS into the Digital UNIX Kernel|Main/BuildingAFSIntoTheDigitalUNIXKernel]]
+[[Building AFS into the Digital UNIX Kernel|BuildingAFSIntoTheDigitalUNIXKernel]]
## <a name="Enabling AFS Login on Digital UN"></a> Enabling AFS Login on Digital UNIX Systems
-[[Enabling AFS Login on Digital UNIX Systems|Main/EnablingAFSLoginOnDigitalUNIXSystems]]
+[[Enabling AFS Login on Digital UNIX Systems|EnablingAFSLoginOnDigitalUNIXSystems]]
Proceed to Loading and Creating Client Files.
## <a name="Building AFS into the HP-UX Kern"></a> Building AFS into the HP-UX Kernel
-[[Building AFS into the HP-UX Kernel|Main/BuildingAFSIntoTheHP-UXKernel]]
+[[Building AFS into the HP-UX Kernel|BuildingAFSIntoTheHP-UXKernel]]
## <a name="Enabling AFS Login on HP-UX Syst"></a> Enabling AFS Login on HP-UX Systems
-[[Enabling AFS Login on HP-UX Systems|Main/EnablingAFSLoginOnHP-UXSystems]]
+[[Enabling AFS Login on HP-UX Systems|EnablingAFSLoginOnHP-UXSystems]]
Proceed to Loading and Creating Client Files.
## <a name="Loading AFS Into The IRIX Kernel"></a> Loading AFS Into The IRIX Kernel
-[[Loading AFS into the IRIX Kernel|Main/LoadingAFSIntoTheIRIXKernel]]
+[[Loading AFS into the IRIX Kernel|LoadingAFSIntoTheIRIXKernel]]
## <a name="Enabling AFS Login on IRIX Syste"></a> Enabling AFS Login on IRIX Systems
-[[Enabling AFS Login on IRIX Systems|Main/EnablingAFSLoginOnIRIXSystems]].
+[[Enabling AFS Login on IRIX Systems|EnablingAFSLoginOnIRIXSystems]].
After taking any necessary action, proceed to Loading and Creating Client Files.
## <a name="Loading AFS into the Linux Kerne"></a> Loading AFS into the Linux Kernel
-[[Loading AFS into the Linux Kernel|Main/LoadingAFSIntoTheLinuxKernel]]
+[[Loading AFS into the Linux Kernel|LoadingAFSIntoTheLinuxKernel]]
## <a name="Enabling AFS Login on Linux Syst"></a> Enabling AFS Login on Linux Systems
-[[Enabling AFS Login on Linux Systems|Main/EnablingAFSLoginOnLinuxSystems]]
+[[Enabling AFS Login on Linux Systems|EnablingAFSLoginOnLinuxSystems]]
Proceed to Loading and Creating Client Files.
## <a name="Loading AFS into the Solaris Ker"></a> Loading AFS into the Solaris Kernel
-[[Loading AFS into the Solaris Kernel|Main/LoadingAFSIntoTheSolarisKernel]]
+[[Loading AFS into the Solaris Kernel|LoadingAFSIntoTheSolarisKernel]]
## <a name="Enabling AFS Login on Solaris Sy"></a> Enabling AFS Login on Solaris Systems
-[[Enabling AFS Login on Solaris Systems|Main/EnablingAFSLoginOnSolarisSystems]]
+[[Enabling AFS Login on Solaris Systems|EnablingAFSLoginOnSolarisSystems]]
Proceed to Loading and Creating Client Files.
\* An existing client machine in your cell
-\* The [[CellServDB]].sample file included in the sysname/root.client/usr/vice/etc directory of each AFS CD-ROM; add an entry for the local cell by following the instructions in [[Creating the Client CellServDB File|Main/CreatingTheClientCellServDBFile]]
+\* The [[CellServDB]].sample file included in the sysname/root.client/usr/vice/etc directory of each AFS CD-ROM; add an entry for the local cell by following the instructions in [[Creating the Client CellServDB File|CreatingTheClientCellServDBFile]]
## <a name="Configuring the Cache"></a> Configuring the Cache
-[[Configuring the Cache|Main/ConfiguringTheCache]]
+[[Configuring the Cache|ConfiguringTheCache]]
## <a name="Configuring the Cache Manager"></a> Configuring the Cache Manager
-[[Configuring the Cache Manager|Main/ConfiguringTheCacheManager]]
+[[Configuring the Cache Manager|ConfiguringTheCacheManager]]
## <a name="Starting the Cache Manager and I"></a> Starting the Cache Manager and Installing the AFS Initialization Script
## <a name="Running the Script on AIX System"></a> Running the Script on AIX Systems
-[[Initialization Script on AIX|Main/InitializationScriptOnAIX]]
+[[Initialization Script on AIX|InitializationScriptOnAIX]]
If a volume for housing AFS binaries for this machine's system type does not already exist, proceed to Setting Up Volumes and Loading Binaries into AFS. Otherwise, the installation is complete.
## <a name="Running the Script on Digital UN"></a> Running the Script on Digital UNIX Systems
-[[Initialization Script on Digital UNIX|Main/InitializationScriptOnDigitalUNIX]]
+[[Initialization Script on Digital UNIX|InitializationScriptOnDigitalUNIX]]
If a volume for housing AFS binaries for this machine's system type does not already exist, proceed to Setting Up Volumes and Loading Binaries into AFS. Otherwise, the installation is complete.
## <a name="Running the Script on HP-UX Syst"></a> Running the Script on HP-UX Systems
-[[Initialization Script on HP-UX|Main/InitializationScriptOnHP-UX]]
+[[Initialization Script on HP-UX|InitializationScriptOnHP-UX]]
If a volume for housing AFS binaries for this machine's system type does not already exist, proceed to Setting Up Volumes and Loading Binaries into AFS. Otherwise, the installation is complete.
## <a name="Running the Script on IRIX Syste"></a> Running the Script on IRIX Systems
-[[Initialization Script on IRIX|Main/InitializationScriptOnIRIX]]
+[[Initialization Script on IRIX|InitializationScriptOnIRIX]]
If a volume for housing AFS binaries for this machine's system type does not already exist, proceed to Setting Up Volumes and Loading Binaries into AFS. Otherwise, the installation is complete.
## <a name="Running the Script on Linux Syst"></a> Running the Script on Linux Systems
-[[Initialization Script on Linux|Main/InitializationScriptOnLinux]]
+[[Initialization Script on Linux|InitializationScriptOnLinux]]
If a volume for housing AFS binaries for this machine's system type does not already exist, proceed to Setting Up Volumes and Loading Binaries into AFS. Otherwise, the installation is complete.
## <a name="Running the Script on Solaris Sy"></a> Running the Script on Solaris Systems
-[[Initialization Script on Solaris|Main/InitializationScriptOnSolaris]]
+[[Initialization Script on Solaris|InitializationScriptOnSolaris]]
If a volume for housing AFS binaries for this machine's system type does not already exist, proceed to Setting Up Volumes and Loading Binaries into AFS. Otherwise, the installation is complete.
# <a name="Getting Started on AIX Systems"></a> Getting Started on AIX Systems
-[[Loading AFS into the AIX Kernel|Main/LoadingAFSIntoTheAIXKernel]]
+[[Loading AFS into the AIX Kernel|LoadingAFSIntoTheAIXKernel]]
## <a name="Replacing the fsck Program Helpe"></a> Replacing the fsck Program Helper on AIX Systems
Never run the standard fsck program on AFS server partitions. It discards AFS volumes.
-[[Replacing the fsck Program Helper on AIX Systems|Main/ReplacingTheFsckProgramHelperOnAIXSystems]]
+[[Replacing the fsck Program Helper on AIX Systems|ReplacingTheFsckProgramHelperOnAIXSystems]]
## <a name="Configuring Server Volumes on AI"></a> Configuring Server Volumes on AIX Systems
If this system is going to be used as a file server to share some of its disk space, create a directory called /vicepxx for each AFS server partition you are configuring (there must be at least one). If it is not going to be a file server you can skip this step.
-[[Configuring Server Volumes on AIX|Main/ConfiguringServerVolumesOnAIX]]
+[[Configuring Server Volumes on AIX|ConfiguringServerVolumesOnAIX]]
-If the machine is to remain an AFS client, incorporate AFS into its authentication system, following the instructions in [[Enabling AFS Login on AIX Systems|Main/EnablingAFSLoginOnAIXSystems]].
+If the machine is to remain an AFS client, incorporate AFS into its authentication system, following the instructions in [[Enabling AFS Login on AIX Systems|EnablingAFSLoginOnAIXSystems]].
Proceed to Starting Server Programs.
If the machine's hardware and software configuration exactly matches another Digital UNIX machine on which AFS is already built into the kernel, you can copy the kernel from that machine to this one. In general, however, it is better to build AFS modifications into the kernel on each machine according to the following instructions.
-[[Building AFS into the Digital UNIX Kernel|Main/BuildingAFSIntoTheDigitalUNIXKernel]]
+[[Building AFS into the Digital UNIX Kernel|BuildingAFSIntoTheDigitalUNIXKernel]]
## <a name="Replacing the fsck Program on Di"></a> Replacing the fsck Program on Digital UNIX Systems
Never run the standard fsck program on AFS server partitions. It discards AFS volumes.
-[[Replacing the fsck Program on Digital UNIX Systems|Main/ReplacingTheFsckProgramOnDigitalUNIXSystems]]
+[[Replacing the fsck Program on Digital UNIX Systems|ReplacingTheFsckProgramOnDigitalUNIXSystems]]
## <a name="Configuring Server Volumes on Di"></a> Configuring Server Volumes on Digital UNIX Systems
If this system is going to be used as a file server to share some of its disk space, create a directory called /vicepxx for each AFS server partition you are configuring (there must be at least one). If it is not going to be a file server you can skip this step.
-[[Configuring Server Volumes on Digital UNIX|Main/ConfiguringServerVolumesOnDigitalUNIX]]
+[[Configuring Server Volumes on Digital UNIX|ConfiguringServerVolumesOnDigitalUNIX]]
-If the machine is to remain an AFS client, incorporate AFS into its authentication system, following the instructions in [[Enabling AFS Login on Digital UNIX Systems|Main/EnablingAFSLoginOnDigitalUNIXSystems]].
+If the machine is to remain an AFS client, incorporate AFS into its authentication system, following the instructions in [[Enabling AFS Login on Digital UNIX Systems|EnablingAFSLoginOnDigitalUNIXSystems]].
Proceed to Starting Server Programs.
Begin by building AFS modifications into the kernel, then configure server partitions and replace the HP-UX fsck program with a version that correctly handles AFS volumes.
-[[Building AFS into the HP-UX Kernel|Main/BuildingAFSIntoTheHP-UXKernel]]
+[[Building AFS into the HP-UX Kernel|BuildingAFSIntoTheHP-UXKernel]]
## <a name="Configuring the AFS-modified fsc"></a> Configuring the AFS-modified fsck Program on HP-UX Systems
Never run the standard fsck program on AFS server partitions. It discards AFS volumes.
-[[Configuring the AFS-modified fsck Program on HP-UX Systems|Main/ConfiguringTheAFS-modifiedFsckProgramOnHP-UXSystems]]
+[[Configuring the AFS-modified fsck Program on HP-UX Systems|ConfiguringTheAFS-modifiedFsckProgramOnHP-UXSystems]]
## <a name="Configuring Server Volumes on HP"></a> Configuring Server Volumes on HP-UX Systems
If this system is going to be used as a file server to share some of its disk space, create a directory called /vicepxx for each AFS server partition you are configuring (there must be at least one). If it is not going to be a file server you can skip this step.
-[[Configuring Server Volumes on HP-UX|Main/ConfiguringServerVolumesOnHP-UX]]
+[[Configuring Server Volumes on HP-UX|ConfiguringServerVolumesOnHP-UX]]
-If the machine is to remain an AFS client, incorporate AFS into its authentication system, following the instructions in [[Enabling AFS Login on HP-UX Systems|Main/EnablingAFSLoginOnHP-UXSystems]].
+If the machine is to remain an AFS client, incorporate AFS into its authentication system, following the instructions in [[Enabling AFS Login on HP-UX Systems|EnablingAFSLoginOnHP-UXSystems]].
Proceed to Starting Server Programs.
You do not need to replace IRIX fsck program, because the version that SGI distributes handles AFS volumes properly.
-[[Loading AFS into the IRIX Kernel|Main/LoadingAFSIntoTheIRIXKernel]]
+[[Loading AFS into the IRIX Kernel|LoadingAFSIntoTheIRIXKernel]]
## <a name="Configuring Server Volumes on IR"></a> Configuring Server Volumes on IRIX Systems
If this system is going to be used as a file server to share some of its disk space, create a directory called /vicepxx for each AFS server partition you are configuring (there must be at least one). If it is not going to be a file server you can skip this step.
-[[Configuring Server Volumes on IRIX|Main/ConfiguringServerVolumesOnIRIX]]
+[[Configuring Server Volumes on IRIX|ConfiguringServerVolumesOnIRIX]]
-1. If the machine is to remain an AFS client, incorporate AFS into its authentication system, following the instructions in [[Enabling AFS Login on IRIX Systems|Main/EnablingAFSLoginOnIRIXSystems]].
+1. If the machine is to remain an AFS client, incorporate AFS into its authentication system, following the instructions in [[Enabling AFS Login on IRIX Systems|EnablingAFSLoginOnIRIXSystems]].
1. Proceed to Starting Server Programs.
# <a name="Getting Started on Linux Systems"></a> Getting Started on Linux Systems
-[[Loading AFS into the Linux Kernel|Main/LoadingAFSIntoTheLinuxKernel]]
+[[Loading AFS into the Linux Kernel|LoadingAFSIntoTheLinuxKernel]]
## <a name="Configuring Server Volumes on Li"></a> Configuring Server Volumes on Linux Systems
If this system is going to be used as a file server to share some of its disk space, create a directory called /vicepxx for each AFS server partition you are configuring (there must be at least one). If it is not going to be a file server you can skip this step.
-[[Configuring Server Volumes on Linux|Main/ConfiguringServerVolumesOnLinux]]
+[[Configuring Server Volumes on Linux|ConfiguringServerVolumesOnLinux]]
-If the machine is to remain an AFS client, incorporate AFS into its authentication system, following the instructions in [[Enabling AFS Login on Linux Systems|Main/EnablingAFSLoginOnLinuxSystems]].
+If the machine is to remain an AFS client, incorporate AFS into its authentication system, following the instructions in [[Enabling AFS Login on Linux Systems|EnablingAFSLoginOnLinuxSystems]].
Proceed to Starting Server Programs.
# <a name="Getting Started on Solaris Syste"></a> Getting Started on Solaris Systems
-[[Loading AFS into the Solaris Kernel|Main/LoadingAFSIntoTheSolarisKernel]]
+[[Loading AFS into the Solaris Kernel|LoadingAFSIntoTheSolarisKernel]]
## <a name="Configuring the AFS-modified fsc"></a> Configuring the AFS-modified fsck Program on Solaris Systems
Never run the standard fsck program on AFS server partitions. It discards AFS volumes.
-[[Configuring the AFS-modified fsck Program on Solaris Systems|Main/ConfiguringTheAFS-modifiedFsckProgramOnSolarisSystems]]
+[[Configuring the AFS-modified fsck Program on Solaris Systems|ConfiguringTheAFS-modifiedFsckProgramOnSolarisSystems]]
## <a name="Configuring Server Volumes On So"></a> Configuring Server Volumes On Solaris
If this system is going to be used as a file server to share some of its disk space, create a directory called /vicepxx for each AFS server partition you are configuring (there must be at least one). If it is not going to be a file server you can skip this step.
-[[Configuring Server Volumes on Solaris|Main/ConfiguringServerVolumesOnSolaris]]
+[[Configuring Server Volumes on Solaris|ConfiguringServerVolumesOnSolaris]]
-If the machine is to remain an AFS client, incorporate AFS into its authentication system, following the instructions in [[Enabling AFS Login on Solaris Systems|Main/EnablingAFSLoginOnSolarisSystems]].
+If the machine is to remain an AFS client, incorporate AFS into its authentication system, following the instructions in [[Enabling AFS Login on Solaris Systems|EnablingAFSLoginOnSolarisSystems]].
Proceed to Starting Server Programs.
\* An existing client machine in your cell
-\* The [[CellServDB]].sample file included in the sysname/root.client/usr/vice/etc directory of each AFS CD-ROM; add an entry for the local cell by following the instructions in [[Creating the Client CellServDB File|Main/CreatingTheClientCellServDBFile]]
+\* The [[CellServDB]].sample file included in the sysname/root.client/usr/vice/etc directory of each AFS CD-ROM; add an entry for the local cell by following the instructions in [[Creating the Client CellServDB File|CreatingTheClientCellServDBFile]]
-1. Create the cacheinfo file for either a disk cache or a memory cache. [[Configuring the Cache|Main/ConfiguringTheCache]]
+1. Create the cacheinfo file for either a disk cache or a memory cache. [[Configuring the Cache|ConfiguringTheCache]]
-1. Proceed to [[Configuring the CacheManager|Main/ConfiguringTheCacheManager]]
+1. Proceed to [[Configuring the CacheManager|ConfiguringTheCacheManager]]
1. If appropriate, follow the instructions in Storing AFS Binaries in AFS to copy the AFS binaries for this system type into an AFS volume. See the introduction to this section for further discussion.
## <a name="On AIX systems:"></a> On AIX systems:
-[[Initialization Script on AIX|Main/InitializationScriptOnAIX]]
+[[Initialization Script on AIX|InitializationScriptOnAIX]]
Proceed to Step 4.
## <a name="On Digital UNIX systems:"></a> On Digital UNIX systems:
-[[Initialization Script on Digital UNIX|Main/InitializationScriptOnDigitalUNIX]]
+[[Initialization Script on Digital UNIX|InitializationScriptOnDigitalUNIX]]
Proceed to Step 4.
## <a name="On HP-UX systems:"></a> On HP-UX systems:
-[[Initialization Script on HP-UX|Main/InitializationScriptOnHP-UX]]
+[[Initialization Script on HP-UX|InitializationScriptOnHP-UX]]
Proceed to Step 4.
## <a name="On IRIX systems:"></a> On IRIX systems:
-[[Initialization Script on IRIX|Main/InitializationScriptOnIRIX]]
+[[Initialization Script on IRIX|InitializationScriptOnIRIX]]
Proceed to Step 4.
## <a name="On Linux systems:"></a> On Linux systems:
-[[Initialization Script on Linux|Main/InitializationScriptOnLinux]]
+[[Initialization Script on Linux|InitializationScriptOnLinux]]
Proceed to Step 4.
## <a name="On Solaris systems:"></a> On Solaris systems:
-[[Initialization Script on Solaris|Main/InitializationScriptOnSolaris]]
+[[Initialization Script on Solaris|InitializationScriptOnSolaris]]
Step 4. Verify that /usr/afs and its subdirectories on the new file server machine meet the ownership and mode bit requirements outlined in Protecting Sensitive AFS Directories. If necessary, use the chmod command to correct the mode bits.
## <a name="Loading AFS into the AIX Kernel"></a> Loading AFS into the AIX Kernel
-[[Loading AFS into the AIX Kernel|Main/LoadingAFSIntoTheAIXKernel]]
+[[Loading AFS into the AIX Kernel|LoadingAFSIntoTheAIXKernel]]
## <a name="Replacing the fsck Program Helpe"></a> Replacing the fsck Program Helper on AIX Systems
Never run the standard fsck program on AFS server partitions. It discards AFS volumes.
-[[Replacing the fsck Program Helper on AIX Systems|Main/ReplacingTheFsckProgramHelperOnAIXSystems]]
+[[Replacing the fsck Program Helper on AIX Systems|ReplacingTheFsckProgramHelperOnAIXSystems]]
## <a name="Configuring Server Volumes on AI"></a> Configuring Server Volumes on AIX Systems
If this system is going to be used as a file server to share some of its disk space, create a directory called /vicepxx for each AFS server partition you are configuring (there must be at least one). If it is not going to be a file server you can skip this step.
-[[Configuring Server Volumes on AIX|Main/ConfiguringServerVolumesOnAIX]]
+[[Configuring Server Volumes on AIX|ConfiguringServerVolumesOnAIX]]
-If you plan to retain client functionality on this machine after completing the installation, proceed to [[Enabling AFS Login on AIX Systems|Main/EnablingAFSLoginOnAIXSystems]]. Otherwise, proceed to Starting the BOS Server.
+If you plan to retain client functionality on this machine after completing the installation, proceed to [[Enabling AFS Login on AIX Systems|EnablingAFSLoginOnAIXSystems]]. Otherwise, proceed to Starting the BOS Server.
# <a name="Getting Started on Digital UNIX"></a><a name="Getting Started on Digital UNIX "></a> Getting Started on Digital UNIX Systems
## <a name="Loading AFS into the Digital UNI"></a> Loading AFS into the Digital UNIX Kernel
-[[Building AFS into the Digital UNIX Kernel|Main/BuildingAFSIntoTheDigitalUNIXKernel]]
+[[Building AFS into the Digital UNIX Kernel|BuildingAFSIntoTheDigitalUNIXKernel]]
## <a name="Replacing the fsck Program on Di"></a> Replacing the fsck Program on Digital UNIX Systems
Never run the standard fsck program on AFS server partitions. It discards AFS volumes.
-[[Replacing the fsck Program on Digital UNIX Systems|Main/ReplacingTheFsckProgramOnDigitalUNIXSystems]]
+[[Replacing the fsck Program on Digital UNIX Systems|ReplacingTheFsckProgramOnDigitalUNIXSystems]]
## <a name="Configuring Server Volumes on Di"></a> Configuring Server Volumes on Digital UNIX Systems
If this system is going to be used as a file server to share some of its disk space, create a directory called /vicepxx for each AFS server partition you are configuring (there must be at least one). If it is not going to be a file server you can skip this step.
-[[Configuring Server Volumes on Digital UNIX|Main/ConfiguringServerVolumesOnDigitalUNIX]]
+[[Configuring Server Volumes on Digital UNIX|ConfiguringServerVolumesOnDigitalUNIX]]
-If you plan to retain client functionality on this machine after completing the installation, proceed to [[Enabling AFS Login on Digital UNIX Systems|Main/EnablingAFSLoginOnDigitalUNIXSystems]]. Otherwise, proceed to Starting the BOS Server.
+If you plan to retain client functionality on this machine after completing the installation, proceed to [[Enabling AFS Login on Digital UNIX Systems|EnablingAFSLoginOnDigitalUNIXSystems]]. Otherwise, proceed to Starting the BOS Server.
# <a name="Getting Started on HP-UX Systems"></a> Getting Started on HP-UX Systems
## <a name="Building AFS into the HP-UX Kern"></a> Building AFS into the HP-UX Kernel
-[[Building AFS into the HP-UX Kernel|Main/BuildingAFSIntoTheHP-UXKernel]]
+[[Building AFS into the HP-UX Kernel|BuildingAFSIntoTheHP-UXKernel]]
## <a name="Configuring the AFS-modified fsc"></a> Configuring the AFS-modified fsck Program on HP-UX Systems
Never run the standard fsck program on AFS server partitions. It discards AFS volumes.
-[[Configuring the AFS-modified fsck Program on HP-UX Systems|Main/ConfiguringTheAFS-modifiedFsckProgramOnHP-UXSystems]]
+[[Configuring the AFS-modified fsck Program on HP-UX Systems|ConfiguringTheAFS-modifiedFsckProgramOnHP-UXSystems]]
## <a name="Configuring Server Volumes on HP"></a> Configuring Server Volumes on HP-UX Systems
If this system is going to be used as a file server to share some of its disk space, create a directory called /vicepxx for each AFS server partition you are configuring (there must be at least one). If it is not going to be a file server you can skip this step.
-[[Configuring Server Volumes on HP-UX|Main/ConfiguringServerVolumesOnHP-UX]]
+[[Configuring Server Volumes on HP-UX|ConfiguringServerVolumesOnHP-UX]]
-If you plan to retain client functionality on this machine after completing the installation, proceed to [[Enabling AFS Login on HP-UX Systems|Main/EnablingAFSLoginOnHP-UXSystems]]. Otherwise, proceed to Starting the BOS Server.
+If you plan to retain client functionality on this machine after completing the installation, proceed to [[Enabling AFS Login on HP-UX Systems|EnablingAFSLoginOnHP-UXSystems]]. Otherwise, proceed to Starting the BOS Server.
# <a name="Getting Started on IRIX Systems"></a> Getting Started on IRIX Systems
## <a name="Loading AFS into the IRIX Kernel"></a> Loading AFS into the IRIX Kernel
-[[Loading AFS into the IRIX Kernel|Main/LoadingAFSIntoTheIRIXKernel]]
+[[Loading AFS into the IRIX Kernel|LoadingAFSIntoTheIRIXKernel]]
Proceed to Configuring Server Partitions on IRIX Systems.
If this system is going to be used as a file server to share some of its disk space, create a directory called /vicepxx for each AFS server partition you are configuring (there must be at least one). If it is not going to be a file server you can skip this step.
-[[Configuring Server Volumes on IRIX|Main/ConfiguringServerVolumesOnIRIX]]
+[[Configuring Server Volumes on IRIX|ConfiguringServerVolumesOnIRIX]]
-If you plan to retain client functionality on this machine after completing the installation, proceed to [[Enabling AFS Login on IRIX Systems|Main/EnablingAFSLoginOnIRIXSystems]]. Otherwise, proceed to Starting the BOS Server.
+If you plan to retain client functionality on this machine after completing the installation, proceed to [[Enabling AFS Login on IRIX Systems|EnablingAFSLoginOnIRIXSystems]]. Otherwise, proceed to Starting the BOS Server.
# <a name="Getting Started on Linux Systems"></a> Getting Started on Linux Systems
## <a name="Loading AFS into the Linux Kerne"></a> Loading AFS into the Linux Kernel
-[[Loading AFS into the Linux Kernel|Main/LoadingAFSIntoTheLinuxKernel]]
+[[Loading AFS into the Linux Kernel|LoadingAFSIntoTheLinuxKernel]]
## <a name="Configuring Server Volumes on Li"></a> Configuring Server Volumes on Linux Systems
If this system is going to be used as a file server to share some of its disk space, create a directory called /vicepxx for each AFS server partition you are configuring (there must be at least one). If it is not going to be a file server you can skip this step.
-[[Configuring Server Volumes On Linux|Main/ConfiguringServerVolumesOnLinux]]
+[[Configuring Server Volumes On Linux|ConfiguringServerVolumesOnLinux]]
-If you plan to retain client functionality on this machine after completing the installation, proceed to [[Enabling AFS Login on Linux Systems|Main/EnablingAFSLoginOnLinuxSystems]]. Otherwise, proceed to Starting the BOS Server.
+If you plan to retain client functionality on this machine after completing the installation, proceed to [[Enabling AFS Login on Linux Systems|EnablingAFSLoginOnLinuxSystems]]. Otherwise, proceed to Starting the BOS Server.
# <a name="Getting Started on Solaris Syste"></a> Getting Started on Solaris Systems
## <a name="Loading AFS into the Solaris Ker"></a> Loading AFS into the Solaris Kernel
-[[Loading AFS into the Solaris Kernel|Main/LoadingAFSIntoTheSolarisKernel]]
+[[Loading AFS into the Solaris Kernel|LoadingAFSIntoTheSolarisKernel]]
## <a name="Configuring the AFS-modified fsc"></a> Configuring the AFS-modified fsck Program on Solaris Systems
Never run the standard fsck program on AFS server partitions. It discards AFS volumes.
-[[Configuring the AFS-modified fsck Program on Solaris Systems|Main/ConfiguringTheAFS-modifiedFsckProgramOnSolarisSystems]]
+[[Configuring the AFS-modified fsck Program on Solaris Systems|ConfiguringTheAFS-modifiedFsckProgramOnSolarisSystems]]
## <a name="Configuring Server Partitions on"></a> Configuring Server Partitions on Solaris Systems
If this system is going to be used as a file server to share some of its disk space, create a directory called /vicepxx for each AFS server partition you are configuring (there must be at least one). If it is not going to be a file server you can skip this step.
-[[Configuring Server Volumes On Solaris|Main/ConfiguringServerVolumesOnSolaris]]
+[[Configuring Server Volumes On Solaris|ConfiguringServerVolumesOnSolaris]]
If you plan to retain client functionality on this machine after completing the installation, proceed to Enabling AFS Login on Solaris Systems. Otherwise, proceed to Starting the BOS Server.
Note: If you plan to remove client functionality from this machine after completing the installation, skip this section and proceed to Starting the BOS Server.
-[[Enabling AFS Login on Solaris Systems|Main/EnablingAFSLoginOnSolarisSystems]]
+[[Enabling AFS Login on Solaris Systems|EnablingAFSLoginOnSolarisSystems]]
Proceed to Starting the BOS Server (or if referring to these instructions while installing an additional file server machine, return to Starting Server Programs).
## <a name="Creating the Client _CellServDB"></a><a name="Creating the Client _CellServDB "></a> Creating the Client [[CellServDB]] File
-[[Creating the Client CellServDB File|Main/CreatingTheClientCellServDBFile]]
+[[Creating the Client CellServDB File|CreatingTheClientCellServDBFile]]
## <a name="Configuring the Cache"></a> Configuring the Cache
-[[Configuring the Cache|Main/ConfiguringTheCache]]
+[[Configuring the Cache|ConfiguringTheCache]]
## <a name="Configuring the Cache Manager"></a> Configuring the Cache Manager
-[[Configuring the Cache Manager|Main/ConfiguringTheCacheManager]]
+[[Configuring the Cache Manager|ConfiguringTheCacheManager]]
# <a name="Overview: Completing the Install"></a> Overview: Completing the Installation of the First AFS Machine
## <a name="On AIX systems:"></a> On AIX systems:
-[[Initialization Script on AIX|Main/InitializationScriptOnAIX]]
+[[Initialization Script on AIX|InitializationScriptOnAIX]]
Proceed to Step 4.
## <a name="On Digital UNIX systems:"></a> On Digital UNIX systems:
-[[Initialization Script on Digital UNIX|Main/InitializationScriptOnDigitalUNIX]]
+[[Initialization Script on Digital UNIX|InitializationScriptOnDigitalUNIX]]
Proceed to Step 4.
## <a name="On HP-UX systems:"></a> On HP-UX systems:
-[[Initialization Script on HP-UX|Main/InitializationScriptOnHP-UX]]
+[[Initialization Script on HP-UX|InitializationScriptOnHP-UX]]
Proceed to Step 4.
## <a name="On IRIX systems:"></a> On IRIX systems:
-[[Initialization Script on IRIX|Main/InitializationScriptOnIRIX]]
+[[Initialization Script on IRIX|InitializationScriptOnIRIX]]
Proceed to Step 4.
## <a name="On Linux systems:"></a> On Linux systems:
-[[Initialization Script on Linux|Main/InitializationScriptOnLinux]]
+[[Initialization Script on Linux|InitializationScriptOnLinux]]
Proceed to Step 4.
## <a name="On Solaris systems:"></a> On Solaris systems:
-[[Initialization Script on Solaris|Main/InitializationScriptOnSolaris]]
+[[Initialization Script on Solaris|InitializationScriptOnSolaris]]
Step 4. Verify that /usr/afs and its subdirectories on the new file server machine meet the ownership and mode bit requirements outlined in Protecting Sensitive AFS Directories. If necessary, use the chmod command to correct the mode bits.
/usr/heimdal/klist
# you should see you have afs/greekmythology.com ticket having some expiration time etc.
-Proceed to the [Starting File Server](http://www.openafs.org/pages/doc/QuickStartUnix/auqbg005.htm#HDRWQ60) section of the [[OpenAFS]] documentation. The rest of the documentation can be completed without any changes. (What about replacing NTP with something recent, though...? See FAQ [[3.22|Main/AdminFAQ#NTP]] and [[[NTP|Main/FurtherReading#NTP]]])
+Proceed to the [Starting File Server](http://www.openafs.org/pages/doc/QuickStartUnix/auqbg005.htm#HDRWQ60) section of the [[OpenAFS]] documentation. The rest of the documentation can be completed without any changes. (What about replacing NTP with something recent, though...? See FAQ [[3.22|AdminFAQ#NTP]] and [[[NTP|FurtherReading#NTP]]])
## <a name="Setting up Transparent Login"></a> Setting up Transparent Login
- [[FreeBSDPort]] -- Server ported. Cache manager available, not stable yet.
-- [[HPUX11Port|Main/HP-UX11Port]] -- Missing RX code reconstructed. Header needed, available from HP. Available in 1.2.10.
+- [[HPUX11Port|HP-UX11Port]] -- Missing RX code reconstructed. Header needed, available from HP. Available in 1.2.10.
- [[NetBSDPort]] -- No timeline available.
This is a place holder for notes on the redesign of the openafs.org website.
-In particular, the new site must be designed to be accessible to various groups of users who have very different needs. Here is a [[site outline|Main/NewSiteOutline]] which should follow these requirements:
+In particular, the new site must be designed to be accessible to various groups of users who have very different needs. Here is a [[site outline|NewSiteOutline]] which should follow these requirements:
1. [[OpenAFS]] administrators
1. easy access to the "best" binaries (and perhaps source) for their server and client platforms
> I was wondering how Solaris x86 would be doing as AFS fileserver compared to Red Hat 7.3 Linux on the same hardware.
>
-> I've conducted some benchmarks using [[PostMark|Main/PerformanceWork#PostMark]] and arla's afsfsperf to get an answer (not _the_ answer!) to this question.
+> I've conducted some benchmarks using [[PostMark|PerformanceWork#PostMark]] and arla's afsfsperf to get an answer (not _the_ answer!) to this question.
>
> I've used [[OpenAFS]]-1.2.8 with inode and namei interface on Solaris with non-logging and logging file system for the /vicepa partition.
>
- Answers to some often asked questions
- Pointers to further information
-Definitive and detailed information on AFS is provided in Transarc's AFS manuals ([[[UserGuide|Main/FurtherReading#UserGuide]]], [[[CommandsRef|Main/FurtherReading#CommandsRef]]], [[[AdminGuide|Main/FurtherReading#AdminGuide]]]).
+Definitive and detailed information on AFS is provided in Transarc's AFS manuals ([[[UserGuide|FurtherReading#UserGuide]]], [[[CommandsRef|FurtherReading#CommandsRef]]], [[[AdminGuide|FurtherReading#AdminGuide]]]).
The intended audience ranges from people who know little of the subject and want to know more to those who have experience with AFS and wish to share useful information by contributing to the faq.
-Some [words](https://lists.openafs.org/pipermail/openafs-info/2002-February/003281.html) from [[RussAllbery]] on [[process authentication groups|Main/ProcessAuthenticationGroup]] ([[PAG]]s) with edits:
+Some [words](https://lists.openafs.org/pipermail/openafs-info/2002-February/003281.html) from [[RussAllbery]] on [[process authentication groups|ProcessAuthenticationGroup]] ([[PAG]]s) with edits:
A PAG holds the authentication information (i.e. tokens or basically AFS service tickets) needed by the [[CacheManager]] to identify you to AFS servers and visa versa (i.e. Kerberos provides [[MutualAuthentication]]). Each PAG is represented by a number, typically encoded as a pair of "funny" groups in your group list. Thus, because it is part of your credentials, it is naturally (on Unix systems at least) and automatically propagated to child processes. These children will have access to your tokens even if they have a diffenent UID (e.g. set uid root programs like lpr can still access your files).
For user logins, though, you generally want to be sure that something puts each login into a separate PAG.
-Use `klog -setpag` to create a (new) PAG after logging in. In a [[KerberosV]] environment, use `aklog -setpag`. There's also [[pagsh|Main/UsageFAQ#2_06_What_is_pagsh_]].
+Use `klog -setpag` to create a (new) PAG after logging in. In a [[KerberosV]] environment, use `aklog -setpag`. There's also [[pagsh|UsageFAQ#2_06_What_is_pagsh_]].
-- [[TedAnderson]] - 07 Feb 2002
<td> no </td>
<td> yes </td>
<td> yes </td>
- <td>[[PowerPC]] - [[Main/DarwinPort]] 1.2 - [[Main/MacOSX]]</td>
+ <td>[[PowerPC]] - [[DarwinPort]] 1.2 - [[MacOSX]]</td>
</tr>
<tr>
<td> ppc_darwin_13 </td>
<td> no </td>
<td> yes </td>
<td> yes </td>
- <td>[[PowerPC]] - [[Main/DarwinPort]] 1.3 - [[Main/MacOSX]]</td>
+ <td>[[PowerPC]] - [[DarwinPort]] 1.3 - [[MacOSX]]</td>
</tr>
<tr>
<td> ppc_linux22 </td>
- **%INCLUDINGWEB% Web**
-- [[%INCLUDINGWEB% Web Home|Main/WebHome]]
-- [[Changes|Main/WebChanges]]
-- [[Index|Main/WebIndex]]
-- [[Search|Main/WebSearch]]
+- [[%INCLUDINGWEB% Web Home|WebHome]]
+- [[Changes|WebChanges]]
+- [[Index|WebIndex]]
+- [[Search|WebSearch]]
----
**_Preferences:_**
- List of topics of the %WIKITOOLNAME%.%WEB% web:
- - Set WEBTOPICLIST = [[Home|Main/WebHome]] | [[Changes|Main/WebChanges]] | [[Index|Main/WebIndex]] | [[Search|Main/WebSearch]] | Go <input name="topic" size="16" type="text" />
+ - Set WEBTOPICLIST = [[Home|WebHome]] | [[Changes|WebChanges]] | [[Index|WebIndex]] | [[Search|WebSearch]] | Go <input name="topic" size="16" type="text" />
- Web specific background color: (Pick a lighter one of the [[StandardColors]])
- Set WEBBGCOLOR = #99CCFF
### <a name="Freelance Client Support"></a> Freelance Client Support
-This option can be set during installation. After installation, a registry entry must be edited. It can be found in `HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\Parameters` and is called `FreelanceClient` (type DWORD). Set it to 1 to enable Freelance Mode. See the [[Troubleshooting Guide|Main/WindowsTroubleshootingGuide#What_is_Freelance_Mode_]] for more information on Freelance Mode. Default is zero (disabled).
+This option can be set during installation. After installation, a registry entry must be edited. It can be found in `HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TransarcAFSDaemon\Parameters` and is called `FreelanceClient` (type DWORD). Set it to 1 to enable Freelance Mode. See the [[Troubleshooting Guide|WindowsTroubleshootingGuide#What_is_Freelance_Mode_]] for more information on Freelance Mode. Default is zero (disabled).
#### <a name="Freelance Root Setup"></a> Freelance Root Setup
As with most things on the computer, this error message is not entirely correct. It is not neccessarily the version number of the key that is wrong. Two of the most common reasons are
- Wrong cell. You may have obtained tokens for one cell and are now trying to reach another cell. Try doing `afslog` for the new cell if you know you should have access to it.
-- Old server. Support for [[KerberosV]] tickets is a relatively new feature of [[OpenAFS]]. You will need an [[OpenAFS]] 1.2.8 or later server to use the feature. Either update the server, or disable [[KerberosV]]. Read about the latter in the [[Configuration Reference Guide|Main/WindowsConfigurationReferenceGuide#Disable_Automatic_Use_of_KerberosV]].
+- Old server. Support for [[KerberosV]] tickets is a relatively new feature of [[OpenAFS]]. You will need an [[OpenAFS]] 1.2.8 or later server to use the feature. Either update the server, or disable [[KerberosV]]. Read about the latter in the [[Configuration Reference Guide|WindowsConfigurationReferenceGuide#Disable_Automatic_Use_of_KerberosV]].
### <a name="Why can't I use _OpenAFS with an"></a> Why can't I use [[OpenAFS]] with an Active Directory KDC?
If you have a laptop, or will otherwise be without a connection to the servers of your default cell, you should have this enabled. If your computer can always communicate with the servers of the default cell, this mode is superfluous.
-To switch Freelance Mode on and off, please read the [[Configuration Reference|Main/WindowsConfigurationReferenceGuide#Freelance_Client_Support]].
+To switch Freelance Mode on and off, please read the [[Configuration Reference|WindowsConfigurationReferenceGuide#Freelance_Client_Support]].
### <a name="What is "High Security Mode"?"></a> What is "High Security Mode"?
git://git.openafs.org / openafs-wiki.git / commitdiff