This commit fixes unrecognized tags and attributes, misplaced tags,
unescaped characters (such as '&', and spaces in URLs), empty paragraphs
and spans, and missing DOCTYPEs in the top level directory html files,
reported by the html tidy tool.
$ tidy -q -e cvs.html
line 42 column 19 - Error: <bold> is not recognized!
line 42 column 19 - Warning: discarding unexpected <bold>
line 42 column 33 - Warning: discarding unexpected </bold>
$ tidy -q -e gsoc.html
line 1 column 1 - Warning: missing <!DOCTYPE> declaration
line 100 column 1 - Warning: trimming empty <p>
line 189 column 1 - Warning: trimming empty <p>
line 193 column 1 - Warning: trimming empty <p>
line 197 column 1 - Warning: trimming empty <p>
line 229 column 23 - Warning: <font> element removed from HTML5
$ tidy -q -e macos.html
line 58 column 1 - Warning: inserting implicit <p>
line 81 column 1 - Warning: inserting implicit <p>
line 104 column 1 - Warning: inserting implicit <p>
line 126 column 1 - Warning: inserting implicit <p>
line 151 column 1 - Warning: inserting implicit <p>
line 177 column 97 - Warning: unescaped & or unknown entity "&cat_id"
line 212 column 97 - Warning: unescaped & or unknown entity "&cat_id"
line 58 column 1 - Warning: trimming empty <p>
line 81 column 1 - Warning: trimming empty <p>
line 104 column 1 - Warning: trimming empty <p>
line 126 column 1 - Warning: trimming empty <p>
line 151 column 1 - Warning: trimming empty <p>
line 428 column 1 - Warning: trimming empty <p>
$ tidy -q -e main.html
line 309 column 5 - Warning: missing <li>
line 49 column 1 - Warning: <table> lacks "summary" attribute
line 53 column 9 - Warning: trimming empty <span>
$ tidy -q -e navbar.html
line 9 column 1 - Warning: <table> lacks "summary" attribute
$ tidy -q -e no-more-des.html
line 1 column 1 - Warning: missing <!DOCTYPE> declaration
line 65 column 1 - Error: <du> is not recognized!
line 65 column 1 - Warning: discarding unexpected <du>
line 64 column 1 - Warning: missing </blockquote> before <li>
line 66 column 3 - Warning: inserting implicit <ul>
line 79 column 1 - Warning: discarding unexpected </du>
line 66 column 3 - Warning: missing </ul> before </blockquote>
line 86 column 1 - Error: <du> is not recognized!
line 86 column 1 - Warning: discarding unexpected <du>
line 84 column 1 - Warning: missing </blockquote> before <li>
line 87 column 2 - Warning: inserting implicit <ul>
line 120 column 1 - Warning: discarding unexpected </du>
line 87 column 2 - Warning: missing </ul> before </blockquote>
line 85 column 1 - Warning: trimming empty <p>
$ tidy -q -e openafs-vista-announce.html
line 1 column 1 - Warning: missing <!DOCTYPE> declaration
$ tidy -q -e projects.html
line 20 column 51 - Warning: replacing </p> with <br>
line 26 column 35 - Warning: replacing </p> with <br>
line 37 column 20 - Warning: replacing </p> with <br>
line 40 column 19 - Warning: replacing </p> with <br>
line 43 column 20 - Warning: replacing </p> with <br>
line 46 column 28 - Warning: replacing </p> with <br>
line 51 column 49 - Warning: replacing </p> with <br>
line 53 column 26 - Warning: replacing </p> with <br>
line 58 column 13 - Warning: replacing </p> with <br>
line 68 column 42 - Warning: replacing </p> with <br>
line 72 column 40 - Warning: replacing </p> with <br>
line 83 column 20 - Warning: replacing </p> with <br>
line 86 column 32 - Warning: replacing </p> with <br>
line 89 column 43 - Warning: replacing </p> with <br>
line 92 column 26 - Warning: replacing </p> with <br>
line 95 column 23 - Warning: replacing </p> with <br>
$ tidy -q -e roadmap.html
line 24 column 1 - Warning: <a> escaping malformed URI reference
line 78 column 1 - Warning: <h2> proprietary attribute "wrap"
$ tidy -q -e success.html
line 277 column 58 - Warning: discarding unexpected </tt>
line 345 column 13 - Warning: discarding unexpected </b>
line 16 column 1 - Warning: trimming empty <p>
line 19 column 1 - Warning: trimming empty <p>
line 25 column 36 - Warning: trimming empty <span>
line 26 column 56 - Warning: trimming empty <span>
line 27 column 21 - Warning: trimming empty <p>
line 31 column 1 - Warning: trimming empty <p>
line 37 column 1 - Warning: trimming empty <p>
line 41 column 1 - Warning: trimming empty <p>
line 44 column 1 - Warning: trimming empty <p>
line 51 column 1 - Warning: trimming empty <p>
line 56 column 1 - Warning: trimming empty <p>
line 61 column 1 - Warning: trimming empty <p>
line 66 column 34 - Warning: trimming empty <span>
line 67 column 48 - Warning: trimming empty <span>
line 84 column 1 - Warning: trimming empty <p>
line 86 column 1 - Warning: trimming empty <p>
line 100 column 1 - Warning: trimming empty <p>
line 102 column 1 - Warning: trimming empty <p>
line 109 column 1 - Warning: trimming empty <p>
line 111 column 1 - Warning: trimming empty <p>
line 135 column 1 - Warning: trimming empty <p>
line 137 column 1 - Warning: trimming empty <p>
line 149 column 1 - Warning: trimming empty <p>
line 151 column 1 - Warning: trimming empty <p>
line 157 column 1 - Warning: trimming empty <p>
line 165 column 1 - Warning: trimming empty <p>
line 205 column 1 - Warning: trimming empty <p>
line 552 column 1 - Warning: trimming empty <p>
line 79 column 1 - Warning: <h2> proprietary attribute "wrap"
line 167 column 1 - Warning: <h2> proprietary attribute "wrap"
line 169 column 1 - Warning: <p> proprietary attribute "wrap"
line 170 column 1 - Warning: <p> proprietary attribute "wrap"
line 174 column 1 - Warning: <p> proprietary attribute "wrap"
line 176 column 1 - Warning: <p> proprietary attribute "wrap"
line 178 column 1 - Warning: <p> proprietary attribute "wrap"
line 181 column 1 - Warning: <p> proprietary attribute "wrap"
line 207 column 1 - Warning: <h2> proprietary attribute "wrap"
line 209 column 1 - Warning: <p> proprietary attribute "wrap"
line 230 column 1 - Warning: <p> proprietary attribute "wrap"
line 232 column 1 - Warning: <p> proprietary attribute "wrap"
line 233 column 1 - Warning: <p> proprietary attribute "wrap"
line 253 column 1 - Warning: <p> proprietary attribute "wrap"
line 258 column 1 - Warning: <h2> proprietary attribute "wrap"
$ tidy -q -e support.html
line 99 column 6 - Warning: discarding unexpected </p>
line 20 column 17 - Warning: <a> escaping malformed URI reference
line 34 column 17 - Warning: <a> escaping malformed URI reference
line 35 column 17 - Warning: <a> escaping malformed URI reference
$ tidy -q -e support.html
line 99 column 6 - Warning: discarding unexpected </p>
line 20 column 17 - Warning: <a> escaping malformed URI reference
line 34 column 17 - Warning: <a> escaping malformed URI reference
line 35 column 17 - Warning: <a> escaping malformed URI reference
$ tidy -q -e uiuc_capstone.html
line 1 column 1 - Warning: missing <!DOCTYPE> declaration
line 78 column 1 - Warning: <a> escaping malformed URI reference
$ tidy -q -e windows.html
line 22 column 9 - Warning: missing <li>
line 32 column 9 - Warning: missing <li>
line 101 column 48 - Warning: <a> attribute with missing trailing quote mark
line 349 column 111 - Warning: unescaped & or unknown entity "&DisplayLang"
line 104 column 1 - Warning: <a> escaping malformed URI reference
line 208 column 33 - Warning: <img> lacks "alt" attribute
Change-Id: I2fad0bfeb8a188aef29d2263ef09685d57333a30
Reviewed-on: https://gerrit.openafs.org/13549
Reviewed-by: Cheyenne Wills <cwills@sinenomine.net>
Reviewed-by: Stephan Wiesand <stephan.wiesand@desy.de>
Tested-by: Stephan Wiesand <stephan.wiesand@desy.de>
in a subdirectory of the current directory
named <code>openafs</code>. The repository itself is in
the <code>.git</code> subdirectory of that
- directory. <bold>WARNING:</bold> The repository is approximately
+ directory. <strong>WARNING:</strong> The repository is approximately
78MiB currently and will only grow, so it may take some time to
download the first time over a slow network connection.
</p>
+<!DOCTYPE html>
<html>
<head>
we're happy to help you to learn them. Please join us on #openafs on freenode,
in the Jabber conference openafs@conference.openafs.org, or on the
openafs-devel@openafs.org mailing list.
-<p>
+</p>
<h3>Background reading</h3>
If you are interested in working on OpenAFS this
<h4><a name="kafs"></a>An alternate implementation of a userspace helper interface for Linux kafs</h4>
<h5>Student: Weylan (Wang) Lei</h5>
-<p />
+<p>
During last year's Google Summer of Code, an interface for allowing use of OpenAFS userspace programs with kafs was developed. This was found to not be acceptable to the Linux kernel core due to the pioctl ultiplexor system call. An alternate approach using [gs]etxattr(), add_key() and keyctl() and /proc with O_NODE was done; This year's project aims to extend upon that work.
+</p>
<h4><a name="NetBSD_port"></a>A port of OpenAFS to NetBSD</h4>
<h5>Student: Matt Smith</h5>
-<p />
+<p>
Around the same time the original Linux port of AFS was done, a port to NetBSD was also available. While NetBSD has evolved, the original AFS port did not keep pace. Since then, a port to NetBSD has been highly desired. This project will port the OpenAFS client to run on NetBSD.
+</p>
<h4><a name="Encrypted_storage"></a> Encrypted storage </h4>
<h5>Student: Sanket Agarwal</h5>
-<p />
+<p>
The AFS protocol offers encryption for data transport from client to server.
However, that data is stored on the server in cleartext, where it can
potentially be read by the administrators of that server. This poses a real
contents. This is a challenging project, during which the student will gain
an in depth knowledge of kernel programming, distributed systems, and
cryptography.
+</p>
<h4>Unix or Windows Cache Manager support for Apple Doublefiles (Extended /
Posix Attributes)</h4>
<h5>Student: Kelli Ireland</h5>
<h4>Implementing Microsoft's Safe String (StrSafe.h) Library for UNIX/Linux</h4>
<h5>Student: Jonas Sundberg</h5>
<p>Microsoft has developed a safe C String manipulation library (StrSafe.h).
-The advantages of the <font color="#ffffff" style="BACKGROUND-COLOR: #3399ff">
-Strsafe</font> functions include:</p>
+The advantages of the
+<code>Strsafe</code> functions include:</p>
<ul>
<li>The size of the destination buffer is always provided to the function to
ensure that the function does not write past the end of the buffer. </li>
<ul>
<li> The installer is not signed with a certificate accepted by OS X. With the default security settings, it can't be run with a double click. It takes a secondary (right) click and choosing "Open" from the menu instead.
</ul>
-</p>
<br><br>
<h2><a name="mountainlion">Maintenance Release: OpenAFS 1.6.5 for MacOS 10.8 (Mountain Lion)</a></h2>
(released 24 Jul 2013)<br>
<li>Finder does not display the AFS volume on the Desktop unless the user has selected 'Connected servers" in Finder->Preferences->General.(<A HREF="http://rt.central.org/rt/Ticket/Display.html?id=75382">Bug 75382</A>)</li>
<li>Kerberos API does not permit reliable display of Kerberos error messages.</li>
</ul>
-</p>
<br><br>
<h2><a name="lion">Maintenance Release: OpenAFS 1.6.5 for MacOS 10.7 (Lion)</a></h2>
(released 24 Jul 2013)<br>
<li>Finder does not display the AFS volume on the Desktop unless the user has selected 'Connected servers" in Finder->Preferences->General.(<A HREF="http://rt.central.org/rt/Ticket/Display.html?id=75382">Bug 75382</A>)</li>
<li>Kerberos API does not permit reliable display of Kerberos error messages.</li>
</ul>
-</p>
<br><br>
<h2><a name="snowleopard">Maintenance Release: OpenAFS 1.6.5 for MacOS 10.6 (Snowleopard)</a></h2>
(released 24 Jul 2013)<br>
<ul>
<li>Finder does not display the AFS volume on the Desktop unless the user has selected 'Connected servers" in Finder->Preferences->General.(<A HREF="http://rt.central.org/rt/Ticket/Display.html?id=75382">Bug 75382</A>)</li>
</ul>
-</p>
<br><br>
<h2><a name="leopard">Maintenance Release: OpenAFS 1.6.1 for MacOS 10.5 (Leopard)</a></h2>
(released 2 Apr 2012)<br>
<li>Finder does not display the AFS volume on the Desktop unless the user has selected 'Connected servers" in Finder->Preferences->General.</li>
<li>Finder consumes excess resources while AFS running after upgrade from 10.4. (<A HREF="http://rt.central.org/rt/Ticket/Display.html?id=87482">Bug 87482</A>)</li>
</ul>
-</p>
<br><br>
<h2><a name="tiger">Maintenance Release: OpenAFS 1.4.11 for MacOS 10.4 (Tiger)</a>
<font color="#FF0000">**Recommended**</font></h2>
</ul>
<p>Note: If you receive the message <b>"You cannot continue. There is
nothing to install."</B> you need to remove the OpenAFS package receipt
-from "/Library/Receipts". <a href="http://www.osxgnu.org/software/pkgdetail.html?project_id=244&cat_id=212">OSXPM</a> is a tool that can be used to
+from "/Library/Receipts". <a href="http://www.osxgnu.org/software/pkgdetail.html?project_id=244&cat_id=212">OSXPM</a> is a tool that can be used to
perform package management on MacOS X, or you can simply use the bundled uninstaller in the OpenAFS disk image.
</p>
<br>
</ul>
<p>Note: If you receive the message <b>"You cannot continue. There is
nothing to install."</B> you need to remove the OpenAFS package receipt
-from "/Library/Receipts". <a href="http://www.osxgnu.org/software/pkgdetail.html?project_id=244&cat_id=212">OSXPM</a> is a tool that can be used to
+from "/Library/Receipts". <a href="http://www.osxgnu.org/software/pkgdetail.html?project_id=244&cat_id=212">OSXPM</a> is a tool that can be used to
perform package management on MacOS X, or you can simply use the bundled uninstaller in the OpenAFS disk image.
</p>
<h2><a name="growl">Growl Notifier for MacOS X</a></h2>
<p>
As of OpenAFS 1.5.73, a Growl notifier is included. You can find it in /Library/OpenAFS/Tools/tools/growlagent-openafs. It can be run as any user. The <A HREF="http://growl.info">Growl</A> software must be installed and running. Additionally, before any events will be received, you must, once each time AFS is started, run <B>"sudo fs mariner localhost"</B>. Future versions will likely include persistent configuration for this.
-<p>
+</p>
<h2><a name="tool">Third Party AFS Tools for MacOS X</a></h2>
<ul>
<li><A HREF="http://www.lnf.infn.it/~bisegni/Main/Afs_Commander.html">AFS Commander</A>: an OSX preferences pane to simplify management of the OpenAFS client. This tool is bundled with recent OpenAFS releases.</li>
<div style="text-align:left">
-<table style="width: 1000">
+<table style="width: 1000" summary="">
<tr>
<td> </td>
</tr>
-</table><span></span>
+</table>
</div>
<h2>Recent OpenAFS News</h2>
<li>but not 4.5</li>
</ul>
</li>
- <li>Basic support for the latest OS X and FreeBSD releases</li>
+ <li>Basic support for the latest OS X and FreeBSD releases
<ul>
<li>no packaging support for current OS X yet</li>
</ul>
+ </li>
<li>Linux cache managers will return unused kernel memory earlier and
in smaller chunks, lowering memory use for vcaches and avoiding
stalls</li>
</head>
<body class="navbar">
-<table class="navbar" width="140"
+<table class="navbar" width="140" summary=""
cellspacing="3" border="0" cellpadding="0">
<tr><th class="navbar" colspan=2 align=left>
+<!DOCTYPE html>
<html>
<head>
installation, configuration, and administration.</p>
<blockquote>
-<du>
+<ul>
<li>
2004:
<a class="moz-txt-link-freetext" href="http://www-conf.slac.stanford.edu/AFSBestPractices">http://www-conf.slac.stanford.edu/AFSBestPractices</a>
<li>
2006:
<a class="moz-txt-link-freetext" href="http://workshop.openafs.org/afsbpw06/">http://workshop.openafs.org/afsbpw06/</a></li>
-</du>
+</ul>
</blockquote>
<p>With this historical foundation in place, the OpenAFS Elders are
officially announcing the deprecation of kaserver and endorsing the following
roadmap for transitioning from single DES to stronger ciphers:</p>
<blockquote>
-<p></p>
-<du>
+<ul>
<li>Effective immediately, kaserver releases will log a warning
at startup stating that kaserver support has been deprecated and
that a migration to a Kerberos 5 solution should begin.</li>
default on clients, then disabled by default on servers, and
eventually it will be removed from the source tree. Further details
will be announced as part of the OpenAFS 2.0 release.</li>
-</du>
+</ul>
</blockquote>
<p>If a significant security hole is identified in either kaserver or DES
prior to its removal from the OpenAFS source tree, the OpenAFS Elders
+<!DOCTYPE html>
<html>
<head>
<h2>Pending projects</h2>
The following are items known to be in progress, and, where available, a point of contact.
<dl>
-<dt><p>Hierarchical Storage Management Integration</p></dt>
+<dt>Hierarchical Storage Management Integration</dt>
<dd><p>Provide support for storing AFS files into a HSM system (DMF is
the first targeted HSM system). Contact Ken Hornstein
(kenh@cmf.nrl.navy.mil) for more information. This project
has been made possible in part by support from SGI.
</p></dd>
-<dt><p>Disconnected AFS Operations</p></dt>
+<dt>Disconnected AFS Operations</dt>
<dd><p>Provides the ability to use AFS while not connected to a network.
Significant work was completed during the 2008 Google Summer of Code and
currently resides in the OpenAFS Git repository as part of the
disconnected client modified the same objects. Contact Simon Wilkinson
(sxw@inf.ed.ac.uk) for more information.</p>
</dd>
-<dt><p>FreeBSD port</p></dt>
+<dt>FreeBSD port</dt>
<dd><p>Server ported. Cache manager support is not yet complete.</p>
</dd>
-<dt><p>NetBSD port</p></dt>
+<dt>NetBSD port</dt>
<dd><p>Server ported. No timeline available.</p>
</dd>
-<dt><p>OpenBSD port</p></dt>
+<dt>OpenBSD port</dt>
<dd><p>In progress. Cache manager works but not recommended for production use.</p>
</dd>
-<dt><p>Better Documentation</p></dt>
+<dt>Better Documentation</dt>
<dd><p>In progress. On-going projects have produced a complete set of new
<a href="http://www.openafs.org/manpages/">man pages</a>, a replacement for the
Unix Quick Start Guide, and progress on a new Administrator's Guide. Contact Russ Allbery if you'd like to contribute</p>
</dd>
-<dt><p>Kerberos v5 and multiple encryption types</p></dt>
+<dt>Kerberos v5 and multiple encryption types</dt>
<dd><p>In progress. Add Kerberos v5 and additional encryption type support. Contact Marcus Watts or Matt Benjamin</p>
-<dt><p>RxUDP Improvements</p></dt>
+<dt>RxUDP Improvements</dt>
<dd><p>In progress. Your File System Inc. was awarded a SBIR grant to improve
the performance characteristics of the Rx RPC mechanism. During Phase I
many implementation deficiencies were corrected and maximum throughput was
raised from 60MB/second to 240MB/second. </p></dd>
-<dt><p>RxTCP</p></dt>
+<dt>RxTCP</dt>
<dd><p><a href="http://workshop.openafs.org/afsbpw06/talks/kenh-rxtcp.pdf">In progress.</a>
Implement Rx API on top of TCP/IP in order to gain performance on high speed
networks and improve the behavior of AFS across firewalls and network address
translators. Ken Hornstein began the effort. Contact Jeffrey Altman
for additional information.</p>
</dd>
-<dt><p>HostAFSd<p></dt>
+<dt>HostAFSd</dt>
<dd><p>In progress. Implement an AFS server that exports portions of the local file system to AFS clients. Contact Derrick Brashear.
</dd>
-<dt><p>Native Windows file system support</p></dt>
+<dt>Native Windows file system support</dt>
<dd><p>In Progress. Implement AFS as a Windows Network Redirector and File System Filter instead of as a virtual SMB server.
Contact Jeffrey Altman and Peter Scott for additional information.</p>
</dd>
-<dt><p>Better server preference support</p></dt>
+<dt>Better server preference support</dt>
<dd><p>In progress. Allow selectable continuous or on-demand server preferences in clients based on available information about Rx connection round trip times instead of classful networking approach currently used.
This project is being worked on by Jacob Thebault-Spieker as a 2009 Google
Summer of Code project. Contact Derrick Brashear (shadow@dementia.org)</p>
The following are items which have been proposed, but which are not yet in progress. A point of contact is included where appropriate.
<dl>
-<dt><p>IPv6 support</p></dt>
+<dt>IPv6 support</dt>
<dd><p>Make AFS support IPv6.</p>
</dd>
-<dt><p>Multiple volume versions</p></dt>
+<dt>Multiple volume versions</dt>
<dd><p>Support for multiple "clones" of a single volume.</p>
</dd>
-<dt><p>Selectable UBIK best host algorithm</p></dt>
+<dt>Selectable UBIK best host algorithm</dt>
<dd><p>Change lowest IP metric to something administrator-selectable.</p>
</dd>
-<dt><p>Volume dump editor</p></dt>
+<dt>Volume dump editor</dt>
<dd><p>Tool to allow editing volume dumps.</p>
</dd>
-<dt><p>Partition UUIDs</p></dt>
+<dt>Partition UUIDs</dt>
<dd><p>Create partition UUIDs such that the vldb can be rapidly updated if a disk is moved from one machine to another. Contact Derrick Brashear (shadow@dementia.org).
</dd>
<dt><p>Directory format extensions to support Unicode filenames</dt>
fixed timelines for future plans. Regardless, there is still an overarching
plan for the desired trend of future development, with major features and
milestones to be reached. Please send inquiries, comments, and offers of support to
-<a href="mailto:openafs-gatekeepers@openafs.org?subject=OpenAFS Roadmap Feedback">
+<a href="mailto:openafs-gatekeepers@openafs.org?subject=OpenAFS%20Roadmap%20Feedback">
openafs-gatekeepers@openafs.org</a>. Where external contributors have promised
contributions, they are included, as are timelines when those are provided.
The following release schedule is subject to change.</p>
<h1 align="center">Development Wish List</h1>
-<h2 wrap><a name="modernization"></a>Modernization of crypto and network support</h2>
+<h2><a name="modernization"></a>Modernization of crypto and network support</h2>
<p>Over the years, the AFS protocol has not kept up with developments in
cryptography and network protocols, sticking with single-DES-grade encryption
and remaining an IPv4-only service. The 2013 security release moved
<h1>OpenAFS Success Stories</h1>
<h2 align="left"><a name="case-slac"></a>Stanford Linear Accelerator Center</h2>
-<dl>
-<dd>AFS supports all of the following projects in that most of the tools (compilers,
+<p>AFS supports all of the following projects in that most of the tools (compilers,
CVS code trees, etc.) are in AFS as well as some of the data input and output for
their simulations (some Monte Carlo type simulations but mostly data for GEANT simulations).
-<p></p>
+</p><p>
Here are three press releases about three very different branches of science going
on at SLAC.
-<p></p>
+</p><p>
The first is about our biggest experiment, BaBar. They proved a certain kind of
CP ("charge-parity") violation that explains in part the asymmetry between matter
and antimatter. This explains (in part) why after the Big Bang more matter than
antimatter was left over and the universe could form. BaBar has taken around 2 PetaByte
of data sitting on tape but all their development tools and software code sit in
-AFS. BaBar uses AFS for<span class="moz-txt-citetags"> </span>
-worldwide collaboration, and distribution of their code<span class="moz-txt-citetags">
-</span>repositories.<p></p>
+AFS. BaBar uses AFS for
+worldwide collaboration, and distribution of their code
+repositories.</p><p>
September 28, 2006 - New Form of CP Violation Discovered <br>
<a class="moz-txt-link-freetext" href="http://home.slac.stanford.edu/pressreleases/2006/20060928.htm">
http://home.slac.stanford.edu/pressreleases/2006/20060928.htm</a>
-<p></p>
+</p><p>
The second one is astrophysics research done at KIPAC (Kavli Institute for Particle
Astrophysics and Cosmology). They did mass analysis of pictures from the Chandra
X-ray Observatory and for the first time directly observed the Dark Matter. The
data itself is again not in AFS but most of the development tools and software code
is in AFS.
-<p></p>
+</p><p>
August 21, 2006 - Dark Matter Observed <br>
<a class="moz-txt-link-freetext" href="http://home.slac.stanford.edu/pressreleases/2006/20060821.htm">
http://home.slac.stanford.edu/pressreleases/2006/20060821.htm</a>
-<p></p>
+</p><p>
The next two are about our Synchrotron Radiation Lab (SSRL). They highlight the
application of SLAC's physics technology for completely different branches of science.
-<p></p>
+</p><p>
August 2, 2006 - Modern Technology Reveals Ancient Science <br>
<a class="moz-txt-link-freetext" href="http://home.slac.stanford.edu/pressreleases/2006/20060802.htm">
http://home.slac.stanford.edu/pressreleases/2006/20060802.htm</a>
+</p>
<p>Archimedes Manuscript Yields Secrets Under X-Ray Gaze <br>
<a class="moz-txt-link-freetext" href="http://home.slac.stanford.edu/pressreleases/2005/20050518.htm">
http://home.slac.stanford.edu/pressreleases/2005/20050518.htm</a> </p>
-<p></p>
+<p>
SLAC is currently expanding the computer center's relationship with SSRL to provide
AFS space for their tools like Gaussian (sequential and parallel). They have also
started to use our standard software development tools (compilers, etc.) in AFS
space.
-<p></p>
+</p><p>
Lastly, a very widely used toolkit, GEANT4 (<a class="moz-txt-link-freetext" href="http://geant4.web.cern.ch/geant4/">http://geant4.web.cern.ch/geant4/</a>),
for the simulation of the passage of particles through matter is being co-developed
at SLAC. Everything they do is in AFS. Among many, many other things, this toolkit
is used for medical simulations of radiation treatments of tumors in the human body.
-<p></p>
+</p><p>
A summary of research performed at SLAC in 2006:
<a class="moz-txt-link-freetext" href="http://today.slac.stanford.edu/feature/holiday-message06.asp">
http://today.slac.stanford.edu/feature/holiday-message06.asp</a>
+</p>
<p>Since 1998, SLAC has stored all user home directories in AFS. AFS is
-available to the several thousand<span class="moz-txt-citetags"> </span>machines
-in its batch farm and is used primarily for the<span class="moz-txt-citetags">
-</span>delivery of binaries for batch jobs.</p>
+available to the several thousand machines
+in its batch farm and is used primarily for the
+delivery of binaries for batch jobs.</p>
<p>How much data (in TB)?
5.5TB<br>
How many users?
How many file servers?
15 fileservers<br>
How much storage per file server? 34GB to 1.6TB</p>
-</dd></dl>
-<h2 wrap><a name="case-pdc"></a>ParallellDatorCentrum, Center for Parallel Computers
+
+<h2><a name="case-pdc"></a>ParallellDatorCentrum, Center for Parallel Computers
at KTH </h2>
-<dl><dd>
+<p>
One of the computing centers in Sweden for research. Situated at KTH, Royal Institute
of Technology, Stockholm. Written by Harald Barth.
-<p></p>
+</p><p>
Historical reasons:
-<p></p>
+</p>
<ul>
<li>In the infancy of network file systems different parts of the decentralized
computing service groups at KTH were looking for a platform independent file
fact. To abandon AFS would make it necessary to rewrite all this - accumulated
since approximately 1992.</li>
</ul>
-<p></p>
+<p>
Reasons important back then but not as important any more:
-<p></p>
+</p>
<ul>
<li>As network speed has increased a factor of 100, hard disk speeds have only
a factor of 10. So local cache on the workstations/computing nodes, once a crucial
detail of AFS, is not the overall important reason to deploy AFS any more.
</li>
</ul>
-<p></p>
+<p>
Reasons still important:
-<p></p>
+</p>
<ul>
<li>Design of location independence. Users access their files though globally
unique path names which do not change. Period. The file system handles all mapping
freely. For example no problem to write data on MacOSX, store it on a mix of
Solaris and Linux servers and read it back on Windows. </li>
</ul>
-<p></p>
+<p>
Challenges for the future:
-<p></p>
+</p>
<ul>
<li>Encryption: AFS has means for data check summing and encryption. However
the encryption standards of the 90s are not adequate any more. Work is in progress
has to be spent to implement the mechanisms to do this in the framework of AFS.
</li>
</ul>
-<p></p>
+<p>
AFS usage at PDC in numbers (2007-01-01):
-<p></p>
+</p><p>
Number of Clients: Unknown. PDC manages 5 clusters with a total of more than 1200
computing nodes. When the clusters are new, they use to appear around rank 70 of
the top 500 list. All production systems use AFS. There may be a single digit number
of computers which have no access to the AFS space. Add to that the number of researchers
who access their data from their own workstations from all over the Internet.
-<p></p>
+</p><p>
Number of simultaneous users: 100-200.<br>
Number of users with $HOME in pdc.kth.se AFS space: Approx 3000.<br>
Amount of data in AFS: Approx 5TB.<br>
Number of files: Approx 65 000 000.<br>
Number of file servers: 11<br>
Approx storage per server: 1TB<br>
-<p></p>
-</dd></dl>
-<h2 wrap><a name="case-pictage"></a>Pictage Inc. </h2>
-<dl><dd>
-<p wrap><a href="http://www.pictage.com/">http://www.pictage.com/</a></p>
-<p wrap>Pictage's business is worldwide. They provide services to wedding
+</p>
+
+<h2><a name="case-pictage"></a>Pictage Inc. </h2>
+
+<p><a href="http://www.pictage.com/">http://www.pictage.com/</a></p>
+<p>Pictage's business is worldwide. They provide services to wedding
photographers who upload the photos they have taken. Pictage then makes the
photos available to the wedding party for photo selection and printing.
Photos selected for printing are retouched by hand using Adobe Photoshop.</p>
-<p wrap>Pictage uses OpenAFS to store all of the original photos, the processed
+<p>Pictage uses OpenAFS to store all of the original photos, the processed
photos, and the web content.</p>
-<p wrap>Work flow is managed by the use of mount points and symlinks which are placed
+<p>Work flow is managed by the use of mount points and symlinks which are placed
within directories assigned to various photographers and their associated events. </p>
-<p wrap>Pictage storage has exceeded 200TB of data and more then 40 million files.
+<p>Pictage storage has exceeded 200TB of data and more then 40 million files.
They frequently push the limits of the AFS directory structures running into the
directory entry limitations. </p>
-<p wrap>Directory search performance is one of their bottlenecks. Unlike more modern
+<p>Directory search performance is one of their bottlenecks. Unlike more modern
file systems, AFS does not use a B+ tree representation and directory searches
within the case-insensitive Microsoft Windows client are
linear in nature. This wastes significant CPU utilization and clock
files that do not exist such as Java class files, the optimization does not
apply, and the linear search must still be
used.</p>
+<p>
Number of simultaneous users: 150 AFS client users; 1000 web server users<br>
Amount of data in AFS: Approx 215TB<br>
Amount of AFS storage: 265TB with planned growth to 425TB in twelve months<br>
Approx storage per server: depending on age of server 1.2TB to 25TB<p>
(statistics as of 22 May 2007)<br>
</p>
-<p></p>
-</dd></dl>
-<h2 wrap><a name="case-ncsa"></a>NCSA at UIUC</h2>
-<dl><dd>
-<p wrap>HDF is a project that helps support the research projects that NCSA provides
+<h2><a name="case-ncsa"></a>NCSA at UIUC</h2>
+<p>HDF is a project that helps support the research projects that NCSA provides
computing services for.<br>
<br>
This page is prettier and has some more concise history: <br>
systems range from clusters to servers to desktop systems and the binaries can be
dropped right into AFS which users grab via ftp. They need an authenticated
file system that supports all of those platforms. </p>
-<p wrap>NCSA's Security team uses AFS for storing security incidents and collaborating
+<p>NCSA's Security team uses AFS for storing security incidents and collaborating
with off-site users.</p>
-<p wrap>And some comments from Christopher Lindsey about future directions:</p>
-<p wrap>"I can tell you about possible future direction.<br>
+<p>And some comments from Christopher Lindsey about future directions:</p>
+<p>"I can tell you about possible future direction.<br>
<br>
"We've all noticed that the stand-alone University model doesn't work.
Just like businesses that merge, Universities are finding that they need<br>
be submitted on Jan 22 that will revolutionize how HPC resources within
the TeraGrid are used. The ubiquity and security of AFS make it the <br>
perfect foundation for this project.</p>
-<p wrap>"As far as timings, we might be able to do some dprof timings between here
+<p>"As far as timings, we might be able to do some dprof timings between here
and Argonne Labs over iwire (<a class="moz-txt-link-freetext" href="http://www.iwire.org/">http://www.iwire.org/</a>).
Ironically, the
bottleneck there will be the GigE NIC on the AFS servers."</p>
-</dd></dl>
-<h2 wrap><a name="case-usgs"></a>United States Geological Survey</h2>
-<dl><dd>
+
+<h2><a name="case-usgs"></a>United States Geological Survey</h2>
+
<h4>Background</h4>
<p>The use of AFS at the United States Geological
Survey, USGS, started in response to a requirement to provide natural hazard
<h4>Why are we using AFS</h4>
<p>AFS was chosen as it was the only multi-platform software
available to provide geographically distributed content replication,
-access control, and user transparency as required by our </tt>
+access control, and user transparency as required by our
project.</p>
<h4>How we are using AFS</h4>
<p>Three Web servers at each module have an
<p>Our content maintainers are overwhelmingly
using Windows XP, with perhaps 5% using Mac OS X and still smaller numbers using
Linux and Solaris.</p>
-<h4>Staffing</b></h4>
+<h4>Staffing</h4>
<p>Our entire staff consists of 3 full-time
employees, 1 part-time employee, and one manager. These individuals manage the
budget, hardware, operating system maintenance, security, software updates,
custom programming and user support for both the AFS and Web components of the
service.</p>
-</dd></dl>
+
<h2>Robert Carter, Duke University Office of Information Technology, shared:</h2>
-<dl>
-<dd>
+
+
<p>We're using the OpenAFS client code pretty extensively, and
have been since fairly early in its release cycle. We're running the
OpenAFS client on all of our Windows lab machines (we cheered the day the
have a modestly-large AFS cell comprising Solaris servers of various vintage
(Solaris 2.6, mostly, with some Solaris 8 on our more recent acquisitions).
</p>
-</dd>
-</dl>
+
+
<h2>Jimmy Engelbrecht, Kungliga Tekniska Högskolan Elektro Department, shared:</h2>
-<dl>
-<dd>
+
+
<p>
Our cell runs on OpenAFS fileservers on Tru64 5.0a. We have 0.5 - 1 TB of data
and about 250-400 clients. We are VERY pleased with the fileserver, it's quite stable, no crashes in the 6 months we've been running them.
Our 15 Solaris clients are running OpenAFS, we are very pleased with
this one. (We plan to have about 100 Solaris hosts in a few months.)
</p>
-</dd>
-</dl>
+
+
<h2>Chris Huebsch, volunteer administrator for Dr. Wilhelm Andre Gymnasium, Chemnitz, Germany, shared:</h2>
-<dl>
-<dd>
+
+
<p>
I first used AFS in 1995 during my first year as a student. Now I am a
member of the academic staff at Chemnitz University of Technology.
connected with 128 kbit). We hope that by replicating a ro-db-server and
many volumes to that server will be sufficient to keep things working.
</p>
-</dd>
-</dl>
+
+
<h2>Derrick Brashear, Carnegie Mellon University Computing Services Division and OpenAFS volunteer, shared:</h2>
-<dl>
-<dd>
+
+
<p>
Computing Services rolled out OpenAFS to both clients and servers early, and now runs modern versions on Solaris 2.6 servers, as well as on Solaris 7 and 8 and locally-updated Redhat 6.1 clients. Additionally, the OpenAFS Windows NT client is being tested general rollout.</p>
<p>
Despite often using pre-release versions of the software few problems have been experienced, and fixes have generally been quickly forthcoming, either internally done and contributed back to the community, or thanks to the many active contributors to the ongoing success of the project.
</p>
-</dd>
-</dl>
+
+
<h2>Matthew E. Hoskins, New Jersey Institute of Technology University Information Systems, shared:</h2>
-<dl>
-<dd>
+
+
<p>
University Information Systems (UIS) started testing OpenAFS about 7
months ago for the purpose of binary standardization across our web,
and we are starting to roll our cell into production. We currently have
~140gb of vicep space across four servers (2 linux, 2 solaris8). The
cell gracefully handled two events of failed disks without interruption.
+</p>
<p>
OpenAFS has and will continue to help me keep our 45 web, application,
and database servers running the same versions of binaries and scripts.
+</p>
<p>
As our programmers learn of the features and capabilities of OpenAFS
they increasingly want their workstations added as clients also (mixture
of sun and linux boxes). As trust builds in OpenAFS we will also start
moving production data into volumes rather than local storage. This will
allow applications to "float" between nodes as necessary.
+</p>
<p>
Our site has been a long time Transarc customer for our academic cell
(2.6Tb, 6 fileservers, 17000 users, 100s of workstations), The OpenAFS
project and its contributors are breathing new life into a wonderful
technology.
+</p>
<p>
Some features that would be of value:
+</p>
<ul>
<li>OpenAFS documentation on kaserver -> krb5 migration</li>
<li>OpenAFS documentation on setup for new krb5 cells</li>
I am working on converting all my various perl scripts into a perl
module so i can contribute it and open it up for community development.
</p>
-<dd>
-<p>
-</dl>
+
+
+
<h1>Sharing your OpenAFS Story</h1>
Please contact the <a href="mailto:openafs-gatekeepers@openafs.org">OpenAFS
Gatekeepers</a> to share your success story.<div id="footer"><hr>
<ul>
<li><div><p><strong>The
</strong>
- <a href="mailto:openafs-info@openafs.org?subject=Request for Assistance with OpenAFS">
+ <a href="mailto:openafs-info@openafs.org?subject=Request%20for%20Assistance%20with%20OpenAFS">
<strong>openafs-info@openafs.org</strong></a><strong> mailing list</strong></p>
<p>This mailing list is a general all-purpose forum for discussing
any aspect of using and deploying OpenAFS. <a href="https://lists.openafs.org/pipermail/openafs-info/">Archives</a>
you would like to meet other OpenAFS users and interact in real time,
this is often a good place to start.</p></div></li>
<li><div><p><strong>OpenAFS Bug Reporting</strong></p><p>
- <a href="mailto:openafs-bugs@openafs.org?subject=Bug Report">Bug Reports</a> and
- <a href="mailto:openafs-bugs@openafs.org?subject=Feature Request">Feature Requests</a> may be filed with the development community.
+ <a href="mailto:openafs-bugs@openafs.org?subject=Bug%20Report">Bug Reports</a> and
+ <a href="mailto:openafs-bugs@openafs.org?subject=Feature%20Request">Feature Requests</a> may be filed with the development community.
Open bugs and requests can be
<a href="https://rt.central.org/rt/Search/Results.html?Order=ASC&DefaultQueue=10&Query=Queue%20%3D%20%27openafs-bugs%27%20AND%20(Status%20%3D%20%27open%27%20OR%20Status%20%3D%20%27new%27)&Rows=50&OrderBy=id&Page=1&Format=&user=guest&pass=guest">
reviewed</a>. All requests are addressed as time permits by the
</p></li>
<li><p>
The organization is open to new contracts and customers.
-</li></p>
+</p></li>
</ol>
<div id="footer"><hr>
<link href="/openafs.css" rel="stylesheet" type="text/css">
</head>
<body class="top">
-<table class="top" width="100%" cellspacing="0" border="0" cellpadding="0">
+<table class="top" width="100%" cellspacing="0" border="0" cellpadding="0" summary="">
<tr><th class="top" width=250>
<img src="/images/openafs-logo.jpg" width="216" height="150" alt="OpenAFS Logo">
</th>
-<td class="top" align=right valign=top><table>
+<td class="top" align=right valign=top><table summary="">
<tr>
<td class="top" align=right>
<a href="https://indico.cern.ch/conferenceDisplay.py?confId=271400" title="European AFS and Kerberos Conference 2014" target="_blank">European AFS and Kerberos Conference 2014</a><br>
+<!DOCTYPE html>
<html>
<head>
has the appropriate permissions. All in all, the user should not notice
that AFS is not a native part of the operating system and the user interface.</p>
<p>Mockups of proposals for the Explorer Shell extension can be found at
-<a href="http://www.secure-endpoints.com/openafs-windows-roadmap.html#shell extensions">
+<a href="http://www.secure-endpoints.com/openafs-windows-roadmap.html#shell%20extensions">
http://www.secure-endpoints.com/openafs-windows-roadmap.html#shell extensions</a>.
This project consists of multiple components that can be successfully
implemented one at a time. The successful completion of this project does
<li><a href="#whichversion">How to Decide Which Version to Install</a></li>
<li><a href="#signatures">Digital Signatures</a></li>
<li><a href="#features-release">OpenAFS for Windows 1.7.31 (aka 1.7.3100)</a></li>
+<li>
<ul>
<li><a href="#1_7_features">Features</a>
<li><a href="#1_7_docs">Documentation</a>
<li><a href="#1_7_32bit_downloads">32-bit Downloads</a>
</ul>
+</li>
<li><a href="#maintenance-release">OpenAFS for Windows 1.6.1 (aka 1.6.0104)</a></li>
+<li>
<ul>
<li><a href="#1_6_features">Features</a>
<li><a href="#1_6_docs">Documentation</a>
<li><a href="#1_6_32bit_downloads">32-bit Downloads</a>
<li><a href="#1_6_64bit_downloads">64-bit Downloads</a>
</ul>
+</li>
<li><a href="#kfw">Kerberos for Windows (MIT or Heimdal)</a></li>
<li><a href="#hotfix">Microsoft Hot Fixes</a></li>
<p>
Installers are produced and signed by <a href="https://www.secure-endpoints.com" title="Secure Endpoints Inc.">
Secure Endpoints Inc.</a> or <a href="http://www.your-file-system.com" title="Your File System Inc.">Your File System Inc.</a>.
-<b>Note: Your File System, Inc. was renamed to <a href="https://www.auristor.com" title=AuriStor, Inc.">AuriStor, Inc.</a> on 28 Oct 2015.</b>
+<b>Note: Your File System, Inc. was renamed to <a href="https://www.auristor.com" title="AuriStor, Inc.">AuriStor, Inc.</a> on 28 Oct 2015.</b>
If the signature is missing do not complete the installation process and send e-mail to
-<a href="mailto:openafs-security@openafs.org?subject=Missing or Incorrect Digital Signature">openafs-security@openafs.org</a>
+<a href="mailto:openafs-security@openafs.org?subject=Missing%20or%20Incorrect%20Digital%20Signature">openafs-security@openafs.org</a>
<br>
<h2><a name="features-release">OpenAFS for Windows 1.7.31 (1.7.3100)</a></h2>
<h2><a name="maintenance-release">OpenAFS for Windows 1.6.1 (1.6.0104)</a></h2>
-(updated 28 March 2012)<p> <img border="0" src="images/wVista-Works.png" width="209" height="93"></p>
+(updated 28 March 2012)<p> <img border="0" src="images/wVista-Works.png" width="209" height="93" alt=""></p>
<h3><a name="1_6_features"></a>Significant Changes since 1.6.0b:</h3>
<ul>
<li>"fs setserverprefs -vl" works again</li>
UNC paths</li>
<li>Windows Vista Specific Issues<ul>
<li>The help files provided with OpenAFS are in .HLP format.
- <a href="http://www.microsoft.com/downloads/details.aspx?FamilyID=6ebcfad9-d3f5-4365-8070-334cd175d4bb&DisplayLang=en">WinHlp32.exe must be
+ <a href="http://www.microsoft.com/downloads/details.aspx?FamilyID=6ebcfad9-d3f5-4365-8070-334cd175d4bb&DisplayLang=en">WinHlp32.exe must be
downloaded separately from Microsoft.</a> Secure Endpoints Inc. is funding the
development of compatible HtmlHelp (.CHM) files.</li>
</ul></li>
git://git.openafs.org / openafs-web.git / commitdiff