On Thu, 3 May 2012 18:53:52 +0200
Bernhard Schmidt bschm...@freebsd.org wrote:
Hi folks,
As some of you might know there has been some work going on porting
support for new Ralink chipsets from OpenBSD. Several different
drivers where floating around but nothing seemed to be decent enough
On Saturday 05 May 2012 09:52:58 Sergey V. Dyatko wrote:
On Thu, 3 May 2012 18:53:52 +0200
Bernhard Schmidt bschm...@freebsd.org wrote:
Hi folks,
As some of you might know there has been some work going on porting
support for new Ralink chipsets from OpenBSD. Several different
On Saturday 05 May 2012 09:52:58 Sergey V. Dyatko wrote:
On Thu, 3 May 2012 18:53:52 +0200
Bernhard Schmidt bschm...@freebsd.org wrote:
Hi folks,
As some of you might know there has been some work going on porting
support for new Ralink chipsets from OpenBSD. Several different
On Sat, 5 May 2012 12:51:10 +0200
Bernhard Schmidt bschm...@freebsd.org wrote:
On Saturday 05 May 2012 09:52:58 Sergey V. Dyatko wrote:
On Thu, 3 May 2012 18:53:52 +0200
Bernhard Schmidt bschm...@freebsd.org wrote:
Hi folks,
As some of you might know there has been some work
On Sat, May 5, 2012 at 2:27 PM, Sergey V. Dyatko
sergey.dya...@gmail.com wrote:
On Sat, 5 May 2012 12:51:10 +0200
Bernhard Schmidt bschm...@freebsd.org wrote:
Please apply attached patch (also here [1]) on top of the first one,
it fixes channel switching for = 3070 (called the wrong function,
Hello lists.
Since Friday, I have on all of our FreeBSD 10.0-CURRENT/amd64 boxes
massive trouble with net/openldap24-server (SASL enabled, so it is
openldap-sasl-server).
Last time OpenLDAP worked was Thursday last week, when obviously a
problematic update to the OS was made - it is a wild
On 5 May 2012 16:55, Hartmann, O. ohart...@zedat.fu-berlin.de wrote:
Hello lists.
Since Friday, I have on all of our FreeBSD 10.0-CURRENT/amd64 boxes
massive trouble with net/openldap24-server (SASL enabled, so it is
openldap-sasl-server).
Last time OpenLDAP worked was Thursday last week,
On 05/05/12 18:34, Chris Rees wrote:
On 5 May 2012 16:55, Hartmann, O. ohart...@zedat.fu-berlin.de wrote:
Hello lists.
Since Friday, I have on all of our FreeBSD 10.0-CURRENT/amd64 boxes
massive trouble with net/openldap24-server (SASL enabled, so it is
openldap-sasl-server).
Last time
On 05/03/12 20:49, Tim Kientzle wrote:
On May 3, 2012, at 1:34 PM, AN wrote:
Thu May 3 16:25:27 EDT 2012
FreeBSD FBSD10 10.0-CURRENT FreeBSD 10.0-CURRENT #13 r234872: Tue May 1
13:09:55 EDT 2012 root@FBSD10:/usr/obj/usr/src/sys/MYKERNEL amd64
# svn up
Updated to revision 234981
I
After updating from -CURRENT as of April 5 to one built today, I now get
a core dump running ctfmerge on libc:
ctfmerge -L VERSION -g -o libc.so.7 syscall.So fork.So..
Bus error (core dumped)
*** [libc.so.7] Error code 138
Anyone else seeing this or have any idea how to avoid it? Let me know
On 05/05/12 20:36, Bjoern A. Zeeb wrote:
On 5. May 2012, at 15:54 , Hartmann, O. wrote:
I'm floating like a dead man in the water and I was wondering if someone
else doesn't face this problem. FreeBSD is said to be run in large
environments, so at least one should have OpenLDAP as user
Steve Wills wrote:
After updating from -CURRENT as of April 5 to one built today, I now get
a core dump running ctfmerge on libc:
ctfmerge -L VERSION -g -o libc.so.7 syscall.So fork.So..
Bus error (core dumped)
*** [libc.so.7] Error code 138
Anyone else seeing this or have any idea how
On 05/05/12 15:43, b. f. wrote:
Steve Wills wrote:
After updating from -CURRENT as of April 5 to one built today, I now get
a core dump running ctfmerge on libc:
ctfmerge -L VERSION -g -o libc.so.7 syscall.So fork.So..
Bus error (core dumped)
*** [libc.so.7] Error code 138
Anyone else
On 5/5/12, Steve Wills swi...@freebsd.org wrote:
On 05/05/12 15:43, b. f. wrote:
Steve Wills wrote:
After updating from -CURRENT as of April 5 to one built today, I now get
a core dump running ctfmerge on libc:
ctfmerge -L VERSION -g -o libc.so.7 syscall.So fork.So..
Bus error (core
On 2012/5/6 5:08, b. f. wrote:
On 5/5/12, Steve Willsswi...@freebsd.org wrote:
On 05/05/12 15:43, b. f. wrote:
Steve Wills wrote:
After updating from -CURRENT as of April 5 to one built today, I now get
a core dump running ctfmerge on libc:
ctfmerge -L VERSION -g -o libc.so.7 syscall.So
On 2012-05-05 17:54, Hartmann, O. wrote:
Since Friday, I have on all of our FreeBSD 10.0-CURRENT/amd64 boxes
massive trouble with net/openldap24-server (SASL enabled, so it is
openldap-sasl-server).
Last time OpenLDAP worked was Thursday last week, when obviously a
problematic update to the
Hi,
On Saturday 05 May 2012 18:56:33 Lars Engels wrote:
On Fri, May 04, 2012 at 06:48:42PM +0700, Erich Dollansky wrote:
Hi,
one thing I noticed: How does your /etc/make.conf look like?
Mine is here:
# added by use.perl 2012-05-02 14:49:54
PERL_VERSION=5.12.4
WITH_NEW_XORG
Hi,
On Saturday 05 May 2012 04:40:50 matt wrote:
On 05/03/12 22:12, Artem Tuchinsky wrote:
Is it possibly that the patch got applied twice? I had some errors a
not at my side.
while back that were resulting from an inconsistent mixture of
pre-patch, post-patch and double patched
Hi,
On Friday 04 May 2012 22:15:44 Artem Tuchinsky wrote:
my make.conf:
thanks for this. I included most of it into mine.
I am still not with a running system. It seems that I miss something very
simple. I will redo the whole thing and see what happens then.
Erich
On Sat, May 5, 2012 at 7:54 PM, David Xu listlog2...@gmail.com wrote:
On 2012/5/6 5:08, b. f. wrote:
On 5/5/12, Steve Willsswi...@freebsd.org wrote:
On 05/05/12 15:43, b. f. wrote:
Steve Wills wrote:
After updating from -CURRENT as of April 5 to one built today, I now
get
a core dump
On 05/05/12 23:56, Andrzej Tobola wrote:
On Sat, May 05, 2012 at 05:54:50PM +0200, Hartmann, O. wrote:
Hello lists.
Since Friday, I have on all of our FreeBSD 10.0-CURRENT/amd64 boxes
massive trouble with net/openldap24-server (SASL enabled, so it is
openldap-sasl-server).
Last time
On 05/06/12 01:55, Dimitry Andric wrote:
On 2012-05-05 17:54, Hartmann, O. wrote:
Since Friday, I have on all of our FreeBSD 10.0-CURRENT/amd64 boxes
massive trouble with net/openldap24-server (SASL enabled, so it is
openldap-sasl-server).
Last time OpenLDAP worked was Thursday last week,
22 matches
Mail list logo
