On 2003.11.11 11:15:11 +0200, Anton Yudin wrote:
>
> RB_BOOTINFO, defined in reboot.h, not found in
> sys/boot/i386/boot2/boot2.c ..
> can somebody fix this?
I'm rather sure bde already fixed this some hours ago in
src/sys/boot/i386/boot2/boot2.c v 1.66.
--
RB_BOOTINFO, defined in reboot.h, not found in
sys/boot/i386/boot2/boot2.c ..
can somebody fix this?
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to
y=2 -S -o
boot2.s.tmp /u
sr/src/sys/boot/i386/boot2/boot2.c
/usr/src/sys/boot/i386/boot2/boot2.c: In function `load':
/usr/src/sys/boot/i386/boot2/boot2.c:362: error: `RB_BOOTINFO'
undeclared (first
use in this function)
/usr/src/sys/boot/i386/boot2/boot2.c:362: error: (Each undeclared
On 20-Mar-2002 Thomas Quinot wrote:
> Le 2002-03-20, John Baldwin écrivait :
>
>> Looks mostly ok to me. Not entirely sure about the autoboot changes
>> as it looks weird to load(kname) right before you change what kname
>> is. I think the logic must somehow be wrong there.
>
> But this is wh
Le 2002-03-20, John Baldwin écrivait :
> Looks mostly ok to me. Not entirely sure about the autoboot changes
> as it looks weird to load(kname) right before you change what kname
> is. I think the logic must somehow be wrong there.
But this is what is currently in the code (as I mentioned in t
On 20-Mar-2002 Pierre Beyssac wrote:
> Would anyone mind if I commit the following to i386/boot2.c?
> I've reviewed and tested them.
>
> add -n option to boot2 to disallow user interruption
> http://www.FreeBSD.org/cgi/query-pr.cgi?pr=36016
Looks fine to me.
>
Would anyone mind if I commit the following to i386/boot2.c?
I've reviewed and tested them.
add -n option to boot2 to disallow user interruption
http://www.FreeBSD.org/cgi/query-pr.cgi?pr=36016
boot2 cleanup (modulo style(9) and a minor typo in a comment):
http://www.FreeBS
I think I've just stumbled over a little problem with boot2.c in
-current. If I boot a kernel directly from boot2 rather than through the
loader, the root filesystem gets mounted as the old-style wd0s1a rather
than the new ad0a (or whatever). This means that init gets somewhat
upset if /etc/