1 OpenAFS News -- history of user-visible changes. October 19, 2001
3 * Changes incorporated in OpenAFS 1.2.3
5 ** Cell aliases for dynroot can be specified in the CellAlias file in
6 /usr/vice/etc or /usr/local/etc/openafs, in format "realname alias",
7 one per line. They can also be managed at runtime with "fs newalias"
10 * Changes incorporated in OpenAFS 1.2.2
12 ** Solaris 9 and Linux PA-RISC are now supported
14 ** fileserver will not erroneously delay legitimate errors for 3 seconds
15 after 10 errors are returned (e.g. stat() on a directory you can't read)
17 ** Rx MTU calculation now works for Irix, Solaris and Linux
19 ** If afsd is started with the -dynroot flag, /afs will be locally
20 generated from the CellServDB. AFSDB cells will be mounted
21 automatically upon access.
23 ** The namei fileserver allows vice "partitions" to be directories instead
24 of partitions and will attach and display accordingly. Creating the file
25 "AlwaysAttach" in the /vicepX directory is used as the trigger to attach it.
27 ** TSM support for butc no longer requires editing a Makefile, simply
28 specify the --enable-tivoli-tsm configure option.
30 ** Linux builds no longer require source changes every time the kernel
31 inode structure changes; the OpenAFS sources will now configure
32 itself to the actual inode structure as defined in the kernel
35 * Changes incorporated in OpenAFS 1.2.1
37 ** vfsck on Digital UNIX and Solaris will now refuse to fsck mounted
40 * Changes incorporated in OpenAFS 1.2.0
42 ** AFS now supports --prefix and the other directory options of
43 configure. By default AFS builds assuming it will be installed in
44 /usr/local. In order to get traditional AFS directory paths (/usr/afs
45 and /usr/vice/etc) use the --enable-transarc-paths option to
46 configure. More details on the new directory layout are found in README.
48 * Changes incorporated in OpenAFS 1.1.1a
50 ** Windows 95/98/ME/NT/2000 - Consistent versioning
51 Installation, AFS Control Center, Client dialog boxes and properties
52 pages for executables display a consistent OpenAFS version number.
53 Installation detects previous installation and prompts the user for upgrade
56 ** Windows 95/98/ME/NT/2000 - Installation features
57 During installation the user can select the source of the CellservDB file,
58 AFS home cell, and drive mappings. During installation a drive path
59 mapping can include a variable that will be substituted with the current
60 UserName that is logged in.
62 ** Windows 2000/NT - Integrated logon
63 The Integrated Logon feature works now.
65 ** Windows 95/98/ME - Logon script features
66 The Windows 95/98/ME client now offers a command-line option for starting up
67 the AFS client without authenication. It is now possilbe to start the AFS
68 client first and obtain tokens, and map drives all through Windows scripts.
69 This helps using Windows 95/98/ME client in Kerberos 5 environment.
71 ** Windows 2000/NT - LANA numbers
72 AFS client now scans the LANA numbers to establish the correct NETBIOS
73 connection. NetBEUI is no longer needed. The user no longer needs to find
74 the correct LANA number.
76 ** Windows 2000/NT - OpenAFS naming consistancy
77 Further progress has been made to remove references to "Transarc AFS"
78 and replace with "OpenAFS".
82 * Changes since OpenAFS 1.0
84 ** AFS now builds with configure. The README for building has been
85 updated and includes full details.
87 ** A client system can now have multiple sysname values for @sys.
88 They will be searched in order when looking up files in AFS. The
89 -newsysname argument to fs sysname can be repeated to set multiple
92 ** A new system group is created for new cells (system:ptsviewers
93 with id -203). If this group exists, members of this group can
94 examine and read the entire protection database. They can examine
95 all users and groups and can get the membership of any group.
97 ** A new program, pt_util has been added to the distribution. This
98 program allows users to print the contents of the protection
99 database or to edit the protection database without running a
100 ptserver. It can be used to set up a new cell without ever running
101 in noauth mode. Run pt_util -h for help.
103 ** The fs setcrypt and fs getcrypt commands have been added. These
104 commands allow the system administrator to require that the client
105 encrypt all authenticated traffic between the client workstation
106 and AFS. The encryption used is weak, but is likely better than
107 sending unencrypted traffic in most environments. Some functions,
108 such as looking for a volume may not be encrypted, but data
109 transfer certainly is. By default data is not encrypted. At this
110 time no significant experimentation with server performance has
113 ** By default AFS is compiled with AFS_AFSDB_ENV, enabling the -afsdb
114 option to be given to afsd on startup. If this option is used, then new
115 cells will be looked up using AFSDB records stored in DNS if they
116 are not found in CellServDB. This means that users can create
117 cross-cell mountpoints in directories they control to access cells
118 not in root.afs, and that cells in root.afs need not be in the
121 ** AFS database servers can be marked as read-only clones. Surround
122 the hostname in square brackets on the bos addhost command and the
123 database server will never be elected sync site. This is useful
124 for cells distributed over a wide region.
126 ** The AFS servers now support the -syslog flag. This flag causes
127 them to log to syslog rather than to files. This flag is not
128 supported on NT. For all servers besides the salvager, the flag can
129 also be specified as -syslog=facility, where facility is an integer
130 facility code from syslog.h. A -syslogfacility option is provided for
131 the salvager to accomplish the same goal.
133 ** If the --enable-fast-restart flag is given when configuring AFS,
134 then the salvager supports the -dontsalvage flag which causes it to
135 exit without salvaging any volumes. If this is configured into the
136 third command of a fs process, then the fileserver will start without
137 salvaging. It will fail to attach volumes that need salvaging and they
138 can be salvaged manually. This provides significantly better server
139 startup performance at the cost of administrative complexity.
141 ** If the --enable-bitmap-later flag is given when configuring AFS,
142 then the fileserver creates bitmaps for free vnodes on demand, allowing
145 ** If bosserver finds a BosConfig.new file at startup, it reads this
146 file and renames it to BosConfig. This allows bosserver to be
147 reconfigured at next restart.
149 ** The bosserver can be placed in a restricted mode in
150 which AFS superusers are only granted limited access to the server
151 host. The following functionality is disabled when restricted mode is in
155 bos getlog (except for files with no '/'s in their name)*
161 specific exceptions are made for functionality that "bos salvage"
164 a cron bnode who's name is "salvage-tmp", time is now, and command
165 begins with "/usr/afs/bin/salvager" may be created. This bnode
166 deletes itself when complete, so no special "delete" support is needed.
167 This functionality may be removed in the future if a "Salvage" RPC is
170 The file with the exact path /usr/afs/logs/SalvageLog may be fetched,
171 since that is how bos salvage [...] -showlog is implimented.
173 Restricted mode is enabled using a new bos command (bos setrestricted)
174 or bossever command line switch (bosserver -restricted). Restricted
175 mode can be disabled by a) sending the bosserver process a SIGFPE (which
176 will then allow restricted operations until the next restart or
177 setrestricted command) or b) editing /usr/afs/local/BosConfig
178 (or BosConfig.new), and restarting the bosserver.
180 ** The bos UserList of trusted administrators can now contain
181 cross-realm Kerberos principals.
183 ** udebug now takes --server not --servers.
185 ** Several error messages have been improved to include volume
188 ** Several new ports have been included for UNIX platforms: Darwin
189 (ppc_darwin_12 and ppc_darwin_13), Linux 2.4 (i386_linux24), Linux on
190 the Powerpc (ppc_linux22 and ppc_linux24), Linux on the Sparc
191 (sparc_linux22, sparc64_linux22 and sparc64_linux24) .
193 ** Incomplete FreeBSD and Alpha Linux ports are included. The
194 FreeBSD port has a working server and the Alpha Linux port has a
195 partially working client.
197 ** A native client for Windows 95/98/ME has been added to the distribution.
198 With this program, a gateway machine is no longer required for Windows 9x
199 to access AFS files. One drive letter will be created on your machine by
200 default - Z:. The Z: drive will be the root of the AFS tree, allowing you
201 to browse all sites that have AFS servers available. Additional drive
202 letters can be defined for other AFS directories. A Windows Explorer
203 shell extension is included that allows you to right click on items
204 within an AFS tree to bring up an "AFS" menu item and perform various
205 operations on a file or directory. The most useful item is "Access
206 Control Lists", which allows you to view and edit the permissions of a
207 particular directory. Command line tools are also available in the
208 install directory. These commands include klog, unlog, tokens, kpasswd,
209 symlink, fs and pts. The installable includes a readme file that contains
210 more information on how to use the client program and known issues.
212 ** support for large caches in afsd. Cachefiles are stored in
213 subdirectories. The default is 2048 files per subdirectory, which
214 should work fine in most situations. You can use the new afsd
215 option -files_per_subdir to change this number. Note that the first
216 time you run afsd with this patch, your cachefiles will get moved
217 into subdirectories. If you subsequently run an older version of
218 afsd, you will lose all your cached files.