From mboxrd@z Thu Jan 1 00:00:00 1970 Content-Transfer-Encoding: 7bit Content-Type: multipart/alternative; boundary="_----------=_1174070708232810" MIME-Version: 1.0 From: ramkromberg@mail.com To: 9fans@cse.psu.edu Date: Fri, 16 Mar 2007 20:45:08 +0200 Message-Id: <20070316184508.5CAC686ADD@cal1-1.us4.outblaze.com> Subject: [9fans] Re: Help a poor man out - poor man's installation. Topicbox-Message-UUID: 26a92012-ead2-11e9-9d60-3106f5b1d025 This is a multi-part message in MIME format. --_----------=_1174070708232810 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1" >If you have anough disk to generate a FAT partition to temporarly hold >the unzip'ed ISO then put it there - or maybe put a spare hard disk in >box temporarly. > >You should then be able to use the boot/install floppy image which is on the >same page as the ISO at the bell-labs site to start the installer. > >It will offer the devices where it thinks the ISO should live and you can >chose your FAT partition; and you are off... > >Don't worry if it takes a long time it often doesn't use DMA during install >but you can turn that on later. Alsi I would suggest you do a fossil only >install for now unless you want to build a proper fileserver, again you >can convert later. > >-Steve I already tried it like so: hda1 linux swap hda2 bootable fat32 with grub4dos hda3 Freesco Linux I put the plan9.iso on hda2 and booted the floppy and got: Boot device: fd0 boot from: so I entered : boot from: sdC1!plan9.iso What did I do wrong ? --_----------=_1174070708232810 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset="iso-8859-1" >If you have anough disk to generate a FAT partition to temporarly hold<= br>>the unzip'ed ISO then put it there - or maybe put a spare hard disk = in
>box temporarly.
>
>You should then be able to use the= boot/install floppy image which is on the
>same page as the ISO at t= he bell-labs site to start the installer.
>
>It will offer the = devices where it thinks the ISO should live and you can
>chose your F= AT partition; and you are off...
>
>Don't worry if it takes a l= ong time it often doesn't use DMA during install
>but you can turn th= at on later. Alsi I would suggest you do a fossil only
>install for n= ow unless you want to build a proper fileserver, again you
>can conve= rt later.
>
>-Steve

I already tried it like so:
hda1 = linux swap
hda2 bootable fat32 with grub4dos
hda3 Freesco Linux
I put the plan9.iso on hda2 and booted the floppy and got:
Boot device= : fd0
boot from:

so I entered :
boot from: sdC1!plan9.iso
<= br>What did I do wrong ?

--=20

3D""

--_----------=_1174070708232810-- From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <24ddae20b271ac31369c12bd4bd1b88b@coraid.com> Subject: Re: [9fans] Re: Help a poor man out - poor man's installation. From: erik quanstrom Date: Fri, 16 Mar 2007 14:12:42 -0500 To: 9fans@cse.psu.edu MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Topicbox-Message-UUID: 26c0dc84-ead2-11e9-9d60-3106f5b1d025 you didn't do anything wrong. i don't think 9load recognizes your [sp]ata chipset. you should see something like this if it recognises the hd: Boot devices: fd0 ether0 sdC0!dos sdC0!9fat in your case you should see sdC1!dos in the list. one further bit, plan 9 does not recognize fat32. - erik From mboxrd@z Thu Jan 1 00:00:00 1970 Content-Transfer-Encoding: 7bit Content-Type: multipart/alternative; boundary="_----------=_117411461393735" MIME-Version: 1.0 From: ramkromberg@mail.com To: 9fans@cse.psu.edu Date: Sat, 17 Mar 2007 08:56:53 +0200 Message-Id: <20070317065653.E044F86ADD@cal1-1.us4.outblaze.com> Subject: [9fans] Re: Help a poor man out - poor man's installation. Topicbox-Message-UUID: 272b40b0-ead2-11e9-9d60-3106f5b1d025 This is a multi-part message in MIME format. --_----------=_117411461393735 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="iso-8859-1" >you didn't do anything wrong. i don't think 9load recognizes your >[sp]ata chipset. you should see something like this if it recognises >the hd: > > Boot devices: fd0 ether0 sdC0!dos sdC0!9fat > >in your case you should see sdC1!dos in the list. one further bit, >plan 9 does not recognize fat32. > >- erik ya, i tried sdC1!dos so its must be the hardware. Figures as much, it is somewhat of a legacy HW ;-) Well, I suppose this thread is resolved, I won't even bother with asking a driver +/- patched kernel so its VM for me ;-) Thankes ! Ram Kromberg ramkromberg@mail.com --_----------=_117411461393735 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset="iso-8859-1" >you didn't do anything wrong.  i don't think 9load recognizes your=
>[sp]ata chipset.  you should see something like this if it rec= ognises
>the hd:
>
>    Boot devices: fd0 = ether0 sdC0!dos sdC0!9fat
>
>in your case you should see sdC1!d= os in the list.  one further bit,
>plan 9 does not recognize fat= 32.
>
>- erik

ya, i tried sdC1!dos so its must be the ha= rdware.
Figures as much, it is somewhat of a legacy HW ;-)
Well, I su= ppose this thread is resolved, I won't even bother with asking a driver +/-= patched kernel so its VM for me ;-)

Thankes !
Ram Kromberg
ra= mkromberg@mail.com

--=20

3D""

--_----------=_117411461393735--