Bureaucrats, Interface administrators, Administrators (Semantic MediaWiki), Curators (Semantic MediaWiki), Editors (Semantic MediaWiki), Administrators, Widget editors
23,422
edits
MCP-CMS: Difference between revisions
From Cibernética Americana
Jump to navigationJump to search
no edit summary
No edit summary |
No edit summary |
||
| Line 118: | Line 118: | ||
Aside from the modification for the MCP machine model, it is otherwise just zsh however the following (mode) commands are available to establish different shell behaviour in support of the KEE: | Aside from the modification for the MCP machine model, it is otherwise just zsh however the following (mode) commands are available to establish different shell behaviour in support of the KEE: | ||
<ul><li><b>shcl</b> </li><li><b>shhs</b></li><li><b>upsh</b></li></ul> | <ul><li><b>shcl</b> </li><li><b>shhs</b></li><li><b>upsh</b></li></ul> | ||
which have the lisp, haskell, and prolog natures, respectively. <b>shcl</b> is the only one which is a full shell, the others are ways to do posix shell things in lang. While in general Lisp and prolog implementations can vary, shcl and upsh require sbcl and swipl, respectively. | which have the lisp, haskell, and prolog natures, respectively. <b>shcl</b> is the only one which is a full shell, the others are ways to do posix shell things in lang. While in general Lisp and prolog implementations can vary, shcl and upsh require sbcl and swipl, respectively. During early dev, before DCP WFL is available DCP is implemented in these shells plus MCP. | ||
<b>mcpcms</b> can be accessed with ssh using the following script. Using the FQDSAgentName syntax is equivalent to what the launch link does in an AKPERSONs session.<pre><tt>#!/usr/bin/bash | <b>mcpcms</b> can be accessed with ssh using the following script. Using the FQDSAgentName syntax is equivalent to what the launch link does in an AKPERSONs session.<pre><tt>#!/usr/bin/bash | ||
# save as <fileName> and invoke with <fileName> <connect-spec> where | # save as <fileName> and invoke with <fileName> <connect-spec> where | ||
