Pietro Gagliardi wrote:
- Modify the kernel (it is based on Unix - even Microsoft says so)
Sure it is...in the same way that VMS is based on UNIX (which means not
at all)
>> I think this is at the root of why 9vx cannot run on MS-Windows.
> No, it's not.
I can only appologise for emailing before reading the vx30 paper properly,
I now understand (some of) how cunning it really is.
I 9vx for windows is the way to go.
Thanks russ.
-Steve
>> Apparently, after a fork, a child retains it's parent's
>> pid in _tos->pid.
>
> I think this is at the root of why 9vx cannot run on MS-Windows.
No, it's not. The words fork and pid in that sentence
are concepts completely internal to 9vx. The host OS,
be it OS X or Linux or Windows, has a
- Modify the kernel (it is based on Unix - even Microsoft says so)
- Learn how Cygwin does it
- Don't use real processes, like in Inferno
On Jun 30, 2008, at 8:34 AM, Steve Simon wrote:
Apparently, after a fork, a child retains it's parent's
pid in _tos->pid.
I think this is at the root of wh
> Apparently, after a fork, a child retains it's parent's
> pid in _tos->pid.
I think this is at the root of why 9vx cannot run on MS-Windows.
I have been very slowly crawling towards an updated port of 9pm
(p9p for windows as it was) learing the Windows API and the plan9
kernel as I go.
The one
> Thank you for the detailed reports.
> It makes it very easy to fix the bugs!
It really is my pleasure. Hunting bugs is
one of my favorite pastimes. Well, that's
not completely true: hunting bugs is usually
only fun when dealing with code of a certain
quality. Plan 9 makes the cut, as does all
of
> On 9vx, iostats suicides:
>
> term% iostats echo
> iostats 128: suicide: sys: trap: page fault pc=0xb21c
>
> Apparently, after a fork, a child retains it's parent's
> pid in _tos->pid. It isn't updated until the next syscall
> finishes with kexit.
>
> This is a problem if the child's f
On 9vx, iostats suicides:
term% iostats echo
iostats 128: suicide: sys: trap: page fault pc=0xb21c
Apparently, after a fork, a child retains it's parent's
pid in _tos->pid. It isn't updated until the next syscall
finishes with kexit.
This is a problem if the child's first function call i
