From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <4186E561.2050707@telus.net> Date: Mon, 1 Nov 2004 17:39:45 -0800 From: Paul Lalonde User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6b) Gecko/20031205 Thunderbird/0.4 MIME-Version: 1.0 To: 9fans@cse.psu.edu Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: [9fans] Booting Plan9 standalone and in vmware Topicbox-Message-UUID: f9cb2dbe-eacd-11e9-9e20-41e7f4b1d025 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