From: Jason Stevens <jsteve@superglobalmegacorp.com>
To: <tuhs@minnie.tuhs.org>, Madeline Autumn-Rose <b4@gewt.net>
Subject: Re: [TUHS] Mach'86
Date: Wed, 17 Jul 2019 00:04:35 +0000 [thread overview]
Message-ID: <ADFDF14544A65F35.277366cf-d5af-45d9-974d-4ba7315d3a2a@mail.outlook.com> (raw)
In-Reply-To: <cea17418-bc8b-44a3-960a-f1b51e6af0e3@www.fastmail.com>
[-- Attachment #1: Type: text/plain, Size: 1791 bytes --]
Mach has its own ps. The problem is that it just dumps core. I rebuilt it from inside the source, and it has some weird pathing issues, but it dumps core too.
At that point I kind of gave up.
One fun thing is searching the boot string reveals exactly one machine running this build. Although I would imagine that they probably have nothing left of this..
#N thrash
#S DEC VAX 11/785; Mach/4.3/2/1
#O Princeton University, Department of Computer Science
#C Pat Parseghian
#E princeton!pep
#T +1 609 452 6261
#P Engineering Quadrangle, Princeton, NJ 08544
#L 40 21 N / 74 40 W
#W princeton!pep (Pat Parseghian); Mon Nov 6 18:19:19 EST 1989
Get Outlook for Android
On Wed, Jul 17, 2019 at 3:37 AM +0800, "Madeline Autumn-Rose" <b4@gewt.net> wrote:
On Tue, Jul 16, 2019, at 02:33, Jason Stevens wrote:
I uploaded my SIMH config, along with the RP06 disk images here: https://sourceforge.net/projects/bsd42/files/4BSD%20under%20Windows/v0.4/Mach86.zip/download
`ps` is a little unhappy. Hmm. Wonder why.
myname# ps aux
USER PID %CPU %MEM SZ RSS TT STAT TIME COMMAND
ps: cant read u for pid -26328 from /dev/drum
ps: cant read indir pte to get u for pid 0 from /dev/kmem
ps: cant read u for pid -15008 from /dev/drum
ps: cant read indir pte to get u for pid 0 from /dev/kmem
ps: cant read u for pid -32767 from /dev/drum
ps: cant read indir pte to get u for pid 0 from /dev/kmem
ps: cant read u for pid 0 from /dev/drum
ps: cant read u for pid 0 from /dev/drum
ps: cant read indir pte to get u for pid 124 from /dev/kmem
I don't think those PIDs should be negative. :)
--
Madeline Autumn-Rose
b4@gewt.net
[-- Attachment #2: Type: text/html, Size: 5008 bytes --]
next prev parent reply other threads:[~2019-07-17 0:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-16 9:32 Jason Stevens
2019-07-16 19:26 ` Madeline Autumn-Rose
2019-07-17 0:04 ` Jason Stevens [this message]
2019-07-16 19:34 ` Madeline Autumn-Rose
2019-07-17 7:33 ` emanuel stiebler
2019-07-17 14:12 ` Clem Cole
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=ADFDF14544A65F35.277366cf-d5af-45d9-974d-4ba7315d3a2a@mail.outlook.com \
--to=jsteve@superglobalmegacorp.com \
--cc=b4@gewt.net \
--cc=tuhs@minnie.tuhs.org \
/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).