From: "Matt" <matt@proweb.co.uk>
To: <9fans@cse.psu.edu>
Subject: [9fans] drawterm etc.
Date: Sun, 30 Jul 2000 14:13:56 +0100 [thread overview]
Message-ID: <001101bffa28$0bd4e240$02a7b6c3@lucid.proweb.net> (raw)
In-Reply-To: <200007300228.WAA17889@cse.psu.edu>
he he I'm beginning to feel stupid now I can't get stuff working
so 2 things
1. I am not stupid (AFAIK)
2. I can't get drawterm to connect
donk Jul 30 13:39:11 giving up on tcp17013!*!: announce opening
/net/tcp17013/clone: file does not exist
and it's true
/net/tcp17013 does not exist but you knew that
the binary of couse sits in /bin/service
that surely can't be wrong so i know for sure it's my setup
hurry up and write that book and I'll stop asking
Matt
next prev parent reply other threads:[~2000-07-30 13:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-30 2:28 [9fans] /sys/lib/pcdist/README Russ Cox
2000-07-30 13:13 ` Matt [this message]
2000-07-30 15:20 [9fans] drawterm etc Russ Cox
[not found] <200007301521.QAA06462@pw001.proweb.co.uk>
2000-07-30 16:30 ` Matt
[not found] <200007302230.XAA03260@pw001.proweb.co.uk>
2000-07-31 19:05 ` Matt
[not found] <200007311932.PAA10741@smtp2.fas.harvard.edu>
2000-07-31 22:49 ` Matt
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='001101bffa28$0bd4e240$02a7b6c3@lucid.proweb.net' \
--to=matt@proweb.co.uk \
--cc=9fans@cse.psu.edu \
/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).