<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="FeedCreator 1.8" -->
<?xml-stylesheet href="http://docs.hpc.udel.edu/lib/exe/css.php?s=feed" type="text/css"?>
<rss version="2.0">
    <channel xmlns:g="http://base.google.com/ns/1.0">
        <title>hpc documentation - technical:cc3-build</title>
        <description></description>
        <link>http://docs.hpc.udel.edu/</link>
        <lastBuildDate>Tue, 14 Apr 2026 19:41:43 +0000</lastBuildDate>
        <generator>FeedCreator 1.8</generator>
        <image>
            <url>http://docs.hpc.udel.edu/_media/wiki/dokuwiki.svg</url>
            <title>hpc documentation</title>
            <link>http://docs.hpc.udel.edu/</link>
        </image>
        <item>
            <title>efi</title>
            <link>http://docs.hpc.udel.edu/technical/cc3-build/efi</link>
            <description>Working with EFI

Previous clusters&#039; nodes used BIOS hardware interfaces.  Nodes in CC3 prefer the use of EFI, to the point of requiring it in some cases (e.g. the in-rack storage server nodes).  A basic knowledge of the EFI shell was invaluable in addressing hardware issues in nodes; summarized here is use of the EFI shell on the OCP2930w nodes.</description>
            <author>anonymous@undisclosed.example.com (Anonymous)</author>
            <pubDate>Fri, 27 Apr 2018 16:45:52 +0000</pubDate>
        </item>
        <item>
            <title>start</title>
            <link>http://docs.hpc.udel.edu/technical/cc3-build/start</link>
            <description>Community Cluster 3 Build Docs

Throughout the process of bringing CC3 online for our users there are technical challenges that require research, design, and testing of solutions to problems.  Some of those problems may affect others.  Collected here is documentation generated by the deployment of our third community cluster.</description>
            <author>anonymous@undisclosed.example.com (Anonymous)</author>
            <pubDate>Fri, 27 Apr 2018 16:46:57 +0000</pubDate>
        </item>
    </channel>
</rss>
