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