>: I think you should still be able to login to the system via network.
>: Send me /var/run/dmesg.out, /boot.config, /boot/loader.rc and your
>: kernel configuration file for examination.
>
>(Sorry. Insufficient clarity is ever the petty hobgoblin that haunts
>my email. Or is it otiose purple?
Quoth Kazutaka YOKOTA on Mon, 26 July:
:
: >After upgrading from 3.2 CD to 3.2-STABLE, the console disappears
: >when the kernel boots. How can I stop this behaviour?
:
: I think you should still be able to login to the system via network.
: Send me /var/run/dmesg.out, /boot.config, /boot/loade
>After upgrading from 3.2 CD to 3.2-STABLE, the console disappears
>when the kernel boots. How can I stop this behaviour?
I think you should still be able to login to the system via network.
Send me /var/run/dmesg.out, /boot.config, /boot/loader.rc and your
kernel configuration file for examina
> today I fetched the fresh 3.2 stable code using cvsup, starting make
> buildworld. It failed. Since I´m out of my depth here, maybe you could
> help.
You missed the HEADS UP messages posted by John Polstra on -stable on 03 Jul?
[you do follow the stable mailinglist, don't you!?]
The softupdat
After upgrading from 3.2 CD to 3.2-STABLE, the console disappears
when the kernel boots. How can I stop this behaviour?
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
This is from 3.2 sources cvsup'd today.
The buildworld on the nfs server goes fine, the make.conf files are
identical on the server and client, but make installworld on the client gives:
[... lots of lines ...]
===> gnu/usr.bin/perl/perl
install -c -s -o root -g wheel -m 555 perl /usr/bin
/usr/
Please don't send messages individually to me and then to a list.
Send to both at the same time with the same message - it wastes less
of peoples time.
This is my answer to your personal email with the same content:
: Hi,
:
: The ``host is down'' message just means it's getting no response f
