From: "ron minnich" <rminnich@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] Xen 3.1 w/ Plan 9 domU: plan9.img file after install not
Date: Thu, 5 Jul 2007 00:01:59 -0700 [thread overview]
Message-ID: <13426df10707050001s4ac9f3b0h2a3d881479b407d3@mail.gmail.com> (raw)
In-Reply-To: <468C283B.403@sbcglobal.net>
>oot: can't connect to file server: '#S/sdC0/' file does not exist
That should bd sd00 on Xen, not sdC0. Where is sdC0 getting set?
ron
next prev parent reply other threads:[~2007-07-05 7:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-04 16:40 [9fans] Xen 3.1 w/ Plan 9 domU: plan9.img file after install not recognized Mike
2007-07-04 17:05 ` [9fans] Xen 3.1 w/ Plan 9 domU: plan9.img file after install not Richard Miller
2007-07-04 17:26 ` ron minnich
2007-07-06 13:21 ` Richard Miller
2007-07-06 14:43 ` ron minnich
2007-07-06 15:03 ` Richard Miller
2007-07-04 23:07 ` Mike
2007-07-05 7:01 ` ron minnich [this message]
2007-07-05 14:17 ` Mike
2007-07-05 8:39 ` Richard Miller
2007-07-05 14:11 ` Mike
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=13426df10707050001s4ac9f3b0h2a3d881479b407d3@mail.gmail.com \
--to=rminnich@gmail.com \
--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).