1 OpenAFS News -- history of user-visible changes. October 19, 2001
3 * Changes incorporated in OpenAFS 1.3
5 ** Mountpoint directory information can be faked by the cache manager,
6 making operations such as stat'ing all cells under /afs much faster.
7 This is enabled by passing -fakestat to afsd, but might not be stable
10 * Changes incorporated in OpenAFS 1.2.4
12 ** Server logfiles now more consistant about format in which hosts are
15 ** vfsck on Solaris will now allow force runs (using -y flag) even if old
18 * Changes incorporated in OpenAFS 1.2.3
20 ** Cell aliases for dynroot can be specified in the CellAlias file in
21 /usr/vice/etc or /usr/local/etc/openafs, in format "realname alias",
22 one per line. They can also be managed at runtime with "fs newalias"
25 * Changes incorporated in OpenAFS 1.2.2
27 ** Solaris 9 and Linux PA-RISC are now supported
29 ** fileserver will not erroneously delay legitimate errors for 3 seconds
30 after 10 errors are returned (e.g. stat() on a directory you can't read)
32 ** Rx MTU calculation now works for Irix, Solaris and Linux
34 ** If afsd is started with the -dynroot flag, /afs will be locally
35 generated from the CellServDB. AFSDB cells will be mounted
36 automatically upon access.
38 ** The namei fileserver allows vice "partitions" to be directories instead
39 of partitions and will attach and display accordingly. Creating the file
40 "AlwaysAttach" in the /vicepX directory is used as the trigger to attach it.
42 ** TSM support for butc no longer requires editing a Makefile, simply
43 specify the --enable-tivoli-tsm configure option.
45 ** Linux builds no longer require source changes every time the kernel
46 inode structure changes; the OpenAFS sources will now configure
47 itself to the actual inode structure as defined in the kernel
50 * Changes incorporated in OpenAFS 1.2.1
52 ** vfsck on Digital UNIX and Solaris will now refuse to fsck mounted
55 * Changes incorporated in OpenAFS 1.2.0
57 ** AFS now supports --prefix and the other directory options of
58 configure. By default AFS builds assuming it will be installed in
59 /usr/local. In order to get traditional AFS directory paths (/usr/afs
60 and /usr/vice/etc) use the --enable-transarc-paths option to
61 configure. More details on the new directory layout are found in README.
63 * Changes incorporated in OpenAFS 1.1.1a
65 ** Windows 95/98/ME/NT/2000 - Consistent versioning
66 Installation, AFS Control Center, Client dialog boxes and properties
67 pages for executables display a consistent OpenAFS version number.
68 Installation detects previous installation and prompts the user for upgrade
71 ** Windows 95/98/ME/NT/2000 - Installation features
72 During installation the user can select the source of the CellservDB file,
73 AFS home cell, and drive mappings. During installation a drive path
74 mapping can include a variable that will be substituted with the current
75 UserName that is logged in.
77 ** Windows 2000/NT - Integrated logon
78 The Integrated Logon feature works now.
80 ** Windows 95/98/ME - Logon script features
81 The Windows 95/98/ME client now offers a command-line option for starting up
82 the AFS client without authenication. It is now possilbe to start the AFS
83 client first and obtain tokens, and map drives all through Windows scripts.
84 This helps using Windows 95/98/ME client in Kerberos 5 environment.
86 ** Windows 2000/NT - LANA numbers
87 AFS client now scans the LANA numbers to establish the correct NETBIOS
88 connection. NetBEUI is no longer needed. The user no longer needs to find
89 the correct LANA number.
91 ** Windows 2000/NT - OpenAFS naming consistancy
92 Further progress has been made to remove references to "Transarc AFS"
93 and replace with "OpenAFS".
97 * Changes since OpenAFS 1.0
99 ** AFS now builds with configure. The README for building has been
100 updated and includes full details.
102 ** A client system can now have multiple sysname values for @sys.
103 They will be searched in order when looking up files in AFS. The
104 -newsysname argument to fs sysname can be repeated to set multiple
107 ** A new system group is created for new cells (system:ptsviewers
108 with id -203). If this group exists, members of this group can
109 examine and read the entire protection database. They can examine
110 all users and groups and can get the membership of any group.
112 ** A new program, pt_util has been added to the distribution. This
113 program allows users to print the contents of the protection
114 database or to edit the protection database without running a
115 ptserver. It can be used to set up a new cell without ever running
116 in noauth mode. Run pt_util -h for help.
118 ** The fs setcrypt and fs getcrypt commands have been added. These
119 commands allow the system administrator to require that the client
120 encrypt all authenticated traffic between the client workstation
121 and AFS. The encryption used is weak, but is likely better than
122 sending unencrypted traffic in most environments. Some functions,
123 such as looking for a volume may not be encrypted, but data
124 transfer certainly is. By default data is not encrypted. At this
125 time no significant experimentation with server performance has
128 ** By default AFS is compiled with AFS_AFSDB_ENV, enabling the -afsdb
129 option to be given to afsd on startup. If this option is used, then new
130 cells will be looked up using AFSDB records stored in DNS if they
131 are not found in CellServDB. This means that users can create
132 cross-cell mountpoints in directories they control to access cells
133 not in root.afs, and that cells in root.afs need not be in the
136 ** AFS database servers can be marked as read-only clones. Surround
137 the hostname in square brackets on the bos addhost command and the
138 database server will never be elected sync site. This is useful
139 for cells distributed over a wide region.
141 ** The AFS servers now support the -syslog flag. This flag causes
142 them to log to syslog rather than to files. This flag is not
143 supported on NT. For all servers besides the salvager, the flag can
144 also be specified as -syslog=facility, where facility is an integer
145 facility code from syslog.h. A -syslogfacility option is provided for
146 the salvager to accomplish the same goal.
148 ** If the --enable-fast-restart flag is given when configuring AFS,
149 then the salvager supports the -dontsalvage flag which causes it to
150 exit without salvaging any volumes. If this is configured into the
151 third command of a fs process, then the fileserver will start without
152 salvaging. It will fail to attach volumes that need salvaging and they
153 can be salvaged manually. This provides significantly better server
154 startup performance at the cost of administrative complexity.
156 ** If the --enable-bitmap-later flag is given when configuring AFS,
157 then the fileserver creates bitmaps for free vnodes on demand, allowing
160 ** If bosserver finds a BosConfig.new file at startup, it reads this
161 file and renames it to BosConfig. This allows bosserver to be
162 reconfigured at next restart.
164 ** The bosserver can be placed in a restricted mode in
165 which AFS superusers are only granted limited access to the server
166 host. The following functionality is disabled when restricted mode is in
170 bos getlog (except for files with no '/'s in their name)*
176 specific exceptions are made for functionality that "bos salvage"
179 a cron bnode who's name is "salvage-tmp", time is now, and command
180 begins with "/usr/afs/bin/salvager" may be created. This bnode
181 deletes itself when complete, so no special "delete" support is needed.
182 This functionality may be removed in the future if a "Salvage" RPC is
185 The file with the exact path /usr/afs/logs/SalvageLog may be fetched,
186 since that is how bos salvage [...] -showlog is implimented.
188 Restricted mode is enabled using a new bos command (bos setrestricted)
189 or bossever command line switch (bosserver -restricted). Restricted
190 mode can be disabled by a) sending the bosserver process a SIGFPE (which
191 will then allow restricted operations until the next restart or
192 setrestricted command) or b) editing /usr/afs/local/BosConfig
193 (or BosConfig.new), and restarting the bosserver.
195 ** The bos UserList of trusted administrators can now contain
196 cross-realm Kerberos principals.
198 ** udebug now takes --server not --servers.
200 ** Several error messages have been improved to include volume
203 ** Several new ports have been included for UNIX platforms: Darwin
204 (ppc_darwin_12 and ppc_darwin_13), Linux 2.4 (i386_linux24), Linux on
205 the Powerpc (ppc_linux22 and ppc_linux24), Linux on the Sparc
206 (sparc_linux22, sparc64_linux22 and sparc64_linux24) .
208 ** Incomplete FreeBSD and Alpha Linux ports are included. The
209 FreeBSD port has a working server and the Alpha Linux port has a
210 partially working client.
212 ** A native client for Windows 95/98/ME has been added to the distribution.
213 With this program, a gateway machine is no longer required for Windows 9x
214 to access AFS files. One drive letter will be created on your machine by
215 default - Z:. The Z: drive will be the root of the AFS tree, allowing you
216 to browse all sites that have AFS servers available. Additional drive
217 letters can be defined for other AFS directories. A Windows Explorer
218 shell extension is included that allows you to right click on items
219 within an AFS tree to bring up an "AFS" menu item and perform various
220 operations on a file or directory. The most useful item is "Access
221 Control Lists", which allows you to view and edit the permissions of a
222 particular directory. Command line tools are also available in the
223 install directory. These commands include klog, unlog, tokens, kpasswd,
224 symlink, fs and pts. The installable includes a readme file that contains
225 more information on how to use the client program and known issues.
227 ** support for large caches in afsd. Cachefiles are stored in
228 subdirectories. The default is 2048 files per subdirectory, which
229 should work fine in most situations. You can use the new afsd
230 option -files_per_subdir to change this number. Note that the first
231 time you run afsd with this patch, your cachefiles will get moved
232 into subdirectories. If you subsequently run an older version of
233 afsd, you will lose all your cached files.