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