From: Sam <sah@softcardsystems.com>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] booting issue
Date: Fri, 12 Jul 2002 13:31:14 -0400 [thread overview]
Message-ID: <Pine.LNX.4.30.0207121328060.2801-100000@athena> (raw)
pbslba did the trick. I updated the wiki - my very first experience - to
reflect the quick solution. May I give a giant *huzzah* for the wiki?
Very cool.
Cheers,
Sam
On Fri, 12 Jul 2002, Sam wrote:
> Hello gang,
>
> It's time to update our cpu/fs here to 4e and while reading over
> Forsyth's wiki "upgrade roadmap" if you will, I realize I need
> a kfs system running 4e.
>
> I've had a 4e install on my disk for some time, but it wouldn't
> boot and I haven't had time to poke at it. Now is the time. Here's
> the problem:
>
> The system is a IBM TP 600E, with a 10GB disk. It currently
> boots windoze (for dvds) & linux. The partitions are laid out as follows:
>
> [root@9top sah]# /sbin/fdisk -l /dev/hda
>
> Disk /dev/hda: 240 heads, 63 sectors, 1299 cylinders
> Units = cylinders of 15120 * 512 bytes
>
> Device Boot Start End Blocks Id System
> /dev/hda1 * 1 272 2056288+ 6 FAT16
> /dev/hda2 273 681 3092040 83 Linux
> /dev/hda3 682 752 536760 5 Extended
> /dev/hda4 753 1299 4135320 39 Plan 9
> /dev/hda5 682 752 536728+ 82 Linux swap
>
> ... so my question is, when I boot plan9 from lilo using the
> line:
>
> other=/dev/hda4
> label=plan9
> table=/dev/hda
>
> as has been suggested in the archives, why do I get this on boot
> (roughly):
>
> Loading Plan9
> PBS ... Bad format or I/O error
> Press a key to reboot
>
> and if common, how do I make it stop doing this?
>
> Cheers,
>
> Sam
>
>
next reply other threads:[~2002-07-12 17:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-12 17:31 Sam [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-07-12 14:24 Sam
2002-07-12 15:46 ` Sam
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=Pine.LNX.4.30.0207121328060.2801-100000@athena \
--to=sah@softcardsystems.com \
--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).