Groups | Search | Server Info | Login | Register
Groups > alt.sys.pdp10 > #9835
| From | jayjwa <jayjwa@atr2.ath.cx.invalid> |
|---|---|
| Newsgroups | alt.sys.pdp10 |
| Subject | Re: TOPS-10 networking in modern time |
| Date | 2025-12-31 12:17 -0500 |
| Organization | Atr2 RG 2025 |
| Message-ID | <87o6nefu4h.fsf@atr2.ath.cx> (permalink) |
| References | (7 earlier) <10itjtr$tdk1$1@dont-email.me> <87h5t96wx3.fsf@atr2.ath.cx> <10iuivt$17bgf$1@dont-email.me> <87qzsblwm1.fsf@atr2.ath.cx> <10j1tq7$27kgq$1@dont-email.me> |
"G." <nan6328@iperbole.invalid> writes:
> I'm starting to think that running everything on the same host may not
> be the best solution. You could incur in (virtual) network issues
> and/or could end up with a too slow emulated system.
About 60% is on Linux and the rest on Sun. Both systems are 8 core, and
the Sun has 12g RAM and loadavg almost never reaches 1.0 so I think it
has power enough.
> Do you know if your monitor is idling? On klh10 one needs to patch the
> monitor (CONO 740,1) but I have no idea about Simh, maybe it's too
> "sleepy"?
It think the Panda dist is patched, the idle line is
devdef idler 700 host
for TOPS-20. For TOPS-10, the instuctions have you patch to either 740
or 700, but 740 caused explosions so it ended up as:
CONO 700,1 ;AC1 - DON'T CAUSE EXCESSIVE MEMORY INTERFERENCE
> Mine is pretty snappy, actually even better than LAT. I'm more and
> more convinced that you may have some serious issue with your
> installation. Maybe some misalignment between the monitor and Galaxy,
> who knows... Did you use some pre-made installation? If yes, do you
> know if it has the latest patches?
That's the way it's looking. It was this .zip:
https://www.sky-visions.com/dec/tops704/
but I patched the monitor for post-Nov 2021 networking, my node/area,
and more memory.
> It may also depend on the emulator, mine runs on klh10 and is hosted
> by a friend on some little ARM64 SBC. I chose klh10 instead of Simh
> because back when I made my installation it was the only KL10 emulator
> available, and I wanted it instead of a KS10 because of the network
> support.
TOPS-20 uses KLH10, my other stuff uses Open SIMH and Mark's.
> TOPS-10 speaks both CTERM and RTERM, thus it should work anyway but
> with CTERM is dead slow. RSTS (to name one) speaks only RTERM whereas
> Linux speaks only CTERM. If you want to try some outbound connection
> from TOPS-10 use NRT for RTERM and NFT for FAL. I don't think there is
> any CTERM client and definitely there is no outbound LAT (back then it
> was only inbound).
Noted.
> There seems to be something off here. Job 14, 15, and 18 are in TO
> state which should mean Terminal Output, i.e. they want to output
> something (some error?) and are awaiting for a terminal. IIRC you
> should ATTACH to each job and check. Indeed, NODNAM should do its
> thing and then disappear. Also, I'm not sure that having two MX jobs
> is correct.
The two MX jobs showed up after I setup NODNAM. Before it was just one,
like it should be. I ATTACHed to NODNAM and it just gave EXIT. I guess
it needed a special invite to finish. That cleared the Busy devices
list. Maybe NODNAME isn't the best choice for today's systems? I run it
as
LOGIN
NODNAM
in SYSJOB.INI . After that is
LOGIN
MX
Maybe I'm not supposed to use LOGIN and just put NODNAM? Everything else
in that file has LOGIN on the line before. When I ATTACH to the two
others, I land at . .
.systat
Please type ^C first
^C <--- which I do
Then those TO's disappear if I .kjob on them. Now it looks like so:
.systat
Status of KL+NETMON-704 at 9:44:12 on 31-Dec-98
Uptime 11:01:07, 124% Null time = 124% Idle + 0% Lost, 0% Overhead
16 Jobs in use out of 128. 16 logged in, 14 detached.
Job Who Line# What Size(P) State Run Time
1 [OPR] DET104 STOMPR 7+11 SL 0 01
2 [OPR] CTY SYSTAT 23+SPY RN 1
3 30,1 4 NETWOR 14+18 ^C 0
4 [OPR] DET104 ACTDAE 178+40 SL 3
5 [OPR] DET104 DAEMON 20+SPY SL 1
6 [OPR] DET104 FILDAE 17 HB 0
7 [OPR] DET104 QUASAR 74+40 SL 2
8 [OPR] DET104 ORION 108+40 SL 1
9 [OPR] DET104 PULSAR 66+40 HB 0
12 [OPR] DET104 MIC 5+15 SL 0
14 [OPR] DET104 MX 121+45 HB 1
15 [OPR] DET104 MX 121+45 HB 1
18 [OPR] DET104 NEBULA 26+40 HB 0
19 [OPR] DET104 CATLOG 147+40 HB 0
20 [OPR] DET104 NML 38+135 HB 17
21 [OPR] DET104 FAL-10 104+40 SL 1
n means job runs in HPQ n
High Segments:
Program Device Owner High(P) Users
INITIA DSKB [SYS] 11 1
GLXLIB DSKB [SYS] 40 7
MIC DSKB [SYS] 15 1
(PRIV) Job 14 45 1
(PRIV) Job 15 45 1
(PRIV) Job 20 135 1
NETWOR DSKB [SYS] 18 1
Swapping space used = 1329/8192 = 16%
Virt. Core used = 1378/8192 = 17%
6068P Core left
Active swapping ratio = 23/7446 = .00
Virt. Core saved by sharing = 240/(240+1378) = 15%
Average job size =1069/16 = 66.8P+549/16 = 34.3P Total=1618/16 = 101P
No busy devices
System File Structures:
Name Free Mount
DSKB 240980 3
Total Free 240980
> PULSAR is the disk and tape processor (mount requests, etc.) and ORION
> is the operator command processor, basically the back-end of OPR. Do
> you happen to have some unmounted and/or unformatted disk or tape
> attached to the emulator?
Nope, just the system disk(s). The printer is supposed to go to
printer.txt, but I've yet to see it work. From the commands I've read,
it should be working, says it's working, but does not. That's really low
priority though.
>> Busy devices:
>> Device Job Why Logical
>> TSK15 3 init
>> TSK15 3 init
>> TSK15 3 init
>> TSK15 3 init
>> TSK15 3 init
>
> This too seems a bit weird. But maybe it's just some missing terminal
> or some issue in your TTY.INI. Actually I'm wondering if those TSK15
> entries may have something to do with job 15, i.e. NODNAM...
They disappeared after the ATTACH to NODNAM. Maybe I should go back to
NODES.CMD once the system is up.
> No, I'm sorry, I have no idea. Actually I don't even know "who" should
> update it, whether the monitor or some job. Mine indeed gets updated:
>
> DSKB1:ERROR.SYS[1,4]
> Access date: 30-Dec-25
> Creation time, date: 1:25 30-Dec-25
> Access protection: 155
> Mode: 17
> Words written: 37489.
> Estimated length: 120.
> Blocks allocated: 300.
> Written on unit(s) 1 on controller 0 on CPU 2034
> Author: 1,2
> Data block in directory: 115450.
> Internal creation date, time: 30-Dec-25 1:24:50
> RIB block number: 17220.
> Account: SYSTEM
>
> However, I've never used SPEAR and I don't seem able to do
> so. Apparently I'm missing several .SPE files.
Yours is getting written to. TOPS-20 works right off, but 10
doesn't on my install. OK, you've giving me some things to
work on, thank you.
--
PGP Key ID: 781C A3E2 C6ED 70A6 B356 7AF5 B510 542E D460 5CAE
"The Internet should always be the Wild West!"
Back to alt.sys.pdp10 | Previous | Next — Previous in thread | Next in thread | Find similar
TOPS-10 networking in modern time jayjwa <jayjwa@atr2.ath.cx.invalid> - 2025-12-14 20:55 -0500
Re: TOPS-10 networking in modern time Rich Alderson <news@alderson.users.panix.com> - 2025-12-14 21:23 -0500
Re: TOPS-10 networking in modern time Al Kossow <aek@bitsavers.org> - 2025-12-14 18:34 -0800
Re: TOPS-10 networking in modern time drb@ihatespam.msu.edu (Dennis Boone) - 2025-12-15 03:04 +0000
Re: TOPS-10 networking in modern time jayjwa <jayjwa@atr2.ath.cx.invalid> - 2025-12-15 14:34 -0500
Re: TOPS-10 networking in modern time Rich Alderson <news@alderson.users.panix.com> - 2025-12-15 17:03 -0500
Re: TOPS-10 networking in modern time jayjwa <jayjwa@atr2.ath.cx.invalid> - 2025-12-16 11:35 -0500
Re: TOPS-10 networking in modern time Rich Alderson <news@alderson.users.panix.com> - 2025-12-16 22:12 -0500
Re: TOPS-10 networking in modern time Johnny Billquist <bqt@softjar.se> - 2025-12-17 10:31 +0100
Re: TOPS-10 networking in modern time jayjwa <jayjwa@atr2.ath.cx.invalid> - 2025-12-17 11:06 -0500
Re: TOPS-10 networking in modern time jayjwa <jayjwa@atr2.ath.cx.invalid> - 2025-12-17 10:56 -0500
Re: TOPS-10 networking in modern time Johnny Billquist <bqt@softjar.se> - 2025-12-20 13:27 +0100
Re: TOPS-10 networking in modern time Lars Brinkhoff <lars.spam@nocrew.org> - 2025-12-20 13:23 +0000
Re: TOPS-10 networking in modern time jayjwa <jayjwa@atr2.ath.cx.invalid> - 2025-12-20 11:59 -0500
Re: TOPS-10 networking in modern time Johnny Billquist <bqt@softjar.se> - 2025-12-25 11:35 +0100
Re: TOPS-10 networking in modern time "G." <nan6328@iperbole.invalid> - 2025-12-29 17:59 +0100
Re: TOPS-10 networking in modern time "G." <nan6328@iperbole.invalid> - 2025-12-28 10:47 +0100
Re: TOPS-10 networking in modern time jayjwa <jayjwa@atr2.ath.cx.invalid> - 2025-12-28 18:21 -0500
Re: TOPS-10 networking in modern time "G." <nan6328@iperbole.invalid> - 2025-12-29 11:07 +0100
Re: TOPS-10 networking in modern time Johnny Billquist <bqt@softjar.se> - 2025-12-29 13:20 +0100
Re: TOPS-10 networking in modern time jayjwa <jayjwa@atr2.ath.cx.invalid> - 2025-12-29 12:22 -0500
Re: TOPS-10 networking in modern time "G." <nan6328@iperbole.invalid> - 2025-12-29 20:43 +0100
Re: TOPS-10 networking in modern time jayjwa <jayjwa@atr2.ath.cx.invalid> - 2025-12-30 11:57 -0500
Re: TOPS-10 networking in modern time Johnny Billquist <bqt@softjar.se> - 2025-12-31 15:21 +0100
Re: TOPS-10 networking in modern time jayjwa <jayjwa@atr2.ath.cx.invalid> - 2025-12-31 12:33 -0500
Re: TOPS-10 networking in modern time Johnny Billquist <bqt@softjar.se> - 2025-12-31 15:20 +0100
Re: TOPS-10 networking in modern time "G." <nan6328@iperbole.invalid> - 2025-12-29 17:59 +0100
Re: TOPS-10 networking in modern time jayjwa <jayjwa@atr2.ath.cx.invalid> - 2025-12-29 12:05 -0500
Re: TOPS-10 networking in modern time "G." <nan6328@iperbole.invalid> - 2025-12-29 19:58 +0100
Re: TOPS-10 networking in modern time jayjwa <jayjwa@atr2.ath.cx.invalid> - 2025-12-30 12:15 -0500
Re: TOPS-10 networking in modern time "G." <nan6328@iperbole.invalid> - 2025-12-31 02:21 +0100
Re: TOPS-10 networking in modern time jayjwa <jayjwa@atr2.ath.cx.invalid> - 2025-12-31 12:17 -0500
Re: TOPS-10 networking in modern time "G." <nan6328@iperbole.invalid> - 2026-01-01 18:32 +0100
Re: TOPS-10 networking in modern time jayjwa <jayjwa@atr2.ath.cx.invalid> - 2026-01-02 13:27 -0500
Re: TOPS-10 networking in modern time "G." <nan6328@iperbole.invalid> - 2026-01-05 13:37 +0100
Re: TOPS-10 networking in modern time jayjwa <jayjwa@atr2.ath.cx.invalid> - 2026-01-05 12:52 -0500
Re: TOPS-10 networking in modern time "G." <nan6328@iperbole.invalid> - 2026-01-06 01:37 +0100
Re: TOPS-10 networking in modern time jayjwa <jayjwa@atr2.ath.cx.invalid> - 2026-01-06 12:18 -0500
csiph-web