From: lehmann@ans-netz.de (Oliver Lehmann)
Subject: [TUHS] System III - TCP/IP
Date: Sat, 07 Nov 2015 20:03:58 +0100 [thread overview]
Message-ID: <20151107200358.Horde.M1lYZZyTC4t0Qb8KrygKzhy@avocado.salatschuessel.net> (raw)
Hi,
i have an old Z8001 based SysIII variant and I would love to have
TCP/IP on it (SLIP first, later with a homebrew ethernet device).
I wonder if someone ever saw TCP/IP available on a System III?
I have lets say 90% of the kernel running on it as source
available and I started digging in the available 4.2 BSD sources.
It looks like there would be much to do to hack in TCP/IP on my
own (no IPC, no Net, no PTY, no....).
I got K5JB running (userland TCP/IP implementation) after I fixed
some C code because the C Compiler available on the system is.....
kinda limited.
telnetd is of course not working as there are no pseudo-teletypes
on this SYSIII. At least I got ping, echoping and ftpd up and
running via SLIP
(10.1.1.2 is my SysIII box:)
# ping -c3 10.1.1.2
PING 10.1.1.2 (10.1.1.2): 56 data bytes
64 bytes from 10.1.1.2: icmp_seq=0 ttl=254 time=316.317 ms
64 bytes from 10.1.1.2: icmp_seq=1 ttl=254 time=297.328 ms
64 bytes from 10.1.1.2: icmp_seq=2 ttl=254 time=296.369 ms
--- 10.1.1.2 ping statistics ---
3 packets transmitted, 3 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 296.369/303.338/316.317/9.186 ms
# ftp 10.1.1.2
Connected to 10.1.1.2.
220 FTP version K5JB.k37 ready at Tue Apr 30 22:25:47 1991
Name (10.1.1.2:root): test
331 Enter PASS command
Password:
230 Logged in
ftp> get sa.timer
local: sa.timer remote: sa.timer
500 Unknown command
500 Unknown command
200 Port command okay
150 Opening data connection for RETR sa.timer
2571 0.53 KB/s
226 File sent OK
2571 bytes received in 00:05 (0.48 KB/s)
ftp> get wega
local: wega remote: wega
200 Port command okay
150 Opening data connection for RETR wega
98723 0.51 KB/s
226 File sent OK
98723 bytes received in 03:05 (0.51 KB/s)
ftp> exit
221 Goodbye!
#
So I wonder if someone got anything SYSIII -> Net/TCP/IP related
which could help me in any way to get a SYSIII kernel capable of
TCP/IP and PTYs to get a telnetd up and running via SLIP is my
first goal.
Regards,
Oliver
next reply other threads:[~2015-11-07 19:03 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-07 19:03 Oliver Lehmann [this message]
2015-11-07 19:20 ` Larry McVoy
2015-11-07 20:27 ` Cory Smelosky
2015-11-08 7:11 ` Larry McVoy
2015-11-08 7:22 ` John Cowan
2015-11-08 8:20 ` Cory Smelosky
2015-11-08 14:45 ` Dave Horsfall
2015-11-08 17:04 ` Steve Nickolas
2015-11-09 4:34 ` Larry McVoy
2015-11-07 21:28 ` Clem Cole
2015-11-07 22:07 ` Cory Smelosky
2015-11-07 22:13 ` Oliver Lehmann
2015-11-08 5:10 ` Derek Fawcus
2015-11-08 5:39 ` Nick Downing
2015-11-08 9:40 ` Oliver Lehmann
2015-11-08 13:38 ` Oliver Lehmann
2015-11-09 0:21 ` Nick Downing
2015-11-09 8:15 ` Oliver Lehmann
2015-11-09 8:16 ` Oliver Lehmann
2015-11-09 9:40 ` Oliver Lehmann
2015-11-09 9:40 ` Oliver Lehmann
2015-11-09 22:36 ` Nick Downing
2015-11-09 0:31 ` Nick Downing
2015-11-11 1:54 ` Cornelius Keck
2015-11-11 6:46 ` Oliver Lehmann
2015-11-08 15:52 Noel Chiappa
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20151107200358.Horde.M1lYZZyTC4t0Qb8KrygKzhy@avocado.salatschuessel.net \
--to=lehmann@ans-netz.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).