1 OpenAFS News -- history of user-visible changes. April 10, 2003.
3 * Changes incorporated in OpenAFS 1.3
5 ** Mountpoint directory information is now only faked for cross-cell
6 mountpoits when using the -fakestat flag (e.g. for the directories
7 under /afs, but not for most other volumes mounted inside the cell).
8 The -fakestat-all switch can be used to fake information for all
11 ** When fakestat is enabled on MacOSX, the Finder can be used to browse
12 a fully-populated /afs directory. However, this precludes reliable
13 use of entire volumes as MacOS bundles (i.e. containing a Contents
14 directory in the root of the volume).
16 ** Mountpoint directory information can be faked by the cache manager,
17 making operations such as stat'ing all cells under /afs much faster.
18 This is enabled by passing -fakestat to afsd, but might not be stable
21 * Changes incorporated in OpenAFS 1.2.9
23 ** The kaserver now defaults to not allowing interrealm authentication,
24 due to security vulnerabilities in the krb4 protocol. The new
25 "-crossrealm" flag to the kaserver is provided to reenable interrealm
26 authentication if desired.
28 ** RedHat Linux 9.0 is now supported.
30 ** Solaris 9 12/02 is now supported. Solaris 7 and 8 x86 should now
33 ** On Linux machines using 2.2 series kernels, 2.2.19 or higher is now
36 ** An OpenAFS 1.2.9 afsd will not work with kernel modules built from
37 an earlier OpenAFS release. In general, using a mismatched afsd and
38 kernel modules set is unsupported; it is not recommended that you use
39 such a configuration on a regular basis.
41 * Changes incorporated in OpenAFS 1.2.8
43 ** Mountpoint directory information is now only faked for cross-cell
44 mountpoits when using the -fakestat flag (e.g. for the directories
45 under /afs, but not for most other volumes mounted inside the cell).
46 The -fakestat-all switch can be used to fake information for all
49 ** HPUX 11.0 is now supported.
51 ** It is now possible for AFS to use Kerberos 5 directly, via rxkad 2b.
52 See the OpenAFS 1.2.8 Release Notes for more information on using this
55 ** An NFS translator kernel module is now included and compiled by default
58 * Changes incorporated in OpenAFS 1.2.7
60 ** MacOS X 10.2 is now supported. FreeBSD 4.3 and later support is included
61 in this release, but is still under active development and should only
62 be used by those doing active development on the OpenAFS FreeBSD client.
64 ** When fakestat is enabled on MacOSX, the Finder can be used to browse
65 a fully-populated /afs directory. However, this precludes reliable
66 use of entire volumes as MacOS bundles (i.e. containing a Contents
67 directory in the root of the volume).
69 ** The fileserver will now use Rx pings to determine if clients are reachable
70 prior to allocating resources to them, to prevent asymmetric clients from
71 consuming all fileserver resources.
73 * Changes incorporated in OpenAFS 1.2.6
75 ** Mountpoint directory information can be faked by the cache manager,
76 making operations such as stat'ing all cells under /afs much faster.
77 This is enabled by passing -fakestat to afsd.
79 ** Solaris 9 FCS and Solaris 7 and 8 x86 are now supported.
81 * Changes incorporated in OpenAFS 1.2.5
83 ** A remote denial of service attack in the AIX and IRIX clients has
84 been fixed. Users of those platforms are strongly encouraged to
87 ** Fixed race conditions in fileserver that could result in crash.
89 * Changes incorporated in OpenAFS 1.2.4
91 ** Server logfiles now more consistant about format in which hosts are
94 ** vfsck on Solaris will now allow force runs (using -y flag) even if old
97 * Changes incorporated in OpenAFS 1.2.3
99 ** Cell aliases for dynroot can be specified in the CellAlias file in
100 /usr/vice/etc or /usr/local/etc/openafs, in format "realname alias",
101 one per line. They can also be managed at runtime with "fs newalias"
102 and "fs listaliases".
104 * Changes incorporated in OpenAFS 1.2.2
106 ** Solaris 9 and Linux PA-RISC are now supported
108 ** fileserver will not erroneously delay legitimate errors for 3 seconds
109 after 10 errors are returned (e.g. stat() on a directory you can't read)
111 ** Rx MTU calculation now works for Irix, Solaris and Linux
113 ** If afsd is started with the -dynroot flag, /afs will be locally
114 generated from the CellServDB. AFSDB cells will be mounted
115 automatically upon access.
117 ** The namei fileserver allows vice "partitions" to be directories instead
118 of partitions and will attach and display accordingly. Creating the file
119 "AlwaysAttach" in the /vicepX directory is used as the trigger to attach it.
121 ** TSM support for butc no longer requires editing a Makefile, simply
122 specify the --enable-tivoli-tsm configure option.
124 ** Linux builds no longer require source changes every time the kernel
125 inode structure changes; the OpenAFS sources will now configure
126 itself to the actual inode structure as defined in the kernel
129 * Changes incorporated in OpenAFS 1.2.1
131 ** vfsck on Digital UNIX and Solaris will now refuse to fsck mounted
134 * Changes incorporated in OpenAFS 1.2.0
136 ** AFS now supports --prefix and the other directory options of
137 configure. By default AFS builds assuming it will be installed in
138 /usr/local. In order to get traditional AFS directory paths (/usr/afs
139 and /usr/vice/etc) use the --enable-transarc-paths option to
140 configure. More details on the new directory layout are found in README.
142 * Changes incorporated in OpenAFS 1.1.1a
144 ** Windows 95/98/ME/NT/2000 - Consistent versioning
145 Installation, AFS Control Center, Client dialog boxes and properties
146 pages for executables display a consistent OpenAFS version number.
147 Installation detects previous installation and prompts the user for upgrade
150 ** Windows 95/98/ME/NT/2000 - Installation features
151 During installation the user can select the source of the CellservDB file,
152 AFS home cell, and drive mappings. During installation a drive path
153 mapping can include a variable that will be substituted with the current
154 UserName that is logged in.
156 ** Windows 2000/NT - Integrated logon
157 The Integrated Logon feature works now.
159 ** Windows 95/98/ME - Logon script features
160 The Windows 95/98/ME client now offers a command-line option for starting up
161 the AFS client without authenication. It is now possilbe to start the AFS
162 client first and obtain tokens, and map drives all through Windows scripts.
163 This helps using Windows 95/98/ME client in Kerberos 5 environment.
165 ** Windows 2000/NT - LANA numbers
166 AFS client now scans the LANA numbers to establish the correct NETBIOS
167 connection. NetBEUI is no longer needed. The user no longer needs to find
168 the correct LANA number.
170 ** Windows 2000/NT - OpenAFS naming consistancy
171 Further progress has been made to remove references to "Transarc AFS"
172 and replace with "OpenAFS".
176 * Changes since OpenAFS 1.0
178 ** AFS now builds with configure. The README for building has been
179 updated and includes full details.
181 ** A client system can now have multiple sysname values for @sys.
182 They will be searched in order when looking up files in AFS. The
183 -newsysname argument to fs sysname can be repeated to set multiple
186 ** A new system group is created for new cells (system:ptsviewers
187 with id -203). If this group exists, members of this group can
188 examine and read the entire protection database. They can examine
189 all users and groups and can get the membership of any group.
191 ** A new program, pt_util has been added to the distribution. This
192 program allows users to print the contents of the protection
193 database or to edit the protection database without running a
194 ptserver. It can be used to set up a new cell without ever running
195 in noauth mode. Run pt_util -h for help.
197 ** The fs setcrypt and fs getcrypt commands have been added. These
198 commands allow the system administrator to require that the client
199 encrypt all authenticated traffic between the client workstation
200 and AFS. The encryption used is weak, but is likely better than
201 sending unencrypted traffic in most environments. Some functions,
202 such as looking for a volume may not be encrypted, but data
203 transfer certainly is. By default data is not encrypted. At this
204 time no significant experimentation with server performance has
207 ** By default AFS is compiled with AFS_AFSDB_ENV, enabling the -afsdb
208 option to be given to afsd on startup. If this option is used, then new
209 cells will be looked up using AFSDB records stored in DNS if they
210 are not found in CellServDB. This means that users can create
211 cross-cell mountpoints in directories they control to access cells
212 not in root.afs, and that cells in root.afs need not be in the
215 ** AFS database servers can be marked as read-only clones. Surround
216 the hostname in square brackets on the bos addhost command and the
217 database server will never be elected sync site. This is useful
218 for cells distributed over a wide region.
220 ** The AFS servers now support the -syslog flag. This flag causes
221 them to log to syslog rather than to files. This flag is not
222 supported on NT. For all servers besides the salvager, the flag can
223 also be specified as -syslog=facility, where facility is an integer
224 facility code from syslog.h. A -syslogfacility option is provided for
225 the salvager to accomplish the same goal.
227 ** If the --enable-fast-restart flag is given when configuring AFS,
228 then the salvager supports the -dontsalvage flag which causes it to
229 exit without salvaging any volumes. If this is configured into the
230 third command of a fs process, then the fileserver will start without
231 salvaging. It will fail to attach volumes that need salvaging and they
232 can be salvaged manually. This provides significantly better server
233 startup performance at the cost of administrative complexity.
235 ** If the --enable-bitmap-later flag is given when configuring AFS,
236 then the fileserver creates bitmaps for free vnodes on demand, allowing
239 ** If bosserver finds a BosConfig.new file at startup, it reads this
240 file and renames it to BosConfig. This allows bosserver to be
241 reconfigured at next restart.
243 ** The bosserver can be placed in a restricted mode in
244 which AFS superusers are only granted limited access to the server
245 host. The following functionality is disabled when restricted mode is in
249 bos getlog (except for files with no '/'s in their name)*
255 specific exceptions are made for functionality that "bos salvage"
258 a cron bnode who's name is "salvage-tmp", time is now, and command
259 begins with "/usr/afs/bin/salvager" may be created. This bnode
260 deletes itself when complete, so no special "delete" support is needed.
261 This functionality may be removed in the future if a "Salvage" RPC is
264 The file with the exact path /usr/afs/logs/SalvageLog may be fetched,
265 since that is how bos salvage [...] -showlog is implimented.
267 Restricted mode is enabled using a new bos command (bos setrestricted)
268 or bossever command line switch (bosserver -restricted). Restricted
269 mode can be disabled by a) sending the bosserver process a SIGFPE (which
270 will then allow restricted operations until the next restart or
271 setrestricted command) or b) editing /usr/afs/local/BosConfig
272 (or BosConfig.new), and restarting the bosserver.
274 ** The bos UserList of trusted administrators can now contain
275 cross-realm Kerberos principals.
277 ** udebug now takes --server not --servers.
279 ** Several error messages have been improved to include volume
282 ** Several new ports have been included for UNIX platforms: Darwin
283 (ppc_darwin_12 and ppc_darwin_13), Linux 2.4 (i386_linux24), Linux on
284 the Powerpc (ppc_linux22 and ppc_linux24), Linux on the Sparc
285 (sparc_linux22, sparc64_linux22 and sparc64_linux24) .
287 ** Incomplete FreeBSD and Alpha Linux ports are included. The
288 FreeBSD port has a working server and the Alpha Linux port has a
289 partially working client.
291 ** A native client for Windows 95/98/ME has been added to the distribution.
292 With this program, a gateway machine is no longer required for Windows 9x
293 to access AFS files. One drive letter will be created on your machine by
294 default - Z:. The Z: drive will be the root of the AFS tree, allowing you
295 to browse all sites that have AFS servers available. Additional drive
296 letters can be defined for other AFS directories. A Windows Explorer
297 shell extension is included that allows you to right click on items
298 within an AFS tree to bring up an "AFS" menu item and perform various
299 operations on a file or directory. The most useful item is "Access
300 Control Lists", which allows you to view and edit the permissions of a
301 particular directory. Command line tools are also available in the
302 install directory. These commands include klog, unlog, tokens, kpasswd,
303 symlink, fs and pts. The installable includes a readme file that contains
304 more information on how to use the client program and known issues.
306 ** support for large caches in afsd. Cachefiles are stored in
307 subdirectories. The default is 2048 files per subdirectory, which
308 should work fine in most situations. You can use the new afsd
309 option -files_per_subdir to change this number. Note that the first
310 time you run afsd with this patch, your cachefiles will get moved
311 into subdirectories. If you subsequently run an older version of
312 afsd, you will lose all your cached files.