From mboxrd@z Thu Jan  1 00:00:00 1970
MIME-Version: 1.0
In-Reply-To: <AANLkTinPvPjyw=cNgyVqs43zvJc=pOrFavXVYEEYkJ17@mail.gmail.com>
References: <AANLkTinPvPjyw=cNgyVqs43zvJc=pOrFavXVYEEYkJ17@mail.gmail.com>
Date: Sun, 12 Dec 2010 22:18:32 -0800
Message-ID: <AANLkTinYZZ5w4JtRoJS4==PadZFvYzX+aULX+wzJg47U@mail.gmail.com>
From: ron minnich <rminnich@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Content-Type: text/plain; charset=ISO-8859-1
Subject: Re: [9fans] plug boot problem
Topicbox-Message-UUID: 8bff7674-ead6-11e9-9d60-3106f5b1d025

On Sun, Dec 12, 2010 at 4:37 PM, ron minnich <rminnich@gmail.com> wrote:
> I am having a simple problem which I know I've already solved -- but
> the machine is elsewhere.


It's turning out not to be simple at all. The *init* is the init
process. It is the hand-crafted kernel process and it sets up an
initial name space and calls exec with a boot file name and argv. The
exec file name is /boot/boot; the argv is supplied by the kernel. It's
bogus; arg[1] is 2.

I'll let you now. No idea why this is an issue when I'm not using
standard boot (yet).

ron