From: Lucio De Re <lucio@proxima.alt.za>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Strange boot behaviour
Date: Fri, 13 Feb 2004 14:58:19 +0200 [thread overview]
Message-ID: <20040213145818.A21321@cackle.proxima.alt.za> (raw)
In-Reply-To: <20040213081548.K4743@cackle.proxima.alt.za>; from Lucio De Re on Fri, Feb 13, 2004 at 08:15:48AM +0200
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
next prev parent reply other threads:[~2004-02-13 12:58 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-12 13:48 Lucio De Re
2004-02-12 14:35 ` David Presotto
2004-02-12 16:16 ` [9fans] seeking for the truth rog
2004-02-12 16:32 ` David Presotto
2004-02-12 17:10 ` rog
2004-02-12 16:50 ` Dave Lukes
2004-02-12 16:59 ` Rob Pike
2004-02-12 17:03 ` Fco.J.Ballesteros
2004-02-12 17:17 ` Charles Forsyth
2004-02-12 17:22 ` Charles Forsyth
2004-02-12 18:00 ` rob pike, esq.
2004-02-12 18:05 ` Charles Forsyth
2004-02-12 18:10 ` rog
2004-02-12 18:10 ` David Presotto
2004-02-12 17:26 ` Fco.J.Ballesteros
2004-02-12 17:35 ` Dave Lukes
2004-02-12 20:19 ` boyd, rounin
2004-02-13 6:15 ` [9fans] Strange boot behaviour Lucio De Re
2004-02-13 12:58 ` Lucio De Re [this message]
2004-02-14 21:49 ` David Presotto
2004-02-16 5:52 ` Lucio De Re
2004-02-16 6:39 ` Lucio De Re
2004-02-16 9:22 ` Lucio De Re
2004-02-17 15:20 ` 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=20040213145818.A21321@cackle.proxima.alt.za \
--to=lucio@proxima.alt.za \
--cc=9fans@cse.psu.edu \
/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).