From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <4627CCBF.20103@conducive.org> Date: Fri, 20 Apr 2007 04:10:39 +0800 From: W B Hacker User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8.0.8) Gecko/20061030 SeaMonkey/1.0.6 MIME-Version: 1.0 To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu> Subject: Re: [9fans] something evil happening when partitioning a hdd with the plan9 installer References: <20070409055131.18fa0ecc@minitux.homeshield> <9f3897940704090220h38b97aa5w357553c0eeab45d5@mail.gmail.com> <4627938b.770bb367.10ad.4f71@mx.google.com> In-Reply-To: <4627938b.770bb367.10ad.4f71@mx.google.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable Topicbox-Message-UUID: 4c8298e0-ead2-11e9-9d60-3106f5b1d025 John Soros wrote: > Okay, now plan9 is working on my laptop, here is how I did it: I made a > primary partition for plan9 in lunix, then I used fdisk to set the part= ition > type to plan9 (this is the only partitioning program that know plan9 ty= pe > partitions). It may be the only one you have used that correctly reports them as Plan9= , but=20 it is by no means the only one that can create and manipulate a Plan9 par= tion. All that FreeBSD's toolset needs is the correct decimal or hex partion ty= pe code=20 to effect that. Not hard to then hack and re-assemble boot0 so that it th= en=20 reports them correctly as 'Plan9' in the multi-boot choices. >=20 > After this all went pretty easily, I installed the standard way from cd= rom, I > just didn't do any partitioning as that was already done. >=20 > For the bootsetup step I selected plan9 way of booting, and at the ques= tion > wether to install plan9 loader to the MBR I answered No. >=20 > Now I can boot plan9 on the primary partition #1 from grub like so: >=20 > title Plan9 from outer space root (hd0,0) chainloader +1 boot >=20 > Thanks for all the replies, and all the suggestions. Cheers to all plan= 9 > users! I there's any plan9 users in Hungary, I'd be very happy to meet = them!=20 > John boot0 - combined with the 'as issued' Plan9 '9fat' loading tools, does t= hat=20 reasonably well w/o grub or Lilo. The advantage is that it is less sensit= ive to=20 whether the HDD in question is still in the same relative position as whe= n first=20 installed to (which ordinarily requires editing lilo.conf or grub's menu.= lst). Not ordinarily an issue with single-HDD laptops, but perhaps worht a look= =20 if/as/when Plan9 might have been installed to an external HDD. >=20 >=20 > On Mon, 9 Apr 2007 11:20:22 +0200 "Pawe=C5=82 Lasek" > wrote: >=20 >> On 4/9/07, John Soros wrote: >>=20 >> [cut] >>=20 >> In this case, I'd recommend repartitioning with plain linux fdisk and=20 >> reserve a partition for plan9 using it (Set partition type to plan9, y= ou >> can check the number using built-in help IIRC), then during plan9=20 >> installation just choose that partition and tell plan9 fdisk to don't = write >> anything. >>=20 >> And somebody ought to make plan9 bootable from something other than pr= imary >> partition (The same problem I have with Solaris 10. I could use those = 70 GB >> of hdd in my school computer, but there are not enough primary partiti= on >> numbers left for it's disklabel...) >>=20 >>=20 >=20 I have not yet attempted booting Plan9 from an 'extended' partition, but = have=20 been able to use block-mode loaders to start it from a 'primary' partitio= n=20 (slice) on a 200 GB HDD that was otherwise out of the reach of the BIOS (= 3 older=20 MB tested, some with 1999 vintage BIOS). It should be equally possible to start Plan9 from a non-primary partition= -=20 perhaps the real issue is not 'reaching' it, but whether it can understan= d where=20 it is and finish the boot? The FAT-within-Plan9-fs-type toolset Plan9 uses is still one of the most=20 flexible ways of getting up and running. It shouldn't take much to keep that approach compatible with progressivel= y newer=20 hardware and boot loaders. Bill Hacker