From owner-freebsd-current@FreeBSD.ORG Sun Mar 10 00:07:04 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id DF0EB530; Sun, 10 Mar 2013 00:07:04 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.21]) by mx1.freebsd.org (Postfix) with ESMTP id A39F41CB; Sun, 10 Mar 2013 00:07:04 +0000 (UTC) Received: from troutmask.apl.washington.edu (localhost.apl.washington.edu [127.0.0.1]) by troutmask.apl.washington.edu (8.14.6/8.14.6) with ESMTP id r29NdUka095296; Sat, 9 Mar 2013 15:39:30 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.14.6/8.14.6/Submit) id r29NdUS2095295; Sat, 9 Mar 2013 15:39:30 -0800 (PST) (envelope-from sgk) Date: Sat, 9 Mar 2013 15:39:30 -0800 From: Steve Kargl To: Dimitry Andric Subject: Re: CURRENT: lang/gcc fails to build on CURRENT with error: configure: error: no usable dependency style found Message-ID: <20130309233930.GA95285@troutmask.apl.washington.edu> References: <513B56E8.2060702@zedat.fu-berlin.de> <8F5265A6-396A-426F-A3F8-EFD44D167313@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <8F5265A6-396A-426F-A3F8-EFD44D167313@FreeBSD.org> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: FreeBSD Current , "Hartmann, O." , freebsd-ports@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Mar 2013 00:07:04 -0000 On Sat, Mar 09, 2013 at 05:02:56PM +0100, Dimitry Andric wrote: > On Mar 9, 2013, at 16:36 , "Hartmann, O." wrote: > > I have one specific FreeBSD 10.0-CURRENT box (FreeBSD 10.0-CURRENT #0 > > r248061: Fri Mar 8 19:44:30 CET 2013 amd64) which rejects to build > > either lang/gcc or lang/gcc46 with the very same error shown below. > ? > > checking whether cc supports -pedantic -Wno-long-long... yes > > checking dependency style of cc... none > > configure: error: no usable dependency style found > > gmake[2]: *** [configure-stage1-libcpp] Error 1 > > gmake[2]: Leaving directory `/usr/ports/lang/gcc/work/build' > > gmake[1]: *** [stage1-bubble] Error 2 > > gmake[1]: Leaving directory `/usr/ports/lang/gcc/work/build' > > gmake: *** [all] Error 2 > > *** [do-build] Error code 1 > > What is the actual error in the resulting config.log file? Unfortunately autoconf error message are virtually information-free? > If you have a clang built FreeBSD-current, then it is no longer possible to *bootstrap* gcc-4.6.x, gcc-4.7.x, nor the upcoming gcc-4.8.0. AFAICT, the problem is related to /usr/bin/cpp. I haven't tried earlier versions of gcc. -- Steve From owner-freebsd-current@FreeBSD.ORG Sun Mar 10 02:21:45 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 51A68EF9 for ; Sun, 10 Mar 2013 02:21:45 +0000 (UTC) (envelope-from zbeeble@gmail.com) Received: from mail-vb0-x22d.google.com (mail-vb0-x22d.google.com [IPv6:2607:f8b0:400c:c02::22d]) by mx1.freebsd.org (Postfix) with ESMTP id 0FAD16FA for ; Sun, 10 Mar 2013 02:21:44 +0000 (UTC) Received: by mail-vb0-f45.google.com with SMTP id p1so1141587vbi.4 for ; Sat, 09 Mar 2013 18:21:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=HAagzD4pmPAy1ozvIKh23qSohbUREVPLe++vQZlrX78=; b=MlP63Mn13dJqoefZFfL+c7reJkIai7veIWX3oBWtA+aKtdEMI0oXvBRugU/68yzdm4 jwHsMtyXx4FwWZjCeTEVWhJK92jkL92k7qlNonyehwd61vTqYQTJfBTEg0ibOVZ4c5xZ 0UWtiXaaTf3VpOFO3Dntse8EBWRXK/2GtmU9X7JNFP/891rMr5Ks0UkxGJxo++QJnAh4 XSCDPVkeospm6hoPvxEwKWWhdwhwTW7PjFEXz9oczhVGS7lSLb0kb+TgomHCTTC74uHU vYf7Tl9ZjeBbmhJ4n/6jM0yfcWa2rMgH7e1vOv/amEt4qvWTV8QLcHkY4ZBff2Ex5F4F ip3Q== MIME-Version: 1.0 X-Received: by 10.220.40.9 with SMTP id i9mr3021264vce.23.1362882104607; Sat, 09 Mar 2013 18:21:44 -0800 (PST) Received: by 10.220.232.6 with HTTP; Sat, 9 Mar 2013 18:21:44 -0800 (PST) In-Reply-To: References: Date: Sat, 9 Mar 2013 21:21:44 -0500 Message-ID: Subject: Re: multi-homing in freebsd From: Zaphod Beeblebrox To: Yasir hussan Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: Current , Daniel Nebdal X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Mar 2013 02:21:45 -0000 On Sat, Mar 9, 2013 at 8:57 AM, Yasir hussan wrote: > i want to have differnet ips`s and each should have different interface, > it could be a virtual interface. like u can made it like > > *ifconfig arge0.1 create* > > but each ip should able to access from differnet machine > > This is linux-specific. We don't create sub interfaces. If you want the equivalent on FreeBSD, you would just: ifconfig arge0 192.168.0.1/24 ifconfig arge0 192.168.1.1/24 alias ... and so on for as many addresses as you require. Replace "alias" with "delete" to remove an alias from an interface (including the first one). In retrospect, it might be good for us to harmonize the meanings there... > On Sat, Mar 9, 2013 at 7:29 AM, Daniel Nebdal wrote: > >> Going by Zaphod's recommendation of using a /32 for each IP, how about >> this? >> >> ifconfig arge0 inet 192.168.1.100/32 >> ifconfig arge0 alias 192.169.1.100/32 >> > Nope, you miss an important point. If you were going to add 192.168.0.[123] you might: ifconfig em0 192.168.0.1/24 ifconfig em0 192.168.0.2/32 alias ifconfig em0 192.168.0.3/32 alias ... these three addresses are on the _same_ network. In your example above, you would require the correct netmask for each network _unless_ you did something like the following: ifconfig em0 192.168.1.1/15 ifconfig em0 192.168.1.100/32 alias ifconfig em0 192.169.1.100/32 alias ... ie: you're in effect saying the network goes from 192.168.1.0 to 192.169.255.255. From owner-freebsd-current@FreeBSD.ORG Sun Mar 10 02:58:35 2013 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 93548E6; Sun, 10 Mar 2013 02:58:35 +0000 (UTC) (envelope-from imb@protected-networks.net) Received: from sarah.protected-networks.net (sarah.protected-networks.net [IPv6:2001:470:1f07:4e1::1]) by mx1.freebsd.org (Postfix) with ESMTP id 2D03783E; Sun, 10 Mar 2013 02:58:35 +0000 (UTC) Received: from toshi.auburn.protected-networks.net (toshi.auburn.protected-networks.net [202.12.127.84]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "Iain Butler", Issuer "RSA Class 2 Personal CA v2" (verified OK)) (Authenticated sender: imb@protected-networks.net) by sarah.protected-networks.net (Postfix) with ESMTPSA id D92EA6149; Sat, 9 Mar 2013 21:58:33 -0500 (EST) DomainKey-Signature: a=rsa-sha1; s=200509; d=protected-networks.net; c=nofws; q=dns; h=message-id:date:from:user-agent:mime-version:to:subject: x-enigmail-version:openpgp:content-type; b=LM4OPUw2EgrLzHiJ2taTnjxu1XED1T6LzuGxm8NV8BlnWGcOaPC0QABn89T3eRtsw JpbLLUSk4/3km6zPuxhPsSwh6P3XM+XPBmU6cKoaQSx3/4DrgwQJ07zmn8wWU18 Message-ID: <513BF6D7.1010509@protected-networks.net> Date: Sat, 09 Mar 2013 21:58:31 -0500 From: Michael Butler User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:17.0) Gecko/20130308 Thunderbird/17.0.4 MIME-Version: 1.0 To: emulation@FreeBSD.org, FreeBSD Current Subject: VirtualBox driver patch for -current post SVN r248084 X-Enigmail-Version: 1.5.1 OpenPGP: id=0442D492 Content-Type: multipart/mixed; boundary="------------070900040706060205080306" X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Mar 2013 02:58:35 -0000 This is a multi-part message in MIME format. --------------070900040706060205080306 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit With the changing of the vm_object mutex to a rwlock, the VirtualBox drivers (emulators/virtualbox-ose-kmod) need the attached patch to run, imb --------------070900040706060205080306-- From owner-freebsd-current@FreeBSD.ORG Sun Mar 10 03:02:24 2013 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id E5B932C6; Sun, 10 Mar 2013 03:02:24 +0000 (UTC) (envelope-from imb@protected-networks.net) Received: from sarah.protected-networks.net (sarah.protected-networks.net [IPv6:2001:470:1f07:4e1::1]) by mx1.freebsd.org (Postfix) with ESMTP id B68DB8EA; Sun, 10 Mar 2013 03:02:24 +0000 (UTC) Received: from toshi.auburn.protected-networks.net (toshi.auburn.protected-networks.net [202.12.127.84]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client CN "Iain Butler", Issuer "RSA Class 2 Personal CA v2" (verified OK)) (Authenticated sender: imb@protected-networks.net) by sarah.protected-networks.net (Postfix) with ESMTPSA id D1BD36149; Sat, 9 Mar 2013 22:02:17 -0500 (EST) DomainKey-Signature: a=rsa-sha1; s=200509; d=protected-networks.net; c=nofws; q=dns; h=message-id:date:from:user-agent:mime-version:to:subject: references:in-reply-to:x-enigmail-version:openpgp:content-type:content-transfer-encoding; b=TCtxvGVgXAAOv0j2odegi2skZI6aU1sSeyLsw7RegoSKVYeAT72tHjhE1R0Ca+eif AYhtwkvcB9jeUl21Ze09b70ebdc6KvahQCvdz4p9TT0y6nBsOIl7RhcI8kAKu5l Message-ID: <513BF7B8.9040901@protected-networks.net> Date: Sat, 09 Mar 2013 22:02:16 -0500 From: Michael Butler User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:17.0) Gecko/20130308 Thunderbird/17.0.4 MIME-Version: 1.0 To: emulation@FreeBSD.org, FreeBSD Current Subject: Re: VirtualBox driver patch for -current post SVN r248084 References: <513BF6D7.1010509@protected-networks.net> In-Reply-To: <513BF6D7.1010509@protected-networks.net> X-Enigmail-Version: 1.5.1 OpenPGP: id=0442D492 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Mar 2013 03:02:25 -0000 On 03/09/13 21:58, Michael Butler wrote: > With the changing of the vm_object mutex to a rwlock, the VirtualBox > drivers (emulators/virtualbox-ose-kmod) need the attached patch to run, > > imb *** src/VBox/Runtime/r0drv/freebsd/memobj-r0drv-freebsd.c~ Sat Mar 9 21:15:12 2013 --- src/VBox/Runtime/r0drv/freebsd/memobj-r0drv-freebsd.c Sat Mar 9 21:21:20 2013 *************** *** 162,168 **** case RTR0MEMOBJTYPE_PHYS: case RTR0MEMOBJTYPE_PHYS_NC: { ! VM_OBJECT_LOCK(pMemFreeBSD->pObject); vm_page_t pPage = vm_page_find_least(pMemFreeBSD->pObject, 0); #if __FreeBSD_version < 900000 /* See http://lists.freebsd.org/pipermail/freebsd-current/2012-November/037963.html */ --- 162,168 ---- case RTR0MEMOBJTYPE_PHYS: case RTR0MEMOBJTYPE_PHYS_NC: { ! VM_OBJECT_WLOCK(pMemFreeBSD->pObject); vm_page_t pPage = vm_page_find_least(pMemFreeBSD->pObject, 0); #if __FreeBSD_version < 900000 /* See http://lists.freebsd.org/pipermail/freebsd-current/2012-November/037963.html */ *************** *** 177,183 **** #if __FreeBSD_version < 900000 vm_page_unlock_queues(); #endif ! VM_OBJECT_UNLOCK(pMemFreeBSD->pObject); vm_object_deallocate(pMemFreeBSD->pObject); break; } --- 177,183 ---- #if __FreeBSD_version < 900000 vm_page_unlock_queues(); #endif ! VM_OBJECT_WUNLOCK(pMemFreeBSD->pObject); vm_object_deallocate(pMemFreeBSD->pObject); break; } *************** *** 205,214 **** while (cTries <= 1) { ! VM_OBJECT_LOCK(pObject); pPages = vm_page_alloc_contig(pObject, iPIndex, fFlags, cPages, 0, VmPhysAddrHigh, uAlignment, 0, VM_MEMATTR_DEFAULT); ! VM_OBJECT_UNLOCK(pObject); if (pPages) break; vm_pageout_grow_cache(cTries, 0, VmPhysAddrHigh); --- 205,214 ---- while (cTries <= 1) { ! VM_OBJECT_WLOCK(pObject); pPages = vm_page_alloc_contig(pObject, iPIndex, fFlags, cPages, 0, VmPhysAddrHigh, uAlignment, 0, VM_MEMATTR_DEFAULT); ! VM_OBJECT_WUNLOCK(pObject); if (pPages) break; vm_pageout_grow_cache(cTries, 0, VmPhysAddrHigh); *************** *** 228,234 **** if (!pPages) return pPages; ! VM_OBJECT_LOCK(pObject); for (vm_pindex_t iPage = 0; iPage < cPages; iPage++) { vm_page_t pPage = pPages + iPage; --- 228,234 ---- if (!pPages) return pPages; ! VM_OBJECT_WLOCK(pObject); for (vm_pindex_t iPage = 0; iPage < cPages; iPage++) { vm_page_t pPage = pPages + iPage; *************** *** 240,246 **** atomic_add_int(&cnt.v_wire_count, 1); } } ! VM_OBJECT_UNLOCK(pObject); return pPages; #endif } --- 240,246 ---- atomic_add_int(&cnt.v_wire_count, 1); } } ! VM_OBJECT_WUNLOCK(pObject); return pPages; #endif } *************** *** 264,270 **** if (!pPage) { /* Free all allocated pages */ ! VM_OBJECT_LOCK(pObject); while (iPage-- > 0) { pPage = vm_page_lookup(pObject, iPage); --- 264,270 ---- if (!pPage) { /* Free all allocated pages */ ! VM_OBJECT_WLOCK(pObject); while (iPage-- > 0) { pPage = vm_page_lookup(pObject, iPage); *************** *** 278,284 **** vm_page_unlock_queues(); #endif } ! VM_OBJECT_UNLOCK(pObject); return rcNoMem; } } --- 278,284 ---- vm_page_unlock_queues(); #endif } ! VM_OBJECT_WUNLOCK(pObject); return rcNoMem; } } *************** *** 411,419 **** if (fContiguous) { Assert(enmType == RTR0MEMOBJTYPE_PHYS); ! VM_OBJECT_LOCK(pMemFreeBSD->pObject); pMemFreeBSD->Core.u.Phys.PhysBase = VM_PAGE_TO_PHYS(vm_page_find_least(pMemFreeBSD->pObject, 0)); ! VM_OBJECT_UNLOCK(pMemFreeBSD->pObject); pMemFreeBSD->Core.u.Phys.fAllocated = true; } --- 411,419 ---- if (fContiguous) { Assert(enmType == RTR0MEMOBJTYPE_PHYS); ! VM_OBJECT_WLOCK(pMemFreeBSD->pObject); pMemFreeBSD->Core.u.Phys.PhysBase = VM_PAGE_TO_PHYS(vm_page_find_least(pMemFreeBSD->pObject, 0)); ! VM_OBJECT_WUNLOCK(pMemFreeBSD->pObject); pMemFreeBSD->Core.u.Phys.fAllocated = true; } *************** *** 823,831 **** case RTR0MEMOBJTYPE_PHYS_NC: { RTHCPHYS addr; ! VM_OBJECT_LOCK(pMemFreeBSD->pObject); addr = VM_PAGE_TO_PHYS(vm_page_lookup(pMemFreeBSD->pObject, iPage)); ! VM_OBJECT_UNLOCK(pMemFreeBSD->pObject); return addr; } --- 823,831 ---- case RTR0MEMOBJTYPE_PHYS_NC: { RTHCPHYS addr; ! VM_OBJECT_WLOCK(pMemFreeBSD->pObject); addr = VM_PAGE_TO_PHYS(vm_page_lookup(pMemFreeBSD->pObject, iPage)); ! VM_OBJECT_WUNLOCK(pMemFreeBSD->pObject); return addr; } *** src/VBox/Runtime/r0drv/freebsd/the-freebsd-kernel.h~ Wed Dec 19 13:27:29 2012 --- src/VBox/Runtime/r0drv/freebsd/the-freebsd-kernel.h Sat Mar 9 21:37:09 2013 *************** *** 57,62 **** --- 57,63 ---- #include #include #include + #include #include #include /* for vtophys */ #include From owner-freebsd-current@FreeBSD.ORG Sun Mar 10 04:21:18 2013 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id EBB424F8; Sun, 10 Mar 2013 04:21:17 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by mx1.freebsd.org (Postfix) with ESMTP id BC690ABD; Sun, 10 Mar 2013 04:21:17 +0000 (UTC) Received: from freebsd-current.sentex.ca (localhost [127.0.0.1]) by freebsd-current.sentex.ca (8.14.5/8.14.5) with ESMTP id r2A4LBV7005044; Sat, 9 Mar 2013 23:21:11 -0500 (EST) (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-current.sentex.ca (8.14.5/8.14.5/Submit) id r2A4LBuD005031; Sun, 10 Mar 2013 04:21:11 GMT (envelope-from tinderbox@freebsd.org) Date: Sun, 10 Mar 2013 04:21:11 GMT Message-Id: <201303100421.r2A4LBuD005031@freebsd-current.sentex.ca> X-Authentication-Warning: freebsd-current.sentex.ca: tinderbox set sender to FreeBSD Tinderbox using -f Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Subject: [head tinderbox] failure on mips/mips Precedence: bulk X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Mar 2013 04:21:18 -0000 TB --- 2013-03-10 03:10:26 - tinderbox 2.10 running on freebsd-current.sentex.ca TB --- 2013-03-10 03:10:26 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012 des@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2013-03-10 03:10:26 - starting HEAD tinderbox run for mips/mips TB --- 2013-03-10 03:10:26 - cleaning the object tree TB --- 2013-03-10 03:11:29 - /usr/local/bin/svn stat /src TB --- 2013-03-10 03:11:38 - At svn revision 248114 TB --- 2013-03-10 03:11:39 - building world TB --- 2013-03-10 03:11:39 - CROSS_BUILD_TESTING=YES TB --- 2013-03-10 03:11:39 - MAKEOBJDIRPREFIX=/obj TB --- 2013-03-10 03:11:39 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-03-10 03:11:39 - SRCCONF=/dev/null TB --- 2013-03-10 03:11:39 - TARGET=mips TB --- 2013-03-10 03:11:39 - TARGET_ARCH=mips TB --- 2013-03-10 03:11:39 - TZ=UTC TB --- 2013-03-10 03:11:39 - __MAKE_CONF=/dev/null TB --- 2013-03-10 03:11:39 - cd /src TB --- 2013-03-10 03:11:39 - /usr/bin/make -B buildworld >>> Building an up-to-date make(1) >>> World build started on Sun Mar 10 03:11:44 UTC 2013 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools >>> stage 4.1: building includes >>> stage 4.2: building libraries >>> stage 4.3: make dependencies >>> stage 4.4: building everything >>> World build completed on Sun Mar 10 04:14:16 UTC 2013 TB --- 2013-03-10 04:14:16 - cd /src/sys/mips/conf TB --- 2013-03-10 04:14:16 - /usr/sbin/config -m ADM5120 TB --- 2013-03-10 04:14:16 - skipping ADM5120 kernel TB --- 2013-03-10 04:14:16 - cd /src/sys/mips/conf TB --- 2013-03-10 04:14:16 - /usr/sbin/config -m ALCHEMY TB --- 2013-03-10 04:14:16 - skipping ALCHEMY kernel TB --- 2013-03-10 04:14:16 - cd /src/sys/mips/conf TB --- 2013-03-10 04:14:16 - /usr/sbin/config -m AP91 TB --- 2013-03-10 04:14:16 - building AP91 kernel TB --- 2013-03-10 04:14:16 - CROSS_BUILD_TESTING=YES TB --- 2013-03-10 04:14:16 - MAKEOBJDIRPREFIX=/obj TB --- 2013-03-10 04:14:16 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-03-10 04:14:16 - SRCCONF=/dev/null TB --- 2013-03-10 04:14:16 - TARGET=mips TB --- 2013-03-10 04:14:16 - TARGET_ARCH=mips TB --- 2013-03-10 04:14:16 - TZ=UTC TB --- 2013-03-10 04:14:16 - __MAKE_CONF=/dev/null TB --- 2013-03-10 04:14:16 - cd /src TB --- 2013-03-10 04:14:16 - /usr/bin/make -B buildkernel KERNCONF=AP91 >>> Kernel build for AP91 started on Sun Mar 10 04:14:16 UTC 2013 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything >>> Kernel build for AP91 completed on Sun Mar 10 04:17:57 UTC 2013 TB --- 2013-03-10 04:17:57 - cd /src/sys/mips/conf TB --- 2013-03-10 04:17:57 - /usr/sbin/config -m AP93 TB --- 2013-03-10 04:17:57 - building AP93 kernel TB --- 2013-03-10 04:17:57 - CROSS_BUILD_TESTING=YES TB --- 2013-03-10 04:17:57 - MAKEOBJDIRPREFIX=/obj TB --- 2013-03-10 04:17:57 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-03-10 04:17:57 - SRCCONF=/dev/null TB --- 2013-03-10 04:17:57 - TARGET=mips TB --- 2013-03-10 04:17:57 - TARGET_ARCH=mips TB --- 2013-03-10 04:17:57 - TZ=UTC TB --- 2013-03-10 04:17:57 - __MAKE_CONF=/dev/null TB --- 2013-03-10 04:17:57 - cd /src TB --- 2013-03-10 04:17:57 - /usr/bin/make -B buildkernel KERNCONF=AP93 >>> Kernel build for AP93 started on Sun Mar 10 04:17:57 UTC 2013 >>> stage 1: configuring the kernel >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3.1: making dependencies >>> stage 3.2: building everything [...] cc -O -pipe -G0 -Werror -D_KERNEL -DKLD_MODULE -nostdinc -DHAVE_KERNEL_OPTION_HEADERS -include /obj/mips.mips/src/sys/AP93/opt_global.h -I. -I@ -I@/contrib/altq -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-common -g -G0 -fno-pic -mno-abicalls -mlong-calls -I/obj/mips.mips/src/sys/AP93 -msoft-float -ffreestanding -std=iso9899:1999 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -c /src/sys/modules/wlan/../../net80211/ieee80211_wds.c cc -O -pipe -G0 -Werror -D_KERNEL -DKLD_MODULE -nostdinc -DHAVE_KERNEL_OPTION_HEADERS -include /obj/mips.mips/src/sys/AP93/opt_global.h -I. -I@ -I@/contrib/altq -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-common -g -G0 -fno-pic -mno-abicalls -mlong-calls -I/obj/mips.mips/src/sys/AP93 -msoft-float -ffreestanding -std=iso9899:1999 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -c /src/sys/modules/wlan/../../net80211/ieee80211_ddb.c cc -O -pipe -G0 -Werror -D_KERNEL -DKLD_MODULE -nostdinc -DHAVE_KERNEL_OPTION_HEADERS -include /obj/mips.mips/src/sys/AP93/opt_global.h -I. -I@ -I@/contrib/altq -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-common -g -G0 -fno-pic -mno-abicalls -mlong-calls -I/obj/mips.mips/src/sys/AP93 -msoft-float -ffreestanding -std=iso9899:1999 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -c /src/sys/modules/wlan/../../net80211/ieee80211_tdma.c cc -O -pipe -G0 -Werror -D_KERNEL -DKLD_MODULE -nostdinc -DHAVE_KERNEL_OPTION_HEADERS -include /obj/mips.mips/src/sys/AP93/opt_global.h -I. -I@ -I@/contrib/altq -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-common -g -G0 -fno-pic -mno-abicalls -mlong-calls -I/obj/mips.mips/src/sys/AP93 -msoft-float -ffreestanding -std=iso9899:1999 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -fdiagnostics-show-option -c /src/sys/modules/wlan/../../net80211/ieee80211_superg.c cc1: warnings being treated as errors /src/sys/modules/wlan/../../net80211/ieee80211_superg.c: In function 'ieee80211_ff_age': /src/sys/modules/wlan/../../net80211/ieee80211_superg.c:537: warning: 'vap' is used uninitialized in this function /src/sys/modules/wlan/../../net80211/ieee80211_superg.c:535: note: 'vap' was declared here *** [ieee80211_superg.o] Error code 1 Stop in /src/sys/modules/wlan. *** [all] Error code 1 Stop in /src/sys/modules. *** [modules-all] Error code 1 Stop in /obj/mips.mips/src/sys/AP93. *** [buildkernel] Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2013-03-10 04:21:10 - WARNING: /usr/bin/make returned exit code 1 TB --- 2013-03-10 04:21:10 - ERROR: failed to build AP93 kernel TB --- 2013-03-10 04:21:10 - 3000.89 user 635.16 system 4244.42 real http://tinderbox.freebsd.org/tinderbox-head-ss-build-HEAD-mips-mips.full From owner-freebsd-current@FreeBSD.ORG Sun Mar 10 05:04:27 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 7021E16F; Sun, 10 Mar 2013 05:04:27 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-we0-x231.google.com (mail-we0-x231.google.com [IPv6:2a00:1450:400c:c03::231]) by mx1.freebsd.org (Postfix) with ESMTP id 94024CB3; Sun, 10 Mar 2013 05:04:26 +0000 (UTC) Received: by mail-we0-f177.google.com with SMTP id d7so2395032wer.8 for ; Sat, 09 Mar 2013 21:04:25 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=iO5oMm7Z+N6X681iVmxwglrEtQCekphv9q8zMr39k6g=; b=OK7ZSwzmAgdeBaMeeCiFTKWm7ESgtgnUtlov5Q3iq1B/Pr4drRiZadT1ysT8JoNYwL lIyrumeCMPZttDIzAwrJJwsWU8kHvHBLli2ySDLjqSExbW8IANjM155hQYy+YyYdbiBD wdXX0UIiBytvqeNKnyUtYAmeqUEyGootvXE2fxgl0O//1JQ4IbPr90X4fwQ3f0eObgrI rYWhb9+yn75hkZT/TUK3LijOKjCGWCpjUJOLDfF1wMD0k1RwDwX3NVGScI4SJAeOmG8W CxsJMBaGfeNxotbse71cMrpgPOn433aw3AYlvCRJb1oI+XLEmyXOW/T3jUdZ3QkK1H/A 1YUw== MIME-Version: 1.0 X-Received: by 10.180.94.135 with SMTP id dc7mr5982973wib.11.1362891865796; Sat, 09 Mar 2013 21:04:25 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.216.111.201 with HTTP; Sat, 9 Mar 2013 21:04:25 -0800 (PST) In-Reply-To: <201303100438.r2A4c61V049385@svn.freebsd.org> References: <201303100438.r2A4c61V049385@svn.freebsd.org> Date: Sat, 9 Mar 2013 21:04:25 -0800 X-Google-Sender-Auth: m3fUlwh4x41pNVpb3hskmFhbMZ0 Message-ID: Subject: Re: svn commit: r248127 - head/sys/net80211 From: Adrian Chadd To: src-committers@freebsd.org, svn-src-all@freebsd.org, svn-src-head@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Mar 2013 05:04:27 -0000 if I break the build again before bsdcan, I promise I'll buy a nice bottle of scotch and distribute small quantities to developers who ask. Adrian On 9 March 2013 20:38, Adrian Chadd wrote: > Author: adrian > Date: Sun Mar 10 04:38:06 2013 > New Revision: 248127 > URL: http://svnweb.freebsd.org/changeset/base/248127 > > Log: > Kill this, it's not needed at this point and (hopefully) the parent > has correctly locked the ic/vap. > > Modified: > head/sys/net80211/ieee80211_superg.c > > Modified: head/sys/net80211/ieee80211_superg.c > ============================================================================== > --- head/sys/net80211/ieee80211_superg.c Sun Mar 10 03:52:35 2013 (r248126) > +++ head/sys/net80211/ieee80211_superg.c Sun Mar 10 04:38:06 2013 (r248127) > @@ -534,8 +534,6 @@ ff_flush(struct mbuf *head, struct mbuf > struct ieee80211_node *ni; > struct ieee80211vap *vap; > > - IEEE80211_TX_LOCK_ASSERT(vap->iv_ic); > - > for (m = head; m != last; m = next) { > next = m->m_nextpkt; > m->m_nextpkt = NULL; From owner-freebsd-current@FreeBSD.ORG Sun Mar 10 09:44:16 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 38B1D5D5 for ; Sun, 10 Mar 2013 09:44:16 +0000 (UTC) (envelope-from peo@intersonic.se) Received: from neonpark.inter-sonic.com (neonpark.inter-sonic.com [212.247.8.98]) by mx1.freebsd.org (Postfix) with ESMTP id A79B93FF for ; Sun, 10 Mar 2013 09:44:15 +0000 (UTC) X-Virus-Scanned: amavisd-new at BSDLabs AB Message-ID: <513C55E3.9060409@intersonic.se> Date: Sun, 10 Mar 2013 10:44:03 +0100 From: Per olof Ljungmark Organization: Intersonic AB User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130310 Thunderbird/17.0.4 MIME-Version: 1.0 To: "Hartmann, O." Subject: Re: CURRENT (r248061):Thunderbird SIGNAL 11 with OpenLDAP / nscd(1) broken pipe/ References: <513AFBE3.8070506@zedat.fu-berlin.de> <513AFFF0.6010500@zedat.fu-berlin.de> <513BB5F7.10201@intersonic.se> <513BC76F.6000609@zedat.fu-berlin.de> In-Reply-To: <513BC76F.6000609@zedat.fu-berlin.de> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: FreeBSD Current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Mar 2013 09:44:16 -0000 On 2013-03-10 00:36, Hartmann, O. wrote: > Am 03/09/13 23:21, schrieb Per olof Ljungmark: >> On 2013-03-09 10:25, Hartmann, O. wrote: >>> Am 03/09/13 10:07, schrieb Hartmann, O.: >>>> For the introduction, I filed a PR for this at beginning of 2012 and >>>> suffered from the very same problem close to two years before on ALL >>>> FreeBSD versions and platforms using OpenLDAP as the user backend: >>>> >>>> ports/164239: [PATCH] mail/thunderbird: crash with nss_ldap >>>> >>>> Even with the suggested patch by the maintainer the problem stayed. >>>> >>>> With the introduction of bad code due to updates with > r247804 and the >>>> following issues of SIGNAL 13/broken pipe, the problem now is even worse >>>> in FreeBSD 10.0 r248061. >>>> From my limited point of view I guess this long lasting unresolved >>>> problem could have been revealed itself and I hope this could be fixed >>>> along with fixing nscd(1). >>>> >>>> Again, Thunderbird in all flavours since 2010 crashes on FreeBSD 8/9 and >>>> now 10.0-CURRENT when it is used on systems with user backend in >>>> OpenLDAP or any LDAP (Thunderbird works on non-OpenLDAP backed systems >>>> of the same OS revision). >>>> >>>> I was able to "solve" the problem by starting Firefox first and only >>>> Firefox getting started prior to Thunderbird resolved the problem for a >>>> while, but closing Firefox and waiting a bit left Thunderbird >>>> unstarteable again until Firefox was closed and reopened again. >>>> >>>> I guess this strange behaviour reveals a deeper issue not necessarily >>>> bound to nscd(1) (since the problem with Thunderbird also occurs without >>>> nscd(1), BUT always bound to the use of OpenLDAP backend (with >>>> security/pam_ldap and net/nss_ldap from ports). >>>> >>>> Now, on FreeBSD 10.0-CURRENT r248061/amd64, Thunderbird dies immediately >>>> with SIGNAL 11 on those boxes with OpenLDAP backend and no "trick" makes >>>> Thunderbird starting enymore. >>>> >>>> In my desperation, I did a truss, see below and it seems to me that >>>> there is a problem getting the effective UID, since the SIGNAL 11 arises >>>> after geteuid(). >>>> >>>> At the moment, I have switched off nscd(1) by default since it is broken >>>> in CURRENT or doing very strange things (see list about broken pipe in >>>> the system, sudo(1) or even the port's system (SIGNAL 13)). >>>> >>>> I think there is a major issue covered and I hope this could be solved >>>> by the problems triggered. >>>> >>>> it is hard to believe that I'm the only one using FreeBSD for both >>>> workstation and server environment in conjuction with OpenLDAP and >>>> facing the problem with a popular software like Thunderbird. >>>> >>>> If it is a stupid configuation problem then this must be very, very >>>> special since it is now sticky with me for years. >>>> >>>> Here comes the truss ...: >>>> >>>> open("/etc/pwd.db",O_RDONLY,00) = 4 (0x4) >>>> fcntl(4,F_SETFD,FD_CLOEXEC) = 0 (0x0) >>>> fstat(4,{ mode=-rw-r--r-- ,inode=117927,size=40960,blksize=16384 }) = 0 >>>> (0x0) >>>> read(4,"\0\^F\^Ua\0\0\0\^B\0\0\^D\M-R\0"...,260) = 260 (0x104) >>>> pread(0x4,0x801bfc000,0x1000,0x6000,0x1,0x0) = 4096 (0x1000) >>>> pread(0x4,0x813927000,0x1000,0x2000,0x1,0x0) = 4096 (0x1000) >>>> close(4) = 0 (0x0) >>>> socket(PF_LOCAL,SOCK_STREAM,0) = 4 (0x4) >>>> connect(4,{ AF_UNIX "/var/run/nscd" },15) ERR#2 'No such file or >>>> directory' >>>> close(4) = 0 (0x0) >>>> sigprocmask(SIG_SETMASK,SIGHUP|SIGINT|SIGQUIT|SIGILL|SIGTRAP|SIGABRT|SIGEMT|SIGFPE|SIGKILL|SIGBUS|SIGSEGV|SIGSYS|SIGPIPE|SIGALRM|SIGTERM|SIGURG|SIGSTOP|SIGTSTP|SIGCONT|SIGCHLD|SIGTTIN|SIGTTOU|SIGIO|SIGXCPU|SIGXFSZ|SIGVTALRM|SIGPROF|SIGWINCH|SIGINFO|SIGUSR1|SIGUSR2,0x0) >>>> = 0 (0x0) >>>> sigaction(SIGPIPE,{ SIG_IGN 0x0 ss_t },{ SIG_IGN SA_RESTART ss_t }) = 0 >>>> (0x0) >>>> sigprocmask(SIG_SETMASK,0x0,0x0) = 0 (0x0) >>>> getpid() = 3235 (0xca3) >>>> geteuid() = 2002 (0x7d2) >>>> open("/usr/local/etc/nss_ldap.conf",O_RDONLY,0666) = 4 (0x4) >>>> fstat(4,{ mode=-rw-r--r-- ,inode=5818085,size=7997,blksize=16384 }) = 0 >>>> (0x0) >>>> fstat(4,{ mode=-rw-r--r-- ,inode=5818085,size=7997,blksize=16384 }) = 0 >>>> (0x0) >>>> read(4,"@(#)$Id: ldap.conf,v 2.47 2006/0"...,16384) = 7997 (0x1f3d) >>>> read(4,0x813928000,16384) = 0 (0x0) >>>> close(4) = 0 (0x0) >>>> __sysctl(0x7fffffffb1f8,0x2,0x7fffffffb220,0x7fffffffb200,0x0,0x0) = 0 (0x0) >>>> gettimeofday({1362819606.123684 },0x0) = 0 (0x0) >>>> getpid() = 3235 (0xca3) >>>> issetugid(0x35001c1c,0x80,0x801b1b600,0x10,0x2,0x1) = 0 (0x0) >>>> open("/etc/resolv.conf",O_RDONLY,0666) = 4 (0x4) >>>> fstat(4,{ mode=-rw-r--r-- ,inode=117845,size=101,blksize=16384 }) = 0 (0x0) >>>> read(4,"# Generated by resolvconf\nnames"...,16384) = 101 (0x65) >>>> read(4,0x813928000,16384) = 0 (0x0) >>>> close(4) = 0 (0x0) >>>> __sysctl(0x7fffffffab28,0x2,0x7fffffffad20,0x7fffffffab30,0x0,0x0) = 0 (0x0) >>>> issetugid(0x801526ae8,0x2e,0x2e,0x2e,0x101010101010101,0x8080808080808080) >>>> = 0 (0x0) >>>> stat("/etc/nsswitch.conf",{ mode=-rw-r--r-- >>>> ,inode=117790,size=991,blksize=16384 }) = 0 (0x0) >>>> open("/etc/hosts",O_RDONLY,0666) = 4 (0x4) >>>> fstat(4,{ mode=-rw-r--r-- ,inode=117862,size=2418,blksize=16384 }) = 0 (0x0) >>>> read(4,"# $FreeBSD: head/etc/hosts 10999"...,16384) = 2418 (0x972) >>>> close(4) = 0 (0x0) >>>> open("/usr/local/etc/openldap/ldap.conf",O_RDONLY,0666) = 4 (0x4) >>>> fstat(4,{ mode=-rw-r--r-- ,inode=5817420,size=410,blksize=16384 }) = 0 (0x0) >>>> read(4,"#\n# LDAP Defaults\n#\n\n# See l"...,16384) = 410 (0x19a) >>>> read(4,0x813928000,16384) = 0 (0x0) >>>> close(4) = 0 (0x0) >>>> geteuid() = 2002 (0x7d2) >>>> getuid() = 2002 (0x7d2) >>>> open("/home/ohartmann/ldaprc",O_RDONLY,0666) ERR#2 'No such file or >>>> directory' >>>> open("/home/ohartmann/.ldaprc",O_RDONLY,0666) ERR#2 'No such file or >>>> directory' >>>> open("ldaprc",O_RDONLY,0666) ERR#2 'No such file or >>>> directory' >>>> sigprocmask(SIG_SETMASK,SIGHUP|SIGINT|SIGQUIT|SIGILL|SIGTRAP|SIGABRT|SIGEMT|SIGFPE|SIGKILL|SIGBUS|SIGSEGV|SIGSYS|SIGPIPE|SIGALRM|SIGTERM|SIGURG|SIGSTOP|SIGTSTP|SIGCONT|SIGCHLD|SIGTTIN|SIGTTOU|SIGIO|SIGXCPU|SIGXFSZ|SIGVTALRM|SIGPROF|SIGWINCH|SIGINFO|SIGUSR1|SIGUSR2,0x0) >>>> = 0 (0x0) >>>> sigaction(SIGPIPE,{ SIG_IGN SA_RESTART ss_t },{ SIG_IGN 0x0 ss_t }) = 0 >>>> (0x0) >>>> sigprocmask(SIG_SETMASK,0x0,0x0) = 0 (0x0) >>>> getuid() = 2002 (0x7d2) >>>> stat("/etc/nsswitch.conf",{ mode=-rw-r--r-- >>>> ,inode=117790,size=991,blksize=16384 }) = 0 (0x0) >>>> geteuid() = 2002 (0x7d2) >>>> open("/etc/pwd.db",O_RDONLY,00) = 4 (0x4) >>>> fcntl(4,F_SETFD,FD_CLOEXEC) = 0 (0x0) >>>> fstat(4,{ mode=-rw-r--r-- ,inode=117927,size=40960,blksize=16384 }) = 0 >>>> (0x0) >>>> read(4,"\0\^F\^Ua\0\0\0\^B\0\0\^D\M-R\0"...,260) = 260 (0x104) >>>> pread(0x4,0x813928000,0x1000,0x6000,0x1,0x0) = 4096 (0x1000) >>>> pread(0x4,0x813929000,0x1000,0x5000,0x1,0x0) = 4096 (0x1000) >>>> close(4) = 0 (0x0) >>>> socket(PF_LOCAL,SOCK_STREAM,0) = 4 (0x4) >>>> connect(4,{ AF_UNIX "/var/run/nscd" },15) ERR#2 'No such file or >>>> directory' >>>> close(4) = 0 (0x0) >>>> sigprocmask(SIG_SETMASK,SIGHUP|SIGINT|SIGQUIT|SIGILL|SIGTRAP|SIGABRT|SIGEMT|SIGFPE|SIGKILL|SIGBUS|SIGSEGV|SIGSYS|SIGPIPE|SIGALRM|SIGTERM|SIGURG|SIGSTOP|SIGTSTP|SIGCONT|SIGCHLD|SIGTTIN|SIGTTOU|SIGIO|SIGXCPU|SIGXFSZ|SIGVTALRM|SIGPROF|SIGWINCH|SIGINFO|SIGUSR1|SIGUSR2,0x0) >>>> = 0 (0x0) >>>> sigaction(SIGPIPE,{ SIG_IGN 0x0 ss_t },{ SIG_IGN SA_RESTART ss_t }) = 0 >>>> (0x0) >>>> sigprocmask(SIG_SETMASK,0x0,0x0) = 0 (0x0) >>>> stat("/usr/local/etc/nss_ldap.conf",{ mode=-rw-r--r-- >>>> ,inode=5818085,size=7997,blksize=16384 }) = 0 (0x0) >>>> getpid() = 3235 (0xca3) >>>> geteuid() = 2002 (0x7d2) >>>> SIGNAL 11 (SIGSEGV) >>>> process exit, rval = 0 >>> >>> Deleting /usr/local/etc/nss_ldap.conf, which is a link (hard or soft, >>> doesn't matter the result) to /usr/local/etc/ldap.conf, makes >>> Thunderbird start again as OpenLDAP backend wasn't configured/installed. >>> >>> But in that case, no OpenLDAP backed up users are available on the system.SE556539368201 >> >> Not 100% sure but I believe I'm working right now on a system with >> LDAP-based user accounts ( a Samba LDAP directory ) through pam_ldap (in >> pam.d), nss_ldap (nsswitch.conf) and /usr/local/etc/nss_ldap.conf >> exactly as you describe. >> >> Never had issues similar to the above in the 7-STABLE through 9-STABLE >> series. The only problem I have with TB is its apetite for memory. >> >> Perhaps I'm missing something? May the difference be that my account is >> in /etc/passwd too? I could log in as a different user and check if >> you'd like. >> >> id peo >> uid=1001(peo) gid=0(wheel) groups=0(wheel),513(domusers),512(domadmin) >> >> Cheers, >> >> //per >> > > > My account is on LDAP. > Can you try with a user on LDAP? > Logging in as a user present only in the LDAP database shows me that a piece of user information is missing: [I have no name!@kreutzman ~]$ If you know what is missing please let me know so I can fix it. If I am logged in as the above user and do a "ls -l" only the numerical id is shown as file owner. However, when I start TB it does complain over missing user info but runs fine nevertheless. Cheers, //per From owner-freebsd-current@FreeBSD.ORG Sun Mar 10 12:42:20 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 61728FCB; Sun, 10 Mar 2013 12:42:20 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) by mx1.freebsd.org (Postfix) with ESMTP id 17723ADB; Sun, 10 Mar 2013 12:42:19 +0000 (UTC) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost1.zedat.fu-berlin.de (Exim 4.80.1) with esmtp (envelope-from ) id <1UEfZt-000C5L-Hj>; Sun, 10 Mar 2013 13:42:13 +0100 Received: from e178008226.adsl.alicedsl.de ([85.178.8.226] helo=[192.168.0.128]) by inpost2.zedat.fu-berlin.de (Exim 4.80.1) with esmtpsa (envelope-from ) id <1UEfZt-0009UW-Eo>; Sun, 10 Mar 2013 13:42:13 +0100 Subject: 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 From: "O. Hartmann" To: FreeBSD Current In-Reply-To: <513AFBE3.8070506@zedat.fu-berlin.de> References: <513AFBE3.8070506@zedat.fu-berlin.de> Content-Type: text/plain; charset="us-ascii" Organization: FU Berlin Date: Sun, 10 Mar 2013 12:44:08 +0100 Message-ID: <1362915848.11970.4.camel@thor.walstatt.dyndns.org> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit X-Originating-IP: 85.178.8.226 Cc: freebsd-ports@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Mar 2013 12:42:20 -0000 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 openldap-sasl-client-2.4.33_1 ===>>> Waiting on fetch & checksum for net/openldap24-sasl-client <<<=== ===> openldap-sasl-client-2.4.33_1 conflicts with installed package(s): openldap-sasl-client-2.4.33_1 /usr/local net/openldap24-sasl-client They install files into the same place. You may want to stop build with Ctrl + C. This looks weird tome, since how can /usr/local/ be a port? My update tool is ports-mgmt/portmaster. Regards, Oliver From owner-freebsd-current@FreeBSD.ORG Sun Mar 10 17:39:54 2013 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 6EB81C42; Sun, 10 Mar 2013 17:39:54 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by mx1.freebsd.org (Postfix) with ESMTP id 2E33D8A1; Sun, 10 Mar 2013 17:39:53 +0000 (UTC) Received: from freebsd-current.sentex.ca (localhost [127.0.0.1]) by freebsd-current.sentex.ca (8.14.5/8.14.5) with ESMTP id r2AHbstv062238; Sun, 10 Mar 2013 13:37:54 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-current.sentex.ca (8.14.5/8.14.5/Submit) id r2AHbsBd062225; Sun, 10 Mar 2013 17:37:54 GMT (envelope-from tinderbox@freebsd.org) Date: Sun, 10 Mar 2013 17:37:54 GMT Message-Id: <201303101737.r2AHbsBd062225@freebsd-current.sentex.ca> X-Authentication-Warning: freebsd-current.sentex.ca: tinderbox set sender to FreeBSD Tinderbox using -f Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Subject: [head tinderbox] failure on i386/i386 Precedence: bulk X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Mar 2013 17:39:54 -0000 TB --- 2013-03-10 17:20:18 - tinderbox 2.10 running on freebsd-current.sentex.ca TB --- 2013-03-10 17:20:18 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012 des@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2013-03-10 17:20:18 - starting HEAD tinderbox run for i386/i386 TB --- 2013-03-10 17:20:18 - cleaning the object tree TB --- 2013-03-10 17:20:18 - /usr/local/bin/svn stat /src TB --- 2013-03-10 17:20:22 - At svn revision 248133 TB --- 2013-03-10 17:20:23 - building world TB --- 2013-03-10 17:20:23 - CROSS_BUILD_TESTING=YES TB --- 2013-03-10 17:20:23 - MAKEOBJDIRPREFIX=/obj TB --- 2013-03-10 17:20:23 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-03-10 17:20:23 - SRCCONF=/dev/null TB --- 2013-03-10 17:20:23 - TARGET=i386 TB --- 2013-03-10 17:20:23 - TARGET_ARCH=i386 TB --- 2013-03-10 17:20:23 - TZ=UTC TB --- 2013-03-10 17:20:23 - __MAKE_CONF=/dev/null TB --- 2013-03-10 17:20:23 - cd /src TB --- 2013-03-10 17:20:23 - /usr/bin/make -B buildworld >>> Building an up-to-date make(1) >>> World build started on Sun Mar 10 17:20:28 UTC 2013 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools [...] c++ -O2 -pipe -I/src/lib/clang/libclangcodegen/../../../contrib/llvm/include -I/src/lib/clang/libclangcodegen/../../../contrib/llvm/tools/clang/include -I/src/lib/clang/libclangcodegen/../../../contrib/llvm/tools/clang/lib/CodeGen -I. -I/src/lib/clang/libclangcodegen/../../../contrib/llvm/../../lib/clang/include -DLLVM_ON_UNIX -DLLVM_ON_FREEBSD -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS -fno-strict-aliasing -DLLVM_DEFAULT_TARGET_TRIPLE=\"i386-unknown-freebsd10.0\" -DLLVM_HOSTTRIPLE=\"x86_64-unknown-freebsd10.0\" -DDEFAULT_SYSROOT=\"/obj/i386.i386/src/tmp\" -I/obj/i386.i386/src/tmp/legacy/usr/include -fno-exceptions -fno-rtti -c /src/lib/clang/libclangcodegen/../../../contrib/llvm/tools/clang/lib/CodeGen/CGRTTI.cpp -o CGRTTI.o c++ -O2 -pipe -I/src/lib/clang/libclangcodegen/../../../contrib/llvm/include -I/src/lib/clang/libclangcodegen/../../../contrib/llvm/tools/clang/include -I/src/lib/clang/libclangcodegen/../../../contrib/llvm/tools/clang/lib/CodeGen -I. -I/src/lib/clang/libclangcodegen/../../../contrib/llvm/../../lib/clang/include -DLLVM_ON_UNIX -DLLVM_ON_FREEBSD -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS -fno-strict-aliasing -DLLVM_DEFAULT_TARGET_TRIPLE=\"i386-unknown-freebsd10.0\" -DLLVM_HOSTTRIPLE=\"x86_64-unknown-freebsd10.0\" -DDEFAULT_SYSROOT=\"/obj/i386.i386/src/tmp\" -I/obj/i386.i386/src/tmp/legacy/usr/include -fno-exceptions -fno-rtti -c /src/lib/clang/libclangcodegen/../../../contrib/llvm/tools/clang/lib/CodeGen/CGRecordLayoutBuilder.cpp -o CGRecordLayoutBuilder.o c++ -O2 -pipe -I/src/lib/clang/libclangcodegen/../../../contrib/llvm/include -I/src/lib/clang/libclangcodegen/../../../contrib/llvm/tools/clang/include -I/src/lib/clang/libclangcodegen/../../../contrib/llvm/tools/clang/lib/CodeGen -I. -I/src/lib/clang/libclangcodegen/../../../contrib/llvm/../../lib/clang/include -DLLVM_ON_UNIX -DLLVM_ON_FREEBSD -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS -fno-strict-aliasing -DLLVM_DEFAULT_TARGET_TRIPLE=\"i386-unknown-freebsd10.0\" -DLLVM_HOSTTRIPLE=\"x86_64-unknown-freebsd10.0\" -DDEFAULT_SYSROOT=\"/obj/i386.i386/src/tmp\" -I/obj/i386.i386/src/tmp/legacy/usr/include -fno-exceptions -fno-rtti -c /src/lib/clang/libclangcodegen/../../../contrib/llvm/tools/clang/lib/CodeGen/CGStmt.cpp -o CGStmt.o /src/lib/clang/libclangcodegen/../../../contrib/llvm/tools/clang/lib/CodeGen/CGStmt.cpp: In member function 'void clang::CodeGen::CodeGenFunction::EmitAsmStmt(const clang::AsmStmt&)': /src/lib/clang/libclangcodegen/../../../contrib/llvm/tools/clang/lib/CodeGen/CGStmt.cpp:1418: internal compiler error: in var_ann, at tree-flow-inline.h:127 Please submit a full bug report, with preprocessed source if appropriate. See for instructions. *** [CGStmt.o] Error code 1 Stop in /src/lib/clang/libclangcodegen. *** [all] Error code 1 Stop in /src/lib/clang. *** [cross-tools] Error code 1 Stop in /src. *** [_cross-tools] Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2013-03-10 17:37:54 - WARNING: /usr/bin/make returned exit code 1 TB --- 2013-03-10 17:37:54 - ERROR: failed to build world TB --- 2013-03-10 17:37:54 - 890.21 user 110.57 system 1056.11 real http://tinderbox.freebsd.org/tinderbox-head-ss-build-HEAD-i386-i386.full From owner-freebsd-current@FreeBSD.ORG Sun Mar 10 20:43:01 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 0DAE6528; Sun, 10 Mar 2013 20:43:01 +0000 (UTC) (envelope-from pawel@dawidek.net) Received: from mail.dawidek.net (garage.dawidek.net [91.121.88.72]) by mx1.freebsd.org (Postfix) with ESMTP id C8B72F01; Sun, 10 Mar 2013 20:43:00 +0000 (UTC) Received: from localhost (89-73-195-149.dynamic.chello.pl [89.73.195.149]) by mail.dawidek.net (Postfix) with ESMTPSA id 0FC82BEF; Sun, 10 Mar 2013 21:39:50 +0100 (CET) Date: Sun, 10 Mar 2013 21:44:30 +0100 From: Pawel Jakub Dawidek To: John Baldwin Subject: Re: r247839: broken pipe - for top, sudo and ports Message-ID: <20130310204430.GB9784@garage.freebsd.pl> References: <5135B7E1.3050002@zedat.fu-berlin.de> <5135BBD9.9090009@FreeBSD.org> <51364914.2010104@zedat.fu-berlin.de> <201303060804.57238.jhb@freebsd.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Bn2rw/3z4jIqBvZU" Content-Disposition: inline In-Reply-To: <201303060804.57238.jhb@freebsd.org> X-OS: FreeBSD 10.0-CURRENT amd64 User-Agent: Mutt/1.5.21 (2010-09-15) Cc: davide@FreeBSD.org, Dimitry Andric , freebsd-current@freebsd.org, "Hartmann, O." X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Mar 2013 20:43:01 -0000 --Bn2rw/3z4jIqBvZU Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Mar 06, 2013 at 08:04:57AM -0500, John Baldwin wrote: > On Tuesday, March 05, 2013 2:35:48 pm Hartmann, O. wrote: > > On recent FreeBSD 10.0-CURRENT/amd64 (CLANG buildworld, serveral systems > > (3) the same symptoms)), many services drop a sporadic > >=20 > > broken pipe > >=20 > > This happesn to system's top (I have to type it several times to get > > finally a top), it happens to "sudo su -", it happens to SSH (drops > > connection with broken pipe) and as I reported earlier, it seems to > > affect the entire port system, since I can not build any port, I receive > >=20 > > *** [do-extract] Signal 13 > >=20 > > This is dramatic for me, because several modules (rtc, linux_adobe ...) > > can not be recompiled as it is required by the last /usr/src/UPDATING > > entry 20130304. > >=20 > > Since dbus fails to start and even the nVidia driver (which is a kernel > > module, it canot be built and therefore ... ). > >=20 > > Dimitry, I put you into CC, just in case. It seems that the last commits > > (not only the new DRM2 mess) broke something. > >=20 > > I hope that others using FreeBSD 10.0CURRENT with CLANG can confirm thi= s.\ >=20 > Have you tried backing up to just before all of pjd@'s file descriptor and > capsicum commits? It broke some other stuff initially related to fd pass= ing, > so I don't think it is beyond imagination that it broke something with UN= IX > domain sockets in general. Is there a consensus already if this is result of my changes or davide's r247804? I just upgraded my laptop to today's HEAD and I don't see any weird behaviour yet. If someone can provide a way to reproduce the problem, I'd be happy to investigate. --=20 Pawel Jakub Dawidek http://www.wheelsystems.com FreeBSD committer http://www.FreeBSD.org Am I Evil? Yes, I Am! http://tupytaj.pl --Bn2rw/3z4jIqBvZU Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEARECAAYFAlE88K4ACgkQForvXbEpPzQlQACgovYkKt+YDykpeTJ3bEh6epaY JBcAoO3EP0EoQ25Uh6DggAec/uQFS7ak =cj7/ -----END PGP SIGNATURE----- --Bn2rw/3z4jIqBvZU-- From owner-freebsd-current@FreeBSD.ORG Sun Mar 10 21:23:12 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 8286E128; Sun, 10 Mar 2013 21:23:12 +0000 (UTC) (envelope-from jilles@stack.nl) Received: from mx1.stack.nl (unknown [IPv6:2001:610:1108:5012::107]) by mx1.freebsd.org (Postfix) with ESMTP id 3E329109; Sun, 10 Mar 2013 21:23:12 +0000 (UTC) Received: from snail.stack.nl (snail.stack.nl [IPv6:2001:610:1108:5010::131]) by mx1.stack.nl (Postfix) with ESMTP id 172CC1203BF; Sun, 10 Mar 2013 22:22:57 +0100 (CET) Received: by snail.stack.nl (Postfix, from userid 1677) id E65542848C; Sun, 10 Mar 2013 22:22:56 +0100 (CET) Date: Sun, 10 Mar 2013 22:22:56 +0100 From: Jilles Tjoelker To: Jan Beich Subject: Re: r247839: broken pipe - for top, sudo and ports Message-ID: <20130310212256.GD94667@stack.nl> References: <5135B7E1.3050002@zedat.fu-berlin.de> <5135BBD9.9090009@FreeBSD.org> <51364914.2010104@zedat.fu-berlin.de> <51364E8D.5020608@zedat.fu-berlin.de> <20130306212408.GA15814@stack.nl> <1UDUQ3-0009HU-83@internal.tormail.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1UDUQ3-0009HU-83@internal.tormail.org> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: Davide Italiano , "Hartmann, O." , FreeBSD Current , Dimitry Andric X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Mar 2013 21:23:12 -0000 On Thu, Mar 07, 2013 at 04:54:01AM -0100, Jan Beich wrote: > Jilles Tjoelker writes: > > On Tue, Mar 05, 2013 at 08:59:09PM +0100, Hartmann, O. wrote: > >> A "truss top" reveals this, is this of help? > >> [...] > >> stat("/etc/nsswitch.conf",{ mode=-rw-r--r-- > >> ,inode=162310,size=1007,blksize=32768 }) = 0 (0x0) > >> stat("/etc/nsswitch.conf",{ mode=-rw-r--r-- > >> ,inode=162310,size=1007,blksize=32768 }) = 0 (0x0) > >> stat("/etc/nsswitch.conf",{ mode=-rw-r--r-- > >> ,inode=162310,size=1007,blksize=32768 }) = 0 (0x0) > >> stat("/etc/nsswitch.conf",{ mode=-rw-r--r-- > >> ,inode=162310,size=1007,blksize=32768 }) = 0 (0x0) > >> stat("/etc/nsswitch.conf",{ mode=-rw-r--r-- > >> ,inode=162310,size=1007,blksize=32768 }) = 0 (0x0) > >> socket(PF_LOCAL,SOCK_STREAM,0) = 4 (0x4) > >> connect(4,{ AF_UNIX "/var/run/nscd" },15) = 0 (0x0) > >> fcntl(4,F_SETFL,O_NONBLOCK) = 0 (0x0) > >> kqueue(0x80183b000,0x80122fc58,0x10,0x80062b308,0x80183b010,0x2) = 5 (0x5) > >> kevent(5,{0x4,EVFILT_WRITE,EV_ADD,0,0x0,0x0},1,0x0,0,0x0) = 0 (0x0) > >> kqueue(0x5,0x7fffffffd2e0,0x1,0x0,0x0,0x0) = 6 (0x6) > >> kevent(6,{0x4,EVFILT_READ,EV_ADD,0,0x0,0x0},1,0x0,0,0x0) = 0 (0x0) > >> kevent(5,{0x4,EVFILT_WRITE,EV_ADD,1,0x4,0x0},1,0x0,0,0x0) = 0 (0x0) > >> kevent(5,0x0,0,{0x4,EVFILT_WRITE,EV_EOF,0,0x2000,0x0},1,0x0) = 1 (0x1) > >> sendmsg(0x4,0x7fffffffd290,0x0,0x1,0x1,0x0) ERR#32 'Broken pipe' > >> SIGNAL 13 (SIGPIPE) > >> process exit, rval = 0 > > Apparently there is a bug that causes nscd to close the connection > > immediately but even then it is wrong that this terminates the calling > > program with SIGPIPE. > > The below patch prevents the SIGPIPE but cannot revive the connection to > > nscd. This may cause numeric UIDs in top or increase the load on the > > directory server. It is compile tested only. > [...] > The patch seems to fix the issue in a world after r247804. I don't see > numeric UIDs in top but without the patch top crashes with SIGPIPE a lot > less frequently than sudo or make install (in base/ports) for me. > In my case shutting down nscd helped, too. Compared to stock > nsswitch.conf I only have "cache" added. Can you find what causes nscd to close the connection quickly, such as using ktrace? -- Jilles Tjoelker From owner-freebsd-current@FreeBSD.ORG Sun Mar 10 22:11:33 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 5ADA23D9; Sun, 10 Mar 2013 22:11:33 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) by mx1.freebsd.org (Postfix) with ESMTP id 140482BE; Sun, 10 Mar 2013 22:11:32 +0000 (UTC) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost1.zedat.fu-berlin.de (Exim 4.80.1) with esmtp (envelope-from ) id <1UEoSq-001ZKa-6K>; Sun, 10 Mar 2013 23:11:32 +0100 Received: from e178008226.adsl.alicedsl.de ([85.178.8.226] helo=munin.geoinf.fu-berlin.de) by inpost2.zedat.fu-berlin.de (Exim 4.80.1) with esmtpsa (envelope-from ) id <1UEoSq-000dLD-3O>; Sun, 10 Mar 2013 23:11:32 +0100 Message-ID: <513D0553.2060302@zedat.fu-berlin.de> Date: Sun, 10 Mar 2013 23:12:35 +0100 From: "Hartmann, O." Organization: FU Berlin User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130309 Thunderbird/17.0.4 MIME-Version: 1.0 To: Pawel Jakub Dawidek Subject: Re: r247839: broken pipe - for top, sudo and ports References: <5135B7E1.3050002@zedat.fu-berlin.de> <5135BBD9.9090009@FreeBSD.org> <51364914.2010104@zedat.fu-berlin.de> <201303060804.57238.jhb@freebsd.org> <20130310204430.GB9784@garage.freebsd.pl> In-Reply-To: <20130310204430.GB9784@garage.freebsd.pl> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Originating-IP: 85.178.8.226 Cc: davide@FreeBSD.org, freebsd-current@freebsd.org, Dimitry Andric X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Mar 2013 22:11:33 -0000 Am 03/10/13 21:44, schrieb Pawel Jakub Dawidek: > On Wed, Mar 06, 2013 at 08:04:57AM -0500, John Baldwin wrote: >> On Tuesday, March 05, 2013 2:35:48 pm Hartmann, O. wrote: >>> On recent FreeBSD 10.0-CURRENT/amd64 (CLANG buildworld, serveral systems >>> (3) the same symptoms)), many services drop a sporadic >>> >>> broken pipe >>> >>> This happesn to system's top (I have to type it several times to get >>> finally a top), it happens to "sudo su -", it happens to SSH (drops >>> connection with broken pipe) and as I reported earlier, it seems to >>> affect the entire port system, since I can not build any port, I receive >>> >>> *** [do-extract] Signal 13 >>> >>> This is dramatic for me, because several modules (rtc, linux_adobe ...) >>> can not be recompiled as it is required by the last /usr/src/UPDATING >>> entry 20130304. >>> >>> Since dbus fails to start and even the nVidia driver (which is a kernel >>> module, it canot be built and therefore ... ). >>> >>> Dimitry, I put you into CC, just in case. It seems that the last commits >>> (not only the new DRM2 mess) broke something. >>> >>> I hope that others using FreeBSD 10.0CURRENT with CLANG can confirm this.\ >> >> Have you tried backing up to just before all of pjd@'s file descriptor and >> capsicum commits? It broke some other stuff initially related to fd passing, >> so I don't think it is beyond imagination that it broke something with UNIX >> domain sockets in general. > > Is there a consensus already if this is result of my changes or davide's > r247804? > > I just upgraded my laptop to today's HEAD and I don't see any weird > behaviour yet. If someone can provide a way to reproduce the problem, > I'd be happy to investigate. > Just checked on one of my servers running most recent FreeBSD: FreeBSD 10.0-CURRENT #0 r248106: Sat Mar 9 16:43:06 CET 2013 amd64 Starting nscd with service nscd onestart and try to recompile suod with portmaster sudo results in [...] ===> Extracting for sudo-1.8.6.p7 => SHA256 Checksum OK for sudo-1.8.6p7.tar.gz. *** [do-extract] Signal 13 /etc/nscd.conf is as it is provided in /usr/share/examples/etc/nscd.conf. sudo itself also acts weird and sometimes, sporadically, with broken pipe. If I start nscd by system startup, even now with the above shown recent version of FBSD CURRENT, sometimes OpenLDAP's slapd doesn' startup - this is critical. As stated before, switching off nscd solves the problem. Regards, oh From owner-freebsd-current@FreeBSD.ORG Sun Mar 10 22:29:09 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id DBC04AF9; Sun, 10 Mar 2013 22:29:09 +0000 (UTC) (envelope-from jbeich@tormail.org) Received: from outgoing.tormail.org (outgoing.tormail.org [82.221.96.22]) by mx1.freebsd.org (Postfix) with ESMTP id 86BE1368; Sun, 10 Mar 2013 22:29:09 +0000 (UTC) Received: from localhost ([127.0.0.1] helo=internal.tormail.org) by outgoing.tormail.org with esmtp (Exim 4.72) (envelope-from ) id 1UEojq-0007vW-J5; Mon, 11 Mar 2013 01:29:07 +0300 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=tormail.org; s=tm; h=Message-Id:X-TorMail-User:Content-Type:MIME-Version:References:Date:Subject:Cc:To:From; bh=cXRwQhp4kIX0p8n8qWK7pdNAmLuqhKgkVjT5+ZP0xT8=; b=hYvOb3cJNVzGFOezNnxzHKoVmVbrHtB2c8DVUA/WacCnklicLRibwmBbIKcQv4FTXDQMrGimvicJ6jsMvBtaoFIn82DsER+yI5oAlhLEuFVAADgoTJ9gbBTPhuDlwpaylgksiorFe7ux5mJ8vs2cGb/T/o2MrenZ5x/CMg6DqY8=; Received: from jbeich by internal.tormail.org with local (Exim 4.63) (envelope-from ) id 1UEoh3-000Ly7-Mf; Sun, 10 Mar 2013 22:26:21 +0000 From: Jan Beich To: Jilles Tjoelker Subject: Re: r247839: broken pipe - for top, sudo and ports Date: Sun, 10 Mar 2013 20:26:03 -0200 References: <5135B7E1.3050002@zedat.fu-berlin.de> <5135BBD9.9090009@FreeBSD.org> <51364914.2010104@zedat.fu-berlin.de> <51364E8D.5020608@zedat.fu-berlin.de> <20130306212408.GA15814@stack.nl> <1UDUQ3-0009HU-83@internal.tormail.org> <20130310212256.GD94667@stack.nl> MIME-Version: 1.0 Content-Type: text/plain X-TorMail-User: jbeich Message-Id: <1UEoh3-000Ly7-Mf@internal.tormail.org> Cc: Davide Italiano , "Hartmann, O." , FreeBSD Current , Dimitry Andric X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Mar 2013 22:29:09 -0000 Jilles Tjoelker writes: > On Thu, Mar 07, 2013 at 04:54:01AM -0100, Jan Beich wrote: > >> Jilles Tjoelker writes: > >> > On Tue, Mar 05, 2013 at 08:59:09PM +0100, Hartmann, O. wrote: > >> >> A "truss top" reveals this, is this of help? > >> >> [...] >> >> stat("/etc/nsswitch.conf",{ mode=-rw-r--r-- >> >> ,inode=162310,size=1007,blksize=32768 }) = 0 (0x0) >> >> stat("/etc/nsswitch.conf",{ mode=-rw-r--r-- >> >> ,inode=162310,size=1007,blksize=32768 }) = 0 (0x0) >> >> stat("/etc/nsswitch.conf",{ mode=-rw-r--r-- >> >> ,inode=162310,size=1007,blksize=32768 }) = 0 (0x0) >> >> stat("/etc/nsswitch.conf",{ mode=-rw-r--r-- >> >> ,inode=162310,size=1007,blksize=32768 }) = 0 (0x0) >> >> stat("/etc/nsswitch.conf",{ mode=-rw-r--r-- >> >> ,inode=162310,size=1007,blksize=32768 }) = 0 (0x0) >> >> socket(PF_LOCAL,SOCK_STREAM,0) = 4 (0x4) >> >> connect(4,{ AF_UNIX "/var/run/nscd" },15) = 0 (0x0) >> >> fcntl(4,F_SETFL,O_NONBLOCK) = 0 (0x0) >> >> kqueue(0x80183b000,0x80122fc58,0x10,0x80062b308,0x80183b010,0x2) >> >> = 5 (0x5) >> >> kevent(5,{0x4,EVFILT_WRITE,EV_ADD,0,0x0,0x0},1,0x0,0,0x0) = 0 (0x0) >> >> kqueue(0x5,0x7fffffffd2e0,0x1,0x0,0x0,0x0) = 6 (0x6) >> >> kevent(6,{0x4,EVFILT_READ,EV_ADD,0,0x0,0x0},1,0x0,0,0x0) = 0 (0x0) >> >> kevent(5,{0x4,EVFILT_WRITE,EV_ADD,1,0x4,0x0},1,0x0,0,0x0) = 0 (0x0) >> >> kevent(5,0x0,0,{0x4,EVFILT_WRITE,EV_EOF,0,0x2000,0x0},1,0x0) = 1 (0x1) >> >> sendmsg(0x4,0x7fffffffd290,0x0,0x1,0x1,0x0) ERR#32 'Broken pipe' >> >> SIGNAL 13 (SIGPIPE) >> >> process exit, rval = 0 > >> > Apparently there is a bug that causes nscd to close the connection >> > immediately but even then it is wrong that this terminates the calling >> > program with SIGPIPE. > >> > The below patch prevents the SIGPIPE but cannot revive the connection to >> > nscd. This may cause numeric UIDs in top or increase the load on the >> > directory server. It is compile tested only. >> [...] > >> The patch seems to fix the issue in a world after r247804. I don't see >> numeric UIDs in top but without the patch top crashes with SIGPIPE a lot >> less frequently than sudo or make install (in base/ports) for me. > >> In my case shutting down nscd helped, too. Compared to stock >> nsswitch.conf I only have "cache" added. > > Can you find what causes nscd to close the connection quickly, such as > using ktrace? # single user mode $ ktrace -p $(pgrep nscd); top -b; ktrace -c; kdump 71 nscd GIO fd 5 wrote 0 bytes "" 71 nscd GIO fd 5 read 32 bytes 0x0000 0400 0000 0000 0000 ffff 1000 0000 0000 0100 |..................| 0x0012 0000 0000 0000 0000 0000 0000 0000 |..............| 71 nscd RET kevent 1 71 nscd CALL accept(0x4,0,0) 71 nscd RET accept 6 71 nscd CALL getsockopt(0x6,0,0x1,0x7fffff9fce28,0x7fffff9fce24) 71 nscd RET getsockopt 0 71 nscd CALL kevent(0x5,0x7fffff9fcf00,0x2,0,0,0x7fffff9fcf50) 71 nscd GIO fd 5 wrote 64 bytes 0x0000 0600 0000 0000 0000 f9ff 1100 0000 0000 401f |................@.| 0x0012 0000 401f 0000 40e6 4002 0800 0000 0600 0000 |..@...@.@.........| 0x0024 0000 0000 ffff 1100 0100 0000 0400 0000 0000 |..................| 0x0036 0000 40e6 4002 0800 0000 |..@.@.....| 71 nscd GIO fd 5 read 0 bytes "" 71 nscd RET kevent 0 71 nscd CALL kevent(0x5,0x7fffff9fcec0,0x1,0,0,0x7fffff9fcee0) 71 nscd GIO fd 5 wrote 32 bytes 0x0000 0400 0000 0000 0000 ffff 1100 0000 0000 0000 |..................| 0x0012 0000 0000 0000 0000 0000 0000 0000 |..............| 71 nscd GIO fd 5 read 0 bytes "" 71 nscd RET kevent 0 71 nscd CALL kevent(0x5,0,0,0x7fffff9fcec0,0x1,0) 71 nscd GIO fd 5 wrote 0 bytes "" 71 nscd GIO fd 5 read 32 bytes 0x0000 0600 0000 0000 0000 f9ff 3000 0000 0000 0100 |..........0.......| 0x0012 0000 0000 0000 40e6 4002 0800 0000 |......@.@.....| 71 nscd RET kevent 1 71 nscd CALL close(0x6) 71 nscd RET close 0 71 nscd CALL kevent(0x5,0,0,0x7fffff9fcec0,0x1,0) From owner-freebsd-current@FreeBSD.ORG Sun Mar 10 23:50:40 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 9D42FBDA; Sun, 10 Mar 2013 23:50:40 +0000 (UTC) (envelope-from jilles@stack.nl) Received: from mx1.stack.nl (relay02.stack.nl [IPv6:2001:610:1108:5010::104]) by mx1.freebsd.org (Postfix) with ESMTP id 4DB597D7; Sun, 10 Mar 2013 23:50:40 +0000 (UTC) Received: from snail.stack.nl (snail.stack.nl [IPv6:2001:610:1108:5010::131]) by mx1.stack.nl (Postfix) with ESMTP id F15C83592FE; Mon, 11 Mar 2013 00:50:37 +0100 (CET) Received: by snail.stack.nl (Postfix, from userid 1677) id DAD762848C; Mon, 11 Mar 2013 00:50:37 +0100 (CET) Date: Mon, 11 Mar 2013 00:50:37 +0100 From: Jilles Tjoelker To: Jan Beich Subject: Re: r247839: broken pipe - for top, sudo and ports Message-ID: <20130310235037.GE94667@stack.nl> References: <5135B7E1.3050002@zedat.fu-berlin.de> <5135BBD9.9090009@FreeBSD.org> <51364914.2010104@zedat.fu-berlin.de> <51364E8D.5020608@zedat.fu-berlin.de> <20130306212408.GA15814@stack.nl> <1UDUQ3-0009HU-83@internal.tormail.org> <20130310212256.GD94667@stack.nl> <1UEoh3-000Ly7-Mf@internal.tormail.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1UEoh3-000Ly7-Mf@internal.tormail.org> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: Davide Italiano , Dimitry Andric , FreeBSD Current , "Hartmann, O." X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 10 Mar 2013 23:50:40 -0000 On Sun, Mar 10, 2013 at 08:26:03PM -0200, Jan Beich wrote: > Jilles Tjoelker writes: > > On Thu, Mar 07, 2013 at 04:54:01AM -0100, Jan Beich wrote: > >> Jilles Tjoelker writes: > >> > On Tue, Mar 05, 2013 at 08:59:09PM +0100, Hartmann, O. wrote: > >> >> A "truss top" reveals this, is this of help? > >> >> [...] > >> >> stat("/etc/nsswitch.conf",{ mode=-rw-r--r-- > >> >> ,inode=162310,size=1007,blksize=32768 }) = 0 (0x0) > >> >> stat("/etc/nsswitch.conf",{ mode=-rw-r--r-- > >> >> ,inode=162310,size=1007,blksize=32768 }) = 0 (0x0) > >> >> stat("/etc/nsswitch.conf",{ mode=-rw-r--r-- > >> >> ,inode=162310,size=1007,blksize=32768 }) = 0 (0x0) > >> >> stat("/etc/nsswitch.conf",{ mode=-rw-r--r-- > >> >> ,inode=162310,size=1007,blksize=32768 }) = 0 (0x0) > >> >> stat("/etc/nsswitch.conf",{ mode=-rw-r--r-- > >> >> ,inode=162310,size=1007,blksize=32768 }) = 0 (0x0) > >> >> socket(PF_LOCAL,SOCK_STREAM,0) = 4 (0x4) > >> >> connect(4,{ AF_UNIX "/var/run/nscd" },15) = 0 (0x0) > >> >> fcntl(4,F_SETFL,O_NONBLOCK) = 0 (0x0) > >> >> kqueue(0x80183b000,0x80122fc58,0x10,0x80062b308,0x80183b010,0x2) > >> >> = 5 (0x5) > >> >> kevent(5,{0x4,EVFILT_WRITE,EV_ADD,0,0x0,0x0},1,0x0,0,0x0) = 0 (0x0) > >> >> kqueue(0x5,0x7fffffffd2e0,0x1,0x0,0x0,0x0) = 6 (0x6) > >> >> kevent(6,{0x4,EVFILT_READ,EV_ADD,0,0x0,0x0},1,0x0,0,0x0) = 0 (0x0) > >> >> kevent(5,{0x4,EVFILT_WRITE,EV_ADD,1,0x4,0x0},1,0x0,0,0x0) = 0 (0x0) > >> >> kevent(5,0x0,0,{0x4,EVFILT_WRITE,EV_EOF,0,0x2000,0x0},1,0x0) = 1 (0x1) > >> >> sendmsg(0x4,0x7fffffffd290,0x0,0x1,0x1,0x0) ERR#32 'Broken pipe' > >> >> SIGNAL 13 (SIGPIPE) > >> >> process exit, rval = 0 > >> > Apparently there is a bug that causes nscd to close the connection > >> > immediately but even then it is wrong that this terminates the calling > >> > program with SIGPIPE. > >> > The below patch prevents the SIGPIPE but cannot revive the connection to > >> > nscd. This may cause numeric UIDs in top or increase the load on the > >> > directory server. It is compile tested only. > >> [...] > >> The patch seems to fix the issue in a world after r247804. I don't see > >> numeric UIDs in top but without the patch top crashes with SIGPIPE a lot > >> less frequently than sudo or make install (in base/ports) for me. > >> In my case shutting down nscd helped, too. Compared to stock > >> nsswitch.conf I only have "cache" added. > > Can you find what causes nscd to close the connection quickly, such as > > using ktrace? > # single user mode > $ ktrace -p $(pgrep nscd); top -b; ktrace -c; kdump > 71 nscd GIO fd 5 wrote 0 bytes > "" > 71 nscd GIO fd 5 read 32 bytes > 0x0000 0400 0000 0000 0000 ffff 1000 0000 0000 0100 |..................| > 0x0012 0000 0000 0000 0000 0000 0000 0000 |..............| > > 71 nscd RET kevent 1 > 71 nscd CALL accept(0x4,0,0) > 71 nscd RET accept 6 We are in usr.sbin/nscd/nscd.c accept_connection() here. > 71 nscd CALL getsockopt(0x6,0,0x1,0x7fffff9fce28,0x7fffff9fce24) > 71 nscd RET getsockopt 0 Probably getpeereid(). On another note, nscd leaks the file descriptor if this, the below init_query_state() or the below kevent() fails. > 71 nscd CALL kevent(0x5,0x7fffff9fcf00,0x2,0,0,0x7fffff9fcf50) > 71 nscd GIO fd 5 wrote 64 bytes > 0x0000 0600 0000 0000 0000 f9ff 1100 0000 0000 401f |................@.| > 0x0012 0000 401f 0000 40e6 4002 0800 0000 0600 0000 |..@...@.@.........| > 0x0024 0000 0000 ffff 1100 0100 0000 0400 0000 0000 |..................| > 0x0036 0000 40e6 4002 0800 0000 |..@.@.....| > Adding an EVFILT_TIMER and an EVFILT_READ. The data field for the EVFILT_TIMER is a bit strange. I would expect 0x0000000000001f40 (8000 decimal) but it puts instead 0x00001f4000001f40. This does not happen when I run tools/regression/kqueue/kqtest on a stable/9 amd64 machine or on ref10-amd64 which currently runs r247722. On a head (r248047) i386 machine, the data field looks right. > 71 nscd GIO fd 5 read 0 bytes > "" > 71 nscd RET kevent 0 > 71 nscd CALL kevent(0x5,0x7fffff9fcec0,0x1,0,0,0x7fffff9fcee0) > 71 nscd GIO fd 5 wrote 32 bytes > 0x0000 0400 0000 0000 0000 ffff 1100 0000 0000 0000 |..................| > 0x0012 0000 0000 0000 0000 0000 0000 0000 |..............| > Probably registering interest for the next connection. > 71 nscd GIO fd 5 read 0 bytes > "" > 71 nscd RET kevent 0 > 71 nscd CALL kevent(0x5,0,0,0x7fffff9fcec0,0x1,0) > 71 nscd GIO fd 5 wrote 0 bytes > "" > 71 nscd GIO fd 5 read 32 bytes > 0x0000 0600 0000 0000 0000 f9ff 3000 0000 0000 0100 |..........0.......| > 0x0012 0000 0000 0000 40e6 4002 0800 0000 |......@.@.....| > The timer has already expired. This cannot be right. (It cannot be that EVFILT_READ is broken and eight seconds actually passed because the send calls would have worked in that case.) tools/regression/kqueue/kqtest works correctly on the aforementioned r248047 head i386 machine. > 71 nscd RET kevent 1 > 71 nscd CALL close(0x6) > 71 nscd RET close 0 > 71 nscd CALL kevent(0x5,0,0,0x7fffff9fcec0,0x1,0) -- Jilles Tjoelker From owner-freebsd-current@FreeBSD.ORG Mon Mar 11 10:17:53 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 362F83C5; Mon, 11 Mar 2013 10:17:53 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from tensor.andric.com (tensor.andric.com [IPv6:2001:7b8:3a7:1:2d0:b7ff:fea0:8c26]) by mx1.freebsd.org (Postfix) with ESMTP id D18D22F5; Mon, 11 Mar 2013 10:17:52 +0000 (UTC) Received: from [192.168.0.6] (spaceball.home.andric.com [192.168.0.6]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id 29ECA5C73; Mon, 11 Mar 2013 11:17:52 +0100 (CET) Message-ID: <513DAF4F.50602@FreeBSD.org> Date: Mon, 11 Mar 2013 11:17:51 +0100 From: Dimitry Andric Organization: The FreeBSD Project User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:20.0) Gecko/20100101 Thunderbird/20.0 MIME-Version: 1.0 To: Steve Kargl Subject: Re: CURRENT: lang/gcc fails to build on CURRENT with error: configure: error: no usable dependency style found References: <513B56E8.2060702@zedat.fu-berlin.de> <8F5265A6-396A-426F-A3F8-EFD44D167313@FreeBSD.org> <20130309233930.GA95285@troutmask.apl.washington.edu> In-Reply-To: <20130309233930.GA95285@troutmask.apl.washington.edu> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD Current , "Hartmann, O." , freebsd-ports@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Mar 2013 10:17:53 -0000 On 2013-03-10 00:39, Steve Kargl wrote: ... > If you have a clang built FreeBSD-current, then it is no > longer possible to *bootstrap* gcc-4.6.x, gcc-4.7.x, nor > the upcoming gcc-4.8.0. AFAICT, the problem is related > to /usr/bin/cpp. I haven't tried earlier versions of > gcc. I have built the lang/gcc47 and lang/gcc48 ports just now, and they compiled without any issues. What is the exact error you have been getting? I think there must be a common problem you and Oliver have in your build environment, most likely non-default CFLAGS. What happens if you remove make.conf and src.conf, do the gcc ports then build successfully? From owner-freebsd-current@FreeBSD.ORG Mon Mar 11 10:57:50 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id C49CA327; Mon, 11 Mar 2013 10:57:50 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) by mx1.freebsd.org (Postfix) with ESMTP id 708BD6D6; Mon, 11 Mar 2013 10:57:50 +0000 (UTC) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost1.zedat.fu-berlin.de (Exim 4.80.1) with esmtp (envelope-from ) id <1UF0QO-000Fv1-I4>; Mon, 11 Mar 2013 11:57:48 +0100 Received: from e178007196.adsl.alicedsl.de ([85.178.7.196] helo=munin.geoinf.fu-berlin.de) by inpost2.zedat.fu-berlin.de (Exim 4.80.1) with esmtpsa (envelope-from ) id <1UF0QO-001LEB-En>; Mon, 11 Mar 2013 11:57:48 +0100 Message-ID: <513DB8ED.2090306@zedat.fu-berlin.de> Date: Mon, 11 Mar 2013 11:58:53 +0100 From: "Hartmann, O." Organization: FU Berlin User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130309 Thunderbird/17.0.4 MIME-Version: 1.0 To: Dimitry Andric Subject: Re: CURRENT: lang/gcc fails to build on CURRENT with error: configure: error: no usable dependency style found References: <513B56E8.2060702@zedat.fu-berlin.de> <8F5265A6-396A-426F-A3F8-EFD44D167313@FreeBSD.org> <20130309233930.GA95285@troutmask.apl.washington.edu> <513DAF4F.50602@FreeBSD.org> In-Reply-To: <513DAF4F.50602@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Originating-IP: 85.178.7.196 Cc: FreeBSD Current , freebsd-ports@freebsd.org, Steve Kargl X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Mar 2013 10:57:50 -0000 Am 03/11/13 11:17, schrieb Dimitry Andric: > On 2013-03-10 00:39, Steve Kargl wrote: > ... >> If you have a clang built FreeBSD-current, then it is no >> longer possible to *bootstrap* gcc-4.6.x, gcc-4.7.x, nor >> the upcoming gcc-4.8.0. AFAICT, the problem is related >> to /usr/bin/cpp. I haven't tried earlier versions of >> gcc. > > I have built the lang/gcc47 and lang/gcc48 ports just now, and they > compiled without any issues. What is the exact error you have been > getting? > > I think there must be a common problem you and Oliver have in your build > environment, most likely non-default CFLAGS. What happens if you remove > make.conf and src.conf, do the gcc ports then build successfully? I have build port lang/gcc and lang/gcc46 recently on another box running the same configuration files like the boxes which fail (/etc/make.conf and /etc/src.conf). When removing /etc/make.conf and /etc/src.conf as requested, first thing I realize is that perl 5.14 wants to be installed - while I use throughout all systems perl 5.16. Having the default /etc/make.conf with only the PERL specific adaption PER_VERSION=5.16.2 gives a quite short journey into compiling lang/gcc with the following error: cc -c -DHAVE_CONFIG_H -O2 -pipe -I/usr/local/include -fno-strict-aliasing -I. -I.././../gcc-4.6.3/libiberty/../include -W -Wall -Wwrite-strings -Wc++-compat -Wstrict-prototypes -pedantic .././../gcc-4.6.3/libiberty/strverscmp.c -o strverscmp.o rm -f ./libiberty.a pic/./libiberty.a /usr/local/bin/ar rc ./libiberty.a \ ./regex.o ./cplus-dem.o ./cp-demangle.o ./md5.o ./sha1.o ./alloca.o ./argv.o ./choose-temp.o ./concat.o ./cp-demint.o ./crc32.o ./dyn-string.o ./fdmatch.o ./fibheap.o ./filename_cmp.o ./floatformat.o ./fnmatch.o ./fopen_unlocked.o ./getopt.o ./getopt1.o ./getpwd.o ./getruntime.o ./hashtab.o ./hex.o ./lbasename.o ./lrealpath.o ./make-relative-prefix.o ./make-temp-file.o ./objalloc.o ./obstack.o ./partition.o ./pexecute.o ./physmem.o ./pex-common.o ./pex-one.o ./pex-unix.o ./safe-ctype.o ./simple-object.o ./simple-object-coff.o ./simple-object-elf.o ./simple-object-mach-o.o ./sort.o ./spaces.o ./splay-tree.o ./strerror.o ./strsignal.o ./unlink-if-ordinary.o ./xatexit.o ./xexit.o ./xmalloc.o ./xmemdup.o ./xstrdup.o ./xstrerror.o ./xstrndup.o ./mempcpy.o ./strverscmp.o /usr/local/bin/ranlib ./libiberty.a if [ x"-fpic" != x ]; then \ cd pic; \ /usr/local/bin/ar rc ./libiberty.a \ ./regex.o ./cplus-dem.o ./cp-demangle.o ./md5.o ./sha1.o ./alloca.o ./argv.o ./choose-temp.o ./concat.o ./cp-demint.o ./crc32.o ./dyn-string.o ./fdmatch.o ./fibheap.o ./filename_cmp.o ./floatformat.o ./fnmatch.o ./fopen_unlocked.o ./getopt.o ./getopt1.o ./getpwd.o ./getruntime.o ./hashtab.o ./hex.o ./lbasename.o ./lrealpath.o ./make-relative-prefix.o ./make-temp-file.o ./objalloc.o ./obstack.o ./partition.o ./pexecute.o ./physmem.o ./pex-common.o ./pex-one.o ./pex-unix.o ./safe-ctype.o ./simple-object.o ./simple-object-coff.o ./simple-object-elf.o ./simple-object-mach-o.o ./sort.o ./spaces.o ./splay-tree.o ./strerror.o ./strsignal.o ./unlink-if-ordinary.o ./xatexit.o ./xexit.o ./xmalloc.o ./xmemdup.o ./xstrdup.o ./xstrerror.o ./xstrndup.o ./mempcpy.o ./strverscmp.o; \ /usr/local/bin/ranlib ./libiberty.a; \ cd ..; \ else true; fi gmake[2]: Leaving directory `/usr/ports/lang/gcc/work/build/libiberty' gmake[1]: Leaving directory `/usr/ports/lang/gcc/work/build' gmake: *** [all] Error 2 *** [do-build] Error code 1 Stop in /usr/ports/lang/gcc. *** [build] Error code 1 From owner-freebsd-current@FreeBSD.ORG Mon Mar 11 11:04:00 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 646E6816 for ; Mon, 11 Mar 2013 11:04:00 +0000 (UTC) (envelope-from clbuisson@orange.fr) Received: from smtp.smtpout.orange.fr (smtp01.smtpout.orange.fr [80.12.242.123]) by mx1.freebsd.org (Postfix) with ESMTP id EC902732 for ; Mon, 11 Mar 2013 11:03:59 +0000 (UTC) Received: from localhost ([92.136.17.114]) by mwinf5d48 with ME id AB3q1l0052Tfxgk03B3q94; Mon, 11 Mar 2013 12:03:51 +0100 Message-ID: <513DBA15.6010505@orange.fr> Date: Mon, 11 Mar 2013 12:03:49 +0100 From: Claude Buisson User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:10.0.12) Gecko/20130109 Thunderbird/10.0.12 MIME-Version: 1.0 To: Dimitry Andric Subject: Re: CURRENT: lang/gcc fails to build on CURRENT with error: configure: error: no usable dependency style found References: <513B56E8.2060702@zedat.fu-berlin.de> <8F5265A6-396A-426F-A3F8-EFD44D167313@FreeBSD.org> <20130309233930.GA95285@troutmask.apl.washington.edu> <513DAF4F.50602@FreeBSD.org> In-Reply-To: <513DAF4F.50602@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD Current , "Hartmann, O." , freebsd-ports@freebsd.org, Steve Kargl X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Mar 2013 11:04:00 -0000 On 03/11/2013 11:17, Dimitry Andric wrote: > On 2013-03-10 00:39, Steve Kargl wrote: > ... >> If you have a clang built FreeBSD-current, then it is no >> longer possible to *bootstrap* gcc-4.6.x, gcc-4.7.x, nor >> the upcoming gcc-4.8.0. AFAICT, the problem is related >> to /usr/bin/cpp. I haven't tried earlier versions of >> gcc. > > I have built the lang/gcc47 and lang/gcc48 ports just now, and they > compiled without any issues. What is the exact error you have been > getting? > > I think there must be a common problem you and Oliver have in your build > environment, most likely non-default CFLAGS. What happens if you remove > make.conf and src.conf, do the gcc ports then build successfully? > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > FWIW, Yesterday, I built lang/gcc on a 10.0-CURRENT amd64 svn 247236, WITH_CLANG_IS_CC, and got the same error than the OP. NO non-default CFLAGS. The build succeeded with USE_GCC=any I tried to restore the bootstrap phase by partially reverting r302041, and the build errored with clang AND with the base gcc, at another place (some double definitions building libcpp). Claude Buisson From owner-freebsd-current@FreeBSD.ORG Mon Mar 11 11:00:45 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 2C6BD4D9; Mon, 11 Mar 2013 11:00:45 +0000 (UTC) (envelope-from zeising@daemonic.se) Received: from mail.lysator.liu.se (mail.lysator.liu.se [IPv6:2001:6b0:17:f0a0::3]) by mx1.freebsd.org (Postfix) with ESMTP id AF1D76FE; Mon, 11 Mar 2013 11:00:42 +0000 (UTC) Received: from mail.lysator.liu.se (localhost [127.0.0.1]) by mail.lysator.liu.se (Postfix) with ESMTP id 13E4640008; Mon, 11 Mar 2013 12:00:42 +0100 (CET) Received: by mail.lysator.liu.se (Postfix, from userid 1004) id 0952C40007; Mon, 11 Mar 2013 12:00:42 +0100 (CET) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on bernadotte.lysator.liu.se X-Spam-Level: X-Spam-Status: No, score=0.0 required=5.0 tests=AWL autolearn=disabled version=3.3.1 X-Spam-Score: 0.0 Received: from mx.daemonic.se (mx.daemonic.se [IPv6:2001:470:dca9:0:1::3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.lysator.liu.se (Postfix) with ESMTPSA id 2EC8A40003; Mon, 11 Mar 2013 12:00:41 +0100 (CET) Received: from mailscanner.daemonic.se (mailscanner.daemonic.se [IPv6:2001:470:dca9:0:1::6]) by mx.daemonic.se (Postfix) with ESMTPS id 3ZPbvT6zdPz8hVn; Mon, 11 Mar 2013 12:00:37 +0100 (CET) X-Virus-Scanned: amavisd-new at daemonic.se Received: from mx.daemonic.se ([10.1.0.3]) (using TLS with cipher CAMELLIA256-SHA) by mailscanner.daemonic.se (mailscanner.daemonic.se [10.1.0.6]) (amavisd-new, port 10025) with ESMTPS id XLzt89l4R6_c; Mon, 11 Mar 2013 12:00:35 +0100 (CET) Received: from mail.daemonic.se (mail.daemonic.se [10.1.0.4]) by mx.daemonic.se (Postfix) with ESMTPS id 3ZPbvR36cSz8hVm; Mon, 11 Mar 2013 12:00:35 +0100 (CET) Received: from [IPv6:2001:470:dca9:1::3] (celes.daemonic.se [IPv6:2001:470:dca9:1::3]) by mail.daemonic.se (Postfix) with ESMTPSA id 3ZPbvP207Tz9Ctq; Mon, 11 Mar 2013 12:00:33 +0100 (CET) Message-ID: <513DB954.9080205@daemonic.se> Date: Mon, 11 Mar 2013 12:00:36 +0100 From: Niclas Zeising User-Agent: Mutt/1.5.21 MIME-Version: 1.0 To: "Hartmann, O." Subject: Re: CURRENT: lang/gcc fails to build on CURRENT with error: configure: error: no usable dependency style found References: <513B56E8.2060702@zedat.fu-berlin.de> <8F5265A6-396A-426F-A3F8-EFD44D167313@FreeBSD.org> <20130309233930.GA95285@troutmask.apl.washington.edu> <513DAF4F.50602@FreeBSD.org> <513DB8ED.2090306@zedat.fu-berlin.de> In-Reply-To: <513DB8ED.2090306@zedat.fu-berlin.de> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP X-Mailman-Approved-At: Mon, 11 Mar 2013 11:27:44 +0000 Cc: FreeBSD Current , Dimitry Andric , Steve Kargl , freebsd-ports@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Mar 2013 11:00:45 -0000 On 2013-03-11 11:58, Hartmann, O. wrote: > Am 03/11/13 11:17, schrieb Dimitry Andric: >> On 2013-03-10 00:39, Steve Kargl wrote: >> ... >>> If you have a clang built FreeBSD-current, then it is no >>> longer possible to *bootstrap* gcc-4.6.x, gcc-4.7.x, nor >>> the upcoming gcc-4.8.0. AFAICT, the problem is related >>> to /usr/bin/cpp. I haven't tried earlier versions of >>> gcc. >> >> I have built the lang/gcc47 and lang/gcc48 ports just now, and they >> compiled without any issues. What is the exact error you have been >> getting? >> >> I think there must be a common problem you and Oliver have in your build >> environment, most likely non-default CFLAGS. What happens if you remove >> make.conf and src.conf, do the gcc ports then build successfully? > > > > I have build port lang/gcc and lang/gcc46 recently on another box > running the same configuration files like the boxes which fail > (/etc/make.conf and /etc/src.conf). > > When removing /etc/make.conf and /etc/src.conf as requested, first thing > I realize is that perl 5.14 wants to be installed - while I use > throughout all systems perl 5.16. > > Having the default /etc/make.conf with only the PERL specific adaption > > PER_VERSION=5.16.2 > > gives a quite short journey into compiling lang/gcc with the following > error: > > cc -c -DHAVE_CONFIG_H -O2 -pipe -I/usr/local/include > -fno-strict-aliasing -I. -I.././../gcc-4.6.3/libiberty/../include -W > -Wall -Wwrite-strings -Wc++-compat -Wstrict-prototypes -pedantic > .././../gcc-4.6.3/libiberty/strverscmp.c -o strverscmp.o > rm -f ./libiberty.a pic/./libiberty.a > /usr/local/bin/ar rc ./libiberty.a \ > ./regex.o ./cplus-dem.o ./cp-demangle.o ./md5.o ./sha1.o ./alloca.o > ./argv.o ./choose-temp.o ./concat.o ./cp-demint.o ./crc32.o > ./dyn-string.o ./fdmatch.o ./fibheap.o ./filename_cmp.o ./floatformat.o > ./fnmatch.o ./fopen_unlocked.o ./getopt.o ./getopt1.o ./getpwd.o > ./getruntime.o ./hashtab.o ./hex.o ./lbasename.o ./lrealpath.o > ./make-relative-prefix.o ./make-temp-file.o ./objalloc.o ./obstack.o > ./partition.o ./pexecute.o ./physmem.o ./pex-common.o ./pex-one.o > ./pex-unix.o ./safe-ctype.o ./simple-object.o ./simple-object-coff.o > ./simple-object-elf.o ./simple-object-mach-o.o ./sort.o ./spaces.o > ./splay-tree.o ./strerror.o ./strsignal.o ./unlink-if-ordinary.o > ./xatexit.o ./xexit.o ./xmalloc.o ./xmemdup.o ./xstrdup.o ./xstrerror.o > ./xstrndup.o ./mempcpy.o ./strverscmp.o > /usr/local/bin/ranlib ./libiberty.a > if [ x"-fpic" != x ]; then \ > cd pic; \ > /usr/local/bin/ar rc ./libiberty.a \ > ./regex.o ./cplus-dem.o ./cp-demangle.o ./md5.o ./sha1.o ./alloca.o > ./argv.o ./choose-temp.o ./concat.o ./cp-demint.o ./crc32.o > ./dyn-string.o ./fdmatch.o ./fibheap.o ./filename_cmp.o ./floatformat.o > ./fnmatch.o ./fopen_unlocked.o ./getopt.o ./getopt1.o ./getpwd.o > ./getruntime.o ./hashtab.o ./hex.o ./lbasename.o ./lrealpath.o > ./make-relative-prefix.o ./make-temp-file.o ./objalloc.o ./obstack.o > ./partition.o ./pexecute.o ./physmem.o ./pex-common.o ./pex-one.o > ./pex-unix.o ./safe-ctype.o ./simple-object.o ./simple-object-coff.o > ./simple-object-elf.o ./simple-object-mach-o.o ./sort.o ./spaces.o > ./splay-tree.o ./strerror.o ./strsignal.o ./unlink-if-ordinary.o > ./xatexit.o ./xexit.o ./xmalloc.o ./xmemdup.o ./xstrdup.o ./xstrerror.o > ./xstrndup.o ./mempcpy.o ./strverscmp.o; \ > /usr/local/bin/ranlib ./libiberty.a; \ > cd ..; \ > else true; fi > gmake[2]: Leaving directory `/usr/ports/lang/gcc/work/build/libiberty' > gmake[1]: Leaving directory `/usr/ports/lang/gcc/work/build' > gmake: *** [all] Error 2 > *** [do-build] Error code 1 > > Stop in /usr/ports/lang/gcc. > *** [build] Error code 1 Do you, by any chance, use BSD grep? Regards! -- From owner-freebsd-current@FreeBSD.ORG Mon Mar 11 11:51:23 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 50EC1FA; Mon, 11 Mar 2013 11:51:23 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) by mx1.freebsd.org (Postfix) with ESMTP id 07488B38; Mon, 11 Mar 2013 11:51:22 +0000 (UTC) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost1.zedat.fu-berlin.de (Exim 4.80.1) with esmtp (envelope-from ) id <1UF1GD-000YTS-UB>; Mon, 11 Mar 2013 12:51:21 +0100 Received: from e178007196.adsl.alicedsl.de ([85.178.7.196] helo=[192.168.0.128]) by inpost2.zedat.fu-berlin.de (Exim 4.80.1) with esmtpsa (envelope-from ) id <1UF1GD-001Q6q-PH>; Mon, 11 Mar 2013 12:51:21 +0100 Subject: Re: CURRENT: lang/gcc fails to build on CURRENT with error: configure: error: no usable dependency style found From: "O. Hartmann" To: Niclas Zeising In-Reply-To: <513DB954.9080205@daemonic.se> References: <513B56E8.2060702@zedat.fu-berlin.de> <8F5265A6-396A-426F-A3F8-EFD44D167313@FreeBSD.org> <20130309233930.GA95285@troutmask.apl.washington.edu> <513DAF4F.50602@FreeBSD.org> <513DB8ED.2090306@zedat.fu-berlin.de> <513DB954.9080205@daemonic.se> Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-0AsZaMsZZrgSMtcrJ3+9" Organization: FU Berlin Date: Mon, 11 Mar 2013 12:51:21 +0100 Message-ID: <1363002681.48204.1.camel@thor.walstatt.dyndns.org> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port X-Originating-IP: 85.178.7.196 Cc: FreeBSD Current , Dimitry Andric , freebsd-ports@freebsd.org, Steve Kargl X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Mar 2013 11:51:23 -0000 --=-0AsZaMsZZrgSMtcrJ3+9 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable On Mon, 2013-03-11 at 12:00 +0100, Niclas Zeising wrote: > On 2013-03-11 11:58, Hartmann, O. wrote: > > Am 03/11/13 11:17, schrieb Dimitry Andric: > >> On 2013-03-10 00:39, Steve Kargl wrote: > >> ... > >>> If you have a clang built FreeBSD-current, then it is no > >>> longer possible to *bootstrap* gcc-4.6.x, gcc-4.7.x, nor > >>> the upcoming gcc-4.8.0. AFAICT, the problem is related > >>> to /usr/bin/cpp. I haven't tried earlier versions of > >>> gcc. > >> > >> I have built the lang/gcc47 and lang/gcc48 ports just now, and they > >> compiled without any issues. What is the exact error you have been > >> getting? > >> > >> I think there must be a common problem you and Oliver have in your bui= ld > >> environment, most likely non-default CFLAGS. What happens if you remo= ve > >> make.conf and src.conf, do the gcc ports then build successfully? > >=20 > >=20 > >=20 > > I have build port lang/gcc and lang/gcc46 recently on another box > > running the same configuration files like the boxes which fail > > (/etc/make.conf and /etc/src.conf). > >=20 > > When removing /etc/make.conf and /etc/src.conf as requested, first thin= g > > I realize is that perl 5.14 wants to be installed - while I use > > throughout all systems perl 5.16. > >=20 > > Having the default /etc/make.conf with only the PERL specific adaption > >=20 > > PER_VERSION=3D5.16.2 > >=20 > > gives a quite short journey into compiling lang/gcc with the following > > error: > >=20 > > cc -c -DHAVE_CONFIG_H -O2 -pipe -I/usr/local/include > > -fno-strict-aliasing -I. -I.././../gcc-4.6.3/libiberty/../include -W > > -Wall -Wwrite-strings -Wc++-compat -Wstrict-prototypes -pedantic > > .././../gcc-4.6.3/libiberty/strverscmp.c -o strverscmp.o > > rm -f ./libiberty.a pic/./libiberty.a > > /usr/local/bin/ar rc ./libiberty.a \ > > ./regex.o ./cplus-dem.o ./cp-demangle.o ./md5.o ./sha1.o ./alloca.o > > ./argv.o ./choose-temp.o ./concat.o ./cp-demint.o ./crc32.o > > ./dyn-string.o ./fdmatch.o ./fibheap.o ./filename_cmp.o ./floatformat.o > > ./fnmatch.o ./fopen_unlocked.o ./getopt.o ./getopt1.o ./getpwd.o > > ./getruntime.o ./hashtab.o ./hex.o ./lbasename.o ./lrealpath.o > > ./make-relative-prefix.o ./make-temp-file.o ./objalloc.o ./obstack.o > > ./partition.o ./pexecute.o ./physmem.o ./pex-common.o ./pex-one.o > > ./pex-unix.o ./safe-ctype.o ./simple-object.o ./simple-object-coff.o > > ./simple-object-elf.o ./simple-object-mach-o.o ./sort.o ./spaces.o > > ./splay-tree.o ./strerror.o ./strsignal.o ./unlink-if-ordinary.o > > ./xatexit.o ./xexit.o ./xmalloc.o ./xmemdup.o ./xstrdup.o ./xstrerror.o > > ./xstrndup.o ./mempcpy.o ./strverscmp.o > > /usr/local/bin/ranlib ./libiberty.a > > if [ x"-fpic" !=3D x ]; then \ > > cd pic; \ > > /usr/local/bin/ar rc ./libiberty.a \ > > ./regex.o ./cplus-dem.o ./cp-demangle.o ./md5.o ./sha1.o ./alloca.o > > ./argv.o ./choose-temp.o ./concat.o ./cp-demint.o ./crc32.o > > ./dyn-string.o ./fdmatch.o ./fibheap.o ./filename_cmp.o ./floatformat.o > > ./fnmatch.o ./fopen_unlocked.o ./getopt.o ./getopt1.o ./getpwd.o > > ./getruntime.o ./hashtab.o ./hex.o ./lbasename.o ./lrealpath.o > > ./make-relative-prefix.o ./make-temp-file.o ./objalloc.o ./obstack.o > > ./partition.o ./pexecute.o ./physmem.o ./pex-common.o ./pex-one.o > > ./pex-unix.o ./safe-ctype.o ./simple-object.o ./simple-object-coff.o > > ./simple-object-elf.o ./simple-object-mach-o.o ./sort.o ./spaces.o > > ./splay-tree.o ./strerror.o ./strsignal.o ./unlink-if-ordinary.o > > ./xatexit.o ./xexit.o ./xmalloc.o ./xmemdup.o ./xstrdup.o ./xstrerror.o > > ./xstrndup.o ./mempcpy.o ./strverscmp.o; \ > > /usr/local/bin/ranlib ./libiberty.a; \ > > cd ..; \ > > else true; fi > > gmake[2]: Leaving directory `/usr/ports/lang/gcc/work/build/libiberty' > > gmake[1]: Leaving directory `/usr/ports/lang/gcc/work/build' > > gmake: *** [all] Error 2 > > *** [do-build] Error code 1 > >=20 > > Stop in /usr/ports/lang/gcc. > > *** [build] Error code 1 >=20 > Do you, by any chance, use BSD grep? > Regards! Yes, I do. But I use it on ALL systems, even on that box, which is compiling lang/gcc. But that specific box is Ivy-Bridge architecture, the others are all C2D (if, and only if the tuning of the compiler CLANG is miscompiling code affecting this issue ...). Oliver --=-0AsZaMsZZrgSMtcrJ3+9 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iQEcBAABAgAGBQJRPcU5AAoJEOgBcD7A/5N8jqoIAKdtvhIi1SxF7YKQbKfNJeq7 dkAk8LSJ02ZbXgxF04uO16v5ZkJgpRF2JMFu0fWkCVWbtaUscRmnb9BVJ+AVlWI9 lW64vi7xWbV6LuKyAqgdcgaqeDagzL+dpTgWb7g5gxPbE9S+rO00yVEwKOD2FRip V+d9hpschbav+uZ7GYN0Ssy2Fop5X07oU0MbWOLv0cxesx5cNTln/ck9p3KTE/RI md53uL87yWtJaCBsuGz8k6k6Dfzen3+xQ5YBr4TK83KfPtDcwmt4Pa1NferWK2uz AqJdhLVB55OIWqjp6fAFbkaRTVK+7X3ffao8z1RalRAntdOesutikXeqQAsDv3M= =f8IB -----END PGP SIGNATURE----- --=-0AsZaMsZZrgSMtcrJ3+9-- From owner-freebsd-current@FreeBSD.ORG Mon Mar 11 12:55:52 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id D76C8427 for ; Mon, 11 Mar 2013 12:55:52 +0000 (UTC) (envelope-from clbuisson@orange.fr) Received: from smtp.smtpout.orange.fr (smtp07.smtpout.orange.fr [80.12.242.129]) by mx1.freebsd.org (Postfix) with ESMTP id 529ABF32 for ; Mon, 11 Mar 2013 12:55:51 +0000 (UTC) Received: from localhost ([92.136.17.114]) by mwinf5d30 with ME id ACvn1l00K2Tfxgk03Cvomz; Mon, 11 Mar 2013 13:55:50 +0100 Message-ID: <513DD452.5040403@orange.fr> Date: Mon, 11 Mar 2013 13:55:46 +0100 From: Claude Buisson User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:10.0.12) Gecko/20130109 Thunderbird/10.0.12 MIME-Version: 1.0 To: Niclas Zeising Subject: Re: CURRENT: lang/gcc fails to build on CURRENT with error: configure: error: no usable dependency style found References: <513B56E8.2060702@zedat.fu-berlin.de> <8F5265A6-396A-426F-A3F8-EFD44D167313@FreeBSD.org> <20130309233930.GA95285@troutmask.apl.washington.edu> <513DAF4F.50602@FreeBSD.org> <513DB8ED.2090306@zedat.fu-berlin.de> <513DB954.9080205@daemonic.se> In-Reply-To: <513DB954.9080205@daemonic.se> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Dimitry Andric , FreeBSD Current , "Hartmann, O." , freebsd-ports@freebsd.org, Steve Kargl X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Mar 2013 12:55:52 -0000 On 03/11/2013 12:00, Niclas Zeising wrote: > On 2013-03-11 11:58, Hartmann, O. wrote: >> Am 03/11/13 11:17, schrieb Dimitry Andric: >>> On 2013-03-10 00:39, Steve Kargl wrote: >>> ... >>>> If you have a clang built FreeBSD-current, then it is no >>>> longer possible to *bootstrap* gcc-4.6.x, gcc-4.7.x, nor >>>> the upcoming gcc-4.8.0. AFAICT, the problem is related >>>> to /usr/bin/cpp. I haven't tried earlier versions of >>>> gcc. >>> >>> I have built the lang/gcc47 and lang/gcc48 ports just now, and they >>> compiled without any issues. What is the exact error you have been >>> getting? >>> >>> I think there must be a common problem you and Oliver have in your build >>> environment, most likely non-default CFLAGS. What happens if you remove >>> make.conf and src.conf, do the gcc ports then build successfully? >> >> >> >> I have build port lang/gcc and lang/gcc46 recently on another box >> running the same configuration files like the boxes which fail >> (/etc/make.conf and /etc/src.conf). >> >> When removing /etc/make.conf and /etc/src.conf as requested, first thing >> I realize is that perl 5.14 wants to be installed - while I use >> throughout all systems perl 5.16. >> >> Having the default /etc/make.conf with only the PERL specific adaption >> >> PER_VERSION=5.16.2 >> >> gives a quite short journey into compiling lang/gcc with the following >> error: >> >> cc -c -DHAVE_CONFIG_H -O2 -pipe -I/usr/local/include >> -fno-strict-aliasing -I. -I.././../gcc-4.6.3/libiberty/../include -W >> -Wall -Wwrite-strings -Wc++-compat -Wstrict-prototypes -pedantic >> .././../gcc-4.6.3/libiberty/strverscmp.c -o strverscmp.o >> rm -f ./libiberty.a pic/./libiberty.a >> /usr/local/bin/ar rc ./libiberty.a \ >> ./regex.o ./cplus-dem.o ./cp-demangle.o ./md5.o ./sha1.o ./alloca.o >> ./argv.o ./choose-temp.o ./concat.o ./cp-demint.o ./crc32.o >> ./dyn-string.o ./fdmatch.o ./fibheap.o ./filename_cmp.o ./floatformat.o >> ./fnmatch.o ./fopen_unlocked.o ./getopt.o ./getopt1.o ./getpwd.o >> ./getruntime.o ./hashtab.o ./hex.o ./lbasename.o ./lrealpath.o >> ./make-relative-prefix.o ./make-temp-file.o ./objalloc.o ./obstack.o >> ./partition.o ./pexecute.o ./physmem.o ./pex-common.o ./pex-one.o >> ./pex-unix.o ./safe-ctype.o ./simple-object.o ./simple-object-coff.o >> ./simple-object-elf.o ./simple-object-mach-o.o ./sort.o ./spaces.o >> ./splay-tree.o ./strerror.o ./strsignal.o ./unlink-if-ordinary.o >> ./xatexit.o ./xexit.o ./xmalloc.o ./xmemdup.o ./xstrdup.o ./xstrerror.o >> ./xstrndup.o ./mempcpy.o ./strverscmp.o >> /usr/local/bin/ranlib ./libiberty.a >> if [ x"-fpic" != x ]; then \ >> cd pic; \ >> /usr/local/bin/ar rc ./libiberty.a \ >> ./regex.o ./cplus-dem.o ./cp-demangle.o ./md5.o ./sha1.o ./alloca.o >> ./argv.o ./choose-temp.o ./concat.o ./cp-demint.o ./crc32.o >> ./dyn-string.o ./fdmatch.o ./fibheap.o ./filename_cmp.o ./floatformat.o >> ./fnmatch.o ./fopen_unlocked.o ./getopt.o ./getopt1.o ./getpwd.o >> ./getruntime.o ./hashtab.o ./hex.o ./lbasename.o ./lrealpath.o >> ./make-relative-prefix.o ./make-temp-file.o ./objalloc.o ./obstack.o >> ./partition.o ./pexecute.o ./physmem.o ./pex-common.o ./pex-one.o >> ./pex-unix.o ./safe-ctype.o ./simple-object.o ./simple-object-coff.o >> ./simple-object-elf.o ./simple-object-mach-o.o ./sort.o ./spaces.o >> ./splay-tree.o ./strerror.o ./strsignal.o ./unlink-if-ordinary.o >> ./xatexit.o ./xexit.o ./xmalloc.o ./xmemdup.o ./xstrdup.o ./xstrerror.o >> ./xstrndup.o ./mempcpy.o ./strverscmp.o; \ >> /usr/local/bin/ranlib ./libiberty.a; \ >> cd ..; \ >> else true; fi >> gmake[2]: Leaving directory `/usr/ports/lang/gcc/work/build/libiberty' >> gmake[1]: Leaving directory `/usr/ports/lang/gcc/work/build' >> gmake: *** [all] Error 2 >> *** [do-build] Error code 1 >> >> Stop in /usr/ports/lang/gcc. >> *** [build] Error code 1 > > Do you, by any chance, use BSD grep? > Regards! TILT !! I remade my world (same source, but WITH_BSD_GREP (and WITH_BSD_PATCH) commented out in src.conf), and now lang/gcc can be built/installed without error with clang. BTW, I already had to force the use of gnugrep in some scripts, because bsdgrep do not support constructs like: ...| grep -f - ... Claude Buisson From owner-freebsd-current@FreeBSD.ORG Mon Mar 11 13:13:24 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 620CC30A; Mon, 11 Mar 2013 13:13:24 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.21]) by mx1.freebsd.org (Postfix) with ESMTP id 4333C106; Mon, 11 Mar 2013 13:13:24 +0000 (UTC) Received: from troutmask.apl.washington.edu (localhost.apl.washington.edu [127.0.0.1]) by troutmask.apl.washington.edu (8.14.6/8.14.6) with ESMTP id r2BDDIpc057544; Mon, 11 Mar 2013 06:13:18 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.14.6/8.14.6/Submit) id r2BDDIJp057543; Mon, 11 Mar 2013 06:13:18 -0700 (PDT) (envelope-from sgk) Date: Mon, 11 Mar 2013 06:13:18 -0700 From: Steve Kargl To: Dimitry Andric Subject: Re: CURRENT: lang/gcc fails to build on CURRENT with error: configure: error: no usable dependency style found Message-ID: <20130311131318.GA57506@troutmask.apl.washington.edu> References: <513B56E8.2060702@zedat.fu-berlin.de> <8F5265A6-396A-426F-A3F8-EFD44D167313@FreeBSD.org> <20130309233930.GA95285@troutmask.apl.washington.edu> <513DAF4F.50602@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <513DAF4F.50602@FreeBSD.org> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: FreeBSD Current , "Hartmann, O." , freebsd-ports@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Mar 2013 13:13:24 -0000 On Mon, Mar 11, 2013 at 11:17:51AM +0100, Dimitry Andric wrote: > On 2013-03-10 00:39, Steve Kargl wrote: > ... > > If you have a clang built FreeBSD-current, then it is no > > longer possible to *bootstrap* gcc-4.6.x, gcc-4.7.x, nor > > the upcoming gcc-4.8.0. AFAICT, the problem is related > > to /usr/bin/cpp. I haven't tried earlier versions of > > gcc. > > I have built the lang/gcc47 and lang/gcc48 ports just now, and they > compiled without any issues. What is the exact error you have been > getting? Note, I said explicitly said *bootstrap*. I can build 4.6, 4.7, and 4.8. I cannot *bootstrap* these compilers. The entire build log from 'gmake bootstrap |& tee gcc-4.8.0.log' is here http://troutmask.apl.washington.edu/gcc-4.8.0.log The last few lines are checking whether /home/sgk/gcc/obj4x/./prev-gcc/xgcc -B/home/sgk/gcc/obj4x/./prev-gcc/ -B/home/sgk/work/4x/x86_64-unknown-freebsd10.0/bin/ -B/home/sgk/work/4x/x86_64-unknown-freebsd10.0/bin/ -B/home/sgk/work/4x/x86_64-unknown-freebsd10.0/lib/ -isystem /home/sgk/work/4x/x86_64-unknown-freebsd10.0/include -isystem /home/sgk/work/4x/x86_64-unknown-freebsd10.0/sys-include supports -fno-rtti... yes checking dependency style of /home/sgk/gcc/obj4x/./prev-gcc/xg++ -B/home/sgk/gcc/obj4x/./prev-gcc/ -B/home/sgk/work/4x/x86_64-unknown-freebsd10.0/bin/ -nostdinc++ -B/home/sgk/gcc/obj4x/prev-x86_64-unknown-freebsd10.0/libstdc++-v3/src/.libs -B/home/sgk/gcc/obj4x/prev-x86_64-unknown-freebsd10.0/libstdc++-v3/libsupc++/.libs -I/home/sgk/gcc/obj4x/prev-x86_64-unknown-freebsd10.0/libstdc++-v3/include/x86_64-unknown-freebsd10.0 -I/home/sgk/gcc/obj4x/prev-x86_64-unknown-freebsd10.0/libstdc++-v3/include -I/home/sgk/gcc/gcc4x/libstdc++-v3/libsupc++ -L/home/sgk/gcc/obj4x/prev-x86_64-unknown-freebsd10.0/libstdc++-v3/src/.libs -L/home/sgk/gcc/obj4x/prev-x86_64-unknown-freebsd10.0/libstdc++-v3/libsupc++/.libs... none configure: error: no usable dependency style found gmake[2]: *** [configure-stage2-libcpp] Error 1 gmake[2]: Leaving directory `/usr/home/sgk/gcc/obj4x' gmake[1]: *** [stage2-bubble] Error 2 gmake[1]: Leaving directory `/usr/home/sgk/gcc/obj4x' gmake: *** [bootstrap] Error 2 > I think there must be a common problem you and Oliver have in your build > environment, most likely non-default CFLAGS. No. Here's my make.conf. KERNCONF=SPEW CPUTYPE?=opteron FFLAGS+= -O2 -pipe -march=native -mtune=native -funroll-loops -ftree-vectorize MALLOC_PRODUCTION="YES" WITHOUT_LIB32="YES" WITHOUT_MODULES="YES" WITHOUT_NLS="YES" WITH_BSD_GREP="YES" WITH_PROFILE="YES" WITH_PKGNG=yes PRINTERDEVICE=ps # # Crap for ports. # DISABLE_MAKE_JOBS="YES" WITH_GHOSTSCRIPT_VER=8 # # added by use.perl 2013-02-19 12:45:06 PERL_VERSION=5.12.4 -- Steve From owner-freebsd-current@FreeBSD.ORG Mon Mar 11 13:16:23 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id BCDCA64E; Mon, 11 Mar 2013 13:16:23 +0000 (UTC) (envelope-from zeising+freebsd@daemonic.se) Received: from mail.lysator.liu.se (mail.lysator.liu.se [IPv6:2001:6b0:17:f0a0::3]) by mx1.freebsd.org (Postfix) with ESMTP id 62A2F14E; Mon, 11 Mar 2013 13:16:23 +0000 (UTC) Received: from mail.lysator.liu.se (localhost [127.0.0.1]) by mail.lysator.liu.se (Postfix) with ESMTP id CD30A40009; Mon, 11 Mar 2013 14:16:21 +0100 (CET) Received: by mail.lysator.liu.se (Postfix, from userid 1004) id C27BF40008; Mon, 11 Mar 2013 14:16:21 +0100 (CET) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on bernadotte.lysator.liu.se X-Spam-Level: X-Spam-Status: No, score=0.0 required=5.0 tests=none autolearn=disabled version=3.3.1 X-Spam-Score: 0.0 Received: from mx.daemonic.se (mx.daemonic.se [IPv6:2001:470:dca9:0:1::3]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.lysator.liu.se (Postfix) with ESMTPSA id D5DD840007; Mon, 11 Mar 2013 14:16:20 +0100 (CET) Received: from mailscanner.daemonic.se (mailscanner.daemonic.se [IPv6:2001:470:dca9:0:1::6]) by mx.daemonic.se (Postfix) with ESMTPS id 3ZPfvy2kDrz8hVn; Mon, 11 Mar 2013 14:16:14 +0100 (CET) X-Virus-Scanned: amavisd-new at daemonic.se Received: from mx.daemonic.se ([10.1.0.3]) (using TLS with cipher CAMELLIA256-SHA) by mailscanner.daemonic.se (mailscanner.daemonic.se [10.1.0.6]) (amavisd-new, port 10025) with ESMTPS id 71OjiJ6T2by4; Mon, 11 Mar 2013 14:16:09 +0100 (CET) Received: from mail.daemonic.se (mail.daemonic.se [IPv6:2001:470:dca9:0:1::4]) by mx.daemonic.se (Postfix) with ESMTPS id 3ZPfvs2srTz8hVm; Mon, 11 Mar 2013 14:16:09 +0100 (CET) Received: from vivi.daemonic.se (vivi.daemonic.se [IPv6:2001:470:dca9:1::4]) by mail.daemonic.se (Postfix) with ESMTPSA id 3ZPfvs08Kcz9Ctq; Mon, 11 Mar 2013 14:16:09 +0100 (CET) Message-ID: <513DD90F.2090700@daemonic.se> Date: Mon, 11 Mar 2013 14:15:59 +0100 From: Niclas Zeising User-Agent: Mutt/1.5.21 MIME-Version: 1.0 To: Steve Kargl Subject: Re: CURRENT: lang/gcc fails to build on CURRENT with error: configure: error: no usable dependency style found References: <513B56E8.2060702@zedat.fu-berlin.de> <8F5265A6-396A-426F-A3F8-EFD44D167313@FreeBSD.org> <20130309233930.GA95285@troutmask.apl.washington.edu> <513DAF4F.50602@FreeBSD.org> <20130311131318.GA57506@troutmask.apl.washington.edu> In-Reply-To: <20130311131318.GA57506@troutmask.apl.washington.edu> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP Cc: "Hartmann, O." , FreeBSD Current , Dimitry Andric , freebsd-ports@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Mar 2013 13:16:23 -0000 On 03/11/13 14:13, Steve Kargl wrote: > On Mon, Mar 11, 2013 at 11:17:51AM +0100, Dimitry Andric wrote: >> On 2013-03-10 00:39, Steve Kargl wrote: >> ... >>> If you have a clang built FreeBSD-current, then it is no >>> longer possible to *bootstrap* gcc-4.6.x, gcc-4.7.x, nor >>> the upcoming gcc-4.8.0. AFAICT, the problem is related >>> to /usr/bin/cpp. I haven't tried earlier versions of >>> gcc. >> >> I have built the lang/gcc47 and lang/gcc48 ports just now, and they >> compiled without any issues. What is the exact error you have been >> getting? > > Note, I said explicitly said *bootstrap*. I can build 4.6, 4.7, > and 4.8. I cannot *bootstrap* these compilers. The entire > build log from 'gmake bootstrap |& tee gcc-4.8.0.log' is > here > > http://troutmask.apl.washington.edu/gcc-4.8.0.log > > The last few lines are > > checking whether /home/sgk/gcc/obj4x/./prev-gcc/xgcc -B/home/sgk/gcc/obj4x/./prev-gcc/ -B/home/sgk/work/4x/x86_64-unknown-freebsd10.0/bin/ -B/home/sgk/work/4x/x86_64-unknown-freebsd10.0/bin/ -B/home/sgk/work/4x/x86_64-unknown-freebsd10.0/lib/ -isystem /home/sgk/work/4x/x86_64-unknown-freebsd10.0/include -isystem /home/sgk/work/4x/x86_64-unknown-freebsd10.0/sys-include supports -fno-rtti... yes > checking dependency style of /home/sgk/gcc/obj4x/./prev-gcc/xg++ -B/home/sgk/gcc/obj4x/./prev-gcc/ -B/home/sgk/work/4x/x86_64-unknown-freebsd10.0/bin/ -nostdinc++ -B/home/sgk/gcc/obj4x/prev-x86_64-unknown-freebsd10.0/libstdc++-v3/src/.libs -B/home/sgk/gcc/obj4x/prev-x86_64-unknown-freebsd10.0/libstdc++-v3/libsupc++/.libs -I/home/sgk/gcc/obj4x/prev-x86_64-unknown-freebsd10.0/libstdc++-v3/include/x86_64-unknown-freebsd10.0 -I/home/sgk/gcc/obj4x/prev-x86_64-unknown-freebsd10.0/libstdc++-v3/include -I/home/sgk/gcc/gcc4x/libstdc++-v3/libsupc++ -L/home/sgk/gcc/obj4x/prev-x86_64-unknown-freebsd10.0/libstdc++-v3/src/.libs -L/home/sgk/gcc/obj4x/prev-x86_64-unknown-freebsd10.0/libstdc++-v3/libsupc++/.libs... none > configure: error: no usable dependency style found > gmake[2]: *** [configure-stage2-libcpp] Error 1 > gmake[2]: Leaving directory `/usr/home/sgk/gcc/obj4x' > gmake[1]: *** [stage2-bubble] Error 2 > gmake[1]: Leaving directory `/usr/home/sgk/gcc/obj4x' > gmake: *** [bootstrap] Error 2 > >> I think there must be a common problem you and Oliver have in your build >> environment, most likely non-default CFLAGS. > > No. Here's my make.conf. > > KERNCONF=SPEW > CPUTYPE?=opteron > FFLAGS+= -O2 -pipe -march=native -mtune=native -funroll-loops -ftree-vectorize > MALLOC_PRODUCTION="YES" > WITHOUT_LIB32="YES" > WITHOUT_MODULES="YES" > WITHOUT_NLS="YES" > WITH_BSD_GREP="YES" > WITH_PROFILE="YES" > WITH_PKGNG=yes > PRINTERDEVICE=ps > # > # Crap for ports. > # > DISABLE_MAKE_JOBS="YES" > WITH_GHOSTSCRIPT_VER=8 > # > # added by use.perl 2013-02-19 12:45:06 > PERL_VERSION=5.12.4 > This is most likely due to a incompatibility between bsd grep and gnu grep. Try to switch to gnu grep, and the problem will most likely go away. Regards! -- Niclas From owner-freebsd-current@FreeBSD.ORG Mon Mar 11 16:29:36 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id C54A1D03; Mon, 11 Mar 2013 16:29:36 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from springbank.echomania.com (andric.com [IPv6:2a03:6000:1008:0:230:48ff:fe51:76b6]) by mx1.freebsd.org (Postfix) with ESMTP id 79015E4B; Mon, 11 Mar 2013 16:29:36 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at springbank.echomania.com Received: from [192.168.0.6] (tensor.andric.com [87.251.56.140]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by springbank.echomania.com (Postfix) with ESMTPSA id 5B379A7078; Mon, 11 Mar 2013 17:29:12 +0100 (CET) Message-ID: <513E0656.7000601@FreeBSD.org> Date: Mon, 11 Mar 2013 17:29:10 +0100 From: Dimitry Andric Organization: The FreeBSD Project User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:20.0) Gecko/20100101 Thunderbird/20.0 MIME-Version: 1.0 To: Niclas Zeising , Steve Kargl Subject: Re: CURRENT: lang/gcc fails to build on CURRENT with error: configure: error: no usable dependency style found References: <513B56E8.2060702@zedat.fu-berlin.de> <8F5265A6-396A-426F-A3F8-EFD44D167313@FreeBSD.org> <20130309233930.GA95285@troutmask.apl.washington.edu> <513DAF4F.50602@FreeBSD.org> <20130311131318.GA57506@troutmask.apl.washington.edu> <513DD90F.2090700@daemonic.se> In-Reply-To: <513DD90F.2090700@daemonic.se> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD Current , "Hartmann, O." , =?ISO-8859-1?Q?G=E1bor_K=F6vesd=E1n?= , freebsd-ports@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Mar 2013 16:29:36 -0000 On 2013-03-11 14:15, Niclas Zeising wrote: > On 03/11/13 14:13, Steve Kargl wrote: ... >> No. Here's my make.conf. >> >> KERNCONF=SPEW >> CPUTYPE?=opteron >> FFLAGS+= -O2 -pipe -march=native -mtune=native -funroll-loops -ftree-vectorize >> MALLOC_PRODUCTION="YES" >> WITHOUT_LIB32="YES" >> WITHOUT_MODULES="YES" >> WITHOUT_NLS="YES" >> WITH_BSD_GREP="YES" >> WITH_PROFILE="YES" >> WITH_PKGNG=yes >> PRINTERDEVICE=ps >> # >> # Crap for ports. >> # >> DISABLE_MAKE_JOBS="YES" >> WITH_GHOSTSCRIPT_VER=8 >> # >> # added by use.perl 2013-02-19 12:45:06 >> PERL_VERSION=5.12.4 >> > > This is most likely due to a incompatibility between bsd grep and gnu > grep. Try to switch to gnu grep, and the problem will most likely go away. Yes, this is definitely due to a BSD grep bug. The depcomp tests create a file sub/conftest.Po, containing: ======================================================================== sub/conftest.o: sub/conftest.c sub/conftst1.h sub/conftst2.h \ sub/conftst3.h sub/conftst4.h sub/conftst5.h sub/conftst6.h sub/conftst1.h: sub/conftst2.h: sub/conftst3.h: sub/conftst4.h: sub/conftst5.h: sub/conftst6.h: ======================================================================== Then it runs "grep sub/conftest.o sub/conftest.Po", which fails with BSD grep, and succeeds with GNU grep. BSD grep does something very strange here: $ echo 'foo.bar' | grep foo.bar foo.bar $ echo 'foo.barx' | grep foo.bar foo.barx $ echo 'sub/foo.bar' | grep sub/foo.bar sub/foo.bar $ echo 'sub/foo.barx' | grep sub/foo.bar $ echo $? 1 So why does it not match in the last case? GNU grep works: $ echo 'sub/foo.barx' | gnugrep sub/foo.bar sub/foo.barx From owner-freebsd-current@FreeBSD.ORG Mon Mar 11 16:58:07 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 085F09B0; Mon, 11 Mar 2013 16:58:07 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) by mx1.freebsd.org (Postfix) with ESMTP id B8AFCFCA; Mon, 11 Mar 2013 16:58:06 +0000 (UTC) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost1.zedat.fu-berlin.de (Exim 4.80.1) with esmtp (envelope-from ) id <1UF62x-002P9V-B1>; Mon, 11 Mar 2013 17:57:59 +0100 Received: from e178007196.adsl.alicedsl.de ([85.178.7.196] helo=[192.168.0.128]) by inpost2.zedat.fu-berlin.de (Exim 4.80.1) with esmtpsa (envelope-from ) id <1UF62x-001s7c-5T>; Mon, 11 Mar 2013 17:57:59 +0100 Subject: Re: CURRENT: lang/gcc fails to build on CURRENT with error: configure: error: no usable dependency style found From: "O. Hartmann" To: Dimitry Andric In-Reply-To: <513E0656.7000601@FreeBSD.org> References: <513B56E8.2060702@zedat.fu-berlin.de> <8F5265A6-396A-426F-A3F8-EFD44D167313@FreeBSD.org> <20130309233930.GA95285@troutmask.apl.washington.edu> <513DAF4F.50602@FreeBSD.org> <20130311131318.GA57506@troutmask.apl.washington.edu> <513DD90F.2090700@daemonic.se> <513E0656.7000601@FreeBSD.org> Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-wtJ6LF3otrgdSdsxdIa7" Organization: FU Berlin Date: Mon, 11 Mar 2013 17:57:58 +0100 Message-ID: <1363021078.51002.1.camel@thor.walstatt.dyndns.org> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port X-Originating-IP: 85.178.7.196 Cc: Niclas Zeising , FreeBSD Current , freebsd-ports@freebsd.org, Steve Kargl , =?ISO-8859-1?Q?G=E1bor_K=F6vesd=E1n?= X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Mar 2013 16:58:07 -0000 --=-wtJ6LF3otrgdSdsxdIa7 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable On Mon, 2013-03-11 at 17:29 +0100, Dimitry Andric wrote: > On 2013-03-11 14:15, Niclas Zeising wrote: > > On 03/11/13 14:13, Steve Kargl wrote: > ... > >> No. Here's my make.conf. > >> > >> KERNCONF=3DSPEW > >> CPUTYPE?=3Dopteron > >> FFLAGS+=3D -O2 -pipe -march=3Dnative -mtune=3Dnative -funroll-loops -f= tree-vectorize > >> MALLOC_PRODUCTION=3D"YES" > >> WITHOUT_LIB32=3D"YES" > >> WITHOUT_MODULES=3D"YES" > >> WITHOUT_NLS=3D"YES" > >> WITH_BSD_GREP=3D"YES" > >> WITH_PROFILE=3D"YES" > >> WITH_PKGNG=3Dyes > >> PRINTERDEVICE=3Dps > >> # > >> # Crap for ports. > >> # > >> DISABLE_MAKE_JOBS=3D"YES" > >> WITH_GHOSTSCRIPT_VER=3D8 > >> # > >> # added by use.perl 2013-02-19 12:45:06 > >> PERL_VERSION=3D5.12.4 > >> > > > > This is most likely due to a incompatibility between bsd grep and gnu > > grep. Try to switch to gnu grep, and the problem will most likely go a= way. >=20 > Yes, this is definitely due to a BSD grep bug. The depcomp tests > create a file sub/conftest.Po, containing: >=20 > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > sub/conftest.o: sub/conftest.c sub/conftst1.h sub/conftst2.h \ > sub/conftst3.h sub/conftst4.h sub/conftst5.h sub/conftst6.h >=20 > sub/conftst1.h: >=20 > sub/conftst2.h: >=20 > sub/conftst3.h: >=20 > sub/conftst4.h: >=20 > sub/conftst5.h: >=20 > sub/conftst6.h: > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >=20 > Then it runs "grep sub/conftest.o sub/conftest.Po", which fails with BSD > grep, and succeeds with GNU grep. >=20 > BSD grep does something very strange here: >=20 > $ echo 'foo.bar' | grep foo.bar > foo.bar > $ echo 'foo.barx' | grep foo.bar > foo.barx > $ echo 'sub/foo.bar' | grep sub/foo.bar > sub/foo.bar > $ echo 'sub/foo.barx' | grep sub/foo.bar > $ echo $? > 1 >=20 > So why does it not match in the last case? GNU grep works: >=20 > $ echo 'sub/foo.barx' | gnugrep sub/foo.bar > sub/foo.barx After disabling WITH_BSD_GREP and rebuild of the system, it seems that the machines in question now build lang/gcc. --=-wtJ6LF3otrgdSdsxdIa7 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iQEcBAABAgAGBQJRPg0WAAoJEOgBcD7A/5N8FLUIALEtSvCZEhbbVtHpHGo5Ds0K RoeCyN++Z2MgPIRKoSIrEnoGAJ2D3WM69eIRlp6Ha68w/uUW3TqaVJ5vE24aCUuO X4huHIeNDSj+CCUOYVKLBX90UdYGHrrXyToTnXW+aClsBCJbFo7KIk6ZM4GDvse4 1vCkhRRS9IZQZrKlivZNseSjERg5YUWcvXV+jK5rWJ7KxgGr4mAwMG3Dvdbymthh W11pHcwcHGnew1aXO6Xp6wfeYQnGkBCzMEUcEv045oWDT2U25BlEoL7PWTx1B08o zV7aDMkFwk4/V72ccszqliXCz2nlZi9DNyUiLMORFMi1WSdAuaimLKHojixJ3nY= =gHqj -----END PGP SIGNATURE----- --=-wtJ6LF3otrgdSdsxdIa7-- From owner-freebsd-current@FreeBSD.ORG Mon Mar 11 17:19:49 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 5FFE6310; Mon, 11 Mar 2013 17:19:49 +0000 (UTC) (envelope-from c.kworr@gmail.com) Received: from mail-bk0-x232.google.com (mail-bk0-x232.google.com [IPv6:2a00:1450:4008:c01::232]) by mx1.freebsd.org (Postfix) with ESMTP id 7501E1B2; Mon, 11 Mar 2013 17:19:48 +0000 (UTC) Received: by mail-bk0-f50.google.com with SMTP id jg9so1842920bkc.37 for ; Mon, 11 Mar 2013 10:19:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=ENlSAPJjwgaEUpx4ZNLJvTzo23DzvdhETnbsDYtuMuA=; b=gaUPriBLLAifZ5JspBjCIGJetKlfalwOzOPlJJ6x23gsiq8M6fU1ouuyjBqqqbDLvB mDXKMGPErcwgJaKFN7SpPpld0argp9IG49hUDtskm5mSs0bREHpVofBXHeqLaViZjodY Yta9GHxV3xrl3ZwLY3qYA0Ev60A7V87E60dszzTDbQ72BjQRLVRmA3Fx+nnmpc42/85Q ZfDsXGldHcQjdChMaRDzd1AxLsvtxQthqfCmUiasfgQedQP2EYqSY4vwR+eYBdybD5ef 7o6f1gDaMVDyt7lnbqfuTRUtRx6OnB6Mzm5YyrS9oCTSpVWxB1/flZ5bIh2GNaU3WkgF bszw== X-Received: by 10.205.64.199 with SMTP id xj7mr5015593bkb.76.1363022387437; Mon, 11 Mar 2013 10:19:47 -0700 (PDT) Received: from [192.168.1.129] ([91.196.229.122]) by mx.google.com with ESMTPS id o2sm4370704bkv.3.2013.03.11.10.19.45 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 11 Mar 2013 10:19:46 -0700 (PDT) Message-ID: <513E1230.2020101@gmail.com> Date: Mon, 11 Mar 2013 19:19:44 +0200 From: Volodymyr Kostyrko User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:19.0) Gecko/20100101 Firefox/19.0 SeaMonkey/2.16.1 MIME-Version: 1.0 To: "O. Hartmann" , =?UTF-8?B?R8OhYm9yIEvDtnY=?= =?UTF-8?B?ZXNkw6Fu?= Subject: Re: CURRENT: lang/gcc fails to build on CURRENT with error: configure: error: no usable dependency style found References: <513B56E8.2060702@zedat.fu-berlin.de> <8F5265A6-396A-426F-A3F8-EFD44D167313@FreeBSD.org> <20130309233930.GA95285@troutmask.apl.washington.edu> <513DAF4F.50602@FreeBSD.org> <20130311131318.GA57506@troutmask.apl.washington.edu> <513DD90F.2090700@daemonic.se> <513E0656.7000601@FreeBSD.org> <1363021078.51002.1.camel@thor.walstatt.dyndns.org> In-Reply-To: <1363021078.51002.1.camel@thor.walstatt.dyndns.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Cc: Niclas Zeising , FreeBSD Current , Dimitry Andric , Steve Kargl , freebsd-ports@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Mar 2013 17:19:49 -0000 11.03.2013 18:57, O. Hartmann пишет: > On Mon, 2013-03-11 at 17:29 +0100, Dimitry Andric wrote: >> On 2013-03-11 14:15, Niclas Zeising wrote: >> BSD grep does something very strange here: >> >> $ echo 'foo.bar' | grep foo.bar >> foo.bar >> $ echo 'foo.barx' | grep foo.bar >> foo.barx >> $ echo 'sub/foo.bar' | grep sub/foo.bar >> sub/foo.bar >> $ echo 'sub/foo.barx' | grep sub/foo.bar >> $ echo $? >> 1 >> >> So why does it not match in the last case? GNU grep works: >> >> $ echo 'sub/foo.barx' | gnugrep sub/foo.bar >> sub/foo.barx > > After disabling WITH_BSD_GREP and rebuild of the system, it seems that > the machines in question now build lang/gcc. > > So how about resurrecting http://www.freebsd.org/cgi/query-pr.cgi?pr=bin/167921 ? Looks like BSD_GREP still has some problems with slashes. http://scan.freebsd.your.org/freebsd-head/usr.bin.grep/2013-03-10-amd64/ has some good pointers on where to start. I'm not that familiar with C to dive in. -- Sphinx of black quartz, judge my vow. From owner-freebsd-current@FreeBSD.ORG Mon Mar 11 19:02:18 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 4D13E75C; Mon, 11 Mar 2013 19:02:18 +0000 (UTC) (envelope-from jbeich@tormail.org) Received: from outgoing.tormail.org (outgoing.tormail.org [82.221.96.22]) by mx1.freebsd.org (Postfix) with ESMTP id F12B194C; Mon, 11 Mar 2013 19:02:17 +0000 (UTC) Received: from localhost ([127.0.0.1] helo=internal.tormail.org) by outgoing.tormail.org with esmtp (Exim 4.72) (envelope-from ) id 1UF7z6-0002K1-V1; Mon, 11 Mar 2013 22:02:09 +0300 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=tormail.org; s=tm; h=Message-Id:X-TorMail-User:Content-Type:MIME-Version:References:Date:Subject:Cc:To:From; bh=IqgcCBH5Te78qZSYieo60acor9tGwYCiSGWotk1gXis=; b=uDQZx3zrQlJcd1/ZcgSEeCY4GaCoRBjV+Ctixn4PTvKoXY5qYrS04k5YfVlQmyHJ+kzXYXMxLZWBV06AhgWdFlTshLVDQOtgl8ak6ovKFnYCtZE3Vis9HvE0lzqOiO8oFlqZNKEir4xSw2RkzN144j5OehGoC+1VGVOq/V88C9E=; Received: from jbeich by internal.tormail.org with local (Exim 4.63) (envelope-from ) id 1UF7wX-000BVL-0y; Mon, 11 Mar 2013 18:59:31 +0000 From: Jan Beich To: Dimitry Andric Subject: Re: CURRENT: lang/gcc fails to build on CURRENT with error: configure: error: no usable dependency style found Date: Mon, 11 Mar 2013 19:00:01 +0000 References: <513B56E8.2060702@zedat.fu-berlin.de> <8F5265A6-396A-426F-A3F8-EFD44D167313@FreeBSD.org> <20130309233930.GA95285@troutmask.apl.washington.edu> <513DAF4F.50602@FreeBSD.org> <20130311131318.GA57506@troutmask.apl.washington.edu> <513DD90F.2090700@daemonic.se> <513E0656.7000601@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain X-TorMail-User: jbeich Message-Id: <1UF7wX-000BVL-0y@internal.tormail.org> Cc: Steve Kargl , FreeBSD Current , =?utf-8?B?R8OhYm9yIEvDtnZlc2TDoW4=?= , freebsd-ports@freebsd.org, Niclas Zeising , "Hartmann, O." X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Mar 2013 19:02:18 -0000 Dimitry Andric writes: > $ echo 'sub/foo.barx' | grep sub/foo.bar > $ echo $? > 1 $ echo 'sub/foo.barx' | env -i grep sub/foo.bar $ echo 'sub/foolbarx' | env -i grep sub/foo.bar $ echo 'sub/foo.barx' | env -i grep 'sub/foo\.bar' sub/foo.barx $ echo 'sub/foo.barx' | env -i grep -o sub/foo.bar sub/foo.bar $ echo 'sub/foo.barx' | env -i grep --color=no sub/foo.bar sub/foo.barx A buggy shortcut? From owner-freebsd-current@FreeBSD.ORG Mon Mar 11 21:05:54 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 6E131E35; Mon, 11 Mar 2013 21:05:54 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from tensor.andric.com (tensor.andric.com [IPv6:2001:7b8:3a7:1:2d0:b7ff:fea0:8c26]) by mx1.freebsd.org (Postfix) with ESMTP id 2DBBB15C; Mon, 11 Mar 2013 21:05:54 +0000 (UTC) Received: from coleburn.home.andric.com (coleburn.home.andric.com [192.168.0.15]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id 8E9825C44; Mon, 11 Mar 2013 22:05:50 +0100 (CET) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\)) Subject: Re: CURRENT: lang/gcc fails to build on CURRENT with error: configure: error: no usable dependency style found From: Dimitry Andric In-Reply-To: <1UF7wX-000BVL-0y@internal.tormail.org> Date: Mon, 11 Mar 2013 22:05:47 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: <0C12B97B-F096-4EB3-8225-07D590F4E34B@FreeBSD.org> References: <513B56E8.2060702@zedat.fu-berlin.de> <8F5265A6-396A-426F-A3F8-EFD44D167313@FreeBSD.org> <20130309233930.GA95285@troutmask.apl.washington.edu> <513DAF4F.50602@FreeBSD.org> <20130311131318.GA57506@troutmask.apl.washington.edu> <513DD90F.2090700@daemonic.se> <513E0656.7000601@FreeBSD.org> <1UF7wX-000BVL-0y@internal.tormail.org> To: Jan Beich X-Mailer: Apple Mail (2.1499) Cc: Steve Kargl , FreeBSD Current , =?iso-8859-1?Q?G=E1bor_K=F6vesd=E1n?= , freebsd-ports@freebsd.org, Niclas Zeising , "O. Hartmann" , Mark Johnston X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Mar 2013 21:05:54 -0000 On 2013-03-11 20:00, Jan Beich wrote: > Dimitry Andric writes: >=20 >> $ echo 'sub/foo.barx' | grep sub/foo.bar >> $ echo $? >> 1 >=20 > $ echo 'sub/foo.barx' | env -i grep sub/foo.bar > $ echo 'sub/foolbarx' | env -i grep sub/foo.bar > $ echo 'sub/foo.barx' | env -i grep 'sub/foo\.bar' > sub/foo.barx > $ echo 'sub/foo.barx' | env -i grep -o sub/foo.bar > sub/foo.bar > $ echo 'sub/foo.barx' | env -i grep --color=3Dno sub/foo.bar > sub/foo.barx >=20 > A buggy shortcut? No, after some digging in and debugging of the bsdgrep code, I found out = it is a regression caused by r246917, which is a fix for "bin/175213: = [patch] bsdgrep(1) segfaults upon malicious input". If you revert it, = bsdgrep starts working correctly again. I think it would be best to back out r246917 for now, until the = regression can be fixed properly. Having bsdgrep crash is bad, but not = returning any results while it should is even worse... From owner-freebsd-current@FreeBSD.ORG Mon Mar 11 21:18:58 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 4AF5F625; Mon, 11 Mar 2013 21:18:58 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.21]) by mx1.freebsd.org (Postfix) with ESMTP id 0DDAE250; Mon, 11 Mar 2013 21:18:58 +0000 (UTC) Received: from troutmask.apl.washington.edu (localhost.apl.washington.edu [127.0.0.1]) by troutmask.apl.washington.edu (8.14.6/8.14.6) with ESMTP id r2BLIqPm012203; Mon, 11 Mar 2013 14:18:52 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.14.6/8.14.6/Submit) id r2BLIpkm012202; Mon, 11 Mar 2013 14:18:51 -0700 (PDT) (envelope-from sgk) Date: Mon, 11 Mar 2013 14:18:51 -0700 From: Steve Kargl To: Dimitry Andric Subject: Re: CURRENT: lang/gcc fails to build on CURRENT with error: configure: error: no usable dependency style found Message-ID: <20130311211851.GA12143@troutmask.apl.washington.edu> References: <513B56E8.2060702@zedat.fu-berlin.de> <8F5265A6-396A-426F-A3F8-EFD44D167313@FreeBSD.org> <20130309233930.GA95285@troutmask.apl.washington.edu> <513DAF4F.50602@FreeBSD.org> <20130311131318.GA57506@troutmask.apl.washington.edu> <513DD90F.2090700@daemonic.se> <513E0656.7000601@FreeBSD.org> <1UF7wX-000BVL-0y@internal.tormail.org> <0C12B97B-F096-4EB3-8225-07D590F4E34B@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <0C12B97B-F096-4EB3-8225-07D590F4E34B@FreeBSD.org> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: FreeBSD Current , =?iso-8859-1?Q?G=E1bor_K=F6vesd=E1n?= , freebsd-ports@freebsd.org, Niclas Zeising , "O. Hartmann" , Mark Johnston , Jan Beich X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Mar 2013 21:18:58 -0000 On Mon, Mar 11, 2013 at 10:05:47PM +0100, Dimitry Andric wrote: > On 2013-03-11 20:00, Jan Beich wrote: > > Dimitry Andric writes: > > > >> $ echo 'sub/foo.barx' | grep sub/foo.bar > >> $ echo $? > >> 1 > > > > $ echo 'sub/foo.barx' | env -i grep sub/foo.bar > > $ echo 'sub/foolbarx' | env -i grep sub/foo.bar > > $ echo 'sub/foo.barx' | env -i grep 'sub/foo\.bar' > > sub/foo.barx > > $ echo 'sub/foo.barx' | env -i grep -o sub/foo.bar > > sub/foo.bar > > $ echo 'sub/foo.barx' | env -i grep --color=no sub/foo.bar > > sub/foo.barx > > > > A buggy shortcut? > > No, after some digging in and debugging of the bsdgrep code, I > found out it is a regression caused by r246917, which is a fix > for "bin/175213: [patch] bsdgrep(1) segfaults upon malicious input". > If you revert it, bsdgrep starts working correctly again. First, I can report that bootstrapping gcc-4.8.0 works if I use gnugrep instead of bsdgrep. The above explains why I had previously seen the failure as I was using an older bsdgrep. Second, an apology is owed to the clang gang as I attributed the problem to clang as it showed up on my system after converted everything over to clang. > I think it would be best to back out r246917 for now, until the > regression can be fixed properly. Having bsdgrep crash is bad, > but not returning any results while it should is even worse... I tend to agree with your assessment that r246817 should be reverted, because I hit this issue in configure scripts and there is a large amount of software that uses autotool for configuration. -- Steve From owner-freebsd-current@FreeBSD.ORG Tue Mar 12 07:09:18 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id C5103694 for ; Tue, 12 Mar 2013 07:09:18 +0000 (UTC) (envelope-from dieterich.joh@gmail.com) Received: from mail-qc0-x235.google.com (mail-qc0-x235.google.com [IPv6:2607:f8b0:400d:c01::235]) by mx1.freebsd.org (Postfix) with ESMTP id 74C77CDB for ; Tue, 12 Mar 2013 07:09:18 +0000 (UTC) Received: by mail-qc0-f181.google.com with SMTP id a22so1916010qcs.12 for ; Tue, 12 Mar 2013 00:09:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :content-type; bh=+WDKnL1bVA3sL5uweqHFNSUeAJbkqcPz9s6SbYHIitc=; b=Khk789OjGxztmfWt54yQE7Bw+47qijY0dyJi3wCfsZ8A6MMIaA9IuapB2DPcB3cgHP oeQ9+fKAMAinj6kyC2Q+kQYijcvmKQ0OA1WQdhKeTejSMSWwiIQhO7HXfFrANOZYmWk1 v1sQiptnfh7ZgFp8T8bnoN/h5HFiNcCGTvWOOGNFVKN+iz3LR3aMcz2eOxBJwn9oFspC qn728Zpedhc//YZG3jZuiIKXNMPyggTZPS2apMJis1azJGHP8jtlFTMvsB5CQ1GAP6Ze oz++MN2/bwNS0y8/4XaBMYncq3gRDHRrMxHDoFn9f0qSZXITzryICVmRVS2UeBMdknPl WuOQ== X-Received: by 10.49.51.5 with SMTP id g5mr24188060qeo.9.1363072157940; Tue, 12 Mar 2013 00:09:17 -0700 (PDT) Received: from bresson.poelloepaeae.de (pool-173-72-34-218.cmdnnj.fios.verizon.net. [173.72.34.218]) by mx.google.com with ESMTPS id u7sm26158856qau.2.2013.03.12.00.09.16 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 12 Mar 2013 00:09:16 -0700 (PDT) Message-ID: <513ED49B.4060503@gmail.com> Date: Tue, 12 Mar 2013 03:09:15 -0400 From: Johannes Dieterich User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130309 Thunderbird/17.0.4 MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Headphone support on Thinkpad T430s Content-Type: multipart/mixed; boundary="------------060809090908040901030403" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Mar 2013 07:09:18 -0000 This is a multi-part message in MIME format. --------------060809090908040901030403 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Dear list, please see a patch to enable proper headphone support on Thinkpad T430s models. The quirk uses the same logic as the recent patch to CURRENT to enable some other Thinkpad models. Unfortunately, I cannot comment if this will work for other models (such as the regular T430) as well, therefore I used the T430S identifier. Hope someone can commit this, Johannes --------------060809090908040901030403 Content-Type: text/plain; charset=us-ascii; name="t430s_headphones.diff" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="t430s_headphones.diff" Index: sys/dev/sound/pci/hda/hdaa_patches.c =================================================================== --- sys/dev/sound/pci/hda/hdaa_patches.c (revision 248186) +++ sys/dev/sound/pci/hda/hdaa_patches.c (working copy) @@ -344,7 +344,8 @@ break; } } else if (id == HDA_CODEC_ALC269 && - subid == LENOVO_X1CRBN_SUBVENDOR) { + (subid == LENOVO_X1CRBN_SUBVENDOR || + subid == LENOVO_T430S_SUBVENDOR)) { switch (nid) { case 21: patch = "as=1 seq=15"; Index: sys/dev/sound/pci/hda/hdac.h =================================================================== --- sys/dev/sound/pci/hda/hdac.h (revision 248186) +++ sys/dev/sound/pci/hda/hdac.h (working copy) @@ -218,13 +218,14 @@ #define LENOVO_VENDORID 0x17aa #define LENOVO_3KN100_SUBVENDOR HDA_MODEL_CONSTRUCT(LENOVO, 0x2066) #define LENOVO_3KN200_SUBVENDOR HDA_MODEL_CONSTRUCT(LENOVO, 0x384e) -#define LENOVO_B450_SUBVENDOR HDA_MODEL_CONSTRUCT(LENOVO, 0x3a0d) +#define LENOVO_B450_SUBVENDOR HDA_MODEL_CONSTRUCT(LENOVO, 0x3a0d) #define LENOVO_TCA55_SUBVENDOR HDA_MODEL_CONSTRUCT(LENOVO, 0x1015) #define LENOVO_X1_SUBVENDOR HDA_MODEL_CONSTRUCT(LENOVO, 0x21e8) #define LENOVO_X1CRBN_SUBVENDOR HDA_MODEL_CONSTRUCT(LENOVO, 0x21f9) #define LENOVO_X220_SUBVENDOR HDA_MODEL_CONSTRUCT(LENOVO, 0x21da) #define LENOVO_X300_SUBVENDOR HDA_MODEL_CONSTRUCT(LENOVO, 0x20ac) #define LENOVO_T420_SUBVENDOR HDA_MODEL_CONSTRUCT(LENOVO, 0x21ce) +#define LENOVO_T430S_SUBVENDOR HDA_MODEL_CONSTRUCT(LENOVO, 0x21fb) #define LENOVO_T520_SUBVENDOR HDA_MODEL_CONSTRUCT(LENOVO, 0x21cf) #define LENOVO_ALL_SUBVENDOR HDA_MODEL_CONSTRUCT(LENOVO, 0xffff) --------------060809090908040901030403-- From owner-freebsd-current@FreeBSD.ORG Tue Mar 12 07:28:47 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 5C437939 for ; Tue, 12 Mar 2013 07:28:47 +0000 (UTC) (envelope-from hiren.panchasara@gmail.com) Received: from mail-ee0-f54.google.com (mail-ee0-f54.google.com [74.125.83.54]) by mx1.freebsd.org (Postfix) with ESMTP id F1ADFDB1 for ; Tue, 12 Mar 2013 07:28:46 +0000 (UTC) Received: by mail-ee0-f54.google.com with SMTP id c41so2625930eek.41 for ; Tue, 12 Mar 2013 00:28:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=d2EgHqmGWVsM7P2ucYBow+3TdsMh00e+qIit1SgmIWo=; b=QyjRdxR3QlpaGDPfKvrnYQkTpDY/swCEXC8MKMhanDzZMOjV8XKOO5Qj/IBVvLl8Xl dY5+pk6eq+MjGpxViAqrQrqh08413zdz4k4xO5zAMQ3+hZJkxxmkfo6k3H7bj2ttH5vP CJVw42fk382BxyNm/iVi9ragt/v1iZaVELgWQ7bx9WPkCJSiojb+QHZBp7NYukRa3m/a SxLHy1w2sFcqWXiruQ42/inI+XIkr2QL96XhDB4iA451NLhR6DvI9wtLoGVvmpxVDtoJ dpfRHD0J+kno2zwOi668scnGlbzqkDq7Hoo3uFPR9aW/AY9MHmTI9rGTMthuiINibzci yKLw== MIME-Version: 1.0 X-Received: by 10.14.215.193 with SMTP id e41mr45233423eep.32.1363073325719; Tue, 12 Mar 2013 00:28:45 -0700 (PDT) Received: by 10.14.133.204 with HTTP; Tue, 12 Mar 2013 00:28:45 -0700 (PDT) In-Reply-To: <513ED49B.4060503@gmail.com> References: <513ED49B.4060503@gmail.com> Date: Tue, 12 Mar 2013 00:28:45 -0700 Message-ID: Subject: Re: Headphone support on Thinkpad T430s From: hiren panchasara To: Johannes Dieterich Content-Type: text/plain; charset=UTF-8 Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Mar 2013 07:28:47 -0000 On Tue, Mar 12, 2013 at 12:09 AM, Johannes Dieterich wrote: > Dear list, > > please see a patch to enable proper headphone support on Thinkpad T430s > models. The quirk uses the same logic as the recent patch to CURRENT to > enable some other Thinkpad models. Unfortunately, I cannot comment if this > will work for other models (such as the regular T430) as well, therefore I > used the T430S identifier. For T430, the pins are at 0x21f3 so you assumed right. This patch would not work on it. T430S is the correct identifier. cheers, Hiren > > Hope someone can commit this, > > Johannes > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@FreeBSD.ORG Tue Mar 12 07:35:48 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 04A81ACD for ; Tue, 12 Mar 2013 07:35:48 +0000 (UTC) (envelope-from dieterich.joh@gmail.com) Received: from mail-qa0-f45.google.com (mail-qa0-f45.google.com [209.85.216.45]) by mx1.freebsd.org (Postfix) with ESMTP id B2D19E01 for ; Tue, 12 Mar 2013 07:35:47 +0000 (UTC) Received: by mail-qa0-f45.google.com with SMTP id g10so1444911qah.11 for ; Tue, 12 Mar 2013 00:35:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=/7nlmfEW8DMEmDDqgatR2ksNJkn7ZaphujTxo0iiVg4=; b=r3O3p7mwQw27lMC18L9/HlM+bY8MNOiS3Dlk4uc9go4uzd3jft/jVzBt8v5EWIJKSa OjKT2mHci1XqQHTx/6xf1DOuPbKUQnxW1EcOp138xKnsShGJ6TqCf1XHIkYMU6dS+vHr qB2ZtQLXkmBNEf46It+SAFfnM6tFWzygu//Sz9y3nb4q1CZa5/yz6jK1/lTS2SAmrV7h 8A8VFLX+JyfIrJH+4svDkreuH1c4wCybFH0KEXJL4dNM+Cfa9lRIrBSR5lDGlhEb+gig 3AJOiYk2CEYlkZPr+ckkyys6XxGqzHXfsYjvEhyCCnKVw9X5EuX0w3M7fG4KTT43JGdk qLig== X-Received: by 10.224.182.70 with SMTP id cb6mr20675004qab.80.1363073741670; Tue, 12 Mar 2013 00:35:41 -0700 (PDT) Received: from bresson.poelloepaeae.de (pool-173-72-34-218.cmdnnj.fios.verizon.net. [173.72.34.218]) by mx.google.com with ESMTPS id ku2sm29413265qeb.4.2013.03.12.00.35.40 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 12 Mar 2013 00:35:40 -0700 (PDT) Message-ID: <513EDACB.2070901@gmail.com> Date: Tue, 12 Mar 2013 03:35:39 -0400 From: Johannes Dieterich User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130309 Thunderbird/17.0.4 MIME-Version: 1.0 To: "Sergey V. Dyatko" , freebsd-current@freebsd.org Subject: Re: Headphone support on Thinkpad T430s References: <513ED49B.4060503@gmail.com> <20130312103408.58abbb8e@laptop> In-Reply-To: <20130312103408.58abbb8e@laptop> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Mar 2013 07:35:48 -0000 On 03/12/13 03:34, Sergey V. Dyatko wrote: > On Tue, 12 Mar 2013 00:28:45 -0700 > hiren panchasara wrote: > >> On Tue, Mar 12, 2013 at 12:09 AM, Johannes Dieterich >> wrote: >>> Dear list, >>> >>> please see a patch to enable proper headphone support on Thinkpad >>> T430s models. The quirk uses the same logic as the recent patch to >>> CURRENT to enable some other Thinkpad models. Unfortunately, I >>> cannot comment if this will work for other models (such as the >>> regular T430) as well, therefore I used the T430S identifier. >> For T430, the pins are at 0x21f3 so you assumed right. This patch >> would not work on it. >> T430S is the correct identifier. >> > > and don't touch my B450 please :) Sorry, just formatting. Otherwise it is unchanged. :-) Best Johannes From owner-freebsd-current@FreeBSD.ORG Tue Mar 12 07:43:40 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 45559CB9 for ; Tue, 12 Mar 2013 07:43:40 +0000 (UTC) (envelope-from kolyasir@gmail.com) Received: from mail-qa0-f45.google.com (mail-qa0-f45.google.com [209.85.216.45]) by mx1.freebsd.org (Postfix) with ESMTP id 00E9FE6F for ; Tue, 12 Mar 2013 07:43:39 +0000 (UTC) Received: by mail-qa0-f45.google.com with SMTP id g10so1437524qah.4 for ; Tue, 12 Mar 2013 00:43:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=K2skPpa+zAFTnPiC9MbBpOTCjT1hsgqQjcqJC3w7Fbw=; b=bk7E7d7SfggHRzWq0+tqyTYV4+XT6XAmlexlKaKkEIqbPYGcSiHWHklQDC4yp8MJfj VmRBKkFz45zoZdrBS8w2RcZQoRcu54P3cvPXCCMGW0hkqoKEZdBSxPEGmWg9M5+7UoE6 XdkCX7fDXwYIKVNZxF1yVxzYO+/2UMfknMWd3zU7rtSKB/dxayYQGclSDzpA7Y7PCsvP XyKv1YxA7mGuI+o9JI8+5fnaOL7zxZOakB4mwo/IRMTpC6Bq2usdfLgCuGJWDE/0opqq ugoW3FNraG0HhqUHntPUPkTu1xfkPNBV3KFREFTVL9syk+FSVU3TpfQXp7Jm+WgObbIC mVYw== MIME-Version: 1.0 X-Received: by 10.224.117.66 with SMTP id p2mr15330671qaq.45.1363074219529; Tue, 12 Mar 2013 00:43:39 -0700 (PDT) Received: by 10.49.48.197 with HTTP; Tue, 12 Mar 2013 00:43:39 -0700 (PDT) Date: Tue, 12 Mar 2013 03:43:39 -0400 Message-ID: Subject: using multiple interfaces for same Network Card From: Yasir hussan To: Current Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Mar 2013 07:43:40 -0000 Hi guys, Is there any way that i can have multiple interfaces which i can able to access from any other machine for same single network card, I am able to create new interfaces like # ifconfig arge0.1 create but i am unable to access it frm any other machine. I want it be able to oing from any other machine.... Thanks From owner-freebsd-current@FreeBSD.ORG Tue Mar 12 08:04:47 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 82FE0519 for ; Tue, 12 Mar 2013 08:04:47 +0000 (UTC) (envelope-from SNasonov@BCC.RU) Received: from extmx.bcc.ru (extmx.bcc.ru [217.170.85.214]) by mx1.freebsd.org (Postfix) with ESMTP id BDBA4F39 for ; Tue, 12 Mar 2013 08:04:46 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by extmx.bcc.ru (Postfix) with ESMTP id D3B8816011; Tue, 12 Mar 2013 12:04:33 +0400 (GMT-4) Received: from extmx.bcc.ru ([127.0.0.1]) by localhost (extmx.bcc.ru [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 30817-04; Tue, 12 Mar 2013 12:04:28 +0400 (GMT-4) Received: from mail.bcc (unknown [172.16.250.23]) by extmx.bcc.ru (Postfix) with ESMTP id A54E013562; Tue, 12 Mar 2013 12:04:28 +0400 (GMT-4) Received: from snasonovnbwxp.bcc ([192.168.201.205]) by mail.bcc over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Tue, 12 Mar 2013 12:04:32 +0400 From: Sergey Nasonov To: freebsd-current@freebsd.org Subject: Re: Headphone support on Thinkpad T430s Date: Tue, 12 Mar 2013 12:04:25 +0400 Message-ID: <1584949.6vl9dv5U6v@snasonovnbwxp.bcc> Organization: BCC User-Agent: KMail/4.9.5 (FreeBSD/9.1-STABLE; KDE/4.9.5; amd64; ; ) In-Reply-To: <513ED49B.4060503@gmail.com> References: <513ED49B.4060503@gmail.com> MIME-Version: 1.0 X-OriginalArrivalTime: 12 Mar 2013 08:04:32.0975 (UTC) FILETIME=[3AEE6DF0:01CE1EF8] X-Virus-Scanned: amavisd-new at bcc.ru Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: Johannes Dieterich X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Mar 2013 08:04:47 -0000 I have T430 and to get headphone working I am using following workaround: hint.hdaa.4.nid21.config="as=1 seq=15" in /boot/device.hints So the final patch should looks like this Index: sys/dev/sound/pci/hda/hdaa_patches.c =================================================================== --- sys/dev/sound/pci/hda/hdaa_patches.c (revision 248186) +++ sys/dev/sound/pci/hda/hdaa_patches.c (working copy) @@ -344,7 +344,8 @@ break; } } else if (id == HDA_CODEC_ALC269 && - subid == LENOVO_X1CRBN_SUBVENDOR) { + (subid == LENOVO_X1CRBN_SUBVENDOR || + subid == LENOVO_T430_SUBVENDOR || + subid == LENOVO_T430S_SUBVENDOR)) { switch (nid) { case 21: patch = "as=1 seq=15"; Index: sys/dev/sound/pci/hda/hdac.h =================================================================== --- sys/dev/sound/pci/hda/hdac.h (revision 248186) +++ sys/dev/sound/pci/hda/hdac.h (working copy) @@ -218,13 +218,14 @@ #define LENOVO_VENDORID 0x17aa #define LENOVO_3KN100_SUBVENDOR HDA_MODEL_CONSTRUCT(LENOVO, 0x2066) #define LENOVO_3KN200_SUBVENDOR HDA_MODEL_CONSTRUCT(LENOVO, 0x384e) -#define LENOVO_B450_SUBVENDOR HDA_MODEL_CONSTRUCT(LENOVO, 0x3a0d) +#define LENOVO_B450_SUBVENDOR HDA_MODEL_CONSTRUCT(LENOVO, 0x3a0d) #define LENOVO_TCA55_SUBVENDOR HDA_MODEL_CONSTRUCT(LENOVO, 0x1015) #define LENOVO_X1_SUBVENDOR HDA_MODEL_CONSTRUCT(LENOVO, 0x21e8) #define LENOVO_X1CRBN_SUBVENDOR HDA_MODEL_CONSTRUCT(LENOVO, 0x21f9) #define LENOVO_X220_SUBVENDOR HDA_MODEL_CONSTRUCT(LENOVO, 0x21da) #define LENOVO_X300_SUBVENDOR HDA_MODEL_CONSTRUCT(LENOVO, 0x20ac) #define LENOVO_T420_SUBVENDOR HDA_MODEL_CONSTRUCT(LENOVO, 0x21ce) +#define LENOVO_T430_SUBVENDOR HDA_MODEL_CONSTRUCT(LENOVO, 0x21f3) +#define LENOVO_T430S_SUBVENDOR HDA_MODEL_CONSTRUCT(LENOVO, 0x21fb) #define LENOVO_T520_SUBVENDOR HDA_MODEL_CONSTRUCT(LENOVO, 0x21cf) #define LENOVO_ALL_SUBVENDOR HDA_MODEL_CONSTRUCT(LENOVO, 0xffff) On Tuesday 12 March 2013 03:09:15 Johannes Dieterich wrote: > Dear list, > > please see a patch to enable proper headphone support on Thinkpad T430s > models. The quirk uses the same logic as the recent patch to CURRENT to > enable some other Thinkpad models. Unfortunately, I cannot comment if > this will work for other models (such as the regular T430) as well, > therefore I used the T430S identifier. > > Hope someone can commit this, > > Johannes -- Best Regards, Nasonov Sergey From owner-freebsd-current@FreeBSD.ORG Tue Mar 12 10:08:22 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 1C9BD188 for ; Tue, 12 Mar 2013 10:08:22 +0000 (UTC) (envelope-from tevans.uk@googlemail.com) Received: from mail-la0-x22f.google.com (mail-la0-x22f.google.com [IPv6:2a00:1450:4010:c03::22f]) by mx1.freebsd.org (Postfix) with ESMTP id 7FBA9810 for ; Tue, 12 Mar 2013 10:08:21 +0000 (UTC) Received: by mail-la0-f47.google.com with SMTP id fj20so4984157lab.34 for ; Tue, 12 Mar 2013 03:08:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=ukNYjkG9VJlblgFA4ybga4aBh1/gmEuPOTX1pHRhI0Q=; b=MRPnYj2Crgl2PLDaFYCkJvjhHNn13rRmLTKF83VQXndaiKAzDU6DOZQqoN1wWFG8kh k8hKEGap4Zf56OUjaWUZxU8xiRIwWijqilX+/SCPHX0dtAEPlqZsiPi4zw/Jov+7zzEu BiQuRXvm3WnURWsMxglW9aEzyvuoVBkdvchg7LyU56yQ3dQ8kzvrYfLAqXNAWTRxsvAc 3BdNcNJXeM4lu/KI1bQy9nekgI/Q8voDiBnX51XYii3606Gw6RoCgTjlEfaNU5OFOgO9 iVcutOwcUcwniibW1xnBN1Jf6OkjUJCzTr9DxSrFGC2x8iTyQOyot29qSV9zrJ6YOZuE DbEA== MIME-Version: 1.0 X-Received: by 10.112.88.72 with SMTP id be8mr5878067lbb.116.1363082900215; Tue, 12 Mar 2013 03:08:20 -0700 (PDT) Received: by 10.112.26.135 with HTTP; Tue, 12 Mar 2013 03:08:20 -0700 (PDT) In-Reply-To: References: Date: Tue, 12 Mar 2013 10:08:20 +0000 Message-ID: Subject: Re: using multiple interfaces for same Network Card From: Tom Evans To: Yasir hussan Content-Type: text/plain; charset=UTF-8 Cc: Current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Mar 2013 10:08:22 -0000 On Tue, Mar 12, 2013 at 7:43 AM, Yasir hussan wrote: > Hi guys, > > Is there any way that i can have multiple interfaces which i can able to > access from any other machine for same single network card, I am able to > create new interfaces like > > # ifconfig arge0.1 create > > but i am unable to access it frm any other machine. I want it be able to > oing from any other machine.... > > Thanks I see you asked about this yesterday: https://groups.google.com/forum/?fromgroups=#!topic/mailing.freebsd.current/uP9BC7_dSrA "ifconfig create" is how aliases are created on linux. You need to use "ifconfig alias" on FreeBSD. As was pointed out to you yesterday when you asked. Cheers Tom From owner-freebsd-current@FreeBSD.ORG Tue Mar 12 10:41:12 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 0E8EBFE7 for ; Tue, 12 Mar 2013 10:41:12 +0000 (UTC) (envelope-from kolyasir@gmail.com) Received: from mail-qa0-f54.google.com (mail-qa0-f54.google.com [209.85.216.54]) by mx1.freebsd.org (Postfix) with ESMTP id 8BF43A06 for ; Tue, 12 Mar 2013 10:41:10 +0000 (UTC) Received: by mail-qa0-f54.google.com with SMTP id hg5so1488171qab.6 for ; Tue, 12 Mar 2013 03:41:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=v72kLmTlbjlGwsFWNWu5f25PC5q7Ujek+5Pvd23k7Wo=; b=BC3ITg9NqXtX+z/o9a1F5p8b/Tr437uDsHE4vqhevZrD7E44TJnOh7iNhpMwDrx7Zd byscUf+WthaemPl9mt0QL8YFaBliXf/xPTLRTK1NE486SzhR2awqYA8jJGE41oVLU1dM xM7VP8kD6xdrr807foQv3bD7ku4TzZEFbgog1g7f1BEAcZYf2Ya6KPyv6D+F92VyEciO 84NAFL7gsuesxh1dafVlKwqk+GXYNILJViox3sIPuGcjB+6IgiDjPFLVNIm5nydFswT5 zYKQf/QdHHQIDl6kDixbZBswYlEpOxhsVZ8sj5oLdmomwzl6Ya0P8/R97rlz6HUWFMpj OZ0g== MIME-Version: 1.0 X-Received: by 10.49.15.198 with SMTP id z6mr24303706qec.6.1363084864448; Tue, 12 Mar 2013 03:41:04 -0700 (PDT) Received: by 10.49.48.197 with HTTP; Tue, 12 Mar 2013 03:41:04 -0700 (PDT) In-Reply-To: References: Date: Tue, 12 Mar 2013 06:41:04 -0400 Message-ID: Subject: Re: using multiple interfaces for same Network Card From: Yasir hussan To: Tom Evans Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: Current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Mar 2013 10:41:12 -0000 Thanks for notic but all the elebration was for make alias on one interface but i want to have multiple interface, i can no where that some one would have tring to creating new interfaces and using them, or may be i am missing something, just send its solution if have, solution should be for On Tue, Mar 12, 2013 at 6:08 AM, Tom Evans wrote: > On Tue, Mar 12, 2013 at 7:43 AM, Yasir hussan wrote: > > Hi guys, > > > > Is there any way that i can have multiple interfaces which i can able to > > access from any other machine for same single network card, I am able to > > create new interfaces like > > > > # ifconfig arge0.1 create > > > > but i am unable to access it frm any other machine. I want it be able to > > oing from any other machine.... > > > > Thanks > > I see you asked about this yesterday: > > > https://groups.google.com/forum/?fromgroups=#!topic/mailing.freebsd.current/uP9BC7_dSrA > > "ifconfig create" is how aliases are created on linux. You > need to use "ifconfig alias" on FreeBSD. As was pointed > out to you yesterday when you asked. > > Cheers > > Tom > From owner-freebsd-current@FreeBSD.ORG Tue Mar 12 10:44:45 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 60FE252D for ; Tue, 12 Mar 2013 10:44:45 +0000 (UTC) (envelope-from hiren.panchasara@gmail.com) Received: from mail-ee0-f53.google.com (mail-ee0-f53.google.com [74.125.83.53]) by mx1.freebsd.org (Postfix) with ESMTP id 01407A66 for ; Tue, 12 Mar 2013 10:44:44 +0000 (UTC) Received: by mail-ee0-f53.google.com with SMTP id e53so2584314eek.26 for ; Tue, 12 Mar 2013 03:44:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=zre6pXainB4VqHlBxZIM8perQEEGYC8cWTVZXvNVGO8=; b=oVipmVzW7Ht8wtxATjZglEqXyM0R0E2vXQN9omNfSSNXHtyOv3c2huVTLmBXWDAlEk Lb8J+j04IWd9nHrr/wJA+kH90vn8vc30nM1qq3LB8x4DM9gMSqVzKjVSF21kGJDeb6bW FcR+eiKW4RZe0PBsXUmRMNe9jgmeMa2+4b4lbRetLaa7z3qo+/Tx3RpI2S264KneZff4 NNuEEuOUbtIMiYueeV4K0Uw43c/UqyIy50sXrKaRM6ce423d6ntrds21K6/JubxoZNKV 14XNevK66Z7MW0lSZKdT8+muJ9h+n/vgV34n0Siryg4s4vyWGWIhXNCgof1M975ZUpxs zcSg== MIME-Version: 1.0 X-Received: by 10.14.219.129 with SMTP id m1mr41278202eep.16.1363085083884; Tue, 12 Mar 2013 03:44:43 -0700 (PDT) Received: by 10.14.133.204 with HTTP; Tue, 12 Mar 2013 03:44:43 -0700 (PDT) In-Reply-To: <1584949.6vl9dv5U6v@snasonovnbwxp.bcc> References: <513ED49B.4060503@gmail.com> <1584949.6vl9dv5U6v@snasonovnbwxp.bcc> Date: Tue, 12 Mar 2013 03:44:43 -0700 Message-ID: Subject: Re: Headphone support on Thinkpad T430s From: hiren panchasara To: Sergey Nasonov Content-Type: text/plain; charset=UTF-8 Cc: Johannes Dieterich , freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Mar 2013 10:44:45 -0000 On Tue, Mar 12, 2013 at 1:04 AM, Sergey Nasonov wrote: > I have T430 and to get headphone working I am using following workaround: > > hint.hdaa.4.nid21.config="as=1 seq=15" in /boot/device.hints > > So the final patch should looks like this > > Index: sys/dev/sound/pci/hda/hdaa_patches.c > =================================================================== > --- sys/dev/sound/pci/hda/hdaa_patches.c (revision 248186) > +++ sys/dev/sound/pci/hda/hdaa_patches.c (working copy) > @@ -344,7 +344,8 @@ > break; > } > } else if (id == HDA_CODEC_ALC269 && > - subid == LENOVO_X1CRBN_SUBVENDOR) { > + (subid == LENOVO_X1CRBN_SUBVENDOR || > + subid == LENOVO_T430_SUBVENDOR || > + subid == LENOVO_T430S_SUBVENDOR)) { > switch (nid) { > case 21: > patch = "as=1 seq=15"; > Index: sys/dev/sound/pci/hda/hdac.h > =================================================================== > --- sys/dev/sound/pci/hda/hdac.h (revision 248186) > +++ sys/dev/sound/pci/hda/hdac.h (working copy) > @@ -218,13 +218,14 @@ > #define LENOVO_VENDORID 0x17aa > #define LENOVO_3KN100_SUBVENDOR HDA_MODEL_CONSTRUCT(LENOVO, 0x2066) > #define LENOVO_3KN200_SUBVENDOR HDA_MODEL_CONSTRUCT(LENOVO, 0x384e) > -#define LENOVO_B450_SUBVENDOR HDA_MODEL_CONSTRUCT(LENOVO, 0x3a0d) > +#define LENOVO_B450_SUBVENDOR HDA_MODEL_CONSTRUCT(LENOVO, 0x3a0d) > #define LENOVO_TCA55_SUBVENDOR HDA_MODEL_CONSTRUCT(LENOVO, 0x1015) > #define LENOVO_X1_SUBVENDOR HDA_MODEL_CONSTRUCT(LENOVO, 0x21e8) > #define LENOVO_X1CRBN_SUBVENDOR HDA_MODEL_CONSTRUCT(LENOVO, 0x21f9) > #define LENOVO_X220_SUBVENDOR HDA_MODEL_CONSTRUCT(LENOVO, 0x21da) > #define LENOVO_X300_SUBVENDOR HDA_MODEL_CONSTRUCT(LENOVO, 0x20ac) > #define LENOVO_T420_SUBVENDOR HDA_MODEL_CONSTRUCT(LENOVO, 0x21ce) > +#define LENOVO_T430_SUBVENDOR HDA_MODEL_CONSTRUCT(LENOVO, 0x21f3) > +#define LENOVO_T430S_SUBVENDOR HDA_MODEL_CONSTRUCT(LENOVO, 0x21fb) > #define LENOVO_T520_SUBVENDOR HDA_MODEL_CONSTRUCT(LENOVO, 0x21cf) > #define LENOVO_ALL_SUBVENDOR HDA_MODEL_CONSTRUCT(LENOVO, 0xffff) > > > On Tuesday 12 March 2013 03:09:15 Johannes Dieterich wrote: >> Dear list, >> >> please see a patch to enable proper headphone support on Thinkpad T430s >> models. The quirk uses the same logic as the recent patch to CURRENT to >> enable some other Thinkpad models. Unfortunately, I cannot comment if >> this will work for other models (such as the regular T430) as well, >> therefore I used the T430S identifier. >> >> Hope someone can commit this, http://svnweb.freebsd.org/changeset/base/248187 Glebius just did. cheers, Hiren >> >> Johannes > -- > Best Regards, > Nasonov Sergey > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@FreeBSD.ORG Tue Mar 12 12:02:31 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id E410F26E for ; Tue, 12 Mar 2013 12:02:31 +0000 (UTC) (envelope-from matthew@freebsd.org) Received: from smtp.infracaninophile.co.uk (smtp6.infracaninophile.co.uk [IPv6:2001:8b0:151:1:3cd3:cd67:fafa:3d78]) by mx1.freebsd.org (Postfix) with ESMTP id 6855BFDF for ; Tue, 12 Mar 2013 12:02:31 +0000 (UTC) Received: from rufus.webfusion.com (mail.heartinternet.co.uk [79.170.40.31]) (authenticated bits=0) by smtp.infracaninophile.co.uk (8.14.6/8.14.6) with ESMTP id r2CC2EFU001993 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for ; Tue, 12 Mar 2013 12:02:21 GMT (envelope-from matthew@freebsd.org) DKIM-Filter: OpenDKIM Filter v2.8.0 smtp.infracaninophile.co.uk r2CC2EFU001993 Authentication-Results: smtp.infracaninophile.co.uk/r2CC2EFU001993; dkim=none reason="no signature"; dkim-adsp=none (unprotected policy) X-Authentication-Warning: lucid-nonsense.infracaninophile.co.uk: Host mail.heartinternet.co.uk [79.170.40.31] claimed to be rufus.webfusion.com Message-ID: <513F1945.4000902@freebsd.org> Date: Tue, 12 Mar 2013 12:02:13 +0000 From: Matthew Seaman User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130220 Thunderbird/17.0.3 MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Re: using multiple interfaces for same Network Card References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Scanned: clamav-milter 0.97.6 at lucid-nonsense.infracaninophile.co.uk X-Virus-Status: Clean X-Spam-Status: No, score=-1.6 required=5.0 tests=AWL,BAYES_00,SPF_SOFTFAIL autolearn=no version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on lucid-nonsense.infracaninophile.co.uk X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Mar 2013 12:02:32 -0000 On 12/03/2013 10:41, Yasir hussan wrote: > Thanks for notic but all the elebration was for make alias on one interface > but i want to have multiple interface, i can no where that some one would > have tring to creating new interfaces and using them, or may be i am > missing something, just send its solution if have, solution should be for Sorry, we're not understanding you very well. If you have a network card with several ethernet sockets on it, then the OS will already present you with an interface per socket. That's pretty obvious, so I guess that's not what you're really after. Do you mean you want to use VLans? (virtual local area networks) -- that involves creating what are effectively separate virtual interfaces, one for ech vlan, all based on the same physical interface. Note: you need support and configuration for this in you networking switch gear. However, to configure vlan interfaces on FreeBSD, edit /etc/rc.conf to add first a setting to show what vlan interfaces you want to attach to your physical interface: vlans_em0="vlan101 vlan102 vlan107" Then you can set the vlan tag on creation of each clan by adding: create_args_vlan101="vlan 101" create_args_vlan102="vlan 102" create_args_vlan107="vlan 107" plus you'll need to set up IP addresses on the new vlan interfaces exactly as you would for a physical interface/ See vlan(4) for more detail. Cheers, Matthew From owner-freebsd-current@FreeBSD.ORG Tue Mar 12 12:12:29 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id AC085C77 for ; Tue, 12 Mar 2013 12:12:29 +0000 (UTC) (envelope-from ianf@clue.co.za) Received: from zcs03.jnb1.cloudseed.co.za (zcs03.jnb1.cloudseed.co.za [41.154.0.139]) by mx1.freebsd.org (Postfix) with ESMTP id 489F0131 for ; Tue, 12 Mar 2013 12:12:29 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by zcs03.jnb1.cloudseed.co.za (Postfix) with ESMTP id 5552E2B42F3B; Tue, 12 Mar 2013 14:06:34 +0200 (SAST) X-Virus-Scanned: amavisd-new at zcs03.jnb1.cloudseed.co.za Received: from zcs03.jnb1.cloudseed.co.za ([127.0.0.1]) by localhost (zcs03.jnb1.cloudseed.co.za [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GT2ePRPOLOSR; Tue, 12 Mar 2013 14:06:33 +0200 (SAST) Received: from clue.co.za (unknown [197.87.27.46]) by zcs03.jnb1.cloudseed.co.za (Postfix) with ESMTPSA id B66002B42F09; Tue, 12 Mar 2013 14:06:33 +0200 (SAST) Received: from localhost ([127.0.0.1] helo=new.clue.co.za) by clue.co.za with esmtp (Exim 4.80.1 (FreeBSD)) (envelope-from ) id 1UFNyS-000H0R-TC; Tue, 12 Mar 2013 14:06:32 +0200 To: Yasir hussan From: Ian FREISLICH Subject: Re: using multiple interfaces for same Network Card In-Reply-To: References: X-Attribution: BOFH Date: Tue, 12 Mar 2013 14:06:32 +0200 Message-Id: Cc: Tom Evans , Current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Mar 2013 12:12:29 -0000 Yasir hussan wrote: > Thanks for notic but all the elebration was for make alias on one > interface but i want to have multiple interface, i can no where that > some one would have tring to creating new interfaces and using them, > or may be i am missing something, just send its solution if have, > solution should be for I still think you're confusing Linux semantics with FreeBSD semantics. On linux you would have: eth0 Link encap:Ethernet HWaddr 00:1E:C9:53:0B:61 inet addr:10.0.0.1 Bcast:10.0.0.255 Mask:255.255.255.0 inet6 addr: fe80::21e:c9ff:fe53:b61/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:211328068 errors:0 dropped:0 overruns:0 frame:0 TX packets:368394006 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:34065846811 (31.7 GiB) TX bytes:476377525764 (443.6 GiB) Interrupt:169 Memory:e6000000-e6011100 eth0:1 Link encap:Ethernet HWaddr 00:1E:C9:53:0B:61 inet addr:10.0.1.1 Bcast:10.0.1.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 Interrupt:169 Memory:e6000000-e6011100 On FreeBSD you would have: re0: flags=8843 metric 0 mtu 1500 options=8209b ether 54:04:a6:96:0c:1e inet 10.0.0.1 netmask 0xffffff00 broadcast 10.0.0.255 inet 10.0.1.1 netmask 0xffffff00 broadcast 10.0.1.255 media: Ethernet autoselect (1000baseT ) status: active These are both the same thing. Is there any particular reason that you want multiple interfaces? I can't see a use for it beyond "it's what I'm used to seeing" unless they're VLAN interfaces. Ian -- Ian Freislich From owner-freebsd-current@FreeBSD.ORG Tue Mar 12 18:33:03 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id CC3A1463 for ; Tue, 12 Mar 2013 18:33:03 +0000 (UTC) (envelope-from kolyasir@gmail.com) Received: from mail-qe0-f45.google.com (mail-qe0-f45.google.com [209.85.128.45]) by mx1.freebsd.org (Postfix) with ESMTP id 92274D97 for ; Tue, 12 Mar 2013 18:33:03 +0000 (UTC) Received: by mail-qe0-f45.google.com with SMTP id b4so102046qen.18 for ; Tue, 12 Mar 2013 11:32:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=DEbhseZPK68bkABPJQigRX89U8G58bVr2PTBfSBOB9c=; b=tSATUsi0745seJJz+Sm0J+dDyIOFBjeKNbMy6ln9o/Q4lTfPqbIpkRtAza0mJfZu+e LTy01HeYIe5k9HN9aQz/10mlsDbjWGMLT0xbp6BL2+U+dBpVd3nNT6aJAM6LyQ/aeiIR 3jNGZ0iP+nn7kDANgfXiQJ8yKRZTE3mIiEbQy5EWpQ/LL8vhnX5kXWkI40+Q8bGDEawz klhAg6BcSbtxkGKcn7eWjtiFGDD/t8LMQbVqYfZT33SckjEsAoVL4JJ8vr3o6916BhmE iNqkyHJCcT2v8EAEs3jW5/KZO4t3nOKfEv024OZJUquted6yaFNiN5PXEyGKLJQDo3L+ cl6g== MIME-Version: 1.0 X-Received: by 10.224.216.8 with SMTP id hg8mr24062203qab.74.1363113177187; Tue, 12 Mar 2013 11:32:57 -0700 (PDT) Received: by 10.49.48.197 with HTTP; Tue, 12 Mar 2013 11:32:57 -0700 (PDT) In-Reply-To: References: Date: Tue, 12 Mar 2013 23:32:57 +0500 Message-ID: Subject: Re: using multiple interfaces for same Network Card From: Yasir hussan To: Ian FREISLICH Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: Tom Evans , Current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Mar 2013 18:33:03 -0000 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-command/i tried to use it as ifconfig vlan11 create 10.10.11.1 255.255.255.0 vlan 11 vlandev arge0 ifconfig vlan12 create 10.10.12.1 255.255.255.0 vlan 12 vlandev arge0 ifconfig vlan13 create 10.10.13.1 255.255.255.0 vlan 13 vlandev arge0 ifconfig vlan14 create 10.10.14.1 255.255.255.0 vlan 14 vlandev arge0 i was expecting that it will create interfaces which will work under arge0, and will able to ping from any pc, Does any one have used it, kindly guide me about it Thanks On Tue, Mar 12, 2013 at 5:06 PM, Ian FREISLICH wrote: > Yasir hussan wrote: > > Thanks for notic but all the elebration was for make alias on one > > interface but i want to have multiple interface, i can no where that > > some one would have tring to creating new interfaces and using them, > > or may be i am missing something, just send its solution if have, > > solution should be for > > I still think you're confusing Linux semantics with FreeBSD semantics. > > On linux you would have: > eth0 Link encap:Ethernet HWaddr 00:1E:C9:53:0B:61 > inet addr:10.0.0.1 Bcast:10.0.0.255 Mask:255.255.255.0 > inet6 addr: fe80::21e:c9ff:fe53:b61/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:211328068 errors:0 dropped:0 overruns:0 frame:0 > TX packets:368394006 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:34065846811 (31.7 GiB) TX bytes:476377525764 (443.6 > GiB) > Interrupt:169 Memory:e6000000-e6011100 > > eth0:1 Link encap:Ethernet HWaddr 00:1E:C9:53:0B:61 > inet addr:10.0.1.1 Bcast:10.0.1.255 Mask:255.255.255.0 > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > Interrupt:169 Memory:e6000000-e6011100 > > > On FreeBSD you would have: > > re0: flags=8843 metric 0 mtu 1500 > > options=8209b > ether 54:04:a6:96:0c:1e > inet 10.0.0.1 netmask 0xffffff00 broadcast 10.0.0.255 > inet 10.0.1.1 netmask 0xffffff00 broadcast 10.0.1.255 > media: Ethernet autoselect (1000baseT ) > status: active > > These are both the same thing. Is there any particular reason that > you want multiple interfaces? I can't see a use for it beyond "it's > what I'm used to seeing" unless they're VLAN interfaces. > > Ian > > -- > Ian Freislich > From owner-freebsd-current@FreeBSD.ORG Tue Mar 12 18:39:54 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 848AE701 for ; Tue, 12 Mar 2013 18:39:54 +0000 (UTC) (envelope-from jmg@h2.funkthat.com) Received: from h2.funkthat.com (gate2.funkthat.com [208.87.223.18]) by mx1.freebsd.org (Postfix) with ESMTP id 644FAE77 for ; Tue, 12 Mar 2013 18:39:54 +0000 (UTC) Received: from h2.funkthat.com (localhost [127.0.0.1]) by h2.funkthat.com (8.14.3/8.14.3) with ESMTP id r2CIdlsU065633 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 12 Mar 2013 11:39:48 -0700 (PDT) (envelope-from jmg@h2.funkthat.com) Received: (from jmg@localhost) by h2.funkthat.com (8.14.3/8.14.3/Submit) id r2CIdliQ065632; Tue, 12 Mar 2013 11:39:47 -0700 (PDT) (envelope-from jmg) Date: Tue, 12 Mar 2013 11:39:47 -0700 From: John-Mark Gurney To: Yasir hussan Subject: Re: using multiple interfaces for same Network Card Message-ID: <20130312183947.GB88785@funkthat.com> Mail-Followup-To: Yasir hussan , Current References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i X-Operating-System: FreeBSD 7.2-RELEASE i386 X-PGP-Fingerprint: 54BA 873B 6515 3F10 9E88 9322 9CB1 8F74 6D3F A396 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html X-to-the-FBI-CIA-and-NSA: HI! HOW YA DOIN? can i haz chizburger? X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.2.2 (h2.funkthat.com [127.0.0.1]); Tue, 12 Mar 2013 11:39:48 -0700 (PDT) Cc: Current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Mar 2013 18:39:54 -0000 Yasir hussan wrote this message on Tue, Mar 12, 2013 at 23:32 +0500: > 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-command/i > tried to use it as > > ifconfig vlan11 create 10.10.11.1 255.255.255.0 vlan 11 vlandev arge0 > ifconfig vlan12 create 10.10.12.1 255.255.255.0 vlan 12 vlandev arge0 > ifconfig vlan13 create 10.10.13.1 255.255.255.0 vlan 13 vlandev arge0 > ifconfig vlan14 create 10.10.14.1 255.255.255.0 vlan 14 vlandev arge0 > > i was expecting that it will create interfaces which will work under arge0, > and will able to ping from any pc, Does any one have used it, kindly guide > me about it vlans are a way to add different broadcast domains.. You need to have a vlan capable switch/machine connected and properly configured... If you plug in the machine to a normal switch, and the other machine isn't vlan aware not much will happen... Now if you configure your machine to route (net.inet.ip.forwarding) and setup the pc w/ the proper routing tables, you'll be able to ping the machines... If this doesn't help, please talk w/ a local network engineer to help you configure your network properly... I'm succussfully using FreeBSD with both vlans, and aliases (multiple ips on a single interface aka broadcast domain)... > On Tue, Mar 12, 2013 at 5:06 PM, Ian FREISLICH wrote: > > > Yasir hussan wrote: > > > Thanks for notic but all the elebration was for make alias on one > > > interface but i want to have multiple interface, i can no where that > > > some one would have tring to creating new interfaces and using them, > > > or may be i am missing something, just send its solution if have, > > > solution should be for > > > > I still think you're confusing Linux semantics with FreeBSD semantics. > > > > On linux you would have: > > eth0 Link encap:Ethernet HWaddr 00:1E:C9:53:0B:61 > > inet addr:10.0.0.1 Bcast:10.0.0.255 Mask:255.255.255.0 > > inet6 addr: fe80::21e:c9ff:fe53:b61/64 Scope:Link > > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > > RX packets:211328068 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:368394006 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:0 txqueuelen:1000 > > RX bytes:34065846811 (31.7 GiB) TX bytes:476377525764 (443.6 > > GiB) > > Interrupt:169 Memory:e6000000-e6011100 > > > > eth0:1 Link encap:Ethernet HWaddr 00:1E:C9:53:0B:61 > > inet addr:10.0.1.1 Bcast:10.0.1.255 Mask:255.255.255.0 > > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > > Interrupt:169 Memory:e6000000-e6011100 > > > > > > On FreeBSD you would have: > > > > re0: flags=8843 metric 0 mtu 1500 > > > > options=8209b > > ether 54:04:a6:96:0c:1e > > inet 10.0.0.1 netmask 0xffffff00 broadcast 10.0.0.255 > > inet 10.0.1.1 netmask 0xffffff00 broadcast 10.0.1.255 > > media: Ethernet autoselect (1000baseT ) > > status: active > > > > These are both the same thing. Is there any particular reason that > > you want multiple interfaces? I can't see a use for it beyond "it's > > what I'm used to seeing" unless they're VLAN interfaces. -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." From owner-freebsd-current@FreeBSD.ORG Tue Mar 12 19:03:24 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id D2523553 for ; Tue, 12 Mar 2013 19:03:24 +0000 (UTC) (envelope-from kolyasir@gmail.com) Received: from mail-qe0-f53.google.com (mail-qe0-f53.google.com [209.85.128.53]) by mx1.freebsd.org (Postfix) with ESMTP id 942B630B for ; Tue, 12 Mar 2013 19:03:24 +0000 (UTC) Received: by mail-qe0-f53.google.com with SMTP id cz11so119493qeb.40 for ; Tue, 12 Mar 2013 12:03:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type; bh=jfSYPBz9J153kSloxCByttP/cD4zoLuCgRjzJa9lEZo=; b=c5pn/i4tsBIn0WuExSwXwpMzjToSjyV5+gpi3vi18dmbMr63vVdf9DpK019694p84A 0qsMI/tMb7/kBK68HAMa+iVOv9JQmaQ1/CeSyFUwO5oiFHZTrdSKpX/4A9ofiGYwX0sA mxgz54l25VfpPwGRbBrVW4Ou+/5SfvFFB5FKYP7iUvYy3X8cQ5zdctkdz4sNMppK2UkE wrF9IOGXhw6/E8lfpSclWnx0VVXnWuYrHtAMXo8qmmHgzTH4IdVSmYrrfFKhvdpQUZlh PkO14SG1n+ayQItwIL4nxnqYaHaqeQOYFziG9D0HQFf8y+AcVS+Dusnnia3pg/P/J+wh ytEg== MIME-Version: 1.0 X-Received: by 10.49.2.7 with SMTP id 7mr615617qeq.45.1363114998299; Tue, 12 Mar 2013 12:03:18 -0700 (PDT) Received: by 10.49.48.197 with HTTP; Tue, 12 Mar 2013 12:03:18 -0700 (PDT) In-Reply-To: <20130312183947.GB88785@funkthat.com> References: <20130312183947.GB88785@funkthat.com> Date: Wed, 13 Mar 2013 00:03:18 +0500 Message-ID: Subject: Re: using multiple interfaces for same Network Card From: Yasir hussan To: Yasir hussan , Current Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Mar 2013 19:03:25 -0000 U say u were successfully using vlans by vlandev in FreeBSD , Can u send me exact commands and configuration which u were applying, It will be very helpful for me... Thank On Tue, Mar 12, 2013 at 11:39 PM, John-Mark Gurney wrote: > Yasir hussan wrote this message on Tue, Mar 12, 2013 at 23:32 +0500: > > 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-command/i > > tried to use it as > > > > ifconfig vlan11 create 10.10.11.1 255.255.255.0 vlan 11 vlandev arge0 > > ifconfig vlan12 create 10.10.12.1 255.255.255.0 vlan 12 vlandev arge0 > > ifconfig vlan13 create 10.10.13.1 255.255.255.0 vlan 13 vlandev arge0 > > ifconfig vlan14 create 10.10.14.1 255.255.255.0 vlan 14 vlandev arge0 > > > > i was expecting that it will create interfaces which will work under > arge0, > > and will able to ping from any pc, Does any one have used it, kindly > guide > > me about it > > vlans are a way to add different broadcast domains.. You need to have a > vlan capable switch/machine connected and properly configured... If you > plug in the machine to a normal switch, and the other machine isn't vlan > aware not much will happen... > > Now if you configure your machine to route (net.inet.ip.forwarding) and > setup the pc w/ the proper routing tables, you'll be able to ping the > machines... > > If this doesn't help, please talk w/ a local network engineer to help > you configure your network properly... > > I'm succussfully using FreeBSD with both vlans, and aliases (multiple > ips on a single interface aka broadcast domain)... > > > On Tue, Mar 12, 2013 at 5:06 PM, Ian FREISLICH wrote: > > > > > Yasir hussan wrote: > > > > Thanks for notic but all the elebration was for make alias on one > > > > interface but i want to have multiple interface, i can no where that > > > > some one would have tring to creating new interfaces and using them, > > > > or may be i am missing something, just send its solution if have, > > > > solution should be for > > > > > > I still think you're confusing Linux semantics with FreeBSD semantics. > > > > > > On linux you would have: > > > eth0 Link encap:Ethernet HWaddr 00:1E:C9:53:0B:61 > > > inet addr:10.0.0.1 Bcast:10.0.0.255 Mask:255.255.255.0 > > > inet6 addr: fe80::21e:c9ff:fe53:b61/64 Scope:Link > > > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > > > RX packets:211328068 errors:0 dropped:0 overruns:0 frame:0 > > > TX packets:368394006 errors:0 dropped:0 overruns:0 carrier:0 > > > collisions:0 txqueuelen:1000 > > > RX bytes:34065846811 (31.7 GiB) TX bytes:476377525764 (443.6 > > > GiB) > > > Interrupt:169 Memory:e6000000-e6011100 > > > > > > eth0:1 Link encap:Ethernet HWaddr 00:1E:C9:53:0B:61 > > > inet addr:10.0.1.1 Bcast:10.0.1.255 Mask:255.255.255.0 > > > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > > > Interrupt:169 Memory:e6000000-e6011100 > > > > > > > > > On FreeBSD you would have: > > > > > > re0: flags=8843 metric 0 mtu > 1500 > > > > > > > options=8209b > > > ether 54:04:a6:96:0c:1e > > > inet 10.0.0.1 netmask 0xffffff00 broadcast 10.0.0.255 > > > inet 10.0.1.1 netmask 0xffffff00 broadcast 10.0.1.255 > > > media: Ethernet autoselect (1000baseT ) > > > status: active > > > > > > These are both the same thing. Is there any particular reason that > > > you want multiple interfaces? I can't see a use for it beyond "it's > > > what I'm used to seeing" unless they're VLAN interfaces. > > -- > John-Mark Gurney Voice: +1 415 225 5579 > > "All that I will do, has been done, All that I have, has not." > From owner-freebsd-current@FreeBSD.ORG Tue Mar 12 19:11:01 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 8F2A091F; Tue, 12 Mar 2013 19:11:01 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: from mail-ia0-x231.google.com (mail-ia0-x231.google.com [IPv6:2607:f8b0:4001:c02::231]) by mx1.freebsd.org (Postfix) with ESMTP id 312A8688; Tue, 12 Mar 2013 19:11:01 +0000 (UTC) Received: by mail-ia0-f177.google.com with SMTP id y25so180865iay.36 for ; Tue, 12 Mar 2013 12:11:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:sender:date:from:to:cc:subject:message-id:references :mime-version:content-type:content-disposition:in-reply-to :user-agent; bh=snufR6p8yF7vbCwSlbGNBgnOa+YhksQGwg0YM27pmZ4=; b=BQtvoOQUogYLPYUKJ1A+Oo44v9+IPr4tyk1EHthT4DI3/NtsCpSMQsoFYCpv2aL2oi zRFP9QFgTaL5xdW5uYmvW1YJ0hWddNTqTjQeip1wpWLz3fvVgn5JEA4US+qIknmmnPlr OrSYLs1xqSHWU4d9qxNnJOmleBKE5x9gZghry5gen7OL9S9FBAd3oTY2ws0R/ErtOYa4 XEKghD+9xjWfeKtJ6vpxerMX9o4ChqzHaInIOjC7ZK+Yqg8Rwx3O4KQTLyPMcLlw+yFG vSDaj8g3xYnW9NswbrE811sm5ioqg2YN285ybmXLwMKkMk2v6N4bI4fQZ1S7LkRzJLcG ibiQ== X-Received: by 10.50.195.134 with SMTP id ie6mr12734330igc.6.1363115460868; Tue, 12 Mar 2013 12:11:00 -0700 (PDT) Received: from oddish.sandvine.com ([64.7.137.182]) by mx.google.com with ESMTPS id ih1sm21170795igc.3.2013.03.12.12.10.58 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 12 Mar 2013 12:11:00 -0700 (PDT) Sender: Mark Johnston Date: Tue, 12 Mar 2013 15:10:53 -0400 From: Mark Johnston To: Steve Kargl Subject: Re: CURRENT: lang/gcc fails to build on CURRENT with error: configure: error: no usable dependency style found Message-ID: <20130312191053.GB3372@oddish.sandvine.com> References: <513B56E8.2060702@zedat.fu-berlin.de> <8F5265A6-396A-426F-A3F8-EFD44D167313@FreeBSD.org> <20130309233930.GA95285@troutmask.apl.washington.edu> <513DAF4F.50602@FreeBSD.org> <20130311131318.GA57506@troutmask.apl.washington.edu> <513DD90F.2090700@daemonic.se> <513E0656.7000601@FreeBSD.org> <1UF7wX-000BVL-0y@internal.tormail.org> <0C12B97B-F096-4EB3-8225-07D590F4E34B@FreeBSD.org> <20130311211851.GA12143@troutmask.apl.washington.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20130311211851.GA12143@troutmask.apl.washington.edu> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: Dimitry Andric , FreeBSD Current , =?iso-8859-1?Q?G=E1bor_K=F6vesd=E1n?= , freebsd-ports@freebsd.org, Niclas Zeising , "O. Hartmann" , Mark Johnston , Jan Beich X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Mar 2013 19:11:01 -0000 On Mon, Mar 11, 2013 at 02:18:51PM -0700, Steve Kargl wrote: > On Mon, Mar 11, 2013 at 10:05:47PM +0100, Dimitry Andric wrote: > > On 2013-03-11 20:00, Jan Beich wrote: > > > Dimitry Andric writes: > > > > > >> $ echo 'sub/foo.barx' | grep sub/foo.bar > > >> $ echo $? > > >> 1 > > > > > > $ echo 'sub/foo.barx' | env -i grep sub/foo.bar > > > $ echo 'sub/foolbarx' | env -i grep sub/foo.bar > > > $ echo 'sub/foo.barx' | env -i grep 'sub/foo\.bar' > > > sub/foo.barx > > > $ echo 'sub/foo.barx' | env -i grep -o sub/foo.bar > > > sub/foo.bar > > > $ echo 'sub/foo.barx' | env -i grep --color=no sub/foo.bar > > > sub/foo.barx > > > > > > A buggy shortcut? > > > > No, after some digging in and debugging of the bsdgrep code, I > > found out it is a regression caused by r246917, which is a fix > > for "bin/175213: [patch] bsdgrep(1) segfaults upon malicious input". > > If you revert it, bsdgrep starts working correctly again. > > First, I can report that bootstrapping gcc-4.8.0 works if I use > gnugrep instead of bsdgrep. The above explains why I had previously > seen the failure as I was using an older bsdgrep. > > Second, an apology is owed to the clang gang as I attributed the > problem to clang as it showed up on my system after converted > everything over to clang. > > > I think it would be best to back out r246917 for now, until the > > regression can be fixed properly. Having bsdgrep crash is bad, > > but not returning any results while it should is even worse... > > I tend to agree with your assessment that r246817 should be > reverted, because I hit this issue in configure scripts and > there is a large amount of software that uses autotool for > configuration. Sorry about this, I will revert it and revisit the problem. I've been using bsdgrep by default for a while and somehow haven't run into this. -Mark From owner-freebsd-current@FreeBSD.ORG Tue Mar 12 20:16:35 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 7EECDCA2 for ; Tue, 12 Mar 2013 20:16:35 +0000 (UTC) (envelope-from erdgeist@erdgeist.org) Received: from elektropost.org (elektropost.org [217.13.206.130]) by mx1.freebsd.org (Postfix) with ESMTP id BD0E23DA for ; Tue, 12 Mar 2013 20:16:34 +0000 (UTC) Received: (qmail 58471 invoked from network); 12 Mar 2013 20:16:33 -0000 Received: from elektropost.org (HELO elektropost.org) (erdgeist@erdgeist.org) by elektropost.org with CAMELLIA256-SHA encrypted SMTP; 12 Mar 2013 20:16:33 -0000 Message-ID: <513F8D20.2050707@erdgeist.org> Date: Tue, 12 Mar 2013 21:16:32 +0100 From: Dirk Engling User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130216 Thunderbird/17.0.3 MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: pidfile_open incorrectly returns EAGAIN when pidfile is locked X-Enigmail-Version: 1.5.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Mar 2013 20:16:35 -0000 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 | O_TRUNC | O_CLOEXEC | O_NONBLOCK, mode); fails when another daemon holds the lock and flopen sets errno to EAGAIN, the check 4 lines below in if (errno == EWOULDBLOCK && pidptr != NULL) { means that the pidfile_read is never executed. This results in my second daemon receiving an EAGAIN which clearly was meant to report a race condition between two daemons starting at the same time and the first one not yet finishing pidfile_write. The expected behavior would be to set errno to EEXIST, even if no pidptr was passed. Regards, erdgeist From owner-freebsd-current@FreeBSD.ORG Tue Mar 12 21:11:58 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id DE35C8AD; Tue, 12 Mar 2013 21:11:58 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from bigwig.baldwin.cx (bigknife-pt.tunnel.tserv9.chi1.ipv6.he.net [IPv6:2001:470:1f10:75::2]) by mx1.freebsd.org (Postfix) with ESMTP id B8A35850; Tue, 12 Mar 2013 21:11:58 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 1872FB917; Tue, 12 Mar 2013 17:11:58 -0400 (EDT) From: John Baldwin To: freebsd-current@freebsd.org, d@delphij.net Subject: Re: FULL_PREEMPTION Date: Tue, 12 Mar 2013 08:56:37 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110714-p25; KDE/4.5.5; amd64; ; ) References: <513A26B9.7060305@delphij.net> In-Reply-To: <513A26B9.7060305@delphij.net> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201303120856.37443.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Tue, 12 Mar 2013 17:11:58 -0400 (EDT) Cc: Andriy Gapon X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Mar 2013 21:11:58 -0000 On Friday, March 08, 2013 12:58:17 pm Xin Li wrote: > Hi, > > I have seen a few posts from Andriy as as well as the PC-BSD default > that for desktop systems, kern.sched.preempt_thresh=224 would improve > responsiveness. Looking at the code, it seems that this is equivalent > to compiling the kernel with FULL_PREEMPTION. > > The sys/conf/NOTES says, however: > > # FULL_PREEMPTION instructs the kernel to preempt non-realtime kernel > # threads. Its sole use is to expose race conditions and other > # bugs during development. Enabling this option will reduce > # performance and increase the frequency of kernel panics by > # design. If you aren't sure that you need it then you don't. > # Relies on the PREEMPTION option. DON'T TURN THIS ON. > > Despite the possibility of exposing race conditions as well as > potentially hurting throughput because of (possibly more) context > switching, is it considered as a goal that we should support it? If > so, should we enable it on -CURRENT? No, it's only ever intended as a debugging aid. I suppose we could consider enabling it in HEAD only just as we do with INVARIANTS, etc. However, when it was added it was never intended to be used for production. -- John Baldwin From owner-freebsd-current@FreeBSD.ORG Tue Mar 12 22:16:45 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 8DA3D87C for ; Tue, 12 Mar 2013 22:16:45 +0000 (UTC) (envelope-from bdrewery@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 70995B53 for ; Tue, 12 Mar 2013 22:16:45 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.6/8.14.6) with ESMTP id r2CMGipA093590 for ; Tue, 12 Mar 2013 22:16:44 GMT (envelope-from bdrewery@freefall.freebsd.org) Received: (from bdrewery@localhost) by freefall.freebsd.org (8.14.6/8.14.6/Submit) id r2CMGiOv093587 for freebsd-current@freebsd.org; Tue, 12 Mar 2013 22:16:44 GMT (envelope-from bdrewery) Received: (qmail 14915 invoked from network); 12 Mar 2013 17:16:42 -0500 Received: from unknown (HELO ?192.168.0.74?) (freebsd@shatow.net@74.94.87.209) by sweb.xzibition.com with ESMTPA; 12 Mar 2013 17:16:42 -0500 Message-ID: <513FA948.5020808@FreeBSD.org> Date: Tue, 12 Mar 2013 17:16:40 -0500 From: Bryan Drewery Organization: FreeBSD User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130215 Thunderbird/17.0.3 MIME-Version: 1.0 To: "O. Hartmann" Subject: 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 References: <513AFBE3.8070506@zedat.fu-berlin.de> <1362915848.11970.4.camel@thor.walstatt.dyndns.org> In-Reply-To: <1362915848.11970.4.camel@thor.walstatt.dyndns.org> X-Enigmail-Version: 1.5.1 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="----enig2EPUFGQXIRGJOANDDERMV" Cc: FreeBSD Current , freebsd-ports@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Mar 2013 22:16:45 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) ------enig2EPUFGQXIRGJOANDDERMV Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable 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: >=20 > =3D=3D=3D> Cleaning for openldap-sasl-client-2.4.33_1 > =3D=3D=3D>>> Waiting on fetch & checksum for net/openldap24-sasl-client= <<<=3D=3D=3D >=20 > =3D=3D=3D> openldap-sasl-client-2.4.33_1 conflicts with installed > package(s):=20 > openldap-sasl-client-2.4.33_1 > /usr/local > net/openldap24-sasl-client >=20 > They install files into the same place. > You may want to stop build with Ctrl + C. >=20 >=20 > This looks weird tome, since how can /usr/local/ be a port? >=20 > My update tool is ports-mgmt/portmaster. >=20 > Regards, >=20 > Oliver >=20 I have just committed a fix to the ports tree for this. --=20 Regards, Bryan Drewery bdrewery@freenode/EFNet ------enig2EPUFGQXIRGJOANDDERMV Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJRP6lMAAoJEG54KsA8mwz51y8QAIK+UxYsxjCaDHV7lVnSUwAM NtjJobUUtBgz9UJnKH0eA7HPSvkDIcm+sIIJfbLXmhIR2ChjUymH8zjr/OlXL6vb /nxvp+dtOo5JRMO84/fkitQSb53ZzggsN99vuROHkWg1LymPaRF40SpllpW4apoV Kbho7H02TSdWEj227Y3AbtwMHkfcqK4zSAgkx8EL65+TlZCtS2Of7K6lYMqpCB9W J4WfQdRQ/kYgPuTfIU+zF+9rkOOmRxnyyMLnzSw87GR4QmbZCKvBvt5Ts6fYqp6r KM4wwT2osiUA3IeO8sfq53Dt3YEGM8zSppf97LhCc5dBLWrck/GNX/tEupw/+Rad MAuFBrOA7pj7rDL1cA1CZjphtYb11QHjUetXK+tdAz5P23SU46ABKnetCONZTGIx Bmf4DbhCo6UoUqLGGmPoTSqLoMw9XU4Ll41RqZN63nfBf1EW6Nj1B3YvygPQCMAt Vh8KnJOjGs8xW/bx+lfqcMYuwuzQjL57BARSwvAyjU1AWWabo7uEbw1Z5olLHGA0 CfwH1zXwhA5W7GqYNIi1O7BGez+glDvpdGxZPtXOSmQnugiKoIBsi6caEKw0RrKh EobZZ9DahxI9kR6BoQOBS6wD9o8zay/cP7wAIrYVwi1VwAlJzoMxOEmJUh/tCE2S rqC/ZcKuRWVpUjXB3QxR =3ts8 -----END PGP SIGNATURE----- ------enig2EPUFGQXIRGJOANDDERMV-- From owner-freebsd-current@FreeBSD.ORG Tue Mar 12 22:44:14 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id BD7DD74 for ; Tue, 12 Mar 2013 22:44:14 +0000 (UTC) (envelope-from uzimac@da3m0n8t3r.com) Received: from z.umatar.com (z.umatar.com [66.135.39.87]) by mx1.freebsd.org (Postfix) with ESMTP id 84F85DD9 for ; Tue, 12 Mar 2013 22:44:14 +0000 (UTC) Received: from z.umatar.com (localhost [127.0.0.1]) by z.umatar.com (8.14.5/8.14.3) with ESMTP id r2CMi8uY003084 for ; Tue, 12 Mar 2013 15:44:08 -0700 (PDT) (envelope-from uzimac@da3m0n8t3r.com) Received: (from uzimac@localhost) by z.umatar.com (8.14.5/8.14.3/Submit) id r2CMi8Q6003083 for freebsd-current@freebsd.org; Tue, 12 Mar 2013 15:44:08 -0700 (PDT) (envelope-from uzimac@da3m0n8t3r.com) X-Authentication-Warning: z.umatar.com: uzimac set sender to uzimac@da3m0n8t3r.com using -f From: "Waitman Gobble" Subject: libtool/ld shared libraries To: FreeBSD Current Message-Id: <1363128248.3078@da3m0n8t3r.com> X-Originating-IP: 70.90.171.37 X-Mailer: Usermin 1.510 Date: Tue, 12 Mar 2013 15:44:08 -0700 (PDT) MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="bound1363128248" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Mar 2013 22:44:14 -0000 This is a multi-part message in MIME format. --bound1363128248 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 7bit Hi, I'm trying to figure out why my 10.0-CURRENT machine is having issues producing *.so shared library... [659] > uname -a FreeBSD dx.burplex.com 10.0-CURRENT FreeBSD 10.0-CURRENT #0 r248165: Mon Mar 11 18:20:30 PDT 2013 root@dx.burplex.com:/usr/obj/usr/src/sys/FURAHA amd64 checking dynamic linker characteristics... no checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... yes checking if libtool supports shared libraries... no creating libtool appending configuration tag "CXX" to libtool checking whether the clang++ linker (/usr/bin/ld) supports shared libraries... no checking whether the clang++ linker (/usr/bin/ld) supports shared libraries... no checking dynamic linker characteristics... no checking how to hardcode library paths into programs... unsupported [660] > pkg version | grep libtool libtool-2.4.2 = (as example) my 9.1-STABLE machine is working OK. # uname -a FreeBSD do.burplex.com 9.1-STABLE FreeBSD 9.1-STABLE #0 r246923M: Sun Feb 17 18:30:48 PST 2013 da3m0n8t3r@do.burplex.com:/usr/obj/usr/src/sys/KAGISO amd64 checking whether the cc linker (/usr/bin/ld) supports shared libraries... yes checking dynamic linker characteristics... freebsd9.1 ld.so checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... yes checking if libtool supports shared libraries... yes # pkg_info | grep libtool libtool-2.4.2 Generic shared library support script I kind of remember running into this in the past but I can't recall the solution.. Help or pointers appreciated! Thank you, -- Waitman Gobble San Jose California USA --bound1363128248-- From owner-freebsd-current@FreeBSD.ORG Tue Mar 12 23:05:10 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 71F3E9A8 for ; Tue, 12 Mar 2013 23:05:10 +0000 (UTC) (envelope-from jim.harris@gmail.com) Received: from mail-ee0-f42.google.com (mail-ee0-f42.google.com [74.125.83.42]) by mx1.freebsd.org (Postfix) with ESMTP id D37A5F10 for ; Tue, 12 Mar 2013 23:05:09 +0000 (UTC) Received: by mail-ee0-f42.google.com with SMTP id b47so171761eek.15 for ; Tue, 12 Mar 2013 16:05:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=EnT7Uw8VkWV8rWXZiF5MSM9halzom62POTQtCJpYjAE=; b=FmHnCzdESkWZHOpPG4iPjPFQonvkCSznoyFmtJ9KeGuOIduOW8gqYa+C66+Wmkm2g9 7Wwy4fgVVilZz9jO+6giK/E11sQ7M5QBVZpYbk79xa24r9lU79jAKsgipBdcD103GU/E U2pMnv3Sr3E5vKv8h9IhtRMBTAp8YdGIfDhbdAIeqHjEMBsssMftYpvxa8feEQF+HD1o yKgBBvQGw6uScipxbAlmqZehL5zzxg8zntA+SvISi+d+1clfQ6AHtC1zdGgIN8wEaPIx u7DpLxcBZkSJ8z7NI4pEQRvgaMwm1nlay58/4SPfLAmyiDJavLtrFPuK/kSKRji38Wrh bKFA== MIME-Version: 1.0 X-Received: by 10.14.3.133 with SMTP id 5mr52295800eeh.43.1363129508483; Tue, 12 Mar 2013 16:05:08 -0700 (PDT) Sender: jim.harris@gmail.com Received: by 10.14.96.129 with HTTP; Tue, 12 Mar 2013 16:05:08 -0700 (PDT) In-Reply-To: <1363128248.3078@da3m0n8t3r.com> References: <1363128248.3078@da3m0n8t3r.com> Date: Tue, 12 Mar 2013 16:05:08 -0700 X-Google-Sender-Auth: Q9xblXFhAbRO7GzXE3PwdnJpiig Message-ID: Subject: Re: libtool/ld shared libraries From: Jim Harris To: Waitman Gobble Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: FreeBSD Current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 12 Mar 2013 23:05:10 -0000 On Tue, Mar 12, 2013 at 3:44 PM, Waitman Gobble wrote: > > Hi, > > I'm trying to figure out why my 10.0-CURRENT machine is having issues > producing *.so shared library... > > [659] > uname -a > FreeBSD dx.burplex.com 10.0-CURRENT FreeBSD 10.0-CURRENT #0 r248165: Mon > Mar 11 18:20:30 PDT 2013 root@dx.burplex.com:/usr/obj/usr/src/sys/FURAHA > amd64 > > checking dynamic linker characteristics... no > checking how to hardcode library paths into programs... immediate > checking whether stripping libraries is possible... yes > checking if libtool supports shared libraries... no > > creating libtool > appending configuration tag "CXX" to libtool > checking whether the clang++ linker (/usr/bin/ld) supports shared > libraries... no > checking whether the clang++ linker (/usr/bin/ld) supports shared > libraries... no > checking dynamic linker characteristics... no > checking how to hardcode library paths into programs... unsupported > > [660] > pkg version | grep libtool > libtool-2.4.2 = > > > > (as example) my 9.1-STABLE machine is working OK. > > # uname -a > FreeBSD do.burplex.com 9.1-STABLE FreeBSD 9.1-STABLE #0 r246923M: Sun Feb > 17 18:30:48 PST 2013 da3m0n8t3r@do.burplex.com:/usr/obj/usr/src/sys/KAGISO > amd64 > > checking whether the cc linker (/usr/bin/ld) supports shared libraries... > yes > checking dynamic linker characteristics... freebsd9.1 ld.so > checking how to hardcode library paths into programs... immediate > checking whether stripping libraries is possible... yes > checking if libtool supports shared libraries... yes > > # pkg_info | grep libtool > libtool-2.4.2 Generic shared library support script > > > > I kind of remember running into this in the past but I can't recall the > solution.. > > I've run into this before too. I believe it was the configure script interpreting "FreeBSD 10" as "FreeBSD 1", and therefore thinking shared library support wasn't available. Regards, -Jim From owner-freebsd-current@FreeBSD.ORG Wed Mar 13 00:17:48 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 1E5E1C04; Wed, 13 Mar 2013 00:17:48 +0000 (UTC) (envelope-from uzimac@da3m0n8t3r.com) Received: from z.umatar.com (z.umatar.com [66.135.39.87]) by mx1.freebsd.org (Postfix) with ESMTP id 926CC2D8; Wed, 13 Mar 2013 00:17:47 +0000 (UTC) Received: from z.umatar.com (localhost [127.0.0.1]) by z.umatar.com (8.14.5/8.14.3) with ESMTP id r2D0HkQx052116; Tue, 12 Mar 2013 17:17:46 -0700 (PDT) (envelope-from uzimac@da3m0n8t3r.com) Received: (from uzimac@localhost) by z.umatar.com (8.14.5/8.14.3/Submit) id r2D0HkAY052115; Tue, 12 Mar 2013 17:17:46 -0700 (PDT) (envelope-from uzimac@da3m0n8t3r.com) X-Authentication-Warning: z.umatar.com: uzimac set sender to uzimac@da3m0n8t3r.com using -f From: "Waitman Gobble" Subject: Re: libtool/ld shared libraries To: Jim Harris Message-Id: <1363133866.52110@da3m0n8t3r.com> X-Originating-IP: 70.90.171.37 X-Mailer: Usermin 1.510 In-Reply-To: Date: Tue, 12 Mar 2013 17:17:46 -0700 (PDT) MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="bound1363133866" Cc: FreeBSD Current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Mar 2013 00:17:48 -0000 This is a multi-part message in MIME format. --bound1363133866 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Jim Harris wrote .. > On Tue, Mar 12, 2013 at 3:44 PM, Waitman Gobble wrote: > > > > > Hi, > > > > I'm trying to figure out why my 10.0-CURRENT machine is having issues > > producing *.so shared library... > > > > [659] > uname -a > > FreeBSD dx.burplex.com 10.0-CURRENT FreeBSD 10.0-CURRENT #0 r248165: Mon > > Mar 11 18:20:30 PDT 2013 root@dx.burplex.com:/usr/obj/usr/src/sys/FURAHA > > amd64 > > > > checking dynamic linker characteristics... no > > checking how to hardcode library paths into programs... immediate > > checking whether stripping libraries is possible... yes > > checking if libtool supports shared libraries... no > > > > creating libtool > > appending configuration tag "CXX" to libtool > > checking whether the clang++ linker (/usr/bin/ld) supports shared > > libraries... no > > checking whether the clang++ linker (/usr/bin/ld) supports shared > > libraries... no > > checking dynamic linker characteristics... no > > checking how to hardcode library paths into programs... unsupported > > > > [660] > pkg version | grep libtool > > libtool-2.4.2 = > > > > > > > > (as example) my 9.1-STABLE machine is working OK. > > > > # uname -a > > FreeBSD do.burplex.com 9.1-STABLE FreeBSD 9.1-STABLE #0 r246923M: Sun Feb > > 17 18:30:48 PST 2013 da3m0n8t3r@do.burplex.com:/usr/obj/usr/src/sys/KAGISO > > amd64 > > > > checking whether the cc linker (/usr/bin/ld) supports shared libraries... > > yes > > checking dynamic linker characteristics... freebsd9.1 ld.so > > checking how to hardcode library paths into programs... immediate > > checking whether stripping libraries is possible... yes > > checking if libtool supports shared libraries... yes > > > > # pkg_info | grep libtool > > libtool-2.4.2 Generic shared library support script > > > > > > > > I kind of remember running into this in the past but I can't recall the > > solution.. > > > > > I've run into this before too. I believe it was the configure script > interpreting "FreeBSD 10" as "FreeBSD 1", and therefore thinking shared > library support wasn't available. > > Regards, > > -Jim > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" oh, that's exactly what's going on, thanks! ie, freebsd1*) dynamic_linker=no ;; ld_shlibs_CXX=no etc -- Waitman Gobble San Jose California USA --bound1363133866-- From owner-freebsd-current@FreeBSD.ORG Wed Mar 13 01:10:22 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id B8E20AFE for ; Wed, 13 Mar 2013 01:10:22 +0000 (UTC) (envelope-from jmg@h2.funkthat.com) Received: from h2.funkthat.com (gate2.funkthat.com [208.87.223.18]) by mx1.freebsd.org (Postfix) with ESMTP id 9292A6D2 for ; Wed, 13 Mar 2013 01:10:22 +0000 (UTC) Received: from h2.funkthat.com (localhost [127.0.0.1]) by h2.funkthat.com (8.14.3/8.14.3) with ESMTP id r2D1ALV5070140 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 12 Mar 2013 18:10:21 -0700 (PDT) (envelope-from jmg@h2.funkthat.com) Received: (from jmg@localhost) by h2.funkthat.com (8.14.3/8.14.3/Submit) id r2D1ALjC070139; Tue, 12 Mar 2013 18:10:21 -0700 (PDT) (envelope-from jmg) Date: Tue, 12 Mar 2013 18:10:21 -0700 From: John-Mark Gurney To: Yasir hussan Subject: Re: using multiple interfaces for same Network Card Message-ID: <20130313011021.GC88785@funkthat.com> Mail-Followup-To: Yasir hussan , Current References: <20130312183947.GB88785@funkthat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i X-Operating-System: FreeBSD 7.2-RELEASE i386 X-PGP-Fingerprint: 54BA 873B 6515 3F10 9E88 9322 9CB1 8F74 6D3F A396 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html X-to-the-FBI-CIA-and-NSA: HI! HOW YA DOIN? can i haz chizburger? X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.2.2 (h2.funkthat.com [127.0.0.1]); Tue, 12 Mar 2013 18:10:21 -0700 (PDT) Cc: Current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Mar 2013 01:10:22 -0000 Yasir hussan wrote this message on Wed, Mar 13, 2013 at 00:03 +0500: > U say u were successfully using vlans by vlandev in FreeBSD , Can u send > me exact commands and configuration which u were applying, It will be very > helpful for me... This is how I use it on my router... These lines are in rc.conf, from a 9.0 box: ifconfig_npe1="inet 192.168.x.x netmask 255.255.255.0" vlans_npe1="12 13" ifconfig_npe1_12="inet 10.y.y.y netmask 255.255.255.0" ifconfig_npe1_13="inet z.z.z.z netmask 255.255.255.0" ifconfig_npe1_13_alias0="inet z.z.z.z2 netmask 255.255.255.255" Replace npe1 w/ the interface you are using.. And obviously replace the ip's w/ the correct ones... My internet connection is connected to vlan 13 on npe1, and I have two ip addressess associated w/ that interface... I believe you can do "/etc/rc.d/netif start" if you don't want to reboot, but I've never done that.. I've just rebooted, since this is my router and I want to make sure it comes up... Good luck... > On Tue, Mar 12, 2013 at 11:39 PM, John-Mark Gurney wrote: > > > Yasir hussan wrote this message on Tue, Mar 12, 2013 at 23:32 +0500: > > > 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-command/i > > > tried to use it as > > > > > > ifconfig vlan11 create 10.10.11.1 255.255.255.0 vlan 11 vlandev arge0 > > > ifconfig vlan12 create 10.10.12.1 255.255.255.0 vlan 12 vlandev arge0 > > > ifconfig vlan13 create 10.10.13.1 255.255.255.0 vlan 13 vlandev arge0 > > > ifconfig vlan14 create 10.10.14.1 255.255.255.0 vlan 14 vlandev arge0 > > > > > > i was expecting that it will create interfaces which will work under > > arge0, > > > and will able to ping from any pc, Does any one have used it, kindly > > guide > > > me about it > > > > vlans are a way to add different broadcast domains.. You need to have a > > vlan capable switch/machine connected and properly configured... If you > > plug in the machine to a normal switch, and the other machine isn't vlan > > aware not much will happen... > > > > Now if you configure your machine to route (net.inet.ip.forwarding) and > > setup the pc w/ the proper routing tables, you'll be able to ping the > > machines... > > > > If this doesn't help, please talk w/ a local network engineer to help > > you configure your network properly... > > > > I'm succussfully using FreeBSD with both vlans, and aliases (multiple > > ips on a single interface aka broadcast domain)... > > > > > On Tue, Mar 12, 2013 at 5:06 PM, Ian FREISLICH wrote: > > > > > > > Yasir hussan wrote: > > > > > Thanks for notic but all the elebration was for make alias on one > > > > > interface but i want to have multiple interface, i can no where that > > > > > some one would have tring to creating new interfaces and using them, > > > > > or may be i am missing something, just send its solution if have, > > > > > solution should be for > > > > > > > > I still think you're confusing Linux semantics with FreeBSD semantics. > > > > > > > > On linux you would have: > > > > eth0 Link encap:Ethernet HWaddr 00:1E:C9:53:0B:61 > > > > inet addr:10.0.0.1 Bcast:10.0.0.255 Mask:255.255.255.0 > > > > inet6 addr: fe80::21e:c9ff:fe53:b61/64 Scope:Link > > > > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > > > > RX packets:211328068 errors:0 dropped:0 overruns:0 frame:0 > > > > TX packets:368394006 errors:0 dropped:0 overruns:0 carrier:0 > > > > collisions:0 txqueuelen:1000 > > > > RX bytes:34065846811 (31.7 GiB) TX bytes:476377525764 (443.6 > > > > GiB) > > > > Interrupt:169 Memory:e6000000-e6011100 > > > > > > > > eth0:1 Link encap:Ethernet HWaddr 00:1E:C9:53:0B:61 > > > > inet addr:10.0.1.1 Bcast:10.0.1.255 Mask:255.255.255.0 > > > > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > > > > Interrupt:169 Memory:e6000000-e6011100 > > > > > > > > > > > > On FreeBSD you would have: > > > > > > > > re0: flags=8843 metric 0 mtu > > 1500 > > > > > > > > > > options=8209b > > > > ether 54:04:a6:96:0c:1e > > > > inet 10.0.0.1 netmask 0xffffff00 broadcast 10.0.0.255 > > > > inet 10.0.1.1 netmask 0xffffff00 broadcast 10.0.1.255 > > > > media: Ethernet autoselect (1000baseT ) > > > > status: active > > > > > > > > These are both the same thing. Is there any particular reason that > > > > you want multiple interfaces? I can't see a use for it beyond "it's > > > > what I'm used to seeing" unless they're VLAN interfaces. -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." From owner-freebsd-current@FreeBSD.ORG Wed Mar 13 01:24:54 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id B5DFCD0F for ; Wed, 13 Mar 2013 01:24:54 +0000 (UTC) (envelope-from Benjamin.Close@clearchain.com) Received: from mail.clearchain.com (leo.clearchain.com [199.73.29.74]) by mx1.freebsd.org (Postfix) with ESMTP id 4460874F for ; Wed, 13 Mar 2013 01:24:52 +0000 (UTC) Received: from [192.168.155.199] ([121.91.33.21]) (authenticated bits=0) by mail.clearchain.com (8.14.5/8.14.5) with ESMTP id r2D0w6N4046016 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Wed, 13 Mar 2013 11:28:15 +1030 (CST) (envelope-from Benjamin.Close@clearchain.com) Message-ID: <513FCF2D.1000006@clearchain.com> Date: Wed, 13 Mar 2013 11:28:21 +1030 From: Benjamin Close User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130307 Thunderbird/17.0.4 MIME-Version: 1.0 To: Ian FREISLICH Subject: Re: using multiple interfaces for same Network Card References: In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (mail.clearchain.com [199.73.29.74]); Wed, 13 Mar 2013 11:28:17 +1030 (CST) Cc: Tom Evans , Yasir hussan , Current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Mar 2013 01:24:54 -0000 On 12/03/2013 22:36, Ian FREISLICH wrote: > Yasir hussan wrote: >> Thanks for notic but all the elebration was for make alias on one >> interface but i want to have multiple interface, i can no where that >> some one would have tring to creating new interfaces and using them, >> or may be i am missing something, just send its solution if have, >> solution should be for > I still think you're confusing Linux semantics with FreeBSD semantics. > > On linux you would have: > eth0 Link encap:Ethernet HWaddr 00:1E:C9:53:0B:61 > inet addr:10.0.0.1 Bcast:10.0.0.255 Mask:255.255.255.0 > inet6 addr: fe80::21e:c9ff:fe53:b61/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:211328068 errors:0 dropped:0 overruns:0 frame:0 > TX packets:368394006 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:34065846811 (31.7 GiB) TX bytes:476377525764 (443.6 GiB) > Interrupt:169 Memory:e6000000-e6011100 > > eth0:1 Link encap:Ethernet HWaddr 00:1E:C9:53:0B:61 > inet addr:10.0.1.1 Bcast:10.0.1.255 Mask:255.255.255.0 > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > Interrupt:169 Memory:e6000000-e6011100 > > > On FreeBSD you would have: > > re0: flags=8843 metric 0 mtu 1500 > options=8209b > ether 54:04:a6:96:0c:1e > inet 10.0.0.1 netmask 0xffffff00 broadcast 10.0.0.255 > inet 10.0.1.1 netmask 0xffffff00 broadcast 10.0.1.255 > media: Ethernet autoselect (1000baseT ) > status: active > > These are both the same thing. Is there any particular reason that > you want multiple interfaces? I can't see a use for it beyond "it's > what I'm used to seeing" unless they're VLAN interfaces. > > Ian > Just a comment on the aliases vs virtual interfaces. Having used both aliases and virtual interfaces, there is use cases which have always been easier under Linux than FreeBSD due to the virtual interface. Once case is firewall rules that follow the device. Let me explain. Lets say under freebsd I setup two lans on the same card using aliases and a switch that is NOT vlan capable (ie home adsl modem, some other unmanaged switch). ifconfig re0 172.16.1.1 ifconfig re0 alias 192.168.1.1 The firewall rules require the net to be used rather than an interface since the interface handles more than one lan. ie (pf style): pass in quick on re0 from 192.168.1.1/24 to any Linux makes this easier: ifconfig eth0 172.16.1.1 ifconfig eth0:1 192.168.1.1 pass in quick on eth0:1 from any to any Whilst it's a minor difference, I can shift the device IP and my firewall rules automatically follow. This is just one case where having a virtual device make things easier vs aliases. Cheers, Benjamin From owner-freebsd-current@FreeBSD.ORG Wed Mar 13 01:35:45 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 82AF3F43 for ; Wed, 13 Mar 2013 01:35:45 +0000 (UTC) (envelope-from ml@my.gd) Received: from mail-wg0-f51.google.com (mail-wg0-f51.google.com [74.125.82.51]) by mx1.freebsd.org (Postfix) with ESMTP id 0E1AA7BD for ; Wed, 13 Mar 2013 01:35:44 +0000 (UTC) Received: by mail-wg0-f51.google.com with SMTP id 8so478474wgl.30 for ; Tue, 12 Mar 2013 18:35:43 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:x-mailer:from:subject:date :to:x-gm-message-state; bh=S+faIdRSKy8lT9VRmyfk3gooG/6lnEQmDTQZ8yXwLnk=; b=gZHv+S4TwBXhnOCIRRnng57kLmdbOCoF1zV4+FLnXAcIVmm/UmOdlLN8fGbvm2szxH e5363ecBhMOT4ePo/trCnLXWT+rpS2/1TmV+/87mFzET/64GkPZhSN21wvAQuTB+AFVG MA09y936W9sepRCRasSzuXe0t7dlsVRo2jzUCRUo0i2TfaMihL+JcnpQbaVCIKG0Oq0Y EzOSRs1JLBhg/nPy2Qv1GQZxNva7wWu966nkamnKv0Z9juhmVtYIMkZQVNFpFo2NBrI8 JwfKMT4JsqkiYrbVSi29kt5McTb5PouYQrjZsvdrivskMo1wKi0oabzX/KwxjkbpU5dI +fEA== X-Received: by 10.180.75.110 with SMTP id b14mr23793475wiw.21.1363138543513; Tue, 12 Mar 2013 18:35:43 -0700 (PDT) Received: from ?IPv6:2a01:e35:8a58:2600:dd05:db5b:e25e:ec7c? ([2a01:e35:8a58:2600:dd05:db5b:e25e:ec7c]) by mx.google.com with ESMTPS id k5sm27801728wiy.5.2013.03.12.18.35.41 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 12 Mar 2013 18:35:42 -0700 (PDT) References: <513FCF2D.1000006@clearchain.com> Mime-Version: 1.0 (1.0) In-Reply-To: <513FCF2D.1000006@clearchain.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Message-Id: <0619561E-E343-4190-9C42-5BC5396D47E1@my.gd> X-Mailer: iPhone Mail (10B144) From: Damien Fleuriot Subject: Re: using multiple interfaces for same Network Card Date: Wed, 13 Mar 2013 02:35:22 +0100 To: Benjamin Close X-Gm-Message-State: ALoCoQnQDA0199fuJ3DhUveva7QyB26+VA4uNHFvCLB8DDlTBb0VRiX/Qi1BhQKeJE4/SnF/rcJT Cc: Tom Evans , Yasir hussan , Ian FREISLICH , Current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Mar 2013 01:35:45 -0000 On 13 Mar 2013, at 01:58, Benjamin Close wro= te: > On 12/03/2013 22:36, Ian FREISLICH wrote: >> Yasir hussan wrote: >>> Thanks for notic but all the elebration was for make alias on one >>> interface but i want to have multiple interface, i can no where that >>> some one would have tring to creating new interfaces and using them, >>> or may be i am missing something, just send its solution if have, >>> solution should be for >> I still think you're confusing Linux semantics with FreeBSD semantics. >>=20 >> On linux you would have: >> eth0 Link encap:Ethernet HWaddr 00:1E:C9:53:0B:61 >> inet addr:10.0.0.1 Bcast:10.0.0.255 Mask:255.255.255.0 >> inet6 addr: fe80::21e:c9ff:fe53:b61/64 Scope:Link >> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 >> RX packets:211328068 errors:0 dropped:0 overruns:0 frame:0 >> TX packets:368394006 errors:0 dropped:0 overruns:0 carrier:0 >> collisions:0 txqueuelen:1000 >> RX bytes:34065846811 (31.7 GiB) TX bytes:476377525764 (443.6 G= iB) >> Interrupt:169 Memory:e6000000-e6011100 >>=20 >> eth0:1 Link encap:Ethernet HWaddr 00:1E:C9:53:0B:61 >> inet addr:10.0.1.1 Bcast:10.0.1.255 Mask:255.255.255.0 >> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 >> Interrupt:169 Memory:e6000000-e6011100 >>=20 >>=20 >> On FreeBSD you would have: >>=20 >> re0: flags=3D8843 metric 0 mtu 15= 00 >> options=3D8209b >> ether 54:04:a6:96:0c:1e >> inet 10.0.0.1 netmask 0xffffff00 broadcast 10.0.0.255 >> inet 10.0.1.1 netmask 0xffffff00 broadcast 10.0.1.255 >> media: Ethernet autoselect (1000baseT ) >> status: active >>=20 >> These are both the same thing. Is there any particular reason that >> you want multiple interfaces? I can't see a use for it beyond "it's >> what I'm used to seeing" unless they're VLAN interfaces. >>=20 >> Ian >=20 > Just a comment on the aliases vs virtual interfaces. Having used both alia= ses and virtual interfaces, there is use cases which have always been easie= r under Linux than FreeBSD due to the virtual interface. >=20 > Once case is firewall rules that follow the device. > Let me explain. >=20 > Lets say under freebsd I setup two lans on the same card using aliases and= a switch that is NOT vlan capable (ie home adsl modem, some other unmanaged= switch). > ifconfig re0 172.16.1.1 > ifconfig re0 alias 192.168.1.1 >=20 > The firewall rules require the net to be used rather than an interface sin= ce the interface handles more than one lan. > ie (pf style): >=20 > pass in quick on re0 from 192.168.1.1/24 to any >=20 > Linux makes this easier: >=20 > ifconfig eth0 172.16.1.1 > ifconfig eth0:1 192.168.1.1 >=20 > pass in quick on eth0:1 from any to any >=20 > Whilst it's a minor difference, I can shift the device IP and my firewall r= ules automatically follow. This is just one case where having a virtual devi= ce make things easier=20 I fail to see a use case where having 2 networks on a single interface would= be useful, let alone desirable. This isn't to say your reasoning behind the PF rules thing is incorrect, all= I'm saying is "oh god no" to this. By the way I'm wondering if this would work: re0 has IPs 192.168.0.1234, 10.0.0.1/24 pass in quick on re0 inet from re0:1:network re0:network =3D 192.168.0.0/24 re0:1 =3D 10.0.0.1/32 I wonder if re0:1:network would expand to 10.0.0.0/24...= From owner-freebsd-current@FreeBSD.ORG Wed Mar 13 07:55:12 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 9351D180; Wed, 13 Mar 2013 07:55:12 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) by mx1.freebsd.org (Postfix) with ESMTP id 5067A9F3; Wed, 13 Mar 2013 07:55:12 +0000 (UTC) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost1.zedat.fu-berlin.de (Exim 4.80.1) with esmtp (envelope-from ) id <1UFgWl-003UyE-5i>; Wed, 13 Mar 2013 08:55:11 +0100 Received: from e178012080.adsl.alicedsl.de ([85.178.12.80] helo=[192.168.0.128]) by inpost2.zedat.fu-berlin.de (Exim 4.80.1) with esmtpsa (envelope-from ) id <1UFgWl-0000UH-0R>; Wed, 13 Mar 2013 08:55:11 +0100 Subject: 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 From: "O. Hartmann" To: Bryan Drewery In-Reply-To: <513FA948.5020808@FreeBSD.org> References: <513AFBE3.8070506@zedat.fu-berlin.de> <1362915848.11970.4.camel@thor.walstatt.dyndns.org> <513FA948.5020808@FreeBSD.org> Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-1oVvJL0DVfxswojX2nlB" Organization: FU Berlin Date: Wed, 13 Mar 2013 08:55:10 +0100 Message-ID: <1363161310.1607.1.camel@thor.walstatt.dyndns.org> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port X-Originating-IP: 85.178.12.80 Cc: FreeBSD Current , freebsd-ports@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Mar 2013 07:55:12 -0000 --=-1oVvJL0DVfxswojX2nlB Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable 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: > >=20 > > =3D=3D=3D> Cleaning for openldap-sasl-client-2.4.33_1 > > =3D=3D=3D>>> Waiting on fetch & checksum for net/openldap24-sasl-client= <<<=3D=3D=3D > >=20 > > =3D=3D=3D> openldap-sasl-client-2.4.33_1 conflicts with installed > > package(s):=20 > > openldap-sasl-client-2.4.33_1 > > /usr/local > > net/openldap24-sasl-client > >=20 > > They install files into the same place. > > You may want to stop build with Ctrl + C. > >=20 > >=20 > > This looks weird tome, since how can /usr/local/ be a port? > >=20 > > My update tool is ports-mgmt/portmaster. > >=20 > > Regards, > >=20 > > Oliver > >=20 >=20 > I have just committed a fix to the ports tree for this. >=20 >=20 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: 314034 for me. Regards, Oliver --=-1oVvJL0DVfxswojX2nlB Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iQEcBAABAgAGBQJRQDDeAAoJEOgBcD7A/5N8O2MH/3pYIPp8mlRxcdGl5gT1TRO7 k9oQ9nVtRRBv+w3xCqphqNn0jOXDpE9UaGlcSqzi2QDxUaTAdnUwceBmE4xoMYW6 EjueuuMnfsLlM8PlGF0oZdiKNI08ZmEp9qfBazdjiMmnTK3JJ33SErPVoJSKs63H lV3b4EmBJaki0fuVZOPB7U0yIpShdX2CFHDqxKzjk0NTvyrc0JKMCnVIp2jL3hCi YiFy8jsDudCPHN0acVjEMDY4/B3/77r1dSetbAuI074VUadV+BkV1IHUkDTESEGV NyJO9q5Zb0SUwVmDLTKlchHe+TwsXKYHjcknDFkYizqFPR9TYjSiv/3h3QssgQ0= =1kas -----END PGP SIGNATURE----- --=-1oVvJL0DVfxswojX2nlB-- From owner-freebsd-current@FreeBSD.ORG Wed Mar 13 09:49:45 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id E290D5C4 for ; Wed, 13 Mar 2013 09:49:45 +0000 (UTC) (envelope-from bdrewery@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 9B60D156 for ; Wed, 13 Mar 2013 09:49:45 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.6/8.14.6) with ESMTP id r2D9njA4026028 for ; Wed, 13 Mar 2013 09:49:45 GMT (envelope-from bdrewery@freefall.freebsd.org) Received: (from bdrewery@localhost) by freefall.freebsd.org (8.14.6/8.14.6/Submit) id r2D9njTf026025 for freebsd-current@freebsd.org; Wed, 13 Mar 2013 09:49:45 GMT (envelope-from bdrewery) Received: (qmail 99523 invoked from network); 13 Mar 2013 04:49:43 -0500 Received: from unknown (HELO ?10.10.0.24?) (freebsd@shatow.net@10.10.0.24) by sweb.xzibition.com with ESMTPA; 13 Mar 2013 04:49:43 -0500 Message-ID: <51404BA0.5050006@FreeBSD.org> Date: Wed, 13 Mar 2013 04:49:20 -0500 From: Bryan Drewery Organization: FreeBSD User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130215 Thunderbird/17.0.3 MIME-Version: 1.0 To: "O. Hartmann" Subject: 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 References: <513AFBE3.8070506@zedat.fu-berlin.de> <1362915848.11970.4.camel@thor.walstatt.dyndns.org> <513FA948.5020808@FreeBSD.org> <1363161310.1607.1.camel@thor.walstatt.dyndns.org> In-Reply-To: <1363161310.1607.1.camel@thor.walstatt.dyndns.org> X-Enigmail-Version: 1.5.1 OpenPGP: id=3C9B0CF9; url=http://www.shatow.net/bryan/bryan.asc Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="----enig2LNMFPVGLBUTJPLGPHEHD" Cc: FreeBSD Current , freebsd-ports@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Mar 2013 09:49:45 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) ------enig2LNMFPVGLBUTJPLGPHEHD Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable 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. >> >> >=20 > Hello. >=20 > 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 >=20 > Revision: 314034 >=20 > for me. >=20 > Regards, >=20 > Oliver >=20 >=20 The change was to Mk/bsd.port.mk in r314004 --=20 Regards, Bryan Drewery bdrewery@freenode/EFNet ------enig2LNMFPVGLBUTJPLGPHEHD Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJRQEuwAAoJEG54KsA8mwz54fwP/256gqLagKlIvCQgETJYZMaT O9FmWQlTRUhvSfRWv1VjuwPBUvKc2wGevZJf61dhhe58NxJC+JcB6mb3xr4dLwIm sbdKB8c22L+q8h2bEvMbkWQnNMdIOzcIIBntQuccHBzyIt94qjG853BO4Iwzi7fi 6xmGoejy9vACylxEj19U/7smDXLWsXJh4Nd7pDaTlY3mmtRLtxwP/bzyOxySxndQ ylqCoMvikrSKUkOQ6vlZsupXACp15TN14x1D9SGlg7nBSpy5CmmZk8rFcNQ9Y90c w9lKyuw4ZOeNPGu3YoZOl+cNbtjZD0jYbdHpEGS+ZLY67l8XbcNQY2vIobZjT3g7 2D2ofjOa7ir0QdO1H/ujGUp9oLSFHIAWKo+83BhegIR3zpQt37HvIQw4fApnFUCE ZW/LwGt4AwXuuS43ffIwB8YSPkcgJIYO8WsU3C9EMw1wg72XZTMpdsXfsVrekZDb O0lXGoq5INEa187ODVV7nl10KkuSF9Nm4XZgzO4riVpBd9g1UhrgcaSYskCPh2gn 034rbU74Dy6ULwKr/dqawZ6N4eOYGzLc3ioxKM+jnoC61NNRSw25HLLtVQLes5rl qB9c5Hvgh2uZV633RuWVP8qBV9FfiVBTcQzdqAhD/mPr3zvll7yolImDffoapmWd w12s0t9SH9RrKMzK3OPO =KwV5 -----END PGP SIGNATURE----- ------enig2LNMFPVGLBUTJPLGPHEHD-- From owner-freebsd-current@FreeBSD.ORG Wed Mar 13 08:30:26 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id AA9E2D1A for ; Wed, 13 Mar 2013 08:30:26 +0000 (UTC) (envelope-from ianf@cloudseed.co.za) Received: from zcs04.jnb1.cloudseed.co.za (zcs04.jnb1.cloudseed.co.za [41.154.0.161]) by mx1.freebsd.org (Postfix) with ESMTP id 1E246C2D for ; Wed, 13 Mar 2013 08:30:25 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by zcs04.jnb1.cloudseed.co.za (Postfix) with ESMTP id 3DD9A2A82F0F; Wed, 13 Mar 2013 10:21:18 +0200 (SAST) X-Virus-Scanned: amavisd-new at zcs04.jnb1.cloudseed.co.za Received: from zcs04.jnb1.cloudseed.co.za ([127.0.0.1]) by localhost (zcs04.jnb1.cloudseed.co.za [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RAyP61nphCOl; Wed, 13 Mar 2013 10:21:17 +0200 (SAST) Received: from clue.co.za (unknown [197.87.27.46]) by zcs04.jnb1.cloudseed.co.za (Postfix) with ESMTPSA id 47F172A829F1; Wed, 13 Mar 2013 10:21:17 +0200 (SAST) Received: from localhost ([127.0.0.1] helo=zen.clue.co.za) by clue.co.za with esmtp (Exim 4.80.1 (FreeBSD)) (envelope-from ) id 1UFgw0-0000fa-LX; Wed, 13 Mar 2013 10:21:16 +0200 To: Yasir hussan From: Ian FREISLICH Subject: Re: using multiple interfaces for same Network Card In-Reply-To: References: X-Attribution: BOFH Date: Wed, 13 Mar 2013 10:21:15 +0200 Message-Id: X-Mailman-Approved-At: Wed, 13 Mar 2013 11:27:35 +0000 Cc: Tom Evans , Current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Mar 2013 08:30:26 -0000 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 255.255.255.0 vlan 11 vlandev arge0 > ifconfig vlan12 create 10.10.12.1 255.255.255.0 vlan 12 vlandev arge0 > ifconfig vlan13 create 10.10.13.1 255.255.255.0 vlan 13 vlandev arge0 > ifconfig vlan14 create 10.10.14.1 255.255.255.0 vlan 14 vlandev arge0 you want: ifconfig vlan11 create vlan 11 vlandev arge0 inet 10.10.11.1 netmask 255.255.255.0 or ifconfig vlan11 create vlan 11 vlandev arge0 inet 10.10.11.1/24 Ian -- Ian Freislich From owner-freebsd-current@FreeBSD.ORG Wed Mar 13 12:21:39 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 72FAB6EE; Wed, 13 Mar 2013 12:21:39 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) by mx1.freebsd.org (Postfix) with ESMTP id 30E45D8B; Wed, 13 Mar 2013 12:21:39 +0000 (UTC) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost1.zedat.fu-berlin.de (Exim 4.80.1) with esmtp (envelope-from ) id <1UFkgc-000uJ0-4z>; Wed, 13 Mar 2013 13:21:38 +0100 Received: from e178007100.adsl.alicedsl.de ([85.178.7.100] helo=[192.168.0.128]) by inpost2.zedat.fu-berlin.de (Exim 4.80.1) with esmtpsa (envelope-from ) id <1UFkgc-000NfR-00>; Wed, 13 Mar 2013 13:21:38 +0100 Subject: 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 From: "O. Hartmann" To: Bryan Drewery In-Reply-To: <51404BA0.5050006@FreeBSD.org> References: <513AFBE3.8070506@zedat.fu-berlin.de> <1362915848.11970.4.camel@thor.walstatt.dyndns.org> <513FA948.5020808@FreeBSD.org> <1363161310.1607.1.camel@thor.walstatt.dyndns.org> <51404BA0.5050006@FreeBSD.org> Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-DbQ/awr7o2YpL8MFtOtt" Date: Wed, 13 Mar 2013 13:21:37 +0100 Message-ID: <1363177297.1607.33.camel@thor.walstatt.dyndns.org> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port X-Originating-IP: 85.178.7.100 Cc: FreeBSD Current , freebsd-ports@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Mar 2013 12:21:39 -0000 --=-DbQ/awr7o2YpL8MFtOtt Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable 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. > >> > >> > >=20 > > Hello. > >=20 > > 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 > >=20 > > Revision: 314034 > >=20 > > for me. > >=20 > > Regards, > >=20 > > Oliver > >=20 > >=20 >=20 > The change was to Mk/bsd.port.mk in r314004 >=20 Well, even with clearing the build and the directory and getting it from scratch, on FreeBSD 10-CURRENT I have still the same error. make rmconfig doesn't change anything, also. --=-DbQ/awr7o2YpL8MFtOtt Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iQEcBAABAgAGBQJRQG9RAAoJEOgBcD7A/5N8QCMIAJ/xCdEF/cfFQwh0sdjISFhs MG98g05tDfSwAaIOD8YFF+MLWqCSLNP/RaiMr/mLtyksFyo/nhKacZZuvj/BPtbU 4cb0p//oVLTQZ7EcYtBeWtxUs06bPa1Psm8Z9+6nq41DiOHq6LDWy2MV2B8tsqfX FImPU235ZMCrVph1c5e83g4UTFhN17b26xbIimdbTpQr/Amjvy6rqA44+db0hHdL 9q4JpZLgxuGX6gU8MovrQifsfFXpXmdtU02ryi8RtgBpAzO5YJ7X3oLgyuYhurwT 8b1ZoHBkG5UPe44kTizWnZ6fdIxKXRAGfRWQ57Hz2CMpkdtuCnSSU/Dpa1hTHjE= =OmlN -----END PGP SIGNATURE----- --=-DbQ/awr7o2YpL8MFtOtt-- From owner-freebsd-current@FreeBSD.ORG Wed Mar 13 12:26:44 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 3EA26B5E for ; Wed, 13 Mar 2013 12:26:44 +0000 (UTC) (envelope-from bdrewery@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 2174FDF3 for ; Wed, 13 Mar 2013 12:26:44 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.6/8.14.6) with ESMTP id r2DCQh26056210 for ; Wed, 13 Mar 2013 12:26:43 GMT (envelope-from bdrewery@freefall.freebsd.org) Received: (from bdrewery@localhost) by freefall.freebsd.org (8.14.6/8.14.6/Submit) id r2DCQhad056207 for freebsd-current@freebsd.org; Wed, 13 Mar 2013 12:26:43 GMT (envelope-from bdrewery) Received: (qmail 11587 invoked from network); 13 Mar 2013 07:26:41 -0500 Received: from unknown (HELO ?10.10.0.24?) (freebsd@shatow.net@10.10.0.24) by sweb.xzibition.com with ESMTPA; 13 Mar 2013 07:26:41 -0500 Message-ID: <5140707A.5000008@FreeBSD.org> Date: Wed, 13 Mar 2013 07:26:34 -0500 From: Bryan Drewery Organization: FreeBSD User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130215 Thunderbird/17.0.3 MIME-Version: 1.0 To: "O. Hartmann" Subject: 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 References: <513AFBE3.8070506@zedat.fu-berlin.de> <1362915848.11970.4.camel@thor.walstatt.dyndns.org> <513FA948.5020808@FreeBSD.org> <1363161310.1607.1.camel@thor.walstatt.dyndns.org> <51404BA0.5050006@FreeBSD.org> <1363177297.1607.33.camel@thor.walstatt.dyndns.org> In-Reply-To: <1363177297.1607.33.camel@thor.walstatt.dyndns.org> X-Enigmail-Version: 1.5.1 OpenPGP: id=3C9B0CF9; url=http://www.shatow.net/bryan/bryan.asc Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="----enig2ULXTVFXCOUEJBDPWNBGO" Cc: FreeBSD Current , freebsd-ports@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Mar 2013 12:26:44 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) ------enig2ULXTVFXCOUEJBDPWNBGO Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable 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 tree a few minutes ago and can not se= e >>> any changes by now. The port's tree is at >>> >>> Revision: 314034 >>> >>> for me. >>> >>> Regards, >>> >>> Oliver >>> >>> >> >> The change was to Mk/bsd.port.mk in r314004 >> >=20 > Well, even with clearing the build and the directory and getting it fro= m > scratch, on FreeBSD 10-CURRENT I have still the same error. >=20 > make rmconfig >=20 > doesn't change anything, also. >=20 It's not a problem with net/openldap24-sasl-client specifically. It's a /usr/ports/Mk problem. Run: portsnap fetch extract Mk This will update your Mk files to the latest. --=20 Regards, Bryan Drewery bdrewery@freenode/EFNet ------enig2ULXTVFXCOUEJBDPWNBGO Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJRQHB6AAoJEG54KsA8mwz5vpAP/0ON3PFjaSXtazZgif+V7j5Y vvrDxmvOt8r0JvaQNpGfj1YR1vZIv44EZLy0j8m9/5sqKuE87rPIeIkGOxIcbtLu ZaWFgx+UnLPg5scWv5INH1WPA8dYZZg5cSygSZD3HWzeaMzW4BX6ox2yGWuQBvMv QRkBN2Q7b3i7pEv/Xkrmnnutqk7YqtQGP953L8VIBPTb+vIEhcdPmLi7YKVptJbX rrJGJto8Q0agkVZTju4u5lW6DKEBILdnNQGIj9iMDYn48RqirQFviuA8S6EA/XEs Mc8UCZfPa+Ap8abDkTNM3A7COFcp2fpOBycZ2NiKa+3heg6ghQms6eXnMGnu/zw4 JlIeJpFsfFUQHRbydgmkkSAtwOCmFcDmhDNTNukD9rVxNFb2kQUMIlAvW/j0sUoR nkZ6opxbHB5W5MfWkxZb79pqm0+UnWZlzeg66we+5VOcsGsgIRq9oQtne32GoZ0o ar82d+sI/iUkHc4uQbtXzwbS8u+uWowGez7xh8lK0odj9CvlsJKb5PnWF+R5UnxL DFkZwcDYB73iksObEq8CsvAugvd4Gpn34t3zEROcbeucyJ5GjsZSt0Bk0JsdYJE8 5qktSwGBOD2pNc50epqWFm4aK06hjd5YVGyfPjon79fcSArTVe2sePOHha8rmlP/ 2fgk/SZc/01YQ781trYt =WNYI -----END PGP SIGNATURE----- ------enig2ULXTVFXCOUEJBDPWNBGO-- From owner-freebsd-current@FreeBSD.ORG Wed Mar 13 12:57:59 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 101F47BA for ; Wed, 13 Mar 2013 12:57:59 +0000 (UTC) (envelope-from cvs-src@yandex.ru) Received: from forward4h.mail.yandex.net (forward4h.mail.yandex.net [IPv6:2a02:6b8:0:f05::4]) by mx1.freebsd.org (Postfix) with ESMTP id BCB96B5 for ; Wed, 13 Mar 2013 12:57:57 +0000 (UTC) Received: from smtp1h.mail.yandex.net (smtp1h.mail.yandex.net [84.201.187.144]) by forward4h.mail.yandex.net (Yandex) with ESMTP id 5CB2C1B2226C for ; Wed, 13 Mar 2013 16:57:56 +0400 (MSK) Received: from smtp1h.mail.yandex.net (localhost [127.0.0.1]) by smtp1h.mail.yandex.net (Yandex) with ESMTP id 2CE4C1340362 for ; Wed, 13 Mar 2013 16:57:56 +0400 (MSK) Received: from ctsoff2.webstroy.ru (ctsoff2.webstroy.ru [213.27.12.78]) by smtp1h.mail.yandex.net (nwsmtp/Yandex) with ESMTP id vthWABBk-vthupNpr; Wed, 13 Mar 2013 16:57:55 +0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1363179476; bh=dDEbGg5Kbq70gtAdpPNsKVGl1oiQ7LoaT/lLSQ6ZKEg=; h=Message-ID:Date:From:User-Agent:MIME-Version:To:Subject: Content-Type:Content-Transfer-Encoding; b=qKSn3Nr/Q70F4voRRPYgkRRCALueEQwoe7/Q1l2zELD0zDC7/ETiQW7KUuuege2Zf p3zRCvLdYVa7RZFuoWbzMRFOVXYTkwnTQU8gEz0BjLa14WWZuSqLbO5LaL0J/Xk0Wo b096Y6yrpwLxodQOi8AqYpf/2BNs2UVtTv2XPEXU= Message-ID: <514077C0.4010700@yandex.ru> Date: Wed, 13 Mar 2013 16:57:36 +0400 From: Ruslan Makhmatkhanov User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130311 Thunderbird/17.0.4 MIME-Version: 1.0 To: FreeBSD Current Subject: sysinstall and graid mirror on 9.1R Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Mar 2013 12:57:59 -0000 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 access to that system, so will not be able to test anything. But it's 100% reproducible in that configuration. -- Regards, Ruslan Tinderboxing kills... the drives. From owner-freebsd-current@FreeBSD.ORG Wed Mar 13 13:31:10 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 6024D181 for ; Wed, 13 Mar 2013 13:31:10 +0000 (UTC) (envelope-from m.e.sanliturk@gmail.com) Received: from mail-vb0-x236.google.com (mail-vb0-x236.google.com [IPv6:2607:f8b0:400c:c02::236]) by mx1.freebsd.org (Postfix) with ESMTP id 162982F9 for ; Wed, 13 Mar 2013 13:31:10 +0000 (UTC) Received: by mail-vb0-f54.google.com with SMTP id l1so488982vba.13 for ; Wed, 13 Mar 2013 06:31:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=qgHyAODxwmpnAYP849tzN8fAK1IiPRDWIi7PnozSGCM=; b=wM+JhThYnKNgLoQdhVaqduCjlOhdVByhA6P3+kaAXVLLaYXoBPHP0Sz/ZCITKJ21Sb MvtFgNMmhYxjXrnqy56sW35qL7yye9xH60p5apbDpGZS9/zHKYwpaGEs2m3GD5Nqt6xj 47flDMuabAcz9G4ZRy1EVX1i6oM/1Y9v9NvZktR2T884TQXIWNkCeQGiMYVIWvt8EMdV rbm43owGmqf/2CnuvgoT5G9xfuwS+woWr+UKP2j8yCY7Q1zK/q7/BM4fpHMLJBeINrXV UjoRewKZ9hubtYp3vx8O4755Pfs2fqLmU00t7SxB4/SGBVQoeAvdksFZcx29ESkce3e8 VjCQ== MIME-Version: 1.0 X-Received: by 10.220.40.9 with SMTP id i9mr7962873vce.23.1363181469660; Wed, 13 Mar 2013 06:31:09 -0700 (PDT) Received: by 10.58.220.33 with HTTP; Wed, 13 Mar 2013 06:31:09 -0700 (PDT) Date: Wed, 13 Mar 2013 06:31:09 -0700 Message-ID: Subject: Network Card Configuration during Installation From: Mehmet Erol Sanliturk To: FreeBSD Current Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Mar 2013 13:31:10 -0000 Dear All , Yesterday ( March 11 , 2013 ) I have installed latest Current snapshot . During network card installation http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/bsdinstall-post.html ( 2.9.2 Configuring Network Interfaces ) there is NO any loop to configure multiple network cards ( Figure 2-22. Choose a Network Interface ) . At the end , I wanted to configure an additional network card from menu : 2.9.7 Final Configuration ( Figure 2-43. Final Configuration ) It seems that this additional network configuration step is DESTROYING the previously selected another network card configuration , and replacing it by the newly selected ( different ) network card configuration . I did not select third network card configuration , therefore I do not know whether last selected one replaces the previous selected one or not . After the installation , the installed system is not operational any more if the erased network card definition is required . My suggestion : Please : Introduce a loop into step ( 2.9.2 Configuring Network Interfaces ) ( Figure 2-22. Choose a Network Interface ) Make network configuration steps additive if a different network card is selected. If the same network card is selected , in this case , retain last selected definition by erasing previous definition for the same network card . Thank you very much . Mehmet Erol Sanliturk From owner-freebsd-current@FreeBSD.ORG Wed Mar 13 13:55:43 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 0C0F232A; Wed, 13 Mar 2013 13:55:43 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) by mx1.freebsd.org (Postfix) with ESMTP id BDE4B72B; Wed, 13 Mar 2013 13:55:42 +0000 (UTC) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost1.zedat.fu-berlin.de (Exim 4.80.1) with esmtp (envelope-from ) id <1UFm9d-001Wcv-H2>; Wed, 13 Mar 2013 14:55:41 +0100 Received: from e178007100.adsl.alicedsl.de ([85.178.7.100] helo=[192.168.0.128]) by inpost2.zedat.fu-berlin.de (Exim 4.80.1) with esmtpsa (envelope-from ) id <1UFm9d-000Vb6-DE>; Wed, 13 Mar 2013 14:55:41 +0100 Subject: 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 From: "O. Hartmann" To: Bryan Drewery In-Reply-To: <5140707A.5000008@FreeBSD.org> References: <513AFBE3.8070506@zedat.fu-berlin.de> <1362915848.11970.4.camel@thor.walstatt.dyndns.org> <513FA948.5020808@FreeBSD.org> <1363161310.1607.1.camel@thor.walstatt.dyndns.org> <51404BA0.5050006@FreeBSD.org> <1363177297.1607.33.camel@thor.walstatt.dyndns.org> <5140707A.5000008@FreeBSD.org> Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-MSJTjq8x6s57DxRScI0n" Date: Wed, 13 Mar 2013 14:55:40 +0100 Message-ID: <1363182940.1607.35.camel@thor.walstatt.dyndns.org> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port X-Originating-IP: 85.178.7.100 Cc: FreeBSD Current , freebsd-ports@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Mar 2013 13:55:43 -0000 --=-MSJTjq8x6s57DxRScI0n Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable 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 ports tree for this. > >>>> > >>>> > >>> > >>> Hello. > >>> > >>> Well, I just updated the port's tree a few minutes ago and can not se= e > >>> any changes by now. The port's tree is at > >>> > >>> Revision: 314034 > >>> > >>> for me. > >>> > >>> Regards, > >>> > >>> Oliver > >>> > >>> > >> > >> The change was to Mk/bsd.port.mk in r314004 > >> > >=20 > > Well, even with clearing the build and the directory and getting it fro= m > > scratch, on FreeBSD 10-CURRENT I have still the same error. > >=20 > > make rmconfig > >=20 > > doesn't change anything, also. > >=20 >=20 > It's not a problem with net/openldap24-sasl-client specifically. It's a > /usr/ports/Mk problem. >=20 > Run: portsnap fetch extract Mk >=20 > This will update your Mk files to the latest. >=20 I'm with "svn update", so I did this and it seems not to be changed. Still no further update in the exspected file nor does the port build properly. I think I have to wait? Oliver --=-MSJTjq8x6s57DxRScI0n Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iQEcBAABAgAGBQJRQIVcAAoJEOgBcD7A/5N8csEH/1L+0K7JSdiyve4cnt66TURA 0nS3DLYxec5RBl7zyIyB/cd2LllK/h+JPAbCvevsYy7/HNdfpDD04+TDVeKC2jQy dg9nAwVdexG/KduQI8lc45TJVsoQBVl2GXHfcL2J518Xt7GjOVWXLbJRdy8oG3qR YOe2wnkL370vWbi5KCm+fOWCY+AVPa30H0RP9a6s63+PTFrEzPVWmcNeLMYuMznp gcb6QrVlFYiPQQlki0ULCKrwtGI8yWsiQQPFfmEAhAXmuSdPx7ETKhn8PV4X6vj8 xmWvFPeRZgRTVPMuJOjJJt6Ms6ZGg1gDJScrYi5jBQdKzc7LtmPp7gLu7floSaw= =1RsM -----END PGP SIGNATURE----- --=-MSJTjq8x6s57DxRScI0n-- From owner-freebsd-current@FreeBSD.ORG Wed Mar 13 14:55:01 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 675186A9 for ; Wed, 13 Mar 2013 14:55:01 +0000 (UTC) (envelope-from bdrewery@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 48EFCB90 for ; Wed, 13 Mar 2013 14:55:01 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.6/8.14.6) with ESMTP id r2DEt06x083230 for ; Wed, 13 Mar 2013 14:55:00 GMT (envelope-from bdrewery@freefall.freebsd.org) Received: (from bdrewery@localhost) by freefall.freebsd.org (8.14.6/8.14.6/Submit) id r2DEt0nc083226 for freebsd-current@freebsd.org; Wed, 13 Mar 2013 14:55:00 GMT (envelope-from bdrewery) Received: (qmail 53410 invoked from network); 13 Mar 2013 09:54:58 -0500 Received: from unknown (HELO ?192.168.0.74?) (freebsd@shatow.net@74.94.87.209) by sweb.xzibition.com with ESMTPA; 13 Mar 2013 09:54:58 -0500 Message-ID: <51409342.3070707@FreeBSD.org> Date: Wed, 13 Mar 2013 09:54:58 -0500 From: Bryan Drewery Organization: FreeBSD User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130215 Thunderbird/17.0.3 MIME-Version: 1.0 To: "O. Hartmann" Subject: 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 References: <513AFBE3.8070506@zedat.fu-berlin.de> <1362915848.11970.4.camel@thor.walstatt.dyndns.org> <513FA948.5020808@FreeBSD.org> <1363161310.1607.1.camel@thor.walstatt.dyndns.org> <51404BA0.5050006@FreeBSD.org> <1363177297.1607.33.camel@thor.walstatt.dyndns.org> <5140707A.5000008@FreeBSD.org> <1363182940.1607.35.camel@thor.walstatt.dyndns.org> In-Reply-To: <1363182940.1607.35.camel@thor.walstatt.dyndns.org> X-Enigmail-Version: 1.5.1 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="----enig2JRSVHLSLVJAWDEERXUGX" Cc: FreeBSD Current , freebsd-ports@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Mar 2013 14:55:01 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) ------enig2JRSVHLSLVJAWDEERXUGX Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable 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 have just committed a fix to the ports tree for this. >=20 > I'm with "svn update", so I did this and it seems not to be changed. > Still no further update in the exspected file nor does the port build > properly. >=20 > I think I have to wait? >=20 > Oliver >=20 Exactly what error are you getting now? The weird one showing "/usr/local" should be fixed. --=20 Regards, Bryan Drewery bdrewery@freenode/EFNet ------enig2JRSVHLSLVJAWDEERXUGX Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJRQJNCAAoJEG54KsA8mwz5JUYP/0c7jyY+H1CCp9Zito/ZC5qG 4O4Q2SNjKkSHU6kuS6k+BNOVOxA6XTTHV42EFFLt+j5vjU4eN2Y0iJkxGIZrg4HT uR+t0ikuetYmC8txZ4GnDooMg8A7p58PEsU56G+jbHn/+x28cMBW+BcPs9RAX+4Y kBTp1wIu8zFwtwdHlNJn0ZM6qKY40xiNc54wi3YiBZJGVZlWyo7mFJLfePjqDb9k 19oYo8cxrjvuuW7OiEODjfws/EOzkbKhCOaMV4fJzsCv+aArD/Qa8YY2FYyH+xES Qfl1Pr3EbWIMeAzpRwxMeUKWj8EjAiVMSYCrOamu0VAmR7ZVXcGJkyYJF+dkRwaK qRSlnIbF+DwwLQvXLCx6NHpxejhbzOqFvcyUkkW5RR/g91VxOQK9i8YSBFHvLG7u JLYge1Hc9+sYyylMilIIaBSwMEE3eYCcCbU6niLb7HwYn+taTWAzR+CmboNBlBjz OeuJGDxXENCdeC+SADMS/i1MufbOkvg1eadAOPhtonCi2z7Z5ok5ZLsEaH/7YOwE 5fAhhAuto2h29xxyJJEESt60sJEKA4cxHr0XxjgfQReCyBH3xWUtofAJ1XuIkkHS TQWhgpUi+6RBf1nUKYF/pICfztEHz+P3m5U8fpvanb2yTfCZAIIuHeUhX3UFh8MR pGcKZSkzqHKJ/nSa4QYX =tqDS -----END PGP SIGNATURE----- ------enig2JRSVHLSLVJAWDEERXUGX-- From owner-freebsd-current@FreeBSD.ORG Wed Mar 13 16:49:44 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id BC1C94D0; Wed, 13 Mar 2013 16:49:44 +0000 (UTC) (envelope-from ohartman@zedat.fu-berlin.de) Received: from outpost1.zedat.fu-berlin.de (outpost1.zedat.fu-berlin.de [130.133.4.66]) by mx1.freebsd.org (Postfix) with ESMTP id 74CF56E9; Wed, 13 Mar 2013 16:49:43 +0000 (UTC) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost1.zedat.fu-berlin.de (Exim 4.80.1) with esmtp (envelope-from ) id <1UFos3-002ZvE-3X>; Wed, 13 Mar 2013 17:49:43 +0100 Received: from telesto.geoinf.fu-berlin.de ([130.133.86.198]) by inpost2.zedat.fu-berlin.de (Exim 4.80.1) with esmtps (envelope-from ) id <1UFos3-000k6N-0U>; Wed, 13 Mar 2013 17:49:43 +0100 Subject: 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 From: "O. Hartmann" To: Bryan Drewery In-Reply-To: <51409342.3070707@FreeBSD.org> References: <513AFBE3.8070506@zedat.fu-berlin.de> <1362915848.11970.4.camel@thor.walstatt.dyndns.org> <513FA948.5020808@FreeBSD.org> <1363161310.1607.1.camel@thor.walstatt.dyndns.org> <51404BA0.5050006@FreeBSD.org> <1363177297.1607.33.camel@thor.walstatt.dyndns.org> <5140707A.5000008@FreeBSD.org> <1363182940.1607.35.camel@thor.walstatt.dyndns.org> <51409342.3070707@FreeBSD.org> Content-Type: text/plain; charset="us-ascii" Date: Wed, 13 Mar 2013 17:49:42 +0100 Message-ID: <1363193382.10588.2.camel@telesto> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit X-Originating-IP: 130.133.86.198 Cc: FreeBSD Current , freebsd-ports@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Mar 2013 16:49:44 -0000 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 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. > > > > I'm with "svn update", so I did this and it seems not to be changed. > > Still no further update in the exspected file nor does the port build > > properly. > > > > I think I have to wait? > > > > Oliver > > > > Exactly what error are you getting now? The weird one showing > "/usr/local" should be fixed. > Ups, I'm very sorry. I confused this PR with another serious PR that concerns build breakage of net/openldap24-server (which is different). The problems regarding to this reported problem (what we are talking about by now) has been gone so far. regards, Oliver From owner-freebsd-current@FreeBSD.ORG Wed Mar 13 17:51:16 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id EA27E90B for ; Wed, 13 Mar 2013 17:51:16 +0000 (UTC) (envelope-from rysto32@gmail.com) Received: from mail-ob0-x22e.google.com (mail-ob0-x22e.google.com [IPv6:2607:f8b0:4003:c01::22e]) by mx1.freebsd.org (Postfix) with ESMTP id BA588A63 for ; Wed, 13 Mar 2013 17:51:16 +0000 (UTC) Received: by mail-ob0-f174.google.com with SMTP id 16so1319847obc.33 for ; Wed, 13 Mar 2013 10:51:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=yHm+iqWcV5zhVCLCf0txwcLXb6Bgok/YFenYIAhP6Y4=; b=iFrLjAoR9hlU4cDAfGNRognWCm9p59r9AmLs893dPFeTCqMm81pioTk8I3WYMb5UHu fbnqxMLnOUo9/BsWz4Ecxdu9QAlATO5hlPPvMV9JwYZJi7uQMb/zNvPcsYd12nzzxX8P mfuIHoGa0oZK5fkqwMZQxNFncIPHHxgvqxCuEiaEbBEDo+od3X5HW1bJCJH8LJzSMFUo 1eEKEU95VVsXn4yx5J/SvBjZQtx6n/c1BUgQmm8V55QfNO49MgcVvQAeZJ66dW19IRDg fDetmZl1/S0wp/XNefsmb81S89Ve7x8SuxgF3czsQ0Vk4IbB4fapOqnjgOlfOReV8Cvi 9g5A== MIME-Version: 1.0 X-Received: by 10.60.18.233 with SMTP id z9mr16072101oed.19.1363195767930; Wed, 13 Mar 2013 10:29:27 -0700 (PDT) Received: by 10.76.109.236 with HTTP; Wed, 13 Mar 2013 10:29:27 -0700 (PDT) Date: Wed, 13 Mar 2013 13:29:27 -0400 Message-ID: Subject: [PATCH] Add support for Exar XR17V358IV to puc(4) From: Ryan Stone To: FreeBSD Current Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Mar 2013 17:51:17 -0000 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 tools for stressing out serial ports. I'm not sure if anybody has any suggestions for this. I plan to commit this within a couple of days if nobody has any objections. I'll try to get it MFC'ed for 8.4-RELEASE, The patch can be found here: http://people.freebsd.org/~rstone/patches/exar_358.diff I've also included it inline in case anybody wants to review it: commit d1da80b5c90b3ae5a44db165cb032e9e86d2c804 Author: Ryan Stone Date: Mon Mar 11 17:02:13 2013 -0400 add support for Exar XR17V358IV 8-port serial port to puc(4) diff --git a/sys/dev/puc/pucdata.c b/sys/dev/puc/pucdata.c index 6d933e8..34d6986 100644 --- a/sys/dev/puc/pucdata.c +++ b/sys/dev/puc/pucdata.c @@ -50,6 +50,7 @@ __FBSDID("$FreeBSD$"); static puc_config_f puc_config_amc; static puc_config_f puc_config_diva; static puc_config_f puc_config_exar; +static puc_config_f puc_config_exar_pcie; static puc_config_f puc_config_icbook; static puc_config_f puc_config_moxa; static puc_config_f puc_config_oxford_pcie; @@ -630,6 +631,13 @@ const struct puc_cfg puc_pci_devices[] = { PUC_PORT_8S, 0x10, 0, -1, }, + { 0x13a8, 0x0358, 0xffff, 0, + "Exar XR17V358IV", + 125000000, + PUC_PORT_8S, 0x10, 0, -1, + .config_function = puc_config_exar_pcie + }, + { 0x13fe, 0x1600, 0x1602, 0x0002, "Advantech PCI-1602", DEFAULT_RCLK * 8, @@ -1186,6 +1194,17 @@ puc_config_exar(struct puc_softc *sc, enum puc_cfg_cmd cmd, int port, } static int +puc_config_exar_pcie(struct puc_softc *sc, enum puc_cfg_cmd cmd, int port, + intptr_t *res) +{ + if (cmd == PUC_CFG_GET_OFS) { + *res = port * 0x400; + return (0); + } + return (ENXIO); +} + +static int puc_config_icbook(struct puc_softc *sc, enum puc_cfg_cmd cmd, int port, intptr_t *res) { From owner-freebsd-current@FreeBSD.ORG Wed Mar 13 19:20:29 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 583D364C; Wed, 13 Mar 2013 19:20:29 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from bigwig.baldwin.cx (bigknife-pt.tunnel.tserv9.chi1.ipv6.he.net [IPv6:2001:470:1f10:75::2]) by mx1.freebsd.org (Postfix) with ESMTP id DD28F124; Wed, 13 Mar 2013 19:20:28 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 33AACB91A; Wed, 13 Mar 2013 15:20:28 -0400 (EDT) From: John Baldwin To: freebsd-current@freebsd.org Subject: Re: pidfile_open incorrectly returns EAGAIN when pidfile is locked Date: Wed, 13 Mar 2013 11:18:36 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110714-p25; KDE/4.5.5; amd64; ; ) References: <513F8D20.2050707@erdgeist.org> In-Reply-To: <513F8D20.2050707@erdgeist.org> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201303131118.36811.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Wed, 13 Mar 2013 15:20:28 -0400 (EDT) Cc: Dirk Engling X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Mar 2013 19:20:29 -0000 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 | O_TRUNC | O_CLOEXEC | O_NONBLOCK, mode); > > fails when another daemon holds the lock and flopen sets errno to > EAGAIN, the check 4 lines below in > > if (errno == EWOULDBLOCK && pidptr != NULL) { > > means that the pidfile_read is never executed. > > This results in my second daemon receiving an EAGAIN which clearly was > meant to report a race condition between two daemons starting at the > same time and the first one not yet finishing pidfile_write. > > The expected behavior would be to set errno to EEXIST, even if no pidptr > was passed. Yes, I think it should actually perform the same logic even if pidptr is NULL of waiting for the other daemon to finish starting up. Something like this: Index: lib/libutil/pidfile.c =================================================================== --- pidfile.c (revision 248162) +++ pidfile.c (working copy) @@ -100,6 +100,7 @@ pidfile_open(const char *path, mode_t mode, pid_t struct stat sb; int error, fd, len, count; struct timespec rqtp; + pid_t dummy; pfh = malloc(sizeof(*pfh)); if (pfh == NULL) @@ -126,7 +127,9 @@ pidfile_open(const char *path, mode_t mode, pid_t fd = flopen(pfh->pf_path, O_WRONLY | O_CREAT | O_TRUNC | O_CLOEXEC | O_NONBLOCK, mode); if (fd == -1) { - if (errno == EWOULDBLOCK && pidptr != NULL) { + if (errno == EWOULDBLOCK) { + if (pidptr == NULL) + pidptr = &dummy; count = 20; rqtp.tv_sec = 0; rqtp.tv_nsec = 5000000; -- John Baldwin From owner-freebsd-current@FreeBSD.ORG Wed Mar 13 21:26:16 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id C937FDA5; Wed, 13 Mar 2013 21:26:16 +0000 (UTC) (envelope-from pawel@dawidek.net) Received: from mail.dawidek.net (garage.dawidek.net [91.121.88.72]) by mx1.freebsd.org (Postfix) with ESMTP id 8F0A8C22; Wed, 13 Mar 2013 21:26:16 +0000 (UTC) Received: from localhost (89-73-195-149.dynamic.chello.pl [89.73.195.149]) by mail.dawidek.net (Postfix) with ESMTPSA id 7D70E6AF; Wed, 13 Mar 2013 22:23:03 +0100 (CET) Date: Wed, 13 Mar 2013 22:27:50 +0100 From: Pawel Jakub Dawidek To: John Baldwin Subject: Re: pidfile_open incorrectly returns EAGAIN when pidfile is locked Message-ID: <20130313212750.GC1372@garage.freebsd.pl> References: <513F8D20.2050707@erdgeist.org> <201303131118.36811.jhb@freebsd.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="ncSAzJYg3Aa9+CRW" Content-Disposition: inline In-Reply-To: <201303131118.36811.jhb@freebsd.org> X-OS: FreeBSD 10.0-CURRENT amd64 User-Agent: Mutt/1.5.21 (2010-09-15) Cc: Dirk Engling , freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Mar 2013 21:26:16 -0000 --ncSAzJYg3Aa9+CRW Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable 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 pidfile_open > >=20 > > fd =3D flopen(pfh->pf_path, > > O_WRONLY | O_CREAT | O_TRUNC | O_CLOEXEC | O_NONBLOCK, mode); > >=20 > > fails when another daemon holds the lock and flopen sets errno to > > EAGAIN, the check 4 lines below in > >=20 > > if (errno =3D=3D EWOULDBLOCK && pidptr !=3D NULL) { > >=20 > > means that the pidfile_read is never executed. > >=20 > > This results in my second daemon receiving an EAGAIN which clearly was > > meant to report a race condition between two daemons starting at the > > same time and the first one not yet finishing pidfile_write. > >=20 > > The expected behavior would be to set errno to EEXIST, even if no pidptr > > was passed. >=20 > Yes, I think it should actually perform the same logic even if pidptr is > NULL of waiting for the other daemon to finish starting up. Something li= ke > this: >=20 > Index: lib/libutil/pidfile.c > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > --- pidfile.c (revision 248162) > +++ pidfile.c (working copy) > @@ -100,6 +100,7 @@ pidfile_open(const char *path, mode_t mode, pid_t > struct stat sb; > int error, fd, len, count; > struct timespec rqtp; > + pid_t dummy; > =20 > pfh =3D malloc(sizeof(*pfh)); > if (pfh =3D=3D NULL) > @@ -126,7 +127,9 @@ pidfile_open(const char *path, mode_t mode, pid_t > fd =3D flopen(pfh->pf_path, > O_WRONLY | O_CREAT | O_TRUNC | O_CLOEXEC | O_NONBLOCK, mode); > if (fd =3D=3D -1) { > - if (errno =3D=3D EWOULDBLOCK && pidptr !=3D NULL) { > + if (errno =3D=3D EWOULDBLOCK) { > + if (pidptr =3D=3D NULL) > + pidptr =3D &dummy; > count =3D 20; > rqtp.tv_sec =3D 0; > rqtp.tv_nsec =3D 5000000; I agree EEXIST should be returned, but I don't like reading existing pidfile (including waiting for the other process to write its PID) just to throw read PID away. How about this patch? http://people.freebsd.org/~pjd/patches/pidfile.c.patch --=20 Pawel Jakub Dawidek http://www.wheelsystems.com FreeBSD committer http://www.FreeBSD.org Am I Evil? Yes, I Am! http://tupytaj.pl --ncSAzJYg3Aa9+CRW Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEARECAAYFAlFA71YACgkQForvXbEpPzRVuACeNxSf6DagXiOt8Dv5/qaT4vbN /RwAmwaTqTGScNqfgQIk7yOcPuJoNRsp =OQHV -----END PGP SIGNATURE----- --ncSAzJYg3Aa9+CRW-- From owner-freebsd-current@FreeBSD.ORG Wed Mar 13 21:59:27 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 41A5EDEE for ; Wed, 13 Mar 2013 21:59:27 +0000 (UTC) (envelope-from erdgeist@erdgeist.org) Received: from elektropost.org (elektropost.org [217.13.206.130]) by mx1.freebsd.org (Postfix) with ESMTP id 960C5F95 for ; Wed, 13 Mar 2013 21:59:26 +0000 (UTC) Received: (qmail 4149 invoked from network); 13 Mar 2013 21:59:18 -0000 Received: from elektropost.org (HELO elektropost.org) (erdgeist@erdgeist.org) by elektropost.org with AES256-SHA encrypted SMTP; 13 Mar 2013 21:59:18 -0000 Date: Wed, 13 Mar 2013 22:59:17 +0100 (CET) From: Dirk Engling To: Pawel Jakub Dawidek Subject: Re: pidfile_open incorrectly returns EAGAIN when pidfile is locked In-Reply-To: <20130313212750.GC1372@garage.freebsd.pl> Message-ID: References: <513F8D20.2050707@erdgeist.org> <201303131118.36811.jhb@freebsd.org> <20130313212750.GC1372@garage.freebsd.pl> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Mar 2013 21:59:27 -0000 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 else branch, you can get rid of the if branch, guard the else branch by a + if (pidptr) { and let the if (errno == 0 || errno == EAGAIN) fix the errno Regards, erdgeist From owner-freebsd-current@FreeBSD.ORG Wed Mar 13 22:06:58 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 5724425E; Wed, 13 Mar 2013 22:06:58 +0000 (UTC) (envelope-from pawel@dawidek.net) Received: from mail.dawidek.net (garage.dawidek.net [91.121.88.72]) by mx1.freebsd.org (Postfix) with ESMTP id 1FA45F3; Wed, 13 Mar 2013 22:06:57 +0000 (UTC) Received: from localhost (89-73-195-149.dynamic.chello.pl [89.73.195.149]) by mail.dawidek.net (Postfix) with ESMTPSA id 748E66CD; Wed, 13 Mar 2013 23:03:44 +0100 (CET) Date: Wed, 13 Mar 2013 23:08:31 +0100 From: Pawel Jakub Dawidek To: Dirk Engling Subject: Re: pidfile_open incorrectly returns EAGAIN when pidfile is locked Message-ID: <20130313220831.GF1372@garage.freebsd.pl> References: <513F8D20.2050707@erdgeist.org> <201303131118.36811.jhb@freebsd.org> <20130313212750.GC1372@garage.freebsd.pl> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="5CUMAwwhRxlRszMD" Content-Disposition: inline In-Reply-To: X-OS: FreeBSD 10.0-CURRENT amd64 User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Mar 2013 22:06:58 -0000 --5CUMAwwhRxlRszMD Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Mar 13, 2013 at 10:59:17PM +0100, Dirk Engling wrote: >=20 > On Wed, 13 Mar 2013, Pawel Jakub Dawidek wrote: >=20 > > How about this patch? > > > > http://people.freebsd.org/~pjd/patches/pidfile.c.patch >=20 > If you move the lines >=20 > + if (errno =3D=3D 0 || errno =3D=3D EAGAIN) > + errno =3D EEXIST; >=20 > out of the else branch, you can get rid of the if branch, guard the else= =20 > branch by a >=20 > + if (pidptr) { >=20 > and let the if (errno =3D=3D 0 || errno =3D=3D EAGAIN) fix the errno I think I considered something similar at first, but the change I proposed was optimal, IMHO at the cost of producing pretty large diff, because of indentation change. But to be sure, can you send a patch of your proposed change? --=20 Pawel Jakub Dawidek http://www.wheelsystems.com FreeBSD committer http://www.FreeBSD.org Am I Evil? Yes, I Am! http://tupytaj.pl --5CUMAwwhRxlRszMD Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEARECAAYFAlFA+N8ACgkQForvXbEpPzSwOwCgucrbfgLbYpEndajoK84jzNel TbYAoIlOUughbXL1fwTXkqucJtyv4pNk =Nnvl -----END PGP SIGNATURE----- --5CUMAwwhRxlRszMD-- From owner-freebsd-current@FreeBSD.ORG Thu Mar 14 04:13:36 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id F25DE7DF for ; Thu, 14 Mar 2013 04:13:36 +0000 (UTC) (envelope-from andy@neu.net) Received: from mail.neu.net (neu.net [199.48.129.194]) by mx1.freebsd.org (Postfix) with ESMTP id BA34B137 for ; Thu, 14 Mar 2013 04:13:35 +0000 (UTC) Received: from neu.net (neu.net [199.48.129.194]) by mail.neu.net (8.14.6/8.14.5) with ESMTP id r2E4DSa5032881 for ; Thu, 14 Mar 2013 00:13:28 -0400 (EDT) (envelope-from andy@neu.net) Date: Thu, 14 Mar 2013 00:13:28 -0400 (EDT) From: AN To: freebsd-current@freebsd.org Subject: FYI - warning: KLD In-Reply-To: Message-ID: References: User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII X-Virus-Scanned: clamav-milter 0.97.6 at my.mail.server X-Virus-Status: Clean X-Spam-Status: No, score=0.0 required=4.5 tests=RP_MATCHES_RCVD autolearn=unavailable version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on mail.neu.net X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Mar 2013 04:13:37 -0000 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 system freeze that required a power cycle. I noticed the following on verbose boot. From dmesg: warning: KLD '/boot/kernel/linprocfs.ko' is newer than the linker.hints file Just a heads up in case it's the symptom of another issue. # dmesg |grep warning warning: KLD '/boot/kernel/linprocfs.ko' is newer than the linker.hints file warning: KLD '/boot/kernel/ums.ko' is newer than the linker.hints file warning: KLD '/boot/kernel/uhid.ko' is newer than the linker.hints file From owner-freebsd-current@FreeBSD.ORG Thu Mar 14 05:41:10 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id ED0AB5B8 for ; Thu, 14 Mar 2013 05:41:10 +0000 (UTC) (envelope-from uzimac@da3m0n8t3r.com) Received: from z.umatar.com (z.umatar.com [66.135.39.87]) by mx1.freebsd.org (Postfix) with ESMTP id B50223FD for ; Thu, 14 Mar 2013 05:41:10 +0000 (UTC) Received: from z.umatar.com (localhost [127.0.0.1]) by z.umatar.com (8.14.5/8.14.3) with ESMTP id r2E5f4X8081269 for ; Wed, 13 Mar 2013 22:41:04 -0700 (PDT) (envelope-from uzimac@da3m0n8t3r.com) Received: (from uzimac@localhost) by z.umatar.com (8.14.5/8.14.3/Submit) id r2E5f4s2081268 for freebsd-current@freebsd.org; Wed, 13 Mar 2013 22:41:04 -0700 (PDT) (envelope-from uzimac@da3m0n8t3r.com) X-Authentication-Warning: z.umatar.com: uzimac set sender to uzimac@da3m0n8t3r.com using -f From: "Waitman Gobble" Subject: reservation of n, n (3) failed To: freebsd-current@freebsd.org Message-Id: <1363239664.81230@da3m0n8t3r.com> X-Originating-IP: 50.197.134.190 X-Mailer: Usermin 1.510 Date: Wed, 13 Mar 2013 22:41:04 -0700 (PDT) MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="bound1363239664" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Mar 2013 05:41:11 -0000 This is a multi-part message in MIME format. --bound1363239664 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 7bit Hi, I swapped out the CPU on this machine today, I don't recall seeing these messages previously: acpi0: reservation of 0, a0000 (3) failed acpi0: reservation of 100000, bfcd0000 (3) failed Does anyone have an idea about what this refers to? Here's the boot log. > uname -a FreeBSD dx.burplex.com 10.0-CURRENT FreeBSD 10.0-CURRENT #0 r248165: Mon Mar 11 18:20:30 PDT 2013 root@dx.burplex.com:/usr/obj/usr/src/sys/FURAHA amd64 Copyright (c) 1992-2013 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 10.0-CURRENT #0 r248165: Mon Mar 11 18:20:30 PDT 2013 root@dx.burplex.com:/usr/obj/usr/src/sys/FURAHA amd64 FreeBSD clang version 3.2 (tags/RELEASE_32/final 170710) 20121221 CPU: AMD FX(tm)-8350 Eight-Core Processor (4027.01-MHz K8-class CPU) Origin = "AuthenticAMD" Id = 0x600f20 Family = 0x15 Model = 0x2 Stepping = 0 Features=0x178bfbff Features2=0x3e98320b AMD Features=0x2e500800 AMD Features2=0x1ebbfff,NodeId,TBM,Topology,,> Standard Extended Features=0x8 TSC: P-state invariant, performance statistics real memory = 34359738368 (32768 MB) avail memory = 33082753024 (31550 MB) Event timer "LAPIC" quality 400 ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 8 CPUs FreeBSD/SMP: 1 package(s) x 8 core(s) cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 2 cpu3 (AP): APIC ID: 3 cpu4 (AP): APIC ID: 4 cpu5 (AP): APIC ID: 5 cpu6 (AP): APIC ID: 6 cpu7 (AP): APIC ID: 7 ioapic0: Changing APIC ID to 8 ioapic0 irqs 0-23 on motherboard acpi0: on motherboard acpi0: Power Button (fixed) acpi0: reservation of 0, a0000 (3) failed acpi0: reservation of 100000, bfcd0000 (3) failed cpu0: on acpi0 cpu1: on acpi0 cpu2: on acpi0 cpu3: on acpi0 cpu4: on acpi0 cpu5: on acpi0 cpu6: on acpi0 cpu7: on acpi0 attimer0: port 0x40-0x43 on acpi0 Timecounter "i8254" frequency 1193182 Hz quality 0 Event timer "i8254" frequency 1193182 Hz quality 100 hpet0: iomem 0xfed00000-0xfed003ff irq 0,8 on acpi0 Timecounter "HPET" frequency 14318180 Hz quality 950 atrtc0: port 0x70-0x73 on acpi0 Event timer "RTC" frequency 32768 Hz quality 0 Timecounter "ACPI-safe" frequency 3579545 Hz quality 850 Thank you, -- Waitman Gobble San Jose California USA --bound1363239664-- From owner-freebsd-current@FreeBSD.ORG Thu Mar 14 07:28:27 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 06ED39E5 for ; Thu, 14 Mar 2013 07:28:27 +0000 (UTC) (envelope-from erdgeist@erdgeist.org) Received: from elektropost.org (elektropost.org [217.13.206.130]) by mx1.freebsd.org (Postfix) with ESMTP id 4D3448F5 for ; Thu, 14 Mar 2013 07:28:25 +0000 (UTC) Received: (qmail 81582 invoked from network); 14 Mar 2013 07:28:24 -0000 Received: from elektropost.org (HELO elektropost.org) (erdgeist@erdgeist.org) by elektropost.org with CAMELLIA256-SHA encrypted SMTP; 14 Mar 2013 07:28:24 -0000 Message-ID: <51417C19.9060002@erdgeist.org> Date: Thu, 14 Mar 2013 08:28:25 +0100 From: Dirk Engling User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130216 Thunderbird/17.0.3 MIME-Version: 1.0 To: Pawel Jakub Dawidek Subject: Re: pidfile_open incorrectly returns EAGAIN when pidfile is locked References: <513F8D20.2050707@erdgeist.org> <201303131118.36811.jhb@freebsd.org> <20130313212750.GC1372@garage.freebsd.pl> <20130313220831.GF1372@garage.freebsd.pl> In-Reply-To: <20130313220831.GF1372@garage.freebsd.pl> X-Enigmail-Version: 1.5.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Mar 2013 07:28:27 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 13.03.13 23:08, Pawel Jakub Dawidek wrote: > I think I considered something similar at first, but the change I > proposed was optimal, IMHO at the cost of producing pretty large > diff, because of indentation change. But to be sure, can you send a > patch of your proposed change? http://erdgeist.org/arts/software/Code/pidfile.c.diff Pozdrawiam, erdgeist -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Darwin) iEYEARECAAYFAlFBfBkACgkQuN1wFypsMNOUlQCeJw4F9B+8g8SGFZ4kpUtz6T3Z qPcAn1K5bTF43r2FMOWmpLZIxKz3pW8z =1Zvv -----END PGP SIGNATURE----- From owner-freebsd-current@FreeBSD.ORG Thu Mar 14 08:42:49 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 1E7C1EAB; Thu, 14 Mar 2013 08:42:49 +0000 (UTC) (envelope-from pawel@dawidek.net) Received: from mail.dawidek.net (garage.dawidek.net [91.121.88.72]) by mx1.freebsd.org (Postfix) with ESMTP id CE7ACBDE; Thu, 14 Mar 2013 08:42:48 +0000 (UTC) Received: from localhost (89-73-195-149.dynamic.chello.pl [89.73.195.149]) by mail.dawidek.net (Postfix) with ESMTPSA id BD13B7AF; Thu, 14 Mar 2013 09:39:33 +0100 (CET) Date: Thu, 14 Mar 2013 09:44:20 +0100 From: Pawel Jakub Dawidek To: Dirk Engling Subject: Re: pidfile_open incorrectly returns EAGAIN when pidfile is locked Message-ID: <20130314084420.GH1372@garage.freebsd.pl> References: <513F8D20.2050707@erdgeist.org> <201303131118.36811.jhb@freebsd.org> <20130313212750.GC1372@garage.freebsd.pl> <20130313220831.GF1372@garage.freebsd.pl> <51417C19.9060002@erdgeist.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="7J16OGEJ/mt06A90" Content-Disposition: inline In-Reply-To: <51417C19.9060002@erdgeist.org> X-OS: FreeBSD 10.0-CURRENT amd64 User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Mar 2013 08:42:49 -0000 --7J16OGEJ/mt06A90 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Mar 14, 2013 at 08:28:25AM +0100, Dirk Engling wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 >=20 > On 13.03.13 23:08, Pawel Jakub Dawidek wrote: >=20 > > I think I considered something similar at first, but the change I=20 > > proposed was optimal, IMHO at the cost of producing pretty large > > diff, because of indentation change. But to be sure, can you send a > > patch of your proposed change? >=20 > http://erdgeist.org/arts/software/Code/pidfile.c.diff Right. Your patch assumes EWOULDBLOCK is equal to EAGAIN, which is true on FreeBSD, but is not portable. Also in case pidptr is NULL you compare errno three times instead of just one (not a big deal of course, just something that could be done a bit more optimal:)). --=20 Pawel Jakub Dawidek http://www.wheelsystems.com FreeBSD committer http://www.FreeBSD.org Am I Evil? Yes, I Am! http://tupytaj.pl --7J16OGEJ/mt06A90 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEARECAAYFAlFBjeQACgkQForvXbEpPzTiUgCffVExSr5zUMsgST7+nXsv6Qzv 6agAmgNFGJPKCnZxbwEEdi3S8z3SUhho =5Sc5 -----END PGP SIGNATURE----- --7J16OGEJ/mt06A90-- From owner-freebsd-current@FreeBSD.ORG Thu Mar 14 09:33:39 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id E61936BA for ; Thu, 14 Mar 2013 09:33:39 +0000 (UTC) (envelope-from erdgeist@erdgeist.org) Received: from elektropost.org (elektropost.org [217.13.206.130]) by mx1.freebsd.org (Postfix) with ESMTP id 366E3E43 for ; Thu, 14 Mar 2013 09:33:38 +0000 (UTC) Received: (qmail 666 invoked from network); 14 Mar 2013 09:33:36 -0000 Received: from elektropost.org (HELO elektropost.org) (erdgeist@erdgeist.org) by elektropost.org with AES256-SHA encrypted SMTP; 14 Mar 2013 09:33:36 -0000 Date: Thu, 14 Mar 2013 10:33:35 +0100 (CET) From: Dirk Engling To: Pawel Jakub Dawidek Subject: Re: pidfile_open incorrectly returns EAGAIN when pidfile is locked In-Reply-To: <20130314084420.GH1372@garage.freebsd.pl> Message-ID: References: <513F8D20.2050707@erdgeist.org> <201303131118.36811.jhb@freebsd.org> <20130313212750.GC1372@garage.freebsd.pl> <20130313220831.GF1372@garage.freebsd.pl> <51417C19.9060002@erdgeist.org> <20130314084420.GH1372@garage.freebsd.pl> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Mar 2013 09:33:40 -0000 On Thu, 14 Mar 2013, Pawel Jakub Dawidek wrote: > Right. Your patch assumes EWOULDBLOCK is equal to EAGAIN, which is true > on FreeBSD, but is not portable. Also in case pidptr is NULL you compare > errno three times instead of just one (not a big deal of course, just > something that could be done a bit more optimal:)). You're right. OTOH, wouldn't modifying pidfile_read to return EAGAIN and not EWOULDBLOCK totally be worth saving that 2 lines in the patch? ;) erdgeist From owner-freebsd-current@FreeBSD.ORG Thu Mar 14 11:29:33 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 3B613DA0 for ; Thu, 14 Mar 2013 11:29:33 +0000 (UTC) (envelope-from bdrewery@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 0B4A05E4 for ; Thu, 14 Mar 2013 11:29:33 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.6/8.14.6) with ESMTP id r2EBTWc0040479 for ; Thu, 14 Mar 2013 11:29:32 GMT (envelope-from bdrewery@freefall.freebsd.org) Received: (from bdrewery@localhost) by freefall.freebsd.org (8.14.6/8.14.6/Submit) id r2EBTWkU040472 for freebsd-current@freebsd.org; Thu, 14 Mar 2013 11:29:32 GMT (envelope-from bdrewery) Received: (qmail 78887 invoked from network); 14 Mar 2013 06:29:30 -0500 Received: from unknown (HELO ?10.10.0.24?) (freebsd@shatow.net@10.10.0.24) by sweb.xzibition.com with ESMTPA; 14 Mar 2013 06:29:30 -0500 Message-ID: <5141B491.1010800@FreeBSD.org> Date: Thu, 14 Mar 2013 06:29:21 -0500 From: Bryan Drewery Organization: FreeBSD User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130215 Thunderbird/17.0.3 MIME-Version: 1.0 To: FreeBSD Current , freebsd-stable@FreeBSD.ORG, freebsd-pkg@freebsd.org, FreeBSD Ports Subject: [HEADS UP] pkgng binary packages regression in 1.0.9. Fixed in 1.0.9_1 X-Enigmail-Version: 1.5.1 OpenPGP: id=3C9B0CF9; url=http://www.shatow.net/bryan/bryan.asc Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="----enig2HLITPBSOMQOVSNECCDCW" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Mar 2013 11:29:33 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) ------enig2HLITPBSOMQOVSNECCDCW Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable This only affects binary-packages-only users. pkg 1.0.9 had a regression with 'pkg update' that will prevent updating your repository. Please skip this version and use 1.0.9_1. This version was only in ports for 7 hours. Due to the security incident, there are still no official FreeBSD packages. If you are using an unofficial mirror, it is unlikely it would have upgraded to 1.0.9 in the time it was in the tree. If you are building your own packages and managed to get onto 1.0.9 you can upgrade to 1.0.9_1 as follows: # cp /usr/local/sbin/pkgs-static . # pkg delete -f pkg # ./pkg-static add URL-TO-YOUR-PACKAGESITE/All/pkg-1.0.9_1.txz #optional # rm pkg-static As for how this managed to get released. We did do a functional test of this before releasing, but due to the nature of 'pkg update' using a cache, it was not immediately obvious that it was broken. We do need your help with adding more automated tests. http://lists.freebsd.org/pipermail/freebsd-pkg/2013-March/000016.html has our call for help on this front and more information. Regards, Bryan Drewery ------enig2HLITPBSOMQOVSNECCDCW Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJRQbSRAAoJEG54KsA8mwz52NIP/igM9AdMDymYeI6ejOJH0ONR vvp7iP1henSZacwOi+sLqUK70JiPThx0fCwzLJbMa1E4hjhP4Ge5qEOK0sp1BLQL S+jj33q3WeBLOu7pH+LbyY1OnKhswdIhcfGKn5qxFxu+Xz2E1qVjIewK3hSP87jR q5r1ShCqYXXKRDRjeR5tura+W3gls/OoCYpwLs2+xu9nL+VuXkczyq/y4aaCGyRw 3OJFS269V5eVB714sY7lkiSj1SlbF1nrNOzv01XfuMYW8fcBPIybu2CeyUaQN5fg HxN84UImUcD9mcyjBBx+v0Dr7YqsjYYBa2jz3x30yoHMPnq13K94QXmUszwt2734 DD2cq8Wn1ey/OEduNVN1tSuz5g/83LDXtNjOrBOxzGkV3hbp1ZEAD0jbIk5yOwY2 ID7PBCl/ENyoA+yrIoArGXTEqOPMFfpbErsIQYg8xhxLMObBhBNsn/sjQuAG4TRC YwKd1ePetNf2jbVca2tCRjJYCwBigIdgNtdfIyayUyiatF1zwkfdeqMNBhl+UkhQ MfOwm4BH6/hYYF3Ldv3/d5gcx8aoHx/EvRlKbY4EXs9TXZzdreypeXdGpKg/jKz1 J535rkWWgxRUZml+RXanU9h24vLG0r+W4EfyXediDRilsdChprLkxIVDN3OhQdnM 5TECBoONJJEoGYZroos3 =U0Cw -----END PGP SIGNATURE----- ------enig2HLITPBSOMQOVSNECCDCW-- From owner-freebsd-current@FreeBSD.ORG Thu Mar 14 14:05:40 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 9FC36ABA for ; Thu, 14 Mar 2013 14:05:40 +0000 (UTC) (envelope-from kolyasir@gmail.com) Received: from mail-qa0-f54.google.com (mail-qa0-f54.google.com [209.85.216.54]) by mx1.freebsd.org (Postfix) with ESMTP id 69B7DEF9 for ; Thu, 14 Mar 2013 14:05:40 +0000 (UTC) Received: by mail-qa0-f54.google.com with SMTP id hg5so1240028qab.6 for ; Thu, 14 Mar 2013 07:05:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=ozV4ivhxJMYWCAddMmUuIXYz6X68JcNnAlWfrTbHPbY=; b=RWQxOmiryy/DEeIkJE1FWUJA13E8FoDQ9TU54/qvf/YwAuIjNdTTkeF9TF9LxL/r+h AjhY+LApa/UMXxZQtTdFvweGOQxsbLZEiuxPBU1GV7h8fIRViPBgzwzWix0dFOLxEr8v x99NAgLk1IqFrn7FhY2S5H041qAgm6xWvbDmc3LyK2a5syPg5PlsLjSba6nThMU1lrkv d+onW+Ar0eKdaXzo2Wjj2K+MuOp1z3QWLt5nA34z1rnrKSvFFSzD4qKC2ghxRXEEwOdI aeZaxOSsYp/+6yM7NMtwz0M549UXASpu/TxMgFhAdsQlnTh9YpAHIbOWeCYWrYJXsFCn f3lg== MIME-Version: 1.0 X-Received: by 10.224.60.15 with SMTP id n15mr3432780qah.45.1363269933967; Thu, 14 Mar 2013 07:05:33 -0700 (PDT) Received: by 10.49.48.197 with HTTP; Thu, 14 Mar 2013 07:05:33 -0700 (PDT) Date: Thu, 14 Mar 2013 10:05:33 -0400 Message-ID: Subject: vlan interface does not repond on untagged packets From: Yasir hussan To: Current Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Mar 2013 14:05:40 -0000 Hi, i am creating and testing vlan using these commands, *ifconfig arge0 192.168.100.10 netmask 255.255.255.0* * * *ifconfig vlan4 create* *ifconfig vlan4 vlandev arge0 vlan 4* *ifconfig vlan4 192.168.1.10 netmask 255.255.255.0* here arge0 is the default interface of my ethernet device, now i want to access vlan4 interface from an other pc which has linux and is dirctly connected to my freebsd machine, now if i try to ping linux machine it will send tagged packets but linux does not recogniz it and leave it, and similarly when i try to ping linux machine to vlan4 interface on freebsd, linux send untagged packets so vlan4 does not response to it. I want that my vlan4 interface could able to recongnize untagged packets and could respond to it Thanks From owner-freebsd-current@FreeBSD.ORG Thu Mar 14 14:49:11 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id BABAA599 for ; Thu, 14 Mar 2013 14:49:11 +0000 (UTC) (envelope-from cjones@innerlightcorp.com) Received: from mx1.hosteddomainservices.com (mx1.hosteddomainservices.com [97.75.176.81]) by mx1.freebsd.org (Postfix) with ESMTP id 8AD911F4 for ; Thu, 14 Mar 2013 14:49:11 +0000 (UTC) From: "Charlie Jones" To: Subject: Error question Date: Thu, 14 Mar 2013 08:49:09 -0600 Message-ID: <006801ce20c3$15da9080$418fb180$@com> MIME-Version: 1.0 Thread-Index: Ac4gwxXMO6TcGxABR0Wc0gwSRhHDfg== Content-Language: en-us X-Virus-Scanned: ClamAV via mx1.hosteddomainservices.com Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Mar 2013 14:49:11 -0000 I am trying to upgrade to 9.1-RELEASE uname -a FreeBSD havoc.innerlightcorp.com 8.2-RELEASE-p2 FreeBSD 8.2-RELEASE-p2 #0: Mon May 30 12:58:18 MDT 2011 root@havoc.innerlightcorp.com:/usr/obj/usr/src/sys/CUSTOM amd64 I received these messages at the end of the make buildworld process. Is it something that I should be concerned with? Any ideas? I don't want to compound the problem by moving on when I see Error code 1. rm -f freebsd.cf freebsd.submit.cf cd /usr/src; MACHINE=i386 MACHINE_ARCH=i386 MACHINE_CPU="i686 mmx sse sse2" MAKEOBJDIRPREFIX=/usr/obj/lib32 _SHLIBDIRPREFIX=/usr/obj/usr/src/lib32 _LDSCRIPTROOT=/usr/obj/usr/src/lib32 VERSION="FreeBSD 8.2-RELEASE-p2 amd64 802000" INSTALL="sh /usr/src/tools/install.sh" PATH=/usr/obj/usr/src/tmp/legacy/usr/sbin:/usr/obj/usr/src/tmp/legacy/usr/bi n:/usr/obj/usr/src/tmp/legacy/usr/games:/usr/obj/usr/src/tmp/legacy/bin:/usr /obj/usr/src/tmp/usr/sbin:/usr/obj/usr/src/tmp/usr/bin:/usr/obj/usr/src/tmp/ usr/games:/sbin:/bin:/usr/sbin:/usr/bin LIBDIR=/usr/lib32 SHLIBDIR=/usr/lib32 COMPILER_TYPE=clang /usr/obj/usr/src/make.amd64/make AS="as --32" LD="ld -m elf_i386_fbsd -Y P,/usr/obj/usr/src/lib32/usr/lib32" CC="cc -m32 -march=nocona -DCOMPAT_32BIT -isystem /usr/obj/usr/src/lib32/usr/include/ -L/usr/obj/usr/src/lib32/usr/lib32 -B/usr/obj/usr/src/lib32/usr/lib32" CXX="c++ -m32 -march=nocona -DCOMPAT_32BIT -isystem /usr/obj/usr/src/lib32/usr/include/ -L/usr/obj/usr/src/lib32/usr/lib32 -B/usr/obj/usr/src/lib32/usr/lib32" DESTDIR=/usr/obj/usr/src/lib32 -DCOMPAT_32BIT -DLIBRARIES_ONLY -DNO_CPU_CFLAGS -DNO_CTF -DNO_LINT -DWITHOUT_BIND -DWITHOUT_MAN -DWITHOUT_INFO -DWITHOUT_HTML -f Makefile.inc1 par-cleandir "/usr/src/Makefile.inc1", line 175: CPUTYPE global should be set with ?=. *** [_cleanobj] Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. Thanks in advance Charlie Jones From owner-freebsd-current@FreeBSD.ORG Thu Mar 14 14:57:28 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 90239766; Thu, 14 Mar 2013 14:57:28 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from bigwig.baldwin.cx (bigknife-pt.tunnel.tserv9.chi1.ipv6.he.net [IPv6:2001:470:1f10:75::2]) by mx1.freebsd.org (Postfix) with ESMTP id 619A6265; Thu, 14 Mar 2013 14:57:28 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id A9A52B992; Thu, 14 Mar 2013 10:57:27 -0400 (EDT) From: John Baldwin To: Pawel Jakub Dawidek Subject: Re: pidfile_open incorrectly returns EAGAIN when pidfile is locked Date: Thu, 14 Mar 2013 09:42:40 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110714-p25; KDE/4.5.5; amd64; ; ) References: <513F8D20.2050707@erdgeist.org> <51417C19.9060002@erdgeist.org> <20130314084420.GH1372@garage.freebsd.pl> In-Reply-To: <20130314084420.GH1372@garage.freebsd.pl> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Message-Id: <201303140942.40945.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Thu, 14 Mar 2013 10:57:27 -0400 (EDT) Cc: Dirk Engling , freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Mar 2013 14:57:28 -0000 On Thursday, March 14, 2013 4:44:20 am Pawel Jakub Dawidek wrote: > On Thu, Mar 14, 2013 at 08:28:25AM +0100, Dirk Engling wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA1 > > > > On 13.03.13 23:08, Pawel Jakub Dawidek wrote: > > > > > I think I considered something similar at first, but the change I > > > proposed was optimal, IMHO at the cost of producing pretty large > > > diff, because of indentation change. But to be sure, can you send a > > > patch of your proposed change? > > > > http://erdgeist.org/arts/software/Code/pidfile.c.diff > > Right. Your patch assumes EWOULDBLOCK is equal to EAGAIN, which is true > on FreeBSD, but is not portable. Also in case pidptr is NULL you compare > errno three times instead of just one (not a big deal of course, just > something that could be done a bit more optimal:)). Geeze, why not just add an else. That's the really short diff: Index: pidfile.c =================================================================== --- pidfile.c (revision 248162) +++ pidfile.c (working copy) @@ -140,7 +140,8 @@ pidfile_open(const char *path, mode_t mode, pid_t *pidptr = -1; if (errno == 0 || errno == EAGAIN) errno = EEXIST; - } + } else if (errno == EWOULDBLOCK) + errno = EEXIST; free(pfh); return (NULL); } -- John Baldwin From owner-freebsd-current@FreeBSD.ORG Thu Mar 14 15:36:03 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 4BDB3897 for ; Thu, 14 Mar 2013 15:36:03 +0000 (UTC) (envelope-from dnebdal@gmail.com) Received: from mail-lb0-f178.google.com (mail-lb0-f178.google.com [209.85.217.178]) by mx1.freebsd.org (Postfix) with ESMTP id CE0BC749 for ; Thu, 14 Mar 2013 15:36:02 +0000 (UTC) Received: by mail-lb0-f178.google.com with SMTP id n1so1994372lba.37 for ; Thu, 14 Mar 2013 08:36:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=Hf9R7uOHobsRazLq2PJvVH3sBG/DW7TyyVVvrp760m0=; b=O/99vth6aMd+n3W2DSxD8qhbZAyw6bElgY4GjTKMcSXMXTgiNo0LqYU74zoNu8VZVi BzKvga7UD0IClVnn7AVUvO57pQZIYVnOLqC6Eb0OK9XOPK3pKEIWUceaZ8ZMKKE8fIbJ K3oMCfu2+fwpKpc6stVh6rwALo56qVTShYUVJqD5pkihpmlZWIH2FAWMt3kdGgnl3bsz j7sG8KpqouIUmZD20zJnOUcVukazTxfG4B+3CH2Xbe7GRlUj6ks9jIPqfdaNTtyTGfqQ oxG+Ge44f7+5XJqwnUQd/+rulQobeyrAfAkjRKk1bQ/6bcOZWYm2/kw3DDhHygTnmT/c 7m0g== MIME-Version: 1.0 X-Received: by 10.112.37.194 with SMTP id a2mr1328326lbk.40.1363275361252; Thu, 14 Mar 2013 08:36:01 -0700 (PDT) Received: by 10.112.80.133 with HTTP; Thu, 14 Mar 2013 08:36:01 -0700 (PDT) In-Reply-To: <006801ce20c3$15da9080$418fb180$@com> References: <006801ce20c3$15da9080$418fb180$@com> Date: Thu, 14 Mar 2013 16:36:01 +0100 Message-ID: Subject: Re: Error question From: Daniel Nebdal To: Charlie Jones Content-Type: text/plain; charset=ISO-8859-1 Cc: Current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Mar 2013 15:36:03 -0000 How does your make.conf and src.conf look? On Thu, Mar 14, 2013 at 3:49 PM, Charlie Jones wrote: > I am trying to upgrade to 9.1-RELEASE > > uname -a > > FreeBSD havoc.innerlightcorp.com 8.2-RELEASE-p2 FreeBSD 8.2-RELEASE-p2 #0: > Mon May 30 12:58:18 MDT 2011 > root@havoc.innerlightcorp.com:/usr/obj/usr/src/sys/CUSTOM amd64 > > > > I received these messages at the end of the make buildworld process. Is it > something that I should be concerned with? Any ideas? I don't want to > compound the problem by moving on when I see Error code 1. > > > > rm -f freebsd.cf freebsd.submit.cf > > cd /usr/src; MACHINE=i386 MACHINE_ARCH=i386 MACHINE_CPU="i686 mmx sse sse2" > MAKEOBJDIRPREFIX=/usr/obj/lib32 _SHLIBDIRPREFIX=/usr/obj/usr/src/lib32 > _LDSCRIPTROOT=/usr/obj/usr/src/lib32 VERSION="FreeBSD 8.2-RELEASE-p2 amd64 > 802000" INSTALL="sh /usr/src/tools/install.sh" > PATH=/usr/obj/usr/src/tmp/legacy/usr/sbin:/usr/obj/usr/src/tmp/legacy/usr/bi > n:/usr/obj/usr/src/tmp/legacy/usr/games:/usr/obj/usr/src/tmp/legacy/bin:/usr > /obj/usr/src/tmp/usr/sbin:/usr/obj/usr/src/tmp/usr/bin:/usr/obj/usr/src/tmp/ > usr/games:/sbin:/bin:/usr/sbin:/usr/bin LIBDIR=/usr/lib32 > SHLIBDIR=/usr/lib32 COMPILER_TYPE=clang /usr/obj/usr/src/make.amd64/make > AS="as --32" LD="ld -m elf_i386_fbsd -Y P,/usr/obj/usr/src/lib32/usr/lib32" > CC="cc -m32 -march=nocona -DCOMPAT_32BIT -isystem > /usr/obj/usr/src/lib32/usr/include/ -L/usr/obj/usr/src/lib32/usr/lib32 > -B/usr/obj/usr/src/lib32/usr/lib32" CXX="c++ -m32 -march=nocona > -DCOMPAT_32BIT -isystem /usr/obj/usr/src/lib32/usr/include/ > -L/usr/obj/usr/src/lib32/usr/lib32 -B/usr/obj/usr/src/lib32/usr/lib32" > DESTDIR=/usr/obj/usr/src/lib32 -DCOMPAT_32BIT -DLIBRARIES_ONLY > -DNO_CPU_CFLAGS -DNO_CTF -DNO_LINT -DWITHOUT_BIND -DWITHOUT_MAN > -DWITHOUT_INFO -DWITHOUT_HTML -f Makefile.inc1 par-cleandir > > "/usr/src/Makefile.inc1", line 175: CPUTYPE global should be set with ?=. > > *** [_cleanobj] Error code 1 > > > > Stop in /usr/src. > > *** Error code 1 > > > > Stop in /usr/src. > > > > Thanks in advance > > Charlie Jones > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@FreeBSD.ORG Thu Mar 14 16:28:26 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 35EC975E; Thu, 14 Mar 2013 16:28:26 +0000 (UTC) (envelope-from pawel@dawidek.net) Received: from mail.dawidek.net (garage.dawidek.net [91.121.88.72]) by mx1.freebsd.org (Postfix) with ESMTP id E7C869CE; Thu, 14 Mar 2013 16:28:25 +0000 (UTC) Received: from localhost (58.wheelsystems.com [83.12.187.58]) by mail.dawidek.net (Postfix) with ESMTPSA id 2CA0593F; Thu, 14 Mar 2013 17:25:11 +0100 (CET) Date: Thu, 14 Mar 2013 17:29:58 +0100 From: Pawel Jakub Dawidek To: John Baldwin Subject: Re: pidfile_open incorrectly returns EAGAIN when pidfile is locked Message-ID: <20130314162958.GD1344@garage.freebsd.pl> References: <513F8D20.2050707@erdgeist.org> <51417C19.9060002@erdgeist.org> <20130314084420.GH1372@garage.freebsd.pl> <201303140942.40945.jhb@freebsd.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Ns7jmDPpOpCD+GE/" Content-Disposition: inline In-Reply-To: <201303140942.40945.jhb@freebsd.org> X-OS: FreeBSD 10.0-CURRENT amd64 User-Agent: Mutt/1.5.21 (2010-09-15) Cc: Dirk Engling , freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Mar 2013 16:28:26 -0000 --Ns7jmDPpOpCD+GE/ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Mar 14, 2013 at 09:42:40AM -0400, John Baldwin wrote: > On Thursday, March 14, 2013 4:44:20 am Pawel Jakub Dawidek wrote: > > On Thu, Mar 14, 2013 at 08:28:25AM +0100, Dirk Engling wrote: > > > -----BEGIN PGP SIGNED MESSAGE----- > > > Hash: SHA1 > > >=20 > > > On 13.03.13 23:08, Pawel Jakub Dawidek wrote: > > >=20 > > > > I think I considered something similar at first, but the change I= =20 > > > > proposed was optimal, IMHO at the cost of producing pretty large > > > > diff, because of indentation change. But to be sure, can you send a > > > > patch of your proposed change? > > >=20 > > > http://erdgeist.org/arts/software/Code/pidfile.c.diff > >=20 > > Right. Your patch assumes EWOULDBLOCK is equal to EAGAIN, which is true > > on FreeBSD, but is not portable. Also in case pidptr is NULL you compare > > errno three times instead of just one (not a big deal of course, just > > something that could be done a bit more optimal:)). >=20 > Geeze, why not just add an else. That's the really short diff: Heh, I did consider that as well, but here you check errno twice, instead of once. Guys, is there anything wrong with the patch I proposed? > Index: pidfile.c > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > --- pidfile.c (revision 248162) > +++ pidfile.c (working copy) > @@ -140,7 +140,8 @@ pidfile_open(const char *path, mode_t mode, pid_t > *pidptr =3D -1; > if (errno =3D=3D 0 || errno =3D=3D EAGAIN) > errno =3D EEXIST; > - } > + } else if (errno =3D=3D EWOULDBLOCK) > + errno =3D EEXIST; > free(pfh); > return (NULL); > } --=20 Pawel Jakub Dawidek http://www.wheelsystems.com FreeBSD committer http://www.FreeBSD.org Am I Evil? Yes, I Am! http://tupytaj.pl --Ns7jmDPpOpCD+GE/ Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEARECAAYFAlFB+wYACgkQForvXbEpPzRh2QCgza1GSffrMYCDy95g+AUzOrDM MxUAn2pE9dQ3l3Mr0cRrhfwmPeI2f3gb =hdBk -----END PGP SIGNATURE----- --Ns7jmDPpOpCD+GE/-- From owner-freebsd-current@FreeBSD.ORG Thu Mar 14 16:47:49 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 8692E23B for ; Thu, 14 Mar 2013 16:47:49 +0000 (UTC) (envelope-from erdgeist@erdgeist.org) Received: from elektropost.org (elektropost.org [217.13.206.130]) by mx1.freebsd.org (Postfix) with ESMTP id CD30DAC7 for ; Thu, 14 Mar 2013 16:47:48 +0000 (UTC) Received: (qmail 74549 invoked from network); 14 Mar 2013 16:47:47 -0000 Received: from elektropost.org (HELO elektropost.org) (erdgeist@erdgeist.org) by elektropost.org with CAMELLIA256-SHA encrypted SMTP; 14 Mar 2013 16:47:47 -0000 Message-ID: <5141FF33.5030108@erdgeist.org> Date: Thu, 14 Mar 2013 17:47:47 +0100 From: Dirk Engling User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130216 Thunderbird/17.0.3 MIME-Version: 1.0 To: Pawel Jakub Dawidek Subject: Re: pidfile_open incorrectly returns EAGAIN when pidfile is locked References: <513F8D20.2050707@erdgeist.org> <51417C19.9060002@erdgeist.org> <20130314084420.GH1372@garage.freebsd.pl> <201303140942.40945.jhb@freebsd.org> <20130314162958.GD1344@garage.freebsd.pl> In-Reply-To: <20130314162958.GD1344@garage.freebsd.pl> X-Enigmail-Version: 1.5.1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Mar 2013 16:47:49 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 14.03.13 17:29, Pawel Jakub Dawidek wrote: > Heh, I did consider that as well, but here you check errno twice, > instead of once. Guys, is there anything wrong with the patch I > proposed? Except some obvious bike shed color issues there is nothing wrong with your patch. Regards, erdgeist -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Darwin) iEYEARECAAYFAlFB/zIACgkQuN1wFypsMNMqzQCdHFgaP9XzsRPm8PmQA/bmXmCm G/kAn0oUrTkp80yRSpizfO4GoS/WKo+x =pCkU -----END PGP SIGNATURE----- From owner-freebsd-current@FreeBSD.ORG Thu Mar 14 16:51:14 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 43EDD395; Thu, 14 Mar 2013 16:51:14 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from bigwig.baldwin.cx (bigknife-pt.tunnel.tserv9.chi1.ipv6.he.net [IPv6:2001:470:1f10:75::2]) by mx1.freebsd.org (Postfix) with ESMTP id 13EDFB03; Thu, 14 Mar 2013 16:51:14 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id CA788B96E; Thu, 14 Mar 2013 12:51:11 -0400 (EDT) From: John Baldwin To: Pawel Jakub Dawidek Subject: Re: pidfile_open incorrectly returns EAGAIN when pidfile is locked Date: Thu, 14 Mar 2013 12:50:59 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110714-p25; KDE/4.5.5; amd64; ; ) References: <513F8D20.2050707@erdgeist.org> <201303140942.40945.jhb@freebsd.org> <20130314162958.GD1344@garage.freebsd.pl> In-Reply-To: <20130314162958.GD1344@garage.freebsd.pl> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Message-Id: <201303141250.59521.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Thu, 14 Mar 2013 12:51:12 -0400 (EDT) Cc: Dirk Engling , freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Mar 2013 16:51:14 -0000 On Thursday, March 14, 2013 12:29:58 pm Pawel Jakub Dawidek wrote: > On Thu, Mar 14, 2013 at 09:42:40AM -0400, John Baldwin wrote: > > On Thursday, March 14, 2013 4:44:20 am Pawel Jakub Dawidek wrote: > > > On Thu, Mar 14, 2013 at 08:28:25AM +0100, Dirk Engling wrote: > > > > -----BEGIN PGP SIGNED MESSAGE----- > > > > Hash: SHA1 > > > > > > > > On 13.03.13 23:08, Pawel Jakub Dawidek wrote: > > > > > > > > > I think I considered something similar at first, but the change I > > > > > proposed was optimal, IMHO at the cost of producing pretty large > > > > > diff, because of indentation change. But to be sure, can you send a > > > > > patch of your proposed change? > > > > > > > > http://erdgeist.org/arts/software/Code/pidfile.c.diff > > > > > > Right. Your patch assumes EWOULDBLOCK is equal to EAGAIN, which is true > > > on FreeBSD, but is not portable. Also in case pidptr is NULL you compare > > > errno three times instead of just one (not a big deal of course, just > > > something that could be done a bit more optimal:)). > > > > Geeze, why not just add an else. That's the really short diff: > > Heh, I did consider that as well, but here you check errno twice, > instead of once. Guys, is there anything wrong with the patch I > proposed? I'm sure the compiler can work that out just fine and it should do whatever is most readable to the programmer. I don't care either way. -- John Baldwin From owner-freebsd-current@FreeBSD.ORG Thu Mar 14 17:11:39 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 08378A6A; Thu, 14 Mar 2013 17:11:39 +0000 (UTC) (envelope-from cswiger@mac.com) Received: from nk11p00mm-asmtp009.mac.com (nk11p00mm-asmtp009.mac.com [17.158.161.8]) by mx1.freebsd.org (Postfix) with ESMTP id C07A0D64; Thu, 14 Mar 2013 17:11:38 +0000 (UTC) Received: from cswiger1.apple.com ([17.209.4.71]) by nk11p00mm-asmtp009.mac.com (Oracle Communications Messaging Server 7u4-26.01(7.0.4.26.0) 64bit (built Jul 13 2012)) with ESMTPSA id <0MJN00BN3UEJUA00@nk11p00mm-asmtp009.mac.com>; Thu, 14 Mar 2013 17:11:08 +0000 (GMT) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.10.8626,1.0.431,0.0.0000 definitions=2013-03-14_06:2013-03-14,2013-03-14,1970-01-01 signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 ipscore=0 suspectscore=0 phishscore=0 bulkscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=6.0.2-1302030000 definitions=main-1303140104 Subject: Re: pidfile_open incorrectly returns EAGAIN when pidfile is locked MIME-version: 1.0 (Apple Message framework v1085) Content-type: text/plain; charset=us-ascii From: Chuck Swiger In-reply-to: <201303141250.59521.jhb@freebsd.org> Date: Thu, 14 Mar 2013 10:11:07 -0700 Content-transfer-encoding: 7bit Message-id: <455D2A2E-97FE-42EF-A371-B7D7A9A0E14C@mac.com> References: <513F8D20.2050707@erdgeist.org> <201303140942.40945.jhb@freebsd.org> <20130314162958.GD1344@garage.freebsd.pl> <201303141250.59521.jhb@freebsd.org> To: John Baldwin , Pawel Jakub Dawidek X-Mailer: Apple Mail (2.1085) Cc: freebsd-current Current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Mar 2013 17:11:39 -0000 Hi-- On Mar 14, 2013, at 9:50 AM, John Baldwin wrote: > On Thursday, March 14, 2013 12:29:58 pm Pawel Jakub Dawidek wrote: [ ... ] >> Heh, I did consider that as well, but here you check errno twice, >> instead of once. Guys, is there anything wrong with the patch I >> proposed? > > I'm sure the compiler can work that out just fine and it should do whatever > is most readable to the programmer. I don't care either way. Strong +1. Having the code be correct and readable is much more important then trying to hand-optimize a single-digit # of integer compares in startup code that usually runs ~once per process. (Worrying about and minimizing file access to the pidfile would be a different matter, since the compiler can't optimize around that...) Regards, -- -Chuck From owner-freebsd-current@FreeBSD.ORG Thu Mar 14 19:06:39 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id C69B7D7D for ; Thu, 14 Mar 2013 19:06:39 +0000 (UTC) (envelope-from gyrd-se@thanelange.no) Received: from smtp.getmail.no (smtp.getmail.no [84.208.15.66]) by mx1.freebsd.org (Postfix) with ESMTP id 501D95E5 for ; Thu, 14 Mar 2013 19:06:39 +0000 (UTC) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; charset=ISO-8859-1 Received: from get-mta-scan04.get.basefarm.net ([10.5.16.4]) by get-mta-out01.get.basefarm.net (Sun Java(tm) System Messaging Server 7.0-0.04 64bit (built Jun 20 2008)) with ESMTP id <0MJN00JR8ZQW1Q80@get-mta-out01.get.basefarm.net> for freebsd-current@freebsd.org; Thu, 14 Mar 2013 20:06:32 +0100 (MET) Received: from get-mta-scan04.get.basefarm.net (localhost.localdomain [127.0.0.1]) by localhost (Email Security Appliance) with SMTP id 82F8A770DA_1421FB8B for ; Thu, 14 Mar 2013 19:06:32 +0000 (GMT) Received: from smtp.getmail.no (unknown [10.5.16.4]) by get-mta-scan04.get.basefarm.net (Sophos Email Appliance) with ESMTP id 3246B770BC_1421FB8F for ; Thu, 14 Mar 2013 19:06:32 +0000 (GMT) Received: from cm-84.211.88.167.getinternet.no ([84.211.88.167]) by get-mta-in01.get.basefarm.net (Sun Java(tm) System Messaging Server 7.0-0.04 64bit (built Jun 20 2008)) with SMTP id <0MJN00CZ5ZQRVV10@get-mta-in01.get.basefarm.net> for freebsd-current@freebsd.org; Thu, 14 Mar 2013 20:06:32 +0100 (MET) Received: (qmail 48407 invoked by uid 89); Thu, 14 Mar 2013 20:06:26 +0100 Received: from unknown (HELO ?10.0.10.184?) (gyrd@thanelange.no@77.241.104.2) by cm-84.211.88.167.getinternet.no with SMTP; Thu, 14 Mar 2013 20:06:26 +0100 Message-id: <51421FB2.5070204@thanelange.no> Date: Thu, 14 Mar 2013 20:06:26 +0100 From: Gyrd Thane Lange User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130307 Thunderbird/17.0.4 To: freebsd-current@freebsd.org, Yasir hussan Subject: Re: vlan interface does not repond on untagged packets References: In-reply-to: X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Mar 2013 19:06:39 -0000 On 14.03.2013 15:05, Yasir hussan wrote: > Hi, > > i am creating and testing vlan using these commands, > > *ifconfig arge0 192.168.100.10 netmask 255.255.255.0* > * > * > *ifconfig vlan4 create* > *ifconfig vlan4 vlandev arge0 vlan 4* > *ifconfig vlan4 192.168.1.10 netmask 255.255.255.0* > > here arge0 is the default interface of my ethernet device, This looks about right, you can test it locally on the FreeBSD machine with: freebsd# ifconfig vlan4 vlan4: flags=8843 metric 0 mtu 1500 options=3 ether 50:e5:49:5f:1f:89 inet 192.168.1.10 netmask 0xffffff00 broadcast 192.168.1.255 inet6 fe80::52e5:49ff:fe5f:1f89%vlan4 prefixlen 64 scopeid 0x8 nd6 options=21 media: Ethernet autoselect (100baseTX ) status: active vlan: 4 parent interface: re0 freebsd# ping 192.168.1.10 (you should receive a lot of replies from yourself) > now i want to access vlan4 interface from an other pc which has linux and > is dirctly connected to my freebsd machine, now if i try to ping linux > machine it will send tagged packets but linux does not recogniz it and > leave it, and similarly when i try to ping linux machine to vlan4 interface > on freebsd, linux send untagged packets so vlan4 does not response to it. Unless you have set up vlan interfaces on the Linux machine then this is to be expected. Using instructions from: https://wiki.archlinux.org/index.php/VLAN linux# ip link add link eth0 name eth0.4 type vlan id 4 linux# ip addr add 192.168.1.20/24 brd 192.168.1.255 dev eth0.4 linux# ip link set dev eth0.4 up Note: if you have udev running it will override your "eth0.4" name, and call it something else. After the first command: linux# ip link show (Will give a list. You should probably find something like "eth.4@eth0" near the end. Continue the rest of the commands with whatever part of the name before the "@". I.e. strip away the "@eth0" at end.) Use ifconfig and ping locally to verify that you have the vlan setup. You should now be able to reach both of the machines from each other. Assuming they are connected to the same network switch. > I want that my vlan4 interface could able to recongnize untagged packets > and could respond to it Now this is an entirely new and important requirement! I have read your previous threads, and still don't understand your networking requirement. For a vlan to work, tagging all the packets are essential. All the machines, including all the clients must also have the same vlan configured for it to work. It will *not work* otherwise. What exactly is your requirement? Could you please tell us *why* the other machines are unable to use the primary IP address (192.168.100.10) assigned to the arge0 interface? Once we have a better grasp of the situation we will be able to better guide you. Best regards, Gyrd ^_^ > > Thanks From owner-freebsd-current@FreeBSD.ORG Thu Mar 14 20:19:30 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 1B953852; Thu, 14 Mar 2013 20:19:30 +0000 (UTC) (envelope-from pawel@dawidek.net) Received: from mail.dawidek.net (garage.dawidek.net [91.121.88.72]) by mx1.freebsd.org (Postfix) with ESMTP id D3EBB943; Thu, 14 Mar 2013 20:19:29 +0000 (UTC) Received: from localhost (89-73-195-149.dynamic.chello.pl [89.73.195.149]) by mail.dawidek.net (Postfix) with ESMTPSA id E38A0A77; Thu, 14 Mar 2013 21:16:14 +0100 (CET) Date: Thu, 14 Mar 2013 21:21:02 +0100 From: Pawel Jakub Dawidek To: Chuck Swiger Subject: Re: pidfile_open incorrectly returns EAGAIN when pidfile is locked Message-ID: <20130314202101.GA1446@garage.freebsd.pl> References: <513F8D20.2050707@erdgeist.org> <201303140942.40945.jhb@freebsd.org> <20130314162958.GD1344@garage.freebsd.pl> <201303141250.59521.jhb@freebsd.org> <455D2A2E-97FE-42EF-A371-B7D7A9A0E14C@mac.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="cWoXeonUoKmBZSoM" Content-Disposition: inline In-Reply-To: <455D2A2E-97FE-42EF-A371-B7D7A9A0E14C@mac.com> X-OS: FreeBSD 10.0-CURRENT amd64 User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-current Current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Mar 2013 20:19:30 -0000 --cWoXeonUoKmBZSoM Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Mar 14, 2013 at 10:11:07AM -0700, Chuck Swiger wrote: > Hi-- >=20 > On Mar 14, 2013, at 9:50 AM, John Baldwin wrote: > > On Thursday, March 14, 2013 12:29:58 pm Pawel Jakub Dawidek wrote: >=20 > [ ... ] > >> Heh, I did consider that as well, but here you check errno twice, > >> instead of once. Guys, is there anything wrong with the patch I > >> proposed? > >=20 > > I'm sure the compiler can work that out just fine and it should do what= ever > > is most readable to the programmer. I don't care either way. >=20 > Strong +1. Having the code be correct and readable is much more important > then trying to hand-optimize a single-digit # of integer compares in > startup code that usually runs ~once per process. Well, I think my version is more obvious, just the diff is larger. Anyway, I think enough has been said already about this crucial change:) --=20 Pawel Jakub Dawidek http://www.wheelsystems.com FreeBSD committer http://www.FreeBSD.org Am I Evil? Yes, I Am! http://tupytaj.pl --cWoXeonUoKmBZSoM Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEARECAAYFAlFCMS0ACgkQForvXbEpPzT25ACgzB7icyos1h0RnM56kRx7AGHI HuEAnij80bFynlzTeZycNPCKbLnYfNg7 =29eY -----END PGP SIGNATURE----- --cWoXeonUoKmBZSoM-- From owner-freebsd-current@FreeBSD.ORG Thu Mar 14 20:35:42 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 07F072FD; Thu, 14 Mar 2013 20:35:42 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from bigwig.baldwin.cx (bigknife-pt.tunnel.tserv9.chi1.ipv6.he.net [IPv6:2001:470:1f10:75::2]) by mx1.freebsd.org (Postfix) with ESMTP id D3FE8A12; Thu, 14 Mar 2013 20:35:41 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 43BB7B94C; Thu, 14 Mar 2013 16:35:41 -0400 (EDT) From: John Baldwin To: Pawel Jakub Dawidek Subject: Re: pidfile_open incorrectly returns EAGAIN when pidfile is locked Date: Thu, 14 Mar 2013 16:34:28 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110714-p25; KDE/4.5.5; amd64; ; ) References: <513F8D20.2050707@erdgeist.org> <455D2A2E-97FE-42EF-A371-B7D7A9A0E14C@mac.com> <20130314202101.GA1446@garage.freebsd.pl> In-Reply-To: <20130314202101.GA1446@garage.freebsd.pl> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Message-Id: <201303141634.28269.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Thu, 14 Mar 2013 16:35:41 -0400 (EDT) Cc: freebsd-current Current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 14 Mar 2013 20:35:42 -0000 On Thursday, March 14, 2013 4:21:02 pm Pawel Jakub Dawidek wrote: > On Thu, Mar 14, 2013 at 10:11:07AM -0700, Chuck Swiger wrote: > > Hi-- > > > > On Mar 14, 2013, at 9:50 AM, John Baldwin wrote: > > > On Thursday, March 14, 2013 12:29:58 pm Pawel Jakub Dawidek wrote: > > > > [ ... ] > > >> Heh, I did consider that as well, but here you check errno twice, > > >> instead of once. Guys, is there anything wrong with the patch I > > >> proposed? > > > > > > I'm sure the compiler can work that out just fine and it should do whatever > > > is most readable to the programmer. I don't care either way. > > > > Strong +1. Having the code be correct and readable is much more important > > then trying to hand-optimize a single-digit # of integer compares in > > startup code that usually runs ~once per process. > > Well, I think my version is more obvious, just the diff is larger. > Anyway, I think enough has been said already about this crucial change:) Yours is fine, commit it already. -- John Baldwin From owner-freebsd-current@FreeBSD.ORG Fri Mar 15 06:49:20 2013 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 1A132C1E; Fri, 15 Mar 2013 06:49:20 +0000 (UTC) (envelope-from tinderbox@freebsd.org) Received: from freebsd-current.sentex.ca (freebsd-current.sentex.ca [64.7.128.98]) by mx1.freebsd.org (Postfix) with ESMTP id DAD94326; Fri, 15 Mar 2013 06:49:19 +0000 (UTC) Received: from freebsd-current.sentex.ca (localhost [127.0.0.1]) by freebsd-current.sentex.ca (8.14.5/8.14.5) with ESMTP id r2F6nD3A041040; Fri, 15 Mar 2013 02:49:13 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-current.sentex.ca (8.14.5/8.14.5/Submit) id r2F6nDC5041034; Fri, 15 Mar 2013 06:49:13 GMT (envelope-from tinderbox@freebsd.org) Date: Fri, 15 Mar 2013 06:49:13 GMT Message-Id: <201303150649.r2F6nDC5041034@freebsd-current.sentex.ca> X-Authentication-Warning: freebsd-current.sentex.ca: tinderbox set sender to FreeBSD Tinderbox using -f Sender: FreeBSD Tinderbox From: FreeBSD Tinderbox To: FreeBSD Tinderbox , , Subject: [head tinderbox] failure on amd64/amd64 Precedence: bulk X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Mar 2013 06:49:20 -0000 TB --- 2013-03-15 06:30:20 - tinderbox 2.10 running on freebsd-current.sentex.ca TB --- 2013-03-15 06:30:20 - FreeBSD freebsd-current.sentex.ca 8.3-PRERELEASE FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012 des@freebsd-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64 TB --- 2013-03-15 06:30:20 - starting HEAD tinderbox run for amd64/amd64 TB --- 2013-03-15 06:30:20 - cleaning the object tree TB --- 2013-03-15 06:30:20 - /usr/local/bin/svn stat /src TB --- 2013-03-15 06:30:24 - At svn revision 248313 TB --- 2013-03-15 06:30:25 - building world TB --- 2013-03-15 06:30:25 - CROSS_BUILD_TESTING=YES TB --- 2013-03-15 06:30:25 - MAKEOBJDIRPREFIX=/obj TB --- 2013-03-15 06:30:25 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-03-15 06:30:25 - SRCCONF=/dev/null TB --- 2013-03-15 06:30:25 - TARGET=amd64 TB --- 2013-03-15 06:30:25 - TARGET_ARCH=amd64 TB --- 2013-03-15 06:30:25 - TZ=UTC TB --- 2013-03-15 06:30:25 - __MAKE_CONF=/dev/null TB --- 2013-03-15 06:30:25 - cd /src TB --- 2013-03-15 06:30:25 - /usr/bin/make -B buildworld >>> Building an up-to-date make(1) >>> World build started on Fri Mar 15 06:30:30 UTC 2013 >>> Rebuilding the temporary build tree >>> stage 1.1: legacy release compatibility shims >>> stage 1.2: bootstrap tools >>> stage 2.1: cleaning up the object tree >>> stage 2.2: rebuilding the object tree >>> stage 2.3: build tools >>> stage 3: cross tools [...] c++ -O2 -pipe -I/src/lib/clang/libclangcodegen/../../../contrib/llvm/include -I/src/lib/clang/libclangcodegen/../../../contrib/llvm/tools/clang/include -I/src/lib/clang/libclangcodegen/../../../contrib/llvm/tools/clang/lib/CodeGen -I. -I/src/lib/clang/libclangcodegen/../../../contrib/llvm/../../lib/clang/include -DLLVM_ON_UNIX -DLLVM_ON_FREEBSD -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS -fno-strict-aliasing -DLLVM_DEFAULT_TARGET_TRIPLE=\"x86_64-unknown-freebsd10.0\" -DLLVM_HOSTTRIPLE=\"x86_64-unknown-freebsd10.0\" -DDEFAULT_SYSROOT=\"/obj/amd64.amd64/src/tmp\" -I/obj/amd64.amd64/src/tmp/legacy/usr/include -fno-exceptions -fno-rtti -c /src/lib/clang/libclangcodegen/../../../contrib/llvm/tools/clang/lib/CodeGen/CodeGenModule.cpp -o CodeGenModule.o c++ -O2 -pipe -I/src/lib/clang/libclangcodegen/../../../contrib/llvm/include -I/src/lib/clang/libclangcodegen/../../../contrib/llvm/tools/clang/include -I/src/lib/clang/libclangcodegen/../../../contrib/llvm/tools/clang/lib/CodeGen -I. -I/src/lib/clang/libclangcodegen/../../../contrib/llvm/../../lib/clang/include -DLLVM_ON_UNIX -DLLVM_ON_FREEBSD -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS -fno-strict-aliasing -DLLVM_DEFAULT_TARGET_TRIPLE=\"x86_64-unknown-freebsd10.0\" -DLLVM_HOSTTRIPLE=\"x86_64-unknown-freebsd10.0\" -DDEFAULT_SYSROOT=\"/obj/amd64.amd64/src/tmp\" -I/obj/amd64.amd64/src/tmp/legacy/usr/include -fno-exceptions -fno-rtti -c /src/lib/clang/libclangcodegen/../../../contrib/llvm/tools/clang/lib/CodeGen/CodeGenTBAA.cpp -o CodeGenTBAA.o c++ -O2 -pipe -I/src/lib/clang/libclangcodegen/../../../contrib/llvm/include -I/src/lib/clang/libclangcodegen/../../../contrib/llvm/tools/clang/include -I/src/lib/clang/libclangcodegen/../../../contrib/llvm/tools/clang/lib/CodeGen -I. -I/src/lib/clang/libclangcodegen/../../../contrib/llvm/../../lib/clang/include -DLLVM_ON_UNIX -DLLVM_ON_FREEBSD -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS -fno-strict-aliasing -DLLVM_DEFAULT_TARGET_TRIPLE=\"x86_64-unknown-freebsd10.0\" -DLLVM_HOSTTRIPLE=\"x86_64-unknown-freebsd10.0\" -DDEFAULT_SYSROOT=\"/obj/amd64.amd64/src/tmp\" -I/obj/amd64.amd64/src/tmp/legacy/usr/include -fno-exceptions -fno-rtti -c /src/lib/clang/libclangcodegen/../../../contrib/llvm/tools/clang/lib/CodeGen/CodeGenTypes.cpp -o CodeGenTypes.o /src/lib/clang/libclangcodegen/../../../contrib/llvm/tools/clang/lib/CodeGen/CodeGenTypes.cpp: In destructor 'clang::CodeGen::CodeGenTypes::~CodeGenTypes()': /src/lib/clang/libclangcodegen/../../../contrib/llvm/tools/clang/lib/CodeGen/CodeGenTypes.cpp:39: internal compiler error: in var_ann, at tree-flow-inline.h:127 Please submit a full bug report, with preprocessed source if appropriate. See for instructions. *** [CodeGenTypes.o] Error code 1 Stop in /src/lib/clang/libclangcodegen. *** [all] Error code 1 Stop in /src/lib/clang. *** [cross-tools] Error code 1 Stop in /src. *** [_cross-tools] Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2013-03-15 06:49:13 - WARNING: /usr/bin/make returned exit code 1 TB --- 2013-03-15 06:49:13 - ERROR: failed to build world TB --- 2013-03-15 06:49:13 - 941.80 user 120.08 system 1132.81 real http://tinderbox.freebsd.org/tinderbox-head-ss-build-HEAD-amd64-amd64.full From owner-freebsd-current@FreeBSD.ORG Fri Mar 15 13:41:01 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 3A01564E for ; Fri, 15 Mar 2013 13:41:01 +0000 (UTC) (envelope-from andre@freebsd.org) Received: from c00l3r.networx.ch (c00l3r.networx.ch [62.48.2.2]) by mx1.freebsd.org (Postfix) with ESMTP id D075AED for ; Fri, 15 Mar 2013 13:41:00 +0000 (UTC) Received: (qmail 64416 invoked from network); 15 Mar 2013 14:53:01 -0000 Received: from unknown (HELO [62.48.0.94]) ([62.48.0.94]) (envelope-sender ) by c00l3r.networx.ch (qmail-ldap-1.03) with SMTP for ; 15 Mar 2013 14:53:01 -0000 Message-ID: <514324E8.30209@freebsd.org> Date: Fri, 15 Mar 2013 14:40:56 +0100 From: Andre Oppermann User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130215 Thunderbird/17.0.3 MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: NewNFS vs. oldNFS for 10.0? Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: rmacklem@uoguelph.ca X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Mar 2013 13:41:01 -0000 Hi Rick, all, is there a plan to decide for one NFS implementation for FreeBSD 10.0, or to keep both around indefinately? I'm talking about: oldNFS in sys/{nfs, nfsclient, nfsserver} NFSv2+NFSv3 newNFS in sys/fs/{nfs, nfsclient, nfsserver} NFSv2+NFSv3+NFSv4 NewNFS supports newer NFS standards and seems to have proven itself in some quite heavy traffic environments. Is there any reason to keep oldNFS around other than nostalgic? -- Andre From owner-freebsd-current@FreeBSD.ORG Fri Mar 15 13:53:24 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id F24FBD0B; Fri, 15 Mar 2013 13:53:23 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-jnhn.mail.uoguelph.ca (esa-jnhn.mail.uoguelph.ca [131.104.91.44]) by mx1.freebsd.org (Postfix) with ESMTP id A0A751C9; Fri, 15 Mar 2013 13:53:23 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AqEEAGAmQ1GDaFvO/2dsb2JhbABDiDi8ZYICdIIqAQEBBAEBASArIAsbGAICDRkCKQEJJgYIBwQBHASHcwywG5JwgSOBKosYfDQHgi2BEwOUHYI+gR+PY4MmIDKBBTU X-IronPort-AV: E=Sophos;i="4.84,850,1355115600"; d="scan'208";a="21377539" Received: from erie.cs.uoguelph.ca (HELO zcs3.mail.uoguelph.ca) ([131.104.91.206]) by esa-jnhn.mail.uoguelph.ca with ESMTP; 15 Mar 2013 09:53:21 -0400 Received: from zcs3.mail.uoguelph.ca (localhost.localdomain [127.0.0.1]) by zcs3.mail.uoguelph.ca (Postfix) with ESMTP id EA5C9B3F15; Fri, 15 Mar 2013 09:53:21 -0400 (EDT) Date: Fri, 15 Mar 2013 09:53:21 -0400 (EDT) From: Rick Macklem To: Andre Oppermann Message-ID: <2090268844.3936361.1363355601938.JavaMail.root@erie.cs.uoguelph.ca> In-Reply-To: <514324E8.30209@freebsd.org> Subject: Re: NewNFS vs. oldNFS for 10.0? MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [172.17.91.201] X-Mailer: Zimbra 6.0.10_GA_2692 (ZimbraWebClient - FF3.0 (Win)/6.0.10_GA_2692) Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Mar 2013 13:53:24 -0000 Andre Oppermann wrote: > Hi Rick, all, > > is there a plan to decide for one NFS implementation for FreeBSD 10.0, > or to keep both around indefinately? > > I'm talking about: > oldNFS in sys/{nfs, nfsclient, nfsserver} NFSv2+NFSv3 > newNFS in sys/fs/{nfs, nfsclient, nfsserver} NFSv2+NFSv3+NFSv4 > > NewNFS supports newer NFS standards and seems to have proven itself in > some quite heavy traffic environments. > > Is there any reason to keep oldNFS around other than nostalgic? > I was planning on asking the "collective" that question at some point. I think the newNFS works well enough that it can become the only NFS in the kernel for 10.0, but I don't see that as my decision. I am only aware of 2 possible regressions of the new one w.r.t. the old one: - A performance issue for the new server when under heavy NFS over TCP load, where there is excessive contention on a single mutex, etc. - I think we now have a patch that resolves this, which is being tested by Garrett Wollman. If testing goes well and a refined version of the patch makes it into head, this should be resolved. - A few sites have run into performance problems for the new NFS client, that were a result of it using a larger default I/O size (64K vs 32K for the old one). I believe the performance problem was related to network interface/driver issues for the larger 64K+ RPC messages. This can be dealt with 2 ways: - Leave it as it is now and then any site with this problem will need to use rsize=32768,wsize=32768 mount options to avoid it. OR - Modify the new client so that it uses 32K by default instead of the size specified by a server. (Most servers specify 64K or larger these days. FreeBSD is currently at 64. Solaris is 256K and allows 1Mbyte. So, I was going to ask the question. Maybe now is the time. Any comments w.r.t. removing the oldNFS from the kernel for 10.0 would be appreciated, rick > -- > Andre > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to > "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@FreeBSD.ORG Fri Mar 15 14:02:01 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 42013430; Fri, 15 Mar 2013 14:02:01 +0000 (UTC) (envelope-from lars@netapp.com) Received: from mx12.netapp.com (mx12.netapp.com [216.240.18.77]) by mx1.freebsd.org (Postfix) with ESMTP id 252EE28D; Fri, 15 Mar 2013 14:02:01 +0000 (UTC) X-IronPort-AV: E=Sophos;i="4.84,850,1355126400"; d="scan'208";a="31091599" Received: from smtp1.corp.netapp.com ([10.57.156.124]) by mx12-out.netapp.com with ESMTP; 15 Mar 2013 07:02:00 -0700 Received: from vmwexceht04-prd.hq.netapp.com (vmwexceht04-prd.hq.netapp.com [10.106.77.34]) by smtp1.corp.netapp.com (8.13.1/8.13.1/NTAP-1.6) with ESMTP id r2FE20jR003924; Fri, 15 Mar 2013 07:02:00 -0700 (PDT) Received: from SACEXCMBX01-PRD.hq.netapp.com ([169.254.2.218]) by vmwexceht04-prd.hq.netapp.com ([10.106.77.34]) with mapi id 14.02.0342.003; Fri, 15 Mar 2013 07:02:00 -0700 From: "Eggert, Lars" To: Andre Oppermann Subject: Re: NewNFS vs. oldNFS for 10.0? Thread-Topic: NewNFS vs. oldNFS for 10.0? Thread-Index: AQHOIYLPEsCxsg9cck2Q0y59+EQ/fpinPaKA Date: Fri, 15 Mar 2013 14:01:59 +0000 Message-ID: References: <514324E8.30209@freebsd.org> In-Reply-To: <514324E8.30209@freebsd.org> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.104.60.116] Content-Type: text/plain; charset="us-ascii" Content-ID: <570D0F23741E6E4CB1284E4004CC4BA8@tahoe.netapp.com> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: "" , "" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Mar 2013 14:02:01 -0000 Hi, this reminds me that I ran into an issue lately with the new NFS and lockin= g for NFSv3 mounts on a client that ran -CURRENT and a server that ran -STA= BLE. When I ran "portmaster -a" on the client, which mounted /usr/ports and /usr= /local, as well as the location of the respective sqlite databases over NFS= v3, the client network stack became unresponsive on all interfaces for 30 o= r so seconds and e.g. SSH connections broke. The serial console remained ac= tive throughout, and the system didn't crash. About a minute after the wedg= ie I could SSH into the box again, too. The issue went away when I killed lockd on the client, but that caused the = sqlite database to become corrupted over time. The workaround for me was to= move to NFSv4, which has been working fine. (One more reason to make it th= e default...) I'm not really sure how to debug this further, but would be willing to work= with someone off-list who'd tell me what tests to run. Lars= From owner-freebsd-current@FreeBSD.ORG Fri Mar 15 14:08:41 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id AAD21697; Fri, 15 Mar 2013 14:08:41 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-jnhn.mail.uoguelph.ca (esa-jnhn.mail.uoguelph.ca [131.104.91.44]) by mx1.freebsd.org (Postfix) with ESMTP id 636A92FE; Fri, 15 Mar 2013 14:08:41 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AqAEAGgqQ1GDaFvO/2dsb2JhbABDiDG8ZYF7dIIqAQEEASNWBRYYAgINGQJZBoghBrAhknKBI4EqjBQ0B4ItgRMDlluRAoMmIIFs X-IronPort-AV: E=Sophos;i="4.84,850,1355115600"; d="scan'208";a="21380755" Received: from erie.cs.uoguelph.ca (HELO zcs3.mail.uoguelph.ca) ([131.104.91.206]) by esa-jnhn.mail.uoguelph.ca with ESMTP; 15 Mar 2013 10:08:40 -0400 Received: from zcs3.mail.uoguelph.ca (localhost.localdomain [127.0.0.1]) by zcs3.mail.uoguelph.ca (Postfix) with ESMTP id 7892FB3F43; Fri, 15 Mar 2013 10:08:40 -0400 (EDT) Date: Fri, 15 Mar 2013 10:08:40 -0400 (EDT) From: Rick Macklem To: Lars Eggert Message-ID: <1547734002.3937074.1363356520474.JavaMail.root@erie.cs.uoguelph.ca> In-Reply-To: Subject: Re: NewNFS vs. oldNFS for 10.0? MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [172.17.91.202] X-Mailer: Zimbra 6.0.10_GA_2692 (ZimbraWebClient - FF3.0 (Win)/6.0.10_GA_2692) Cc: freebsd-current , Andre Oppermann X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Mar 2013 14:08:41 -0000 Lars Eggert wrote: > Hi, > > this reminds me that I ran into an issue lately with the new NFS and > locking for NFSv3 mounts on a client that ran -CURRENT and a server > that ran -STABLE. > > When I ran "portmaster -a" on the client, which mounted /usr/ports and > /usr/local, as well as the location of the respective sqlite databases > over NFSv3, the client network stack became unresponsive on all > interfaces for 30 or so seconds and e.g. SSH connections broke. The > serial console remained active throughout, and the system didn't > crash. About a minute after the wedgie I could SSH into the box again, > too. > > The issue went away when I killed lockd on the client, but that caused > the sqlite database to become corrupted over time. The workaround for > me was to move to NFSv4, which has been working fine. (One more reason > to make it the default...) > I've mentioned limitations w.r.t. the design of the NLM protocol (rpc.lockd) before. Any time there is any kind of network topology issue, it will run into difficulties. There may also be other issues. However, since both the old and new client use the same rpc.lockd in the same way (the new one just cribbed the code from the old one), I think the same problem would exist for the old one. As such, I don't believe this is a regression. rick > I'm not really sure how to debug this further, but would be willing to > work with someone off-list who'd tell me what tests to run. > > Lars From owner-freebsd-current@FreeBSD.ORG Fri Mar 15 14:24:18 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id B5A768E5 for ; Fri, 15 Mar 2013 14:24:18 +0000 (UTC) (envelope-from andre@freebsd.org) Received: from c00l3r.networx.ch (c00l3r.networx.ch [62.48.2.2]) by mx1.freebsd.org (Postfix) with ESMTP id 2AA973C8 for ; Fri, 15 Mar 2013 14:24:17 +0000 (UTC) Received: (qmail 66578 invoked from network); 15 Mar 2013 15:36:18 -0000 Received: from unknown (HELO [62.48.0.94]) ([62.48.0.94]) (envelope-sender ) by c00l3r.networx.ch (qmail-ldap-1.03) with SMTP for ; 15 Mar 2013 15:36:18 -0000 Message-ID: <51432F0D.2040002@freebsd.org> Date: Fri, 15 Mar 2013 15:24:13 +0100 From: Andre Oppermann User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130215 Thunderbird/17.0.3 MIME-Version: 1.0 To: "Eggert, Lars" Subject: Re: NewNFS vs. oldNFS for 10.0? References: <514324E8.30209@freebsd.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "" , "" X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Mar 2013 14:24:18 -0000 On 15.03.2013 15:01, Eggert, Lars wrote: > Hi, > > this reminds me that I ran into an issue lately with the new NFS and locking for NFSv3 mounts on a client that ran -CURRENT and a server that ran > -STABLE. > > When I ran "portmaster -a" on the client, which mounted /usr/ports and /usr/local, as well as the location of the respective sqlite databases over > NFSv3, the client network stack became unresponsive on all interfaces for 30 or so seconds and e.g. SSH connections broke. The serial console > remained active throughout, and the system didn't crash. About a minute after the wedgie I could SSH into the box again, too. The total wedge of all interfaces certainly shouldn't happen. This smells like blocking on a lock on a socket_upcall() thereby wedging tcp_input. I don't know the lockd code so maybe Rick knows how this could happen. -- Andre > The issue went away when I killed lockd on the client, but that caused the sqlite database to become corrupted over time. The workaround for me > was to move to NFSv4, which has been working fine. (One more reason to make it the default...) > > I'm not really sure how to debug this further, but would be willing to work with someone off-list who'd tell me what tests to run. > > Lars _______________________________________________ freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > > From owner-freebsd-current@FreeBSD.ORG Fri Mar 15 14:43:18 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id DD945E39 for ; Fri, 15 Mar 2013 14:43:18 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from bigwig.baldwin.cx (bigknife-pt.tunnel.tserv9.chi1.ipv6.he.net [IPv6:2001:470:1f10:75::2]) by mx1.freebsd.org (Postfix) with ESMTP id BB794682 for ; Fri, 15 Mar 2013 14:43:18 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 190CEB94A; Fri, 15 Mar 2013 10:43:18 -0400 (EDT) From: John Baldwin To: freebsd-current@freebsd.org Subject: Re: reservation of n, n (3) failed Date: Fri, 15 Mar 2013 09:43:42 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110714-p25; KDE/4.5.5; amd64; ; ) References: <1363239664.81230@da3m0n8t3r.com> In-Reply-To: <1363239664.81230@da3m0n8t3r.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Message-Id: <201303150943.42474.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Fri, 15 Mar 2013 10:43:18 -0400 (EDT) Cc: Waitman Gobble X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Mar 2013 14:43:18 -0000 On Thursday, March 14, 2013 1:41:04 am Waitman Gobble wrote: > > Hi, > > I swapped out the CPU on this machine today, I don't recall seeing these messages previously: > > acpi0: reservation of 0, a0000 (3) failed > acpi0: reservation of 100000, bfcd0000 (3) failed You can ignore those. acpi is trying to reserve the addresses used for RAM as system resources, but the ram0 driver has already done so. -- John Baldwin From owner-freebsd-current@FreeBSD.ORG Fri Mar 15 14:43:22 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id E4978F32; Fri, 15 Mar 2013 14:43:22 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from bigwig.baldwin.cx (bigknife-pt.tunnel.tserv9.chi1.ipv6.he.net [IPv6:2001:470:1f10:75::2]) by mx1.freebsd.org (Postfix) with ESMTP id C4C5D684; Fri, 15 Mar 2013 14:43:22 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 3688FB948; Fri, 15 Mar 2013 10:43:22 -0400 (EDT) From: John Baldwin To: freebsd-current@freebsd.org Subject: Re: NewNFS vs. oldNFS for 10.0? Date: Fri, 15 Mar 2013 09:46:28 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110714-p25; KDE/4.5.5; amd64; ; ) References: <514324E8.30209@freebsd.org> In-Reply-To: <514324E8.30209@freebsd.org> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201303150946.29100.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Fri, 15 Mar 2013 10:43:22 -0400 (EDT) Cc: rmacklem@uoguelph.ca, Andre Oppermann X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Mar 2013 14:43:23 -0000 On Friday, March 15, 2013 9:40:56 am Andre Oppermann wrote: > Hi Rick, all, > > is there a plan to decide for one NFS implementation for FreeBSD 10.0, > or to keep both around indefinately? > > I'm talking about: > oldNFS in sys/{nfs, nfsclient, nfsserver} NFSv2+NFSv3 > newNFS in sys/fs/{nfs, nfsclient, nfsserver} NFSv2+NFSv3+NFSv4 > > NewNFS supports newer NFS standards and seems to have proven itself in > some quite heavy traffic environments. > > Is there any reason to keep oldNFS around other than nostalgic? It can probably be removed. It's kind of handy to keep around as long as 8.x is around since it uses oldNFS by default as it makes merging bugfixes to the NFS client a bit easier (you fix both clients in HEAD and can then just svn merge both of those to 8 and 9). Having several fixes to the NFS client recently and being in a position of still using 8.x with oldNFS in production, I would prefer to not remove it quite yet. -- John Baldwin From owner-freebsd-current@FreeBSD.ORG Fri Mar 15 15:24:37 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 42A24250 for ; Fri, 15 Mar 2013 15:24:37 +0000 (UTC) (envelope-from andre@freebsd.org) Received: from c00l3r.networx.ch (c00l3r.networx.ch [62.48.2.2]) by mx1.freebsd.org (Postfix) with ESMTP id 93FF2890 for ; Fri, 15 Mar 2013 15:24:36 +0000 (UTC) Received: (qmail 70835 invoked from network); 15 Mar 2013 16:36:36 -0000 Received: from unknown (HELO [62.48.0.94]) ([62.48.0.94]) (envelope-sender ) by c00l3r.networx.ch (qmail-ldap-1.03) with SMTP for ; 15 Mar 2013 16:36:36 -0000 Message-ID: <51433D30.30405@freebsd.org> Date: Fri, 15 Mar 2013 16:24:32 +0100 From: Andre Oppermann User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130215 Thunderbird/17.0.3 MIME-Version: 1.0 To: John Baldwin Subject: Re: NewNFS vs. oldNFS for 10.0? References: <514324E8.30209@freebsd.org> <201303150946.29100.jhb@freebsd.org> In-Reply-To: <201303150946.29100.jhb@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org, rmacklem@uoguelph.ca X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Mar 2013 15:24:37 -0000 On 15.03.2013 14:46, John Baldwin wrote: > On Friday, March 15, 2013 9:40:56 am Andre Oppermann wrote: >> Hi Rick, all, >> >> is there a plan to decide for one NFS implementation for FreeBSD 10.0, >> or to keep both around indefinately? >> >> I'm talking about: >> oldNFS in sys/{nfs, nfsclient, nfsserver} NFSv2+NFSv3 >> newNFS in sys/fs/{nfs, nfsclient, nfsserver} NFSv2+NFSv3+NFSv4 >> >> NewNFS supports newer NFS standards and seems to have proven itself in >> some quite heavy traffic environments. >> >> Is there any reason to keep oldNFS around other than nostalgic? > > It can probably be removed. It's kind of handy to keep around as long as 8.x > is around since it uses oldNFS by default as it makes merging bugfixes to the > NFS client a bit easier (you fix both clients in HEAD and can then just svn > merge both of those to 8 and 9). Having several fixes to the NFS client > recently and being in a position of still using 8.x with oldNFS in production, > I would prefer to not remove it quite yet. Do you have a timeframe on the sunset of oldNFS in HEAD so we can communicate a) that oldNFS won't be in 10.0; and b) it will go on date X? Would it make sense to make oldNFS more difficult to compile into the kernel on HEAD to notify all those with legacy kernel config files? -- Andre From owner-freebsd-current@FreeBSD.ORG Fri Mar 15 15:45:27 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 92BE4815; Fri, 15 Mar 2013 15:45:27 +0000 (UTC) (envelope-from uzimac@da3m0n8t3r.com) Received: from z.umatar.com (z.umatar.com [66.135.39.87]) by mx1.freebsd.org (Postfix) with ESMTP id 66D9F9AA; Fri, 15 Mar 2013 15:45:27 +0000 (UTC) Received: from z.umatar.com (localhost [127.0.0.1]) by z.umatar.com (8.14.5/8.14.3) with ESMTP id r2FFjQmT025303; Fri, 15 Mar 2013 08:45:26 -0700 (PDT) (envelope-from uzimac@da3m0n8t3r.com) Received: (from uzimac@localhost) by z.umatar.com (8.14.5/8.14.3/Submit) id r2FFjQh3025302; Fri, 15 Mar 2013 08:45:26 -0700 (PDT) (envelope-from uzimac@da3m0n8t3r.com) X-Authentication-Warning: z.umatar.com: uzimac set sender to uzimac@da3m0n8t3r.com using -f From: "Waitman Gobble" Subject: Re: reservation of n, n (3) failed To: John Baldwin Message-Id: <1363362326.25215@da3m0n8t3r.com> X-Originating-IP: 70.90.171.37 X-Mailer: Usermin 1.510 In-Reply-To: <201303150943.42474.jhb@freebsd.org> Date: Fri, 15 Mar 2013 08:45:26 -0700 (PDT) MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="bound1363362326" Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Mar 2013 15:45:27 -0000 This is a multi-part message in MIME format. --bound1363362326 Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 7bit John Baldwin wrote .. > On Thursday, March 14, 2013 1:41:04 am Waitman Gobble wrote: > > > > Hi, > > > > I swapped out the CPU on this machine today, I don't recall seeing these messages > previously: > > > > acpi0: reservation of 0, a0000 (3) failed > > acpi0: reservation of 100000, bfcd0000 (3) failed > > You can ignore those. acpi is trying to reserve the addresses used for RAM > as system resources, but the ram0 driver has already done so. > > -- > John Baldwin Hi, Thank you, I appreciate the info. -- Waitman Gobble San Jose California USA --bound1363362326-- From owner-freebsd-current@FreeBSD.ORG Fri Mar 15 16:55:25 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 383DAC96; Fri, 15 Mar 2013 16:55:25 +0000 (UTC) (envelope-from bright@mu.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id 1B922D74; Fri, 15 Mar 2013 16:55:25 +0000 (UTC) Received: from kruse-124.4.ixsystems.com (drawbridge.ixsystems.com [206.40.55.65]) by elvis.mu.org (Postfix) with ESMTPSA id AD1F71A3E09; Fri, 15 Mar 2013 09:55:24 -0700 (PDT) Message-ID: <51435271.2040402@mu.org> Date: Fri, 15 Mar 2013 09:55:13 -0700 From: Alfred Perlstein User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130307 Thunderbird/17.0.4 MIME-Version: 1.0 To: Andre Oppermann Subject: Re: NewNFS vs. oldNFS for 10.0? References: <514324E8.30209@freebsd.org> <201303150946.29100.jhb@freebsd.org> <51433D30.30405@freebsd.org> In-Reply-To: <51433D30.30405@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: rmacklem@uoguelph.ca, freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Mar 2013 16:55:25 -0000 On 3/15/13 8:24 AM, Andre Oppermann wrote: > On 15.03.2013 14:46, John Baldwin wrote: >> On Friday, March 15, 2013 9:40:56 am Andre Oppermann wrote: >>> Hi Rick, all, >>> >>> is there a plan to decide for one NFS implementation for FreeBSD 10.0, >>> or to keep both around indefinately? >>> >>> I'm talking about: >>> oldNFS in sys/{nfs, nfsclient, nfsserver} NFSv2+NFSv3 >>> newNFS in sys/fs/{nfs, nfsclient, nfsserver} NFSv2+NFSv3+NFSv4 >>> >>> NewNFS supports newer NFS standards and seems to have proven itself in >>> some quite heavy traffic environments. >>> >>> Is there any reason to keep oldNFS around other than nostalgic? >> >> It can probably be removed. It's kind of handy to keep around as >> long as 8.x >> is around since it uses oldNFS by default as it makes merging >> bugfixes to the >> NFS client a bit easier (you fix both clients in HEAD and can then >> just svn >> merge both of those to 8 and 9). Having several fixes to the NFS client >> recently and being in a position of still using 8.x with oldNFS in >> production, >> I would prefer to not remove it quite yet. > > Do you have a timeframe on the sunset of oldNFS in HEAD so we can > communicate > a) that oldNFS won't be in 10.0; and b) it will go on date X? > > Would it make sense to make oldNFS more difficult to compile into the > kernel > on HEAD to notify all those with legacy kernel config files? > NFS is a key feature of FreeBSD. Prematurely removing the old code as a failsafe fallback for long time users and those building appliances on FreeBSD would be tremendously risky for those users and consequently for FreeBSD's reputation. The old NFS code in FreeBSD took many years to become stable and still occasionally has regressions introduced due to other system changes. The new code, while really good and very ambitions really deserves more time to soak than what we have given it. Just recently our team has found issues with performance, stability and interoperability that gave us concern and forces us to use the old nfs system. While we certainly should encourage people to use the new nfs code, that does not require us to break old kernel configs nor to prematurely remove a codebase that has many years of testing. Finally, I think it is really premature to declare a sunset for the oldnfs until the users are gushing with approval over the new system. -Alfred From owner-freebsd-current@FreeBSD.ORG Fri Mar 15 17:55:06 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 4C543C45; Fri, 15 Mar 2013 17:55:06 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wi0-x22e.google.com (mail-wi0-x22e.google.com [IPv6:2a00:1450:400c:c05::22e]) by mx1.freebsd.org (Postfix) with ESMTP id B5CAD1C7; Fri, 15 Mar 2013 17:55:05 +0000 (UTC) Received: by mail-wi0-f174.google.com with SMTP id hi8so793469wib.1 for ; Fri, 15 Mar 2013 10:55:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=nOR9Incd0z1X+JOBTntv2yQsK/H9gmZfshZbzezx9DE=; b=tOlmysuKXQKgoa7uuDKwHfIt9V7Aean8zdf5Ude5Fc/oE2Y+jPsWyo8/shrHp0v+k/ nl3AjE2s+bs7h0Vlv2uKgTV8g+fZ2/6hGBz0tnuaxmidkBDtwFYVs4tgFUW7thg3Ix+s Mgo9XfhRZPafVwVdhyx5XAyNLbsDcYfmhSJ4IlOnu1IKeO2Z0E/31CiaOOOnXYWur3QF 64pNdQC0oMozhoD9h/zW8RY/HplB4QUOTDtM3gi7ySMNfht7OUFhpVvLBbftqZmMUOYq I3znDevzsT+55oX7VBj93tV8rG+uY0Ps/yU0LqqvzBQqmJmPQj3+L8Y5xRD2IiWdG8HI 47EQ== MIME-Version: 1.0 X-Received: by 10.180.97.233 with SMTP id ed9mr4647778wib.32.1363370104736; Fri, 15 Mar 2013 10:55:04 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.216.111.201 with HTTP; Fri, 15 Mar 2013 10:55:04 -0700 (PDT) In-Reply-To: <51435271.2040402@mu.org> References: <514324E8.30209@freebsd.org> <201303150946.29100.jhb@freebsd.org> <51433D30.30405@freebsd.org> <51435271.2040402@mu.org> Date: Fri, 15 Mar 2013 10:55:04 -0700 X-Google-Sender-Auth: 58XniyE5nNCqt5B5gZOe9hNT4yc Message-ID: Subject: Re: NewNFS vs. oldNFS for 10.0? From: Adrian Chadd To: Alfred Perlstein Content-Type: text/plain; charset=ISO-8859-1 Cc: rmacklem@uoguelph.ca, Andre Oppermann , freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Mar 2013 17:55:06 -0000 On 15 March 2013 09:55, Alfred Perlstein wrote: > Finally, I think it is really premature to declare a sunset for the oldnfs > until the users are gushing with approval over the new system. The flipside to this argument (and coming from you is kind of amusing :-) is that without any kind of sunset time stated, companies won't push back or be forced to migrate, so they may stick with oldnfs for years to come. It sounds like your employer has made that choice, at least for the short term. Nothing in your email stated that you had filed bugs (but I'm sure you have), nor that you were dedicating any resources to help Rick and others iron out the bugs in NFSv4. So I'm all for sunsetting oldnfs by 10.x, and lighting a fire up peoples' asses to realise that stuff _needs_ to get debugged before 10.0 is cut, or they're going to be in for an even rougher ride in the future. adrian From owner-freebsd-current@FreeBSD.ORG Fri Mar 15 18:11:23 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 64356472; Fri, 15 Mar 2013 18:11:23 +0000 (UTC) (envelope-from bright@mu.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id 42253388; Fri, 15 Mar 2013 18:11:23 +0000 (UTC) Received: from kruse-124.4.ixsystems.com (drawbridge.ixsystems.com [206.40.55.65]) by elvis.mu.org (Postfix) with ESMTPSA id C8D671A3E16; Fri, 15 Mar 2013 11:11:21 -0700 (PDT) Message-ID: <5143643D.3040609@mu.org> Date: Fri, 15 Mar 2013 11:11:09 -0700 From: Alfred Perlstein User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130307 Thunderbird/17.0.4 MIME-Version: 1.0 To: Adrian Chadd Subject: Re: NewNFS vs. oldNFS for 10.0? References: <514324E8.30209@freebsd.org> <201303150946.29100.jhb@freebsd.org> <51433D30.30405@freebsd.org> <51435271.2040402@mu.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: rmacklem@uoguelph.ca, Andre Oppermann , freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Mar 2013 18:11:23 -0000 On 3/15/13 10:55 AM, Adrian Chadd wrote: > On 15 March 2013 09:55, Alfred Perlstein wrote: > >> Finally, I think it is really premature to declare a sunset for the oldnfs >> until the users are gushing with approval over the new system. > The flipside to this argument (and coming from you is kind of amusing > :-) is that without any kind of sunset time stated, companies won't > push back or be forced to migrate, so they may stick with oldnfs for > years to come. I have never in my entire career pushed for "breaking users in the interest of forward progress." > > It sounds like your employer has made that choice, at least for the > short term. Nothing in your email stated that you had filed bugs (but > I'm sure you have), nor that you were dedicating any resources to help > Rick and others iron out the bugs in NFSv4. People in my org have been working with NFS and reporting issues for the past year. I'm quite certain that Doug White has reported issues due to missing certain caching features of the old code. This is not indicative that newNFS is bad, just that it still needs some work. > > So I'm all for sunsetting oldnfs by 10.x, and lighting a fire up > peoples' asses to realise that stuff _needs_ to get debugged before > 10.0 is cut, or they're going to be in for an even rougher ride in the > future. > > Sure, and how much NFS do you actually use and support exactly? -Alfred From owner-freebsd-current@FreeBSD.ORG Fri Mar 15 18:47:00 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 064E8C12; Fri, 15 Mar 2013 18:47:00 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wi0-x22b.google.com (mail-wi0-x22b.google.com [IPv6:2a00:1450:400c:c05::22b]) by mx1.freebsd.org (Postfix) with ESMTP id 6D2237D3; Fri, 15 Mar 2013 18:46:59 +0000 (UTC) Received: by mail-wi0-f171.google.com with SMTP id hn17so838995wib.4 for ; Fri, 15 Mar 2013 11:46:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=c74WaPpWKg5efyGbJFgXdLmQwxt65oxmXK+LS7qKiFs=; b=S6SkrL05fdZELIOYPVf/RHxFU1rM59KhSU15NJBRi/NjBWZ/mKlwjYflw6HtktP20O pDA/nxstnevHQX5ACCA4iB2A3llmxJ48ISouGsdq09amfKD8rqpV9h8P/27U0Tml+W+9 XpUW+MstRYu4oisLrvuAR+cuzzPH6Jc974OCMUFvuLM/rpFZiQcRJx8QZO9iysGDW8pG oPhNw1+8ZdmIkRr87S18eyLc3iAHaBtP93Ympre7EeLdBTn2ClmMDKKqng15lBGDvQLH c4Ca0FNp1+qdjJxJxv83ZVd7IIRY1IkJ9KfqfxUWLf1Ch8/uKQTajqGXQkWW9KDwhxfz ZxXQ== MIME-Version: 1.0 X-Received: by 10.180.94.135 with SMTP id dc7mr4984392wib.11.1363373217887; Fri, 15 Mar 2013 11:46:57 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.216.111.201 with HTTP; Fri, 15 Mar 2013 11:46:57 -0700 (PDT) In-Reply-To: <5143643D.3040609@mu.org> References: <514324E8.30209@freebsd.org> <201303150946.29100.jhb@freebsd.org> <51433D30.30405@freebsd.org> <51435271.2040402@mu.org> <5143643D.3040609@mu.org> Date: Fri, 15 Mar 2013 11:46:57 -0700 X-Google-Sender-Auth: YK0e2KVYDZ9MG2Lj0_umwqi4NDU Message-ID: Subject: Re: NewNFS vs. oldNFS for 10.0? From: Adrian Chadd To: Alfred Perlstein Content-Type: text/plain; charset=ISO-8859-1 Cc: rmacklem@uoguelph.ca, Andre Oppermann , freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Mar 2013 18:47:00 -0000 On 15 March 2013 11:11, Alfred Perlstein wrote: > People in my org have been working with NFS and reporting issues for the > past year. I'm quite certain that Doug White has reported issues due to > missing certain caching features of the old code. > > This is not indicative that newNFS is bad, just that it still needs some > work. Good news. and yes, it needs more work, but it doesn't preclude it from having a cutover date set. Even if that date is something far in the future, like 11.0. Or we'll just end up with two NFS stacks for some undetermined amount of time. > Sure, and how much NFS do you actually use and support exactly? .. and exactly how much would that lend to this discussion? I'm not arguing NFS technical details, I'm arguing project forward thinking and planning. These don't need me to be waist deep in NFS, it needs a broader view of how things may and may not go. I lived through the pain of Linux having multiple NFS implementations for precisely this reason. It was a clusterfsck of a nightmare of epic proportions. We should avoid that. adrian From owner-freebsd-current@FreeBSD.ORG Fri Mar 15 18:56:44 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 0E98A1B9; Fri, 15 Mar 2013 18:56:44 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from mail-qe0-f50.google.com (mail-qe0-f50.google.com [209.85.128.50]) by mx1.freebsd.org (Postfix) with ESMTP id A4E0D872; Fri, 15 Mar 2013 18:56:43 +0000 (UTC) Received: by mail-qe0-f50.google.com with SMTP id k5so2154085qej.9 for ; Fri, 15 Mar 2013 11:56:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=tirRrKY4a8xbUfIvAalfMJAWQWauoOqoY2kMziychjU=; b=K1GNvecT3QsgA4m7d5cIDLLkbahoWWKF0CPYvXdtno/BUyfnV/Vv9lrf/WTXLGpDZC 230oiIdB0BW34gZgcnzhSYActxTj1cxOrfa4aM3dUlAHpvs29BeDHGvrvFc0pQ/OXZOT ipR3Aw9i7jO5dYESY0WGIatqH1Jh8dFt+8pe9BuZzjLnQXy6iKBhfnZ/r/iNoFFeZ27d ZxS753y135epY0po37yCXDSFkc0AkmLN5iX13n7fOO6N0vWHO5bpAeBCq0FlM0k0WpQT CFg5Ik143YJoE5Z8W2eDBeIz96KXApQ8ApyNeCq3uWTsTfoAGnM0R+ricaieIJkfEVmO tPfQ== MIME-Version: 1.0 X-Received: by 10.49.58.173 with SMTP id s13mr7913637qeq.29.1363373797007; Fri, 15 Mar 2013 11:56:37 -0700 (PDT) Received: by 10.49.50.67 with HTTP; Fri, 15 Mar 2013 11:56:36 -0700 (PDT) In-Reply-To: References: <514324E8.30209@freebsd.org> <201303150946.29100.jhb@freebsd.org> <51433D30.30405@freebsd.org> <51435271.2040402@mu.org> <5143643D.3040609@mu.org> Date: Fri, 15 Mar 2013 11:56:36 -0700 Message-ID: Subject: Re: NewNFS vs. oldNFS for 10.0? From: Freddie Cash To: Adrian Chadd Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: Alfred Perlstein , Andre Oppermann , Rick Macklem , FreeBSD-Current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Mar 2013 18:56:44 -0000 Isn't the general process (or at least past pattern) to: - have 1 release cycle with just the old code (aka 8.x with oldNFS) - have 1 release cycle with old and new code, default to old (aka 9.x with oldNFS + newNFS) - have 1 release cycle with old and new code, default to new (aka 10.x with newNFS) - remove the old code from next release (aka 11.0) Or is that too long of a time-frame to migrate from old to new? On Fri, Mar 15, 2013 at 11:46 AM, Adrian Chadd wrote: > On 15 March 2013 11:11, Alfred Perlstein wrote: > > > People in my org have been working with NFS and reporting issues for the > > past year. I'm quite certain that Doug White has reported issues due to > > missing certain caching features of the old code. > > > > This is not indicative that newNFS is bad, just that it still needs some > > work. > > Good news. and yes, it needs more work, but it doesn't preclude it > from having a cutover date set. Even if that date is something far in > the future, like 11.0. > > Or we'll just end up with two NFS stacks for some undetermined amount of > time. > > > Sure, and how much NFS do you actually use and support exactly? > > .. and exactly how much would that lend to this discussion? > > I'm not arguing NFS technical details, I'm arguing project forward > thinking and planning. These don't need me to be waist deep in NFS, it > needs a broader view of how things may and may not go. > > I lived through the pain of Linux having multiple NFS implementations > for precisely this reason. It was a clusterfsck of a nightmare of epic > proportions. We should avoid that. > > > > adrian > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > -- Freddie Cash fjwcash@gmail.com From owner-freebsd-current@FreeBSD.ORG Fri Mar 15 21:03:18 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 25EB9163; Fri, 15 Mar 2013 21:03:18 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from bigwig.baldwin.cx (bigknife-pt.tunnel.tserv9.chi1.ipv6.he.net [IPv6:2001:470:1f10:75::2]) by mx1.freebsd.org (Postfix) with ESMTP id 04C1E333; Fri, 15 Mar 2013 21:03:18 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 26D62B943; Fri, 15 Mar 2013 17:03:17 -0400 (EDT) From: John Baldwin To: Andre Oppermann Subject: Re: NewNFS vs. oldNFS for 10.0? Date: Fri, 15 Mar 2013 17:03:09 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110714-p25; KDE/4.5.5; amd64; ; ) References: <514324E8.30209@freebsd.org> <201303150946.29100.jhb@freebsd.org> <51433D30.30405@freebsd.org> In-Reply-To: <51433D30.30405@freebsd.org> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201303151703.09688.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Fri, 15 Mar 2013 17:03:17 -0400 (EDT) Cc: freebsd-current@freebsd.org, rmacklem@uoguelph.ca X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Mar 2013 21:03:18 -0000 On Friday, March 15, 2013 11:24:32 am Andre Oppermann wrote: > On 15.03.2013 14:46, John Baldwin wrote: > > On Friday, March 15, 2013 9:40:56 am Andre Oppermann wrote: > >> Hi Rick, all, > >> > >> is there a plan to decide for one NFS implementation for FreeBSD 10.0, > >> or to keep both around indefinately? > >> > >> I'm talking about: > >> oldNFS in sys/{nfs, nfsclient, nfsserver} NFSv2+NFSv3 > >> newNFS in sys/fs/{nfs, nfsclient, nfsserver} NFSv2+NFSv3+NFSv4 > >> > >> NewNFS supports newer NFS standards and seems to have proven itself in > >> some quite heavy traffic environments. > >> > >> Is there any reason to keep oldNFS around other than nostalgic? > > > > It can probably be removed. It's kind of handy to keep around as long as 8.x > > is around since it uses oldNFS by default as it makes merging bugfixes to the > > NFS client a bit easier (you fix both clients in HEAD and can then just svn > > merge both of those to 8 and 9). Having several fixes to the NFS client > > recently and being in a position of still using 8.x with oldNFS in production, > > I would prefer to not remove it quite yet. > > Do you have a timeframe on the sunset of oldNFS in HEAD so we can communicate > a) that oldNFS won't be in 10.0; and b) it will go on date X? I thought I implied one above: when 8.x is EOL'd. However, that has more to do with developer convience. It's actually a PITA to use the old NFS client even on 9.0. > Would it make sense to make oldNFS more difficult to compile into the kernel > on HEAD to notify all those with legacy kernel config files? No. The old client doesn't work out of the box unless you change your fstab to s/nfs/oldnfs/. Also, tools like nfsstat don't work with the old nfs client either. Do you have an actual reason for wanting this change? As someone who is actively working on NFS (and applying and testing fixes on both old and new) I'd like to keep the old one for now. Does that break something for you? -- John Baldwin From owner-freebsd-current@FreeBSD.ORG Sat Mar 16 00:38:01 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 4DAD7165; Sat, 16 Mar 2013 00:38:01 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-jnhn.mail.uoguelph.ca (esa-jnhn.mail.uoguelph.ca [131.104.91.44]) by mx1.freebsd.org (Postfix) with ESMTP id E7A267F4; Sat, 16 Mar 2013 00:38:00 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AqEEACq+Q1GDaFvO/2dsb2JhbABDiDG8eoF9dIIqAQEBAwEBAQEgKyALBRYOCgICDRkCKQEJJgYIBwQBHASHbQYMsH2SXYEjgSqLCBB8NAeCLYETA5Qdgj6BH49jgyYgMoEFNQ X-IronPort-AV: E=Sophos;i="4.84,854,1355115600"; d="scan'208";a="21480082" Received: from erie.cs.uoguelph.ca (HELO zcs3.mail.uoguelph.ca) ([131.104.91.206]) by esa-jnhn.mail.uoguelph.ca with ESMTP; 15 Mar 2013 20:37:53 -0400 Received: from zcs3.mail.uoguelph.ca (localhost.localdomain [127.0.0.1]) by zcs3.mail.uoguelph.ca (Postfix) with ESMTP id 78C8FB402B; Fri, 15 Mar 2013 20:37:53 -0400 (EDT) Date: Fri, 15 Mar 2013 20:37:53 -0400 (EDT) From: Rick Macklem To: Alfred Perlstein Message-ID: <793530868.3962258.1363394273384.JavaMail.root@erie.cs.uoguelph.ca> In-Reply-To: <5143643D.3040609@mu.org> Subject: Re: NewNFS vs. oldNFS for 10.0? MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [172.17.91.203] X-Mailer: Zimbra 6.0.10_GA_2692 (ZimbraWebClient - FF3.0 (Win)/6.0.10_GA_2692) Cc: Adrian Chadd , freebsd-current@freebsd.org, Andre Oppermann X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 16 Mar 2013 00:38:01 -0000 Alfred Perlstein wrote: > On 3/15/13 10:55 AM, Adrian Chadd wrote: > > On 15 March 2013 09:55, Alfred Perlstein wrote: > > > >> Finally, I think it is really premature to declare a sunset for the > >> oldnfs > >> until the users are gushing with approval over the new system. > > The flipside to this argument (and coming from you is kind of > > amusing > > :-) is that without any kind of sunset time stated, companies won't > > push back or be forced to migrate, so they may stick with oldnfs for > > years to come. > > I have never in my entire career pushed for "breaking users in the > interest of forward progress." > > > > > > It sounds like your employer has made that choice, at least for the > > short term. Nothing in your email stated that you had filed bugs > > (but > > I'm sure you have), nor that you were dedicating any resources to > > help > > Rick and others iron out the bugs in NFSv4. > > People in my org have been working with NFS and reporting issues for > the > past year. I'm quite certain that Doug White has reported issues due > to > missing certain caching features of the old code. > You should get him to post w.r.t. his issues again. I must have missed or forgotten what they were. As far as I know, the client caching code is just a clone of what the oldNFS client does, although it's possible that some differences are there. If he/you are referring to the DRC in the server, then, yes, I am aware that work related to overheads/delays for TCP caching exists. rick > This is not indicative that newNFS is bad, just that it still needs > some > work. > > > > > So I'm all for sunsetting oldnfs by 10.x, and lighting a fire up > > peoples' asses to realise that stuff _needs_ to get debugged before > > 10.0 is cut, or they're going to be in for an even rougher ride in > > the > > future. > > > > > Sure, and how much NFS do you actually use and support exactly? > > -Alfred > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to > "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@FreeBSD.ORG Sat Mar 16 00:43:09 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 50D3032F; Sat, 16 Mar 2013 00:43:09 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-annu.net.uoguelph.ca (esa-annu.mail.uoguelph.ca [131.104.91.36]) by mx1.freebsd.org (Postfix) with ESMTP id DBF6881F; Sat, 16 Mar 2013 00:43:08 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AqAEAKW9Q1GDaFvO/2dsb2JhbABDiDG6FYJlgX10gioBAQQBI1YFFg4KAgINGQJZBoghBrEJkl2BI4EqjBQ0B4ItgRMDlluRAoMmIIFs X-IronPort-AV: E=Sophos;i="4.84,854,1355115600"; d="scan'208";a="19264370" Received: from erie.cs.uoguelph.ca (HELO zcs3.mail.uoguelph.ca) ([131.104.91.206]) by esa-annu.net.uoguelph.ca with ESMTP; 15 Mar 2013 20:43:07 -0400 Received: from zcs3.mail.uoguelph.ca (localhost.localdomain [127.0.0.1]) by zcs3.mail.uoguelph.ca (Postfix) with ESMTP id 603ADB3EE1; Fri, 15 Mar 2013 20:43:07 -0400 (EDT) Date: Fri, 15 Mar 2013 20:43:07 -0400 (EDT) From: Rick Macklem To: John Baldwin Message-ID: <1627787090.3962321.1363394587341.JavaMail.root@erie.cs.uoguelph.ca> In-Reply-To: <201303151703.09688.jhb@freebsd.org> Subject: Re: NewNFS vs. oldNFS for 10.0? MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [172.17.91.203] X-Mailer: Zimbra 6.0.10_GA_2692 (ZimbraWebClient - FF3.0 (Win)/6.0.10_GA_2692) Cc: freebsd-current@freebsd.org, Andre Oppermann X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 16 Mar 2013 00:43:09 -0000 John Baldwin wrote: > On Friday, March 15, 2013 11:24:32 am Andre Oppermann wrote: > > On 15.03.2013 14:46, John Baldwin wrote: > > > On Friday, March 15, 2013 9:40:56 am Andre Oppermann wrote: > > >> Hi Rick, all, > > >> > > >> is there a plan to decide for one NFS implementation for FreeBSD > > >> 10.0, > > >> or to keep both around indefinately? > > >> > > >> I'm talking about: > > >> oldNFS in sys/{nfs, nfsclient, nfsserver} NFSv2+NFSv3 > > >> newNFS in sys/fs/{nfs, nfsclient, nfsserver} NFSv2+NFSv3+NFSv4 > > >> > > >> NewNFS supports newer NFS standards and seems to have proven > > >> itself in > > >> some quite heavy traffic environments. > > >> > > >> Is there any reason to keep oldNFS around other than nostalgic? > > > > > > It can probably be removed. It's kind of handy to keep around as > > > long as 8.x > > > is around since it uses oldNFS by default as it makes merging > > > bugfixes to the > > > NFS client a bit easier (you fix both clients in HEAD and can then > > > just svn > > > merge both of those to 8 and 9). Having several fixes to the NFS > > > client > > > recently and being in a position of still using 8.x with oldNFS in > > > production, > > > I would prefer to not remove it quite yet. > > > > Do you have a timeframe on the sunset of oldNFS in HEAD so we can > > communicate > > a) that oldNFS won't be in 10.0; and b) it will go on date X? > > I thought I implied one above: when 8.x is EOL'd. However, that has > more to do > with developer convience. It's actually a PITA to use the old NFS > client even > on 9.0. > > > Would it make sense to make oldNFS more difficult to compile into > > the kernel > > on HEAD to notify all those with legacy kernel config files? > > No. The old client doesn't work out of the box unless you change your > fstab > to s/nfs/oldnfs/. Also, tools like nfsstat don't work with the old nfs > client > either. > Just fyi, "nfsstat -o" should still report stats for the old NFS. (I suspect John meant that it does not by default.) > Do you have an actual reason for wanting this change? As someone who > is actively > working on NFS (and applying and testing fixes on both old and new) > I'd like to > keep the old one for now. Does that break something for you? > > -- > John Baldwin From owner-freebsd-current@FreeBSD.ORG Sat Mar 16 00:44:47 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 0FF8F452 for ; Sat, 16 Mar 2013 00:44:47 +0000 (UTC) (envelope-from peter@wemm.org) Received: from mail-vc0-f179.google.com (mail-vc0-f179.google.com [209.85.220.179]) by mx1.freebsd.org (Postfix) with ESMTP id AD2BD83D for ; Sat, 16 Mar 2013 00:44:46 +0000 (UTC) Received: by mail-vc0-f179.google.com with SMTP id gf12so1652854vcb.24 for ; Fri, 15 Mar 2013 17:44:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=wemm.org; s=google; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=xSS/FkVrLlVNBPuO7uqXJBAWxIRM0DJIMqMEP5uR7R4=; b=Xr7CvhvA0VWDnolEIoV2O7bJ3m8akxngSGHQ/7d6M9sFJKUhAP2Y1AKlMinWwtvn4K 4cnI2wXBpnPXCWFx51tZGtJ1UyJeyE8jUvYR3DWE+FoevirifJuc4+aYI8jx2z+83xLf 0/ao0c0eiFcHGQX0ASa+GJC3+8+orgJRuK6b4= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type:x-gm-message-state; bh=xSS/FkVrLlVNBPuO7uqXJBAWxIRM0DJIMqMEP5uR7R4=; b=KDvQin4pqPyMrigtjDb6o2JB/WcIRaKUhnd2Z/yFHQbYt5CAxhZB0tiQKFWQWEJDP2 uT6x+1XaOEuFyZ+qTN/hU6qCVwvELvX5M6smJqJ50ebWkhaLPXWgYxWMURYgxll8JE8+ ue7iL0If1gi9T43bVUCAV96HlxsYp4LbqRCWIOk1Lmk0bYehaksJZhJ3g8o+noaDgZ7S w0uDrJBKjTq12c70OfTTrbD1Bxq9WKQ97FEZeMT7oJ7DZstc8Gr8IqW3cOxCyUKcdXJx n0B/G7+2+QJnluRYuHvDh5E2nu99CJPYBwOZfixKgnfKMDCGQcJwYARxOKGtO63pWQjy uyig== MIME-Version: 1.0 X-Received: by 10.52.24.205 with SMTP id w13mr8230912vdf.61.1363394680681; Fri, 15 Mar 2013 17:44:40 -0700 (PDT) Received: by 10.221.11.72 with HTTP; Fri, 15 Mar 2013 17:44:40 -0700 (PDT) In-Reply-To: <201303151703.09688.jhb@freebsd.org> References: <514324E8.30209@freebsd.org> <201303150946.29100.jhb@freebsd.org> <51433D30.30405@freebsd.org> <201303151703.09688.jhb@freebsd.org> Date: Fri, 15 Mar 2013 17:44:40 -0700 Message-ID: Subject: Re: NewNFS vs. oldNFS for 10.0? From: Peter Wemm To: John Baldwin Content-Type: text/plain; charset=ISO-8859-1 X-Gm-Message-State: ALoCoQmAzEC20ibr6OKZlpPN8ExH5XnDR+aCurOgWOtRW1fht1E8Id+rdSWydejZ6G2D+GTfV0Av Cc: freebsd-current@freebsd.org, Andre Oppermann , rmacklem@uoguelph.ca X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 16 Mar 2013 00:44:47 -0000 On Fri, Mar 15, 2013 at 2:03 PM, John Baldwin wrote: > On Friday, March 15, 2013 11:24:32 am Andre Oppermann wrote: >> On 15.03.2013 14:46, John Baldwin wrote: >> > On Friday, March 15, 2013 9:40:56 am Andre Oppermann wrote: >> >> Hi Rick, all, >> >> >> >> is there a plan to decide for one NFS implementation for FreeBSD 10.0, >> >> or to keep both around indefinately? >> >> >> >> I'm talking about: >> >> oldNFS in sys/{nfs, nfsclient, nfsserver} NFSv2+NFSv3 >> >> newNFS in sys/fs/{nfs, nfsclient, nfsserver} NFSv2+NFSv3+NFSv4 >> >> >> >> NewNFS supports newer NFS standards and seems to have proven itself in >> >> some quite heavy traffic environments. >> >> >> >> Is there any reason to keep oldNFS around other than nostalgic? >> > >> > It can probably be removed. It's kind of handy to keep around as long as 8.x >> > is around since it uses oldNFS by default as it makes merging bugfixes to the >> > NFS client a bit easier (you fix both clients in HEAD and can then just svn >> > merge both of those to 8 and 9). Having several fixes to the NFS client >> > recently and being in a position of still using 8.x with oldNFS in production, >> > I would prefer to not remove it quite yet. >> >> Do you have a timeframe on the sunset of oldNFS in HEAD so we can communicate >> a) that oldNFS won't be in 10.0; and b) it will go on date X? > > I thought I implied one above: when 8.x is EOL'd. However, that has more to do > with developer convience. It's actually a PITA to use the old NFS client even > on 9.0. Yes to both. As somebody who uses oldNFS in production in 9.x, I can vouch for that. Personally I'd like to see oldnfs go away from head after a comfortable dust-settling period 8.4-R and then call it a day. Although, please, as part of this please hunt down and s/newnfs/nfs/g in the process. This should be done well before 10.x so loose ends can be tracked down and fixed. -- Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com; KI6FJV bitcoin:188ZjyYLFJiEheQZw4UtU27e2FMLmuRBUE From owner-freebsd-current@FreeBSD.ORG Sat Mar 16 00:52:02 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 1FC2D628; Sat, 16 Mar 2013 00:52:02 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-annu.net.uoguelph.ca (esa-annu.mail.uoguelph.ca [131.104.91.36]) by mx1.freebsd.org (Postfix) with ESMTP id B1882878; Sat, 16 Mar 2013 00:52:01 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AqEEAMfBQ1GDaFvO/2dsb2JhbABDiDG8eoF9dIIqAQEBBAEBASArIAsbDgoCAg0ZAiMGAQkmBggHBAEZAwSHYQMPDLB3iHMNiVuBI4EqiX+BGXw0B4ItgRMDlB1egWCBH4pJhRqDJiAygQU1 X-IronPort-AV: E=Sophos;i="4.84,854,1355115600"; d="scan'208";a="19264799" Received: from erie.cs.uoguelph.ca (HELO zcs3.mail.uoguelph.ca) ([131.104.91.206]) by esa-annu.net.uoguelph.ca with ESMTP; 15 Mar 2013 20:52:00 -0400 Received: from zcs3.mail.uoguelph.ca (localhost.localdomain [127.0.0.1]) by zcs3.mail.uoguelph.ca (Postfix) with ESMTP id 80B07B3F91; Fri, 15 Mar 2013 20:52:00 -0400 (EDT) Date: Fri, 15 Mar 2013 20:52:00 -0400 (EDT) From: Rick Macklem To: Freddie Cash Message-ID: <636921049.3962434.1363395120474.JavaMail.root@erie.cs.uoguelph.ca> In-Reply-To: Subject: Re: NewNFS vs. oldNFS for 10.0? MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [172.17.91.203] X-Mailer: Zimbra 6.0.10_GA_2692 (ZimbraWebClient - FF3.0 (Win)/6.0.10_GA_2692) Cc: Adrian Chadd , Alfred Perlstein , Andre Oppermann , FreeBSD-Current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 16 Mar 2013 00:52:02 -0000 Freddie Cash wrote: > Isn't the general process (or at least past pattern) to: > - have 1 release cycle with just the old code (aka 8.x with oldNFS) > - have 1 release cycle with old and new code, default to old (aka 9.x > with oldNFS + newNFS) Actually, your numbering is out by one. 7.x - old only 8.x - old and new, with old default 9.x - old and new, with new default I, personally, don't care if 10.x has both in it or not. The only downside I see is that it often means generating patches for both, but this usually occurs when the code in the old and new are virtually identical (new cloned from old). rick > - have 1 release cycle with old and new code, default to new (aka 10.x > with newNFS) > > - remove the old code from next release (aka 11.0) > > > > Or is that too long of a time-frame to migrate from old to new? > > > > > > On Fri, Mar 15, 2013 at 11:46 AM, Adrian Chadd < adrian@freebsd.org > > wrote: > > > On 15 March 2013 11:11, Alfred Perlstein < bright@mu.org > wrote: > > > People in my org have been working with NFS and reporting issues for > > the > > past year. I'm quite certain that Doug White has reported issues due > > to > > missing certain caching features of the old code. > > > > This is not indicative that newNFS is bad, just that it still needs > > some > > work. > > Good news. and yes, it needs more work, but it doesn't preclude it > from having a cutover date set. Even if that date is something far in > the future, like 11.0. > > Or we'll just end up with two NFS stacks for some undetermined amount > of time. > > > Sure, and how much NFS do you actually use and support exactly? > > .. and exactly how much would that lend to this discussion? > > I'm not arguing NFS technical details, I'm arguing project forward > thinking and planning. These don't need me to be waist deep in NFS, it > needs a broader view of how things may and may not go. > > I lived through the pain of Linux having multiple NFS implementations > for precisely this reason. It was a clusterfsck of a nightmare of epic > proportions. We should avoid that. > > > > adrian > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to " > freebsd-current-unsubscribe@freebsd.org " > > > > -- > Freddie Cash > fjwcash@gmail.com From owner-freebsd-current@FreeBSD.ORG Fri Mar 15 23:50:07 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id B6E8FA19 for ; Fri, 15 Mar 2013 23:50:07 +0000 (UTC) (envelope-from gvdl@juniper.net) Received: from exprod7og124.obsmtp.com (exprod7og124.obsmtp.com [64.18.2.26]) by mx1.freebsd.org (Postfix) with ESMTP id 5F2596BE for ; Fri, 15 Mar 2013 23:50:07 +0000 (UTC) Received: from P-EMHUB02-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob124.postini.com ([64.18.6.12]) with SMTP ID DSNKUUOzqfrjKSAg6D7OfSv7Du7khjCUAeU1@postini.com; Fri, 15 Mar 2013 16:50:07 PDT Received: from P-CLDFE02-HQ.jnpr.net (172.24.192.60) by P-EMHUB02-HQ.jnpr.net (172.24.192.36) with Microsoft SMTP Server (TLS) id 8.3.213.0; Fri, 15 Mar 2013 16:46:23 -0700 Received: from o365mail.juniper.net (207.17.137.149) by o365mail.juniper.net (172.24.192.60) with Microsoft SMTP Server id 14.1.355.2; Fri, 15 Mar 2013 16:46:22 -0700 Received: from am1outboundpool.messaging.microsoft.com (213.199.154.204) by o365mail.juniper.net (207.17.137.149) with Microsoft SMTP Server (TLS) id 14.1.355.2; Fri, 15 Mar 2013 16:48:52 -0700 Received: from mail20-am1-R.bigfish.com (10.3.201.225) by AM1EHSOBE023.bigfish.com (10.3.207.145) with Microsoft SMTP Server id 14.1.225.23; Fri, 15 Mar 2013 23:46:20 +0000 Received: from mail20-am1 (localhost [127.0.0.1]) by mail20-am1-R.bigfish.com (Postfix) with ESMTP id BCE11A0187 for ; Fri, 15 Mar 2013 23:46:20 +0000 (UTC) X-Forefront-Antispam-Report: CIP:157.56.242.197; KIP:(null); UIP:(null); (null); H:BL2PRD0512HT001.namprd05.prod.outlook.com; R:internal; EFV:INT X-SpamScore: 0 X-BigFish: PS0(zzc85fhzz1f42h1ee6h1de0h1202h1e76h1d1ah1d2ahzz17326ah8275dhz2dh2a8h668h839hd25he5bhf0ah1288h12a5h12bdh137ah139eh1441h14ddh1504h1537h162dh1631h1662h1758h1898h18e1h1946h19b5h19ceh1ad9h1b0ah1b2bh1155h) Received: from mail20-am1 (localhost.localdomain [127.0.0.1]) by mail20-am1 (MessageSwitch) id 1363391178647619_22626; Fri, 15 Mar 2013 23:46:18 +0000 (UTC) Received: from AM1EHSMHS005.bigfish.com (unknown [10.3.201.250]) by mail20-am1.bigfish.com (Postfix) with ESMTP id 92443300071 for ; Fri, 15 Mar 2013 23:46:18 +0000 (UTC) Received: from BL2PRD0512HT001.namprd05.prod.outlook.com (157.56.242.197) by AM1EHSMHS005.bigfish.com (10.3.207.105) with Microsoft SMTP Server (TLS) id 14.1.225.23; Fri, 15 Mar 2013 23:46:17 +0000 Received: from gvdl-mbp15.jnpr.net (66.129.224.52) by pod51010.outlook.com (10.255.233.34) with Microsoft SMTP Server (TLS) id 14.16.275.6; Fri, 15 Mar 2013 23:46:16 +0000 From: Godfrey Van der Linden Subject: kmod linking is very strange Message-ID: Date: Fri, 15 Mar 2013 16:46:13 -0700 To: MIME-Version: 1.0 (Mac OS X Mail 6.1 \(1498\)) X-Mailer: Apple Mail (2.1498) X-Originating-IP: [66.129.224.52] X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn% X-FOPE-CONNECTOR: Id%12219$Dn%FREEBSD.ORG$RO%2$TLS%5$FQDN%onpremiseedge-1018244.customer.frontbridge.com$TlsDn%o365mail.juniper.net X-Mailman-Approved-At: Sat, 16 Mar 2013 01:18:51 +0000 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Mar 2013 23:50:07 -0000 G'day, All. First post so please be gentle ;-). Are the barracudas here? Summary: Module link-elf will link against static symbols and will fail if the = kernel is not compiled with DDB or the required MODULE_DEPEND has been = stripped of local symbols, see nm -g miibus.ko. I propose that we add a = sysctl & associated boot arg that only allows kmod loading against = externally visible symbols. Then in 11 we can enable this flag by = default. In Detail: Due to another bug in sys/conf/kmod.mk, = (http://www.freebsd.org/cgi/query-pr.cgi?pr=3D177008, contains a patch) = the miibus.ko exports no symbols. I.e. symbols are 'static'.=20 sys/kern/link-elf.c:link_elf_lookup_symbol() is the culprit. After = determining that an external symbol can't be found, it does the = following. /* If we have not found it, look at the full table (if loaded) = */ if (ef->symtab =3D=3D ef->ddbsymtab) return (ENOENT); /* Exhaustive search */ for (i =3D 0, symp =3D ef->ddbsymtab; i < ef->ddbsymcnt; i++, = symp++) { strp =3D ef->ddbstrtab + symp->st_name; if (strcmp(name, strp) =3D=3D 0) { if (symp->st_shndx !=3D SHN_UNDEF || (symp->st_value !=3D 0 && ELF_ST_TYPE(symp->st_info) =3D=3D = STT_FUNC)) { *sym =3D (c_linker_sym_t) symp; return (0); } return (ENOENT); } } This code walks the ddbsymtab looking for any symbol, including locals. Any kernel that is not built with DDB or any MODULE_DEPEND dependency = .ko that is stripped will break module loading. Godfrey van der Linden= From owner-freebsd-current@FreeBSD.ORG Sat Mar 16 02:08:58 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 191BC2B8; Sat, 16 Mar 2013 02:08:58 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-jnhn.mail.uoguelph.ca (esa-jnhn.mail.uoguelph.ca [131.104.91.44]) by mx1.freebsd.org (Postfix) with ESMTP id A423CA81; Sat, 16 Mar 2013 02:08:57 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AqAEALPTQ1GDaFvO/2dsb2JhbABDiDG8eoF9dIIqAQEEASNWBRYYAgINGQJZBhOIDgaweJJagSOBKowUNAeCLYETA5ZbkQKDJiCBbA X-IronPort-AV: E=Sophos;i="4.84,855,1355115600"; d="scan'208";a="21484686" Received: from erie.cs.uoguelph.ca (HELO zcs3.mail.uoguelph.ca) ([131.104.91.206]) by esa-jnhn.mail.uoguelph.ca with ESMTP; 15 Mar 2013 22:08:56 -0400 Received: from zcs3.mail.uoguelph.ca (localhost.localdomain [127.0.0.1]) by zcs3.mail.uoguelph.ca (Postfix) with ESMTP id B3CBDB3F13; Fri, 15 Mar 2013 22:08:56 -0400 (EDT) Date: Fri, 15 Mar 2013 22:08:56 -0400 (EDT) From: Rick Macklem To: Peter Wemm Message-ID: <1716481334.3963421.1363399736691.JavaMail.root@erie.cs.uoguelph.ca> In-Reply-To: Subject: Re: NewNFS vs. oldNFS for 10.0? MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [172.17.91.202] X-Mailer: Zimbra 6.0.10_GA_2692 (ZimbraWebClient - FF3.0 (Win)/6.0.10_GA_2692) Cc: freebsd-current@freebsd.org, Andre Oppermann X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 16 Mar 2013 02:08:58 -0000 Peter Wemm wrote: > On Fri, Mar 15, 2013 at 2:03 PM, John Baldwin wrote: > > On Friday, March 15, 2013 11:24:32 am Andre Oppermann wrote: > >> On 15.03.2013 14:46, John Baldwin wrote: > >> > On Friday, March 15, 2013 9:40:56 am Andre Oppermann wrote: > >> >> Hi Rick, all, > >> >> > >> >> is there a plan to decide for one NFS implementation for FreeBSD > >> >> 10.0, > >> >> or to keep both around indefinately? > >> >> > >> >> I'm talking about: > >> >> oldNFS in sys/{nfs, nfsclient, nfsserver} NFSv2+NFSv3 > >> >> newNFS in sys/fs/{nfs, nfsclient, nfsserver} > >> >> NFSv2+NFSv3+NFSv4 > >> >> > >> >> NewNFS supports newer NFS standards and seems to have proven > >> >> itself in > >> >> some quite heavy traffic environments. > >> >> > >> >> Is there any reason to keep oldNFS around other than nostalgic? > >> > > >> > It can probably be removed. It's kind of handy to keep around as > >> > long as 8.x > >> > is around since it uses oldNFS by default as it makes merging > >> > bugfixes to the > >> > NFS client a bit easier (you fix both clients in HEAD and can > >> > then just svn > >> > merge both of those to 8 and 9). Having several fixes to the NFS > >> > client > >> > recently and being in a position of still using 8.x with oldNFS > >> > in production, > >> > I would prefer to not remove it quite yet. > >> > >> Do you have a timeframe on the sunset of oldNFS in HEAD so we can > >> communicate > >> a) that oldNFS won't be in 10.0; and b) it will go on date X? > > > > I thought I implied one above: when 8.x is EOL'd. However, that has > > more to do > > with developer convience. It's actually a PITA to use the old NFS > > client even > > on 9.0. > > Yes to both. As somebody who uses oldNFS in production in 9.x, I can > vouch for that. > I was just wondering if there are technical issues you've run into w.r.t. the new one that has you running the old one? Oh, and are you referring to client or server side or both? Thanks, rick > Personally I'd like to see oldnfs go away from head after a > comfortable dust-settling period 8.4-R and then call it a day. > > Although, please, as part of this please hunt down and s/newnfs/nfs/g > in the process. This should be done well before 10.x so loose ends > can be tracked down and fixed. > > -- > Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com; > KI6FJV > bitcoin:188ZjyYLFJiEheQZw4UtU27e2FMLmuRBUE From owner-freebsd-current@FreeBSD.ORG Sat Mar 16 02:13:41 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id A95413DC; Sat, 16 Mar 2013 02:13:41 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-annu.net.uoguelph.ca (esa-annu.mail.uoguelph.ca [131.104.91.36]) by mx1.freebsd.org (Postfix) with ESMTP id 3EF23A9F; Sat, 16 Mar 2013 02:13:40 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AqEEAL3UQ1GDaFvO/2dsb2JhbABDiDG8eoF9dIIqAQEBBAEBASArIAsbGAICDRkCKQEJJgYPBAEcBIdzDLBtklqBI4Eqixh8NAeCLYETA5Qdgj6BH49jgyYgMoEFNQ X-IronPort-AV: E=Sophos;i="4.84,855,1355115600"; d="scan'208";a="19269333" Received: from erie.cs.uoguelph.ca (HELO zcs3.mail.uoguelph.ca) ([131.104.91.206]) by esa-annu.net.uoguelph.ca with ESMTP; 15 Mar 2013 22:13:39 -0400 Received: from zcs3.mail.uoguelph.ca (localhost.localdomain [127.0.0.1]) by zcs3.mail.uoguelph.ca (Postfix) with ESMTP id ED783B3F23; Fri, 15 Mar 2013 22:13:39 -0400 (EDT) Date: Fri, 15 Mar 2013 22:13:39 -0400 (EDT) From: Rick Macklem To: Andre Oppermann Message-ID: <1138560306.3963522.1363400019941.JavaMail.root@erie.cs.uoguelph.ca> In-Reply-To: <51432F0D.2040002@freebsd.org> Subject: Re: NewNFS vs. oldNFS for 10.0? MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [172.17.91.201] X-Mailer: Zimbra 6.0.10_GA_2692 (ZimbraWebClient - FF3.0 (Win)/6.0.10_GA_2692) Cc: freebsd-current , Lars Eggert X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 16 Mar 2013 02:13:41 -0000 Andre Oppermann wrote: > On 15.03.2013 15:01, Eggert, Lars wrote: > > Hi, > > > > this reminds me that I ran into an issue lately with the new NFS and > > locking for NFSv3 mounts on a client that ran -CURRENT and a server > > that ran > > -STABLE. > > > > When I ran "portmaster -a" on the client, which mounted /usr/ports > > and /usr/local, as well as the location of the respective sqlite > > databases over > > NFSv3, the client network stack became unresponsive on all > > interfaces for 30 or so seconds and e.g. SSH connections broke. The > > serial console > > remained active throughout, and the system didn't crash. About a > > minute after the wedgie I could SSH into the box again, too. > > The total wedge of all interfaces certainly shouldn't happen. This > smells like blocking on a lock on a socket_upcall() thereby wedging > tcp_input. I don't know the lockd code so maybe Rick knows how this > could happen. > I'm afraid I can't help much. The lockd and all the NFS stuff (old and new) share the kernel rpc (sys/rpc) code and that is where the upcalls are. At a quick look at them, they do have to acquire a mutex, but it would be hard to believe that would take 30sec? Also, I think (I'm not familiar with the NLM, so I'm not sure) that the NLM normally uses UDP and not TCP. It is a separate protocol with different port#s etc than NFS. rick > -- > Andre > > > The issue went away when I killed lockd on the client, but that > > caused the sqlite database to become corrupted over time. The > > workaround for me > > was to move to NFSv4, which has been working fine. (One more reason > > to make it the default...) > > > > I'm not really sure how to debug this further, but would be willing > > to work with someone off-list who'd tell me what tests to run. > > > > Lars _______________________________________________ > > freebsd-current@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-current To > > unsubscribe, send any mail to > > "freebsd-current-unsubscribe@freebsd.org" > > > > From owner-freebsd-current@FreeBSD.ORG Sat Mar 16 14:51:03 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 4D72D323 for ; Sat, 16 Mar 2013 14:51:03 +0000 (UTC) (envelope-from lokedhs@gmail.com) Received: from mail-lb0-f175.google.com (mail-lb0-f175.google.com [209.85.217.175]) by mx1.freebsd.org (Postfix) with ESMTP id CE99911E for ; Sat, 16 Mar 2013 14:51:02 +0000 (UTC) Received: by mail-lb0-f175.google.com with SMTP id n3so3476096lbo.6 for ; Sat, 16 Mar 2013 07:50:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=EZT1qQH2K3LVzjDkC+fnAP4OfKtyRXFWY+T29NtaJ+o=; b=gEv39G2iFnZnTdFf6NlOYTRXTOgNh4aXQRPNN/cvY5CbZVsm3CbqMA5hIdM+lXIsqq hd12/K510FI+k0VzrY5kU7RrtTV09Ah9TzlD3YNCVQqAPoNYGQnDgqDtyEC7aM3suynE lBOlpY11dwGRDojEn4jE4jeh7pGJYnizEYgoNa+G4yUhqwMsc6xQdY5AzpwsxTjX7aT6 G5HoZCIw/lZHbisjkVTet+cwz5nYhDTA97BUJx/VTLPoLC4EG0foGKDXWJ0kkPRr2nDU CKQMmOy2SqA7y11dhQcFqi+0V785hVL9fbDud+euH2j4K9A0wMpexAVFEoDHgfpe17yC oFTA== MIME-Version: 1.0 X-Received: by 10.112.10.138 with SMTP id i10mr4111713lbb.24.1363445456302; Sat, 16 Mar 2013 07:50:56 -0700 (PDT) Received: by 10.112.21.167 with HTTP; Sat, 16 Mar 2013 07:50:56 -0700 (PDT) Date: Sat, 16 Mar 2013 22:50:56 +0800 Message-ID: Subject: Strange error when compiling minimal GSSAPI application From: =?ISO-8859-1?Q?Elias_M=E5rtenson?= To: freebsd-current@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 16 Mar 2013 14:51:03 -0000 Is there a problem with the GSSAPI implementation in FreeBSD? I'm trying to compile a minimal application that does nothing more than including the file gssapi/gssapi_krb5.h: #include int main(void) { return 0; } When compiling this with "gcc foo.c" I get the following error: In file included from foo.c:1: /usr/include/gssapi/gssapi_krb5.h:139: error: expected declaration specifiers or '...' before 'time_t' I have to admit that I'm a bit stumped as to why I get the error message in the first place. The line in question looks like this: OM_uint32 gsskrb5_extract_authtime_from_sec_context(OM_uint32 *, gss_ctx_id_t, time_t *); I checked the preprocessor output and there are indeed correct typedefs for OM_uint32, gss_ctx_id_t and time_t, so I can't really see why this error would occur. In any case, given the import program, this behaviour isn't really correct as far as I can tell. Any input on this? Regards, Elias From owner-freebsd-current@FreeBSD.ORG Sat Mar 16 16:00:56 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id BABE44A7 for ; Sat, 16 Mar 2013 16:00:56 +0000 (UTC) (envelope-from gpalmer@freebsd.org) Received: from noop.in-addr.com (mail.in-addr.com [IPv6:2001:470:8:162::1]) by mx1.freebsd.org (Postfix) with ESMTP id 8F65F308 for ; Sat, 16 Mar 2013 16:00:56 +0000 (UTC) Received: from gjp by noop.in-addr.com with local (Exim 4.80.1 (FreeBSD)) (envelope-from ) id 1UGtXS-000Cch-GK; Sat, 16 Mar 2013 12:00:54 -0400 Date: Sat, 16 Mar 2013 12:00:54 -0400 From: Gary Palmer To: Daniel Nebdal Subject: Re: multi-homing in freebsd Message-ID: <20130316160054.GB52706@in-addr.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: gpalmer@freebsd.org X-SA-Exim-Scanned: No (on noop.in-addr.com); SAEximRunCond expanded to false Cc: Zaphod Beeblebrox , Yasir hussan , Current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 16 Mar 2013 16:00:56 -0000 On Sat, Mar 09, 2013 at 01:29:27PM +0100, Daniel Nebdal wrote: > Going by Zaphod's recommendation of using a /32 for each IP, how about this? > > ifconfig arge0 inet 192.168.1.100/32 > ifconfig arge0 alias 192.169.1.100/32 > > I wouldn't recommend 192.169, though - only 192.168.x.x is reserved > for private networks, and 192.169 is a valid IP-routable prefix, > assigned to some US company. > To be exact: The ranges from RFC1918 are 10.0.0.0/8, 172.16.0.0 /20 > and 192.168.0.0/24. I think you mean the RFC1918 ranges are 10.0.0.0/8 (aka 10.0.0.0 through 10.255.255.255) 172.16.0.0/12 (aka 172.16.0.0 through 172.31.255.255) 192.168.0.0/16 (aka 192.168.0.0 through 192.168.255.255) Regards, Gary From owner-freebsd-current@FreeBSD.ORG Sat Mar 16 16:59:52 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 6029C34F for ; Sat, 16 Mar 2013 16:59:52 +0000 (UTC) (envelope-from deeptech71@gmail.com) Received: from mail-ea0-x22f.google.com (mail-ea0-x22f.google.com [IPv6:2a00:1450:4013:c01::22f]) by mx1.freebsd.org (Postfix) with ESMTP id F170D886 for ; Sat, 16 Mar 2013 16:59:51 +0000 (UTC) Received: by mail-ea0-f175.google.com with SMTP id o10so1927129eaj.6 for ; Sat, 16 Mar 2013 09:59:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; bh=C9B/7x9382G8n6iD1+ytauolkb5xb2SF+Yj7nCrmlJQ=; b=ztvVOwwVAfAAOieETHNSw/Cmp0VWdFcJi+rCMkPspIIhthiS2AfIc9Cpsgg4ViInZn Wr8mBCs+FVSCvnqRhY8+MRWO5N8gLft39fteo1VGUpXt4EQlkgmmxCoMOhizAbZLyCVD U3S0I/A/FhVJ/oyEl6OVYW3O3ra1265Eo0rk15aVGs/au5BKFsMnm0ksLKK6tWNAF4Nq e3Is8JIr0L3z4H6CBWVNPNa2D/BkSs/EWwpNuVBsdzyePYtyheWepfIwlDfdB0cblOq3 8GoPZIWnAN8gKPlqtTiZVq2UQWaSMawwRzN49MslkT42ojERLnF1nrviUDUoo6i6+CGV JMjw== X-Received: by 10.15.45.201 with SMTP id b49mr30615950eew.9.1363453190987; Sat, 16 Mar 2013 09:59:50 -0700 (PDT) Received: from [192.168.1.80] (4E5C584D.dsl.pool.telekom.hu. [78.92.88.77]) by mx.google.com with ESMTPS id s3sm16865114eem.4.2013.03.16.09.59.49 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 16 Mar 2013 09:59:49 -0700 (PDT) Message-ID: <5144A501.3070502@gmail.com> Date: Sat, 16 Mar 2013 17:59:45 +0100 From: deeptech71 User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:18.0) Gecko/20100101 SeaMonkey/2.15 MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: mdoc warning: .Fx: Unknown FreeBSD version `10' (#181) Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 16 Mar 2013 16:59:52 -0000 When running ``man script'' (world r248258), I get: mdoc warning: .Fx: Unknown FreeBSD version `10' (#181) (and the whole man page, which quickly hides the warning). From owner-freebsd-current@FreeBSD.ORG Sat Mar 16 20:29:56 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id DB363DFE for ; Sat, 16 Mar 2013 20:29:55 +0000 (UTC) (envelope-from kaduk@mit.edu) Received: from dmz-mailsec-scanner-3.mit.edu (DMZ-MAILSEC-SCANNER-3.MIT.EDU [18.9.25.14]) by mx1.freebsd.org (Postfix) with ESMTP id 84C66157 for ; Sat, 16 Mar 2013 20:29:54 +0000 (UTC) X-AuditID: 1209190e-b7f266d0000008cb-3d-5144d50fb7bc Received: from mailhub-auth-2.mit.edu ( [18.7.62.36]) by dmz-mailsec-scanner-3.mit.edu (Symantec Messaging Gateway) with SMTP id 4C.03.02251.F05D4415; Sat, 16 Mar 2013 16:24:47 -0400 (EDT) Received: from outgoing.mit.edu (OUTGOING-AUTH-1.MIT.EDU [18.9.28.11]) by mailhub-auth-2.mit.edu (8.13.8/8.9.2) with ESMTP id r2GKOlw3029563; Sat, 16 Mar 2013 16:24:47 -0400 Received: from multics.mit.edu (SYSTEM-LOW-SIPB.MIT.EDU [18.187.2.37]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.8/8.12.4) with ESMTP id r2GKOjiP030963 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sat, 16 Mar 2013 16:24:46 -0400 Received: (from kaduk@localhost) by multics.mit.edu (8.12.9.20060308) id r2GKOj0L016228; Sat, 16 Mar 2013 16:24:45 -0400 (EDT) Date: Sat, 16 Mar 2013 16:24:44 -0400 (EDT) From: Benjamin Kaduk To: =?ISO-8859-15?Q?Elias_M=E5rtenson?= Subject: Re: Strange error when compiling minimal GSSAPI application In-Reply-To: Message-ID: References: User-Agent: Alpine 1.10 (GSO 962 2008-03-14) MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="-559023410-362651775-1363465485=:9389" X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmpmleLIzCtJLcpLzFFi42IRYrdT0eW/6hJosGG5icWcNx+YLJ5M5HZg 8pjxaT6Lx85Zd9kDmKK4bFJSczLLUov07RK4Mh7vXMxc0ClS8fPeD9YGxukCXYycHBICJhIT 3j5igbDFJC7cW8/WxcjFISSwj1Gi+fFvKGcjo8TxP4+hnENMEkcngTicQE4Do0TjkjoQm0VA W2Lt5r9go9gEVCRmvtkIViMiYC2x69tmMJtZQF7i/5XLTCC2sICLxIlLT8DinAKBEjs+TwWL 8wo4SBy9tpgFYn6AROuiX8wgtqiAjsTq/VNYIGoEJU7OfMICMdNfYvK77ywTGAVnIUnNQpKa xcgBZNtITLhXCRHWlrh/s41tASPLKkbZlNwq3dzEzJzi1GTd4uTEvLzUIl1jvdzMEr3UlNJN jKCw5pTk28H49aDSIUYBDkYlHt4GV+dAIdbEsuLK3EOMkhxMSqK8N0+4BArxJeWnVGYkFmfE F5XmpBYfYpTgYFYS4a2uAMrxpiRWVqUW5cOkpDlYlMR5r6Tc9BcSSE8sSc1OTS1ILYLJynBw KEnwnr8M1ChYlJqeWpGWmVOCkGbi4AQZzgM0XOUKyPDigsTc4sx0iPwpRkUpcd7dIM0CIImM 0jy4XljaecUoDvSKMO8nkCoeYMqC634FNJgJaPC+K04gg0sSEVJSDYwJhbtcTJ3rQupqLXPn zy6fl3/LeO51x1dWz3ZUap35uIRhWeBs0/vMug4sS9M+sX/pLE7fcenOobds3wVW2bx+1XVW 3NtjHaMlV/viUjYWNd2bld/WKt7Y5vHGuOlgsqHf6pKO6hVuGa0l+9esahUI1Ux92S2ePJe5 WO09J/OXeoZJ9nPUKpRYijMSDbWYi4oTAYxG/IAWAwAA Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 16 Mar 2013 20:29:56 -0000 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. ---559023410-362651775-1363465485=:9389 Content-Type: TEXT/PLAIN; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: QUOTED-PRINTABLE On Sat, 16 Mar 2013, Elias M=E5rtenson wrote: > Is there a problem with the GSSAPI implementation in FreeBSD? There might be; I can't remember if I had trouble with it in my current=20 application even before I started using the gss_pseudo_random feature=20 which it does not support (which caused me to switch to the MIT krb5=20 implementation). > I'm trying to compile a minimal application that does nothing more than > including the file gssapi/gssapi_krb5.h: > > #include > > int main(void) > { > return 0; > } You do not mention which version of FreeBSD you are using. > When compiling this with "gcc foo.c" I get the following error: > > In file included from foo.c:1: > /usr/include/gssapi/gssapi_krb5.h:139: error: expected declaration > specifiers or '...' before 'time_t' I find that clang's warning/error messages are frequently more helpful=20 than gcc's. Running the same experiment on my 10-current (r247267) setup= =20 I get a somewhat different error: /usr/include/gssapi/gssapi_krb5.h:56: error: expected '=3D', ',', ';', 'asm= '=20 or '__attribute__' before 'extern' It seems that GSSAPI_CPP_START is never defined, for one. > I have to admit that I'm a bit stumped as to why I get the error message = in > the first place. The line in question looks like this: > > OM_uint32 > gsskrb5_extract_authtime_from_sec_context(OM_uint32 *, gss_ctx_id_t, > time_t *); > > I checked the preprocessor output and there are indeed correct typedefs f= or > OM_uint32, gss_ctx_id_t and time_t, so I can't really see why this error > would occur. The previous line may also be relevant. You do not have any=20 GSSAPI_LIB_FUNCTION or GSSAPI_LIB_CALL macros in the type specification of= =20 the function, though? (I do.) > In any case, given the import program, this behaviour isn't really correc= t > as far as I can tell. > > Any input on this? The provided gssapi_krb5 support is certainly suboptimal -- including the= =20 header at all gives a warning that it uses the deprecated path "gssapi.h"= =20 to get the generic gssapi declarations. Might be, it needs further love. -Ben Kaduk ---559023410-362651775-1363465485=:9389-- From owner-freebsd-current@FreeBSD.ORG Sat Mar 16 21:48:05 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id E2DB2D3F for ; Sat, 16 Mar 2013 21:48:05 +0000 (UTC) (envelope-from rmacklem@uoguelph.ca) Received: from esa-jnhn.mail.uoguelph.ca (esa-jnhn.mail.uoguelph.ca [131.104.91.44]) by mx1.freebsd.org (Postfix) with ESMTP id 8EB5036F for ; Sat, 16 Mar 2013 21:48:05 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AqEEAOfnRFGDaFvO/2dsb2JhbABDiDS9AIIDdIIqAQEBAwEBAQEgKyALBRYaAg0ZAikBCSYGCAcEARwEh20GDLBxkXaBI4xCfDQHgi2BEwOUIII+gR+PY4MmIDKBBTU X-IronPort-AV: E=Sophos;i="4.84,857,1355115600"; d="scan'208";a="21550684" Received: from erie.cs.uoguelph.ca (HELO zcs3.mail.uoguelph.ca) ([131.104.91.206]) by esa-jnhn.mail.uoguelph.ca with ESMTP; 16 Mar 2013 17:48:04 -0400 Received: from zcs3.mail.uoguelph.ca (localhost.localdomain [127.0.0.1]) by zcs3.mail.uoguelph.ca (Postfix) with ESMTP id 34683B3F16; Sat, 16 Mar 2013 17:48:04 -0400 (EDT) Date: Sat, 16 Mar 2013 17:48:04 -0400 (EDT) From: Rick Macklem To: =?utf-8?Q?Elias_M=C3=A5rtenson?= Message-ID: <2066103901.3973627.1363470484193.JavaMail.root@erie.cs.uoguelph.ca> In-Reply-To: Subject: Re: Strange error when compiling minimal GSSAPI application MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [172.17.91.203] X-Mailer: Zimbra 6.0.10_GA_2692 (ZimbraWebClient - FF3.0 (Win)/6.0.10_GA_2692) Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 16 Mar 2013 21:48:05 -0000 Elias Martenson wrote: > Is there a problem with the GSSAPI implementation in FreeBSD? > > I'm trying to compile a minimal application that does nothing more > than > including the file gssapi/gssapi_krb5.h: > If you add: #include it compiles. in included by krb5.h, which I suspect most programs that use the gssapi_krb5.h stuff also uses. rick > #include > > int main(void) > { > return 0; > } > > When compiling this with "gcc foo.c" I get the following error: > > In file included from foo.c:1: > /usr/include/gssapi/gssapi_krb5.h:139: error: expected declaration > specifiers or '...' before 'time_t' > > I have to admit that I'm a bit stumped as to why I get the error > message in > the first place. The line in question looks like this: > > OM_uint32 > gsskrb5_extract_authtime_from_sec_context(OM_uint32 *, gss_ctx_id_t, > time_t *); > > I checked the preprocessor output and there are indeed correct > typedefs for > OM_uint32, gss_ctx_id_t and time_t, so I can't really see why this > error > would occur. > > In any case, given the import program, this behaviour isn't really > correct > as far as I can tell. > > Any input on this? > > Regards, > Elias > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to > "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@FreeBSD.ORG Sat Mar 16 22:05:08 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id B06583B1 for ; Sat, 16 Mar 2013 22:05:08 +0000 (UTC) (envelope-from f0andrey@gmail.com) Received: from mail-wi0-x230.google.com (mail-wi0-x230.google.com [IPv6:2a00:1450:400c:c05::230]) by mx1.freebsd.org (Postfix) with ESMTP id 2938A401 for ; Sat, 16 Mar 2013 22:05:08 +0000 (UTC) Received: by mail-wi0-f176.google.com with SMTP id hm14so1566575wib.9 for ; Sat, 16 Mar 2013 15:05:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=6MzJ7PAnL9/kwSd+j3tWQGq7/hfMtBVj0bRfkk9koJA=; b=SGP8BFetUzVFYStuSk6cGX6u85o8s2PbICNL/jIsO6j2Apl4s5VYUG3JlPcb43XSYU zLDcMY52qQWNcf4xKIwkySyu8v95jOKV+/CZ9wL1oIx5AqmgEP0wfQGxNVSZFB/ePDIf pRRIoPzGPdBvxc/JE/MS630Hi551TD2hF7W6mCuTUaAPVlGBLXhNvF1pDo08L34jH+/M IwiU6hps64jS564H49ZCzHRkgGADvQZRwEBfFkBB0sQJvsEmKUdvBfjGahyrhlrSop72 NAJS6HkpH3oyYf6kDa8f4Mk0omaHc3YTMP4YKQwUZbr9HRxVNggvPdkMOd7FZAStU+3b 02SA== MIME-Version: 1.0 X-Received: by 10.180.109.82 with SMTP id hq18mr9587439wib.0.1363471507211; Sat, 16 Mar 2013 15:05:07 -0700 (PDT) Received: by 10.194.157.35 with HTTP; Sat, 16 Mar 2013 15:05:07 -0700 (PDT) In-Reply-To: <5144A501.3070502@gmail.com> References: <5144A501.3070502@gmail.com> Date: Sun, 17 Mar 2013 02:05:07 +0400 Message-ID: Subject: Re: mdoc warning: .Fx: Unknown FreeBSD version `10' (#181) From: Andrey Fesenko To: deeptech71 Content-Type: text/plain; charset=UTF-8 Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 16 Mar 2013 22:05:08 -0000 On Sat, Mar 16, 2013 at 8:59 PM, deeptech71 wrote: > When running ``man script'' (world r248258), I get: > > mdoc warning: .Fx: Unknown FreeBSD version `10' (#181) > > (and the whole man page, which quickly hides the warning). reproduce # whereis man man: /usr/bin/man /usr/share/man/man1/man.1.gz /usr/src/usr.bin/man # uname -a FreeBSD x220.local 10.0-CURRENT FreeBSD 10.0-CURRENT #0 r248378: Sun Mar 17 00:11:12 MSK 2013 andrey@x220.local:/usr/obj/usr/src/sys/W_BOOK amd64 % man script | head -1 mdoc warning: .Fx: Unknown FreeBSD version `10' (#181) SCRIPT(1) FreeBSD General Commands Manual SCRIPT(1) not correct macros .Fx may be fix % diff script.1 script.1.orig 181c181 < .Fx 10.0 . --- > .Fx 10 . mandoc without this error From owner-freebsd-current@FreeBSD.ORG Sat Mar 16 22:20:28 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id EB6E56FB for ; Sat, 16 Mar 2013 22:20:28 +0000 (UTC) (envelope-from kaduk@mit.edu) Received: from dmz-mailsec-scanner-8.mit.edu (DMZ-MAILSEC-SCANNER-8.MIT.EDU [18.7.68.37]) by mx1.freebsd.org (Postfix) with ESMTP id 814B1650 for ; Sat, 16 Mar 2013 22:20:28 +0000 (UTC) X-AuditID: 12074425-b7fec6d000007584-c6-5144eef9fc11 Received: from mailhub-auth-3.mit.edu ( [18.9.21.43]) by dmz-mailsec-scanner-8.mit.edu (Symantec Messaging Gateway) with SMTP id 53.C3.30084.9FEE4415; Sat, 16 Mar 2013 18:15:21 -0400 (EDT) Received: from outgoing.mit.edu (OUTGOING-AUTH-1.MIT.EDU [18.9.28.11]) by mailhub-auth-3.mit.edu (8.13.8/8.9.2) with ESMTP id r2GMFKv5030234; Sat, 16 Mar 2013 18:15:21 -0400 Received: from multics.mit.edu (SYSTEM-LOW-SIPB.MIT.EDU [18.187.2.37]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.8/8.12.4) with ESMTP id r2GMFIjO031919 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sat, 16 Mar 2013 18:15:19 -0400 Received: (from kaduk@localhost) by multics.mit.edu (8.12.9.20060308) id r2GMFIGk000233; Sat, 16 Mar 2013 18:15:18 -0400 (EDT) Date: Sat, 16 Mar 2013 18:15:18 -0400 (EDT) From: Benjamin Kaduk To: Rick Macklem Subject: Re: Strange error when compiling minimal GSSAPI application In-Reply-To: <2066103901.3973627.1363470484193.JavaMail.root@erie.cs.uoguelph.ca> Message-ID: References: <2066103901.3973627.1363470484193.JavaMail.root@erie.cs.uoguelph.ca> User-Agent: Alpine 1.10 (GSO 962 2008-03-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrGIsWRmVeSWpSXmKPExsUixCmqrfvznUugwcefehZz3nxgsngykdvi 4bJrTA7MHjM+zWfx2DnrLrvH7817mQKYo7hsUlJzMstSi/TtErgy7jTvZS54ylwxd143UwPj P6YuRk4OCQETiV83PrFA2GISF+6tZ+ti5OIQEtjHKHFzygImCGcjo8SL5WfYQaqEBA4xSfSs q4dINDBKrL53GqydRUBbYuOnB2wgNpuAisTMNxvBbBEBdYnNq/uZQWxmgUSJ/zuOgsWFBVwk Tlx6AmZzCgRKPD50EqyGV8BB4uD2X2wQywIk3h1awApiiwroSKzeP4UFokZQ4uTMJywQMy0l zv25zjaBUXAWktQsJKkFjEyrGGVTcqt0cxMzc4pTk3WLkxPz8lKLdC30cjNL9FJTSjcxgoKX 3UV1B+OEQ0qHGAU4GJV4eCvsnAOFWBPLiitzDzFKcjApifJefukSKMSXlJ9SmZFYnBFfVJqT WnyIUYKDWUmEt7oCKMebklhZlVqUD5OS5mBREue9kXLTX0ggPbEkNTs1tSC1CCYrw8GhJMEr DoxSIcGi1PTUirTMnBKENBMHJ8hwHqDh9SA1vMUFibnFmekQ+VOMilLivBYgCQGQREZpHlwv LLm8YhQHekWY1wWkigeYmOC6XwENZgIavO+KE8jgkkSElFQD41rXzKS9lr47NOJSjXsq/5Uo zRZN1nmalt4dnbigL/SUzcflJyaVRhbY9T3+692lmLtJ+telv2cy/hyYblCcfXbJ08XfznSV 8lhlMtzpna50q2bFlH/mUgF/tv2eK1n/1r4l9lu5wBUROY+OSvV3YjMZYk49//iloCF2Y95z qwpP1Xc5XjwvlViKMxINtZiLihMBg1oNvAkDAAA= Cc: freebsd-current@freebsd.org, =?ISO-8859-15?Q?Elias_M=E5rtenson?= X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 16 Mar 2013 22:20:29 -0000 On Sat, 16 Mar 2013, Rick Macklem wrote: > Elias Martenson wrote: > >> Is there a problem with the GSSAPI implementation in FreeBSD? >> >> I'm trying to compile a minimal application that does nothing more >> than >> including the file gssapi/gssapi_krb5.h: >> > If you add: > #include > it compiles. in included by krb5.h, which I suspect most > programs that use the gssapi_krb5.h stuff also uses. Which FreeBSD version are you on, Rick? -Ben From owner-freebsd-current@FreeBSD.ORG Sat Mar 16 22:40:18 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 2955BDFF for ; Sat, 16 Mar 2013 22:40:18 +0000 (UTC) (envelope-from pluknet@gmail.com) Received: from mail-we0-x232.google.com (mail-we0-x232.google.com [IPv6:2a00:1450:400c:c03::232]) by mx1.freebsd.org (Postfix) with ESMTP id BD9BF6E5 for ; Sat, 16 Mar 2013 22:40:17 +0000 (UTC) Received: by mail-we0-f178.google.com with SMTP id o45so3818961wer.23 for ; Sat, 16 Mar 2013 15:40:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=EZ2ESC/15wQ1bjMRFxcqsbT4DGSVNj+jp+1/U25nN+w=; b=NFjoje49DOjLnkbdw2srMH86pEXVIrVBi4rXzr+MBXNS6wrPqN16N/7Rj9OdtJPmXO 2Lx76hIi7FOnPQWMEnMLS/mUAnk4WXV44T08gdBPldxPOX15akSL6mRB7P9MmM5c6NIX i0vCJCMK1YuYS6EPB+vnEMcx2bTej8udTjNJWWwLnqcJB/uD4DBqzVNcm5EoIODV1yKP xcjg+Qopz1ZTQHceXbxZVLlMbChjllR+1CXWR6NSVXSJ3jc75jmO3r2qiUtP5wPGYef2 Z5Q2Uw4yV0nykZ9Sam2enSgWmJZ19nSSv2HBrNPYVacQhtlXZjnRnjMx44X/v7hlcusF 4eig== MIME-Version: 1.0 X-Received: by 10.180.79.227 with SMTP id m3mr9525381wix.12.1363473615557; Sat, 16 Mar 2013 15:40:15 -0700 (PDT) Received: by 10.194.86.167 with HTTP; Sat, 16 Mar 2013 15:40:15 -0700 (PDT) In-Reply-To: References: <5144A501.3070502@gmail.com> Date: Sun, 17 Mar 2013 02:40:15 +0400 Message-ID: Subject: Re: mdoc warning: .Fx: Unknown FreeBSD version `10' (#181) From: Sergey Kandaurov To: Andrey Fesenko , deeptech71 Content-Type: text/plain; charset=ISO-8859-1 Cc: FreeBSD Current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 16 Mar 2013 22:40:18 -0000 On 17 March 2013 02:05, Andrey Fesenko wrote: > On Sat, Mar 16, 2013 at 8:59 PM, deeptech71 wrote: >> When running ``man script'' (world r248258), I get: >> >> mdoc warning: .Fx: Unknown FreeBSD version `10' (#181) >> >> (and the whole man page, which quickly hides the warning). > > reproduce > > # whereis man > man: /usr/bin/man /usr/share/man/man1/man.1.gz /usr/src/usr.bin/man > # uname -a > FreeBSD x220.local 10.0-CURRENT FreeBSD 10.0-CURRENT #0 r248378: Sun > Mar 17 00:11:12 MSK 2013 > andrey@x220.local:/usr/obj/usr/src/sys/W_BOOK amd64 > > % man script | head -1 > mdoc warning: .Fx: Unknown FreeBSD version `10' (#181) > SCRIPT(1) FreeBSD General Commands Manual SCRIPT(1) > > not correct macros .Fx may be fix > % diff script.1 script.1.orig > 181c181 > < .Fx 10.0 . > --- >> .Fx 10 . Fix committed in r248388, thanks. -- wbr, pluknet From owner-freebsd-current@FreeBSD.ORG Sat Mar 16 23:13:59 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id F010A1D6; Sat, 16 Mar 2013 23:13:59 +0000 (UTC) (envelope-from jbeich@tormail.org) Received: from outgoing.tormail.org (outgoing.tormail.org [82.221.96.22]) by mx1.freebsd.org (Postfix) with ESMTP id AF96D81E; Sat, 16 Mar 2013 23:13:59 +0000 (UTC) Received: from localhost ([127.0.0.1] helo=internal.tormail.org) by outgoing.tormail.org with esmtp (Exim 4.72) (envelope-from ) id 1UH0IO-00068j-DJ; Sun, 17 Mar 2013 02:13:50 +0300 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=tormail.org; s=tm; h=Message-Id:X-TorMail-User:Content-Type:MIME-Version:References:Date:In-Reply-To:Subject:Cc:To:From; bh=jOqHM8ZnQnJOEZxoAjgqk2BI0vKKkASvTdp6ptYjT2Q=; b=h11BvG4/EksvPzsCJjLsGhQkWqWJN1ii5srD/deR0jKa1b+WhlD6KUOQIh69Qbf6kcKtl8zNxB7FYYiowiM9h/hkZhJO8HMukjdb0MyUHhjqT9rN7Me9zkQFfSh0Ozh/s8t2BTCY4L3Rh/RsnEWr9JIyQQfDdGFQTU5Oho0dAqI=; Received: from jbeich by internal.tormail.org with local (Exim 4.63) (envelope-from ) id 1UH0FV-0007mk-8T; Sat, 16 Mar 2013 23:10:51 +0000 From: Jan Beich To: Andrey Fesenko Subject: Re: mdoc warning: .Fx: Unknown FreeBSD version `10' (#181) In-Reply-To: (Andrey Fesenko's message of "Sun, 17 Mar 2013 02:05:07 +0400") Date: Sun, 17 Mar 2013 09:11:31 +1000 References: <5144A501.3070502@gmail.com> MIME-Version: 1.0 Content-Type: text/plain X-TorMail-User: jbeich Message-Id: <1UH0FV-0007mk-8T@internal.tormail.org> Cc: deeptech71 , freebsd-current@freebsd.org, Brian Somers X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 16 Mar 2013 23:14:00 -0000 Andrey Fesenko writes: > On Sat, Mar 16, 2013 at 8:59 PM, deeptech71 wrote: > >> When running ``man script'' (world r248258), I get: >> >> mdoc warning: .Fx: Unknown FreeBSD version `10' (#181) >> >> (and the whole man page, which quickly hides the warning). There's one more .Fx bug in __iconv_get_list(3) since 9.0. > not correct macros .Fx may be fix > % diff script.1 script.1.orig > 181c181 > < .Fx 10.0 . > --- >> .Fx 10 . Brian, what happened to MFC'ing -d/-p/-r options ? r238896 seems to work just fine on script(1) from /stable/9 and /stable/8. From owner-freebsd-current@FreeBSD.ORG Sat Mar 16 23:22:13 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 2A50E6A4; Sat, 16 Mar 2013 23:22:13 +0000 (UTC) (envelope-from dnebdal@gmail.com) Received: from mail-la0-x22d.google.com (mail-la0-x22d.google.com [IPv6:2a00:1450:4010:c03::22d]) by mx1.freebsd.org (Postfix) with ESMTP id 538D1880; Sat, 16 Mar 2013 23:22:12 +0000 (UTC) Received: by mail-la0-f45.google.com with SMTP id er20so4959597lab.32 for ; Sat, 16 Mar 2013 16:22:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=pU8E3wP9LoyIq57CxjNQZ3QYfBFHBQx3W4TKdqUyw/g=; b=BV9gB/H8rqs9dmtBMGZ9cqVh7PS7G1Jorv66F7/whRUT6HOJWUiVEztU6gGl7WRxOc ugWE63AsPQPgfEpV6acs10LiC7rtS/UDxQWI7oXduFMCp59lkrqt25E/kNaQWFA41Pdx 6s8hIP7NFYbVGsP44IWYKe+sMLGBmHywV15yJTRCL8+BBemOvUXYEqL3zP18bx/USzmL TgLohtpL7+GfaGcBL6aAbLuRwLHi9yrL2ySMay2dWFGNWG2IsElZF/BkxU8xEWCHyOnS sYvZS1EkKeRAUEJzmB88ulpg+PNBH0uQopkxlJUJNQbjwZMZsCkqzerW5pS+UywVNZ9L zzlw== MIME-Version: 1.0 X-Received: by 10.152.123.34 with SMTP id lx2mr9972313lab.52.1363476131158; Sat, 16 Mar 2013 16:22:11 -0700 (PDT) Received: by 10.112.80.133 with HTTP; Sat, 16 Mar 2013 16:22:11 -0700 (PDT) In-Reply-To: <20130316160054.GB52706@in-addr.com> References: <20130316160054.GB52706@in-addr.com> Date: Sun, 17 Mar 2013 00:22:11 +0100 Message-ID: Subject: Re: multi-homing in freebsd From: Daniel Nebdal To: Gary Palmer Content-Type: text/plain; charset=ISO-8859-1 Cc: Zaphod Beeblebrox , Yasir hussan , Current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 16 Mar 2013 23:22:13 -0000 On Sat, Mar 16, 2013 at 5:00 PM, Gary Palmer wrote: > On Sat, Mar 09, 2013 at 01:29:27PM +0100, Daniel Nebdal wrote: >> Going by Zaphod's recommendation of using a /32 for each IP, how about this? >> >> ifconfig arge0 inet 192.168.1.100/32 >> ifconfig arge0 alias 192.169.1.100/32 >> >> I wouldn't recommend 192.169, though - only 192.168.x.x is reserved >> for private networks, and 192.169 is a valid IP-routable prefix, >> assigned to some US company. >> To be exact: The ranges from RFC1918 are 10.0.0.0/8, 172.16.0.0 /20 >> and 192.168.0.0/24. > > I think you mean the RFC1918 ranges are > > 10.0.0.0/8 (aka 10.0.0.0 through 10.255.255.255) > 172.16.0.0/12 (aka 172.16.0.0 through 172.31.255.255) > 192.168.0.0/16 (aka 192.168.0.0 through 192.168.255.255) > > Regards, > > Gary Uhm, yes. I can't have been entirely awake when I wrote that.