MCP-CMS: Difference between revisions

From Cibernética Americana
Jump to navigationJump to search
No change in size ,  2 January 2022
no edit summary
No edit summary
No edit summary
Line 66: Line 66:
         Operators use CANDE for MCP shell ops which can use:
         Operators use CANDE for MCP shell ops which can use:
         <ul>
         <ul>
         <li><p style="width: 60%;">mcpcms, the default, a custom zsh.<br><br> Only mcpcms need be set in /etc/shells, the others execute as
         <li><p style="width: 60%;">mcpcms, the default, a custom zsh.</p> </li>
            commands in a mcpcms session, and only shcl gives a shell like live command line. The other two require a user supplied
            haskell or prolog script, and are not general interactive shells unless that script provides that functionality.</p> </li>
         <br>or<br>
         <br>or<br>
         <li>shcl, common lisp nature</li>
         <li>shcl, common lisp nature</li>
Line 74: Line 72:
         <li>upsh, prolog nature</li>
         <li>upsh, prolog nature</li>
         </ul>
         </ul>
         <blockquote>
         <blockquote> Only mcpcms need be set in /etc/shells, the others execute as
            commands in a mcpcms session, and only shcl gives a shell like live command line. The other two require a user supplied
            haskell or prolog script, and are not general interactive shells unless that script provides that functionality.<br><br>
         Shell scope (local or MCP or DCP) scope is determined by the nature of the node and privilege level.<br> GHC is the haskell implementation. Lisp and prolog implementations are variable, and multiple can be combined.
         Shell scope (local or MCP or DCP) scope is determined by the nature of the node and privilege level.<br> GHC is the haskell implementation. Lisp and prolog implementations are variable, and multiple can be combined.
         </blockquote>
         </blockquote>

Navigation menu