At 5:56 PM -0800 11/3/00, Henry B. Hotz wrote:

:)I don't think bootpath and bootargs are supported in OF 1.0.5 so I
:)don't understand where they might come from.  Can anyone comment?

Actually, they do. 'boot scsi-int/sd@3:0,OFWBOOT.XCF fd' and 'boot
scsi-int/sd@3:0,OFWBOOT.XCF /bandit/gc/swim3' actually load ofwboot.xcf
from the CD and the kernel from the floppy.

:)SYNOPSIS
:)	boot {promdev[@addr][:part],}ofwboot.xcf exit
:)	boot {promdev[@addr][:part],}ofwboot.xcf -{a|s|d}[a|s|d...]
:)	boot {promdev[@addr][:part],}ofwboot.xcf
:)		[[promdev[{:|,}partition]]/]filename[ a|s|d...]

Don't forget
	boot {promdev[@addr][:part],}
where in some cases you don't need a filename (such as if you're booting
from a `partition zero' bootloader which knows to use ofwboot.xcf.  Of
course specifying ofwboot.xcf doesn't affect it at all, but it's not
strictly necessary.

:)	ofwboot is the primary boot loader for the Macintosh PowerPC
:)port of NetBSD.  It depends on Open Firmware for it's I/O to read the
:)NetBSD kernel.  If promdev is a SCSI disk then addr is the SCSI id.
                                                                  ^^
ID.

:)If the command line options are missing or invalid it will read Open
:)Firmware environment variables to get its options as described under
:)ENVIRONMENT.  If it still can't load a file then the -a option is
:)forced.

"Note, the default environment variables are to boot MacOS".

:)	In addition a filename can be given followed by the above
:)option letters without the `-' flag.  It can be a full path for some
:)versions of Open Firmware on some filesystem types.  It can be
:)preceded by an Open Firmware device path including unit number.  The
:)partition number will be deleted on Open Firmware versions 1 and 2,
:)and will be forced to zero on Open Firmware 3 or greater.

The last part isn't clear.  Partition numbers do matter in all versions of
OF.  Many typical uses are partition zero (for `partition zero' bootloaders
(floppy, HD for OF 1 and 2) and ISO CD-ROMs).

:)	Open Firmware environment variables can be displayed with
:)printenv (no arguments) and set with setenv (same as under csh) from
:)the Open Firmware command line.  Booting MacOS or booting with
:)cmd-opt-P-R held down resets them to their default values.

AFAIK:  Booting MacOS on OF 3 machines changes nothing.  On OF 2 machines
only affects real-base.  On OF 1 machines resets all to default values.

Someone correct me if I'm wrong.

So far so good, thanks for working on this!

  -- MW