- Original Message -
Perhaps not, but they do support FreeBSD. I've started several support cases
with FreeBSD-specific problems and they've fixed all so far.
Yes, it is not a blackhole of support. At $JOB, we got caught by the FreeBSD
specific issue of the busted timer that was
6 aug 2013 kl. 08:05 skrev Bryan Venteicher bry...@daemoninthecloset.org:
- Original Message -
Perhaps not, but they do support FreeBSD. I've started several support cases
with FreeBSD-specific problems and they've fixed all so far.
Yes, it is not a blackhole of support. At
Buildword on r253984 fails ins BIND9:
cc -O2 -pipe -O3 -march=native
-I/usr/src/usr.sbin/pkg_install/create/../lib -pipe -O3 -std=gnu99
-Qunused-arguments -fstack-protector -Wsystem-headers -Werror -Wall
-Wno-format-y2k -W -Wno-unused-parameter -Wstrict-prototypes
-Wmissing-prototypes
TB --- 2013-08-06 06:20:28 - tinderbox 2.10 running on freebsd-current.sentex.ca
TB --- 2013-08-06 06:20:28 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE
FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012
d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64
TB ---
TB --- 2013-08-06 06:20:28 - tinderbox 2.10 running on freebsd-current.sentex.ca
TB --- 2013-08-06 06:20:28 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE
FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012
d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64
TB ---
2013/7/24 下午10:26 於 Jia-Shiun Li jiash...@gmail.com 寫道：
On Wed, Jul 24, 2013 at 4:02 AM, Alexander Motin m...@freebsd.org wrote:
cam.k kernel module includes all existing periph drivers in one bundle.
Loading cam.ko you are probably getting sg driver also, that triggers
reported issue. You
TB --- 2013-08-06 11:41:02 - tinderbox 2.10 running on freebsd-current.sentex.ca
TB --- 2013-08-06 11:41:02 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE
FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012
d...@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64
TB ---
...
Patching file using Plan A...
Hunk #1 succeeded at 53 with fuzz 1 (offset -2 lines).
patch: misordered hunks! output would be garbled
But what I see is that patching actually fails.
So:
Hunk #1 succeeded is a lie, it did not succeed - target file was not changed
at all.
On Mon, Aug 5, 2013 at 10:53 PM, Gary Jennejohn
gljennj...@googlemail.comwrote:
On Mon, 5 Aug 2013 10:29:23 -0700
Craig Rodrigues rodr...@freebsd.org wrote:
On the booted an running system, if you type:
sysctl kern.conftxt
that will display the actual kernel config options used to
I forgot to mention, sysctl kern.conftxt
will only display something if you have this in your kernel config:
options INCLUDE_CONFIG_FILE # Include this file in kernel
It's always handy to have that in your kernel config.
--
Craig
No wonder why, it wasn't working for me and
On 05.08.2013 23:53, Luigi Rizzo wrote:
On Mon, Aug 05, 2013 at 11:04:44PM +0200, Andre Oppermann wrote:
On 05.08.2013 19:36, Luigi Rizzo wrote:
...
[picking a post at random to reply in this thread]
tell whether or not we should bail out).
Ideally we don't want to have any locks in the
On Sun, Aug 04, 2013 at 08:55:30PM -0400 I heard the voice of
Glen Barber, and lo! it spake thus:
The error generated is non-fatal, and once I receive response on a
proposed patch, will be suppressed if the svn version used to check
out the tree is not compatible with that used to check the
On Tue, Aug 06, 2013 at 01:11:07PM -0500, Matthew D. Fuller wrote:
On Sun, Aug 04, 2013 at 08:55:30PM -0400 I heard the voice of
Glen Barber, and lo! it spake thus:
The error generated is non-fatal, and once I receive response on a
proposed patch, will be suppressed if the svn version
thanks for the explanations and for experimenting with the various
alternatives.
I started this thread just to understand whether
something was already in place, and to make sure that what I
do with netmap is not worse than the situation we have now.
I guess that while the best solution comes
14 matches
Mail list logo
