On Thu, 23 Aug 2012, Ken Smith wrote:
Hi,
let me reply to the very initial email in this monster of public thread.
With both the doc and ports repositories now moved to SVN it has been
decided to not export the 9.1 release branch activity to CVS. So
csup/cvsup update mechanisms are not availa
Could you elaborate?
After setting WITHOUT_GCC I don't have
installed gcc/++ so it looks like it's working.
--
View this message in context:
http://freebsd.1045724.n5.nabble.com/Clang-as-default-compiler-tp5742836p5744598.html
Sent from the freebsd-stable mailing list archive at Nabble.com.
On asus m5a97 mobo with amd 8120, RC1. Loading amdtemp.ko
shows no temperature. People on the net post having source
from head solved the issue. Would it be included in 9.1
release? If not, I might compile source and rename it to
something like temperature.ko, then load it.
Btw, someone knows about
I installed the package ntfs-fusefs on two different servers and both
causes kernel panic when trying to copy anything.
A server using FreeBSD 9.0 STABLE amd64 and the other using FreeBSD 9
RC1 amd64.
Someone is having the same problem?
Gondim
___
fre
On 09/18/2012 18:14, Marcelo Gondim wrote:
I installed the package ntfs-fusefs on two different servers and both
causes kernel panic when trying to copy anything.
I got panics, too, but found some patch that I attached to ports/169165.
Unfortunately, the maintainer of sysutils/fusefs-kmod (Cce
On Tue, Sep 18, 2012 at 10:21 AM, Jan Henrik Sylvester wrote:
> On 09/18/2012 18:14, Marcelo Gondim wrote:
>>
>> I installed the package ntfs-fusefs on two different servers and both
>> causes kernel panic when trying to copy anything.
>
>
> I got panics, too, but found some patch that I attached
On Tue, Sep 18, 2012 at 5:14 PM, Marcelo Gondim wrote:
> I installed the package ntfs-fusefs on two different servers and both causes
> kernel panic when trying to copy anything.
> A server using FreeBSD 9.0 STABLE amd64 and the other using FreeBSD 9 RC1
> amd64.
> Someone is having the same probl
Daniel Eischen wrote:
>
> My rc.conf is something like this:
>
> #
> # For now, force ath0 to use the same MAC address as xl0.
> # This works around a bug where lagg is unable to set the
> # MAC address of the underlying wlan0 interface.
> #
> ifconfig_ath0="ether 01:02:03:04:05:06"
> wlans_ath0=
On Tue, 18 Sep 2012, David DeSimone wrote:
Daniel Eischen wrote:
My rc.conf is something like this:
#
# For now, force ath0 to use the same MAC address as xl0.
# This works around a bug where lagg is unable to set the
# MAC address of the underlying wlan0 interface.
#
ifconfig_ath0="ether 01
