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