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