From: andrey mirtchovski <mirtchov@cpsc.ucalgary.ca>
To: 9fans@cse.psu.edu
Subject: Re: RE: RE: [9fans] boot error walking
Date: Fri, 13 Feb 2004 07:09:02 -0700 [thread overview]
Message-ID: <18f255a4a8e3663476b54ad398168871@plan9.ucalgary.ca> (raw)
In-Reply-To: <5031791e.791e5031@rutgers.edu>
the bootfile argument is just a prompt telling 9load where to look
for a kernel.
the first item is the disk -- sdC0 is correct since you have only one
disk, and it's IDE. if you had a second or were booting from cdrom it
could be sdC1 or sdD0.
the second is the partition on the disk (out of the plan9 slice) -- in
a kfs installation the main partition is called 'fs', in fossil it's
'fossil'. the small-ish dos partition holding the kernels is 9fat.
since 9load doesn't know about fossil at all and it seems like it has
no idea of kfs, your safest bet is to continue using 9fat and just
copy your freshly compiled kernels there.
the third one is the path to the kernel. in Plan 9 kernels are put by
default in /386 (ls that dir and you'll see them there).
so, the menu entry should be sdC0!9fat!9pcauth...
andrey
> Well if kfs is dead, long live fossil! I'll reinstall with the fossil filesystem. The bootfile in plan9.ini will now be:
>
> bootfile:sdC0!fs!9pcauth
>
> according to the wiki. But also according to the wiki the menu bootfile in plan9.ini is:
>
> bootfile:sdC0!9fat!9pcauth
>
> Is this right?
>
> And thanks,
> Brian
>
next prev parent reply other threads:[~2004-02-13 14:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-13 14:49 Herbert B. Hancock
2004-02-13 14:09 ` andrey mirtchovski [this message]
2004-02-13 15:06 ` David Presotto
2004-02-13 15:14 ` ron minnich
2004-02-13 14:55 Tiit Lankots
2004-02-13 15:20 Tiit Lankots
2004-02-13 15:23 Tiit Lankots
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=18f255a4a8e3663476b54ad398168871@plan9.ucalgary.ca \
--to=mirtchov@cpsc.ucalgary.ca \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).