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