Thank you. It is compiling OK now.
On Sun, Feb 28, 2010 at 3:06 PM, ge...@plan9.bell-labs.com wrote:
Sorry, I'd forgotten to push /sys/src/9/kw/sdscsi.c to sources.
It's fixed now.
Following a suggestion on 9fans (thank you, whoever it was) I added
two sets of clock settings to VGADB courtesy of the VESA code in
aux/vga.
Recent updates to lib/vgadb prompted me to wonder how I could retain
the additional information and still replicate lib/vgadb from
sources. I'm looking
The workstation I'm using presently seems to trigger as many
interrupts as stats(1) can display, while the syscall graph is also
extremely busy.
I presume this is anomalous. Killing the single instance of
timesync(1) does not seem to make any difference at all.
Any suggestions to where I should
On Sun, Feb 28, 2010 at 3:27 AM, Anthony Sorace a...@9srv.net wrote:
The multi-touch stuff added to plan9ports to make the Apple Magic
Mouse work is really nice; I confess I didn't really believe Russ when he
described it as feeling natural, but it does. It's pretty easy to forget
about
On Sun Feb 28 04:57:09 EST 2010, lu...@proxima.alt.za wrote:
The workstation I'm using presently seems to trigger as many
interrupts as stats(1) can display, while the syscall graph is also
extremely busy.
I presume this is anomalous. Killing the single instance of
timesync(1) does not
doing things to 9vx seems like a bad idea compared to just having a
p9p server with the /mouse and /mousectl for the magic mouse, and then
mounting that in your 9vx /dev.
same thing applies to drawterm, inferno, and probably glendix, which
together with 9vx and p9p is your entire aviary
regardless the code base is mostly the same for all three
and moving the code over should be fairly straightforward.
russ
in the process of cleaning trying to get rc working with 4-byte
utf-8 sequences, i noticed that rc has a few weak points when
it comes to handling runes that have nothing to do with rune
size. for example this script
; cat badbq
#!/bin/rc
nl='
'
ifs=α$nl
On Sun, Feb 28, 2010 at 1:55 AM, lu...@proxima.alt.za wrote:
The workstation I'm using presently seems to trigger as many
interrupts as stats(1) can display, while the syscall graph is also
extremely busy.
workstation only? I.e. it is not running venti?
ron
