MCP-CMS: Difference between revisions

From Cibernética Americana
Jump to navigationJump to search
194 bytes removed ,  2 January 2022
no edit summary
No edit summary
No edit summary
Line 64: Line 64:
         </blockquote>
         </blockquote>
     <button type="button" class="collapsible">hide/show</button>  
     <button type="button" class="collapsible">hide/show</button>  
  <div class="content">
<div class="content">
   <blockquote>
   <blockquote>
         The namestyle is a homage to  
         The namestyle is a homage to <a href=https://en.wikipedia.org/wiki/MCP>MCP</a> and <a href=https://en.wikipedia.org/wiki/Conversational_Monitor_System>VM/CMS</a> .
        <a href=https://en.wikipedia.org/wiki/MCP>MCP</a> and <a href=https://en.wikipedia.org/wiki/Conversational_Monitor_System>VM/CMS</a> .
        While initially only linux is supported, more kernel OS support is intended. MCP communicates with clients via an MCS, and operators one wrapping the ssh protocol.
        While initially only linux is supported, more kernel OS support is intended.
        The end command processor is just the assigned shell for the ssh connection which can be:
  </blockquote>
  <blockquote>
    MCP communicates with clients via an MCS, and operators use a command processing one. The end command processor is
    just the assigned shell for a ssh connection to the node in the MCP which can be:
         <ul>
         <ul>
         <li>shcl, common lisp nature</li>
         <li>shcl, common lisp nature</li>
Line 78: Line 74:
         <li>upsh, prolog nature</li>
         <li>upsh, prolog nature</li>
         <br>or<br>
         <br>or<br>
         <li><p style="width: 60%;">CMS, the default nature for mcpcms, which is zsh modified for DCP/MCP/MCS.<br><br> Only mcpcms can be set in /etc/shells, the others execute as
         <li><p style="width: 60%;">mcpcms, the default nature for mcpcms, which is a custom zsh.<br><br> Only mcpcms can be set in /etc/shells, the others execute as
             commands in a mcp shell, and only shcl gives a live default command line like fish under standard zsh. The other two require a user supplied
             commands in a mcp shell, and only shcl gives a shell like live command line. The other two require a user supplied
             hs or pl script, and are not general interactive shells unless that script provides that functionality.</p> </li>
             haskell or prolog script, and are not general interactive shells unless that script provides that functionality.</p> </li>
         </ul>
         </ul>
         <blockquote>
         <blockquote>
Line 86: Line 82:
         for haskell. Lisp and prolog implementations are variable, and multiple can be combined.
         for haskell. Lisp and prolog implementations are variable, and multiple can be combined.
         </blockquote>
         </blockquote>
         The CMS level is always present, the others are outer shells adapted for the domain space knowledge engineering context.<br>
         The mcpcms level is always present, the others are outer shells adapted for the domain space knowledge engineering context.<br>
         Although adapted for MCP, I try to keep them close to the standard versions, as generic lang specific outer shells.<br>
         Although diverged for DS, an effort will be made to track changes in still vital original lang specific shells.<br>
         My preferred <a href=https://en.wikipedia.org/wiki/Domain_engineering>DDD</a> uses the three HOLs&sup2; listed but the bash level is appropriate for
         The KEE uses the three HOLs&sup2; listed but the bash/zsh level is appropriate for regular unix  shell ops with MCP.
        shell ops with MCP unaware software, CANDE, and WFL jobs.
     </blockquote>
     </blockquote>
     <b>mcpcms</b> linux command line invocation uses:  
     <b>mcpcms</b> linux command line invocation uses:  
Line 101: Line 96:
     </tt>  
     </tt>  
     </div>
     </div>
         <blockquote style="position: relative;top: -60px;">Roadmap
         <blockquote style="position: relative;top: -60px;">Roadmap
         <ul>
         <ul>

Navigation menu