Re[2]: [9fans] sources pull - cannot boot (sigh) - sorted

Re[2]: [9fans] sources pull - cannot boot (sigh) - sorted

[steve.simon]

Hi,

All sorted, one change to Russ's instructions, the backup
kernel was called sdC0!fs!/386/_9pcdisk.gz - ie gziped.

Looking at the dates on the kernel source everything looks
like everything it compiled ok - including boot.c.

Just to make sure I did a make clean, deleted /sys/src/9/boot/libboot.a8,
and rebuilt the kernel to prove I can still bootstrap myself, which I can.

Thanks once again Russ,

-Steve
____________________Reply Separator____________________
Subject:    Re: [9fans] sources pull - cannot boot (sigh)
Author: 9fans@cse.psu.edu
Date:       16/12/02 19:23

You don't need to reinstall, but you do need
to get at your plan9.ini.  If you pulled, you should
have gotten a fresh copy of the old kernel in /386/_9pcdisk.

If you can change your plan9.ini to boot from sdC0!fs!/386/_9pcdisk
you should be all set.

If you run Windows on a FAT file system, you can copy
c:\plan9\plan9ini.bak to c:\plan9\plan9.ini and then edit
that -- 9load looks there before 9fat.

If not, http://plan9.bell-labs.com/~rsc/flop.gz is a compressed
floppy image that contains only 9load and a minimal plan9.ini.
You can download that and edit the plan9.ini there (or not;
it will prompt you for a boot file).

As for your actual kernel problem, it sounds like
/sys/src/9/boot/local.c didn't get updated or didn't
get recompiled when you rebuilt your kernel.
The paths in the connectlocal function should
say "/boot/kfs" and not "/kfs".  If they say the
latter, your source is out of date.  If they say the
former, maybe your build used an old object file,
though I thought we had rules in place to do the
right thing.

Russ