9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
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] OT: plan9port compilation failure
Date: Wed, 12 Jul 2006 11:26:12 +0200	[thread overview]
Message-ID: <200607120926.k6C9QCU18153@zamenhof.cs.utwente.nl> (raw)
In-Reply-To: Your message of "Mon, 10 Jul 2006 19:37:37 -0700." <1152585457.7683.49.camel@linux.site>

> > I run it on sunos 5.8 and build it with sun cc (Sun WorkShop 6 C 5.1).
>
>   Now, that is a pretty old piece of software. Is there any reason
> you don't want to upgrade ?

the sunos or the sun cc?

I guess the sun cc was not upgraded because nobody really cared enough.
for the usual c stuff it is ok (apart from those mis(sing) features
of which you will see the consequences in the plan9port cvs logs),
and those really caring here have probably been using gcc anyway.

the number of suns here is pretty low now, I'm not sure upgrades
would be considered worthwhile.
most people switched to pc's with linux or windows, or occasional mac.
this also changed how interchangeble the machines are.
on the suns we only have the bare os locally, and all home dirs
and (non-default) applications come from the fileservers.
for the linux machines most applications are local too,
which (potentially) makes them all different. that's not all.
with the suns we had usually a single os version on all machines,
or at most two at times of change.  I think we have at least three
versions of linux with some consequential shared lib incompatibilities.

> > For the last year and a half I've been using (daily, including 9term)
> > a plan9port that I built early january 2005.
> >
> > I've just rebuild plan9port from cvs (sunos 5.8, sun cc).
> > I needed minor tweaks (like the threadimpl.h thing reported here, thx)
> > I've not used much of it yet, some things (e.g. acme) do work, some not.
>
>   Hm. It kinda works for me. At least things I care about.

same here now.

however, I do have the feeling that typing in the acme tags is now even
slower than it already was. could this be a consequence of devdraw,
or other changes? (my previous acme version was from early 2005).
Also (but this is not new, I think?) in acme a single click to scroll
sometimes results in multiple scrollings.
when scrolling with b2 pressed the scrolling cannot keep up with
the mouse moving and you see the mouse cursor being warped up or down
into the scroll 'elevator' and (because of that?) the elevator jumps
up and down and up while scrolling on its way up, or overshoots and
scrolls back and forth until it is finally stable.
this all on a sun blade 100 - maybe that is too slow a machine now?

anyway, these are just little nits.
I agree that on solaris it works pretty well,
definitely those things I care about, and that's pretty impressive
(especially impressive when considering what russ recently wrote).

Axel.


      reply	other threads:[~2006-07-12  9:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-06 20:06 ISHWAR RATTAN
2006-07-06 20:19 ` Richard Bilson
2006-07-07  3:27   ` ISHWAR RATTAN
2006-07-07  3:30     ` William Josephson
2006-07-07 16:44       ` Russ Cox
2006-07-10 15:26         ` Axel Belinfante
2006-07-11  2:37           ` Roman Shaposhnik
2006-07-12  9:26             ` Axel Belinfante [this message]

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=200607120926.k6C9QCU18153@zamenhof.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).