>> for the record, i've seen this and enclosed better values that fix the
>> problem in pr kern/11406.
>
>At least for this case, re-ordering some of the steps when the image is
>built ends up with a ramdisk that has 2(!) blocks left.  I don't know of
>the other cases in kern/11406 are fixed in the same way or not yet...

all i know is that it stopped working and i came up with those new
values.  it works now for me, but that's only because i'm still
*using* the new values.

all yours.  i dunno.

-- 
|-----< "CODE WARRIOR" >-----|
codewarrior@daemon.org             * "ah!  i see you have the internet
twofsonet@graffiti.com (Andrew Brown)                that goes *ping*!"
andrew@crossbar.com       * "information is power -- share the wealth."