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