Fedor Konstantinov wrote:
22.03.2013 17:41, Oleg Safiullin :
Johnny Billquist wrote:
On 2013-03-22 14:32, Fedor Konstantinov wrote:
Hi, All,
is there any way to change system name on RSX-11M-PLUS without re-SYSGEN?
You could just patch the system. :-)
$SYSNM is where the name is, unless I remember wrong. Check the address in the map, and then ZAP the .SYS image. (And/or open the memory locations on the running system, and change the value.)
Also, DECnet can change the name of a running system.
But no, there is no command that does it for you.
MCR>CON SET SYS NAME=XXXXXX
:)
>CON SET SYS NAME=SKNRX2
CON -- Command Syntax error
-- SET SYS<?>NAME=SKNRX2
I think this command works in M+ V4.6 only.
22.03.2013 17:41, Oleg Safiullin :
Johnny Billquist wrote:
On 2013-03-22 14:32, Fedor Konstantinov wrote:
Hi, All,
is there any way to change system name on RSX-11M-PLUS without re-SYSGEN?
You could just patch the system. :-)
$SYSNM is where the name is, unless I remember wrong. Check the address in the map, and then ZAP the .SYS image. (And/or open the memory locations on the running system, and change the value.)
Also, DECnet can change the name of a running system.
But no, there is no command that does it for you.
MCR>CON SET SYS NAME=XXXXXX
:)
>CON SET SYS NAME=SKNRX2
CON -- Command Syntax error
-- SET SYS<?>NAME=SKNRX2
Johnny Billquist wrote:
On 2013-03-22 14:32, Fedor Konstantinov wrote:
Hi, All,
is there any way to change system name on RSX-11M-PLUS without re-SYSGEN?
You could just patch the system. :-)
$SYSNM is where the name is, unless I remember wrong. Check the address in the map, and then ZAP the .SYS image. (And/or open the memory locations on the running system, and change the value.)
Also, DECnet can change the name of a running system.
But no, there is no command that does it for you.
MCR>CON SET SYS NAME=XXXXXX
:)
On 2013-03-22 14:32, Fedor Konstantinov wrote:
Hi, All,
is there any way to change system name on RSX-11M-PLUS without re-SYSGEN?
You could just patch the system. :-)
$SYSNM is where the name is, unless I remember wrong. Check the address in the map, and then ZAP the .SYS image. (And/or open the memory locations on the running system, and change the value.)
Also, DECnet can change the name of a running system.
But no, there is no command that does it for you.
Johnny
Hi list,
I have opened a notes conference named MAINFRAMES to talk about... IBM mainframes (yeah, I know I have beaten myself with the originality of the conference name). Everyone interested is invited to join. Just point your NOTES client to BITXOW:: and you will be set (unless I have done something wrong).
On Thursday, March 21, 2013 at 12:55 PM, Mark Pizzolato wrote:
On Thursday, March 21, 2013 at 12:40 PM, Cory Smelosky wrote:
On 2013-03-19 23:38, Cory Smelosky wrote:
I am now having an issue...
%SYSTEM-F-ABORT, abort
, fatal hardware error %NCP-W-UNRCMP, Unrecognized
component , Circuit Circuit = QNA-0
The xq device is attached correctly, and it works in other OSes...but
OpenVMS seems to not see it.
Device XQA0:, device type unknown, is online, network device, device is a
template only.
Error count 5 Operations completed
0
Owner process "" Owner UIC
[SYSTEM]
Owner process ID 00000000 Dev Prot
S:RWPL,O:RWPL,G,W
Reference count 0 Default buffer size
512
Please send along the configuration file you are booting the simh vax
instance with AND the output of:
sim> SHOW VERSION
sim> SHOW ETHERNET
We can take this offline if you want...
Please also send what is output when you initially invoke the simh vax instance (before the boot command).
Thanks.
- Mark
On Thursday, March 21, 2013 at 12:40 PM, Cory Smelosky wrote:
On 2013-03-19 23:38, Cory Smelosky wrote:
I am now having an issue...
%SYSTEM-F-ABORT, abort
, fatal hardware error
%NCP-W-UNRCMP, Unrecognized component , Circuit Circuit = QNA-0
The xq device is attached correctly, and it works in other OSes...but
OpenVMS seems to not see it.
Device XQA0:, device type unknown, is online, network device, device is a
template only.
Error count 5 Operations completed
0
Owner process "" Owner UIC
[SYSTEM]
Owner process ID 00000000 Dev Prot
S:RWPL,O:RWPL,G,W
Reference count 0 Default buffer size
512
Please send along the configuration file you are booting the simh vax instance with AND the output of:
sim> SHOW VERSION
sim> SHOW ETHERNET
We can take this offline if you want...
- Mark
On 2013-03-19 23:38, Cory Smelosky wrote:
On 19 Mar 2013, at 23:37, "Dave McGuire" <mcguire at neurotica.com> wrote:
On 03/19/2013 11:03 PM, Cory Smelosky wrote:
I've gotten OpenSXCE installed and I have managed to get zones to work. It took a
little bit of effort and a lot of time but I have done it.
Nice work. You really should document how you did it.
Thank you. I only had to modify one file to make it work it was a surprisingly simple fix. I will definitely document it if my next task succeeds. I'm going to do a bizarre chain starting at OpenSolaris build 134 and jumping to experimental OpenIndiana 150 for SPARC via IPS, then I will create a zone there on my zones zpool and use it as a template. I will then detach that zone and go back to OpenSXCE. I will then clone that zone for use with the real zones. Having 3 working drives makes this quick and safe. ;)
If all of this works, I can share me templates with you if you'd like.
Yow. You have absorbed Solaris amazingly quickly.
I can pick things up quite quickly if I put my mind to it. ;)
-Dave
--
Dave McGuire, AK4HZ
New Kensington, PA
I am now having an issue...
%SYSTEM-F-ABORT, abort
, fatal hardware error
%NCP-W-UNRCMP, Unrecognized component , Circuit
Circuit = QNA-0
The xq device is attached correctly, and it works in other OSes...but OpenVMS seems to not see it.
Device XQA0:, device type unknown, is online, network device, device is a
template only.
Error count 5 Operations completed 0
Owner process "" Owner UIC [SYSTEM]
Owner process ID 00000000 Dev Prot S:RWPL,O:RWPL,G,W
Reference count 0 Default buffer size 512
Besides that, OpenVMS doesn't show it anywhere, as multinet doesn't come up on it and SHO KNOWN CIR doesn't list the circuit.
I can't test 3.9-0 as it doesn't build, so i'm limited to latest git. ;) Is this a bug or am I doing something wrong? ;)
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Experiments
below
On Thu, Mar 21, 2013 at 9:20 AM, Johnny Billquist <bqt at softjar.se> wrote:
They call it a "hybrid", whatever that might mean
A performance hack is what it means.
Ok, I was a tad sloppy and skipped some steps for brevity - my apologies.
CMU created Mach by starting with the Pascal based ukernel Accent from the CMU SPICE project and marrying it with BSD UNIX to bring the user space along. Accent is a true uKernel written for the "Pascalto" (aka the Triple Drip Perq) and CMU rewrote the porting they anted into C and hacked originally BSD 4.1 - ripping out the primariarly the memory and tasking system and widely released became Mach 2.5 after the BSD 4.2 upgrade.
So yes, the API is BSD 4.2, plus the Mach calls. The Messaging, Tasking and Memory support is all CMU (modeled/based on Accent) and support the communications concept of a "port" - which is a distributed message capability. The drivers for were BSD and it originally ran on the VAX. The BSD 4.2 command system was also basis for the distribution. I do not remember when the "BSD NET2" code replaced the BSD 4.2 code - but for the purposed of this discussion I will call them the same [grab me off line if you really what to know the differences].
The key is that CMU envisioned Accent and Mach (and for that matter Accent's for runner - RIG) as distributed OS's which is why the ukernel ideas important. ukernels are message based and message based systems are >>much<< more natural for NORMA (no remote memory access) "multicomputers." But many people (like me) felt that ukernels were just a better way from a software engineering standpoint to build a kernel, since the way the system structured.
But ... Mach 2.5 was a monolithic kernel and because of the BSD basis had support for many different architecture families, from Vax to 68K, NS32000, iPX386 etc and thus would be able to migrate from CMU to places like NeXT, OSF et al.
At the time of the Mach 25 release, CMU had started to work on a pure ukernel called Mach 3.0 which was not completed at CMU, but rather at the OSF/RI and a number of partners. Including my then employer - Locus Computing Corp - who was working as kernel hackers for for hire for most of the major players [DEC, Sun, HP, IBM, or in the case of OSF/1 - Intel].
At OSF and friends a lot of time and study was done considering the performance issues of a pure kernel vs. the monolithic (using the 2.5 and 3.0 based kernels on a 386). The hybrid approach is a hack to allow, some of the system "servers" to continue to be bound into the address space of the kernel so, that two messages are not needed for those system calls.
The "hybrid" idea came from the fact that for 3.0 ukernel, the memory support still is part of the kernel itself (in many ukernels like the grand daddy of them all - Dykstra's THE - the memory support is also a "server layer" in "user" space). In fact, the Mach 3.0 "micro kernel" was about 1-1.5 megabytes on a 386 which is hardly "micro" (at the time people were proposing a "nano-kernel" to solve that].
So the hybrid kernel allows the kernel behave like a pure ukernel when desired, but still allows the performance benefits of a monolithic kernel. Of course because its not a pure ukernel, it suffers all of the security issues and more difficulties of distribution for the kernel across multiprocessors that monolithic kernels have.
Clem
