From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <5d375e920703241422p2df7c87ag4575dddffef2c7d7@mail.gmail.com> Date: Sat, 24 Mar 2007 22:22:43 +0100 From: Uriel To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu> Subject: Re: [9fans] Dum-Bass question In-Reply-To: <460593A9.7070707@conducive.org> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <460593A9.7070707@conducive.org> Topicbox-Message-UUID: 303f64e2-ead2-11e9-9d60-3106f5b1d025 glendy# 9fat: glendy# cd /n/9fat glendy# lc 9LOAD 9pc 9pccpuf 9pccpuf.gz 9pcf 9pxeload PLAN9.INI glendy# lookman 9fat man 2 authsrv # authsrv(2) man 4 dossrv # dossrv(4) man 8 9load # 9load(8) man 8 booting # booting(8) man 8 prep # prep(8) man 8 update # update(8) Best wishes uriel On 3/24/07, W B Hacker wrote: > Fans, > > Online docs (http://planb.lsub.org/magic/man2html/8/9load) describing Plan9's > boot process, say, in part: > > ...in order to find configuration information, 9load searches all units on > devices fd and sdCn, in that order, for a file called plan9\plan9.ini or > plan9.ini (see plan9.ini(8)) on a partition named dos or 9fat. If one is found, > searching stops and the file is read into memory at physical address 0x1200 > where it can be found later by any loaded bootfile. Some options in plan9.ini > are used by 9load... > > NB: These may be the wrong docs... Google dasn't *quite* read minds....) > > > Elsewhere, instructions and examples are publshed for *creating* a plan9.ini file. > > My questions are: > > - Does a CD-install of 'native' Plan9 to a combined fossil/venti HDD partition > (eminently bootable, runnable) create a default 'plan9.ini'? > > - If so, *where*, and how can I cat or Sam it from a running system? > > - If not, how and where *does* Plan9 derive the functionally equivalent > information it needs to complete the boot process? > > (i.e. - given that it is operating the hardware as expected, what goes on > if/as/when the above search *fails*?) > > Objective of the exercise (at this point) is to confirm that plan9.ini or > functional equivalent, effects the published default of disabling the second > core in a Core-D P4, and, if so, attempt to re-enable same and see what, if > anything, breaks. > > A mere link to more appropriate docs may be all I need... > > Perplexed (after ls'ing all over Hell and at least half of Texas..) > > Bill Hacker > > > > >