From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Fri, 1 Feb 2008 17:42:17 +0000 To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu> Subject: Re: [9fans] Serious Problem Running Plan 9 on Virtual PC From: "Eris Discordia" Content-Type: text/plain; format=flowed; delsp=yes; charset=iso-8859-15 MIME-Version: 1.0 References: <483225c878c1c7865dfdcc3e26c53c35@quanstro.net> Content-Transfer-Encoding: 7bit Message-ID: In-Reply-To: <483225c878c1c7865dfdcc3e26c53c35@quanstro.net> User-Agent: Opera Mail/9.23 (Win32) Topicbox-Message-UUID: 3f489bec-ead3-11e9-9d60-3106f5b1d025 On Fri, 01 Feb 2008 15:43:36 -0000, erik quanstrom wrote: >> >> I have noticed an eccentricity: when the live system boots, it boots >> from >> #S/dev/sdD0/data but the installed system boots from >> #S/dev/sdC0/fossil. I >> tried changing that to #S/dev/sdC0/data, but then the boot process >> complains that it cannot find /boot/kfs and stops. > > that's because you boot from a (virtual?) cdrom during the install > process. > typically this is sdD0. when you boot from the normal system, you boot > from the virtual hard drive, sdC0. the super special el torito process > makes a cdrom appear differently when its booted from than when > it's just accessed normally. > > - erik > I see, thanks for the explanation. I suppose then, that #S/dev/sdC0/fossil is perfectly OK for booting from. With this situation at hand, and the bag of nasty little tricks empty, I think the better option is to either try another virtualization/emulation solution (I gave up on Bochs x86 emulator just a few minutes ago, it was too unstable and slow for my purpose) or get a used hard drive for that little old PC sitting in the corner of my room. -- Using Opera's revolutionary e-mail client: http://www.opera.com/mail/