What kinds of modifications would be necessary to get plan9 booting on
intel macs? The latest releases don't seem to boot, they just hang.
Is it possible to modify the live cd isos to list an option that would
allow booting with the *nomp=1 option set? It seems to prevent the
ability for me to use vesa modes on my dual core Thinkpad T60, and as
a result the coloring looks really screwed up. Dark green background,
terminals with black
Anyone else notice the latest builds of plan9 have a delay with
keyboard input from the bootloader?
When I use ftpfs to mount a ftp site and then bind /n/ftp to another
location. All appears to work fine in /n/ftp and in the other
location. When I type ns, I can clearly see the pipe bind for ftpfs
mounted to /n/ftp. When I unmount /n/ftp I can type ls on /n/ftp and
not see anything there. But if
I forgot to mention when I bind /n/ftp I was really binding
/n/ftp/directory to another location.
On Sat, Dec 6, 2008 at 3:44 PM, Brad Frank <[EMAIL PROTECTED]> wrote:
> When I use ftpfs to mount a ftp site and then bind /n/ftp to another
> location. All appears to work fine in /n/ft
dir4.
So what I guess I was expecting to see from ns when using the ftpfs
scenario, was to see not only a pipe bind to /n/ftp. But Also a pipe
bind to my other location, since the other location was a bind to
/n/ftp.
On Sat, Dec 6, 2008 at 5:17 PM, Brad Frank <[EMAIL PROTECTED]> wrote:
>
oh yeah, it seems to do a pipe bind to the other location, only when
binding to the root. If I bind to /n/ftp/directory, it doesn't show
the pipe bind in ns.
On Sat, Dec 6, 2008 at 5:52 PM, Brad Frank <[EMAIL PROTECTED]> wrote:
> I guess what confuses me when dealing with something
Hi, I recently did a clean install of plan9 on qemu on linux. I've noticed
that the load is spiking on an interval every 30 seconds or something like
that. I looked at suggestions that it might be venti and timesync. But it
couldn't be venti because I didn't install venti, I have a fossil only
inst
Yes, doing those things would be an alternative. But the bigger question is
why is fossil hitting the load like that while running in Qemu. And also,
another question is whether this would be happening on physical hardware as
well... Is there anything I can do to figure out why it is doing that, an
Well, it is also important to note that I am getting these spikes on
qemu while the emulator is essentially idling.
There really should be no reason it should be hitting the virtual disk
like that repeatedly on intervals. Is there no
other explanation for why it would be doing that?
10 matches
Mail list logo
