Bureaucrats, Interface administrators, Administrators (Semantic MediaWiki), Curators (Semantic MediaWiki), Editors (Semantic MediaWiki), Administrators, Widget editors
23,423
edits
MCP-CMS: Difference between revisions
From Cibernética Americana
no edit summary
No edit summary |
No edit summary |
||
| Line 63: | Line 63: | ||
</span> | </span> | ||
</blockquote> | </blockquote> | ||
<button type="button" class="collapsible">hide/show</button> <div class="content"></div> | <button type="button" class="collapsible">hide/show</button> <div class="content"> | ||
<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> | |||
<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> | |||
Shell scope (local or MCP or DCP) scope is determined by the nature of the node and privilege level.<br> GHC is the assumed | |||
for haskell. Lisp and prolog implementations are variable, and multiple can be combined. | |||
</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> can be directly invoked with ssh @ <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> where the port is system provided in the user's DCMS account profile </pre> | |||
</li> | |||
</ul></tt> | |||
</div> | |||
<blockquote style="position: relative;top: -60px;">Roadmap | <blockquote style="position: relative;top: -60px;">Roadmap | ||
