From: Axel Belinfante <Axel.Belinfante@cs.utwente.nl>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] drawterm on solaris
Date: Sat, 5 Nov 2005 22:46:21 +0100 [thread overview]
Message-ID: <200511052146.jA5LkMw05745@demeter.cs.utwente.nl> (raw)
In-Reply-To: Your message of "Fri, 04 Nov 2005 23:43:23 +0100." <200511042243.jA4MhNo17891@demeter.cs.utwente.nl>
> > > > There are new drawterm binaries at http://swtch.com/drawterm/
> > >
> > > I almost don't dare to ask...
> > > anybody tried to compile it (with success)
> > > for sunos 5.8?
> >
> > To answer my own question: after a little struggle I have a drawterm.
> >
> > When I start it with my usual -a and -c flags it says:
> >
> > | cpu: cannot write user/domain choice in p9any:
> > | '/mnt/factotum/ctl' does not exist
> > |
> > | goodbye
> >
> > Is this something I missed in the struggle?
> > Or the effect of a too old p9p installation?
> > Or?
> >
> > (running cpu from a plan9 terminal works fine,
> > as does old drawterm)
>
> commenting out the 'exits' at the end of 'fatal'
> and adding some debug prints shows me a bit more.
> seems like the '/mnt/factotum/ctl does not exist
> somehow is stuck from a previous error and not reset.
>
> reading p9any negotiation: p9sk1@cs.utwente.nl
> cpu: cannot write user/domain choice in p9any: 11 != 20: p9sk1 cs.utwente.nl
> cpu: cannot write p9sk1 challenge: (factotum ctl err msg)
> user@cs.utwente.nl password:
> cpu: cannot send ticket and authenticator back in p9sk1: cs gave empty translation
> list
> cpu: can't authenticate slurp: cs gave empty translation list
> cpu: wrting network: dir: fd out of range or not open
> cpu: wanting for FS: fd out of range or not open: fd out of range or not open
> remote cpu:
> goodbye
If solaris is the only system where the following breaks,
seems we know again why we still love it, even if just a bit -
to keep us honest.
(the above is a probably bad attempt at paraphrasing the Geoff's
'active port [...] to keep the code honest' line at the wiki)
anyway, the fix below brings me to:
'can't authenticate: cpuserver: can't establish ssl connection: bad algorithm'
I'll continue digging.
Axel.
; cvs diff -buw devip-posix.c
Index: devip-posix.c
===================================================================
RCS file: /cvs/drawterm/kern/devip-posix.c,v
retrieving revision 1.1
diff -b -u -w -r1.1 devip-posix.c
--- devip-posix.c 8 Aug 2005 12:50:11 -0000 1.1
+++ devip-posix.c 5 Nov 2005 21:26:36 -0000
@@ -199,7 +199,7 @@
int
so_send(int fd, void *d, int n, int f)
{
- send(fd, d, n, f);
+ return send(fd, d, n, f);
}
int
next prev parent reply other threads:[~2005-11-05 21:46 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-04 17:21 [9fans] drawterm Russ Cox
2005-11-04 20:09 ` Gabriel Diaz
2005-11-04 18:21 ` "Nils O. Selåsdal"
2005-11-04 20:47 ` Gabriel Diaz
2005-11-04 20:18 ` Russ Cox
2005-11-04 20:13 ` Axel Belinfante
2005-11-04 22:14 ` Axel Belinfante
2005-11-04 22:43 ` Axel Belinfante
2005-11-05 21:46 ` Axel Belinfante [this message]
2005-11-05 21:55 ` [9fans] drawterm on solaris Axel Belinfante
2005-11-05 23:09 ` Axel Belinfante
2005-11-04 22:50 ` [9fans] drawterm Brantley Coile
2005-11-04 23:01 ` andrey mirtchovski
2005-11-04 23:04 ` Brantley Coile
2005-11-04 23:08 ` Tim Wiess
2005-11-04 23:16 ` andrey mirtchovski
2005-11-07 17:49 ` [9fans] drawterm Russ Cox
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=200511052146.jA5LkMw05745@demeter.cs.utwente.nl \
--to=axel.belinfante@cs.utwente.nl \
--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).