The new emulator address will be em.prirun.com, and since I own that domain name, it won't be changing again. Still have to add the port number to get the specific version of Primos you want (8001 and up).Thank you Jim for making these time travel journeys possible. I just tried port 8005 and was pleased to see Rev 23.4.Y2K.R1 where DSM is running. This is great. However, by default it looks like DSM doesn't let ordinary users do anything. I can't even
Jim
On Thursday, 28 January 2016 17:22:59 UTC, Jim Wilcoxson wrote:run innocuous commands like list_process, list_cvs etc. Can the permissions be slightly loosened please? I expected that ordinary users could use the SIM (System Information and Metering) commands.
The new emulator address will be em.prirun.com, and since I own that domain name, it won't be changing again. Still have to add the port number to get the specific version of Primos you want (8001 and up).Thank you Jim for making these time travel journeys possible. I just tried port 8005 and was pleased to see Rev 23.4.Y2K.R1 where DSM is running. This is great. However, by default it looks like DSM doesn't let ordinary users do anything. I can't even
Jim
On Sunday, September 11, 2016 at 3:52:46 AM UTC-4, marlow...@gmail.com wrote:even run innocuous commands like list_process, list_cvs etc. Can the permissions be slightly loosened please? I expected that ordinary users could use the SIM (System Information and Metering) commands.
On Thursday, 28 January 2016 17:22:59 UTC, Jim Wilcoxson wrote:
The new emulator address will be em.prirun.com, and since I own that domain name, it won't be changing again. Still have to add the port number to get the specific version of Primos you want (8001 and up).Thank you Jim for making these time travel journeys possible. I just tried port 8005 and was pleased to see Rev 23.4.Y2K.R1 where DSM is running. This is great. However, by default it looks like DSM doesn't let ordinary users do anything. I can't
Jim
Hi Andrew! I don't know anything about DSM, but poked around a little bit in config_dsm and ran across the user access section. No idea how this stuff works, but the current config looks like this:
Do you want to list all the user access definitions ? yes
User access definition ALIEN$ is:
User/ACL group .ANY_USER$ from location(s):
.ALIEN_NODES$
Function/function group: STATUS_DSM is allowed on node/node groups:
.GROUP$
User access definition DSM_ADMINISTRATOR$ is:
User/ACL group SYSTEM from location(s):
.GROUP$
Function/function group: .ANY_FUNCTION$ is allowed on node/node groups:
.ANY_NODE$
User access definition DSM_OPERATOR$ is:
User/ACL group SYSTEM from location(s):
LOCAL$
Function/function group: .RESUS$ is allowed on node/node groups:
.ANY_NODE$
Function/function group: .SIM$ is allowed on node/node groups:
.ANY_NODE$
User access definition DTB_USER$ is:
User/ACL group .DTB$ from location(s):
.ANY_NODE$
Function/function group: .DTB$ is allowed on node/node groups:
.ANY_NODE$
I have one user, GUEST, setup on this emulator. Do I just add group .DTB$ to that user? Does that let it do crazy things, or just "read only" commands?
[snip]Thank you Jim for making these time travel journeys possible. I just tried port 8005 and was pleased to see Rev 23.4.Y2K.R1 where DSM is running. This is great. However, by default it looks like DSM doesn't let ordinary users do anything.
Did they offer brain surgeon classes in DSM? The tag line could have been:
"DSM: Power beyond comprehension"
On Sunday, September 11, 2016 at 3:01:35 PM UTC-4, Andrew Marlow wrote:even run innocuous commands like list_process, list_cvs etc. Can the permissions be slightly loosened please? I expected that ordinary users could use the SIM (System Information and Metering) commands.
On Sunday, 11 September 2016 16:16:03 UTC+1, Jim Wilcoxson wrote:
On Sunday, September 11, 2016 at 3:52:46 AM UTC-4, marlow...@gmail.com wrote:
On Thursday, 28 January 2016 17:22:59 UTC, Jim Wilcoxson wrote:
The new emulator address will be em.prirun.com, and since I own that domain name, it won't be changing again. Still have to add the port number to get the specific version of Primos you want (8001 and up).Thank you Jim for making these time travel journeys possible. I just tried port 8005 and was pleased to see Rev 23.4.Y2K.R1 where DSM is running. This is great. However, by default it looks like DSM doesn't let ordinary users do anything. I can't
Jim
include access to RESUS. the RESUS command lets you become the system console!Hi Andrew! I don't know anything about DSM, but poked around a little bit in config_dsm and ran across the user access section. No idea how this stuff works, but the current config looks like this:
Do you want to list all the user access definitions ? yes
User access definition ALIEN$ is:
User/ACL group .ANY_USER$ from location(s):
.ALIEN_NODES$
Function/function group: STATUS_DSM is allowed on node/node groups:
.GROUP$
User access definition DSM_ADMINISTRATOR$ is:
User/ACL group SYSTEM from location(s):
.GROUP$
Function/function group: .ANY_FUNCTION$ is allowed on node/node groups:
.ANY_NODE$
User access definition DSM_OPERATOR$ is:
User/ACL group SYSTEM from location(s):
LOCAL$
Function/function group: .RESUS$ is allowed on node/node groups:
.ANY_NODE$
Function/function group: .SIM$ is allowed on node/node groups:
.ANY_NODE$
User access definition DTB_USER$ is:
User/ACL group .DTB$ from location(s):
.ANY_NODE$
Function/function group: .DTB$ is allowed on node/node groups:
.ANY_NODE$
I have one user, GUEST, setup on this emulator. Do I just add group .DTB$ to that user? Does that let it do crazy things, or just "read only" commands?
The DSM_OPERATORS group is close to what is wanted but it has access to the RESUS command, which is normally denied to ordinary users. So you will need to create a new user access definition, say DSM_USER, which is like DSM_OPERATOR but does not
So I want to create user access DSM_USER, add function group .SIM$ to it, and then say User/ACL group GUEST from location LOCAL$. .SIM$ includes these functions:
Function group .SIM$ contains:
LIST_ASSIGNED_DEVICES, LIST_ASYNC, LIST_COMM_CONTROLLERS, LIST_CONFIG,
LIST_DISKS, LIST_LAN_NODES, LIST_MEMORY, LIST_PRIMENET_LINKS,
LIST_PRIMENET_NODES, LIST_PRIMENET_PORTS, LIST_PROCESS, LIST_SEMAPHORES,
LIST_SYNC, LIST_UNITS, LIST_VCS, PRIVATE_LOGGER
What is PRIVATE_LOGGER? Is it okay, or do I need to create a new function group without that?
Did they offer brain surgeon classes in DSM? The tag line could have been:
"DSM: Power beyond comprehension"
On Tuesday, 13 September 2016 08:48:38 UTC+1, Andrew Marlow wrote:
[snip]
[snip]Thank you Jim for making these time travel journeys possible. I just tried port 8005 and was pleased to see Rev 23.4.Y2K.R1 where DSM is running. This is great. However, by default it looks like DSM doesn't let ordinary users do anything.
Did they offer brain surgeon classes in DSM? The tag line could have been:
"DSM: Power beyond comprehension"
I would still like to use it and I bet several of my former colleagues at Willen Lake (UK) would like to as well. Please let us know when you have managed to make the changes using that infamous CONFIG_DSM comand, thanks.
On Sunday, 11 September 2016 16:16:03 UTC+1, Jim Wilcoxson wrote:even run innocuous commands like list_process, list_cvs etc. Can the permissions be slightly loosened please? I expected that ordinary users could use the SIM (System Information and Metering) commands.
On Sunday, September 11, 2016 at 3:52:46 AM UTC-4, marlow...@gmail.com wrote:
On Thursday, 28 January 2016 17:22:59 UTC, Jim Wilcoxson wrote:
The new emulator address will be em.prirun.com, and since I own that domain name, it won't be changing again. Still have to add the port number to get the specific version of Primos you want (8001 and up).Thank you Jim for making these time travel journeys possible. I just tried port 8005 and was pleased to see Rev 23.4.Y2K.R1 where DSM is running. This is great. However, by default it looks like DSM doesn't let ordinary users do anything. I can't
Jim
include access to RESUS. the RESUS command lets you become the system console!Hi Andrew! I don't know anything about DSM, but poked around a little bit in config_dsm and ran across the user access section. No idea how this stuff works, but the current config looks like this:
Do you want to list all the user access definitions ? yes
User access definition ALIEN$ is:
User/ACL group .ANY_USER$ from location(s):
.ALIEN_NODES$
Function/function group: STATUS_DSM is allowed on node/node groups:
.GROUP$
User access definition DSM_ADMINISTRATOR$ is:
User/ACL group SYSTEM from location(s):
.GROUP$
Function/function group: .ANY_FUNCTION$ is allowed on node/node groups:
.ANY_NODE$
User access definition DSM_OPERATOR$ is:
User/ACL group SYSTEM from location(s):
LOCAL$
Function/function group: .RESUS$ is allowed on node/node groups:
.ANY_NODE$
Function/function group: .SIM$ is allowed on node/node groups:
.ANY_NODE$
User access definition DTB_USER$ is:
User/ACL group .DTB$ from location(s):
.ANY_NODE$
Function/function group: .DTB$ is allowed on node/node groups:
.ANY_NODE$
I have one user, GUEST, setup on this emulator. Do I just add group .DTB$ to that user? Does that let it do crazy things, or just "read only" commands?
The DSM_OPERATORS group is close to what is wanted but it has access to the RESUS command, which is normally denied to ordinary users. So you will need to create a new user access definition, say DSM_USER, which is like DSM_OPERATOR but does not
[snip]I would still like to use it and I bet several of my former colleagues at Willen Lake (UK) would like to as well. Please let us know when you have managed to make the changes using that infamous CONFIG_DSM comand, thanks.
Well, I tried. I created "user access definition" DSM_USER$, with "function group" .SIM$, and added user GUEST to it. Then went to save it:
Geez, this thing is really terrible. Sorry Andrew!
So after being forced to create a new DSM file, I'm assuming I have to activate it somehow. But START_DSM doesn't take a pathname, so I have no idea how to do that.
On Wednesday, 21 September 2016 15:15:37 UTC+1, Jim Wilcoxson wrote:
I would still like to use it and I bet several of my former colleagues at Willen Lake (UK) would like to as well. Please let us know when you have managed to make the changes using that infamous CONFIG_DSM comand, thanks.
Well, I tried. I created "user access definition" DSM_USER$, with "function group" .SIM$, and added user GUEST to it. Then went to save it:[snip]
Looks to me like you have saved it correctly.
Geez, this thing is really terrible. Sorry Andrew!
Don't apologise. I agree it's terrible. I said so at the time but was not listened to.
So after being forced to create a new DSM file, I'm assuming I have to activate it somehow. But START_DSM doesn't take a pathname, so I have no idea how to do that.
I can't remember but it might via the DISTRIBUTE_DSM command.
There should be help on it via the help command. This is the only thing I can think of, it was all so long ago....
Enter pathname for configuration: DSM*>CONFIG_FILES>DSM_DEFAULT.CONFIG
Error from DSM_ADMIN (DSM_admin-420):
DSM_DEFAULT.CONFIG is a reserved DSM configuration.
Cool!
Enter pathname for configuration: DSM*>CONFIG_FILES>DSM_DEFAULT.CONFIG
Error from DSM_ADMIN (DSM_admin-420):
DSM_DEFAULT.CONFIG is a reserved DSM configuration.
The manual says that DSM_DEFAULT.CONFIG should never be changed, and
that it may be necessary to use COPY to manage config files. (That's
largely aimed at multi-system networks, but the point of including it
here is that it's legit to do that.)
The default config allegedly allows just SYSTEM on the local system to
do any task.
It looks like the intended workflow is to write to DSM_RESTART.CONFIG.
De
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 296 |
Nodes: | 16 (2 / 14) |
Uptime: | 62:29:58 |
Calls: | 6,654 |
Files: | 12,200 |
Messages: | 5,331,627 |