Dear FreeBSD port maintainer:
As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically notify users of ports
that are marked as "broken" in their Makefiles. In many cases
these ports are failing to compile on some subset of the FreeBSD
build envir
Dear FreeBSD port maintainer:
As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically schedule removal of ports
that have been judged to have outlived their usefulness. Often,
this is due to a better alternative having become available and/or
the
Dear FreeBSD port maintainer:
As part of an ongoing effort to reduce the number of problems in the
FreeBSD ports system, we periodically notify users about
ports that are marked as "forbidden" in their Makefiles. Often,
these ports are so marked due to security concerns, such as known
exploits.
What is the current procedure for installing guest additions on
non-FreeBSD guests? With a FreeBSD host and XP guest, the guest exits
instantly when Devices/Install Guest Additions/Yes is chosen. But the
downloadable guest additions from virtualbox.org aren't ISO format any
more.
This is Vi
On Wed, 7 Nov 2012, Warren Block wrote:
What is the current procedure for installing guest additions on non-FreeBSD
guests? With a FreeBSD host and XP guest, the guest exits instantly when
Devices/Install Guest Additions/Yes is chosen. But the downloadable guest
additions from virtualbox.org
