Re: CURRENT (r248128): PKGNG weirdness: openldap-sasl-client-2.4.33_1 conflicts with installed package(s): openldap-sasl-client-2.4.33_1 AND /usr/local AND net/openldap24-sasl-client

2013-03-13 Thread O. Hartmann
On Tue, 2013-03-12 at 17:16 -0500, Bryan Drewery wrote: On 3/10/2013 6:44 AM, O. Hartmann wrote: On FreeBSD 10.0-CURRENT #0 r248128: Sun Mar 10 10:41:10 CET 2013 I receive the error message below when trying to update installed port openldap24-sasl-client: === Cleaning for

Re: CURRENT (r248128): PKGNG weirdness: openldap-sasl-client-2.4.33_1 conflicts with installed package(s): openldap-sasl-client-2.4.33_1 AND /usr/local AND net/openldap24-sasl-client

2013-03-13 Thread Bryan Drewery
On 3/13/2013 2:55 AM, O. Hartmann wrote: On Tue, 2013-03-12 at 17:16 -0500, Bryan Drewery wrote: I have just committed a fix to the ports tree for this. Hello. Well, I just updated the port's tree a few minutes ago and can not see any changes by now. The port's tree is at Revision:

Re: using multiple interfaces for same Network Card

2013-03-13 Thread Ian FREISLICH
Yasir hussan wrote: --20cf3005141ab7271904d7be84ff Yes, i want to use them as vlan interface, Does any one has used *vlandev*, after seen this http://www.cyberciti.biz/faq/howto-configure-freebsd-vlans-with-ifconfig-comm and/i tried to use it as ifconfig vlan11 create 10.10.11.1

Re: CURRENT (r248128): PKGNG weirdness: openldap-sasl-client-2.4.33_1 conflicts with installed package(s): openldap-sasl-client-2.4.33_1 AND /usr/local AND net/openldap24-sasl-client

2013-03-13 Thread O. Hartmann
On Wed, 2013-03-13 at 04:49 -0500, Bryan Drewery wrote: On 3/13/2013 2:55 AM, O. Hartmann wrote: On Tue, 2013-03-12 at 17:16 -0500, Bryan Drewery wrote: I have just committed a fix to the ports tree for this. Hello. Well, I just updated the port's tree a few minutes ago and can

Re: CURRENT (r248128): PKGNG weirdness: openldap-sasl-client-2.4.33_1 conflicts with installed package(s): openldap-sasl-client-2.4.33_1 AND /usr/local AND net/openldap24-sasl-client

2013-03-13 Thread Bryan Drewery
On 3/13/2013 7:21 AM, O. Hartmann wrote: On Wed, 2013-03-13 at 04:49 -0500, Bryan Drewery wrote: On 3/13/2013 2:55 AM, O. Hartmann wrote: On Tue, 2013-03-12 at 17:16 -0500, Bryan Drewery wrote: I have just committed a fix to the ports tree for this. Hello. Well, I just updated the port's

sysinstall and graid mirror on 9.1R

2013-03-13 Thread Ruslan Makhmatkhanov
Hi, I know sysinstall is deprecated and gone from -current, but there is still 8/9 that will be supported for few years so this may worth fixing. Got this anytime I starting sysinstall on a system, installed onto graid mirror: http://people.freebsd.org/~rm/sysinstall_graid.png No more have

Re: CURRENT (r248128): PKGNG weirdness: openldap-sasl-client-2.4.33_1 conflicts with installed package(s): openldap-sasl-client-2.4.33_1 AND /usr/local AND net/openldap24-sasl-client

2013-03-13 Thread O. Hartmann
On Wed, 2013-03-13 at 07:26 -0500, Bryan Drewery wrote: On 3/13/2013 7:21 AM, O. Hartmann wrote: On Wed, 2013-03-13 at 04:49 -0500, Bryan Drewery wrote: On 3/13/2013 2:55 AM, O. Hartmann wrote: On Tue, 2013-03-12 at 17:16 -0500, Bryan Drewery wrote: I have just committed a fix to the

Re: CURRENT (r248128): PKGNG weirdness: openldap-sasl-client-2.4.33_1 conflicts with installed package(s): openldap-sasl-client-2.4.33_1 AND /usr/local AND net/openldap24-sasl-client

2013-03-13 Thread Bryan Drewery
On 3/13/2013 8:55 AM, O. Hartmann wrote: On Wed, 2013-03-13 at 07:26 -0500, Bryan Drewery wrote: On 3/13/2013 7:21 AM, O. Hartmann wrote: On Wed, 2013-03-13 at 04:49 -0500, Bryan Drewery wrote: On 3/13/2013 2:55 AM, O. Hartmann wrote: On Tue, 2013-03-12 at 17:16 -0500, Bryan Drewery wrote: I

Re: CURRENT (r248128): PKGNG weirdness: openldap-sasl-client-2.4.33_1 conflicts with installed package(s): openldap-sasl-client-2.4.33_1 AND /usr/local AND net/openldap24-sasl-client

2013-03-13 Thread O. Hartmann
On Wed, 2013-03-13 at 09:54 -0500, Bryan Drewery wrote: On 3/13/2013 8:55 AM, O. Hartmann wrote: On Wed, 2013-03-13 at 07:26 -0500, Bryan Drewery wrote: On 3/13/2013 7:21 AM, O. Hartmann wrote: On Wed, 2013-03-13 at 04:49 -0500, Bryan Drewery wrote: On 3/13/2013 2:55 AM, O. Hartmann

[PATCH] Add support for Exar XR17V358IV to puc(4)

2013-03-13 Thread Ryan Stone
I've implemented support for Exar XR17V358IV 8-port UARTs. These are quite similar to previous Exar UARTs, with the notable exception of the strange 125MHz clock. I've done some basic testing using it as a tty at 9600 baud and 115200 baud, but nothing really extensive. I can't seem to find any

Re: pidfile_open incorrectly returns EAGAIN when pidfile is locked

2013-03-13 Thread John Baldwin
On Tuesday, March 12, 2013 4:16:32 pm Dirk Engling wrote: While debugging my own daemon I noticed that pidfile_open does not perform the appropriate checks for a running daemon if the caller does not provide a pidptr to pidfile_open fd = flopen(pfh-pf_path, O_WRONLY | O_CREAT |

Re: pidfile_open incorrectly returns EAGAIN when pidfile is locked

2013-03-13 Thread Pawel Jakub Dawidek
On Wed, Mar 13, 2013 at 11:18:36AM -0400, John Baldwin wrote: On Tuesday, March 12, 2013 4:16:32 pm Dirk Engling wrote: While debugging my own daemon I noticed that pidfile_open does not perform the appropriate checks for a running daemon if the caller does not provide a pidptr to

Re: pidfile_open incorrectly returns EAGAIN when pidfile is locked

2013-03-13 Thread Dirk Engling
On Wed, 13 Mar 2013, Pawel Jakub Dawidek wrote: How about this patch? http://people.freebsd.org/~pjd/patches/pidfile.c.patch If you move the lines + if (errno == 0 || errno == EAGAIN) + errno = EEXIST; out of the

Re: pidfile_open incorrectly returns EAGAIN when pidfile is locked

2013-03-13 Thread Pawel Jakub Dawidek
On Wed, Mar 13, 2013 at 10:59:17PM +0100, Dirk Engling wrote: On Wed, 13 Mar 2013, Pawel Jakub Dawidek wrote: How about this patch? http://people.freebsd.org/~pjd/patches/pidfile.c.patch If you move the lines + if (errno == 0 || errno == EAGAIN) +

FYI - warning: KLD

2013-03-13 Thread AN
FreeBSD FBSD10 10.0-CURRENT FreeBSD 10.0-CURRENT #37 r248259: Wed Mar 13 21:46:51 CDT 2013 root@FBSD10:/usr/obj/usr/src/sys/MYKERNEL amd64 I just wanted to report something that I don't recall seeing before. After updating to r248259 on Wed Mar 13 23:00:02 CDT 2013, I experienced a

reservation of n, n (3) failed

2013-03-13 Thread Waitman Gobble
Hi, I swapped out the CPU on this machine today, I don't recall seeing these messages previously: acpi0: reservation of 0, a (3) failed acpi0: reservation of 10, bfcd (3) failed Does anyone have an idea about what this refers to? Here's the boot log. uname -a FreeBSD