>
>Hi,
>
>NetBSD/mipsco doesn't do anything with the bootmode environment
>variable - it is only used by the PROM monitor at startup time.
>
>According to the documentation I have:
>
>   If bootmode is c, the PROM monitor does a cold boot.   A cold boot loads
>   the file specified by the environment variable bootfile and passes it
>   the argument -a.  Typically, bootfile is the standalone shell (sash).
>   Sash interprets the -a option as a request to load the operating system
>   as specified in the volume header of the device from which sash was
>   loaded.

Is it a electronical documentation ? or a parper one ?

>
>In NetBSD speak, the -a option is a "ask for root device" the logic of
>which is defined in sys/boot_flag.h as:
>
>         switch (arg) {                                          \
>         case 'a': /* ask for file name to boot from */          \
>                 (retval) |= RB_ASKNAME;                         \
>                 break;                                          \
>
>Therefore, it is behaving as expected for NetBSD, but maybe not for
>RISC/os
>
>The MD layer is capable of over-riding the behavour, but as it stands it
>passes the flags thru for default *BSD type behavour.
>
>If this is causing a problem for you in some way could you give us more
>detail on why you consider this an issue.

No problem for me, the only think I need is a standalone boot.
how do you want to process ?  reading a PROM variable telling the kernel
to overide -a argument if set ?

Julien

_________________________________________________________________
Add photos to your e-mail with MSN 8. Get 2 months FREE*. 
http://join.msn.com/?page=features/featuredemail