9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Bakul Shah <bakul@bitblocks.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] what arch
Date: Fri,  9 May 2014 13:51:46 -0700	[thread overview]
Message-ID: <20140509205146.3DD03B827@mail.bitblocks.com> (raw)
In-Reply-To: Your message of "Fri, 09 May 2014 13:37:04 PDT." <CAP6exYL5KwdwKGM-KkFboHXpTt+Xv7o7WnHLm08OPGY1QX-xmg@mail.gmail.com>

On Fri, 09 May 2014 13:37:04 PDT ron minnich <rminnich@gmail.com> wrote:
> somebody referred me to the discussion.
>
> Sometimes we found people wanted to build on their existing OS (Linux,
> OSX, whatever) in a cross-build way, and, further, didn't want to do
> that in a VM, because they had tools they liked.
>
> github.com/rminnich/NxM is the last snapshot of the Sandia/BL fork,
> and it has scripts and instructions to crossbuild it all on Linux.
> It's not elegant but it works. At the time, we used Gerrit and Jenkins
> for our control and validation. For each commit, gerrit would kick off
> a jenkins run, which would do the full build from scratch, boot in
> qemu, and run a set of regression tests. Gerrit would -1 the patch if
> the jenkins pass did not work.
>
> Full build, starting from nothing, of tools, libs, bin, kernels, was
> about two minutes on Linux. If you added gs into the mix, it was more
> like 4 minutes IIRC. Ran fine on amd64.

Seems very slow : )

Full plan9 *native* build of the kernel, libs and bin on a
/RapsberryPi/ is about 4 minutes Crossbuilding i386 kernel on
it takes about 3 minutes (I haven't tried a full crossbuild).
Building the 9pi kernel under 9vx takes about 11 seconds on my
MBP @ home. Don't recall the full build time.

For comparison, a native Linux kernel build on RPi takes over
10 hours.

For another comparison, RPi seems about 16-20 time slower
compared to a MBP.

> One suggestion I'd like to float here: the LPL is a problem for both
> BSD and GPL worlds (see Theo's notes from 2003 on that issue). It
> might be useful for new from-scratch software to be released under
> 3-clause BSD; or under the Inferno license for that matter. In other
> words, if you don't have to use the LPL, use 3-clause BSD instead. One
> person has already very kindly allowed us to use their drivers in
> Akaros with the LPL replaced with 3-clause BSD.

Agree.



  parent reply	other threads:[~2014-05-09 20:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-09 20:37 ron minnich
2014-05-09 20:44 ` erik quanstrom
2014-05-09 20:48 ` erik quanstrom
2014-05-09 20:51 ` Bakul Shah [this message]
2014-05-09 21:40   ` ron minnich
2014-05-09 21:46 ` Charles Forsyth
2014-05-09 22:05   ` 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=20140509205146.3DD03B827@mail.bitblocks.com \
    --to=bakul@bitblocks.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).