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