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