1 -- [[StevenJenkins]] - 08 Jun 2007
3 This is an entry point into the code architecture. As always, the source for your release is the authoritative reference, but this wiki is designed to help navigate the source and point out relevant documentation.
7 - <http://www.openafs.org/cgi-bin/cvsweb.cgi/openafs/doc/pdf/> Early architectural documents. Out of date, but still important. You should especially read the Architectural Overview document (archov-doc.pdf)
8 - To understand the source layout, consult src/SOURCE-MAP -- this is a good place to go after reading the Architectural Overview
9 - Need to document the build environment issues -- README, README.DEVEL, README.CVS
10 - src/BUILDNOTES (at least in the 1.4 tree) is not very helpful
14 - Getting the source, preferably via CVS
16 README.CVS has the following line:
18 Do not use the CVS tree unless you know what you're doing.
20 This document helps you learn what you're doing.
22 - cvs co, regen.sh (& when to run regen.sh)
26 In the source itself ---
28 - **find | grep** is very helpful. For example, to find all the RX packages (ie, so that you can start to identify the various namespaces of components), you can do:
30 find . -name \*.xg -exec grep -H "^package" {} \; | grep -v 'example' | grep -v 'bulktest' | \
31 sed -e 's|^./src/||' | sed -e 's/package/ /' | awk '{printf "%10s %s\n", $2, $1}'
35 VOTE_ ubik/ubik_int.xg:
36 DISK_ ubik/ubik_int.xg:
37 SAMPLE_ ubik/utst_int.xg:
38 VL_ vlserver/vldbint.xg:
39 UPDATE_ update/update.xg:
41 RXGK_ rxgk/rxgk_proto.xg:
42 RXAFSCB_ fsint/afscbint.xg:
43 RXAFS_ fsint/afsint.xg:
44 RXSTATS_ rxstat/rxstat.xg:
45 PR_ ptserver/ptint.xg:
47 BUMON_ bubasics/backmon.xg:
49 BC_ bubasics/bumon.xg:
51 RMTSYS_ sys/rmtsys.xg:
52 AFSVol volser/volint.xg:
54 In other words, if something starts with BOZO\_, you know that it is generated by rxgen, and the interface is defined in `bozo/bosint.xg`.
56 In addition to the package name, also note that only rxstat uses an M prefix; all others use S.
58 - cscope: a source code browser, linked to your editor. Setup is simple: cd to your source tree and run:
66 to start. The interface is simple. I tend to use it for finding things, but not necessarily for editing. When I'm studying the source, trying to understand how components link together, or bug-hunting, I tend to live inside `cscope`.
68 - doxygen: what it is, how to set up, how to use, how to make even more useful (ie, src code changes)
70 - gdb: examples of using (primarily b, bt)