Anonymous

MCP-CMS: Difference between revisions

From Cibernética Americana
no edit summary
No edit summary
No edit summary
Line 67: Line 67:
         <ul>
         <ul>
         <li><p style="width: 60%;">mcpcms, the default, a custom zsh.</p> </li>
         <li><p style="width: 60%;">mcpcms, the default, a custom zsh.</p> </li>
         and optionally
         and any of <br>
         <li>shcl, common lisp nature</li>
         <li>shcl (common lisp nature)</li>
         <li>HsShellScript, haskell nature</li>
         <li>HsShellScript (haskell nature)</li>
         <li>upsh, prolog nature</li>
         <li>upsh (prolog nature)</li>
         </ul>
         </ul>
         <blockquote> Only mcpcms need be set in /etc/shells, the others execute as
         <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
             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.  
             haskell or prolog script, and are not general interactive shells unless user script includes that functionality.  
         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>