From mboxrd@z Thu Jan  1 00:00:00 1970
From: Lucio De Re <lucio@proxima.alt.za>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Strange boot behaviour
Message-ID: <20040213145818.A21321@cackle.proxima.alt.za>
References: <20040212154846.E4743@cackle.proxima.alt.za> <7264eca72458d500639cb8fcb8c4ca79@plan9.bell-labs.com> <20040213081548.K4743@cackle.proxima.alt.za>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
In-Reply-To: <20040213081548.K4743@cackle.proxima.alt.za>; from Lucio De Re on Fri, Feb 13, 2004 at 08:15:48AM +0200
Date: Fri, 13 Feb 2004 14:58:19 +0200
Topicbox-Message-UUID: e2171742-eacc-11e9-9e20-41e7f4b1d025

On Fri, Feb 13, 2004 at 08:15:48AM +0200, Lucio De Re wrote:
>
> On Thu, Feb 12, 2004 at 09:35:59AM -0500, David Presotto wrote:
> >
> > So, if you load a 9pcf and a 9pcdisk both built from the same sources,
> > one can see #S/sd00/fossil and the other can't?  That should be
> > impossible.  I have no idea why that would be.
> >
> It isn't impossible, unless I'm misreading the new trace (appended
> below).  It is extremely unlikely that the 9pcdisk and 9pcf kernels
> are significantly different because of something I did and I suppose
> supplying sources etc won't really help unless I supply the hardware
> too :-(
> >
For the record, running fossil on top of a network loaded 9pcdisk
(with the necessary tweaks to recognise the SCSI controller - added
below unless I forget), seems just fine.  Not that I've done anything
extraordinary with it, not a Venti in sight, for example.

I just want the machine to be self-contained and running a CPU
kernel, so I still need a solution to my problem.  My feeling is
that somehow the partition information is not being read correctly,
but there isn't any obvious reason for it.

If no one has a better suggestion, I'll try to add debugging
information to 9load and the various kernels and watch what happens,
over the weekend.

++L