<!DOCTYPE html>
<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <p>Dear Andreas,</p>
    <p>thank you for the suggestion, I have signed up for an account for
      the wiki and the mailing list.<br>
    </p>
    <p>I agree that adding updates to the wiki would be even better,
      hence my email to the lustre discussion mailing list. My intention
      was for it to be picked up by those in charge of the wiki - while
      in parallel ensuring that the information is available and wont
      get lost in the meantime.<br>
      Contributing directly myself is another option.<br>
    </p>
    <p>There is significant overlap across distribution releases with
      specific details changing (kernel version numbers, the odd package
      here and there, small name changes).<br>
      How to best present and organise this so that it is scalable is
      actually quite a tricky question. Right now I have take then
      approach of two nearly identical markdown files with appropriate
      adaptions, however this doesn't scale well in the long term. <br>
    </p>
    <p>Kind regards<br>
      Detlev</p>
    <p></p>
    <div class="moz-cite-prefix">On 10/4/24 10:16, Andreas Dilger wrote:<br>
    </div>
    <blockquote type="cite"
      cite="mid:E3FE05C1-97DE-4575-B5E7-24F41EF43341@whamcloud.com">
      <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
      Hi Detlev,
      <div class="">thank you for taking the time to update the
        documentation.  This is valuable for many others in the
        community.<br class="">
        <div class=""><br class="">
        </div>
        <div class="">Rather than put the updated instructions in your
          personal GitHub repository, it would be better to update the
          pages on the wiki (if the changes are minor), or create new
          pages (if there are significant differences from the old
          pages).</div>
        <div class=""><br class="">
        </div>
        <div class="">Having the updated pages will be much more visible
          to other Lustre users in the future.  There is a Lustre
          Documentation Working Group that is just in the process of
          updating pages on the wiki, and would welcome your
          contribution.  You can register for an account directly on the
          wiki.</div>
        <div class=""><br class="">
        </div>
        <div class="">For more information about the DWG, please see:</div>
        <div class=""><a
            href="https://wiki.opensfs.org/Documentation_Working_Group"
            class="moz-txt-link-freetext" moz-do-not-send="true">https://wiki.opensfs.org/Documentation_Working_Group</a></div>
        <div class=""><br class="">
        </div>
        <div class="">Cheers, Andreas<br class="">
          <div><br class="">
            <blockquote type="cite" class="">
              <div class="">On Oct 4, 2024, at 01:45, Detlev Conrad
                Mielczarek <<a
                  href="mailto:detlev.conrad.mielczarek@hu-berlin.de"
                  class="moz-txt-link-freetext" moz-do-not-send="true">detlev.conrad.mielczarek@hu-berlin.de</a>>
                wrote:</div>
              <br class="Apple-interchange-newline">
              <div class="">
                <div class="">[You don't often get email from <a
                    href="mailto:detlev.conrad.mielczarek@hu-berlin.de"
                    class="moz-txt-link-freetext" moz-do-not-send="true">
                    detlev.conrad.mielczarek@hu-berlin.de</a>. Learn why
                  this is important at <a
                    href="https://aka.ms/LearnAboutSenderIdentification"
                    class="moz-txt-link-freetext" moz-do-not-send="true">
                    https://aka.ms/LearnAboutSenderIdentification</a> ]<br
                    class="">
                  <br class="">
                  Dear Mailing List Members,<br class="">
                  <br class="">
                  we use a lustre file server internally and were
                  looking to set up a test<br class="">
                  environment where we can experiment.<br class="">
                  As lustre server rpms are not available for all Linux
                  operating systems,<br class="">
                  I have spent some time adapting the existing
                  instructions (for Rocky 8.7<br class="">
                  from <a
href="https://wiki.whamcloud.com/pages/viewpage.action?pageId=258179277"
                    class="moz-txt-link-freetext" moz-do-not-send="true">
https://wiki.whamcloud.com/pages/viewpage.action?pageId=258179277</a> )<br
                    class="">
                  to Rocky 8.10 as well as Rocky 9.4.<br class="">
                  <br class="">
                  These have been made available in a github repository
                  and I though that<br class="">
                  my experiences/observations may be of interest to
                  provide a tutorial for<br class="">
                  the more recent Rocky Updates on the wiki.<br class="">
                  The text is available here:<br class="">
                  <a
href="https://github.com/DetlevCM/lustre-build-instructions"
                    class="moz-txt-link-freetext" moz-do-not-send="true">https://github.com/DetlevCM/lustre-build-instructions</a><br
                    class="">
                  <br class="">
                  Kind regards<br class="">
                  Detlev<br class="">
                  <br class="">
                  --<br class="">
                  Detlev Conrad Mielczarek - HPC Team<br class="">
                  (deutsch, english, français)<br class="">
                  Humboldt-Universität zu Berlin<br class="">
                  Computer- und Medienservice<br class="">
                  10099 Berlin, Germany<br class="">
                  email: <a class="moz-txt-link-abbreviated" href="mailto:detlev.conrad.mielczarek@hu-berlin.de">detlev.conrad.mielczarek@hu-berlin.de</a><br
                    class="">
                  <br class="">
                  _______________________________________________<br
                    class="">
                  lustre-discuss mailing list<br class="">
                  <a class="moz-txt-link-abbreviated" href="mailto:lustre-discuss@lists.lustre.org">lustre-discuss@lists.lustre.org</a><br class="">
<a class="moz-txt-link-freetext" href="http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org">http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org</a><br
                    class="">
                </div>
              </div>
            </blockquote>
          </div>
          <br class="">
          <div class="">
            <div dir="auto"
style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;"
              class="">
              <div dir="auto"
style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;"
                class="">
                <div dir="auto"
style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;"
                  class="">
                  <div dir="auto"
style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;"
                    class="">
                    <div dir="auto"
style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;"
                      class="">
                      <div dir="auto"
style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;"
                        class="">
                        <div>Cheers, Andreas</div>
                        <div>--</div>
                        <div>Andreas Dilger</div>
                        <div>Lustre Principal Architect</div>
                        <div>Whamcloud</div>
                        <div><br class="">
                        </div>
                        <div><br class="">
                        </div>
                        <div><br class="">
                        </div>
                      </div>
                    </div>
                  </div>
                </div>
              </div>
              <br class="Apple-interchange-newline">
            </div>
            <br class="Apple-interchange-newline">
            <br class="Apple-interchange-newline">
          </div>
          <br class="">
        </div>
      </div>
    </blockquote>
    <pre class="moz-signature" cols="72">-- 
Detlev Conrad Mielczarek - HPC Team
(deutsch, english, français)
Humboldt-Universität zu Berlin
Computer- und Medienservice
10099 Berlin, Germany
email: <a class="moz-txt-link-abbreviated" href="mailto:detlev.conrad.mielczarek@hu-berlin.de">detlev.conrad.mielczarek@hu-berlin.de</a></pre>
  </body>
</html>