From owner-freebsd-arch@freebsd.org Sun Oct 11 03:20:44 2015 Return-Path: Delivered-To: freebsd-arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id CF0EDA0FB99 for ; Sun, 11 Oct 2015 03:20:44 +0000 (UTC) (envelope-from vangyzen@FreeBSD.org) Received: from smtp.vangyzen.net (hotblack.vangyzen.net [199.48.133.146]) by mx1.freebsd.org (Postfix) with ESMTP id AEB3C1A9B for ; Sun, 11 Oct 2015 03:20:43 +0000 (UTC) (envelope-from vangyzen@FreeBSD.org) Received: from coconut.local (unknown [76.164.15.242]) by smtp.vangyzen.net (Postfix) with ESMTPSA id A63B95649D for ; Sat, 10 Oct 2015 22:20:36 -0500 (CDT) Subject: Re: RFC: Automatically Reloading /etc/resolv.conf To: freebsd-arch@freebsd.org References: <5615886F.3060601@FreeBSD.org> From: Eric van Gyzen Message-ID: <5619D580.7040505@FreeBSD.org> Date: Sat, 10 Oct 2015 22:20:32 -0500 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 In-Reply-To: <5615886F.3060601@FreeBSD.org> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Oct 2015 03:20:44 -0000 On 10/7/15 4:02 PM, Eric van Gyzen wrote: > I would like to change the libc resolver to automatically reload > /etc/resolv.conf when the latter changes. I implemented and tested the rate-limited stat(2) approach. I would be grateful for a review: https://reviews.freebsd.org/D3867 Eric From owner-freebsd-arch@freebsd.org Tue Oct 13 08:05:03 2015 Return-Path: Delivered-To: freebsd-arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 725A7A110A8 for ; Tue, 13 Oct 2015 08:05:03 +0000 (UTC) (envelope-from hps@selasky.org) Received: from mail.turbocat.net (heidi.turbocat.net [88.198.202.214]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 3B2121D9C for ; Tue, 13 Oct 2015 08:05:02 +0000 (UTC) (envelope-from hps@selasky.org) Received: from laptop015.home.selasky.org (cm-176.74.213.204.customer.telag.net [176.74.213.204]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.turbocat.net (Postfix) with ESMTPSA id 2E4CF1FE022 for ; Tue, 13 Oct 2015 10:04:52 +0200 (CEST) To: "freebsd-arch@freebsd.org" From: Hans Petter Selasky Subject: [RFC] New callout API function coming Message-ID: <561CBB8B.5010508@selasky.org> Date: Tue, 13 Oct 2015 10:06:35 +0200 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Oct 2015 08:05:03 -0000 Hi, I'm currently working together with Julien Charbon on adding a new callout_drain_async() function to the callout API. If you have some comments or questions, the patch is available here: https://reviews.freebsd.org/D3521 I hope to submit this piece of code by the end of this week. --HPS From owner-freebsd-arch@freebsd.org Thu Oct 15 05:05:15 2015 Return-Path: Delivered-To: freebsd-arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 83CE8A150D0 for ; Thu, 15 Oct 2015 05:05:15 +0000 (UTC) (envelope-from bdrewery@FreeBSD.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 6B3E81C2F for ; Thu, 15 Oct 2015 05:05:15 +0000 (UTC) (envelope-from bdrewery@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id 6A698A150CF; Thu, 15 Oct 2015 05:05:15 +0000 (UTC) Delivered-To: arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6A00EA150CE for ; Thu, 15 Oct 2015 05:05:15 +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 589941C2E for ; Thu, 15 Oct 2015 05:05:15 +0000 (UTC) (envelope-from bdrewery@FreeBSD.org) Received: from mail.xzibition.com (localhost [IPv6:::1]) by freefall.freebsd.org (Postfix) with ESMTP id 527D9132F for ; Thu, 15 Oct 2015 05:05:15 +0000 (UTC) (envelope-from bdrewery@FreeBSD.org) Received: from mail.xzibition.com (localhost [172.31.3.2]) by mail.xzibition.com (Postfix) with ESMTP id 06BF4FAAC for ; Thu, 15 Oct 2015 05:05:15 +0000 (UTC) X-Virus-Scanned: amavisd-new at mail.xzibition.com Received: from mail.xzibition.com ([172.31.3.2]) by mail.xzibition.com (mail.xzibition.com [172.31.3.2]) (amavisd-new, port 10026) with LMTP id uo9SYrWURUB8 for ; Thu, 15 Oct 2015 05:05:12 +0000 (UTC) To: arch@FreeBSD.org DKIM-Filter: OpenDKIM Filter v2.9.2 mail.xzibition.com EDF51FAA4 From: Bryan Drewery Subject: make -n -n X-Enigmail-Draft-Status: N1110 Organization: FreeBSD Message-ID: <561F3406.9050906@FreeBSD.org> Date: Wed, 14 Oct 2015 22:05:10 -0700 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Oct 2015 05:05:15 -0000 Does anyone consider 'make -n -n' a thing for top-level builds? We have this ${_+_} thing in Makefiles that used to expand to '+' if you gave '-n -n'. This was so just 1 '-n' would just show what the top-level Makefile would do: ~/svn/clean2 # make -n includes cd /root/svn/clean2; PATH=3D/sbin:/bin:/usr/sbin:/usr/bin make -m /root/svn/clean2/share/mk -f Makefile.inc1 TARGET=3Damd64 TARGET_ARCH=3Damd64 includes Versus the more expected (at least for bmake) -n behavior of traversing sub-makes: ~/svn/clean2 # make -n -n includes =3D=3D=3D> lib (includes) =3D=3D=3D> lib/csu (includes) =3D=3D=3D> lib/csu/amd64 (includes) =3D=3D=3D> lib/libcompiler_rt (includes) =3D=3D=3D> lib/libc (includes) =3D=3D=3D> lib/libc/tests (includes) =3D=3D=3D> lib/libc/tests/tls_dso (includes) =3D=3D=3D> lib/libc/tests/c063 (includes) etc... Note the actual output may be off due to local changes, but the point is that -n with bmake is documented to run sub-makes with -n as well, so it calls right down the chain showing all build commands without taking any real actions. Bmake added a '-N' flag that essentially does the hack that we've put into our top-level Makefile - it doesn't run sub-makes. So having said all of that, the ${_+_} never expands anymore since r251748 (June 2013). The act of it working in top-level has only been fixed since r288391 (September 2015). Given it was broken for this long period I assume no one uses '-n -n' or even knew about it. I would like to remove it (-n -n and _+_) and just use the (bmake) documented -n and -N flags and use '+' everywhere appropriate. Note that we use .MAKE in some targets that achieves largely the same thing, but many sub-make calls don't have a .MAKE and lack a proper '+' to recurse in Makefile.inc1. --=20 Regards, Bryan Drewery From owner-freebsd-arch@freebsd.org Thu Oct 15 05:17:53 2015 Return-Path: Delivered-To: freebsd-arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BC971A15460 for ; Thu, 15 Oct 2015 05:17:53 +0000 (UTC) (envelope-from bdrewery@FreeBSD.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id A3725E0 for ; Thu, 15 Oct 2015 05:17:53 +0000 (UTC) (envelope-from bdrewery@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id A0733A1545E; Thu, 15 Oct 2015 05:17:53 +0000 (UTC) Delivered-To: arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A00EFA1545D for ; Thu, 15 Oct 2015 05:17:53 +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 8E356DF for ; Thu, 15 Oct 2015 05:17:53 +0000 (UTC) (envelope-from bdrewery@FreeBSD.org) Received: from mail.xzibition.com (localhost [IPv6:::1]) by freefall.freebsd.org (Postfix) with ESMTP id 87B1F14C2 for ; Thu, 15 Oct 2015 05:17:53 +0000 (UTC) (envelope-from bdrewery@FreeBSD.org) Received: from mail.xzibition.com (localhost [172.31.3.2]) by mail.xzibition.com (Postfix) with ESMTP id 3920EFABE for ; Thu, 15 Oct 2015 05:17:53 +0000 (UTC) X-Virus-Scanned: amavisd-new at mail.xzibition.com Received: from mail.xzibition.com ([172.31.3.2]) by mail.xzibition.com (mail.xzibition.com [172.31.3.2]) (amavisd-new, port 10026) with LMTP id h2UOdSfxvhUI for ; Thu, 15 Oct 2015 05:17:50 +0000 (UTC) Subject: Re: make -n -n DKIM-Filter: OpenDKIM Filter v2.9.2 mail.xzibition.com 40C61FAB8 To: arch@FreeBSD.org References: <561F3406.9050906@FreeBSD.org> From: Bryan Drewery Organization: FreeBSD Message-ID: <561F36FD.2080606@FreeBSD.org> Date: Wed, 14 Oct 2015 22:17:49 -0700 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 In-Reply-To: <561F3406.9050906@FreeBSD.org> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Oct 2015 05:17:53 -0000 On 10/14/15 10:05 PM, Bryan Drewery wrote: > Does anyone consider 'make -n -n' a thing for top-level builds? > ... > > So having said all of that, the ${_+_} never expands anymore since > r251748 (June 2013). The act of it working in top-level has only been > fixed since r288391 (September 2015). r251750 (June 2013) also makes it so buildworld -n causes a real rm -rf to be executed, so I'm guessing no one even uses this since it has not been fixed yet. > > Given it was broken for this long period I assume no one uses '-n -n' or > even knew about it. > > I would like to remove it (-n -n and _+_) and just use the (bmake) > documented -n and -N flags and use '+' everywhere appropriate. Note that > we use .MAKE in some targets that achieves largely the same thing, but > many sub-make calls don't have a .MAKE and lack a proper '+' to recurse > in Makefile.inc1. > -- Regards, Bryan Drewery From owner-freebsd-arch@freebsd.org Thu Oct 15 16:56:56 2015 Return-Path: Delivered-To: freebsd-arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id ACA29A1578C for ; Thu, 15 Oct 2015 16:56:56 +0000 (UTC) (envelope-from s-4vmdzyiikq64m1mrc1np602eqfys2iuxz9hl00lgopp00nguly4sta2g@bounce.linkedin.com) Received: from maila-ab.linkedin.com (maila-ab.linkedin.com [IPv6:2620:109:c006:104::130]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.linkedin.com", Issuer "DigiCert Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 63D031621 for ; Thu, 15 Oct 2015 16:56:56 +0000 (UTC) (envelope-from s-4vmdzyiikq64m1mrc1np602eqfys2iuxz9hl00lgopp00nguly4sta2g@bounce.linkedin.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linkedin.com; s=proddkim1024; t=1444928203; bh=NQC4pycadwpppYmoXlTtuUpZafniBSxg5FOvIWRbEvQ=; h=From:Subject:MIME-Version:Content-Type:To:Date:X-LinkedIn-Class: X-LinkedIn-Template:X-LinkedIn-fbl; b=Ugkb2qbFDhXWiKS0Vvx0upQop2lpIOZeaZDA+ByMF3qNSy1WdvOd95CQO7TurWEYw M0h/NeTnz17TpdGSBvP5KfmBYQfI7qQ0Td9uugdz29UUFk6xtBF0wjbh08JYjpZP3t /8Seq5mpAILkVFPzEUTmD1wFG6wCnelKUlijcDtc= From: LinkedIn Security Message-ID: <1090004798.104340.1444928203264.JavaMail.app@lva1-app3009.prod.linkedin.com> Subject: Sairam, your password was successfully reset MIME-Version: 1.0 To: Sairam Chengala Date: Thu, 15 Oct 2015 16:56:43 +0000 (UTC) X-LinkedIn-Class: ACCT-ADMIN X-LinkedIn-Template: security_reset_password_notification X-LinkedIn-fbl: m2-aszva6rx43tzmzxpwu0ofw5dravm9tub9h7tfl9kq9t4dn4yfl8gaac8idylpl97uykwjjpxkalt0gvkw5tnxbepync8j82vfusmye X-LinkedIn-Id: i9hmy-ifsgy0zv-6d Content-Type: text/plain;charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Oct 2015 16:56:56 -0000 Hi Sairam, You've successfully changed your LinkedIn password. Thanks for using LinkedIn! The LinkedIn Team When and where this happened: Date:October 15, 2015, 12:56 PM Browser:Chrome Mobile Operating System:Android Approximate Location:South Orange, New Jersey, United States Didn't do this? Be sure to change your password right away: https://www.lin= kedin.com/e/v2?e=3Di9hmy-ifsgy0zv-6d&a=3Duas-request-password-reset&midToke= n=3DAQFN2Z6JzeYPdA&ek=3Dsecurity_reset_password_notification This email was intended for Sairam Chengala (Senior Associate (Software Eng= ineer)).=20 Learn why we included this: https://www.linkedin.com/e/v2?e=3Di9hmy-ifsgy0z= v-6d&a=3DcustomerServiceUrl&midToken=3DAQFN2Z6JzeYPdA&ek=3Dsecurity_reset_p= assword_notification&articleId=3D4788 If you need assistance or have questions, please contact LinkedIn Customer = Service: https://www.linkedin.com/e/v2?e=3Di9hmy-ifsgy0zv-6d&a=3DcustomerSe= rviceUrl&midToken=3DAQFN2Z6JzeYPdA&ek=3Dsecurity_reset_password_notificatio= n © 2015 LinkedIn Corporation, 2029 Stierlin Court, Mountain View CA 940= 43. LinkedIn and the LinkedIn logo are registered trademarks of LinkedIn. From owner-freebsd-arch@freebsd.org Sat Oct 17 02:47:44 2015 Return-Path: Delivered-To: freebsd-arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0035CA17A30 for ; Sat, 17 Oct 2015 02:47:44 +0000 (UTC) (envelope-from s-4tw5ft5zjgz9rukke1rwslbf4bdqjcmedhcz86edpm9hz8ml1sqke14h@bounce.linkedin.com) Received: from maila-cf.linkedin.com (maila-cf.linkedin.com [IPv6:2620:109:c003:104::134]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.linkedin.com", Issuer "DigiCert Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id BF569F5E for ; Sat, 17 Oct 2015 02:47:43 +0000 (UTC) (envelope-from s-4tw5ft5zjgz9rukke1rwslbf4bdqjcmedhcz86edpm9hz8ml1sqke14h@bounce.linkedin.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linkedin.com; s=proddkim1024; t=1445050058; bh=6HF1c6ph8Xok/ip4pJZPZavmyuwOKbsGg/EEWn1cfLo=; h=From:Subject:MIME-Version:Content-Type:To:Date:X-LinkedIn-Class: X-LinkedIn-Template:X-LinkedIn-fbl; b=qoc/4rtU+QRqDwlJoONAKn1ZCOCbW0ArPdA7VNMnHD2GXbscuP3k2+JB+A3hGPoJh kteiAbxEeQokyS2sRlnet8QNh+7nD+7LIu2MSgwTGo7/ByGuZ5m5KSB0hiSUMpZvjA FSnrxAllCZ9q+Gw2qpIh6VYZKrO+6gQIXxGxz7CE= From: LinkedIn Security Message-ID: <1517058558.427482.1445050058135.JavaMail.app@lva1-app5679.prod.linkedin.com> Subject: Sairam, here's the link to reset your password MIME-Version: 1.0 To: Sairam Chengala Date: Sat, 17 Oct 2015 02:47:38 +0000 (UTC) X-LinkedIn-Class: ACCT-ADMIN X-LinkedIn-Template: security_password_reset X-LinkedIn-fbl: m2-aszq7vvji5i6hvgy1oafrvv8e75ko1hljjat7z4xawbh5z92mq3gneu9qffjrgg3dkni3gktd5chpximxcnitjcow2myxhmn5pddh6 X-LinkedIn-Id: i9hmy-ifuhhstj-68 Content-Type: text/plain;charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Oct 2015 02:47:44 -0000 Hi Sairam, You recently requested a password reset.=20 To change your LinkedIn password, paste the following link into your browse= r: https://www.linkedin.com/e/rpp/30675850/freebsd-arch%40freebsd%2Eorg/146= 614985600726420/?hs=3Dtrue&tok=3D3pn8OzwYj7vCY1 The link will expire in 24 hours, so be sure to use it right away. Thanks for using LinkedIn! The LinkedIn Team This email was intended for Sairam Chengala (Senior Associate (Software Eng= ineer)).=20 Learn why we included this: https://www.linkedin.com/e/v2?e=3Di9hmy-ifuhhst= j-68&a=3DcustomerServiceUrl&midToken=3DAQFN2Z6JzeYPdA&ek=3Dsecurity_passwor= d_reset&articleId=3D4788 If you need assistance or have questions, please contact LinkedIn Customer = Service: https://www.linkedin.com/e/v2?e=3Di9hmy-ifuhhstj-68&a=3DcustomerSe= rviceUrl&midToken=3DAQFN2Z6JzeYPdA&ek=3Dsecurity_password_reset © 2015 LinkedIn Corporation, 2029 Stierlin Court, Mountain View CA 940= 43. LinkedIn and the LinkedIn logo are registered trademarks of LinkedIn. From owner-freebsd-arch@freebsd.org Sat Oct 17 02:49:53 2015 Return-Path: Delivered-To: freebsd-arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0668EA17AEC for ; Sat, 17 Oct 2015 02:49:53 +0000 (UTC) (envelope-from s-4u6k942dqxh03cfi7hdedizrkee11wnmixd0e3pmdp51i1anryu4f4u1@bounce.linkedin.com) Received: from maila-ba.linkedin.com (maila-ba.linkedin.com [108.174.3.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.linkedin.com", Issuer "DigiCert Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id A02FC1D5 for ; Sat, 17 Oct 2015 02:49:52 +0000 (UTC) (envelope-from s-4u6k942dqxh03cfi7hdedizrkee11wnmixd0e3pmdp51i1anryu4f4u1@bounce.linkedin.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linkedin.com; s=proddkim1024; t=1445050122; bh=oKEEVSzKojY/xwpOPb7bKGWg0CzdQC1aGlsrtUKFlzM=; h=From:Subject:MIME-Version:Content-Type:To:Date:X-LinkedIn-Class: X-LinkedIn-Template:X-LinkedIn-fbl; b=ZBSlVTefrGRTsHSHGLatZXDVM/VRNRCUn98KwEmF6m1HyI4UTC0SfGpxUvjCMXWo4 PcUfeGve9GSI5c2ffh3NMF+XbbtLytCIsLHtiZ3X9yYkn8Ob1QRNi3z5lEUAHH1/m0 UNWnM7m8uiP72RvN49Fc+ZJ3G/O9WNFFYjkTlQyo= From: LinkedIn Security Message-ID: <591667882.390572.1445050122726.JavaMail.app@lva1-app9079.prod.linkedin.com> Subject: Sairam, here's the link to reset your password MIME-Version: 1.0 To: Sairam Chengala Date: Sat, 17 Oct 2015 02:48:42 +0000 (UTC) X-LinkedIn-Class: ACCT-ADMIN X-LinkedIn-Template: security_password_reset X-LinkedIn-fbl: m2-aszylrog9840oeccfx4ag9etwrh31eg1vz7ubrodxg1dek87h57lyto1w6elv82dwc69qfhp3gmqtvagiyg5k5dxmojmrrh894myyi X-LinkedIn-Id: i9hmy-ifuhj6nw-52 Content-Type: text/plain;charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Oct 2015 02:49:53 -0000 Hi Sairam, You recently requested a password reset.=20 To change your LinkedIn password, paste the following link into your browse= r: https://www.linkedin.com/e/rpp/30675850/freebsd-arch%40freebsd%2Eorg/146= 614985600726420/?hs=3Dtrue&tok=3D2i5fkvVCj8vCY1 The link will expire in 24 hours, so be sure to use it right away. Thanks for using LinkedIn! The LinkedIn Team This email was intended for Sairam Chengala (Senior Associate (Software Eng= ineer)).=20 Learn why we included this: https://www.linkedin.com/e/v2?e=3Di9hmy-ifuhj6n= w-52&a=3DcustomerServiceUrl&midToken=3DAQFN2Z6JzeYPdA&ek=3Dsecurity_passwor= d_reset&articleId=3D4788 If you need assistance or have questions, please contact LinkedIn Customer = Service: https://www.linkedin.com/e/v2?e=3Di9hmy-ifuhj6nw-52&a=3DcustomerSe= rviceUrl&midToken=3DAQFN2Z6JzeYPdA&ek=3Dsecurity_password_reset © 2015 LinkedIn Corporation, 2029 Stierlin Court, Mountain View CA 940= 43. LinkedIn and the LinkedIn logo are registered trademarks of LinkedIn. From owner-freebsd-arch@freebsd.org Sat Oct 17 02:58:41 2015 Return-Path: Delivered-To: freebsd-arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3F4FCA17D40 for ; Sat, 17 Oct 2015 02:58:41 +0000 (UTC) (envelope-from s-4vln2rcszxzfskqep3go49wqyarlghnx04n02ur7xq6gcu4qzbomna5t@bounce.linkedin.com) Received: from maila-dd.linkedin.com (maila-dd.linkedin.com [108.174.6.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.linkedin.com", Issuer "DigiCert Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 056C28D8 for ; Sat, 17 Oct 2015 02:58:40 +0000 (UTC) (envelope-from s-4vln2rcszxzfskqep3go49wqyarlghnx04n02ur7xq6gcu4qzbomna5t@bounce.linkedin.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linkedin.com; s=proddkim1024; t=1445050653; bh=VbsiffdWztXRPOJciEUvBCmXVfmhYyRS1LG/qmaLbmA=; h=From:Subject:MIME-Version:Content-Type:To:Date:X-LinkedIn-Class: X-LinkedIn-Template:X-LinkedIn-fbl; b=CA8HXfiFnXaWXAMl85a939BGJgT7ujX9mz/IRtn32BUOOKc8E7n4kiCSXzUzkwsf8 OIUidbGEXCBkaq7IXuCRZsYYHlwTb3oZxzAEXaGCtTzobWvWvz2/ycMNNz7mTXAAdI 2Svj6shJC3PGqlJmax6kGx6qBIDLmqh+K/ehzrpw= From: LinkedIn Security Message-ID: <1304255551.224178.1445050653184.JavaMail.app@ela4-app8097.prod.linkedin.com> Subject: Sairam, your password was successfully reset MIME-Version: 1.0 To: Sairam Chengala Date: Sat, 17 Oct 2015 02:57:33 +0000 (UTC) X-LinkedIn-Class: ACCT-ADMIN X-LinkedIn-Template: security_reset_password_notification X-LinkedIn-fbl: m2-aszpkja85zmh8qsegyagp91fxronlv00111nxoo1h1rto51nccksqf4d8c0ahhnzzrl8llatu4h3l34v1iaqxnhbpyxe9o78jc39yu X-LinkedIn-Id: i9hmy-ifuhujv6-4a Content-Type: text/plain;charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Oct 2015 02:58:41 -0000 Hi Sairam, You've successfully changed your LinkedIn password. Thanks for using LinkedIn! The LinkedIn Team When and where this happened: Date:October 17, 2015, 2:57 AM (GMT) Browser:Firefox Operating System:OS X Approximate Location:United States Didn't do this? Be sure to change your password right away: https://www.lin= kedin.com/e/v2?e=3Di9hmy-ifuhujv6-4a&a=3Duas-request-password-reset&midToke= n=3DAQFN2Z6JzeYPdA&ek=3Dsecurity_reset_password_notification This email was intended for Sairam Chengala (Senior Associate (Software Eng= ineer)).=20 Learn why we included this: https://www.linkedin.com/e/v2?e=3Di9hmy-ifuhujv= 6-4a&a=3DcustomerServiceUrl&midToken=3DAQFN2Z6JzeYPdA&ek=3Dsecurity_reset_p= assword_notification&articleId=3D4788 If you need assistance or have questions, please contact LinkedIn Customer = Service: https://www.linkedin.com/e/v2?e=3Di9hmy-ifuhujv6-4a&a=3DcustomerSe= rviceUrl&midToken=3DAQFN2Z6JzeYPdA&ek=3Dsecurity_reset_password_notificatio= n © 2015 LinkedIn Corporation, 2029 Stierlin Court, Mountain View CA 940= 43. LinkedIn and the LinkedIn logo are registered trademarks of LinkedIn. From owner-freebsd-arch@freebsd.org Sat Oct 17 16:27:23 2015 Return-Path: Delivered-To: freebsd-arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 95052A17F87 for ; Sat, 17 Oct 2015 16:27:23 +0000 (UTC) (envelope-from johnandsara2@cox.net) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 7ADB521B for ; Sat, 17 Oct 2015 16:27:23 +0000 (UTC) (envelope-from johnandsara2@cox.net) Received: by mailman.ysv.freebsd.org (Postfix) id 7AD5AA17F86; Sat, 17 Oct 2015 16:27:23 +0000 (UTC) Delivered-To: arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 7A6CEA17F85 for ; Sat, 17 Oct 2015 16:27:23 +0000 (UTC) (envelope-from johnandsara2@cox.net) Received: from fed1rmfepi106.cox.net (fed1rmfepi106.cox.net [68.230.241.137]) by mx1.freebsd.org (Postfix) with ESMTP id 5725521A for ; Sat, 17 Oct 2015 16:27:23 +0000 (UTC) (envelope-from johnandsara2@cox.net) Received: from eastrmimpo305 ([68.230.241.237]) by eastrmfepo103.cox.net (InterMail vM.8.01.05.15 201-2260-151-145-20131218) with ESMTP id <20151017153759.SXPO28770.eastrmfepo103.cox.net@eastrmimpo305> for ; Sat, 17 Oct 2015 11:37:59 -0400 Received: from [192.168.3.15] ([72.219.204.96]) by eastrmimpo305 with cox id WFdy1r00H25Jhjc01FdyHD; Sat, 17 Oct 2015 11:37:58 -0400 X-CT-Class: Clean X-CT-Score: 0.00 X-CT-RefID: str=0001.0A020201.56226B56.0145,ss=1,re=0.000,fgs=0 X-CT-Spam: 0 X-Authority-Analysis: v=2.0 cv=KuOTLxqN c=1 sm=1 a=OPrADkie5Htls158/1P3IQ==:17 a=kviXuzpPAAAA:8 a=5_aGdUW4pVRo2noaqvIA:9 a=wPNLvfGTeEIA:10 a=OPrADkie5Htls158/1P3IQ==:117 X-CM-Score: 0.00 Authentication-Results: cox.net; none Message-ID: <56226911.9050406@cox.net> Date: Sat, 17 Oct 2015 11:28:17 -0400 From: "John D. Hendrickson" User-Agent: Thunderbird 2.0.0.24 (X11/20100228) MIME-Version: 1.0 To: Bryan Drewery CC: arch@FreeBSD.org Subject: Re: make -n -n References: <561F3406.9050906@FreeBSD.org> <561F36FD.2080606@FreeBSD.org> In-Reply-To: <561F36FD.2080606@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Oct 2015 16:27:23 -0000 Bryan Drewery wrote: > On 10/14/15 10:05 PM, Bryan Drewery wrote: >> Does anyone consider 'make -n -n' a thing for top-level builds? >> > ... >> So having said all of that, the ${_+_} never expands anymore since >> r251748 (June 2013). The act of it working in top-level has only been >> fixed since r288391 (September 2015). > > r251750 (June 2013) also makes it so buildworld -n causes a real rm -rf > to be executed, so I'm guessing no one even uses this since it has not > been fixed yet. > >> Given it was broken for this long period I assume no one uses '-n -n' or >> even knew about it. >> >> I would like to remove it (-n -n and _+_) and just use the (bmake) >> documented -n and -N flags and use '+' everywhere appropriate. Note that >> we use .MAKE in some targets that achieves largely the same thing, but >> many sub-make calls don't have a .MAKE and lack a proper '+' to recurse >> in Makefile.inc1. >> > > -n Display the commands that would have been executed, but do not actually execute them. i dont see the point of the question "is for top of world" because -n necessarily does "nothing" however pmake(1) is one of these "wares" that continually becomes incompatible with itself forward and backward ... you should say what version of pmake (or freebsd) you are using if you wish proper usage advice. on the other hand one nice thing about freebsd is proper usage for a given "release" is supposedly already provided - which works only for that given release (maybe) From owner-freebsd-arch@freebsd.org Sat Oct 17 16:27:24 2015 Return-Path: Delivered-To: freebsd-arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BDF35A17F8C for ; Sat, 17 Oct 2015 16:27:24 +0000 (UTC) (envelope-from johnandsara2@cox.net) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id A3FE4221 for ; Sat, 17 Oct 2015 16:27:24 +0000 (UTC) (envelope-from johnandsara2@cox.net) Received: by mailman.ysv.freebsd.org (Postfix) id A3FDCA17F8B; Sat, 17 Oct 2015 16:27:24 +0000 (UTC) Delivered-To: arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id A39ECA17F8A for ; Sat, 17 Oct 2015 16:27:24 +0000 (UTC) (envelope-from johnandsara2@cox.net) Received: from fed1rmfepi106.cox.net (fed1rmfepi106.cox.net [68.230.241.137]) by mx1.freebsd.org (Postfix) with ESMTP id 80A8E220 for ; Sat, 17 Oct 2015 16:27:24 +0000 (UTC) (envelope-from johnandsara2@cox.net) Received: from eastrmimpo110 ([68.230.241.223]) by eastrmfepo202.cox.net (InterMail vM.8.01.05.15 201-2260-151-145-20131218) with ESMTP id <20151017153914.LNCB16920.eastrmfepo202.cox.net@eastrmimpo110> for ; Sat, 17 Oct 2015 11:39:14 -0400 Received: from [192.168.3.15] ([72.219.204.96]) by eastrmimpo110 with cox id WFfE1r00325Jhjc01FfE8o; Sat, 17 Oct 2015 11:39:14 -0400 X-CT-Class: Clean X-CT-Score: 0.00 X-CT-RefID: str=0001.0A020205.56226BA2.00A0,ss=1,re=0.000,fgs=0 X-CT-Spam: 0 X-Authority-Analysis: v=2.0 cv=FaLpMuC6 c=1 sm=1 a=OPrADkie5Htls158/1P3IQ==:17 a=kviXuzpPAAAA:8 a=jE9PVPMpqX5-yLpioWUA:9 a=wPNLvfGTeEIA:10 a=OPrADkie5Htls158/1P3IQ==:117 X-CM-Score: 0.00 Authentication-Results: cox.net; none Message-ID: <5622695D.6040700@cox.net> Date: Sat, 17 Oct 2015 11:29:33 -0400 From: "John D. Hendrickson" User-Agent: Thunderbird 2.0.0.24 (X11/20100228) MIME-Version: 1.0 To: Bryan Drewery CC: arch@FreeBSD.org Subject: Re: make -n -n References: <561F3406.9050906@FreeBSD.org> In-Reply-To: <561F3406.9050906@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Oct 2015 16:27:24 -0000 Bryan Drewery wrote: > Does anyone consider 'make -n -n' a thing for top-level builds? > > We have this ${_+_} thing in Makefiles that used to expand to '+' if you > gave '-n -n'. This was so just 1 '-n' would just show what the > top-level Makefile would do: > > ~/svn/clean2 # make -n includes > cd /root/svn/clean2; PATH=/sbin:/bin:/usr/sbin:/usr/bin make -m > /root/svn/clean2/share/mk -f Makefile.inc1 TARGET=amd64 > TARGET_ARCH=amd64 includes > > Versus the more expected (at least for bmake) -n behavior of traversing > sub-makes: > > ~/svn/clean2 # make -n -n includes > ===> lib (includes) > ===> lib/csu (includes) > ===> lib/csu/amd64 (includes) > ===> lib/libcompiler_rt (includes) > ===> lib/libc (includes) > ===> lib/libc/tests (includes) > ===> lib/libc/tests/tls_dso (includes) > ===> lib/libc/tests/c063 (includes) > etc... > > Note the actual output may be off due to local changes, but the point is > that -n with bmake is documented to run sub-makes with -n as well, so it > calls right down the chain showing all build commands without taking any > real actions. > > Bmake added a '-N' flag that essentially does the hack that we've put > into our top-level Makefile - it doesn't run sub-makes. > > > So having said all of that, the ${_+_} never expands anymore since > r251748 (June 2013). The act of it working in top-level has only been > fixed since r288391 (September 2015). > > Given it was broken for this long period I assume no one uses '-n -n' or > even knew about it. > > I would like to remove it (-n -n and _+_) and just use the (bmake) > documented -n and -N flags and use '+' everywhere appropriate. Note that > we use .MAKE in some targets that achieves largely the same thing, but > many sub-make calls don't have a .MAKE and lack a proper '+' to recurse > in Makefile.inc1. > if you take a Makefile for older pmake and run it with newer - there is no telling what might happen (unless of course it's already been tried) no telling From owner-freebsd-arch@freebsd.org Sat Oct 17 16:40:40 2015 Return-Path: Delivered-To: freebsd-arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 461B5A171A4 for ; Sat, 17 Oct 2015 16:40:40 +0000 (UTC) (envelope-from bdrewery@FreeBSD.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 2838BAF2 for ; Sat, 17 Oct 2015 16:40:40 +0000 (UTC) (envelope-from bdrewery@FreeBSD.org) Received: by mailman.ysv.freebsd.org (Postfix) id 261FDA171A2; Sat, 17 Oct 2015 16:40:40 +0000 (UTC) Delivered-To: arch@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 0AD64A171A0 for ; Sat, 17 Oct 2015 16:40:40 +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 D9787AF1; Sat, 17 Oct 2015 16:40:39 +0000 (UTC) (envelope-from bdrewery@FreeBSD.org) Received: from mail.xzibition.com (localhost [IPv6:::1]) by freefall.freebsd.org (Postfix) with ESMTP id D2FDF1985; Sat, 17 Oct 2015 16:40:39 +0000 (UTC) (envelope-from bdrewery@FreeBSD.org) Received: from mail.xzibition.com (localhost [172.31.3.2]) by mail.xzibition.com (Postfix) with ESMTP id 90A6514F50; Sat, 17 Oct 2015 16:40:39 +0000 (UTC) X-Virus-Scanned: amavisd-new at mail.xzibition.com Received: from mail.xzibition.com ([172.31.3.2]) by mail.xzibition.com (mail.xzibition.com [172.31.3.2]) (amavisd-new, port 10026) with LMTP id V-Llb-DxS_D6; Sat, 17 Oct 2015 16:40:32 +0000 (UTC) Subject: Re: make -n -n DKIM-Filter: OpenDKIM Filter v2.9.2 mail.xzibition.com 82ECD14F48 To: "John D. Hendrickson" References: <561F3406.9050906@FreeBSD.org> <5622695D.6040700@cox.net> Cc: arch@FreeBSD.org From: Bryan Drewery Openpgp: id=F9173CB2C3AAEA7A5C8A1F0935D771BB6E4697CF; url=http://www.shatow.net/bryan/bryan2.asc Organization: FreeBSD Message-ID: <562279FF.1020603@FreeBSD.org> Date: Sat, 17 Oct 2015 09:40:31 -0700 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 In-Reply-To: <5622695D.6040700@cox.net> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="xtvFmFE5cPGrUOAh5G1SWb5bXjjTKnSGJ" X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Oct 2015 16:40:40 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --xtvFmFE5cPGrUOAh5G1SWb5bXjjTKnSGJ Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 10/17/2015 8:29 AM, John D. Hendrickson wrote: > Bryan Drewery wrote: >> Does anyone consider 'make -n -n' a thing for top-level builds? >> >> We have this ${_+_} thing in Makefiles that used to expand to '+' if y= ou >> gave '-n -n'. This was so just 1 '-n' would just show what the >> top-level Makefile would do: >> >> ~/svn/clean2 # make -n includes >> cd /root/svn/clean2; PATH=3D/sbin:/bin:/usr/sbin:/usr/bin make -m >> /root/svn/clean2/share/mk -f Makefile.inc1 TARGET=3Damd64 >> TARGET_ARCH=3Damd64 includes >> >> Versus the more expected (at least for bmake) -n behavior of traversin= g >> sub-makes: >> >> ~/svn/clean2 # make -n -n includes >> =3D=3D=3D> lib (includes) >> =3D=3D=3D> lib/csu (includes) >> =3D=3D=3D> lib/csu/amd64 (includes) >> =3D=3D=3D> lib/libcompiler_rt (includes) >> =3D=3D=3D> lib/libc (includes) >> =3D=3D=3D> lib/libc/tests (includes) >> =3D=3D=3D> lib/libc/tests/tls_dso (includes) >> =3D=3D=3D> lib/libc/tests/c063 (includes) >> etc... >> >> Note the actual output may be off due to local changes, but the point = is >> that -n with bmake is documented to run sub-makes with -n as well, so = it >> calls right down the chain showing all build commands without taking a= ny >> real actions. >> >> Bmake added a '-N' flag that essentially does the hack that we've put >> into our top-level Makefile - it doesn't run sub-makes. >> >> >> So having said all of that, the ${_+_} never expands anymore since >> r251748 (June 2013). The act of it working in top-level has only been >> fixed since r288391 (September 2015). >> >> Given it was broken for this long period I assume no one uses '-n -n' = or >> even knew about it. >> >> I would like to remove it (-n -n and _+_) and just use the (bmake) >> documented -n and -N flags and use '+' everywhere appropriate. Note th= at >> we use .MAKE in some targets that achieves largely the same thing, but= >> many sub-make calls don't have a .MAKE and lack a proper '+' to recurs= e >> in Makefile.inc1. >> >=20 > if you take a Makefile for older pmake and run it with newer - there is= > no telling what might happen (unless of course it's already been tried)= >=20 > no telling >=20 I'm talking about head, where only bmake is supported. Either way, the '-n -n' feature was not documented anywhere that I can find. I am making the change here to desupport '-n -n' and make '-n' and '-N' behave as documented in the bmake manpage. --=20 Regards, Bryan Drewery --xtvFmFE5cPGrUOAh5G1SWb5bXjjTKnSGJ Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBAgAGBQJWInn/AAoJEDXXcbtuRpfPtroIAISIWhmACPrUQwtnCnhEci5K BJUS/Kt3mUg0vQAwpRf/eVKNlLzW2WS72Hq6z76UTRcBuWCYyyTNqRch4Imzp+z3 BsS7bsmLamP167at9oSkjRlDkx1uNQ6mod7VG7dlAZsqfGRkGJqIZgBFkQKx4IVu mp1DMUzXhYIupMOLCHPofbjBG7EwXiAp355LQDCxzXbPpSv3uKviTzknlakkmpbo 7V7Om+X9CDOVM81eMyT/hMOpweRl/nOtFtaxaYwzFGq9WBGkYL0DthmS0dJgZidm IDY2vl+mjdNrLyvRmd7pUe7Afv4++4eIxeTPKzgbqTmmHKD3VEwjzK7F3XZr5UU= =zd6F -----END PGP SIGNATURE----- --xtvFmFE5cPGrUOAh5G1SWb5bXjjTKnSGJ--