From b6b01fe28b3a14d9923c94297b019c6cddd5a7d0 Mon Sep 17 00:00:00 2001 From: "https://www.google.com/accounts/o8/id?id=AItOawk_GD3B2YRV5t7ZM5GOh2nD2jfC6Rihqvg" Date: Sat, 12 Mar 2011 16:31:26 -0800 Subject: [PATCH 1/1] --- AFSLore/HowToBuildOpenAFSFromSource.mdwn | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/AFSLore/HowToBuildOpenAFSFromSource.mdwn b/AFSLore/HowToBuildOpenAFSFromSource.mdwn index 539c393..a213350 100644 --- a/AFSLore/HowToBuildOpenAFSFromSource.mdwn +++ b/AFSLore/HowToBuildOpenAFSFromSource.mdwn @@ -27,11 +27,11 @@ See the end of this page for instructions on how to build RPM packages. ## The Longer Story -Building and packaging OpenAFS is not difficult on most modern unix-like +Building and packaging OpenAFS is not difficult on current unix-like systems. A small number of fairly common libraries and tools are required. The kernel headers and a compiler capable of building a kernel module is needed to -build the OpenAFS kernel module needed for the AFS client (and for legacy so -called inode fileservers.) The gnu autoconf and automake tools are used to +build the OpenAFS kernel module (used by the cache manager and for +inode-backend fileservers.) The gnu autoconf and automake tools are used to configure the build system, so should be familiar to most people accustomed to building binaries on unix-like systems. -- 1.9.4