|
|
| Line 63: |
Line 63: |
| </span> | | </span> |
| </blockquote> | | </blockquote> |
| <button type="button" class="collapsible">hide/show</button> | | <button type="button" class="collapsible">hide/show</button> <div class="content"></div> |
| <div class="content"> <blockquote> | | |
| MCP shells may have any one of the following natures:
| |
| <ul>
| |
| <li>shcl, common lisp nature</li>
| |
| <li>HsShellScript, haskell nature</li>
| |
| <li>upsh, prolog nature</li>
| |
| <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
| |
| 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
| |
| hs or pl script, and are not general interactive shells unless that script provides that functionality.</p> </li>
| |
| </ul>
| |
| <blockquote>
| |
| Shells have either MCP (single linux host) or DCP (whole cluster) scope, ip shells are limited to the former.<br> GHC and SWI are assumed
| |
| for haskell and prolog, but lisp can be any combination of Allegro, CCL, (user supplied) or sbcl (the default).
| |
| </blockquote>
| |
| The CMS 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>
| |
| My preferred <a href=https://en.wikipedia.org/wiki/Domain_engineering>DDD</a> uses the three HOLs² listed but the bash level is appropriate for
| |
| shell ops with MCP unaware software, CANDE, and WFL jobs.
| |
| </blockquote><blockquote>
| |
| 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> .
| |
| <br><br>
| |
| While initially only linux is supported, more kernel OS support is intended.
| |
| </blockquote>
| |
| <br><b>mcpcms</b> may be accessed at the command line @ <station-name> where | |
| <tt>
| |
| <ul>
| |
| <li style="padding: -2px;"><pre><station-name> ::= ipV6Address[port] | ipV4Address[port] | FQDSAgentName </pre></li>
| |
| <li><pre>FQDSAgentName ::= <sameboatUserid>@<sameboatDomain>:<port></pre></li>
| |
| <li><pre>examples
| |
| [2601:603:1481:30a0:7a4f:21f:3026:6a5e]:50142
| |
| maryh@bufyyz.sameboat.live:50142
| |
| maryh@maryh.sameboat
| |
| 94.68.134.5
| |
| | |
| where the port is system assigned in the last two
| |
| </pre>
| |
| </li>The IPV6 and
| |
| suffix-free domain forms require DS routing and peering, respectively. Sessions launched by ip do not persist and are strictly contained within the agent's session. </ul></tt></pre>
| |
| </div>
| |
| <blockquote style="position: relative;top: -60px;">Roadmap | | <blockquote style="position: relative;top: -60px;">Roadmap |
| <ul> | | <ul> |
