On 08/25/11 01:27, Volodymyr Kostyrko wrote:
24.08.2011 12:01, Tony Maher wrote:
Hello,
recently (not sure exactly when) my xterms no longer showed the
underscore character.
In my .Xresources I had (and have had this setting for years):
XTerm*faceName: Monospace
XTerm*faceSize: 10
I noticed
David Schultz wrote:
On Wed, Jul 13, 2011, Dr. A. Haakh wrote:
Oliver Pinter schrieb:
On 7/12/11, Dr. A. Haakhbugrepor...@haakh.de wrote:
log2() log2f have been MFCd to 8-STABLE (r216210 and r216210) but are
still missing in 7-STABLE.
See
On 08/25/11 01:43, Mark Saad wrote:
What else is in you .Xresources file.
I removed it entirely and problem remains.
Also have you tried using xft formated font names. Ie xft:luxi mono:size=10 ?
xterm -fa 'xft:luxi mono:size=10'
produces an xterm which display correctly
xterm -fa
Hi,
We have observed what appears to be a crash in what appears to be the
interrupt thread for the igb(8) driver on one of our systems. This
machine runs May 22's 8.2-STABLE. For some reason the IP of the crash
(0x806d6399) points to the key_sendup0() function, however we
never had
Hi,
We have observed what appears to be a crash in the interrupt thread for
the igb(8) driver on one of our systems. This machine runs May 22's
8.2-STABLE. For some reason the IP of the crash (0x806d6399)
points to the key_sendup0() function, however we never had IPsec
configured on
Sorry for crossposting, but I got no answer at all from freebsd-fs. Anyone
in here having any ideas/suggestions on this?
cu
Gerrit
Begin forwarded message:
Date: Tue, 23 Aug 2011 17:02:55 +0200
From: Gerrit Kühn ger...@pmp.uni-hannover.de
To: freebsd...@freebsd.org
Subject: zfs snapshot:
25.08.2011 16:41, Maxim Sobolev пишет:
Hi,
We have observed what appears to be a crash in the interrupt thread for
the igb(8) driver on one of our systems. This machine runs May 22's
8.2-STABLE. For some reason the IP of the crash (0x806d6399)
points to the key_sendup0()
On 8/25/2011 3:30 AM, Eugene Grosbein wrote:
It would be nice to see KDB backtrace with symbols:
options KDB
options KDB_TRACE
options KDB_UNATTENDED
options DDB
options DDB_NUMSYM
and options KDB_UNATTENDED if you wish.
For next crash, of course:-)
I installed FreeBSD 8.2 release on a 64-bit machine (amd64) and it has gcc
4.2.1 built in. The library directories are lib, lib32 and lib64. When I
compiled for 64-bit the compilation was successful.
However, the problem is when I am compiling for 32-bit on this 64-bit
machine. We are getting
On 25/08/2011 15:28, noel beck wrote:
The following is the example of the error when compiling in 32-bit on a
64-bit machine:
[gsaid@Bruno ~]$ gcc -m32 -o hello hello.c
I don't think -m32 is supported at all.
___
freebsd-stable@freebsd.org
On Thu, Aug 25, 2011 at 2:28 PM, noel beck nb...@hobsoft.com.mt wrote:
I installed FreeBSD 8.2 release on a 64-bit machine (amd64) and it has gcc
4.2.1 built in. The library directories are lib, lib32 and lib64. When I
compiled for 64-bit the compilation was successful.
However, the problem
On Thu, Aug 25, 2011 at 06:28:18AM -0700, noel beck wrote:
I installed FreeBSD 8.2 release on a 64-bit machine (amd64) and it has gcc
4.2.1 built in. The library directories are lib, lib32 and lib64. When I
compiled for 64-bit the compilation was successful.
However, the problem is when I
On 24 August 2011 16:14, per...@pluto.rain.com wrote:
When the specified or calculated rate exceeds 64KB/sec, the
required sleep interval between 64KB chunks is less than one
second. Since diskcheckd calculates the interval in whole seconds
-- because it calls sleep() rather than usleep() or
2011/8/25 Gerrit Kühn ger...@pmp.uni-hannover.de
Sorry for crossposting, but I got no answer at all from freebsd-fs. Anyone
in here having any ideas/suggestions on this?
Is this the same thing as kern/156781?
-Andy
Begin forwarded message:
Date: Tue, 23 Aug 2011 17:02:55 +0200
From:
14 matches
Mail list logo
