erik quanstrom wrote:
I'm serving drives to WinXP64 via AOE with http://winaoe.org/
I've had a few blue screens but I think they have been caused by the
server side serving bad data.
what do you mean by "server side"?
My dodgy programming :> I'm hacking around in vblade.c
Sorry, I se
> I'm serving drives to WinXP64 via AOE with http://winaoe.org/
> I've had a few blue screens but I think they have been caused by the
> server side serving bad data.
what do you mean by "server side"?
> If the vblade goes away after being
> mounted the NT kernel keeps trying to read it which
I've added kbin to pcf, so the set of distributed kernels with kbin in
them is now pc, pccd, pcdisk and pcf. pcflop is excluded to try to
keep its size down so that it will continue to fit on a floppy, though
I suspect that that struggle will soon be lost and we'll have to use
CDs for initial inst
however you can use the -i switch to initialize a blank
file. (you're free to use a raw disk or partition, too.)
- erik
or say "damn, where did my partition table go !"
I can't remember if I lost any work :)
strings /dev/sdC0/plan9 will let me know eventually !
note to self, be more car
On Fri, 11 Jul 2008, andrey mirtchovski wrote:
change the definition of VX32_LDFLAGS in src/Makefrag to:
VX32_LDFLAGS := -Llibvxc -L$(dir $(shell gcc -m32 -print-libgcc-file-name)) \
With this change I get the error:
..
$ ld: errno: TLS definition in /lib/libc.so.6 section .tbss mismatches
On Sun, Jul 13, 2008 at 07:27:29AM -0400, erik quanstrom wrote:
> > This computer is attached to a KVM that includes USB keyboard & mouse
> > via a single USB attachment to the Dell (the KVM is a USB hub,
> > obviously).
> >
> > The mouse seems to work just fine but when I'm in rio and hit a key
On Sun, Jul 13, 2008 at 12:52:54AM -0700, Anthony Martin wrote:
> > term% cat /dev/drivers | grep kbin # kbin(3)
>
> Sorry about the terseness. I meant to also say that
> you'll have to add the kbin device to your kernel
> configuration and recompile. I don't think it's in
> the default.
Makes s
On 7/13/08, erik quanstrom <[EMAIL PROTECTED]> wrote:
> it seems the prior diagnosis is correct. the cpu kernels
> cpu, cpuf don't have the kbin device built in.
>
> however i'm a little confused. do you start rio automaticly
> on your cpu server?
It seems that pcf doesn't have the kbin device b
> This computer is attached to a KVM that includes USB keyboard & mouse
> via a single USB attachment to the Dell (the KVM is a USB hub,
> obviously).
>
> The mouse seems to work just fine but when I'm in rio and hit a key on
> the USB keyboard I get the following error:
>
> usb/kb: /dev/kbin: un
> term% cat /dev/drivers | grep kbin # kbin(3)
Sorry about the terseness. I meant to also say that
you'll have to add the kbin device to your kernel
configuration and recompile. I don't think it's in
the default.
Anthony
term% cat /dev/drivers | grep kbin # kbin(3)
11 matches
Mail list logo
