9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: ron minnich <rminnich@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Returning to Plan 9: Virtualization, Distributions
Date: Tue, 22 Nov 2011 15:21:39 -0800	[thread overview]
Message-ID: <CAP6exYKcZZXPsLYgGigvUMuFsOkAgHt0aeXiYbOupxO9zn4cBA@mail.gmail.com> (raw)
In-Reply-To: <de375f7bc0a1eaffd389018bcf4b258a@brasstown.quanstro.net>

There's confusion here, and I am partly to blame ...

if you get googlecode.com/p/nix-os

you'll get a file system image that will be usable on a 32-bit
machine. We use it with 9vx. That image includes all the bits you need
to build and boot a NIX kernel. The intent of this distro is to allow
32-bit users to create 64-bit kernels and test. So the nix-os repo is
designed to let you set up on a 32-bit machine and bootstrap a
separate 64-bit machine. We thus envision you having more than one
system available.

I use it as follows:
hg clone http://googlecode.com/p/nix-os nix-os
cd nix-os
./9vx.OSX10.6 -r . -u rminnich
(get on the machine)
objtype=386
cd /sys/src/ape/lib
mk install
cd /sys/src
objtype=amd64
mk install
cd /sys/src/nix/k10
mk install

You are then good to go, unless I missed a step. You need some 386
bits from ape to build the 64-bit code.

We've set up nix-os root file system to play nice with 9vx, which is
why we include a 9vx for osx in the file system.

so to repeat: nix-os is a mercurial image of a root file system for
32-bit nodes, and it is intended to make it easy for you to boot
64-bit nodes. We assumed that you had at least one 32-bit and one
64-bit system.

I hope this helps a little.

ron



  reply	other threads:[~2011-11-22 23:21 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-22 15:39 Joel C. Salomon
2011-11-22 15:46 ` ron minnich
2011-11-22 15:56   ` Gabriel Díaz López de la llave
     [not found]   ` <CAL_gH73FUfzOdFg1HHMomr8_kubMwYvraXnkYUqQQ4hbzD33iw@mail.gmail.c>
2011-11-22 16:00     ` erik quanstrom
2011-11-22 22:57       ` Joel C. Salomon
2011-11-22 23:04         ` erik quanstrom
2011-11-22 23:21           ` ron minnich [this message]
2011-11-23  7:49             ` Francisco J Ballesteros
2011-11-22 23:06         ` John Floren
2011-11-22 19:41 ` Jack Norton
2011-11-22 22:50   ` Joel C. Salomon
2011-11-22 23:00     ` Giacomo Tesio
2011-11-22 22:14 ` John Floren
2011-11-22 22:53   ` [9fans] Let's get VM configs onto the Wiki Lyndon Nerenberg
2011-11-22 22:58     ` erik quanstrom
2011-11-22 23:12       ` Lyndon Nerenberg
2011-11-22 23:22         ` andrey mirtchovski
2011-11-22 23:22           ` andrey mirtchovski
2011-11-22 23:37             ` Lyndon Nerenberg
2011-11-22 23:33       ` andrew zerger
2011-11-24 21:16     ` Bakul Shah
2011-11-24 21:25       ` Lyndon Nerenberg
2011-11-24 22:05       ` ron minnich
2011-11-24 22:28         ` Bakul Shah
2011-11-27  0:14 ` [9fans] Returning to Plan 9: Virtualization, Distributions Ruben Schuller
2011-11-27  6:29   ` Jens Staal
2011-11-27  7:08     ` John Floren
2011-11-27  9:18       ` Lucio De Re

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=CAP6exYKcZZXPsLYgGigvUMuFsOkAgHt0aeXiYbOupxO9zn4cBA@mail.gmail.com \
    --to=rminnich@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).