Last I checked attempting to boot off a slave drive using the second
stage didn't pass parameters in correctly (it may load the right
kernel, but then does the wrong thing with root).  Net booting using
the second stage was completely non-functional.

Using just the firmware to do either of these functions works
correctly.  However, the firmware (definitely on a raq2) *does* have a
limitation on size.

I'm unhappy that those features were lost with the addition of the
second stage boot.  (Despite cdi@ calling it a 1st stage, the firmware
really is the first stage.)

Has this changed?

-=erik.


On 8/9/07, Izumi Tsutsui <tsutsui@ceres.dti.ne.jp> wrote:
> cyber@NetBSD.org wrote:
>
> > This seems like a pretty rare situation to add it to GENERIC.  Until the
> > second stage properly supports netbooting and booting off of a second drive
> > on a raq2 I'd like to not see any more bloat to GENERIC.
>
> What problem can be solved by these features of bootloader?
> AFAIK There is no size restriction for the native bootloader to
> load kernels.
> (and current bootloader seems to be able to load kernels from a slave drive)
> ---
> Izumi Tsutsui
>



-- 
"Too bad $VOLUNTEERS don't get their act together and provide
$SOLUTION_TO_VERY_DIFFICULT_PROBLEM in a decent fashion"  -- from IRC,
#netbsd, EFNet