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