9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: lucio@proxima.alt.za
To: 9fans@cse.psu.edu
Subject: [9fans] Niggles
Date: Thu, 31 Oct 2002 03:08:56 +0200	[thread overview]
Message-ID: <99d3c18c199e0f08daa8f011d7a692b0@proxima.alt.za> (raw)

Just a few oddities with a recent version of Plan 9.

1.  In text mode, the keyboard handler seems to be a little erratic.
In RIO no problems seem to occur.  The behaviour seems to be caused by
the occasional backspace and consists of the addition of spurious
characters that are not echoed to the screen.  Hard to describe, even
harder to pinpoint.  The most common situation is an invalid command
name or command argument value that has a space or some other
character in it not present in the command line itself.  It is
frequent enough to be a bit of a bother on an auth or cpu server.  I
can't recall if I ever encountered on the FS. I think the problem
appeared in 4th Edition, I can probably check later this month.

Hm, I haven't ever checked if switching to VGA mode makes a difference
or not.

2.  My Intellimouse seems to be misunderstood: the right button quite
regularly starts duplicating the middle button function in RIO, SAM
and ACME; a wloc command in any window restores it to its more useful
behaviour.  I only noticed this recently, I'm using a stand-alone
workstation with the second ISO image (the one I asked Russ about a
few days before its recent release - I think it's current, send me a
digest and I'll compare).

3.  I started getting vncv lockouts so I switched to a newer
workstation, keeping the disks unchanged and the lockouts as well as
frequent vncv failures have stopped.  I find this quite baffling, but
not unexpected.  I also have a Gygabyte motherboard that seems
incapable of handling any OSes like Plan 9, NetBSD or WinNT that need
real memory protection.  I think it's MMU related.  Hm, could be
CPU-related, too, the chip is Cyrix/IBM rather than Intel, but I think
I tried a different CPU once.

Can't think of anything else presently, I may follow up on this if I
recall or encounter any other small issues that one can easily live
with.

++L



             reply	other threads:[~2002-10-31  1:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-31  1:08 lucio [this message]
2002-11-01  5:06 Geoff Collyer
2002-11-01 17:28 a
2002-11-01 17:33 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=99d3c18c199e0f08daa8f011d7a692b0@proxima.alt.za \
    --to=lucio@proxima.alt.za \
    --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).