On Tuesday, October 15, 2002, at 07:04 AM, Daniel Eggert wrote:

>
> On s=F8ndag, okt 13, 2002, at 01:24 Europe/Copenhagen, Michael Bartosh=20=

> wrote:
>
>> OK, some progress-
>>
>> when I give the .gz as an argument to the boot cmd- ie-
>>
>> boot scsi-int/sd@0:,\OFWBOOT.XCF;1 NETBSD.GZ;1

I think this type of command works when the machine is working with
a cd9660 (iso) style image and not hfs. I get the impression from the
install docs that some versions of earlier macs only work with iso=20
filesystems
and some with only hfs, and some with both. This could be partly a=20
matter
of how you burned the disk, as I ran into something like this on a=20
powerbook
G4 where I didn't burn the disk right, and it only saw the iso=20
filenames in
capitals, instead of the lower case filenames.

As far as the kernel filename, it seems to depend on what type of=20
filesystem
it is being read from as to how to name it. If I put the ofwboot.xcf=20
and netbsd.gz
files on the hfs partition, I think I was using something like

boot hd:,\ofwboot.xcf hd:\netbsd.gz

in recent times I finally found out that I could boot just ofwboot.xcf=20=

from the
hfs partition and netbsd from my netbsd a partition (partition 11 in my=20=

case) using

boot hd:\ofwboot.xcf hd:11,/netbsd

The upshot is that the filenames change depending upon the underlying
filesystem that you are using, and the ofw dir command only works on ofw
supported filesystems.  I don't recall if it is another netbsd port, or=20=

linux which
has a facility in the boot program that allows you to get a directory=20
listing off
of the disk. However, Since ofwboot alone knows what it understands, if=20=

it
could give a directory listing from whatever it was reading from, it=20
might help
sort out these confusions. Maybe even partition info would be needed in=20=

some
instances. Personally, I looked at the source for ofwboot and got=20
somewhat
confused, but think I may have finally figured out how it gets stuff=20
off of different
style filesystems, but am not at all sure. I find it a very surprising=20=

program.

>>
>> ... I don't see the error about
>>
>> /netbsd: Inappropriate file type or formatt
>>
>> However the boot still hangs at the 0x800000 line
>
> What exactly are you seeing.
> What do you mean by 'the 0x800000 line'?
>
>> On Saturday, October 12, 2002, at 04:44 PM, Michael Bartosh wrote:
>>
>>> I'm trying to follow the ANS con RAID directions.
>>>
>>> a) the format of the command in the pdf:
>>>
>>> boot scsi-int/sd@0:,\ofwboox.xcf
>>>
>>> ...isn't working. I'm having to do:
>>>
>>> boot scsi-int/sd@0:,\OFWBOOT.XCF;1
>>>
>>> ...to get the loader to go.
>>>
>>> Then, instead of a Boot: prompt, it's like the loader is trying to=20=

>>> boot something called /netbsd, which fails because it's not there=20
>>> (netbsd.gz... is)
>>>
>>>
>>> I don't recall this happening when I ran an install on my 700.
>>>
>>> Ideas?
>
>
> Daniel
>