On May 7, 12:24 pm, [EMAIL PROTECTED] wrote:
Hi.
I am trying to install INFERNO in FreeBSD 7.0 using the downloaded
inferno CD image. Created user 'inferno' with /home/inferno as
inferno root directory. Running the install script I get the
following error:
$ /mnt/install/FreeBSD-386.sh
the terminals need ipaddresses in /lib/ndb/local. if you are not pxe
booting, the minimum requirment is to have an entry like
sys=gnot ip=192.168.0.100
the man pages ndb(6) and ndb(8) should be helpful.
- erik
thank you for your answer...
in my /lib/ndb/local i have all the ip's what i
the terminals need ipaddresses in /lib/ndb/local. if you are not pxe
booting, the minimum requirment is to have an entry like
sys=gnot ip=192.168.0.100
the man pages ndb(6) and ndb(8) should be helpful.
- erik
thank you for your answer...
in my /lib/ndb/local i have all the
if you're going to pxe boot, you should generally be using bootf=9load.
sorry, bootf=/386/9load.
- erik
While there's certainly significant overlap in users, you
might have better luck on Vita Nuova's Inferno list. I
forget the subscription information off hand, but I'm
certain you'll find it on their web site.
Anthony
On Thu, May 8, 2008 at 1:21 PM, erik quanstrom [EMAIL PROTECTED] wrote:
if you're going to pxe boot, you should generally be using bootf=9load.
sorry, bootf=/386/9load.
you mean 9pxeload ?
--
- curiosity sKilled the cat
On Thu, 2008-05-08 at 13:24 -0400, Russ Cox wrote:
So I have to allocate 56 bytes (sizeof(Tos) on 386) of space above the
top of stack (before copying argc and argv) and set AX to that
address, correct?
Yes. And you need to maintain it.
At the very least you need to initialize
On Thu, May 8, 2008 at 12:56 PM, Brian L. Stuart [EMAIL PROTECTED] wrote:
I've found something that looks odd in the way v9fs
under Linux interacts with a fossil running on Plan 9.
If I create a file by redirecting output, the shell
seems able to happily create the file. If I try to
cp a
-- Original message --
From: Eric Van Hensbergen [EMAIL PROTECTED]
On Thu, May 8, 2008 at 12:56 PM, Brian L. Stuart [EMAIL PROTECTED] wrote:
- v9fs defines P9_OEXCL to be 4, where
/sys/include/libc.h defines OEXCL to be 0x1000
Which version of v9fs
From: Brian L. Stuart [EMAIL PROTECTED]
From: Eric Van Hensbergen [EMAIL PROTECTED]
On Thu, May 8, 2008 at 12:56 PM, Brian L. Stuart [EMAIL PROTECTED]
wrote:
- v9fs defines P9_OEXCL to be 4, where
/sys/include/libc.h defines OEXCL to be 0x1000
Which version of v9fs are you
So I have to allocate 56 bytes (sizeof(Tos) on 386) of space above
the
top of stack (before copying argc and argv) and set AX to that
address, correct?
Yes. And you need to maintain it.
At the very least you need to initialize tos-pid
and update it on return from rfork.
I set EAX before
I set EAX before starting the executable, but still no luck :(
On Plan 9, for /bin/mk:
acid: symbols(_tos)
_tos D 0x00016084
acid: mem(0x00016084, X)
0xdfffefc8
I'm probing address 0x16084 on linux after every instruction (using
ptrace's singlestep), and it
It seems bizarre that factotum would
volunteer my terminal's user id, which is totally disjoint from the
user id namespace of the cpu server.
if the user id namespace is disjoint, does that mean you are running
more than one auth server?
- erik
Hi Russ,
You should print AX after every instruction too, to see if
you've actually set it up the way you think you did.
I did, and to my surprise, AX is 0, even though I set it properly in
the loader. It appears as if Linux is setting AX to 0 sometime after
the loader finishes, but
14 matches
Mail list logo
