From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <41A186E4.8030307@telus.net>
Date: Sun, 21 Nov 2004 22:27:48 -0800
From: Paul Lalonde <plalonde@telus.net>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
	rv:1.6b) Gecko/20031205 Thunderbird/0.4
MIME-Version: 1.0
To: Paul Lalonde <plalonde@telus.net>
References: <9db9f0f0b8b406624cb2566b76698029@plan9.ucalgary.ca>
	<41A03239.1070905@telus.net>
In-Reply-To: <41A03239.1070905@telus.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: [9fans] Re: Booting a new kernel
Topicbox-Message-UUID: 07d64a88-eace-11e9-9e20-41e7f4b1d025

I'm an idiot.  My vmware machine had a disk mounted that the 9fat: 
script found it, instead of my usual boot partition.  It's working fine 
now.

The next thing is to get my pxe booting going, and it's going well 
(9pxeload is running on the new terminal), but I'm having troubles 
creating /cfg/pxe/xxxxxxxxxx, as I have no rooted cfg directory,
and mkdir tells me that I can't make one on '/', which is what I'd expect.

Should I just build the tree somewhere arbitrary and bind it?

Paul

Paul Lalonde wrote:

> I'm trying to build a CPU/auth server, and I'm failing to get it to 
> boot.  I've placed the kernel in the fat partition, same place as my 
> terminal kernel (which works fine, and is one I built myself a while 
> ago), and added an entry in my plan9.ini allowing me to choose it:
>
> [4e]
> bootfile=sdD0!9fat!9pcfnew
> bootfile=sdD0!9fat!9pccpuf
>
> When I choose 9pcfnew it works fine, but when I try 9pccpuf I get the 
> error:
> error walking to 9pccpuf
> Boot devices: ....
>
> Any clues?
> Thanks,
>    Paul
>
>