From: yy <yiyu.jgl@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] plan9 go output faults on 9vx with rfork
Date: Mon, 24 Jan 2011 18:18:58 +0100 [thread overview]
Message-ID: <AANLkTi=FSygkwVDWG5qrNDb0XJ6YKXio3wa-Tz1F5H+i@mail.gmail.com> (raw)
In-Reply-To: <AANLkTi=1HAk4m7sHPy8VhsLWNQ3gOh8oLBNni+anOk3w@mail.gmail.com>
2011/1/23 ron minnich <rminnich@gmail.com>:
> change all sem* bits in a/sysproc.c to use uint32 not long
> change ed script so it won't do the wrong thing in future.
Just for the records, the ed scripts are not working with current
kernel sources, they need to be updated. I gave it a try, but
sometimes I started from the ed script and sometimes from the .c file.
I was just trying to make it work, but would be surprised if it worked
well (as a matter of fact, last time I tried to update the code using
the ed scripts I broke 9vx and it was a hassle for everyone, just see
this thread: http://9fans.net/archive/2010/09/190). In particular, the
use of uint32 or long is not uniform. The situation is even worse for
the ip code, there are no scripts at all. This is in my TODO list, but
I'm not working on it now and I don't know when (or if) I will.
--
- yiyus || JGL . 4l77.com
next prev parent reply other threads:[~2011-01-24 17:18 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTikJ3y5exFtTic+8dhUsUqeZBDmR=S-8VzKDK0GH@mail.gmail.com>
[not found] ` <AANLkTink4CrELJfGf3W15caSYX8Se5ygsm_WeMRdCBz=@mail.gmail.com>
[not found] ` <AANLkTikUa1KF+8NP54BHicus++YbeZbD48E7z=1H0Y5V@mail.gmail.com>
[not found] ` <AANLkTinAe_r2EbqOHZGVjaN8yDbhja0m5MUuJfMrn6Cs@mail.gmail.com>
2011-01-20 6:59 ` ron minnich
2011-01-20 16:48 ` David Leimbach
[not found] ` <AANLkTintaOjTpC6Eaz3Ka7256KXYzaDeYg3jsqbCT5Wx@mail.gmail.com>
[not found] ` <AANLkTim3MH0t6H1522DnHf-P_E7a0rtt6FzY9f3ti10i@mail.gmail.com>
[not found] ` <AANLkTi=1btTKGVd_gKk+abAjTEwsEPMBhP4L3agrDubg@mail.gmail.com>
[not found] ` <AANLkTimuhE_G46f0J3nRBos1kVSDvTvUwvUb8u0RsR4A@mail.gmail.com>
[not found] ` <AANLkTiki2v5MgdxwgjQpJopnrRQhBXKm80+aua_FFAef@mail.gmail.com>
[not found] ` <AANLkTi=fi2Xm0R1Jx2NcrKUkyJaYqnizDP0xJPgaenMY@mail.gmail.com>
2011-01-23 2:43 ` ron minnich
2011-01-23 2:48 ` erik quanstrom
2011-01-23 2:56 ` ron minnich
2011-01-23 3:00 ` erik quanstrom
2011-01-23 19:20 ` Charles Forsyth
2011-01-23 19:15 ` Devon H. O'Dell
2011-01-23 20:40 ` EBo
2011-01-23 22:00 ` ron minnich
2011-01-24 12:11 ` EBo
2011-01-24 17:18 ` yy [this message]
2011-01-24 17:24 ` erik quanstrom
2011-01-25 14:28 ` Richard Miller
2011-01-24 17:24 ` ron minnich
2011-02-08 0:05 ` yy
2011-01-24 20:02 ` Steve Simon
2011-01-23 23:40 ` Charles Forsyth
2011-01-24 1:18 ` ron minnich
2011-01-24 12:17 ` EBo
2011-01-24 17:16 ` ron minnich
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='AANLkTi=FSygkwVDWG5qrNDb0XJ6YKXio3wa-Tz1F5H+i@mail.gmail.com' \
--to=yiyu.jgl@gmail.com \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).