From: Larry McVoy <lm@neteng.engr.sgi.com>
To: miguel@nuclecu.unam.mx, shaver@neon.ingenia.ca, linux@yon.engr.sgi.com
Cc: kenmcd@gonzo.melbourne.sgi.com
Subject: nifty tools on Linux/IRIX
Date: Wed, 28 May 1997 12:24:36 -0700 [thread overview]
Message-ID: <199705281924.MAA09260@neteng.engr.sgi.com> (raw)
Miguel asked about cool tools. Talk to Ken, he's the man.
------- Forwarded Message
Date: Fri, 23 May 1997 05:20:54 -0500
From: "Ken McDonell" <kenmcd@gonzo.melbourne.sgi.com>
To: ptg@melbourne.sgi.com
cc: lm@cthulhu
Subject: scary ... irix and linux exchange simple PCP PDUs
After minor brain-failure on my part, we have success at exchanging
the PDU headers (with no translation for the PDU body).
linux -> linux -> linux
[guest@linux pcp]$ ./pdu-client -D1 -h linux.engr.sgi.com 12345
pdu-client: PID 12334
pdu-client: connected fd=3
[12334]pmXmitPDU: DATA_X fd=3 len=16
000: 10 700b 302e 12345678
[12334]pmGetPDU: DATA_X fd=3 len=16 from=12329 moreinput? no
000: 10 700b 3029 12345678
linux -> irix -> linux
[guest@linux pcp]$ ./pdu-client -D1 -h bozo.melbourne.sgi.com 12345
pdu-client: PID 12333
pdu-client: connected fd=3
[12333]pmXmitPDU: DATA_X fd=3 len=16
000: 10 700b 302d 12345678
[12333]pmGetPDU: DATA_X fd=3 len=16 from=29807 moreinput? no
000: 10 700b 746f 12345678
irix -> linux -> irix
bozo 8% ./pdu-client -D1 -h linux.engr.sgi.com 12345
pdu-client: PID 29821
pdu-client: connected fd=3
[29821]pmXmitPDU: DATA_X fd=3 len=16
000: 10 700b 747d 12345678
[29821]pmGetPDU: DATA_X fd=3 len=16 from=12329 moreinput? no
000: 10 700b 3029 12345678
Now moving onto the translation of the PDU body for each PDU type.
------- End of Forwarded Message
next reply other threads:[~1997-05-28 19:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-05-28 19:24 Larry McVoy [this message]
1997-05-29 14:01 ` nifty tools on Linux/IRIX David Chatterton
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=199705281924.MAA09260@neteng.engr.sgi.com \
--to=lm@neteng.engr.sgi.com \
--cc=kenmcd@gonzo.melbourne.sgi.com \
--cc=linux@yon.engr.sgi.com \
--cc=miguel@nuclecu.unam.mx \
--cc=shaver@neon.ingenia.ca \
/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