Hello,
trying to use acmeedit I got from sb here I encountered this in
$PLAN9/lib/acme.rc file:
fn newwindow {
winctl=`{9p read acme/new/ctl}
winid=$winctl(1)
winctl noscroll
}
fn winctl {
echo $* | 9p write acme/$winid/ctl
}
... many more lines
I believe
I am sorry, ignore it, please. I can have both variable and function
at the same time, as it seems...
Ruda
On 20 March 2011 16:13, Rudolf Sykora rudolf.syk...@gmail.com wrote:
Hello,
trying to use acmeedit I got from sb here I encountered this in
$PLAN9/lib/acme.rc file:
fn newwindow {
As a workaround, I tried putting echo dma on /dev/sdC0/ctl in
termrc. This was sufficient to keep a fossil-only install from failing.
But, even *with* this workaround, a fossil+venti install would still
return i/o errors. That's probably because fossil calls venti before
init calls termrc.
does anything think that it's a mistake to default dma on?
I have a lot of old kit around and can't for the hell of me figure out
which drives do need and which ones don't want DMA, occasionally
losing if nothing else a lot of time and effort in repairing a bad
assumption. Having a kernel
I have a lot of old kit around and can't for the hell of me figure out
which drives do need and which ones don't want DMA, occasionally
i thought that dma problems were almost always controller/cable or master/slave
related? almost all the device i deal with are sata these days. and before
Hello,
I'm finishing the integration of John Hobby's MetaPost to kerTeX.
Since MetaPost can work with either some instance of TeX or troff for
formatting labels included in the figures, it can be of general use even
for troff only users.
So the question:
MetaPost was first named (for plain
i've been taking a careful look at interrupts recently
because i had a number of machines that just didn't
work. that problem turned out not to be too hard,
and was easily fixed. it turns out that one needs to
do a dance for lapic apic ids 7. (this code is already
in 9atom.)
along the way, i
erik quanstrom quans...@quanstro.net writes:
i thought that dma problems were almost always controller/cable or
master/slave
related? almost all the device i deal with are sata these days. and before
that, i stuck to scsi.
smiley, did the kernel with *sdC0dma support print anything
smiley, did the kernel with *sdC0dma support print anything different?
Yes, it did. I noticed that the DMA kernel prints nomp: no mp
structure at bootup.
that's related to how interrupts are delivered. it doesn't have anything
directly to do with ide.
But I didn't save kmesg from the
