Search results

The trick with your brand-new 10.3-RELEASE box would be to update to 10.3-RELEASE-p10 (or whatever the latest is) and then try the upgrade to 11.0-RELEASE. So the first step is to update 10.3-RELEASE to the latest patch-level before attempt to update to the new wanted release. # freebsd-update...

If you're not completely sure about what are you doing, it's always better to use the default port options.

Initial (limited) support for RPi3 has been landed in HEAD. https://lists.freebsd.org/pipermail/freebsd-arm/2016-October/014831.html

Well, you're using FreeBSD 11/amd64 so I guessed that could be a problem but according to portsmon, it builds fine on 11. Check out that you're using the default configuration options for security/botan110 and you don't have something out of place in your /etc/make.conf

I agree ;)

You can ask him via email if you aren't sure :)

First, be sure that you have updated your ports tree. Currently we have bumped PORTREVISION to 4, and you have the previous one. So you should have libreoffice-5.0.6_4 in ports. Rebuild devel/icu before try again.

See 213418 for further details.

The author is Matthew D. Fuller http://www.over-yonder.net/~fullermd/rants/bsd4linux/01

It's confirmed. I just upgraded www/firefox. % pkg info firefox firefox-49.0_8,1 Name : firefox Version : 49.0_8,1 Installed on : Wed Oct 12 00:18:56 2016 CEST Origin : www/firefox Architecture : freebsd:10:x86:64 Prefix : /usr/local Categories : ipv6...

According to devel/monotone/Makefile you should have installed security/botan110. LIB_DEPENDS= libpcre.so:devel/pcre \ libidn.so:dns/libidn \ libsqlite3.so:databases/sqlite3 \ libbotan-1.10.so:security/botan110

It's good to know, that worked well for you :)

You can use the defaultroute_delay option in rc.conf to make the system wait a while before bringing up the default routes. defaultroute_delay="30" # Time to wait for a default route on a DHCP interface.

According to the vt man page you can add kern.vt.enable_bell=0 in loader.conf or sysctl.conf.

Oops! theme KEY was missing in my previous comment :p PS. I edited comment #3 to fix the command.

Kalero, Can you post your results?

It could be related in someway... I thought :) The OP could run something to check if the configuration of his VM is correct. From another machine that's not the host, ping your VM: ping ip_failover From the VM, run the following: tcpdump host <ip_from_where_you_ping>

In the following article is used a similar configuration, so it's worth to give it a try. Or you can directly ask for help in the OVH Forums.

It looks promising: https://github.com/martanne/vis

The listing of the hardware specific interfaces, like ath0 etc was removed in 11. There's a sysctl for it now: sysctl net.wlan.devices scottro's howto will be helpful here: https://srobb.net/fbsdquickwireless.html https://wiki.freebsd.org/WhatsNew/FreeBSD11