9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Paul Lalonde <plalonde@telus.net>
To: 9fans@cse.psu.edu
Subject: [9fans] Booting Plan9 standalone and in vmware
Date: Mon,  1 Nov 2004 17:39:45 -0800	[thread overview]
Message-ID: <4186E561.2050707@telus.net> (raw)

I've been trying to get my Plan 9 installation to boot either from power 
on (I use grub as my boot loader, and the disk in question is on 
#S/sdD0, and that boots fine that way), or from vmware (where if I mount 
both disks, I get grub, select my plan 9 option, and it boots fine).  
The catch comes that most of the time my machine comes us as linux, and 
I want it to reboot that way automatically.  If I'm slow on the uptake 
in vmware, it tries to boot my linux partition and things go to hell in 
a handbasket. 

I'd like to set up my vmware machine to use my machine's /dev/hdc as 
#S/sdC0 so that I can use the mbr on that drive to get into plan9 
directly when using the vm.  Doing so, boot requests a root drive and 
user, then prints:
time...
fossil(#S/sdC0/fossil)...fsOpen: open /dev/sdD0/fossil: 
'/dev/sdD0/fossil does not exist'

etc, ending in a panic: boot process died: unknown.

Where is this reference to /dev/sdD0/fossil encoded?  In asking for the 
root it correctly prompts with [local!#S/sdC0/fossil], and I would 
expect to try opening that instead of sdD0.

Any ideas?

Thanks,
    Paul



             reply	other threads:[~2004-11-02  1:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-02  1:39 Paul Lalonde [this message]
2004-11-02  2:46 ` Kenji Okamoto
2004-11-02  2:52   ` Paul Lalonde
2004-11-02  3:24   ` andrey mirtchovski
2004-11-02  4:12   ` blstuart
2004-11-02 12:16   ` boyd, rounin
2004-11-04  1:58     ` Kenji Okamoto
2004-11-02  1:54 YAMANASHI Takeshi
2004-11-02  2:08 ` Paul Lalonde
2004-11-02  2:21   ` andrey mirtchovski
2004-11-02  2:48     ` Paul Lalonde

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=4186E561.2050707@telus.net \
    --to=plalonde@telus.net \
    --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).