9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Lucio De Re <lucio@proxima.alt.za>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Trap in 5c compiling rc?
Date: Tue,  7 Dec 2010 08:42:51 +0200	[thread overview]
Message-ID: <20101207064250.GA1908@fangle.proxima.alt.za> (raw)
In-Reply-To: <AANLkTinsB_TQUK6RxN_8v=UgfwJDzvopxqtLk84yhM0K@mail.gmail.com>

On Mon, Dec 06, 2010 at 09:57:50PM -0800, Paul Lalonde wrote:
>
> Getting closer.  I still seem to be lacking syscallfmt.c which is called out
> explicitly in the mkfile but isn't in sysfromiso.  The version in sys/pc
> clearly won't work.
>
You can't just grab it off sources?

	9fs sources
	fcp /n/sources/plan9/sys/src/9/kw/syscallfmt.c /sys/src/9/kw/

I rebuilt 9plug on a fresh native plan 9n distribution in the last hour,
without a hitch.  I even tested it on my sheevaplug and other that I
haven't yet figured out how to get flash going, it worked without any
intervention.

Any suggestions on getting rid of the need for a console by supplying
#F/flash/flash0 and putting intelligent settings in there?  I'd love
to get to the point where the sheeva just starts up without human
intervention when there are file and auth services for it to use.

I'm a little concerned about guessing my way around flash, I'd rather
have instructions that are known to work.  But the sheer simplicity of
the whole system is mind boggling.

++L



  reply	other threads:[~2010-12-07  6:42 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-05  2:12 Paul Lalonde
2010-12-05  8:33 ` Bruce Ellis
2010-12-05  9:41   ` Charles Forsyth
2010-12-05  9:49     ` Charles Forsyth
2010-12-05 11:38       ` Bruce Ellis
2010-12-05 13:24       ` erik quanstrom
2010-12-05 16:16         ` Paul Lalonde
2010-12-05 16:42           ` Paul Lalonde
2010-12-05 18:02             ` Charles Forsyth
2010-12-05 18:15               ` ron minnich
2010-12-05 18:28                 ` ron minnich
2010-12-07  1:08                   ` Paul Lalonde
2010-12-07  1:14                     ` ron minnich
2010-12-07  1:54                       ` erik quanstrom
2010-12-07  3:51                         ` ron minnich
2010-12-07  5:57                           ` Paul Lalonde
2010-12-07  6:42                             ` Lucio De Re [this message]
2010-12-07 13:34                               ` erik quanstrom
2010-12-07 13:37                             ` erik quanstrom
2010-12-07 15:32                               ` Paul Lalonde
2010-12-07 16:26                               ` ron minnich
2010-12-07 16:39                                 ` ron minnich
2010-12-08  4:26                                   ` Paul Lalonde
2010-12-08  0:33                                     ` Lucio De Re
2010-12-08  4:34                                     ` Paul Lalonde
2010-12-08  0:38                                       ` Lucio De Re
2010-12-08  5:25                                     ` ron minnich
2010-12-08  6:13                                       ` Lucio De Re
2010-12-08  6:21                                         ` ron minnich
2010-12-08 12:18                                         ` Paul Lalonde
2010-12-08 13:06                                     ` erik quanstrom
2010-12-08 19:26                                       ` Paul Lalonde
2010-12-05 17:08           ` erik quanstrom

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=20101207064250.GA1908@fangle.proxima.alt.za \
    --to=lucio@proxima.alt.za \
    --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).