From owner-freebsd-current@FreeBSD.ORG Sun Aug 19 07:22:30 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4C23E106564A for ; Sun, 19 Aug 2012 07:22:30 +0000 (UTC) (envelope-from bjwela@gmail.com) Received: from mail-lb0-f182.google.com (mail-lb0-f182.google.com [209.85.217.182]) by mx1.freebsd.org (Postfix) with ESMTP id C2DFC8FC0A for ; Sun, 19 Aug 2012 07:22:29 +0000 (UTC) Received: by lbbgk8 with SMTP id gk8so3534744lbb.13 for ; Sun, 19 Aug 2012 00:22:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=8QbYO2u8rAhkabllJwafCZTW/ej1jdXSN/BMfEosgPg=; b=tIoxySatKAbFmYd6gexypwBWUScAdRwmCuU8KVlMsV/CB8sE7t/AMHBX106ykXvcdT UipLjQxqRJZShm26asYn4Zr7hnNGIKcYopwfvohPdH1q8CGxyOZHbmwW81R8e5CWTOTO j0XZ4QevIMLbSjigLrQIgTZmEBF5pRFGzzYKv4hdNUJvLS/HsZCfrkV9hHJ1KXdl3GEv txVgdP1KPp6K5YSnIz4sSzY0g3SyTTzh5C7F/Tmn+5IGFYPSg5CVkzcq9SeN5xqWVp59 HpuNhAOVctBYPG0f6AmiGc17v13zh3X99X5w9YdxtVaKmEnId7a2NYUmWaw4uppKBmRq CgWw== MIME-Version: 1.0 Received: by 10.112.48.103 with SMTP id k7mr4425745lbn.88.1345360948317; Sun, 19 Aug 2012 00:22:28 -0700 (PDT) Received: by 10.114.14.168 with HTTP; Sun, 19 Aug 2012 00:22:28 -0700 (PDT) Date: Sun, 19 Aug 2012 09:22:28 +0200 Message-ID: From: Bjorn Larsson To: freebsd-current@freebsd.org Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: gptzfsboot problem on HP P410i Smart Array X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 19 Aug 2012 07:22:30 -0000 Dear We are having problems with gptzfsboot on a HP DL360 G7 using the P410i Smart Array Controller. I=92ve some information on this in the archive on this mailing list that th= is has supposedly been fixed with revision 227400, by implementing the edd data structure. However we still see the same problem and by adding a printf() in zfsboot.c fixes the problem. Please, let me know if anyone have seen this problem and if there is a fix for it? Best regards, Bj=F6rn Larsson From owner-freebsd-current@FreeBSD.ORG Sun Aug 19 14:00:44 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 571BF106566B for ; Sun, 19 Aug 2012 14:00:44 +0000 (UTC) (envelope-from randy@psg.com) Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by mx1.freebsd.org (Postfix) with ESMTP id 33C388FC12 for ; Sun, 19 Aug 2012 14:00:43 +0000 (UTC) Received: from localhost ([127.0.0.1] helo=rair.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.80 (FreeBSD)) (envelope-from ) id 1T363V-000Jmy-Ck for freebsd-current@freebsd.org; Sun, 19 Aug 2012 14:00:41 +0000 Date: Sun, 19 Aug 2012 23:01:01 +0900 Message-ID: From: Randy Bush To: FreeBSD Current User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.7 - "Harue") Content-Type: text/plain; charset=US-ASCII Subject: buildworld c++ internal error X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 19 Aug 2012 14:00:44 -0000 soekris 5501, been running fbsd since 6.x csup Aug 18 22:38 gmt rm -rf /usr/obj buildworld c++ -O2 -pipe -DIPFIREWALL_NAT -march=pentium -I/usr/src/lib/clang/libllvmcore/../../../contrib/llvm/include -I/usr/src/lib/clang/libllvmcore/../../../contrib/llvm/tools/clang/include -I/usr/src/lib/clang/libllvmcore/../../../contrib/llvm/lib/VMCore -I. -I/usr/src/lib/clang/libllvmcore/../../../contrib/llvm/../../lib/clang/include -DLLVM_ON_UNIX -DLLVM_ON_FREEBSD -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS -DLLVM_DEFAULT_TARGET_TRIPLE=\"i386-unknown-freebsd9.0\" -DDEFAULT_SYSROOT=\"\" -fstack-protector -fno-exceptions -c /usr/src/lib/clang/libllvmcore/../../../contrib/llvm/lib/VMCore/Function.cpp -o Function.o {standard input}: Assembler messages: {standard input}:36465: Warning: end of file not at end of a line; newline inserted {standard input}:36631: Error: unknown pseudo-op: `.lc798' c++: Internal error: Killed: 9 (program cc1plus) Please submit a full bug report. See for instructions. *** Error code 1 Stop in /usr/src/lib/clang/libllvmcore. # cat /etc/make.conf KERNCONF=SOEK0 CPUTYPE?=i586 CFLAGS+= -DIPFIREWALL_NAT MAKE_IDEA=YES WITHOUT_X11=yes USA_RESIDENT=YES # cat /etc/src.conf WITHOUT_ATM=yes WITHOUT_BIND=yes WITHOUT_BLUETOOTH=yes WITHOUT_FLOPPY=yes WITHOUT_GAMES=yes WITHOUT_GPIB=YES WITHOUT_I4B=YES WITH_IDEA=yes WITHOUT_IPFILTER=yes WITHOUT_IPX=yes WITHOUT_KERBEROS=yes WITHOUT_LPR=yes WITHOUT_OBJC=yes WITHOUT_PF=YES WITHOUT_PROFILE=yes WITHOUT_SENDMAIL=yes WITHOUT_USB=yes From owner-freebsd-current@FreeBSD.ORG Sun Aug 19 14:31:41 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C0A8C106564A for ; Sun, 19 Aug 2012 14:31:41 +0000 (UTC) (envelope-from rysto32@gmail.com) Received: from mail-vc0-f182.google.com (mail-vc0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id 733038FC08 for ; Sun, 19 Aug 2012 14:31:41 +0000 (UTC) Received: by vcbgb22 with SMTP id gb22so5537289vcb.13 for ; Sun, 19 Aug 2012 07:31:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=5r5xFyXaBDZGabzNt+fxAm7vGqwrHR2E1HbpH6j+Adw=; b=OemMTq8QcPwG/+QKrcZ2iMOP0ZVvBx2DnSFyCHE54tou+EsM/zINBuc0PhHe3e1rEL wwYAR/dq7i8MFHzpu2/WIDwfoHu+jQhWxdwsn0KLzrtugo+oMCwIfe87LaDk0KPCfTTZ VYDORDkYw31U58CO+AzM0uyEHovdfLf+etfYmwluDeMaJ/5UGlPLjNHSq5eKzZCKCIQi TZGoYxTslH+sPwSlj5MwlwtioOaIZ1D7OlMw8yFZyyZoSYGjpm2yL0GknfUmovyNF/SC BLlXUb6JiCZ57nQ+MZqXNnrt0wRtfkjkszMsiZ9Nm49mgpboCi7fleAU+P2m0+aQNo6H XMmw== MIME-Version: 1.0 Received: by 10.52.67.7 with SMTP id j7mr6567336vdt.91.1345386700385; Sun, 19 Aug 2012 07:31:40 -0700 (PDT) Received: by 10.58.207.114 with HTTP; Sun, 19 Aug 2012 07:31:40 -0700 (PDT) Received: by 10.58.207.114 with HTTP; Sun, 19 Aug 2012 07:31:40 -0700 (PDT) In-Reply-To: References: Date: Sun, 19 Aug 2012 10:31:40 -0400 Message-ID: From: Ryan Stone To: Randy Bush Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: FreeBSD Current Subject: Re: buildworld c++ internal error X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 19 Aug 2012 14:31:41 -0000 Is the system running out of memory? A message will go to dmesg if so. On Aug 19, 2012 10:01 AM, "Randy Bush" wrote: > soekris 5501, been running fbsd since 6.x > csup Aug 18 22:38 gmt > rm -rf /usr/obj > buildworld > > c++ -O2 -pipe -DIPFIREWALL_NAT -march=pentium > -I/usr/src/lib/clang/libllvmcore/../../../contrib/llvm/include > -I/usr/src/lib/clang/libllvmcore/../../../contrib/llvm/tools/clang/include > -I/usr/src/lib/clang/libllvmcore/../../../contrib/llvm/lib/VMCore -I. > -I/usr/src/lib/clang/libllvmcore/../../../contrib/llvm/../../lib/clang/include > -DLLVM_ON_UNIX -DLLVM_ON_FREEBSD -D__STDC_LIMIT_MACROS > -D__STDC_CONSTANT_MACROS > -DLLVM_DEFAULT_TARGET_TRIPLE=\"i386-unknown-freebsd9.0\" > -DDEFAULT_SYSROOT=\"\" -fstack-protector -fno-exceptions -c > /usr/src/lib/clang/libllvmcore/../../../contrib/llvm/lib/VMCore/Function.cpp > -o Function.o > {standard input}: Assembler messages: > {standard input}:36465: Warning: end of file not at end of a line; newline > inserted > {standard input}:36631: Error: unknown pseudo-op: `.lc798' > c++: Internal error: Killed: 9 (program cc1plus) > Please submit a full bug report. > See for instructions. > *** Error code 1 > > Stop in /usr/src/lib/clang/libllvmcore. > > # cat /etc/make.conf > KERNCONF=SOEK0 > CPUTYPE?=i586 > CFLAGS+= -DIPFIREWALL_NAT > MAKE_IDEA=YES > WITHOUT_X11=yes > USA_RESIDENT=YES > > # cat /etc/src.conf > WITHOUT_ATM=yes > WITHOUT_BIND=yes > WITHOUT_BLUETOOTH=yes > WITHOUT_FLOPPY=yes > WITHOUT_GAMES=yes > WITHOUT_GPIB=YES > WITHOUT_I4B=YES > WITH_IDEA=yes > WITHOUT_IPFILTER=yes > WITHOUT_IPX=yes > WITHOUT_KERBEROS=yes > WITHOUT_LPR=yes > WITHOUT_OBJC=yes > WITHOUT_PF=YES > WITHOUT_PROFILE=yes > WITHOUT_SENDMAIL=yes > WITHOUT_USB=yes > _______________________________________________ > 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 Sun Aug 19 14:39:01 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B564C106566B for ; Sun, 19 Aug 2012 14:39:01 +0000 (UTC) (envelope-from randy@psg.com) Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by mx1.freebsd.org (Postfix) with ESMTP id 992E58FC08 for ; Sun, 19 Aug 2012 14:39:01 +0000 (UTC) Received: from localhost ([127.0.0.1] helo=rair.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.80 (FreeBSD)) (envelope-from ) id 1T36ea-000JtB-K3; Sun, 19 Aug 2012 14:39:00 +0000 Date: Sun, 19 Aug 2012 23:39:20 +0900 Message-ID: From: Randy Bush To: Ryan Stone In-Reply-To: References: User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.7 - "Harue") Content-Type: text/plain; charset=US-ASCII Cc: FreeBSD Current Subject: Re: buildworld c++ internal error X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 19 Aug 2012 14:39:01 -0000 > Is the system running out of memory? A message will go to dmesg if so. bingo! thank you. pid 73951 (cc1plus), uid 0, was killed: out of swap space as this is a 8g cd card machine, i may have a problem. it's not as if i can boot a cd rom and run shrinkfs randy From owner-freebsd-current@FreeBSD.ORG Sun Aug 19 16:32:06 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7BA96106566C for ; Sun, 19 Aug 2012 16:32:06 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe09.c2i.net [212.247.155.2]) by mx1.freebsd.org (Postfix) with ESMTP id 06FB98FC0A for ; Sun, 19 Aug 2012 16:32:05 +0000 (UTC) X-T2-Spam-Status: No, hits=-0.2 required=5.0 tests=ALL_TRUSTED, BAYES_50 Received: from [176.74.212.201] (account mc467741@c2i.net HELO laptop015.hselasky.homeunix.org) by mailfe09.swip.net (CommuniGate Pro SMTP 5.4.4) with ESMTPA id 135029756; Sun, 19 Aug 2012 18:31:56 +0200 From: Hans Petter Selasky To: Andrew Turner , freebsd-current@freebsd.org Date: Sun, 19 Aug 2012 18:32:39 +0200 User-Agent: KMail/1.13.7 (FreeBSD/9.1-PRERELEASE; KDE/4.8.4; amd64; ; ) References: <20120819202622.6db6a8dd@fubar.geek.nz> In-Reply-To: X-Face: 'mmZ:T{)),Oru^0c+/}w'`gU1$ubmG?lp!=R4Wy\ELYo2)@'UZ24N@ =?iso-8859-1?q?d2+AyewRX=7DmAm=3BYp=0A=09=7CU=5B?=@, _z/([?1bCfM{_"B<.J>mICJCHAzzGHI{y7{%JVz%R~yJHIji`y> =?iso-8859-1?q?Y=7Dk1C4TfysrsUI=0A=09-=25GU9V5=5DiUZF=26nRn9mJ=27=3F=26?=>O MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Message-Id: <201208191832.39569.hselasky@c2i.net> Cc: Subject: Recent changes in AT91 kernel code causes USB to not work [WAS: r239214 - in head/sys: dev/usb dev/usb/controller sys] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 19 Aug 2012 16:32:06 -0000 Hi, I'm trying to reproduce using "src/sys/KB920X arm". So far the platform doesn't boot, because recent commits removed one ore more of these clocks: sc->sc_iclk = at91_pmc_clock_ref("udc_clk"); sc->sc_fclk = at91_pmc_clock_ref("udpck"); So I get a crash at a NULL pointer when trying to access one of these clocks. How to fix this? I simply added a NULL check. Now the platform hangs when setting up the OHCI: sys/dev/usb/controller/ohci_atmelarm.c + printf("CLOCK ON\n"); at91_pmc_clock_enable(sc->iclk); at91_pmc_clock_enable(sc->fclk); bus_space_write_4(sc->sc_ohci.sc_io_tag, sc->sc_ohci.sc_io_hdl, OHCI_CONTROL, 0); + printf("INIT\n"); I see the clock ON printout, and then nothing more! Not sure if this is caused by IRQ's hanging or not. Andrew Turner: Can you fix these issues so that I can reproduce? --HPS From owner-freebsd-current@FreeBSD.ORG Sun Aug 19 16:41:42 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 06077106566C for ; Sun, 19 Aug 2012 16:41:42 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from forward5h.mail.yandex.net (forward5h.mail.yandex.net [IPv6:2a02:6b8:0:f05::5]) by mx1.freebsd.org (Postfix) with ESMTP id 6C65A8FC08 for ; Sun, 19 Aug 2012 16:41:41 +0000 (UTC) Received: from smtp1h.mail.yandex.net (smtp1h.mail.yandex.net [84.201.187.144]) by forward5h.mail.yandex.net (Yandex) with ESMTP id 05896D01CA6; Sun, 19 Aug 2012 20:41:39 +0400 (MSK) Received: from smtp1h.mail.yandex.net (localhost [127.0.0.1]) by smtp1h.mail.yandex.net (Yandex) with ESMTP id C2CAB134014C; Sun, 19 Aug 2012 20:41:39 +0400 (MSK) Received: from dynamic-178-141-5-132.kirov.comstar-r.ru (dynamic-178-141-5-132.kirov.comstar-r.ru [178.141.5.132]) by smtp1h.mail.yandex.net (nwsmtp/Yandex) with ESMTP id fdR870Ye-fdRC2hdA; Sun, 19 Aug 2012 20:41:39 +0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1345394499; bh=jkcb9P8aifvPyQv8/ypriWkDCc39JSkDg3QgwfNfyls=; h=Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject: References:In-Reply-To:X-Enigmail-Version:Content-Type; b=ZTtc1WBQblDkxWa4+rls/kvMsZ00GwAUfVFBoD8nLYv/y3dX7Sh7uxMOaZtcDoh3u 3CVQXP89Z3Ibvm7ZqGYIRn17hnK5gHc5203zpsq2iZfrBnJDtD22GgheaOUplEQnBj L1Ggal3kSZsRcLq9rSpMVXXO3pH5vrtSEtVBCbQQ= Message-ID: <50311741.3000204@yandex.ru> Date: Sun, 19 Aug 2012 20:41:37 +0400 From: "Andrey V. Elsukov" User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:10.0.3) Gecko/20120406 Thunderbird/10.0.3 MIME-Version: 1.0 To: Bjorn Larsson References: In-Reply-To: X-Enigmail-Version: 1.4 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig7C16E76F6234FC4AA125E4F8" Cc: freebsd-current@freebsd.org Subject: Re: gptzfsboot problem on HP P410i Smart Array X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 19 Aug 2012 16:41:42 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig7C16E76F6234FC4AA125E4F8 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 19.08.2012 11:22, Bjorn Larsson wrote: > We are having problems with gptzfsboot on a HP DL360 G7 using the P410i= > Smart Array Controller. > I=E2=80=99ve some information on this in the archive on this mailing li= st that this > has supposedly been fixed with revision 227400, by implementing the edd= > data structure. > However we still see the same problem and by adding a printf() in zfsbo= ot.c > fixes the problem. > Please, let me know if anyone have seen this problem and if there is a = fix > for it? Hi, what exactly do you have? --=20 WBR, Andrey V. Elsukov --------------enig7C16E76F6234FC4AA125E4F8 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.0.19 (FreeBSD) iQEcBAEBAgAGBQJQMRdBAAoJEAHF6gQQyKF678MH/0jiAyG5GR07WralzrbMA7TE wKavaQoRrhPEgqayNx9TQYJtn7PgL0kqa8W40vqCE3uDrQOv2179I1vTGUCSzjpK yhNugahnusyQVEOpHVme5YE3Wq8a5NLQbTAjYgNKKKY1GEDmTy0VtEoA2OHuUzFE qO/OCv9oEDFZRcMOWsc+gR9xmRHGszUY3tvFT1QX3HgaXGWWgbDf8cYRI2xCavA3 TtESL3ZMOjv8pPFI+7AMAyJq0gArVxwQ8M5CixvEHvFB6ZkxUHjnqmFPFAdBV0bg 66RphuiFAps7v2nR70+L5HQzKrb2Fc0uPlMGq+92li4qLVHb3Qp0geNHFyGDr+k= =RMXb -----END PGP SIGNATURE----- --------------enig7C16E76F6234FC4AA125E4F8-- From owner-freebsd-current@FreeBSD.ORG Sun Aug 19 16:45:08 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id DE7D4106564A for ; Sun, 19 Aug 2012 16:45:07 +0000 (UTC) (envelope-from tim@kientzle.com) Received: from monday.kientzle.com (99-115-135-74.uvs.sntcca.sbcglobal.net [99.115.135.74]) by mx1.freebsd.org (Postfix) with ESMTP id B96CE8FC1A for ; Sun, 19 Aug 2012 16:45:07 +0000 (UTC) Received: (from root@localhost) by monday.kientzle.com (8.14.4/8.14.4) id q7JGj6uq044987; Sun, 19 Aug 2012 16:45:06 GMT (envelope-from tim@kientzle.com) Received: from [192.168.2.143] (CiscoE3000 [192.168.1.65]) by kientzle.com with SMTP id iepnahn9udytbk8p3mmsjsem8w; Sun, 19 Aug 2012 16:45:06 +0000 (UTC) (envelope-from tim@kientzle.com) Mime-Version: 1.0 (Apple Message framework v1278) Content-Type: text/plain; charset=us-ascii From: Tim Kientzle In-Reply-To: <20120812132047.GA33526@psconsult.nl> Date: Sun, 19 Aug 2012 09:45:05 -0700 Content-Transfer-Encoding: 7bit Message-Id: References: <20120812132047.GA33526@psconsult.nl> To: Paul Schenkeveld X-Mailer: Apple Mail (2.1278) Cc: Current FreeBSD Subject: Re: make package fails in chroot: tar: getvfsbyname failed: No such file or directory X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 19 Aug 2012 16:45:08 -0000 On Aug 12, 2012, at 6:20 AM, Paul Schenkeveld wrote: > Hi, > > I have a wrapper script that builds packages in a chroot environment > which happily runs on release 6 thru 9 and earlier 10 but fails with: > > tar: getvfsbyname failed: No such file or directory > > on a recent -CURRENT. > > What I could dig up so far is that "make package-recursive" calls > pkg_create(1) which in turn calls "tar -c -f .tbz -j -T -" > and then starts feeding filenames that should go into the tarball. > > Something has changed in libarchive when > src/contrib/libarchive/libarchive/archive_read_disk_posix.c was > introduced (libarchive 3.0.3, svn rev 232153 I think) where > setup_current_filesystem() calls getvfsbyname(). > > Now it's getting too hairy for me so I hope someone with more > insight in this kind of stuff can help me out. > > My chroot environment has a root directory which is a subdir of my build > environment, so not a mountpoint by itself. /usr/src and /usr/ports are > NFS mounted from a fileserver and I have devfs mounted on /dev. libarchive does do an initial getvfsbyname() when you ask it to traverse a directory tree so that it can accurately handle later requests about mountpoints and filesystem types. This code is admittedly a little intricate. You've apparently found a case where getvfsbyname() is getting handed a bad filename argument. Maybe one of the filenames getting fed into -T doesn't exist. (In which case tar should report an error, but it should be a clear error.) Can you add a printf() nearby that getvfsbyname() call, to dump the argument that's causing problems? Tim From owner-freebsd-current@FreeBSD.ORG Sun Aug 19 17:59:10 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6CCB81065674 for ; Sun, 19 Aug 2012 17:59:10 +0000 (UTC) (envelope-from rysto32@gmail.com) Received: from mail-vb0-f54.google.com (mail-vb0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id 1D9BB8FC1A for ; Sun, 19 Aug 2012 17:59:09 +0000 (UTC) Received: by vbmv11 with SMTP id v11so6217349vbm.13 for ; Sun, 19 Aug 2012 10:59:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=rSYW4qChmt7wnmbP54wbFZrY6cEYGPprjh7TU7rdxW0=; b=H2FWjhXsBPAqonLWom6p5jBUrE3bTCAYs95mNcHRrUdsiZqXWukQDmRyDenCHrsoam BD20hs6jrKy2H+Q311C2QHWsEJpqvEC1vYnYF6nq4mc19cuymF+3uaM1+AKLsfp0LyHQ Q+hNGiRwe9QCWYW9NUlSbNtquOPGTwuecRqjnfmBdVzX88sH94CQuEY1K+9MWHCKTYFQ CgbdZudCrowJzCdgELhUGKBvk4LHbJvCKYghkKRAlDQqJTwKw4+HOwBq8qWX+/haLfHY peB3EmdYvMFgdgXSEH6sq1qP0dkfEFwgc9/oU4WvM2TNjwkoWrnTVmLuvedCRFT/a+xs z88A== MIME-Version: 1.0 Received: by 10.52.97.196 with SMTP id ec4mr6827445vdb.96.1345399149019; Sun, 19 Aug 2012 10:59:09 -0700 (PDT) Received: by 10.58.207.114 with HTTP; Sun, 19 Aug 2012 10:59:08 -0700 (PDT) Received: by 10.58.207.114 with HTTP; Sun, 19 Aug 2012 10:59:08 -0700 (PDT) In-Reply-To: References: Date: Sun, 19 Aug 2012 13:59:08 -0400 Message-ID: From: Ryan Stone To: Randy Bush Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: FreeBSD Current Subject: Re: buildworld c++ internal error X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 19 Aug 2012 17:59:10 -0000 Are you running make with -j something? You may have to scale that back, unfortunately. C++ compilers seem to be much more memory hungry than straight C compilers. On Aug 19, 2012 10:39 AM, "Randy Bush" wrote: > > Is the system running out of memory? A message will go to dmesg if so. > > bingo! thank you. > > pid 73951 (cc1plus), uid 0, was killed: out of swap space > > as this is a 8g cd card machine, i may have a problem. it's not as if i > can boot a cd rom and run shrinkfs > > randy > From owner-freebsd-current@FreeBSD.ORG Sun Aug 19 18:06:08 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 312501065672 for ; Sun, 19 Aug 2012 18:06:08 +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 ECD988FC0C for ; Sun, 19 Aug 2012 18:06:07 +0000 (UTC) Received: from toshi.auburn.protected-networks.net (toshi.auburn.protected-networks.net [IPv6:2001:470:1f07:4e1::4]) (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 A095A6106; Sun, 19 Aug 2012 14:06:00 -0400 (EDT) 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:cc:subject: references:in-reply-to:x-enigmail-version:openpgp:content-type:content-transfer-encoding; b=I44dMueDLQdu88nGIH8NbhEzuOQjq4LniAiP4SW1iEQRLHe3mczZs6FAZPn8hPjyE F7bNGu9o4FlvXK0cHyUcDgbVjE4UDK9VEfnicGuJw3VY5hY1JmdmesYpGvMGO9m Message-ID: <50312B06.7090101@protected-networks.net> Date: Sun, 19 Aug 2012 14:05:58 -0400 From: Michael Butler User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:14.0) Gecko/20120727 Thunderbird/14.0 MIME-Version: 1.0 To: Randy Bush References: In-Reply-To: X-Enigmail-Version: 1.4.3 OpenPGP: id=0442D492 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: FreeBSD Current , Ryan Stone Subject: Re: buildworld c++ internal error X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 19 Aug 2012 18:06:08 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 08/19/12 10:39, Randy Bush wrote: >> Is the system running out of memory? A message will go to dmesg if so. > > bingo! thank you. > > pid 73951 (cc1plus), uid 0, was killed: out of swap space > > as this is a 8g cd card machine, i may have a problem. it's not as if i > can boot a cd rom and run shrinkfs The only other option I can think of is to reduce the level of optimization, i.e. use '-O' in lieu of '-O2', if you can afford the (relatively small) performance loss, imb -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (FreeBSD) iEYEARECAAYFAlAxKwYACgkQQv9rrgRC1JIA5ACfabjvFFrgID1vfNKRojWJZR0Y CGwAn39bj4ruaKnNITtfOrF51RH6Ewe3 =D9F6 -----END PGP SIGNATURE----- From owner-freebsd-current@FreeBSD.ORG Sun Aug 19 19:29:12 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8BB381065674 for ; Sun, 19 Aug 2012 19:29:12 +0000 (UTC) (envelope-from yanegomi@gmail.com) Received: from mail-ob0-f182.google.com (mail-ob0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id 4DEB48FC0C for ; Sun, 19 Aug 2012 19:29:11 +0000 (UTC) Received: by obbun3 with SMTP id un3so11418097obb.13 for ; Sun, 19 Aug 2012 12:29:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=bBL7KhhBNEghLE+HR2sbsgHs+7WwYmJ1RfAVzn43YlQ=; b=tVE8CYzdZIx2/gj8SG+m+u3jOWJL5W0qwq7TxIMrNAceGjTgPUX5p+auu4HQkGrW2I q4XeH6VRaMkV/LsiWN1x9SWK/zlsxODvwPNvmyM7QlgBNEYd2MwYBOPTgyPP4AjW9rlp T0EA6jHSAEyDeMZKzYM6RYIWLl54ZAfhqBolk//TE2TTTn5w86t9HFk6nNsOoHziwVYC tTinfkA8WxgwVodHdH9bax0NyNoAxFw4RuV4N26+EPYsyYlCI37glc2JVM3ie17lBPvh jf9R1V9qdOUsfKv11usxMk8+b5A4v1/Q9QzyqjuBlQZ4BuXxS7PHRDSkZTCdC5+hAVwM spGA== MIME-Version: 1.0 Received: by 10.182.1.10 with SMTP id 10mr8653809obi.54.1345404551465; Sun, 19 Aug 2012 12:29:11 -0700 (PDT) Received: by 10.76.142.201 with HTTP; Sun, 19 Aug 2012 12:29:11 -0700 (PDT) In-Reply-To: References: Date: Sun, 19 Aug 2012 12:29:11 -0700 Message-ID: From: Garrett Cooper To: Ryan Stone Content-Type: text/plain; charset=ISO-8859-1 Cc: Randy Bush , FreeBSD Current Subject: Re: buildworld c++ internal error X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 19 Aug 2012 19:29:12 -0000 On Sun, Aug 19, 2012 at 10:59 AM, Ryan Stone wrote: > Are you running make with -j something? You may have to scale that back, > unfortunately. C++ compilers seem to be much more memory hungry than > straight C compilers. It depends on how complex the code is as well (IIRC class nesting resulted in nasty overhead). Thanks! -Garrett From owner-freebsd-current@FreeBSD.ORG Sun Aug 19 20:01:59 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A378C106566B for ; Sun, 19 Aug 2012 20:01:59 +0000 (UTC) (envelope-from tim@kientzle.com) Received: from monday.kientzle.com (99-115-135-74.uvs.sntcca.sbcglobal.net [99.115.135.74]) by mx1.freebsd.org (Postfix) with ESMTP id 611928FC14 for ; Sun, 19 Aug 2012 20:01:58 +0000 (UTC) Received: (from root@localhost) by monday.kientzle.com (8.14.4/8.14.4) id q7JK1vXW045797; Sun, 19 Aug 2012 20:01:57 GMT (envelope-from tim@kientzle.com) Received: from [192.168.2.143] (CiscoE3000 [192.168.1.65]) by kientzle.com with SMTP id dj2wk5u9j7eqzhvhpxqnunmysa; Sun, 19 Aug 2012 20:01:57 +0000 (UTC) (envelope-from tim@kientzle.com) Mime-Version: 1.0 (Apple Message framework v1278) Content-Type: text/plain; charset=iso-8859-1 From: Tim Kientzle In-Reply-To: Date: Sun, 19 Aug 2012 13:01:56 -0700 Content-Transfer-Encoding: 7bit Message-Id: References: <20120812132047.GA33526@psconsult.nl> To: Current FreeBSD , Paul Schenkeveld X-Mailer: Apple Mail (2.1278) Cc: Garrett Cooper Subject: Re: make package fails in chroot: tar: getvfsbyname failed: No such file or directory X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 19 Aug 2012 20:01:59 -0000 On Aug 19, 2012, at 12:17 PM, Garrett Cooper wrote: > On Sun, Aug 19, 2012 at 9:45 AM, Tim Kientzle wrote: >> >> On Aug 12, 2012, at 6:20 AM, Paul Schenkeveld wrote: >> >>> Hi, >>> >>> I have a wrapper script that builds packages in a chroot environment >>> which happily runs on release 6 thru 9 and earlier 10 but fails with: >>> >>> tar: getvfsbyname failed: No such file or directory >>> >>> on a recent -CURRENT. >> >> libarchive does do an initial getvfsbyname() when you ask it >> to traverse a directory tree so that it can accurately handle later >> requests about mountpoints and filesystem types. This code >> is admittedly a little intricate. > > The problem most likely is the fact that all mountpoints are > exposed via chroot, thus, if it's checking to see if a mountpoint > exists, it may exist outside of the chroot. > I reviewed the code to refresh my memory. Some of what I said before was not quite right. Libarchive's directory traversal tracks information about the filesystem type so that clients such as bsdtar can efficiently skip synthetic filesystems (/dev or /proc) or network filesystems (NFS or SMB mounts). The net effect is something like this: For each file: stat() or lstat() or fstat() the file look up dev number in an internal cache if the dev number is new: fstatfs() the open fd to get the FS name getvfsbyname() to identify the FS type Unless there's a logic error in libarchive itself, this would suggest that somehow fstatfs() is returning a filesystem type that getvfsbyname() can't identify. Paul: What filesystem are you using? What does "mount" show? Does it work outside the chroot? Tim From owner-freebsd-current@FreeBSD.ORG Sun Aug 19 22:17:40 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3160C106564A for ; Sun, 19 Aug 2012 22:17:40 +0000 (UTC) (envelope-from randy@psg.com) Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by mx1.freebsd.org (Postfix) with ESMTP id 0DE998FC0A for ; Sun, 19 Aug 2012 22:17:40 +0000 (UTC) Received: from localhost ([127.0.0.1] helo=rair.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.80 (FreeBSD)) (envelope-from ) id 1T3DoR-000Lef-8A for freebsd-current@freebsd.org; Sun, 19 Aug 2012 22:17:39 +0000 Date: Mon, 20 Aug 2012 07:17:59 +0900 Message-ID: From: Randy Bush To: FreeBSD Current In-Reply-To: <50312B06.7090101@protected-networks.net> References: User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.7 - "Harue") Content-Type: text/plain; charset=US-ASCII Subject: Re: buildworld c++ internal error X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 19 Aug 2012 22:17:40 -0000 Ryan Stone wrote: > Are you running make with -j something? no way > C++ compilers seem to be much more memory hungry than straight C > compilers. c++ is far too crufty and clever. no free lunch. Michael Butler wrote: > The only other option I can think of is to reduce the level of > optimization, i.e. use '-O' in lieu of '-O2', if you can afford the > (relatively small) performance loss, trying now. it takes 840 mins to run, so ... the only thing a night's sleep got me was the idea of attaching an external sata drive and putting swap on it. randy From owner-freebsd-current@FreeBSD.ORG Mon Aug 20 02:28:35 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D0B3410657BA for ; Mon, 20 Aug 2012 02:28:35 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from mail-gg0-f182.google.com (mail-gg0-f182.google.com [209.85.161.182]) by mx1.freebsd.org (Postfix) with ESMTP id 81C868FC0A for ; Mon, 20 Aug 2012 02:28:35 +0000 (UTC) Received: by ggnk4 with SMTP id k4so5857926ggn.13 for ; Sun, 19 Aug 2012 19:28:28 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=sender:subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer :x-gm-message-state; bh=5tiVN03sjrXPRIT+8jv5u0t4pSq4/GqTmpkeymO2y5c=; b=XXB11NcjRijOgft2scitVNC7ObCiMs63IlQ4LB9rhm/+YRSZ8g9MEsCmOdVW3oeH1b xT4Tpyi2bO8E7s5fA5aHfo/33OA8z1PVFymQhGK/7aAOF216AwM0hvI9olSa1CmatmwR /s0JfCo9m0nZlb+Coc0eWmj/SnYZFNwQjmpc8GKODL9+y7WyLq1LZFh4yREqeMb2smKM eHRj9axUiKSUSbrKEz17posY0hCrudEgEi/0ZDHV5b8EyozfYBM/dkXtHdccWGQ1NqC7 ZJKlwpNiV0oMIIxNFpjp1fSFeNgZJHI80yeGBNT8XXLtyWhzfgAAF6vfQ6Rd/vuUlv6F Os7A== Received: by 10.50.158.226 with SMTP id wx2mr8516159igb.18.1345429707319; Sun, 19 Aug 2012 19:28:27 -0700 (PDT) Received: from 63.imp.bsdimp.com (50-78-194-198-static.hfc.comcastbusiness.net. [50.78.194.198]) by mx.google.com with ESMTPS id pp4sm23154939igb.5.2012.08.19.19.28.25 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 19 Aug 2012 19:28:26 -0700 (PDT) Sender: Warner Losh Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii From: Warner Losh In-Reply-To: <201208191832.39569.hselasky@c2i.net> Date: Sun, 19 Aug 2012 20:28:24 -0600 Content-Transfer-Encoding: quoted-printable Message-Id: <4BC29F9C-B068-4464-9619-3ACD00D7C388@bsdimp.com> References: <20120819202622.6db6a8dd@fubar.geek.nz> <201208191832.39569.hselasky@c2i.net> To: Hans Petter Selasky X-Mailer: Apple Mail (2.1084) X-Gm-Message-State: ALoCoQlJkj/b9PGkiR3l90q0GHuV5ZQN7QnTQ7mrXEhU1OGjGCCLUWvGEwdL4oSbJradi7DYEAIP Cc: freebsd-current@freebsd.org, Andrew Turner Subject: Re: Recent changes in AT91 kernel code causes USB to not work [WAS: r239214 - in head/sys: dev/usb dev/usb/controller sys] X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 20 Aug 2012 02:28:35 -0000 On Aug 19, 2012, at 10:32 AM, Hans Petter Selasky wrote: > Hi, >=20 > I'm trying to reproduce using "src/sys/KB920X arm". >=20 > So far the platform doesn't boot, because recent commits removed one = ore more=20 > of these clocks: >=20 > sc->sc_iclk =3D at91_pmc_clock_ref("udc_clk"); > sc->sc_fclk =3D at91_pmc_clock_ref("udpck"); AT91RM9200 hasn't supported clocks very well at all. But I don't think = that these clocks have ever been defined on the 9200 platform. > So I get a crash at a NULL pointer when trying to access one of these = clocks. >=20 > How to fix this? Hmmmm, the code didn't even compile until recently, and has crashed = every time I used it. > I simply added a NULL check. Now the platform hangs when setting up = the OHCI: >=20 > sys/dev/usb/controller/ohci_atmelarm.c >=20 > + printf("CLOCK ON\n"); > at91_pmc_clock_enable(sc->iclk); > at91_pmc_clock_enable(sc->fclk); These should be nops, because we enable all the pmc clocks early in the = attach process. that's likely the problem, if we aren't turning on the = clocks to the usb device (gadget), then=20 > bus_space_write_4(sc->sc_ohci.sc_io_tag, sc->sc_ohci.sc_io_hdl, > OHCI_CONTROL, 0); >=20 > + printf("INIT\n"); >=20 > I see the clock ON printout, and then nothing more! Not sure if this = is caused=20 > by IRQ's hanging or not. >=20 > Andrew Turner: Can you fix these issues so that I can reproduce? It would help if you could pin-point where this stuff fails in the = stream of commits. I know mine were purposely small and isolated so = that they would be easy to bisect. Warner= From owner-freebsd-current@FreeBSD.ORG Mon Aug 20 07:28:32 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A161F106566C for ; Mon, 20 Aug 2012 07:28:32 +0000 (UTC) (envelope-from bjwela@gmail.com) Received: from mail-lb0-f182.google.com (mail-lb0-f182.google.com [209.85.217.182]) by mx1.freebsd.org (Postfix) with ESMTP id 1C8C68FC0A for ; Mon, 20 Aug 2012 07:28:31 +0000 (UTC) Received: by lbbgg13 with SMTP id gg13so154284lbb.13 for ; Mon, 20 Aug 2012 00:28:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=WRQAClmrOuKRZKSGgE68W2vIzN7PNBWpxM1wDIDN19w=; b=d/OLXaKHW/lFGLpiMxxTvhirjzT3SvwhUuxUf+sPwIBoQoc4IBgBjbo/Yk+ZC/zxw0 PPmuKJv8LVNzwJPK1gtgM1fDmJToaSPm/Zf4N4sCL/W/Xweuetl0LBKAhoAERhdC3Wny zGAASaFrmq3krs9PSBBYeBPg2fccPqbnO/mcheA/2Ew95g4qSJf0gwterzA9841G+Lfy 4MmdyuqoDOHG10snRtq3GLYpYmj5u72CbvZXa0TN7WXQsEWhvCbDPXi6c+r9O2tvL5oK QYlpgPaimunZsejsqjrYNyrfXlCABEphiySLnVZwsGEmzzVEe3e6kP2NPcENkcrCY4/r Ka5A== MIME-Version: 1.0 Received: by 10.152.110.80 with SMTP id hy16mr2933751lab.8.1345447710580; Mon, 20 Aug 2012 00:28:30 -0700 (PDT) Received: by 10.114.14.168 with HTTP; Mon, 20 Aug 2012 00:28:30 -0700 (PDT) In-Reply-To: <50311741.3000204@yandex.ru> References: <50311741.3000204@yandex.ru> Date: Mon, 20 Aug 2012 09:28:30 +0200 Message-ID: From: Bjorn Larsson To: "Andrey V. Elsukov" Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Cc: freebsd-current@freebsd.org Subject: Re: gptzfsboot problem on HP P410i Smart Array X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 20 Aug 2012 07:28:32 -0000 Hi Andrey, We are installing freeBSD using ZFS as root filesystem using the GPT method as described on the freeBSD ZFS wiki. We are creating a GPT boot partition with the gptzfsboot program embedded and then a zroot partition with the freeBSD binaries. This works well and boots on every system we tested except HP P410i smart array systems. The problem is that no disks are identified in gptzfsboot and the following error code is displayed: gptzfsboot: error 1 lba 32 gptzfsboot: error 1 lba 1 It appears that gptzfsboot is not identifying the drives properly. However, when we insert a printf() command in main() in zfsboot.c to troubleshoot the identification problem, the system boots perfectly fine. This is a problem that I believe was fixed last year in 9-CURRENT by implementing a proper struct for edd rather than using a char array for BIOS communication. However, it doesn't seems to have fixed the on the p410i smart arrays. Best regards, Bj=F6rn Larsson On Sun, Aug 19, 2012 at 6:41 PM, Andrey V. Elsukov wrot= e: > > On 19.08.2012 11:22, Bjorn Larsson wrote: > > We are having problems with gptzfsboot on a HP DL360 G7 using the P410i > > Smart Array Controller. > > I=92ve some information on this in the archive on this mailing list tha= t this > > has supposedly been fixed with revision 227400, by implementing the edd > > data structure. > > However we still see the same problem and by adding a printf() in zfsbo= ot.c > > fixes the problem. > > Please, let me know if anyone have seen this problem and if there is a = fix > > for it? > > Hi, > > what exactly do you have? > > -- > WBR, Andrey V. Elsukov > From owner-freebsd-current@FreeBSD.ORG Mon Aug 20 08:32:55 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx2.freebsd.org (mx2.freebsd.org [IPv6:2001:4f8:fff6::35]) by hub.freebsd.org (Postfix) with ESMTP id 249C6106564A; Mon, 20 Aug 2012 08:32:55 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from opti.dougb.net (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id E8C7D14DF92; Mon, 20 Aug 2012 08:32:54 +0000 (UTC) Message-ID: <5031F636.1020405@FreeBSD.org> Date: Mon, 20 Aug 2012 01:32:54 -0700 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:14.0) Gecko/20120728 Thunderbird/14.0 MIME-Version: 1.0 To: Alexander Motin References: <157941699.20120815004542@serebryakov.spb.ru> <502AE8B5.9090106@FreeBSD.org> <502B775D.7000101@FreeBSD.org> In-Reply-To: <502B775D.7000101@FreeBSD.org> X-Enigmail-Version: 1.4.3 OpenPGP: id=1A1ABC84 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Adrian Chadd , lev@freebsd.org, current@freebsd.org Subject: Re: CURRENT as gateway on not-so-fast hardware: where is a bottlneck? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 20 Aug 2012 08:32:55 -0000 On 08/15/2012 03:18, Alexander Motin wrote: > On 15.08.2012 03:09, Doug Barton wrote: >> On 08/14/2012 12:20 PM, Adrian Chadd wrote: >>> Would you be willing to compile a kernel with KTR so you can capture >>> some KTR scheduler dumps? >>> >>> That way the scheduler peeps can feed this into schedgraph.py (and you >>> can too!) to figure out what's going on. >>> >>> Maybe things aren't being scheduled correctly and the added latency is >>> killing performance? >> >> You might also try switching to SCHED_ULE to see if it helps. >> >> Although, in the last few months as mav has been converging the 2 I've >> started to see the same problems I saw on my desktop systems previously >> re-appear even using ULE. For example, if I'm watching an AVI with VLC >> and start doing anything that generates a lot of interrupts (like moving >> large quantities of data from one disk to another) the video and sound >> start to skip. Also, various other desktop features (like menus, window >> switching, etc.) start to take measurable time to happen, sometimes >> seconds. >> >> ... and lest you think this is just a desktop problem, I've seen the >> same scenario on 8.x systems used as web servers. With ULE they were >> frequently getting into peak load situations that created what I called >> "mini thundering herd" problems where they could never quite get caught >> up. Whereas switching to 4BSD the same servers got into high-load >> situations less often, and they recovered on their own in minutes. > > It is quite pointless to speculate without real info like mentioned > above KTR_SCHED traces. I'm sorry, you're quite wrong about that. In the cases I mentioned, and in about 2 out of 3 of the cases where users reported problems and I suggested that they try 4BSD, the results were clear. This obviously points out that there is a serious problem with ULE, and if I were the one who was responsible for that code I would be looking at ways of helping users figure out where the problems are. But that's just me. > Main thing I've learned about schedulers, things > there never work as you expect. There are two many factors are relations > to predict behavior in every case. In the web hosting case that I mentioned, I purposely kept every other factor consistent; and changed only s/ULE/4BSD/. The results were both clear and consistent. > What's about playing AVIs and using other GUIs, key word here and for > ULE in general is interactivity. ULE gives huge boost to threads it > counts interactive. I'm not using ULE. I haven't for over a year. Sorry if I wasn't clear. > If somebody still wish area for experiments, there is always some: > - if you want video player to not lag, set negative nice for it (ULE is > not a magician to guess user wishes); At the same time, I don't have these problems on my Linux systems, and I don't need to adjust anything. Not to mention that given how web servers are one of our main server implementations, the fact that we have what seems to be a serious performance problem with out default scheduler in that use case seems like an issue that we would want to address. Doug -- I am only one, but I am one. I cannot do everything, but I can do something. And I will not let what I cannot do interfere with what I can do. -- Edward Everett Hale, (1822 - 1909) From owner-freebsd-current@FreeBSD.ORG Mon Aug 20 09:42:02 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id DA01E106564A; Mon, 20 Aug 2012 09:42:02 +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 AC2148FC14; Mon, 20 Aug 2012 09:42:02 +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 q7K9fuHd081815; Mon, 20 Aug 2012 05:41:56 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-current.sentex.ca (8.14.5/8.14.5/Submit) id q7K9fuLr081814; Mon, 20 Aug 2012 09:41:56 GMT (envelope-from tinderbox@freebsd.org) Date: Mon, 20 Aug 2012 09:41:56 GMT Message-Id: <201208200941.q7K9fuLr081814@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 , , Precedence: bulk Cc: Subject: [head tinderbox] failure on powerpc/powerpc X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Aug 2012 09:42:03 -0000 TB --- 2012-08-20 07:18:24 - tinderbox 2.9 running on freebsd-current.sentex.ca TB --- 2012-08-20 07:18:24 - 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 --- 2012-08-20 07:18:24 - starting HEAD tinderbox run for powerpc/powerpc TB --- 2012-08-20 07:18:24 - cleaning the object tree TB --- 2012-08-20 07:18:24 - cvsupping the source tree TB --- 2012-08-20 07:18:24 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/powerpc/powerpc/supfile TB --- 2012-08-20 07:18:38 - building world TB --- 2012-08-20 07:18:38 - CROSS_BUILD_TESTING=YES TB --- 2012-08-20 07:18:38 - MAKEOBJDIRPREFIX=/obj TB --- 2012-08-20 07:18:38 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-08-20 07:18:38 - SRCCONF=/dev/null TB --- 2012-08-20 07:18:38 - TARGET=powerpc TB --- 2012-08-20 07:18:38 - TARGET_ARCH=powerpc TB --- 2012-08-20 07:18:38 - TZ=UTC TB --- 2012-08-20 07:18:38 - __MAKE_CONF=/dev/null TB --- 2012-08-20 07:18:38 - cd /src TB --- 2012-08-20 07:18:38 - /usr/bin/make -B buildworld >>> World build started on Mon Aug 20 07:18:40 UTC 2012 >>> 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 Mon Aug 20 09:38:17 UTC 2012 TB --- 2012-08-20 09:38:17 - generating LINT kernel config TB --- 2012-08-20 09:38:17 - cd /src/sys/powerpc/conf TB --- 2012-08-20 09:38:17 - /usr/bin/make -B LINT TB --- 2012-08-20 09:38:17 - cd /src/sys/powerpc/conf TB --- 2012-08-20 09:38:17 - /usr/sbin/config -m LINT TB --- 2012-08-20 09:38:17 - building LINT kernel TB --- 2012-08-20 09:38:17 - CROSS_BUILD_TESTING=YES TB --- 2012-08-20 09:38:17 - MAKEOBJDIRPREFIX=/obj TB --- 2012-08-20 09:38:17 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-08-20 09:38:17 - SRCCONF=/dev/null TB --- 2012-08-20 09:38:17 - TARGET=powerpc TB --- 2012-08-20 09:38:17 - TARGET_ARCH=powerpc TB --- 2012-08-20 09:38:17 - TZ=UTC TB --- 2012-08-20 09:38:17 - __MAKE_CONF=/dev/null TB --- 2012-08-20 09:38:17 - cd /src TB --- 2012-08-20 09:38:17 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Mon Aug 20 09:38:17 UTC 2012 >>> 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 -c -O -pipe -std=c99 -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 -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/libfdt -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -msoft-float -Wa,-many -fno-omit-frame-pointer -msoft-float -mno-altivec -ffreestanding -fstack-protector -Werror /src/sys/dev/ath/if_ath_tx.c -I/src/sys/dev/ath /src/sys/dev/ath/if_ath_tx.c: In function 'ath_tx_chaindesclist': /src/sys/dev/ath/if_ath_tx.c:379: error: 'ATH_DEBUG_XMIT' undeclared (first use in this function) /src/sys/dev/ath/if_ath_tx.c:379: error: (Each undeclared identifier is reported only once /src/sys/dev/ath/if_ath_tx.c:379: error: for each function it appears in.) cc1: warnings being treated as errors /src/sys/dev/ath/if_ath_tx.c:380: warning: implicit declaration of function 'ath_printtxbuf' /src/sys/dev/ath/if_ath_tx.c:380: warning: nested extern declaration of 'ath_printtxbuf' [-Wnested-externs] *** Error code 1 Stop in /obj/powerpc.powerpc/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2012-08-20 09:41:56 - WARNING: /usr/bin/make returned exit code 1 TB --- 2012-08-20 09:41:56 - ERROR: failed to build LINT kernel TB --- 2012-08-20 09:41:56 - 6823.00 user 892.34 system 8612.02 real http://tinderbox.freebsd.org/tinderbox-head-HEAD-powerpc-powerpc.full From owner-freebsd-current@FreeBSD.ORG Mon Aug 20 10:00:04 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0494D1065670; Mon, 20 Aug 2012 10:00:03 +0000 (UTC) (envelope-from mavbsd@gmail.com) Received: from mail-ey0-f182.google.com (mail-ey0-f182.google.com [209.85.215.182]) by mx1.freebsd.org (Postfix) with ESMTP id F208A8FC0C; Mon, 20 Aug 2012 10:00:02 +0000 (UTC) Received: by eaak11 with SMTP id k11so2037055eaa.13 for ; Mon, 20 Aug 2012 03:00:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=uTpxsM9V4AZtucAoVNTw1DN/PP/hvRynPt2UYNtq6Yo=; b=p6UiSfb8LG/+QHkjbeaKwqy2M9pvNcCS+hHn44GeSpogUR54Bh6iDKFyM2RjFAVkRl xI2I1vqKN3pHUqt9uV64K9FNmddyeKwtS35JjsYMhJUetIFLLyK0hmetccAus9WfmruV urHvk5vyCCd2Bv67+D0rJ7kQJT2O582MT39khBg7J+3Sku4OMTnbnRMOLDYimpb1zOaK C1qYw/ixVJfyzbNGxo8M4uPNMtrjCwA9c1COfRh+c4uOgZF9BE5WEEp+32eZrvcRY9ms pnS9eEEeiNkpVfXNQ1bP8pNTE3kacn3JLBwTVRW44rSCghLpG/bHqcyiWTOdbr2hCfPb m0Uw== Received: by 10.14.1.9 with SMTP id 9mr7998146eec.9.1345456801915; Mon, 20 Aug 2012 03:00:01 -0700 (PDT) Received: from mavbook.mavhome.dp.ua ([91.198.175.1]) by mx.google.com with ESMTPS id 9sm40398353eei.12.2012.08.20.03.00.00 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 20 Aug 2012 03:00:01 -0700 (PDT) Sender: Alexander Motin Message-ID: <50320A9E.5070303@FreeBSD.org> Date: Mon, 20 Aug 2012 12:59:58 +0300 From: Alexander Motin User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:13.0) Gecko/20120628 Thunderbird/13.0.1 MIME-Version: 1.0 To: Doug Barton References: <157941699.20120815004542@serebryakov.spb.ru> <502AE8B5.9090106@FreeBSD.org> <502B775D.7000101@FreeBSD.org> <5031F636.1020405@FreeBSD.org> In-Reply-To: <5031F636.1020405@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Adrian Chadd , lev@freebsd.org, current@freebsd.org Subject: Re: CURRENT as gateway on not-so-fast hardware: where is a bottlneck? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 20 Aug 2012 10:00:04 -0000 On 20.08.2012 11:32, Doug Barton wrote: > On 08/15/2012 03:18, Alexander Motin wrote: >> On 15.08.2012 03:09, Doug Barton wrote: >>> On 08/14/2012 12:20 PM, Adrian Chadd wrote: >>>> Would you be willing to compile a kernel with KTR so you can capture >>>> some KTR scheduler dumps? >>>> >>>> That way the scheduler peeps can feed this into schedgraph.py (and you >>>> can too!) to figure out what's going on. >>>> >>>> Maybe things aren't being scheduled correctly and the added latency is >>>> killing performance? >>> >>> You might also try switching to SCHED_ULE to see if it helps. >>> >>> Although, in the last few months as mav has been converging the 2 I've >>> started to see the same problems I saw on my desktop systems previously >>> re-appear even using ULE. For example, if I'm watching an AVI with VLC >>> and start doing anything that generates a lot of interrupts (like moving >>> large quantities of data from one disk to another) the video and sound >>> start to skip. Also, various other desktop features (like menus, window >>> switching, etc.) start to take measurable time to happen, sometimes >>> seconds. >>> >>> ... and lest you think this is just a desktop problem, I've seen the >>> same scenario on 8.x systems used as web servers. With ULE they were >>> frequently getting into peak load situations that created what I called >>> "mini thundering herd" problems where they could never quite get caught >>> up. Whereas switching to 4BSD the same servers got into high-load >>> situations less often, and they recovered on their own in minutes. >> >> It is quite pointless to speculate without real info like mentioned >> above KTR_SCHED traces. > > I'm sorry, you're quite wrong about that. In the cases I mentioned, and > in about 2 out of 3 of the cases where users reported problems and I > suggested that they try 4BSD, the results were clear. This obviously > points out that there is a serious problem with ULE, and if I were the > one who was responsible for that code I would be looking at ways of > helping users figure out where the problems are. But that's just me. I am not telling anything bad about 4BSD. Choice is provided because they are indeed different and none is perfect. 4BSD also has problems. What I would like to say is that if we want to improve situation, we need more detailed info then just verbal description. I am not telling that ULE is perfect. I went there because I've seen problems, and I am still fixing some pieces. I am just trying to explain described behavior from the point of my knowledge about it, hoping that it may help somebody to set up some new experiments or try some tuning/fixing. -- Alexander Motin From owner-freebsd-current@FreeBSD.ORG Mon Aug 20 10:06:04 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 14A0C106564A; Mon, 20 Aug 2012 10:06:04 +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 D9ACF8FC0A; Mon, 20 Aug 2012 10:06:03 +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 q7KA63CR084093; Mon, 20 Aug 2012 06:06:03 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-current.sentex.ca (8.14.5/8.14.5/Submit) id q7KA62qb084092; Mon, 20 Aug 2012 10:06:02 GMT (envelope-from tinderbox@freebsd.org) Date: Mon, 20 Aug 2012 10:06:02 GMT Message-Id: <201208201006.q7KA62qb084092@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 , , Precedence: bulk Cc: Subject: [head tinderbox] failure on sparc64/sparc64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Aug 2012 10:06:04 -0000 TB --- 2012-08-20 08:58:06 - tinderbox 2.9 running on freebsd-current.sentex.ca TB --- 2012-08-20 08:58:06 - 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 --- 2012-08-20 08:58:06 - starting HEAD tinderbox run for sparc64/sparc64 TB --- 2012-08-20 08:58:06 - cleaning the object tree TB --- 2012-08-20 08:58:06 - cvsupping the source tree TB --- 2012-08-20 08:58:07 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/sparc64/sparc64/supfile TB --- 2012-08-20 08:58:57 - building world TB --- 2012-08-20 08:58:57 - CROSS_BUILD_TESTING=YES TB --- 2012-08-20 08:58:57 - MAKEOBJDIRPREFIX=/obj TB --- 2012-08-20 08:58:57 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-08-20 08:58:57 - SRCCONF=/dev/null TB --- 2012-08-20 08:58:57 - TARGET=sparc64 TB --- 2012-08-20 08:58:57 - TARGET_ARCH=sparc64 TB --- 2012-08-20 08:58:57 - TZ=UTC TB --- 2012-08-20 08:58:57 - __MAKE_CONF=/dev/null TB --- 2012-08-20 08:58:57 - cd /src TB --- 2012-08-20 08:58:57 - /usr/bin/make -B buildworld >>> World build started on Mon Aug 20 08:58:58 UTC 2012 >>> 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 Mon Aug 20 10:01:29 UTC 2012 TB --- 2012-08-20 10:01:29 - generating LINT kernel config TB --- 2012-08-20 10:01:29 - cd /src/sys/sparc64/conf TB --- 2012-08-20 10:01:29 - /usr/bin/make -B LINT TB --- 2012-08-20 10:01:29 - cd /src/sys/sparc64/conf TB --- 2012-08-20 10:01:29 - /usr/sbin/config -m LINT TB --- 2012-08-20 10:01:29 - building LINT kernel TB --- 2012-08-20 10:01:29 - CROSS_BUILD_TESTING=YES TB --- 2012-08-20 10:01:29 - MAKEOBJDIRPREFIX=/obj TB --- 2012-08-20 10:01:29 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-08-20 10:01:29 - SRCCONF=/dev/null TB --- 2012-08-20 10:01:29 - TARGET=sparc64 TB --- 2012-08-20 10:01:29 - TARGET_ARCH=sparc64 TB --- 2012-08-20 10:01:29 - TZ=UTC TB --- 2012-08-20 10:01:29 - __MAKE_CONF=/dev/null TB --- 2012-08-20 10:01:29 - cd /src TB --- 2012-08-20 10:01:29 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Mon Aug 20 10:01:29 UTC 2012 >>> 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 -c -O2 -pipe -fno-strict-aliasing -std=c99 -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 -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mcmodel=medany -msoft-float -ffreestanding -fstack-protector -Werror /src/sys/dev/ath/if_ath_tx.c -I/src/sys/dev/ath /src/sys/dev/ath/if_ath_tx.c: In function 'ath_tx_chaindesclist': /src/sys/dev/ath/if_ath_tx.c:379: error: 'ATH_DEBUG_XMIT' undeclared (first use in this function) /src/sys/dev/ath/if_ath_tx.c:379: error: (Each undeclared identifier is reported only once /src/sys/dev/ath/if_ath_tx.c:379: error: for each function it appears in.) cc1: warnings being treated as errors /src/sys/dev/ath/if_ath_tx.c:380: warning: implicit declaration of function 'ath_printtxbuf' /src/sys/dev/ath/if_ath_tx.c:380: warning: nested extern declaration of 'ath_printtxbuf' [-Wnested-externs] *** Error code 1 Stop in /obj/sparc64.sparc64/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2012-08-20 10:06:02 - WARNING: /usr/bin/make returned exit code 1 TB --- 2012-08-20 10:06:02 - ERROR: failed to build LINT kernel TB --- 2012-08-20 10:06:02 - 3160.90 user 562.65 system 4076.09 real http://tinderbox.freebsd.org/tinderbox-head-HEAD-sparc64-sparc64.full From owner-freebsd-current@FreeBSD.ORG Mon Aug 20 10:25:38 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx2.freebsd.org (mx2.freebsd.org [IPv6:2001:4f8:fff6::35]) by hub.freebsd.org (Postfix) with ESMTP id 3F148106566B; Mon, 20 Aug 2012 10:25:38 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from opti.dougb.net (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id E2DD014D92C; Mon, 20 Aug 2012 10:25:37 +0000 (UTC) Message-ID: <503210A1.7010803@FreeBSD.org> Date: Mon, 20 Aug 2012 03:25:37 -0700 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:14.0) Gecko/20120728 Thunderbird/14.0 MIME-Version: 1.0 To: Alexander Motin References: <157941699.20120815004542@serebryakov.spb.ru> <502AE8B5.9090106@FreeBSD.org> <502B775D.7000101@FreeBSD.org> <5031F636.1020405@FreeBSD.org> <50320A9E.5070303@FreeBSD.org> In-Reply-To: <50320A9E.5070303@FreeBSD.org> X-Enigmail-Version: 1.4.3 OpenPGP: id=1A1ABC84 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Adrian Chadd , lev@freebsd.org, current@freebsd.org Subject: Re: CURRENT as gateway on not-so-fast hardware: where is a bottlneck? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 20 Aug 2012 10:25:38 -0000 On 08/20/2012 02:59, Alexander Motin wrote: > On 20.08.2012 11:32, Doug Barton wrote: >> On 08/15/2012 03:18, Alexander Motin wrote: >>> On 15.08.2012 03:09, Doug Barton wrote: >>>> On 08/14/2012 12:20 PM, Adrian Chadd wrote: >>>>> Would you be willing to compile a kernel with KTR so you can capture >>>>> some KTR scheduler dumps? >>>>> >>>>> That way the scheduler peeps can feed this into schedgraph.py (and you >>>>> can too!) to figure out what's going on. >>>>> >>>>> Maybe things aren't being scheduled correctly and the added latency is >>>>> killing performance? >>>> >>>> You might also try switching to SCHED_ULE to see if it helps. >>>> >>>> Although, in the last few months as mav has been converging the 2 I've >>>> started to see the same problems I saw on my desktop systems previously >>>> re-appear even using ULE. For example, if I'm watching an AVI with VLC >>>> and start doing anything that generates a lot of interrupts (like >>>> moving >>>> large quantities of data from one disk to another) the video and sound >>>> start to skip. Also, various other desktop features (like menus, window >>>> switching, etc.) start to take measurable time to happen, sometimes >>>> seconds. >>>> >>>> ... and lest you think this is just a desktop problem, I've seen the >>>> same scenario on 8.x systems used as web servers. With ULE they were >>>> frequently getting into peak load situations that created what I called >>>> "mini thundering herd" problems where they could never quite get caught >>>> up. Whereas switching to 4BSD the same servers got into high-load >>>> situations less often, and they recovered on their own in minutes. >>> >>> It is quite pointless to speculate without real info like mentioned >>> above KTR_SCHED traces. >> >> I'm sorry, you're quite wrong about that. In the cases I mentioned, and >> in about 2 out of 3 of the cases where users reported problems and I >> suggested that they try 4BSD, the results were clear. This obviously >> points out that there is a serious problem with ULE, and if I were the >> one who was responsible for that code I would be looking at ways of >> helping users figure out where the problems are. But that's just me. > > I am not telling anything bad about 4BSD. Yes, I get that, but thanks for making it clear. > Choice is provided because > they are indeed different and none is perfect. ... which is why I'm asking you to stop making them more the same until we get a better idea of what the issues are. > What I would like to say is that if we want to improve situation, we > need more detailed info then just verbal description. And what I'm saying is that the only realistic way that you're going to get that information that you need is to make it easier for users to give it to you. I don't know what form that is going to need to take, I don't know anything about schedulers. > I am not telling > that ULE is perfect. I went there because I've seen problems, and I am > still fixing some pieces. I am just trying to explain described behavior > from the point of my knowledge about it, hoping that it may help > somebody to set up some new experiments or try some tuning/fixing. Yes, I think it's great that you're doing this work. I'm glad to see that someone is improving ULE. It clearly needs it. :) Doug -- I am only one, but I am one. I cannot do everything, but I can do something. And I will not let what I cannot do interfere with what I can do. -- Edward Everett Hale, (1822 - 1909) From owner-freebsd-current@FreeBSD.ORG Mon Aug 20 10:33:28 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C4B3D106566B; Mon, 20 Aug 2012 10:33:28 +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 92F788FC12; Mon, 20 Aug 2012 10:33:28 +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 q7KAXRas053334; Mon, 20 Aug 2012 06:33:27 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-current.sentex.ca (8.14.5/8.14.5/Submit) id q7KAXRWZ053333; Mon, 20 Aug 2012 10:33:27 GMT (envelope-from tinderbox@freebsd.org) Date: Mon, 20 Aug 2012 10:33:27 GMT Message-Id: <201208201033.q7KAXRWZ053333@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 , , Precedence: bulk Cc: Subject: [head tinderbox] failure on powerpc64/powerpc X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Aug 2012 10:33:28 -0000 TB --- 2012-08-20 07:45:14 - tinderbox 2.9 running on freebsd-current.sentex.ca TB --- 2012-08-20 07:45:14 - 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 --- 2012-08-20 07:45:14 - starting HEAD tinderbox run for powerpc64/powerpc TB --- 2012-08-20 07:45:14 - cleaning the object tree TB --- 2012-08-20 07:45:14 - cvsupping the source tree TB --- 2012-08-20 07:45:14 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/powerpc64/powerpc/supfile TB --- 2012-08-20 07:46:54 - building world TB --- 2012-08-20 07:46:54 - CROSS_BUILD_TESTING=YES TB --- 2012-08-20 07:46:54 - MAKEOBJDIRPREFIX=/obj TB --- 2012-08-20 07:46:54 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-08-20 07:46:54 - SRCCONF=/dev/null TB --- 2012-08-20 07:46:54 - TARGET=powerpc TB --- 2012-08-20 07:46:54 - TARGET_ARCH=powerpc64 TB --- 2012-08-20 07:46:54 - TZ=UTC TB --- 2012-08-20 07:46:54 - __MAKE_CONF=/dev/null TB --- 2012-08-20 07:46:54 - cd /src TB --- 2012-08-20 07:46:54 - /usr/bin/make -B buildworld >>> World build started on Mon Aug 20 07:46:55 UTC 2012 >>> 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 >>> stage 5.1: building 32 bit shim libraries >>> World build completed on Mon Aug 20 10:30:00 UTC 2012 TB --- 2012-08-20 10:30:00 - generating LINT kernel config TB --- 2012-08-20 10:30:00 - cd /src/sys/powerpc/conf TB --- 2012-08-20 10:30:00 - /usr/bin/make -B LINT TB --- 2012-08-20 10:30:00 - cd /src/sys/powerpc/conf TB --- 2012-08-20 10:30:00 - /usr/sbin/config -m LINT TB --- 2012-08-20 10:30:00 - building LINT kernel TB --- 2012-08-20 10:30:00 - CROSS_BUILD_TESTING=YES TB --- 2012-08-20 10:30:00 - MAKEOBJDIRPREFIX=/obj TB --- 2012-08-20 10:30:00 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-08-20 10:30:00 - SRCCONF=/dev/null TB --- 2012-08-20 10:30:00 - TARGET=powerpc TB --- 2012-08-20 10:30:00 - TARGET_ARCH=powerpc64 TB --- 2012-08-20 10:30:00 - TZ=UTC TB --- 2012-08-20 10:30:00 - __MAKE_CONF=/dev/null TB --- 2012-08-20 10:30:00 - cd /src TB --- 2012-08-20 10:30:00 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Mon Aug 20 10:30:00 UTC 2012 >>> 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 -c -O -pipe -std=c99 -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 -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/libfdt -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -msoft-float -Wa,-many -fno-omit-frame-pointer -msoft-float -mno-altivec -mcall-aixdesc -ffreestanding -fstack-protector -Werror /src/sys/dev/ath/if_ath_tx.c -I/src/sys/dev/ath /src/sys/dev/ath/if_ath_tx.c: In function 'ath_tx_chaindesclist': /src/sys/dev/ath/if_ath_tx.c:379: error: 'ATH_DEBUG_XMIT' undeclared (first use in this function) /src/sys/dev/ath/if_ath_tx.c:379: error: (Each undeclared identifier is reported only once /src/sys/dev/ath/if_ath_tx.c:379: error: for each function it appears in.) cc1: warnings being treated as errors /src/sys/dev/ath/if_ath_tx.c:380: warning: implicit declaration of function 'ath_printtxbuf' /src/sys/dev/ath/if_ath_tx.c:380: warning: nested extern declaration of 'ath_printtxbuf' [-Wnested-externs] *** Error code 1 Stop in /obj/powerpc.powerpc64/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2012-08-20 10:33:27 - WARNING: /usr/bin/make returned exit code 1 TB --- 2012-08-20 10:33:27 - ERROR: failed to build LINT kernel TB --- 2012-08-20 10:33:27 - 8312.90 user 1128.27 system 10092.84 real http://tinderbox.freebsd.org/tinderbox-head-HEAD-powerpc64-powerpc.full From owner-freebsd-current@FreeBSD.ORG Mon Aug 20 11:42:39 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 828AF106566B for ; Mon, 20 Aug 2012 11:42:39 +0000 (UTC) (envelope-from decke@bluelife.at) Received: from mail-wg0-f50.google.com (mail-wg0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id 072758FC08 for ; Mon, 20 Aug 2012 11:42:38 +0000 (UTC) Received: by wgbds11 with SMTP id ds11so5189676wgb.31 for ; Mon, 20 Aug 2012 04:42:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bluelife.at; s=google; h=mime-version:sender:x-originating-ip:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=xXV+hvQuCPJfDMldXvixIhJh74ZcmjaUQ8AzfWPpdeg=; b=b+y7+hVf3Vsr0bEnYWNq69y58sEqD9XMmhkKWpTGZ6U/L0r+dG9B8jM8aZB64EQIip rs+zTzRoUvW69f9UTuYhvNerTt369Tba83M9XBLoPv0tMLm+P5C80D50VTZJq7RjFl6k TWHKYzDxXC98gnXB4u/RzKYqL7/nZSOgm5xc4= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:sender:x-originating-ip:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :x-gm-message-state; bh=xXV+hvQuCPJfDMldXvixIhJh74ZcmjaUQ8AzfWPpdeg=; b=pGv+JPJM0FRsgfNeH9rjh1/5rPSi8nXc/wqeejUiK1pLL1CzL46grAurOVubgN0n38 6JipYUEwNJc9yILT8Mo/001hZsHJj2vVath7g8Vs5vHtWk0W8SE99s9jDt1r6qsG+jWB Ut0DzSHcYqSpoDlm2ghxHAwUAhRV9NhUlgGoyLnV0mzIiFD6pDObM5YQ1tnLhAmyYVeN qhdFaERiJWmOqZCDXjIytqrK1MENUzYoRQ8l0lTJAsAWIY3oAlupys/ICNVinA8NDE2G BvP+ZkzLB927hW2VbPSwG9qdUhmkdfBYpND92PNuc2BXyjOP5Q+vz5N9gwit51WyPfsu Lacg== MIME-Version: 1.0 Received: by 10.180.81.38 with SMTP id w6mr28302443wix.10.1345462951692; Mon, 20 Aug 2012 04:42:31 -0700 (PDT) Sender: decke@bluelife.at Received: by 10.180.90.15 with HTTP; Mon, 20 Aug 2012 04:42:31 -0700 (PDT) X-Originating-IP: [80.123.233.199] In-Reply-To: References: <20120812132047.GA33526@psconsult.nl> Date: Mon, 20 Aug 2012 13:42:31 +0200 X-Google-Sender-Auth: GahuyOQ7q0KEUBagyMzrNgPib1M Message-ID: From: =?ISO-8859-1?Q?Bernhard_Fr=F6hlich?= To: Tim Kientzle Content-Type: text/plain; charset=ISO-8859-1 X-Gm-Message-State: ALoCoQkRArfSb2rBdngQkdg5aKk7uJiTWEg0+v+40Okpa9Cer0rpcPT8azHXzvDnSRrjHlhzTJeq Cc: Garrett Cooper , Current FreeBSD , Paul Schenkeveld Subject: Re: make package fails in chroot: tar: getvfsbyname failed: No such file or directory X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 20 Aug 2012 11:42:39 -0000 On Sun, Aug 19, 2012 at 10:01 PM, Tim Kientzle wrote: > > On Aug 19, 2012, at 12:17 PM, Garrett Cooper wrote: > >> On Sun, Aug 19, 2012 at 9:45 AM, Tim Kientzle wrote: >>> >>> On Aug 12, 2012, at 6:20 AM, Paul Schenkeveld wrote: >>> >>>> Hi, >>>> >>>> I have a wrapper script that builds packages in a chroot environment >>>> which happily runs on release 6 thru 9 and earlier 10 but fails with: >>>> >>>> tar: getvfsbyname failed: No such file or directory >>>> >>>> on a recent -CURRENT. >>> >>> libarchive does do an initial getvfsbyname() when you ask it >>> to traverse a directory tree so that it can accurately handle later >>> requests about mountpoints and filesystem types. This code >>> is admittedly a little intricate. >> >> The problem most likely is the fact that all mountpoints are >> exposed via chroot, thus, if it's checking to see if a mountpoint >> exists, it may exist outside of the chroot. >> > > I reviewed the code to refresh my memory. Some > of what I said before was not quite right. > > Libarchive's directory traversal tracks information about > the filesystem type so that clients such as bsdtar can > efficiently skip synthetic filesystems (/dev or /proc) or > network filesystems (NFS or SMB mounts). > > The net effect is something like this: > > For each file: > stat() or lstat() or fstat() the file > look up dev number in an internal cache > if the dev number is new: > fstatfs() the open fd to get the FS name > getvfsbyname() to identify the FS type > > Unless there's a logic error in libarchive itself, this > would suggest that somehow fstatfs() is returning > a filesystem type that getvfsbyname() can't > identify. > > Paul: > What filesystem are you using? > > What does "mount" show? > > Does it work outside the chroot? I also see the same on the redports.org build machines. It builds within a jail there which is completely on a tmpfs. Interestinly everything is fine with a 10-CURRENT/amd64 jail but it breaks in a 10-CURRENT/i386 jail. Both are running on the same 10-CURRENT/amd64 which is around 2 months old. https://redports.org/buildarchive/20120814130205-56327/ -- Bernhard Froehlich http://www.bluelife.at/ From owner-freebsd-current@FreeBSD.ORG Mon Aug 20 12:09:26 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 46888106568B; Mon, 20 Aug 2012 12:09:26 +0000 (UTC) (envelope-from david@catwhisker.org) Received: from albert.catwhisker.org (m209-73.dsl.rawbw.com [198.144.209.73]) by mx1.freebsd.org (Postfix) with ESMTP id 02DA78FC12; Mon, 20 Aug 2012 12:09:25 +0000 (UTC) Received: from albert.catwhisker.org (localhost [127.0.0.1]) by albert.catwhisker.org (8.14.5/8.14.5) with ESMTP id q7KC9PxX011042; Mon, 20 Aug 2012 05:09:25 -0700 (PDT) (envelope-from david@albert.catwhisker.org) Received: (from david@localhost) by albert.catwhisker.org (8.14.5/8.14.5/Submit) id q7KC9PbA011041; Mon, 20 Aug 2012 05:09:25 -0700 (PDT) (envelope-from david) Date: Mon, 20 Aug 2012 05:09:25 -0700 From: David Wolfskill To: current@freebsd.org Message-ID: <20120820120925.GE1415@albert.catwhisker.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="HnQK338I3UIa/qiP" Content-Disposition: inline User-Agent: Mutt/1.5.21 (2010-09-15) Cc: adrian@freebsd.org Subject: FreeBSD buildkernel fails @r239409 in sys/dev/ath/if_ath_tx.c X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 20 Aug 2012 12:09:26 -0000 --HnQK338I3UIa/qiP Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable This is using clang: =2E.. >>> stage 3.2: building everything cd /usr/obj/usr/src/sys/CANARY; MAKEOBJDIRPREFIX=3D/usr/obj MACHINE_ARCH= =3Di386 MACHINE=3Di386 CPUTYPE=3D GROFF_BIN_PATH=3D/usr/obj/usr/src/tmp/l= egacy/usr/bin GROFF_FONT_PATH=3D/usr/obj/usr/src/tmp/legacy/usr/share/grof= f_font GROFF_TMAC_PATH=3D/usr/obj/usr/src/tmp/legacy/usr/share/tmac _SHLI= BDIRPREFIX=3D/usr/obj/usr/src/tmp _LDSCRIPTROOT=3D VERSION=3D"FreeBSD 10.= 0-CURRENT i386 1000017" INSTALL=3D"sh /usr/src/tools/install.sh" PATH=3D/= usr/obj/usr/src/tmp/legacy/usr/sbin:/usr/obj/usr/src/tmp/legacy/usr/bin:/us= r/obj/usr/src/tmp/legacy/usr/games:/usr/obj/usr/src/tmp/usr/sbin:/usr/obj/u= sr/src/tmp/usr/bin:/usr/obj/usr/src/tmp/usr/games:/sbin:/bin:/usr/sbin:/usr= /bin /usr/obj/usr/src/make.i386/make KERNEL=3Dkernel all -DNO_MODULES_OBJ clang -c -O -pipe -std=3Dc99 -g -Wall -Wredundant-decls -Wnested-externs -= Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qu= al -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -= fdiagnostics-show-option -Wno-error-tautological-compare -Wno-error-empty-= body -Wno-error-parentheses-equality -nostdinc -I. -I/usr/src/sys -I/usr/= src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_gl= obal.h -mno-aes -mno-avx -mno-mmx -mno-sse -msoft-float -ffreestanding -fs= tack-protector -Werror /usr/src/sys/dev/ath/if_ath_tx.c -I/usr/src/sys/dev= /ath /usr/src/sys/dev/ath/if_ath_tx.c:379:22: error: use of undeclared identifier 'ATH_DEBUG_XMIT' if (sc->sc_debug & ATH_DEBUG_XMIT) ^ /usr/src/sys/dev/ath/if_ath_tx.c:380:4: error: implicit declaration of func= tion 'ath_printtxbuf' is invalid in C99 [-Werror,-Wimplicit-function-declaration] ath_printtxbuf(sc, bf, qnum, 0, 0); ^ 2 errors generated. *** [if_ath_tx.o] Error code 1 Stop in /common/S4/obj/usr/src/sys/CANARY. *** [buildkernel] Error code 1 Stop in /usr/src. *** [buildkernel] Error code 1 Stop in /usr/src. Peace, david --=20 David H. Wolfskill david@catwhisker.org Depriving a girl or boy of an opportunity for education is evil. See http://www.catwhisker.org/~david/publickey.gpg for my public key. --HnQK338I3UIa/qiP Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEARECAAYFAlAyKPQACgkQmprOCmdXAD1xrwCfRYm4OTsBahXySWaseJ9cf51O EAAAn1tNk4H535TZGS+69+pv0tAijSnc =hrxL -----END PGP SIGNATURE----- --HnQK338I3UIa/qiP-- From owner-freebsd-current@FreeBSD.ORG Mon Aug 20 12:12:33 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 53297106567C; Mon, 20 Aug 2012 12:12:33 +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 C822B8FC20; Mon, 20 Aug 2012 12:12:32 +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 q7KCCW99093396; Mon, 20 Aug 2012 08:12:32 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-current.sentex.ca (8.14.5/8.14.5/Submit) id q7KCCW2M093395; Mon, 20 Aug 2012 12:12:32 GMT (envelope-from tinderbox@freebsd.org) Date: Mon, 20 Aug 2012 12:12:32 GMT Message-Id: <201208201212.q7KCCW2M093395@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 , , Precedence: bulk Cc: Subject: [head tinderbox] failure on arm/arm X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Aug 2012 12:12:33 -0000 TB --- 2012-08-20 10:40:00 - tinderbox 2.9 running on freebsd-current.sentex.ca TB --- 2012-08-20 10:40:00 - 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 --- 2012-08-20 10:40:00 - starting HEAD tinderbox run for arm/arm TB --- 2012-08-20 10:40:00 - cleaning the object tree TB --- 2012-08-20 10:40:00 - cvsupping the source tree TB --- 2012-08-20 10:40:00 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/arm/arm/supfile TB --- 2012-08-20 10:41:06 - building world TB --- 2012-08-20 10:41:06 - CROSS_BUILD_TESTING=YES TB --- 2012-08-20 10:41:06 - MAKEOBJDIRPREFIX=/obj TB --- 2012-08-20 10:41:06 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-08-20 10:41:06 - SRCCONF=/dev/null TB --- 2012-08-20 10:41:06 - TARGET=arm TB --- 2012-08-20 10:41:06 - TARGET_ARCH=arm TB --- 2012-08-20 10:41:06 - TZ=UTC TB --- 2012-08-20 10:41:06 - __MAKE_CONF=/dev/null TB --- 2012-08-20 10:41:06 - cd /src TB --- 2012-08-20 10:41:06 - /usr/bin/make -B buildworld >>> World build started on Mon Aug 20 10:41:07 UTC 2012 >>> 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 Mon Aug 20 11:43:37 UTC 2012 TB --- 2012-08-20 11:43:37 - cd /src/sys/arm/conf TB --- 2012-08-20 11:43:37 - /usr/sbin/config -m ARMADAXP TB --- 2012-08-20 11:43:37 - skipping ARMADAXP kernel TB --- 2012-08-20 11:43:37 - cd /src/sys/arm/conf TB --- 2012-08-20 11:43:37 - /usr/sbin/config -m ATMEL TB --- 2012-08-20 11:43:37 - building ATMEL kernel TB --- 2012-08-20 11:43:37 - CROSS_BUILD_TESTING=YES TB --- 2012-08-20 11:43:37 - MAKEOBJDIRPREFIX=/obj TB --- 2012-08-20 11:43:37 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-08-20 11:43:37 - SRCCONF=/dev/null TB --- 2012-08-20 11:43:37 - TARGET=arm TB --- 2012-08-20 11:43:37 - TARGET_ARCH=arm TB --- 2012-08-20 11:43:37 - TZ=UTC TB --- 2012-08-20 11:43:37 - __MAKE_CONF=/dev/null TB --- 2012-08-20 11:43:37 - cd /src TB --- 2012-08-20 11:43:37 - /usr/bin/make -B buildkernel KERNCONF=ATMEL >>> Kernel build for ATMEL started on Mon Aug 20 11:43:37 UTC 2012 >>> 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 ATMEL completed on Mon Aug 20 11:47:11 UTC 2012 TB --- 2012-08-20 11:47:11 - cd /src/sys/arm/conf TB --- 2012-08-20 11:47:11 - /usr/sbin/config -m AVILA TB --- 2012-08-20 11:47:11 - skipping AVILA kernel TB --- 2012-08-20 11:47:11 - cd /src/sys/arm/conf TB --- 2012-08-20 11:47:11 - /usr/sbin/config -m BEAGLEBONE TB --- 2012-08-20 11:47:11 - skipping BEAGLEBONE kernel TB --- 2012-08-20 11:47:11 - cd /src/sys/arm/conf TB --- 2012-08-20 11:47:11 - /usr/sbin/config -m BWCT TB --- 2012-08-20 11:47:11 - building BWCT kernel TB --- 2012-08-20 11:47:11 - CROSS_BUILD_TESTING=YES TB --- 2012-08-20 11:47:11 - MAKEOBJDIRPREFIX=/obj TB --- 2012-08-20 11:47:11 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-08-20 11:47:11 - SRCCONF=/dev/null TB --- 2012-08-20 11:47:11 - TARGET=arm TB --- 2012-08-20 11:47:11 - TARGET_ARCH=arm TB --- 2012-08-20 11:47:11 - TZ=UTC TB --- 2012-08-20 11:47:11 - __MAKE_CONF=/dev/null TB --- 2012-08-20 11:47:11 - cd /src TB --- 2012-08-20 11:47:11 - /usr/bin/make -B buildkernel KERNCONF=BWCT >>> Kernel build for BWCT started on Mon Aug 20 11:47:11 UTC 2012 >>> 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 BWCT completed on Mon Aug 20 11:49:21 UTC 2012 TB --- 2012-08-20 11:49:21 - cd /src/sys/arm/conf TB --- 2012-08-20 11:49:21 - /usr/sbin/config -m CAMBRIA TB --- 2012-08-20 11:49:21 - skipping CAMBRIA kernel TB --- 2012-08-20 11:49:21 - cd /src/sys/arm/conf TB --- 2012-08-20 11:49:21 - /usr/sbin/config -m CNS11XXNAS TB --- 2012-08-20 11:49:21 - building CNS11XXNAS kernel TB --- 2012-08-20 11:49:21 - CROSS_BUILD_TESTING=YES TB --- 2012-08-20 11:49:21 - MAKEOBJDIRPREFIX=/obj TB --- 2012-08-20 11:49:21 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-08-20 11:49:21 - SRCCONF=/dev/null TB --- 2012-08-20 11:49:21 - TARGET=arm TB --- 2012-08-20 11:49:21 - TARGET_ARCH=arm TB --- 2012-08-20 11:49:21 - TZ=UTC TB --- 2012-08-20 11:49:21 - __MAKE_CONF=/dev/null TB --- 2012-08-20 11:49:21 - cd /src TB --- 2012-08-20 11:49:21 - /usr/bin/make -B buildkernel KERNCONF=CNS11XXNAS >>> Kernel build for CNS11XXNAS started on Mon Aug 20 11:49:21 UTC 2012 >>> 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 CNS11XXNAS completed on Mon Aug 20 11:51:49 UTC 2012 TB --- 2012-08-20 11:51:49 - cd /src/sys/arm/conf TB --- 2012-08-20 11:51:49 - /usr/sbin/config -m CRB TB --- 2012-08-20 11:51:49 - skipping CRB kernel TB --- 2012-08-20 11:51:49 - cd /src/sys/arm/conf TB --- 2012-08-20 11:51:49 - /usr/sbin/config -m DB-78XXX TB --- 2012-08-20 11:51:49 - building DB-78XXX kernel TB --- 2012-08-20 11:51:49 - CROSS_BUILD_TESTING=YES TB --- 2012-08-20 11:51:49 - MAKEOBJDIRPREFIX=/obj TB --- 2012-08-20 11:51:49 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-08-20 11:51:49 - SRCCONF=/dev/null TB --- 2012-08-20 11:51:49 - TARGET=arm TB --- 2012-08-20 11:51:49 - TARGET_ARCH=arm TB --- 2012-08-20 11:51:49 - TZ=UTC TB --- 2012-08-20 11:51:49 - __MAKE_CONF=/dev/null TB --- 2012-08-20 11:51:49 - cd /src TB --- 2012-08-20 11:51:49 - /usr/bin/make -B buildkernel KERNCONF=DB-78XXX >>> Kernel build for DB-78XXX started on Mon Aug 20 11:51:49 UTC 2012 >>> 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 DB-78XXX completed on Mon Aug 20 11:54:38 UTC 2012 TB --- 2012-08-20 11:54:38 - cd /src/sys/arm/conf TB --- 2012-08-20 11:54:38 - /usr/sbin/config -m DB-88F5XXX TB --- 2012-08-20 11:54:38 - building DB-88F5XXX kernel TB --- 2012-08-20 11:54:38 - CROSS_BUILD_TESTING=YES TB --- 2012-08-20 11:54:38 - MAKEOBJDIRPREFIX=/obj TB --- 2012-08-20 11:54:38 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-08-20 11:54:38 - SRCCONF=/dev/null TB --- 2012-08-20 11:54:38 - TARGET=arm TB --- 2012-08-20 11:54:38 - TARGET_ARCH=arm TB --- 2012-08-20 11:54:38 - TZ=UTC TB --- 2012-08-20 11:54:38 - __MAKE_CONF=/dev/null TB --- 2012-08-20 11:54:38 - cd /src TB --- 2012-08-20 11:54:38 - /usr/bin/make -B buildkernel KERNCONF=DB-88F5XXX >>> Kernel build for DB-88F5XXX started on Mon Aug 20 11:54:38 UTC 2012 >>> 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 DB-88F5XXX completed on Mon Aug 20 11:57:20 UTC 2012 TB --- 2012-08-20 11:57:20 - cd /src/sys/arm/conf TB --- 2012-08-20 11:57:20 - /usr/sbin/config -m DB-88F6XXX TB --- 2012-08-20 11:57:21 - building DB-88F6XXX kernel TB --- 2012-08-20 11:57:21 - CROSS_BUILD_TESTING=YES TB --- 2012-08-20 11:57:21 - MAKEOBJDIRPREFIX=/obj TB --- 2012-08-20 11:57:21 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-08-20 11:57:21 - SRCCONF=/dev/null TB --- 2012-08-20 11:57:21 - TARGET=arm TB --- 2012-08-20 11:57:21 - TARGET_ARCH=arm TB --- 2012-08-20 11:57:21 - TZ=UTC TB --- 2012-08-20 11:57:21 - __MAKE_CONF=/dev/null TB --- 2012-08-20 11:57:21 - cd /src TB --- 2012-08-20 11:57:21 - /usr/bin/make -B buildkernel KERNCONF=DB-88F6XXX >>> Kernel build for DB-88F6XXX started on Mon Aug 20 11:57:21 UTC 2012 >>> 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 DB-88F6XXX completed on Mon Aug 20 12:00:16 UTC 2012 TB --- 2012-08-20 12:00:16 - cd /src/sys/arm/conf TB --- 2012-08-20 12:00:16 - /usr/sbin/config -m DOCKSTAR TB --- 2012-08-20 12:00:16 - building DOCKSTAR kernel TB --- 2012-08-20 12:00:16 - CROSS_BUILD_TESTING=YES TB --- 2012-08-20 12:00:16 - MAKEOBJDIRPREFIX=/obj TB --- 2012-08-20 12:00:16 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-08-20 12:00:16 - SRCCONF=/dev/null TB --- 2012-08-20 12:00:16 - TARGET=arm TB --- 2012-08-20 12:00:16 - TARGET_ARCH=arm TB --- 2012-08-20 12:00:16 - TZ=UTC TB --- 2012-08-20 12:00:16 - __MAKE_CONF=/dev/null TB --- 2012-08-20 12:00:16 - cd /src TB --- 2012-08-20 12:00:16 - /usr/bin/make -B buildkernel KERNCONF=DOCKSTAR >>> Kernel build for DOCKSTAR started on Mon Aug 20 12:00:16 UTC 2012 >>> 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 DOCKSTAR completed on Mon Aug 20 12:02:52 UTC 2012 TB --- 2012-08-20 12:02:52 - cd /src/sys/arm/conf TB --- 2012-08-20 12:02:52 - /usr/sbin/config -m EA3250 TB --- 2012-08-20 12:02:52 - building EA3250 kernel TB --- 2012-08-20 12:02:52 - CROSS_BUILD_TESTING=YES TB --- 2012-08-20 12:02:52 - MAKEOBJDIRPREFIX=/obj TB --- 2012-08-20 12:02:52 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-08-20 12:02:52 - SRCCONF=/dev/null TB --- 2012-08-20 12:02:52 - TARGET=arm TB --- 2012-08-20 12:02:52 - TARGET_ARCH=arm TB --- 2012-08-20 12:02:52 - TZ=UTC TB --- 2012-08-20 12:02:52 - __MAKE_CONF=/dev/null TB --- 2012-08-20 12:02:52 - cd /src TB --- 2012-08-20 12:02:52 - /usr/bin/make -B buildkernel KERNCONF=EA3250 >>> Kernel build for EA3250 started on Mon Aug 20 12:02:52 UTC 2012 >>> 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 EA3250 completed on Mon Aug 20 12:05:30 UTC 2012 TB --- 2012-08-20 12:05:30 - cd /src/sys/arm/conf TB --- 2012-08-20 12:05:30 - /usr/sbin/config -m EB9200 TB --- 2012-08-20 12:05:30 - building EB9200 kernel TB --- 2012-08-20 12:05:30 - CROSS_BUILD_TESTING=YES TB --- 2012-08-20 12:05:30 - MAKEOBJDIRPREFIX=/obj TB --- 2012-08-20 12:05:30 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-08-20 12:05:30 - SRCCONF=/dev/null TB --- 2012-08-20 12:05:30 - TARGET=arm TB --- 2012-08-20 12:05:30 - TARGET_ARCH=arm TB --- 2012-08-20 12:05:30 - TZ=UTC TB --- 2012-08-20 12:05:30 - __MAKE_CONF=/dev/null TB --- 2012-08-20 12:05:30 - cd /src TB --- 2012-08-20 12:05:30 - /usr/bin/make -B buildkernel KERNCONF=EB9200 >>> Kernel build for EB9200 started on Mon Aug 20 12:05:31 UTC 2012 >>> 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 EB9200 completed on Mon Aug 20 12:08:01 UTC 2012 TB --- 2012-08-20 12:08:01 - cd /src/sys/arm/conf TB --- 2012-08-20 12:08:01 - /usr/sbin/config -m EP80219 TB --- 2012-08-20 12:08:01 - skipping EP80219 kernel TB --- 2012-08-20 12:08:01 - cd /src/sys/arm/conf TB --- 2012-08-20 12:08:01 - /usr/sbin/config -m ETHERNUT5 TB --- 2012-08-20 12:08:01 - building ETHERNUT5 kernel TB --- 2012-08-20 12:08:01 - CROSS_BUILD_TESTING=YES TB --- 2012-08-20 12:08:01 - MAKEOBJDIRPREFIX=/obj TB --- 2012-08-20 12:08:01 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-08-20 12:08:01 - SRCCONF=/dev/null TB --- 2012-08-20 12:08:01 - TARGET=arm TB --- 2012-08-20 12:08:01 - TARGET_ARCH=arm TB --- 2012-08-20 12:08:01 - TZ=UTC TB --- 2012-08-20 12:08:01 - __MAKE_CONF=/dev/null TB --- 2012-08-20 12:08:01 - cd /src TB --- 2012-08-20 12:08:01 - /usr/bin/make -B buildkernel KERNCONF=ETHERNUT5 >>> Kernel build for ETHERNUT5 started on Mon Aug 20 12:08:02 UTC 2012 >>> 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 -Werror -D_KERNEL -DKLD_MODULE -nostdinc -I. -I/src/sys/modules/ath/../../dev/ath -I/src/sys/modules/ath/../../dev/ath/ath_hal -DHAVE_KERNEL_OPTION_HEADERS -include /obj/arm.arm/src/sys/ETHERNUT5/opt_global.h -I. -I@ -I@/contrib/altq -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-common -I/obj/arm.arm/src/sys/ETHERNUT5 -mcpu=arm9 -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/ath/../../dev/ath/if_ath_tx.c /src/sys/modules/ath/../../dev/ath/if_ath_tx.c: In function 'ath_tx_chaindesclist': /src/sys/modules/ath/../../dev/ath/if_ath_tx.c:379: error: 'ATH_DEBUG_XMIT' undeclared (first use in this function) /src/sys/modules/ath/../../dev/ath/if_ath_tx.c:379: error: (Each undeclared identifier is reported only once /src/sys/modules/ath/../../dev/ath/if_ath_tx.c:379: error: for each function it appears in.) cc1: warnings being treated as errors /src/sys/modules/ath/../../dev/ath/if_ath_tx.c:380: warning: implicit declaration of function 'ath_printtxbuf' /src/sys/modules/ath/../../dev/ath/if_ath_tx.c:380: warning: nested extern declaration of 'ath_printtxbuf' [-Wnested-externs] *** Error code 1 Stop in /src/sys/modules/ath. *** Error code 1 Stop in /src/sys/modules. *** Error code 1 Stop in /obj/arm.arm/src/sys/ETHERNUT5. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2012-08-20 12:12:31 - WARNING: /usr/bin/make returned exit code 1 TB --- 2012-08-20 12:12:31 - ERROR: failed to build ETHERNUT5 kernel TB --- 2012-08-20 12:12:31 - 3844.17 user 789.78 system 5551.18 real http://tinderbox.freebsd.org/tinderbox-head-HEAD-arm-arm.full From owner-freebsd-current@FreeBSD.ORG Mon Aug 20 12:31:38 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2947E106567F for ; Mon, 20 Aug 2012 12:31:38 +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 F38868FC0A for ; Mon, 20 Aug 2012 12:31:37 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 4518EB972; Mon, 20 Aug 2012 08:31:37 -0400 (EDT) From: John Baldwin To: freebsd-current@freebsd.org Date: Mon, 20 Aug 2012 08:04:31 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110714-p17; KDE/4.5.5; amd64; ; ) References: In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201208200804.31932.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Mon, 20 Aug 2012 08:31:37 -0400 (EDT) Cc: Monthadar Al Jaberi Subject: Re: kernel page fult for a valid pointer? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 20 Aug 2012 12:31:38 -0000 On Saturday, August 18, 2012 2:29:26 pm Monthadar Al Jaberi wrote: > Hi, > > I am wondering is there a reason for getting "Fatal trap 12: page > fault while in kernel mode" "supervisor read, page not present" for an > address used to be valid in kernel space? > > I dont really understand why I am getting this, I added a hardware > watchpoint on the address, and when I got to the debuger I could read > the memory content and dump for that address. But when I continue from > the debugger I get the panic and now when I try to read the memory > content I get *** error reading from address ce733000 ***. Whatever memory was there might have been unmapped? For example, memory pointed to by I/O buffers (struct buf/bio) use transient mappings that are only valid while an I/O request is in progress. -- John Baldwin From owner-freebsd-current@FreeBSD.ORG Mon Aug 20 12:31:39 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8473C1065675; Mon, 20 Aug 2012 12:31:39 +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 5AD1A8FC17; Mon, 20 Aug 2012 12:31:39 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id AF243B941; Mon, 20 Aug 2012 08:31:38 -0400 (EDT) From: John Baldwin To: freebsd-current@freebsd.org Date: Mon, 20 Aug 2012 08:06:06 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110714-p17; KDE/4.5.5; amd64; ; ) References: <6882.1345325806@critter.freebsd.dk> In-Reply-To: <6882.1345325806@critter.freebsd.dk> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201208200806.06990.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Mon, 20 Aug 2012 08:31:38 -0400 (EDT) Cc: Poul-Henning Kamp , Matt Jacob Subject: Re: BUFSIZ = 1024, still ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 20 Aug 2012 12:31:39 -0000 On Saturday, August 18, 2012 5:36:46 pm Poul-Henning Kamp wrote: > In message <50300540.9060906@feral.com>, Matthew Jacob writes: > >If you're going to talk about making a change to defaults, the default > >MAXPHYS and DLFTPHYS have been undersized for years now. > > Indeed, but as I understand it, those require device driver changes ? Scott already made the device driver changes for MAXPHYS and there are various shops with run with a raised MAXPHYS already. -- John Baldwin From owner-freebsd-current@FreeBSD.ORG Mon Aug 20 12:31:40 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D37B6106567D; Mon, 20 Aug 2012 12:31:40 +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 A8DF38FC1B; Mon, 20 Aug 2012 12:31:40 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 08A66B91C; Mon, 20 Aug 2012 08:31:40 -0400 (EDT) From: John Baldwin To: freebsd-current@freebsd.org Date: Mon, 20 Aug 2012 08:24:38 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110714-p17; KDE/4.5.5; amd64; ; ) References: <6800.1345323911@critter.freebsd.dk> In-Reply-To: <6800.1345323911@critter.freebsd.dk> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201208200824.38500.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Mon, 20 Aug 2012 08:31:40 -0400 (EDT) Cc: Poul-Henning Kamp , Matt Jacob Subject: Re: BUFSIZ = 1024, still ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 20 Aug 2012 12:31:40 -0000 On Saturday, August 18, 2012 5:05:11 pm Poul-Henning Kamp wrote: > In message <5030033B.4060705@feral.com>, Matthew Jacob writes: > >On 8/18/2012 1:32 PM, Poul-Henning Kamp wrote: > >> Shouldn't we at least increase it to pagesize ? > >> > >What data suggests to you it would be better at pagesize? > > The number of system calls to fwrite() a big file ? Have you looked at an actual ktrace? :) stdio doesn't use BUFSIZ for regular files: head/lib/libc/stdio/makebuf.c: /* * Internal routine to determine `proper' buffering for a file. */ int __swhatbuf(fp, bufsize, couldbetty) FILE *fp; size_t *bufsize; int *couldbetty; { struct stat st; if (fp->_file < 0 || _fstat(fp->_file, &st) < 0) { ... *bufsize = BUFSIZ; return (__SNPT); } ... if (st.st_blksize <= 0) { *bufsize = BUFSIZ; return (__SNPT); } *bufsize = st.st_blksize; ... } For a regular file stdio will use the filesystem's block size, not BUFSIZ. Test program: #include #include int main(int ac, char **av) { char junk; FILE *fp; int i; fp = fopen("/tmp/junk", "w"); if (fp == NULL) err(1, "fopen"); for (i = 0; i < 1024 * 1024; i++) if (fwrite(&junk, sizeof(junk), 1, fp) != 1) errx(1, "fwrite failed"); return (0); } ktrace excerpt: 42599 a.out CALL write(0x3,0x800a04000,0x4000) 42599 a.out RET write 16384/0x4000 42599 a.out CALL write(0x3,0x800a04000,0x4000) 42599 a.out RET write 16384/0x4000 42599 a.out CALL write(0x3,0x800a04000,0x4000) 42599 a.out RET write 16384/0x4000 42599 a.out CALL write(0x3,0x800a04000,0x4000) 42599 a.out RET write 16384/0x4000 42599 a.out CALL write(0x3,0x800a04000,0x4000) 42599 a.out RET write 16384/0x4000 42599 a.out CALL write(0x3,0x800a04000,0x4000) 42599 a.out RET write 16384/0x4000 This hint also works for pipes (they set st_blksize to PAGE_SIZE). Given that, I think BUFSIZ should just be left alone. -- John Baldwin From owner-freebsd-current@FreeBSD.ORG Mon Aug 20 12:31:50 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C582A1065680; Mon, 20 Aug 2012 12:31:50 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mail.zoral.com.ua (mx0.zoral.com.ua [91.193.166.200]) by mx1.freebsd.org (Postfix) with ESMTP id 114FA8FC14; Mon, 20 Aug 2012 12:31:49 +0000 (UTC) Received: from skuns.kiev.zoral.com.ua (localhost [127.0.0.1]) by mail.zoral.com.ua (8.14.2/8.14.2) with ESMTP id q7KCVsMH024365; Mon, 20 Aug 2012 15:31:54 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.14.5/8.14.5) with ESMTP id q7KCVgLc086767; Mon, 20 Aug 2012 15:31:42 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.5/8.14.5/Submit) id q7KCVglY086766; Mon, 20 Aug 2012 15:31:42 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Mon, 20 Aug 2012 15:31:42 +0300 From: Konstantin Belousov To: Bernhard Fr?hlich Message-ID: <20120820123142.GY33100@deviant.kiev.zoral.com.ua> References: <20120812132047.GA33526@psconsult.nl> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="hblleJHDxiLJUoyx" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i X-Virus-Scanned: clamav-milter 0.95.2 at skuns.kiev.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=-4.0 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on skuns.kiev.zoral.com.ua Cc: Garrett Cooper , Current FreeBSD , Paul Schenkeveld Subject: Re: make package fails in chroot: tar: getvfsbyname failed: No such file or directory X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 20 Aug 2012 12:31:50 -0000 --hblleJHDxiLJUoyx Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Aug 20, 2012 at 01:42:31PM +0200, Bernhard Fr?hlich wrote: > On Sun, Aug 19, 2012 at 10:01 PM, Tim Kientzle wrote: > > > > On Aug 19, 2012, at 12:17 PM, Garrett Cooper wrote: > > > >> On Sun, Aug 19, 2012 at 9:45 AM, Tim Kientzle wrote: > >>> > >>> On Aug 12, 2012, at 6:20 AM, Paul Schenkeveld wrote: > >>> > >>>> Hi, > >>>> > >>>> I have a wrapper script that builds packages in a chroot environment > >>>> which happily runs on release 6 thru 9 and earlier 10 but fails with: > >>>> > >>>> tar: getvfsbyname failed: No such file or directory > >>>> > >>>> on a recent -CURRENT. > >>> > >>> libarchive does do an initial getvfsbyname() when you ask it > >>> to traverse a directory tree so that it can accurately handle later > >>> requests about mountpoints and filesystem types. This code > >>> is admittedly a little intricate. > >> > >> The problem most likely is the fact that all mountpoints are > >> exposed via chroot, thus, if it's checking to see if a mountpoint > >> exists, it may exist outside of the chroot. > >> > > > > I reviewed the code to refresh my memory. Some > > of what I said before was not quite right. > > > > Libarchive's directory traversal tracks information about > > the filesystem type so that clients such as bsdtar can > > efficiently skip synthetic filesystems (/dev or /proc) or > > network filesystems (NFS or SMB mounts). > > > > The net effect is something like this: > > > > For each file: > > stat() or lstat() or fstat() the file > > look up dev number in an internal cache > > if the dev number is new: > > fstatfs() the open fd to get the FS name > > getvfsbyname() to identify the FS type > > > > Unless there's a logic error in libarchive itself, this > > would suggest that somehow fstatfs() is returning > > a filesystem type that getvfsbyname() can't > > identify. > > > > Paul: > > What filesystem are you using? > > > > What does "mount" show? > > > > Does it work outside the chroot? >=20 > I also see the same on the redports.org build machines. > It builds within a jail there which is completely on a tmpfs. > Interestinly everything is fine with a 10-CURRENT/amd64 > jail but it breaks in a 10-CURRENT/i386 jail. Both are > running on the same 10-CURRENT/amd64 which is > around 2 months old. >=20 > https://redports.org/buildarchive/20120814130205-56327/ Try this. diff --git a/sys/kern/vfs_subr.c b/sys/kern/vfs_subr.c index 1d6136a..631d3f2 100644 --- a/sys/kern/vfs_subr.c +++ b/sys/kern/vfs_subr.c @@ -41,6 +41,7 @@ #include __FBSDID("$FreeBSD$"); =20 +#include "opt_compat.h" #include "opt_ddb.h" #include "opt_watchdog.h" =20 @@ -3111,21 +3112,49 @@ DB_SHOW_COMMAND(mount, db_show_mount) /* * Fill in a struct xvfsconf based on a struct vfsconf. */ -static void -vfsconf2x(struct vfsconf *vfsp, struct xvfsconf *xvfsp) +static int +vfsconf2x(struct sysctl_req *req, struct vfsconf *vfsp) { + struct xvfsconf xvfsp; =20 - strcpy(xvfsp->vfc_name, vfsp->vfc_name); - xvfsp->vfc_typenum =3D vfsp->vfc_typenum; - xvfsp->vfc_refcount =3D vfsp->vfc_refcount; - xvfsp->vfc_flags =3D vfsp->vfc_flags; + bzero(&xvfsp, sizeof(xvfsp)); + strcpy(xvfsp.vfc_name, vfsp->vfc_name); + xvfsp.vfc_typenum =3D vfsp->vfc_typenum; + xvfsp.vfc_refcount =3D vfsp->vfc_refcount; + xvfsp.vfc_flags =3D vfsp->vfc_flags; /* * These are unused in userland, we keep them * to not break binary compatibility. */ - xvfsp->vfc_vfsops =3D NULL; - xvfsp->vfc_next =3D NULL; + xvfsp.vfc_vfsops =3D NULL; + xvfsp.vfc_next =3D NULL; + return (SYSCTL_OUT(req, &xvfsp, sizeof(xvfsp))); +} + +#ifdef COMPAT_FREEBSD32 +struct xvfsconf32 { + uint32_t vfc_vfsops; + char vfc_name[MFSNAMELEN]; + int32_t vfc_typenum; + int32_t vfc_refcount; + int32_t vfc_flags; + uint32_t vfc_next; +}; + +static int +vfsconf2x32(struct sysctl_req *req, struct vfsconf *vfsp) +{ + struct xvfsconf32 xvfsp; + + strcpy(xvfsp.vfc_name, vfsp->vfc_name); + xvfsp.vfc_typenum =3D vfsp->vfc_typenum; + xvfsp.vfc_refcount =3D vfsp->vfc_refcount; + xvfsp.vfc_flags =3D vfsp->vfc_flags; + xvfsp.vfc_vfsops =3D 0; + xvfsp.vfc_next =3D 0; + return (SYSCTL_OUT(req, &xvfsp, sizeof(xvfsp))); } +#endif =20 /* * Top level filesystem related information gathering. @@ -3134,14 +3163,16 @@ static int sysctl_vfs_conflist(SYSCTL_HANDLER_ARGS) { struct vfsconf *vfsp; - struct xvfsconf xvfsp; int error; =20 error =3D 0; TAILQ_FOREACH(vfsp, &vfsconf, vfc_list) { - bzero(&xvfsp, sizeof(xvfsp)); - vfsconf2x(vfsp, &xvfsp); - error =3D SYSCTL_OUT(req, &xvfsp, sizeof xvfsp); +#ifdef COMPAT_FREEBSD32 + if (req->flags & SCTL_MASK32) + error =3D vfsconf2x32(req, vfsp); + else +#endif + error =3D vfsconf2x(req, vfsp); if (error) break; } @@ -3161,7 +3192,6 @@ vfs_sysctl(SYSCTL_HANDLER_ARGS) int *name =3D (int *)arg1 - 1; /* XXX */ u_int namelen =3D arg2 + 1; /* XXX */ struct vfsconf *vfsp; - struct xvfsconf xvfsp; =20 log(LOG_WARNING, "userland calling deprecated sysctl, " "please rebuild world\n"); @@ -3185,9 +3215,12 @@ vfs_sysctl(SYSCTL_HANDLER_ARGS) break; if (vfsp =3D=3D NULL) return (EOPNOTSUPP); - bzero(&xvfsp, sizeof(xvfsp)); - vfsconf2x(vfsp, &xvfsp); - return (SYSCTL_OUT(req, &xvfsp, sizeof(xvfsp))); +#ifdef COMPAT_FREEBSD32 + if (req->flags & SCTL_MASK32) + return (vfsconf2x32(req, vfsp)); + else +#endif + return (vfsconf2x(req, vfsp)); } return (EOPNOTSUPP); } --hblleJHDxiLJUoyx Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (FreeBSD) iEYEARECAAYFAlAyLi0ACgkQC3+MBN1Mb4gyRQCeNC9eH+7VtlGP6EgSdOrFANgf I7sAoNAGHbekSdJ5R8eSMlN+V5naO/ve =Oj1N -----END PGP SIGNATURE----- --hblleJHDxiLJUoyx-- From owner-freebsd-current@FreeBSD.ORG Mon Aug 20 13:21:41 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E588D106564A; Mon, 20 Aug 2012 13:21:41 +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 B5CB88FC23; Mon, 20 Aug 2012 13:21:41 +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 q7KDLer5080498; Mon, 20 Aug 2012 09:21:40 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-current.sentex.ca (8.14.5/8.14.5/Submit) id q7KDLe4T080490; Mon, 20 Aug 2012 13:21:40 GMT (envelope-from tinderbox@freebsd.org) Date: Mon, 20 Aug 2012 13:21:40 GMT Message-Id: <201208201321.q7KDLe4T080490@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 , , Precedence: bulk Cc: Subject: [head tinderbox] failure on i386/pc98 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Aug 2012 13:21:42 -0000 TB --- 2012-08-20 10:40:00 - tinderbox 2.9 running on freebsd-current.sentex.ca TB --- 2012-08-20 10:40:00 - 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 --- 2012-08-20 10:40:00 - starting HEAD tinderbox run for i386/pc98 TB --- 2012-08-20 10:40:00 - cleaning the object tree TB --- 2012-08-20 10:40:00 - cvsupping the source tree TB --- 2012-08-20 10:40:00 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/i386/pc98/supfile TB --- 2012-08-20 10:41:06 - building world TB --- 2012-08-20 10:41:06 - CROSS_BUILD_TESTING=YES TB --- 2012-08-20 10:41:06 - MAKEOBJDIRPREFIX=/obj TB --- 2012-08-20 10:41:06 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-08-20 10:41:06 - SRCCONF=/dev/null TB --- 2012-08-20 10:41:06 - TARGET=pc98 TB --- 2012-08-20 10:41:06 - TARGET_ARCH=i386 TB --- 2012-08-20 10:41:06 - TZ=UTC TB --- 2012-08-20 10:41:06 - __MAKE_CONF=/dev/null TB --- 2012-08-20 10:41:06 - cd /src TB --- 2012-08-20 10:41:06 - /usr/bin/make -B buildworld >>> World build started on Mon Aug 20 10:41:07 UTC 2012 >>> 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 Mon Aug 20 13:13:46 UTC 2012 TB --- 2012-08-20 13:13:46 - generating LINT kernel config TB --- 2012-08-20 13:13:46 - cd /src/sys/pc98/conf TB --- 2012-08-20 13:13:46 - /usr/bin/make -B LINT TB --- 2012-08-20 13:13:46 - cd /src/sys/pc98/conf TB --- 2012-08-20 13:13:46 - /usr/sbin/config -m LINT TB --- 2012-08-20 13:13:46 - building LINT kernel TB --- 2012-08-20 13:13:46 - CROSS_BUILD_TESTING=YES TB --- 2012-08-20 13:13:46 - MAKEOBJDIRPREFIX=/obj TB --- 2012-08-20 13:13:46 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-08-20 13:13:46 - SRCCONF=/dev/null TB --- 2012-08-20 13:13:46 - TARGET=pc98 TB --- 2012-08-20 13:13:46 - TARGET_ARCH=i386 TB --- 2012-08-20 13:13:46 - TZ=UTC TB --- 2012-08-20 13:13:46 - __MAKE_CONF=/dev/null TB --- 2012-08-20 13:13:46 - cd /src TB --- 2012-08-20 13:13:46 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Mon Aug 20 13:13:46 UTC 2012 >>> 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 -c -O2 -pipe -fno-strict-aliasing -std=c99 -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 -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-sse -msoft-float -ffreestanding -fstack-protector -Werror -pg -mprofiler-epilogue /src/sys/dev/ath/if_ath_tx.c -I/src/sys/dev/ath /src/sys/dev/ath/if_ath_tx.c: In function 'ath_tx_chaindesclist': /src/sys/dev/ath/if_ath_tx.c:379: error: 'ATH_DEBUG_XMIT' undeclared (first use in this function) /src/sys/dev/ath/if_ath_tx.c:379: error: (Each undeclared identifier is reported only once /src/sys/dev/ath/if_ath_tx.c:379: error: for each function it appears in.) cc1: warnings being treated as errors /src/sys/dev/ath/if_ath_tx.c:380: warning: implicit declaration of function 'ath_printtxbuf' /src/sys/dev/ath/if_ath_tx.c:380: warning: nested extern declaration of 'ath_printtxbuf' [-Wnested-externs] *** Error code 1 Stop in /obj/pc98.i386/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2012-08-20 13:21:40 - WARNING: /usr/bin/make returned exit code 1 TB --- 2012-08-20 13:21:40 - ERROR: failed to build LINT kernel TB --- 2012-08-20 13:21:40 - 6715.01 user 964.95 system 9699.93 real http://tinderbox.freebsd.org/tinderbox-head-HEAD-i386-pc98.full From owner-freebsd-current@FreeBSD.ORG Mon Aug 20 13:24:40 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1F7BC106566C; Mon, 20 Aug 2012 13:24:40 +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 DF1258FC16; Mon, 20 Aug 2012 13:24:39 +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 q7KDOdYV093843; Mon, 20 Aug 2012 09:24:39 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-current.sentex.ca (8.14.5/8.14.5/Submit) id q7KDOdUr093835; Mon, 20 Aug 2012 13:24:39 GMT (envelope-from tinderbox@freebsd.org) Date: Mon, 20 Aug 2012 13:24:39 GMT Message-Id: <201208201324.q7KDOdUr093835@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 , , Precedence: bulk Cc: Subject: [head tinderbox] failure on i386/i386 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Aug 2012 13:24:40 -0000 TB --- 2012-08-20 10:40:00 - tinderbox 2.9 running on freebsd-current.sentex.ca TB --- 2012-08-20 10:40:00 - 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 --- 2012-08-20 10:40:00 - starting HEAD tinderbox run for i386/i386 TB --- 2012-08-20 10:40:00 - cleaning the object tree TB --- 2012-08-20 10:40:00 - cvsupping the source tree TB --- 2012-08-20 10:40:00 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/i386/i386/supfile TB --- 2012-08-20 10:47:13 - building world TB --- 2012-08-20 10:47:13 - CROSS_BUILD_TESTING=YES TB --- 2012-08-20 10:47:13 - MAKEOBJDIRPREFIX=/obj TB --- 2012-08-20 10:47:13 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-08-20 10:47:13 - SRCCONF=/dev/null TB --- 2012-08-20 10:47:13 - TARGET=i386 TB --- 2012-08-20 10:47:13 - TARGET_ARCH=i386 TB --- 2012-08-20 10:47:13 - TZ=UTC TB --- 2012-08-20 10:47:13 - __MAKE_CONF=/dev/null TB --- 2012-08-20 10:47:13 - cd /src TB --- 2012-08-20 10:47:13 - /usr/bin/make -B buildworld >>> World build started on Mon Aug 20 10:47:14 UTC 2012 >>> 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 Mon Aug 20 13:15:30 UTC 2012 TB --- 2012-08-20 13:15:30 - generating LINT kernel config TB --- 2012-08-20 13:15:30 - cd /src/sys/i386/conf TB --- 2012-08-20 13:15:30 - /usr/bin/make -B LINT TB --- 2012-08-20 13:15:31 - cd /src/sys/i386/conf TB --- 2012-08-20 13:15:31 - /usr/sbin/config -m LINT TB --- 2012-08-20 13:15:31 - building LINT kernel TB --- 2012-08-20 13:15:31 - CROSS_BUILD_TESTING=YES TB --- 2012-08-20 13:15:31 - MAKEOBJDIRPREFIX=/obj TB --- 2012-08-20 13:15:31 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-08-20 13:15:31 - SRCCONF=/dev/null TB --- 2012-08-20 13:15:31 - TARGET=i386 TB --- 2012-08-20 13:15:31 - TARGET_ARCH=i386 TB --- 2012-08-20 13:15:31 - TZ=UTC TB --- 2012-08-20 13:15:31 - __MAKE_CONF=/dev/null TB --- 2012-08-20 13:15:31 - cd /src TB --- 2012-08-20 13:15:31 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Mon Aug 20 13:15:31 UTC 2012 >>> 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 -c -O2 -pipe -fno-strict-aliasing -std=c99 -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 -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-sse -msoft-float -ffreestanding -fstack-protector -Werror -pg -mprofiler-epilogue /src/sys/dev/ath/if_ath_tx.c -I/src/sys/dev/ath /src/sys/dev/ath/if_ath_tx.c: In function 'ath_tx_chaindesclist': /src/sys/dev/ath/if_ath_tx.c:379: error: 'ATH_DEBUG_XMIT' undeclared (first use in this function) /src/sys/dev/ath/if_ath_tx.c:379: error: (Each undeclared identifier is reported only once /src/sys/dev/ath/if_ath_tx.c:379: error: for each function it appears in.) cc1: warnings being treated as errors /src/sys/dev/ath/if_ath_tx.c:380: warning: implicit declaration of function 'ath_printtxbuf' /src/sys/dev/ath/if_ath_tx.c:380: warning: nested extern declaration of 'ath_printtxbuf' [-Wnested-externs] *** Error code 1 Stop in /obj/i386.i386/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2012-08-20 13:24:39 - WARNING: /usr/bin/make returned exit code 1 TB --- 2012-08-20 13:24:39 - ERROR: failed to build LINT kernel TB --- 2012-08-20 13:24:39 - 6804.70 user 970.36 system 9878.36 real http://tinderbox.freebsd.org/tinderbox-head-HEAD-i386-i386.full From owner-freebsd-current@FreeBSD.ORG Mon Aug 20 13:32:21 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D0144106566C; Mon, 20 Aug 2012 13:32:21 +0000 (UTC) (envelope-from mavbsd@gmail.com) Received: from mail-ey0-f182.google.com (mail-ey0-f182.google.com [209.85.215.182]) by mx1.freebsd.org (Postfix) with ESMTP id D01BB8FC15; Mon, 20 Aug 2012 13:32:20 +0000 (UTC) Received: by eaak11 with SMTP id k11so2136001eaa.13 for ; Mon, 20 Aug 2012 06:32:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=UUQ999bsigvjylyqCfIotwsOZq7twjh4eLJi7RPUW/g=; b=vB/+dVHf9t23S+GZj8UIUvY8Cz0/Lqztt5UjGxcvSXGIKri9sv3ZanmmAI37UGwMt5 n+V4/A+cTSh3zZKLKuIEER3oAf33XwGCwjVlRAriO+ATGLk2qWHTXgIVN5dZ73U1xuTp JzcbqpE4oLLtkAj0VLYuh32Kgxa4RJ4jAUprmsE2ahlVxtDGwOtBTW9OZZP27gRSLzp9 4loluZkW4+iENrGWScXTohbrLdJtHWHJXU9TMXvnl5ZRLZNdMNaDu9tqrcWAK2+rhwZo F4SICluGP9oMx1cAJXHjiSR8TT4OSssaYKCcr4vLPHseBIhHCuK0mq2YY5Qn21+MuKzy Gaiw== Received: by 10.14.219.198 with SMTP id m46mr8708579eep.18.1345469539533; Mon, 20 Aug 2012 06:32:19 -0700 (PDT) Received: from mavbook.mavhome.dp.ua ([91.198.175.1]) by mx.google.com with ESMTPS id y1sm42026154eel.0.2012.08.20.06.32.17 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 20 Aug 2012 06:32:18 -0700 (PDT) Sender: Alexander Motin Message-ID: <50323C5F.5090109@FreeBSD.org> Date: Mon, 20 Aug 2012 16:32:15 +0300 From: Alexander Motin User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:13.0) Gecko/20120628 Thunderbird/13.0.1 MIME-Version: 1.0 To: Doug Barton References: <157941699.20120815004542@serebryakov.spb.ru> <502AE8B5.9090106@FreeBSD.org> <502B775D.7000101@FreeBSD.org> <5031F636.1020405@FreeBSD.org> <50320A9E.5070303@FreeBSD.org> <503210A1.7010803@FreeBSD.org> In-Reply-To: <503210A1.7010803@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Adrian Chadd , lev@freebsd.org, current@freebsd.org Subject: Re: CURRENT as gateway on not-so-fast hardware: where is a bottlneck? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 20 Aug 2012 13:32:22 -0000 On 20.08.2012 13:25, Doug Barton wrote: > On 08/20/2012 02:59, Alexander Motin wrote: >> On 20.08.2012 11:32, Doug Barton wrote: >>> On 08/15/2012 03:18, Alexander Motin wrote: >>>> On 15.08.2012 03:09, Doug Barton wrote: >>>>> On 08/14/2012 12:20 PM, Adrian Chadd wrote: >>>>>> Would you be willing to compile a kernel with KTR so you can capture >>>>>> some KTR scheduler dumps? >>>>>> >>>>>> That way the scheduler peeps can feed this into schedgraph.py (and you >>>>>> can too!) to figure out what's going on. >>>>>> >>>>>> Maybe things aren't being scheduled correctly and the added latency is >>>>>> killing performance? >>>>> >>>>> You might also try switching to SCHED_ULE to see if it helps. >>>>> >>>>> Although, in the last few months as mav has been converging the 2 I've >>>>> started to see the same problems I saw on my desktop systems previously >>>>> re-appear even using ULE. For example, if I'm watching an AVI with VLC >>>>> and start doing anything that generates a lot of interrupts (like >>>>> moving >>>>> large quantities of data from one disk to another) the video and sound >>>>> start to skip. Also, various other desktop features (like menus, window >>>>> switching, etc.) start to take measurable time to happen, sometimes >>>>> seconds. >>>>> >>>>> ... and lest you think this is just a desktop problem, I've seen the >>>>> same scenario on 8.x systems used as web servers. With ULE they were >>>>> frequently getting into peak load situations that created what I called >>>>> "mini thundering herd" problems where they could never quite get caught >>>>> up. Whereas switching to 4BSD the same servers got into high-load >>>>> situations less often, and they recovered on their own in minutes. >>>> >>>> It is quite pointless to speculate without real info like mentioned >>>> above KTR_SCHED traces. >>> >>> I'm sorry, you're quite wrong about that. In the cases I mentioned, and >>> in about 2 out of 3 of the cases where users reported problems and I >>> suggested that they try 4BSD, the results were clear. This obviously >>> points out that there is a serious problem with ULE, and if I were the >>> one who was responsible for that code I would be looking at ways of >>> helping users figure out where the problems are. But that's just me. >> >> I am not telling anything bad about 4BSD. > > Yes, I get that, but thanks for making it clear. > >> Choice is provided because >> they are indeed different and none is perfect. > > ... which is why I'm asking you to stop making them more the same until > we get a better idea of what the issues are. I have no plans to converge them. I've just found problem in ULE, that was replicated into 4BSD and it would be strange to fix one without another. But fixing it exposed another old problem specific to 4BSD, which I fixed reusing logically equivalent code from ULE. I saw no reason to reinvent a wheel there, same as to not fix obvious bug. Sure, it can change behavior in some way, but ULE is not guilty. -- Alexander Motin From owner-freebsd-current@FreeBSD.ORG Mon Aug 20 13:49:49 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4B854106564A; Mon, 20 Aug 2012 13:49:49 +0000 (UTC) (envelope-from monthadar@gmail.com) Received: from mail-pb0-f54.google.com (mail-pb0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id 19BCF8FC0C; Mon, 20 Aug 2012 13:49:48 +0000 (UTC) Received: by pbbrp2 with SMTP id rp2so7362304pbb.13 for ; Mon, 20 Aug 2012 06:49:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=FNSChAwdg/d23OASFliW0+j93Aqu3UnhOw9Qdy0A7vw=; b=HsSAlmbmVXDQ54PiWdWXr5mQiKC/q4YjaNcJnk2Lp3dGjzYVttFulEaoQpgG9ojTKL Iuzw7pL7THr/Urctw0R+fVjAmCPUMpyLZJ/or8Qam2ezhmwAsq1PeOEUTsEbigWk9Gzd nxA6H4mtLChYhIHNpSC3Xeb9efrWP2/5JcOCb5kWIsVzLa4LCUg3SUphMpZnwVpimYFQ DjZUW6SEv8MvzVc7WS6FqlMyZ1fZmodmfYflnfcYUZpGfTrMA6kYhVV44HKQdhD1tV2u a4jkU/JBFs6qL1FF1bhfGNxfOaMg/IhcnwsPuf9iEMWCLMwT3r/i1HuxFpNrzjnkBvqt 6IMQ== MIME-Version: 1.0 Received: by 10.66.87.66 with SMTP id v2mr29711977paz.71.1345470588217; Mon, 20 Aug 2012 06:49:48 -0700 (PDT) Received: by 10.68.32.197 with HTTP; Mon, 20 Aug 2012 06:49:48 -0700 (PDT) In-Reply-To: <201208200804.31932.jhb@freebsd.org> References: <201208200804.31932.jhb@freebsd.org> Date: Mon, 20 Aug 2012 15:49:48 +0200 Message-ID: From: Monthadar Al Jaberi To: John Baldwin Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-current@freebsd.org Subject: Re: kernel page fult for a valid pointer? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 20 Aug 2012 13:49:49 -0000 On Mon, Aug 20, 2012 at 2:04 PM, John Baldwin wrote: > On Saturday, August 18, 2012 2:29:26 pm Monthadar Al Jaberi wrote: >> Hi, >> >> I am wondering is there a reason for getting "Fatal trap 12: page >> fault while in kernel mode" "supervisor read, page not present" for an >> address used to be valid in kernel space? >> >> I dont really understand why I am getting this, I added a hardware >> watchpoint on the address, and when I got to the debuger I could read >> the memory content and dump for that address. But when I continue from >> the debugger I get the panic and now when I try to read the memory >> content I get *** error reading from address ce733000 ***. > > Whatever memory was there might have been unmapped? For example, > memory pointed to by I/O buffers (struct buf/bio) use transient > mappings that are only valid while an I/O request is in progress. Thank you the for the reply, so if a struct gets freed will the page it was on get un-mapped, so that I cant dump it in debugger? Even VirtualBox debugger cant dump the memory giving "VERR_PAGE_TABLE_NOT_PRESENT: Reading memory at...". In my case it is a struct ieee80211_node which gets freed, but where does the page get unmaped? I tried doubling the memory in VirtualBox. br, > > -- > John Baldwin -- Monthadar Al Jaberi From owner-freebsd-current@FreeBSD.ORG Mon Aug 20 13:58:41 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CD10F106564A; Mon, 20 Aug 2012 13:58:41 +0000 (UTC) (envelope-from mj@feral.com) Received: from ns1.feral.com (ns1.feral.com [192.67.166.1]) by mx1.freebsd.org (Postfix) with ESMTP id 7FFA88FC19; Mon, 20 Aug 2012 13:58:41 +0000 (UTC) Received: from [192.168.135.103] (c-24-5-173-152.hsd1.ca.comcast.net [24.5.173.152]) (authenticated bits=0) by ns1.feral.com (8.14.4/8.14.4) with ESMTP id q7KDwX6q078221 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Mon, 20 Aug 2012 06:58:34 -0700 (PDT) (envelope-from mj@feral.com) Message-ID: <50324284.2080305@feral.com> Date: Mon, 20 Aug 2012 06:58:28 -0700 From: Matthew Jacob Organization: Feral Software User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0 MIME-Version: 1.0 To: John Baldwin References: <6800.1345323911@critter.freebsd.dk> <201208200824.38500.jhb@freebsd.org> In-Reply-To: <201208200824.38500.jhb@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (ns1.feral.com [192.67.166.1]); Mon, 20 Aug 2012 06:58:35 -0700 (PDT) Cc: Poul-Henning Kamp , freebsd-current@freebsd.org, Matt Jacob Subject: Re: BUFSIZ = 1024, still ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: mj@feral.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Aug 2012 13:58:41 -0000 On 8/20/2012 5:24 AM, John Baldwin wrote: > On Saturday, August 18, 2012 5:05:11 pm Poul-Henning Kamp wrote: >> In message <5030033B.4060705@feral.com>, Matthew Jacob writes: >>> On 8/18/2012 1:32 PM, Poul-Henning Kamp wrote: >>>> Shouldn't we at least increase it to pagesize ? >>>> >>> What data suggests to you it would be better at pagesize? >> The number of system calls to fwrite() a big file ? > Have you looked at an actual ktrace? :) stdio doesn't use BUFSIZ for > regular files: > > head/lib/libc/stdio/makebuf.c: > /* > * Internal routine to determine `proper' buffering for a file. > */ > int > __swhatbuf(fp, bufsize, couldbetty) > FILE *fp; > size_t *bufsize; > int *couldbetty; > { > struct stat st; > > if (fp->_file < 0 || _fstat(fp->_file, &st) < 0) { > ... > *bufsize = BUFSIZ; > return (__SNPT); > } > > ... > if (st.st_blksize <= 0) { > *bufsize = BUFSIZ; > return (__SNPT); > } > > *bufsize = st.st_blksize; > ... > } > > For a regular file stdio will use the filesystem's block size, not BUFSIZ. > > Test program: > > #include > #include > > int > main(int ac, char **av) > { > char junk; > FILE *fp; > int i; > > fp = fopen("/tmp/junk", "w"); > if (fp == NULL) > err(1, "fopen"); > for (i = 0; i < 1024 * 1024; i++) > if (fwrite(&junk, sizeof(junk), 1, fp) != 1) > errx(1, "fwrite failed"); > return (0); > } > > ktrace excerpt: > > 42599 a.out CALL write(0x3,0x800a04000,0x4000) > 42599 a.out RET write 16384/0x4000 > 42599 a.out CALL write(0x3,0x800a04000,0x4000) > 42599 a.out RET write 16384/0x4000 > 42599 a.out CALL write(0x3,0x800a04000,0x4000) > 42599 a.out RET write 16384/0x4000 > 42599 a.out CALL write(0x3,0x800a04000,0x4000) > 42599 a.out RET write 16384/0x4000 > 42599 a.out CALL write(0x3,0x800a04000,0x4000) > 42599 a.out RET write 16384/0x4000 > 42599 a.out CALL write(0x3,0x800a04000,0x4000) > 42599 a.out RET write 16384/0x4000 > > This hint also works for pipes (they set st_blksize to PAGE_SIZE). Given > that, I think BUFSIZ should just be left alone. > Perfect. Data. From owner-freebsd-current@FreeBSD.ORG Mon Aug 20 13:59:01 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 031BE106566C; Mon, 20 Aug 2012 13:59:01 +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 C5AFB8FC15; Mon, 20 Aug 2012 13:59:00 +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 q7KDx0oB062928; Mon, 20 Aug 2012 09:59:00 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-current.sentex.ca (8.14.5/8.14.5/Submit) id q7KDx03b062927; Mon, 20 Aug 2012 13:59:00 GMT (envelope-from tinderbox@freebsd.org) Date: Mon, 20 Aug 2012 13:59:00 GMT Message-Id: <201208201359.q7KDx03b062927@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 , , Precedence: bulk Cc: Subject: [head tinderbox] failure on amd64/amd64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Aug 2012 13:59:01 -0000 TB --- 2012-08-20 10:40:00 - tinderbox 2.9 running on freebsd-current.sentex.ca TB --- 2012-08-20 10:40:00 - 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 --- 2012-08-20 10:40:00 - starting HEAD tinderbox run for amd64/amd64 TB --- 2012-08-20 10:40:00 - cleaning the object tree TB --- 2012-08-20 10:40:00 - cvsupping the source tree TB --- 2012-08-20 10:40:00 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/amd64/amd64/supfile TB --- 2012-08-20 10:41:03 - building world TB --- 2012-08-20 10:41:03 - CROSS_BUILD_TESTING=YES TB --- 2012-08-20 10:41:03 - MAKEOBJDIRPREFIX=/obj TB --- 2012-08-20 10:41:03 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-08-20 10:41:03 - SRCCONF=/dev/null TB --- 2012-08-20 10:41:03 - TARGET=amd64 TB --- 2012-08-20 10:41:03 - TARGET_ARCH=amd64 TB --- 2012-08-20 10:41:03 - TZ=UTC TB --- 2012-08-20 10:41:03 - __MAKE_CONF=/dev/null TB --- 2012-08-20 10:41:03 - cd /src TB --- 2012-08-20 10:41:03 - /usr/bin/make -B buildworld >>> World build started on Mon Aug 20 10:41:04 UTC 2012 >>> 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 >>> stage 5.1: building 32 bit shim libraries >>> World build completed on Mon Aug 20 13:50:41 UTC 2012 TB --- 2012-08-20 13:50:41 - generating LINT kernel config TB --- 2012-08-20 13:50:41 - cd /src/sys/amd64/conf TB --- 2012-08-20 13:50:41 - /usr/bin/make -B LINT TB --- 2012-08-20 13:50:41 - cd /src/sys/amd64/conf TB --- 2012-08-20 13:50:41 - /usr/sbin/config -m LINT TB --- 2012-08-20 13:50:41 - building LINT kernel TB --- 2012-08-20 13:50:41 - CROSS_BUILD_TESTING=YES TB --- 2012-08-20 13:50:41 - MAKEOBJDIRPREFIX=/obj TB --- 2012-08-20 13:50:41 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-08-20 13:50:41 - SRCCONF=/dev/null TB --- 2012-08-20 13:50:41 - TARGET=amd64 TB --- 2012-08-20 13:50:41 - TARGET_ARCH=amd64 TB --- 2012-08-20 13:50:41 - TZ=UTC TB --- 2012-08-20 13:50:41 - __MAKE_CONF=/dev/null TB --- 2012-08-20 13:50:41 - cd /src TB --- 2012-08-20 13:50:41 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Mon Aug 20 13:50:41 UTC 2012 >>> 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 -c -O2 -frename-registers -pipe -fno-strict-aliasing -std=c99 -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 -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -Werror -pg -mprofiler-epilogue /src/sys/dev/ath/if_ath_tx.c -I/src/sys/dev/ath /src/sys/dev/ath/if_ath_tx.c: In function 'ath_tx_chaindesclist': /src/sys/dev/ath/if_ath_tx.c:379: error: 'ATH_DEBUG_XMIT' undeclared (first use in this function) /src/sys/dev/ath/if_ath_tx.c:379: error: (Each undeclared identifier is reported only once /src/sys/dev/ath/if_ath_tx.c:379: error: for each function it appears in.) cc1: warnings being treated as errors /src/sys/dev/ath/if_ath_tx.c:380: warning: implicit declaration of function 'ath_printtxbuf' /src/sys/dev/ath/if_ath_tx.c:380: warning: nested extern declaration of 'ath_printtxbuf' [-Wnested-externs] *** Error code 1 Stop in /obj/amd64.amd64/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2012-08-20 13:58:59 - WARNING: /usr/bin/make returned exit code 1 TB --- 2012-08-20 13:58:59 - ERROR: failed to build LINT kernel TB --- 2012-08-20 13:58:59 - 8246.30 user 1307.34 system 11939.17 real http://tinderbox.freebsd.org/tinderbox-head-HEAD-amd64-amd64.full From owner-freebsd-current@FreeBSD.ORG Mon Aug 20 14:01:23 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 752481065674; Mon, 20 Aug 2012 14:01:23 +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 3B8338FC22; Mon, 20 Aug 2012 14:01:22 +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 q7KE1MUc076861; Mon, 20 Aug 2012 10:01:22 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-current.sentex.ca (8.14.5/8.14.5/Submit) id q7KE1MmD076853; Mon, 20 Aug 2012 14:01:22 GMT (envelope-from tinderbox@freebsd.org) Date: Mon, 20 Aug 2012 14:01:22 GMT Message-Id: <201208201401.q7KE1MmD076853@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 , , Precedence: bulk Cc: Subject: [head tinderbox] failure on ia64/ia64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Aug 2012 14:01:23 -0000 TB --- 2012-08-20 12:12:32 - tinderbox 2.9 running on freebsd-current.sentex.ca TB --- 2012-08-20 12:12:32 - 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 --- 2012-08-20 12:12:32 - starting HEAD tinderbox run for ia64/ia64 TB --- 2012-08-20 12:12:32 - cleaning the object tree TB --- 2012-08-20 12:12:32 - cvsupping the source tree TB --- 2012-08-20 12:12:32 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/ia64/ia64/supfile TB --- 2012-08-20 12:13:11 - building world TB --- 2012-08-20 12:13:11 - CROSS_BUILD_TESTING=YES TB --- 2012-08-20 12:13:11 - MAKEOBJDIRPREFIX=/obj TB --- 2012-08-20 12:13:11 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-08-20 12:13:11 - SRCCONF=/dev/null TB --- 2012-08-20 12:13:11 - TARGET=ia64 TB --- 2012-08-20 12:13:11 - TARGET_ARCH=ia64 TB --- 2012-08-20 12:13:11 - TZ=UTC TB --- 2012-08-20 12:13:11 - __MAKE_CONF=/dev/null TB --- 2012-08-20 12:13:11 - cd /src TB --- 2012-08-20 12:13:11 - /usr/bin/make -B buildworld >>> World build started on Mon Aug 20 12:13:12 UTC 2012 >>> 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 Mon Aug 20 13:54:27 UTC 2012 TB --- 2012-08-20 13:54:27 - generating LINT kernel config TB --- 2012-08-20 13:54:27 - cd /src/sys/ia64/conf TB --- 2012-08-20 13:54:27 - /usr/bin/make -B LINT TB --- 2012-08-20 13:54:27 - cd /src/sys/ia64/conf TB --- 2012-08-20 13:54:27 - /usr/sbin/config -m LINT TB --- 2012-08-20 13:54:27 - building LINT kernel TB --- 2012-08-20 13:54:27 - CROSS_BUILD_TESTING=YES TB --- 2012-08-20 13:54:27 - MAKEOBJDIRPREFIX=/obj TB --- 2012-08-20 13:54:27 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-08-20 13:54:27 - SRCCONF=/dev/null TB --- 2012-08-20 13:54:27 - TARGET=ia64 TB --- 2012-08-20 13:54:27 - TARGET_ARCH=ia64 TB --- 2012-08-20 13:54:27 - TZ=UTC TB --- 2012-08-20 13:54:27 - __MAKE_CONF=/dev/null TB --- 2012-08-20 13:54:27 - cd /src TB --- 2012-08-20 13:54:27 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Mon Aug 20 13:54:27 UTC 2012 >>> 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 -c -O2 -pipe -fno-strict-aliasing -std=c99 -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 -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/ia64/libuwx/src -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mconstant-gp -ffixed-r13 -mfixed-range=f32-f127 -fpic -ffreestanding -Werror /src/sys/dev/ath/if_ath_tx.c -I/src/sys/dev/ath /src/sys/dev/ath/if_ath_tx.c: In function 'ath_tx_chaindesclist': /src/sys/dev/ath/if_ath_tx.c:379: error: 'ATH_DEBUG_XMIT' undeclared (first use in this function) /src/sys/dev/ath/if_ath_tx.c:379: error: (Each undeclared identifier is reported only once /src/sys/dev/ath/if_ath_tx.c:379: error: for each function it appears in.) cc1: warnings being treated as errors /src/sys/dev/ath/if_ath_tx.c:380: warning: implicit declaration of function 'ath_printtxbuf' /src/sys/dev/ath/if_ath_tx.c:380: warning: nested extern declaration of 'ath_printtxbuf' [-Wnested-externs] *** Error code 1 Stop in /obj/ia64.ia64/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2012-08-20 14:01:22 - WARNING: /usr/bin/make returned exit code 1 TB --- 2012-08-20 14:01:22 - ERROR: failed to build LINT kernel TB --- 2012-08-20 14:01:22 - 4557.75 user 713.62 system 6530.21 real http://tinderbox.freebsd.org/tinderbox-head-HEAD-ia64-ia64.full From owner-freebsd-current@FreeBSD.ORG Mon Aug 20 14:27:11 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DE1D0106566B; Mon, 20 Aug 2012 14:27:11 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-pb0-f54.google.com (mail-pb0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id A54DE8FC27; Mon, 20 Aug 2012 14:27:10 +0000 (UTC) Received: by pbbrp2 with SMTP id rp2so7412590pbb.13 for ; Mon, 20 Aug 2012 07:27:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=RvHZ3Jc9YFfcHGjtLS6nO7JQeAQnAfSdEAx8gDwpLXs=; b=dU319/i/UlJxS+sk4Vx8j8IvA/CGz6w62NeYeYKMNopeOd9a469UjLVtfWzlYQVwkq vUmvoHEDhuENHPVrjRbR0BjHFoGvVoiyqTxNg+V8Sjvgshz0NAQDxCCfefU8NWKJDEg8 4epKBiQe3lHyEx7raEQ/54o6ksFOyxqS8FkzUQCccO/UhXbNQ7DL0Czr39oE3z6UhMYO sxnK+cPyPcKxISKHO50ljJisrM5nFcbbeWWTgIY3UdtiM5Me3Y2vSP92L/yuUcvuRgQ7 Q2S5tG/eQzls2Q6p1XTc4bziFtKTEDq9M2AbMcQYf8IHXldYzoFaUc2HoPFoUr4X3LG8 qXJg== MIME-Version: 1.0 Received: by 10.68.136.40 with SMTP id px8mr34774915pbb.153.1345472830376; Mon, 20 Aug 2012 07:27:10 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.68.43.169 with HTTP; Mon, 20 Aug 2012 07:27:10 -0700 (PDT) In-Reply-To: <201208201359.q7KDx03b062927@freebsd-current.sentex.ca> References: <201208201359.q7KDx03b062927@freebsd-current.sentex.ca> Date: Mon, 20 Aug 2012 07:27:10 -0700 X-Google-Sender-Auth: Q_59Mr3G1IcMSmaNeMfHuOy9Cwg Message-ID: From: Adrian Chadd To: FreeBSD Tinderbox Content-Type: text/plain; charset=ISO-8859-1 Cc: amd64@freebsd.org, current@freebsd.org Subject: Re: [head tinderbox] failure on amd64/amd64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 20 Aug 2012 14:27:12 -0000 ... I'll fix that. Honestly, it built for me.. Adrian From owner-freebsd-current@FreeBSD.ORG Mon Aug 20 14:27:35 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F0A4610656D8 for ; Mon, 20 Aug 2012 14:27:34 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-pz0-f54.google.com (mail-pz0-f54.google.com [209.85.210.54]) by mx1.freebsd.org (Postfix) with ESMTP id C32C98FC18 for ; Mon, 20 Aug 2012 14:27:34 +0000 (UTC) Received: by dadr6 with SMTP id r6so2337917dad.13 for ; Mon, 20 Aug 2012 07:27:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=nWa3QMYMk3R/tCKeqWzu8Rhb8O6Er6UL1VUUug2M0IM=; b=uxAoxLt/aNOHC+ZDDMXT1y/TMqdQA8qMoIJYcmZsi7qzxQD3KMq7B8MOw8g1hxZ/Do 2/md/LkePZCmYhvNjC+IHYAEBRxOGBTgS1pd1zSZTtBs9NnE9gqh7YzZhlpmQWP2YLqR ve5xMyQgdA3390GoldEliymKJPXryMe6RHjQ2aPjFn93HpJr6TMIAcA/vyC76TIksjis U1An/DmZ3jVD7Sami4Uim68mzVSmXNFqAQ9DyUgAO4a84GHBPl6olYnJC0xjI8H2xOFb hsJ3HbXWU2Gm2cnnugl3CvsaDcOLdfMBzteVzgvC7gQQAYctkIPwK/p8MSZQ/himEHGq O6ug== MIME-Version: 1.0 Received: by 10.68.231.233 with SMTP id tj9mr34810385pbc.39.1345472854114; Mon, 20 Aug 2012 07:27:34 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.68.43.169 with HTTP; Mon, 20 Aug 2012 07:27:34 -0700 (PDT) In-Reply-To: <20120820120925.GE1415@albert.catwhisker.org> References: <20120820120925.GE1415@albert.catwhisker.org> Date: Mon, 20 Aug 2012 07:27:34 -0700 X-Google-Sender-Auth: dEvVofuJz4X-uKAu-dEKrOufVjQ Message-ID: From: Adrian Chadd To: David Wolfskill Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: current@freebsd.org Subject: Re: FreeBSD buildkernel fails @r239409 in sys/dev/ath/if_ath_tx.c X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 20 Aug 2012 14:27:35 -0000 Yup, I forgot an #ifdef ATH_DEBUG. I'll fix it shortly. Adrian On 20 August 2012 05:09, David Wolfskill wrote: > This is using clang: > > ... >>>> stage 3.2: building everything > cd /usr/obj/usr/src/sys/CANARY; MAKEOBJDIRPREFIX=3D/usr/obj MACHINE_ARCH= =3Di386 MACHINE=3Di386 CPUTYPE=3D GROFF_BIN_PATH=3D/usr/obj/usr/src/tmp/l= egacy/usr/bin GROFF_FONT_PATH=3D/usr/obj/usr/src/tmp/legacy/usr/share/grof= f_font GROFF_TMAC_PATH=3D/usr/obj/usr/src/tmp/legacy/usr/share/tmac _SHLI= BDIRPREFIX=3D/usr/obj/usr/src/tmp _LDSCRIPTROOT=3D VERSION=3D"FreeBSD 10.= 0-CURRENT i386 1000017" INSTALL=3D"sh /usr/src/tools/install.sh" PATH=3D/= usr/obj/usr/src/tmp/legacy/usr/sbin:/usr/obj/usr/src/tmp/legacy/usr/bin:/us= r/obj/usr/src/tmp/legacy/usr/games:/usr/obj/usr/src/tmp/usr/sbin:/usr/obj/u= sr/src/tmp/usr/bin:/usr/obj/usr/src/tmp/usr/games:/sbin:/bin:/usr/sbin:/usr= /bin /usr/obj/usr/src/make.i386/make KERNEL=3Dkernel all -DNO_MODULES_OBJ > clang -c -O -pipe -std=3Dc99 -g -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 -Wno-error-tautological-compare -Wno-error-empt= y-body -Wno-error-parentheses-equality -nostdinc -I. -I/usr/src/sys -I/us= r/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_= global.h -mno-aes -mno-avx -mno-mmx -mno-sse -msoft-float -ffreestanding -= fstack-protector -Werror /usr/src/sys/dev/ath/if_ath_tx.c -I/usr/src/sys/d= ev/ath > /usr/src/sys/dev/ath/if_ath_tx.c:379:22: error: use of undeclared identif= ier > 'ATH_DEBUG_XMIT' > if (sc->sc_debug & ATH_DEBUG_XMIT) > ^ > /usr/src/sys/dev/ath/if_ath_tx.c:380:4: error: implicit declaration of fu= nction > 'ath_printtxbuf' is invalid in C99 > [-Werror,-Wimplicit-function-declaration] > ath_printtxbuf(sc, bf, qnum, 0, 0); > ^ > 2 errors generated. > *** [if_ath_tx.o] Error code 1 > > Stop in /common/S4/obj/usr/src/sys/CANARY. > *** [buildkernel] Error code 1 > > Stop in /usr/src. > *** [buildkernel] Error code 1 > > Stop in /usr/src. > > Peace, > david > -- > David H. Wolfskill david@catwhisker.org > Depriving a girl or boy of an opportunity for education is evil. > > See http://www.catwhisker.org/~david/publickey.gpg for my public key. From owner-freebsd-current@FreeBSD.ORG Mon Aug 20 15:17:00 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8CDEF10656D2 for ; Mon, 20 Aug 2012 15:17:00 +0000 (UTC) (envelope-from decke@bluelife.at) Received: from mail-wi0-f178.google.com (mail-wi0-f178.google.com [209.85.212.178]) by mx1.freebsd.org (Postfix) with ESMTP id 0B95F8FC08 for ; Mon, 20 Aug 2012 15:16:59 +0000 (UTC) Received: by wibhr14 with SMTP id hr14so3038889wib.13 for ; Mon, 20 Aug 2012 08:16:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bluelife.at; s=google; h=mime-version:sender:x-originating-ip:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=TcJw8fMcpRAgeL9Sa70wdSQFdIGhYZgNYSycxNrHuUo=; b=Zqz/dpHydT3UE/efhs2xNt4+dUVQVzFoOLwMBrTpz3dvO5pNe2XdNviT/ZQWDEFxz5 Cr2GujW3Rm5pspfsAREHAHzbY3NT2xHtFWUe5lEbR1ZqoE3bHVdF4beTAAisxukPzTsN R7pzgkqoP71XNj+EdCWxIbRy/5Ixnnu87Xukg= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:sender:x-originating-ip:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :x-gm-message-state; bh=TcJw8fMcpRAgeL9Sa70wdSQFdIGhYZgNYSycxNrHuUo=; b=K/NaSHzmI9r4+paTlHNGyecKbptKFJzxUKV2FNLg+e7FIiSbV/P2eC7uw2VgRa5ZDl KdgBMD6it/P67BXrVU8iIU9Ri79ZaLKlfw3VMPx44tBdmrcUYs0W769MQVHsbAgD9Ytp pTLpBmxVvvRurjWiP9wZRLFwZoB48FvK0sc8mQ0/fGEUpK69dTZG3NKlnidVR+lYSH0C ugfPyLydYOYxnfXaKcnz5Ek730PV5CTF0Ykr6gadcxserg3XtdHnDx5cXGP5U0+bGW86 ZKLTU6SDpnL5VGzk9fuVv+6jBpWuALiUB7ND+D7JfppFdKThy6jErwJHjLxtw5strVej ipuA== MIME-Version: 1.0 Received: by 10.216.52.213 with SMTP id e63mr6982454wec.205.1345475818724; Mon, 20 Aug 2012 08:16:58 -0700 (PDT) Sender: decke@bluelife.at Received: by 10.180.90.15 with HTTP; Mon, 20 Aug 2012 08:16:58 -0700 (PDT) X-Originating-IP: [80.123.233.199] In-Reply-To: <20120820123142.GY33100@deviant.kiev.zoral.com.ua> References: <20120812132047.GA33526@psconsult.nl> <20120820123142.GY33100@deviant.kiev.zoral.com.ua> Date: Mon, 20 Aug 2012 17:16:58 +0200 X-Google-Sender-Auth: zYSQpY6rBG0L91XsnGh_7ucuGdo Message-ID: From: =?ISO-8859-1?Q?Bernhard_Fr=F6hlich?= To: Konstantin Belousov Content-Type: text/plain; charset=ISO-8859-1 X-Gm-Message-State: ALoCoQkmenx7txoHoNKC/ZYyyE36dZHFgLHsCqlXaptElBooi+KxkgoYjmmo5ImuNHRHA2cJXvSD Cc: Garrett Cooper , Current FreeBSD , Paul Schenkeveld Subject: Re: make package fails in chroot: tar: getvfsbyname failed: No such file or directory X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 20 Aug 2012 15:17:00 -0000 On Mon, Aug 20, 2012 at 2:31 PM, Konstantin Belousov wrote: > On Mon, Aug 20, 2012 at 01:42:31PM +0200, Bernhard Fr?hlich wrote: >> On Sun, Aug 19, 2012 at 10:01 PM, Tim Kientzle wrote: >> > >> > On Aug 19, 2012, at 12:17 PM, Garrett Cooper wrote: >> > >> >> On Sun, Aug 19, 2012 at 9:45 AM, Tim Kientzle wrote: >> >>> >> >>> On Aug 12, 2012, at 6:20 AM, Paul Schenkeveld wrote: >> >>> >> >>>> Hi, >> >>>> >> >>>> I have a wrapper script that builds packages in a chroot environment >> >>>> which happily runs on release 6 thru 9 and earlier 10 but fails with: >> >>>> >> >>>> tar: getvfsbyname failed: No such file or directory >> >>>> >> >>>> on a recent -CURRENT. >> >>> >> >>> libarchive does do an initial getvfsbyname() when you ask it >> >>> to traverse a directory tree so that it can accurately handle later >> >>> requests about mountpoints and filesystem types. This code >> >>> is admittedly a little intricate. >> >> >> >> The problem most likely is the fact that all mountpoints are >> >> exposed via chroot, thus, if it's checking to see if a mountpoint >> >> exists, it may exist outside of the chroot. >> >> >> > >> > I reviewed the code to refresh my memory. Some >> > of what I said before was not quite right. >> > >> > Libarchive's directory traversal tracks information about >> > the filesystem type so that clients such as bsdtar can >> > efficiently skip synthetic filesystems (/dev or /proc) or >> > network filesystems (NFS or SMB mounts). >> > >> > The net effect is something like this: >> > >> > For each file: >> > stat() or lstat() or fstat() the file >> > look up dev number in an internal cache >> > if the dev number is new: >> > fstatfs() the open fd to get the FS name >> > getvfsbyname() to identify the FS type >> > >> > Unless there's a logic error in libarchive itself, this >> > would suggest that somehow fstatfs() is returning >> > a filesystem type that getvfsbyname() can't >> > identify. >> > >> > Paul: >> > What filesystem are you using? >> > >> > What does "mount" show? >> > >> > Does it work outside the chroot? >> >> I also see the same on the redports.org build machines. >> It builds within a jail there which is completely on a tmpfs. >> Interestinly everything is fine with a 10-CURRENT/amd64 >> jail but it breaks in a 10-CURRENT/i386 jail. Both are >> running on the same 10-CURRENT/amd64 which is >> around 2 months old. >> >> https://redports.org/buildarchive/20120814130205-56327/ > > Try this. > > diff --git a/sys/kern/vfs_subr.c b/sys/kern/vfs_subr.c > index 1d6136a..631d3f2 100644 > --- a/sys/kern/vfs_subr.c > +++ b/sys/kern/vfs_subr.c > @@ -41,6 +41,7 @@ > #include > __FBSDID("$FreeBSD$"); > > +#include "opt_compat.h" > #include "opt_ddb.h" > #include "opt_watchdog.h" > > @@ -3111,21 +3112,49 @@ DB_SHOW_COMMAND(mount, db_show_mount) > /* > * Fill in a struct xvfsconf based on a struct vfsconf. > */ > -static void > -vfsconf2x(struct vfsconf *vfsp, struct xvfsconf *xvfsp) > +static int > +vfsconf2x(struct sysctl_req *req, struct vfsconf *vfsp) > { > + struct xvfsconf xvfsp; > > - strcpy(xvfsp->vfc_name, vfsp->vfc_name); > - xvfsp->vfc_typenum = vfsp->vfc_typenum; > - xvfsp->vfc_refcount = vfsp->vfc_refcount; > - xvfsp->vfc_flags = vfsp->vfc_flags; > + bzero(&xvfsp, sizeof(xvfsp)); > + strcpy(xvfsp.vfc_name, vfsp->vfc_name); > + xvfsp.vfc_typenum = vfsp->vfc_typenum; > + xvfsp.vfc_refcount = vfsp->vfc_refcount; > + xvfsp.vfc_flags = vfsp->vfc_flags; > /* > * These are unused in userland, we keep them > * to not break binary compatibility. > */ > - xvfsp->vfc_vfsops = NULL; > - xvfsp->vfc_next = NULL; > + xvfsp.vfc_vfsops = NULL; > + xvfsp.vfc_next = NULL; > + return (SYSCTL_OUT(req, &xvfsp, sizeof(xvfsp))); > +} > + > +#ifdef COMPAT_FREEBSD32 > +struct xvfsconf32 { > + uint32_t vfc_vfsops; > + char vfc_name[MFSNAMELEN]; > + int32_t vfc_typenum; > + int32_t vfc_refcount; > + int32_t vfc_flags; > + uint32_t vfc_next; > +}; > + > +static int > +vfsconf2x32(struct sysctl_req *req, struct vfsconf *vfsp) > +{ > + struct xvfsconf32 xvfsp; > + > + strcpy(xvfsp.vfc_name, vfsp->vfc_name); > + xvfsp.vfc_typenum = vfsp->vfc_typenum; > + xvfsp.vfc_refcount = vfsp->vfc_refcount; > + xvfsp.vfc_flags = vfsp->vfc_flags; > + xvfsp.vfc_vfsops = 0; > + xvfsp.vfc_next = 0; > + return (SYSCTL_OUT(req, &xvfsp, sizeof(xvfsp))); > } > +#endif > > /* > * Top level filesystem related information gathering. > @@ -3134,14 +3163,16 @@ static int > sysctl_vfs_conflist(SYSCTL_HANDLER_ARGS) > { > struct vfsconf *vfsp; > - struct xvfsconf xvfsp; > int error; > > error = 0; > TAILQ_FOREACH(vfsp, &vfsconf, vfc_list) { > - bzero(&xvfsp, sizeof(xvfsp)); > - vfsconf2x(vfsp, &xvfsp); > - error = SYSCTL_OUT(req, &xvfsp, sizeof xvfsp); > +#ifdef COMPAT_FREEBSD32 > + if (req->flags & SCTL_MASK32) > + error = vfsconf2x32(req, vfsp); > + else > +#endif > + error = vfsconf2x(req, vfsp); > if (error) > break; > } > @@ -3161,7 +3192,6 @@ vfs_sysctl(SYSCTL_HANDLER_ARGS) > int *name = (int *)arg1 - 1; /* XXX */ > u_int namelen = arg2 + 1; /* XXX */ > struct vfsconf *vfsp; > - struct xvfsconf xvfsp; > > log(LOG_WARNING, "userland calling deprecated sysctl, " > "please rebuild world\n"); > @@ -3185,9 +3215,12 @@ vfs_sysctl(SYSCTL_HANDLER_ARGS) > break; > if (vfsp == NULL) > return (EOPNOTSUPP); > - bzero(&xvfsp, sizeof(xvfsp)); > - vfsconf2x(vfsp, &xvfsp); > - return (SYSCTL_OUT(req, &xvfsp, sizeof(xvfsp))); > +#ifdef COMPAT_FREEBSD32 > + if (req->flags & SCTL_MASK32) > + return (vfsconf2x32(req, vfsp)); > + else > +#endif > + return (vfsconf2x(req, vfsp)); > } > return (EOPNOTSUPP); > } Wow that was fast! It will take a few days until I am able to give it a try because I'm traveling for the next few days but I will report back as soon as possible. -- Bernhard Froehlich http://www.bluelife.at/ From owner-freebsd-current@FreeBSD.ORG Mon Aug 20 15:20:18 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8FDB71065674; Mon, 20 Aug 2012 15:20:18 +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 559928FC18; Mon, 20 Aug 2012 15:20: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 q7KFKHwb007705; Mon, 20 Aug 2012 11:20:17 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-current.sentex.ca (8.14.5/8.14.5/Submit) id q7KFKHpN007692; Mon, 20 Aug 2012 15:20:17 GMT (envelope-from tinderbox@freebsd.org) Date: Mon, 20 Aug 2012 15:20:17 GMT Message-Id: <201208201520.q7KFKHpN007692@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 , , Precedence: bulk Cc: Subject: [head tinderbox] failure on sparc64/sparc64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Aug 2012 15:20:18 -0000 TB --- 2012-08-20 14:01:22 - tinderbox 2.9 running on freebsd-current.sentex.ca TB --- 2012-08-20 14:01:22 - 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 --- 2012-08-20 14:01:22 - starting HEAD tinderbox run for sparc64/sparc64 TB --- 2012-08-20 14:01:22 - cleaning the object tree TB --- 2012-08-20 14:04:44 - cvsupping the source tree TB --- 2012-08-20 14:04:44 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/sparc64/sparc64/supfile TB --- 2012-08-20 14:05:33 - building world TB --- 2012-08-20 14:05:33 - CROSS_BUILD_TESTING=YES TB --- 2012-08-20 14:05:33 - MAKEOBJDIRPREFIX=/obj TB --- 2012-08-20 14:05:33 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-08-20 14:05:33 - SRCCONF=/dev/null TB --- 2012-08-20 14:05:33 - TARGET=sparc64 TB --- 2012-08-20 14:05:33 - TARGET_ARCH=sparc64 TB --- 2012-08-20 14:05:33 - TZ=UTC TB --- 2012-08-20 14:05:33 - __MAKE_CONF=/dev/null TB --- 2012-08-20 14:05:33 - cd /src TB --- 2012-08-20 14:05:33 - /usr/bin/make -B buildworld >>> World build started on Mon Aug 20 14:05:33 UTC 2012 >>> 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 Mon Aug 20 15:15:02 UTC 2012 TB --- 2012-08-20 15:15:02 - generating LINT kernel config TB --- 2012-08-20 15:15:02 - cd /src/sys/sparc64/conf TB --- 2012-08-20 15:15:02 - /usr/bin/make -B LINT TB --- 2012-08-20 15:15:02 - cd /src/sys/sparc64/conf TB --- 2012-08-20 15:15:02 - /usr/sbin/config -m LINT TB --- 2012-08-20 15:15:02 - building LINT kernel TB --- 2012-08-20 15:15:02 - CROSS_BUILD_TESTING=YES TB --- 2012-08-20 15:15:02 - MAKEOBJDIRPREFIX=/obj TB --- 2012-08-20 15:15:02 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-08-20 15:15:02 - SRCCONF=/dev/null TB --- 2012-08-20 15:15:02 - TARGET=sparc64 TB --- 2012-08-20 15:15:02 - TARGET_ARCH=sparc64 TB --- 2012-08-20 15:15:02 - TZ=UTC TB --- 2012-08-20 15:15:02 - __MAKE_CONF=/dev/null TB --- 2012-08-20 15:15:02 - cd /src TB --- 2012-08-20 15:15:02 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Mon Aug 20 15:15:02 UTC 2012 >>> 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 -c -O2 -pipe -fno-strict-aliasing -std=c99 -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 -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mcmodel=medany -msoft-float -ffreestanding -fstack-protector -Werror /src/sys/dev/ath/if_ath_tx.c -I/src/sys/dev/ath /src/sys/dev/ath/if_ath_tx.c: In function 'ath_tx_chaindesclist': /src/sys/dev/ath/if_ath_tx.c:379: error: 'ATH_DEBUG_XMIT' undeclared (first use in this function) /src/sys/dev/ath/if_ath_tx.c:379: error: (Each undeclared identifier is reported only once /src/sys/dev/ath/if_ath_tx.c:379: error: for each function it appears in.) cc1: warnings being treated as errors /src/sys/dev/ath/if_ath_tx.c:380: warning: implicit declaration of function 'ath_printtxbuf' /src/sys/dev/ath/if_ath_tx.c:380: warning: nested extern declaration of 'ath_printtxbuf' [-Wnested-externs] *** Error code 1 Stop in /obj/sparc64.sparc64/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2012-08-20 15:20:17 - WARNING: /usr/bin/make returned exit code 1 TB --- 2012-08-20 15:20:17 - ERROR: failed to build LINT kernel TB --- 2012-08-20 15:20:17 - 3227.58 user 604.12 system 4734.39 real http://tinderbox.freebsd.org/tinderbox-head-HEAD-sparc64-sparc64.full From owner-freebsd-current@FreeBSD.ORG Mon Aug 20 15:49:27 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9C42A106566B; Mon, 20 Aug 2012 15:49:27 +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 6AB788FC14; Mon, 20 Aug 2012 15:49:27 +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 q7KFnQsL012768; Mon, 20 Aug 2012 11:49:26 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-current.sentex.ca (8.14.5/8.14.5/Submit) id q7KFnQeU012763; Mon, 20 Aug 2012 15:49:26 GMT (envelope-from tinderbox@freebsd.org) Date: Mon, 20 Aug 2012 15:49:26 GMT Message-Id: <201208201549.q7KFnQeU012763@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 , , Precedence: bulk Cc: Subject: [head tinderbox] failure on powerpc/powerpc X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Aug 2012 15:49:27 -0000 TB --- 2012-08-20 13:24:39 - tinderbox 2.9 running on freebsd-current.sentex.ca TB --- 2012-08-20 13:24:39 - 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 --- 2012-08-20 13:24:39 - starting HEAD tinderbox run for powerpc/powerpc TB --- 2012-08-20 13:24:39 - cleaning the object tree TB --- 2012-08-20 13:26:22 - cvsupping the source tree TB --- 2012-08-20 13:26:22 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/powerpc/powerpc/supfile TB --- 2012-08-20 13:27:12 - building world TB --- 2012-08-20 13:27:12 - CROSS_BUILD_TESTING=YES TB --- 2012-08-20 13:27:12 - MAKEOBJDIRPREFIX=/obj TB --- 2012-08-20 13:27:12 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-08-20 13:27:12 - SRCCONF=/dev/null TB --- 2012-08-20 13:27:12 - TARGET=powerpc TB --- 2012-08-20 13:27:12 - TARGET_ARCH=powerpc TB --- 2012-08-20 13:27:12 - TZ=UTC TB --- 2012-08-20 13:27:12 - __MAKE_CONF=/dev/null TB --- 2012-08-20 13:27:12 - cd /src TB --- 2012-08-20 13:27:12 - /usr/bin/make -B buildworld >>> World build started on Mon Aug 20 13:27:13 UTC 2012 >>> 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 Mon Aug 20 15:45:57 UTC 2012 TB --- 2012-08-20 15:45:57 - generating LINT kernel config TB --- 2012-08-20 15:45:57 - cd /src/sys/powerpc/conf TB --- 2012-08-20 15:45:57 - /usr/bin/make -B LINT TB --- 2012-08-20 15:45:57 - cd /src/sys/powerpc/conf TB --- 2012-08-20 15:45:57 - /usr/sbin/config -m LINT TB --- 2012-08-20 15:45:57 - building LINT kernel TB --- 2012-08-20 15:45:57 - CROSS_BUILD_TESTING=YES TB --- 2012-08-20 15:45:57 - MAKEOBJDIRPREFIX=/obj TB --- 2012-08-20 15:45:57 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-08-20 15:45:57 - SRCCONF=/dev/null TB --- 2012-08-20 15:45:57 - TARGET=powerpc TB --- 2012-08-20 15:45:57 - TARGET_ARCH=powerpc TB --- 2012-08-20 15:45:57 - TZ=UTC TB --- 2012-08-20 15:45:57 - __MAKE_CONF=/dev/null TB --- 2012-08-20 15:45:57 - cd /src TB --- 2012-08-20 15:45:57 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Mon Aug 20 15:45:58 UTC 2012 >>> 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 -c -O -pipe -std=c99 -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 -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/libfdt -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -msoft-float -Wa,-many -fno-omit-frame-pointer -msoft-float -mno-altivec -ffreestanding -fstack-protector -Werror /src/sys/dev/ath/if_ath_tx.c -I/src/sys/dev/ath /src/sys/dev/ath/if_ath_tx.c: In function 'ath_tx_chaindesclist': /src/sys/dev/ath/if_ath_tx.c:379: error: 'ATH_DEBUG_XMIT' undeclared (first use in this function) /src/sys/dev/ath/if_ath_tx.c:379: error: (Each undeclared identifier is reported only once /src/sys/dev/ath/if_ath_tx.c:379: error: for each function it appears in.) cc1: warnings being treated as errors /src/sys/dev/ath/if_ath_tx.c:380: warning: implicit declaration of function 'ath_printtxbuf' /src/sys/dev/ath/if_ath_tx.c:380: warning: nested extern declaration of 'ath_printtxbuf' [-Wnested-externs] *** Error code 1 Stop in /obj/powerpc.powerpc/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2012-08-20 15:49:26 - WARNING: /usr/bin/make returned exit code 1 TB --- 2012-08-20 15:49:26 - ERROR: failed to build LINT kernel TB --- 2012-08-20 15:49:26 - 6834.09 user 922.09 system 8687.16 real http://tinderbox.freebsd.org/tinderbox-head-HEAD-powerpc-powerpc.full From owner-freebsd-current@FreeBSD.ORG Mon Aug 20 16:47:49 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 764911065679; Mon, 20 Aug 2012 16:47:49 +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 45EF18FC14; Mon, 20 Aug 2012 16:47:48 +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 q7KGlmdZ036548; Mon, 20 Aug 2012 12:47:48 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-current.sentex.ca (8.14.5/8.14.5/Submit) id q7KGlmgH036547; Mon, 20 Aug 2012 16:47:48 GMT (envelope-from tinderbox@freebsd.org) Date: Mon, 20 Aug 2012 16:47:48 GMT Message-Id: <201208201647.q7KGlmgH036547@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 , , Precedence: bulk Cc: Subject: [head tinderbox] failure on powerpc64/powerpc X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Aug 2012 16:47:49 -0000 TB --- 2012-08-20 13:59:00 - tinderbox 2.9 running on freebsd-current.sentex.ca TB --- 2012-08-20 13:59:00 - 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 --- 2012-08-20 13:59:00 - starting HEAD tinderbox run for powerpc64/powerpc TB --- 2012-08-20 13:59:00 - cleaning the object tree TB --- 2012-08-20 14:01:42 - cvsupping the source tree TB --- 2012-08-20 14:01:42 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/powerpc64/powerpc/supfile TB --- 2012-08-20 14:03:14 - building world TB --- 2012-08-20 14:03:14 - CROSS_BUILD_TESTING=YES TB --- 2012-08-20 14:03:14 - MAKEOBJDIRPREFIX=/obj TB --- 2012-08-20 14:03:14 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-08-20 14:03:14 - SRCCONF=/dev/null TB --- 2012-08-20 14:03:14 - TARGET=powerpc TB --- 2012-08-20 14:03:14 - TARGET_ARCH=powerpc64 TB --- 2012-08-20 14:03:14 - TZ=UTC TB --- 2012-08-20 14:03:14 - __MAKE_CONF=/dev/null TB --- 2012-08-20 14:03:14 - cd /src TB --- 2012-08-20 14:03:14 - /usr/bin/make -B buildworld >>> World build started on Mon Aug 20 14:03:15 UTC 2012 >>> 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 >>> stage 5.1: building 32 bit shim libraries >>> World build completed on Mon Aug 20 16:44:15 UTC 2012 TB --- 2012-08-20 16:44:15 - generating LINT kernel config TB --- 2012-08-20 16:44:15 - cd /src/sys/powerpc/conf TB --- 2012-08-20 16:44:15 - /usr/bin/make -B LINT TB --- 2012-08-20 16:44:15 - cd /src/sys/powerpc/conf TB --- 2012-08-20 16:44:15 - /usr/sbin/config -m LINT TB --- 2012-08-20 16:44:15 - building LINT kernel TB --- 2012-08-20 16:44:15 - CROSS_BUILD_TESTING=YES TB --- 2012-08-20 16:44:15 - MAKEOBJDIRPREFIX=/obj TB --- 2012-08-20 16:44:15 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-08-20 16:44:15 - SRCCONF=/dev/null TB --- 2012-08-20 16:44:15 - TARGET=powerpc TB --- 2012-08-20 16:44:15 - TARGET_ARCH=powerpc64 TB --- 2012-08-20 16:44:15 - TZ=UTC TB --- 2012-08-20 16:44:15 - __MAKE_CONF=/dev/null TB --- 2012-08-20 16:44:15 - cd /src TB --- 2012-08-20 16:44:15 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Mon Aug 20 16:44:15 UTC 2012 >>> 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 -c -O -pipe -std=c99 -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 -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/libfdt -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -msoft-float -Wa,-many -fno-omit-frame-pointer -msoft-float -mno-altivec -mcall-aixdesc -ffreestanding -fstack-protector -Werror /src/sys/dev/ath/if_ath_tx.c -I/src/sys/dev/ath /src/sys/dev/ath/if_ath_tx.c: In function 'ath_tx_chaindesclist': /src/sys/dev/ath/if_ath_tx.c:379: error: 'ATH_DEBUG_XMIT' undeclared (first use in this function) /src/sys/dev/ath/if_ath_tx.c:379: error: (Each undeclared identifier is reported only once /src/sys/dev/ath/if_ath_tx.c:379: error: for each function it appears in.) cc1: warnings being treated as errors /src/sys/dev/ath/if_ath_tx.c:380: warning: implicit declaration of function 'ath_printtxbuf' /src/sys/dev/ath/if_ath_tx.c:380: warning: nested extern declaration of 'ath_printtxbuf' [-Wnested-externs] *** Error code 1 Stop in /obj/powerpc.powerpc64/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2012-08-20 16:47:48 - WARNING: /usr/bin/make returned exit code 1 TB --- 2012-08-20 16:47:48 - ERROR: failed to build LINT kernel TB --- 2012-08-20 16:47:48 - 8360.92 user 1141.90 system 10127.84 real http://tinderbox.freebsd.org/tinderbox-head-HEAD-powerpc64-powerpc.full From owner-freebsd-current@FreeBSD.ORG Mon Aug 20 18:21:34 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6E81C106567A for ; Mon, 20 Aug 2012 18:21:34 +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 3E4518FC16 for ; Mon, 20 Aug 2012 18:21:34 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 93F15B941; Mon, 20 Aug 2012 14:21:33 -0400 (EDT) From: John Baldwin To: Monthadar Al Jaberi Date: Mon, 20 Aug 2012 12:15:58 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110714-p17; KDE/4.5.5; amd64; ; ) References: <201208200804.31932.jhb@freebsd.org> In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201208201215.58033.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Mon, 20 Aug 2012 14:21:33 -0400 (EDT) Cc: freebsd-current@freebsd.org Subject: Re: kernel page fult for a valid pointer? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 20 Aug 2012 18:21:34 -0000 On Monday, August 20, 2012 9:49:48 am Monthadar Al Jaberi wrote: > On Mon, Aug 20, 2012 at 2:04 PM, John Baldwin wrote: > > On Saturday, August 18, 2012 2:29:26 pm Monthadar Al Jaberi wrote: > >> Hi, > >> > >> I am wondering is there a reason for getting "Fatal trap 12: page > >> fault while in kernel mode" "supervisor read, page not present" for an > >> address used to be valid in kernel space? > >> > >> I dont really understand why I am getting this, I added a hardware > >> watchpoint on the address, and when I got to the debuger I could read > >> the memory content and dump for that address. But when I continue from > >> the debugger I get the panic and now when I try to read the memory > >> content I get *** error reading from address ce733000 ***. > > > > Whatever memory was there might have been unmapped? For example, > > memory pointed to by I/O buffers (struct buf/bio) use transient > > mappings that are only valid while an I/O request is in progress. > > Thank you the for the reply, so if a struct gets freed will the page > it was on get un-mapped, so that I cant dump it in debugger? Even > VirtualBox debugger cant dump the memory giving > "VERR_PAGE_TABLE_NOT_PRESENT: Reading memory at...". > > In my case it is a struct ieee80211_node which gets freed, but where > does the page get unmaped? I tried doubling the memory in VirtualBox. Well, things that are malloc'd are a bit trickier. I do believe they can get unmapped if the backing slab is released to the system during a uma_reclaim(). -- John Baldwin From owner-freebsd-current@FreeBSD.ORG Mon Aug 20 18:30:33 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DF6ED10656A8; Mon, 20 Aug 2012 18:30:33 +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 8E84A8FC19; Mon, 20 Aug 2012 18:30:33 +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 q7KIUWkg077046; Mon, 20 Aug 2012 14:30:32 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-current.sentex.ca (8.14.5/8.14.5/Submit) id q7KIUWwt077045; Mon, 20 Aug 2012 18:30:32 GMT (envelope-from tinderbox@freebsd.org) Date: Mon, 20 Aug 2012 18:30:32 GMT Message-Id: <201208201830.q7KIUWwt077045@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 , , Precedence: bulk Cc: Subject: [head tinderbox] failure on arm/arm X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Aug 2012 18:30:34 -0000 TB --- 2012-08-20 16:50:00 - tinderbox 2.9 running on freebsd-current.sentex.ca TB --- 2012-08-20 16:50:00 - 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 --- 2012-08-20 16:50:00 - starting HEAD tinderbox run for arm/arm TB --- 2012-08-20 16:50:00 - cleaning the object tree TB --- 2012-08-20 16:56:30 - cvsupping the source tree TB --- 2012-08-20 16:56:30 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/arm/arm/supfile TB --- 2012-08-20 16:59:05 - building world TB --- 2012-08-20 16:59:05 - CROSS_BUILD_TESTING=YES TB --- 2012-08-20 16:59:05 - MAKEOBJDIRPREFIX=/obj TB --- 2012-08-20 16:59:05 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-08-20 16:59:05 - SRCCONF=/dev/null TB --- 2012-08-20 16:59:05 - TARGET=arm TB --- 2012-08-20 16:59:05 - TARGET_ARCH=arm TB --- 2012-08-20 16:59:05 - TZ=UTC TB --- 2012-08-20 16:59:05 - __MAKE_CONF=/dev/null TB --- 2012-08-20 16:59:05 - cd /src TB --- 2012-08-20 16:59:05 - /usr/bin/make -B buildworld >>> World build started on Mon Aug 20 16:59:06 UTC 2012 >>> 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 Mon Aug 20 18:01:33 UTC 2012 TB --- 2012-08-20 18:01:33 - cd /src/sys/arm/conf TB --- 2012-08-20 18:01:33 - /usr/sbin/config -m ARMADAXP TB --- 2012-08-20 18:01:34 - skipping ARMADAXP kernel TB --- 2012-08-20 18:01:34 - cd /src/sys/arm/conf TB --- 2012-08-20 18:01:34 - /usr/sbin/config -m ATMEL TB --- 2012-08-20 18:01:34 - building ATMEL kernel TB --- 2012-08-20 18:01:34 - CROSS_BUILD_TESTING=YES TB --- 2012-08-20 18:01:34 - MAKEOBJDIRPREFIX=/obj TB --- 2012-08-20 18:01:34 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-08-20 18:01:34 - SRCCONF=/dev/null TB --- 2012-08-20 18:01:34 - TARGET=arm TB --- 2012-08-20 18:01:34 - TARGET_ARCH=arm TB --- 2012-08-20 18:01:34 - TZ=UTC TB --- 2012-08-20 18:01:34 - __MAKE_CONF=/dev/null TB --- 2012-08-20 18:01:34 - cd /src TB --- 2012-08-20 18:01:34 - /usr/bin/make -B buildkernel KERNCONF=ATMEL >>> Kernel build for ATMEL started on Mon Aug 20 18:01:34 UTC 2012 >>> 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 ATMEL completed on Mon Aug 20 18:05:05 UTC 2012 TB --- 2012-08-20 18:05:05 - cd /src/sys/arm/conf TB --- 2012-08-20 18:05:05 - /usr/sbin/config -m AVILA TB --- 2012-08-20 18:05:06 - skipping AVILA kernel TB --- 2012-08-20 18:05:06 - cd /src/sys/arm/conf TB --- 2012-08-20 18:05:06 - /usr/sbin/config -m BEAGLEBONE TB --- 2012-08-20 18:05:06 - skipping BEAGLEBONE kernel TB --- 2012-08-20 18:05:06 - cd /src/sys/arm/conf TB --- 2012-08-20 18:05:06 - /usr/sbin/config -m BWCT TB --- 2012-08-20 18:05:06 - building BWCT kernel TB --- 2012-08-20 18:05:06 - CROSS_BUILD_TESTING=YES TB --- 2012-08-20 18:05:06 - MAKEOBJDIRPREFIX=/obj TB --- 2012-08-20 18:05:06 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-08-20 18:05:06 - SRCCONF=/dev/null TB --- 2012-08-20 18:05:06 - TARGET=arm TB --- 2012-08-20 18:05:06 - TARGET_ARCH=arm TB --- 2012-08-20 18:05:06 - TZ=UTC TB --- 2012-08-20 18:05:06 - __MAKE_CONF=/dev/null TB --- 2012-08-20 18:05:06 - cd /src TB --- 2012-08-20 18:05:06 - /usr/bin/make -B buildkernel KERNCONF=BWCT >>> Kernel build for BWCT started on Mon Aug 20 18:05:06 UTC 2012 >>> 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 BWCT completed on Mon Aug 20 18:07:15 UTC 2012 TB --- 2012-08-20 18:07:15 - cd /src/sys/arm/conf TB --- 2012-08-20 18:07:15 - /usr/sbin/config -m CAMBRIA TB --- 2012-08-20 18:07:15 - skipping CAMBRIA kernel TB --- 2012-08-20 18:07:15 - cd /src/sys/arm/conf TB --- 2012-08-20 18:07:15 - /usr/sbin/config -m CNS11XXNAS TB --- 2012-08-20 18:07:15 - building CNS11XXNAS kernel TB --- 2012-08-20 18:07:15 - CROSS_BUILD_TESTING=YES TB --- 2012-08-20 18:07:15 - MAKEOBJDIRPREFIX=/obj TB --- 2012-08-20 18:07:15 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-08-20 18:07:15 - SRCCONF=/dev/null TB --- 2012-08-20 18:07:15 - TARGET=arm TB --- 2012-08-20 18:07:15 - TARGET_ARCH=arm TB --- 2012-08-20 18:07:15 - TZ=UTC TB --- 2012-08-20 18:07:15 - __MAKE_CONF=/dev/null TB --- 2012-08-20 18:07:15 - cd /src TB --- 2012-08-20 18:07:15 - /usr/bin/make -B buildkernel KERNCONF=CNS11XXNAS >>> Kernel build for CNS11XXNAS started on Mon Aug 20 18:07:15 UTC 2012 >>> 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 CNS11XXNAS completed on Mon Aug 20 18:09:42 UTC 2012 TB --- 2012-08-20 18:09:42 - cd /src/sys/arm/conf TB --- 2012-08-20 18:09:42 - /usr/sbin/config -m CRB TB --- 2012-08-20 18:09:42 - skipping CRB kernel TB --- 2012-08-20 18:09:42 - cd /src/sys/arm/conf TB --- 2012-08-20 18:09:42 - /usr/sbin/config -m DB-78XXX TB --- 2012-08-20 18:09:42 - building DB-78XXX kernel TB --- 2012-08-20 18:09:42 - CROSS_BUILD_TESTING=YES TB --- 2012-08-20 18:09:42 - MAKEOBJDIRPREFIX=/obj TB --- 2012-08-20 18:09:42 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-08-20 18:09:42 - SRCCONF=/dev/null TB --- 2012-08-20 18:09:42 - TARGET=arm TB --- 2012-08-20 18:09:42 - TARGET_ARCH=arm TB --- 2012-08-20 18:09:42 - TZ=UTC TB --- 2012-08-20 18:09:42 - __MAKE_CONF=/dev/null TB --- 2012-08-20 18:09:42 - cd /src TB --- 2012-08-20 18:09:42 - /usr/bin/make -B buildkernel KERNCONF=DB-78XXX >>> Kernel build for DB-78XXX started on Mon Aug 20 18:09:42 UTC 2012 >>> 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 DB-78XXX completed on Mon Aug 20 18:12:33 UTC 2012 TB --- 2012-08-20 18:12:33 - cd /src/sys/arm/conf TB --- 2012-08-20 18:12:33 - /usr/sbin/config -m DB-88F5XXX TB --- 2012-08-20 18:12:33 - building DB-88F5XXX kernel TB --- 2012-08-20 18:12:33 - CROSS_BUILD_TESTING=YES TB --- 2012-08-20 18:12:33 - MAKEOBJDIRPREFIX=/obj TB --- 2012-08-20 18:12:33 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-08-20 18:12:33 - SRCCONF=/dev/null TB --- 2012-08-20 18:12:33 - TARGET=arm TB --- 2012-08-20 18:12:33 - TARGET_ARCH=arm TB --- 2012-08-20 18:12:33 - TZ=UTC TB --- 2012-08-20 18:12:33 - __MAKE_CONF=/dev/null TB --- 2012-08-20 18:12:33 - cd /src TB --- 2012-08-20 18:12:33 - /usr/bin/make -B buildkernel KERNCONF=DB-88F5XXX >>> Kernel build for DB-88F5XXX started on Mon Aug 20 18:12:33 UTC 2012 >>> 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 DB-88F5XXX completed on Mon Aug 20 18:15:14 UTC 2012 TB --- 2012-08-20 18:15:14 - cd /src/sys/arm/conf TB --- 2012-08-20 18:15:14 - /usr/sbin/config -m DB-88F6XXX TB --- 2012-08-20 18:15:14 - building DB-88F6XXX kernel TB --- 2012-08-20 18:15:14 - CROSS_BUILD_TESTING=YES TB --- 2012-08-20 18:15:14 - MAKEOBJDIRPREFIX=/obj TB --- 2012-08-20 18:15:14 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-08-20 18:15:14 - SRCCONF=/dev/null TB --- 2012-08-20 18:15:14 - TARGET=arm TB --- 2012-08-20 18:15:14 - TARGET_ARCH=arm TB --- 2012-08-20 18:15:14 - TZ=UTC TB --- 2012-08-20 18:15:14 - __MAKE_CONF=/dev/null TB --- 2012-08-20 18:15:14 - cd /src TB --- 2012-08-20 18:15:14 - /usr/bin/make -B buildkernel KERNCONF=DB-88F6XXX >>> Kernel build for DB-88F6XXX started on Mon Aug 20 18:15:14 UTC 2012 >>> 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 DB-88F6XXX completed on Mon Aug 20 18:18:08 UTC 2012 TB --- 2012-08-20 18:18:08 - cd /src/sys/arm/conf TB --- 2012-08-20 18:18:08 - /usr/sbin/config -m DOCKSTAR TB --- 2012-08-20 18:18:08 - building DOCKSTAR kernel TB --- 2012-08-20 18:18:08 - CROSS_BUILD_TESTING=YES TB --- 2012-08-20 18:18:08 - MAKEOBJDIRPREFIX=/obj TB --- 2012-08-20 18:18:08 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-08-20 18:18:08 - SRCCONF=/dev/null TB --- 2012-08-20 18:18:08 - TARGET=arm TB --- 2012-08-20 18:18:08 - TARGET_ARCH=arm TB --- 2012-08-20 18:18:08 - TZ=UTC TB --- 2012-08-20 18:18:08 - __MAKE_CONF=/dev/null TB --- 2012-08-20 18:18:08 - cd /src TB --- 2012-08-20 18:18:08 - /usr/bin/make -B buildkernel KERNCONF=DOCKSTAR >>> Kernel build for DOCKSTAR started on Mon Aug 20 18:18:08 UTC 2012 >>> 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 DOCKSTAR completed on Mon Aug 20 18:20:46 UTC 2012 TB --- 2012-08-20 18:20:46 - cd /src/sys/arm/conf TB --- 2012-08-20 18:20:46 - /usr/sbin/config -m EA3250 TB --- 2012-08-20 18:20:46 - building EA3250 kernel TB --- 2012-08-20 18:20:46 - CROSS_BUILD_TESTING=YES TB --- 2012-08-20 18:20:46 - MAKEOBJDIRPREFIX=/obj TB --- 2012-08-20 18:20:46 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-08-20 18:20:46 - SRCCONF=/dev/null TB --- 2012-08-20 18:20:46 - TARGET=arm TB --- 2012-08-20 18:20:46 - TARGET_ARCH=arm TB --- 2012-08-20 18:20:46 - TZ=UTC TB --- 2012-08-20 18:20:46 - __MAKE_CONF=/dev/null TB --- 2012-08-20 18:20:46 - cd /src TB --- 2012-08-20 18:20:46 - /usr/bin/make -B buildkernel KERNCONF=EA3250 >>> Kernel build for EA3250 started on Mon Aug 20 18:20:47 UTC 2012 >>> 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 EA3250 completed on Mon Aug 20 18:23:26 UTC 2012 TB --- 2012-08-20 18:23:26 - cd /src/sys/arm/conf TB --- 2012-08-20 18:23:26 - /usr/sbin/config -m EB9200 TB --- 2012-08-20 18:23:26 - building EB9200 kernel TB --- 2012-08-20 18:23:26 - CROSS_BUILD_TESTING=YES TB --- 2012-08-20 18:23:26 - MAKEOBJDIRPREFIX=/obj TB --- 2012-08-20 18:23:26 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-08-20 18:23:26 - SRCCONF=/dev/null TB --- 2012-08-20 18:23:26 - TARGET=arm TB --- 2012-08-20 18:23:26 - TARGET_ARCH=arm TB --- 2012-08-20 18:23:26 - TZ=UTC TB --- 2012-08-20 18:23:26 - __MAKE_CONF=/dev/null TB --- 2012-08-20 18:23:26 - cd /src TB --- 2012-08-20 18:23:26 - /usr/bin/make -B buildkernel KERNCONF=EB9200 >>> Kernel build for EB9200 started on Mon Aug 20 18:23:26 UTC 2012 >>> 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 EB9200 completed on Mon Aug 20 18:25:57 UTC 2012 TB --- 2012-08-20 18:25:57 - cd /src/sys/arm/conf TB --- 2012-08-20 18:25:57 - /usr/sbin/config -m EP80219 TB --- 2012-08-20 18:25:57 - skipping EP80219 kernel TB --- 2012-08-20 18:25:57 - cd /src/sys/arm/conf TB --- 2012-08-20 18:25:57 - /usr/sbin/config -m ETHERNUT5 TB --- 2012-08-20 18:25:57 - building ETHERNUT5 kernel TB --- 2012-08-20 18:25:57 - CROSS_BUILD_TESTING=YES TB --- 2012-08-20 18:25:57 - MAKEOBJDIRPREFIX=/obj TB --- 2012-08-20 18:25:57 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-08-20 18:25:57 - SRCCONF=/dev/null TB --- 2012-08-20 18:25:57 - TARGET=arm TB --- 2012-08-20 18:25:57 - TARGET_ARCH=arm TB --- 2012-08-20 18:25:57 - TZ=UTC TB --- 2012-08-20 18:25:57 - __MAKE_CONF=/dev/null TB --- 2012-08-20 18:25:57 - cd /src TB --- 2012-08-20 18:25:57 - /usr/bin/make -B buildkernel KERNCONF=ETHERNUT5 >>> Kernel build for ETHERNUT5 started on Mon Aug 20 18:25:57 UTC 2012 >>> 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 -Werror -D_KERNEL -DKLD_MODULE -nostdinc -I. -I/src/sys/modules/ath/../../dev/ath -I/src/sys/modules/ath/../../dev/ath/ath_hal -DHAVE_KERNEL_OPTION_HEADERS -include /obj/arm.arm/src/sys/ETHERNUT5/opt_global.h -I. -I@ -I@/contrib/altq -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-common -I/obj/arm.arm/src/sys/ETHERNUT5 -mcpu=arm9 -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/ath/../../dev/ath/if_ath.c cc -O -pipe -Werror -D_KERNEL -DKLD_MODULE -nostdinc -I. -I/src/sys/modules/ath/../../dev/ath -I/src/sys/modules/ath/../../dev/ath/ath_hal -DHAVE_KERNEL_OPTION_HEADERS -include /obj/arm.arm/src/sys/ETHERNUT5/opt_global.h -I. -I@ -I@/contrib/altq -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-common -I/obj/arm.arm/src/sys/ETHERNUT5 -mcpu=arm9 -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/ath/../../dev/ath/if_ath_debug.c cc -O -pipe -Werror -D_KERNEL -DKLD_MODULE -nostdinc -I. -I/src/sys/modules/ath/../../dev/ath -I/src/sys/modules/ath/../../dev/ath/ath_hal -DHAVE_KERNEL_OPTION_HEADERS -include /obj/arm.arm/src/sys/ETHERNUT5/opt_global.h -I. -I@ -I@/contrib/altq -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-common -I/obj/arm.arm/src/sys/ETHERNUT5 -mcpu=arm9 -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/ath/../../dev/ath/if_ath_keycache.c cc -O -pipe -Werror -D_KERNEL -DKLD_MODULE -nostdinc -I. -I/src/sys/modules/ath/../../dev/ath -I/src/sys/modules/ath/../../dev/ath/ath_hal -DHAVE_KERNEL_OPTION_HEADERS -include /obj/arm.arm/src/sys/ETHERNUT5/opt_global.h -I. -I@ -I@/contrib/altq -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-common -I/obj/arm.arm/src/sys/ETHERNUT5 -mcpu=arm9 -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/ath/../../dev/ath/if_ath_sysctl.c cc -O -pipe -Werror -D_KERNEL -DKLD_MODULE -nostdinc -I. -I/src/sys/modules/ath/../../dev/ath -I/src/sys/modules/ath/../../dev/ath/ath_hal -DHAVE_KERNEL_OPTION_HEADERS -include /obj/arm.arm/src/sys/ETHERNUT5/opt_global.h -I. -I@ -I@/contrib/altq -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-common -I/obj/arm.arm/src/sys/ETHERNUT5 -mcpu=arm9 -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/ath/../../dev/ath/if_ath_tx.c cc1: warnings being treated as errors /src/sys/modules/ath/../../dev/ath/if_ath_tx.c: In function 'ath_tx_chaindesclist': /src/sys/modules/ath/../../dev/ath/if_ath_tx.c:310: warning: unused variable 'qnum' [-Wunused-variable] *** Error code 1 Stop in /src/sys/modules/ath. *** Error code 1 Stop in /src/sys/modules. *** Error code 1 Stop in /obj/arm.arm/src/sys/ETHERNUT5. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2012-08-20 18:30:32 - WARNING: /usr/bin/make returned exit code 1 TB --- 2012-08-20 18:30:32 - ERROR: failed to build ETHERNUT5 kernel TB --- 2012-08-20 18:30:32 - 3844.56 user 795.80 system 6032.30 real http://tinderbox.freebsd.org/tinderbox-head-HEAD-arm-arm.full From owner-freebsd-current@FreeBSD.ORG Mon Aug 20 18:57:40 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6514D106564A for ; Mon, 20 Aug 2012 18:57:40 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-pz0-f54.google.com (mail-pz0-f54.google.com [209.85.210.54]) by mx1.freebsd.org (Postfix) with ESMTP id 36D578FC0C for ; Mon, 20 Aug 2012 18:57:40 +0000 (UTC) Received: by dadr6 with SMTP id r6so2516355dad.13 for ; Mon, 20 Aug 2012 11:57:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type :content-transfer-encoding; bh=St8t3J1AbxMFoSRTV7uatooGatjjgYo+fxEfLj6zvjU=; b=O3WfP2uutOu1HrLNUbGrKN0t9ji6hv30GAvVXbsIhfwraXd+dQD+awjUVwzA1+6gRd pIOoGlDpzausHRE850bHKf1iqdAmj6jUF2C4b2JuhnxMsPaaUTWrCGTctrc0i5r3qmaV y6rygUck0OUmjkIGfAn7huYOh5ZgiRuMDe0Iovfi1KxM5XkJJafz4+f0x6/3YMbxuVr9 sySWLWD1iMUwByg4fhboENOwOqFKRpmLwQe8DnKvGyiLasmyOErJABzpAr54SWD6BhsM OTUodC0oV/He1Uvz18XFfAjh++zKX0N8XWGEFBXbu2p1/H5Y+uFP1oZ1zpGzB2QBZZOw AGlA== MIME-Version: 1.0 Received: by 10.68.238.74 with SMTP id vi10mr14666296pbc.48.1345489059786; Mon, 20 Aug 2012 11:57:39 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.68.43.169 with HTTP; Mon, 20 Aug 2012 11:57:39 -0700 (PDT) In-Reply-To: <201208201830.q7KIUWwt077045@freebsd-current.sentex.ca> References: <201208201830.q7KIUWwt077045@freebsd-current.sentex.ca> Date: Mon, 20 Aug 2012 11:57:39 -0700 X-Google-Sender-Auth: bjquf6T8TWQ8RA7iNr5g3EoLqcc Message-ID: From: Adrian Chadd To: current@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: Subject: Re: [head tinderbox] failure on arm/arm X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 20 Aug 2012 18:57:40 -0000 Fixed. On 20 August 2012 11:30, FreeBSD Tinderbox wrote: > TB --- 2012-08-20 16:50:00 - tinderbox 2.9 running on freebsd-current.sen= tex.ca > TB --- 2012-08-20 16:50:00 - FreeBSD freebsd-current.sentex.ca 8.3-PREREL= EASE FreeBSD 8.3-PRERELEASE #0: Mon Mar 26 13:54:12 EDT 2012 des@freebs= d-current.sentex.ca:/usr/obj/usr/src/sys/GENERIC amd64 > TB --- 2012-08-20 16:50:00 - starting HEAD tinderbox run for arm/arm > TB --- 2012-08-20 16:50:00 - cleaning the object tree > TB --- 2012-08-20 16:56:30 - cvsupping the source tree > TB --- 2012-08-20 16:56:30 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sente= x.ca /tinderbox/HEAD/arm/arm/supfile > TB --- 2012-08-20 16:59:05 - building world > TB --- 2012-08-20 16:59:05 - CROSS_BUILD_TESTING=3DYES > TB --- 2012-08-20 16:59:05 - MAKEOBJDIRPREFIX=3D/obj > TB --- 2012-08-20 16:59:05 - PATH=3D/usr/bin:/usr/sbin:/bin:/sbin > TB --- 2012-08-20 16:59:05 - SRCCONF=3D/dev/null > TB --- 2012-08-20 16:59:05 - TARGET=3Darm > TB --- 2012-08-20 16:59:05 - TARGET_ARCH=3Darm > TB --- 2012-08-20 16:59:05 - TZ=3DUTC > TB --- 2012-08-20 16:59:05 - __MAKE_CONF=3D/dev/null > TB --- 2012-08-20 16:59:05 - cd /src > TB --- 2012-08-20 16:59:05 - /usr/bin/make -B buildworld >>>> World build started on Mon Aug 20 16:59:06 UTC 2012 >>>> 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 Mon Aug 20 18:01:33 UTC 2012 > TB --- 2012-08-20 18:01:33 - cd /src/sys/arm/conf > TB --- 2012-08-20 18:01:33 - /usr/sbin/config -m ARMADAXP > TB --- 2012-08-20 18:01:34 - skipping ARMADAXP kernel > TB --- 2012-08-20 18:01:34 - cd /src/sys/arm/conf > TB --- 2012-08-20 18:01:34 - /usr/sbin/config -m ATMEL > TB --- 2012-08-20 18:01:34 - building ATMEL kernel > TB --- 2012-08-20 18:01:34 - CROSS_BUILD_TESTING=3DYES > TB --- 2012-08-20 18:01:34 - MAKEOBJDIRPREFIX=3D/obj > TB --- 2012-08-20 18:01:34 - PATH=3D/usr/bin:/usr/sbin:/bin:/sbin > TB --- 2012-08-20 18:01:34 - SRCCONF=3D/dev/null > TB --- 2012-08-20 18:01:34 - TARGET=3Darm > TB --- 2012-08-20 18:01:34 - TARGET_ARCH=3Darm > TB --- 2012-08-20 18:01:34 - TZ=3DUTC > TB --- 2012-08-20 18:01:34 - __MAKE_CONF=3D/dev/null > TB --- 2012-08-20 18:01:34 - cd /src > TB --- 2012-08-20 18:01:34 - /usr/bin/make -B buildkernel KERNCONF=3DATME= L >>>> Kernel build for ATMEL started on Mon Aug 20 18:01:34 UTC 2012 >>>> 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 ATMEL completed on Mon Aug 20 18:05:05 UTC 2012 > TB --- 2012-08-20 18:05:05 - cd /src/sys/arm/conf > TB --- 2012-08-20 18:05:05 - /usr/sbin/config -m AVILA > TB --- 2012-08-20 18:05:06 - skipping AVILA kernel > TB --- 2012-08-20 18:05:06 - cd /src/sys/arm/conf > TB --- 2012-08-20 18:05:06 - /usr/sbin/config -m BEAGLEBONE > TB --- 2012-08-20 18:05:06 - skipping BEAGLEBONE kernel > TB --- 2012-08-20 18:05:06 - cd /src/sys/arm/conf > TB --- 2012-08-20 18:05:06 - /usr/sbin/config -m BWCT > TB --- 2012-08-20 18:05:06 - building BWCT kernel > TB --- 2012-08-20 18:05:06 - CROSS_BUILD_TESTING=3DYES > TB --- 2012-08-20 18:05:06 - MAKEOBJDIRPREFIX=3D/obj > TB --- 2012-08-20 18:05:06 - PATH=3D/usr/bin:/usr/sbin:/bin:/sbin > TB --- 2012-08-20 18:05:06 - SRCCONF=3D/dev/null > TB --- 2012-08-20 18:05:06 - TARGET=3Darm > TB --- 2012-08-20 18:05:06 - TARGET_ARCH=3Darm > TB --- 2012-08-20 18:05:06 - TZ=3DUTC > TB --- 2012-08-20 18:05:06 - __MAKE_CONF=3D/dev/null > TB --- 2012-08-20 18:05:06 - cd /src > TB --- 2012-08-20 18:05:06 - /usr/bin/make -B buildkernel KERNCONF=3DBWCT >>>> Kernel build for BWCT started on Mon Aug 20 18:05:06 UTC 2012 >>>> 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 BWCT completed on Mon Aug 20 18:07:15 UTC 2012 > TB --- 2012-08-20 18:07:15 - cd /src/sys/arm/conf > TB --- 2012-08-20 18:07:15 - /usr/sbin/config -m CAMBRIA > TB --- 2012-08-20 18:07:15 - skipping CAMBRIA kernel > TB --- 2012-08-20 18:07:15 - cd /src/sys/arm/conf > TB --- 2012-08-20 18:07:15 - /usr/sbin/config -m CNS11XXNAS > TB --- 2012-08-20 18:07:15 - building CNS11XXNAS kernel > TB --- 2012-08-20 18:07:15 - CROSS_BUILD_TESTING=3DYES > TB --- 2012-08-20 18:07:15 - MAKEOBJDIRPREFIX=3D/obj > TB --- 2012-08-20 18:07:15 - PATH=3D/usr/bin:/usr/sbin:/bin:/sbin > TB --- 2012-08-20 18:07:15 - SRCCONF=3D/dev/null > TB --- 2012-08-20 18:07:15 - TARGET=3Darm > TB --- 2012-08-20 18:07:15 - TARGET_ARCH=3Darm > TB --- 2012-08-20 18:07:15 - TZ=3DUTC > TB --- 2012-08-20 18:07:15 - __MAKE_CONF=3D/dev/null > TB --- 2012-08-20 18:07:15 - cd /src > TB --- 2012-08-20 18:07:15 - /usr/bin/make -B buildkernel KERNCONF=3DCNS1= 1XXNAS >>>> Kernel build for CNS11XXNAS started on Mon Aug 20 18:07:15 UTC 2012 >>>> 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 CNS11XXNAS completed on Mon Aug 20 18:09:42 UTC 2012 > TB --- 2012-08-20 18:09:42 - cd /src/sys/arm/conf > TB --- 2012-08-20 18:09:42 - /usr/sbin/config -m CRB > TB --- 2012-08-20 18:09:42 - skipping CRB kernel > TB --- 2012-08-20 18:09:42 - cd /src/sys/arm/conf > TB --- 2012-08-20 18:09:42 - /usr/sbin/config -m DB-78XXX > TB --- 2012-08-20 18:09:42 - building DB-78XXX kernel > TB --- 2012-08-20 18:09:42 - CROSS_BUILD_TESTING=3DYES > TB --- 2012-08-20 18:09:42 - MAKEOBJDIRPREFIX=3D/obj > TB --- 2012-08-20 18:09:42 - PATH=3D/usr/bin:/usr/sbin:/bin:/sbin > TB --- 2012-08-20 18:09:42 - SRCCONF=3D/dev/null > TB --- 2012-08-20 18:09:42 - TARGET=3Darm > TB --- 2012-08-20 18:09:42 - TARGET_ARCH=3Darm > TB --- 2012-08-20 18:09:42 - TZ=3DUTC > TB --- 2012-08-20 18:09:42 - __MAKE_CONF=3D/dev/null > TB --- 2012-08-20 18:09:42 - cd /src > TB --- 2012-08-20 18:09:42 - /usr/bin/make -B buildkernel KERNCONF=3DDB-7= 8XXX >>>> Kernel build for DB-78XXX started on Mon Aug 20 18:09:42 UTC 2012 >>>> 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 DB-78XXX completed on Mon Aug 20 18:12:33 UTC 2012 > TB --- 2012-08-20 18:12:33 - cd /src/sys/arm/conf > TB --- 2012-08-20 18:12:33 - /usr/sbin/config -m DB-88F5XXX > TB --- 2012-08-20 18:12:33 - building DB-88F5XXX kernel > TB --- 2012-08-20 18:12:33 - CROSS_BUILD_TESTING=3DYES > TB --- 2012-08-20 18:12:33 - MAKEOBJDIRPREFIX=3D/obj > TB --- 2012-08-20 18:12:33 - PATH=3D/usr/bin:/usr/sbin:/bin:/sbin > TB --- 2012-08-20 18:12:33 - SRCCONF=3D/dev/null > TB --- 2012-08-20 18:12:33 - TARGET=3Darm > TB --- 2012-08-20 18:12:33 - TARGET_ARCH=3Darm > TB --- 2012-08-20 18:12:33 - TZ=3DUTC > TB --- 2012-08-20 18:12:33 - __MAKE_CONF=3D/dev/null > TB --- 2012-08-20 18:12:33 - cd /src > TB --- 2012-08-20 18:12:33 - /usr/bin/make -B buildkernel KERNCONF=3DDB-8= 8F5XXX >>>> Kernel build for DB-88F5XXX started on Mon Aug 20 18:12:33 UTC 2012 >>>> 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 DB-88F5XXX completed on Mon Aug 20 18:15:14 UTC 2012 > TB --- 2012-08-20 18:15:14 - cd /src/sys/arm/conf > TB --- 2012-08-20 18:15:14 - /usr/sbin/config -m DB-88F6XXX > TB --- 2012-08-20 18:15:14 - building DB-88F6XXX kernel > TB --- 2012-08-20 18:15:14 - CROSS_BUILD_TESTING=3DYES > TB --- 2012-08-20 18:15:14 - MAKEOBJDIRPREFIX=3D/obj > TB --- 2012-08-20 18:15:14 - PATH=3D/usr/bin:/usr/sbin:/bin:/sbin > TB --- 2012-08-20 18:15:14 - SRCCONF=3D/dev/null > TB --- 2012-08-20 18:15:14 - TARGET=3Darm > TB --- 2012-08-20 18:15:14 - TARGET_ARCH=3Darm > TB --- 2012-08-20 18:15:14 - TZ=3DUTC > TB --- 2012-08-20 18:15:14 - __MAKE_CONF=3D/dev/null > TB --- 2012-08-20 18:15:14 - cd /src > TB --- 2012-08-20 18:15:14 - /usr/bin/make -B buildkernel KERNCONF=3DDB-8= 8F6XXX >>>> Kernel build for DB-88F6XXX started on Mon Aug 20 18:15:14 UTC 2012 >>>> 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 DB-88F6XXX completed on Mon Aug 20 18:18:08 UTC 2012 > TB --- 2012-08-20 18:18:08 - cd /src/sys/arm/conf > TB --- 2012-08-20 18:18:08 - /usr/sbin/config -m DOCKSTAR > TB --- 2012-08-20 18:18:08 - building DOCKSTAR kernel > TB --- 2012-08-20 18:18:08 - CROSS_BUILD_TESTING=3DYES > TB --- 2012-08-20 18:18:08 - MAKEOBJDIRPREFIX=3D/obj > TB --- 2012-08-20 18:18:08 - PATH=3D/usr/bin:/usr/sbin:/bin:/sbin > TB --- 2012-08-20 18:18:08 - SRCCONF=3D/dev/null > TB --- 2012-08-20 18:18:08 - TARGET=3Darm > TB --- 2012-08-20 18:18:08 - TARGET_ARCH=3Darm > TB --- 2012-08-20 18:18:08 - TZ=3DUTC > TB --- 2012-08-20 18:18:08 - __MAKE_CONF=3D/dev/null > TB --- 2012-08-20 18:18:08 - cd /src > TB --- 2012-08-20 18:18:08 - /usr/bin/make -B buildkernel KERNCONF=3DDOCK= STAR >>>> Kernel build for DOCKSTAR started on Mon Aug 20 18:18:08 UTC 2012 >>>> 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 DOCKSTAR completed on Mon Aug 20 18:20:46 UTC 2012 > TB --- 2012-08-20 18:20:46 - cd /src/sys/arm/conf > TB --- 2012-08-20 18:20:46 - /usr/sbin/config -m EA3250 > TB --- 2012-08-20 18:20:46 - building EA3250 kernel > TB --- 2012-08-20 18:20:46 - CROSS_BUILD_TESTING=3DYES > TB --- 2012-08-20 18:20:46 - MAKEOBJDIRPREFIX=3D/obj > TB --- 2012-08-20 18:20:46 - PATH=3D/usr/bin:/usr/sbin:/bin:/sbin > TB --- 2012-08-20 18:20:46 - SRCCONF=3D/dev/null > TB --- 2012-08-20 18:20:46 - TARGET=3Darm > TB --- 2012-08-20 18:20:46 - TARGET_ARCH=3Darm > TB --- 2012-08-20 18:20:46 - TZ=3DUTC > TB --- 2012-08-20 18:20:46 - __MAKE_CONF=3D/dev/null > TB --- 2012-08-20 18:20:46 - cd /src > TB --- 2012-08-20 18:20:46 - /usr/bin/make -B buildkernel KERNCONF=3DEA32= 50 >>>> Kernel build for EA3250 started on Mon Aug 20 18:20:47 UTC 2012 >>>> 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 EA3250 completed on Mon Aug 20 18:23:26 UTC 2012 > TB --- 2012-08-20 18:23:26 - cd /src/sys/arm/conf > TB --- 2012-08-20 18:23:26 - /usr/sbin/config -m EB9200 > TB --- 2012-08-20 18:23:26 - building EB9200 kernel > TB --- 2012-08-20 18:23:26 - CROSS_BUILD_TESTING=3DYES > TB --- 2012-08-20 18:23:26 - MAKEOBJDIRPREFIX=3D/obj > TB --- 2012-08-20 18:23:26 - PATH=3D/usr/bin:/usr/sbin:/bin:/sbin > TB --- 2012-08-20 18:23:26 - SRCCONF=3D/dev/null > TB --- 2012-08-20 18:23:26 - TARGET=3Darm > TB --- 2012-08-20 18:23:26 - TARGET_ARCH=3Darm > TB --- 2012-08-20 18:23:26 - TZ=3DUTC > TB --- 2012-08-20 18:23:26 - __MAKE_CONF=3D/dev/null > TB --- 2012-08-20 18:23:26 - cd /src > TB --- 2012-08-20 18:23:26 - /usr/bin/make -B buildkernel KERNCONF=3DEB92= 00 >>>> Kernel build for EB9200 started on Mon Aug 20 18:23:26 UTC 2012 >>>> 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 EB9200 completed on Mon Aug 20 18:25:57 UTC 2012 > TB --- 2012-08-20 18:25:57 - cd /src/sys/arm/conf > TB --- 2012-08-20 18:25:57 - /usr/sbin/config -m EP80219 > TB --- 2012-08-20 18:25:57 - skipping EP80219 kernel > TB --- 2012-08-20 18:25:57 - cd /src/sys/arm/conf > TB --- 2012-08-20 18:25:57 - /usr/sbin/config -m ETHERNUT5 > TB --- 2012-08-20 18:25:57 - building ETHERNUT5 kernel > TB --- 2012-08-20 18:25:57 - CROSS_BUILD_TESTING=3DYES > TB --- 2012-08-20 18:25:57 - MAKEOBJDIRPREFIX=3D/obj > TB --- 2012-08-20 18:25:57 - PATH=3D/usr/bin:/usr/sbin:/bin:/sbin > TB --- 2012-08-20 18:25:57 - SRCCONF=3D/dev/null > TB --- 2012-08-20 18:25:57 - TARGET=3Darm > TB --- 2012-08-20 18:25:57 - TARGET_ARCH=3Darm > TB --- 2012-08-20 18:25:57 - TZ=3DUTC > TB --- 2012-08-20 18:25:57 - __MAKE_CONF=3D/dev/null > TB --- 2012-08-20 18:25:57 - cd /src > TB --- 2012-08-20 18:25:57 - /usr/bin/make -B buildkernel KERNCONF=3DETHE= RNUT5 >>>> Kernel build for ETHERNUT5 started on Mon Aug 20 18:25:57 UTC 2012 >>>> 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 -Werror -D_KERNEL -DKLD_MODULE -nostdinc -I. -I/src/sys/modu= les/ath/../../dev/ath -I/src/sys/modules/ath/../../dev/ath/ath_hal -DHAVE_K= ERNEL_OPTION_HEADERS -include /obj/arm.arm/src/sys/ETHERNUT5/opt_global.h -= I. -I@ -I@/contrib/altq -finline-limit=3D8000 --param inline-unit-growth=3D= 100 --param large-function-growth=3D1000 -fno-common -I/obj/arm.arm/src/sy= s/ETHERNUT5 -mcpu=3Darm9 -ffreestanding -std=3Diso9899:1999 -Wall -Wredunda= nt-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpoint= er-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extension= s -Wmissing-include-dirs -fdiagnostics-show-option -c /src/sys/modules/= ath/../../dev/ath/if_ath.c > cc -O -pipe -Werror -D_KERNEL -DKLD_MODULE -nostdinc -I. -I/src/sys/modu= les/ath/../../dev/ath -I/src/sys/modules/ath/../../dev/ath/ath_hal -DHAVE_K= ERNEL_OPTION_HEADERS -include /obj/arm.arm/src/sys/ETHERNUT5/opt_global.h -= I. -I@ -I@/contrib/altq -finline-limit=3D8000 --param inline-unit-growth=3D= 100 --param large-function-growth=3D1000 -fno-common -I/obj/arm.arm/src/sy= s/ETHERNUT5 -mcpu=3Darm9 -ffreestanding -std=3Diso9899:1999 -Wall -Wredunda= nt-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpoint= er-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extension= s -Wmissing-include-dirs -fdiagnostics-show-option -c /src/sys/modules/= ath/../../dev/ath/if_ath_debug.c > cc -O -pipe -Werror -D_KERNEL -DKLD_MODULE -nostdinc -I. -I/src/sys/modu= les/ath/../../dev/ath -I/src/sys/modules/ath/../../dev/ath/ath_hal -DHAVE_K= ERNEL_OPTION_HEADERS -include /obj/arm.arm/src/sys/ETHERNUT5/opt_global.h -= I. -I@ -I@/contrib/altq -finline-limit=3D8000 --param inline-unit-growth=3D= 100 --param large-function-growth=3D1000 -fno-common -I/obj/arm.arm/src/sy= s/ETHERNUT5 -mcpu=3Darm9 -ffreestanding -std=3Diso9899:1999 -Wall -Wredunda= nt-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpoint= er-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extension= s -Wmissing-include-dirs -fdiagnostics-show-option -c /src/sys/modules/= ath/../../dev/ath/if_ath_keycache.c > cc -O -pipe -Werror -D_KERNEL -DKLD_MODULE -nostdinc -I. -I/src/sys/modu= les/ath/../../dev/ath -I/src/sys/modules/ath/../../dev/ath/ath_hal -DHAVE_K= ERNEL_OPTION_HEADERS -include /obj/arm.arm/src/sys/ETHERNUT5/opt_global.h -= I. -I@ -I@/contrib/altq -finline-limit=3D8000 --param inline-unit-growth=3D= 100 --param large-function-growth=3D1000 -fno-common -I/obj/arm.arm/src/sy= s/ETHERNUT5 -mcpu=3Darm9 -ffreestanding -std=3Diso9899:1999 -Wall -Wredunda= nt-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpoint= er-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extension= s -Wmissing-include-dirs -fdiagnostics-show-option -c /src/sys/modules/= ath/../../dev/ath/if_ath_sysctl.c > cc -O -pipe -Werror -D_KERNEL -DKLD_MODULE -nostdinc -I. -I/src/sys/modu= les/ath/../../dev/ath -I/src/sys/modules/ath/../../dev/ath/ath_hal -DHAVE_K= ERNEL_OPTION_HEADERS -include /obj/arm.arm/src/sys/ETHERNUT5/opt_global.h -= I. -I@ -I@/contrib/altq -finline-limit=3D8000 --param inline-unit-growth=3D= 100 --param large-function-growth=3D1000 -fno-common -I/obj/arm.arm/src/sy= s/ETHERNUT5 -mcpu=3Darm9 -ffreestanding -std=3Diso9899:1999 -Wall -Wredunda= nt-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpoint= er-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extension= s -Wmissing-include-dirs -fdiagnostics-show-option -c /src/sys/modules/= ath/../../dev/ath/if_ath_tx.c > cc1: warnings being treated as errors > /src/sys/modules/ath/../../dev/ath/if_ath_tx.c: In function 'ath_tx_chain= desclist': > /src/sys/modules/ath/../../dev/ath/if_ath_tx.c:310: warning: unused varia= ble 'qnum' [-Wunused-variable] > *** Error code 1 > > Stop in /src/sys/modules/ath. > *** Error code 1 > > Stop in /src/sys/modules. > *** Error code 1 > > Stop in /obj/arm.arm/src/sys/ETHERNUT5. > *** Error code 1 > > Stop in /src. > *** Error code 1 > > Stop in /src. > TB --- 2012-08-20 18:30:32 - WARNING: /usr/bin/make returned exit code 1 > TB --- 2012-08-20 18:30:32 - ERROR: failed to build ETHERNUT5 kernel > TB --- 2012-08-20 18:30:32 - 3844.56 user 795.80 system 6032.30 real > > > http://tinderbox.freebsd.org/tinderbox-head-HEAD-arm-arm.full > _______________________________________________ > freebsd-arm@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" From owner-freebsd-current@FreeBSD.ORG Mon Aug 20 18:58:16 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx2.freebsd.org (mx2.freebsd.org [IPv6:2001:4f8:fff6::35]) by hub.freebsd.org (Postfix) with ESMTP id BAEA8106588B; Mon, 20 Aug 2012 18:58:16 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from opti.dougb.net (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id EC90614E949; Mon, 20 Aug 2012 18:57:36 +0000 (UTC) Message-ID: <503288A0.8020705@FreeBSD.org> Date: Mon, 20 Aug 2012 11:57:36 -0700 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:14.0) Gecko/20120728 Thunderbird/14.0 MIME-Version: 1.0 To: Alexander Motin References: <157941699.20120815004542@serebryakov.spb.ru> <502AE8B5.9090106@FreeBSD.org> <502B775D.7000101@FreeBSD.org> <5031F636.1020405@FreeBSD.org> <50320A9E.5070303@FreeBSD.org> <503210A1.7010803@FreeBSD.org> <50323C5F.5090109@FreeBSD.org> In-Reply-To: <50323C5F.5090109@FreeBSD.org> X-Enigmail-Version: 1.4.3 OpenPGP: id=1A1ABC84 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Adrian Chadd , lev@freebsd.org, current@freebsd.org Subject: Re: CURRENT as gateway on not-so-fast hardware: where is a bottlneck? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 20 Aug 2012 18:58:16 -0000 On 08/20/2012 06:32, Alexander Motin wrote: > I have no plans to converge them. I've just found problem in ULE, that > was replicated into 4BSD and it would be strange to fix one without > another. But fixing it exposed another old problem specific to 4BSD, > which I fixed reusing logically equivalent code from ULE. I saw no > reason to reinvent a wheel there, same as to not fix obvious bug. Sure, > it can change behavior in some way, but ULE is not guilty. Thank you for that explanation. -- I am only one, but I am one. I cannot do everything, but I can do something. And I will not let what I cannot do interfere with what I can do. -- Edward Everett Hale, (1822 - 1909) From owner-freebsd-current@FreeBSD.ORG Mon Aug 20 19:40:24 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 492331065688; Mon, 20 Aug 2012 19:40:24 +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 0710D8FC19; Mon, 20 Aug 2012 19:40:23 +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 q7KJeNYh065444; Mon, 20 Aug 2012 15:40:23 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-current.sentex.ca (8.14.5/8.14.5/Submit) id q7KJeNgn065439; Mon, 20 Aug 2012 19:40:23 GMT (envelope-from tinderbox@freebsd.org) Date: Mon, 20 Aug 2012 19:40:23 GMT Message-Id: <201208201940.q7KJeNgn065439@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 , , Precedence: bulk Cc: Subject: [head tinderbox] failure on i386/pc98 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Aug 2012 19:40:24 -0000 TB --- 2012-08-20 16:50:00 - tinderbox 2.9 running on freebsd-current.sentex.ca TB --- 2012-08-20 16:50:00 - 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 --- 2012-08-20 16:50:00 - starting HEAD tinderbox run for i386/pc98 TB --- 2012-08-20 16:50:00 - cleaning the object tree TB --- 2012-08-20 16:55:07 - cvsupping the source tree TB --- 2012-08-20 16:55:07 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/i386/pc98/supfile TB --- 2012-08-20 16:58:53 - building world TB --- 2012-08-20 16:58:53 - CROSS_BUILD_TESTING=YES TB --- 2012-08-20 16:58:53 - MAKEOBJDIRPREFIX=/obj TB --- 2012-08-20 16:58:53 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-08-20 16:58:53 - SRCCONF=/dev/null TB --- 2012-08-20 16:58:53 - TARGET=pc98 TB --- 2012-08-20 16:58:53 - TARGET_ARCH=i386 TB --- 2012-08-20 16:58:53 - TZ=UTC TB --- 2012-08-20 16:58:53 - __MAKE_CONF=/dev/null TB --- 2012-08-20 16:58:53 - cd /src TB --- 2012-08-20 16:58:53 - /usr/bin/make -B buildworld >>> World build started on Mon Aug 20 16:58:54 UTC 2012 >>> 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 Mon Aug 20 19:32:25 UTC 2012 TB --- 2012-08-20 19:32:25 - generating LINT kernel config TB --- 2012-08-20 19:32:25 - cd /src/sys/pc98/conf TB --- 2012-08-20 19:32:25 - /usr/bin/make -B LINT TB --- 2012-08-20 19:32:25 - cd /src/sys/pc98/conf TB --- 2012-08-20 19:32:25 - /usr/sbin/config -m LINT TB --- 2012-08-20 19:32:25 - building LINT kernel TB --- 2012-08-20 19:32:25 - CROSS_BUILD_TESTING=YES TB --- 2012-08-20 19:32:25 - MAKEOBJDIRPREFIX=/obj TB --- 2012-08-20 19:32:25 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-08-20 19:32:25 - SRCCONF=/dev/null TB --- 2012-08-20 19:32:25 - TARGET=pc98 TB --- 2012-08-20 19:32:25 - TARGET_ARCH=i386 TB --- 2012-08-20 19:32:25 - TZ=UTC TB --- 2012-08-20 19:32:25 - __MAKE_CONF=/dev/null TB --- 2012-08-20 19:32:25 - cd /src TB --- 2012-08-20 19:32:25 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Mon Aug 20 19:32:25 UTC 2012 >>> 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 -c -O2 -pipe -fno-strict-aliasing -std=c99 -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 -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-sse -msoft-float -ffreestanding -fstack-protector -Werror -pg -mprofiler-epilogue /src/sys/dev/ath/if_ath_beacon.c -I/src/sys/dev/ath cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -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 -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-sse -msoft-float -ffreestanding -fstack-protector -Werror -pg -mprofiler-epilogue /src/sys/dev/ath/if_ath_debug.c -I/src/sys/dev/ath cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -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 -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-sse -msoft-float -ffreestanding -fstack-protector -Werror -pg -mprofiler-epilogue /src/sys/dev/ath/if_ath_keycache.c -I/src/sys/dev/ath cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -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 -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-sse -msoft-float -ffreestanding -fstack-protector -Werror -pg -mprofiler-epilogue /src/sys/dev/ath/if_ath_led.c -I/src/sys/dev/ath cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -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 -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-sse -msoft-float -ffreestanding -fstack-protector -Werror -pg -mprofiler-epilogue /src/sys/dev/ath/if_ath_tx.c -I/src/sys/dev/ath cc1: warnings being treated as errors /src/sys/dev/ath/if_ath_tx.c: In function 'ath_tx_chaindesclist': /src/sys/dev/ath/if_ath_tx.c:310: warning: unused variable 'qnum' [-Wunused-variable] *** Error code 1 Stop in /obj/pc98.i386/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2012-08-20 19:40:23 - WARNING: /usr/bin/make returned exit code 1 TB --- 2012-08-20 19:40:23 - ERROR: failed to build LINT kernel TB --- 2012-08-20 19:40:23 - 6724.56 user 972.17 system 10222.66 real http://tinderbox.freebsd.org/tinderbox-head-HEAD-i386-pc98.full From owner-freebsd-current@FreeBSD.ORG Mon Aug 20 19:40:34 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 64D4A106567A; Mon, 20 Aug 2012 19:40:34 +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 33C2A8FC22; Mon, 20 Aug 2012 19:40:34 +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 q7KJeX8v066095; Mon, 20 Aug 2012 15:40:33 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-current.sentex.ca (8.14.5/8.14.5/Submit) id q7KJeXW9066091; Mon, 20 Aug 2012 19:40:33 GMT (envelope-from tinderbox@freebsd.org) Date: Mon, 20 Aug 2012 19:40:33 GMT Message-Id: <201208201940.q7KJeXW9066091@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 , , Precedence: bulk Cc: Subject: [head tinderbox] failure on i386/i386 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Aug 2012 19:40:34 -0000 TB --- 2012-08-20 16:50:00 - tinderbox 2.9 running on freebsd-current.sentex.ca TB --- 2012-08-20 16:50:00 - 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 --- 2012-08-20 16:50:00 - starting HEAD tinderbox run for i386/i386 TB --- 2012-08-20 16:50:00 - cleaning the object tree TB --- 2012-08-20 16:55:23 - cvsupping the source tree TB --- 2012-08-20 16:55:23 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/i386/i386/supfile TB --- 2012-08-20 16:58:52 - building world TB --- 2012-08-20 16:58:52 - CROSS_BUILD_TESTING=YES TB --- 2012-08-20 16:58:52 - MAKEOBJDIRPREFIX=/obj TB --- 2012-08-20 16:58:52 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-08-20 16:58:52 - SRCCONF=/dev/null TB --- 2012-08-20 16:58:52 - TARGET=i386 TB --- 2012-08-20 16:58:52 - TARGET_ARCH=i386 TB --- 2012-08-20 16:58:52 - TZ=UTC TB --- 2012-08-20 16:58:52 - __MAKE_CONF=/dev/null TB --- 2012-08-20 16:58:52 - cd /src TB --- 2012-08-20 16:58:52 - /usr/bin/make -B buildworld >>> World build started on Mon Aug 20 16:58:54 UTC 2012 >>> 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 Mon Aug 20 19:31:14 UTC 2012 TB --- 2012-08-20 19:31:14 - generating LINT kernel config TB --- 2012-08-20 19:31:14 - cd /src/sys/i386/conf TB --- 2012-08-20 19:31:14 - /usr/bin/make -B LINT TB --- 2012-08-20 19:31:14 - cd /src/sys/i386/conf TB --- 2012-08-20 19:31:14 - /usr/sbin/config -m LINT TB --- 2012-08-20 19:31:14 - building LINT kernel TB --- 2012-08-20 19:31:14 - CROSS_BUILD_TESTING=YES TB --- 2012-08-20 19:31:14 - MAKEOBJDIRPREFIX=/obj TB --- 2012-08-20 19:31:14 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-08-20 19:31:14 - SRCCONF=/dev/null TB --- 2012-08-20 19:31:14 - TARGET=i386 TB --- 2012-08-20 19:31:14 - TARGET_ARCH=i386 TB --- 2012-08-20 19:31:14 - TZ=UTC TB --- 2012-08-20 19:31:14 - __MAKE_CONF=/dev/null TB --- 2012-08-20 19:31:14 - cd /src TB --- 2012-08-20 19:31:14 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Mon Aug 20 19:31:14 UTC 2012 >>> 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 -c -O2 -pipe -fno-strict-aliasing -std=c99 -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 -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-sse -msoft-float -ffreestanding -fstack-protector -Werror -pg -mprofiler-epilogue /src/sys/dev/ath/if_ath_beacon.c -I/src/sys/dev/ath cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -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 -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-sse -msoft-float -ffreestanding -fstack-protector -Werror -pg -mprofiler-epilogue /src/sys/dev/ath/if_ath_debug.c -I/src/sys/dev/ath cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -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 -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-sse -msoft-float -ffreestanding -fstack-protector -Werror -pg -mprofiler-epilogue /src/sys/dev/ath/if_ath_keycache.c -I/src/sys/dev/ath cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -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 -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-sse -msoft-float -ffreestanding -fstack-protector -Werror -pg -mprofiler-epilogue /src/sys/dev/ath/if_ath_led.c -I/src/sys/dev/ath cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -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 -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-sse -msoft-float -ffreestanding -fstack-protector -Werror -pg -mprofiler-epilogue /src/sys/dev/ath/if_ath_tx.c -I/src/sys/dev/ath cc1: warnings being treated as errors /src/sys/dev/ath/if_ath_tx.c: In function 'ath_tx_chaindesclist': /src/sys/dev/ath/if_ath_tx.c:310: warning: unused variable 'qnum' [-Wunused-variable] *** Error code 1 Stop in /obj/i386.i386/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2012-08-20 19:40:33 - WARNING: /usr/bin/make returned exit code 1 TB --- 2012-08-20 19:40:33 - ERROR: failed to build LINT kernel TB --- 2012-08-20 19:40:33 - 6816.80 user 990.07 system 10233.27 real http://tinderbox.freebsd.org/tinderbox-head-HEAD-i386-i386.full From owner-freebsd-current@FreeBSD.ORG Mon Aug 20 19:43:16 2012 Return-Path: Delivered-To: current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C93A7106564A; Mon, 20 Aug 2012 19:43:16 +0000 (UTC) (envelope-from bapt@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id B0AB08FC0A; Mon, 20 Aug 2012 19:43:16 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q7KJhGL9019474; Mon, 20 Aug 2012 19:43:16 GMT (envelope-from bapt@FreeBSD.org) Received: (from bapt@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q7KJhGCI019473; Mon, 20 Aug 2012 19:43:16 GMT (envelope-from bapt@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: bapt set sender to bapt@FreeBSD.org using -f Date: Mon, 20 Aug 2012 21:43:13 +0200 From: Baptiste Daroussin To: ports@FreeBSD.org, current@FreeBSD.org Message-ID: <20120820194313.GC23607@ithaqua.etoilebsd.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="sHrvAb52M6C8blB9" Content-Disposition: inline User-Agent: Mutt/1.5.21 (2010-09-15) Cc: Subject: pkgng 1.0 release schedule, and HEAD switch to pkgng by default schedule X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 20 Aug 2012 19:43:16 -0000 --sHrvAb52M6C8blB9 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hi all, Since 1.0-rc6 release, everything looks ready for a final release of 1.0, I'll give more details on the release commit bit :) this is planned for 30th august 2012. Current was supposed to switch to pkgng by default today, it has been delayed until the nvidia-driver is fixed with pkgng. Thanksfully kwm@ and danfe@ has been working on this, and the situation should be fixed pretty soon. Please continue testing pkgng and reporting bugs, if you are new comers do not hesitate to ask question about pkgng so that we can improve documentation: The usual links about pkgng: - http://wiki.freebsd.org/pkgng - http://wiki.freebsd.org/PkgPrimer - https://github.com/pkgng/pkgng/blob/master/FAQ.md - http://people.freebsd.org/~bapt/pres-pkgng-bsdcan.pdf - http://www.youtube.com/watch?v=4Hxq7AHZ27I regards, Bapt --sHrvAb52M6C8blB9 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEARECAAYFAlAyk1EACgkQ8kTtMUmk6EypcACfQAr1XgcxHODQByyOAxljS0xw s4YAoKBMuzMzVYkLTCHUSuY/+Ly25Hvy =x+HW -----END PGP SIGNATURE----- --sHrvAb52M6C8blB9-- From owner-freebsd-current@FreeBSD.ORG Mon Aug 20 20:18:34 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5ECF61065678; Mon, 20 Aug 2012 20:18:34 +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 2D12C8FC08; Mon, 20 Aug 2012 20:18:33 +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 q7KKIXMc056634; Mon, 20 Aug 2012 16:18:33 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-current.sentex.ca (8.14.5/8.14.5/Submit) id q7KKIXAR056632; Mon, 20 Aug 2012 20:18:33 GMT (envelope-from tinderbox@freebsd.org) Date: Mon, 20 Aug 2012 20:18:33 GMT Message-Id: <201208202018.q7KKIXAR056632@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 , , Precedence: bulk Cc: Subject: [head tinderbox] failure on amd64/amd64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Aug 2012 20:18:34 -0000 TB --- 2012-08-20 16:50:00 - tinderbox 2.9 running on freebsd-current.sentex.ca TB --- 2012-08-20 16:50:00 - 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 --- 2012-08-20 16:50:00 - starting HEAD tinderbox run for amd64/amd64 TB --- 2012-08-20 16:50:00 - cleaning the object tree TB --- 2012-08-20 16:59:38 - cvsupping the source tree TB --- 2012-08-20 16:59:38 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/amd64/amd64/supfile TB --- 2012-08-20 17:00:33 - building world TB --- 2012-08-20 17:00:33 - CROSS_BUILD_TESTING=YES TB --- 2012-08-20 17:00:33 - MAKEOBJDIRPREFIX=/obj TB --- 2012-08-20 17:00:33 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-08-20 17:00:33 - SRCCONF=/dev/null TB --- 2012-08-20 17:00:33 - TARGET=amd64 TB --- 2012-08-20 17:00:33 - TARGET_ARCH=amd64 TB --- 2012-08-20 17:00:33 - TZ=UTC TB --- 2012-08-20 17:00:33 - __MAKE_CONF=/dev/null TB --- 2012-08-20 17:00:33 - cd /src TB --- 2012-08-20 17:00:33 - /usr/bin/make -B buildworld >>> World build started on Mon Aug 20 17:00:34 UTC 2012 >>> 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 >>> stage 5.1: building 32 bit shim libraries >>> World build completed on Mon Aug 20 20:09:36 UTC 2012 TB --- 2012-08-20 20:09:36 - generating LINT kernel config TB --- 2012-08-20 20:09:36 - cd /src/sys/amd64/conf TB --- 2012-08-20 20:09:36 - /usr/bin/make -B LINT TB --- 2012-08-20 20:09:36 - cd /src/sys/amd64/conf TB --- 2012-08-20 20:09:36 - /usr/sbin/config -m LINT TB --- 2012-08-20 20:09:36 - building LINT kernel TB --- 2012-08-20 20:09:36 - CROSS_BUILD_TESTING=YES TB --- 2012-08-20 20:09:36 - MAKEOBJDIRPREFIX=/obj TB --- 2012-08-20 20:09:36 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-08-20 20:09:36 - SRCCONF=/dev/null TB --- 2012-08-20 20:09:36 - TARGET=amd64 TB --- 2012-08-20 20:09:36 - TARGET_ARCH=amd64 TB --- 2012-08-20 20:09:36 - TZ=UTC TB --- 2012-08-20 20:09:36 - __MAKE_CONF=/dev/null TB --- 2012-08-20 20:09:36 - cd /src TB --- 2012-08-20 20:09:36 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Mon Aug 20 20:09:37 UTC 2012 >>> 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 -c -O2 -frename-registers -pipe -fno-strict-aliasing -std=c99 -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 -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -Werror -pg -mprofiler-epilogue /src/sys/dev/ath/if_ath_beacon.c -I/src/sys/dev/ath cc -c -O2 -frename-registers -pipe -fno-strict-aliasing -std=c99 -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 -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -Werror -pg -mprofiler-epilogue /src/sys/dev/ath/if_ath_debug.c -I/src/sys/dev/ath cc -c -O2 -frename-registers -pipe -fno-strict-aliasing -std=c99 -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 -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -Werror -pg -mprofiler-epilogue /src/sys/dev/ath/if_ath_keycache.c -I/src/sys/dev/ath cc -c -O2 -frename-registers -pipe -fno-strict-aliasing -std=c99 -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 -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -Werror -pg -mprofiler-epilogue /src/sys/dev/ath/if_ath_led.c -I/src/sys/dev/ath cc -c -O2 -frename-registers -pipe -fno-strict-aliasing -std=c99 -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 -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mno-mmx -mno-sse -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -Werror -pg -mprofiler-epilogue /src/sys/dev/ath/if_ath_tx.c -I/src/sys/dev/ath cc1: warnings being treated as errors /src/sys/dev/ath/if_ath_tx.c: In function 'ath_tx_chaindesclist': /src/sys/dev/ath/if_ath_tx.c:310: warning: unused variable 'qnum' [-Wunused-variable] *** Error code 1 Stop in /obj/amd64.amd64/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2012-08-20 20:18:33 - WARNING: /usr/bin/make returned exit code 1 TB --- 2012-08-20 20:18:33 - ERROR: failed to build LINT kernel TB --- 2012-08-20 20:18:33 - 8251.34 user 1306.14 system 12513.00 real http://tinderbox.freebsd.org/tinderbox-head-HEAD-amd64-amd64.full From owner-freebsd-current@FreeBSD.ORG Mon Aug 20 20:20:20 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1ED7F106564A; Mon, 20 Aug 2012 20:20: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 DA1598FC15; Mon, 20 Aug 2012 20:20: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 q7KKKIGb064850; Mon, 20 Aug 2012 16:20:18 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-current.sentex.ca (8.14.5/8.14.5/Submit) id q7KKKIaA064841; Mon, 20 Aug 2012 20:20:18 GMT (envelope-from tinderbox@freebsd.org) Date: Mon, 20 Aug 2012 20:20:18 GMT Message-Id: <201208202020.q7KKKIaA064841@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 , , Precedence: bulk Cc: Subject: [head tinderbox] failure on ia64/ia64 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Aug 2012 20:20:20 -0000 TB --- 2012-08-20 18:30:32 - tinderbox 2.9 running on freebsd-current.sentex.ca TB --- 2012-08-20 18:30:32 - 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 --- 2012-08-20 18:30:32 - starting HEAD tinderbox run for ia64/ia64 TB --- 2012-08-20 18:30:32 - cleaning the object tree TB --- 2012-08-20 18:31:21 - cvsupping the source tree TB --- 2012-08-20 18:31:21 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/ia64/ia64/supfile TB --- 2012-08-20 18:31:58 - building world TB --- 2012-08-20 18:31:58 - CROSS_BUILD_TESTING=YES TB --- 2012-08-20 18:31:58 - MAKEOBJDIRPREFIX=/obj TB --- 2012-08-20 18:31:58 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-08-20 18:31:58 - SRCCONF=/dev/null TB --- 2012-08-20 18:31:58 - TARGET=ia64 TB --- 2012-08-20 18:31:58 - TARGET_ARCH=ia64 TB --- 2012-08-20 18:31:58 - TZ=UTC TB --- 2012-08-20 18:31:58 - __MAKE_CONF=/dev/null TB --- 2012-08-20 18:31:58 - cd /src TB --- 2012-08-20 18:31:58 - /usr/bin/make -B buildworld >>> World build started on Mon Aug 20 18:31:59 UTC 2012 >>> 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 Mon Aug 20 20:13:41 UTC 2012 TB --- 2012-08-20 20:13:41 - generating LINT kernel config TB --- 2012-08-20 20:13:41 - cd /src/sys/ia64/conf TB --- 2012-08-20 20:13:41 - /usr/bin/make -B LINT TB --- 2012-08-20 20:13:41 - cd /src/sys/ia64/conf TB --- 2012-08-20 20:13:41 - /usr/sbin/config -m LINT TB --- 2012-08-20 20:13:41 - building LINT kernel TB --- 2012-08-20 20:13:41 - CROSS_BUILD_TESTING=YES TB --- 2012-08-20 20:13:41 - MAKEOBJDIRPREFIX=/obj TB --- 2012-08-20 20:13:41 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-08-20 20:13:41 - SRCCONF=/dev/null TB --- 2012-08-20 20:13:41 - TARGET=ia64 TB --- 2012-08-20 20:13:41 - TARGET_ARCH=ia64 TB --- 2012-08-20 20:13:41 - TZ=UTC TB --- 2012-08-20 20:13:41 - __MAKE_CONF=/dev/null TB --- 2012-08-20 20:13:41 - cd /src TB --- 2012-08-20 20:13:41 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Mon Aug 20 20:13:41 UTC 2012 >>> 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 -c -O2 -pipe -fno-strict-aliasing -std=c99 -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 -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/ia64/libuwx/src -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mconstant-gp -ffixed-r13 -mfixed-range=f32-f127 -fpic -ffreestanding -Werror /src/sys/dev/ath/if_ath_beacon.c -I/src/sys/dev/ath cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -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 -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/ia64/libuwx/src -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mconstant-gp -ffixed-r13 -mfixed-range=f32-f127 -fpic -ffreestanding -Werror /src/sys/dev/ath/if_ath_debug.c -I/src/sys/dev/ath cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -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 -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/ia64/libuwx/src -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mconstant-gp -ffixed-r13 -mfixed-range=f32-f127 -fpic -ffreestanding -Werror /src/sys/dev/ath/if_ath_keycache.c -I/src/sys/dev/ath cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -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 -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/ia64/libuwx/src -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mconstant-gp -ffixed-r13 -mfixed-range=f32-f127 -fpic -ffreestanding -Werror /src/sys/dev/ath/if_ath_led.c -I/src/sys/dev/ath cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -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 -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/ia64/libuwx/src -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mconstant-gp -ffixed-r13 -mfixed-range=f32-f127 -fpic -ffreestanding -Werror /src/sys/dev/ath/if_ath_tx.c -I/src/sys/dev/ath cc1: warnings being treated as errors /src/sys/dev/ath/if_ath_tx.c: In function 'ath_tx_chaindesclist': /src/sys/dev/ath/if_ath_tx.c:310: warning: unused variable 'qnum' [-Wunused-variable] *** Error code 1 Stop in /obj/ia64.ia64/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2012-08-20 20:20:18 - WARNING: /usr/bin/make returned exit code 1 TB --- 2012-08-20 20:20:18 - ERROR: failed to build LINT kernel TB --- 2012-08-20 20:20:18 - 4562.62 user 714.12 system 6586.10 real http://tinderbox.freebsd.org/tinderbox-head-HEAD-ia64-ia64.full From owner-freebsd-current@FreeBSD.ORG Mon Aug 20 21:06:52 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3A2401065670 for ; Mon, 20 Aug 2012 21:06:52 +0000 (UTC) (envelope-from peter@rulingia.com) Received: from vps.rulingia.com (host-122-100-2-194.octopus.com.au [122.100.2.194]) by mx1.freebsd.org (Postfix) with ESMTP id BD6F08FC16 for ; Mon, 20 Aug 2012 21:06:51 +0000 (UTC) Received: from aspire.rulingia.com (12.58.233.220.static.exetel.com.au [220.233.58.12]) by vps.rulingia.com (8.14.5/8.14.5) with ESMTP id q7KL6eHD079326 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 21 Aug 2012 07:06:44 +1000 (EST) (envelope-from peter@rulingia.com) Received: from aspire.rulingia.com (localhost [127.0.0.1]) by aspire.rulingia.com (8.14.5/8.14.5) with ESMTP id q7KKijQx042827 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 21 Aug 2012 06:45:15 +1000 (EST) (envelope-from peter@aspire.rulingia.com) Received: (from peter@localhost) by aspire.rulingia.com (8.14.5/8.14.5/Submit) id q7KKiiBO042826; Tue, 21 Aug 2012 06:44:44 +1000 (EST) (envelope-from peter) Date: Tue, 21 Aug 2012 06:44:44 +1000 From: Peter Jeremy To: Randy Bush Message-ID: <20120820204444.GA27130@aspire.rulingia.com> References: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="u3/rZRmxL6MmkK24" Content-Disposition: inline In-Reply-To: X-PGP-Key: http://www.rulingia.com/keys/peter.pgp User-Agent: Mutt/1.5.21 (2010-09-15) Cc: FreeBSD Current Subject: Re: buildworld c++ internal error X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 20 Aug 2012 21:06:52 -0000 --u3/rZRmxL6MmkK24 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2012-Aug-20 07:17:59 +0900, Randy Bush wrote: >the only thing a night's sleep got me was the idea of attaching an >external sata drive and putting swap on it. You can also swap to a file via NFS. --=20 Peter Jeremy --u3/rZRmxL6MmkK24 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEARECAAYFAlAyobwACgkQ/opHv/APuIdpywCguPjqGRwsOqCKf+7Zpg9YGZC/ uaMAni84mBVpQzhWZ8WX6LQw5oQO1HaY =bEIr -----END PGP SIGNATURE----- --u3/rZRmxL6MmkK24-- From owner-freebsd-current@FreeBSD.ORG Mon Aug 20 21:25:16 2012 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 281F0106564A; Mon, 20 Aug 2012 21:25:16 +0000 (UTC) (envelope-from simon@FreeBSD.org) Received: from emx.nitro.dk (emx.nitro.dk [IPv6:2a01:4f8:120:7384::102]) by mx1.freebsd.org (Postfix) with ESMTP id A74AE8FC0C; Mon, 20 Aug 2012 21:25:15 +0000 (UTC) Received: from mailscan.leto.nitro.dk (mailscan.leto.nitro.dk [127.0.1.4]) by emx.nitro.dk (Postfix) with ESMTP id D0F0C2B573A; Mon, 20 Aug 2012 21:25:14 +0000 (UTC) Received: from emx.nitro.dk ([127.0.1.2]) by mailscan.leto.nitro.dk (mailscan.leto.nitro.dk [127.0.1.4]) (amavisd-new, port 10024) with LMTP id Iuz68t91ZSFk; Mon, 20 Aug 2012 21:25:12 +0000 (UTC) Received: from zaphod.local (unknown [89.100.2.68]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by emx.nitro.dk (Postfix) with ESMTPSA id 75F4A2B5736; Mon, 20 Aug 2012 21:25:12 +0000 (UTC) Message-ID: <5032AB28.9070306@FreeBSD.org> Date: Mon, 20 Aug 2012 22:24:56 +0100 From: "Simon L. B. Nielsen" Organization: FreeBSD Security Team User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:13.0) Gecko/20120614 Thunderbird/13.0.1 MIME-Version: 1.0 To: freebsd-security@FreeBSD.org, freebsd-current@FreeBSD.org X-Enigmail-Version: 1.4.3 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigC0A5E7BB9CE9D73AFB4E2313" Cc: Subject: [HEADSUP] geli(4) weak master key generation on -CURRENT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 20 Aug 2012 21:25:16 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigC0A5E7BB9CE9D73AFB4E2313 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hello, If you are not using geli(4) on -CURRENT (AKA FreeBSD 10) you can safely ignore this mail. If you are, please read on! -CURRENT users of geli(4) should be advised that, a geli(4) device may have weak master key, if the provider is created on -CURRENT system built against source code between r238116 (Jul 4 17:54:17 2012 UTC) and r239184 (non-inclusive, Aug 10 18:43:29 2012 UTC). One can verify if its provider was created with weak keys by running: # geli dump | grep version If the version is 7 and the system did not include this fix (r239184) when provider was initialized, then the data has to be backed up, underlying provider overwritten with random data, system upgraded and provider recreated. Thanks to Fabian Keil for reporting the issue, Pawel Jakub Dawidek for fixing it, and Xin Li for drafting this text. PS. This only affects FreeBSD 10 / -CURRENT, and as -CURRENT isn't supported by the FreeBSD Security Team, we are not releasing an advisory, just this heads up. --=20 Simon L. B. Nielsen FreeBSD Security Officer --------------enigC0A5E7BB9CE9D73AFB4E2313 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 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlAyqzcACgkQFdaIBMps37LryQCfSCa1m271tv/9b1Wsr88++C2M cNYAmweTW7GrVIy4EYtsuza/s5Jd5wKq =N/Dw -----END PGP SIGNATURE----- --------------enigC0A5E7BB9CE9D73AFB4E2313-- From owner-freebsd-current@FreeBSD.ORG Mon Aug 20 21:53:49 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id DA6D0106564A for ; Mon, 20 Aug 2012 21:53:49 +0000 (UTC) (envelope-from randy@psg.com) Received: from ran.psg.com (ran.psg.com [IPv6:2001:418:1::36]) by mx1.freebsd.org (Postfix) with ESMTP id BDDC18FC0A for ; Mon, 20 Aug 2012 21:53:49 +0000 (UTC) Received: from localhost ([127.0.0.1] helo=rair.psg.com.psg.com) by ran.psg.com with esmtp (Exim 4.80 (FreeBSD)) (envelope-from ) id 1T3Zuu-0000I5-5F for freebsd-current@freebsd.org; Mon, 20 Aug 2012 21:53:48 +0000 Date: Tue, 21 Aug 2012 06:54:08 +0900 Message-ID: From: Randy Bush To: FreeBSD Current In-Reply-To: <20120820204444.GA27130@aspire.rulingia.com> References: <20120820204444.GA27130@aspire.rulingia.com> User-Agent: Wanderlust/2.15.9 (Almost Unreal) Emacs/22.3 Mule/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.7 - "Harue") Content-Type: text/plain; charset=US-ASCII Subject: Re: buildworld c++ internal error X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 20 Aug 2012 21:53:49 -0000 -O allowed it to buildworld! randy From owner-freebsd-current@FreeBSD.ORG Mon Aug 20 21:57:21 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id DAA2C106564A for ; Mon, 20 Aug 2012 21:57:21 +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 8B3D58FC15 for ; Mon, 20 Aug 2012 21:57:21 +0000 (UTC) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost1.zedat.fu-berlin.de (Exim 4.69) with esmtp (envelope-from ) id <1T3ZyJ-0008Sz-T9>; Mon, 20 Aug 2012 23:57:20 +0200 Received: from e178002159.adsl.alicedsl.de ([85.178.2.159] helo=thor.walstatt.dyndns.org) by inpost2.zedat.fu-berlin.de (Exim 4.69) with esmtpsa (envelope-from ) id <1T3ZyJ-0006dP-Nb>; Mon, 20 Aug 2012 23:57:19 +0200 Message-ID: <5032B2BA.9090204@zedat.fu-berlin.de> Date: Mon, 20 Aug 2012 23:57:14 +0200 From: "O. Hartmann" User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:14.0) Gecko/20120810 Thunderbird/14.0 MIME-Version: 1.0 To: Adam McDougall References: <502D12C0.2060405@zedat.fu-berlin.de> <502F4D46.60907@zedat.fu-berlin.de> <502FFBAF.50003@egr.msu.edu> In-Reply-To: <502FFBAF.50003@egr.msu.edu> X-Enigmail-Version: 1.4.3 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig4FE1AD6D68C1E6B590FC7107" X-Originating-IP: 85.178.2.159 Cc: freebsd-current@freebsd.org Subject: Re: OpenLDAP/SASL2 problem in FreeBSD 10.0-CURRENT WAS: Re: HELP! core dumps: install, mtree, et cetera all of the sudden after portmaster security/cyrus-sasl2 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 20 Aug 2012 21:57:21 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig4FE1AD6D68C1E6B590FC7107 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Am 08/18/12 22:31, schrieb Adam McDougall: > On 8/18/2012 4:07 AM, O. Hartmann wrote: >> My setups on all boxes using OpenLDAP, the port >> net/opendldap24-client/server has security/cyrus-sasl2 enabled. >> I use nsswitch and nascd. >> >> The problem: >> I can not anymore install or reinstall (using portmaster, patched for >> pkgng) the ports >> >> security/cyrus-sasl2 >> net/openldap24-client >> >> When performing an update (no matter which one), The installation >> process dies when installing the packages (see error for openldap-clei= nt >> below, it is proxy for cyrus-sasl2 also). >> >> After a failed installation, close to all binaries I touch start to >> coredump in a mustang way. ls(1) works, but ls -la dumps core (resolvi= ng >> the ownership-issue?). >> >> The only way to "save" the box is to copy missing libldap_r-2.4.so.8 o= r >> libsasl2.so.2 to /usr/local/lib/ from another, compatible box or from = a >> backup. >> >> It is impossible to me to update/reinstall either net/openldap24-clien= t >> or security/cyrus-sasl2. >> >> =3D=3D=3D> Installing for openldap-sasl-client-2.4.32_1 >> =3D=3D=3D> Generating temporary packing list >> Segmentation fault (core dumped) >> *** [install-mtree] Error code 139 >> > What happens if you disable both LDAP and cache support from NSS before= > upgrading either of those two packages? Installing files certainly mus= t > invoke functions that need to translate owners/groups to uid/gid so per= haps > something related to that suddenly fails during an attempt to replace > the library. It sounds like if your LDAP support becomes corrupt, then= > it leaves a gaping hole in the NSS critical path that many parts of the= > system must be using. When you run into this situation and can resolve= > it easily by replacing the old ldap library, is the old one corrupt? > Missing? Can you save a copy for evaluation? Does your system break i= n > a similar manner simply by renaming the LDAP library, or does it behave= > worse only if there is a faulty LDAP library being used by nss_ldap? I see the same issue in single user mode, when nscd isn't running. But /etc/pam.d/system delegates to LDAP for non-local id. When the issues arise, the open ldap library libldap_r.so isn't available anymore because something run wrong during the update. I dumped portmaster, use portupgrade at the moment. It seems, that this works so far, no matter why. When that happened (also with libsasl2.so, the same), I have to use /rescue/tar to extract the backup found in /usr/ports/packages/portmaster-backup/. bsdtar also fails. I can't say the LDAP lib is worse. It is simply missing after the installation ran rogue. At the moment, I try to dump also pkg and run the old pkg_xxx stuff again. Maybe something got corrupt when I swapped to pkgng or pkgng has a serious bug not capable of handling those situations. or I was too brave using the patched portmaster in the first place, which compromised my installation and the problems I face now are a consequnce of some hidden problems elsewere ... --------------enig4FE1AD6D68C1E6B590FC7107 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.0.19 (FreeBSD) iQEcBAEBAgAGBQJQMrK/AAoJEOgBcD7A/5N8Zb4H/RHPjHHw3pNJnal3LV5EG2qH agVUMYPD+WCfXf46qUaYQg3PyGIKJuWyE0D/0xijiBRrNrM/vN441fo1yBZi40hZ K8yftehZX36fDEIGgRpyHF9Vn8RbxTVf78nnc1We4aGDcmw3j2DVlwP22s0uWtY0 tCmUX43zCq6j7YWin6WAiqlaO0aS7z8dofi8s8komEqfpgEPVgHfTyP7hp3yjZvz AihrqGiA5aWG9PxDbboB0P5mPPg/2dn+EeNpOIRkdfS6698OVR671U1Uh6trgBgp L7GiArvYLsdJLN5Oa9zlXlQIgvypZGWab3c/d+otA9iL/xi8pgzAdsCLFpdatV8= =Pni3 -----END PGP SIGNATURE----- --------------enig4FE1AD6D68C1E6B590FC7107-- From owner-freebsd-current@FreeBSD.ORG Mon Aug 20 22:08:26 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4C306106564A; Mon, 20 Aug 2012 22:08:26 +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 1AAD68FC0A; Mon, 20 Aug 2012 22:08:25 +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 q7KM8PNo012223; Mon, 20 Aug 2012 18:08:25 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-current.sentex.ca (8.14.5/8.14.5/Submit) id q7KM8P4q012216; Mon, 20 Aug 2012 22:08:25 GMT (envelope-from tinderbox@freebsd.org) Date: Mon, 20 Aug 2012 22:08:25 GMT Message-Id: <201208202208.q7KM8P4q012216@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 , , Precedence: bulk Cc: Subject: [head tinderbox] failure on powerpc/powerpc X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Aug 2012 22:08:26 -0000 TB --- 2012-08-20 19:40:33 - tinderbox 2.9 running on freebsd-current.sentex.ca TB --- 2012-08-20 19:40:33 - 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 --- 2012-08-20 19:40:33 - starting HEAD tinderbox run for powerpc/powerpc TB --- 2012-08-20 19:40:34 - cleaning the object tree TB --- 2012-08-20 19:42:59 - cvsupping the source tree TB --- 2012-08-20 19:42:59 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/powerpc/powerpc/supfile TB --- 2012-08-20 19:44:00 - building world TB --- 2012-08-20 19:44:00 - CROSS_BUILD_TESTING=YES TB --- 2012-08-20 19:44:00 - MAKEOBJDIRPREFIX=/obj TB --- 2012-08-20 19:44:00 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-08-20 19:44:00 - SRCCONF=/dev/null TB --- 2012-08-20 19:44:00 - TARGET=powerpc TB --- 2012-08-20 19:44:00 - TARGET_ARCH=powerpc TB --- 2012-08-20 19:44:00 - TZ=UTC TB --- 2012-08-20 19:44:00 - __MAKE_CONF=/dev/null TB --- 2012-08-20 19:44:00 - cd /src TB --- 2012-08-20 19:44:00 - /usr/bin/make -B buildworld >>> World build started on Mon Aug 20 19:44:01 UTC 2012 >>> 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 Mon Aug 20 22:04:04 UTC 2012 TB --- 2012-08-20 22:04:04 - generating LINT kernel config TB --- 2012-08-20 22:04:04 - cd /src/sys/powerpc/conf TB --- 2012-08-20 22:04:04 - /usr/bin/make -B LINT TB --- 2012-08-20 22:04:04 - cd /src/sys/powerpc/conf TB --- 2012-08-20 22:04:04 - /usr/sbin/config -m LINT TB --- 2012-08-20 22:04:04 - building LINT kernel TB --- 2012-08-20 22:04:04 - CROSS_BUILD_TESTING=YES TB --- 2012-08-20 22:04:04 - MAKEOBJDIRPREFIX=/obj TB --- 2012-08-20 22:04:04 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-08-20 22:04:04 - SRCCONF=/dev/null TB --- 2012-08-20 22:04:04 - TARGET=powerpc TB --- 2012-08-20 22:04:04 - TARGET_ARCH=powerpc TB --- 2012-08-20 22:04:04 - TZ=UTC TB --- 2012-08-20 22:04:04 - __MAKE_CONF=/dev/null TB --- 2012-08-20 22:04:04 - cd /src TB --- 2012-08-20 22:04:04 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Mon Aug 20 22:04:04 UTC 2012 >>> 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 -c -O -pipe -std=c99 -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 -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/libfdt -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -msoft-float -Wa,-many -fno-omit-frame-pointer -msoft-float -mno-altivec -ffreestanding -fstack-protector -Werror /src/sys/dev/ath/if_ath_beacon.c -I/src/sys/dev/ath cc -c -O -pipe -std=c99 -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 -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/libfdt -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -msoft-float -Wa,-many -fno-omit-frame-pointer -msoft-float -mno-altivec -ffreestanding -fstack-protector -Werror /src/sys/dev/ath/if_ath_debug.c -I/src/sys/dev/ath cc -c -O -pipe -std=c99 -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 -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/libfdt -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -msoft-float -Wa,-many -fno-omit-frame-pointer -msoft-float -mno-altivec -ffreestanding -fstack-protector -Werror /src/sys/dev/ath/if_ath_keycache.c -I/src/sys/dev/ath cc -c -O -pipe -std=c99 -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 -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/libfdt -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -msoft-float -Wa,-many -fno-omit-frame-pointer -msoft-float -mno-altivec -ffreestanding -fstack-protector -Werror /src/sys/dev/ath/if_ath_led.c -I/src/sys/dev/ath cc -c -O -pipe -std=c99 -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 -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/libfdt -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -msoft-float -Wa,-many -fno-omit-frame-pointer -msoft-float -mno-altivec -ffreestanding -fstack-protector -Werror /src/sys/dev/ath/if_ath_tx.c -I/src/sys/dev/ath cc1: warnings being treated as errors /src/sys/dev/ath/if_ath_tx.c: In function 'ath_tx_chaindesclist': /src/sys/dev/ath/if_ath_tx.c:310: warning: unused variable 'qnum' [-Wunused-variable] *** Error code 1 Stop in /obj/powerpc.powerpc/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2012-08-20 22:08:25 - WARNING: /usr/bin/make returned exit code 1 TB --- 2012-08-20 22:08:25 - ERROR: failed to build LINT kernel TB --- 2012-08-20 22:08:25 - 6855.27 user 928.74 system 8871.12 real http://tinderbox.freebsd.org/tinderbox-head-HEAD-powerpc-powerpc.full From owner-freebsd-current@FreeBSD.ORG Tue Aug 21 02:16:52 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2B648106566B; Tue, 21 Aug 2012 02:16:52 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.freebsd.org (Postfix) with ESMTP id D23C08FC12; Tue, 21 Aug 2012 02:16:51 +0000 (UTC) Received: from [127.0.0.1] (Scott4long@pooker.samsco.org [168.103.85.57]) (authenticated bits=0) by pooker.samsco.org (8.14.5/8.14.5) with ESMTP id q7L1xgmS050717; Mon, 20 Aug 2012 19:59:42 -0600 (MDT) (envelope-from scottl@samsco.org) Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 (Mac OS X Mail 6.0 \(1485\)) From: Scott Long In-Reply-To: <50300C6D.3030501@feral.com> Date: Mon, 20 Aug 2012 19:59:42 -0600 Content-Transfer-Encoding: quoted-printable Message-Id: References: <6882.1345325806@critter.freebsd.dk> <50300C6D.3030501@feral.com> To: Matt Jacob X-Mailer: Apple Mail (2.1485) X-Spam-Status: No, score=-50.0 required=3.8 tests=ALL_TRUSTED, T_RP_MATCHES_RCVD autolearn=unavailable version=3.3.0 X-Spam-Checker-Version: SpamAssassin 3.3.0 (2010-01-18) on pooker.samsco.org Cc: Poul-Henning Kamp , freebsd-current@freebsd.org Subject: Re: BUFSIZ = 1024, still ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 21 Aug 2012 02:16:52 -0000 On Aug 18, 2012, at 3:43 PM, Matthew Jacob wrote: > On 8/18/2012 2:36 PM, Poul-Henning Kamp wrote: >> In message <50300540.9060906@feral.com>, Matthew Jacob writes: >>=20 >>> [...] that there might be a measurable >>> difference for having to copy 4K (unaligned) than 1K (unaligned) to >>> kernel space for disposition. >> Actually, as far as I'm aware, the 4K would be page-aligned by >> default due to our malloc(3) implementation. >>=20 >>> Wasn't there just a recent discussion about running 1.x binaries? >> 1.x binaries wouldn't notice and wouldn't be able to tell >> if BUFSIZ is different in 10.x > I wasn't concerned about those specifically- I was just using this as = an example of leaving stuff alone. >=20 >>> If you're going to talk about making a change to defaults, the = default >>> MAXPHYS and DLFTPHYS have been undersized for years now. >> Indeed, but as I understand it, those require device driver changes ? > Ah, well 10.X would be an ideal time to find out! >=20 This gets brought up from time to time, and I honestly thought that I = swept most of the problems up a few years ago. The mistake that I made = in the mlx driver that was recently corrected was evidence of a previous = sweep. If anyone wants to do another sweep, the thing to grep for is any = drivers that use MAXPHYS to size their i/o's. For the drivers that do = that, you then have to see if they can actually handle an arbitrary = number of scatter-gather elements. If they can't then they need to stop = using MAXPHYS and start using a constant that applies to the driver. My = quick scan shows the following would need to be investigated: sys/dev/ata (legacy ata) /sys/dev/isp /sys/dev/mmcsd /sys/dev/mvs The only other problem is that struct but contains an element sized on = MAXPHYS for doing swapper I/O. Increasing MAXPHYS will increase this, = and at one point I think that Alan Cox might have wanted to find a = better way to hold swap info. Otherwise, increasing MAXPHYS causes no = problems and is something that has run in production for quite some time = at places like Yahoo and Netflix. Scott From owner-freebsd-current@FreeBSD.ORG Tue Aug 21 02:26:09 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4E3091065670 for ; Tue, 21 Aug 2012 02:26:09 +0000 (UTC) (envelope-from mj@feral.com) Received: from ns1.feral.com (ns1.feral.com [192.67.166.1]) by mx1.freebsd.org (Postfix) with ESMTP id 012F68FC0A for ; Tue, 21 Aug 2012 02:26:08 +0000 (UTC) Received: from [192.168.135.103] (c-24-5-173-152.hsd1.ca.comcast.net [24.5.173.152]) (authenticated bits=0) by ns1.feral.com (8.14.4/8.14.4) with ESMTP id q7L2Q73O078618 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for ; Mon, 20 Aug 2012 19:26:07 -0700 (PDT) (envelope-from mj@feral.com) Message-ID: <5032F1BA.2080603@feral.com> Date: Mon, 20 Aug 2012 19:26:02 -0700 From: Matthew Jacob Organization: Feral Software User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0 MIME-Version: 1.0 To: freebsd-current@freebsd.org References: <6882.1345325806@critter.freebsd.dk> <50300C6D.3030501@feral.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (ns1.feral.com [192.67.166.1]); Mon, 20 Aug 2012 19:26:07 -0700 (PDT) Subject: Re: BUFSIZ = 1024, still ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Matt Jacob List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Aug 2012 02:26:09 -0000 On 8/20/2012 6:59 PM, Scott Long wrote: > On Aug 18, 2012, at 3:43 PM, Matthew Jacob wrote: > >> On 8/18/2012 2:36 PM, Poul-Henning Kamp wrote: >>> In message <50300540.9060906@feral.com>, Matthew Jacob writes: >>> >>>> [...] that there might be a measurable >>>> difference for having to copy 4K (unaligned) than 1K (unaligned) to >>>> kernel space for disposition. >>> Actually, as far as I'm aware, the 4K would be page-aligned by >>> default due to our malloc(3) implementation. >>> >>>> Wasn't there just a recent discussion about running 1.x binaries? >>> 1.x binaries wouldn't notice and wouldn't be able to tell >>> if BUFSIZ is different in 10.x >> I wasn't concerned about those specifically- I was just using this as an example of leaving stuff alone. >> >>>> If you're going to talk about making a change to defaults, the default >>>> MAXPHYS and DLFTPHYS have been undersized for years now. >>> Indeed, but as I understand it, those require device driver changes ? >> Ah, well 10.X would be an ideal time to find out! >> > This gets brought up from time to time, and I honestly thought that I swept most of the problems up a few years ago. The mistake that I made in the mlx driver that was recently corrected was evidence of a previous sweep. > > If anyone wants to do another sweep, the thing to grep for is any drivers that use MAXPHYS to size their i/o's. For the drivers that do that, you then have to see if they can actually handle an arbitrary number of scatter-gather elements. If they can't then they need to stop using MAXPHYS and start using a constant that applies to the driver. My quick scan shows the following would need to be investigated: > > sys/dev/ata (legacy ata) > /sys/dev/isp > /sys/dev/mmcsd > /sys/dev/mvs > > The only other problem is that struct but contains an element sized on MAXPHYS for doing swapper I/O. Increasing MAXPHYS will increase this, and at one point I think that Alan Cox might have wanted to find a better way to hold swap info. Otherwise, increasing MAXPHYS causes no problems and is something that has run in production for quite some time at places like Yahoo and Netflix. > > I think I merely asked whether we were going to increase the defaults. Are you suggesting we eliminate MAXPHYS for drivers entirely and just base upon the drivers' native limits? The isp driver very specifically uses MAXPHYS right now because it's a manifest constant. If we're eliminating it, that's fine by my. What mechanism will be used to break up transfers then? From owner-freebsd-current@FreeBSD.ORG Tue Aug 21 09:27:24 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7138A1065670 for ; Tue, 21 Aug 2012 09:27:24 +0000 (UTC) (envelope-from freebsd-current@m.gmane.org) Received: from plane.gmane.org (plane.gmane.org [80.91.229.3]) by mx1.freebsd.org (Postfix) with ESMTP id 25D798FC08 for ; Tue, 21 Aug 2012 09:27:23 +0000 (UTC) Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1T3kk5-0005Fk-Pn for freebsd-current@freebsd.org; Tue, 21 Aug 2012 11:27:21 +0200 Received: from lara.cc.fer.hr ([161.53.72.113]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 21 Aug 2012 11:27:21 +0200 Received: from ivoras by lara.cc.fer.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 21 Aug 2012 11:27:21 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-current@freebsd.org From: Ivan Voras Date: Tue, 21 Aug 2012 11:27:08 +0200 Lines: 33 Message-ID: References: <20120820194313.GC23607@ithaqua.etoilebsd.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigB62EFFDD29BF4F3567BE1129" X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: lara.cc.fer.hr User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:10.0) Gecko/20120213 Thunderbird/10.0 In-Reply-To: <20120820194313.GC23607@ithaqua.etoilebsd.net> X-Enigmail-Version: 1.3.5 Subject: Re: pkgng 1.0 release schedule, and HEAD switch to pkgng by default schedule X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 21 Aug 2012 09:27:24 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigB62EFFDD29BF4F3567BE1129 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 20/08/2012 21:43, Baptiste Daroussin wrote: > Hi all, >=20 > Since 1.0-rc6 release, everything looks ready for a final release of 1.= 0, I'll > give more details on the release commit bit :) this is planned for 30th= august > 2012. Congratulations, it's great! :) --------------enigB62EFFDD29BF4F3567BE1129 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.0.19 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlAzVGwACgkQ/QjVBj3/HSwJiACfUn6JISIU0VvaHVkAqivIjjky t3EAn1ja234qOUfmwOmHQbMj2dS9LNHH =PfXp -----END PGP SIGNATURE----- --------------enigB62EFFDD29BF4F3567BE1129-- From owner-freebsd-current@FreeBSD.ORG Tue Aug 21 09:39:53 2012 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E8B15106566B; Tue, 21 Aug 2012 09:39:53 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 0D7F28FC17; Tue, 21 Aug 2012 09:39:52 +0000 (UTC) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id MAA11195; Tue, 21 Aug 2012 12:39:45 +0300 (EEST) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1T3kw4-000G6A-SJ; Tue, 21 Aug 2012 12:39:44 +0300 Message-ID: <5033575E.1080000@FreeBSD.org> Date: Tue, 21 Aug 2012 12:39:42 +0300 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:14.0) Gecko/20120728 Thunderbird/14.0 MIME-Version: 1.0 To: freebsd-current@FreeBSD.org References: <6882.1345325806@critter.freebsd.dk> <50300C6D.3030501@feral.com> In-Reply-To: X-Enigmail-Version: 1.4.3 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Poul-Henning Kamp , Matt Jacob Subject: Re: BUFSIZ = 1024, still ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 21 Aug 2012 09:39:54 -0000 on 21/08/2012 04:59 Scott Long said the following: > This gets brought up from time to time, and I honestly thought that I swept > most of the problems up a few years ago. The mistake that I made in the mlx > driver that was recently corrected was evidence of a previous sweep. > > If anyone wants to do another sweep, the thing to grep for is any drivers > that use MAXPHYS to size their i/o's. For the drivers that do that, you then > have to see if they can actually handle an arbitrary number of scatter-gather > elements. If they can't then they need to stop using MAXPHYS and start using > a constant that applies to the driver. My quick scan shows the following > would need to be investigated: > > sys/dev/ata (legacy ata) /sys/dev/isp /sys/dev/mmcsd /sys/dev/mvs > > The only other problem is that struct but contains an element sized on > MAXPHYS for doing swapper I/O. Increasing MAXPHYS will increase this, and at > one point I think that Alan Cox might have wanted to find a better way to > hold swap info. Otherwise, increasing MAXPHYS causes no problems and is > something that has run in production for quite some time at places like Yahoo > and Netflix. I would like to use this opportunity to remind about another abuse in drivers: MAXBSIZE. This constant should be private to buffer cache / FS drivers layer, but some drivers abuse it for things related to physical I/O (mostly [only?] as bus_dma_tag_create parameter). -- Andriy Gapon From owner-freebsd-current@FreeBSD.ORG Tue Aug 21 10:11:43 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D0FEA106564A for ; Tue, 21 Aug 2012 10:11:43 +0000 (UTC) (envelope-from satan@ukr.net) Received: from hell.ukr.net (hell.ukr.net [212.42.67.68]) by mx1.freebsd.org (Postfix) with ESMTP id 90A9F8FC0A for ; Tue, 21 Aug 2012 10:11:43 +0000 (UTC) Received: from satan by hell.ukr.net with local ID 1T3lBH-0008jK-IY for current@freebsd.org; Tue, 21 Aug 2012 12:55:27 +0300 Date: Tue, 21 Aug 2012 12:55:27 +0300 From: Vitalij Satanivskij To: current@freebsd.org Message-ID: <20120821095527.GA33206@hell.ukr.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.21 (2010-09-15) Cc: Subject: dhclient cause up/down cycle after 239356 ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 21 Aug 2012 10:11:43 -0000 Hi all, After last update my home machine begin doin some strange things - Aug 21 08:28:25 home kernel: fxp0: link state changed to UP Aug 21 08:28:25 home kernel: fxp0: link state changed to DOWN Aug 21 08:28:27 home kernel: fxp0: link state changed to UP Aug 21 08:28:33 home dhclient: New IP Address (fxp0): xx.xx.xx.xx Aug 21 08:28:33 home kernel: fxp0: link state changed to DOWN Aug 21 08:28:33 home dhclient: New Subnet Mask (fxp0): 255.255.255.0 Aug 21 08:28:33 home dhclient: New Broadcast Address (fxp0): xx.xx.xx.255 Aug 21 08:28:33 home dhclient: New Routers (fxp0): xx.xx.xx.1 Aug 21 08:28:33 home dhclient[1395]: Interface fxp0 is down, dhclient exiting Aug 21 08:28:33 home dhclient[1339]: connection closed Aug 21 08:28:33 home dhclient[1339]: exiting. Aug 21 08:28:35 home kernel: fxp0: link state changed to UP Aug 21 08:28:35 home kernel: fxp0: link state changed to DOWN Aug 21 08:28:37 home kernel: fxp0: link state changed to UP Aug 21 08:28:40 home dhclient: New IP Address (fxp0): xx.xx.xx.xx Aug 21 08:28:40 home kernel: fxp0: link state changed to DOWN Aug 21 08:28:40 home dhclient: New Subnet Mask (fxp0): 255.255.255.0 Aug 21 08:28:40 home dhclient: New Broadcast Address (fxp0): xx.xx.xx.255 Aug 21 08:28:40 home dhclient: New Routers (fxp0): xx.xx.xx.1 Aug 21 08:28:40 home dhclient[1519]: Interface fxp0 is down, dhclient exiting Aug 21 08:28:40 home dhclient[1465]: connection closed Aug 21 08:28:40 home dhclient[1465]: exiting. Aug 21 08:28:42 home kernel: fxp0: link state changed to UP Aug 21 08:28:42 home kernel: fxp0: link state changed to DOWN Aug 21 08:28:44 home kernel: fxp0: link state changed to UP Aug 21 08:28:48 home dhclient: New IP Address (fxp0): xx.xx.xx.xx I have next configuration in rc.conf - ifconfig_fxp0="SYNCDHCP" in /etc/dhclient.conf interface "fxp0" { supersede domain-name "home"; supersede domain-name-servers 127.0.0.1; } Also /etc/start_if.fxp0 With content - ifconfig fxp0 ether xx:xx:xx:xx:xx:xx ifconfig fxp0 -tso ifconfig fxp0 polling And yes, no problem with static ip on fxp0 and no up/down sequence From owner-freebsd-current@FreeBSD.ORG Tue Aug 21 11:18:07 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5899A1065670 for ; Tue, 21 Aug 2012 11:18:07 +0000 (UTC) (envelope-from yanegomi@gmail.com) Received: from mail-ob0-f182.google.com (mail-ob0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id 1FA178FC18 for ; Tue, 21 Aug 2012 11:18:06 +0000 (UTC) Received: by obbun3 with SMTP id un3so14966251obb.13 for ; Tue, 21 Aug 2012 04:18:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=2aSBuTS+yA4Pv35usJ43189UHXm+Yt2GUD/914ts/CU=; b=kSMWjmJnedUsfm9KSLMC3XS5e0x7rirJJgiVmkEVfm/vYRdpZBQVMTs6yJyo4OAUKo WtXbouLOTKK+TBl7oAcguoXXZzqeoYuDVVa624zAEuzTcvijsIvKP39buSKGZGMAmwin FzOuzKw1vhqe7doTrpLUalGbpOjqefB+fXo6zQc0vDSkf2Hvw63qVhtFG/oLbPzKCtC8 eN2E/zfM8orE2awsS5miZNl+nu+k7s4tSWpIvKZVzMzGQVzV73SiQJ2RhfhyhihRAk8l B2qPBwk8plmLe0mqma6W3VGtSyOA23sJiL+7bnRGo0o5U0A6vMrGd3TuAIC9IHhD/vJC NIlA== MIME-Version: 1.0 Received: by 10.60.20.69 with SMTP id l5mr12401304oee.114.1345547885564; Tue, 21 Aug 2012 04:18:05 -0700 (PDT) Received: by 10.76.142.201 with HTTP; Tue, 21 Aug 2012 04:18:05 -0700 (PDT) In-Reply-To: <20120821095527.GA33206@hell.ukr.net> References: <20120821095527.GA33206@hell.ukr.net> Date: Tue, 21 Aug 2012 04:18:05 -0700 Message-ID: From: Garrett Cooper To: Vitalij Satanivskij Content-Type: text/plain; charset=ISO-8859-1 Cc: current@freebsd.org Subject: Re: dhclient cause up/down cycle after 239356 ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 21 Aug 2012 11:18:07 -0000 On Tue, Aug 21, 2012 at 2:55 AM, Vitalij Satanivskij wrote: > Hi all, > > After last update my home machine begin doin some strange things - ... Try reverting r239356 -- if that works, then please let jhb@ know. -Garrett From owner-freebsd-current@FreeBSD.ORG Tue Aug 21 11:40:42 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5025F10657C8; Tue, 21 Aug 2012 11:40:42 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from onlyone.friendlyhosting.spb.ru (onlyone.friendlyhosting.spb.ru [IPv6:2a01:4f8:131:60a2::2]) by mx1.freebsd.org (Postfix) with ESMTP id AA3A58FC1E; Tue, 21 Aug 2012 11:40:39 +0000 (UTC) Received: from lion.home.serebryakov.spb.ru (unknown [IPv6:2001:470:923f:1:8870:d54b:33e8:55b2]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.friendlyhosting.spb.ru (Postfix) with ESMTPA id 4E2934AC31; Tue, 21 Aug 2012 15:40:38 +0400 (MSK) Date: Tue, 21 Aug 2012 15:40:35 +0400 From: Lev Serebryakov Organization: FreeBSD X-Priority: 3 (Normal) Message-ID: <67977762.20120821154035@serebryakov.spb.ru> To: Garrett Cooper In-Reply-To: References: <20120821095527.GA33206@hell.ukr.net> MIME-Version: 1.0 Content-Type: text/plain; charset=windows-1251 Content-Transfer-Encoding: quoted-printable Cc: current@freebsd.org, jhb@FreeBSD.org Subject: r239356: does it mean, that synchronous dhcp and dhcplcinet with disabled devd gone? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: lev@FreeBSD.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Aug 2012 11:40:42 -0000 Hello, Garrett. You wrote 21 =E0=E2=E3=F3=F1=F2=E0 2012 =E3., 15:18:05: GC> Try reverting r239356 -- if that works, then please let jhb@ know. I'm confused by this commit, because it seems (from comment alone), that dhclient will not work without devd anymore (with "synchronous dhcp" option in rc.conf). Am I right? --=20 // Black Lion AKA Lev Serebryakov From owner-freebsd-current@FreeBSD.ORG Tue Aug 21 11:45:53 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1C5E2106564A; Tue, 21 Aug 2012 11:45:53 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from onlyone.friendlyhosting.spb.ru (onlyone.friendlyhosting.spb.ru [IPv6:2a01:4f8:131:60a2::2]) by mx1.freebsd.org (Postfix) with ESMTP id CE4368FC17; Tue, 21 Aug 2012 11:45:52 +0000 (UTC) Received: from lion.home.serebryakov.spb.ru (unknown [IPv6:2001:470:923f:1:8870:d54b:33e8:55b2]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.friendlyhosting.spb.ru (Postfix) with ESMTPA id 8A2194AC2D; Tue, 21 Aug 2012 15:45:51 +0400 (MSK) Date: Tue, 21 Aug 2012 15:45:48 +0400 From: Lev Serebryakov Organization: FreeBSD X-Priority: 3 (Normal) Message-ID: <1243982625.20120821154548@serebryakov.spb.ru> To: Garrett Cooper , current@freebsd.org, jhb@FreeBSD.org In-Reply-To: <67977762.20120821154035@serebryakov.spb.ru> References: <20120821095527.GA33206@hell.ukr.net> <67977762.20120821154035@serebryakov.spb.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=windows-1251 Content-Transfer-Encoding: quoted-printable Cc: Subject: Re: r239356: does it mean, that synchronous dhcp and dhcplcinet with disabled devd gone? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: lev@FreeBSD.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Aug 2012 11:45:53 -0000 Hello, Lev. You wrote 21 =E0=E2=E3=F3=F1=F2=E0 2012 =E3., 15:40:35: GC>> Try reverting r239356 -- if that works, then please let jhb@ know. LS> I'm confused by this commit, because it seems (from comment alone), LS> that dhclient will not work without devd anymore (with "synchronous LS> dhcp" option in rc.conf). LS> Am I right? Also, I don't like idea of removing IP address from interface when cable is unplugged. It was very disturbing behavior of Windows machines for years. I've unplug cable to change switch port for only a second and all connections are broken, even if one second later dhcpclient receive SAME lease! I don't like this. FreeBSD was very tolerant to unplugging cable for eons, and I (and not only me) like it. If I understand this change properly, it is no more the case :( --=20 // Black Lion AKA Lev Serebryakov From owner-freebsd-current@FreeBSD.ORG Tue Aug 21 11:53:12 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C0BD110656D1; Tue, 21 Aug 2012 11:53:12 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from onlyone.friendlyhosting.spb.ru (onlyone.friendlyhosting.spb.ru [IPv6:2a01:4f8:131:60a2::2]) by mx1.freebsd.org (Postfix) with ESMTP id 7D3528FC17; Tue, 21 Aug 2012 11:53:12 +0000 (UTC) Received: from lion.home.serebryakov.spb.ru (unknown [IPv6:2001:470:923f:1:8870:d54b:33e8:55b2]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.friendlyhosting.spb.ru (Postfix) with ESMTPA id 13A1B4AC2D; Tue, 21 Aug 2012 15:53:10 +0400 (MSK) Date: Tue, 21 Aug 2012 15:53:08 +0400 From: Lev Serebryakov Organization: FreeBSD X-Priority: 3 (Normal) Message-ID: <1959717636.20120821155308@serebryakov.spb.ru> To: Garrett Cooper , current@freebsd.org, jhb@FreeBSD.org In-Reply-To: <67977762.20120821154035@serebryakov.spb.ru> References: <20120821095527.GA33206@hell.ukr.net> <67977762.20120821154035@serebryakov.spb.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=windows-1251 Content-Transfer-Encoding: quoted-printable Cc: Peter Jeremy Subject: Re: r239356: does it mean, that synchronous dhcp and dhcplcinet with disabled devd gone? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: lev@FreeBSD.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Aug 2012 11:53:12 -0000 Hello, Garrett. You wrote 21 =E0=E2=E3=F3=F1=F2=E0 2012 =E3., 15:40:35: GC>> Try reverting r239356 -- if that works, then please let jhb@ know. LS> I'm confused by this commit, because it seems (from comment alone), LS> that dhclient will not work without devd anymore (with "synchronous LS> dhcp" option in rc.conf). LS> Am I right? And if I'm right about understanding what this change does, it is POLA violation for sure. Both consequences: unable to use dhcclient without devd (user will need to restart it by hands after each cable unplugging event) and removing IP address from interface on cable unplugging or other interface down event but before lease is expired. If I'm right in understanding this commit, I vote to back it out and find better solution, may be, two new options: one to remove IP and one to exit on interface down. And default behavior should be OLD ONE about IP address in any case and OLD ONE about exit in case when dhclient isn't started by devd, but by rc scripts directly. --=20 // Black Lion AKA Lev Serebryakov From owner-freebsd-current@FreeBSD.ORG Tue Aug 21 11:56:10 2012 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8C80E106566B for ; Tue, 21 Aug 2012 11:56:10 +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 40DB58FC08 for ; Tue, 21 Aug 2012 11:56:10 +0000 (UTC) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost1.zedat.fu-berlin.de (Exim 4.69) for freebsd-current@FreeBSD.org with esmtp (envelope-from ) id <1T3n44-0000U4-Hu>; Tue, 21 Aug 2012 13:56:08 +0200 Received: from e178031016.adsl.alicedsl.de ([85.178.31.16] helo=thor.walstatt.dyndns.org) by inpost2.zedat.fu-berlin.de (Exim 4.69) for freebsd-current@FreeBSD.org with esmtpsa (envelope-from ) id <1T3n44-00038r-CU>; Tue, 21 Aug 2012 13:56:08 +0200 Message-ID: <50337752.8070707@zedat.fu-berlin.de> Date: Tue, 21 Aug 2012 13:56:02 +0200 From: "O. Hartmann" User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:14.0) Gecko/20120810 Thunderbird/14.0 MIME-Version: 1.0 To: Current FreeBSD X-Enigmail-Version: 1.4.3 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig41F43945D916890FC140153E" X-Originating-IP: 85.178.31.16 Cc: Subject: FreeBSD 10.0-CURRENT r239477 doesn't compile: virtualbox-ose-kmod-4.1.18_1 is marked as broken: Does not compile on FreeBSD < 8.2. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 21 Aug 2012 11:56:10 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig41F43945D916890FC140153E Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: quoted-printable Today I ran into a problem with FreeBSD 10.0-CURRENT #0 r239477 recompiling the VBox kernel module: =3D=3D=3D> Cleaning for virtualbox-ose-kmod-4.1.18_1 =3D=3D=3D> virtualbox-ose-kmod-4.1.18_1 is marked as broken: Does not co= mpile on FreeBSD < 8.2. *** [all] Error code 1 Stop in /usr/ports/emulators/virtualbox-ose-kmod. The port compiled prior to the updates of today. oh --------------enig41F43945D916890FC140153E 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.0.19 (FreeBSD) iQEcBAEBAgAGBQJQM3dXAAoJEOgBcD7A/5N87aoH/ijRMJ2OHbGiXIzDGS5cjcTb ABkwX4nBTxRqp3h/DZhhzfvBWHO2+poRMtIFoxmYhTSbX1n2avNijtQNB+cN9ta4 Dfjn3lOUPRPMuQYVd3SFad/N/KQfqQAnbUALm0akghz2LckeFhC+yLqZ5AziMZ/C I94Fhq0+TSSBQ7RZT+IYGRgzUY6DdRDofaxo50eyVuIE4J1d+ZkzIoXwek9Qyq7V a1t25e/5oUYzkl5vBlhE9286Vd45cjEJOFFRTHX3TgTCPJF5h7s4PzkSWcVXeT8f kf0IyM2zVgg64hiZ7D70MyesKr8CF6co9UbYtdnoI/nqtfQFg8+XJxp6pjVZSv8= =SNEx -----END PGP SIGNATURE----- --------------enig41F43945D916890FC140153E-- From owner-freebsd-current@FreeBSD.ORG Tue Aug 21 12:05:40 2012 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1E937106566B; Tue, 21 Aug 2012 12:05:40 +0000 (UTC) (envelope-from uqs@FreeBSD.org) Received: from acme.spoerlein.net (acme.spoerlein.net [IPv6:2a01:4f8:131:23c2::1]) by mx1.freebsd.org (Postfix) with ESMTP id A83E48FC0C; Tue, 21 Aug 2012 12:05:39 +0000 (UTC) Received: from localhost (acme.spoerlein.net [IPv6:2a01:4f8:131:23c2::1]) by acme.spoerlein.net (8.14.5/8.14.5) with ESMTP id q7LC5cBx007076 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Tue, 21 Aug 2012 14:05:38 +0200 (CEST) (envelope-from uqs@FreeBSD.org) Date: Tue, 21 Aug 2012 14:05:37 +0200 From: Ulrich =?utf-8?B?U3DDtnJsZWlu?= To: "Simon L. B. Nielsen" Message-ID: <20120821120537.GL1202@acme.spoerlein.net> Mail-Followup-To: "Simon L. B. Nielsen" , freebsd-security@FreeBSD.org, freebsd-current@FreeBSD.org References: <5032AB28.9070306@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5032AB28.9070306@FreeBSD.org> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-security@FreeBSD.org, freebsd-current@FreeBSD.org Subject: Re: [HEADSUP] geli(4) weak master key generation on -CURRENT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 21 Aug 2012 12:05:40 -0000 On Mon, 2012-08-20 at 22:24:56 +0100, Simon L. B. Nielsen wrote: > Hello, > > If you are not using geli(4) on -CURRENT (AKA FreeBSD 10) you can safely > ignore this mail. If you are, please read on! > > -CURRENT users of geli(4) should be advised that, a geli(4) device may > have weak master key, if the provider is created on -CURRENT system > built against source code between r238116 (Jul 4 17:54:17 2012 UTC) > and r239184 (non-inclusive, Aug 10 18:43:29 2012 UTC). > > One can verify if its provider was created with weak keys by running: > > # geli dump | grep version > > If the version is 7 and the system did not include this fix (r239184) > when provider was initialized, then the data has to be backed up, > underlying provider overwritten with random data, system upgraded and > provider recreated. > > Thanks to Fabian Keil for reporting the issue, Pawel Jakub Dawidek for > fixing it, and Xin Li for drafting this text. > > PS. This only affects FreeBSD 10 / -CURRENT, and as -CURRENT isn't > supported by the FreeBSD Security Team, we are not releasing an > advisory, just this heads up. I haven't read commit mails in a very long time, but is there code in place that will issue a warning upon geli attach if version 7 is detected? While -CURRENT is not supported, there might be a lot of disks initialized with version 7 and they'll eventually be upgraded to 10.0-RELEASE (the OS, not necessarily the geli volumes). Thanks Uli From owner-freebsd-current@FreeBSD.ORG Tue Aug 21 12:44:00 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 55333106564A; Tue, 21 Aug 2012 12:44:00 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) by mx1.freebsd.org (Postfix) with ESMTP id 047A38FC16; Tue, 21 Aug 2012 12:44:00 +0000 (UTC) Received: from slw by zxy.spb.ru with local (Exim 4.69 (FreeBSD)) (envelope-from ) id 1T3nqh-000Jik-AI; Tue, 21 Aug 2012 16:46:23 +0400 Date: Tue, 21 Aug 2012 16:46:23 +0400 From: Slawa Olhovchenkov To: Lev Serebryakov Message-ID: <20120821124623.GC88729@zxy.spb.ru> References: <20120821095527.GA33206@hell.ukr.net> <67977762.20120821154035@serebryakov.spb.ru> <1243982625.20120821154548@serebryakov.spb.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <1243982625.20120821154548@serebryakov.spb.ru> User-Agent: Mutt/1.5.21 (2010-09-15) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false Cc: Garrett Cooper , current@freebsd.org, jhb@FreeBSD.org Subject: Re: r239356: does it mean, that synchronous dhcp and dhcplcinet with disabled devd gone? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 21 Aug 2012 12:44:00 -0000 On Tue, Aug 21, 2012 at 03:45:48PM +0400, Lev Serebryakov wrote: > Hello, Lev. > You wrote 21 Á×ÇÕÓÔÁ 2012 Ç., 15:40:35: > > GC>> Try reverting r239356 -- if that works, then please let jhb@ know. > LS> I'm confused by this commit, because it seems (from comment alone), > LS> that dhclient will not work without devd anymore (with "synchronous > LS> dhcp" option in rc.conf). > LS> Am I right? > Also, I don't like idea of removing IP address from interface when > cable is unplugged. It was very disturbing behavior of Windows > machines for years. I've unplug cable to change switch port for only a > second and all connections are broken, even if one second later > dhcpclient receive SAME lease! I don't like this. FreeBSD was very > tolerant to unplugging cable for eons, and I (and not only me) like > it. If I understand this change properly, it is no more the case :( Not only cable. Turn on microwave, lost WiFi connection and lost all open ssh session (and other network connection). From owner-freebsd-current@FreeBSD.ORG Tue Aug 21 13:26:54 2012 Return-Path: Delivered-To: current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9FE241065670; Tue, 21 Aug 2012 13:26:54 +0000 (UTC) (envelope-from jlh@FreeBSD.org) Received: from smtp5-g21.free.fr (smtp5-g21.free.fr [IPv6:2a01:e0c:1:1599::14]) by mx1.freebsd.org (Postfix) with ESMTP id 439988FC0C; Tue, 21 Aug 2012 13:26:50 +0000 (UTC) Received: from endor.tataz.chchile.org (unknown [82.233.239.98]) by smtp5-g21.free.fr (Postfix) with ESMTP id E8A41D48054; Tue, 21 Aug 2012 15:26:44 +0200 (CEST) Received: from felucia.tataz.chchile.org (felucia.tataz.chchile.org [192.168.1.9]) by endor.tataz.chchile.org (Postfix) with ESMTP id D49682BB; Tue, 21 Aug 2012 15:26:43 +0200 (CEST) Received: by felucia.tataz.chchile.org (Postfix, from userid 1000) id B17B310FE0; Tue, 21 Aug 2012 13:26:43 +0000 (UTC) Date: Tue, 21 Aug 2012 15:26:43 +0200 From: Jeremie Le Hen To: Baptiste Daroussin Message-ID: <20120821132643.GE37262@felucia.tataz.chchile.org> Mail-Followup-To: Baptiste Daroussin , ports@FreeBSD.org, current@FreeBSD.org References: <20120820194313.GC23607@ithaqua.etoilebsd.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20120820194313.GC23607@ithaqua.etoilebsd.net> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: ports@FreeBSD.org, current@FreeBSD.org Subject: Re: pkgng 1.0 release schedule, and HEAD switch to pkgng by default schedule X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 21 Aug 2012 13:26:54 -0000 Hi Baptise, On Mon, Aug 20, 2012 at 09:43:13PM +0200, Baptiste Daroussin wrote: > > Since 1.0-rc6 release, everything looks ready for a final release of 1.0, I'll > give more details on the release commit bit :) this is planned for 30th august > 2012. > > Current was supposed to switch to pkgng by default today, it has been delayed > until the nvidia-driver is fixed with pkgng. Thanksfully kwm@ and danfe@ has > been working on this, and the situation should be fixed pretty soon. > > Please continue testing pkgng and reporting bugs, if you are new comers do not > hesitate to ask question about pkgng so that we can improve documentation: > > The usual links about pkgng: > - http://wiki.freebsd.org/pkgng > - http://wiki.freebsd.org/PkgPrimer > - https://github.com/pkgng/pkgng/blob/master/FAQ.md > - http://people.freebsd.org/~bapt/pres-pkgng-bsdcan.pdf > - http://www.youtube.com/watch?v=4Hxq7AHZ27I First thank you and all who have worked to make this first release of pkgng. This is a great milestone in FreeBSD history. Supposedly, pkgng will stay opt-in for RELENG_9 and will be the default (opt-out?) on RELENG_10. During the upgrade from the old branch to the new one, how do we ensure users will perform the required step (basically, run pkg2ng) to switch their pkg database to pkgng? Will it be a note in src/UPDATING and as well in the release notes? -- Jeremie Le Hen Scientists say the world is made up of Protons, Neutrons and Electrons. They forgot to mention Morons. From owner-freebsd-current@FreeBSD.ORG Tue Aug 21 13:30:50 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D514D106564A for ; Tue, 21 Aug 2012 13:30:50 +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 8F1378FC12 for ; Tue, 21 Aug 2012 13:30:50 +0000 (UTC) Received: from mail.auburn.protected-networks.net (mail.auburn.protected-networks.net [202.12.127.83]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "mail.auburn.protected-networks.net", Issuer "Protected Networks Certificate Authority" (verified OK)) by sarah.protected-networks.net (Postfix) with ESMTPS id 916906158; Tue, 21 Aug 2012 09:30:49 -0400 (EDT) Authentication-Results: sarah.protected-networks.net; domainkeys=fail (no signature) (testing) header.from=imb@protected-networks.net Received: from mail.auburn.protected-networks.net (localhost.auburn.protected-networks.net [127.0.0.1]) by mail.auburn.protected-networks.net (Postfix) with ESMTP id 723B31CC8D; Tue, 21 Aug 2012 09:30:48 -0400 (EDT) Received: from mail.auburn.protected-networks.net ([127.0.0.1]) by mail.auburn.protected-networks.net (mail.auburn.protected-networks.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5M8L4LfSk3Px; Tue, 21 Aug 2012 09:30:47 -0400 (EDT) Received: from mail.auburn.protected-networks.net (localhost.auburn.protected-networks.net [127.0.0.1]) by mail.auburn.protected-networks.net (Postfix) with ESMTP; Tue, 21 Aug 2012 09:30:47 -0400 (EDT) Received: from 168.159.213.53 (SquirrelMail authenticated user imb) by mail.auburn.protected-networks.net with HTTP; Tue, 21 Aug 2012 09:30:47 -0400 Message-ID: <4f4bfb82a00e2d592013c43df6554e73.squirrel@mail.auburn.protected-networks.net> In-Reply-To: References: <20120820204444.GA27130@aspire.rulingia.com> Date: Tue, 21 Aug 2012 09:30:47 -0400 From: "Michael Butler" To: "Randy Bush" User-Agent: SquirrelMail/1.4.22 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Cc: FreeBSD Current Subject: Re: buildworld c++ internal error X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 21 Aug 2012 13:30:50 -0000 On Mon, August 20, 2012 17:54, Randy Bush wrote: > -O allowed it to buildworld! Should be marginally faster compiling too .. good to hear :-) imb From owner-freebsd-current@FreeBSD.ORG Tue Aug 21 13:46:26 2012 Return-Path: Delivered-To: current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A7D02106566B; Tue, 21 Aug 2012 13:46:26 +0000 (UTC) (envelope-from bapt@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 723DC8FC16; Tue, 21 Aug 2012 13:46:26 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q7LDkQj6006121; Tue, 21 Aug 2012 13:46:26 GMT (envelope-from bapt@FreeBSD.org) Received: (from bapt@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q7LDkQZH006120; Tue, 21 Aug 2012 13:46:26 GMT (envelope-from bapt@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: bapt set sender to bapt@FreeBSD.org using -f Date: Tue, 21 Aug 2012 15:46:23 +0200 From: Baptiste Daroussin To: ports@FreeBSD.org, current@FreeBSD.org Message-ID: <20120821134623.GH5044@ithaqua.etoilebsd.net> References: <20120820194313.GC23607@ithaqua.etoilebsd.net> <20120821132643.GE37262@felucia.tataz.chchile.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="jRdC2OsRnuV8iIl8" Content-Disposition: inline In-Reply-To: <20120821132643.GE37262@felucia.tataz.chchile.org> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: Subject: Re: pkgng 1.0 release schedule, and HEAD switch to pkgng by default schedule X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 21 Aug 2012 13:46:26 -0000 --jRdC2OsRnuV8iIl8 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Aug 21, 2012 at 03:26:43PM +0200, Jeremie Le Hen wrote: > Hi Baptise, >=20 > On Mon, Aug 20, 2012 at 09:43:13PM +0200, Baptiste Daroussin wrote: > >=20 > > Since 1.0-rc6 release, everything looks ready for a final release of 1.= 0, I'll > > give more details on the release commit bit :) this is planned for 30th= august > > 2012. > >=20 > > Current was supposed to switch to pkgng by default today, it has been d= elayed > > until the nvidia-driver is fixed with pkgng. Thanksfully kwm@ and danfe= @ has > > been working on this, and the situation should be fixed pretty soon. > >=20 > > Please continue testing pkgng and reporting bugs, if you are new comers= do not > > hesitate to ask question about pkgng so that we can improve documentati= on: > >=20 > > The usual links about pkgng: > > - http://wiki.freebsd.org/pkgng > > - http://wiki.freebsd.org/PkgPrimer > > - https://github.com/pkgng/pkgng/blob/master/FAQ.md > > - http://people.freebsd.org/~bapt/pres-pkgng-bsdcan.pdf > > - http://www.youtube.com/watch?v=3D4Hxq7AHZ27I >=20 > First thank you and all who have worked to make this first release of > pkgng. This is a great milestone in FreeBSD history. >=20 > Supposedly, pkgng will stay opt-in for RELENG_9 and will be the default > (opt-out?) on RELENG_10. During the upgrade from the old branch to the > new one, how do we ensure users will perform the required step > (basically, run pkg2ng) to switch their pkg database to pkgng? Will it > be a note in src/UPDATING and as well in the release notes? >=20 Yes there will be a note in UPDATING, I'm also pondering modifying pkg_* to= ols to that they show up an advetisement about pkg_install being deprecated. I would also like to just remove pkg_* tools from RELENG_10 if that fits the schedule. regards, Bapt --jRdC2OsRnuV8iIl8 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEARECAAYFAlAzkS8ACgkQ8kTtMUmk6EyGrACfaEb/0ym64azS0sAZN62bUzTF CO0AoIVuEM9cY4QbQIAckq20qdiaF+6A =q5YW -----END PGP SIGNATURE----- --jRdC2OsRnuV8iIl8-- From owner-freebsd-current@FreeBSD.ORG Tue Aug 21 14:07:55 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 50297106564A for ; Tue, 21 Aug 2012 14:07:55 +0000 (UTC) (envelope-from dim@FreeBSD.org) Received: from tensor.andric.com (tensor.andric.com [87.251.56.140]) by mx1.freebsd.org (Postfix) with ESMTP id 0E5EE8FC12 for ; Tue, 21 Aug 2012 14:07:54 +0000 (UTC) Received: from [IPv6:2001:7b8:3a7:0:dd99:997b:50d0:d751] (unknown [IPv6:2001:7b8:3a7:0:dd99:997b:50d0:d751]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id 9C10A5C59; Tue, 21 Aug 2012 16:07:53 +0200 (CEST) Message-ID: <50339638.2080107@FreeBSD.org> Date: Tue, 21 Aug 2012 16:07:52 +0200 From: Dimitry Andric Organization: The FreeBSD Project User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20120815 Thunderbird/15.0 MIME-Version: 1.0 To: Randy Bush References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: FreeBSD Current Subject: Re: buildworld c++ internal error X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 21 Aug 2012 14:07:55 -0000 On 2012-08-19 16:01, Randy Bush wrote: ... > c++ -O2 -pipe -DIPFIREWALL_NAT -march=pentium -I/usr/src/lib/clang/libllvmcore/../../../contrib/llvm/include -I/usr/src/lib/clang/libllvmcore/../../../contrib/llvm/tools/clang/include -I/usr/src/lib/clang/libllvmcore/../../../contrib/llvm/lib/VMCore -I. -I/usr/src/lib/clang/libllvmcore/../../../contrib/llvm/../../lib/clang/include -DLLVM_ON_UNIX -DLLVM_ON_FREEBSD -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS -DLLVM_DEFAULT_TARGET_TRIPLE=\"i386-unknown-freebsd9.0\" -DDEFAULT_SYSROOT=\"\" -fstack-protector -fno-exceptions -c /usr/src/lib/clang/libllvmcore/../../../contrib/llvm/lib/VMCore/Function.cpp -o Function.o > {standard input}: Assembler messages: > {standard input}:36465: Warning: end of file not at end of a line; newline inserted > {standard input}:36631: Error: unknown pseudo-op: `.lc798' > c++: Internal error: Killed: 9 (program cc1plus) If you don't need clang on this box, you could add WITHOUT_CLANG to your src.conf. If you do need clang, you could try building world with it, since it usually is faster than gcc, and uses less memory. :) From owner-freebsd-current@FreeBSD.ORG Tue Aug 21 14:52:55 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 028FD1065670; Tue, 21 Aug 2012 14:52:55 +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 C96408FC15; Tue, 21 Aug 2012 14:52:54 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 459BBB946; Tue, 21 Aug 2012 10:52:54 -0400 (EDT) From: John Baldwin To: freebsd-current@freebsd.org, lev@freebsd.org Date: Tue, 21 Aug 2012 09:34:31 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110714-p17; KDE/4.5.5; amd64; ; ) References: <20120821095527.GA33206@hell.ukr.net> <67977762.20120821154035@serebryakov.spb.ru> <1959717636.20120821155308@serebryakov.spb.ru> In-Reply-To: <1959717636.20120821155308@serebryakov.spb.ru> MIME-Version: 1.0 Content-Type: Text/Plain; charset="windows-1251" Content-Transfer-Encoding: quoted-printable Message-Id: <201208210934.31484.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Tue, 21 Aug 2012 10:52:54 -0400 (EDT) Cc: Garrett Cooper , current@freebsd.org, Peter Jeremy Subject: Re: r239356: does it mean, that synchronous dhcp and dhcplcinet with disabled devd gone? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 21 Aug 2012 14:52:55 -0000 On Tuesday, August 21, 2012 7:53:08 am Lev Serebryakov wrote: > Hello, Garrett. > You wrote 21 =E0=E2=E3=F3=F1=F2=E0 2012 =E3., 15:40:35: >=20 > GC>> Try reverting r239356 -- if that works, then please let jhb@ know. > LS> I'm confused by this commit, because it seems (from comment alone), > LS> that dhclient will not work without devd anymore (with "synchronous > LS> dhcp" option in rc.conf). > LS> Am I right? > And if I'm right about understanding what this change does, it is > POLA violation for sure. Both consequences: unable to use dhcclient > without devd (user will need to restart it by hands after each cable > unplugging event) and removing IP address from interface on cable > unplugging or other interface down event but before lease is expired. >=20 > If I'm right in understanding this commit, I vote to back it out and > find better solution, may be, two new options: one to remove IP and > one to exit on interface down. And default behavior should be OLD > ONE about IP address in any case and OLD ONE about exit in case when > dhclient isn't started by devd, but by rc scripts directly. Humm. devd is the more common case, and we explicitly don't use devd to st= art=20 dhclient on boot even when devd is enabled (so out of the box dhcp would fi= rst=20 be started by rc, but would be restarted by devd). Another option is to rework dhclient to work like it does on OpenBSD where = it renews its lease if the link bounces, but to not exit when the link goes do= wn. =20 That case would fix the currently broken case that you unplug your cable, t= ake=20 your laptop over to another network (e.g. take it home if suspend/resume=20 works), then plug it back in and are still stuck with your old IP. =2D-=20 John Baldwin From owner-freebsd-current@FreeBSD.ORG Tue Aug 21 14:52:55 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 028FD1065670; Tue, 21 Aug 2012 14:52:55 +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 C96408FC15; Tue, 21 Aug 2012 14:52:54 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 459BBB946; Tue, 21 Aug 2012 10:52:54 -0400 (EDT) From: John Baldwin To: freebsd-current@freebsd.org, lev@freebsd.org Date: Tue, 21 Aug 2012 09:34:31 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110714-p17; KDE/4.5.5; amd64; ; ) References: <20120821095527.GA33206@hell.ukr.net> <67977762.20120821154035@serebryakov.spb.ru> <1959717636.20120821155308@serebryakov.spb.ru> In-Reply-To: <1959717636.20120821155308@serebryakov.spb.ru> MIME-Version: 1.0 Content-Type: Text/Plain; charset="windows-1251" Content-Transfer-Encoding: quoted-printable Message-Id: <201208210934.31484.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Tue, 21 Aug 2012 10:52:54 -0400 (EDT) Cc: Garrett Cooper , current@freebsd.org, Peter Jeremy Subject: Re: r239356: does it mean, that synchronous dhcp and dhcplcinet with disabled devd gone? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 21 Aug 2012 14:52:55 -0000 On Tuesday, August 21, 2012 7:53:08 am Lev Serebryakov wrote: > Hello, Garrett. > You wrote 21 =E0=E2=E3=F3=F1=F2=E0 2012 =E3., 15:40:35: >=20 > GC>> Try reverting r239356 -- if that works, then please let jhb@ know. > LS> I'm confused by this commit, because it seems (from comment alone), > LS> that dhclient will not work without devd anymore (with "synchronous > LS> dhcp" option in rc.conf). > LS> Am I right? > And if I'm right about understanding what this change does, it is > POLA violation for sure. Both consequences: unable to use dhcclient > without devd (user will need to restart it by hands after each cable > unplugging event) and removing IP address from interface on cable > unplugging or other interface down event but before lease is expired. >=20 > If I'm right in understanding this commit, I vote to back it out and > find better solution, may be, two new options: one to remove IP and > one to exit on interface down. And default behavior should be OLD > ONE about IP address in any case and OLD ONE about exit in case when > dhclient isn't started by devd, but by rc scripts directly. Humm. devd is the more common case, and we explicitly don't use devd to st= art=20 dhclient on boot even when devd is enabled (so out of the box dhcp would fi= rst=20 be started by rc, but would be restarted by devd). Another option is to rework dhclient to work like it does on OpenBSD where = it renews its lease if the link bounces, but to not exit when the link goes do= wn. =20 That case would fix the currently broken case that you unplug your cable, t= ake=20 your laptop over to another network (e.g. take it home if suspend/resume=20 works), then plug it back in and are still stuck with your old IP. =2D-=20 John Baldwin From owner-freebsd-current@FreeBSD.ORG Tue Aug 21 15:04:39 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 15130106568A; Tue, 21 Aug 2012 15:04:39 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from onlyone.friendlyhosting.spb.ru (onlyone.friendlyhosting.spb.ru [46.4.40.135]) by mx1.freebsd.org (Postfix) with ESMTP id C07AA8FC20; Tue, 21 Aug 2012 15:04:38 +0000 (UTC) Received: from lion.home.serebryakov.spb.ru (unknown [IPv6:2001:470:923f:1:8870:d54b:33e8:55b2]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.friendlyhosting.spb.ru (Postfix) with ESMTPA id A2F2A4AC2D; Tue, 21 Aug 2012 19:04:36 +0400 (MSK) Date: Tue, 21 Aug 2012 19:04:33 +0400 From: Lev Serebryakov Organization: FreeBSD Project X-Priority: 3 (Normal) Message-ID: <1049151425.20120821190433@serebryakov.spb.ru> To: John Baldwin In-Reply-To: <201208210934.31484.jhb@freebsd.org> References: <20120821095527.GA33206@hell.ukr.net> <67977762.20120821154035@serebryakov.spb.ru> <1959717636.20120821155308@serebryakov.spb.ru> <201208210934.31484.jhb@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=windows-1251 Content-Transfer-Encoding: quoted-printable Cc: Garrett Cooper , freebsd-current@freebsd.org, current@freebsd.org, Peter Jeremy Subject: Re: r239356: does it mean, that synchronous dhcp and dhcplcinet with disabled devd gone? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: lev@FreeBSD.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Aug 2012 15:04:39 -0000 Hello, John. You wrote 21 =E0=E2=E3=F3=F1=F2=E0 2012 =E3., 17:34:31: JB> Humm. devd is the more common case, and we explicitly don't use devd t= o start JB> dhclient on boot even when devd is enabled (so out of the box dhcp woul= d first JB> be started by rc, but would be restarted by devd). It is strange, and, maybe, changed some time ago, because when I disable "devd" on my NanoBSD-based router (about year or year and half ago), I've spent several hours to understand, why dhclient doesn't start anymore. And I need to add this to rc.conf: synchronous_dhclient=3D"YES" JB> Another option is to rework dhclient to work like it does on OpenBSD wh= ere it JB> renews its lease if the link bounces, but to not exit when the link goe= s down. Yes, it looks like proper solution. JB> That case would fix the currently broken case that you unplug your cabl= e, take JB> your laptop over to another network (e.g. take it home if suspend/resume JB> works), then plug it back in and are still stuck with your old IP. Yep. But _committed_ solution is very bad. For example, my ISP's switch lost link every second day for second or two. I don't want to lost all open connections, firewall state, etc, and to restart dhclinet by hands, especially, when I'\m not at home anf my girlfriend is. in such case. Another good example was provided by Slava -- WiFi could disconnect for 10-15 seconds for multiple reasons, and dropping of IP and all connections in such case is MAJOR headache. --=20 // Black Lion AKA Lev Serebryakov From owner-freebsd-current@FreeBSD.ORG Tue Aug 21 15:04:39 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 15130106568A; Tue, 21 Aug 2012 15:04:39 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from onlyone.friendlyhosting.spb.ru (onlyone.friendlyhosting.spb.ru [46.4.40.135]) by mx1.freebsd.org (Postfix) with ESMTP id C07AA8FC20; Tue, 21 Aug 2012 15:04:38 +0000 (UTC) Received: from lion.home.serebryakov.spb.ru (unknown [IPv6:2001:470:923f:1:8870:d54b:33e8:55b2]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.friendlyhosting.spb.ru (Postfix) with ESMTPA id A2F2A4AC2D; Tue, 21 Aug 2012 19:04:36 +0400 (MSK) Date: Tue, 21 Aug 2012 19:04:33 +0400 From: Lev Serebryakov Organization: FreeBSD Project X-Priority: 3 (Normal) Message-ID: <1049151425.20120821190433@serebryakov.spb.ru> To: John Baldwin In-Reply-To: <201208210934.31484.jhb@freebsd.org> References: <20120821095527.GA33206@hell.ukr.net> <67977762.20120821154035@serebryakov.spb.ru> <1959717636.20120821155308@serebryakov.spb.ru> <201208210934.31484.jhb@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=windows-1251 Content-Transfer-Encoding: quoted-printable Cc: Garrett Cooper , freebsd-current@freebsd.org, current@freebsd.org, Peter Jeremy Subject: Re: r239356: does it mean, that synchronous dhcp and dhcplcinet with disabled devd gone? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: lev@FreeBSD.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Aug 2012 15:04:39 -0000 Hello, John. You wrote 21 =E0=E2=E3=F3=F1=F2=E0 2012 =E3., 17:34:31: JB> Humm. devd is the more common case, and we explicitly don't use devd t= o start JB> dhclient on boot even when devd is enabled (so out of the box dhcp woul= d first JB> be started by rc, but would be restarted by devd). It is strange, and, maybe, changed some time ago, because when I disable "devd" on my NanoBSD-based router (about year or year and half ago), I've spent several hours to understand, why dhclient doesn't start anymore. And I need to add this to rc.conf: synchronous_dhclient=3D"YES" JB> Another option is to rework dhclient to work like it does on OpenBSD wh= ere it JB> renews its lease if the link bounces, but to not exit when the link goe= s down. Yes, it looks like proper solution. JB> That case would fix the currently broken case that you unplug your cabl= e, take JB> your laptop over to another network (e.g. take it home if suspend/resume JB> works), then plug it back in and are still stuck with your old IP. Yep. But _committed_ solution is very bad. For example, my ISP's switch lost link every second day for second or two. I don't want to lost all open connections, firewall state, etc, and to restart dhclinet by hands, especially, when I'\m not at home anf my girlfriend is. in such case. Another good example was provided by Slava -- WiFi could disconnect for 10-15 seconds for multiple reasons, and dropping of IP and all connections in such case is MAJOR headache. --=20 // Black Lion AKA Lev Serebryakov From owner-freebsd-current@FreeBSD.ORG Tue Aug 21 15:16:12 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 441E01065672 for ; Tue, 21 Aug 2012 15:16:12 +0000 (UTC) (envelope-from freebsd@damnhippie.dyndns.org) Received: from qmta15.emeryville.ca.mail.comcast.net (qmta15.emeryville.ca.mail.comcast.net [76.96.27.228]) by mx1.freebsd.org (Postfix) with ESMTP id 205898FC12 for ; Tue, 21 Aug 2012 15:16:11 +0000 (UTC) Received: from omta05.emeryville.ca.mail.comcast.net ([76.96.30.43]) by qmta15.emeryville.ca.mail.comcast.net with comcast id pSWi1j0070vp7WLAFTG6ah; Tue, 21 Aug 2012 15:16:06 +0000 Received: from damnhippie.dyndns.org ([24.8.232.202]) by omta05.emeryville.ca.mail.comcast.net with comcast id pTG51j00A4NgCEG8RTG5zD; Tue, 21 Aug 2012 15:16:06 +0000 Received: from [172.22.42.240] (revolution.hippie.lan [172.22.42.240]) by damnhippie.dyndns.org (8.14.3/8.14.3) with ESMTP id q7LFG34S022427; Tue, 21 Aug 2012 09:16:03 -0600 (MDT) (envelope-from freebsd@damnhippie.dyndns.org) From: Ian Lepore To: lev@freebsd.org In-Reply-To: <1049151425.20120821190433@serebryakov.spb.ru> References: <20120821095527.GA33206@hell.ukr.net> <67977762.20120821154035@serebryakov.spb.ru> <1959717636.20120821155308@serebryakov.spb.ru> <201208210934.31484.jhb@freebsd.org> <1049151425.20120821190433@serebryakov.spb.ru> Content-Type: text/plain; charset="koi8-r" Date: Tue, 21 Aug 2012 09:16:03 -0600 Message-ID: <1345562163.27688.347.camel@revolution.hippie.lan> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 8bit Cc: Garrett Cooper , Peter Jeremy , freebsd-current@freebsd.org, current@freebsd.org Subject: Re: r239356: does it mean, that synchronous dhcp and dhcplcinet with disabled devd gone? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 21 Aug 2012 15:16:12 -0000 On Tue, 2012-08-21 at 19:04 +0400, Lev Serebryakov wrote: > Hello, John. > You wrote 21 Á×ÇÕÓÔÁ 2012 Ç., 17:34:31: > > JB> Humm. devd is the more common case, and we explicitly don't use devd to start > JB> dhclient on boot even when devd is enabled (so out of the box dhcp would first > JB> be started by rc, but would be restarted by devd). > It is strange, and, maybe, changed some time ago, because when I > disable "devd" on my NanoBSD-based router (about year or year and half > ago), I've spent several hours to understand, why dhclient doesn't > start anymore. And I need to add this to rc.conf: > > synchronous_dhclient="YES" > > JB> Another option is to rework dhclient to work like it does on OpenBSD where it > JB> renews its lease if the link bounces, but to not exit when the link goes down. > Yes, it looks like proper solution. > > JB> That case would fix the currently broken case that you unplug your cable, take > JB> your laptop over to another network (e.g. take it home if suspend/resume > JB> works), then plug it back in and are still stuck with your old IP. > Yep. But _committed_ solution is very bad. For example, my ISP's > switch lost link every second day for second or two. I don't want to > lost all open connections, firewall state, etc, and to restart > dhclinet by hands, especially, when I'\m not at home anf my > girlfriend is. in such case. Another good example was provided by > Slava -- WiFi could disconnect for 10-15 seconds for multiple > reasons, and dropping of IP and all connections in such case is MAJOR > headache. > I don't understand all this talk that makes it sound like you lose your existing network connections when dhclient exits. I don't experience anything like that at all, and never have. I just pulled the network cable on this machine, did "sudo killall dhclient", plugged the network back in, I still have all my ssh connections to the world in a dozen open windows and can interact with any of them. Then I did "sudo dhclient re0" (simulating devd restarting dhclient on link-up) and it reacquired a lease for the same IP it had before I killed it, and still all my open connections are open. It has worked this way for me for years. Does it somehow not work this way for everyone? -- Ian From owner-freebsd-current@FreeBSD.ORG Tue Aug 21 15:16:12 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6F2E61065676 for ; Tue, 21 Aug 2012 15:16:12 +0000 (UTC) (envelope-from freebsd@damnhippie.dyndns.org) Received: from qmta03.emeryville.ca.mail.comcast.net (qmta03.emeryville.ca.mail.comcast.net [76.96.30.32]) by mx1.freebsd.org (Postfix) with ESMTP id 486448FC16 for ; Tue, 21 Aug 2012 15:16:12 +0000 (UTC) Received: from omta05.emeryville.ca.mail.comcast.net ([76.96.30.43]) by qmta03.emeryville.ca.mail.comcast.net with comcast id pSyB1j0010vp7WLA3TG67y; Tue, 21 Aug 2012 15:16:06 +0000 Received: from damnhippie.dyndns.org ([24.8.232.202]) by omta05.emeryville.ca.mail.comcast.net with comcast id pTG51j00A4NgCEG8RTG5zD; Tue, 21 Aug 2012 15:16:06 +0000 Received: from [172.22.42.240] (revolution.hippie.lan [172.22.42.240]) by damnhippie.dyndns.org (8.14.3/8.14.3) with ESMTP id q7LFG34S022427; Tue, 21 Aug 2012 09:16:03 -0600 (MDT) (envelope-from freebsd@damnhippie.dyndns.org) From: Ian Lepore To: lev@freebsd.org In-Reply-To: <1049151425.20120821190433@serebryakov.spb.ru> References: <20120821095527.GA33206@hell.ukr.net> <67977762.20120821154035@serebryakov.spb.ru> <1959717636.20120821155308@serebryakov.spb.ru> <201208210934.31484.jhb@freebsd.org> <1049151425.20120821190433@serebryakov.spb.ru> Content-Type: text/plain; charset="koi8-r" Date: Tue, 21 Aug 2012 09:16:03 -0600 Message-ID: <1345562163.27688.347.camel@revolution.hippie.lan> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 8bit Cc: Garrett Cooper , Peter Jeremy , freebsd-current@freebsd.org, current@freebsd.org Subject: Re: r239356: does it mean, that synchronous dhcp and dhcplcinet with disabled devd gone? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 21 Aug 2012 15:16:12 -0000 On Tue, 2012-08-21 at 19:04 +0400, Lev Serebryakov wrote: > Hello, John. > You wrote 21 Á×ÇÕÓÔÁ 2012 Ç., 17:34:31: > > JB> Humm. devd is the more common case, and we explicitly don't use devd to start > JB> dhclient on boot even when devd is enabled (so out of the box dhcp would first > JB> be started by rc, but would be restarted by devd). > It is strange, and, maybe, changed some time ago, because when I > disable "devd" on my NanoBSD-based router (about year or year and half > ago), I've spent several hours to understand, why dhclient doesn't > start anymore. And I need to add this to rc.conf: > > synchronous_dhclient="YES" > > JB> Another option is to rework dhclient to work like it does on OpenBSD where it > JB> renews its lease if the link bounces, but to not exit when the link goes down. > Yes, it looks like proper solution. > > JB> That case would fix the currently broken case that you unplug your cable, take > JB> your laptop over to another network (e.g. take it home if suspend/resume > JB> works), then plug it back in and are still stuck with your old IP. > Yep. But _committed_ solution is very bad. For example, my ISP's > switch lost link every second day for second or two. I don't want to > lost all open connections, firewall state, etc, and to restart > dhclinet by hands, especially, when I'\m not at home anf my > girlfriend is. in such case. Another good example was provided by > Slava -- WiFi could disconnect for 10-15 seconds for multiple > reasons, and dropping of IP and all connections in such case is MAJOR > headache. > I don't understand all this talk that makes it sound like you lose your existing network connections when dhclient exits. I don't experience anything like that at all, and never have. I just pulled the network cable on this machine, did "sudo killall dhclient", plugged the network back in, I still have all my ssh connections to the world in a dozen open windows and can interact with any of them. Then I did "sudo dhclient re0" (simulating devd restarting dhclient on link-up) and it reacquired a lease for the same IP it had before I killed it, and still all my open connections are open. It has worked this way for me for years. Does it somehow not work this way for everyone? -- Ian From owner-freebsd-current@FreeBSD.ORG Tue Aug 21 15:26:58 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F1E991065686; Tue, 21 Aug 2012 15:26:57 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from onlyone.friendlyhosting.spb.ru (onlyone.friendlyhosting.spb.ru [IPv6:2a01:4f8:131:60a2::2]) by mx1.freebsd.org (Postfix) with ESMTP id 83B978FC12; Tue, 21 Aug 2012 15:26:57 +0000 (UTC) Received: from lion.home.serebryakov.spb.ru (unknown [IPv6:2001:470:923f:1:8870:d54b:33e8:55b2]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.friendlyhosting.spb.ru (Postfix) with ESMTPA id 9AD534AC2D; Tue, 21 Aug 2012 19:26:55 +0400 (MSK) Date: Tue, 21 Aug 2012 19:26:52 +0400 From: Lev Serebryakov Organization: FreeBSD Project X-Priority: 3 (Normal) Message-ID: <709115163.20120821192652@serebryakov.spb.ru> To: Ian Lepore In-Reply-To: <1345562163.27688.347.camel@revolution.hippie.lan> References: <20120821095527.GA33206@hell.ukr.net> <67977762.20120821154035@serebryakov.spb.ru> <1959717636.20120821155308@serebryakov.spb.ru> <201208210934.31484.jhb@freebsd.org> <1049151425.20120821190433@serebryakov.spb.ru> <1345562163.27688.347.camel@revolution.hippie.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: quoted-printable Cc: Garrett Cooper , Peter Jeremy , freebsd-current@freebsd.org, current@freebsd.org Subject: Re: r239356: does it mean, that synchronous dhcp and dhcplcinet with disabled devd gone? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: lev@FreeBSD.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Aug 2012 15:26:58 -0000 Hello, Ian. You wrote 21 =C1=D7=C7=D5=D3=D4=C1 2012 =C7., 19:16:03: IL> It has worked this way for me for years. Does it somehow not work this IL> way for everyone? Please, read comment to r239356. Starting from this revision dhclient exists on interface down and _remiove_ IP address from interface. Removal of address from interface will drop all open connections, which uses this address. --=20 // Black Lion AKA Lev Serebryakov From owner-freebsd-current@FreeBSD.ORG Tue Aug 21 15:26:58 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F1E991065686; Tue, 21 Aug 2012 15:26:57 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from onlyone.friendlyhosting.spb.ru (onlyone.friendlyhosting.spb.ru [IPv6:2a01:4f8:131:60a2::2]) by mx1.freebsd.org (Postfix) with ESMTP id 83B978FC12; Tue, 21 Aug 2012 15:26:57 +0000 (UTC) Received: from lion.home.serebryakov.spb.ru (unknown [IPv6:2001:470:923f:1:8870:d54b:33e8:55b2]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.friendlyhosting.spb.ru (Postfix) with ESMTPA id 9AD534AC2D; Tue, 21 Aug 2012 19:26:55 +0400 (MSK) Date: Tue, 21 Aug 2012 19:26:52 +0400 From: Lev Serebryakov Organization: FreeBSD Project X-Priority: 3 (Normal) Message-ID: <709115163.20120821192652@serebryakov.spb.ru> To: Ian Lepore In-Reply-To: <1345562163.27688.347.camel@revolution.hippie.lan> References: <20120821095527.GA33206@hell.ukr.net> <67977762.20120821154035@serebryakov.spb.ru> <1959717636.20120821155308@serebryakov.spb.ru> <201208210934.31484.jhb@freebsd.org> <1049151425.20120821190433@serebryakov.spb.ru> <1345562163.27688.347.camel@revolution.hippie.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: quoted-printable Cc: Garrett Cooper , Peter Jeremy , freebsd-current@freebsd.org, current@freebsd.org Subject: Re: r239356: does it mean, that synchronous dhcp and dhcplcinet with disabled devd gone? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: lev@FreeBSD.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Aug 2012 15:26:58 -0000 Hello, Ian. You wrote 21 =C1=D7=C7=D5=D3=D4=C1 2012 =C7., 19:16:03: IL> It has worked this way for me for years. Does it somehow not work this IL> way for everyone? Please, read comment to r239356. Starting from this revision dhclient exists on interface down and _remiove_ IP address from interface. Removal of address from interface will drop all open connections, which uses this address. --=20 // Black Lion AKA Lev Serebryakov From owner-freebsd-current@FreeBSD.ORG Tue Aug 21 15:55:16 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A9C821065675 for ; Tue, 21 Aug 2012 15:55:16 +0000 (UTC) (envelope-from freebsd@damnhippie.dyndns.org) Received: from qmta12.emeryville.ca.mail.comcast.net (qmta12.emeryville.ca.mail.comcast.net [76.96.27.227]) by mx1.freebsd.org (Postfix) with ESMTP id 84A548FC19 for ; Tue, 21 Aug 2012 15:55:16 +0000 (UTC) Received: from omta06.emeryville.ca.mail.comcast.net ([76.96.30.51]) by qmta12.emeryville.ca.mail.comcast.net with comcast id pQDs1j00716AWCUACTvAV7; Tue, 21 Aug 2012 15:55:10 +0000 Received: from damnhippie.dyndns.org ([24.8.232.202]) by omta06.emeryville.ca.mail.comcast.net with comcast id pTv81j00Y4NgCEG8STv9zb; Tue, 21 Aug 2012 15:55:10 +0000 Received: from [172.22.42.240] (revolution.hippie.lan [172.22.42.240]) by damnhippie.dyndns.org (8.14.3/8.14.3) with ESMTP id q7LFt752022467; Tue, 21 Aug 2012 09:55:07 -0600 (MDT) (envelope-from freebsd@damnhippie.dyndns.org) From: Ian Lepore To: lev@freebsd.org In-Reply-To: <709115163.20120821192652@serebryakov.spb.ru> References: <20120821095527.GA33206@hell.ukr.net> <67977762.20120821154035@serebryakov.spb.ru> <1959717636.20120821155308@serebryakov.spb.ru> <201208210934.31484.jhb@freebsd.org> <1049151425.20120821190433@serebryakov.spb.ru> <1345562163.27688.347.camel@revolution.hippie.lan> <709115163.20120821192652@serebryakov.spb.ru> Content-Type: text/plain; charset="koi8-r" Date: Tue, 21 Aug 2012 09:55:07 -0600 Message-ID: <1345564507.27688.354.camel@revolution.hippie.lan> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 8bit Cc: Garrett Cooper , freebsd-current@freebsd.org, Peter Jeremy Subject: Re: r239356: does it mean, that synchronous dhcp and dhcplcinet with disabled devd gone? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 21 Aug 2012 15:55:16 -0000 On Tue, 2012-08-21 at 19:26 +0400, Lev Serebryakov wrote: > Hello, Ian. > You wrote 21 Á×ÇÕÓÔÁ 2012 Ç., 19:16:03: > > IL> It has worked this way for me for years. Does it somehow not work this > IL> way for everyone? > Please, read comment to r239356. Starting from this revision > dhclient exists on interface down and _remiove_ IP address from > interface. Removal of address from interface will drop all open > connections, which uses this address. > Aha! That's where the confusion is happening -- I didn't read the comment, I read the code. I don't know what "teardown the configured lease" in that comment means, but it doesn't mean that the interface loses its current configuration, or that any existing connections are perturbed. If the cable is plugged back into the same network, the interface will get the same address it last had and existing connections continue to work, unless the dhcp server recycled that lease to another client while the cable was unplugged (highly unlikely unless the server/network is starved for addresses, since the dhcpd design is to avoid recycling recently-used addresses). The important point is that if you unplug the cable then plug it into a different network, now the right thing will happen -- you will acquire an address on the new network. That's the reason that this change is an important bugfix for a long standing (many many years) bug in freebsd's dhclient. -- Ian From owner-freebsd-current@FreeBSD.ORG Tue Aug 21 16:42:22 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0FB5E106566B for ; Tue, 21 Aug 2012 16:42:22 +0000 (UTC) (envelope-from satan@ukr.net) Received: from hell.ukr.net (hell.ukr.net [212.42.67.68]) by mx1.freebsd.org (Postfix) with ESMTP id B97648FC12 for ; Tue, 21 Aug 2012 16:42:21 +0000 (UTC) Received: from satan by hell.ukr.net with local ID 1T3rWz-000Bw5-Iz ; Tue, 21 Aug 2012 19:42:17 +0300 Date: Tue, 21 Aug 2012 19:42:17 +0300 From: Vitalij Satanivskij To: Garrett Cooper Message-ID: <20120821164217.GA45780@hell.ukr.net> References: <20120821095527.GA33206@hell.ukr.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Cc: Vitalij Satanivskij , current@freebsd.org Subject: Re: dhclient cause up/down cycle after 239356 ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 21 Aug 2012 16:42:22 -0000 Garrett Cooper wrote: GC> On Tue, Aug 21, 2012 at 2:55 AM, Vitalij Satanivskij wrote: GC> > Hi all, GC> > GC> > After last update my home machine begin doin some strange things - GC> GC> ... GC> GC> Try reverting r239356 -- if that works, then please let jhb@ know. GC> -Garrett Yes i'm revert it and everything is ok. Look's like dhclient do down/up sequence - Aug 21 19:21:00 home kernel: fxp0: link state changed to UP Aug 21 19:21:01 home kernel: fxp0: link state changed to DOWN Aug 21 19:21:01 home dhclient: New IP Address (fxp0): xx.xx.xx.xx Aug 21 19:21:01 home dhclient: New Subnet Mask (fxp0): 255.255.255.0 Aug 21 19:21:01 home dhclient: New Broadcast Address (fxp0): xx.xx.xx.xx Aug 21 19:21:01 home dhclient: New Routers (fxp0): xx.xx.xx.xx Aug 21 19:21:03 home kernel: fxp0: link state changed to UP and in r239356 when iface down dhclient exiting then iface become up, dhclient staring, get adress, bring iface down (why?) and exit. Before r239356 iface just doing down/up without dhclient exit and everything work fine. From owner-freebsd-current@FreeBSD.ORG Tue Aug 21 17:01:57 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8C431106566C for ; Tue, 21 Aug 2012 17:01:57 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from onlyone.friendlyhosting.spb.ru (onlyone.friendlyhosting.spb.ru [46.4.40.135]) by mx1.freebsd.org (Postfix) with ESMTP id 41CDD8FC12 for ; Tue, 21 Aug 2012 17:01:57 +0000 (UTC) Received: from lion.home.serebryakov.spb.ru (unknown [IPv6:2001:470:923f:1:8870:d54b:33e8:55b2]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.friendlyhosting.spb.ru (Postfix) with ESMTPA id 5605C4AC2D; Tue, 21 Aug 2012 21:01:55 +0400 (MSK) Date: Tue, 21 Aug 2012 21:01:52 +0400 From: Lev Serebryakov Organization: FreeBSD X-Priority: 3 (Normal) Message-ID: <1409150425.20120821210152@serebryakov.spb.ru> To: Ian Lepore In-Reply-To: <1345564507.27688.354.camel@revolution.hippie.lan> References: <20120821095527.GA33206@hell.ukr.net> <67977762.20120821154035@serebryakov.spb.ru> <1959717636.20120821155308@serebryakov.spb.ru> <201208210934.31484.jhb@freebsd.org> <1049151425.20120821190433@serebryakov.spb.ru> <1345562163.27688.347.camel@revolution.hippie.lan> <709115163.20120821192652@serebryakov.spb.ru> <1345564507.27688.354.camel@revolution.hippie.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: quoted-printable Cc: Garrett Cooper , freebsd-current@freebsd.org, Peter Jeremy Subject: Re: r239356: does it mean, that synchronous dhcp and dhcplcinet with disabled devd gone? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: lev@FreeBSD.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Aug 2012 17:01:57 -0000 Hello, Ian. You wrote 21 =C1=D7=C7=D5=D3=D4=C1 2012 =C7., 19:55:07: IL> I don't know what "teardown the configured lease" in that comment means, IL> but it doesn't mean that the interface loses its current configuration, IL> or that any existing connections are perturbed. Sorry, but comment in PR: http://www.freebsd.org/cgi/query-pr.cgi?pr=3D166656 says: =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 >dhclient on exit should also remove the IP address it has set. Yes, and the patch in the existing PR _should_ do that - it invokes the failure handler in the same way as the other dhclient failure modes. =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 I don't understand what exactly "should" means here -- it should, but it doesn't or it should and it does? But in any case, it looks like here is intention to remove IP address, and= if it doesn't done so, it will be ``fixed'' in future -- no contradictions/objections to this ``desired behavior'' is seen in this PR. IL> The important point is that if you unplug the cable then plug it into a IL> different network, now the right thing will happen -- you will acquire IL> an address on the new network. That's the reason that this change is an IL> important bugfix for a long standing (many many years) bug in freebsd's IL> dhclient. No, I'll be without dhclient at all, if I don't use devd :(. And absence of devd is completely legal, and should be supported. It is perfectly valid and sensible setup for small devices (think: MIPS-based routers, which are started to be supported now), where devd could be very costly in both terms of flash size (it is C++ application and need C++ runtime!) and memory (only devd event on such devices are this cable plugging/unplugging -- so using devd doesn't add any value for such setups). --=20 // Black Lion AKA Lev Serebryakov From owner-freebsd-current@FreeBSD.ORG Tue Aug 21 17:32:55 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 014B11065673 for ; Tue, 21 Aug 2012 17:32:55 +0000 (UTC) (envelope-from ohauer@gmx.de) Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by mx1.freebsd.org (Postfix) with SMTP id 475498FC15 for ; Tue, 21 Aug 2012 17:32:53 +0000 (UTC) Received: (qmail invoked by alias); 21 Aug 2012 17:32:53 -0000 Received: from p578be941.dip0.t-ipconnect.de (EHLO [192.168.0.100]) [87.139.233.65] by mail.gmx.net (mp070) with SMTP; 21 Aug 2012 19:32:53 +0200 X-Authenticated: #1956535 X-Provags-ID: V01U2FsdGVkX1/rHCAtqALrsKU7ssZC9ClzjUZnhZJ5GywrPbI+ZZ 9xnLgaU6KsTXa5 Message-ID: <5033C644.3050302@gmx.de> Date: Tue, 21 Aug 2012 19:32:52 +0200 From: olli hauer User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:14.0) Gecko/20120713 Thunderbird/14.0 MIME-Version: 1.0 To: lev@FreeBSD.org References: <20120821095527.GA33206@hell.ukr.net> <67977762.20120821154035@serebryakov.spb.ru> <1243982625.20120821154548@serebryakov.spb.ru> In-Reply-To: <1243982625.20120821154548@serebryakov.spb.ru> X-Enigmail-Version: 1.4.3 Content-Type: text/plain; charset=windows-1251 Content-Transfer-Encoding: 8bit X-Y-GMX-Trusted: 0 Cc: Garrett Cooper , current@freebsd.org, jhb@FreeBSD.org Subject: Re: r239356: does it mean, that synchronous dhcp and dhcplcinet with disabled devd gone? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 21 Aug 2012 17:32:55 -0000 On 2012-08-21 13:45, Lev Serebryakov wrote: > Hello, Lev. > You wrote 21 àâãóñòà 2012 ã., 15:40:35: > > GC>> Try reverting r239356 -- if that works, then please let jhb@ know. > LS> I'm confused by this commit, because it seems (from comment alone), > LS> that dhclient will not work without devd anymore (with "synchronous > LS> dhcp" option in rc.conf). > LS> Am I right? > Also, I don't like idea of removing IP address from interface when > cable is unplugged. It was very disturbing behavior of Windows > machines for years. I've unplug cable to change switch port for only a > second and all connections are broken, even if one second later > dhcpclient receive SAME lease! I don't like this. FreeBSD was very > tolerant to unplugging cable for eons, and I (and not only me) like > it. If I understand this change properly, it is no more the case :( > Oh, this is certainly exciting for clients in the backbone when a switch will be reloaded because of firmware upgrade. This behavior was a reason for me to run MS machines only virtual instead using fix IP addresses (using ip arp inspection and dhcp snooping on the whole network so fix IPs are a no-go) From owner-freebsd-current@FreeBSD.ORG Tue Aug 21 17:36:33 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9184F1065678 for ; Tue, 21 Aug 2012 17:36:33 +0000 (UTC) (envelope-from freebsd@damnhippie.dyndns.org) Received: from qmta12.emeryville.ca.mail.comcast.net (qmta12.emeryville.ca.mail.comcast.net [76.96.27.227]) by mx1.freebsd.org (Postfix) with ESMTP id 6B1ED8FC14 for ; Tue, 21 Aug 2012 17:36:33 +0000 (UTC) Received: from omta04.emeryville.ca.mail.comcast.net ([76.96.30.35]) by qmta12.emeryville.ca.mail.comcast.net with comcast id pR781j0020lTkoCACVcYml; Tue, 21 Aug 2012 17:36:32 +0000 Received: from damnhippie.dyndns.org ([24.8.232.202]) by omta04.emeryville.ca.mail.comcast.net with comcast id pVcX1j00P4NgCEG8QVcYfL; Tue, 21 Aug 2012 17:36:32 +0000 Received: from [172.22.42.240] (revolution.hippie.lan [172.22.42.240]) by damnhippie.dyndns.org (8.14.3/8.14.3) with ESMTP id q7LHaUfx022604; Tue, 21 Aug 2012 11:36:30 -0600 (MDT) (envelope-from freebsd@damnhippie.dyndns.org) From: Ian Lepore To: lev@freebsd.org In-Reply-To: <1409150425.20120821210152@serebryakov.spb.ru> References: <20120821095527.GA33206@hell.ukr.net> <67977762.20120821154035@serebryakov.spb.ru> <1959717636.20120821155308@serebryakov.spb.ru> <201208210934.31484.jhb@freebsd.org> <1049151425.20120821190433@serebryakov.spb.ru> <1345562163.27688.347.camel@revolution.hippie.lan> <709115163.20120821192652@serebryakov.spb.ru> <1345564507.27688.354.camel@revolution.hippie.lan> <1409150425.20120821210152@serebryakov.spb.ru> Content-Type: text/plain; charset="us-ascii" Date: Tue, 21 Aug 2012 11:36:30 -0600 Message-ID: <1345570590.27688.367.camel@revolution.hippie.lan> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: r239356: does it mean, that synchronous dhcp and dhcplcinet with disabled devd gone? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 21 Aug 2012 17:36:33 -0000 On Tue, 2012-08-21 at 21:01 +0400, Lev Serebryakov wrote: > IL> The important point is that if you unplug the cable then plug it into a > IL> different network, now the right thing will happen -- you will acquire > IL> an address on the new network. That's the reason that this change is an > IL> important bugfix for a long standing (many many years) bug in freebsd's > IL> dhclient. > No, I'll be without dhclient at all, if I don't use devd :(. And > absence of devd is completely legal, and should be supported. It is > perfectly valid and sensible setup for small devices (think: > MIPS-based routers, which are started to be supported now), where devd > could be very costly in both terms of flash size (it is C++ > application and need C++ runtime!) and memory (only devd event on > such devices are this cable plugging/unplugging -- so using devd > doesn't add any value for such setups). > I think it's funny how people have this knee-jerk reaction against C++ apps. The devd executable is not exactly an example of bloatware: 374k statically linked (so it already includes this "C++ runtime" that you think is large). We routinely deploy embedded systems that use apps written exclusively in C++, on systems that only have 32 or 64mb of ram. We've been doing so since the days when the biggest compact flash card you could buy was 64mb. Perhaps the right solution is to add a dhclient command line option to operate in the historical buggy mode: it doesn't exit on link status changes, and fails to work properly if those link status changes are happening because the physical connection has moved to another network. If so, I think the default should be to work correctly, and folks depending on the historical buggy behavior will have to add a parm to rc.conf. -- Ian From owner-freebsd-current@FreeBSD.ORG Tue Aug 21 17:40:33 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2FDC8106564A for ; Tue, 21 Aug 2012 17:40:33 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from onlyone.friendlyhosting.spb.ru (onlyone.friendlyhosting.spb.ru [IPv6:2a01:4f8:131:60a2::2]) by mx1.freebsd.org (Postfix) with ESMTP id B465A8FC28 for ; Tue, 21 Aug 2012 17:40:32 +0000 (UTC) Received: from lion.home.serebryakov.spb.ru (unknown [IPv6:2001:470:923f:1:8870:d54b:33e8:55b2]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.friendlyhosting.spb.ru (Postfix) with ESMTPA id 292A14AC31; Tue, 21 Aug 2012 21:40:31 +0400 (MSK) Date: Tue, 21 Aug 2012 21:40:27 +0400 From: Lev Serebryakov Organization: FreeBSD X-Priority: 3 (Normal) Message-ID: <753514912.20120821214027@serebryakov.spb.ru> To: Ian Lepore In-Reply-To: <1345570590.27688.367.camel@revolution.hippie.lan> References: <20120821095527.GA33206@hell.ukr.net> <67977762.20120821154035@serebryakov.spb.ru> <1959717636.20120821155308@serebryakov.spb.ru> <201208210934.31484.jhb@freebsd.org> <1049151425.20120821190433@serebryakov.spb.ru> <1345562163.27688.347.camel@revolution.hippie.lan> <709115163.20120821192652@serebryakov.spb.ru> <1345564507.27688.354.camel@revolution.hippie.lan> <1409150425.20120821210152@serebryakov.spb.ru> <1345570590.27688.367.camel@revolution.hippie.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-current@freebsd.org Subject: Re: r239356: does it mean, that synchronous dhcp and dhcplcinet with disabled devd gone? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: lev@FreeBSD.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Aug 2012 17:40:33 -0000 Hello, Ian. You wrote 21 =D0=B0=D0=B2=D0=B3=D1=83=D1=81=D1=82=D0=B0 2012 =D0=B3., 21:36= :30: IL> Perhaps the right solution is to add a dhclient command line option to IL> operate in the historical buggy mode: it doesn't exit on link status IL> changes, and fails to work properly if those link status changes are IL> happening because the physical connection has moved to another network. Right solution was spoken by jhb@ already: dhclient should re-request lease on interface down/up cycle. There is no need to exit and be started again in any case. It will work ``as expected'' without any options for everybody. --=20 // Black Lion AKA Lev Serebryakov From owner-freebsd-current@FreeBSD.ORG Tue Aug 21 17:42:30 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8FF82106566B for ; Tue, 21 Aug 2012 17:42:30 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from onlyone.friendlyhosting.spb.ru (onlyone.friendlyhosting.spb.ru [46.4.40.135]) by mx1.freebsd.org (Postfix) with ESMTP id 45D0C8FC18 for ; Tue, 21 Aug 2012 17:42:30 +0000 (UTC) Received: from lion.home.serebryakov.spb.ru (unknown [IPv6:2001:470:923f:1:8870:d54b:33e8:55b2]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.friendlyhosting.spb.ru (Postfix) with ESMTPA id B31A54AC2D; Tue, 21 Aug 2012 21:42:28 +0400 (MSK) Date: Tue, 21 Aug 2012 21:42:25 +0400 From: Lev Serebryakov Organization: FreeBSD X-Priority: 3 (Normal) Message-ID: <686419050.20120821214225@serebryakov.spb.ru> To: Ian Lepore In-Reply-To: <1345570590.27688.367.camel@revolution.hippie.lan> References: <20120821095527.GA33206@hell.ukr.net> <67977762.20120821154035@serebryakov.spb.ru> <1959717636.20120821155308@serebryakov.spb.ru> <201208210934.31484.jhb@freebsd.org> <1049151425.20120821190433@serebryakov.spb.ru> <1345562163.27688.347.camel@revolution.hippie.lan> <709115163.20120821192652@serebryakov.spb.ru> <1345564507.27688.354.camel@revolution.hippie.lan> <1409150425.20120821210152@serebryakov.spb.ru> <1345570590.27688.367.camel@revolution.hippie.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-current@freebsd.org Subject: Re: r239356: does it mean, that synchronous dhcp and dhcplcinet with disabled devd gone? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: lev@FreeBSD.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Aug 2012 17:42:30 -0000 Hello, Ian. You wrote 21 =D0=B0=D0=B2=D0=B3=D1=83=D1=81=D1=82=D0=B0 2012 =D0=B3., 21:36= :30: IL> I think it's funny how people have this knee-jerk reaction against C++ IL> apps. The devd executable is not exactly an example of bloatware: 374k IL> statically linked (so it already includes this "C++ runtime" that you IL> think is large). We routinely deploy embedded systems that use apps IL> written exclusively in C++, on systems that only have 32 or 64mb of ram. IL> We've been doing so since the days when the biggest compact flash card IL> you could buy was 64mb. BTW, typical MIPS SoC-based router has only 16MiB of flash. And, yes, FreeBSD doesn't fit well in this size now, but why add another mandatory program, only role of which is to monitor network cable and re-run the same program every time? --=20 // Black Lion AKA Lev Serebryakov From owner-freebsd-current@FreeBSD.ORG Tue Aug 21 17:45:23 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2183A106568E; Tue, 21 Aug 2012 17:45:23 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) by mx1.freebsd.org (Postfix) with ESMTP id C03128FC14; Tue, 21 Aug 2012 17:45:22 +0000 (UTC) Received: from slw by zxy.spb.ru with local (Exim 4.69 (FreeBSD)) (envelope-from ) id 1T3sYM-000N5A-6B; Tue, 21 Aug 2012 21:47:46 +0400 Date: Tue, 21 Aug 2012 21:47:46 +0400 From: Slawa Olhovchenkov To: Lev Serebryakov Message-ID: <20120821174746.GD88729@zxy.spb.ru> References: <67977762.20120821154035@serebryakov.spb.ru> <1959717636.20120821155308@serebryakov.spb.ru> <201208210934.31484.jhb@freebsd.org> <1049151425.20120821190433@serebryakov.spb.ru> <1345562163.27688.347.camel@revolution.hippie.lan> <709115163.20120821192652@serebryakov.spb.ru> <1345564507.27688.354.camel@revolution.hippie.lan> <1409150425.20120821210152@serebryakov.spb.ru> <1345570590.27688.367.camel@revolution.hippie.lan> <753514912.20120821214027@serebryakov.spb.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <753514912.20120821214027@serebryakov.spb.ru> User-Agent: Mutt/1.5.21 (2010-09-15) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false Cc: Ian Lepore , freebsd-current@freebsd.org Subject: Re: r239356: does it mean, that synchronous dhcp and dhcplcinet with disabled devd gone? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 21 Aug 2012 17:45:23 -0000 On Tue, Aug 21, 2012 at 09:40:27PM +0400, Lev Serebryakov wrote: > Hello, Ian. > You wrote 21 Á×ÇÕÓÔÁ 2012 Ç., 21:36:30: > > IL> Perhaps the right solution is to add a dhclient command line option to > IL> operate in the historical buggy mode: it doesn't exit on link status > IL> changes, and fails to work properly if those link status changes are > IL> happening because the physical connection has moved to another network. > Right solution was spoken by jhb@ already: dhclient should > re-request lease on interface down/up cycle. There is no need to exit > and be started again in any case. It will work ``as expected'' > without any options for everybody. Not re-request lease, simple renew. From owner-freebsd-current@FreeBSD.ORG Tue Aug 21 18:12:10 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx2.freebsd.org (mx2.freebsd.org [69.147.83.53]) by hub.freebsd.org (Postfix) with ESMTP id 04F631065670; Tue, 21 Aug 2012 18:12:10 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from [127.0.0.1] (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id C1CFE14D950; Tue, 21 Aug 2012 18:12:09 +0000 (UTC) Message-ID: <5033CF7A.8080406@FreeBSD.org> Date: Tue, 21 Aug 2012 11:12:10 -0700 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:14.0) Gecko/20120713 Thunderbird/14.0 MIME-Version: 1.0 To: John Baldwin References: <20120821095527.GA33206@hell.ukr.net> <67977762.20120821154035@serebryakov.spb.ru> <1959717636.20120821155308@serebryakov.spb.ru> <201208210934.31484.jhb@freebsd.org> In-Reply-To: <201208210934.31484.jhb@freebsd.org> X-Enigmail-Version: 1.4.3 OpenPGP: id=1A1ABC84 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Garrett Cooper , freebsd-current@freebsd.org, lev@freebsd.org, current@freebsd.org, Peter Jeremy Subject: Re: r239356: does it mean, that synchronous dhcp and dhcplcinet with disabled devd gone? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 21 Aug 2012 18:12:10 -0000 On 8/21/2012 6:34 AM, John Baldwin wrote: > Humm. devd is the more common case, and we explicitly don't use devd to start > dhclient on boot even when devd is enabled (so out of the box dhcp would first > be started by rc, but would be restarted by devd). That sounds reasonable. People who choose not to run devd can be responsible for restarting dhclient themselves. > Another option is to rework dhclient to work like it does on OpenBSD where it > renews its lease if the link bounces, but to not exit when the link goes down. That would be preferable. > That case would fix the currently broken case that you unplug your cable, take > your laptop over to another network (e.g. take it home if suspend/resume > works), then plug it back in and are still stuck with your old IP. I do think it's important to fix this case. However I agree with the chorus of responders that it is more important to maintain our historic resilience to temporary loss of connectivity. Doug -- I am only one, but I am one. I cannot do everything, but I can do something. And I will not let what I cannot do interfere with what I can do. -- Edward Everett Hale, (1822 - 1909) From owner-freebsd-current@FreeBSD.ORG Tue Aug 21 18:12:10 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx2.freebsd.org (mx2.freebsd.org [69.147.83.53]) by hub.freebsd.org (Postfix) with ESMTP id 04F631065670; Tue, 21 Aug 2012 18:12:10 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from [127.0.0.1] (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id C1CFE14D950; Tue, 21 Aug 2012 18:12:09 +0000 (UTC) Message-ID: <5033CF7A.8080406@FreeBSD.org> Date: Tue, 21 Aug 2012 11:12:10 -0700 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:14.0) Gecko/20120713 Thunderbird/14.0 MIME-Version: 1.0 To: John Baldwin References: <20120821095527.GA33206@hell.ukr.net> <67977762.20120821154035@serebryakov.spb.ru> <1959717636.20120821155308@serebryakov.spb.ru> <201208210934.31484.jhb@freebsd.org> In-Reply-To: <201208210934.31484.jhb@freebsd.org> X-Enigmail-Version: 1.4.3 OpenPGP: id=1A1ABC84 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Garrett Cooper , freebsd-current@freebsd.org, lev@freebsd.org, current@freebsd.org, Peter Jeremy Subject: Re: r239356: does it mean, that synchronous dhcp and dhcplcinet with disabled devd gone? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 21 Aug 2012 18:12:10 -0000 On 8/21/2012 6:34 AM, John Baldwin wrote: > Humm. devd is the more common case, and we explicitly don't use devd to start > dhclient on boot even when devd is enabled (so out of the box dhcp would first > be started by rc, but would be restarted by devd). That sounds reasonable. People who choose not to run devd can be responsible for restarting dhclient themselves. > Another option is to rework dhclient to work like it does on OpenBSD where it > renews its lease if the link bounces, but to not exit when the link goes down. That would be preferable. > That case would fix the currently broken case that you unplug your cable, take > your laptop over to another network (e.g. take it home if suspend/resume > works), then plug it back in and are still stuck with your old IP. I do think it's important to fix this case. However I agree with the chorus of responders that it is more important to maintain our historic resilience to temporary loss of connectivity. Doug -- I am only one, but I am one. I cannot do everything, but I can do something. And I will not let what I cannot do interfere with what I can do. -- Edward Everett Hale, (1822 - 1909) From owner-freebsd-current@FreeBSD.ORG Tue Aug 21 18:17:48 2012 Return-Path: Delivered-To: current@FreeBSD.org Received: from mx2.freebsd.org (mx2.freebsd.org [IPv6:2001:4f8:fff6::35]) by hub.freebsd.org (Postfix) with ESMTP id 39B31106566B; Tue, 21 Aug 2012 18:17:48 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from [127.0.0.1] (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id D5DDD14DA48; Tue, 21 Aug 2012 18:17:34 +0000 (UTC) Message-ID: <5033D0C0.4030805@FreeBSD.org> Date: Tue, 21 Aug 2012 11:17:36 -0700 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:14.0) Gecko/20120713 Thunderbird/14.0 MIME-Version: 1.0 To: Baptiste Daroussin References: <20120820194313.GC23607@ithaqua.etoilebsd.net> <20120821132643.GE37262@felucia.tataz.chchile.org> <20120821134623.GH5044@ithaqua.etoilebsd.net> In-Reply-To: <20120821134623.GH5044@ithaqua.etoilebsd.net> X-Enigmail-Version: 1.4.3 OpenPGP: id=1A1ABC84 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: ports@FreeBSD.org, current@FreeBSD.org Subject: Re: pkgng 1.0 release schedule, and HEAD switch to pkgng by default schedule X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 21 Aug 2012 18:17:48 -0000 On 8/21/2012 6:46 AM, Baptiste Daroussin wrote: > I would also like to just remove pkg_* tools from RELENG_10 if that fits the > schedule. Um, no? Until pkg becomes mandatory (which can't happen for several years) the pkg_* tools can't be removed altogether. What _would_ be useful is what should have been done many years ago when it was first suggested: Move the pkg_* tools to ports. It's too late for 9.1 already, but if you made that change today in HEAD, and after 9.1 (but before 8.4) you MFC it to stable/[89], then you could theoretically make pkg mandatory after 9.1 EOLs. To make my point more clear, the ports tree has to support the last release to ship with pkg_* tools in the base throughout its lifetime. To do anything else would be be a massive POLA violation. Doug -- I am only one, but I am one. I cannot do everything, but I can do something. And I will not let what I cannot do interfere with what I can do. -- Edward Everett Hale, (1822 - 1909) From owner-freebsd-current@FreeBSD.ORG Tue Aug 21 18:18:20 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 848671065840 for ; Tue, 21 Aug 2012 18:18:20 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from onlyone.friendlyhosting.spb.ru (onlyone.friendlyhosting.spb.ru [46.4.40.135]) by mx1.freebsd.org (Postfix) with ESMTP id 35D468FC08 for ; Tue, 21 Aug 2012 18:18:20 +0000 (UTC) Received: from lion.home.serebryakov.spb.ru (unknown [IPv6:2001:470:923f:1:8870:d54b:33e8:55b2]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.friendlyhosting.spb.ru (Postfix) with ESMTPA id B61084AC2D; Tue, 21 Aug 2012 22:18:18 +0400 (MSK) Date: Tue, 21 Aug 2012 22:18:15 +0400 From: Lev Serebryakov Organization: FreeBSD X-Priority: 3 (Normal) Message-ID: <867456073.20120821221815@serebryakov.spb.ru> To: Slawa Olhovchenkov In-Reply-To: <20120821174746.GD88729@zxy.spb.ru> References: <67977762.20120821154035@serebryakov.spb.ru> <1959717636.20120821155308@serebryakov.spb.ru> <201208210934.31484.jhb@freebsd.org> <1049151425.20120821190433@serebryakov.spb.ru> <1345562163.27688.347.camel@revolution.hippie.lan> <709115163.20120821192652@serebryakov.spb.ru> <1345564507.27688.354.camel@revolution.hippie.lan> <1409150425.20120821210152@serebryakov.spb.ru> <1345570590.27688.367.camel@revolution.hippie.lan> <753514912.20120821214027@serebryakov.spb.ru> <20120821174746.GD88729@zxy.spb.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: quoted-printable Cc: Ian Lepore , freebsd-current@freebsd.org Subject: Re: r239356: does it mean, that synchronous dhcp and dhcplcinet with disabled devd gone? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: lev@FreeBSD.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Aug 2012 18:18:20 -0000 Hello, Slawa. You wrote 21 =C1=D7=C7=D5=D3=D4=C1 2012 =C7., 21:47:46: SO> Not re-request lease, simple renew. Sorry, I'm not very strong in exact terms here. --=20 // Black Lion AKA Lev Serebryakov From owner-freebsd-current@FreeBSD.ORG Tue Aug 21 18:31:35 2012 Return-Path: Delivered-To: current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C3E29106566C; Tue, 21 Aug 2012 18:31:35 +0000 (UTC) (envelope-from bapt@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 8B7738FC08; Tue, 21 Aug 2012 18:31:35 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q7LIVZOs041393; Tue, 21 Aug 2012 18:31:35 GMT (envelope-from bapt@FreeBSD.org) Received: (from bapt@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q7LIVZtc041391; Tue, 21 Aug 2012 18:31:35 GMT (envelope-from bapt@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: bapt set sender to bapt@FreeBSD.org using -f Date: Tue, 21 Aug 2012 20:31:32 +0200 From: Baptiste Daroussin To: Doug Barton Message-ID: <20120821183132.GJ5044@ithaqua.etoilebsd.net> References: <20120820194313.GC23607@ithaqua.etoilebsd.net> <20120821132643.GE37262@felucia.tataz.chchile.org> <20120821134623.GH5044@ithaqua.etoilebsd.net> <5033D0C0.4030805@FreeBSD.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="ofZMSlrAVk9bLeVm" Content-Disposition: inline In-Reply-To: <5033D0C0.4030805@FreeBSD.org> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: ports@FreeBSD.org, current@FreeBSD.org Subject: Re: pkgng 1.0 release schedule, and HEAD switch to pkgng by default schedule X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 21 Aug 2012 18:31:35 -0000 --ofZMSlrAVk9bLeVm Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Aug 21, 2012 at 11:17:36AM -0700, Doug Barton wrote: > On 8/21/2012 6:46 AM, Baptiste Daroussin wrote: > > I would also like to just remove pkg_* tools from RELENG_10 if that fit= s the > > schedule. >=20 > Um, no? >=20 > Until pkg becomes mandatory (which can't happen for several years) the > pkg_* tools can't be removed altogether. >=20 > What _would_ be useful is what should have been done many years ago when > it was first suggested: Move the pkg_* tools to ports. >=20 > It's too late for 9.1 already, but if you made that change today in > HEAD, and after 9.1 (but before 8.4) you MFC it to stable/[89], then you > could theoretically make pkg mandatory after 9.1 EOLs. >=20 > To make my point more clear, the ports tree has to support the last > release to ship with pkg_* tools in the base throughout its lifetime. To > do anything else would be be a massive POLA violation. >=20 > Doug >=20 > --=20 >=20 > I am only one, but I am one. I cannot do everything, but I can do > something. And I will not let what I cannot do interfere with what > I can do. > -- Edward Everett Hale, (1822 - 1909) that is what I meant of course, sorry if I badly said it at first Bapt --ofZMSlrAVk9bLeVm Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEARECAAYFAlAz1AQACgkQ8kTtMUmk6EyOSQCcCqNHoKOuooxpf2PVr62Dlz65 z14An1MF8LFu2wkrANjxZbP5DZyXvSEJ =UC3c -----END PGP SIGNATURE----- --ofZMSlrAVk9bLeVm-- From owner-freebsd-current@FreeBSD.ORG Tue Aug 21 18:47:37 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E9FD5106564A; Tue, 21 Aug 2012 18:47:37 +0000 (UTC) (envelope-from yanegomi@gmail.com) Received: from mail-yx0-f182.google.com (mail-yx0-f182.google.com [209.85.213.182]) by mx1.freebsd.org (Postfix) with ESMTP id 6B0D98FC08; Tue, 21 Aug 2012 18:47:37 +0000 (UTC) Received: by yenl7 with SMTP id l7so155758yen.13 for ; Tue, 21 Aug 2012 11:47:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=S6SUWKy/pCBzu9jYDVPb27gtCujYTtVY3NAHsXWuIpE=; b=0Dtzl3MZ73SYT3+7FmgPXRji7+ttX5Q2HuZlHAZscczuKuqBrcYp54Rt5kR+5bOORY 8A9Qd4AJtdtL+uclqbRX6ouQsNhI10Olpundj3hf9tLMpX/vTUn88v9t+3KzbWu0/YJ7 OONmgN1dE/wJBo0TqKOvgiCzi0k904oVM24UvTDlc2E+EZXCUY9X3ZPCZYDoRr4PuB92 03DL7jwM2n+wKGE+NnI9Tb5Z6enG6GGhQZtUsxgyIlEqEzBUvOpN9OfOl3cmlIil4dQt 2C2cJMHHCN2yphRhebdELGMb0H8SSY+afSjInM7bYqIKJ2OGQDzGNqDVTMxs8kMhs08m jiIA== MIME-Version: 1.0 Received: by 10.60.171.69 with SMTP id as5mr13995875oec.100.1345574856520; Tue, 21 Aug 2012 11:47:36 -0700 (PDT) Received: by 10.76.142.201 with HTTP; Tue, 21 Aug 2012 11:47:36 -0700 (PDT) In-Reply-To: <5033D0C0.4030805@FreeBSD.org> References: <20120820194313.GC23607@ithaqua.etoilebsd.net> <20120821132643.GE37262@felucia.tataz.chchile.org> <20120821134623.GH5044@ithaqua.etoilebsd.net> <5033D0C0.4030805@FreeBSD.org> Date: Tue, 21 Aug 2012 11:47:36 -0700 Message-ID: From: Garrett Cooper To: Doug Barton Content-Type: text/plain; charset=ISO-8859-1 Cc: ports@freebsd.org, Baptiste Daroussin , current@freebsd.org Subject: Re: pkgng 1.0 release schedule, and HEAD switch to pkgng by default schedule X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 21 Aug 2012 18:47:38 -0000 On Tue, Aug 21, 2012 at 11:17 AM, Doug Barton wrote: > On 8/21/2012 6:46 AM, Baptiste Daroussin wrote: >> I would also like to just remove pkg_* tools from RELENG_10 if that fits the >> schedule. > > Um, no? ... > What _would_ be useful is what should have been done many years ago when > it was first suggested: Move the pkg_* tools to ports. It already exists -- it's just out of date / crufty: $ make describe pkg_install-20090902|/usr/ports/ports-mgmt/pkg_install|/usr/local|FreeBSD -STABLE version of the package tools|/usr/ports/ports-mgmt/pkg_install/pkg-descr|portmgr@FreeBSD.org|ports-mgmt||||||http://www.freebsd.org/cgi/cvsweb.cgi/src/usr.sbin/pkg_install/ > It's too late for 9.1 already, but if you made that change today in > HEAD, and after 9.1 (but before 8.4) you MFC it to stable/[89], then you > could theoretically make pkg mandatory after 9.1 EOLs. > > To make my point more clear, the ports tree has to support the last > release to ship with pkg_* tools in the base throughout its lifetime. To > do anything else would be be a massive POLA violation. Agreed. Thanks, -Garrett From owner-freebsd-current@FreeBSD.ORG Tue Aug 21 18:59:53 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx2.freebsd.org (mx2.freebsd.org [IPv6:2001:4f8:fff6::35]) by hub.freebsd.org (Postfix) with ESMTP id A3A8A1065670; Tue, 21 Aug 2012 18:59:53 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from [127.0.0.1] (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id 612D314DB4B; Tue, 21 Aug 2012 18:59:53 +0000 (UTC) Message-ID: <5033DAAA.20403@FreeBSD.org> Date: Tue, 21 Aug 2012 11:59:54 -0700 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:14.0) Gecko/20120713 Thunderbird/14.0 MIME-Version: 1.0 To: Garrett Cooper References: <20120820194313.GC23607@ithaqua.etoilebsd.net> <20120821132643.GE37262@felucia.tataz.chchile.org> <20120821134623.GH5044@ithaqua.etoilebsd.net> <5033D0C0.4030805@FreeBSD.org> In-Reply-To: X-Enigmail-Version: 1.4.3 OpenPGP: id=1A1ABC84 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: ports@freebsd.org, Baptiste Daroussin , current@freebsd.org Subject: Re: pkgng 1.0 release schedule, and HEAD switch to pkgng by default schedule X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 21 Aug 2012 18:59:53 -0000 On 8/21/2012 11:47 AM, Garrett Cooper wrote: > On Tue, Aug 21, 2012 at 11:17 AM, Doug Barton wrote: >> On 8/21/2012 6:46 AM, Baptiste Daroussin wrote: >>> I would also like to just remove pkg_* tools from RELENG_10 if that fits the >>> schedule. >> >> Um, no? > > ... > >> What _would_ be useful is what should have been done many years ago when >> it was first suggested: Move the pkg_* tools to ports. > > It already exists -- it's just out of date / crufty: Right ... I was using "move" as shorthand for several different ideas, including but not limited to the latest version of the code itself, robust support for the code going forward, the primary supported way of using pkg_*, etc. All of these ideas have been discussed in the past, so I was hoping to avoid having to re-discuss them. :) >> It's too late for 9.1 already, but if you made that change today in >> HEAD, and after 9.1 (but before 8.4) you MFC it to stable/[89], then you >> could theoretically make pkg mandatory after 9.1 EOLs. >> >> To make my point more clear, the ports tree has to support the last >> release to ship with pkg_* tools in the base throughout its lifetime. To >> do anything else would be be a massive POLA violation. > > Agreed. Great (and I saw Baptiste's response on this as well). Glad to hear that we're on the same page about something at least. :) -- I am only one, but I am one. I cannot do everything, but I can do something. And I will not let what I cannot do interfere with what I can do. -- Edward Everett Hale, (1822 - 1909) From owner-freebsd-current@FreeBSD.ORG Tue Aug 21 19:05:11 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 79A1F106566C; Tue, 21 Aug 2012 19:05:11 +0000 (UTC) (envelope-from bapt@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 3FF9E8FC1C; Tue, 21 Aug 2012 19:05:11 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q7LJ5BFs044009; Tue, 21 Aug 2012 19:05:11 GMT (envelope-from bapt@freebsd.org) Received: (from bapt@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q7LJ5BEY044008; Tue, 21 Aug 2012 19:05:11 GMT (envelope-from bapt@freebsd.org) X-Authentication-Warning: freefall.freebsd.org: bapt set sender to bapt@freebsd.org using -f Date: Tue, 21 Aug 2012 21:05:00 +0200 From: Baptiste Daroussin To: Garrett Cooper Message-ID: <20120821190500.GA46595@ithaqua.etoilebsd.net> References: <20120820194313.GC23607@ithaqua.etoilebsd.net> <20120821132643.GE37262@felucia.tataz.chchile.org> <20120821134623.GH5044@ithaqua.etoilebsd.net> <5033D0C0.4030805@FreeBSD.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="lrZ03NoBR/3+SXJZ" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Cc: ports@freebsd.org, Doug Barton , current@freebsd.org Subject: Re: pkgng 1.0 release schedule, and HEAD switch to pkgng by default schedule X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 21 Aug 2012 19:05:11 -0000 --lrZ03NoBR/3+SXJZ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Aug 21, 2012 at 11:47:36AM -0700, Garrett Cooper wrote: > On Tue, Aug 21, 2012 at 11:17 AM, Doug Barton wrote: > > On 8/21/2012 6:46 AM, Baptiste Daroussin wrote: > >> I would also like to just remove pkg_* tools from RELENG_10 if that fi= ts the > >> schedule. > > > > Um, no? >=20 > ... >=20 > > What _would_ be useful is what should have been done many years ago when > > it was first suggested: Move the pkg_* tools to ports. >=20 > It already exists -- it's just out of date / crufty: >=20 > $ make describe > pkg_install-20090902|/usr/ports/ports-mgmt/pkg_install|/usr/local|FreeBSD > -STABLE version of the package > tools|/usr/ports/ports-mgmt/pkg_install/pkg-descr|portmgr@FreeBSD.org|por= ts-mgmt||||||http://www.freebsd.org/cgi/cvsweb.cgi/src/usr.sbin/pkg_install/ >=20 > > It's too late for 9.1 already, but if you made that change today in > > HEAD, and after 9.1 (but before 8.4) you MFC it to stable/[89], then you > > could theoretically make pkg mandatory after 9.1 EOLs. > > > > To make my point more clear, the ports tree has to support the last > > release to ship with pkg_* tools in the base throughout its lifetime. To > > do anything else would be be a massive POLA violation. >=20 > Agreed. > Thanks, > -Garrett Let's rephrase the plan: 1/ if it fits the schedule: get rid of pkg_* tools in current to be able to= have a fully pkgng only 10-RELEASE 2/ switch 9.2 (the ports tree) to pkgng (but keep pkg_* tools maybe drop th= em, but that is to be discussed to avoid POLA 3/ do the same for 8 once all of our supported release are fully pkgng aware and all the pkg_* release are EOLed, drop support for pkg_* tools from the ports tree. regards, Bapt --lrZ03NoBR/3+SXJZ Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEARECAAYFAlAz29wACgkQ8kTtMUmk6ExrlgCgl2KExigBBlfHciEoOoWicaSq Lm0AnRqmvtDmD6JF8O2FHdmLApJY5afN =Ch5O -----END PGP SIGNATURE----- --lrZ03NoBR/3+SXJZ-- From owner-freebsd-current@FreeBSD.ORG Tue Aug 21 19:21:20 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id F33E71065670; Tue, 21 Aug 2012 19:21:19 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) by mx1.freebsd.org (Postfix) with ESMTP id A1EBE8FC14; Tue, 21 Aug 2012 19:21:19 +0000 (UTC) Received: from slw by zxy.spb.ru with local (Exim 4.69 (FreeBSD)) (envelope-from ) id 1T3u3C-000OaM-W9; Tue, 21 Aug 2012 23:23:43 +0400 Date: Tue, 21 Aug 2012 23:23:42 +0400 From: Slawa Olhovchenkov To: Lev Serebryakov Message-ID: <20120821192342.GU98910@zxy.spb.ru> References: <201208210934.31484.jhb@freebsd.org> <1049151425.20120821190433@serebryakov.spb.ru> <1345562163.27688.347.camel@revolution.hippie.lan> <709115163.20120821192652@serebryakov.spb.ru> <1345564507.27688.354.camel@revolution.hippie.lan> <1409150425.20120821210152@serebryakov.spb.ru> <1345570590.27688.367.camel@revolution.hippie.lan> <753514912.20120821214027@serebryakov.spb.ru> <20120821174746.GD88729@zxy.spb.ru> <867456073.20120821221815@serebryakov.spb.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <867456073.20120821221815@serebryakov.spb.ru> User-Agent: Mutt/1.5.21 (2010-09-15) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false Cc: Ian Lepore , freebsd-current@freebsd.org Subject: Re: r239356: does it mean, that synchronous dhcp and dhcplcinet with disabled devd gone? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 21 Aug 2012 19:21:20 -0000 On Tue, Aug 21, 2012 at 10:18:15PM +0400, Lev Serebryakov wrote: > SO> Not re-request lease, simple renew. > Sorry, I'm not very strong in exact terms here. dhcp client can sent different requests: DHCPDISCOVER from 0.0.0.0 to 255.255.255.255 DHCPREQUEST from 0.0.0.0 to SERVER_IP (from DHCPOFFER) or DHCPRELEASE DHCPDISCOVER from 0.0.0.0 to 255.255.255.255 DHCPREQUEST from 0.0.0.0 to SERVER_IP or DHCPREQUEST from 0.0.0.0 to 255.255.255.255 or DHCPREQUEST from IP to SERVER_IP and DHCPINFORM for quering additional parametrs after boot, w/o change IP (for example IE request information about proxy auto config) renew address at lease_time/2 usually DHCPREQUEST from IP to SERVER_IP. From owner-freebsd-current@FreeBSD.ORG Tue Aug 21 19:38:03 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx2.freebsd.org (mx2.freebsd.org [69.147.83.53]) by hub.freebsd.org (Postfix) with ESMTP id 5756C106566C; Tue, 21 Aug 2012 19:38:03 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from [127.0.0.1] (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id A939715FADF; Tue, 21 Aug 2012 19:38:02 +0000 (UTC) Message-ID: <5033E39C.3060700@FreeBSD.org> Date: Tue, 21 Aug 2012 12:38:04 -0700 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:14.0) Gecko/20120713 Thunderbird/14.0 MIME-Version: 1.0 To: Baptiste Daroussin References: <20120820194313.GC23607@ithaqua.etoilebsd.net> <20120821132643.GE37262@felucia.tataz.chchile.org> <20120821134623.GH5044@ithaqua.etoilebsd.net> <5033D0C0.4030805@FreeBSD.org> <20120821190500.GA46595@ithaqua.etoilebsd.net> In-Reply-To: <20120821190500.GA46595@ithaqua.etoilebsd.net> X-Enigmail-Version: 1.4.3 OpenPGP: id=1A1ABC84 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Garrett Cooper , ports@freebsd.org, current@freebsd.org Subject: Re: pkgng 1.0 release schedule, and HEAD switch to pkgng by default schedule X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 21 Aug 2012 19:38:03 -0000 On 8/21/2012 12:05 PM, Baptiste Daroussin wrote: > 1/ if it fits the schedule: get rid of pkg_* tools in current to be > able to have a fully pkgng only 10-RELEASE I think it would fit better with historic precedents to make pkg optional (but default on) in 10, and mandatory in 11. As stated before, I'm fine with removing pkg_* tools from 10 if there is robust support for them in the ports tree. I know you're excited about this project, but let's not lose sight of how big a change this is, and how important ports are to the project. Doug -- I am only one, but I am one. I cannot do everything, but I can do something. And I will not let what I cannot do interfere with what I can do. -- Edward Everett Hale, (1822 - 1909) From owner-freebsd-current@FreeBSD.ORG Tue Aug 21 19:42:11 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 681221065675; Tue, 21 Aug 2012 19:42:11 +0000 (UTC) (envelope-from bapt@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 47E218FC08; Tue, 21 Aug 2012 19:42:11 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q7LJgBJx049735; Tue, 21 Aug 2012 19:42:11 GMT (envelope-from bapt@freebsd.org) Received: (from bapt@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q7LJgBpb049734; Tue, 21 Aug 2012 19:42:11 GMT (envelope-from bapt@freebsd.org) X-Authentication-Warning: freefall.freebsd.org: bapt set sender to bapt@freebsd.org using -f Date: Tue, 21 Aug 2012 21:42:08 +0200 From: Baptiste Daroussin To: Doug Barton Message-ID: <20120821194208.GC46595@ithaqua.etoilebsd.net> References: <20120820194313.GC23607@ithaqua.etoilebsd.net> <20120821132643.GE37262@felucia.tataz.chchile.org> <20120821134623.GH5044@ithaqua.etoilebsd.net> <5033D0C0.4030805@FreeBSD.org> <20120821190500.GA46595@ithaqua.etoilebsd.net> <5033E39C.3060700@FreeBSD.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="yLVHuoLXiP9kZBkt" Content-Disposition: inline In-Reply-To: <5033E39C.3060700@FreeBSD.org> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: Garrett Cooper , ports@freebsd.org, current@freebsd.org Subject: Re: pkgng 1.0 release schedule, and HEAD switch to pkgng by default schedule X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 21 Aug 2012 19:42:11 -0000 --yLVHuoLXiP9kZBkt Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Aug 21, 2012 at 12:38:04PM -0700, Doug Barton wrote: > On 8/21/2012 12:05 PM, Baptiste Daroussin wrote: > > 1/ if it fits the schedule: get rid of pkg_* tools in current to be > > able to have a fully pkgng only 10-RELEASE >=20 > I think it would fit better with historic precedents to make pkg > optional (but default on) in 10, and mandatory in 11. As stated > before, I'm fine with removing pkg_* tools from 10 if there is robust > support for them in the ports tree. >=20 > I know you're excited about this project, but let's not lose sight of > how big a change this is, and how important ports are to the project. >=20 That was what "if it fits the schedule" was about. regards, Bapt --yLVHuoLXiP9kZBkt Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEARECAAYFAlAz5JAACgkQ8kTtMUmk6ExhlwCfa9wO7Q26VcEIbVbZX4zKLUOm IvwAnR7vY2wV2gu+UmiE+NYzlWzOX6w7 =bGLn -----END PGP SIGNATURE----- --yLVHuoLXiP9kZBkt-- From owner-freebsd-current@FreeBSD.ORG Tue Aug 21 19:51:21 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx2.freebsd.org (mx2.freebsd.org [IPv6:2001:4f8:fff6::35]) by hub.freebsd.org (Postfix) with ESMTP id B81FD106566C; Tue, 21 Aug 2012 19:51:21 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from [127.0.0.1] (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id 3903B14E74F; Tue, 21 Aug 2012 19:51:21 +0000 (UTC) Message-ID: <5033E6BA.8080309@FreeBSD.org> Date: Tue, 21 Aug 2012 12:51:22 -0700 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:14.0) Gecko/20120713 Thunderbird/14.0 MIME-Version: 1.0 To: Baptiste Daroussin References: <20120820194313.GC23607@ithaqua.etoilebsd.net> <20120821132643.GE37262@felucia.tataz.chchile.org> <20120821134623.GH5044@ithaqua.etoilebsd.net> <5033D0C0.4030805@FreeBSD.org> <20120821190500.GA46595@ithaqua.etoilebsd.net> <5033E39C.3060700@FreeBSD.org> <20120821194208.GC46595@ithaqua.etoilebsd.net> In-Reply-To: <20120821194208.GC46595@ithaqua.etoilebsd.net> X-Enigmail-Version: 1.4.3 OpenPGP: id=1A1ABC84 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Garrett Cooper , ports@freebsd.org, current@freebsd.org Subject: Re: pkgng 1.0 release schedule, and HEAD switch to pkgng by default schedule X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 21 Aug 2012 19:51:21 -0000 On 8/21/2012 12:42 PM, Baptiste Daroussin wrote: > On Tue, Aug 21, 2012 at 12:38:04PM -0700, Doug Barton wrote: >> On 8/21/2012 12:05 PM, Baptiste Daroussin wrote: >>> 1/ if it fits the schedule: get rid of pkg_* tools in current >>> to be able to have a fully pkgng only 10-RELEASE >> >> I think it would fit better with historic precedents to make pkg >> optional (but default on) in 10, and mandatory in 11. As stated >> before, I'm fine with removing pkg_* tools from 10 if there is >> robust support for them in the ports tree. >> >> I know you're excited about this project, but let's not lose >> sight of how big a change this is, and how important ports are to >> the project. >> > That was what "if it fits the schedule" was about. I think what I'm trying to say, ever so politely, is that what you're suggesting isn't even an option, so it shouldn't be discussed. -- I am only one, but I am one. I cannot do everything, but I can do something. And I will not let what I cannot do interfere with what I can do. -- Edward Everett Hale, (1822 - 1909) From owner-freebsd-current@FreeBSD.ORG Tue Aug 21 19:56:15 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1C34B106567F for ; Tue, 21 Aug 2012 19:56:15 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from mail-pz0-f54.google.com (mail-pz0-f54.google.com [209.85.210.54]) by mx1.freebsd.org (Postfix) with ESMTP id C52798FC1C for ; Tue, 21 Aug 2012 19:56:14 +0000 (UTC) Received: by dadr6 with SMTP id r6so130939dad.13 for ; Tue, 21 Aug 2012 12:56:14 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=sender:subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer :x-gm-message-state; bh=ASGAishuJChgTSinHinIAIgasSFCqRYqJDZ0tplCWog=; b=p17w8pYAhEXhOP+1CJlw3thvJcpMn0tEHtsHO8VP/9kIVa1oMv8ekEqSrnYkOix3ow 56rpIkTaUcA1ygaOREYxOBWmil3sn24QtXEnnF5Tc4yyTwnyGYcqphzUXNKQy1AxzGpy eAIbR6oyQm8H6WnX13VQXW7H0Zt3+kcAdegKob4sqK8UrQ+4f69hOS8rktZwoTl64W+m 5AGUG4ldT/bfJkAl0T/9J5qVA0hpiYLrvSlBV/WvkgTr3HeZgYicY9+TGxkSHmPZ8TsR sFRDv3MOrc2hyaL5gvT9GsgTwWtNb3T0Mph/7BJ0cYsf/dW2hIoiT9jmlTY5hg/PneCP oJ8g== Received: by 10.68.201.73 with SMTP id jy9mr47529318pbc.124.1345578974312; Tue, 21 Aug 2012 12:56:14 -0700 (PDT) Received: from fusionlt2834a.int.fusionio.com ([216.51.42.66]) by mx.google.com with ESMTPS id ox5sm2031416pbc.75.2012.08.21.12.56.13 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 21 Aug 2012 12:56:13 -0700 (PDT) Sender: Warner Losh Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=koi8-r From: Warner Losh In-Reply-To: <20120821124623.GC88729@zxy.spb.ru> Date: Tue, 21 Aug 2012 13:56:11 -0600 Content-Transfer-Encoding: quoted-printable Message-Id: <9481DE65-1249-4EE1-96E0-222ADD46B2E6@bsdimp.com> References: <20120821095527.GA33206@hell.ukr.net> <67977762.20120821154035@serebryakov.spb.ru> <1243982625.20120821154548@serebryakov.spb.ru> <20120821124623.GC88729@zxy.spb.ru> To: Slawa Olhovchenkov X-Mailer: Apple Mail (2.1084) X-Gm-Message-State: ALoCoQmTUDiLE6gdrd+i+RiLm6Ua98aWLJRJHqs95hIC78FHIdS5VxrD5SvlT25z/C2t9/cvZBdq Cc: Garrett Cooper , Lev Serebryakov , current@freebsd.org, jhb@FreeBSD.org Subject: Re: r239356: does it mean, that synchronous dhcp and dhcplcinet with disabled devd gone? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 21 Aug 2012 19:56:15 -0000 On Aug 21, 2012, at 6:46 AM, Slawa Olhovchenkov wrote: > On Tue, Aug 21, 2012 at 03:45:48PM +0400, Lev Serebryakov wrote: >=20 >> Hello, Lev. >> You wrote 21 =C1=D7=C7=D5=D3=D4=C1 2012 =C7., 15:40:35: >>=20 >> GC>> Try reverting r239356 -- if that works, then please let jhb@ = know. >> LS> I'm confused by this commit, because it seems (from comment = alone), >> LS> that dhclient will not work without devd anymore (with = "synchronous >> LS> dhcp" option in rc.conf). >> LS> Am I right? >> Also, I don't like idea of removing IP address from interface when >> cable is unplugged. It was very disturbing behavior of Windows >> machines for years. I've unplug cable to change switch port for only = a >> second and all connections are broken, even if one second later >> dhcpclient receive SAME lease! I don't like this. FreeBSD was very >> tolerant to unplugging cable for eons, and I (and not only me) like >> it. If I understand this change properly, it is no more the case :( >=20 > Not only cable. > Turn on microwave, lost WiFi connection and lost all open ssh > session (and other network connection). mosh helps. Warner From owner-freebsd-current@FreeBSD.ORG Tue Aug 21 20:02:22 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6B1A5106566C for ; Tue, 21 Aug 2012 20:02:22 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from mail-pz0-f54.google.com (mail-pz0-f54.google.com [209.85.210.54]) by mx1.freebsd.org (Postfix) with ESMTP id 305EE8FC0C for ; Tue, 21 Aug 2012 20:02:21 +0000 (UTC) Received: by dadr6 with SMTP id r6so134673dad.13 for ; Tue, 21 Aug 2012 13:02:21 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=sender:subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer :x-gm-message-state; bh=1YjeEkujr25zpRWHD0kXYSeGn3peUJEtwjhJOwAl08s=; b=Y3OX88AmnN8NX85Flsa3yjM8CgSr9ep6FlCqRl0Uyka4cbeCP5L64b0qJaIEIo9Rio YTIn3PA+LNLGmGFHhKxHkS63/mrpx8HRDOciHEJaJupAKhp0eJh4gOxIj02Zc04QCEiU MNb+tGYMYgC4wtLdegUkqjrzlg8e1wJvxctMrjZxdH2NLNT5neQ5pdCE33bJaAZokM/O HkXlhf/7ZtwNct6ymHg9gq+zlVG/WHi2LMkO7pBKMsQrvZF3o20HdC/ApPp238CYPvxU ON9uLByrZ2l6mMNVS18mu7Oo+9oBIcu9WiwY/Rv9S/DYkbGyez2Z5OIWc3BDJlWnNRMX jgQw== Received: by 10.66.73.69 with SMTP id j5mr40781217pav.8.1345579341524; Tue, 21 Aug 2012 13:02:21 -0700 (PDT) Received: from fusionlt2834a.int.fusionio.com ([216.51.42.66]) by mx.google.com with ESMTPS id st6sm2049038pbc.58.2012.08.21.13.02.19 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 21 Aug 2012 13:02:20 -0700 (PDT) Sender: Warner Losh Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii From: Warner Losh In-Reply-To: <1345570590.27688.367.camel@revolution.hippie.lan> Date: Tue, 21 Aug 2012 14:02:18 -0600 Content-Transfer-Encoding: quoted-printable Message-Id: <7EFE4E90-32A6-4A9D-B760-C13629E2D19B@bsdimp.com> References: <20120821095527.GA33206@hell.ukr.net> <67977762.20120821154035@serebryakov.spb.ru> <1959717636.20120821155308@serebryakov.spb.ru> <201208210934.31484.jhb@freebsd.org> <1049151425.20120821190433@serebryakov.spb.ru> <1345562163.27688.347.camel@revolution.hippie.lan> <709115163.20120821192652@serebryakov.spb.ru> <1345564507.27688.354.camel@revolution.hippie.lan> <1409150425.20120821210152@serebryakov.spb.ru> <1345570590.27688.367.camel@revolution.hippie.lan> To: Ian Lepore X-Mailer: Apple Mail (2.1084) X-Gm-Message-State: ALoCoQmDBeizIBe000r69xO0B5LTpvRBIO3gI8mfl01NMnyFoXyuU9lxxAeq5u2S+8jYX4dVJUKB Cc: lev@freebsd.org, freebsd-current@freebsd.org Subject: Re: r239356: does it mean, that synchronous dhcp and dhcplcinet with disabled devd gone? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 21 Aug 2012 20:02:22 -0000 On Aug 21, 2012, at 11:36 AM, Ian Lepore wrote: > On Tue, 2012-08-21 at 21:01 +0400, Lev Serebryakov wrote: >> IL> The important point is that if you unplug the cable then plug it = into a >> IL> different network, now the right thing will happen -- you will = acquire >> IL> an address on the new network. That's the reason that this = change is an >> IL> important bugfix for a long standing (many many years) bug in = freebsd's >> IL> dhclient. >> No, I'll be without dhclient at all, if I don't use devd :(. And >> absence of devd is completely legal, and should be supported. It is >> perfectly valid and sensible setup for small devices (think: >> MIPS-based routers, which are started to be supported now), where = devd >> could be very costly in both terms of flash size (it is C++ >> application and need C++ runtime!) and memory (only devd event on >> such devices are this cable plugging/unplugging -- so using devd >> doesn't add any value for such setups). >>=20 >=20 > I think it's funny how people have this knee-jerk reaction against C++ > apps. The devd executable is not exactly an example of bloatware: = 374k > statically linked (so it already includes this "C++ runtime" that you > think is large). We routinely deploy embedded systems that use apps > written exclusively in C++, on systems that only have 32 or 64mb of = ram. > We've been doing so since the days when the biggest compact flash card > you could buy was 64mb. C++ isn't the problem. Devd's size wouldn't be any smaller if I'd = written it in pure C. People have sent me patches that move it to pure = C over time. Yet, when written in C, the binaries are the same size = (well, within 10k), and the run-time speed and memory consumption are = comparable. Devd was written with the small, embedded system in mind, = and was always considered to be on the path to being mandatory (you are = free to write your own devd-like program, if you like btw). Haven't looked at the dhclient issues surrounding this tread, but C++ = size and bloat of devd is an argument not supported by the objective = facts. Warner From owner-freebsd-current@FreeBSD.ORG Tue Aug 21 20:04:45 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 13F6A106566C for ; Tue, 21 Aug 2012 20:04:45 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from mail-pb0-f54.google.com (mail-pb0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id CBCC78FC16 for ; Tue, 21 Aug 2012 20:04:44 +0000 (UTC) Received: by pbbrp2 with SMTP id rp2so434615pbb.13 for ; Tue, 21 Aug 2012 13:04:44 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=sender:subject:mime-version:content-type:from:x-priority :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to:x-mailer:x-gm-message-state; bh=KjfMat7a3O9c08Iz302Y+BbLBphnz4EFEAtwHWI7LSA=; b=Uxua+x/AsqizHraT0lzucl14n/4aofDq7EJ0RGLZ9EGinRF7yFYuQnmfi7bFn1vSYJ WAR4WDyjoC9ny0YezAxvvTWGjvXWJk9tCc+13ALaP4F9OgvO5ZRIBpjDITruCtZeTcdd lRPxY1PdYFCX3RDa4uYYy4iWRd5L9jqkm4QXmjGvPy5Mjo5s6Zx+FP4lxrqWfJ94ey+8 AcsQyfe9EI2dOFmYEjv0D0kNiKO1vXqjQsNNPhgZT7DjB3KzqBwWUbrSsRY9MMb0qAri WYuj7nM+B6iu8fS84vss0m+Tph5JKroDYWBYUQMg6tEqaPbSToXWzLEA6n0DWE4xdOpD 9aAg== Received: by 10.66.78.69 with SMTP id z5mr40695003paw.14.1345579484247; Tue, 21 Aug 2012 13:04:44 -0700 (PDT) Received: from fusionlt2834a.int.fusionio.com ([216.51.42.66]) by mx.google.com with ESMTPS id rm9sm2045194pbc.72.2012.08.21.13.04.43 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 21 Aug 2012 13:04:43 -0700 (PDT) Sender: Warner Losh Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=utf-8 From: Warner Losh X-Priority: 3 (Normal) In-Reply-To: <686419050.20120821214225@serebryakov.spb.ru> Date: Tue, 21 Aug 2012 14:04:41 -0600 Content-Transfer-Encoding: quoted-printable Message-Id: References: <20120821095527.GA33206@hell.ukr.net> <67977762.20120821154035@serebryakov.spb.ru> <1959717636.20120821155308@serebryakov.spb.ru> <201208210934.31484.jhb@freebsd.org> <1049151425.20120821190433@serebryakov.spb.ru> <1345562163.27688.347.camel@revolution.hippie.lan> <709115163.20120821192652@serebryakov.spb.ru> <1345564507.27688.354.camel@revolution.hippie.lan> <1409150425.20120821210152@serebryakov.spb.ru> <1345570590.27688.367.camel@revolution.hippie.lan> <686419050.20120821214225@serebryakov.spb.ru> To: lev@FreeBSD.org X-Mailer: Apple Mail (2.1084) X-Gm-Message-State: ALoCoQllWpa73hho6XXuuAx5Zlb7O2hAAXuPBTahuyJNlrxsmeVGpDoaJOkBwRixsph39nTeV7dy Cc: Ian Lepore , freebsd-current@freebsd.org Subject: Re: r239356: does it mean, that synchronous dhcp and dhcplcinet with disabled devd gone? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 21 Aug 2012 20:04:45 -0000 On Aug 21, 2012, at 11:42 AM, Lev Serebryakov wrote: > Hello, Ian. > You wrote 21 =D0=B0=D0=B2=D0=B3=D1=83=D1=81=D1=82=D0=B0 2012 =D0=B3., = 21:36:30: >=20 > IL> I think it's funny how people have this knee-jerk reaction against = C++ > IL> apps. The devd executable is not exactly an example of bloatware: = 374k > IL> statically linked (so it already includes this "C++ runtime" that = you > IL> think is large). We routinely deploy embedded systems that use = apps > IL> written exclusively in C++, on systems that only have 32 or 64mb = of ram. > IL> We've been doing so since the days when the biggest compact flash = card > IL> you could buy was 64mb. > BTW, typical MIPS SoC-based router has only 16MiB of flash. And, > yes, FreeBSD doesn't fit well in this size now, but why add another > mandatory program, only role of which is to monitor network cable and > re-run the same program every time? You'd typically not run dhclient in daemon mode in a SoC, since you = don't want to chew up the memory all the time, and you'd likely replace = the system dhclient with one that's simpler... But the network = notification part of devd would be trivial to reproduce if you wanted in = a specialized daemon that would do what's required. Warner From owner-freebsd-current@FreeBSD.ORG Tue Aug 21 20:08:16 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 274CC1065673 for ; Tue, 21 Aug 2012 20:08:16 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from mail-pb0-f54.google.com (mail-pb0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id E13018FC0C for ; Tue, 21 Aug 2012 20:08:15 +0000 (UTC) Received: by pbbrp2 with SMTP id rp2so438678pbb.13 for ; Tue, 21 Aug 2012 13:08:15 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=sender:subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer :x-gm-message-state; bh=ZyK23vdHTFLbJSeDUxfRotlTQuJOPIJxYkIsooVrJMI=; b=IB0cEJJWcywpJSZ7FkGPH1iwMkmFl/R4IWKCVGVyn46xCUQgPeIsVqRq1lDOzJLWbk TAZO924Ty4K0Qt7gqxiCyQM0KG/Jyh0AnNvpWvRhJOv2fvwgZ+zq1ncTRpt6Vr913R6C IWUgVG/Sc+y+g9/K/1wNvqGqSblXi9ZqWC+l2xQXrJLYGNpjayqYsEDX4yTkM8LHGBuv ep1/8OrGrCPRv7yIvesM8iOKL1XdhUN8Mas6WHsdyA1/qRj0T/B2fCk+eOrpyP2lA5wz xK3Q8eMAtKVIvD0+oc2NYj2r/HTNTSl+qYteuroIDEVxWIQb58UwAe+aOKzaRNXgiPx2 OlDg== Received: by 10.66.76.130 with SMTP id k2mr40676474paw.19.1345579695482; Tue, 21 Aug 2012 13:08:15 -0700 (PDT) Received: from fusionlt2834a.int.fusionio.com ([216.51.42.66]) by mx.google.com with ESMTPS id th6sm2089962pbc.0.2012.08.21.13.08.14 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 21 Aug 2012 13:08:14 -0700 (PDT) Sender: Warner Losh Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii From: Warner Losh In-Reply-To: <5033E6BA.8080309@FreeBSD.org> Date: Tue, 21 Aug 2012 14:08:11 -0600 Content-Transfer-Encoding: quoted-printable Message-Id: References: <20120820194313.GC23607@ithaqua.etoilebsd.net> <20120821132643.GE37262@felucia.tataz.chchile.org> <20120821134623.GH5044@ithaqua.etoilebsd.net> <5033D0C0.4030805@FreeBSD.org> <20120821190500.GA46595@ithaqua.etoilebsd.net> <5033E39C.3060700@FreeBSD.org> <20120821194208.GC46595@ithaqua.etoilebsd.net> <5033E6BA.8080309@FreeBSD.org> To: Doug Barton X-Mailer: Apple Mail (2.1084) X-Gm-Message-State: ALoCoQnNY2i0KUHmauTdqOTfBzlQYBUKkGk3+h25rm1DkVVCxUTa/ZyPoo82MTkTWLUaZWOGExl1 Cc: Garrett Cooper , ports@freebsd.org, Baptiste Daroussin , current@freebsd.org Subject: Re: pkgng 1.0 release schedule, and HEAD switch to pkgng by default schedule X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 21 Aug 2012 20:08:16 -0000 On Aug 21, 2012, at 1:51 PM, Doug Barton wrote: > On 8/21/2012 12:42 PM, Baptiste Daroussin wrote: >> On Tue, Aug 21, 2012 at 12:38:04PM -0700, Doug Barton wrote: >>> On 8/21/2012 12:05 PM, Baptiste Daroussin wrote: >>>> 1/ if it fits the schedule: get rid of pkg_* tools in current >>>> to be able to have a fully pkgng only 10-RELEASE >>>=20 >>> I think it would fit better with historic precedents to make pkg=20 >>> optional (but default on) in 10, and mandatory in 11. As stated=20 >>> before, I'm fine with removing pkg_* tools from 10 if there is >>> robust support for them in the ports tree. >>>=20 >>> I know you're excited about this project, but let's not lose >>> sight of how big a change this is, and how important ports are to >>> the project. >>>=20 >> That was what "if it fits the schedule" was about. >=20 > I think what I'm trying to say, ever so politely, is that what you're > suggesting isn't even an option, so it shouldn't be discussed. If you are fine with removing them if there's robust support, how can = you also be suggesting that it is impossible and shouldn't be talked = about? Personally, I think we should handle this the same way that other = replacement tools have been done, which is close to what Baptiste has = proposed. If the new tools are totally awesome, we have replaced old = tools. If the new tools are good, but don't cover the older users, we = develop along size. If they are lame, but somehow get committed anyway, = we take 18 years to replace them with bsdinstall. Warner From owner-freebsd-current@FreeBSD.ORG Tue Aug 21 20:15:18 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx2.freebsd.org (mx2.freebsd.org [IPv6:2001:4f8:fff6::35]) by hub.freebsd.org (Postfix) with ESMTP id D7F15106564A; Tue, 21 Aug 2012 20:15:18 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from [127.0.0.1] (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id A19E014D8EC; Tue, 21 Aug 2012 20:15:18 +0000 (UTC) Message-ID: <5033EC58.3000801@FreeBSD.org> Date: Tue, 21 Aug 2012 13:15:20 -0700 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:14.0) Gecko/20120713 Thunderbird/14.0 MIME-Version: 1.0 To: Warner Losh References: <20120820194313.GC23607@ithaqua.etoilebsd.net> <20120821132643.GE37262@felucia.tataz.chchile.org> <20120821134623.GH5044@ithaqua.etoilebsd.net> <5033D0C0.4030805@FreeBSD.org> <20120821190500.GA46595@ithaqua.etoilebsd.net> <5033E39C.3060700@FreeBSD.org> <20120821194208.GC46595@ithaqua.etoilebsd.net> <5033E6BA.8080309@FreeBSD.org> In-Reply-To: X-Enigmail-Version: 1.4.3 OpenPGP: id=1A1ABC84 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Garrett Cooper , ports@freebsd.org, Baptiste Daroussin , current@freebsd.org Subject: Re: pkgng 1.0 release schedule, and HEAD switch to pkgng by default schedule X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 21 Aug 2012 20:15:19 -0000 On 8/21/2012 1:08 PM, Warner Losh wrote: > > On Aug 21, 2012, at 1:51 PM, Doug Barton wrote: > >> On 8/21/2012 12:42 PM, Baptiste Daroussin wrote: >>> On Tue, Aug 21, 2012 at 12:38:04PM -0700, Doug Barton wrote: >>>> On 8/21/2012 12:05 PM, Baptiste Daroussin wrote: >>>>> 1/ if it fits the schedule: get rid of pkg_* tools in >>>>> current to be able to have a fully pkgng only 10-RELEASE >>>> >>>> I think it would fit better with historic precedents to make >>>> pkg optional (but default on) in 10, and mandatory in 11. As >>>> stated before, I'm fine with removing pkg_* tools from 10 if >>>> there is robust support for them in the ports tree. >>>> >>>> I know you're excited about this project, but let's not lose >>>> sight of how big a change this is, and how important ports are >>>> to the project. >>>> >>> That was what "if it fits the schedule" was about. >> >> I think what I'm trying to say, ever so politely, is that what >> you're suggesting isn't even an option, so it shouldn't be >> discussed. > > If you are fine with removing them if there's robust support, how can > you also be suggesting that it is impossible and shouldn't be talked > about? Those address different parts of the problem. Making pkg mandatory in 10 is different from where the old pkg_* tools end up. The command line tools are just the tip of the iceberg, there are a lot of interactions behind the scenes. > Personally, I think we should handle this the same way that other > replacement tools have been done, which is close to what Baptiste has > proposed. If the new tools are totally awesome, we have replaced old > tools. I don't think we have ever done a complete replacement of major infrastructure in one release. The traditional model has been to deprecate in one release, remove in the next. And in this case, it doesn't matter how awesome the new tools are, they are a MAJOR paradigm shift for how users interact with ports, and we are going to have a lot of users who take years to transition their installed base. No matter how much we may want to move fast on this, it just isn't going to be possible. > If the new tools are good, but don't cover the older users, > we develop along size. Yes, this is precisely what I'm saying. Sorry if I wasn't clear. -- I am only one, but I am one. I cannot do everything, but I can do something. And I will not let what I cannot do interfere with what I can do. -- Edward Everett Hale, (1822 - 1909) From owner-freebsd-current@FreeBSD.ORG Tue Aug 21 21:00:07 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A3C29106566C for ; Tue, 21 Aug 2012 21:00:07 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from onlyone.friendlyhosting.spb.ru (onlyone.friendlyhosting.spb.ru [46.4.40.135]) by mx1.freebsd.org (Postfix) with ESMTP id 584A28FC08 for ; Tue, 21 Aug 2012 21:00:06 +0000 (UTC) Received: from lion.home.serebryakov.spb.ru (unknown [IPv6:2001:470:923f:1:8870:d54b:33e8:55b2]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.friendlyhosting.spb.ru (Postfix) with ESMTPA id 378994AC2D; Wed, 22 Aug 2012 01:00:05 +0400 (MSK) Date: Wed, 22 Aug 2012 01:00:01 +0400 From: Lev Serebryakov Organization: FreeBSD Project X-Priority: 3 (Normal) Message-ID: <733794380.20120822010001@serebryakov.spb.ru> To: Warner Losh In-Reply-To: <7EFE4E90-32A6-4A9D-B760-C13629E2D19B@bsdimp.com> References: <20120821095527.GA33206@hell.ukr.net> <67977762.20120821154035@serebryakov.spb.ru> <1959717636.20120821155308@serebryakov.spb.ru> <201208210934.31484.jhb@freebsd.org> <1049151425.20120821190433@serebryakov.spb.ru> <1345562163.27688.347.camel@revolution.hippie.lan> <709115163.20120821192652@serebryakov.spb.ru> <1345564507.27688.354.camel@revolution.hippie.lan> <1409150425.20120821210152@serebryakov.spb.ru> <1345570590.27688.367.camel@revolution.hippie.lan> <7EFE4E90-32A6-4A9D-B760-C13629E2D19B@bsdimp.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: Ian Lepore , freebsd-current@freebsd.org Subject: Re: r239356: does it mean, that synchronous dhcp and dhcplcinet with disabled devd gone? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: lev@FreeBSD.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Aug 2012 21:00:07 -0000 Hello, Warner. You wrote 22 =D0=B0=D0=B2=D0=B3=D1=83=D1=81=D1=82=D0=B0 2012 =D0=B3., 0:02:= 18: WL> Haven't looked at the dhclient issues surrounding this tread, but WL> C++ size and bloat of devd is an argument not supported by the objectiv= e facts. Ok, lets leave C++ alone, but intended address removal (See PR comments) is POLA violation and, IMHO, serious issue by itself, even without POLA. --=20 // Black Lion AKA Lev Serebryakov From owner-freebsd-current@FreeBSD.ORG Tue Aug 21 21:01:33 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7D6D5106564A for ; Tue, 21 Aug 2012 21:01:33 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from onlyone.friendlyhosting.spb.ru (onlyone.friendlyhosting.spb.ru [IPv6:2a01:4f8:131:60a2::2]) by mx1.freebsd.org (Postfix) with ESMTP id 0D78B8FC16 for ; Tue, 21 Aug 2012 21:01:33 +0000 (UTC) Received: from lion.home.serebryakov.spb.ru (unknown [IPv6:2001:470:923f:1:8870:d54b:33e8:55b2]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.friendlyhosting.spb.ru (Postfix) with ESMTPA id 6A7134AC2D; Wed, 22 Aug 2012 01:01:31 +0400 (MSK) Date: Wed, 22 Aug 2012 01:01:28 +0400 From: Lev Serebryakov Organization: FreeBSD Project X-Priority: 3 (Normal) Message-ID: <1328222662.20120822010128@serebryakov.spb.ru> To: Warner Losh In-Reply-To: References: <20120821095527.GA33206@hell.ukr.net> <67977762.20120821154035@serebryakov.spb.ru> <1959717636.20120821155308@serebryakov.spb.ru> <201208210934.31484.jhb@freebsd.org> <1049151425.20120821190433@serebryakov.spb.ru> <1345562163.27688.347.camel@revolution.hippie.lan> <709115163.20120821192652@serebryakov.spb.ru> <1345564507.27688.354.camel@revolution.hippie.lan> <1409150425.20120821210152@serebryakov.spb.ru> <1345570590.27688.367.camel@revolution.hippie.lan> <686419050.20120821214225@serebryakov.spb.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: Ian Lepore , freebsd-current@freebsd.org Subject: Re: r239356: does it mean, that synchronous dhcp and dhcplcinet with disabled devd gone? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: lev@FreeBSD.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Aug 2012 21:01:33 -0000 Hello, Warner. You wrote 22 =D0=B0=D0=B2=D0=B3=D1=83=D1=81=D1=82=D0=B0 2012 =D0=B3., 0:04:= 41: >> BTW, typical MIPS SoC-based router has only 16MiB of flash. And, >> yes, FreeBSD doesn't fit well in this size now, but why add another >> mandatory program, only role of which is to monitor network cable and >> re-run the same program every time? WL> You'd typically not run dhclient in daemon mode in a SoC, since WL> you don't want to chew up the memory all the time, and you'd WL> likely replace the system dhclient with one that's simpler... But My ISP wants lease renewal every 10800 second (3 hours). Do I need to add cron task if I don't want to run dhclient as a daemon on router? WL> the network notification part of devd would be trivial to WL> reproduce if you wanted in a specialized daemon that would do what's re= quired. IMHO, OpenBSD way, when dhclient renew lease after down/up cycle by itself, is much better. --=20 // Black Lion AKA Lev Serebryakov From owner-freebsd-current@FreeBSD.ORG Tue Aug 21 21:04:28 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B72091065670; Tue, 21 Aug 2012 21:04:28 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from onlyone.friendlyhosting.spb.ru (onlyone.friendlyhosting.spb.ru [46.4.40.135]) by mx1.freebsd.org (Postfix) with ESMTP id 6EE1A8FC20; Tue, 21 Aug 2012 21:04:28 +0000 (UTC) Received: from lion.home.serebryakov.spb.ru (unknown [IPv6:2001:470:923f:1:8870:d54b:33e8:55b2]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.friendlyhosting.spb.ru (Postfix) with ESMTPA id 21A024AC33; Wed, 22 Aug 2012 01:04:27 +0400 (MSK) Date: Wed, 22 Aug 2012 01:04:23 +0400 From: Lev Serebryakov Organization: FreeBSD X-Priority: 3 (Normal) Message-ID: <1481927429.20120822010423@serebryakov.spb.ru> To: Warner Losh In-Reply-To: <9481DE65-1249-4EE1-96E0-222ADD46B2E6@bsdimp.com> References: <20120821095527.GA33206@hell.ukr.net> <67977762.20120821154035@serebryakov.spb.ru> <1243982625.20120821154548@serebryakov.spb.ru> <20120821124623.GC88729@zxy.spb.ru> <9481DE65-1249-4EE1-96E0-222ADD46B2E6@bsdimp.com> MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: quoted-printable Cc: Garrett Cooper , current@freebsd.org, jhb@FreeBSD.org, Slawa Olhovchenkov Subject: Re: r239356: does it mean, that synchronous dhcp and dhcplcinet with disabled devd gone? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: lev@FreeBSD.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Aug 2012 21:04:28 -0000 Hello, Warner. You wrote 21 =C1=D7=C7=D5=D3=D4=C1 2012 =C7., 23:56:11: WL> mosh helps. And what helps in case of on-line backup? Not every network protocol and protocol implementation, unfortunately, supports automatic resume :( --=20 // Black Lion AKA Lev Serebryakov From owner-freebsd-current@FreeBSD.ORG Tue Aug 21 21:27:26 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EE90310656B0; Tue, 21 Aug 2012 21:27:25 +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 94B8C8FC12; Tue, 21 Aug 2012 21:27:25 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id DFE63B91E; Tue, 21 Aug 2012 17:27:24 -0400 (EDT) From: John Baldwin To: freebsd-current@freebsd.org Date: Tue, 21 Aug 2012 17:25:23 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110714-p17; KDE/4.5.5; amd64; ; ) References: <20120821095527.GA33206@hell.ukr.net> <1959717636.20120821155308@serebryakov.spb.ru> <201208210934.31484.jhb@freebsd.org> In-Reply-To: <201208210934.31484.jhb@freebsd.org> MIME-Version: 1.0 Content-Type: Text/Plain; charset="windows-1251" Content-Transfer-Encoding: quoted-printable Message-Id: <201208211725.23381.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Tue, 21 Aug 2012 17:27:25 -0400 (EDT) Cc: Garrett Cooper , lev@freebsd.org, current@freebsd.org, Peter Jeremy Subject: Re: r239356: does it mean, that synchronous dhcp and dhcplcinet with disabled devd gone? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 21 Aug 2012 21:27:26 -0000 On Tuesday, August 21, 2012 9:34:31 am John Baldwin wrote: > On Tuesday, August 21, 2012 7:53:08 am Lev Serebryakov wrote: > > Hello, Garrett. > > You wrote 21 =E0=E2=E3=F3=F1=F2=E0 2012 =E3., 15:40:35: > >=20 > > GC>> Try reverting r239356 -- if that works, then please let jhb@ know. > > LS> I'm confused by this commit, because it seems (from comment alon= e), > > LS> that dhclient will not work without devd anymore (with "synchrono= us > > LS> dhcp" option in rc.conf). > > LS> Am I right? > > And if I'm right about understanding what this change does, it is > > POLA violation for sure. Both consequences: unable to use dhcclient > > without devd (user will need to restart it by hands after each cable > > unplugging event) and removing IP address from interface on cable > > unplugging or other interface down event but before lease is expired. > >=20 > > If I'm right in understanding this commit, I vote to back it out and > > find better solution, may be, two new options: one to remove IP and > > one to exit on interface down. And default behavior should be OLD > > ONE about IP address in any case and OLD ONE about exit in case when > > dhclient isn't started by devd, but by rc scripts directly. >=20 > Humm. devd is the more common case, and we explicitly don't use devd to = start=20 > dhclient on boot even when devd is enabled (so out of the box dhcp would = first=20 > be started by rc, but would be restarted by devd). >=20 > Another option is to rework dhclient to work like it does on OpenBSD wher= e it > renews its lease if the link bounces, but to not exit when the link goes = down. =20 > That case would fix the currently broken case that you unplug your cable,= take=20 > your laptop over to another network (e.g. take it home if suspend/resume= =20 > works), then plug it back in and are still stuck with your old IP. Ok, this is what I came up with, somewhat loosely based on OpenBSD's dhclie= nt. I tested that it survives the following: =2D Unplugging/replugging does not kill an existing ssh session =2D Using ifconfig down/up does not kill an existing ssh session =2D Plugging into a different network does cause dhclient to negotiate a new lease on the new network I've removed the bits to clear the old configuration if dhclient exits due = to 'ifconfig down', and dhclient no longer exits on link down, but instead tra= cks the link state and enters the 'reboot' state when the link goes up. Index: dhcpd.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 =2D-- dhcpd.h (revision 239498) +++ dhcpd.h (working copy) @@ -208,6 +208,7 @@ int errors; int dead; u_int16_t index; + int linkstat; }; =20 struct timeout { Index: dhclient.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 =2D-- dhclient.c (revision 239498) +++ dhclient.c (working copy) @@ -218,6 +218,7 @@ struct sockaddr *sa; struct iaddr a; ssize_t n; + int linkstat; =20 n =3D read(routefd, &msg, sizeof(msg)); rtm =3D (struct rt_msghdr *)msg; @@ -278,10 +279,14 @@ ifi->name); goto die; } =2D if (!interface_link_status(ifi->name)) { =2D warning("Interface %s is down, dhclient exiting", =2D ifi->name); =2D goto die; + linkstat =3D interface_link_status(ifi->name); + if (linkstat !=3D ifi->linkstat) { + debug("%s link state %s -> %s", ifi->name, + ifi->linkstat ? "up" : "down", + linkstat ? "up" : "down"); + ifi->linkstat =3D linkstat; + if (linkstat) + state_reboot(ifi); } break; case RTM_IFANNOUNCE: @@ -321,8 +326,6 @@ =20 die: script_init("FAIL", NULL); =2D if (ifi->client->active) =2D script_write_params("old_", ifi->client->active); if (ifi->client->alias) script_write_params("alias_", ifi->client->alias); script_go(); @@ -437,6 +440,7 @@ } fprintf(stderr, " got link\n"); } + ifi->linkstat =3D 1; =20 if ((nullfd =3D open(_PATH_DEVNULL, O_RDWR, 0)) =3D=3D -1) error("cannot open %s: %m", _PATH_DEVNULL); =2D-=20 John Baldwin From owner-freebsd-current@FreeBSD.ORG Tue Aug 21 21:27:26 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EE90310656B0; Tue, 21 Aug 2012 21:27:25 +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 94B8C8FC12; Tue, 21 Aug 2012 21:27:25 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id DFE63B91E; Tue, 21 Aug 2012 17:27:24 -0400 (EDT) From: John Baldwin To: freebsd-current@freebsd.org Date: Tue, 21 Aug 2012 17:25:23 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110714-p17; KDE/4.5.5; amd64; ; ) References: <20120821095527.GA33206@hell.ukr.net> <1959717636.20120821155308@serebryakov.spb.ru> <201208210934.31484.jhb@freebsd.org> In-Reply-To: <201208210934.31484.jhb@freebsd.org> MIME-Version: 1.0 Content-Type: Text/Plain; charset="windows-1251" Content-Transfer-Encoding: quoted-printable Message-Id: <201208211725.23381.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Tue, 21 Aug 2012 17:27:25 -0400 (EDT) Cc: Garrett Cooper , lev@freebsd.org, current@freebsd.org, Peter Jeremy Subject: Re: r239356: does it mean, that synchronous dhcp and dhcplcinet with disabled devd gone? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 21 Aug 2012 21:27:26 -0000 On Tuesday, August 21, 2012 9:34:31 am John Baldwin wrote: > On Tuesday, August 21, 2012 7:53:08 am Lev Serebryakov wrote: > > Hello, Garrett. > > You wrote 21 =E0=E2=E3=F3=F1=F2=E0 2012 =E3., 15:40:35: > >=20 > > GC>> Try reverting r239356 -- if that works, then please let jhb@ know. > > LS> I'm confused by this commit, because it seems (from comment alon= e), > > LS> that dhclient will not work without devd anymore (with "synchrono= us > > LS> dhcp" option in rc.conf). > > LS> Am I right? > > And if I'm right about understanding what this change does, it is > > POLA violation for sure. Both consequences: unable to use dhcclient > > without devd (user will need to restart it by hands after each cable > > unplugging event) and removing IP address from interface on cable > > unplugging or other interface down event but before lease is expired. > >=20 > > If I'm right in understanding this commit, I vote to back it out and > > find better solution, may be, two new options: one to remove IP and > > one to exit on interface down. And default behavior should be OLD > > ONE about IP address in any case and OLD ONE about exit in case when > > dhclient isn't started by devd, but by rc scripts directly. >=20 > Humm. devd is the more common case, and we explicitly don't use devd to = start=20 > dhclient on boot even when devd is enabled (so out of the box dhcp would = first=20 > be started by rc, but would be restarted by devd). >=20 > Another option is to rework dhclient to work like it does on OpenBSD wher= e it > renews its lease if the link bounces, but to not exit when the link goes = down. =20 > That case would fix the currently broken case that you unplug your cable,= take=20 > your laptop over to another network (e.g. take it home if suspend/resume= =20 > works), then plug it back in and are still stuck with your old IP. Ok, this is what I came up with, somewhat loosely based on OpenBSD's dhclie= nt. I tested that it survives the following: =2D Unplugging/replugging does not kill an existing ssh session =2D Using ifconfig down/up does not kill an existing ssh session =2D Plugging into a different network does cause dhclient to negotiate a new lease on the new network I've removed the bits to clear the old configuration if dhclient exits due = to 'ifconfig down', and dhclient no longer exits on link down, but instead tra= cks the link state and enters the 'reboot' state when the link goes up. Index: dhcpd.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 =2D-- dhcpd.h (revision 239498) +++ dhcpd.h (working copy) @@ -208,6 +208,7 @@ int errors; int dead; u_int16_t index; + int linkstat; }; =20 struct timeout { Index: dhclient.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 =2D-- dhclient.c (revision 239498) +++ dhclient.c (working copy) @@ -218,6 +218,7 @@ struct sockaddr *sa; struct iaddr a; ssize_t n; + int linkstat; =20 n =3D read(routefd, &msg, sizeof(msg)); rtm =3D (struct rt_msghdr *)msg; @@ -278,10 +279,14 @@ ifi->name); goto die; } =2D if (!interface_link_status(ifi->name)) { =2D warning("Interface %s is down, dhclient exiting", =2D ifi->name); =2D goto die; + linkstat =3D interface_link_status(ifi->name); + if (linkstat !=3D ifi->linkstat) { + debug("%s link state %s -> %s", ifi->name, + ifi->linkstat ? "up" : "down", + linkstat ? "up" : "down"); + ifi->linkstat =3D linkstat; + if (linkstat) + state_reboot(ifi); } break; case RTM_IFANNOUNCE: @@ -321,8 +326,6 @@ =20 die: script_init("FAIL", NULL); =2D if (ifi->client->active) =2D script_write_params("old_", ifi->client->active); if (ifi->client->alias) script_write_params("alias_", ifi->client->alias); script_go(); @@ -437,6 +440,7 @@ } fprintf(stderr, " got link\n"); } + ifi->linkstat =3D 1; =20 if ((nullfd =3D open(_PATH_DEVNULL, O_RDWR, 0)) =3D=3D -1) error("cannot open %s: %m", _PATH_DEVNULL); =2D-=20 John Baldwin From owner-freebsd-current@FreeBSD.ORG Tue Aug 21 21:35:18 2012 Return-Path: Delivered-To: current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 04F68106564A; Tue, 21 Aug 2012 21:35:18 +0000 (UTC) (envelope-from flo@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id C0D738FC12; Tue, 21 Aug 2012 21:35:17 +0000 (UTC) Received: from nibbler-osx-wlan.fritz.box (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q7LLZF2N063901; Tue, 21 Aug 2012 21:35:15 GMT (envelope-from flo@FreeBSD.org) Message-ID: <5033FF13.2090003@FreeBSD.org> Date: Tue, 21 Aug 2012 23:35:15 +0200 From: Florian Smeets User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:15.0) Gecko/20120815 Thunderbird/15.0 MIME-Version: 1.0 To: Doug Barton References: <157941699.20120815004542@serebryakov.spb.ru> <502AE8B5.9090106@FreeBSD.org> <502B775D.7000101@FreeBSD.org> <5031F636.1020405@FreeBSD.org> In-Reply-To: <5031F636.1020405@FreeBSD.org> X-Enigmail-Version: 1.5a1pre Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigA13AA7BCE4240602815D84F4" Cc: Alexander Motin , lev@FreeBSD.org, Adrian Chadd , current@FreeBSD.org Subject: Re: CURRENT as gateway on not-so-fast hardware: where is a bottlneck? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 21 Aug 2012 21:35:18 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigA13AA7BCE4240602815D84F4 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On 20.08.12 10:32, Doug Barton wrote: > On 08/15/2012 03:18, Alexander Motin wrote: >> >> It is quite pointless to speculate without real info like mentioned >> above KTR_SCHED traces. >=20 > I'm sorry, you're quite wrong about that. In the cases I mentioned, and= > in about 2 out of 3 of the cases where users reported problems and I > suggested that they try 4BSD, the results were clear. This obviously > points out that there is a serious problem with ULE, and if I were the > one who was responsible for that code I would be looking at ways of > helping users figure out where the problems are. But that's just me. >=20 >> Main thing I've learned about schedulers, things >> there never work as you expect. There are two many factors are relatio= ns >> to predict behavior in every case. >=20 > In the web hosting case that I mentioned, I purposely kept every other > factor consistent; and changed only s/ULE/4BSD/. The results were both > clear and consistent. >=20 Can you please prove that with some actual numbers? I seem to recall you posted something not too long ago but i was unable to find that right now= =2E Also can you tell us what you ran and how. I would really like to reproduce this. Thanks, Florian --------------enigA13AA7BCE4240602815D84F4 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iEYEARECAAYFAlAz/xQACgkQapo8P8lCvwmabACgr2kUZ62RJnd8pDTu9hHis8QQ or0An3BkPQSuH6OAHuEfD+IzHw/xN4Sp =mEa1 -----END PGP SIGNATURE----- --------------enigA13AA7BCE4240602815D84F4-- From owner-freebsd-current@FreeBSD.ORG Tue Aug 21 21:38:13 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 812E81065672 for ; Tue, 21 Aug 2012 21:38:13 +0000 (UTC) (envelope-from freebsd@damnhippie.dyndns.org) Received: from qmta06.emeryville.ca.mail.comcast.net (qmta06.emeryville.ca.mail.comcast.net [76.96.30.56]) by mx1.freebsd.org (Postfix) with ESMTP id 581E58FC0C for ; Tue, 21 Aug 2012 21:38:13 +0000 (UTC) Received: from omta15.emeryville.ca.mail.comcast.net ([76.96.30.71]) by qmta06.emeryville.ca.mail.comcast.net with comcast id pZMh1j0051Y3wxoA6Ze7Js; Tue, 21 Aug 2012 21:38:07 +0000 Received: from damnhippie.dyndns.org ([24.8.232.202]) by omta15.emeryville.ca.mail.comcast.net with comcast id pZe61j0024NgCEG8bZe6j9; Tue, 21 Aug 2012 21:38:07 +0000 Received: from [172.22.42.240] (revolution.hippie.lan [172.22.42.240]) by damnhippie.dyndns.org (8.14.3/8.14.3) with ESMTP id q7LLc4xG022878; Tue, 21 Aug 2012 15:38:04 -0600 (MDT) (envelope-from freebsd@damnhippie.dyndns.org) From: Ian Lepore To: Warner Losh In-Reply-To: References: <20120821095527.GA33206@hell.ukr.net> <67977762.20120821154035@serebryakov.spb.ru> <1959717636.20120821155308@serebryakov.spb.ru> <201208210934.31484.jhb@freebsd.org> <1049151425.20120821190433@serebryakov.spb.ru> <1345562163.27688.347.camel@revolution.hippie.lan> <709115163.20120821192652@serebryakov.spb.ru> <1345564507.27688.354.camel@revolution.hippie.lan> <1409150425.20120821210152@serebryakov.spb.ru> <1345570590.27688.367.camel@revolution.hippie.lan> <686419050.20120821214225@serebryakov.spb.ru> Content-Type: text/plain; charset="koi8-r" Date: Tue, 21 Aug 2012 15:38:04 -0600 Message-ID: <1345585084.27688.377.camel@revolution.hippie.lan> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 8bit Cc: lev@freebsd.org, freebsd-current@freebsd.org Subject: Re: r239356: does it mean, that synchronous dhcp and dhcplcinet with disabled devd gone? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 21 Aug 2012 21:38:13 -0000 On Tue, 2012-08-21 at 14:04 -0600, Warner Losh wrote: > On Aug 21, 2012, at 11:42 AM, Lev Serebryakov wrote: > > > Hello, Ian. > > You wrote 21 Á×ÇÕÓÔÁ 2012 Ç., 21:36:30: > > > > IL> I think it's funny how people have this knee-jerk reaction against C++ > > IL> apps. The devd executable is not exactly an example of bloatware: 374k > > IL> statically linked (so it already includes this "C++ runtime" that you > > IL> think is large). We routinely deploy embedded systems that use apps > > IL> written exclusively in C++, on systems that only have 32 or 64mb of ram. > > IL> We've been doing so since the days when the biggest compact flash card > > IL> you could buy was 64mb. > > BTW, typical MIPS SoC-based router has only 16MiB of flash. And, > > yes, FreeBSD doesn't fit well in this size now, but why add another > > mandatory program, only role of which is to monitor network cable and > > re-run the same program every time? > > You'd typically not run dhclient in daemon mode in a SoC, since you don't want to chew up the memory all the time, and you'd likely replace the system dhclient with one that's simpler... But the network notification part of devd would be trivial to reproduce if you wanted in a specialized daemon that would do what's required. > > Warner > For example, this script can replace devd as a daemon that restarts dhclient when any link comes back up... #!/bin/sh daemon_loop () { while true; do read line if [ -z "${line##!system=IFNET subsystem=* type=LINK_UP}" ] ; then eval ${line##!} /sbin/dhclient $subsystem fi done } cat /dev/devctl | daemon_loop Of course the right thing to do is invoke the proper rc scripts rather than dhclient directly... this is just to illustrate how easy it is to replace devd if your needs are specialized. -- Ian From owner-freebsd-current@FreeBSD.ORG Tue Aug 21 21:43:15 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 07078106564A; Tue, 21 Aug 2012 21:43:15 +0000 (UTC) (envelope-from yanegomi@gmail.com) Received: from mail-gg0-f182.google.com (mail-gg0-f182.google.com [209.85.161.182]) by mx1.freebsd.org (Postfix) with ESMTP id 769028FC08; Tue, 21 Aug 2012 21:43:14 +0000 (UTC) Received: by ggnk4 with SMTP id k4so336888ggn.13 for ; Tue, 21 Aug 2012 14:43:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=9FJtyoT8dYcmbEbjJqdfSwEaw/GtdROAO1HIGoIiCdA=; b=blypZvbF7AuogIFLrQtD3MMh8fwj3Nv/YGd0SzvBIGPAd8tUfDZuXKOJen19FLGAfN UfLGZ28oYr7O+3SChfHAWJX90kio3ZOxriDs9Tf4EQNwlZZ30WakCwVr3oM9s/uRAzNP riOO/q8hjGzrvrSRFS0LeuTE97QgD1ptB8Y3p33neQIW8F6DdmzgHJ6femrx8aW4QVA5 zP1b+yygxuryL2pXlEvSY9qYjb4VLLXne2WTYm+wiMpGRaM5BpBWo75KxzoZ8SFKEMoO sVP4o07AcQE5lW6mT9Vk87VGFhj/KuNas5c5tQ89Ap5ceRA6TvTPGIL2nhOlIII8JG7A AaAg== MIME-Version: 1.0 Received: by 10.60.2.134 with SMTP id 6mr14004052oeu.62.1345585393368; Tue, 21 Aug 2012 14:43:13 -0700 (PDT) Received: by 10.76.142.201 with HTTP; Tue, 21 Aug 2012 14:43:13 -0700 (PDT) In-Reply-To: <5033EC58.3000801@FreeBSD.org> References: <20120820194313.GC23607@ithaqua.etoilebsd.net> <20120821132643.GE37262@felucia.tataz.chchile.org> <20120821134623.GH5044@ithaqua.etoilebsd.net> <5033D0C0.4030805@FreeBSD.org> <20120821190500.GA46595@ithaqua.etoilebsd.net> <5033E39C.3060700@FreeBSD.org> <20120821194208.GC46595@ithaqua.etoilebsd.net> <5033E6BA.8080309@FreeBSD.org> <5033EC58.3000801@FreeBSD.org> Date: Tue, 21 Aug 2012 14:43:13 -0700 Message-ID: From: Garrett Cooper To: Doug Barton Content-Type: text/plain; charset=ISO-8859-1 Cc: ports@freebsd.org, Baptiste Daroussin , current@freebsd.org, Warner Losh Subject: Re: pkgng 1.0 release schedule, and HEAD switch to pkgng by default schedule X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 21 Aug 2012 21:43:15 -0000 On Tue, Aug 21, 2012 at 1:15 PM, Doug Barton wrote: > On 8/21/2012 1:08 PM, Warner Losh wrote: >> >> On Aug 21, 2012, at 1:51 PM, Doug Barton wrote: >> >>> On 8/21/2012 12:42 PM, Baptiste Daroussin wrote: >>>> On Tue, Aug 21, 2012 at 12:38:04PM -0700, Doug Barton wrote: >>>>> On 8/21/2012 12:05 PM, Baptiste Daroussin wrote: >>>>>> 1/ if it fits the schedule: get rid of pkg_* tools in >>>>>> current to be able to have a fully pkgng only 10-RELEASE >>>>> >>>>> I think it would fit better with historic precedents to make >>>>> pkg optional (but default on) in 10, and mandatory in 11. As >>>>> stated before, I'm fine with removing pkg_* tools from 10 if >>>>> there is robust support for them in the ports tree. >>>>> >>>>> I know you're excited about this project, but let's not lose >>>>> sight of how big a change this is, and how important ports are >>>>> to the project. >>>>> >>>> That was what "if it fits the schedule" was about. >>> >>> I think what I'm trying to say, ever so politely, is that what >>> you're suggesting isn't even an option, so it shouldn't be >>> discussed. >> >> If you are fine with removing them if there's robust support, how can >> you also be suggesting that it is impossible and shouldn't be talked >> about? > > Those address different parts of the problem. Making pkg mandatory in 10 > is different from where the old pkg_* tools end up. The command line > tools are just the tip of the iceberg, there are a lot of interactions > behind the scenes. > >> Personally, I think we should handle this the same way that other >> replacement tools have been done, which is close to what Baptiste has >> proposed. If the new tools are totally awesome, we have replaced old >> tools. > > I don't think we have ever done a complete replacement of major > infrastructure in one release. The traditional model has been to > deprecate in one release, remove in the next. > > And in this case, it doesn't matter how awesome the new tools are, they > are a MAJOR paradigm shift for how users interact with ports, and we are > going to have a lot of users who take years to transition their > installed base. No matter how much we may want to move fast on this, it > just isn't going to be possible. What Doug mentioned (and I don't think was really considered, but is valid) would break people that use pkg_* outside of ports. I know of at least two instances where this would be the case (one case that uses pkg_* directly, and another case that uses libpkg from pkg_* 0-o...). I know it's delaying the inevitable (pkg_* is going to go away), but we shouldn't count our chickens before they've hatched as far as how pkgng needs to be used and how things might change. The optional in 8/9/10, mandatory in 11 proposal seems very sane and it allows people to get things worked out properly without too many headaches. Thanks! -Garrett From owner-freebsd-current@FreeBSD.ORG Tue Aug 21 22:13:21 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 410081065674; Tue, 21 Aug 2012 22:13:21 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) by mx1.freebsd.org (Postfix) with ESMTP id E519A8FC0A; Tue, 21 Aug 2012 22:13:20 +0000 (UTC) Received: from slw by zxy.spb.ru with local (Exim 4.69 (FreeBSD)) (envelope-from ) id 1T3wjf-0000si-R0; Wed, 22 Aug 2012 02:15:43 +0400 Date: Wed, 22 Aug 2012 02:15:43 +0400 From: Slawa Olhovchenkov To: Warner Losh Message-ID: <20120821221543.GV98910@zxy.spb.ru> References: <20120821095527.GA33206@hell.ukr.net> <67977762.20120821154035@serebryakov.spb.ru> <1243982625.20120821154548@serebryakov.spb.ru> <20120821124623.GC88729@zxy.spb.ru> <9481DE65-1249-4EE1-96E0-222ADD46B2E6@bsdimp.com> MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <9481DE65-1249-4EE1-96E0-222ADD46B2E6@bsdimp.com> User-Agent: Mutt/1.5.21 (2010-09-15) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false Cc: Garrett Cooper , Lev Serebryakov , current@freebsd.org, jhb@FreeBSD.org Subject: Re: r239356: does it mean, that synchronous dhcp and dhcplcinet with disabled devd gone? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 21 Aug 2012 22:13:21 -0000 On Tue, Aug 21, 2012 at 01:56:11PM -0600, Warner Losh wrote: > > On Aug 21, 2012, at 6:46 AM, Slawa Olhovchenkov wrote: > > > On Tue, Aug 21, 2012 at 03:45:48PM +0400, Lev Serebryakov wrote: > > > >> Hello, Lev. > >> You wrote 21 Á×ÇÕÓÔÁ 2012 Ç., 15:40:35: > >> > >> GC>> Try reverting r239356 -- if that works, then please let jhb@ know. > >> LS> I'm confused by this commit, because it seems (from comment alone), > >> LS> that dhclient will not work without devd anymore (with "synchronous > >> LS> dhcp" option in rc.conf). > >> LS> Am I right? > >> Also, I don't like idea of removing IP address from interface when > >> cable is unplugged. It was very disturbing behavior of Windows > >> machines for years. I've unplug cable to change switch port for only a > >> second and all connections are broken, even if one second later > >> dhcpclient receive SAME lease! I don't like this. FreeBSD was very > >> tolerant to unplugging cable for eons, and I (and not only me) like > >> it. If I understand this change properly, it is no more the case :( > > > > Not only cable. > > Turn on microwave, lost WiFi connection and lost all open ssh > > session (and other network connection). > > mosh helps. No. Not all remote host allow to install mosh. Cisco routers, for example, don't allow to install mosh. From owner-freebsd-current@FreeBSD.ORG Tue Aug 21 22:27:15 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E4790106566C for ; Tue, 21 Aug 2012 22:27:15 +0000 (UTC) (envelope-from peter@rulingia.com) Received: from vps.rulingia.com (host-122-100-2-194.octopus.com.au [122.100.2.194]) by mx1.freebsd.org (Postfix) with ESMTP id 5AD008FC12 for ; Tue, 21 Aug 2012 22:27:14 +0000 (UTC) Received: from server.rulingia.com (c220-239-249-137.belrs5.nsw.optusnet.com.au [220.239.249.137]) by vps.rulingia.com (8.14.5/8.14.5) with ESMTP id q7LMR7Re085177 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 22 Aug 2012 08:27:08 +1000 (EST) (envelope-from peter@rulingia.com) X-Bogosity: Ham, spamicity=0.000000 Received: from server.rulingia.com (localhost.rulingia.com [127.0.0.1]) by server.rulingia.com (8.14.5/8.14.5) with ESMTP id q7LMR2Q5094860 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 22 Aug 2012 08:27:02 +1000 (EST) (envelope-from peter@server.rulingia.com) Received: (from peter@localhost) by server.rulingia.com (8.14.5/8.14.5/Submit) id q7LMR1mj094859; Wed, 22 Aug 2012 08:27:01 +1000 (EST) (envelope-from peter) Date: Wed, 22 Aug 2012 08:27:01 +1000 From: Peter Jeremy To: Vitalij Satanivskij Message-ID: <20120821222701.GA94197@server.rulingia.com> References: <20120821095527.GA33206@hell.ukr.net> <20120821164217.GA45780@hell.ukr.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="17pEHd4RhPHOinZp" Content-Disposition: inline In-Reply-To: <20120821164217.GA45780@hell.ukr.net> X-PGP-Key: http://www.rulingia.com/keys/peter.pgp User-Agent: Mutt/1.5.21 (2010-09-15) Cc: current@freebsd.org Subject: Re: dhclient cause up/down cycle after 239356 ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 21 Aug 2012 22:27:16 -0000 --17pEHd4RhPHOinZp Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2012-Aug-21 19:42:17 +0300, Vitalij Satanivskij wrote: >Look's like dhclient do down/up sequence - Not intentionally. >Aug 21 19:21:00 home kernel: fxp0: link state changed to UP >Aug 21 19:21:01 home kernel: fxp0: link state changed to DOWN >Aug 21 19:21:01 home dhclient: New IP Address (fxp0): xx.xx.xx.xx >Aug 21 19:21:01 home dhclient: New Subnet Mask (fxp0): 255.255.255.0 >Aug 21 19:21:01 home dhclient: New Broadcast Address (fxp0): xx.xx.xx.xx >Aug 21 19:21:01 home dhclient: New Routers (fxp0): xx.xx.xx.xx >Aug 21 19:21:03 home kernel: fxp0: link state changed to UP I can reproduce this behaviour - but only on fxp (i82559 in my case) NICs. My bge (BCM5750) and rl (RTL8139) NICs do not report the spurious DOWN/UP. (I don't normally run DHCP on any fxp interfaces, so I didn't see it during my testing). The problem appears to be the=20 $IFCONFIG $interface inet alias 0.0.0.0 netmask 255.0.0.0 broadcast 255.2= 55.255.255 up executed by /sbin/dhclient-script during PREINIT. This is making the fxp NIC reset the link (actually, assigning _any_ IP address to an fxp NIC causes it to reset the link). The post r239356 dhclient detects the link going down and exits. >Before r239356 iface just doing down/up without dhclient exit and >everything work fine. For you, anyway. Failing to detect link down causes problems for me because my dhclient was not seeing my cable-modem resets and therefore failing to reacquire a DHCP lease. --=20 Peter Jeremy --17pEHd4RhPHOinZp Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEARECAAYFAlA0CzUACgkQ/opHv/APuIfPiwCgsdSK2xDSpxG3e2WV3OqzDwcl 3+0AoLO+E0TNyH24OjfUz2Pm2hmZIIh1 =4TdU -----END PGP SIGNATURE----- --17pEHd4RhPHOinZp-- From owner-freebsd-current@FreeBSD.ORG Tue Aug 21 22:36:29 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 775C91065675 for ; Tue, 21 Aug 2012 22:36:29 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from onlyone.friendlyhosting.spb.ru (onlyone.friendlyhosting.spb.ru [46.4.40.135]) by mx1.freebsd.org (Postfix) with ESMTP id 2B5EE8FC1B for ; Tue, 21 Aug 2012 22:36:28 +0000 (UTC) Received: from lion.home.serebryakov.spb.ru (unknown [IPv6:2001:470:923f:1:8870:d54b:33e8:55b2]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.friendlyhosting.spb.ru (Postfix) with ESMTPA id C0B984AC2D; Wed, 22 Aug 2012 02:36:26 +0400 (MSK) Date: Wed, 22 Aug 2012 02:36:23 +0400 From: Lev Serebryakov Organization: FreeBSD Project X-Priority: 3 (Normal) Message-ID: <1844966139.20120822023623@serebryakov.spb.ru> To: Ian Lepore In-Reply-To: <1345585084.27688.377.camel@revolution.hippie.lan> References: <20120821095527.GA33206@hell.ukr.net> <67977762.20120821154035@serebryakov.spb.ru> <1959717636.20120821155308@serebryakov.spb.ru> <201208210934.31484.jhb@freebsd.org> <1049151425.20120821190433@serebryakov.spb.ru> <1345562163.27688.347.camel@revolution.hippie.lan> <709115163.20120821192652@serebryakov.spb.ru> <1345564507.27688.354.camel@revolution.hippie.lan> <1409150425.20120821210152@serebryakov.spb.ru> <1345570590.27688.367.camel@revolution.hippie.lan> <686419050.20120821214225@serebryakov.spb.ru> <1345585084.27688.377.camel@revolution.hippie.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: quoted-printable Cc: freebsd-current@freebsd.org, Warner Losh Subject: Re: r239356: does it mean, that synchronous dhcp and dhcplcinet with disabled devd gone? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: lev@FreeBSD.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Aug 2012 22:36:29 -0000 Hello, Ian. You wrote 22 =C1=D7=C7=D5=D3=D4=C1 2012 =C7., 1:38:04: IL> For example, this script can replace devd as a daemon that restarts IL> dhclient when any link comes back up... IL> Of course the right thing to do is invoke the proper rc scripts rather IL> than dhclient directly... this is just to illustrate how easy it is to IL> replace devd if your needs are specialized. [sigh] Everything worked with 8.x without problems. It worked with 9.x and -CURR= ENT with adding of ``synchronous_dhclient=3D"YES"'' into /etc/rc.conf (And it cost me about 2 hours of investigation, why dhclient stops to start after upgrade). Next I'll need to write some script. Is it Ok to you? Yes, I understand problem with laptops, which change wire and wireless networks and need to re-acquire new address. But it should be soleved other way. And jhb@ already posted proper solution, BTW! And, as side note, ``man rc.cof'' says NOTHING about relation of devd and ``synchronous_dhclient'' setting! It says about ``start dhclient(8) synchronously at startup'' without explaining, that without this option and with devd disabled, dhclient WILL NOT START AT ALL! And relations between devd and dhclient are not documented at all in: rc.conf(5), dhclient(8), devd.conf(5) and devd(8). And rc.conf(5) explains `devd_enable' as: Run devd(8) to handle device added, removed or unknown events from the ker= nel. And doesn't say a word about network link state. --=20 // Black Lion AKA Lev Serebryakov From owner-freebsd-current@FreeBSD.ORG Tue Aug 21 22:37:43 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 656C4106564A; Tue, 21 Aug 2012 22:37:43 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from onlyone.friendlyhosting.spb.ru (onlyone.friendlyhosting.spb.ru [IPv6:2a01:4f8:131:60a2::2]) by mx1.freebsd.org (Postfix) with ESMTP id EDFB38FC16; Tue, 21 Aug 2012 22:37:42 +0000 (UTC) Received: from lion.home.serebryakov.spb.ru (unknown [IPv6:2001:470:923f:1:8870:d54b:33e8:55b2]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.friendlyhosting.spb.ru (Postfix) with ESMTPA id A714A4AC2D; Wed, 22 Aug 2012 02:37:41 +0400 (MSK) Date: Wed, 22 Aug 2012 02:37:38 +0400 From: Lev Serebryakov Organization: FreeBSD X-Priority: 3 (Normal) Message-ID: <19610511471.20120822023738@serebryakov.spb.ru> To: John Baldwin In-Reply-To: <201208211725.23381.jhb@freebsd.org> References: <20120821095527.GA33206@hell.ukr.net> <1959717636.20120821155308@serebryakov.spb.ru> <201208210934.31484.jhb@freebsd.org> <201208211725.23381.jhb@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=windows-1251 Content-Transfer-Encoding: quoted-printable Cc: Garrett Cooper , freebsd-current@freebsd.org, current@freebsd.org, Peter Jeremy Subject: Re: r239356: does it mean, that synchronous dhcp and dhcplcinet with disabled devd gone? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: lev@FreeBSD.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Aug 2012 22:37:43 -0000 Hello, John. You wrote 22 =E0=E2=E3=F3=F1=F2=E0 2012 =E3., 1:25:23: JB> Ok, this is what I came up with, somewhat loosely based on OpenBSD's dh= client. JB> I tested that it survives the following: JB> - Unplugging/replugging does not kill an existing ssh session JB> - Using ifconfig down/up does not kill an existing ssh session JB> - Plugging into a different network does cause dhclient to negotiate JB> a new lease on the new network THANK YOU! --=20 // Black Lion AKA Lev Serebryakov From owner-freebsd-current@FreeBSD.ORG Tue Aug 21 22:37:43 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 656C4106564A; Tue, 21 Aug 2012 22:37:43 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from onlyone.friendlyhosting.spb.ru (onlyone.friendlyhosting.spb.ru [IPv6:2a01:4f8:131:60a2::2]) by mx1.freebsd.org (Postfix) with ESMTP id EDFB38FC16; Tue, 21 Aug 2012 22:37:42 +0000 (UTC) Received: from lion.home.serebryakov.spb.ru (unknown [IPv6:2001:470:923f:1:8870:d54b:33e8:55b2]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.friendlyhosting.spb.ru (Postfix) with ESMTPA id A714A4AC2D; Wed, 22 Aug 2012 02:37:41 +0400 (MSK) Date: Wed, 22 Aug 2012 02:37:38 +0400 From: Lev Serebryakov Organization: FreeBSD X-Priority: 3 (Normal) Message-ID: <19610511471.20120822023738@serebryakov.spb.ru> To: John Baldwin In-Reply-To: <201208211725.23381.jhb@freebsd.org> References: <20120821095527.GA33206@hell.ukr.net> <1959717636.20120821155308@serebryakov.spb.ru> <201208210934.31484.jhb@freebsd.org> <201208211725.23381.jhb@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=windows-1251 Content-Transfer-Encoding: quoted-printable Cc: Garrett Cooper , freebsd-current@freebsd.org, current@freebsd.org, Peter Jeremy Subject: Re: r239356: does it mean, that synchronous dhcp and dhcplcinet with disabled devd gone? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: lev@FreeBSD.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Aug 2012 22:37:43 -0000 Hello, John. You wrote 22 =E0=E2=E3=F3=F1=F2=E0 2012 =E3., 1:25:23: JB> Ok, this is what I came up with, somewhat loosely based on OpenBSD's dh= client. JB> I tested that it survives the following: JB> - Unplugging/replugging does not kill an existing ssh session JB> - Using ifconfig down/up does not kill an existing ssh session JB> - Plugging into a different network does cause dhclient to negotiate JB> a new lease on the new network THANK YOU! --=20 // Black Lion AKA Lev Serebryakov From owner-freebsd-current@FreeBSD.ORG Tue Aug 21 22:58:14 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id CFB6E106564A; Tue, 21 Aug 2012 22:58:14 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) by mx1.freebsd.org (Postfix) with ESMTP id 7EB9C8FC0C; Tue, 21 Aug 2012 22:58:14 +0000 (UTC) Received: from slw by zxy.spb.ru with local (Exim 4.69 (FreeBSD)) (envelope-from ) id 1T3xR7-0001Tl-UW; Wed, 22 Aug 2012 03:00:37 +0400 Date: Wed, 22 Aug 2012 03:00:37 +0400 From: Slawa Olhovchenkov To: Lev Serebryakov Message-ID: <20120821230037.GE88729@zxy.spb.ru> References: <1049151425.20120821190433@serebryakov.spb.ru> <1345562163.27688.347.camel@revolution.hippie.lan> <709115163.20120821192652@serebryakov.spb.ru> <1345564507.27688.354.camel@revolution.hippie.lan> <1409150425.20120821210152@serebryakov.spb.ru> <1345570590.27688.367.camel@revolution.hippie.lan> <686419050.20120821214225@serebryakov.spb.ru> <1345585084.27688.377.camel@revolution.hippie.lan> <1844966139.20120822023623@serebryakov.spb.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <1844966139.20120822023623@serebryakov.spb.ru> User-Agent: Mutt/1.5.21 (2010-09-15) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false Cc: Ian Lepore , freebsd-current@freebsd.org, Warner Losh Subject: Re: r239356: does it mean, that synchronous dhcp and dhcplcinet with disabled devd gone? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 21 Aug 2012 22:58:14 -0000 On Wed, Aug 22, 2012 at 02:36:23AM +0400, Lev Serebryakov wrote: > Hello, Ian. > You wrote 22 Á×ÇÕÓÔÁ 2012 Ç., 1:38:04: > > IL> For example, this script can replace devd as a daemon that restarts > IL> dhclient when any link comes back up... > > IL> Of course the right thing to do is invoke the proper rc scripts rather > IL> than dhclient directly... this is just to illustrate how easy it is to > IL> replace devd if your needs are specialized. > [sigh] > Everything worked with 8.x without problems. It worked with 9.x and -CURRENT > with adding of ``synchronous_dhclient="YES"'' into /etc/rc.conf (And > it cost me about 2 hours of investigation, why dhclient stops to > start after upgrade). Next I'll need to write some script. Is it Ok > to you? > > Yes, I understand problem with laptops, which change wire and > wireless networks and need to re-acquire new address. But it should > be soleved other way. And jhb@ already posted proper solution, BTW! > > And, as side note, ``man rc.cof'' says NOTHING about relation of devd > and ``synchronous_dhclient'' setting! It says about ``start > dhclient(8) synchronously at startup'' without explaining, that > without this option and with devd disabled, dhclient WILL NOT START > AT ALL! And relations between devd and dhclient are not documented at > all in: rc.conf(5), dhclient(8), devd.conf(5) and devd(8). Time ago synchronous_dhclient is waiting for obtain IP by dhcpclient. w/o synchronous_dhclient and ifconfig_bge0="DHCP" dhcpclient run in background and don't paused boot while obtaining IP address. On perinterface basis: ifconfig_bge0="SYNCDHCP" or ifconfig_bge0="NOSYNCDHCP" Background start of dhcpclient currently by devd, on UP event on ethernet interface. This introduction in 6.2. 2006-08-22. From owner-freebsd-current@FreeBSD.ORG Tue Aug 21 23:09:04 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5C1E5106564A; Tue, 21 Aug 2012 23:09:04 +0000 (UTC) (envelope-from peter@rulingia.com) Received: from vps.rulingia.com (host-122-100-2-194.octopus.com.au [122.100.2.194]) by mx1.freebsd.org (Postfix) with ESMTP id DED448FC0A; Tue, 21 Aug 2012 23:09:03 +0000 (UTC) Received: from server.rulingia.com (c220-239-249-137.belrs5.nsw.optusnet.com.au [220.239.249.137]) by vps.rulingia.com (8.14.5/8.14.5) with ESMTP id q7LN92C5085291 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 22 Aug 2012 09:09:02 +1000 (EST) (envelope-from peter@rulingia.com) X-Bogosity: Ham, spamicity=0.000000 Received: from server.rulingia.com (localhost.rulingia.com [127.0.0.1]) by server.rulingia.com (8.14.5/8.14.5) with ESMTP id q7LN8uQI095287 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 22 Aug 2012 09:08:56 +1000 (EST) (envelope-from peter@server.rulingia.com) Received: (from peter@localhost) by server.rulingia.com (8.14.5/8.14.5/Submit) id q7LN8uj2095286; Wed, 22 Aug 2012 09:08:56 +1000 (EST) (envelope-from peter) Date: Wed, 22 Aug 2012 09:08:56 +1000 From: Peter Jeremy To: John Baldwin Message-ID: <20120821230856.GB94197@server.rulingia.com> References: <20120821095527.GA33206@hell.ukr.net> <1959717636.20120821155308@serebryakov.spb.ru> <201208210934.31484.jhb@freebsd.org> <201208211725.23381.jhb@freebsd.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="K8nIJk4ghYZn606h" Content-Disposition: inline In-Reply-To: <201208211725.23381.jhb@freebsd.org> X-PGP-Key: http://www.rulingia.com/keys/peter.pgp User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-current@freebsd.org Subject: Re: r239356: does it mean, that synchronous dhcp and dhcplcinet with disabled devd gone? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 21 Aug 2012 23:09:04 -0000 --K8nIJk4ghYZn606h Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2012-Aug-21 17:25:23 -0400, John Baldwin wrote: >Ok, this is what I came up with, somewhat loosely based on OpenBSD's dhcli= ent. >I tested that it survives the following: I've also done some limited testing on both bge and fxp NICs and haven't run into any problems. In particular the spurious link resets =66rom fxp don't seem to cause any problems. --=20 Peter Jeremy --K8nIJk4ghYZn606h Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEARECAAYFAlA0FQgACgkQ/opHv/APuIclgQCePpO0cJaoKk0el4Oeu/c4y74H V+0AoLzHR+ofcRYck7Ce3P4J2vsIKdnr =iOsg -----END PGP SIGNATURE----- --K8nIJk4ghYZn606h-- From owner-freebsd-current@FreeBSD.ORG Tue Aug 21 23:14:07 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 896DE106566B; Tue, 21 Aug 2012 23:14:07 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) by mx1.freebsd.org (Postfix) with ESMTP id 1B4958FC0C; Tue, 21 Aug 2012 23:14:06 +0000 (UTC) Received: from slw by zxy.spb.ru with local (Exim 4.69 (FreeBSD)) (envelope-from ) id 1T3xgU-0001hK-50; Wed, 22 Aug 2012 03:16:30 +0400 Date: Wed, 22 Aug 2012 03:16:30 +0400 From: Slawa Olhovchenkov To: John Baldwin Message-ID: <20120821231630.GF88729@zxy.spb.ru> References: <20120821095527.GA33206@hell.ukr.net> <1959717636.20120821155308@serebryakov.spb.ru> <201208210934.31484.jhb@freebsd.org> <201208211725.23381.jhb@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <201208211725.23381.jhb@freebsd.org> User-Agent: Mutt/1.5.21 (2010-09-15) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false Cc: Garrett Cooper , freebsd-current@freebsd.org, lev@freebsd.org, current@freebsd.org, Peter Jeremy Subject: Re: r239356: does it mean, that synchronous dhcp and dhcplcinet with disabled devd gone? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 21 Aug 2012 23:14:07 -0000 On Tue, Aug 21, 2012 at 05:25:23PM -0400, John Baldwin wrote: > On Tuesday, August 21, 2012 9:34:31 am John Baldwin wrote: > > On Tuesday, August 21, 2012 7:53:08 am Lev Serebryakov wrote: > > > Hello, Garrett. > > > You wrote 21 Á×ÇÕÓÔÁ 2012 Ç., 15:40:35: > > > > > > GC>> Try reverting r239356 -- if that works, then please let jhb@ know. > > > LS> I'm confused by this commit, because it seems (from comment alone), > > > LS> that dhclient will not work without devd anymore (with "synchronous > > > LS> dhcp" option in rc.conf). > > > LS> Am I right? > > > And if I'm right about understanding what this change does, it is > > > POLA violation for sure. Both consequences: unable to use dhcclient > > > without devd (user will need to restart it by hands after each cable > > > unplugging event) and removing IP address from interface on cable > > > unplugging or other interface down event but before lease is expired. > > > > > > If I'm right in understanding this commit, I vote to back it out and > > > find better solution, may be, two new options: one to remove IP and > > > one to exit on interface down. And default behavior should be OLD > > > ONE about IP address in any case and OLD ONE about exit in case when > > > dhclient isn't started by devd, but by rc scripts directly. > > > > Humm. devd is the more common case, and we explicitly don't use devd to start > > dhclient on boot even when devd is enabled (so out of the box dhcp would first > > be started by rc, but would be restarted by devd). > > > > Another option is to rework dhclient to work like it does on OpenBSD where it > > renews its lease if the link bounces, but to not exit when the link goes down. > > That case would fix the currently broken case that you unplug your cable, take > > your laptop over to another network (e.g. take it home if suspend/resume > > works), then plug it back in and are still stuck with your old IP. > > Ok, this is what I came up with, somewhat loosely based on OpenBSD's dhclient. > I tested that it survives the following: > > - Unplugging/replugging does not kill an existing ssh session > - Using ifconfig down/up does not kill an existing ssh session > - Plugging into a different network does cause dhclient to negotiate > a new lease on the new network Assign address on interface manualy cause exiting dhcpclient? > I've removed the bits to clear the old configuration if dhclient exits due to > 'ifconfig down', and dhclient no longer exits on link down, but instead tracks > the link state and enters the 'reboot' state when the link goes up. > > Index: dhcpd.h > =================================================================== > --- dhcpd.h (revision 239498) > +++ dhcpd.h (working copy) > @@ -208,6 +208,7 @@ > int errors; > int dead; > u_int16_t index; > + int linkstat; > }; > > struct timeout { > Index: dhclient.c > =================================================================== > --- dhclient.c (revision 239498) > +++ dhclient.c (working copy) > @@ -218,6 +218,7 @@ > struct sockaddr *sa; > struct iaddr a; > ssize_t n; > + int linkstat; > > n = read(routefd, &msg, sizeof(msg)); > rtm = (struct rt_msghdr *)msg; > @@ -278,10 +279,14 @@ > ifi->name); > goto die; > } > - if (!interface_link_status(ifi->name)) { > - warning("Interface %s is down, dhclient exiting", > - ifi->name); > - goto die; > + linkstat = interface_link_status(ifi->name); > + if (linkstat != ifi->linkstat) { > + debug("%s link state %s -> %s", ifi->name, > + ifi->linkstat ? "up" : "down", > + linkstat ? "up" : "down"); > + ifi->linkstat = linkstat; > + if (linkstat) > + state_reboot(ifi); > } > break; > case RTM_IFANNOUNCE: > @@ -321,8 +326,6 @@ > > die: > script_init("FAIL", NULL); > - if (ifi->client->active) > - script_write_params("old_", ifi->client->active); > if (ifi->client->alias) > script_write_params("alias_", ifi->client->alias); > script_go(); > @@ -437,6 +440,7 @@ > } > fprintf(stderr, " got link\n"); > } > + ifi->linkstat = 1; > > if ((nullfd = open(_PATH_DEVNULL, O_RDWR, 0)) == -1) > error("cannot open %s: %m", _PATH_DEVNULL); > > -- > John Baldwin > _______________________________________________ > 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 Aug 21 23:14:07 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 896DE106566B; Tue, 21 Aug 2012 23:14:07 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) by mx1.freebsd.org (Postfix) with ESMTP id 1B4958FC0C; Tue, 21 Aug 2012 23:14:06 +0000 (UTC) Received: from slw by zxy.spb.ru with local (Exim 4.69 (FreeBSD)) (envelope-from ) id 1T3xgU-0001hK-50; Wed, 22 Aug 2012 03:16:30 +0400 Date: Wed, 22 Aug 2012 03:16:30 +0400 From: Slawa Olhovchenkov To: John Baldwin Message-ID: <20120821231630.GF88729@zxy.spb.ru> References: <20120821095527.GA33206@hell.ukr.net> <1959717636.20120821155308@serebryakov.spb.ru> <201208210934.31484.jhb@freebsd.org> <201208211725.23381.jhb@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <201208211725.23381.jhb@freebsd.org> User-Agent: Mutt/1.5.21 (2010-09-15) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false Cc: Garrett Cooper , freebsd-current@freebsd.org, lev@freebsd.org, current@freebsd.org, Peter Jeremy Subject: Re: r239356: does it mean, that synchronous dhcp and dhcplcinet with disabled devd gone? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 21 Aug 2012 23:14:07 -0000 On Tue, Aug 21, 2012 at 05:25:23PM -0400, John Baldwin wrote: > On Tuesday, August 21, 2012 9:34:31 am John Baldwin wrote: > > On Tuesday, August 21, 2012 7:53:08 am Lev Serebryakov wrote: > > > Hello, Garrett. > > > You wrote 21 Á×ÇÕÓÔÁ 2012 Ç., 15:40:35: > > > > > > GC>> Try reverting r239356 -- if that works, then please let jhb@ know. > > > LS> I'm confused by this commit, because it seems (from comment alone), > > > LS> that dhclient will not work without devd anymore (with "synchronous > > > LS> dhcp" option in rc.conf). > > > LS> Am I right? > > > And if I'm right about understanding what this change does, it is > > > POLA violation for sure. Both consequences: unable to use dhcclient > > > without devd (user will need to restart it by hands after each cable > > > unplugging event) and removing IP address from interface on cable > > > unplugging or other interface down event but before lease is expired. > > > > > > If I'm right in understanding this commit, I vote to back it out and > > > find better solution, may be, two new options: one to remove IP and > > > one to exit on interface down. And default behavior should be OLD > > > ONE about IP address in any case and OLD ONE about exit in case when > > > dhclient isn't started by devd, but by rc scripts directly. > > > > Humm. devd is the more common case, and we explicitly don't use devd to start > > dhclient on boot even when devd is enabled (so out of the box dhcp would first > > be started by rc, but would be restarted by devd). > > > > Another option is to rework dhclient to work like it does on OpenBSD where it > > renews its lease if the link bounces, but to not exit when the link goes down. > > That case would fix the currently broken case that you unplug your cable, take > > your laptop over to another network (e.g. take it home if suspend/resume > > works), then plug it back in and are still stuck with your old IP. > > Ok, this is what I came up with, somewhat loosely based on OpenBSD's dhclient. > I tested that it survives the following: > > - Unplugging/replugging does not kill an existing ssh session > - Using ifconfig down/up does not kill an existing ssh session > - Plugging into a different network does cause dhclient to negotiate > a new lease on the new network Assign address on interface manualy cause exiting dhcpclient? > I've removed the bits to clear the old configuration if dhclient exits due to > 'ifconfig down', and dhclient no longer exits on link down, but instead tracks > the link state and enters the 'reboot' state when the link goes up. > > Index: dhcpd.h > =================================================================== > --- dhcpd.h (revision 239498) > +++ dhcpd.h (working copy) > @@ -208,6 +208,7 @@ > int errors; > int dead; > u_int16_t index; > + int linkstat; > }; > > struct timeout { > Index: dhclient.c > =================================================================== > --- dhclient.c (revision 239498) > +++ dhclient.c (working copy) > @@ -218,6 +218,7 @@ > struct sockaddr *sa; > struct iaddr a; > ssize_t n; > + int linkstat; > > n = read(routefd, &msg, sizeof(msg)); > rtm = (struct rt_msghdr *)msg; > @@ -278,10 +279,14 @@ > ifi->name); > goto die; > } > - if (!interface_link_status(ifi->name)) { > - warning("Interface %s is down, dhclient exiting", > - ifi->name); > - goto die; > + linkstat = interface_link_status(ifi->name); > + if (linkstat != ifi->linkstat) { > + debug("%s link state %s -> %s", ifi->name, > + ifi->linkstat ? "up" : "down", > + linkstat ? "up" : "down"); > + ifi->linkstat = linkstat; > + if (linkstat) > + state_reboot(ifi); > } > break; > case RTM_IFANNOUNCE: > @@ -321,8 +326,6 @@ > > die: > script_init("FAIL", NULL); > - if (ifi->client->active) > - script_write_params("old_", ifi->client->active); > if (ifi->client->alias) > script_write_params("alias_", ifi->client->alias); > script_go(); > @@ -437,6 +440,7 @@ > } > fprintf(stderr, " got link\n"); > } > + ifi->linkstat = 1; > > if ((nullfd = open(_PATH_DEVNULL, O_RDWR, 0)) == -1) > error("cannot open %s: %m", _PATH_DEVNULL); > > -- > John Baldwin > _______________________________________________ > 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 Wed Aug 22 01:13:08 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id BDAEE106566C for ; Wed, 22 Aug 2012 01:13:08 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from mail-pz0-f54.google.com (mail-pz0-f54.google.com [209.85.210.54]) by mx1.freebsd.org (Postfix) with ESMTP id 8A3DA8FC12 for ; Wed, 22 Aug 2012 01:13:08 +0000 (UTC) Received: by dadr6 with SMTP id r6so315485dad.13 for ; Tue, 21 Aug 2012 18:13:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:date:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=bCjRMEWYlJ/io+OfyvpmUJ5BQ3nKPlVNFhHixoUzOa4=; b=n1cRRFlCrV8j7DCjJzFifIKZKraIueYxLTbvImbt1zE4DMOTyNyEYsPNDj1/+yZsph hu0bF6w+0IZRl5B5VtY4Y0lm44AlkgeSQxMo1e2nMGRPToS7Z7tAZHV9mmW0wod36GXF klc8thQLYByuW4X+Ghnel1KXihgKdFdatOtKsApJYHrV4rnPjoLo5tkEZ0T4Fc3tRfqt ovfd4QVhJrfFDa57MxfXPgfQbTkPOTKKlFNBP2Ueb7BRmWbZmqA9E73UBz3FmDL1fkxQ 9sYz3QLw1fT50A9AuSRF6cYY5HbUa8TrKO87CVPLEZ67o/kJODeLko3RpQIZUR45q4uQ ZNTQ== Received: by 10.68.129.38 with SMTP id nt6mr49031490pbb.76.1345597981915; Tue, 21 Aug 2012 18:13:01 -0700 (PDT) Received: from pyunyh@gmail.com (lpe4.p59-icn.cdngp.net. [114.111.62.249]) by mx.google.com with ESMTPS id vh7sm2533957pbc.22.2012.08.21.18.12.58 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 21 Aug 2012 18:13:00 -0700 (PDT) Received: by pyunyh@gmail.com (sSMTP sendmail emulation); Wed, 22 Aug 2012 10:12:53 -0700 From: YongHyeon PYUN Date: Wed, 22 Aug 2012 10:12:53 -0700 To: Peter Jeremy Message-ID: <20120822171253.GB3300@michelle.cdnetworks.com> References: <20120821095527.GA33206@hell.ukr.net> <20120821164217.GA45780@hell.ukr.net> <20120821222701.GA94197@server.rulingia.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20120821222701.GA94197@server.rulingia.com> User-Agent: Mutt/1.4.2.3i Cc: Vitalij Satanivskij , current@freebsd.org Subject: Re: dhclient cause up/down cycle after 239356 ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Aug 2012 01:13:08 -0000 On Wed, Aug 22, 2012 at 08:27:01AM +1000, Peter Jeremy wrote: > On 2012-Aug-21 19:42:17 +0300, Vitalij Satanivskij wrote: > >Look's like dhclient do down/up sequence - > > Not intentionally. > > >Aug 21 19:21:00 home kernel: fxp0: link state changed to UP > >Aug 21 19:21:01 home kernel: fxp0: link state changed to DOWN > >Aug 21 19:21:01 home dhclient: New IP Address (fxp0): xx.xx.xx.xx > >Aug 21 19:21:01 home dhclient: New Subnet Mask (fxp0): 255.255.255.0 > >Aug 21 19:21:01 home dhclient: New Broadcast Address (fxp0): xx.xx.xx.xx > >Aug 21 19:21:01 home dhclient: New Routers (fxp0): xx.xx.xx.xx > >Aug 21 19:21:03 home kernel: fxp0: link state changed to UP > > I can reproduce this behaviour - but only on fxp (i82559 in my case) > NICs. My bge (BCM5750) and rl (RTL8139) NICs do not report the > spurious DOWN/UP. (I don't normally run DHCP on any fxp interfaces, > so I didn't see it during my testing). > > The problem appears to be the > $IFCONFIG $interface inet alias 0.0.0.0 netmask 255.0.0.0 broadcast 255.255.255.255 up > executed by /sbin/dhclient-script during PREINIT. This is making the > fxp NIC reset the link (actually, assigning _any_ IP address to an fxp > NIC causes it to reset the link). The post r239356 dhclient detects This comes from the hardware limitation. Assigning addresses will result in programming multicast filter and fxp(4) controllers require full controller reset to reprogram the multicast filter. > the link going down and exits. > > >Before r239356 iface just doing down/up without dhclient exit and > >everything work fine. > > For you, anyway. Failing to detect link down causes problems for me > because my dhclient was not seeing my cable-modem resets and therefore > failing to reacquire a DHCP lease. > > -- > Peter Jeremy From owner-freebsd-current@FreeBSD.ORG Wed Aug 22 01:58:52 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 60133106566B; Wed, 22 Aug 2012 01:58:52 +0000 (UTC) (envelope-from bzeeb-lists@lists.zabbadoz.net) Received: from mx1.sbone.de (bird.sbone.de [46.4.1.90]) by mx1.freebsd.org (Postfix) with ESMTP id 09AB28FC12; Wed, 22 Aug 2012 01:58:51 +0000 (UTC) Received: from mail.sbone.de (mail.sbone.de [IPv6:fde9:577b:c1a9:31::2013:587]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.sbone.de (Postfix) with ESMTPS id 4D26525D3887; Wed, 22 Aug 2012 01:58:50 +0000 (UTC) Received: from content-filter.sbone.de (content-filter.sbone.de [IPv6:fde9:577b:c1a9:31::2013:2742]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPS id 5A437BE84CF; Wed, 22 Aug 2012 01:58:49 +0000 (UTC) X-Virus-Scanned: amavisd-new at sbone.de Received: from mail.sbone.de ([IPv6:fde9:577b:c1a9:31::2013:587]) by content-filter.sbone.de (content-filter.sbone.de [fde9:577b:c1a9:31::2013:2742]) (amavisd-new, port 10024) with ESMTP id UpcZPVP3lDpO; Wed, 22 Aug 2012 01:58:48 +0000 (UTC) Received: from nv.sbone.de (nv.sbone.de [IPv6:fde9:577b:c1a9:31::2013:138]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPSA id 3C168BE799F; Wed, 22 Aug 2012 01:58:48 +0000 (UTC) Date: Wed, 22 Aug 2012 01:58:47 +0000 (UTC) From: "Bjoern A. Zeeb" To: ports@freebsd.org In-Reply-To: <5033EC58.3000801@FreeBSD.org> Message-ID: References: <20120820194313.GC23607@ithaqua.etoilebsd.net> <20120821132643.GE37262@felucia.tataz.chchile.org> <20120821134623.GH5044@ithaqua.etoilebsd.net> <5033D0C0.4030805@FreeBSD.org> <20120821190500.GA46595@ithaqua.etoilebsd.net> <5033E39C.3060700@FreeBSD.org> <20120821194208.GC46595@ithaqua.etoilebsd.net> <5033E6BA.8080309@FreeBSD.org> <5033EC58.3000801@FreeBSD.org> X-OpenPGP-Key-Id: 0x14003F198FEFA3E77207EE8D2B58B8F83CCF1842 MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: current@freebsd.org Subject: Re: pkgng 1.0 release schedule, and HEAD switch to pkgng by default schedule X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 22 Aug 2012 01:58:52 -0000 On Tue, 21 Aug 2012, Doug Barton wrote: > I don't think we have ever done a complete replacement of major > infrastructure in one release. You mean like sysinstall can be used as an installer on 9 that would do something meaningful with the current infrastructure we provide? -- Bjoern A. Zeeb You have to have visions! Stop bit received. Insert coin for new address family. From owner-freebsd-current@FreeBSD.ORG Wed Aug 22 03:14:03 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 34CA61065674 for ; Wed, 22 Aug 2012 03:14:03 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from mail-pb0-f54.google.com (mail-pb0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id AFB888FC14 for ; Wed, 22 Aug 2012 03:14:02 +0000 (UTC) Received: by pbbrp2 with SMTP id rp2so856814pbb.13 for ; Tue, 21 Aug 2012 20:14:02 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=sender:subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer :x-gm-message-state; bh=T6a1FPxXePu18rfydBB4ZUvxDWc+gyy9Z1fktgtGm8o=; b=kvZHLTo06O7S99mOEbiAbVmRk3PUCFGWjGGo9xqUWo0pCixSSnky7oTTy8qrV4gAO0 slHkOECbCbx9sLGpOzHKHmXEm49fEVFm6x3P7AR6WjtlAGonoFR7ME/5+2MKuy5bH7to KvcREZsjNHsznWy2FFvy7ef7B4zXKW12Ok2HNEAkc9r0JUJOtrDlfFN6s2azVNUCG8u1 t95foK9ZQ3xDiBjX9PLJUE9jIBZe0n2JCkR6wARzJX1GAxJUE72PbALwNRle/00A6I8S t26VE9ULTbP5xEE9Q64f4jiQM/GXhX1Amyl+uOo0+PAe8HSNkDUMhqlzxgklH4njzkLY 7bew== Received: by 10.68.216.104 with SMTP id op8mr49125085pbc.65.1345605242161; Tue, 21 Aug 2012 20:14:02 -0700 (PDT) Received: from [10.0.0.63] (50-78-194-198-static.hfc.comcastbusiness.net. [50.78.194.198]) by mx.google.com with ESMTPS id oj8sm2710409pbb.54.2012.08.21.20.14.00 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 21 Aug 2012 20:14:01 -0700 (PDT) Sender: Warner Losh Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=koi8-r From: Warner Losh In-Reply-To: <20120821221543.GV98910@zxy.spb.ru> Date: Tue, 21 Aug 2012 21:13:58 -0600 Content-Transfer-Encoding: quoted-printable Message-Id: References: <20120821095527.GA33206@hell.ukr.net> <67977762.20120821154035@serebryakov.spb.ru> <1243982625.20120821154548@serebryakov.spb.ru> <20120821124623.GC88729@zxy.spb.ru> <9481DE65-1249-4EE1-96E0-222ADD46B2E6@bsdimp.com> <20120821221543.GV98910@zxy.spb.ru> To: Slawa Olhovchenkov X-Mailer: Apple Mail (2.1084) X-Gm-Message-State: ALoCoQmaePKdT14NAtcA7wAO+ZC9sdBgUMoiBzaPvg1tHnCC9dI//xHj1gEoj0b/hGlHUmn8xTxG Cc: Garrett Cooper , Lev Serebryakov , current@freebsd.org, jhb@FreeBSD.org Subject: Re: r239356: does it mean, that synchronous dhcp and dhcplcinet with disabled devd gone? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 22 Aug 2012 03:14:03 -0000 On Aug 21, 2012, at 4:15 PM, Slawa Olhovchenkov wrote: > On Tue, Aug 21, 2012 at 01:56:11PM -0600, Warner Losh wrote: >=20 >>=20 >> On Aug 21, 2012, at 6:46 AM, Slawa Olhovchenkov wrote: >>=20 >>> On Tue, Aug 21, 2012 at 03:45:48PM +0400, Lev Serebryakov wrote: >>>=20 >>>> Hello, Lev. >>>> You wrote 21 =C1=D7=C7=D5=D3=D4=C1 2012 =C7., 15:40:35: >>>>=20 >>>> GC>> Try reverting r239356 -- if that works, then please let jhb@ = know. >>>> LS> I'm confused by this commit, because it seems (from comment = alone), >>>> LS> that dhclient will not work without devd anymore (with = "synchronous >>>> LS> dhcp" option in rc.conf). >>>> LS> Am I right? >>>> Also, I don't like idea of removing IP address from interface = when >>>> cable is unplugged. It was very disturbing behavior of Windows >>>> machines for years. I've unplug cable to change switch port for = only a >>>> second and all connections are broken, even if one second later >>>> dhcpclient receive SAME lease! I don't like this. FreeBSD was very >>>> tolerant to unplugging cable for eons, and I (and not only me) like >>>> it. If I understand this change properly, it is no more the case :( >>>=20 >>> Not only cable. >>> Turn on microwave, lost WiFi connection and lost all open ssh >>> session (and other network connection). >>=20 >> mosh helps. >=20 > No. Not all remote host allow to install mosh. > Cisco routers, for example, don't allow to install mosh. Yes. Mosh helps. You can mosh to a different host, then do what you = need to do to get to the cisco. Does mosh solve the problem in all cases, no. It just helps. Warner= From owner-freebsd-current@FreeBSD.ORG Wed Aug 22 03:15:13 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 08605106566C for ; Wed, 22 Aug 2012 03:15:13 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from mail-pb0-f54.google.com (mail-pb0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id C1A828FC12 for ; Wed, 22 Aug 2012 03:15:12 +0000 (UTC) Received: by pbbrp2 with SMTP id rp2so857854pbb.13 for ; Tue, 21 Aug 2012 20:15:12 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=sender:subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer :x-gm-message-state; bh=vm2LKoM4ApIXzob2Rc92VNdz3ZKhrgQVgb2yQjZh8Mg=; b=hv/WM7v1gecJcx22uAkzTG5D4vlmm4x/Sob8tggAZxvdmxwPJ3rc+6owJ2/ndQgIEB b9fj7bQROm02+0JHEaL6t7+rb1CWlcMQVDsM9D5FcxfJS5/8To9i2Phxf9xUVbyDJf5S BRCD8yjHhneEjc2tSx96DKbIYUaWQ2ya4EXR/PpbdDqnBT0bOKhGnhuXnS4BgNVzIoNx WlMFfDA1/JvYDCpVPZp+bsF1zd4ZFaJt8NYvZiE/YGkzYxT65Yxi57gSOwItRJFDq3PA pwlOsJa0WEryQC6refjEfA15xUQihCiqACz6qxE2IIaNd6YfMDsMIGmvx0SGP6Z7UVd4 wOwQ== Received: by 10.66.88.233 with SMTP id bj9mr42568412pab.72.1345605312397; Tue, 21 Aug 2012 20:15:12 -0700 (PDT) Received: from [10.0.0.63] (50-78-194-198-static.hfc.comcastbusiness.net. [50.78.194.198]) by mx.google.com with ESMTPS id tv6sm2732749pbc.24.2012.08.21.20.15.10 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 21 Aug 2012 20:15:11 -0700 (PDT) Sender: Warner Losh Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=koi8-r From: Warner Losh In-Reply-To: <20120821230037.GE88729@zxy.spb.ru> Date: Tue, 21 Aug 2012 21:15:08 -0600 Content-Transfer-Encoding: quoted-printable Message-Id: <835A0305-C273-402A-826E-C2A87BD062F8@bsdimp.com> References: <1049151425.20120821190433@serebryakov.spb.ru> <1345562163.27688.347.camel@revolution.hippie.lan> <709115163.20120821192652@serebryakov.spb.ru> <1345564507.27688.354.camel@revolution.hippie.lan> <1409150425.20120821210152@serebryakov.spb.ru> <1345570590.27688.367.camel@revolution.hippie.lan> <686419050.20120821214225@serebryakov.spb.ru> <1345585084.27688.377.camel@revolution.hippie.lan> <1844966139.20120822023623@serebryakov.spb.ru> <20120821230037.GE88729@zxy.spb.ru> To: Slawa Olhovchenkov X-Mailer: Apple Mail (2.1084) X-Gm-Message-State: ALoCoQktOkfgE1+nsgvwk1yzh80TWPcRo3fb3C1rtPCu3KhPwVsCleEXwq2SdSqheRcbX+Tfg8Zm Cc: Ian Lepore , Lev Serebryakov , freebsd-current@freebsd.org Subject: Re: r239356: does it mean, that synchronous dhcp and dhcplcinet with disabled devd gone? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 22 Aug 2012 03:15:13 -0000 On Aug 21, 2012, at 5:00 PM, Slawa Olhovchenkov wrote: > On Wed, Aug 22, 2012 at 02:36:23AM +0400, Lev Serebryakov wrote: >=20 >> Hello, Ian. >> You wrote 22 =C1=D7=C7=D5=D3=D4=C1 2012 =C7., 1:38:04: >>=20 >> IL> For example, this script can replace devd as a daemon that = restarts >> IL> dhclient when any link comes back up... >>=20 >> IL> Of course the right thing to do is invoke the proper rc scripts = rather >> IL> than dhclient directly... this is just to illustrate how easy it = is to >> IL> replace devd if your needs are specialized. >> [sigh] >> Everything worked with 8.x without problems. It worked with 9.x and = -CURRENT >> with adding of ``synchronous_dhclient=3D"YES"'' into /etc/rc.conf = (And >> it cost me about 2 hours of investigation, why dhclient stops to >> start after upgrade). Next I'll need to write some script. Is it Ok >> to you? >>=20 >> Yes, I understand problem with laptops, which change wire and >> wireless networks and need to re-acquire new address. But it should >> be soleved other way. And jhb@ already posted proper solution, BTW! >>=20 >> And, as side note, ``man rc.cof'' says NOTHING about relation of = devd >> and ``synchronous_dhclient'' setting! It says about ``start >> dhclient(8) synchronously at startup'' without explaining, that >> without this option and with devd disabled, dhclient WILL NOT START >> AT ALL! And relations between devd and dhclient are not documented at >> all in: rc.conf(5), dhclient(8), devd.conf(5) and devd(8). >=20 > Time ago synchronous_dhclient is waiting for obtain IP by dhcpclient. > w/o synchronous_dhclient and ifconfig_bge0=3D"DHCP" dhcpclient run in > background and don't paused boot while obtaining IP address. > On perinterface basis: ifconfig_bge0=3D"SYNCDHCP" or = ifconfig_bge0=3D"NOSYNCDHCP" >=20 > Background start of dhcpclient currently by devd, on UP event on > ethernet interface. This introduction in 6.2. 2006-08-22. This is why monkeying with default behavior and not documenting changes = are both bad ideas. Warner From owner-freebsd-current@FreeBSD.ORG Wed Aug 22 06:40:15 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 02D47106566B; Wed, 22 Aug 2012 06:40:15 +0000 (UTC) (envelope-from erwin@mail.droso.net) Received: from mail.droso.net (grizzly.droso.dk [78.46.50.170]) by mx1.freebsd.org (Postfix) with ESMTP id AF75B8FC1A; Wed, 22 Aug 2012 06:40:14 +0000 (UTC) Received: by mail.droso.net (Postfix, from userid 1001) id 172906774; Wed, 22 Aug 2012 08:40:13 +0200 (CEST) Date: Wed, 22 Aug 2012 08:40:13 +0200 From: Erwin Lansing To: ports@freebsd.org, current@freebsd.org Message-ID: <20120822064012.GZ27371@droso.net> References: <20120821134623.GH5044@ithaqua.etoilebsd.net> <5033D0C0.4030805@FreeBSD.org> <20120821190500.GA46595@ithaqua.etoilebsd.net> <5033E39C.3060700@FreeBSD.org> <20120821194208.GC46595@ithaqua.etoilebsd.net> <5033E6BA.8080309@FreeBSD.org> <5033EC58.3000801@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD/amd64 9.0-RELEASE User-Agent: Mutt/1.5.21 (2010-09-15) Cc: Subject: Re: pkgng 1.0 release schedule, and HEAD switch to pkgng by default schedule X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 22 Aug 2012 06:40:15 -0000 On Tue, Aug 21, 2012 at 02:43:13PM -0700, Garrett Cooper wrote: > > What Doug mentioned (and I don't think was really considered, but > is valid) would break people that use pkg_* outside of ports. I know > of at least two instances where this would be the case (one case that > uses pkg_* directly, and another case that uses libpkg from pkg_* > 0-o...). As to the old libpkg, it only existed for little over a year and only in HEAD and was even removed from there over a year ago, and the commit message clearly states that it should not be used. OTOH, for those using it, the only alternative for them is probably pkgng which is only now turning stable. Erwin -- Erwin Lansing http://droso.dk erwin@FreeBSD.org http:// www.FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Wed Aug 22 07:13:55 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id CC125106566C for ; Wed, 22 Aug 2012 07:13:55 +0000 (UTC) (envelope-from naylor.b.david@gmail.com) Received: from mail-we0-f182.google.com (mail-we0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id 4BC678FC0A for ; Wed, 22 Aug 2012 07:13:54 +0000 (UTC) Received: by weyx56 with SMTP id x56so2767887wey.13 for ; Wed, 22 Aug 2012 00:13:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:subject:date:user-agent:mime-version:content-type :content-transfer-encoding:message-id; bh=6e4odl4mDMf06tUK0TCP239WC6ZkSSyblPbO/kOsSEI=; b=e3LQN5dMr1cYKP9BC4aEeEF3M2wgEIx1A9eZgq2LobDwc94DRIo/+Eeb1kEbNzgpLd mHLkbUVyWS/xyojbJFVLcgrkvS8yQu7K3hB3HlAPonnmNfsbDilzzorN8Ppy9+ncIMJ2 4P+m3KIL30voe+94Y6vMzu7LkiyFNBkxfMUZz6O9VqSjuYI8UNYHlJB/I5AEvBeSTGts KZUOh8hdTcGBplE1joaypzuiOZxq7iY8H9AwxVmvzU/Wok5l7Fnqt1RonbFI199vzkSt 6luvEqTYqG6QwowbBEzq7/Cj+psLLbcRVAxmbWM1VHNf97JAHXYImxlW1An89pKhsWon gG/Q== Received: by 10.216.192.85 with SMTP id h63mr10228911wen.7.1345619634077; Wed, 22 Aug 2012 00:13:54 -0700 (PDT) Received: from dragon.dg (41-132-210-104.dsl.mweb.co.za. [41.132.210.104]) by mx.google.com with ESMTPS id t7sm10502755wix.6.2012.08.22.00.13.52 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 22 Aug 2012 00:13:53 -0700 (PDT) From: David Naylor To: freebsd-current@freebsd.org Date: Wed, 22 Aug 2012 09:13:44 +0200 User-Agent: KMail/1.13.7 (FreeBSD/9.1-PRERELEASE; KDE/4.8.4; amd64; ; ) MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart14318684.TxW3ytvVdo"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <201208220913.48095.naylor.b.david@gmail.com> Subject: tar not working in an i386 chroot (getvfsbyname) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 22 Aug 2012 07:13:55 -0000 --nextPart14318684.TxW3ytvVdo Content-Type: Text/Plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi, While trying to compile FreeBSD 10 packages I encountered this error: # chroot /scratchpad/freebsd10_i386 tar -cf /dev/null root=20 tar: getvfsbyname failed: No such file or directory tar: Error exit delayed from previous errors. The kernel does have COMPAT_FREEBSD32 in it. To reproduce this (on an=20 =46reeBSD10/amd64 machine) do: # cd /usr/src # make -sj16 buildworld installworld DESTDIR=3D/scratchpad/freebsd10_i386 # chroot /scratchpad/freebsd10_i386 tar -cf /dev/null root Regards --nextPart14318684.TxW3ytvVdo 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) iEYEABECAAYFAlA0hqwACgkQUaaFgP9pFrItAgCfVDH8ovYLfynvbWRjfbMLPQrL fAMAn3T9r0CeNJntgr3VzDbaQOHwQ/w/ =gSlG -----END PGP SIGNATURE----- --nextPart14318684.TxW3ytvVdo-- From owner-freebsd-current@FreeBSD.ORG Wed Aug 22 07:19:06 2012 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 62604106564A for ; Wed, 22 Aug 2012 07:19:06 +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 13C408FC08 for ; Wed, 22 Aug 2012 07:19:05 +0000 (UTC) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost1.zedat.fu-berlin.de (Exim 4.69) with esmtp (envelope-from ) id <1T45DP-0004ix-1m>; Wed, 22 Aug 2012 09:18:59 +0200 Received: from e178010004.adsl.alicedsl.de ([85.178.10.4] helo=thor.walstatt.dyndns.org) by inpost2.zedat.fu-berlin.de (Exim 4.69) with esmtpsa (envelope-from ) id <1T45DO-0005UM-TG>; Wed, 22 Aug 2012 09:18:59 +0200 Message-ID: <503487DE.3050807@zedat.fu-berlin.de> Date: Wed, 22 Aug 2012 09:18:54 +0200 From: "O. Hartmann" User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:14.0) Gecko/20120810 Thunderbird/14.0 MIME-Version: 1.0 To: =?UTF-8?B?QmVybmhhcmQgRnLDtmhsaWNo?= References: <50337752.8070707@zedat.fu-berlin.de> <1345582381.1632.6.camel@Nokia-N900-42-11> In-Reply-To: <1345582381.1632.6.camel@Nokia-N900-42-11> X-Enigmail-Version: 1.4.3 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig865B01EF16F855467CC2ECDA" X-Originating-IP: 85.178.10.4 Cc: Current FreeBSD Subject: Re: FreeBSD 10.0-CURRENT r239477 doesn't compile: virtualbox-ose-kmod-4.1.18_1 is marked as broken: Does not compile on FreeBSD < 8.2. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 22 Aug 2012 07:19:06 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig865B01EF16F855467CC2ECDA Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Am 08/21/12 22:53, schrieb Bernhard Fr=C3=B6hlich: > On Di., 21. Aug. 2012 13:56:02 CEST, O. Hartmann wrote: >=20 >> Today I ran into a problem with FreeBSD 10.0-CURRENT #0 r239477 >> recompiling the VBox kernel module: >> >> =3D=3D=3D> Cleaning for virtualbox-ose-kmod-4.1.18_1 >> =3D=3D=3D> virtualbox-ose-kmod-4.1.18_1 is marked as broken: Does no= t compile >> on FreeBSD < 8.2. >> *** [all] Error code 1 >> >> Stop in /usr/ports/emulators/virtualbox-ose-kmod. >> >> The port compiled prior to the updates of today. >> >> oh >=20 > What is the question? We have deprecated < 8.2 almost five months ago b= ecause of the memobj r0 rewrite. You're the first who complains about thi= s so I'm pretty sure it was the correct decision to move forward. Please = also keep in mind that 8.1 is already EOL. >=20 I do not understand your complains about my mail to the list. For your information: I'm on FreeBSD 10.0-CURRENT and this seems, as far as I know, considered not to be deprecated by now. If I'm wrong in that, sorry= =2E oh --------------enig865B01EF16F855467CC2ECDA 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.0.19 (FreeBSD) iQEcBAEBAgAGBQJQNIfiAAoJEOgBcD7A/5N8mxUIAONEd5Es1L2aAUokUF+ba6ST jfH+BwTq41iF0DksHay3gvOmrYeceZN0x/LHkLnHIV9JfMbKvd5d0VXnbH4g+8JD HTHLcC/SdcAsOdFexTEUkNo55KWs94O2q4c/H2c+2HHDQVpnxlUL/mVPrLzYcJ3x jkqPlS/g7jFrkKNDVIPxjC4elsnnfNifSUdZrqHJmW7li/EFk3pxHlkdmhXMoFcX LMZXxpzYJOxIjHSJ5o68+iSAtT/6x5j0WPKmX51v+z4NGUpl7pp5N+7RrCdFIu7F oIEXyiu0LgCoIB6e1vsvdkdmobmERhC1hkEItINC4j8fjxdOO5GzrdY2FdOQV+g= =phBk -----END PGP SIGNATURE----- --------------enig865B01EF16F855467CC2ECDA-- From owner-freebsd-current@FreeBSD.ORG Wed Aug 22 07:47:00 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx2.freebsd.org (mx2.freebsd.org [IPv6:2001:4f8:fff6::35]) by hub.freebsd.org (Postfix) with ESMTP id E59AB106564A; Wed, 22 Aug 2012 07:47:00 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from [127.0.0.1] (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id 6092114DC61; Wed, 22 Aug 2012 07:47:00 +0000 (UTC) Message-ID: <50348E75.6030609@FreeBSD.org> Date: Wed, 22 Aug 2012 00:47:01 -0700 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:14.0) Gecko/20120713 Thunderbird/14.0 MIME-Version: 1.0 To: "Bjoern A. Zeeb" References: <20120820194313.GC23607@ithaqua.etoilebsd.net> <20120821132643.GE37262@felucia.tataz.chchile.org> <20120821134623.GH5044@ithaqua.etoilebsd.net> <5033D0C0.4030805@FreeBSD.org> <20120821190500.GA46595@ithaqua.etoilebsd.net> <5033E39C.3060700@FreeBSD.org> <20120821194208.GC46595@ithaqua.etoilebsd.net> <5033E6BA.8080309@FreeBSD.org> <5033EC58.3000801@FreeBSD.org> In-Reply-To: X-Enigmail-Version: 1.4.3 OpenPGP: id=1A1ABC84 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: ports@freebsd.org, current@freebsd.org Subject: Re: pkgng 1.0 release schedule, and HEAD switch to pkgng by default schedule X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 22 Aug 2012 07:47:01 -0000 On 8/21/2012 6:58 PM, Bjoern A. Zeeb wrote: > On Tue, 21 Aug 2012, Doug Barton wrote: > >> I don't think we have ever done a complete replacement of major >> infrastructure in one release. > > You mean like sysinstall can be used as an installer on 9 that would > do something meaningful with the current infrastructure we provide? Given the number of users who complain when sysinstall breaks in 9, I'd say yes. Not to mention that sysinstall is a good example of something that we deprecated in one release and removed in the following release. Furthermore, I don't think of the installer as nearly as critical as the ports collection. Yes, it is important, clearly. But it's something that is likely to happen only once in the lifetime of a system, as opposed to the numerous times that users will interact with the ports. Not to mention all of the enterprise users who bypass it altogether. Aside from the installer part of sysinstall, the post-install config portion has been taken over by bsdconfig. So in HEAD you have 2 new tools that are mandatory that fulfill sysinstall's old role; and in 9 you have those same 2 new tools which are the defaults, but optional. That's exactly how it is supposed to work. Finally, the thing that we have to keep in mind is how different the ports tree is from anything else in the base. The infrastructure of the ports has to support all versions of FreeBSD. So we have to be extra cautious about deprecating things. Of course the upside of pkg is that it (properly) lives in the ports tree itself, which will make innovation much easier in a few years. Doug -- I am only one, but I am one. I cannot do everything, but I can do something. And I will not let what I cannot do interfere with what I can do. -- Edward Everett Hale, (1822 - 1909) From owner-freebsd-current@FreeBSD.ORG Wed Aug 22 11:34:40 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EAD07106564A for ; Wed, 22 Aug 2012 11:34:40 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from mail.zoral.com.ua (mx0.zoral.com.ua [91.193.166.200]) by mx1.freebsd.org (Postfix) with ESMTP id 64DE48FC08 for ; Wed, 22 Aug 2012 11:34:39 +0000 (UTC) Received: from skuns.kiev.zoral.com.ua (localhost [127.0.0.1]) by mail.zoral.com.ua (8.14.2/8.14.2) with ESMTP id q7MBYgjA056795; Wed, 22 Aug 2012 14:34:42 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.14.5/8.14.5) with ESMTP id q7MBYU82002935; Wed, 22 Aug 2012 14:34:30 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.5/8.14.5/Submit) id q7MBYU0f002934; Wed, 22 Aug 2012 14:34:30 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Wed, 22 Aug 2012 14:34:30 +0300 From: Konstantin Belousov To: David Naylor Message-ID: <20120822113430.GA33100@deviant.kiev.zoral.com.ua> References: <201208220913.48095.naylor.b.david@gmail.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="dPKyTZoWbiJp7FfC" Content-Disposition: inline In-Reply-To: <201208220913.48095.naylor.b.david@gmail.com> User-Agent: Mutt/1.4.2.3i X-Virus-Scanned: clamav-milter 0.95.2 at skuns.kiev.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=-4.0 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on skuns.kiev.zoral.com.ua Cc: freebsd-current@freebsd.org Subject: Re: tar not working in an i386 chroot (getvfsbyname) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 22 Aug 2012 11:34:41 -0000 --dPKyTZoWbiJp7FfC Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Aug 22, 2012 at 09:13:44AM +0200, David Naylor wrote: > Hi, >=20 > While trying to compile FreeBSD 10 packages I encountered this error: > # chroot /scratchpad/freebsd10_i386 tar -cf /dev/null root=20 > tar: getvfsbyname failed: No such file or directory > tar: Error exit delayed from previous errors. >=20 > The kernel does have COMPAT_FREEBSD32 in it. To reproduce this (on an=20 > FreeBSD10/amd64 machine) do: > # cd /usr/src > # make -sj16 buildworld installworld DESTDIR=3D/scratchpad/freebsd10_i386 > # chroot /scratchpad/freebsd10_i386 tar -cf /dev/null root http://lists.freebsd.org/pipermail/freebsd-current/2012-August/035976.html I need somebody to test this before commit. --dPKyTZoWbiJp7FfC Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (FreeBSD) iEYEARECAAYFAlA0w8UACgkQC3+MBN1Mb4j9qwCg4EuOtrJb8rLzLYZXO0OgVOD1 xbMAoIvhFaGWpPjH9QxjjA8GhpzUhR/Q =hT/S -----END PGP SIGNATURE----- --dPKyTZoWbiJp7FfC-- From owner-freebsd-current@FreeBSD.ORG Wed Aug 22 11:38:43 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 668A91065670 for ; Wed, 22 Aug 2012 11:38:43 +0000 (UTC) (envelope-from naylor.b.david@gmail.com) Received: from mail-vb0-f54.google.com (mail-vb0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id 0ED4F8FC16 for ; Wed, 22 Aug 2012 11:38:42 +0000 (UTC) Received: by vbmv11 with SMTP id v11so1180690vbm.13 for ; Wed, 22 Aug 2012 04:38:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=+67cy3U3lQlx4UzqeXTxkDckgyca+PszRSLVWyp860Q=; b=YQ6pea+6icZlBruHj+OAHVxLkuwSPljf6MMIZId37DsWqPqjTwA5pQ+EZubKdUJdj8 Tzmnlb+S/XG4dUYxD7Dl2Qyjwnki2NMqhlgqv0ptGB6OJoiD+jNXCVZj9EopwBQmOFrt WeuIi4cQrKh3frBbXuoL9uYmTiSkA0IMEDi8vhzgI74Lb1xTueeMSxfnaV5q5iKAtIbS RFW3Uz9kY+hoprnWZCYBwA9jeH3gjxYG77T52uAXVTaX/YojBcbjrBnjmebG6B8DVQxc /JEXOW7rvpPXIFJSUFq7+VRj4TqUjV3cJaEQaTcGIqWVthwaCTk9rJSiHUJme6nOLo0B z/kA== MIME-Version: 1.0 Received: by 10.220.157.1 with SMTP id z1mr3331763vcw.12.1345635521412; Wed, 22 Aug 2012 04:38:41 -0700 (PDT) Received: by 10.58.133.201 with HTTP; Wed, 22 Aug 2012 04:38:41 -0700 (PDT) Received: by 10.58.133.201 with HTTP; Wed, 22 Aug 2012 04:38:41 -0700 (PDT) In-Reply-To: <20120822113430.GA33100@deviant.kiev.zoral.com.ua> References: <201208220913.48095.naylor.b.david@gmail.com> <20120822113430.GA33100@deviant.kiev.zoral.com.ua> Date: Wed, 22 Aug 2012 13:38:41 +0200 Message-ID: From: David Naylor To: Konstantin Belousov Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-current@freebsd.org Subject: Re: tar not working in an i386 chroot (getvfsbyname) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 22 Aug 2012 11:38:43 -0000 I'm test it in ~8 hours and report back. On Aug 22, 2012 1:34 PM, "Konstantin Belousov" wrote: > On Wed, Aug 22, 2012 at 09:13:44AM +0200, David Naylor wrote: > > Hi, > > > > While trying to compile FreeBSD 10 packages I encountered this error: > > # chroot /scratchpad/freebsd10_i386 tar -cf /dev/null root > > tar: getvfsbyname failed: No such file or directory > > tar: Error exit delayed from previous errors. > > > > The kernel does have COMPAT_FREEBSD32 in it. To reproduce this (on an > > FreeBSD10/amd64 machine) do: > > # cd /usr/src > > # make -sj16 buildworld installworld DESTDIR=/scratchpad/freebsd10_i386 > > # chroot /scratchpad/freebsd10_i386 tar -cf /dev/null root > > http://lists.freebsd.org/pipermail/freebsd-current/2012-August/035976.html > > I need somebody to test this before commit. > From owner-freebsd-current@FreeBSD.ORG Wed Aug 22 11:41:59 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 106321065677 for ; Wed, 22 Aug 2012 11:41:59 +0000 (UTC) (envelope-from luigi@onelab2.iet.unipi.it) Received: from onelab2.iet.unipi.it (onelab2.iet.unipi.it [131.114.59.238]) by mx1.freebsd.org (Postfix) with ESMTP id C44958FC18 for ; Wed, 22 Aug 2012 11:41:58 +0000 (UTC) Received: by onelab2.iet.unipi.it (Postfix, from userid 275) id A6DCA7300A; Wed, 22 Aug 2012 14:01:05 +0200 (CEST) Date: Wed, 22 Aug 2012 14:01:05 +0200 From: Luigi Rizzo To: current@freebsd.org Message-ID: <20120822120105.GA63763@onelab2.iet.unipi.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.3i Cc: Subject: less aggressive contigmalloc ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 22 Aug 2012 11:41:59 -0000 I am trying to make netmap adapt the amount of memory it allocates to what is available. At its core, it uses contigmalloc() with small chunks (even down to 1 page) to fetch memory. Problem is, i notice that before failing, contigmalloc() tries to swap out some processes (effectively killing them because i have no swap configured in my picobsd image). This happens with both M_WAITOK and M_NOWAIT, the difference is only in the number of retries it does -- see e.g. sys/vm/vm_kern.c :: kmem_alloc_contig() where it retries once for M_NOWAIT and 3 times for M_WAITOK. I wonder if there is a way to make contigmalloc less aggressive and fail without killing those innocent processes ? cheers luigi From owner-freebsd-current@FreeBSD.ORG Wed Aug 22 12:28:35 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B8AB41065672 for ; Wed, 22 Aug 2012 12:28:35 +0000 (UTC) (envelope-from freebsd-current@m.gmane.org) Received: from plane.gmane.org (plane.gmane.org [80.91.229.3]) by mx1.freebsd.org (Postfix) with ESMTP id 62A248FC1A for ; Wed, 22 Aug 2012 12:28:35 +0000 (UTC) Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1T4A2r-0002z3-T9 for freebsd-current@freebsd.org; Wed, 22 Aug 2012 14:28:25 +0200 Received: from lara.cc.fer.hr ([161.53.72.113]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 22 Aug 2012 14:28:25 +0200 Received: from ivoras by lara.cc.fer.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 22 Aug 2012 14:28:25 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-current@freebsd.org From: Ivan Voras Date: Wed, 22 Aug 2012 14:27:52 +0200 Lines: 52 Message-ID: References: <20120820194313.GC23607@ithaqua.etoilebsd.net> <20120821132643.GE37262@felucia.tataz.chchile.org> <20120821134623.GH5044@ithaqua.etoilebsd.net> <5033D0C0.4030805@FreeBSD.org> <20120821190500.GA46595@ithaqua.etoilebsd.net> <5033E39C.3060700@FreeBSD.org> <20120821194208.GC46595@ithaqua.etoilebsd.net> <5033E6BA.8080309@FreeBSD.org> <5033EC58.3000801@FreeBSD.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigBEC195413E04A1A5B8F3DBE1" X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: lara.cc.fer.hr User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:10.0) Gecko/20120213 Thunderbird/10.0 In-Reply-To: <5033EC58.3000801@FreeBSD.org> X-Enigmail-Version: 1.3.5 Subject: Re: pkgng 1.0 release schedule, and HEAD switch to pkgng by default schedule X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 22 Aug 2012 12:28:35 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigBEC195413E04A1A5B8F3DBE1 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 21/08/2012 22:15, Doug Barton wrote: > And in this case, it doesn't matter how awesome the new tools are, they= > are a MAJOR paradigm shift for how users interact with ports, and we ar= e Unless I've missed something, pkgng is actually *zero* paradigm shift for users familiar with *ports*, and here's why: people using ports can and will continue to use ports the way they are used to. AFAIK, the infrastructure which registers port installation is already there and there are also patches for portupgrade and portmaster which make them interact nicely with the new package database. The only important aspect of this is that the actual package database format changed (IMO, immensely for the better) and there are several other port management utilities which may need to be changed. People who got used to manually altering the old text-based package database will learn either not to do it anymore, since whole classes of errors have now become impossible to have, or learn how to do it with the new format.= Can you explain what you mean as the "paradigm shift" for ports users her= e? OTOH, people using *binary packages* (the very few and miserable users that they are since the old binary package infrastructure has sucked for the last decade or so), will get their world turned upside down, but for the better, and hopefully grow in numbers. --------------enigBEC195413E04A1A5B8F3DBE1 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.0.19 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlA00FAACgkQ/QjVBj3/HSyh/gCgg4LFb6NrYNtb7/anOM4TsLnq Cl4AnApi/u0sEPxfWjHcfSyJj2XS3jsm =wOdV -----END PGP SIGNATURE----- --------------enigBEC195413E04A1A5B8F3DBE1-- From owner-freebsd-current@FreeBSD.ORG Wed Aug 22 12:46:20 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7CA65106566B; Wed, 22 Aug 2012 12:46:20 +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 4E5F08FC0C; Wed, 22 Aug 2012 12:46:20 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 9B340B97D; Wed, 22 Aug 2012 08:46:19 -0400 (EDT) From: John Baldwin To: Slawa Olhovchenkov Date: Wed, 22 Aug 2012 08:43:52 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110714-p17; KDE/4.5.5; amd64; ; ) References: <20120821095527.GA33206@hell.ukr.net> <201208211725.23381.jhb@freebsd.org> <20120821231630.GF88729@zxy.spb.ru> In-Reply-To: <20120821231630.GF88729@zxy.spb.ru> MIME-Version: 1.0 Content-Type: Text/Plain; charset="koi8-r" Content-Transfer-Encoding: quoted-printable Message-Id: <201208220843.52847.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Wed, 22 Aug 2012 08:46:19 -0400 (EDT) Cc: Garrett Cooper , freebsd-current@freebsd.org, lev@freebsd.org, current@freebsd.org, Peter Jeremy Subject: Re: r239356: does it mean, that synchronous dhcp and dhcplcinet with disabled devd gone? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 22 Aug 2012 12:46:20 -0000 On Tuesday, August 21, 2012 7:16:30 pm Slawa Olhovchenkov wrote: > On Tue, Aug 21, 2012 at 05:25:23PM -0400, John Baldwin wrote: >=20 > > On Tuesday, August 21, 2012 9:34:31 am John Baldwin wrote: > > > On Tuesday, August 21, 2012 7:53:08 am Lev Serebryakov wrote: > > > > Hello, Garrett. > > > > You wrote 21 =C1=D7=C7=D5=D3=D4=C1 2012 =C7., 15:40:35: > > > >=20 > > > > GC>> Try reverting r239356 -- if that works, then please let jhb@ k= now. > > > > LS> I'm confused by this commit, because it seems (from comment = alone), > > > > LS> that dhclient will not work without devd anymore (with "synch= ronous > > > > LS> dhcp" option in rc.conf). > > > > LS> Am I right? > > > > And if I'm right about understanding what this change does, it is > > > > POLA violation for sure. Both consequences: unable to use dhcclient > > > > without devd (user will need to restart it by hands after each cab= le > > > > unplugging event) and removing IP address from interface on cable > > > > unplugging or other interface down event but before lease is expir= ed. > > > >=20 > > > > If I'm right in understanding this commit, I vote to back it out = and > > > > find better solution, may be, two new options: one to remove IP and > > > > one to exit on interface down. And default behavior should be OLD > > > > ONE about IP address in any case and OLD ONE about exit in case wh= en > > > > dhclient isn't started by devd, but by rc scripts directly. > > >=20 > > > Humm. devd is the more common case, and we explicitly don't use devd= to start=20 > > > dhclient on boot even when devd is enabled (so out of the box dhcp wo= uld first=20 > > > be started by rc, but would be restarted by devd). > > >=20 > > > Another option is to rework dhclient to work like it does on OpenBSD = where it > > > renews its lease if the link bounces, but to not exit when the link g= oes down. =20 > > > That case would fix the currently broken case that you unplug your ca= ble, take=20 > > > your laptop over to another network (e.g. take it home if suspend/res= ume=20 > > > works), then plug it back in and are still stuck with your old IP. > >=20 > > Ok, this is what I came up with, somewhat loosely based on OpenBSD's dh= client. > > I tested that it survives the following: > >=20 > > - Unplugging/replugging does not kill an existing ssh session > > - Using ifconfig down/up does not kill an existing ssh session > > - Plugging into a different network does cause dhclient to negotiate > > a new lease on the new network >=20 > Assign address on interface manualy cause exiting dhcpclient? Hmm, it does. Is that by design? That seems to be the old behavior of the client from my reading of the code as well. =2D-=20 John Baldwin From owner-freebsd-current@FreeBSD.ORG Wed Aug 22 12:46:20 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7CA65106566B; Wed, 22 Aug 2012 12:46:20 +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 4E5F08FC0C; Wed, 22 Aug 2012 12:46:20 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 9B340B97D; Wed, 22 Aug 2012 08:46:19 -0400 (EDT) From: John Baldwin To: Slawa Olhovchenkov Date: Wed, 22 Aug 2012 08:43:52 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110714-p17; KDE/4.5.5; amd64; ; ) References: <20120821095527.GA33206@hell.ukr.net> <201208211725.23381.jhb@freebsd.org> <20120821231630.GF88729@zxy.spb.ru> In-Reply-To: <20120821231630.GF88729@zxy.spb.ru> MIME-Version: 1.0 Content-Type: Text/Plain; charset="koi8-r" Content-Transfer-Encoding: quoted-printable Message-Id: <201208220843.52847.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Wed, 22 Aug 2012 08:46:19 -0400 (EDT) Cc: Garrett Cooper , freebsd-current@freebsd.org, lev@freebsd.org, current@freebsd.org, Peter Jeremy Subject: Re: r239356: does it mean, that synchronous dhcp and dhcplcinet with disabled devd gone? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 22 Aug 2012 12:46:20 -0000 On Tuesday, August 21, 2012 7:16:30 pm Slawa Olhovchenkov wrote: > On Tue, Aug 21, 2012 at 05:25:23PM -0400, John Baldwin wrote: >=20 > > On Tuesday, August 21, 2012 9:34:31 am John Baldwin wrote: > > > On Tuesday, August 21, 2012 7:53:08 am Lev Serebryakov wrote: > > > > Hello, Garrett. > > > > You wrote 21 =C1=D7=C7=D5=D3=D4=C1 2012 =C7., 15:40:35: > > > >=20 > > > > GC>> Try reverting r239356 -- if that works, then please let jhb@ k= now. > > > > LS> I'm confused by this commit, because it seems (from comment = alone), > > > > LS> that dhclient will not work without devd anymore (with "synch= ronous > > > > LS> dhcp" option in rc.conf). > > > > LS> Am I right? > > > > And if I'm right about understanding what this change does, it is > > > > POLA violation for sure. Both consequences: unable to use dhcclient > > > > without devd (user will need to restart it by hands after each cab= le > > > > unplugging event) and removing IP address from interface on cable > > > > unplugging or other interface down event but before lease is expir= ed. > > > >=20 > > > > If I'm right in understanding this commit, I vote to back it out = and > > > > find better solution, may be, two new options: one to remove IP and > > > > one to exit on interface down. And default behavior should be OLD > > > > ONE about IP address in any case and OLD ONE about exit in case wh= en > > > > dhclient isn't started by devd, but by rc scripts directly. > > >=20 > > > Humm. devd is the more common case, and we explicitly don't use devd= to start=20 > > > dhclient on boot even when devd is enabled (so out of the box dhcp wo= uld first=20 > > > be started by rc, but would be restarted by devd). > > >=20 > > > Another option is to rework dhclient to work like it does on OpenBSD = where it > > > renews its lease if the link bounces, but to not exit when the link g= oes down. =20 > > > That case would fix the currently broken case that you unplug your ca= ble, take=20 > > > your laptop over to another network (e.g. take it home if suspend/res= ume=20 > > > works), then plug it back in and are still stuck with your old IP. > >=20 > > Ok, this is what I came up with, somewhat loosely based on OpenBSD's dh= client. > > I tested that it survives the following: > >=20 > > - Unplugging/replugging does not kill an existing ssh session > > - Using ifconfig down/up does not kill an existing ssh session > > - Plugging into a different network does cause dhclient to negotiate > > a new lease on the new network >=20 > Assign address on interface manualy cause exiting dhcpclient? Hmm, it does. Is that by design? That seems to be the old behavior of the client from my reading of the code as well. =2D-=20 John Baldwin From owner-freebsd-current@FreeBSD.ORG Wed Aug 22 12:51:50 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E39681065673; Wed, 22 Aug 2012 12:51:50 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) by mx1.freebsd.org (Postfix) with ESMTP id 94A958FC26; Wed, 22 Aug 2012 12:51:50 +0000 (UTC) Received: from slw by zxy.spb.ru with local (Exim 4.69 (FreeBSD)) (envelope-from ) id 1T4ARq-000IlI-8E; Wed, 22 Aug 2012 16:54:14 +0400 Date: Wed, 22 Aug 2012 16:54:14 +0400 From: Slawa Olhovchenkov To: John Baldwin Message-ID: <20120822125414.GX98910@zxy.spb.ru> References: <20120821095527.GA33206@hell.ukr.net> <201208211725.23381.jhb@freebsd.org> <20120821231630.GF88729@zxy.spb.ru> <201208220843.52847.jhb@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <201208220843.52847.jhb@freebsd.org> User-Agent: Mutt/1.5.21 (2010-09-15) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false Cc: Garrett Cooper , freebsd-current@freebsd.org, lev@freebsd.org, current@freebsd.org, Peter Jeremy Subject: Re: r239356: does it mean, that synchronous dhcp and dhcplcinet with disabled devd gone? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 22 Aug 2012 12:51:51 -0000 On Wed, Aug 22, 2012 at 08:43:52AM -0400, John Baldwin wrote: > On Tuesday, August 21, 2012 7:16:30 pm Slawa Olhovchenkov wrote: > > On Tue, Aug 21, 2012 at 05:25:23PM -0400, John Baldwin wrote: > > > > > On Tuesday, August 21, 2012 9:34:31 am John Baldwin wrote: > > > > On Tuesday, August 21, 2012 7:53:08 am Lev Serebryakov wrote: > > > > > Hello, Garrett. > > > > > You wrote 21 Á×ÇÕÓÔÁ 2012 Ç., 15:40:35: > > > > > > > > > > GC>> Try reverting r239356 -- if that works, then please let jhb@ know. > > > > > LS> I'm confused by this commit, because it seems (from comment alone), > > > > > LS> that dhclient will not work without devd anymore (with "synchronous > > > > > LS> dhcp" option in rc.conf). > > > > > LS> Am I right? > > > > > And if I'm right about understanding what this change does, it is > > > > > POLA violation for sure. Both consequences: unable to use dhcclient > > > > > without devd (user will need to restart it by hands after each cable > > > > > unplugging event) and removing IP address from interface on cable > > > > > unplugging or other interface down event but before lease is expired. > > > > > > > > > > If I'm right in understanding this commit, I vote to back it out and > > > > > find better solution, may be, two new options: one to remove IP and > > > > > one to exit on interface down. And default behavior should be OLD > > > > > ONE about IP address in any case and OLD ONE about exit in case when > > > > > dhclient isn't started by devd, but by rc scripts directly. > > > > > > > > Humm. devd is the more common case, and we explicitly don't use devd to start > > > > dhclient on boot even when devd is enabled (so out of the box dhcp would first > > > > be started by rc, but would be restarted by devd). > > > > > > > > Another option is to rework dhclient to work like it does on OpenBSD where it > > > > renews its lease if the link bounces, but to not exit when the link goes down. > > > > That case would fix the currently broken case that you unplug your cable, take > > > > your laptop over to another network (e.g. take it home if suspend/resume > > > > works), then plug it back in and are still stuck with your old IP. > > > > > > Ok, this is what I came up with, somewhat loosely based on OpenBSD's dhclient. > > > I tested that it survives the following: > > > > > > - Unplugging/replugging does not kill an existing ssh session > > > - Using ifconfig down/up does not kill an existing ssh session > > > - Plugging into a different network does cause dhclient to negotiate > > > a new lease on the new network > > > > Assign address on interface manualy cause exiting dhcpclient? > > Hmm, it does. Is that by design? That seems to be the old behavior of the > client from my reading of the code as well. I am don't know, but this is comfortable. It is not desirable lost this behavior. From owner-freebsd-current@FreeBSD.ORG Wed Aug 22 12:51:50 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E39681065673; Wed, 22 Aug 2012 12:51:50 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) by mx1.freebsd.org (Postfix) with ESMTP id 94A958FC26; Wed, 22 Aug 2012 12:51:50 +0000 (UTC) Received: from slw by zxy.spb.ru with local (Exim 4.69 (FreeBSD)) (envelope-from ) id 1T4ARq-000IlI-8E; Wed, 22 Aug 2012 16:54:14 +0400 Date: Wed, 22 Aug 2012 16:54:14 +0400 From: Slawa Olhovchenkov To: John Baldwin Message-ID: <20120822125414.GX98910@zxy.spb.ru> References: <20120821095527.GA33206@hell.ukr.net> <201208211725.23381.jhb@freebsd.org> <20120821231630.GF88729@zxy.spb.ru> <201208220843.52847.jhb@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <201208220843.52847.jhb@freebsd.org> User-Agent: Mutt/1.5.21 (2010-09-15) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false Cc: Garrett Cooper , freebsd-current@freebsd.org, lev@freebsd.org, current@freebsd.org, Peter Jeremy Subject: Re: r239356: does it mean, that synchronous dhcp and dhcplcinet with disabled devd gone? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 22 Aug 2012 12:51:51 -0000 On Wed, Aug 22, 2012 at 08:43:52AM -0400, John Baldwin wrote: > On Tuesday, August 21, 2012 7:16:30 pm Slawa Olhovchenkov wrote: > > On Tue, Aug 21, 2012 at 05:25:23PM -0400, John Baldwin wrote: > > > > > On Tuesday, August 21, 2012 9:34:31 am John Baldwin wrote: > > > > On Tuesday, August 21, 2012 7:53:08 am Lev Serebryakov wrote: > > > > > Hello, Garrett. > > > > > You wrote 21 Á×ÇÕÓÔÁ 2012 Ç., 15:40:35: > > > > > > > > > > GC>> Try reverting r239356 -- if that works, then please let jhb@ know. > > > > > LS> I'm confused by this commit, because it seems (from comment alone), > > > > > LS> that dhclient will not work without devd anymore (with "synchronous > > > > > LS> dhcp" option in rc.conf). > > > > > LS> Am I right? > > > > > And if I'm right about understanding what this change does, it is > > > > > POLA violation for sure. Both consequences: unable to use dhcclient > > > > > without devd (user will need to restart it by hands after each cable > > > > > unplugging event) and removing IP address from interface on cable > > > > > unplugging or other interface down event but before lease is expired. > > > > > > > > > > If I'm right in understanding this commit, I vote to back it out and > > > > > find better solution, may be, two new options: one to remove IP and > > > > > one to exit on interface down. And default behavior should be OLD > > > > > ONE about IP address in any case and OLD ONE about exit in case when > > > > > dhclient isn't started by devd, but by rc scripts directly. > > > > > > > > Humm. devd is the more common case, and we explicitly don't use devd to start > > > > dhclient on boot even when devd is enabled (so out of the box dhcp would first > > > > be started by rc, but would be restarted by devd). > > > > > > > > Another option is to rework dhclient to work like it does on OpenBSD where it > > > > renews its lease if the link bounces, but to not exit when the link goes down. > > > > That case would fix the currently broken case that you unplug your cable, take > > > > your laptop over to another network (e.g. take it home if suspend/resume > > > > works), then plug it back in and are still stuck with your old IP. > > > > > > Ok, this is what I came up with, somewhat loosely based on OpenBSD's dhclient. > > > I tested that it survives the following: > > > > > > - Unplugging/replugging does not kill an existing ssh session > > > - Using ifconfig down/up does not kill an existing ssh session > > > - Plugging into a different network does cause dhclient to negotiate > > > a new lease on the new network > > > > Assign address on interface manualy cause exiting dhcpclient? > > Hmm, it does. Is that by design? That seems to be the old behavior of the > client from my reading of the code as well. I am don't know, but this is comfortable. It is not desirable lost this behavior. From owner-freebsd-current@FreeBSD.ORG Wed Aug 22 13:05:39 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 40CE2106564A for ; Wed, 22 Aug 2012 13:05:39 +0000 (UTC) (envelope-from utisoft@gmail.com) Received: from mail-bk0-f54.google.com (mail-bk0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id B95A98FC14 for ; Wed, 22 Aug 2012 13:05:38 +0000 (UTC) Received: by bkcje9 with SMTP id je9so864751bkc.13 for ; Wed, 22 Aug 2012 06:05:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=QJkpUWFAbIrfzu/qcvhJNWYgBeOHnbimHBVlzB34yxM=; b=LHwC0MRw7MwBi3ZPF8LyvigxMgoupRVnV5qtkaiZlUCXE44FsZgCElJWMyVw0Nq+fm lePwWGRGidgCJL5HNTXGYZRfc3gmMmGO8DbkgkveMVaV6/fJStRzuO9P3zUhjioqTEMw hu9slUNp4ajgdGUS/kbjwWVg6agdLSuQJKu5gabpRqk4EQRqTnFsRts/F1btNzXBb+RX dwDWUsM+MMrsaR2aOr6P018cXikYXscxtwoRFEgdpaTJlGouKpdwxqW9qK0JSEuB/A83 Euc2DkwgNVXAWgYbgvl9LZ+axsdwNYjgMrTAyQXsN4bWUReIsGni7VZ4t1seCBCsLhuH 1txQ== Received: by 10.205.118.138 with SMTP id fq10mr6599259bkc.58.1345640732452; Wed, 22 Aug 2012 06:05:32 -0700 (PDT) MIME-Version: 1.0 Sender: utisoft@gmail.com Received: by 10.204.10.141 with HTTP; Wed, 22 Aug 2012 06:05:01 -0700 (PDT) In-Reply-To: <503487DE.3050807@zedat.fu-berlin.de> References: <50337752.8070707@zedat.fu-berlin.de> <1345582381.1632.6.camel@Nokia-N900-42-11> <503487DE.3050807@zedat.fu-berlin.de> From: Chris Rees Date: Wed, 22 Aug 2012 14:05:01 +0100 X-Google-Sender-Auth: RfFc_Z6OUHtFXGhfI8hjopVXGd0 Message-ID: To: "O. Hartmann" Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: =?ISO-8859-1?Q?Bernhard_Fr=F6hlich?= , Current FreeBSD Subject: Re: FreeBSD 10.0-CURRENT r239477 doesn't compile: virtualbox-ose-kmod-4.1.18_1 is marked as broken: Does not compile on FreeBSD < 8.2. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 22 Aug 2012 13:05:39 -0000 On 22 August 2012 08:18, O. Hartmann wrote: > Am 08/21/12 22:53, schrieb Bernhard Fr=F6hlich: >> On Di., 21. Aug. 2012 13:56:02 CEST, O. Hartmann wrote: >> >>> Today I ran into a problem with FreeBSD 10.0-CURRENT #0 r239477 >>> recompiling the VBox kernel module: >>> >>> =3D=3D=3D> Cleaning for virtualbox-ose-kmod-4.1.18_1 >>> =3D=3D=3D> virtualbox-ose-kmod-4.1.18_1 is marked as broken: Does not= compile >>> on FreeBSD < 8.2. >>> *** [all] Error code 1 >>> >>> Stop in /usr/ports/emulators/virtualbox-ose-kmod. >>> >>> The port compiled prior to the updates of today. >>> >>> oh >> >> What is the question? We have deprecated < 8.2 almost five months ago be= cause of the memobj r0 rewrite. You're the first who complains about this s= o I'm pretty sure it was the correct decision to move forward. Please also = keep in mind that 8.1 is already EOL. >> > > I do not understand your complains about my mail to the list. For your > information: I'm on FreeBSD 10.0-CURRENT and this seems, as far as I > know, considered not to be deprecated by now. If I'm wrong in that, sorry= . Can you give us the output of make -C /usr/ports/emulators/virtualbox-ose-kmod -VOSVERSION please? I think your version of sys/param.h could be out of date. Chris From owner-freebsd-current@FreeBSD.ORG Wed Aug 22 14:02:38 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 433051065672 for ; Wed, 22 Aug 2012 14:02:38 +0000 (UTC) (envelope-from utisoft@gmail.com) Received: from mail-bk0-f54.google.com (mail-bk0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id BA5548FC16 for ; Wed, 22 Aug 2012 14:02:37 +0000 (UTC) Received: by bkcje9 with SMTP id je9so925806bkc.13 for ; Wed, 22 Aug 2012 07:02:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=WRpooNbXXELT0oBIWoL2ASdSVJG+MH5M9zz8KTclzxI=; b=0TFOofFCk7pHrN9ojt/L5tyyUVuWU3+IyYk4IGK8sf0meZQBG7tlaYlVfXrnU5jHg/ RE3ESCpIElwMz2ZGe6j5OYZ8BdAsPKYD5hN0Nc9W3EWTJKKREZsAJ43apwVD5p1QDYgV 03tDpe/PRw+NsEVqvVkGCE49umTo40NYgTUui9UzGsDyjVZic9h6VAWuJeIBmhZdj5TA wkNo0psYiOwWdnWCmuWDQB+HEDLgFGeI/UaHQvw1CXrrrPCnrhJjdAb2AO2mwuyR9Z1y iNLm0rsDCgGkSS2kJbFFM9Tz3Wo0ImqzgCrYK3HBPV4WI7sz+BgggX5+4i6qksa1x1mL rjxw== Received: by 10.204.145.82 with SMTP id c18mr6419804bkv.133.1345644156714; Wed, 22 Aug 2012 07:02:36 -0700 (PDT) MIME-Version: 1.0 Sender: utisoft@gmail.com Received: by 10.204.10.141 with HTTP; Wed, 22 Aug 2012 07:02:06 -0700 (PDT) In-Reply-To: <5034DF8B.102@mail.zedat.fu-berlin.de> References: <50337752.8070707@zedat.fu-berlin.de> <1345582381.1632.6.camel@Nokia-N900-42-11> <503487DE.3050807@zedat.fu-berlin.de> <5034DF8B.102@mail.zedat.fu-berlin.de> From: Chris Rees Date: Wed, 22 Aug 2012 15:02:06 +0100 X-Google-Sender-Auth: YrWYlclt0cHw7X0mpUYEV2NfkUc Message-ID: To: "O. Hartmann" Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: =?ISO-8859-1?Q?Bernhard_Fr=F6hlich?= , Current FreeBSD , "O. Hartmann" Subject: Re: FreeBSD 10.0-CURRENT r239477 doesn't compile: virtualbox-ose-kmod-4.1.18_1 is marked as broken: Does not compile on FreeBSD < 8.2. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 22 Aug 2012 14:02:38 -0000 On 22 August 2012 14:32, O. Hartmann wro= te: > On 08/22/12 15:05, Chris Rees wrote: >> On 22 August 2012 08:18, O. Hartmann wrote= : >>> Am 08/21/12 22:53, schrieb Bernhard Fr=F6hlich: >>>> On Di., 21. Aug. 2012 13:56:02 CEST, O. Hartmann wrote: >>>> >>>>> Today I ran into a problem with FreeBSD 10.0-CURRENT #0 r239477 >>>>> recompiling the VBox kernel module: >>>>> >>>>> =3D=3D=3D> Cleaning for virtualbox-ose-kmod-4.1.18_1 >>>>> =3D=3D=3D> virtualbox-ose-kmod-4.1.18_1 is marked as broken: Does n= ot compile >>>>> on FreeBSD < 8.2. >>>>> *** [all] Error code 1 >>>>> >>>>> Stop in /usr/ports/emulators/virtualbox-ose-kmod. >>>>> >>>>> The port compiled prior to the updates of today. >>>>> >>>>> oh >>>> >>>> What is the question? We have deprecated < 8.2 almost five months ago = because of the memobj r0 rewrite. You're the first who complains about this= so I'm pretty sure it was the correct decision to move forward. Please als= o keep in mind that 8.1 is already EOL. >>>> >>> >>> I do not understand your complains about my mail to the list. For your >>> information: I'm on FreeBSD 10.0-CURRENT and this seems, as far as I >>> know, considered not to be deprecated by now. If I'm wrong in that, sor= ry. >> >> Can you give us the output of make -C >> /usr/ports/emulators/virtualbox-ose-kmod -VOSVERSION please? > > 1000017 > >> >> I think your version of sys/param.h could be out of date. >> >> Chris > > > > As soon as I'm sitting in front of the machine again. But I doubt that > the sys/param.h is out of date, since that box has been recompiling > FreeBSD 10.0-CURRENT now for almost every day. Hm, does that mean that the output you gave me earlier was not from the same machine? > When the problem occured, the change to CLANG 3.2-Beta has just been > introduced, installed with "make buildworld installkernel". This > procedere also triggers (via /etc/src.conf) > > PORTS_MODULES=3D "x11/nvidia-driver" > PORTS_MODULES+=3D "emulators/virtualbox-ose-kmod" Please remove the quotes! [1] > the build of the modules for the nvidia GPU and Vbox kernel module. > > Thanks for your response, Something really weird is happening here. All that is happening is that the Makefile is testing against OSVERSION; .if ${OSVERSION} < 802000 BROKEN=3D Does not compile on FreeBSD < 8.2 .endif Since the result from make -VOSVERSION shows that your OSVERSION is indeed above 802000, I am completely at a loss as to what's going on :( Chris [1] http://www.bayofrum.net/~crees/scripts/dont-quote.mk From owner-freebsd-current@FreeBSD.ORG Wed Aug 22 14:09:43 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E4EAE106566C for ; Wed, 22 Aug 2012 14:09:43 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from mail-pz0-f54.google.com (mail-pz0-f54.google.com [209.85.210.54]) by mx1.freebsd.org (Postfix) with ESMTP id A6DAE8FC0C for ; Wed, 22 Aug 2012 14:09:43 +0000 (UTC) Received: by dadr6 with SMTP id r6so822390dad.13 for ; Wed, 22 Aug 2012 07:09:43 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=sender:subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer :x-gm-message-state; bh=wGmqACA2civvRf2mSnmYb8XtWstig29MhQrY1bSC358=; b=Xv/tA3N0bON/+ZG3MEVSLQdrQ+gpzRjHCN93bZSCj1GM9goIcjZzSugamg5N6Kv6x6 IJRDkgduiZ2/G+unp0vlszfI7mlc6yJwnjVr89Azqqve72eHbtUgUXfYFzTX6H45zS4W vi+yeBfwQCPuDfq5P4U5jwgzNuUOx6eISWu9KdOti4aVfa5YIGhBLWhgIxGPH593Eojd K3vK+pP/8vFmevNBJYWivJveS2zX5VU+vAD9MCjCnUPdLpGhFuzhIM+U8/BxF2TO41VI Q9QjlDjQp+i/OhUKVFuBhs6MVikyrBk6LGUq6B/A0GHFi63vhzULi0hEb34Ux6pBJslL Kz5Q== Received: by 10.66.87.138 with SMTP id ay10mr46301601pab.38.1345644583411; Wed, 22 Aug 2012 07:09:43 -0700 (PDT) Received: from [10.0.0.63] (50-78-194-198-static.hfc.comcastbusiness.net. [50.78.194.198]) by mx.google.com with ESMTPS id oj8sm3782308pbb.54.2012.08.22.07.09.37 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 22 Aug 2012 07:09:42 -0700 (PDT) Sender: Warner Losh Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii From: Warner Losh In-Reply-To: Date: Wed, 22 Aug 2012 08:09:34 -0600 Content-Transfer-Encoding: quoted-printable Message-Id: <1EFE819C-1360-4596-9241-45542D71EA7A@bsdimp.com> References: <20120820194313.GC23607@ithaqua.etoilebsd.net> <20120821132643.GE37262@felucia.tataz.chchile.org> <20120821134623.GH5044@ithaqua.etoilebsd.net> <5033D0C0.4030805@FreeBSD.org> <20120821190500.GA46595@ithaqua.etoilebsd.net> <5033E39C.3060700@FreeBSD.org> <20120821194208.GC46595@ithaqua.etoilebsd.net> <5033E6BA.8080309@FreeBSD.org> <5033EC58.3000801@FreeBSD.org> To: Bjoern A. Zeeb X-Mailer: Apple Mail (2.1084) X-Gm-Message-State: ALoCoQnj/2EGGvgv1vu+G3F+Fan7/NMyF6ECpfNcpdGByI4UWnEO9jdZlKqAZ/+Mx3PH0jnhXoTv Cc: ports@freebsd.org, current@freebsd.org Subject: Re: pkgng 1.0 release schedule, and HEAD switch to pkgng by default schedule X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 22 Aug 2012 14:09:44 -0000 On Aug 21, 2012, at 7:58 PM, Bjoern A. Zeeb wrote: > On Tue, 21 Aug 2012, Doug Barton wrote: >=20 >> I don't think we have ever done a complete replacement of major >> infrastructure in one release. >=20 > You mean like sysinstall can be used as an installer on 9 that would > do something meaningful with the current infrastructure we provide? You understood my oblique sysinstall reference... The 'can't do it in = one release' is a red herring. The current package system is by no = means as good as sysinstall was before it was replaced. The new one is = much better and deserves a shot of 'replace in one' if it proves to be = ready. Anything contrary to that is just obstructionism. Warner From owner-freebsd-current@FreeBSD.ORG Wed Aug 22 15:24:59 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 063F71065670; Wed, 22 Aug 2012 15:24:59 +0000 (UTC) (envelope-from yanegomi@gmail.com) Received: from mail-ob0-f182.google.com (mail-ob0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id A9D838FC08; Wed, 22 Aug 2012 15:24:58 +0000 (UTC) Received: by obbun3 with SMTP id un3so2036538obb.13 for ; Wed, 22 Aug 2012 08:24:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=NQtWX6itN3U6KO0pyGC+AHLQaUA/TinLnBwUXIVw4U0=; b=NbViXQvbDBemDNDhY7bPd1DOLQE9AVIXDPBjSZ2skkR3fSeG16bPgW/8+UKHkLBtu7 86eoWsrCq+GVxrFiC9vSLt0GucaJ5hxHMoVwK/n3izU1hVN2wcYxriJQeKg9Xuz7N2IC J8OBytfIwSG7m1Bv7PrhYgTX38QWiaGVmakZpxL8Vc2aKhVxlslfslyv38Xhd4yqZ0lg 0/+fpJlW3LmR5vC8zn4qJMInzN1eZbk9ntQ+ejqasfeu6ruZZQWp/miTXpx4HJn025cm NZbksmelP0sS2n4265eIvGbqAfnDicyMuvKXpFGLkNtNaiaGlpviBLswrigOKx/gJ4D6 tl/Q== MIME-Version: 1.0 Received: by 10.182.111.39 with SMTP id if7mr15634940obb.56.1345649096343; Wed, 22 Aug 2012 08:24:56 -0700 (PDT) Received: by 10.76.142.201 with HTTP; Wed, 22 Aug 2012 08:24:56 -0700 (PDT) In-Reply-To: References: <50337752.8070707@zedat.fu-berlin.de> <1345582381.1632.6.camel@Nokia-N900-42-11> <503487DE.3050807@zedat.fu-berlin.de> <5034DF8B.102@mail.zedat.fu-berlin.de> Date: Wed, 22 Aug 2012 08:24:56 -0700 Message-ID: From: Garrett Cooper To: Chris Rees Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: "O. Hartmann" , Current FreeBSD , "O. Hartmann" , =?ISO-8859-1?Q?Bernhard_Fr=F6hlich?= Subject: Re: FreeBSD 10.0-CURRENT r239477 doesn't compile: virtualbox-ose-kmod-4.1.18_1 is marked as broken: Does not compile on FreeBSD < 8.2. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 22 Aug 2012 15:24:59 -0000 On Wed, Aug 22, 2012 at 7:02 AM, Chris Rees wrote: > On 22 August 2012 14:32, O. Hartmann w= rote: >> On 08/22/12 15:05, Chris Rees wrote: >>> On 22 August 2012 08:18, O. Hartmann wrot= e: >>>> Am 08/21/12 22:53, schrieb Bernhard Fr=F6hlich: >>>>> On Di., 21. Aug. 2012 13:56:02 CEST, O. Hartmann wrote: >>>>> >>>>>> Today I ran into a problem with FreeBSD 10.0-CURRENT #0 r239477 >>>>>> recompiling the VBox kernel module: >>>>>> >>>>>> =3D=3D=3D> Cleaning for virtualbox-ose-kmod-4.1.18_1 >>>>>> =3D=3D=3D> virtualbox-ose-kmod-4.1.18_1 is marked as broken: Does = not compile >>>>>> on FreeBSD < 8.2. >>>>>> *** [all] Error code 1 >>>>>> >>>>>> Stop in /usr/ports/emulators/virtualbox-ose-kmod. >>>>>> >>>>>> The port compiled prior to the updates of today. >>>>>> >>>>>> oh >>>>> >>>>> What is the question? We have deprecated < 8.2 almost five months ago= because of the memobj r0 rewrite. You're the first who complains about thi= s so I'm pretty sure it was the correct decision to move forward. Please al= so keep in mind that 8.1 is already EOL. >>>>> >>>> >>>> I do not understand your complains about my mail to the list. For your >>>> information: I'm on FreeBSD 10.0-CURRENT and this seems, as far as I >>>> know, considered not to be deprecated by now. If I'm wrong in that, so= rry. >>> >>> Can you give us the output of make -C >>> /usr/ports/emulators/virtualbox-ose-kmod -VOSVERSION please? >> >> 1000017 >> >>> >>> I think your version of sys/param.h could be out of date. >>> >>> Chris >> >> >> >> As soon as I'm sitting in front of the machine again. But I doubt that >> the sys/param.h is out of date, since that box has been recompiling >> FreeBSD 10.0-CURRENT now for almost every day. > > Hm, does that mean that the output you gave me earlier was not from > the same machine? > >> When the problem occured, the change to CLANG 3.2-Beta has just been >> introduced, installed with "make buildworld installkernel". This >> procedere also triggers (via /etc/src.conf) >> >> PORTS_MODULES=3D "x11/nvidia-driver" >> PORTS_MODULES+=3D "emulators/virtualbox-ose-kmod" > > Please remove the quotes! [1] > >> the build of the modules for the nvidia GPU and Vbox kernel module. >> >> Thanks for your response, > > Something really weird is happening here. All that is happening is > that the Makefile is testing against OSVERSION; > > .if ${OSVERSION} < 802000 > BROKEN=3D Does not compile on FreeBSD < 8.2 > .endif > > Since the result from make -VOSVERSION shows that your OSVERSION is > indeed above 802000, I am completely at a loss as to what's going on > :( I think this is the issue that I was referring to earlier that I noted to dougb@ but hadn't gotten an opportunity to repro because I've been busy with other things. What does OSVERSION look like when you run it from make buildkernel (use this patch)? Thanks, -Garrett $ svn diff /usr/src/sys/conf/kern.post.mk Index: /usr/src/sys/conf/kern.post.mk =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 --- /usr/src/sys/conf/kern.post.mk (revision 239292) +++ /usr/src/sys/conf/kern.post.mk (working copy) @@ -61,6 +61,8 @@ OSVERSION=3D${OSRELDATE} \ WRKDIRPREFIX=3D${WRKDIRPREFIX} +.warning "PORTSMODULESENV =3D> ${PORTSMODULESENV}" + # The WRKDIR needs to be cleaned before building, and trying to change the target # with a :C pattern below results in install -> instclean all: From owner-freebsd-current@FreeBSD.ORG Wed Aug 22 17:28:34 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A549F1065670 for ; Wed, 22 Aug 2012 17:28:34 +0000 (UTC) (envelope-from satan@ukr.net) Received: from hell.ukr.net (hell.ukr.net [212.42.67.68]) by mx1.freebsd.org (Postfix) with ESMTP id 3D24B8FC08 for ; Wed, 22 Aug 2012 17:28:33 +0000 (UTC) Received: from satan by hell.ukr.net with local ID 1T4Ej8-000DrS-QF ; Wed, 22 Aug 2012 20:28:22 +0300 Date: Wed, 22 Aug 2012 20:28:22 +0300 From: Vitalij Satanivskij To: YongHyeon PYUN Message-ID: <20120822172822.GA52909@hell.ukr.net> References: <20120821095527.GA33206@hell.ukr.net> <20120821164217.GA45780@hell.ukr.net> <20120821222701.GA94197@server.rulingia.com> <20120822171253.GB3300@michelle.cdnetworks.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20120822171253.GB3300@michelle.cdnetworks.com> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: Vitalij Satanivskij , Peter Jeremy , current@freebsd.org Subject: Re: dhclient cause up/down cycle after 239356 ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 22 Aug 2012 17:28:34 -0000 ok next round :) dhclient updated to Revision 239564 with fxp : Aug 22 20:06:48 home kernel: fxp0: link state changed to DOWN Aug 22 20:06:48 home dhclient: New Subnet Mask (fxp0): 255.255.255.0 Aug 22 20:06:48 home dhclient: New Broadcast Address (fxp0): xx.xx.xx.255 Aug 22 20:06:48 home dhclient: New Routers (fxp0): xx.xx.xx.1 Aug 22 20:06:50 home kernel: fxp0: link state changed to UP Aug 22 20:06:53 home dhclient: New IP Address (fxp0): xx.xx.xx.xx Aug 22 20:06:53 home kernel: fxp0: link state changed to DOWN Aug 22 20:06:53 home dhclient: New Subnet Mask (fxp0): 255.255.255.0 Aug 22 20:06:53 home dhclient: New Broadcast Address (fxp0): xx.xx.xx.255 Aug 22 20:06:53 home dhclient: New Routers (fxp0): xx.xx.xx.xx Aug 22 20:06:55 home kernel: fxp0: link state changed to UP Aug 22 20:07:01 home dhclient: New IP Address (fxp0): xx.xx.xx.xx Aug 22 20:07:01 home kernel: fxp0: link state changed to DOWN Aug 22 20:07:01 home dhclient: New Subnet Mask (fxp0): 255.255.255.0 Aug 22 20:07:01 home dhclient: New Broadcast Address (fxp0): xx.xx.xx.255 Aug 22 20:07:01 home dhclient: New Routers (fxp0): xx.xx.xx.xx Aug 22 20:07:03 home kernel: fxp0: link state changed to UP Aug 22 20:07:07 home dhclient: New IP Address (fxp0): xx.xx.xx.xx Aug 22 20:07:07 home kernel: fxp0: link state changed to DOWN Aug 22 20:07:07 home dhclient: New Subnet Mask (fxp0): 255.255.255.0 Aug 22 20:07:07 home dhclient: New Broadcast Address (fxp0): xx.xx.xx.255 Aug 22 20:07:07 home dhclient: New Routers (fxp0): xx.xx.xx.xx Aug 22 20:07:09 home kernel: fxp0: link state changed to UP Aug 22 20:07:13 home dhclient: New IP Address (fxp0): xx.xx.xx.xx Aug 22 20:07:13 home kernel: fxp0: link state changed to DOWN Aug 22 20:07:13 home dhclient: New Subnet Mask (fxp0): 255.255.255.0 Aug 22 20:07:13 home dhclient: New Broadcast Address (fxp0): xx.xx.xx.255 Aug 22 20:07:13 home dhclient: New Routers (fxp0): xx.xx.xx.xx Aug 22 20:07:15 home kernel: fxp0: link state changed to UP ifconfig show that iface doesn't loose ip adress but, link realy loosed (for example 10 from icmp pachets cannot reach destination) Yes, my problem easy fixed by changed ethernet card to em, but there are meny motherboard with integrated ether's... YongHyeon PYUN wrote: YP> On Wed, Aug 22, 2012 at 08:27:01AM +1000, Peter Jeremy wrote: YP> > On 2012-Aug-21 19:42:17 +0300, Vitalij Satanivskij wrote: YP> > >Look's like dhclient do down/up sequence - YP> > YP> > Not intentionally. YP> > YP> > >Aug 21 19:21:00 home kernel: fxp0: link state changed to UP YP> > >Aug 21 19:21:01 home kernel: fxp0: link state changed to DOWN YP> > >Aug 21 19:21:01 home dhclient: New IP Address (fxp0): xx.xx.xx.xx YP> > >Aug 21 19:21:01 home dhclient: New Subnet Mask (fxp0): 255.255.255.0 YP> > >Aug 21 19:21:01 home dhclient: New Broadcast Address (fxp0): xx.xx.xx.xx YP> > >Aug 21 19:21:01 home dhclient: New Routers (fxp0): xx.xx.xx.xx YP> > >Aug 21 19:21:03 home kernel: fxp0: link state changed to UP YP> > YP> > I can reproduce this behaviour - but only on fxp (i82559 in my case) YP> > NICs. My bge (BCM5750) and rl (RTL8139) NICs do not report the YP> > spurious DOWN/UP. (I don't normally run DHCP on any fxp interfaces, YP> > so I didn't see it during my testing). YP> > YP> > The problem appears to be the YP> > $IFCONFIG $interface inet alias 0.0.0.0 netmask 255.0.0.0 broadcast 255.255.255.255 up YP> > executed by /sbin/dhclient-script during PREINIT. This is making the YP> > fxp NIC reset the link (actually, assigning _any_ IP address to an fxp YP> > NIC causes it to reset the link). The post r239356 dhclient detects YP> YP> This comes from the hardware limitation. Assigning addresses will YP> result in programming multicast filter and fxp(4) controllers YP> require full controller reset to reprogram the multicast filter. YP> YP> > the link going down and exits. YP> > YP> > >Before r239356 iface just doing down/up without dhclient exit and YP> > >everything work fine. YP> > YP> > For you, anyway. Failing to detect link down causes problems for me YP> > because my dhclient was not seeing my cable-modem resets and therefore YP> > failing to reacquire a DHCP lease. YP> > YP> > -- YP> > Peter Jeremy YP> YP> YP> _______________________________________________ YP> freebsd-current@freebsd.org mailing list YP> http://lists.freebsd.org/mailman/listinfo/freebsd-current YP> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" From owner-freebsd-current@FreeBSD.ORG Wed Aug 22 17:52:45 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4F0DB106566B; Wed, 22 Aug 2012 17:52:45 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-wi0-f178.google.com (mail-wi0-f178.google.com [209.85.212.178]) by mx1.freebsd.org (Postfix) with ESMTP id A546B8FC15; Wed, 22 Aug 2012 17:52:44 +0000 (UTC) Received: by wibhr14 with SMTP id hr14so11436wib.13 for ; Wed, 22 Aug 2012 10:52:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=QgYgi/lMhFTcSFqwY68m3olMnuP/6P7kOzFPhjXRF/A=; b=Yng/UZQASlPL+wMwx740hFj5Waj3+n/rOdeqhrk+miVUoJJ9wC+IR6n9pTmWN5wkmz ID5T7lMMoVwGqNmtqRjt3vhz5Dq8vs9qiOXi5QJ0KF0YRqR6k0BxclLyQ0X65tgg2pWl 2N9mhsd+3bSvFL3fePLZm16LqiPb8nAGpGvoVUvr1vMC0j3N0wFGpvvgPKvhVawtkWRK 6k4u8n1bB+KAeWIEm6KDYvXFt3QlbTafhD+VjB1+/VZ+grNz/rii7eTtaaUjkyac/vb0 GxDVJL+Vo9Mpc8HHdJOoFZAEXCS3hmeeRNvYWIEA7bMWXEpi9h5tercyB8lmKYIqZUke N+YQ== MIME-Version: 1.0 Received: by 10.180.106.137 with SMTP id gu9mr7646220wib.20.1345657963304; Wed, 22 Aug 2012 10:52:43 -0700 (PDT) Received: by 10.223.63.76 with HTTP; Wed, 22 Aug 2012 10:52:43 -0700 (PDT) In-Reply-To: <1EFE819C-1360-4596-9241-45542D71EA7A@bsdimp.com> References: <20120820194313.GC23607@ithaqua.etoilebsd.net> <20120821132643.GE37262@felucia.tataz.chchile.org> <20120821134623.GH5044@ithaqua.etoilebsd.net> <5033D0C0.4030805@FreeBSD.org> <20120821190500.GA46595@ithaqua.etoilebsd.net> <5033E39C.3060700@FreeBSD.org> <20120821194208.GC46595@ithaqua.etoilebsd.net> <5033E6BA.8080309@FreeBSD.org> <5033EC58.3000801@FreeBSD.org> <1EFE819C-1360-4596-9241-45542D71EA7A@bsdimp.com> Date: Wed, 22 Aug 2012 10:52:43 -0700 Message-ID: From: Kevin Oberman To: Warner Losh Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: ports@freebsd.org, "Bjoern A. Zeeb" , current@freebsd.org Subject: Re: pkgng 1.0 release schedule, and HEAD switch to pkgng by default schedule X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 22 Aug 2012 17:52:45 -0000 On Wed, Aug 22, 2012 at 7:09 AM, Warner Losh wrote: > > On Aug 21, 2012, at 7:58 PM, Bjoern A. Zeeb wrote: > >> On Tue, 21 Aug 2012, Doug Barton wrote: >> >>> I don't think we have ever done a complete replacement of major >>> infrastructure in one release. >> >> You mean like sysinstall can be used as an installer on 9 that would >> do something meaningful with the current infrastructure we provide? > > You understood my oblique sysinstall reference... The 'can't do it in on= e release' is a red herring. The current package system is by no means as = good as sysinstall was before it was replaced. The new one is much better = and deserves a shot of 'replace in one' if it proves to be ready. Anything= contrary to that is just obstructionism. I don't agree. I know that I am not the only one who uses the pkgdb in internal scripts. While getting rid of pkg_* will be a wonderful thing and, for most of the systems I deal with the switch will happen very soon, a couple will need major re-working to replace the use of the pkgdb. Since these are systems that I usually run either the latest STABLE (RELENG_9 at this time) or CURRENT, this would prevent moving to CURRENT or 10-STABLE if I can't do so and still have the option of sticking with the old system for a while. This is especially true for 1.0, until things like adding SVN revision and (hopefully) options to the DB to make working with a combination of packages and ports reasonable. I can't imagine EVER getting away from building some things from source using ports at any time. Yes, I understand that getting rid of pkg_ will allow things to be done that will be difficult (impossible?) to retrofit into pkg_*, but this is a HUGE change for most admins, much bigger than the sysinstall change as it will mostly impact on systems currently running FreeBSD where sysinstall did not. Please, please be very careful about pulling the life support plug on pkg_*= . --=20 R. Kevin Oberman, Network Engineer E-mail: kob6558@gmail.com From owner-freebsd-current@FreeBSD.ORG Wed Aug 22 18:13:43 2012 Return-Path: Delivered-To: current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 094FF106566B; Wed, 22 Aug 2012 18:13:42 +0000 (UTC) (envelope-from bapt@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 9D3FC8FC14; Wed, 22 Aug 2012 18:13:42 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q7MIDgKl045350; Wed, 22 Aug 2012 18:13:42 GMT (envelope-from bapt@FreeBSD.org) Received: (from bapt@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q7MIDf2o045333; Wed, 22 Aug 2012 18:13:41 GMT (envelope-from bapt@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: bapt set sender to bapt@FreeBSD.org using -f Date: Wed, 22 Aug 2012 20:13:39 +0200 From: Baptiste Daroussin To: Kevin Oberman Message-ID: <20120822181339.GB47706@ithaqua.etoilebsd.net> References: <20120821190500.GA46595@ithaqua.etoilebsd.net> <5033E39C.3060700@FreeBSD.org> <20120821194208.GC46595@ithaqua.etoilebsd.net> <5033E6BA.8080309@FreeBSD.org> <5033EC58.3000801@FreeBSD.org> <1EFE819C-1360-4596-9241-45542D71EA7A@bsdimp.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="zx4FCpZtqtKETZ7O" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Cc: ports@FreeBSD.org, "Bjoern A. Zeeb" , current@FreeBSD.org, Warner Losh Subject: Re: pkgng 1.0 release schedule, and HEAD switch to pkgng by default schedule X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 22 Aug 2012 18:13:43 -0000 --zx4FCpZtqtKETZ7O Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Aug 22, 2012 at 10:52:43AM -0700, Kevin Oberman wrote: > On Wed, Aug 22, 2012 at 7:09 AM, Warner Losh wrote: > > > > On Aug 21, 2012, at 7:58 PM, Bjoern A. Zeeb wrote: > > > >> On Tue, 21 Aug 2012, Doug Barton wrote: > >> > >>> I don't think we have ever done a complete replacement of major > >>> infrastructure in one release. > >> > >> You mean like sysinstall can be used as an installer on 9 that would > >> do something meaningful with the current infrastructure we provide? > > > > You understood my oblique sysinstall reference... The 'can't do it in = one release' is a red herring. The current package system is by no means a= s good as sysinstall was before it was replaced. The new one is much bette= r and deserves a shot of 'replace in one' if it proves to be ready. Anythi= ng contrary to that is just obstructionism. >=20 > I don't agree. I know that I am not the only one who uses the pkgdb in > internal scripts. While getting rid of pkg_* will be a wonderful thing > and, for most of the systems I deal with the switch will happen very > soon, a couple will need major re-working to replace the use of the > pkgdb. Since these are systems that I usually run either the latest > STABLE (RELENG_9 at this time) or CURRENT, this would prevent moving > to CURRENT or 10-STABLE if I can't do so and still have the option of > sticking with the old system for a while. This is especially true for > 1.0, until things like adding SVN revision and (hopefully) options to > the DB to make working with a combination of packages and ports > reasonable. I can't imagine EVER getting away from building some > things from source using ports at any time. >=20 > Yes, I understand that getting rid of pkg_ will allow things to be > done that will be difficult (impossible?) to retrofit into pkg_*, but > this is a HUGE change for most admins, much bigger than the sysinstall > change as it will mostly impact on systems currently running FreeBSD > where sysinstall did not. >=20 > Please, please be very careful about pulling the life support plug on pkg= _*. > --=20 > R. Kevin Oberman, Network Engineer > E-mail: kob6558@gmail.com > _______________________________________________ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" That is the reason why I updated today the pkg_install ports so that people= will be able to keep an up to date pkg_* tools for the time the ports tree will support it, (meaning at least EOL of 9.1 and EOL of 8.3) regards, Bapt --zx4FCpZtqtKETZ7O Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEARECAAYFAlA1IVMACgkQ8kTtMUmk6Ew/WwCgo1cPO+O1d7cGQ+Zcz3MnLx0B ud8AnjvfAun77oen7YUPnjwtd/ir7Sop =x0t2 -----END PGP SIGNATURE----- --zx4FCpZtqtKETZ7O-- From owner-freebsd-current@FreeBSD.ORG Wed Aug 22 18:38:20 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3C9851065674; Wed, 22 Aug 2012 18:38: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 A5D798FC0A; Wed, 22 Aug 2012 18:38:19 +0000 (UTC) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost1.zedat.fu-berlin.de (Exim 4.69) with esmtp (envelope-from ) id <1T4Foo-00012e-Kb>; Wed, 22 Aug 2012 20:38:18 +0200 Received: from e178003168.adsl.alicedsl.de ([85.178.3.168] helo=thor.walstatt.dyndns.org) by inpost2.zedat.fu-berlin.de (Exim 4.69) with esmtpsa (envelope-from ) id <1T4Foo-00070M-Eq>; Wed, 22 Aug 2012 20:38:18 +0200 Message-ID: <50352715.3010909@zedat.fu-berlin.de> Date: Wed, 22 Aug 2012 20:38:13 +0200 From: "O. Hartmann" User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:14.0) Gecko/20120810 Thunderbird/14.0 MIME-Version: 1.0 To: Chris Rees References: <50337752.8070707@zedat.fu-berlin.de> <1345582381.1632.6.camel@Nokia-N900-42-11> <503487DE.3050807@zedat.fu-berlin.de> <5034DF8B.102@mail.zedat.fu-berlin.de> In-Reply-To: X-Enigmail-Version: 1.4.3 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enigB68366E0D10F83B59EB99EF5" X-Originating-IP: 85.178.3.168 Cc: =?ISO-8859-1?Q?hard_Fr=F6hlich?= , "O. Hartmann" , Current FreeBSD , =?ISO-8859-1?Q?Bern?= Subject: Re: FreeBSD 10.0-CURRENT r239477 doesn't compile: virtualbox-ose-kmod-4.1.18_1 is marked as broken: Does not compile on FreeBSD < 8.2. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 22 Aug 2012 18:38:20 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigB68366E0D10F83B59EB99EF5 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Am 08/22/12 16:02, schrieb Chris Rees: > On 22 August 2012 14:32, O. Hartmann = wrote: >> On 08/22/12 15:05, Chris Rees wrote: >>> On 22 August 2012 08:18, O. Hartmann wr= ote: >>>> Am 08/21/12 22:53, schrieb Bernhard Fr=F6hlich: >>>>> On Di., 21. Aug. 2012 13:56:02 CEST, O. Hartmann wrote: >>>>> >>>>>> Today I ran into a problem with FreeBSD 10.0-CURRENT #0 r239477 >>>>>> recompiling the VBox kernel module: >>>>>> >>>>>> =3D=3D=3D> Cleaning for virtualbox-ose-kmod-4.1.18_1 >>>>>> =3D=3D=3D> virtualbox-ose-kmod-4.1.18_1 is marked as broken: Doe= s not compile >>>>>> on FreeBSD < 8.2. >>>>>> *** [all] Error code 1 >>>>>> >>>>>> Stop in /usr/ports/emulators/virtualbox-ose-kmod. >>>>>> >>>>>> The port compiled prior to the updates of today. >>>>>> >>>>>> oh >>>>> >>>>> What is the question? We have deprecated < 8.2 almost five months a= go because of the memobj r0 rewrite. You're the first who complains about= this so I'm pretty sure it was the correct decision to move forward. Ple= ase also keep in mind that 8.1 is already EOL. >>>>> >>>> >>>> I do not understand your complains about my mail to the list. For yo= ur >>>> information: I'm on FreeBSD 10.0-CURRENT and this seems, as far as I= >>>> know, considered not to be deprecated by now. If I'm wrong in that, = sorry. >>> >>> Can you give us the output of make -C >>> /usr/ports/emulators/virtualbox-ose-kmod -VOSVERSION please? >> >> 1000017 >> >>> >>> I think your version of sys/param.h could be out of date. >>> >>> Chris >> >> >> >> As soon as I'm sitting in front of the machine again. But I doubt that= >> the sys/param.h is out of date, since that box has been recompiling >> FreeBSD 10.0-CURRENT now for almost every day. >=20 > Hm, does that mean that the output you gave me earlier was not from > the same machine? No, it is the same box. I tried another FBSD 10.0-CURRENT box today at my lab and had success ... but see below ... >=20 >> When the problem occured, the change to CLANG 3.2-Beta has just been >> introduced, installed with "make buildworld installkernel". This >> procedere also triggers (via /etc/src.conf) >> >> PORTS_MODULES=3D "x11/nvidia-driver" >> PORTS_MODULES+=3D "emulators/virtualbox-ose-kmod" >=20 > Please remove the quotes! [1] Better that way? PORTS_MODULES=3D emulators/virtualbox-ose-kmod x11/nvidia-driver= >=20 >> the build of the modules for the nvidia GPU and Vbox kernel module. >> >> Thanks for your response, >=20 > Something really weird is happening here. All that is happening is > that the Makefile is testing against OSVERSION; I guess this is the result of my unpatience! Usually, I install a new kernel, reboot it into single user mode, install world and do the mergemaster stuff. This time, I still ran the old kernel (but even FreeBSD 10.0-CURRENT) and made a installworld. The musterius error occured, when the kernel mod for VBox was about to be compiled. I updated today my lab's box and since this machine also sucked in the new CLANG 3.2 stuff, I was really careful about what would happen. I compiled the system, installed the kernel, booted into single user mode and did the installworld with all mounted filesystems (and service ldconfig start issued) - and had no problems! I did the same today on the faulty box, also no problems after the new compiled system was properly installed. I guess I made a conceptional bad mistake and maybe something got inconsistent due to the new compiler/LLVM stuff? A naiv suggestion. I guess it is a waste of time to investigate this further - except there is a hidden issue ... >=20 > .if ${OSVERSION} < 802000 > BROKEN=3D Does not compile on FreeBSD < 8.2 > .endif >=20 > Since the result from make -VOSVERSION shows that your OSVERSION is > indeed above 802000, I am completely at a loss as to what's going on > :( >=20 > Chris >=20 > [1] http://www.bayofrum.net/~crees/scripts/dont-quote.mk Thanks for the patience, Oliver --------------enigB68366E0D10F83B59EB99EF5 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.0.19 (FreeBSD) iQEcBAEBAgAGBQJQNScZAAoJEOgBcD7A/5N8tS8H/igszz39pyq/n9ELO7pB7kX4 4l3Pvgf4VpiHccT7I9dKUeUU/ssG9MqixxbpfbRRKoe3Unsw0+F027ceI82NL/w0 X/v5m0x9l/3NVRD/R4I7N8bGZkLq3vzYEUwn+i/tHRf1W5JmMgzQftS5Zn5Xz2Dc 7nPj+6syQ+5e0m3Ozf9LaXggsIKwxXNGcuje5MEuikRUrbD7FmjAZXBbKGJovYPR puitfEAW4qBzuj3BopBB+pThF16/nyKL/unw9fONnLSspWSRGW/G0Kwmc+WSwwX2 ceILj6/rG3sXIZWyFI+QGS7TAzKblMfl0b6OCrCh0qIR8lz1Mz9n/VY6LgUkmac= =gBmQ -----END PGP SIGNATURE----- --------------enigB68366E0D10F83B59EB99EF5-- From owner-freebsd-current@FreeBSD.ORG Wed Aug 22 18:42:24 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 30EAD106564A for ; Wed, 22 Aug 2012 18:42:24 +0000 (UTC) (envelope-from utisoft@gmail.com) Received: from mail-lb0-f182.google.com (mail-lb0-f182.google.com [209.85.217.182]) by mx1.freebsd.org (Postfix) with ESMTP id 93F158FC17 for ; Wed, 22 Aug 2012 18:42:23 +0000 (UTC) Received: by lbbgg13 with SMTP id gg13so1027573lbb.13 for ; Wed, 22 Aug 2012 11:42:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=bmOuPhqMBXbvSMsi8/zLEaxuf8duocDEliYJsQPoXNI=; b=SwcyMLhdY97QITLYtBE0Xwsii0umnv1Pg8Q9v2zHkzLGqGwMxyD8YSFv+TlFLDpud/ gsc3SrSmJmobgIIiF1WUcz6GkMGMzkqx9dj9JKQpt7aE2T3s+E/Xio0oGeI4MBYZWYwa 7MR2Wd+JlV9L5gtWFds5n5dKkZwPB8E2pP8po7/97CJB0xGI++ScY9v7KHVk6qVHlgS3 YSSggRObdBt9zYIFUZ1Q2RcXy9tMv7yyS3tzmdDI6rkkdGK54PMWwIcrrPAf7Xnn1dXr HlQTJ/UWjtgCds4cXmvvIU5+ET0DzuP7NQsv+eb5p5UDJNR3tVCjvhhzQCyZ4hnlxRMr J7mw== MIME-Version: 1.0 Received: by 10.112.24.229 with SMTP id x5mr9771472lbf.23.1345660941375; Wed, 22 Aug 2012 11:42:21 -0700 (PDT) Received: by 10.112.60.227 with HTTP; Wed, 22 Aug 2012 11:42:21 -0700 (PDT) Received: by 10.112.60.227 with HTTP; Wed, 22 Aug 2012 11:42:21 -0700 (PDT) In-Reply-To: <50352715.3010909@zedat.fu-berlin.de> References: <50337752.8070707@zedat.fu-berlin.de> <1345582381.1632.6.camel@Nokia-N900-42-11> <503487DE.3050807@zedat.fu-berlin.de> <5034DF8B.102@mail.zedat.fu-berlin.de> <50352715.3010909@zedat.fu-berlin.de> Date: Wed, 22 Aug 2012 19:42:21 +0100 Message-ID: From: Chris Rees To: "O. Hartmann" Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Bernhard Froehlich , freebsd-current , "O. Hartmann" Subject: Re: FreeBSD 10.0-CURRENT r239477 doesn't compile: virtualbox-ose-kmod-4.1.18_1 is marked as broken: Does not compile on FreeBSD < 8.2. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 22 Aug 2012 18:42:24 -0000 On 22 Aug 2012 19:38, "O. Hartmann" wrote: > > Am 08/22/12 16:02, schrieb Chris Rees: > > On 22 August 2012 14:32, O. Hartmann wrote: > >> On 08/22/12 15:05, Chris Rees wrote: > >>> On 22 August 2012 08:18, O. Hartmann wrote: > >>>> Am 08/21/12 22:53, schrieb Bernhard Fr=F6hlich: > >>>>> On Di., 21. Aug. 2012 13:56:02 CEST, O. Hartmann < ohartman@zedat.fu-berlin.de> wrote: > >>>>> > >>>>>> Today I ran into a problem with FreeBSD 10.0-CURRENT #0 r239477 > >>>>>> recompiling the VBox kernel module: > >>>>>> > >>>>>> =3D=3D=3D> Cleaning for virtualbox-ose-kmod-4.1.18_1 > >>>>>> =3D=3D=3D> virtualbox-ose-kmod-4.1.18_1 is marked as broken: Doe= s not compile > >>>>>> on FreeBSD < 8.2. > >>>>>> *** [all] Error code 1 > >>>>>> > >>>>>> Stop in /usr/ports/emulators/virtualbox-ose-kmod. > >>>>>> > >>>>>> The port compiled prior to the updates of today. > >>>>>> > >>>>>> oh > >>>>> > >>>>> What is the question? We have deprecated < 8.2 almost five months ago because of the memobj r0 rewrite. You're the first who complains about this so I'm pretty sure it was the correct decision to move forward. Please also keep in mind that 8.1 is already EOL. > >>>>> > >>>> > >>>> I do not understand your complains about my mail to the list. For your > >>>> information: I'm on FreeBSD 10.0-CURRENT and this seems, as far as I > >>>> know, considered not to be deprecated by now. If I'm wrong in that, sorry. > >>> > >>> Can you give us the output of make -C > >>> /usr/ports/emulators/virtualbox-ose-kmod -VOSVERSION please? > >> > >> 1000017 > >> > >>> > >>> I think your version of sys/param.h could be out of date. > >>> > >>> Chris > >> > >> > >> > >> As soon as I'm sitting in front of the machine again. But I doubt that > >> the sys/param.h is out of date, since that box has been recompiling > >> FreeBSD 10.0-CURRENT now for almost every day. > > > > Hm, does that mean that the output you gave me earlier was not from > > the same machine? > > No, it is the same box. I tried another FBSD 10.0-CURRENT box today at > my lab and had success ... but see below ... > > > > >> When the problem occured, the change to CLANG 3.2-Beta has just been > >> introduced, installed with "make buildworld installkernel". This > >> procedere also triggers (via /etc/src.conf) > >> > >> PORTS_MODULES=3D "x11/nvidia-driver" > >> PORTS_MODULES+=3D "emulators/virtualbox-ose-kmod" > > > > Please remove the quotes! [1] > > Better that way? > PORTS_MODULES=3D emulators/virtualbox-ose-kmod x11/nvidia-driver Much :) > > > >> the build of the modules for the nvidia GPU and Vbox kernel module. > >> > >> Thanks for your response, > > > > Something really weird is happening here. All that is happening is > > that the Makefile is testing against OSVERSION; > > I guess this is the result of my unpatience! Usually, I install a new > kernel, reboot it into single user mode, install world and do the > mergemaster stuff. > > This time, I still ran the old kernel (but even FreeBSD 10.0-CURRENT) > and made a installworld. The musterius error occured, when the kernel > mod for VBox was about to be compiled. > > I updated today my lab's box and since this machine also sucked in the > new CLANG 3.2 stuff, I was really careful about what would happen. I > compiled the system, installed the kernel, booted into single user mode > and did the installworld with all mounted filesystems (and service > ldconfig start issued) - and had no problems! > > I did the same today on the faulty box, also no problems after the new > compiled system was properly installed. > > I guess I made a conceptional bad mistake and maybe something got > inconsistent due to the new compiler/LLVM stuff? A naiv suggestion. > > I guess it is a waste of time to investigate this further - except there > is a hidden issue ... Hm, it does seem weird. If it doesn't bother you any more it's probably not worth chasing; it's enough work to support supported processes if you get what I mean ;) > > > > .if ${OSVERSION} < 802000 > > BROKEN=3D Does not compile on FreeBSD < 8.2 > > .endif > > > > Since the result from make -VOSVERSION shows that your OSVERSION is > > indeed above 802000, I am completely at a loss as to what's going on > > :( > > > > Chris > > > > [1] http://www.bayofrum.net/~crees/scripts/dont-quote.mk > > Thanks for the patience, No problem. Chris From owner-freebsd-current@FreeBSD.ORG Wed Aug 22 18:55:12 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AF6D4106566C; Wed, 22 Aug 2012 18: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 E30138FC1F; Wed, 22 Aug 2012 18:55:11 +0000 (UTC) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost1.zedat.fu-berlin.de (Exim 4.69) with esmtp (envelope-from ) id <1T4G58-0002iO-8I>; Wed, 22 Aug 2012 20:55:10 +0200 Received: from e178003168.adsl.alicedsl.de ([85.178.3.168] helo=thor.walstatt.dyndns.org) by inpost2.zedat.fu-berlin.de (Exim 4.69) with esmtpsa (envelope-from ) id <1T4G57-0007uU-8y>; Wed, 22 Aug 2012 20:55:10 +0200 Message-ID: <50352B03.8020802@zedat.fu-berlin.de> Date: Wed, 22 Aug 2012 20:54:59 +0200 From: "O. Hartmann" User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:14.0) Gecko/20120810 Thunderbird/14.0 MIME-Version: 1.0 To: Garrett Cooper References: <50337752.8070707@zedat.fu-berlin.de> <1345582381.1632.6.camel@Nokia-N900-42-11> <503487DE.3050807@zedat.fu-berlin.de> <5034DF8B.102@mail.zedat.fu-berlin.de> In-Reply-To: X-Enigmail-Version: 1.4.3 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig0B8F5B656EA9E8975D5DAC87" X-Originating-IP: 85.178.3.168 Cc: Chris Rees , "O. Hartmann" , Current FreeBSD , =?ISO-8859-1?Q?Bernhard_Fr=F6hlich?= Subject: Re: FreeBSD 10.0-CURRENT r239477 doesn't compile: virtualbox-ose-kmod-4.1.18_1 is marked as broken: Does not compile on FreeBSD < 8.2. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 22 Aug 2012 18:55:12 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig0B8F5B656EA9E8975D5DAC87 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Am 08/22/12 17:24, schrieb Garrett Cooper: > On Wed, Aug 22, 2012 at 7:02 AM, Chris Rees wrote: >> On 22 August 2012 14:32, O. Hartmann wrote: >>> On 08/22/12 15:05, Chris Rees wrote: >>>> On 22 August 2012 08:18, O. Hartmann w= rote: >>>>> Am 08/21/12 22:53, schrieb Bernhard Fr=F6hlich: >>>>>> On Di., 21. Aug. 2012 13:56:02 CEST, O. Hartmann wrote: >>>>>> >>>>>>> Today I ran into a problem with FreeBSD 10.0-CURRENT #0 r239477 >>>>>>> recompiling the VBox kernel module: >>>>>>> >>>>>>> =3D=3D=3D> Cleaning for virtualbox-ose-kmod-4.1.18_1 >>>>>>> =3D=3D=3D> virtualbox-ose-kmod-4.1.18_1 is marked as broken: Do= es not compile >>>>>>> on FreeBSD < 8.2. >>>>>>> *** [all] Error code 1 >>>>>>> >>>>>>> Stop in /usr/ports/emulators/virtualbox-ose-kmod. >>>>>>> >>>>>>> The port compiled prior to the updates of today. >>>>>>> >>>>>>> oh >>>>>> >>>>>> What is the question? We have deprecated < 8.2 almost five months = ago because of the memobj r0 rewrite. You're the first who complains abou= t this so I'm pretty sure it was the correct decision to move forward. Pl= ease also keep in mind that 8.1 is already EOL. >>>>>> >>>>> >>>>> I do not understand your complains about my mail to the list. For y= our >>>>> information: I'm on FreeBSD 10.0-CURRENT and this seems, as far as = I >>>>> know, considered not to be deprecated by now. If I'm wrong in that,= sorry. >>>> >>>> Can you give us the output of make -C >>>> /usr/ports/emulators/virtualbox-ose-kmod -VOSVERSION please? >>> >>> 1000017 >>> >>>> >>>> I think your version of sys/param.h could be out of date. >>>> >>>> Chris >>> >>> >>> >>> As soon as I'm sitting in front of the machine again. But I doubt tha= t >>> the sys/param.h is out of date, since that box has been recompiling >>> FreeBSD 10.0-CURRENT now for almost every day. >> >> Hm, does that mean that the output you gave me earlier was not from >> the same machine? >> >>> When the problem occured, the change to CLANG 3.2-Beta has just been >>> introduced, installed with "make buildworld installkernel". This >>> procedere also triggers (via /etc/src.conf) >>> >>> PORTS_MODULES=3D "x11/nvidia-driver" >>> PORTS_MODULES+=3D "emulators/virtualbox-ose-kmod" >> >> Please remove the quotes! [1] >> >>> the build of the modules for the nvidia GPU and Vbox kernel module. >>> >>> Thanks for your response, >> >> Something really weird is happening here. All that is happening is >> that the Makefile is testing against OSVERSION; >> >> .if ${OSVERSION} < 802000 >> BROKEN=3D Does not compile on FreeBSD < 8.2 >> .endif >> >> Since the result from make -VOSVERSION shows that your OSVERSION is >> indeed above 802000, I am completely at a loss as to what's going on >> :( >=20 > I think this is the issue that I was referring to earlier that I noted > to dougb@ but hadn't gotten an opportunity to repro because I've been > busy with other things. >=20 > What does OSVERSION look like when you run it from make buildkernel > (use this patch)? >=20 > Thanks, > -Garrett >=20 > $ svn diff /usr/src/sys/conf/kern.post.mk > Index: /usr/src/sys/conf/kern.post.mk > =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 > --- /usr/src/sys/conf/kern.post.mk (revision 239292) > +++ /usr/src/sys/conf/kern.post.mk (working copy) > @@ -61,6 +61,8 @@ > OSVERSION=3D${OSRELDATE} \ > WRKDIRPREFIX=3D${WRKDIRPREFIX} >=20 > +.warning "PORTSMODULESENV =3D> ${PORTSMODULESENV}" > + > # The WRKDIR needs to be cleaned before building, and trying to > change the target > # with a :C pattern below results in install -> instclean > all: >=20 On both systems I have to maintain, the output is: BOX 1, patched: make -C /usr/ports/emulators/virtualbox-ose-kmod -VOSVERSION 1000017 BOX 2, unpatched: make -C /usr/ports/emulators/virtualbox-ose-kmod -VOSVERSION 1000017 No difference. As I reported Chris Rees a moment ago, the "faulty" box was running a kernel compiled with CLANG 3.1 while I installed world with the freshly compiled CLANG 3.2 stuff and then tried to rebuild the kernel module for VBox with this mixture. The CLANG issue is a wild guess. I didn't follow the install procedure for a new world (single user mode startup with new kernel, installworld, mergemaster et cetera). I guess something really nasty happened that way and is possibly not worth to be investigated further. After I rebuild and installed world on my lab's box today the regular way and faced no problems building the kernel module for virtual box, I guess the problem is none but chasing ghosts ... Regards, Oliver --------------enig0B8F5B656EA9E8975D5DAC87 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.0.19 (FreeBSD) iQEcBAEBAgAGBQJQNSsIAAoJEOgBcD7A/5N83oUIALT+oT5puc9v4kC6BEOdwKGb B4ypx89vJUK9oRLI+80EWTXIKX60ErM/dGmr/EzqmPeKmeSAdYEcWgGYZo1Jd0n/ pxWACRtH2BuTKuL+5uFjF2QblgcyuKOd/noo/hqym6xewojXk7uYkzqSeZJyhMfw v6Sd3BQW5MGtLaVhkWSJkkdM8fFj2zHzxf4A6PiaQv8pIy+OjPXb1I5yk61efHIq zpRpisu0upEgYhlW5ZIhE2B6GHydcf4pSHaPDtBPAk4vlEz7ykVodX73HY/S++4D EIGsmXs+uJ4hRdjH1Lf5kghVq7gBD5br2a/Tot9vf1JfrEWfX9vCrSeFrpJNTyg= =YklX -----END PGP SIGNATURE----- --------------enig0B8F5B656EA9E8975D5DAC87-- From owner-freebsd-current@FreeBSD.ORG Wed Aug 22 19:54:57 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5CBF41065673 for ; Wed, 22 Aug 2012 19:54:57 +0000 (UTC) (envelope-from naylor.b.david@gmail.com) Received: from mail-wg0-f50.google.com (mail-wg0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id D97B18FC0A for ; Wed, 22 Aug 2012 19:54:56 +0000 (UTC) Received: by wgbds11 with SMTP id ds11so1130423wgb.31 for ; Wed, 22 Aug 2012 12:54:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:subject:date:user-agent:cc:references:in-reply-to :mime-version:content-type:content-transfer-encoding:message-id; bh=bTfS2UGvkQauDh557udp1h5hsXFkOwbEZ8TGW++2xyg=; b=jQMxf34zOnVXTHc1Mbg5bpdQCSkEHWGDGOj/qGKot+htc3+Md+bRIP8Qw2rpWbebkn qjXZCJ4iU4VDlHe0gTHJlREaeKwp078Vg0CzFb0ujXYwCwfbhl1JI3hIrv/CXQ9/lhue J97gaJgqIEj/00Sw5LgZb3si/xHYnT1/VLnUALesVs5a4DDiiIzEK9fXx1R+wUf6yYvh Vr1P5CehBBtVaMXDwpmDMd1ROQcPH5us0+ufpzpZrPezt8gid4Jb2oFHxpT01rIFcI6t z6NoD3J8PK+N77HNScML2f2CVKc912xi0lHTxTx1fib4gM4wExbkoHfUmSqJ/bG0hEa6 vNVA== Received: by 10.180.19.169 with SMTP id g9mr8449711wie.9.1345665295537; Wed, 22 Aug 2012 12:54:55 -0700 (PDT) Received: from dragon.dg (41-132-210-104.dsl.mweb.co.za. [41.132.210.104]) by mx.google.com with ESMTPS id dc3sm40784137wib.7.2012.08.22.12.54.53 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 22 Aug 2012 12:54:54 -0700 (PDT) From: David Naylor To: Konstantin Belousov Date: Wed, 22 Aug 2012 21:54:46 +0200 User-Agent: KMail/1.13.7 (FreeBSD/9.1-PRERELEASE; KDE/4.8.4; amd64; ; ) References: <201208220913.48095.naylor.b.david@gmail.com> <20120822113430.GA33100@deviant.kiev.zoral.com.ua> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart4105361.oALNXZL2p2"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <201208222154.49948.naylor.b.david@gmail.com> Cc: freebsd-current@freebsd.org Subject: Re: tar not working in an i386 chroot (getvfsbyname) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 22 Aug 2012 19:54:57 -0000 --nextPart4105361.oALNXZL2p2 Content-Type: Text/Plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable On Wednesday, 22 August 2012 13:38:41 David Naylor wrote: > I'm test it in ~8 hours and report back. >=20 > On Aug 22, 2012 1:34 PM, "Konstantin Belousov" wrot= e: > > On Wed, Aug 22, 2012 at 09:13:44AM +0200, David Naylor wrote: > > > Hi, > > >=20 > > > While trying to compile FreeBSD 10 packages I encountered this error: > > > # chroot /scratchpad/freebsd10_i386 tar -cf /dev/null root > > > tar: getvfsbyname failed: No such file or directory > > > tar: Error exit delayed from previous errors. > > >=20 > > > The kernel does have COMPAT_FREEBSD32 in it. To reproduce this (on an > > > FreeBSD10/amd64 machine) do: > > > # cd /usr/src > > > # make -sj16 buildworld installworld DESTDIR=3D/scratchpad/freebsd10_= i386 > > > # chroot /scratchpad/freebsd10_i386 tar -cf /dev/null root > >=20 > > http://lists.freebsd.org/pipermail/freebsd-current/2012-August/035976.h= tm > > l > >=20 > > I need somebody to test this before commit. Applying this patch to 9-STABLE (with some fuzz) I get: # chroot /scratchpad/freebsd10_i386/ tar -cvf /dev/null root a root a root/.k5login a root/.profile a root/.cshrc a root/.login a root/.history The patch works for me. Thanks --nextPart4105361.oALNXZL2p2 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) iEYEABECAAYFAlA1OQkACgkQUaaFgP9pFrJ9aACeLIFN5OfyVAlZSjEakvLF7zrs zh4An1P4aMej8nL0rbVP4wZNquYvoSm5 =EOsQ -----END PGP SIGNATURE----- --nextPart4105361.oALNXZL2p2-- From owner-freebsd-current@FreeBSD.ORG Wed Aug 22 19:56:48 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6BAE110656EC; Wed, 22 Aug 2012 19:56:48 +0000 (UTC) (envelope-from yanegomi@gmail.com) Received: from mail-yx0-f182.google.com (mail-yx0-f182.google.com [209.85.213.182]) by mx1.freebsd.org (Postfix) with ESMTP id D77D38FC1F; Wed, 22 Aug 2012 19:56:47 +0000 (UTC) Received: by yenl7 with SMTP id l7so1233203yen.13 for ; Wed, 22 Aug 2012 12:56:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=QXZ+tR/JnPmbEaR58clirUzJJimqhsnLm1tMrCIOr4o=; b=l+gvncCwFSJj6F94okSaDqfa8VfY9EzX+Bc+ikJVviCejCWxQSyLHioZ0PAe/wy5NZ iuSkWTQpknFdPU0SZqKp0PBkKkqrmQB5deHCvCVI5WzJosNGc3KNWafVYa6aFOb/OYGZ VIuH3y4Eh8w4+2remzEh0spS1PQOoxHKQSist0HFPH+lqtqk5hZgUzT4ZEfnHTtjqkGU zyYOCImazwjz7kI+RWBV3OhTHQ+Kt52s9Mc3c9+jZlQMAcLtcDEv7CoVS3D/oldOolMJ iBsFUWs4gtxSgs0p6Fj2tslrAm4uqL38upCsQGV6UjoR9JY7pf/pZLN97xAa5KdSMvDs UZvw== MIME-Version: 1.0 Received: by 10.60.20.69 with SMTP id l5mr16183979oee.114.1345665406798; Wed, 22 Aug 2012 12:56:46 -0700 (PDT) Received: by 10.76.142.201 with HTTP; Wed, 22 Aug 2012 12:56:46 -0700 (PDT) In-Reply-To: <50352B03.8020802@zedat.fu-berlin.de> References: <50337752.8070707@zedat.fu-berlin.de> <1345582381.1632.6.camel@Nokia-N900-42-11> <503487DE.3050807@zedat.fu-berlin.de> <5034DF8B.102@mail.zedat.fu-berlin.de> <50352B03.8020802@zedat.fu-berlin.de> Date: Wed, 22 Aug 2012 12:56:46 -0700 Message-ID: From: Garrett Cooper To: "O. Hartmann" Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: Chris Rees , "O. Hartmann" , Current FreeBSD , =?ISO-8859-1?Q?Bernhard_Fr=F6hlich?= Subject: Re: FreeBSD 10.0-CURRENT r239477 doesn't compile: virtualbox-ose-kmod-4.1.18_1 is marked as broken: Does not compile on FreeBSD < 8.2. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 22 Aug 2012 19:56:48 -0000 On Wed, Aug 22, 2012 at 11:54 AM, O. Hartmann wrote: > Am 08/22/12 17:24, schrieb Garrett Cooper: >> On Wed, Aug 22, 2012 at 7:02 AM, Chris Rees wrote: >>> On 22 August 2012 14:32, O. Hartmann = wrote: >>>> On 08/22/12 15:05, Chris Rees wrote: >>>>> On 22 August 2012 08:18, O. Hartmann wr= ote: >>>>>> Am 08/21/12 22:53, schrieb Bernhard Fr=F6hlich: >>>>>>> On Di., 21. Aug. 2012 13:56:02 CEST, O. Hartmann wrote: >>>>>>> >>>>>>>> Today I ran into a problem with FreeBSD 10.0-CURRENT #0 r239477 >>>>>>>> recompiling the VBox kernel module: >>>>>>>> >>>>>>>> =3D=3D=3D> Cleaning for virtualbox-ose-kmod-4.1.18_1 >>>>>>>> =3D=3D=3D> virtualbox-ose-kmod-4.1.18_1 is marked as broken: Doe= s not compile >>>>>>>> on FreeBSD < 8.2. >>>>>>>> *** [all] Error code 1 >>>>>>>> >>>>>>>> Stop in /usr/ports/emulators/virtualbox-ose-kmod. >>>>>>>> >>>>>>>> The port compiled prior to the updates of today. >>>>>>>> >>>>>>>> oh >>>>>>> >>>>>>> What is the question? We have deprecated < 8.2 almost five months a= go because of the memobj r0 rewrite. You're the first who complains about t= his so I'm pretty sure it was the correct decision to move forward. Please = also keep in mind that 8.1 is already EOL. >>>>>>> >>>>>> >>>>>> I do not understand your complains about my mail to the list. For yo= ur >>>>>> information: I'm on FreeBSD 10.0-CURRENT and this seems, as far as I >>>>>> know, considered not to be deprecated by now. If I'm wrong in that, = sorry. >>>>> >>>>> Can you give us the output of make -C >>>>> /usr/ports/emulators/virtualbox-ose-kmod -VOSVERSION please? >>>> >>>> 1000017 >>>> >>>>> >>>>> I think your version of sys/param.h could be out of date. >>>>> >>>>> Chris >>>> >>>> >>>> >>>> As soon as I'm sitting in front of the machine again. But I doubt that >>>> the sys/param.h is out of date, since that box has been recompiling >>>> FreeBSD 10.0-CURRENT now for almost every day. >>> >>> Hm, does that mean that the output you gave me earlier was not from >>> the same machine? >>> >>>> When the problem occured, the change to CLANG 3.2-Beta has just been >>>> introduced, installed with "make buildworld installkernel". This >>>> procedere also triggers (via /etc/src.conf) >>>> >>>> PORTS_MODULES=3D "x11/nvidia-driver" >>>> PORTS_MODULES+=3D "emulators/virtualbox-ose-kmod" >>> >>> Please remove the quotes! [1] >>> >>>> the build of the modules for the nvidia GPU and Vbox kernel module. >>>> >>>> Thanks for your response, >>> >>> Something really weird is happening here. All that is happening is >>> that the Makefile is testing against OSVERSION; >>> >>> .if ${OSVERSION} < 802000 >>> BROKEN=3D Does not compile on FreeBSD < 8.2 >>> .endif >>> >>> Since the result from make -VOSVERSION shows that your OSVERSION is >>> indeed above 802000, I am completely at a loss as to what's going on >>> :( >> >> I think this is the issue that I was referring to earlier that I noted >> to dougb@ but hadn't gotten an opportunity to repro because I've been >> busy with other things. >> >> What does OSVERSION look like when you run it from make buildkernel >> (use this patch)? >> >> Thanks, >> -Garrett >> >> $ svn diff /usr/src/sys/conf/kern.post.mk >> Index: /usr/src/sys/conf/kern.post.mk >> =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 >> --- /usr/src/sys/conf/kern.post.mk (revision 239292) >> +++ /usr/src/sys/conf/kern.post.mk (working copy) >> @@ -61,6 +61,8 @@ >> OSVERSION=3D${OSRELDATE} \ >> WRKDIRPREFIX=3D${WRKDIRPREFIX} >> >> +.warning "PORTSMODULESENV =3D> ${PORTSMODULESENV}" >> + >> # The WRKDIR needs to be cleaned before building, and trying to >> change the target >> # with a :C pattern below results in install -> instclean >> all: >> > > On both systems I have to maintain, the output is: > > BOX 1, patched: > make -C /usr/ports/emulators/virtualbox-ose-kmod -VOSVERSION > 1000017 > > BOX 2, unpatched: > make -C /usr/ports/emulators/virtualbox-ose-kmod -VOSVERSION > 1000017 You didn't do what I asked. Please re-read the email I sent last night asking for the output when running make buildkernel. > No difference. > > As I reported Chris Rees a moment ago, the "faulty" box was running a > kernel compiled with CLANG 3.1 while I installed world with the freshly > compiled CLANG 3.2 stuff and then tried to rebuild the kernel module for > VBox with this mixture. The CLANG issue is a wild guess. I didn't follow > the install procedure for a new world (single user mode startup with new > kernel, installworld, mergemaster et cetera). I guess something really > nasty happened that way and is possibly not worth to be investigated > further. > > After I rebuild and installed world on my lab's box today the regular > way and faced no problems building the kernel module for virtual box, I > guess the problem is none but chasing ghosts ... Hmmm... still seems odd, but if it's fixed, oh well... Thanks, -Garrett From owner-freebsd-current@FreeBSD.ORG Wed Aug 22 20:06:32 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9A865106566B; Wed, 22 Aug 2012 20:06:32 +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 57A438FC25; Wed, 22 Aug 2012 20:06:32 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id AA632B9A0; Wed, 22 Aug 2012 16:06:31 -0400 (EDT) From: John Baldwin To: freebsd-current@freebsd.org Date: Wed, 22 Aug 2012 15:35:01 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110714-p17; KDE/4.5.5; amd64; ; ) References: <20120821095527.GA33206@hell.ukr.net> <20120822171253.GB3300@michelle.cdnetworks.com> <20120822172822.GA52909@hell.ukr.net> In-Reply-To: <20120822172822.GA52909@hell.ukr.net> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201208221535.01598.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Wed, 22 Aug 2012 16:06:31 -0400 (EDT) Cc: YongHyeon PYUN , Vitalij Satanivskij , Peter Jeremy , current@freebsd.org Subject: Re: dhclient cause up/down cycle after 239356 ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 22 Aug 2012 20:06:32 -0000 On Wednesday, August 22, 2012 1:28:22 pm Vitalij Satanivskij wrote: > ok next round :) > > dhclient updated to Revision 239564 > > with fxp : > > Aug 22 20:06:48 home kernel: fxp0: link state changed to DOWN > Aug 22 20:06:48 home dhclient: New Subnet Mask (fxp0): 255.255.255.0 > Aug 22 20:06:48 home dhclient: New Broadcast Address (fxp0): xx.xx.xx.255 > Aug 22 20:06:48 home dhclient: New Routers (fxp0): xx.xx.xx.1 > Aug 22 20:06:50 home kernel: fxp0: link state changed to UP > Aug 22 20:06:53 home dhclient: New IP Address (fxp0): xx.xx.xx.xx > Aug 22 20:06:53 home kernel: fxp0: link state changed to DOWN > Aug 22 20:06:53 home dhclient: New Subnet Mask (fxp0): 255.255.255.0 > Aug 22 20:06:53 home dhclient: New Broadcast Address (fxp0): xx.xx.xx.255 > Aug 22 20:06:53 home dhclient: New Routers (fxp0): xx.xx.xx.xx > Aug 22 20:06:55 home kernel: fxp0: link state changed to UP > Aug 22 20:07:01 home dhclient: New IP Address (fxp0): xx.xx.xx.xx > Aug 22 20:07:01 home kernel: fxp0: link state changed to DOWN > Aug 22 20:07:01 home dhclient: New Subnet Mask (fxp0): 255.255.255.0 > Aug 22 20:07:01 home dhclient: New Broadcast Address (fxp0): xx.xx.xx.255 > Aug 22 20:07:01 home dhclient: New Routers (fxp0): xx.xx.xx.xx > Aug 22 20:07:03 home kernel: fxp0: link state changed to UP > Aug 22 20:07:07 home dhclient: New IP Address (fxp0): xx.xx.xx.xx > Aug 22 20:07:07 home kernel: fxp0: link state changed to DOWN > Aug 22 20:07:07 home dhclient: New Subnet Mask (fxp0): 255.255.255.0 > Aug 22 20:07:07 home dhclient: New Broadcast Address (fxp0): xx.xx.xx.255 > Aug 22 20:07:07 home dhclient: New Routers (fxp0): xx.xx.xx.xx > Aug 22 20:07:09 home kernel: fxp0: link state changed to UP > Aug 22 20:07:13 home dhclient: New IP Address (fxp0): xx.xx.xx.xx > Aug 22 20:07:13 home kernel: fxp0: link state changed to DOWN > Aug 22 20:07:13 home dhclient: New Subnet Mask (fxp0): 255.255.255.0 > Aug 22 20:07:13 home dhclient: New Broadcast Address (fxp0): xx.xx.xx.255 > Aug 22 20:07:13 home dhclient: New Routers (fxp0): xx.xx.xx.xx > Aug 22 20:07:15 home kernel: fxp0: link state changed to UP Hmm. Perhaps we could use a debouncer to ignore "short" link flaps? Kind of gross (and OpenBSD doesn't do this). For now this change basically ignores link up events if they occur with 5 seconds of the link down event. The 5 is hardcoded which is kind of yuck. Index: dhcpd.h =================================================================== --- dhcpd.h (revision 239564) +++ dhcpd.h (working copy) @@ -209,6 +209,7 @@ int dead; u_int16_t index; int linkstat; + time_t linktime; }; struct timeout { Index: dhclient.c =================================================================== --- dhclient.c (revision 239564) +++ dhclient.c (working copy) @@ -285,8 +285,14 @@ ifi->linkstat ? "up" : "down", linkstat ? "up" : "down"); ifi->linkstat = linkstat; - if (linkstat) + + /* + * XXX: Hardcoded 5 second grace window on + * link flaps. + */ + if (linkstat && (cur_time - ifi->linktime) >= 5) state_reboot(ifi); + ifi->linktime = cur_time; } break; case RTM_IFANNOUNCE: @@ -441,6 +447,7 @@ fprintf(stderr, " got link\n"); } ifi->linkstat = 1; + ifi->linktime = cur_time; if ((nullfd = open(_PATH_DEVNULL, O_RDWR, 0)) == -1) error("cannot open %s: %m", _PATH_DEVNULL); -- John Baldwin From owner-freebsd-current@FreeBSD.ORG Wed Aug 22 20:06:32 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9A865106566B; Wed, 22 Aug 2012 20:06:32 +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 57A438FC25; Wed, 22 Aug 2012 20:06:32 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id AA632B9A0; Wed, 22 Aug 2012 16:06:31 -0400 (EDT) From: John Baldwin To: freebsd-current@freebsd.org Date: Wed, 22 Aug 2012 15:35:01 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110714-p17; KDE/4.5.5; amd64; ; ) References: <20120821095527.GA33206@hell.ukr.net> <20120822171253.GB3300@michelle.cdnetworks.com> <20120822172822.GA52909@hell.ukr.net> In-Reply-To: <20120822172822.GA52909@hell.ukr.net> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201208221535.01598.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Wed, 22 Aug 2012 16:06:31 -0400 (EDT) Cc: YongHyeon PYUN , Vitalij Satanivskij , Peter Jeremy , current@freebsd.org Subject: Re: dhclient cause up/down cycle after 239356 ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 22 Aug 2012 20:06:32 -0000 On Wednesday, August 22, 2012 1:28:22 pm Vitalij Satanivskij wrote: > ok next round :) > > dhclient updated to Revision 239564 > > with fxp : > > Aug 22 20:06:48 home kernel: fxp0: link state changed to DOWN > Aug 22 20:06:48 home dhclient: New Subnet Mask (fxp0): 255.255.255.0 > Aug 22 20:06:48 home dhclient: New Broadcast Address (fxp0): xx.xx.xx.255 > Aug 22 20:06:48 home dhclient: New Routers (fxp0): xx.xx.xx.1 > Aug 22 20:06:50 home kernel: fxp0: link state changed to UP > Aug 22 20:06:53 home dhclient: New IP Address (fxp0): xx.xx.xx.xx > Aug 22 20:06:53 home kernel: fxp0: link state changed to DOWN > Aug 22 20:06:53 home dhclient: New Subnet Mask (fxp0): 255.255.255.0 > Aug 22 20:06:53 home dhclient: New Broadcast Address (fxp0): xx.xx.xx.255 > Aug 22 20:06:53 home dhclient: New Routers (fxp0): xx.xx.xx.xx > Aug 22 20:06:55 home kernel: fxp0: link state changed to UP > Aug 22 20:07:01 home dhclient: New IP Address (fxp0): xx.xx.xx.xx > Aug 22 20:07:01 home kernel: fxp0: link state changed to DOWN > Aug 22 20:07:01 home dhclient: New Subnet Mask (fxp0): 255.255.255.0 > Aug 22 20:07:01 home dhclient: New Broadcast Address (fxp0): xx.xx.xx.255 > Aug 22 20:07:01 home dhclient: New Routers (fxp0): xx.xx.xx.xx > Aug 22 20:07:03 home kernel: fxp0: link state changed to UP > Aug 22 20:07:07 home dhclient: New IP Address (fxp0): xx.xx.xx.xx > Aug 22 20:07:07 home kernel: fxp0: link state changed to DOWN > Aug 22 20:07:07 home dhclient: New Subnet Mask (fxp0): 255.255.255.0 > Aug 22 20:07:07 home dhclient: New Broadcast Address (fxp0): xx.xx.xx.255 > Aug 22 20:07:07 home dhclient: New Routers (fxp0): xx.xx.xx.xx > Aug 22 20:07:09 home kernel: fxp0: link state changed to UP > Aug 22 20:07:13 home dhclient: New IP Address (fxp0): xx.xx.xx.xx > Aug 22 20:07:13 home kernel: fxp0: link state changed to DOWN > Aug 22 20:07:13 home dhclient: New Subnet Mask (fxp0): 255.255.255.0 > Aug 22 20:07:13 home dhclient: New Broadcast Address (fxp0): xx.xx.xx.255 > Aug 22 20:07:13 home dhclient: New Routers (fxp0): xx.xx.xx.xx > Aug 22 20:07:15 home kernel: fxp0: link state changed to UP Hmm. Perhaps we could use a debouncer to ignore "short" link flaps? Kind of gross (and OpenBSD doesn't do this). For now this change basically ignores link up events if they occur with 5 seconds of the link down event. The 5 is hardcoded which is kind of yuck. Index: dhcpd.h =================================================================== --- dhcpd.h (revision 239564) +++ dhcpd.h (working copy) @@ -209,6 +209,7 @@ int dead; u_int16_t index; int linkstat; + time_t linktime; }; struct timeout { Index: dhclient.c =================================================================== --- dhclient.c (revision 239564) +++ dhclient.c (working copy) @@ -285,8 +285,14 @@ ifi->linkstat ? "up" : "down", linkstat ? "up" : "down"); ifi->linkstat = linkstat; - if (linkstat) + + /* + * XXX: Hardcoded 5 second grace window on + * link flaps. + */ + if (linkstat && (cur_time - ifi->linktime) >= 5) state_reboot(ifi); + ifi->linktime = cur_time; } break; case RTM_IFANNOUNCE: @@ -441,6 +447,7 @@ fprintf(stderr, " got link\n"); } ifi->linkstat = 1; + ifi->linktime = cur_time; if ((nullfd = open(_PATH_DEVNULL, O_RDWR, 0)) == -1) error("cannot open %s: %m", _PATH_DEVNULL); -- John Baldwin From owner-freebsd-current@FreeBSD.ORG Wed Aug 22 20:26:58 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E6691106566C; Wed, 22 Aug 2012 20:26:58 +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 204D88FC15; Wed, 22 Aug 2012 20:26:58 +0000 (UTC) Received: from inpost2.zedat.fu-berlin.de ([130.133.4.69]) by outpost1.zedat.fu-berlin.de (Exim 4.69) with esmtp (envelope-from ) id <1T4HVx-0004rd-3h>; Wed, 22 Aug 2012 22:26:57 +0200 Received: from e178003168.adsl.alicedsl.de ([85.178.3.168] helo=thor.walstatt.dyndns.org) by inpost2.zedat.fu-berlin.de (Exim 4.69) with esmtpsa (envelope-from ) id <1T4HVw-00048S-Tb>; Wed, 22 Aug 2012 22:26:57 +0200 Message-ID: <50354085.2070605@zedat.fu-berlin.de> Date: Wed, 22 Aug 2012 22:26:45 +0200 From: "O. Hartmann" User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:14.0) Gecko/20120810 Thunderbird/14.0 MIME-Version: 1.0 To: Garrett Cooper References: <50337752.8070707@zedat.fu-berlin.de> <1345582381.1632.6.camel@Nokia-N900-42-11> <503487DE.3050807@zedat.fu-berlin.de> <5034DF8B.102@mail.zedat.fu-berlin.de> <50352B03.8020802@zedat.fu-berlin.de> In-Reply-To: X-Enigmail-Version: 1.4.3 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig84BDE460D538188886883A09" X-Originating-IP: 85.178.3.168 Cc: Chris Rees , "O. Hartmann" , Current FreeBSD , =?ISO-8859-1?Q?Bernhard_Fr=F6hlich?= Subject: Re: FreeBSD 10.0-CURRENT r239477 doesn't compile: virtualbox-ose-kmod-4.1.18_1 is marked as broken: Does not compile on FreeBSD < 8.2. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 22 Aug 2012 20:26:59 -0000 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig84BDE460D538188886883A09 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Am 08/22/12 21:56, schrieb Garrett Cooper: > On Wed, Aug 22, 2012 at 11:54 AM, O. Hartmann > wrote: >> Am 08/22/12 17:24, schrieb Garrett Cooper: >>> On Wed, Aug 22, 2012 at 7:02 AM, Chris Rees wrote= : >>>> On 22 August 2012 14:32, O. Hartmann wrote: >>>>> On 08/22/12 15:05, Chris Rees wrote: >>>>>> On 22 August 2012 08:18, O. Hartmann = wrote: >>>>>>> Am 08/21/12 22:53, schrieb Bernhard Fr=F6hlich: >>>>>>>> On Di., 21. Aug. 2012 13:56:02 CEST, O. Hartmann wrote: >>>>>>>> >>>>>>>>> Today I ran into a problem with FreeBSD 10.0-CURRENT #0 r239477= >>>>>>>>> recompiling the VBox kernel module: >>>>>>>>> >>>>>>>>> =3D=3D=3D> Cleaning for virtualbox-ose-kmod-4.1.18_1 >>>>>>>>> =3D=3D=3D> virtualbox-ose-kmod-4.1.18_1 is marked as broken: = Does not compile >>>>>>>>> on FreeBSD < 8.2. >>>>>>>>> *** [all] Error code 1 >>>>>>>>> >>>>>>>>> Stop in /usr/ports/emulators/virtualbox-ose-kmod. >>>>>>>>> >>>>>>>>> The port compiled prior to the updates of today. >>>>>>>>> >>>>>>>>> oh >>>>>>>> >>>>>>>> What is the question? We have deprecated < 8.2 almost five month= s ago because of the memobj r0 rewrite. You're the first who complains ab= out this so I'm pretty sure it was the correct decision to move forward. = Please also keep in mind that 8.1 is already EOL. >>>>>>>> >>>>>>> >>>>>>> I do not understand your complains about my mail to the list. For= your >>>>>>> information: I'm on FreeBSD 10.0-CURRENT and this seems, as far a= s I >>>>>>> know, considered not to be deprecated by now. If I'm wrong in tha= t, sorry. >>>>>> >>>>>> Can you give us the output of make -C >>>>>> /usr/ports/emulators/virtualbox-ose-kmod -VOSVERSION please? >>>>> >>>>> 1000017 >>>>> >>>>>> >>>>>> I think your version of sys/param.h could be out of date. >>>>>> >>>>>> Chris >>>>> >>>>> >>>>> >>>>> As soon as I'm sitting in front of the machine again. But I doubt t= hat >>>>> the sys/param.h is out of date, since that box has been recompiling= >>>>> FreeBSD 10.0-CURRENT now for almost every day. >>>> >>>> Hm, does that mean that the output you gave me earlier was not from >>>> the same machine? >>>> >>>>> When the problem occured, the change to CLANG 3.2-Beta has just bee= n >>>>> introduced, installed with "make buildworld installkernel". This >>>>> procedere also triggers (via /etc/src.conf) >>>>> >>>>> PORTS_MODULES=3D "x11/nvidia-driver" >>>>> PORTS_MODULES+=3D "emulators/virtualbox-ose-kmod" >>>> >>>> Please remove the quotes! [1] >>>> >>>>> the build of the modules for the nvidia GPU and Vbox kernel module.= >>>>> >>>>> Thanks for your response, >>>> >>>> Something really weird is happening here. All that is happening is >>>> that the Makefile is testing against OSVERSION; >>>> >>>> .if ${OSVERSION} < 802000 >>>> BROKEN=3D Does not compile on FreeBSD < 8.2 >>>> .endif >>>> >>>> Since the result from make -VOSVERSION shows that your OSVERSION is >>>> indeed above 802000, I am completely at a loss as to what's going on= >>>> :( >>> >>> I think this is the issue that I was referring to earlier that I note= d >>> to dougb@ but hadn't gotten an opportunity to repro because I've been= >>> busy with other things. >>> >>> What does OSVERSION look like when you run it from make buildkernel >>> (use this patch)? >>> >>> Thanks, >>> -Garrett >>> >>> $ svn diff /usr/src/sys/conf/kern.post.mk >>> Index: /usr/src/sys/conf/kern.post.mk >>> =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 >>> --- /usr/src/sys/conf/kern.post.mk (revision 239292) >>> +++ /usr/src/sys/conf/kern.post.mk (working copy) >>> @@ -61,6 +61,8 @@ >>> OSVERSION=3D${OSRELDATE} \ >>> WRKDIRPREFIX=3D${WRKDIRPREFIX} >>> >>> +.warning "PORTSMODULESENV =3D> ${PORTSMODULESENV}" >>> + >>> # The WRKDIR needs to be cleaned before building, and trying to >>> change the target >>> # with a :C pattern below results in install -> instclean >>> all: >>> >> >> On both systems I have to maintain, the output is: >> >> BOX 1, patched: >> make -C /usr/ports/emulators/virtualbox-ose-kmod -VOSVERSION >> 1000017 >> >> BOX 2, unpatched: >> make -C /usr/ports/emulators/virtualbox-ose-kmod -VOSVERSION >> 1000017 >=20 > You didn't do what I asked. Please re-read the email I sent last night > asking for the output when running make buildkernel. root@thor [src] make -VOSVERSION buildkernel root@thor [src] =2E.. seems to tell me: no output. >=20 >> No difference. >> >> As I reported Chris Rees a moment ago, the "faulty" box was running a >> kernel compiled with CLANG 3.1 while I installed world with the freshl= y >> compiled CLANG 3.2 stuff and then tried to rebuild the kernel module f= or >> VBox with this mixture. The CLANG issue is a wild guess. I didn't foll= ow >> the install procedure for a new world (single user mode startup with n= ew >> kernel, installworld, mergemaster et cetera). I guess something really= >> nasty happened that way and is possibly not worth to be investigated >> further. >> >> After I rebuild and installed world on my lab's box today the regular >> way and faced no problems building the kernel module for virtual box, = I >> guess the problem is none but chasing ghosts ... >=20 > Hmmm... still seems odd, but if it's fixed, oh well... > Thanks, > -Garrett >=20 --------------enig84BDE460D538188886883A09 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.0.19 (FreeBSD) iQEcBAEBAgAGBQJQNUCQAAoJEOgBcD7A/5N8PhsH/jiDn1VFHhZlKoVevedtaxqQ eGAaGhrCnKKaBVlnkdAdsQK/QCLzDwAuT85iz/hEWR9XpUsXSYPOxfUy7DVnEUYb YNmEDHuyDZazSGUrgVQn6a1nZTMtFFnPuPEHztnUyKyrrUdruPw2bjme9MG3J2EB g6hfjAbOGK6JH+Das+DDNp4W3CKucvthIyNSluQiKowY+KGVdOFoMqj+5y4swA+G i8N5kfLuWE0p7SZrjZGoFV4YBTf8eJHzHfm/2/C3yhbyxW8MR/l4Om3rRyCoeUtW F3cymiuHgNWjLhPmUDh1qEZdSIilY957eZtxuZgK9YbApnEISexZaf0zWXHYviw= =LSes -----END PGP SIGNATURE----- --------------enig84BDE460D538188886883A09-- From owner-freebsd-current@FreeBSD.ORG Wed Aug 22 20:45:46 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id AE12D106564A; Wed, 22 Aug 2012 20:45:46 +0000 (UTC) (envelope-from yanegomi@gmail.com) Received: from mail-gg0-f182.google.com (mail-gg0-f182.google.com [209.85.161.182]) by mx1.freebsd.org (Postfix) with ESMTP id 41FAB8FC08; Wed, 22 Aug 2012 20:45:45 +0000 (UTC) Received: by ggnk4 with SMTP id k4so28762ggn.13 for ; Wed, 22 Aug 2012 13:45:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=eoWmXVMlmy7lBX5Z0Z8fhnI2h7mE0UcPi6902bKCBbU=; b=n7O/ecxkgsN2Qj4ZkVWsdQ5N1T6H7k6FTMK/qRbrwqfqOasOS1qNSoO5c9pvL/yEVy TT0PeCJerDsK1PiytY+fZIKxKVOp0hpKA5iPatdkjtQ4kuyt9mDnYlnhMxGA27UBAvtQ gJTF3+rb8XjAb21yU4Cbqdw46uzrZEm+wgMiefHE2lyqL+jiwrWp6VnLxdssrlX2Vwz1 VultbiwkDm9U3sMHDGMU9ha5o/OPSEbfscIP3Uvfsg37WY5H5vtXw9jeTth8fDw63+oV dTKLnWJhOHm4Mt8ZLlNGTPQl2nWkte9cAHBBrMUH0oWLrnmtfA1aHqKNKetZUgk6liHU Yhcg== MIME-Version: 1.0 Received: by 10.60.29.164 with SMTP id l4mr17200290oeh.4.1345668345047; Wed, 22 Aug 2012 13:45:45 -0700 (PDT) Received: by 10.76.142.201 with HTTP; Wed, 22 Aug 2012 13:45:44 -0700 (PDT) In-Reply-To: <50354085.2070605@zedat.fu-berlin.de> References: <50337752.8070707@zedat.fu-berlin.de> <1345582381.1632.6.camel@Nokia-N900-42-11> <503487DE.3050807@zedat.fu-berlin.de> <5034DF8B.102@mail.zedat.fu-berlin.de> <50352B03.8020802@zedat.fu-berlin.de> <50354085.2070605@zedat.fu-berlin.de> Date: Wed, 22 Aug 2012 13:45:44 -0700 Message-ID: From: Garrett Cooper To: "O. Hartmann" Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: Chris Rees , "O. Hartmann" , Current FreeBSD , =?ISO-8859-1?Q?Bernhard_Fr=F6hlich?= Subject: Re: FreeBSD 10.0-CURRENT r239477 doesn't compile: virtualbox-ose-kmod-4.1.18_1 is marked as broken: Does not compile on FreeBSD < 8.2. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 22 Aug 2012 20:45:46 -0000 On Wed, Aug 22, 2012 at 1:26 PM, O. Hartmann wrote: > Am 08/22/12 21:56, schrieb Garrett Cooper: >> On Wed, Aug 22, 2012 at 11:54 AM, O. Hartmann >> wrote: >>> Am 08/22/12 17:24, schrieb Garrett Cooper: >>>> On Wed, Aug 22, 2012 at 7:02 AM, Chris Rees wrote: >>>>> On 22 August 2012 14:32, O. Hartmann wrote: >>>>>> On 08/22/12 15:05, Chris Rees wrote: >>>>>>> On 22 August 2012 08:18, O. Hartmann = wrote: >>>>>>>> Am 08/21/12 22:53, schrieb Bernhard Fr=F6hlich: >>>>>>>>> On Di., 21. Aug. 2012 13:56:02 CEST, O. Hartmann wrote: >>>>>>>>> >>>>>>>>>> Today I ran into a problem with FreeBSD 10.0-CURRENT #0 r239477 >>>>>>>>>> recompiling the VBox kernel module: >>>>>>>>>> >>>>>>>>>> =3D=3D=3D> Cleaning for virtualbox-ose-kmod-4.1.18_1 >>>>>>>>>> =3D=3D=3D> virtualbox-ose-kmod-4.1.18_1 is marked as broken: D= oes not compile >>>>>>>>>> on FreeBSD < 8.2. >>>>>>>>>> *** [all] Error code 1 >>>>>>>>>> >>>>>>>>>> Stop in /usr/ports/emulators/virtualbox-ose-kmod. >>>>>>>>>> >>>>>>>>>> The port compiled prior to the updates of today. >>>>>>>>>> >>>>>>>>>> oh >>>>>>>>> >>>>>>>>> What is the question? We have deprecated < 8.2 almost five months= ago because of the memobj r0 rewrite. You're the first who complains about= this so I'm pretty sure it was the correct decision to move forward. Pleas= e also keep in mind that 8.1 is already EOL. >>>>>>>>> >>>>>>>> >>>>>>>> I do not understand your complains about my mail to the list. For = your >>>>>>>> information: I'm on FreeBSD 10.0-CURRENT and this seems, as far as= I >>>>>>>> know, considered not to be deprecated by now. If I'm wrong in that= , sorry. >>>>>>> >>>>>>> Can you give us the output of make -C >>>>>>> /usr/ports/emulators/virtualbox-ose-kmod -VOSVERSION please? >>>>>> >>>>>> 1000017 >>>>>> >>>>>>> >>>>>>> I think your version of sys/param.h could be out of date. >>>>>>> >>>>>>> Chris >>>>>> >>>>>> >>>>>> >>>>>> As soon as I'm sitting in front of the machine again. But I doubt th= at >>>>>> the sys/param.h is out of date, since that box has been recompiling >>>>>> FreeBSD 10.0-CURRENT now for almost every day. >>>>> >>>>> Hm, does that mean that the output you gave me earlier was not from >>>>> the same machine? >>>>> >>>>>> When the problem occured, the change to CLANG 3.2-Beta has just been >>>>>> introduced, installed with "make buildworld installkernel". This >>>>>> procedere also triggers (via /etc/src.conf) >>>>>> >>>>>> PORTS_MODULES=3D "x11/nvidia-driver" >>>>>> PORTS_MODULES+=3D "emulators/virtualbox-ose-kmod" >>>>> >>>>> Please remove the quotes! [1] >>>>> >>>>>> the build of the modules for the nvidia GPU and Vbox kernel module. >>>>>> >>>>>> Thanks for your response, >>>>> >>>>> Something really weird is happening here. All that is happening is >>>>> that the Makefile is testing against OSVERSION; >>>>> >>>>> .if ${OSVERSION} < 802000 >>>>> BROKEN=3D Does not compile on FreeBSD < 8.2 >>>>> .endif >>>>> >>>>> Since the result from make -VOSVERSION shows that your OSVERSION is >>>>> indeed above 802000, I am completely at a loss as to what's going on >>>>> :( >>>> >>>> I think this is the issue that I was referring to earlier that I noted >>>> to dougb@ but hadn't gotten an opportunity to repro because I've been >>>> busy with other things. >>>> >>>> What does OSVERSION look like when you run it from make buildkernel >>>> (use this patch)? >>>> >>>> Thanks, >>>> -Garrett >>>> >>>> $ svn diff /usr/src/sys/conf/kern.post.mk >>>> Index: /usr/src/sys/conf/kern.post.mk >>>> =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 >>>> --- /usr/src/sys/conf/kern.post.mk (revision 239292) >>>> +++ /usr/src/sys/conf/kern.post.mk (working copy) >>>> @@ -61,6 +61,8 @@ >>>> OSVERSION=3D${OSRELDATE} \ >>>> WRKDIRPREFIX=3D${WRKDIRPREFIX} >>>> >>>> +.warning "PORTSMODULESENV =3D> ${PORTSMODULESENV}" >>>> + >>>> # The WRKDIR needs to be cleaned before building, and trying to >>>> change the target >>>> # with a :C pattern below results in install -> instclean >>>> all: >>>> >>> >>> On both systems I have to maintain, the output is: >>> >>> BOX 1, patched: >>> make -C /usr/ports/emulators/virtualbox-ose-kmod -VOSVERSION >>> 1000017 >>> >>> BOX 2, unpatched: >>> make -C /usr/ports/emulators/virtualbox-ose-kmod -VOSVERSION >>> 1000017 >> >> You didn't do what I asked. Please re-read the email I sent last night >> asking for the output when running make buildkernel. > > root@thor [src] make -VOSVERSION buildkernel > > root@thor [src] > > ... seems to tell me: no output. 1. Apply patch I noted previously to dump out PORTSMODULESENV. 2. Run make buildkernel >bk.log 2>&1. 3. Look for "PORTSMODULESENV =3D> " with the output that prints out OSVERSI= ON=3D. That's what I was referring to in my previous email in complete detail. Thanks, -Garrett From owner-freebsd-current@FreeBSD.ORG Thu Aug 23 00:52:42 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5C8711065670; Thu, 23 Aug 2012 00:52:42 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-pz0-f54.google.com (mail-pz0-f54.google.com [209.85.210.54]) by mx1.freebsd.org (Postfix) with ESMTP id 203618FC08; Thu, 23 Aug 2012 00:52:40 +0000 (UTC) Received: by dadr6 with SMTP id r6so115814dad.13 for ; Wed, 22 Aug 2012 17:52:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=38wIrxOr+ub8y4nI2X+yrAErydekRCU34ZCMGxXkqYk=; b=EPbZA+n+YKygT/m2BMg06MdoYgvyOJ6WqfKUaCFhFuGaJP87056EoEKmoH5B+JRI9S rMoyNCead0a3uP1fQMbbwqsbuFpGrATGO1FMHcjgRb+ZzqojpP3M9E4kFaNbjJdBfBmW HhQ3P+gyEQOR6kxWy4g1BCu1jZWtsCQ5TzbHx+Y2rXZANuYvcGm80kkOlbvDNQ7l9NZo tcf2n23zlSsAI+iSz/DitbEqANIISCgMDQfpaSl6ARLxxsXoalK3nDwDcI1hRfyLOQOw YKI/F1WyoSBmqIvR9Vgu7umNzbGkzMJJHtVh2zZaXp0Qm35hi8uYSBh8sMVR5muoV/ZW b/VQ== MIME-Version: 1.0 Received: by 10.66.85.4 with SMTP id d4mr40588684paz.11.1345683160639; Wed, 22 Aug 2012 17:52:40 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.68.36.106 with HTTP; Wed, 22 Aug 2012 17:52:40 -0700 (PDT) In-Reply-To: <201208221535.01598.jhb@freebsd.org> References: <20120821095527.GA33206@hell.ukr.net> <20120822171253.GB3300@michelle.cdnetworks.com> <20120822172822.GA52909@hell.ukr.net> <201208221535.01598.jhb@freebsd.org> Date: Wed, 22 Aug 2012 17:52:40 -0700 X-Google-Sender-Auth: L77m4Ls4s1pB856ThFmP5453COQ Message-ID: From: Adrian Chadd To: John Baldwin Content-Type: text/plain; charset=ISO-8859-1 Cc: YongHyeon PYUN , Vitalij Satanivskij , freebsd-current@freebsd.org, Peter Jeremy , current@freebsd.org Subject: Re: dhclient cause up/down cycle after 239356 ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 23 Aug 2012 00:52:42 -0000 Ew. Be careful. Your admin may decide to change the VLAN you're on (for example.) You definitely want to renegotiate your link state then. Adrian On 22 August 2012 12:35, John Baldwin wrote: > On Wednesday, August 22, 2012 1:28:22 pm Vitalij Satanivskij wrote: >> ok next round :) >> >> dhclient updated to Revision 239564 >> >> with fxp : >> >> Aug 22 20:06:48 home kernel: fxp0: link state changed to DOWN >> Aug 22 20:06:48 home dhclient: New Subnet Mask (fxp0): 255.255.255.0 >> Aug 22 20:06:48 home dhclient: New Broadcast Address (fxp0): xx.xx.xx.255 >> Aug 22 20:06:48 home dhclient: New Routers (fxp0): xx.xx.xx.1 >> Aug 22 20:06:50 home kernel: fxp0: link state changed to UP >> Aug 22 20:06:53 home dhclient: New IP Address (fxp0): xx.xx.xx.xx >> Aug 22 20:06:53 home kernel: fxp0: link state changed to DOWN >> Aug 22 20:06:53 home dhclient: New Subnet Mask (fxp0): 255.255.255.0 >> Aug 22 20:06:53 home dhclient: New Broadcast Address (fxp0): xx.xx.xx.255 >> Aug 22 20:06:53 home dhclient: New Routers (fxp0): xx.xx.xx.xx >> Aug 22 20:06:55 home kernel: fxp0: link state changed to UP >> Aug 22 20:07:01 home dhclient: New IP Address (fxp0): xx.xx.xx.xx >> Aug 22 20:07:01 home kernel: fxp0: link state changed to DOWN >> Aug 22 20:07:01 home dhclient: New Subnet Mask (fxp0): 255.255.255.0 >> Aug 22 20:07:01 home dhclient: New Broadcast Address (fxp0): xx.xx.xx.255 >> Aug 22 20:07:01 home dhclient: New Routers (fxp0): xx.xx.xx.xx >> Aug 22 20:07:03 home kernel: fxp0: link state changed to UP >> Aug 22 20:07:07 home dhclient: New IP Address (fxp0): xx.xx.xx.xx >> Aug 22 20:07:07 home kernel: fxp0: link state changed to DOWN >> Aug 22 20:07:07 home dhclient: New Subnet Mask (fxp0): 255.255.255.0 >> Aug 22 20:07:07 home dhclient: New Broadcast Address (fxp0): xx.xx.xx.255 >> Aug 22 20:07:07 home dhclient: New Routers (fxp0): xx.xx.xx.xx >> Aug 22 20:07:09 home kernel: fxp0: link state changed to UP >> Aug 22 20:07:13 home dhclient: New IP Address (fxp0): xx.xx.xx.xx >> Aug 22 20:07:13 home kernel: fxp0: link state changed to DOWN >> Aug 22 20:07:13 home dhclient: New Subnet Mask (fxp0): 255.255.255.0 >> Aug 22 20:07:13 home dhclient: New Broadcast Address (fxp0): xx.xx.xx.255 >> Aug 22 20:07:13 home dhclient: New Routers (fxp0): xx.xx.xx.xx >> Aug 22 20:07:15 home kernel: fxp0: link state changed to UP > > Hmm. Perhaps we could use a debouncer to ignore "short" link flaps? Kind of > gross (and OpenBSD doesn't do this). For now this change basically ignores > link up events if they occur with 5 seconds of the link down event. The 5 is > hardcoded which is kind of yuck. > > Index: dhcpd.h > =================================================================== > --- dhcpd.h (revision 239564) > +++ dhcpd.h (working copy) > @@ -209,6 +209,7 @@ > int dead; > u_int16_t index; > int linkstat; > + time_t linktime; > }; > > struct timeout { > Index: dhclient.c > =================================================================== > --- dhclient.c (revision 239564) > +++ dhclient.c (working copy) > @@ -285,8 +285,14 @@ > ifi->linkstat ? "up" : "down", > linkstat ? "up" : "down"); > ifi->linkstat = linkstat; > - if (linkstat) > + > + /* > + * XXX: Hardcoded 5 second grace window on > + * link flaps. > + */ > + if (linkstat && (cur_time - ifi->linktime) >= 5) > state_reboot(ifi); > + ifi->linktime = cur_time; > } > break; > case RTM_IFANNOUNCE: > @@ -441,6 +447,7 @@ > fprintf(stderr, " got link\n"); > } > ifi->linkstat = 1; > + ifi->linktime = cur_time; > > if ((nullfd = open(_PATH_DEVNULL, O_RDWR, 0)) == -1) > error("cannot open %s: %m", _PATH_DEVNULL); > > -- > John Baldwin > _______________________________________________ > 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 Aug 23 00:52:42 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5C8711065670; Thu, 23 Aug 2012 00:52:42 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-pz0-f54.google.com (mail-pz0-f54.google.com [209.85.210.54]) by mx1.freebsd.org (Postfix) with ESMTP id 203618FC08; Thu, 23 Aug 2012 00:52:40 +0000 (UTC) Received: by dadr6 with SMTP id r6so115814dad.13 for ; Wed, 22 Aug 2012 17:52:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=38wIrxOr+ub8y4nI2X+yrAErydekRCU34ZCMGxXkqYk=; b=EPbZA+n+YKygT/m2BMg06MdoYgvyOJ6WqfKUaCFhFuGaJP87056EoEKmoH5B+JRI9S rMoyNCead0a3uP1fQMbbwqsbuFpGrATGO1FMHcjgRb+ZzqojpP3M9E4kFaNbjJdBfBmW HhQ3P+gyEQOR6kxWy4g1BCu1jZWtsCQ5TzbHx+Y2rXZANuYvcGm80kkOlbvDNQ7l9NZo tcf2n23zlSsAI+iSz/DitbEqANIISCgMDQfpaSl6ARLxxsXoalK3nDwDcI1hRfyLOQOw YKI/F1WyoSBmqIvR9Vgu7umNzbGkzMJJHtVh2zZaXp0Qm35hi8uYSBh8sMVR5muoV/ZW b/VQ== MIME-Version: 1.0 Received: by 10.66.85.4 with SMTP id d4mr40588684paz.11.1345683160639; Wed, 22 Aug 2012 17:52:40 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.68.36.106 with HTTP; Wed, 22 Aug 2012 17:52:40 -0700 (PDT) In-Reply-To: <201208221535.01598.jhb@freebsd.org> References: <20120821095527.GA33206@hell.ukr.net> <20120822171253.GB3300@michelle.cdnetworks.com> <20120822172822.GA52909@hell.ukr.net> <201208221535.01598.jhb@freebsd.org> Date: Wed, 22 Aug 2012 17:52:40 -0700 X-Google-Sender-Auth: L77m4Ls4s1pB856ThFmP5453COQ Message-ID: From: Adrian Chadd To: John Baldwin Content-Type: text/plain; charset=ISO-8859-1 Cc: YongHyeon PYUN , Vitalij Satanivskij , freebsd-current@freebsd.org, Peter Jeremy , current@freebsd.org Subject: Re: dhclient cause up/down cycle after 239356 ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 23 Aug 2012 00:52:42 -0000 Ew. Be careful. Your admin may decide to change the VLAN you're on (for example.) You definitely want to renegotiate your link state then. Adrian On 22 August 2012 12:35, John Baldwin wrote: > On Wednesday, August 22, 2012 1:28:22 pm Vitalij Satanivskij wrote: >> ok next round :) >> >> dhclient updated to Revision 239564 >> >> with fxp : >> >> Aug 22 20:06:48 home kernel: fxp0: link state changed to DOWN >> Aug 22 20:06:48 home dhclient: New Subnet Mask (fxp0): 255.255.255.0 >> Aug 22 20:06:48 home dhclient: New Broadcast Address (fxp0): xx.xx.xx.255 >> Aug 22 20:06:48 home dhclient: New Routers (fxp0): xx.xx.xx.1 >> Aug 22 20:06:50 home kernel: fxp0: link state changed to UP >> Aug 22 20:06:53 home dhclient: New IP Address (fxp0): xx.xx.xx.xx >> Aug 22 20:06:53 home kernel: fxp0: link state changed to DOWN >> Aug 22 20:06:53 home dhclient: New Subnet Mask (fxp0): 255.255.255.0 >> Aug 22 20:06:53 home dhclient: New Broadcast Address (fxp0): xx.xx.xx.255 >> Aug 22 20:06:53 home dhclient: New Routers (fxp0): xx.xx.xx.xx >> Aug 22 20:06:55 home kernel: fxp0: link state changed to UP >> Aug 22 20:07:01 home dhclient: New IP Address (fxp0): xx.xx.xx.xx >> Aug 22 20:07:01 home kernel: fxp0: link state changed to DOWN >> Aug 22 20:07:01 home dhclient: New Subnet Mask (fxp0): 255.255.255.0 >> Aug 22 20:07:01 home dhclient: New Broadcast Address (fxp0): xx.xx.xx.255 >> Aug 22 20:07:01 home dhclient: New Routers (fxp0): xx.xx.xx.xx >> Aug 22 20:07:03 home kernel: fxp0: link state changed to UP >> Aug 22 20:07:07 home dhclient: New IP Address (fxp0): xx.xx.xx.xx >> Aug 22 20:07:07 home kernel: fxp0: link state changed to DOWN >> Aug 22 20:07:07 home dhclient: New Subnet Mask (fxp0): 255.255.255.0 >> Aug 22 20:07:07 home dhclient: New Broadcast Address (fxp0): xx.xx.xx.255 >> Aug 22 20:07:07 home dhclient: New Routers (fxp0): xx.xx.xx.xx >> Aug 22 20:07:09 home kernel: fxp0: link state changed to UP >> Aug 22 20:07:13 home dhclient: New IP Address (fxp0): xx.xx.xx.xx >> Aug 22 20:07:13 home kernel: fxp0: link state changed to DOWN >> Aug 22 20:07:13 home dhclient: New Subnet Mask (fxp0): 255.255.255.0 >> Aug 22 20:07:13 home dhclient: New Broadcast Address (fxp0): xx.xx.xx.255 >> Aug 22 20:07:13 home dhclient: New Routers (fxp0): xx.xx.xx.xx >> Aug 22 20:07:15 home kernel: fxp0: link state changed to UP > > Hmm. Perhaps we could use a debouncer to ignore "short" link flaps? Kind of > gross (and OpenBSD doesn't do this). For now this change basically ignores > link up events if they occur with 5 seconds of the link down event. The 5 is > hardcoded which is kind of yuck. > > Index: dhcpd.h > =================================================================== > --- dhcpd.h (revision 239564) > +++ dhcpd.h (working copy) > @@ -209,6 +209,7 @@ > int dead; > u_int16_t index; > int linkstat; > + time_t linktime; > }; > > struct timeout { > Index: dhclient.c > =================================================================== > --- dhclient.c (revision 239564) > +++ dhclient.c (working copy) > @@ -285,8 +285,14 @@ > ifi->linkstat ? "up" : "down", > linkstat ? "up" : "down"); > ifi->linkstat = linkstat; > - if (linkstat) > + > + /* > + * XXX: Hardcoded 5 second grace window on > + * link flaps. > + */ > + if (linkstat && (cur_time - ifi->linktime) >= 5) > state_reboot(ifi); > + ifi->linktime = cur_time; > } > break; > case RTM_IFANNOUNCE: > @@ -441,6 +447,7 @@ > fprintf(stderr, " got link\n"); > } > ifi->linkstat = 1; > + ifi->linktime = cur_time; > > if ((nullfd = open(_PATH_DEVNULL, O_RDWR, 0)) == -1) > error("cannot open %s: %m", _PATH_DEVNULL); > > -- > John Baldwin > _______________________________________________ > 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 Aug 23 01:35:49 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 62ADB106564A; Thu, 23 Aug 2012 01:35:49 +0000 (UTC) (envelope-from peter@rulingia.com) Received: from vps.rulingia.com (host-122-100-2-194.octopus.com.au [122.100.2.194]) by mx1.freebsd.org (Postfix) with ESMTP id CBDFD8FC16; Thu, 23 Aug 2012 01:35:47 +0000 (UTC) Received: from server.rulingia.com (c220-239-249-137.belrs5.nsw.optusnet.com.au [220.239.249.137]) by vps.rulingia.com (8.14.5/8.14.5) with ESMTP id q7N1Zeqj091402 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 23 Aug 2012 11:35:40 +1000 (EST) (envelope-from peter@rulingia.com) X-Bogosity: Ham, spamicity=0.000000 Received: from server.rulingia.com (localhost.rulingia.com [127.0.0.1]) by server.rulingia.com (8.14.5/8.14.5) with ESMTP id q7N1ZYjX032415 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 23 Aug 2012 11:35:34 +1000 (EST) (envelope-from peter@server.rulingia.com) Received: (from peter@localhost) by server.rulingia.com (8.14.5/8.14.5/Submit) id q7N1ZYEb032414; Thu, 23 Aug 2012 11:35:34 +1000 (EST) (envelope-from peter) Date: Thu, 23 Aug 2012 11:35:34 +1000 From: Peter Jeremy To: John Baldwin Message-ID: <20120823013534.GA31015@server.rulingia.com> References: <20120821095527.GA33206@hell.ukr.net> <20120822171253.GB3300@michelle.cdnetworks.com> <20120822172822.GA52909@hell.ukr.net> <201208221535.01598.jhb@freebsd.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="45Z9DzgjV8m4Oswq" Content-Disposition: inline In-Reply-To: <201208221535.01598.jhb@freebsd.org> X-PGP-Key: http://www.rulingia.com/keys/peter.pgp User-Agent: Mutt/1.5.21 (2010-09-15) Cc: YongHyeon PYUN , freebsd-current@freebsd.org Subject: Re: dhclient cause up/down cycle after 239356 ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 23 Aug 2012 01:35:49 -0000 --45Z9DzgjV8m4Oswq Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2012-Aug-22 15:35:01 -0400, John Baldwin wrote: >Hmm. Perhaps we could use a debouncer to ignore "short" link flaps? Kind= of >gross (and OpenBSD doesn't do this). For now this change basically ignores >link up events if they occur with 5 seconds of the link down event. The 5= is >hardcoded which is kind of yuck. I'm also a bit concerned about this for similar reasons to adrian@. We need to distinguish between short link outages caused by (eg) a switch admin reconfiguring the switch (which needs the lease to be re-checked) and those caused by broken NICs which report link status changes when they are touched. Maybe an alternative is to just ignore link flaps when they occur within a few seconds of a script_go(). (And/or make the ignore timeout configurable). Apart from fxp(4), does anyone know how many NICs are similarly broken? Does anyone know why this issue doesn't bite OpenBSD? Does it have a work-around to avoid resetting the link, not report link status changes or just no-one has noticed the issue? BTW to jhb: Can you check your mailer's list configuration. You appear to be adding and leaving in the Cc list. --=20 Peter Jeremy --45Z9DzgjV8m4Oswq Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEARECAAYFAlA1iOYACgkQ/opHv/APuIer+ACfR5VFu11ub75m+ZPCxoYdXZtj iQ4An1RghY5dCpCEMt5tDEAqREGAWhEY =izBM -----END PGP SIGNATURE----- --45Z9DzgjV8m4Oswq-- From owner-freebsd-current@FreeBSD.ORG Thu Aug 23 04:31:36 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 44B13106564A for ; Thu, 23 Aug 2012 04:31:36 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from mail-pb0-f54.google.com (mail-pb0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id 0C3A58FC08 for ; Thu, 23 Aug 2012 04:31:35 +0000 (UTC) Received: by pbbrp2 with SMTP id rp2so600236pbb.13 for ; Wed, 22 Aug 2012 21:31:35 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=sender:subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer :x-gm-message-state; bh=pLXos9u5R0S8zeQs3FFYJ6EVMjjSzt5wEP3GAztmWTc=; b=SKmZbyQ8NfEkCRcPUu2Y4g/41JTzjoQYe/TrPybhuVjMs2ctWbtUbS7WTmf2/R+Hkf C3hWhh5+ZMAZ8p5wAqKi4Sri/uPyHkuf/FI3Z8McrJawZQQBmsw+25mv9MnLM0uq5bgs T6bgIUUcke8/kBr4MK6vmq76ZRTv2g3qFynYw2FS9KG04FD0hljSZuFAblpR8/RJxerN FzPosdwKeWcAgiAnZri/0EYbHjrj1TKbZy4Wimz81aJXILcuVrSadzI/5Of4BCDq/5Pk ZHQiKn1Ixkmd4gRtoh8zBS7ExS6yL+hsZpioIBl7oCnp9nhul+gpPcgei9evToyYo7wD 0HaQ== Received: by 10.66.79.195 with SMTP id l3mr417123pax.33.1345696295436; Wed, 22 Aug 2012 21:31:35 -0700 (PDT) Received: from [10.0.0.63] (50-78-194-198-static.hfc.comcastbusiness.net. [50.78.194.198]) by mx.google.com with ESMTPS id ro7sm5149552pbc.8.2012.08.22.21.31.32 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 22 Aug 2012 21:31:33 -0700 (PDT) Sender: Warner Losh Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii From: Warner Losh In-Reply-To: <20120823013534.GA31015@server.rulingia.com> Date: Wed, 22 Aug 2012 22:31:29 -0600 Content-Transfer-Encoding: quoted-printable Message-Id: References: <20120821095527.GA33206@hell.ukr.net> <20120822171253.GB3300@michelle.cdnetworks.com> <20120822172822.GA52909@hell.ukr.net> <201208221535.01598.jhb@freebsd.org> <20120823013534.GA31015@server.rulingia.com> To: Peter Jeremy X-Mailer: Apple Mail (2.1084) X-Gm-Message-State: ALoCoQkXMGekuOMdaKCUbGwK9yhc8eg0obltsUWxy9413jzpca5FAEcFSvIPXLoXz0hqizjg+C9G Cc: YongHyeon PYUN , freebsd-current@freebsd.org Subject: Re: dhclient cause up/down cycle after 239356 ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 23 Aug 2012 04:31:36 -0000 On Aug 22, 2012, at 7:35 PM, Peter Jeremy wrote: > On 2012-Aug-22 15:35:01 -0400, John Baldwin wrote: >> Hmm. Perhaps we could use a debouncer to ignore "short" link flaps? = Kind of >> gross (and OpenBSD doesn't do this). For now this change basically = ignores >> link up events if they occur with 5 seconds of the link down event. = The 5 is >> hardcoded which is kind of yuck. >=20 > I'm also a bit concerned about this for similar reasons to adrian@. > We need to distinguish between short link outages caused by (eg) a > switch admin reconfiguring the switch (which needs the lease to be > re-checked) and those caused by broken NICs which report link status > changes when they are touched. Maybe an alternative is to just ignore > link flaps when they occur within a few seconds of a script_go(). > (And/or make the ignore timeout configurable). >=20 > Apart from fxp(4), does anyone know how many NICs are similarly > broken? >=20 > Does anyone know why this issue doesn't bite OpenBSD? Does it have > a work-around to avoid resetting the link, not report link status > changes or just no-one has noticed the issue? Speaking of fxp(4), can't it defer reporting link status changes during = the reset sequence it must perform? Wouldn't it be better to fix the = broken driver(s) to behave better than to add a twisty maze of hacks to = dhclient? Warner From owner-freebsd-current@FreeBSD.ORG Thu Aug 23 04:50:54 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 36D031065672; Thu, 23 Aug 2012 04:50:54 +0000 (UTC) (envelope-from pyunyh@gmail.com) Received: from mail-pb0-f54.google.com (mail-pb0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id EDA128FC12; Thu, 23 Aug 2012 04:50:53 +0000 (UTC) Received: by pbbrp2 with SMTP id rp2so625255pbb.13 for ; Wed, 22 Aug 2012 21:50:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:date:to:cc:subject:message-id:reply-to:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=HFmPiWx3CGuNB5oIlJcGJYYdXAbhEYKyVxjiHcn54hU=; b=ICQ1Tl03T77Z4yD1678r773Cr9sfpP+7l52bcO5zm31KsA8YjvVwuHgs9C5842fvsf KiSSzfhC5KTyATNzGXPr+knmbnmtuFFaHy1Uium6ByeYD3PxoHuabg5WPoy86Va11H82 BRSWLqo7B+fBf5msFj/+6wchpoZ72lJHeZQWCWWuFYZiS3pR6K7/IMWLBe1mMejvvsv1 s4rrcZdJR9QYEaFtaSXVNKuM+trTivOn/WRfQcZ0qT64Myqfd1Px+WbzW+TgjZETZKDZ GO3xPSpDi2zLVVdDaQxnMZVfjsRZOVoyH89Dm6jgoOTFjJ9nlAj1Gpse7ME2Soi+d0Vy zofQ== Received: by 10.68.223.164 with SMTP id qv4mr1593017pbc.20.1345697453518; Wed, 22 Aug 2012 21:50:53 -0700 (PDT) Received: from pyunyh@gmail.com (lpe4.p59-icn.cdngp.net. [114.111.62.249]) by mx.google.com with ESMTPS id xd9sm4997321pbc.35.2012.08.22.21.50.49 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 22 Aug 2012 21:50:51 -0700 (PDT) Received: by pyunyh@gmail.com (sSMTP sendmail emulation); Thu, 23 Aug 2012 13:50:43 -0700 From: YongHyeon PYUN Date: Thu, 23 Aug 2012 13:50:43 -0700 To: Peter Jeremy Message-ID: <20120823205043.GC3270@michelle.cdnetworks.com> References: <20120821095527.GA33206@hell.ukr.net> <20120822171253.GB3300@michelle.cdnetworks.com> <20120822172822.GA52909@hell.ukr.net> <201208221535.01598.jhb@freebsd.org> <20120823013534.GA31015@server.rulingia.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20120823013534.GA31015@server.rulingia.com> User-Agent: Mutt/1.4.2.3i Cc: freebsd-current@freebsd.org Subject: Re: dhclient cause up/down cycle after 239356 ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pyunyh@gmail.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Aug 2012 04:50:54 -0000 On Thu, Aug 23, 2012 at 11:35:34AM +1000, Peter Jeremy wrote: > On 2012-Aug-22 15:35:01 -0400, John Baldwin wrote: > >Hmm. Perhaps we could use a debouncer to ignore "short" link flaps? Kind of > >gross (and OpenBSD doesn't do this). For now this change basically ignores > >link up events if they occur with 5 seconds of the link down event. The 5 is > >hardcoded which is kind of yuck. > > I'm also a bit concerned about this for similar reasons to adrian@. > We need to distinguish between short link outages caused by (eg) a > switch admin reconfiguring the switch (which needs the lease to be > re-checked) and those caused by broken NICs which report link status > changes when they are touched. Maybe an alternative is to just ignore > link flaps when they occur within a few seconds of a script_go(). > (And/or make the ignore timeout configurable). > > Apart from fxp(4), does anyone know how many NICs are similarly > broken? FreeBSD used to blindly call driver's if_init() in ether_ioctl() whenever an IP address is assigned to interface. This results in calling foo_init in a driver such that controller/link reset happens after IP address assignment. I tried to fix many ethernet drivers in tree to ignore redundant foo_init() call by checking whether this foo_init() call is the very first time initialization of interface. Both NetBSD/OpenBSD seems to not call if_init() if the driver is already running. Because some controllers(e.g. fxp(4)) may require full controller reset to make multicast work, I couldn't follow their approach. I still don't know what other drivers except fxp(4) require full controller reset. There are too many old ethernet drivers I don't have access. Another reason why fxp(4) requires redundant controller reset is flow control support of the driver. Due to hardware limitation, MAC configuration for negotiated link's flow control parameters also requires controller reset. > > Does anyone know why this issue doesn't bite OpenBSD? Does it have I guess OpenBSD's fxp(4) has to reset controller to update multicast filter but it does not support flow control for fxp(4) yet so OpenBSD may see less number of link flips than that of FreeBSD. > a work-around to avoid resetting the link, not report link status > changes or just no-one has noticed the issue? > > BTW to jhb: Can you check your mailer's list configuration. You > appear to be adding and leaving > in the Cc list. > > -- > Peter Jeremy From owner-freebsd-current@FreeBSD.ORG Thu Aug 23 14:27:47 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C3CC81065672 for ; Thu, 23 Aug 2012 14:27:47 +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 9A5CD8FC0C for ; Thu, 23 Aug 2012 14:27:47 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id ECE7EB963; Thu, 23 Aug 2012 10:27:46 -0400 (EDT) From: John Baldwin To: Peter Jeremy Date: Thu, 23 Aug 2012 08:00:14 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110714-p17; KDE/4.5.5; amd64; ; ) References: <20120821095527.GA33206@hell.ukr.net> <201208221535.01598.jhb@freebsd.org> <20120823013534.GA31015@server.rulingia.com> In-Reply-To: <20120823013534.GA31015@server.rulingia.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Message-Id: <201208230800.14262.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Thu, 23 Aug 2012 10:27:47 -0400 (EDT) Cc: YongHyeon PYUN , freebsd-current@freebsd.org Subject: Re: dhclient cause up/down cycle after 239356 ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 23 Aug 2012 14:27:47 -0000 On Wednesday, August 22, 2012 9:35:34 pm Peter Jeremy wrote: > BTW to jhb: Can you check your mailer's list configuration. You > appear to be adding and leaving > in the Cc list. It's a "feature" of kmail that the kmail developers refuse to provide an option to disable. (It's due to the List-ID for our lists being freebsd-foo@, but the common usage of the lists being foo@. I usually remove the foo@ when replying, but sometimes miss it.) -- John Baldwin From owner-freebsd-current@FreeBSD.ORG Thu Aug 23 14:27:48 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4ED661065673 for ; Thu, 23 Aug 2012 14:27:48 +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 239988FC14 for ; Thu, 23 Aug 2012 14:27:48 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 85C50B964; Thu, 23 Aug 2012 10:27:47 -0400 (EDT) From: John Baldwin To: Peter Jeremy Date: Thu, 23 Aug 2012 08:02:45 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110714-p17; KDE/4.5.5; amd64; ; ) References: <20120821095527.GA33206@hell.ukr.net> <201208221535.01598.jhb@freebsd.org> <20120823013534.GA31015@server.rulingia.com> In-Reply-To: <20120823013534.GA31015@server.rulingia.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Message-Id: <201208230802.45030.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Thu, 23 Aug 2012 10:27:47 -0400 (EDT) Cc: YongHyeon PYUN , freebsd-current@freebsd.org Subject: Re: dhclient cause up/down cycle after 239356 ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 23 Aug 2012 14:27:48 -0000 On Wednesday, August 22, 2012 9:35:34 pm Peter Jeremy wrote: > On 2012-Aug-22 15:35:01 -0400, John Baldwin wrote: > >Hmm. Perhaps we could use a debouncer to ignore "short" link flaps? Kind of > >gross (and OpenBSD doesn't do this). For now this change basically ignores > >link up events if they occur with 5 seconds of the link down event. The 5 is > >hardcoded which is kind of yuck. > > I'm also a bit concerned about this for similar reasons to adrian@. > We need to distinguish between short link outages caused by (eg) a > switch admin reconfiguring the switch (which needs the lease to be > re-checked) and those caused by broken NICs which report link status > changes when they are touched. Maybe an alternative is to just ignore > link flaps when they occur within a few seconds of a script_go(). > (And/or make the ignore timeout configurable). > > Apart from fxp(4), does anyone know how many NICs are similarly > broken? > > Does anyone know why this issue doesn't bite OpenBSD? Does it have > a work-around to avoid resetting the link, not report link status > changes or just no-one has noticed the issue? To be clear, I don't like this hack. If there is a way to fix this in the driver (e.g. not report the link state changes during a reset) that would be far preferable. -- John Baldwin From owner-freebsd-current@FreeBSD.ORG Thu Aug 23 14:35:19 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 814DB1065673 for ; Thu, 23 Aug 2012 14:35:19 +0000 (UTC) (envelope-from luigi@onelab2.iet.unipi.it) Received: from onelab2.iet.unipi.it (onelab2.iet.unipi.it [131.114.59.238]) by mx1.freebsd.org (Postfix) with ESMTP id 472568FC1B for ; Thu, 23 Aug 2012 14:35:17 +0000 (UTC) Received: by onelab2.iet.unipi.it (Postfix, from userid 275) id E4ECB7300A; Thu, 23 Aug 2012 16:54:20 +0200 (CEST) Date: Thu, 23 Aug 2012 16:54:20 +0200 From: Luigi Rizzo To: current@freebsd.org Message-ID: <20120823145420.GB3103@onelab2.iet.unipi.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.3i Cc: Subject: TUNABLE_INT vs TUNABLE_INT_FETCH X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 23 Aug 2012 14:35:19 -0000 Hi, I am a bit unclear on what are the pros and cons of using TUNABLE_INT vs TUNABLE_INT_FETCH within a device driver. As a matter of fact, as i read the definitions in sys/kernel.h I almost wonder whether we need the TUNABLE_INT form at all. can anyone help clarify the differences ? thanks luigi From owner-freebsd-current@FreeBSD.ORG Thu Aug 23 14:52:59 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 04489106566C for ; Thu, 23 Aug 2012 14:52:59 +0000 (UTC) (envelope-from asmrookie@gmail.com) Received: from mail-lb0-f182.google.com (mail-lb0-f182.google.com [209.85.217.182]) by mx1.freebsd.org (Postfix) with ESMTP id 6FC5A8FC08 for ; Thu, 23 Aug 2012 14:52:58 +0000 (UTC) Received: by lbbgg13 with SMTP id gg13so585644lbb.13 for ; Thu, 23 Aug 2012 07:52:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=0ZRILnbCtFGV6Raw+9mFWY6SFFlZdrpEpJfIgGDy7DA=; b=D9YPZsKCfg748YchE0UxEHBacZkDgSXZupr+tPpggbwZReAgGL+M3h84T4UQjJTIJt 9SUrpytCHeB6cNmoJFu7w8kMic1xR6609PJ3p4Gl3/0ozQ76sga2kmueiv+w2GlzAlfd NblJgIR2hyy5J7BWEhzjOIi9pU41pPMPVIoXjnc6h7Fdjl09rooeHJZ3lqMnaw5mHLna yX+vPYWbPKPqBoG6N8ITdG4nzJSFIHmgHHxrD2T6sQxMWwBKUCg/rarf63kHLP1eZgEr qCp//MjoQXcSKsbidldzJoA4i5bv5zuL27i5Fq5j+txUllmTh+wTtzS0L4OMFnYIHIOZ rXUA== MIME-Version: 1.0 Received: by 10.152.112.233 with SMTP id it9mr2006810lab.40.1345733577004; Thu, 23 Aug 2012 07:52:57 -0700 (PDT) Sender: asmrookie@gmail.com Received: by 10.112.102.39 with HTTP; Thu, 23 Aug 2012 07:52:56 -0700 (PDT) In-Reply-To: <20120823145420.GB3103@onelab2.iet.unipi.it> References: <20120823145420.GB3103@onelab2.iet.unipi.it> Date: Thu, 23 Aug 2012 15:52:56 +0100 X-Google-Sender-Auth: 9uwqOn5XA-TmfJ8yUwW5yUtA090 Message-ID: From: Attilio Rao To: Luigi Rizzo Content-Type: text/plain; charset=UTF-8 Cc: current@freebsd.org Subject: Re: TUNABLE_INT vs TUNABLE_INT_FETCH X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: attilio@FreeBSD.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Aug 2012 14:52:59 -0000 On 8/23/12, Luigi Rizzo wrote: > Hi, > I am a bit unclear on what are the pros and cons of using > TUNABLE_INT vs TUNABLE_INT_FETCH within a device driver. TUNABLE_INT is basically the "statically initializer" version of TUNABLE_INT_FETCH. In short terms, you will use TUNABLE_INT_FETCH() in normal functions, while TUNABLE_INT() in data declaration. Attilio -- Peace can only be achieved by understanding - A. Einstein From owner-freebsd-current@FreeBSD.ORG Thu Aug 23 15:46:36 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5235E106566B; Thu, 23 Aug 2012 15:46:36 +0000 (UTC) (envelope-from luigi@onelab2.iet.unipi.it) Received: from onelab2.iet.unipi.it (onelab2.iet.unipi.it [131.114.59.238]) by mx1.freebsd.org (Postfix) with ESMTP id 0E4F78FC14; Thu, 23 Aug 2012 15:46:34 +0000 (UTC) Received: by onelab2.iet.unipi.it (Postfix, from userid 275) id 7416B7300A; Thu, 23 Aug 2012 18:05:43 +0200 (CEST) Date: Thu, 23 Aug 2012 18:05:43 +0200 From: Luigi Rizzo To: Attilio Rao Message-ID: <20120823160543.GD3391@onelab2.iet.unipi.it> References: <20120823145420.GB3103@onelab2.iet.unipi.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i Cc: current@freebsd.org Subject: Re: TUNABLE_INT vs TUNABLE_INT_FETCH X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 23 Aug 2012 15:46:36 -0000 On Thu, Aug 23, 2012 at 03:52:56PM +0100, Attilio Rao wrote: > On 8/23/12, Luigi Rizzo wrote: > > Hi, > > I am a bit unclear on what are the pros and cons of using > > TUNABLE_INT vs TUNABLE_INT_FETCH within a device driver. > > TUNABLE_INT is basically the "statically initializer" version of > TUNABLE_INT_FETCH. > In short terms, you will use TUNABLE_INT_FETCH() in normal functions, > while TUNABLE_INT() in data declaration. The thing is, do we need the data declaration at all ? Using getenv_*() to read the value of a tunable (which is what TUNABLE_INT_FETCH() translates into) has the additional making sure that the variable does not change under your feet e.g. as a result of a kenv. FWIW, the reason i do not particularly like the non-fetch version is the way they are defined: #define TUNABLE_INT(path, var) \ static struct tunable_int __CONCAT(__tunable_int_, __LINE__) = { \ (path), \ (var), \ }; \ SYSINIT(__CONCAT(__Tunable_init_, __LINE__), \ SI_SUB_TUNABLES, SI_ORDER_MIDDLE, tunable_int_init, \ &__CONCAT(__tunable_int_, __LINE__)) note how the identifier uses __LINE__ to make it unique, which means that you cannot have more than one TUNABLE_INT() within the body of another macro (this just hit me yesterday). cheers luigi From owner-freebsd-current@FreeBSD.ORG Thu Aug 23 15:48:28 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 540711065676 for ; Thu, 23 Aug 2012 15:48:28 +0000 (UTC) (envelope-from alan.l.cox@gmail.com) Received: from mail-pb0-f54.google.com (mail-pb0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id 272398FC0A for ; Thu, 23 Aug 2012 15:48:27 +0000 (UTC) Received: by pbbrp2 with SMTP id rp2so1733921pbb.13 for ; Thu, 23 Aug 2012 08:48:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=TjehiaMDmTYOzH+hhF2FCCsSfclkQL6LsIwC3Eaear8=; b=Nb0DkC0kswK6spI29qwJrDP8g3QKg42FwzuaBIYAAcVe5dNWcyrmvs+ZfMAQpE/661 yfa8u5vZ3dcWcI90U6FeNAe0AtgwRBQEO9Yjgy/RTOiyAPC1PaPgIP+jverIYSKKvzk2 W09jHX9yUgWU0svmIaRh8dZT1ug+T9qisVijhjXPU+yzTPfBrtvBSy6vcb+9vK1ypCRD CKUFi2k141l8/CrhqWewhgwUvFdtZ6vwyzkfY99xFdT603fRrLuw22md2XVT8GiWfPJF vxY79tvFYadxi5I2f1zI2J+F24F0DmAw+ghN2rFJ0adOU5TMXLDguG2+E3ycy76OG7jU 2/6A== MIME-Version: 1.0 Received: by 10.68.241.65 with SMTP id wg1mr5835411pbc.25.1345736907770; Thu, 23 Aug 2012 08:48:27 -0700 (PDT) Received: by 10.68.217.40 with HTTP; Thu, 23 Aug 2012 08:48:27 -0700 (PDT) In-Reply-To: <20120822120105.GA63763@onelab2.iet.unipi.it> References: <20120822120105.GA63763@onelab2.iet.unipi.it> Date: Thu, 23 Aug 2012 10:48:27 -0500 Message-ID: From: Alan Cox To: Luigi Rizzo Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: current@freebsd.org Subject: Re: less aggressive contigmalloc ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: alc@freebsd.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Aug 2012 15:48:28 -0000 On Wed, Aug 22, 2012 at 7:01 AM, Luigi Rizzo wrote: > I am trying to make netmap adapt the amount of memory it allocates > to what is available. At its core, it uses contigmalloc() with > small chunks (even down to 1 page) to fetch memory. > > Problem is, i notice that before failing, contigmalloc() > tries to swap out some processes (effectively killing them > because i have no swap configured in my picobsd image). > This happens with both M_WAITOK and M_NOWAIT, the difference > is only in the number of retries it does -- see e.g. > > sys/vm/vm_kern.c :: kmem_alloc_contig() > > where it retries once for M_NOWAIT and 3 times for M_WAITOK. > > I wonder if there is a way to make contigmalloc less aggressive > and fail without killing those innocent processes ? > > Have you actually observed processes being killed with M_NOWAIT? The difference between M_NOWAIT and M_WAITOK is more than just the number of retries. Each successive iteration is more aggressive in its attempt to recover pages. On the first iteration, no pages should be written to swap. Nothing should happen that could result in process termination. Alan From owner-freebsd-current@FreeBSD.ORG Thu Aug 23 15:55:17 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 92635106573C for ; Thu, 23 Aug 2012 15:55:07 +0000 (UTC) (envelope-from asmrookie@gmail.com) Received: from mail-lpp01m010-f54.google.com (mail-lpp01m010-f54.google.com [209.85.215.54]) by mx1.freebsd.org (Postfix) with ESMTP id C9A808FC14 for ; Thu, 23 Aug 2012 15:55:06 +0000 (UTC) Received: by lage12 with SMTP id e12so637981lag.13 for ; Thu, 23 Aug 2012 08:55:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=Uc7DEvbaQiAUYekN6MMLqfd68Tvv9MJ0rGLuVRoWS44=; b=c3MjBzX1GsxOTZLivJb1w7fABLX3m152Oy+9IjJUxpwetQMKAkHcUZ69+NIcCTfkLt 7xbb6t0JYnIUqqD96GxHDqOh6+SC1QrHGo1IuorKxGi0KyjpJ5UVmvnJwO4ZG1SHalZD gLbLRiZ7juQcgd9NdNvzLMMjOD4q5gX+OSh03LOBK6a2/+/NbpX8B+fmclxf3lE3e80m 8IsBEcc0ItlpFupWkJeijw+b/Fkp5mpWjv+OQEtvqBHueFPITTlwbxT4R0H7YQjNiJ2S M4uUXkbgK7ZuE7TRzwrxm3M1HSSKZuVmf6iy2aOLcB2lU5cPCRBDe9UBW+XkVbtEJt5d 63BQ== MIME-Version: 1.0 Received: by 10.112.104.3 with SMTP id ga3mr1117751lbb.77.1345737305227; Thu, 23 Aug 2012 08:55:05 -0700 (PDT) Sender: asmrookie@gmail.com Received: by 10.112.102.39 with HTTP; Thu, 23 Aug 2012 08:55:05 -0700 (PDT) In-Reply-To: <20120823160543.GD3391@onelab2.iet.unipi.it> References: <20120823145420.GB3103@onelab2.iet.unipi.it> <20120823160543.GD3391@onelab2.iet.unipi.it> Date: Thu, 23 Aug 2012 16:55:05 +0100 X-Google-Sender-Auth: X1yG5nDoXfn0Qp-dxZ5fVG24yww Message-ID: From: Attilio Rao To: Luigi Rizzo Content-Type: text/plain; charset=UTF-8 Cc: current@freebsd.org Subject: Re: TUNABLE_INT vs TUNABLE_INT_FETCH X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: attilio@FreeBSD.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Aug 2012 15:55:17 -0000 On Thu, Aug 23, 2012 at 5:05 PM, Luigi Rizzo wrote: > On Thu, Aug 23, 2012 at 03:52:56PM +0100, Attilio Rao wrote: >> On 8/23/12, Luigi Rizzo wrote: >> > Hi, >> > I am a bit unclear on what are the pros and cons of using >> > TUNABLE_INT vs TUNABLE_INT_FETCH within a device driver. >> >> TUNABLE_INT is basically the "statically initializer" version of >> TUNABLE_INT_FETCH. >> In short terms, you will use TUNABLE_INT_FETCH() in normal functions, >> while TUNABLE_INT() in data declaration. > > The thing is, do we need the data declaration at all ? What do you mean with "data declaration"? We need to mimic a "static initialization" usage, so what we do is to use the first SYSINIT() family available (SI_SUB_TUNABLES). You also need the env to look for and the static variable to initialize, so for SYSINIT's sake you need to pack them up in a single argument. Attilio -- Peace can only be achieved by understanding - A. Einstein From owner-freebsd-current@FreeBSD.ORG Thu Aug 23 16:12:36 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AC1CD106564A; Thu, 23 Aug 2012 16:12:36 +0000 (UTC) (envelope-from luigi@onelab2.iet.unipi.it) Received: from onelab2.iet.unipi.it (onelab2.iet.unipi.it [131.114.59.238]) by mx1.freebsd.org (Postfix) with ESMTP id 6C5F08FC0A; Thu, 23 Aug 2012 16:12:36 +0000 (UTC) Received: by onelab2.iet.unipi.it (Postfix, from userid 275) id 494F77300A; Thu, 23 Aug 2012 18:31:45 +0200 (CEST) Date: Thu, 23 Aug 2012 18:31:45 +0200 From: Luigi Rizzo To: alc@freebsd.org Message-ID: <20120823163145.GA3999@onelab2.iet.unipi.it> References: <20120822120105.GA63763@onelab2.iet.unipi.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i Cc: current@freebsd.org Subject: Re: less aggressive contigmalloc ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 23 Aug 2012 16:12:36 -0000 On Thu, Aug 23, 2012 at 10:48:27AM -0500, Alan Cox wrote: > On Wed, Aug 22, 2012 at 7:01 AM, Luigi Rizzo wrote: > > > I am trying to make netmap adapt the amount of memory it allocates > > to what is available. At its core, it uses contigmalloc() with > > small chunks (even down to 1 page) to fetch memory. > > > > Problem is, i notice that before failing, contigmalloc() > > tries to swap out some processes (effectively killing them > > because i have no swap configured in my picobsd image). > > This happens with both M_WAITOK and M_NOWAIT, the difference > > is only in the number of retries it does -- see e.g. > > > > sys/vm/vm_kern.c :: kmem_alloc_contig() > > > > where it retries once for M_NOWAIT and 3 times for M_WAITOK. > > > > I wonder if there is a way to make contigmalloc less aggressive > > and fail without killing those innocent processes ? > > > > > Have you actually observed processes being killed with M_NOWAIT? > > The difference between M_NOWAIT and M_WAITOK is more than just the number > of retries. Each successive iteration is more aggressive in its attempt to > recover pages. On the first iteration, no pages should be written to > swap. Nothing should happen that could result in process termination. yes i do see that. Maybe less aggressive with M_NOWAIT but still kills processes. Here is what i get with a kernel on a qemu machine with not enough memory. This output comes when the kernel is looping around a contigmalloc, getting one page at a time (i have rate-limited prints). The function is netmap_finalize_obj_allocator(), it works for a while, then decides to kill some processes, keeps succeeding, kills some other processes, etc. Eventually memory is over and you see the 'Unable to create...' message at the end. ... 269.005884 netmap_finalize_obj_allocator [593] cluster at 63182 ok PicoBSD (default) (ttyv0) login: pid 60 (getty), uid 0, was killed: out of swap space pid 63 (init), uid 0, was killed: out of swap space pid 62 (init), uid 0, was killed: out of swap space pid 61 (init), uid 0, was killed: out of swap space pid 64 (init), uid 0, was killed: out of swap space pid 51 (getty), uid 0, was killed: out of swap space pid 50 (getty), uid 0, was killed: out of swap space pid 65 (init), uid 0, was killed: out of swap space pid 49 (getty), uid 0, was killed: out of swap space pid 48 (getty), uid 0, was killed: out of swap space pid 47 (getty), uid 0, was killed: out of swap space pid 57 (pkt-gen), uid 0, was killed: out of swap space 269.602751 netmap_finalize_obj_allocator [600] Unable to create cluster at 95452 for 'netmap_buf' allocator If that helps, on this machine i have no swap configured (it is a picobsd image run within qemu) cheers luigi From owner-freebsd-current@FreeBSD.ORG Thu Aug 23 16:26:27 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 87DF5106566C for ; Thu, 23 Aug 2012 16:26:27 +0000 (UTC) (envelope-from jeffreybouquet@yahoo.com) Received: from nm26-vm0.bullet.mail.sp2.yahoo.com (nm26-vm0.bullet.mail.sp2.yahoo.com [98.139.91.230]) by mx1.freebsd.org (Postfix) with SMTP id 2F65B8FC15 for ; Thu, 23 Aug 2012 16:26:27 +0000 (UTC) Received: from [72.30.22.77] by nm26.bullet.mail.sp2.yahoo.com with NNFMP; 23 Aug 2012 16:26:26 -0000 Received: from [72.30.22.33] by tm11.bullet.mail.sp2.yahoo.com with NNFMP; 23 Aug 2012 16:26:26 -0000 Received: from [127.0.0.1] by omp1061.mail.sp2.yahoo.com with NNFMP; 23 Aug 2012 16:26:26 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 755567.4459.bm@omp1061.mail.sp2.yahoo.com Received: (qmail 42019 invoked by uid 60001); 23 Aug 2012 16:26:26 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1345739186; bh=3DspHp/3DlXoy1WBGV5xE3C7i7312TGFXPQFrnJjFDs=; h=X-YMail-OSG:Received:X-Mailer:Message-ID:Date:From:Subject:To:Cc:MIME-Version:Content-Type; b=bV0ZRbQ4tPrKgnJz98gIBYvrb+5kgX1dJsWh9oqrZnGRvOO9ojdg3sEj41EXy/uy6m/uwtXx+8URZI+9olb8La8X3MOzmQrGaNtbeDxamVBBNVnzPDsghC9FgTDNXrKae6MrKMUC7tlfD3Zmru7Dwo5VzSSddcpXMUri1tWK8lI= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:Message-ID:Date:From:Subject:To:Cc:MIME-Version:Content-Type; b=J/kcuFJvYHymiOtNwKcpYFlO90tcuhTQoHn3BvU+rFBW3ZYLB35A1kS4hV49YSqr3Mwt8y1/yWRCIQDzvF8Pco1w5PTVWqAqzg1r75il//9+q5uOZcw3gjAE/cMXPOjHn1/q9cueVCU7tYPeTnC1JQ5V7X1J/W4HIZ/lWqqRNFY=; X-YMail-OSG: B0yPEJ0VM1nHYeMpq_swFO1_7bUPzSMHLOsfllO0SXHgrtW XcrnrsXw9CK6fShCA3fBqUKPkKlLuNer5Nxn7tPLcAldEVG3ATTQK4tGfBGc eP1NeNePCjoDIxLTaYNrHYFEHsXrRBHAGnR096ZL2Rn9NkyuQseg1WmL9GBn EhsycyBXK0fVbDRCPzUacwPU2.Br1z9RV3R1CsjIN49O2BtWpBJq3FlHXw1R o2gJSFovlwINsGmeipb7FHR3eaxPJAa_JGiFJhTVHm9ja3NQ4Gy313pA7gEd xTFKYyf.wIluJHLItxI9WUJqzqU5Uc3_I97WKTVdmgEgzjItrQj8C76vfetw 0K4NuYhQ2rM3CZgXyG1ptX5AmJCulM1wYfJjAWzt6nxufIG_jYGDpfxl0xxo SIs0Vd344YriFJpNLdg.yddwuCIFxyKZu0vyIpD8VHWN7f4AbJtqS4Urba7f iH0wcr7iW0jAf5EEfitYtfTKf6NLwEXi2nv9k5QUY4r34mKKoC3uNayey.f9 Oy10E6BlTBe1ge5sXfsRwTSq8sjQE4.dNOnEXEPbqbt4FKGDPot57kGhumfu w Received: from [66.92.43.99] by web111307.mail.gq1.yahoo.com via HTTP; Thu, 23 Aug 2012 09:26:26 PDT X-Mailer: YahooMailClassic/15.0.8 YahooMailWebService/0.8.121.416 Message-ID: <1345739186.30848.YahooMailClassic@web111307.mail.gq1.yahoo.com> Date: Thu, 23 Aug 2012 09:26:26 -0700 (PDT) From: Jeffrey Bouquet To: freebsd-ports@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailman-Approved-At: Thu, 23 Aug 2012 16:34:44 +0000 Cc: freebsd-current@freebsd.org Subject: pkgng default schedule... registering a few reasons for rethinking the final implementation... X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 23 Aug 2012 16:26:27 -0000 I am following with dread the planned implementation of the deprecation of /var/db/pkg as a package registry... I use each /var/db/pkg directory as a database into the port installation/status, using sed/grep/portmaster/portmanager/.sh scripts/find/pipes etc... to fix stuff. For instance, an upgrade py26 > py27. cd /var/db/pkg ls -lac | grep py26 ls -lac | grep python as the more simple example. .... With due respect to its developers and the persons who agree that the package tools could be upgraded, the mandatory usage of a front-end database to a file directory one is here viewd as mutt-only-mbox, registry-and-bsod rather than /etc/local/rc files, deprecation of sed/grep/find/locate/.sh/portmaster/portmanager as tools to fixup/upgrade the ports that are registered; ... I see concurrently too few tests on lower-end p2, p3 as to whether pkg can run with lesser memory machines (routers...) (pfsense) ... I suspect stalling of successful frontends to bsd (pc-bsd, ghostbsd, pfsense..) due to less-reliability, more-possibility of bugs.. ... Not to mention native tab-completion not dependent upon further customizations, ... Introduces complexity to running earlier versions of BSD virtualized in later versions and vice versa... ... I've innumerable times made "quick work" (2 hours or so) of cross-disk backup/fix/upgrade using /var/db/pkg where doing so with just the pkg tools or my own scripts would take immeasurably longer... ... It would deprecate searching +CONTENTS, for example, or quickly checking the text file +REQUIRED_BY without a database frontend. ... Almost every reply and post have glossed over those points, referring to the benefits of a newer package management system, again glossing over the added memory requirements, number of .so. required, lack of extensive testing across all hardware cpu/memory scenarios... ... "it will be a single tool that will do the job of all the many port/package management scripts currently only available in the ports system (bsdadminscripts)" for example. A single tool, yes. But it won't do all of the edge-case jobs *not* covered by the present pkg_ tools that can be crafted hooking into the /var/db/pkg/ directory structure, with find for example. "pkgng is not a replacement for portmaster or portupgrade..." That was not my question. My concern was with the deprecation of the latter and /var/db/pkg along with the introduction of pkgng. ... Each pkg_ legacy uses about 3-6 .so. afaik. pkg uses 19. ... A review of pkgng on mebsd.com, suggests replacment CLI for tasks one might do with portmaster now. However, they are much more arcane (%H-%M vs -g...) and thus unwelcoming... ... "patches for portmaster and portupgrade to use pkgng tools" Memory requirements with both working together? The ABI between them breaks? ... My concerns are more or less, why should the following *ever* be mandatory... "On both FBSD 10 boxes, the installation of the port security/cyrus-sasl2 got corrupted by "install" and/or "mtree" dumping core and signalling SIGNAL 11. Booting into multiuser mode is impossible, login core dumps SIGNAL 11, many other daemons, too. The only way is to boot into single user mode. An installation failed due to pkg(ng) was missing libarchive.so via portmaster or via core dumping install. By installing on one box, my home box, port security/cyrus-sasl2 manually, luckily install and mtree didn't coredump and it worked - and this procedure rescued me. But on my lab's development box, it didn't work! " (Continues with more equally terrible detail...) (Freebsd-questions, august) ... Or my own experience, today, testing on a p4 pre-p2 memory req. investigations. # pkg stats Unable to open remote database "repo". Try running 'pkg update' first. # pkg update Updating repository catalogue zsh: segmentation fault pkg update ............. So, a kernel option (non default) to deprecate /var/db/pkg? A further development of pkg to concurrently maintain a /var/db/pkg? ...not implying the concurrent deprecation of the latter! Brighter ideas? Thanks for reading these concerns. I am quite perturbed by the announcement of v11 erasing the /var/db/pkg upon which I presently use daily numerous times... And I apologize, in advance, for typos etc. herein... J. Bouquet 2004 v5... From owner-freebsd-current@FreeBSD.ORG Thu Aug 23 16:50:02 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AA067106564A; Thu, 23 Aug 2012 16:50:02 +0000 (UTC) (envelope-from kris@pcbsd.org) Received: from mail.iXsystems.com (newknight.ixsystems.com [206.40.55.70]) by mx1.freebsd.org (Postfix) with ESMTP id 7C2168FC08; Thu, 23 Aug 2012 16:50:02 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by mail.iXsystems.com (Postfix) with ESMTP id 96D671BC4; Thu, 23 Aug 2012 09:50:01 -0700 (PDT) Received: from mail.iXsystems.com ([127.0.0.1]) by localhost (mail.ixsystems.com [127.0.0.1]) (maiad, port 10024) with ESMTP id 37993-09; Thu, 23 Aug 2012 09:50:01 -0700 (PDT) Received: from [192.168.0.182] (75-130-56-30.static.kgpt.tn.charter.com [75.130.56.30]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mail.iXsystems.com (Postfix) with ESMTPSA id 1206D1BC2; Thu, 23 Aug 2012 09:50:00 -0700 (PDT) Message-ID: <50365F37.7040601@pcbsd.org> Date: Thu, 23 Aug 2012 12:49:59 -0400 From: Kris Moore User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:13.0) Gecko/20120621 Thunderbird/13.0.1 MIME-Version: 1.0 To: freebsd-current@freebsd.org, FreeBSD Ports References: <1345739186.30848.YahooMailClassic@web111307.mail.gq1.yahoo.com> In-Reply-To: <1345739186.30848.YahooMailClassic@web111307.mail.gq1.yahoo.com> X-Enigmail-Version: 1.4.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Subject: Re: pkgng default schedule... registering a few reasons for rethinking the final implementation... X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 23 Aug 2012 16:50:02 -0000 On 08/23/2012 12:26, Jeffrey Bouquet wrote: > I am following with dread the planned implementation of the deprecation of /var/db/pkg as a package registry... I use each /var/db/pkg directory as a database into the port installation/status, using sed/grep/portmaster/portmanager/.sh scripts/find/pipes etc... to fix stuff. For instance, an upgrade py26 > py27. > cd /var/db/pkg > ls -lac | grep py26 > ls -lac | grep python > as the more simple example. > .... > With due respect to its developers and the persons who agree that > the package tools could be upgraded, the mandatory > usage of a front-end database to a file directory one > is here viewd as mutt-only-mbox, registry-and-bsod rather > than /etc/local/rc files, deprecation of sed/grep/find/locate/.sh/portmaster/portmanager as tools to fixup/upgrade the ports that are registered; > ... > I see concurrently too few tests on lower-end p2, p3 as to whether > pkg can run with lesser memory machines (routers...) (pfsense) > ... > I suspect stalling of successful frontends to bsd (pc-bsd, ghostbsd, > pfsense..) due to less-reliability, more-possibility of bugs.. > This is of some concern to me as well. A number of our utilities / scripts rely on checking /var/db/pkg as a means to test if a particular package is installed. This is often much faster than running the pkg_* commands, especially when we may be checking thousands of packages in a single run. It will be some work to adjust our utilities to using the various "pkg" commands now, but it can be done. What worries me is performance. If this is significantly slower, it may cause some issues on our end. -- Kris Moore PC-BSD Software iXsystems From owner-freebsd-current@FreeBSD.ORG Thu Aug 23 16:55:00 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6620E106564A; Thu, 23 Aug 2012 16:55:00 +0000 (UTC) (envelope-from utisoft@gmail.com) Received: from mail-bk0-f54.google.com (mail-bk0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id B14F58FC0A; Thu, 23 Aug 2012 16:54:59 +0000 (UTC) Received: by bkcje9 with SMTP id je9so699845bkc.13 for ; Thu, 23 Aug 2012 09:54:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=7ecVlD+UnByvdEGVpmiiG8cvfux/Zo0FU6sAune4588=; b=Fg9Lh4CvL261pbjnCPNHShN2WIchsAjtRhFaK3YA21hryC7LXSgch3d8P/IWkYduh/ g0oJX7GRVcSuhA444LYC/FIbz7azXIIUz9qpy6jNIDxc3Ecu325CTncRuSP4FQcnbuAX FDlX+kslcPuhEHHe/qWAzZMpitsCDOa25LQPMo4qKZp65rvvCoceOO3+NBWjVu4oXaI5 C7K7POTRQFN+hIwnBkup62GffHgTUxQJmxy8w7bQuVJtXwfrwDx1j7/WF/oNXsiDe/+X 8lkT3YJh4bRUcXNi8lWa6dzdrhsSt5Dbzg5R890K/3b2xrrL3fISaav/iNe/dky0yQY1 //Vg== MIME-Version: 1.0 Received: by 10.204.145.82 with SMTP id c18mr826490bkv.133.1345740892710; Thu, 23 Aug 2012 09:54:52 -0700 (PDT) Received: by 10.204.10.141 with HTTP; Thu, 23 Aug 2012 09:54:52 -0700 (PDT) Received: by 10.204.10.141 with HTTP; Thu, 23 Aug 2012 09:54:52 -0700 (PDT) In-Reply-To: <50365F37.7040601@pcbsd.org> References: <1345739186.30848.YahooMailClassic@web111307.mail.gq1.yahoo.com> <50365F37.7040601@pcbsd.org> Date: Thu, 23 Aug 2012 17:54:52 +0100 Message-ID: From: Chris Rees To: Kris Moore Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-current , FreeBSD Mailing List Subject: Re: pkgng default schedule... registering a few reasons for rethinking the final implementation... X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 23 Aug 2012 16:55:00 -0000 On 23 Aug 2012 17:50, "Kris Moore" wrote: > > On 08/23/2012 12:26, Jeffrey Bouquet wrote: > > I am following with dread the planned implementation of the deprecation of /var/db/pkg as a package registry... I use each /var/db/pkg directory as a database into the port installation/status, using sed/grep/portmaster/portmanager/.sh scripts/find/pipes etc... to fix stuff. For instance, an upgrade py26 > py27. > > cd /var/db/pkg > > ls -lac | grep py26 > > ls -lac | grep python > > as the more simple example. > > .... > > With due respect to its developers and the persons who agree that > > the package tools could be upgraded, the mandatory > > usage of a front-end database to a file directory one > > is here viewd as mutt-only-mbox, registry-and-bsod rather > > than /etc/local/rc files, deprecation of sed/grep/find/locate/.sh/portmaster/portmanager as tools to fixup/upgrade the ports that are registered; > > ... > > I see concurrently too few tests on lower-end p2, p3 as to whether > > pkg can run with lesser memory machines (routers...) (pfsense) > > ... > > I suspect stalling of successful frontends to bsd (pc-bsd, ghostbsd, > > pfsense..) due to less-reliability, more-possibility of bugs.. > > > > This is of some concern to me as well. A number of our utilities / > scripts rely on checking /var/db/pkg as a means to test if a particular > package is installed. This is often much faster than running the pkg_* > commands, especially when we may be checking thousands of packages in a > single run. It will be some work to adjust our utilities to using the > various "pkg" commands now, but it can be done. What worries me is > performance. If this is significantly slower, it may cause some issues > on our end. The migration should be no surprise to anyone, since it's been discussed on this very list for a while now. If you have concerns about performance, have you tested them for speed? My instinct is that an sqlite query will be much faster than hundreds of file accesses. Chris From owner-freebsd-current@FreeBSD.ORG Thu Aug 23 17:08:44 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id F3FFA106564A; Thu, 23 Aug 2012 17:08:42 +0000 (UTC) (envelope-from alc@rice.edu) Received: from mh11.mail.rice.edu (mh11.mail.rice.edu [128.42.199.30]) by mx1.freebsd.org (Postfix) with ESMTP id BAA928FC12; Thu, 23 Aug 2012 17:08:42 +0000 (UTC) Received: from mh11.mail.rice.edu (localhost.localdomain [127.0.0.1]) by mh11.mail.rice.edu (Postfix) with ESMTP id 479764C02B4; Thu, 23 Aug 2012 12:08:42 -0500 (CDT) Received: from mh11.mail.rice.edu (localhost.localdomain [127.0.0.1]) by mh11.mail.rice.edu (Postfix) with ESMTP id 461EC4C02AE; Thu, 23 Aug 2012 12:08:42 -0500 (CDT) X-Virus-Scanned: by amavis-2.7.0 at mh11.mail.rice.edu, auth channel Received: from mh11.mail.rice.edu ([127.0.0.1]) by mh11.mail.rice.edu (mh11.mail.rice.edu [127.0.0.1]) (amavis, port 10026) with ESMTP id QwXko6ktEwU4; Thu, 23 Aug 2012 12:08:42 -0500 (CDT) Received: from adsl-216-63-78-18.dsl.hstntx.swbell.net (adsl-216-63-78-18.dsl.hstntx.swbell.net [216.63.78.18]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) (Authenticated sender: alc) by mh11.mail.rice.edu (Postfix) with ESMTPSA id D1EEC4C026D; Thu, 23 Aug 2012 12:08:41 -0500 (CDT) Message-ID: <50366398.2070700@rice.edu> Date: Thu, 23 Aug 2012 12:08:40 -0500 From: Alan Cox User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:8.0) Gecko/20111113 Thunderbird/8.0 MIME-Version: 1.0 To: Luigi Rizzo References: <20120822120105.GA63763@onelab2.iet.unipi.it> <20120823163145.GA3999@onelab2.iet.unipi.it> In-Reply-To: <20120823163145.GA3999@onelab2.iet.unipi.it> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: alc@freebsd.org, current@freebsd.org Subject: Re: less aggressive contigmalloc ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 23 Aug 2012 17:08:44 -0000 On 08/23/2012 11:31, Luigi Rizzo wrote: > On Thu, Aug 23, 2012 at 10:48:27AM -0500, Alan Cox wrote: >> On Wed, Aug 22, 2012 at 7:01 AM, Luigi Rizzo wrote: >> >>> I am trying to make netmap adapt the amount of memory it allocates >>> to what is available. At its core, it uses contigmalloc() with >>> small chunks (even down to 1 page) to fetch memory. >>> >>> Problem is, i notice that before failing, contigmalloc() >>> tries to swap out some processes (effectively killing them >>> because i have no swap configured in my picobsd image). >>> This happens with both M_WAITOK and M_NOWAIT, the difference >>> is only in the number of retries it does -- see e.g. >>> >>> sys/vm/vm_kern.c :: kmem_alloc_contig() >>> >>> where it retries once for M_NOWAIT and 3 times for M_WAITOK. >>> >>> I wonder if there is a way to make contigmalloc less aggressive >>> and fail without killing those innocent processes ? >>> >>> >> Have you actually observed processes being killed with M_NOWAIT? >> >> The difference between M_NOWAIT and M_WAITOK is more than just the number >> of retries. Each successive iteration is more aggressive in its attempt to >> recover pages. On the first iteration, no pages should be written to >> swap. Nothing should happen that could result in process termination. > yes i do see that. > > Maybe less aggressive with M_NOWAIT but still kills processes. Are you compiling world with MALLOC_PRODUCTION? The latest version of jemalloc uses significantly more memory when debugging options are enabled. This first came up in a thread titled "10-CURRENT and swap usage" back in June. Even at its most aggressive, M_WAITOK, contigmalloc() does not directly kill processes. If process death coincides with the use of contigmalloc(), then it is simply the result of earlier, successful contigmalloc() calls, or for that matter any other physical memory allocation calls, having depleted the pool of free pages to the point that the page daemon runs and invokes vm_pageout_oom(). > Here is what i get with a kernel on a qemu machine with not enough > memory. This output comes when the kernel is looping around > a contigmalloc, getting one page at a time (i have rate-limited > prints). The function is netmap_finalize_obj_allocator(), > it works for a while, then decides to kill some processes, > keeps succeeding, kills some other processes, etc. > Eventually memory is over and you see the 'Unable to create...' > message at the end. > > ... > 269.005884 netmap_finalize_obj_allocator [593] cluster at 63182 ok > > PicoBSD (default) (ttyv0) > > login: pid 60 (getty), uid 0, was killed: out of swap space > pid 63 (init), uid 0, was killed: out of swap space > pid 62 (init), uid 0, was killed: out of swap space > pid 61 (init), uid 0, was killed: out of swap space > pid 64 (init), uid 0, was killed: out of swap space > pid 51 (getty), uid 0, was killed: out of swap space > pid 50 (getty), uid 0, was killed: out of swap space > pid 65 (init), uid 0, was killed: out of swap space > pid 49 (getty), uid 0, was killed: out of swap space > pid 48 (getty), uid 0, was killed: out of swap space > pid 47 (getty), uid 0, was killed: out of swap space > pid 57 (pkt-gen), uid 0, was killed: out of swap space > 269.602751 netmap_finalize_obj_allocator [600] Unable to create cluster at 95452 for 'netmap_buf' allocator > > If that helps, on this machine i have no swap configured > (it is a picobsd image run within qemu) > > cheers > luigi > From owner-freebsd-current@FreeBSD.ORG Thu Aug 23 17:10:15 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B02C3106574A; Thu, 23 Aug 2012 17:10:15 +0000 (UTC) (envelope-from mezz.freebsd@gmail.com) Received: from mail-ob0-f182.google.com (mail-ob0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id B72798FC1E; Thu, 23 Aug 2012 17:10:11 +0000 (UTC) Received: by obbun3 with SMTP id un3so2892331obb.13 for ; Thu, 23 Aug 2012 10:10:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=RrR8/zzRzSbMsrDL6b2WQu6muye3WBOtca/0e9jCuhY=; b=CmrpgFazoUT6vtDN9ixWIZu3x0pQU0gS+B47QLsl20tJHFL+4Baj2VnC+fIMKgGVXu pE8T1pebZHRpA+2Ia/C1ftiBaLK5rTynMpGK1z8sgJWpKYQDF8QjLH6uGbzw527PSF4e q6v2Nq4rwnTpJ5RY/a/CSiEs5oaKeeZ+n3c0cJZCUejed41GcZlgO95stQbvQwRbMQ8+ Ctm+d8bo05Va5YXU1bn+LR4AKFlSGENA8O1adJ13XSfSqIDJYz5FLnfKNdstZ/A3DCts 62rGPFR1E2EXZ4pZAmoSUSnM1yjCDiq5nCLTFdHnOwR/qrHVbgLUQnEZDZWw5GjiX/Ry MKgw== MIME-Version: 1.0 Received: by 10.182.53.103 with SMTP id a7mr1684453obp.3.1345741810983; Thu, 23 Aug 2012 10:10:10 -0700 (PDT) Received: by 10.76.97.168 with HTTP; Thu, 23 Aug 2012 10:10:10 -0700 (PDT) In-Reply-To: <50365F37.7040601@pcbsd.org> References: <1345739186.30848.YahooMailClassic@web111307.mail.gq1.yahoo.com> <50365F37.7040601@pcbsd.org> Date: Thu, 23 Aug 2012 12:10:10 -0500 Message-ID: From: Jeremy Messenger To: Kris Moore Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-current@freebsd.org, FreeBSD Ports Subject: Re: pkgng default schedule... registering a few reasons for rethinking the final implementation... X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 23 Aug 2012 17:10:15 -0000 On Thu, Aug 23, 2012 at 11:49 AM, Kris Moore wrote: > On 08/23/2012 12:26, Jeffrey Bouquet wrote: >> I am following with dread the planned implementation of the deprecation = of /var/db/pkg as a package registry... I use each /var/db/pkg directory as= a database into the port installation/status, using sed/grep/portmaster/po= rtmanager/.sh scripts/find/pipes etc... to fix stuff. For instance, an upg= rade py26 > py27. >> cd /var/db/pkg >> ls -lac | grep py26 >> ls -lac | grep python >> as the more simple example. >> .... >> With due respect to its developers and the persons who agree that >> the package tools could be upgraded, the mandatory >> usage of a front-end database to a file directory one >> is here viewd as mutt-only-mbox, registry-and-bsod rather >> than /etc/local/rc files, deprecation of sed/grep/find/locate/.sh/portma= ster/portmanager as tools to fixup/upgrade the ports that are registered; >> ... >> I see concurrently too few tests on lower-end p2, p3 as to whether >> pkg can run with lesser memory machines (routers...) (pfsense) >> ... >> I suspect stalling of successful frontends to bsd (pc-bsd, ghostbsd, >> pfsense..) due to less-reliability, more-possibility of bugs.. >> > > This is of some concern to me as well. A number of our utilities / > scripts rely on checking /var/db/pkg as a means to test if a particular > package is installed. This is often much faster than running the pkg_* > commands, especially when we may be checking thousands of packages in a > single run. It will be some work to adjust our utilities to using the > various "pkg" commands now, but it can be done. What worries me is > performance. If this is significantly slower, it may cause some issues > on our end. Guys, please test it before you say anything. Otherwise it's going to be moved forward without you. > -- > Kris Moore > PC-BSD Software > iXsystems --=20 mezz.freebsd@gmail.com - mezz@FreeBSD.org FreeBSD GNOME Team http://www.FreeBSD.org/gnome/ - gnome@FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Thu Aug 23 17:21:29 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0BD49106566B; Thu, 23 Aug 2012 17:21:29 +0000 (UTC) (envelope-from luigi@onelab2.iet.unipi.it) Received: from onelab2.iet.unipi.it (onelab2.iet.unipi.it [131.114.59.238]) by mx1.freebsd.org (Postfix) with ESMTP id B9E5C8FC08; Thu, 23 Aug 2012 17:21:28 +0000 (UTC) Received: by onelab2.iet.unipi.it (Postfix, from userid 275) id 11C177300A; Thu, 23 Aug 2012 19:40:37 +0200 (CEST) Date: Thu, 23 Aug 2012 19:40:37 +0200 From: Luigi Rizzo To: Attilio Rao Message-ID: <20120823174037.GA4820@onelab2.iet.unipi.it> References: <20120823145420.GB3103@onelab2.iet.unipi.it> <20120823160543.GD3391@onelab2.iet.unipi.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i Cc: current@freebsd.org Subject: Re: TUNABLE_INT vs TUNABLE_INT_FETCH X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 23 Aug 2012 17:21:29 -0000 On Thu, Aug 23, 2012 at 04:55:05PM +0100, Attilio Rao wrote: > On Thu, Aug 23, 2012 at 5:05 PM, Luigi Rizzo wrote: > > On Thu, Aug 23, 2012 at 03:52:56PM +0100, Attilio Rao wrote: > >> On 8/23/12, Luigi Rizzo wrote: > >> > Hi, > >> > I am a bit unclear on what are the pros and cons of using > >> > TUNABLE_INT vs TUNABLE_INT_FETCH within a device driver. > >> > >> TUNABLE_INT is basically the "statically initializer" version of > >> TUNABLE_INT_FETCH. > >> In short terms, you will use TUNABLE_INT_FETCH() in normal functions, > >> while TUNABLE_INT() in data declaration. > > > > The thing is, do we need the data declaration at all ? > > What do you mean with "data declaration"? i am using your words :) > We need to mimic a "static initialization" usage, so what we do is to > use the first SYSINIT() family available (SI_SUB_TUNABLES). You also > need the env to look for and the static variable to initialize, so for > SYSINIT's sake you need to pack them up in a single argument. To explain: as i understand it, kenv variables are created and stored (presumably as strings) even if not explicitly declared as TUNABLE_*(). The role of the SYSINIT() block is presumably to copy the values of interesting entries into C variables (i suppose at boot time, and perhaps even when kenv runs). This should be the 'static initialization' you mention. I think there is only a limited number of cases where this makes sense, in most circumstances the variables passed through the environment should be read explictly via TUNABLE_INT_FETCH() to make sure that they do not change in unexpected moments. This is why in the documentation I'd probably suggest to use the TUNABLE_*_FETCH() variant unless you are really really sure that the variable can change at any time as a result of a kenv call (or make it clear that it *will not* reflect the kenv result, i am not sure how it works). Anyways, thanks for the clarificaiton, now i know what i need to use. cheers luigi From owner-freebsd-current@FreeBSD.ORG Thu Aug 23 17:25:57 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 37840106566B; Thu, 23 Aug 2012 17:25:57 +0000 (UTC) (envelope-from luigi@onelab2.iet.unipi.it) Received: from onelab2.iet.unipi.it (onelab2.iet.unipi.it [131.114.59.238]) by mx1.freebsd.org (Postfix) with ESMTP id 70E058FC0C; Thu, 23 Aug 2012 17:25:56 +0000 (UTC) Received: by onelab2.iet.unipi.it (Postfix, from userid 275) id EF5DE7300A; Thu, 23 Aug 2012 19:45:04 +0200 (CEST) Date: Thu, 23 Aug 2012 19:45:04 +0200 From: Luigi Rizzo To: Alan Cox Message-ID: <20120823174504.GB4820@onelab2.iet.unipi.it> References: <20120822120105.GA63763@onelab2.iet.unipi.it> <20120823163145.GA3999@onelab2.iet.unipi.it> <50366398.2070700@rice.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <50366398.2070700@rice.edu> User-Agent: Mutt/1.4.2.3i Cc: alc@freebsd.org, current@freebsd.org Subject: Re: less aggressive contigmalloc ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 23 Aug 2012 17:25:57 -0000 On Thu, Aug 23, 2012 at 12:08:40PM -0500, Alan Cox wrote: ... > >yes i do see that. > > > >Maybe less aggressive with M_NOWAIT but still kills processes. > > Are you compiling world with MALLOC_PRODUCTION? The latest version of whatever the default is. But: > jemalloc uses significantly more memory when debugging options are > enabled. This first came up in a thread titled "10-CURRENT and swap > usage" back in June. > > Even at its most aggressive, M_WAITOK, contigmalloc() does not directly > kill processes. If process death coincides with the use of > contigmalloc(), then it is simply the result of earlier, successful > contigmalloc() calls, or for that matter any other physical memory > allocation calls, having depleted the pool of free pages to the point > that the page daemon runs and invokes vm_pageout_oom(). does it mean that those previous allocations relied on memory overbooking ? Is there a way to avoid that, then ? cheers luigi From owner-freebsd-current@FreeBSD.ORG Thu Aug 23 17:52:23 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 154A9106564A; Thu, 23 Aug 2012 17:52:23 +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 DCB4D8FC08; Thu, 23 Aug 2012 17:52:22 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 4E6EAB963; Thu, 23 Aug 2012 13:52:22 -0400 (EDT) From: John Baldwin To: freebsd-current@freebsd.org Date: Thu, 23 Aug 2012 13:49:06 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110714-p17; KDE/4.5.5; amd64; ; ) References: <20120823145420.GB3103@onelab2.iet.unipi.it> <20120823174037.GA4820@onelab2.iet.unipi.it> In-Reply-To: <20120823174037.GA4820@onelab2.iet.unipi.it> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201208231349.06372.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Thu, 23 Aug 2012 13:52:22 -0400 (EDT) Cc: Attilio Rao , Luigi Rizzo , current@freebsd.org Subject: Re: TUNABLE_INT vs TUNABLE_INT_FETCH X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 23 Aug 2012 17:52:23 -0000 On Thursday, August 23, 2012 1:40:37 pm Luigi Rizzo wrote: > On Thu, Aug 23, 2012 at 04:55:05PM +0100, Attilio Rao wrote: > > On Thu, Aug 23, 2012 at 5:05 PM, Luigi Rizzo wrote: > > > On Thu, Aug 23, 2012 at 03:52:56PM +0100, Attilio Rao wrote: > > >> On 8/23/12, Luigi Rizzo wrote: > > >> > Hi, > > >> > I am a bit unclear on what are the pros and cons of using > > >> > TUNABLE_INT vs TUNABLE_INT_FETCH within a device driver. > > >> > > >> TUNABLE_INT is basically the "statically initializer" version of > > >> TUNABLE_INT_FETCH. > > >> In short terms, you will use TUNABLE_INT_FETCH() in normal functions, > > >> while TUNABLE_INT() in data declaration. > > > > > > The thing is, do we need the data declaration at all ? > > > > What do you mean with "data declaration"? > > i am using your words :) > > > We need to mimic a "static initialization" usage, so what we do is to > > use the first SYSINIT() family available (SI_SUB_TUNABLES). You also > > need the env to look for and the static variable to initialize, so for > > SYSINIT's sake you need to pack them up in a single argument. > > To explain: as i understand it, kenv variables are created and stored > (presumably as strings) even if not explicitly declared as > TUNABLE_*(). The role of the SYSINIT() block is presumably to > copy the values of interesting entries into C variables > (i suppose at boot time, and perhaps even when kenv runs). > This should be the 'static initialization' you mention. Only at boot time, they are unaffected by 'kenv' running. This is why most tunables that can be changed at runtime have a sysctl of the same name. > I think there is only a limited number of cases where this makes sense, > in most circumstances the variables passed through the environment > should be read explictly via TUNABLE_INT_FETCH() to make sure that > they do not change in unexpected moments. kenv can't change during boot. > This is why in the documentation I'd probably suggest to use > the TUNABLE_*_FETCH() variant unless you are really really > sure that the variable can change at any time as a result of > a kenv call (or make it clear that it *will not* reflect > the kenv result, i am not sure how it works). They have never, ever reflected kenv calls. They are always used for boottime evaluation, and if the code wishes to allow post-boot changes it exports a sysctl of the same name for that purpose. In many cases the code will export a read-only sysctl of the same name even if it can't be changed (this is especially useful for values that have an auto-calculated value if none is provided). -- John Baldwin From owner-freebsd-current@FreeBSD.ORG Thu Aug 23 17:52:23 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 154A9106564A; Thu, 23 Aug 2012 17:52:23 +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 DCB4D8FC08; Thu, 23 Aug 2012 17:52:22 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 4E6EAB963; Thu, 23 Aug 2012 13:52:22 -0400 (EDT) From: John Baldwin To: freebsd-current@freebsd.org Date: Thu, 23 Aug 2012 13:49:06 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110714-p17; KDE/4.5.5; amd64; ; ) References: <20120823145420.GB3103@onelab2.iet.unipi.it> <20120823174037.GA4820@onelab2.iet.unipi.it> In-Reply-To: <20120823174037.GA4820@onelab2.iet.unipi.it> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201208231349.06372.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Thu, 23 Aug 2012 13:52:22 -0400 (EDT) Cc: Attilio Rao , Luigi Rizzo , current@freebsd.org Subject: Re: TUNABLE_INT vs TUNABLE_INT_FETCH X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 23 Aug 2012 17:52:23 -0000 On Thursday, August 23, 2012 1:40:37 pm Luigi Rizzo wrote: > On Thu, Aug 23, 2012 at 04:55:05PM +0100, Attilio Rao wrote: > > On Thu, Aug 23, 2012 at 5:05 PM, Luigi Rizzo wrote: > > > On Thu, Aug 23, 2012 at 03:52:56PM +0100, Attilio Rao wrote: > > >> On 8/23/12, Luigi Rizzo wrote: > > >> > Hi, > > >> > I am a bit unclear on what are the pros and cons of using > > >> > TUNABLE_INT vs TUNABLE_INT_FETCH within a device driver. > > >> > > >> TUNABLE_INT is basically the "statically initializer" version of > > >> TUNABLE_INT_FETCH. > > >> In short terms, you will use TUNABLE_INT_FETCH() in normal functions, > > >> while TUNABLE_INT() in data declaration. > > > > > > The thing is, do we need the data declaration at all ? > > > > What do you mean with "data declaration"? > > i am using your words :) > > > We need to mimic a "static initialization" usage, so what we do is to > > use the first SYSINIT() family available (SI_SUB_TUNABLES). You also > > need the env to look for and the static variable to initialize, so for > > SYSINIT's sake you need to pack them up in a single argument. > > To explain: as i understand it, kenv variables are created and stored > (presumably as strings) even if not explicitly declared as > TUNABLE_*(). The role of the SYSINIT() block is presumably to > copy the values of interesting entries into C variables > (i suppose at boot time, and perhaps even when kenv runs). > This should be the 'static initialization' you mention. Only at boot time, they are unaffected by 'kenv' running. This is why most tunables that can be changed at runtime have a sysctl of the same name. > I think there is only a limited number of cases where this makes sense, > in most circumstances the variables passed through the environment > should be read explictly via TUNABLE_INT_FETCH() to make sure that > they do not change in unexpected moments. kenv can't change during boot. > This is why in the documentation I'd probably suggest to use > the TUNABLE_*_FETCH() variant unless you are really really > sure that the variable can change at any time as a result of > a kenv call (or make it clear that it *will not* reflect > the kenv result, i am not sure how it works). They have never, ever reflected kenv calls. They are always used for boottime evaluation, and if the code wishes to allow post-boot changes it exports a sysctl of the same name for that purpose. In many cases the code will export a read-only sysctl of the same name even if it can't be changed (this is especially useful for values that have an auto-calculated value if none is provided). -- John Baldwin From owner-freebsd-current@FreeBSD.ORG Thu Aug 23 18:29:59 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3F34B106566C; Thu, 23 Aug 2012 18:29:59 +0000 (UTC) (envelope-from jlaffaye.freebsd@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 940B28FC16; Thu, 23 Aug 2012 18:29:57 +0000 (UTC) Received: by eeke52 with SMTP id e52so454300eek.13 for ; Thu, 23 Aug 2012 11:29:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=TllYIeSv5HJzlVroBcHkBIx5JcCJJjlugzUFlkt3PRI=; b=RM6x0r4QKyuDgJyw/UyU2uu8X9TbjE2nr4GtLEB3uU4x5oJraXTfS1iYPtAiER8nBT ZiJ7XVd/CSlfS6sw1Y1JZh6Mo/Wj3TkPz8BPtA9yuS2tYDC85C+hurjRmCCJV8113u1d rdnVOy9rtORkE2pSjkTvRpZ0yNIv/0lPdNRYl9lgGk3xSI58eO+aELFejsvd4aS0darq VZy0bcYb7fiPsZX535ZGRBDvnJaCXXFCPYCM5WUKzifoo5XxNrWBQzkJBeGuzEBSa2tt f4iWVdmuX3IvYCPqHmrxcJTyKsy6KQY7231ZA/Jq8ETBynXLmJXJUeZvfdKaccoGkcpe Kx5A== Received: by 10.14.224.4 with SMTP id w4mr3341302eep.21.1345746596813; Thu, 23 Aug 2012 11:29:56 -0700 (PDT) Received: from ?IPv6:2001:41d0:fc00:100:5cba:b160:79ac:5d0? ([2001:41d0:fc00:100:5cba:b160:79ac:5d0]) by mx.google.com with ESMTPS id u47sm23576701eeo.9.2012.08.23.11.29.54 (version=SSLv3 cipher=OTHER); Thu, 23 Aug 2012 11:29:56 -0700 (PDT) Sender: Julien Laffaye Message-ID: <503676A1.8050202@freebsd.org> Date: Thu, 23 Aug 2012 20:29:53 +0200 From: Julien Laffaye User-Agent: Thunderbird/7.0.1 MIME-Version: 1.0 To: Jeffrey Bouquet References: <1345739186.30848.YahooMailClassic@web111307.mail.gq1.yahoo.com> In-Reply-To: <1345739186.30848.YahooMailClassic@web111307.mail.gq1.yahoo.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org, freebsd-ports@freebsd.org Subject: Re: pkgng default schedule... registering a few reasons for rethinking the final implementation... X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 23 Aug 2012 18:29:59 -0000 On 8/23/2012 6:26 PM, Jeffrey Bouquet wrote: > I am following with dread the planned implementation of the deprecation of /var/db/pkg as a package registry... I use each /var/db/pkg directory as a database into the port installation/status, using sed/grep/portmaster/portmanager/.sh scripts/find/pipes etc... to fix stuff. For instance, an upgrade py26 > py27. > cd /var/db/pkg > ls -lac | grep py26 > ls -lac | grep python > as the more simple example. > .... > With due respect to its developers and the persons who agree that > the package tools could be upgraded, the mandatory > usage of a front-end database to a file directory one > is here viewd as mutt-only-mbox, registry-and-bsod rather > than /etc/local/rc files, deprecation of sed/grep/find/locate/.sh/portmaster/portmanager as tools to fixup/upgrade the ports that are registered; > ... > I see concurrently too few tests on lower-end p2, p3 as to whether > pkg can run with lesser memory machines (routers...) (pfsense) Everyone's is welcome to help us with that! The memory usage can be decreased by using gzip over xz for (un)compression. > ... > I suspect stalling of successful frontends to bsd (pc-bsd, ghostbsd, > pfsense..) due to less-reliability, more-possibility of bugs.. If we get useful detailed bug reports, we will fix 'em! > ... > Not to mention native tab-completion not dependent upon further > customizations, > ... > Introduces complexity to running earlier versions of BSD virtualized > in later versions and vice versa... > ... > I've innumerable times made "quick work" (2 hours or so) of > cross-disk backup/fix/upgrade using /var/db/pkg where doing so > with just the pkg tools or my own scripts would take immeasurably > longer... Why ? > ... > It would deprecate searching +CONTENTS, for example, or quickly > checking the text file +REQUIRED_BY without a database frontend. > ... > Almost every reply and post have glossed over those points, referring > to the benefits of a newer package management system, again glossing > over the added memory requirements, number of .so. required, lack > of extensive testing across all hardware cpu/memory scenarios... > ... > "it will be a single tool that will do the job of all the > many port/package management scripts currently only available > in the ports system (bsdadminscripts)" for example. A single > tool, yes. But it won't do all of the edge-case jobs *not* covered > by the present pkg_ tools that can be crafted hooking into the > /var/db/pkg/ directory structure, with find for example. > "pkgng is not a replacement for portmaster or portupgrade..." That > was not my question. My concern was with the deprecation of > the latter and /var/db/pkg along with the introduction of pkgng. > ... > Each pkg_ legacy uses about 3-6 .so. afaik. > pkg uses 19. 18 :) > ... > A review of pkgng on mebsd.com, suggests replacment CLI for tasks > one might do with portmaster now. However, they are much more > arcane (%H-%M vs -g...) and thus unwelcoming... > ... > "patches for portmaster and portupgrade to use pkgng tools" > Memory requirements with both working together? > The ABI between them breaks? > ... > My concerns are more or less, why should the following *ever* be > mandatory... > "On both FBSD 10 boxes, the installation of the port security/cyrus-sasl2 got > corrupted by "install" and/or "mtree" dumping core and signalling > SIGNAL 11. Booting into multiuser mode is impossible, login core > dumps SIGNAL 11, many other daemons, too. The only way is to boot > into single user mode. > > An installation failed due to pkg(ng) was missing libarchive.so via pkgng only depends on lib in the base system. Why was libarchive.so missing? > portmaster or via core dumping install. By installing on one box, > my home box, port security/cyrus-sasl2 manually, luckily install and > mtree didn't coredump and it worked - and this procedure rescued me. > But on my lab's development box, it didn't work! " > (Continues with more equally terrible detail...) > (Freebsd-questions, august) > ... > Or my own experience, today, testing on a p4 pre-p2 memory req. > investigations. > # pkg stats > Unable to open remote database "repo". Try running 'pkg update' first. > # pkg update > Updating repository catalogue > zsh: segmentation fault pkg update Do you have useful details about this segv, like a backtrace ? > ............. > So, a kernel option (non default) to deprecate /var/db/pkg? > A further development of pkg to concurrently maintain a /var/db/pkg? > ...not implying the concurrent deprecation of the latter! > Brighter ideas? > > Thanks for reading these concerns. I am quite perturbed by the > announcement of v11 erasing the /var/db/pkg upon which I presently > use daily numerous times... > And I apologize, in advance, for typos etc. herein... > > J. Bouquet > 2004 v5... Regards, Julien From owner-freebsd-current@FreeBSD.ORG Thu Aug 23 18:36:02 2012 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 17FE3106564A; Thu, 23 Aug 2012 18:36:02 +0000 (UTC) (envelope-from bapt@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id ED9FD8FC12; Thu, 23 Aug 2012 18:36:01 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q7NIa1BH047601; Thu, 23 Aug 2012 18:36:01 GMT (envelope-from bapt@FreeBSD.org) Received: (from bapt@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q7NIa1Dc047600; Thu, 23 Aug 2012 18:36:01 GMT (envelope-from bapt@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: bapt set sender to bapt@FreeBSD.org using -f Date: Thu, 23 Aug 2012 20:35:59 +0200 From: Baptiste Daroussin To: Julien Laffaye Message-ID: <20120823183558.GB18372@ithaqua.etoilebsd.net> References: <1345739186.30848.YahooMailClassic@web111307.mail.gq1.yahoo.com> <503676A1.8050202@freebsd.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="0eh6TmSyL6TZE2Uz" Content-Disposition: inline In-Reply-To: <503676A1.8050202@freebsd.org> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-current@FreeBSD.org, Jeffrey Bouquet , freebsd-ports@FreeBSD.org Subject: Re: pkgng default schedule... registering a few reasons for rethinking the final implementation... X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 23 Aug 2012 18:36:02 -0000 --0eh6TmSyL6TZE2Uz Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Aug 23, 2012 at 08:29:53PM +0200, Julien Laffaye wrote: > > portmaster or via core dumping install. By installing on one box, > > my home box, port security/cyrus-sasl2 manually, luckily install and > > mtree didn't coredump and it worked - and this procedure rescued me. > > But on my lab's development box, it didn't work! " > > (Continues with more equally terrible detail...) > > (Freebsd-questions, august) > > ... > > Or my own experience, today, testing on a p4 pre-p2 memory req. > > investigations. > > # pkg stats > > Unable to open remote database "repo". Try running 'pkg update' first. > > # pkg update > > Updating repository catalogue > > zsh: segmentation fault pkg update > Do you have useful details about this segv, like a backtrace ? actually this is already fixed in git=20 >=20 > Regards, > Julien > _______________________________________________ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" --0eh6TmSyL6TZE2Uz Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEARECAAYFAlA2eA4ACgkQ8kTtMUmk6Ewq/gCfaWZOtK6/mBuOZYi/+XvMrjMg bsIAn2XLjLm8yZfl98gqR5BS/yM34KfI =8DvX -----END PGP SIGNATURE----- --0eh6TmSyL6TZE2Uz-- From owner-freebsd-current@FreeBSD.ORG Thu Aug 23 19:50:15 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3A9BD1065670; Thu, 23 Aug 2012 19:50:15 +0000 (UTC) (envelope-from kris@pcbsd.org) Received: from mail.iXsystems.com (newknight.ixsystems.com [206.40.55.70]) by mx1.freebsd.org (Postfix) with ESMTP id B669F8FC1B; Thu, 23 Aug 2012 19:50:14 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by mail.iXsystems.com (Postfix) with ESMTP id DFC061B25; Thu, 23 Aug 2012 12:50:13 -0700 (PDT) Received: from mail.iXsystems.com ([127.0.0.1]) by localhost (mail.ixsystems.com [127.0.0.1]) (maiad, port 10024) with ESMTP id 46394-06; Thu, 23 Aug 2012 12:50:13 -0700 (PDT) Received: from [192.168.0.182] (75-130-56-30.static.kgpt.tn.charter.com [75.130.56.30]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mail.iXsystems.com (Postfix) with ESMTPSA id D50831B23; Thu, 23 Aug 2012 12:50:12 -0700 (PDT) Message-ID: <50368973.5040202@pcbsd.org> Date: Thu, 23 Aug 2012 15:50:11 -0400 From: Kris Moore User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:13.0) Gecko/20120621 Thunderbird/13.0.1 MIME-Version: 1.0 To: Jeremy Messenger References: <1345739186.30848.YahooMailClassic@web111307.mail.gq1.yahoo.com> <50365F37.7040601@pcbsd.org> In-Reply-To: X-Enigmail-Version: 1.4.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org, FreeBSD Ports Subject: Re: pkgng default schedule... registering a few reasons for rethinking the final implementation... X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 23 Aug 2012 19:50:15 -0000 On 08/23/2012 13:10, Jeremy Messenger wrote: > On Thu, Aug 23, 2012 at 11:49 AM, Kris Moore wrote: >> On 08/23/2012 12:26, Jeffrey Bouquet wrote: >>> I am following with dread the planned implementation of the deprecation of /var/db/pkg as a package registry... I use each /var/db/pkg directory as a database into the port installation/status, using sed/grep/portmaster/portmanager/.sh scripts/find/pipes etc... to fix stuff. For instance, an upgrade py26 > py27. >>> cd /var/db/pkg >>> ls -lac | grep py26 >>> ls -lac | grep python >>> as the more simple example. >>> .... >>> With due respect to its developers and the persons who agree that >>> the package tools could be upgraded, the mandatory >>> usage of a front-end database to a file directory one >>> is here viewd as mutt-only-mbox, registry-and-bsod rather >>> than /etc/local/rc files, deprecation of sed/grep/find/locate/.sh/portmaster/portmanager as tools to fixup/upgrade the ports that are registered; >>> ... >>> I see concurrently too few tests on lower-end p2, p3 as to whether >>> pkg can run with lesser memory machines (routers...) (pfsense) >>> ... >>> I suspect stalling of successful frontends to bsd (pc-bsd, ghostbsd, >>> pfsense..) due to less-reliability, more-possibility of bugs.. >>> >> This is of some concern to me as well. A number of our utilities / >> scripts rely on checking /var/db/pkg as a means to test if a particular >> package is installed. This is often much faster than running the pkg_* >> commands, especially when we may be checking thousands of packages in a >> single run. It will be some work to adjust our utilities to using the >> various "pkg" commands now, but it can be done. What worries me is >> performance. If this is significantly slower, it may cause some issues >> on our end. > Guys, please test it before you say anything. Otherwise it's going to > be moved forward without you. > > Well, it was about time I got to doing a benchmark of this anyway :) I did quick benchmark of how one of our utilities parses through a list of 1k packages on a newer i5 system: First test, using /var/db/pkg/ check we have been doing: 0.178s 0:00.31 54.8% 0.123s 0:00.26 61.5% 0.099s 0:00.15 60.0% Second test, using "pkg info ": 5.347s 0:11.41 91.7% 5.444s 0:11.52 91.3% 5.878s 0:11.32 91.4% The pkg info command is quite a bit slower in this case, but 5 seconds isn't horrible. Now I ran the same benchmark on a slower 1.66gz Atom system, checking about 1200~ packages: First test, using /var/db/pkg/ check we have been doing: 0.604s 0:00.76 86.8% 0.622s 0:00.77 84.4% 0.614s 0:00.73 90.4% Second test, using "pkg info ": 28.507s 0:54.80 99.1% 28.282s 0:54.60 99.4% 28.302s 0:54.52 99.4% Now this is what concerns me a bit. It took closer to 30 seconds, which is quite a while to wait, especially if a utility like ours has to run these checks when it starts up, to show the user whats installed / not installed on the system. The only way around It I've found is to do a quick "pkg info" on the entire DB, dump that to a list, then begin to grep through that list for each item, but it still takes 10~ seconds on the atom. That may be what I end up having to do, but it still stinks to go from a half a second startup, to 10 seconds each time. Any other ideas on how to do this faster with the new pkgng? -- Kris Moore PC-BSD Software iXsystems From owner-freebsd-current@FreeBSD.ORG Thu Aug 23 20:09:35 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 16112106564A; Thu, 23 Aug 2012 20:09:35 +0000 (UTC) (envelope-from utisoft@gmail.com) Received: from mail-lb0-f182.google.com (mail-lb0-f182.google.com [209.85.217.182]) by mx1.freebsd.org (Postfix) with ESMTP id 555298FC0A; Thu, 23 Aug 2012 20:09:33 +0000 (UTC) Received: by lbbgg13 with SMTP id gg13so829566lbb.13 for ; Thu, 23 Aug 2012 13:09:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type :content-transfer-encoding; bh=0bz0E+s/P0KLZp18sqOoLPR5ciGKkDK9Yg+jodRoUZA=; b=nWzHVmUiui78n1CMVreePkCTs2oZqaPoRQl3ed675/d96JJTHzF1uYjISbqZFWXjti m2pyY4PkSGxf7yrhmi09tKMNjVBYVis13b3cFzmjfZmhe3hl2euuEWgjENcQyRBKilxt X0DouZSdUkwcHnj1HvmqTOjrnooWXk7bq4do1TLpY+svdf0Uvw+DhCqxbSMjwl4RFwKx x+oeJSKaPXSInTmedfeqCoeX2TN8mOECj8I++vNT6kcVgpegiQGj1unrKVe+p2MD6Rae 3CV3MXLNSaCdbNfpzt7AaWZGNRCRzQD8Us5Koqwxo7aht1CtPPzCOcjsKm+DHPEjIXDy jOAQ== Received: by 10.152.146.163 with SMTP id td3mr3143492lab.26.1345752572835; Thu, 23 Aug 2012 13:09:32 -0700 (PDT) MIME-Version: 1.0 Sender: utisoft@gmail.com Received: by 10.112.60.227 with HTTP; Thu, 23 Aug 2012 13:09:00 -0700 (PDT) In-Reply-To: <50368973.5040202@pcbsd.org> References: <1345739186.30848.YahooMailClassic@web111307.mail.gq1.yahoo.com> <50365F37.7040601@pcbsd.org> <50368973.5040202@pcbsd.org> From: Chris Rees Date: Thu, 23 Aug 2012 21:09:00 +0100 X-Google-Sender-Auth: vCGal1TnIHQchit3mlrWyrBLmBQ Message-ID: To: Kris Moore Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: Jeremy Messenger , freebsd-current@freebsd.org, FreeBSD Ports Subject: Re: pkgng default schedule... registering a few reasons for rethinking the final implementation... X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 23 Aug 2012 20:09:35 -0000 On 23 August 2012 20:50, Kris Moore wrote: > On 08/23/2012 13:10, Jeremy Messenger wrote: >> On Thu, Aug 23, 2012 at 11:49 AM, Kris Moore wrote: >>> On 08/23/2012 12:26, Jeffrey Bouquet wrote: >>>> I am following with dread the planned implementation of the deprecatio= n of /var/db/pkg as a package registry... I use each /var/db/pkg directory = as a database into the port installation/status, using sed/grep/portmaster/= portmanager/.sh scripts/find/pipes etc... to fix stuff. For instance, an u= pgrade py26 > py27. >>>> cd /var/db/pkg >>>> ls -lac | grep py26 >>>> ls -lac | grep python >>>> as the more simple example. >>>> .... >>>> With due respect to its developers and the persons who agree that >>>> the package tools could be upgraded, the mandatory >>>> usage of a front-end database to a file directory one >>>> is here viewd as mutt-only-mbox, registry-and-bsod rather >>>> than /etc/local/rc files, deprecation of sed/grep/find/locate/.sh/port= master/portmanager as tools to fixup/upgrade the ports that are registered; >>>> ... >>>> I see concurrently too few tests on lower-end p2, p3 as to whether >>>> pkg can run with lesser memory machines (routers...) (pfsense) >>>> ... >>>> I suspect stalling of successful frontends to bsd (pc-bsd, ghostbsd, >>>> pfsense..) due to less-reliability, more-possibility of bugs.. >>>> >>> This is of some concern to me as well. A number of our utilities / >>> scripts rely on checking /var/db/pkg as a means to test if a particular >>> package is installed. This is often much faster than running the pkg_* >>> commands, especially when we may be checking thousands of packages in a >>> single run. It will be some work to adjust our utilities to using the >>> various "pkg" commands now, but it can be done. What worries me is >>> performance. If this is significantly slower, it may cause some issues >>> on our end. >> Guys, please test it before you say anything. Otherwise it's going to >> be moved forward without you. >> >> > > Well, it was about time I got to doing a benchmark of this anyway :) > > I did quick benchmark of how one of our utilities parses through a list > of 1k packages on a newer i5 system: > > First test, using /var/db/pkg/ check we have been doing: > > 0.178s 0:00.31 54.8% > 0.123s 0:00.26 61.5% > 0.099s 0:00.15 60.0% > > Second test, using "pkg info ": > > 5.347s 0:11.41 91.7% > 5.444s 0:11.52 91.3% > 5.878s 0:11.32 91.4% > > The pkg info command is quite a bit slower in this case, but 5 seconds > isn't horrible. > > Now I ran the same benchmark on a slower 1.66gz Atom system, checking > about 1200~ packages: > > First test, using /var/db/pkg/ check we have been doing: > > 0.604s 0:00.76 86.8% > 0.622s 0:00.77 84.4% > 0.614s 0:00.73 90.4% > > Second test, using "pkg info ": > > 28.507s 0:54.80 99.1% > 28.282s 0:54.60 99.4% > 28.302s 0:54.52 99.4% > > Now this is what concerns me a bit. It took closer to 30 seconds, which > is quite a while to wait, especially if a utility like ours has to run > these checks when it starts up, to show the user whats installed / not > installed on the system. > > The only way around It I've found is to do a quick "pkg info" on the > entire DB, dump that to a list, then begin to grep through that list for > each item, but it still takes 10~ seconds on the atom. That may be what > I end up having to do, but it still stinks to go from a half a second > startup, to 10 seconds each time. Any other ideas on how to do this > faster with the new pkgng? Perhaps refactor your method a little; # Get sample list of packages [crees@pegasus]~% pkg info -qa > pkglist [crees@pegasus]~% wc -l pkglist 712 pkglist # Call pkg info once for each package [crees@pegasus]~% time /dev/null xargs -n 1 pkg info < pkglist > /dev/null 2.18s user 2.32s system 98% cpu 4.544 total # Call pkg info once for all packages [crees@pegasus]~% time pkg info $(cat pkglist) > /dev/null pkg info $(cat pkglist) > /dev/null 0.37s user 0.02s system 98% cpu 0.400 = total Summary; pkgng is awesomely fast... but don't call it lots of times since it has a higher startup time. I presume your code is something like; list_of_packages_to_test=3D$@; for pkg in ${list_of_packages_to_test} do [ -d /var/db/pkg/${pkg} ] && echo Success! Package installed! done ? I don't know exactly what you're testing and how, so I can't offer too much specific advice. Chris From owner-freebsd-current@FreeBSD.ORG Thu Aug 23 20:22:15 2012 Return-Path: Delivered-To: freebsd-current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 40C3F106566B; Thu, 23 Aug 2012 20:22:15 +0000 (UTC) (envelope-from bapt@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 205A28FC12; Thu, 23 Aug 2012 20:22:15 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q7NKMFRc061065; Thu, 23 Aug 2012 20:22:15 GMT (envelope-from bapt@FreeBSD.org) Received: (from bapt@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q7NKMEo7061064; Thu, 23 Aug 2012 20:22:14 GMT (envelope-from bapt@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: bapt set sender to bapt@FreeBSD.org using -f Date: Thu, 23 Aug 2012 22:22:12 +0200 From: Baptiste Daroussin To: Kris Moore Message-ID: <20120823202212.GD18372@ithaqua.etoilebsd.net> References: <1345739186.30848.YahooMailClassic@web111307.mail.gq1.yahoo.com> <50365F37.7040601@pcbsd.org> <50368973.5040202@pcbsd.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="MAH+hnPXVZWQ5cD/" Content-Disposition: inline In-Reply-To: <50368973.5040202@pcbsd.org> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: Jeremy Messenger , freebsd-current@FreeBSD.org, FreeBSD Ports Subject: Re: pkgng default schedule... registering a few reasons for rethinking the final implementation... X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 23 Aug 2012 20:22:15 -0000 --MAH+hnPXVZWQ5cD/ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Aug 23, 2012 at 03:50:11PM -0400, Kris Moore wrote: > On 08/23/2012 13:10, Jeremy Messenger wrote: > > On Thu, Aug 23, 2012 at 11:49 AM, Kris Moore wrote: > >> On 08/23/2012 12:26, Jeffrey Bouquet wrote: > >>> I am following with dread the planned implementation of the deprecati= on of /var/db/pkg as a package registry... I use each /var/db/pkg directory= as a database into the port installation/status, using sed/grep/portmaster= /portmanager/.sh scripts/find/pipes etc... to fix stuff. For instance, an = upgrade py26 > py27. > >>> cd /var/db/pkg > >>> ls -lac | grep py26 > >>> ls -lac | grep python > >>> as the more simple example. > >>> .... > >>> With due respect to its developers and the persons who agree that > >>> the package tools could be upgraded, the mandatory > >>> usage of a front-end database to a file directory one > >>> is here viewd as mutt-only-mbox, registry-and-bsod rather > >>> than /etc/local/rc files, deprecation of sed/grep/find/locate/.sh/por= tmaster/portmanager as tools to fixup/upgrade the ports that are registered; > >>> ... > >>> I see concurrently too few tests on lower-end p2, p3 as to whether > >>> pkg can run with lesser memory machines (routers...) (pfsense) > >>> ... > >>> I suspect stalling of successful frontends to bsd (pc-bsd, ghostbsd, > >>> pfsense..) due to less-reliability, more-possibility of bugs.. > >>> > >> This is of some concern to me as well. A number of our utilities / > >> scripts rely on checking /var/db/pkg as a means to test if a particular > >> package is installed. This is often much faster than running the pkg_* > >> commands, especially when we may be checking thousands of packages in a > >> single run. It will be some work to adjust our utilities to using the > >> various "pkg" commands now, but it can be done. What worries me is > >> performance. If this is significantly slower, it may cause some issues > >> on our end. > > Guys, please test it before you say anything. Otherwise it's going to > > be moved forward without you. > > > > >=20 > Well, it was about time I got to doing a benchmark of this anyway :) >=20 > I did quick benchmark of how one of our utilities parses through a list > of 1k packages on a newer i5 system: >=20 > First test, using /var/db/pkg/ check we have been doing: >=20 > 0.178s 0:00.31 54.8% > 0.123s 0:00.26 61.5% > 0.099s 0:00.15 60.0% > =20 > Second test, using "pkg info ": >=20 > 5.347s 0:11.41 91.7%=20 > 5.444s 0:11.52 91.3% > 5.878s 0:11.32 91.4% >=20 > The pkg info command is quite a bit slower in this case, but 5 seconds > isn't horrible. >=20 > Now I ran the same benchmark on a slower 1.66gz Atom system, checking > about 1200~ packages: >=20 > First test, using /var/db/pkg/ check we have been doing: >=20 > 0.604s 0:00.76 86.8% > 0.622s 0:00.77 84.4% > 0.614s 0:00.73 90.4% > =20 > Second test, using "pkg info ": >=20 > 28.507s 0:54.80 99.1% > 28.282s 0:54.60 99.4% > 28.302s 0:54.52 99.4% >=20 > Now this is what concerns me a bit. It took closer to 30 seconds, which > is quite a while to wait, especially if a utility like ours has to run > these checks when it starts up, to show the user whats installed / not > installed on the system. >=20 > The only way around It I've found is to do a quick "pkg info" on the > entire DB, dump that to a list, then begin to grep through that list for > each item, but it still takes 10~ seconds on the atom. That may be what > I end up having to do, but it still stinks to go from a half a second > startup, to 10 seconds each time. Any other ideas on how to do this > faster with the new pkgng? >=20 > --=20 > Kris Moore > PC-BSD Software > iXsystems >=20 > _______________________________________________ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org" Do you have an example of what information you are trying to get out of that list of packages? Or even better do you have a sample of your script so that I can convert it= to pkgng? (For your informations most of the scripts people gave me, that I converted= to pkgng are faster with pkgng) regards, Bapt --MAH+hnPXVZWQ5cD/ Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEARECAAYFAlA2kPQACgkQ8kTtMUmk6EzfCgCguBvXiooNgle2GvBC+ZmLeDgn mM4AoKDRM4tFrRI+IumrrazwCvgsOklK =YTFV -----END PGP SIGNATURE----- --MAH+hnPXVZWQ5cD/-- From owner-freebsd-current@FreeBSD.ORG Thu Aug 23 20:31:59 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 59E391065670 for ; Thu, 23 Aug 2012 20:31:59 +0000 (UTC) (envelope-from ohauer@gmx.de) Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by mx1.freebsd.org (Postfix) with SMTP id 8EE898FC0C for ; Thu, 23 Aug 2012 20:31:58 +0000 (UTC) Received: (qmail invoked by alias); 23 Aug 2012 20:31:57 -0000 Received: from p578be941.dip0.t-ipconnect.de (EHLO [192.168.0.100]) [87.139.233.65] by mail.gmx.net (mp036) with SMTP; 23 Aug 2012 22:31:57 +0200 X-Authenticated: #1956535 X-Provags-ID: V01U2FsdGVkX1+ErnVkAA6E1jZbczPG4aSt6FLYbYj3i4hyYrqobt uZ3S3Z2VQf7BXy Message-ID: <5036933B.8030603@gmx.de> Date: Thu, 23 Aug 2012 22:31:55 +0200 From: olli hauer User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:14.0) Gecko/20120713 Thunderbird/14.0 MIME-Version: 1.0 To: Kris Moore References: <1345739186.30848.YahooMailClassic@web111307.mail.gq1.yahoo.com> <50365F37.7040601@pcbsd.org> <50368973.5040202@pcbsd.org> In-Reply-To: <50368973.5040202@pcbsd.org> X-Enigmail-Version: 1.4.3 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 Cc: freebsd-current@freebsd.org, FreeBSD Ports Subject: Re: pkgng default schedule... registering a few reasons for rethinking the final implementation... X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 23 Aug 2012 20:31:59 -0000 On 2012-08-23 21:50, Kris Moore wrote: > On 08/23/2012 13:10, Jeremy Messenger wrote: >> On Thu, Aug 23, 2012 at 11:49 AM, Kris Moore wrote: >>> On 08/23/2012 12:26, Jeffrey Bouquet wrote: >>>> I am following with dread the planned implementation of the deprecation of /var/db/pkg as a package registry... I use each /var/db/pkg directory as a database into the port installation/status, using sed/grep/portmaster/portmanager/.sh scripts/find/pipes etc... to fix stuff. For instance, an upgrade py26 > py27. >>>> cd /var/db/pkg >>>> ls -lac | grep py26 >>>> ls -lac | grep python >>>> as the more simple example. >>>> .... >>>> With due respect to its developers and the persons who agree that >>>> the package tools could be upgraded, the mandatory >>>> usage of a front-end database to a file directory one >>>> is here viewd as mutt-only-mbox, registry-and-bsod rather >>>> than /etc/local/rc files, deprecation of sed/grep/find/locate/.sh/portmaster/portmanager as tools to fixup/upgrade the ports that are registered; >>>> ... >>>> I see concurrently too few tests on lower-end p2, p3 as to whether >>>> pkg can run with lesser memory machines (routers...) (pfsense) >>>> ... >>>> I suspect stalling of successful frontends to bsd (pc-bsd, ghostbsd, >>>> pfsense..) due to less-reliability, more-possibility of bugs.. >>>> >>> This is of some concern to me as well. A number of our utilities / >>> scripts rely on checking /var/db/pkg as a means to test if a particular >>> package is installed. This is often much faster than running the pkg_* >>> commands, especially when we may be checking thousands of packages in a >>> single run. It will be some work to adjust our utilities to using the >>> various "pkg" commands now, but it can be done. What worries me is >>> performance. If this is significantly slower, it may cause some issues >>> on our end. >> Guys, please test it before you say anything. Otherwise it's going to >> be moved forward without you. >> >> > > Well, it was about time I got to doing a benchmark of this anyway :) > > I did quick benchmark of how one of our utilities parses through a list > of 1k packages on a newer i5 system: > > First test, using /var/db/pkg/ check we have been doing: > > 0.178s 0:00.31 54.8% > 0.123s 0:00.26 61.5% > 0.099s 0:00.15 60.0% > > Second test, using "pkg info ": > > 5.347s 0:11.41 91.7% > 5.444s 0:11.52 91.3% > 5.878s 0:11.32 91.4% > > The pkg info command is quite a bit slower in this case, but 5 seconds > isn't horrible. > > Now I ran the same benchmark on a slower 1.66gz Atom system, checking > about 1200~ packages: > > First test, using /var/db/pkg/ check we have been doing: > > 0.604s 0:00.76 86.8% > 0.622s 0:00.77 84.4% > 0.614s 0:00.73 90.4% > > Second test, using "pkg info ": > > 28.507s 0:54.80 99.1% > 28.282s 0:54.60 99.4% > 28.302s 0:54.52 99.4% > > Now this is what concerns me a bit. It took closer to 30 seconds, which > is quite a while to wait, especially if a utility like ours has to run > these checks when it starts up, to show the user whats installed / not > installed on the system. > > The only way around It I've found is to do a quick "pkg info" on the > entire DB, dump that to a list, then begin to grep through that list for > each item, but it still takes 10~ seconds on the atom. That may be what > I end up having to do, but it still stinks to go from a half a second > startup, to 10 seconds each time. Any other ideas on how to do this > faster with the new pkgng? > Hi Kris, can you describe what exactly the script is doing. Are you aware that you can feed direct SQL to pkg ? $> echo 'select origin,name,version,comment from packages;' | pkg shell At the beginning I was also a little skeptic, but even for older (slow) machines it works well here. One note, on small systems keep an eye on /var/cache/pkg -- Regards, olli From owner-freebsd-current@FreeBSD.ORG Thu Aug 23 20:50:28 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 938961065673; Thu, 23 Aug 2012 20:50:28 +0000 (UTC) (envelope-from kris@pcbsd.org) Received: from mail.iXsystems.com (newknight.ixsystems.com [206.40.55.70]) by mx1.freebsd.org (Postfix) with ESMTP id 66AC18FC19; Thu, 23 Aug 2012 20:50:27 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by mail.iXsystems.com (Postfix) with ESMTP id 8ABF812E0; Thu, 23 Aug 2012 13:50:27 -0700 (PDT) Received: from mail.iXsystems.com ([127.0.0.1]) by localhost (mail.ixsystems.com [127.0.0.1]) (maiad, port 10024) with ESMTP id 53071-04; Thu, 23 Aug 2012 13:50:27 -0700 (PDT) Received: from [192.168.0.182] (75-130-56-30.static.kgpt.tn.charter.com [75.130.56.30]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mail.iXsystems.com (Postfix) with ESMTPSA id BA66212D7; Thu, 23 Aug 2012 13:50:26 -0700 (PDT) Message-ID: <50369791.8050605@pcbsd.org> Date: Thu, 23 Aug 2012 16:50:25 -0400 From: Kris Moore User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:13.0) Gecko/20120621 Thunderbird/13.0.1 MIME-Version: 1.0 To: olli hauer References: <1345739186.30848.YahooMailClassic@web111307.mail.gq1.yahoo.com> <50365F37.7040601@pcbsd.org> <50368973.5040202@pcbsd.org> <5036933B.8030603@gmx.de> In-Reply-To: <5036933B.8030603@gmx.de> X-Enigmail-Version: 1.4.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org, FreeBSD Ports Subject: Re: pkgng default schedule... registering a few reasons for rethinking the final implementation... X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 23 Aug 2012 20:50:28 -0000 On 08/23/2012 16:31, olli hauer wrote: > On 2012-08-23 21:50, Kris Moore wrote: >> On 08/23/2012 13:10, Jeremy Messenger wrote: >>> On Thu, Aug 23, 2012 at 11:49 AM, Kris Moore wrote: >>>> On 08/23/2012 12:26, Jeffrey Bouquet wrote: >>>>> I am following with dread the planned implementation of the deprecation of /var/db/pkg as a package registry... I use each /var/db/pkg directory as a database into the port installation/status, using sed/grep/portmaster/portmanager/.sh scripts/find/pipes etc... to fix stuff. For instance, an upgrade py26 > py27. >>>>> cd /var/db/pkg >>>>> ls -lac | grep py26 >>>>> ls -lac | grep python >>>>> as the more simple example. >>>>> .... >>>>> With due respect to its developers and the persons who agree that >>>>> the package tools could be upgraded, the mandatory >>>>> usage of a front-end database to a file directory one >>>>> is here viewd as mutt-only-mbox, registry-and-bsod rather >>>>> than /etc/local/rc files, deprecation of sed/grep/find/locate/.sh/portmaster/portmanager as tools to fixup/upgrade the ports that are registered; >>>>> ... >>>>> I see concurrently too few tests on lower-end p2, p3 as to whether >>>>> pkg can run with lesser memory machines (routers...) (pfsense) >>>>> ... >>>>> I suspect stalling of successful frontends to bsd (pc-bsd, ghostbsd, >>>>> pfsense..) due to less-reliability, more-possibility of bugs.. >>>>> >>>> This is of some concern to me as well. A number of our utilities / >>>> scripts rely on checking /var/db/pkg as a means to test if a particular >>>> package is installed. This is often much faster than running the pkg_* >>>> commands, especially when we may be checking thousands of packages in a >>>> single run. It will be some work to adjust our utilities to using the >>>> various "pkg" commands now, but it can be done. What worries me is >>>> performance. If this is significantly slower, it may cause some issues >>>> on our end. >>> Guys, please test it before you say anything. Otherwise it's going to >>> be moved forward without you. >>> >>> >> Well, it was about time I got to doing a benchmark of this anyway :) >> >> I did quick benchmark of how one of our utilities parses through a list >> of 1k packages on a newer i5 system: >> >> First test, using /var/db/pkg/ check we have been doing: >> >> 0.178s 0:00.31 54.8% >> 0.123s 0:00.26 61.5% >> 0.099s 0:00.15 60.0% >> >> Second test, using "pkg info ": >> >> 5.347s 0:11.41 91.7% >> 5.444s 0:11.52 91.3% >> 5.878s 0:11.32 91.4% >> >> The pkg info command is quite a bit slower in this case, but 5 seconds >> isn't horrible. >> >> Now I ran the same benchmark on a slower 1.66gz Atom system, checking >> about 1200~ packages: >> >> First test, using /var/db/pkg/ check we have been doing: >> >> 0.604s 0:00.76 86.8% >> 0.622s 0:00.77 84.4% >> 0.614s 0:00.73 90.4% >> >> Second test, using "pkg info ": >> >> 28.507s 0:54.80 99.1% >> 28.282s 0:54.60 99.4% >> 28.302s 0:54.52 99.4% >> >> Now this is what concerns me a bit. It took closer to 30 seconds, which >> is quite a while to wait, especially if a utility like ours has to run >> these checks when it starts up, to show the user whats installed / not >> installed on the system. >> >> The only way around It I've found is to do a quick "pkg info" on the >> entire DB, dump that to a list, then begin to grep through that list for >> each item, but it still takes 10~ seconds on the atom. That may be what >> I end up having to do, but it still stinks to go from a half a second >> startup, to 10 seconds each time. Any other ideas on how to do this >> faster with the new pkgng? >> > Hi Kris, > > can you describe what exactly the script is doing. > > Are you aware that you can feed direct SQL to pkg ? > $> echo 'select origin,name,version,comment from packages;' | pkg shell > > At the beginning I was also a little skeptic, but even for older (slow) machines it works well here. > One note, on small systems keep an eye on /var/cache/pkg > > -- > Regards, > olli > _______________________________________________ > 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" I'm discussing it with Bapt off-list, but the problem isn't the initial getting of a list of packages. It's that we have to pass multiple "sets" of packages, and get some result back, like "ALL installed", "NONE installed", or "SOME installed". This means we are having to do some extra parsing after getting the initial list back, to determine those results. We have to do that with a number of collections of arbitrary packages (30+) and it is somewhat time-critical for the impatient user clicking between jails to see what package collections are installed on each :) The old way was pretty quick, usually Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id CC79D106566B; Thu, 23 Aug 2012 20:51:50 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-pb0-f54.google.com (mail-pb0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id 968A48FC21; Thu, 23 Aug 2012 20:51:50 +0000 (UTC) Received: by pbbrp2 with SMTP id rp2so2229104pbb.13 for ; Thu, 23 Aug 2012 13:51:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=unVyY+VYk3r6jJWKtNhRpbjCTe9b095zr4YHv0UTtAc=; b=aNwDqUsGzG9keu/NaqG+oCGMsOh0k0xSCe3KEX02vZPs0vI/LjDr7pfL+7Mc0s92PC tbcP6e7aYbn/wZXI11zzSB7OQDhfZUXZpZtf9FtpsloFqu56d3QarYYCVs0NI/wrA89t ctv2JVoak8ec+OJ7rfUBqd4N4Z7evYFH06tD1TFmDSjuL9bTFbpevTdwxR+waF7HRo5Q YVBpGM/xtxdrPlel2dJ9p3bUtcHnOodx6n1eeDqoXG+htg+Sg3pRn5c0XQVQ0a1U+Iv2 Xr3amLZXQtUWkZPF56zO7GcLXZbULAAZlnxILu/otDwlxqwzgjBz4pj4R/xbfVTvbwqA 2upQ== MIME-Version: 1.0 Received: by 10.68.129.131 with SMTP id nw3mr7647262pbb.43.1345755110332; Thu, 23 Aug 2012 13:51:50 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.68.36.106 with HTTP; Thu, 23 Aug 2012 13:51:50 -0700 (PDT) In-Reply-To: <50368973.5040202@pcbsd.org> References: <1345739186.30848.YahooMailClassic@web111307.mail.gq1.yahoo.com> <50365F37.7040601@pcbsd.org> <50368973.5040202@pcbsd.org> Date: Thu, 23 Aug 2012 13:51:50 -0700 X-Google-Sender-Auth: vf58SR7s1vhlYLIbUM06EQ9fmjs Message-ID: From: Adrian Chadd To: Kris Moore Content-Type: text/plain; charset=ISO-8859-1 Cc: Jeremy Messenger , freebsd-current@freebsd.org, FreeBSD Ports Subject: Re: pkgng default schedule... registering a few reasons for rethinking the final implementation... X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 23 Aug 2012 20:51:50 -0000 Hm, it's sqlite, so if the tables are indexed correctly, that should be a quick query? Or is it recursing through each dependency and listing that too? adrian From owner-freebsd-current@FreeBSD.ORG Thu Aug 23 21:25:46 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx2.freebsd.org (mx2.freebsd.org [IPv6:2001:4f8:fff6::35]) by hub.freebsd.org (Postfix) with ESMTP id 6AAE1106566C; Thu, 23 Aug 2012 21:25:46 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from [127.0.0.1] (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id 98E7E14E6CC; Thu, 23 Aug 2012 21:25:43 +0000 (UTC) Message-ID: <50369FD6.4030100@FreeBSD.org> Date: Thu, 23 Aug 2012 14:25:42 -0700 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:14.0) Gecko/20120713 Thunderbird/14.0 MIME-Version: 1.0 To: Ivan Voras References: <20120820194313.GC23607@ithaqua.etoilebsd.net> <20120821132643.GE37262@felucia.tataz.chchile.org> <20120821134623.GH5044@ithaqua.etoilebsd.net> <5033D0C0.4030805@FreeBSD.org> <20120821190500.GA46595@ithaqua.etoilebsd.net> <5033E39C.3060700@FreeBSD.org> <20120821194208.GC46595@ithaqua.etoilebsd.net> <5033E6BA.8080309@FreeBSD.org> <5033EC58.3000801@FreeBSD.org> In-Reply-To: X-Enigmail-Version: 1.4.3 OpenPGP: id=1A1ABC84 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: pkgng 1.0 release schedule, and HEAD switch to pkgng by default schedule X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 23 Aug 2012 21:25:46 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 8/22/2012 5:27 AM, Ivan Voras wrote: > On 21/08/2012 22:15, Doug Barton wrote: > >> And in this case, it doesn't matter how awesome the new tools >> are, they are a MAJOR paradigm shift for how users interact with >> ports, and we are > > Unless I've missed something, Yes, you've missed quite a lot actually. You really need to follow the discussion on ports@ if you want to stay up to speed. > pkgng is actually *zero* paradigm shift for users familiar with > *ports*, and here's why: people using ports can and will continue > to use ports the way they are used to. AFAIK, the infrastructure > which registers port installation is already there and there are > also patches for portupgrade and portmaster which make them > interact nicely with the new package database. For users who only have very limited interaction with the ports tree this is probably true. But what we're seeing is that a lot of users (especially those with larger installations, and re-packagers like PC-BSD) have more than simple/limited ports interaction. For those users the change is going to take time, sometimes significant time to adjust to. > The only important aspect of this is that the actual package > database format changed (IMO, immensely for the better) and there > are several other port management utilities which may need to be > changed. People who got used to manually altering the old > text-based package database will learn either not to do it anymore, > since whole classes of errors have now become impossible to have, > or learn how to do it with the new format. > > Can you explain what you mean as the "paradigm shift" for ports > users here? You just described it. And I certainly hope that the change is indeed for the better, however that has yet to be demonstrated on a large scale. I think shifting the default for 10 is going to give us more data on this point, which is a good thing. But making it mandatory in 10 is premature. > OTOH, people using *binary packages* (the very few and miserable > users that they are since the old binary package infrastructure has > sucked for the last decade or so), will get their world turned > upside down, but for the better, and hopefully grow in numbers. No argument from me on the sucking, but the number of users using the existing packages is not "few." There are more consumers of the FreeBSD-distributed packages than you probably realize. But more importantly there are a LOT of enterprise users who roll their own package infrastructure. I have been trying to get across to some of our src-centric Illuminati for years just how valuable/important the ports are to the FreeBSD Operating _System_. For better or worse I think that this change is going to bear out the truth of what I (and others of course) have been saying. Doug - -- I am only one, but I am one. I cannot do everything, but I can do something. And I will not let what I cannot do interfere with what I can do. -- Edward Everett Hale, (1822 - 1909) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (MingW32) iQEcBAEBCAAGBQJQNp/WAAoJEFzGhvEaGryEpIkH/AqfqLIugyLDWv6ehzaKhne8 pGCIGL6bS6naRzpvMu+hzA+eEg/ZnAp5tOjC2e0qowi50e5fF8CKEt11eZKOkyXA FPQX00kX3KTKMyHd6SEsp6AL5FAihBASN9rVs3BGqBXge/ViI9HIDRBKpQW+11Yd tH3wdCSfflI3UpteyJFFumIxITuTvAhYPBzSFEoThNAmf58qJWTNx8zW5jS3/lis OnCWApouUfYOKdimbpRbguYiAnuX7o/Vrwvc9XQ6awsATDWNSPgf4kgaPvwnp9HH eUlFtsNInlFMT9pwQhS2oQtIccx0BYsCQIXkCNQFIjddvRuUeVNjB5Vdqq7NuLk= =kUKF -----END PGP SIGNATURE----- From owner-freebsd-current@FreeBSD.ORG Thu Aug 23 21:33:16 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 98FB5106566C; Thu, 23 Aug 2012 21:33:16 +0000 (UTC) (envelope-from jilles@stack.nl) Received: from mx1.stack.nl (relay04.stack.nl [IPv6:2001:610:1108:5010::107]) by mx1.freebsd.org (Postfix) with ESMTP id 301068FC17; Thu, 23 Aug 2012 21:33:16 +0000 (UTC) Received: from snail.stack.nl (snail.stack.nl [IPv6:2001:610:1108:5010::131]) by mx1.stack.nl (Postfix) with ESMTP id B50341DD5B8; Thu, 23 Aug 2012 23:33:13 +0200 (CEST) Received: by snail.stack.nl (Postfix, from userid 1677) id 90CA62847B; Thu, 23 Aug 2012 23:33:13 +0200 (CEST) Date: Thu, 23 Aug 2012 23:33:13 +0200 From: Jilles Tjoelker To: Kris Moore Message-ID: <20120823213313.GA56606@stack.nl> References: <1345739186.30848.YahooMailClassic@web111307.mail.gq1.yahoo.com> <50365F37.7040601@pcbsd.org> <50368973.5040202@pcbsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <50368973.5040202@pcbsd.org> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: Jeremy Messenger , freebsd-current@freebsd.org, FreeBSD Ports Subject: Re: pkgng default schedule... registering a few reasons for rethinking the final implementation... X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 23 Aug 2012 21:33:16 -0000 On Thu, Aug 23, 2012 at 03:50:11PM -0400, Kris Moore wrote: > Well, it was about time I got to doing a benchmark of this anyway :) > I did quick benchmark of how one of our utilities parses through a list > of 1k packages on a newer i5 system: > First test, using /var/db/pkg/ check we have been doing: > 0.178s 0:00.31 54.8% > 0.123s 0:00.26 61.5% > 0.099s 0:00.15 60.0% > Second test, using "pkg info ": > 5.347s 0:11.41 91.7% > 5.444s 0:11.52 91.3% > 5.878s 0:11.32 91.4% > The pkg info command is quite a bit slower in this case, but 5 seconds > isn't horrible. > [snip] > The only way around It I've found is to do a quick "pkg info" on the > entire DB, dump that to a list, then begin to grep through that list for > each item, but it still takes 10~ seconds on the atom. That may be what > I end up having to do, but it still stinks to go from a half a second > startup, to 10 seconds each time. Any other ideas on how to do this > faster with the new pkgng? Don't use grep: the list is not big enough to make it worth it. What should work fairly efficiently is to store a list of packages in a shell variable once and then check each sub-package without external programs. list=$(pkg query %n-%v) for pkgwithversion in ...; do case $'\n'$list$'\n' in *$'\n'"$pkgwithversion"$'\n'*) echo yes ;; *) echo no ;; esac done This does assume that the list does not change during the loop. Also, instead of pName=`echo $pkg | rev | cut -d "-" -f 2-25 | rev` try pName=${pkg%-*} and use arithmetic expansion ($((...))) instead of invoking expr where possible. -- Jilles Tjoelker From owner-freebsd-current@FreeBSD.ORG Thu Aug 23 21:54:24 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 88DDF1065672 for ; Thu, 23 Aug 2012 21:54:24 +0000 (UTC) (envelope-from imp@bsdimp.com) Received: from mail-pb0-f54.google.com (mail-pb0-f54.google.com [209.85.160.54]) by mx1.freebsd.org (Postfix) with ESMTP id EB1138FC12 for ; Thu, 23 Aug 2012 21:54:23 +0000 (UTC) Received: by pbbrp2 with SMTP id rp2so2304682pbb.13 for ; Thu, 23 Aug 2012 14:54:23 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=sender:subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer :x-gm-message-state; bh=J2a+iKNkuWOyH0hr9G8t9Ley3phi9hs2Tsl4mg/ze5Q=; b=NNPpndmuxFb61+X+6d9tc8+ZItmskZ8f/DkrX7UqDWPrtR3krOsJ9urzfb7iZyHtc2 qs2WRAvbC82kSSOdQNQ/RnUdIszp58Ll6X/MPLpDh5FSub+avtR+jlin9GdKk+rf3SpC 2ptg5Cv0N7KG+b9UHkNW6v78KkkMN031NhrbMq7kg9urLkXBoevn9pwJRMMzJ+uvflWp dcwS+UjJVdQaAubV4xMVsOD6A8Y5HG3f7Ir6qGPPdyeCBwqdxcTTREAMIpV0OWgABcJh ybc0Dgdt8BDv0lHuNAtLLJPZXtqzoNh6d/JGmAn62kNo4c3WsXv7Oyr8e1k1iQ2vA1VD bb/A== Received: by 10.68.200.227 with SMTP id jv3mr7756481pbc.162.1345758863495; Thu, 23 Aug 2012 14:54:23 -0700 (PDT) Received: from [10.30.101.53] ([209.117.142.2]) by mx.google.com with ESMTPS id gf8sm6778315pbc.52.2012.08.23.14.54.22 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 23 Aug 2012 14:54:23 -0700 (PDT) Sender: Warner Losh Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii From: Warner Losh In-Reply-To: <20120823174504.GB4820@onelab2.iet.unipi.it> Date: Thu, 23 Aug 2012 15:54:20 -0600 Content-Transfer-Encoding: quoted-printable Message-Id: References: <20120822120105.GA63763@onelab2.iet.unipi.it> <20120823163145.GA3999@onelab2.iet.unipi.it> <50366398.2070700@rice.edu> <20120823174504.GB4820@onelab2.iet.unipi.it> To: Luigi Rizzo X-Mailer: Apple Mail (2.1084) X-Gm-Message-State: ALoCoQmQX+qu3EYgWddQgAt7EYl9kLl9BLn1mUV3dNyvgFtlvEFiFSmz/jhSHquZ0Y7wtVkFeRmD Cc: alc@freebsd.org, current@freebsd.org, Alan Cox Subject: Re: less aggressive contigmalloc ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 23 Aug 2012 21:54:24 -0000 On Aug 23, 2012, at 11:45 AM, Luigi Rizzo wrote: > On Thu, Aug 23, 2012 at 12:08:40PM -0500, Alan Cox wrote: > ... >>> yes i do see that. >>>=20 >>> Maybe less aggressive with M_NOWAIT but still kills processes. >>=20 >> Are you compiling world with MALLOC_PRODUCTION? The latest version = of=20 >=20 > whatever the default is. But: The default is OFF, so jemalloc uses oodles and oodles more memory than = before. On any system less than 256MB that I've tried to boot on lately = I've had to define MALLOC_PRODUCTION (which, btw, should be named = WITH_MALLOC_DEBUG instead to conform to our naming scheme for options, = but I digress). With MALLOC_PRODUCTION defined, I boot on 32MB systems = with about 8MB of RAM to spare when I get to the login prompt. Warner >> jemalloc uses significantly more memory when debugging options are=20 >> enabled. This first came up in a thread titled "10-CURRENT and swap=20= >> usage" back in June. >>=20 >> Even at its most aggressive, M_WAITOK, contigmalloc() does not = directly=20 >> kill processes. If process death coincides with the use of=20 >> contigmalloc(), then it is simply the result of earlier, successful=20= >> contigmalloc() calls, or for that matter any other physical memory=20 >> allocation calls, having depleted the pool of free pages to the point=20= >> that the page daemon runs and invokes vm_pageout_oom(). >=20 > does it mean that those previous allocations relied on memory = overbooking ? > Is there a way to avoid that, then ? >=20 > cheers > luigi > _______________________________________________ > 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 Aug 23 22:20:07 2012 Return-Path: Delivered-To: current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 16880106564A; Thu, 23 Aug 2012 22:20:07 +0000 (UTC) (envelope-from swills@FreeBSD.org) Received: from mouf.net (mouf.net [IPv6:2607:fc50:0:4400:216:3eff:fe69:33b3]) by mx1.freebsd.org (Postfix) with ESMTP id B72088FC0A; Thu, 23 Aug 2012 22:20:06 +0000 (UTC) Received: from bender.mouf.net (bender.mouf.net [IPv6:2001:470:8:58f:21c:b3ff:feb5:bf32] (may be forged)) (authenticated bits=0) by mouf.net (8.14.5/8.14.5) with ESMTP id q7NMJMuK052114 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Thu, 23 Aug 2012 18:19:23 -0400 (EDT) (envelope-from swills@FreeBSD.org) From: Steve Wills Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Date: Thu, 23 Aug 2012 18:19:57 -0400 Message-Id: <97612B57-1255-4BB3-A6D3-FC74324C6D67@FreeBSD.org> To: current@FreeBSD.org, ports@FreeBSD.org, Baptiste Daroussin Mime-Version: 1.0 (Apple Message framework v1084) X-Mailer: Apple Mail (2.1084) X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (mouf.net [IPv6:2607:fc50:0:4400:216:3eff:fe69:33b3]); Thu, 23 Aug 2012 18:19:24 -0400 (EDT) X-Spam-Status: No, score=1.3 required=4.5 tests=RDNS_NONE autolearn=no version=3.3.2 X-Spam-Level: * X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on mouf.net X-Virus-Scanned: clamav-milter 0.97.5 at mouf.net X-Virus-Status: Clean Cc: Subject: pkgng suggestion: renaming /usr/sbin/pkg to /usr/sbin/pkg-bootstrap X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 23 Aug 2012 22:20:07 -0000 Hi, It seems to me that renaming the pkg binary in /usr/sbin/pkg to = /usr/sbin/pkg-bootstrap would make sense. =46rom a user standpoint, it = is confusing that running the command gets different results the second = time it is run vs. the first time. I can imagine a user saying "I ran = pkg, but it didn't do what they said it would. Now I run it again, and = it does do what it is supposed to." Also, it would enable setting up a = pkg-bootstrap man page separate from the pkg man page, without confusion = about which one you're looking at. So, opinions? There may still be time to fix it for 9.1 if we can decide = quickly. Thanks, Steve From owner-freebsd-current@FreeBSD.ORG Thu Aug 23 22:27:18 2012 Return-Path: Delivered-To: current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 00EE6106564A; Thu, 23 Aug 2012 22:27:18 +0000 (UTC) (envelope-from bapt@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id D8BF48FC14; Thu, 23 Aug 2012 22:27:17 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q7NMRH6t071725; Thu, 23 Aug 2012 22:27:17 GMT (envelope-from bapt@FreeBSD.org) Received: (from bapt@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q7NMRH6u071724; Thu, 23 Aug 2012 22:27:17 GMT (envelope-from bapt@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: bapt set sender to bapt@FreeBSD.org using -f Date: Fri, 24 Aug 2012 00:27:13 +0200 From: Baptiste Daroussin To: Steve Wills Message-ID: <20120823222712.GH18372@ithaqua.etoilebsd.net> References: <97612B57-1255-4BB3-A6D3-FC74324C6D67@FreeBSD.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="AqCDj3hiknadvR6t" Content-Disposition: inline In-Reply-To: <97612B57-1255-4BB3-A6D3-FC74324C6D67@FreeBSD.org> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: ports@FreeBSD.org, current@FreeBSD.org Subject: Re: pkgng suggestion: renaming /usr/sbin/pkg to /usr/sbin/pkg-bootstrap X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 23 Aug 2012 22:27:18 -0000 --AqCDj3hiknadvR6t Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Aug 23, 2012 at 06:19:57PM -0400, Steve Wills wrote: > Hi, >=20 > It seems to me that renaming the pkg binary in /usr/sbin/pkg to /usr/sbin= /pkg-bootstrap would make sense. From a user standpoint, it is confusing th= at running the command gets different results the second time it is run vs.= the first time. I can imagine a user saying "I ran pkg, but it didn't do w= hat they said it would. Now I run it again, and it does do what it is supp= osed to." Also, it would enable setting up a pkg-bootstrap man page separat= e from the pkg man page, without confusion about which one you're looking a= t. >=20 > So, opinions? There may still be time to fix it for 9.1 if we can decide = quickly. >=20 I do personnally have no opinion on this, I have hesitated long between both before choosing /usr/sbin/pkg. I'm interested in other's opinion. regards, Bapt --AqCDj3hiknadvR6t Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEARECAAYFAlA2rkAACgkQ8kTtMUmk6Ex7wACdEqj6Voz/cLCwB0Wz14EgrAVE SjkAmwVKxjbKoMOA/fheXbJGPAYHiAAM =OmCe -----END PGP SIGNATURE----- --AqCDj3hiknadvR6t-- From owner-freebsd-current@FreeBSD.ORG Thu Aug 23 22:29:36 2012 Return-Path: Delivered-To: current@FreeBSD.org Received: from mx2.freebsd.org (mx2.freebsd.org [69.147.83.53]) by hub.freebsd.org (Postfix) with ESMTP id 5D23B106566C; Thu, 23 Aug 2012 22:29:36 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from [127.0.0.1] (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id 86C95163793; Thu, 23 Aug 2012 22:28:28 +0000 (UTC) Message-ID: <5036AE8B.9030807@FreeBSD.org> Date: Thu, 23 Aug 2012 15:28:27 -0700 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:14.0) Gecko/20120713 Thunderbird/14.0 MIME-Version: 1.0 To: Steve Wills References: <97612B57-1255-4BB3-A6D3-FC74324C6D67@FreeBSD.org> In-Reply-To: <97612B57-1255-4BB3-A6D3-FC74324C6D67@FreeBSD.org> X-Enigmail-Version: 1.4.3 OpenPGP: id=1A1ABC84 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: ports@FreeBSD.org, Baptiste Daroussin , current@FreeBSD.org Subject: Re: pkgng suggestion: renaming /usr/sbin/pkg to /usr/sbin/pkg-bootstrap X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 23 Aug 2012 22:29:36 -0000 On 8/23/2012 3:19 PM, Steve Wills wrote: > Hi, > > It seems to me that renaming the pkg binary in /usr/sbin/pkg to /usr/sbin/pkg-bootstrap would make sense. From a user standpoint, it is confusing that running the command gets different results the second time it is run vs. the first time. I can imagine a user saying "I ran pkg, but it didn't do what they said it would. Now I run it again, and it does do what it is supposed to." Also, it would enable setting up a pkg-bootstrap man page separate from the pkg man page, without confusion about which one you're looking at. > > So, opinions? There may still be time to fix it for 9.1 if we can decide quickly. Yes please. Every time in the past that we have talked about moving the pkg_* tools to the ports the corresponding change for the base was to have a pkg_bootstrap tool that was a use once and forget kind of thing. I was quite surprised when sbin/pkg was added, but since people tell me I already comment on too much, I decided to wait and see what others thought. Doug -- I am only one, but I am one. I cannot do everything, but I can do something. And I will not let what I cannot do interfere with what I can do. -- Edward Everett Hale, (1822 - 1909) From owner-freebsd-current@FreeBSD.ORG Thu Aug 23 22:38:09 2012 Return-Path: Delivered-To: current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DA38B1065674 for ; Thu, 23 Aug 2012 22:38:09 +0000 (UTC) (envelope-from bryan@shatow.net) Received: from secure.xzibition.com (secure.xzibition.com [173.160.118.92]) by mx1.freebsd.org (Postfix) with ESMTP id B8D3F8FC14 for ; Thu, 23 Aug 2012 22:38:07 +0000 (UTC) DomainKey-Signature: a=rsa-sha1; c=nofws; d=shatow.net; h=message-id :date:from:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; q=dns; s=sweb; b=zCyAMo 749ip/57nCSjPJISFyYG7r+Li14jFDBKld7fecEVdoJ/6BZulLmO7vs2XR7JlGq0 aQxOVqarNCnnr+b1I421Id8orsHgwl/MvShUMZQF8II8JGJ7g0b7icvgBWvtf8o0 C4RofMtt1DhORLBrKQfRMoSsVboZFXjCawIy0= DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=shatow.net; h=message-id :date:from:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; s=sweb; bh=De6YInNZyQ/r 7zagddHGx8xHPP0nrN3YFME4m2ooHNo=; b=VIc1nFh1L8e0089RUIEN0kGfZl6L g0egUhMK/hcdLNvWm5230hlsSIrRMqrcv0RESMa8eSGf7N0J5Swa4jpw6jwvtY7l qa9vKHs7HtkcfwtsNh1IBvau+VGb8oNXWwYlN1lNsUYDNg0NeigvKrzBYQsCY24+ EzZ967abMxFCEV0= Received: (qmail 68884 invoked from network); 23 Aug 2012 17:38:05 -0500 Received: from unknown (HELO ?192.168.0.74?) (bryan@shatow.net@74.94.87.209) by sweb.xzibition.com with ESMTPA; 23 Aug 2012 17:38:05 -0500 Message-ID: <5036B0E2.1000600@shatow.net> Date: Thu, 23 Aug 2012 17:38:26 -0500 From: Bryan Drewery User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0 MIME-Version: 1.0 To: Steve Wills , Baptiste Daroussin References: <97612B57-1255-4BB3-A6D3-FC74324C6D67@FreeBSD.org> In-Reply-To: <97612B57-1255-4BB3-A6D3-FC74324C6D67@FreeBSD.org> X-Enigmail-Version: 1.4.3 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: ports@FreeBSD.org, current@FreeBSD.org Subject: Re: pkgng suggestion: renaming /usr/sbin/pkg to /usr/sbin/pkg-bootstrap X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 23 Aug 2012 22:38:10 -0000 On 8/23/2012 5:19 PM, Steve Wills wrote: > Hi, > > It seems to me that renaming the pkg binary in /usr/sbin/pkg to /usr/sbin/pkg-bootstrap would make sense. From a user standpoint, it is confusing that running the command gets different results the second time it is run vs. the first time. I can imagine a user saying "I ran pkg, but it didn't do what they said it would. Now I run it again, and it does do what it is supposed to." Also, it would enable setting up a pkg-bootstrap man page separate from the pkg man page, without confusion about which one you're looking at. > > So, opinions? There may still be time to fix it for 9.1 if we can decide quickly. > > Thanks, > Steve > Even automated tools can be prone to that mistake. I think either we need to make the bootstrapper be silent and forward the command to the downloaded version (kind of surprising... what is taking so long??) (and higher risk to rush in right now) or rename as you suggested. But if we rename, when and who runs it? Will we update bsd.port.mk to run it if needed? Bryan From owner-freebsd-current@FreeBSD.ORG Thu Aug 23 22:54:14 2012 Return-Path: Delivered-To: current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3A899106564A; Thu, 23 Aug 2012 22:54:14 +0000 (UTC) (envelope-from patfbsd@davenulle.org) Received: from smtp.lamaiziere.net (net.lamaiziere.net [94.23.254.147]) by mx1.freebsd.org (Postfix) with ESMTP id 7FAB88FC08; Thu, 23 Aug 2012 22:54:13 +0000 (UTC) Received: from baby-jane.lamaiziere.net (unknown [192.168.1.10]) by smtp.lamaiziere.net (Postfix) with ESMTP id 5740FC324; Fri, 24 Aug 2012 00:54:06 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by baby-jane.lamaiziere.net (Postfix) with ESMTP id E74582CEC18; Fri, 24 Aug 2012 00:54:04 +0200 (CEST) Date: Fri, 24 Aug 2012 00:54:03 +0200 From: Patrick Lamaiziere To: Baptiste Daroussin Message-ID: <20120824005403.7f400d78@davenulle.org> In-Reply-To: <20120823222712.GH18372@ithaqua.etoilebsd.net> References: <97612B57-1255-4BB3-A6D3-FC74324C6D67@FreeBSD.org> <20120823222712.GH18372@ithaqua.etoilebsd.net> X-Mailer: Claws Mail 3.8.1 (GTK+ 2.24.6; i386-portbld-freebsd9.0) Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Cc: ports@FreeBSD.org, current@FreeBSD.org Subject: Re: pkgng suggestion: renaming /usr/sbin/pkg to /usr/sbin/pkg-bootstrap X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 23 Aug 2012 22:54:14 -0000 Le Fri, 24 Aug 2012 00:27:13 +0200, Baptiste Daroussin a écrit : Hello, > > So, opinions? There may still be time to fix it for 9.1 if we can > > decide quickly. > > > I do personnally have no opinion on this, I have hesitated long > between both before choosing /usr/sbin/pkg. > > I'm interested in other's opinion. I was hit by this: install poudriere, forgot to install pkgng (yes it is documented...). Run poudriere bulk, it will be stuck waiting an user input (it does not output anything too) and it closes the poudriere jail juste after a key is pressed. I've spent sometime to understand why pkg was waiting on the "tty" wchan... So yes this is confusing IMO. Regards. From owner-freebsd-current@FreeBSD.ORG Thu Aug 23 23:55:53 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1AF04106564A; Thu, 23 Aug 2012 23:55:53 +0000 (UTC) (envelope-from kabaev@gmail.com) Received: from mail-vc0-f182.google.com (mail-vc0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id 7D5D48FC15; Thu, 23 Aug 2012 23:55:52 +0000 (UTC) Received: by vcbgb22 with SMTP id gb22so1907031vcb.13 for ; Thu, 23 Aug 2012 16:55:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:cc:subject:message-id:in-reply-to:references:x-mailer :mime-version:content-type; bh=VwhM/NC/OAzqMIFqsAVuutF2NuepvlwlMWqTfMZvdBs=; b=ksEQQ8D4On0e7NfzUdhRMA5iSfnv/ohZf7onrMWmhOZa9dh+Hp3kTExqANdacnXDdC tcAR4YEim940ZcCqkESEXT75ylPBhdVQSrPfp/bc0EUqo7SFGgQEv3wIg8YyoILc6+Dz U000sk8tOpONwE1ss2MDRBAMPZvjuLnXCvmcDCImikzUgfQ292NKSu7W1hP4w5fh7wLF Tp7VILt+xniGJXcOO+IfAKA7wfYFbxbZSKSEV4gnrIgStftLq+O5Y6eeajxxNWw2OvxP kDCB4vE5GfJzA6jfvRwKMn9SDzONgJlG4ZKAk/1wGCcUFv3FQ4VN2Gs6qtO+6dijpL3T CW4w== Received: by 10.220.248.69 with SMTP id mf5mr2889967vcb.42.1345766151772; Thu, 23 Aug 2012 16:55:51 -0700 (PDT) Received: from kan.dyndns.org (c-24-63-226-98.hsd1.ma.comcast.net. [24.63.226.98]) by mx.google.com with ESMTPS id xk2sm3992975vec.13.2012.08.23.16.55.50 (version=SSLv3 cipher=OTHER); Thu, 23 Aug 2012 16:55:51 -0700 (PDT) Date: Thu, 23 Aug 2012 19:55:40 -0400 From: Alexander Kabaev To: Steve Wills Message-ID: <20120823195540.335baa2d@kan.dyndns.org> In-Reply-To: <97612B57-1255-4BB3-A6D3-FC74324C6D67@FreeBSD.org> References: <97612B57-1255-4BB3-A6D3-FC74324C6D67@FreeBSD.org> X-Mailer: Claws Mail 3.8.0 (GTK+ 2.24.6; amd64-portbld-freebsd10.0) Mime-Version: 1.0 Content-Type: multipart/signed; micalg=PGP-SHA1; boundary="Sig_/U0E1mWJTS0LcnEYiOr09.HE"; protocol="application/pgp-signature" Cc: ports@FreeBSD.org, Baptiste Daroussin , current@FreeBSD.org Subject: Re: pkgng suggestion: renaming /usr/sbin/pkg to /usr/sbin/pkg-bootstrap X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 23 Aug 2012 23:55:53 -0000 --Sig_/U0E1mWJTS0LcnEYiOr09.HE Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Thu, 23 Aug 2012 18:19:57 -0400 Steve Wills wrote: > Hi, >=20 > It seems to me that renaming the pkg binary in /usr/sbin/pkg > to /usr/sbin/pkg-bootstrap would make sense. From a user standpoint, > it is confusing that running the command gets different results the > second time it is run vs. the first time. I can imagine a user saying > "I ran pkg, but it didn't do what they said it would. Now I run it > again, and it does do what it is supposed to." Also, it would enable > setting up a pkg-bootstrap man page separate from the pkg man page, > without confusion about which one you're looking at. >=20 > So, opinions? There may still be time to fix it for 9.1 if we can > decide quickly. >=20 > Thanks, > Steve >=20 Remove it or rename it. Do _NOT_ make it download the package and install it silently as this is a security nightmare waiting to happen. --=20 Alexander Kabaev --Sig_/U0E1mWJTS0LcnEYiOr09.HE Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iD8DBQFQNsMFQ6z1jMm+XZYRAlk7AJ9rL4dKinLHk9gANmDW65K91045JQCg1TmX /m3IXvv7UfWPsRG74jPVXTY= =dHFj -----END PGP SIGNATURE----- --Sig_/U0E1mWJTS0LcnEYiOr09.HE-- From owner-freebsd-current@FreeBSD.ORG Fri Aug 24 01:58:16 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 669B21065675 for ; Fri, 24 Aug 2012 01:58:16 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: from mail-vb0-f54.google.com (mail-vb0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id 0CF898FC15 for ; Fri, 24 Aug 2012 01:58:15 +0000 (UTC) Received: by vbmv11 with SMTP id v11so1980557vbm.13 for ; Thu, 23 Aug 2012 18:58:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eitanadler.com; s=0xdeadbeef; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; bh=ZdJtL4nfFYyKANpGhYi2PN3Gu/3X42FUQ0FDMergqgI=; b=AOimH+HNQGrfWcAcR1Nsntj9J06aMq0+CptwRXYd+r1zIbLoIfFGF0ebpaSGncbIiu oEG/Dsy3GyiQK8PJw7G531EES8wXGnQWc2hFXgDphB4YRdT5qVFpJhwwgt4EMfqs1S1R rKb3JB85O/BqSxL+uI/SO7YX1rCDkJ16mmmFc= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding:x-gm-message-state; bh=ZdJtL4nfFYyKANpGhYi2PN3Gu/3X42FUQ0FDMergqgI=; b=DC4n01DiKilMz/4gY9VH2wN/jUgJyNSGEG6cgQB6lW0P4sCopE1vEKvCZLqIQSPbqN B2A4rMvbqpJNRRvpUOlKG4nQnwnoPkWs/xq0P54j/+YEzjIXDKFb9WdvdNgj202E7vjN YXsdmvb8y1lbGKEhSwzZNvtA/z/6+ljbmm9FbtRoPnd/+jhLLGV0BHFrfDqj2U6L03aJ V0tYL38IEo/UjgODB6WHOjpTFHL0yMhhgI2m1aLqZArrl0acthKTxtTBKb6wCA/d+HpL A7j/f1GQZRt59R1kEYoMmEhxalz5+XPJWjLoH0bM2xEm6MpAdC7WYCMu5jK/WOL9rwmG h1dQ== Received: by 10.220.141.202 with SMTP id n10mr3098803vcu.49.1345773495273; Thu, 23 Aug 2012 18:58:15 -0700 (PDT) MIME-Version: 1.0 Received: by 10.58.190.227 with HTTP; Thu, 23 Aug 2012 18:57:44 -0700 (PDT) In-Reply-To: <97612B57-1255-4BB3-A6D3-FC74324C6D67@FreeBSD.org> References: <97612B57-1255-4BB3-A6D3-FC74324C6D67@FreeBSD.org> From: Eitan Adler Date: Thu, 23 Aug 2012 21:57:44 -0400 Message-ID: To: Steve Wills Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Gm-Message-State: ALoCoQmU3G4GBCSr155+R7ZGZcFyqlANSThdWyy5V035Aba4yQtT/3EwZIe9fpjJG6P9IWpfRrbG Cc: ports@freebsd.org, Baptiste Daroussin , current@freebsd.org Subject: Re: pkgng suggestion: renaming /usr/sbin/pkg to /usr/sbin/pkg-bootstrap X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 24 Aug 2012 01:58:16 -0000 On 23 August 2012 18:19, Steve Wills wrote: > Hi, > > It seems to me that renaming the pkg binary in /usr/sbin/pkg to /usr/sbin= /pkg-bootstrap would make sense. From a user standpoint, it is confusing th= at running the command gets different results the second time it is run vs.= the first time. I can imagine a user saying "I ran pkg, but it didn't do w= hat they said it would. Now I run it again, and it does do what it is supp= osed to." Also, it would enable setting up a pkg-bootstrap man page separat= e from the pkg man page, without confusion about which one you're looking a= t. > > So, opinions? There may still be time to fix it for 9.1 if we can decide = quickly. no opinion on the name, but imho there should be *something* called "pkg" on a fresh system. Users will install a new system, follow some random how-to, and not realize they missed a step. If the default package errors with exit code 1 and says "run pkgbootstrap first" that is okay too. --=20 Eitan Adler From owner-freebsd-current@FreeBSD.ORG Fri Aug 24 02:05:28 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 6A2E9106566B; Fri, 24 Aug 2012 02:05:28 +0000 (UTC) (envelope-from swills@freebsd.org) Received: from mouf.net (mouf.net [IPv6:2607:fc50:0:4400:216:3eff:fe69:33b3]) by mx1.freebsd.org (Postfix) with ESMTP id 071DC8FC08; Fri, 24 Aug 2012 02:05:27 +0000 (UTC) Received: from bender.mouf.net (bender.mouf.net [IPv6:2001:470:8:58f:21c:b3ff:feb5:bf32] (may be forged)) (authenticated bits=0) by mouf.net (8.14.5/8.14.5) with ESMTP id q7O24frV056045 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Thu, 23 Aug 2012 22:04:42 -0400 (EDT) (envelope-from swills@freebsd.org) Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii From: Steve Wills In-Reply-To: Date: Thu, 23 Aug 2012 22:05:18 -0400 Content-Transfer-Encoding: quoted-printable Message-Id: <785B5BAD-E015-4624-B3A1-D05E1BD97E51@freebsd.org> References: <97612B57-1255-4BB3-A6D3-FC74324C6D67@FreeBSD.org> To: Eitan Adler X-Mailer: Apple Mail (2.1084) X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (mouf.net [IPv6:2607:fc50:0:4400:216:3eff:fe69:33b3]); Thu, 23 Aug 2012 22:04:43 -0400 (EDT) X-Spam-Status: No, score=1.3 required=4.5 tests=RDNS_NONE autolearn=no version=3.3.2 X-Spam-Level: * X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on mouf.net X-Virus-Scanned: clamav-milter 0.97.5 at mouf.net X-Virus-Status: Clean Cc: ports@freebsd.org, Baptiste Daroussin , current@freebsd.org Subject: Re: pkgng suggestion: renaming /usr/sbin/pkg to /usr/sbin/pkg-bootstrap X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 24 Aug 2012 02:05:28 -0000 On Aug 23, 2012, at 9:57 PM, Eitan Adler wrote: > On 23 August 2012 18:19, Steve Wills wrote: >> Hi, >>=20 >> It seems to me that renaming the pkg binary in /usr/sbin/pkg to = /usr/sbin/pkg-bootstrap would make sense. =46rom a user standpoint, it = is confusing that running the command gets different results the second = time it is run vs. the first time. I can imagine a user saying "I ran = pkg, but it didn't do what they said it would. Now I run it again, and = it does do what it is supposed to." Also, it would enable setting up a = pkg-bootstrap man page separate from the pkg man page, without confusion = about which one you're looking at. >>=20 >> So, opinions? There may still be time to fix it for 9.1 if we can = decide quickly. >=20 > no opinion on the name, but imho there should be *something* called > "pkg" on a fresh system. Users will install a new system, follow some > random how-to, and not realize they missed a step. If the default > package errors with exit code 1 and says "run pkgbootstrap first" that > is okay too. Why can't one of those steps be to run "pkg-bootstrap"? Steve From owner-freebsd-current@FreeBSD.ORG Fri Aug 24 02:08:53 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4D0611065674 for ; Fri, 24 Aug 2012 02:08:53 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: from mail-vb0-f54.google.com (mail-vb0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id E522F8FC20 for ; Fri, 24 Aug 2012 02:08:52 +0000 (UTC) Received: by vbmv11 with SMTP id v11so1989687vbm.13 for ; Thu, 23 Aug 2012 19:08:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eitanadler.com; s=0xdeadbeef; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=sMyHVDrJRZNqmDzP+UmyC8ziFzWOGdx5nxKNPRJAyl0=; b=YpiyQy3C6LcpOGXy2byijXVeJwcYXcFixoOY+CRhU4XduWKdgg98YTVt+r1E2o8LnS zwLAloNcyVoubqcj5hizfn1Do+LmKoQr/LLefcHXrYJcJCXt6t2uv72mdMAD5Rt2YZrH 0tdp5gU1tOlxQeu7V+oR6t46uSuV0YQg1PMZA= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:x-gm-message-state; bh=sMyHVDrJRZNqmDzP+UmyC8ziFzWOGdx5nxKNPRJAyl0=; b=iu0gl1JF59GtvCHSEZwDtex3yBsYx6g6iBqthAqx+Y6dEhjyr4Fv+rH/EWaUNlbuuV F2khjrpoi7VI68skVHOQlFiWfzAaVE4piR9dxlfKSsiEkZpNFd6MkcBlFOBGrXayjDaG dOJP4CGDqmEXEtQgwlwjZ8yEe6660GiwlYyiCHxpomEUGNtO6mLusIHfvXxD3wTyV+7u Q5v/x0bXUlQnGAgod78rQy4U0qraF/87Un+ty6fETp60rtmcyjB36PSz+RxSfnxnoWsc 7VjVlAiIDaLtWHe3Pk98Y8tvpuyeqoTY1+oO7m6SQMdraRVnn+2ZNaKkEY4YkO1DSIBJ IPSQ== Received: by 10.220.141.208 with SMTP id n16mr3213329vcu.22.1345774132023; Thu, 23 Aug 2012 19:08:52 -0700 (PDT) MIME-Version: 1.0 Received: by 10.58.190.227 with HTTP; Thu, 23 Aug 2012 19:08:21 -0700 (PDT) In-Reply-To: <785B5BAD-E015-4624-B3A1-D05E1BD97E51@freebsd.org> References: <97612B57-1255-4BB3-A6D3-FC74324C6D67@FreeBSD.org> <785B5BAD-E015-4624-B3A1-D05E1BD97E51@freebsd.org> From: Eitan Adler Date: Thu, 23 Aug 2012 22:08:21 -0400 Message-ID: To: Steve Wills Content-Type: text/plain; charset=UTF-8 X-Gm-Message-State: ALoCoQn9/rSbn59i+nW9AP9PnsAeMYkU80SWnKSnc71D0dv/6fPgAih4UANZS4gbUfqTgHYSZCRu Cc: ports@freebsd.org, Baptiste Daroussin , current@freebsd.org Subject: Re: pkgng suggestion: renaming /usr/sbin/pkg to /usr/sbin/pkg-bootstrap X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 24 Aug 2012 02:08:53 -0000 On 23 August 2012 22:05, Steve Wills wrote: > Why can't one of those steps be to run "pkg-bootstrap"? Because the how-to may not be for a new system ;) -- Eitan Adler From owner-freebsd-current@FreeBSD.ORG Fri Aug 24 02:15:13 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B275A1065674; Fri, 24 Aug 2012 02:15:13 +0000 (UTC) (envelope-from swills@freebsd.org) Received: from mouf.net (mouf.net [IPv6:2607:fc50:0:4400:216:3eff:fe69:33b3]) by mx1.freebsd.org (Postfix) with ESMTP id 676B68FC0C; Fri, 24 Aug 2012 02:15:13 +0000 (UTC) Received: from bender.mouf.net (bender.mouf.net [IPv6:2001:470:8:58f:21c:b3ff:feb5:bf32] (may be forged)) (authenticated bits=0) by mouf.net (8.14.5/8.14.5) with ESMTP id q7O2EPo1056321 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Thu, 23 Aug 2012 22:14:27 -0400 (EDT) (envelope-from swills@freebsd.org) Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii From: Steve Wills In-Reply-To: Date: Thu, 23 Aug 2012 22:15:02 -0400 Content-Transfer-Encoding: quoted-printable Message-Id: <5AC662AA-4874-4BC2-9862-65518B79B840@freebsd.org> References: <97612B57-1255-4BB3-A6D3-FC74324C6D67@FreeBSD.org> <785B5BAD-E015-4624-B3A1-D05E1BD97E51@freebsd.org> To: Eitan Adler X-Mailer: Apple Mail (2.1084) X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (mouf.net [IPv6:2607:fc50:0:4400:216:3eff:fe69:33b3]); Thu, 23 Aug 2012 22:14:27 -0400 (EDT) X-Spam-Status: No, score=1.3 required=4.5 tests=RDNS_NONE autolearn=no version=3.3.2 X-Spam-Level: * X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on mouf.net X-Virus-Scanned: clamav-milter 0.97.5 at mouf.net X-Virus-Status: Clean Cc: ports@freebsd.org, Baptiste Daroussin , current@freebsd.org Subject: Re: pkgng suggestion: renaming /usr/sbin/pkg to /usr/sbin/pkg-bootstrap X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 24 Aug 2012 02:15:13 -0000 On Aug 23, 2012, at 10:08 PM, Eitan Adler wrote: > On 23 August 2012 22:05, Steve Wills wrote: >=20 >> Why can't one of those steps be to run "pkg-bootstrap"? >=20 > Because the how-to may not be for a new system ;) The possibility of bad docs somewhere outside of our control, when we = can (and I am actively working on) document(ing) pkgng for the handbook = seems kinda thin. It's not even "Something's wrong on the Internet!" = (http://xkcd.com/386/), it's "Something might some day be wrong on the = Internet!" Steve From owner-freebsd-current@FreeBSD.ORG Fri Aug 24 02:24:16 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8F7CB1065674 for ; Fri, 24 Aug 2012 02:24:16 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: from mail-vb0-f54.google.com (mail-vb0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id 310418FC12 for ; Fri, 24 Aug 2012 02:24:15 +0000 (UTC) Received: by vbmv11 with SMTP id v11so2002012vbm.13 for ; Thu, 23 Aug 2012 19:24:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eitanadler.com; s=0xdeadbeef; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; bh=TeuksIM5bxvGVq4k95fCjO9Po5hxmKdu0a0VOAqQ5Qk=; b=YZfeC1LD927s/j6z4iII/niOeSbxXZPnvqNRdOhCxLC6Ca/dPedt0W3k3noJnd+j/8 Piu2AJa6IGH4KhHgm5a9tG1mqjy+pUaASBqDkpAkAEA3pU5c8uVq7FZp13Aj3OepcVhC 5i18o1MDqH9xc42DXomoBgBYwmkhPlos6DF/0= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding:x-gm-message-state; bh=TeuksIM5bxvGVq4k95fCjO9Po5hxmKdu0a0VOAqQ5Qk=; b=irNYHbpZEpisNjprDFwM944HvvYLIu8jpkoTBLzDfg38k+FsyiFzATfPKt4+Jgw55M 06Gp60wJBeRLrJxw1HtPcpw/eLCYePUTSjJwWj8YXrZpyqZy853WSKkIUTEyw2a4f8eZ 5VP1t23gVrZ7fMwbKNO3XropRJ5nFEiamSUzCnUyycx/fZa5/udMB1+gKmBAJuNQxj0M KXU/P/DHj5Z7A5sBv3jLHWjSY4KFqwe4mx8MMHEAjg/HTbpQNsTQdaSw08xEVsfvw+r2 omfyqXO7YFM6UiZtNFTKmO58dVhSHhr+Tb3DKw8hYIjzZVJQaX7pfSnfY4VLffg0xpxY UpRQ== Received: by 10.58.133.48 with SMTP id oz16mr3623636veb.1.1345775055345; Thu, 23 Aug 2012 19:24:15 -0700 (PDT) MIME-Version: 1.0 Received: by 10.58.190.227 with HTTP; Thu, 23 Aug 2012 19:23:44 -0700 (PDT) In-Reply-To: <5AC662AA-4874-4BC2-9862-65518B79B840@freebsd.org> References: <97612B57-1255-4BB3-A6D3-FC74324C6D67@FreeBSD.org> <785B5BAD-E015-4624-B3A1-D05E1BD97E51@freebsd.org> <5AC662AA-4874-4BC2-9862-65518B79B840@freebsd.org> From: Eitan Adler Date: Thu, 23 Aug 2012 22:23:44 -0400 Message-ID: To: Steve Wills Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Gm-Message-State: ALoCoQngJRc0+Efv8ijeG9awJLrZdlUhjwubH6JhM08FQWK0eTbCe2Hkc9lVglbAFoTZYrpGlYkR Cc: ports@freebsd.org, Baptiste Daroussin , current@freebsd.org Subject: Re: pkgng suggestion: renaming /usr/sbin/pkg to /usr/sbin/pkg-bootstrap X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 24 Aug 2012 02:24:16 -0000 On 23 August 2012 22:15, Steve Wills wrote: > On Aug 23, 2012, at 10:08 PM, Eitan Adler wrote: > >> On 23 August 2012 22:05, Steve Wills wrote: >> >>> Why can't one of those steps be to run "pkg-bootstrap"? >> >> Because the how-to may not be for a new system ;) > > The possibility of bad docs somewhere outside of our control, when we can= (and I am actively working on) document(ing) pkgng for the handbook seems = kinda thin. It's not even "Something's wrong on the Internet!" (http://xkcd= .com/386/), it's "Something might some day be wrong on the Internet!" It isn't a problem of bad docs. Its a problem of the user following some not-for-new-systems documentation and getting very confused when they see "command not found.". It is practically the definition of POLA. --=20 Eitan Adler From owner-freebsd-current@FreeBSD.ORG Fri Aug 24 02:55:29 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2DDF7106566C; Fri, 24 Aug 2012 02:55:29 +0000 (UTC) (envelope-from swills@freebsd.org) Received: from mouf.net (mouf.net [IPv6:2607:fc50:0:4400:216:3eff:fe69:33b3]) by mx1.freebsd.org (Postfix) with ESMTP id 57F7E8FC16; Fri, 24 Aug 2012 02:55:28 +0000 (UTC) Received: from bender.mouf.net (bender.mouf.net [IPv6:2001:470:8:58f:21c:b3ff:feb5:bf32] (may be forged)) (authenticated bits=0) by mouf.net (8.14.5/8.14.5) with ESMTP id q7O2sfhr056976 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Thu, 23 Aug 2012 22:54:42 -0400 (EDT) (envelope-from swills@freebsd.org) Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii From: Steve Wills In-Reply-To: Date: Thu, 23 Aug 2012 22:55:18 -0400 Content-Transfer-Encoding: quoted-printable Message-Id: References: <97612B57-1255-4BB3-A6D3-FC74324C6D67@FreeBSD.org> <785B5BAD-E015-4624-B3A1-D05E1BD97E51@freebsd.org> <5AC662AA-4874-4BC2-9862-65518B79B840@freebsd.org> To: Eitan Adler X-Mailer: Apple Mail (2.1084) X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (mouf.net [IPv6:2607:fc50:0:4400:216:3eff:fe69:33b3]); Thu, 23 Aug 2012 22:54:43 -0400 (EDT) X-Spam-Status: No, score=1.3 required=4.5 tests=RDNS_NONE autolearn=no version=3.3.2 X-Spam-Level: * X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on mouf.net X-Virus-Scanned: clamav-milter 0.97.5 at mouf.net X-Virus-Status: Clean Cc: ports@freebsd.org, Baptiste Daroussin , current@freebsd.org Subject: Re: pkgng suggestion: renaming /usr/sbin/pkg to /usr/sbin/pkg-bootstrap X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 24 Aug 2012 02:55:29 -0000 On Aug 23, 2012, at 10:23 PM, Eitan Adler wrote: > On 23 August 2012 22:15, Steve Wills wrote: >> On Aug 23, 2012, at 10:08 PM, Eitan Adler wrote: >>=20 >>> On 23 August 2012 22:05, Steve Wills wrote: >>>=20 >>>> Why can't one of those steps be to run "pkg-bootstrap"? >>>=20 >>> Because the how-to may not be for a new system ;) >>=20 >> The possibility of bad docs somewhere outside of our control, when we = can (and I am actively working on) document(ing) pkgng for the handbook = seems kinda thin. It's not even "Something's wrong on the Internet!" = (http://xkcd.com/386/), it's "Something might some day be wrong on the = Internet!" >=20 > It isn't a problem of bad docs. Its a problem of the user following > some not-for-new-systems documentation and getting very confused when > they see "command not found.". It is practically the definition of > POLA. As far as I understand it, POLA is about changing existing things: http://www.freebsd.org/doc/handbook/freebsd-glossary.html#POLA-GLOSSARY So this isn't POLA, it's documentation. Steve From owner-freebsd-current@FreeBSD.ORG Fri Aug 24 03:00:01 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx2.freebsd.org (mx2.freebsd.org [69.147.83.53]) by hub.freebsd.org (Postfix) with ESMTP id 6247A1065670; Fri, 24 Aug 2012 03:00:01 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from [127.0.0.1] (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id 0788E14ED84; Fri, 24 Aug 2012 03:00:00 +0000 (UTC) Message-ID: <5036EE2E.4040606@FreeBSD.org> Date: Thu, 23 Aug 2012 19:59:58 -0700 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:14.0) Gecko/20120713 Thunderbird/14.0 MIME-Version: 1.0 To: Eitan Adler References: <97612B57-1255-4BB3-A6D3-FC74324C6D67@FreeBSD.org> <785B5BAD-E015-4624-B3A1-D05E1BD97E51@freebsd.org> <5AC662AA-4874-4BC2-9862-65518B79B840@freebsd.org> In-Reply-To: X-Enigmail-Version: 1.4.3 OpenPGP: id=1A1ABC84 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: ports@freebsd.org, Steve Wills , Baptiste Daroussin , current@freebsd.org Subject: Re: pkgng suggestion: renaming /usr/sbin/pkg to /usr/sbin/pkg-bootstrap X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 24 Aug 2012 03:00:01 -0000 On 8/23/2012 7:23 PM, Eitan Adler wrote: > On 23 August 2012 22:15, Steve Wills wrote: >> On Aug 23, 2012, at 10:08 PM, Eitan Adler wrote: >> >>> On 23 August 2012 22:05, Steve Wills wrote: >>> >>>> Why can't one of those steps be to run "pkg-bootstrap"? >>> >>> Because the how-to may not be for a new system ;) >> >> The possibility of bad docs somewhere outside of our control, when we can (and I am actively working on) document(ing) pkgng for the handbook seems kinda thin. It's not even "Something's wrong on the Internet!" (http://xkcd.com/386/), it's "Something might some day be wrong on the Internet!" > > It isn't a problem of bad docs. Its a problem of the user following > some not-for-new-systems documentation and getting very confused when > they see "command not found.". It is practically the definition of > POLA. No, POLA refers to not changing long-established practices out from under the user. I tend to agree with Steve here ... we can't be responsible for other people's poorly written docs. You bring up a valid point that we should keep in mind for our own however. The bootstrapping issue will be the smallest possible annoyance on a long road of the migration process. OTOH this is a good use case for the "prompt the user when they type a command for something that can be installed from ports" idea. :) Doug -- I am only one, but I am one. I cannot do everything, but I can do something. And I will not let what I cannot do interfere with what I can do. -- Edward Everett Hale, (1822 - 1909) From owner-freebsd-current@FreeBSD.ORG Fri Aug 24 03:00:57 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 04E551065808 for ; Fri, 24 Aug 2012 03:00:57 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: from mail-vb0-f54.google.com (mail-vb0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id 9B0538FC16 for ; Fri, 24 Aug 2012 03:00:56 +0000 (UTC) Received: by vbmv11 with SMTP id v11so2029387vbm.13 for ; Thu, 23 Aug 2012 20:00:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eitanadler.com; s=0xdeadbeef; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=43pgw1wmU27RrRDLPB9fvQjPy04QreftlkkQXilV8Gg=; b=j1o8P7DVVS99wqWWoXn5qVdIv3ZdaPkaTRGd7m0Nicxt2U2DKMSlG3SpGRUKg4O3rn +5lNjOftG1/M76HIWeIaWjzoKAEZ7YV9IzcNlCwUQCk/yxgDKHGDqJc7Ba2rygl54Dx0 epKoYwvc2UG2oBUWiDlr5m/bfWGGbVUbFwHvc= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:x-gm-message-state; bh=43pgw1wmU27RrRDLPB9fvQjPy04QreftlkkQXilV8Gg=; b=mQOaiesvzxHQnWyFFzhQMMtMBjfWB6Qilgc/39CBq4Fwv1mucY4CBe3jgw//cPtZbQ hVBHd59graJJXv+ByouPAoAH9InUhmXxnlqiRPo9BUjYDNbT9WgynAUDyUyzNehm71Kw LkEyZ+MAPHdp0PtSzK05sWTpjNRUnsukRJoX2cOo4KOCU/Lh7nuNHCGu20BaJMhgBJdP MOtFLtfw2OImdcdeKsqqKLxhDRkmYntmSVrMUqQCSZRBv+Z1nxjiRVTv1sVcxsb1zEx2 K0H6ohKWkzDoO0ElKj8FtiXWkwSVGoBejJUJsG+JmDiXfgVYJgeYJSKFZzEaxiTqXkZH +odA== Received: by 10.52.33.69 with SMTP id p5mr2810352vdi.46.1345777256083; Thu, 23 Aug 2012 20:00:56 -0700 (PDT) MIME-Version: 1.0 Received: by 10.58.190.227 with HTTP; Thu, 23 Aug 2012 20:00:25 -0700 (PDT) In-Reply-To: References: <97612B57-1255-4BB3-A6D3-FC74324C6D67@FreeBSD.org> <785B5BAD-E015-4624-B3A1-D05E1BD97E51@freebsd.org> <5AC662AA-4874-4BC2-9862-65518B79B840@freebsd.org> From: Eitan Adler Date: Thu, 23 Aug 2012 23:00:25 -0400 Message-ID: To: Steve Wills Content-Type: text/plain; charset=UTF-8 X-Gm-Message-State: ALoCoQkbdnUDolhtTBFeJ7jyLo3KW/2oxh9HHMXczVaHUuAFU5PAmtaNRtxer7QmCPA2Yc1rD66j Cc: ports@freebsd.org, Baptiste Daroussin , current@freebsd.org Subject: Re: pkgng suggestion: renaming /usr/sbin/pkg to /usr/sbin/pkg-bootstrap X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 24 Aug 2012 03:00:57 -0000 On 23 August 2012 22:55, Steve Wills wrote: > As far as I understand it, POLA is about changing existing things: okay, so forget POLA. My point is that a user following a how to or even *our* documentation on how to install something unrelated, like say, apache, will be very confused when the documentation tells them to run "pkg install apache" and finds out that pkg doesn't exist. A similar example is needing "rehash" in tcsh. -- Eitan Adler From owner-freebsd-current@FreeBSD.ORG Fri Aug 24 03:04:11 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id ED0151065670 for ; Fri, 24 Aug 2012 03:04:11 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: from mail-vc0-f182.google.com (mail-vc0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id 9209B8FC1C for ; Fri, 24 Aug 2012 03:04:11 +0000 (UTC) Received: by vcbgb22 with SMTP id gb22so2060564vcb.13 for ; Thu, 23 Aug 2012 20:04:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eitanadler.com; s=0xdeadbeef; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=fLoYKDYGfzeMdpoIUOx3zhyLJ0B+eYfjtq1vYfSG6jw=; b=UMGTdoIGai+qb4cuwn00J0J83QNpk2Gs6Ll+ERW1GHt7iJHaW8zzMgGhe/fXSNklXE CqB6+uvsSG5uSt6nBFscbFgM3AQjCf2ReoAQ5nqDBtTFFovDF48d2waGUnrRRfATMjJs A07pZLW+cED+Nl715700l9s1q91oM/4VvDmFE= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:x-gm-message-state; bh=fLoYKDYGfzeMdpoIUOx3zhyLJ0B+eYfjtq1vYfSG6jw=; b=MCX8fKrWOIBbId/hFG9JK6GIjengF9LajkVNpSQQnsdKyqwPfoy72eMEE8gUfQ3QzY jTKuw28HswrA+p5dY7auy7ZYXh1XD/56lh2oLunaAWpdRcBEEN+35Ut0OQdiGKrXghpo DHlG6mupSRnOPd2GrprujziWEcAZe5JrFLmBdVZIeRJzJjbBzpD/JljSEtjiSUCfikWH aM4yCtqmfgPVNcXOiD0pAbgA8FLoCNyUswxeChLPCZbtkiivLzQfp2F5zGrC00k+b0mf lke0TK2Tg2FiAysOnAEilJ3Iwt2Mc1Hglqb3vKLptYJ7ACajGkpNQFqWQ8p391zFKQwY tR5A== Received: by 10.52.20.138 with SMTP id n10mr2772380vde.129.1345777451030; Thu, 23 Aug 2012 20:04:11 -0700 (PDT) MIME-Version: 1.0 Received: by 10.58.190.227 with HTTP; Thu, 23 Aug 2012 20:03:40 -0700 (PDT) In-Reply-To: <5036EE2E.4040606@FreeBSD.org> References: <97612B57-1255-4BB3-A6D3-FC74324C6D67@FreeBSD.org> <785B5BAD-E015-4624-B3A1-D05E1BD97E51@freebsd.org> <5AC662AA-4874-4BC2-9862-65518B79B840@freebsd.org> <5036EE2E.4040606@FreeBSD.org> From: Eitan Adler Date: Thu, 23 Aug 2012 23:03:40 -0400 Message-ID: To: Doug Barton Content-Type: text/plain; charset=UTF-8 X-Gm-Message-State: ALoCoQm3Css5XzWYFpdTwYXG0gAq17vENYBHijI/uPajaa3MfPfUbIiKcD1yM4cIqEEv5TlWZcqw Cc: ports@freebsd.org, Steve Wills , Baptiste Daroussin , current@freebsd.org Subject: Re: pkgng suggestion: renaming /usr/sbin/pkg to /usr/sbin/pkg-bootstrap X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 24 Aug 2012 03:04:12 -0000 On 23 August 2012 22:59, Doug Barton wrote: > No, POLA refers to not changing long-established practices out from > under the user. forget pola > > I tend to agree with Steve here ... we can't be responsible for other > people's poorly written docs. This isn't about poorly written docs. This is the user expecting a tool to exist, which doesn't. Take another example of a sysadmin which rarely installs new systems, installs FreeBSD for the third time, and then gets confused when "pkg install vim" fails. > You bring up a valid point that we should > keep in mind for our own however. The bootstrapping issue will be the > smallest possible annoyance on a long road of the migration process. The bootstrapping issue is a factor even after the migration :) > OTOH this is a good use case for the "prompt the user when they type a > command for something that can be installed from ports" idea. :) even this is fine, provided that *for the command called pkg* it is on by default. note that I'm not talking about the mechanism here, I'm trying to avoid "pkg doesn't seem to be installed on my fresh system" becoming a FAQ. -- Eitan Adler From owner-freebsd-current@FreeBSD.ORG Fri Aug 24 03:56:39 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B3522106567F for ; Fri, 24 Aug 2012 03:56:39 +0000 (UTC) (envelope-from fluffy@fluffy.khv.ru) Received: from forward11.mail.yandex.net (forward11.mail.yandex.net [IPv6:2a02:6b8:0:801::1]) by mx1.freebsd.org (Postfix) with ESMTP id 356738FC17 for ; Fri, 24 Aug 2012 03:56:39 +0000 (UTC) Received: from smtp12.mail.yandex.net (smtp12.mail.yandex.net [95.108.131.191]) by forward11.mail.yandex.net (Yandex) with ESMTP id E7D1BE8277E for ; Fri, 24 Aug 2012 07:56:37 +0400 (MSK) Received: from smtp12.mail.yandex.net (localhost [127.0.0.1]) by smtp12.mail.yandex.net (Yandex) with ESMTP id D49A916A021C for ; Fri, 24 Aug 2012 07:56:37 +0400 (MSK) Received: from client22-22.khabnet.ru (client22-22.khabnet.ru [109.197.22.22]) by smtp12.mail.yandex.net (nwsmtp/Yandex) with ESMTP id uZ5G2QnU-ub5eJ1gM; Fri, 24 Aug 2012 07:56:37 +0400 Message-ID: <5036FB4E.4080407@fluffy.khv.ru> Date: Fri, 24 Aug 2012 14:55:58 +1100 From: Dima Panov User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0 MIME-Version: 1.0 To: current@freebsd.org Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: build error at rpc code X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: fluffy@FreeBSD.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Aug 2012 03:56:39 -0000 Hello! Does anybody get same error at buildworld with recent -current? clang -Os -fno-strict-aliasing -pipe -Qunused-arguments -march=core2 -I/usr/src/lib/libc/include -I /usr/src/lib/libc/../../include -I/usr/src/lib/libc/amd64 -DNLS -D__DBINTERFACE_PRIVATE -I/usr/src/ lib/libc/../../contrib/gdtoa -DINET6 -I/usr/obj/usr/src/lib/libc -I/usr/src/lib/libc/resolv -D_ACL_P RIVATE -DPOSIX_MISTAKE -I/usr/src/lib/libc/../../contrib/jemalloc/include -DMALLOC_PRODUCTION -I/usr /src/lib/libc/../../contrib/tzcode/stdtime -I/usr/src/lib/libc/stdtime -I/usr/src/lib/libc/locale -D BROKEN_DES -DPORTMAP -DDES_BUILTIN -I/usr/src/lib/libc/rpc -DYP -DNS_CACHING -DSYMBOL_VERSIONING -st d=gnu99 -Qunused-arguments -fstack-protector -Wsystem-headers -Werror -Wall -Wno-format-y2k -Wno-uni nitialized -Wno-pointer-sign -Wno-empty-body -Wno-string-plus-int -Wno-tautological-compare -Wno-unu sed-value -Wno-parentheses-equality -Wno-unused-function -Wno-conversion -Wno-switch -Wno-switch-enu m -c /usr/src/lib/libc/gen/getgrent.c -o getgrent.o In file included from /usr/src/lib/libc/gen/getgrent.c:39: In file included from /usr/src/lib/libc/../../include/rpc/rpc.h:76: /usr/src/lib/libc/../../include/rpc/rpcb_clnt.h:69:8: error: unknown type name 'rpcblist' extern rpcblist *rpcb_getmaps(const struct netconfig *, const char *); 1 error generated. *** [getgrent.o] Error code 1 Stop in /usr/src/lib/libc. *** [lib/libc__L] Error code 1 10.0-1000015-CURRENT /usr/bin/clang #0 r238449M: Sat Jul 14 23:34:39 VLAT 2012 CLANG_IS_CC Full buildlog at http://fluffy.homeunix.net/~fluffy/files/screenlog.0 -- Dima Panov (fluffy@FreeBSD.org) (KDE, Office)@FreeBSD team Facebook: http://www.facebook.com/fluffy.khv IRC: fluffy@EFNet, fluffykhv@FreeNode twitter: fluffy_khv | skype: dima.panov From owner-freebsd-current@FreeBSD.ORG Fri Aug 24 04:22:14 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 8882D106564A; Fri, 24 Aug 2012 04:22:14 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) by mx1.freebsd.org (Postfix) with ESMTP id 019D18FC0A; Fri, 24 Aug 2012 04:22:13 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.5/8.14.5) with ESMTP id q7O4MBgh035123; Thu, 23 Aug 2012 22:22:11 -0600 (MDT) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.5/8.14.5/Submit) with ESMTP id q7O4MB10035120; Thu, 23 Aug 2012 22:22:11 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Thu, 23 Aug 2012 22:22:11 -0600 (MDT) From: Warren Block To: Eitan Adler In-Reply-To: Message-ID: References: <97612B57-1255-4BB3-A6D3-FC74324C6D67@FreeBSD.org> <785B5BAD-E015-4624-B3A1-D05E1BD97E51@freebsd.org> <5AC662AA-4874-4BC2-9862-65518B79B840@freebsd.org> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (wonkity.com [127.0.0.1]); Thu, 23 Aug 2012 22:22:11 -0600 (MDT) Cc: ports@freebsd.org, Steve Wills , Baptiste Daroussin , current@freebsd.org Subject: Re: pkgng suggestion: renaming /usr/sbin/pkg to /usr/sbin/pkg-bootstrap X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 24 Aug 2012 04:22:14 -0000 On Thu, 23 Aug 2012, Eitan Adler wrote: > On 23 August 2012 22:55, Steve Wills wrote: > >> As far as I understand it, POLA is about changing existing things: > > okay, so forget POLA. My point is that a user following a how to or > even *our* documentation on how to install something unrelated, like > say, apache, will be very confused when the documentation tells them > to run "pkg install apache" and finds out that pkg doesn't exist. A > similar example is needing "rehash" in tcsh. I need to apologize to Steve Wills. I brought this up on IRC, and then shirked posting it here. My concern was having two programs called "pkg" with decidedly different behavior. Or rather, what appears to the user to be a single program that does not behave predictably. I should also apologize for not looking at this earlier; I was planning on using pkgng after release, and only just now got involved due to documentation. Alexander Kabaev's point about security is interesting. Maybe a compromise would be for /usr/sbin/pkg to remain, but merely show instructions on how to install the pkg package. From owner-freebsd-current@FreeBSD.ORG Fri Aug 24 05:43:37 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 08A4F106566B; Fri, 24 Aug 2012 05:43:37 +0000 (UTC) (envelope-from alc@rice.edu) Received: from mh11.mail.rice.edu (mh11.mail.rice.edu [128.42.199.30]) by mx1.freebsd.org (Postfix) with ESMTP id CCA8B8FC1C; Fri, 24 Aug 2012 05:43:36 +0000 (UTC) Received: from mh11.mail.rice.edu (localhost.localdomain [127.0.0.1]) by mh11.mail.rice.edu (Postfix) with ESMTP id 5E3074C031D; Fri, 24 Aug 2012 00:43:34 -0500 (CDT) Received: from mh11.mail.rice.edu (localhost.localdomain [127.0.0.1]) by mh11.mail.rice.edu (Postfix) with ESMTP id 5CA5F4C0282; Fri, 24 Aug 2012 00:43:34 -0500 (CDT) X-Virus-Scanned: by amavis-2.7.0 at mh11.mail.rice.edu, auth channel Received: from mh11.mail.rice.edu ([127.0.0.1]) by mh11.mail.rice.edu (mh11.mail.rice.edu [127.0.0.1]) (amavis, port 10026) with ESMTP id vGZYHsW8hMxc; Fri, 24 Aug 2012 00:43:34 -0500 (CDT) Received: from adsl-216-63-78-18.dsl.hstntx.swbell.net (adsl-216-63-78-18.dsl.hstntx.swbell.net [216.63.78.18]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) (Authenticated sender: alc) by mh11.mail.rice.edu (Postfix) with ESMTPSA id F1AF44C0216; Fri, 24 Aug 2012 00:43:33 -0500 (CDT) Message-ID: <50371485.1020409@rice.edu> Date: Fri, 24 Aug 2012 00:43:33 -0500 From: Alan Cox User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:8.0) Gecko/20111113 Thunderbird/8.0 MIME-Version: 1.0 To: Luigi Rizzo References: <20120822120105.GA63763@onelab2.iet.unipi.it> <20120823163145.GA3999@onelab2.iet.unipi.it> <50366398.2070700@rice.edu> <20120823174504.GB4820@onelab2.iet.unipi.it> In-Reply-To: <20120823174504.GB4820@onelab2.iet.unipi.it> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: alc@freebsd.org, current@freebsd.org Subject: Re: less aggressive contigmalloc ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 24 Aug 2012 05:43:37 -0000 On 08/23/2012 12:45, Luigi Rizzo wrote: > On Thu, Aug 23, 2012 at 12:08:40PM -0500, Alan Cox wrote: > ... >>> yes i do see that. >>> >>> Maybe less aggressive with M_NOWAIT but still kills processes. >> Are you compiling world with MALLOC_PRODUCTION? The latest version of > whatever the default is. But: > >> jemalloc uses significantly more memory when debugging options are >> enabled. This first came up in a thread titled "10-CURRENT and swap >> usage" back in June. >> >> Even at its most aggressive, M_WAITOK, contigmalloc() does not directly >> kill processes. If process death coincides with the use of >> contigmalloc(), then it is simply the result of earlier, successful >> contigmalloc() calls, or for that matter any other physical memory >> allocation calls, having depleted the pool of free pages to the point >> that the page daemon runs and invokes vm_pageout_oom(). > does it mean that those previous allocations relied on memory overbooking ? Yes. > Is there a way to avoid that, then ? I believe that malloc()'s default minimum allocation size is 4MB. You could reduce that. Alternatively, you can enable MALLOC_PRODUCTION. From owner-freebsd-current@FreeBSD.ORG Fri Aug 24 07:21:57 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B5EB810656A3; Fri, 24 Aug 2012 07:21:56 +0000 (UTC) (envelope-from jlaffaye.freebsd@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 B52268FC24; Fri, 24 Aug 2012 07:21:55 +0000 (UTC) Received: by eeke52 with SMTP id e52so611905eek.13 for ; Fri, 24 Aug 2012 00:21:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=fvSs1IAcJwqLv4AVOP87LRv5VAzbVoDZOb74bjRqqH4=; b=lJsj1OwCbRrJwmyghz4dbcV0h+biEE/XCjHH44CzRJx0pDSoAGh1XzzzXJaybfav1E zd6XfczbUPhWoUMHVJXIncnkw/9XJKqEx285sK52VhgSCwn1pj10KlOCUP2+3QUSU0Es mNvtR16C0Rhl+5OKWG32z0W3STNvGC14ArLLyDOrErLHY3/DUx0RdQa+87hjeg6MGRXK T3G02nJh1vvSC/6YxiW+Hq7snhbW9PmAVFMeXDRJFinh8I7EcBvRrQZq8W0RDtDBT2E0 n31ponpWq5EsaYoT3bc/MUQ229xKL/Xu4P12YzbC4Du2rZdxFqabPql2hXbWi5PKSPuS 5CAA== Received: by 10.14.172.129 with SMTP id t1mr6078105eel.34.1345792908657; Fri, 24 Aug 2012 00:21:48 -0700 (PDT) Received: from ?IPv6:2001:41d0:fc00:100:44f:9421:bae7:af9? ([2001:41d0:fc00:100:44f:9421:bae7:af9]) by mx.google.com with ESMTPS id y1sm27416800eel.0.2012.08.24.00.21.46 (version=SSLv3 cipher=OTHER); Fri, 24 Aug 2012 00:21:47 -0700 (PDT) Sender: Julien Laffaye Message-ID: <50372B8B.6040609@freebsd.org> Date: Fri, 24 Aug 2012 09:21:47 +0200 From: Julien Laffaye User-Agent: Thunderbird/7.0.1 MIME-Version: 1.0 To: Eitan Adler References: <97612B57-1255-4BB3-A6D3-FC74324C6D67@FreeBSD.org> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: ports@freebsd.org, Steve Wills , Baptiste Daroussin , current@freebsd.org Subject: Re: pkgng suggestion: renaming /usr/sbin/pkg to /usr/sbin/pkg-bootstrap X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 24 Aug 2012 07:21:57 -0000 On 8/24/2012 3:57 AM, Eitan Adler wrote: > On 23 August 2012 18:19, Steve Wills wrote: >> Hi, >> >> It seems to me that renaming the pkg binary in /usr/sbin/pkg to /usr/sbin/pkg-bootstrap would make sense. From a user standpoint, it is confusing that running the command gets different results the second time it is run vs. the first time. I can imagine a user saying "I ran pkg, but it didn't do what they said it would. Now I run it again, and it does do what it is supposed to." Also, it would enable setting up a pkg-bootstrap man page separate from the pkg man page, without confusion about which one you're looking at. >> >> So, opinions? There may still be time to fix it for 9.1 if we can decide quickly. > no opinion on the name, but imho there should be *something* called > "pkg" on a fresh system. Users will install a new system, follow some > random how-to, and not realize they missed a step. If the default > package errors with exit code 1 and says "run pkgbootstrap first" that > is okay too. > > Ideally, pkgng bootstrap process will be part of the bsdinstall steps (using the pkg package tarball on the installation media). The bootstrap tool is in base (instead of only on the install media) essentially for installations without the installer (like creating jails). So its true that in these case you have to think to run the bootstrap command. From owner-freebsd-current@FreeBSD.ORG Fri Aug 24 08:12:16 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 59F62106564A; Fri, 24 Aug 2012 08:12:16 +0000 (UTC) (envelope-from dimitry@andric.com) Received: from tensor.andric.com (cl-327.ede-01.nl.sixxs.net [IPv6:2001:7b8:2ff:146::2]) by mx1.freebsd.org (Postfix) with ESMTP id 17AF38FC08; Fri, 24 Aug 2012 08:12:16 +0000 (UTC) Received: from [IPv6:2001:7b8:3a7:0:e813:6fd8:bb8a:248b] (unknown [IPv6:2001:7b8:3a7:0:e813:6fd8:bb8a:248b]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by tensor.andric.com (Postfix) with ESMTPSA id A03185C59; Fri, 24 Aug 2012 10:12:14 +0200 (CEST) Message-ID: <50373763.50608@andric.com> Date: Fri, 24 Aug 2012 10:12:19 +0200 From: Dimitry Andric User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20120815 Thunderbird/15.0 MIME-Version: 1.0 To: fluffy@FreeBSD.org References: <5036FB4E.4080407@fluffy.khv.ru> In-Reply-To: <5036FB4E.4080407@fluffy.khv.ru> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: Dima Panov , current@freebsd.org Subject: Re: build error at rpc code X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 24 Aug 2012 08:12:16 -0000 On 2012-08-24 05:55, Dima Panov wrote: > Does anybody get same error at buildworld with recent -current? ... > In file included from /usr/src/lib/libc/../../include/rpc/rpc.h:76: > /usr/src/lib/libc/../../include/rpc/rpcb_clnt.h:69:8: error: unknown > type name 'rpcblist' > extern rpcblist *rpcb_getmaps(const struct netconfig *, const char *); You are most likely setting CPP as follows: CPP=clang -E Don't do that, use the following instead: CPP=clang-cpp If there is no clang-cpp symlink in /usr/bin yet, just make it manually for now. It will also be created by installworld. From owner-freebsd-current@FreeBSD.ORG Fri Aug 24 08:15:47 2012 Return-Path: Delivered-To: current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 847371065678; Fri, 24 Aug 2012 08:15:47 +0000 (UTC) (envelope-from bapt@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 4E0C78FC0C; Fri, 24 Aug 2012 08:15:47 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q7O8FlOo070774; Fri, 24 Aug 2012 08:15:47 GMT (envelope-from bapt@FreeBSD.org) Received: (from bapt@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q7O8FkTG070773; Fri, 24 Aug 2012 08:15:46 GMT (envelope-from bapt@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: bapt set sender to bapt@FreeBSD.org using -f Date: Fri, 24 Aug 2012 10:15:43 +0200 From: Baptiste Daroussin To: Steve Wills Message-ID: <20120824081543.GB2998@ithaqua.etoilebsd.net> References: <97612B57-1255-4BB3-A6D3-FC74324C6D67@FreeBSD.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="RASg3xLB4tUQ4RcS" Content-Disposition: inline In-Reply-To: <97612B57-1255-4BB3-A6D3-FC74324C6D67@FreeBSD.org> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: ports@FreeBSD.org, current@FreeBSD.org Subject: Re: pkgng suggestion: renaming /usr/sbin/pkg to /usr/sbin/pkg-bootstrap X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 24 Aug 2012 08:15:47 -0000 --RASg3xLB4tUQ4RcS Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Aug 23, 2012 at 06:19:57PM -0400, Steve Wills wrote: > Hi, >=20 > It seems to me that renaming the pkg binary in /usr/sbin/pkg to /usr/sbin= /pkg-bootstrap would make sense. From a user standpoint, it is confusing th= at running the command gets different results the second time it is run vs.= the first time. I can imagine a user saying "I ran pkg, but it didn't do w= hat they said it would. Now I run it again, and it does do what it is supp= osed to." Also, it would enable setting up a pkg-bootstrap man page separat= e from the pkg man page, without confusion about which one you're looking a= t. >=20 > So, opinions? There may still be time to fix it for 9.1 if we can decide = quickly. >=20 > Thanks, > Steve >=20 BTW for people who haven't tested and want to share their opinion, here is = how work /usr/sbin/pkg: it first checks if ${LOCALBASE}/sbin/pkg is there - if yes it directly execute ${LOCALBASE}/sbin/pkg with arguments passed t= o /usr/sbin/pkg - if no then it will determine you ABI (or take the one in environnement variable), and fetch the last available pkgng version from http://pkgbet= a... it will extract pkg-static and use it to install pkgng with itself. on installation is done: it executes ${LOCALBASE}/sbin/pkg with argumen= ts passed to /usr/sbin/pkg. Lots of people having ask in the early days of pkgng for a transparent boot= strap I have done it that way. On of the thing I forgot and kan@ has added is a prompt for the user in cas= e it is going to bootstrap. So that mean that for a normal user, on a fresh vanilla FreeBSD "pkg install vim-lite" will prompt the user asking if he wants to bootstrap pkgng, and once bootstraped proceed to the installation of vim-lite if pkgng is already there then it will just install vim-lite. It was just to clarify, so that anyone understand was this is about. I tend to like the bootstrap like it is now (I find it transparent, and str= aight forward) but as I said earlier I have no strong opinion on this, so it most people prefers a separate pkg-bootstrap tools then I'll do it :) regards, Bapt --RASg3xLB4tUQ4RcS Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEARECAAYFAlA3OC8ACgkQ8kTtMUmk6EwKfQCgkaBvYeH3mgmoyiOCXtaj/WFX G6sAn13g8uE8QbLYzFuHu7gvP513zEwJ =ezgl -----END PGP SIGNATURE----- --RASg3xLB4tUQ4RcS-- From owner-freebsd-current@FreeBSD.ORG Fri Aug 24 08:34:02 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 85F74106564A; Fri, 24 Aug 2012 08:34:02 +0000 (UTC) (envelope-from sergey.dyatko@gmail.com) Received: from mail-lb0-f182.google.com (mail-lb0-f182.google.com [209.85.217.182]) by mx1.freebsd.org (Postfix) with ESMTP id B4F5D8FC15; Fri, 24 Aug 2012 08:34:01 +0000 (UTC) Received: by lbbgg13 with SMTP id gg13so1155624lbb.13 for ; Fri, 24 Aug 2012 01:34:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:cc:subject:message-id:in-reply-to:references:x-mailer :mime-version:content-type:content-transfer-encoding; bh=ofNE824WX1hHVMqqMZ1O+ISykT4JB+KtueWuIDZIwtI=; b=FMdZmrcXyhWBTI2no35GpXtgMejs6gKpHF8zCmfyan1UH24gfJldIqIrLC34g5TxdI SQ5Zcs+YInztsG/lEFeagcBJwF4VmN/KtqVtEQcOj3fhU3hMv9hcT0Qrvx1FSGkc4dHS F7iPZSEY3pNBnDAZpqyIJ9HvXKrPPCvK8ssOL55j+F0PM0H8Zan3RXgBiT9LgM0cNVcX 4jupmxoysjLQmaBhaYtTQw8ruUyH7R0U6WaEhTM9yQieaP7mZ9xZVK1M2sJt7deppKHB Hf5JeItZgUlwF8NLdz+H5GLiMuYcrg7FSeYTci97FNSsMfblcEc8dwv2su1WlRmfbos8 Zx6g== Received: by 10.112.17.195 with SMTP id q3mr2351344lbd.34.1345797240287; Fri, 24 Aug 2012 01:34:00 -0700 (PDT) Received: from laptop (m-s.agava.net. [195.222.84.203]) by mx.google.com with ESMTPS id sm7sm9786951lab.5.2012.08.24.01.33.57 (version=SSLv3 cipher=OTHER); Fri, 24 Aug 2012 01:33:59 -0700 (PDT) Date: Fri, 24 Aug 2012 11:35:10 +0300 From: "Sergey V. Dyatko" Message-ID: <20120824113510.5ad72992@laptop> In-Reply-To: References: <97612B57-1255-4BB3-A6D3-FC74324C6D67@FreeBSD.org> <785B5BAD-E015-4624-B3A1-D05E1BD97E51@freebsd.org> <5AC662AA-4874-4BC2-9862-65518B79B840@freebsd.org> X-Mailer: Claws Mail 3.8.1 (GTK+ 2.24.6; amd64-portbld-freebsd10.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: ports@freebsd.org, current@freebsd.org Subject: Re: pkgng suggestion: renaming /usr/sbin/pkg to /usr/sbin/pkg-bootstrap X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 24 Aug 2012 08:34:02 -0000 On Thu, 23 Aug 2012 23:00:25 -0400 Eitan Adler wrote: > On 23 August 2012 22:55, Steve Wills wrote: > > > As far as I understand it, POLA is about changing existing things: > > okay, so forget POLA. My point is that a user following a how to or > even *our* documentation on how to install something unrelated, like > say, apache, will be very confused when the documentation tells them > to run "pkg install apache" and finds out that pkg doesn't exist. A > similar example is needing "rehash" in tcsh. > what about autorehash, it didn't work ? you commit that change into default tcsh config long time ago :) -- wbr, tiger From owner-freebsd-current@FreeBSD.ORG Fri Aug 24 08:44:28 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 87C54106564A; Fri, 24 Aug 2012 08:44:28 +0000 (UTC) (envelope-from flo@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 56D9C8FC0C; Fri, 24 Aug 2012 08:44:28 +0000 (UTC) Received: from bender.solomo.local (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q7O8iQjb076261; Fri, 24 Aug 2012 08:44:27 GMT (envelope-from flo@freebsd.org) Message-ID: <50373EEA.3080104@freebsd.org> Date: Fri, 24 Aug 2012 10:44:26 +0200 From: Florian Smeets User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:15.0) Gecko/20120823 Thunderbird/15.0 MIME-Version: 1.0 To: Baptiste Daroussin References: <97612B57-1255-4BB3-A6D3-FC74324C6D67@FreeBSD.org> <20120824081543.GB2998@ithaqua.etoilebsd.net> In-Reply-To: <20120824081543.GB2998@ithaqua.etoilebsd.net> X-Enigmail-Version: 1.4.3 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: ports@freebsd.org, Steve Wills , current@freebsd.org Subject: Re: pkgng suggestion: renaming /usr/sbin/pkg to /usr/sbin/pkg-bootstrap X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 24 Aug 2012 08:44:28 -0000 On 08/24/2012 10:15, Baptiste Daroussin wrote: > On Thu, Aug 23, 2012 at 06:19:57PM -0400, Steve Wills wrote: >> Hi, >> >> It seems to me that renaming the pkg binary in /usr/sbin/pkg to /usr/sbin/pkg-bootstrap would make sense. From a user standpoint, it is confusing that running the command gets different results the second time it is run vs. the first time. I can imagine a user saying "I ran pkg, but it didn't do what they said it would. Now I run it again, and it does do what it is supposed to." Also, it would enable setting up a pkg-bootstrap man page separate from the pkg man page, without confusion about which one you're looking at. >> >> So, opinions? There may still be time to fix it for 9.1 if we can decide quickly. >> >> Thanks, >> Steve >> > > BTW for people who haven't tested and want to share their opinion, here is how > work /usr/sbin/pkg: > > it first checks if ${LOCALBASE}/sbin/pkg is there > - if yes it directly execute ${LOCALBASE}/sbin/pkg with arguments passed to /usr/sbin/pkg > - if no then it will determine you ABI (or take the one in environnement > variable), and fetch the last available pkgng version from http://pkgbeta... > it will extract pkg-static and use it to install pkgng with itself. > on installation is done: it executes ${LOCALBASE}/sbin/pkg with arguments > passed to /usr/sbin/pkg. > > Lots of people having ask in the early days of pkgng for a transparent bootstrap > I have done it that way. > > On of the thing I forgot and kan@ has added is a prompt for the user in case it > is going to bootstrap. > > So that mean that for a normal user, on a fresh vanilla FreeBSD > "pkg install vim-lite" will prompt the user asking if he wants to bootstrap > pkgng, and once bootstraped proceed to the installation of vim-lite > > if pkgng is already there then it will just install vim-lite. > > It was just to clarify, so that anyone understand was this is about. > > I tend to like the bootstrap like it is now (I find it transparent, and straight > forward) but as I said earlier I have no strong opinion on this, so it most > people prefers a separate pkg-bootstrap tools then I'll do it :) Having installed a few 9.1-BETA1 boxes recently, i have to say i absolutely like this behavior, it's totally transparent and you can just start installing packages like you could with pkg_add -r. I don't see the need to introduce an additional step. I actually think the current behavior is user friendly, and renaming it would make it more difficult. If people think the current behavior is misleading we could still clarify the confirmation message. Florian From owner-freebsd-current@FreeBSD.ORG Fri Aug 24 09:44:50 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7054B106566B; Fri, 24 Aug 2012 09:44:50 +0000 (UTC) (envelope-from des@des.no) Received: from smtp.des.no (smtp.des.no [194.63.250.102]) by mx1.freebsd.org (Postfix) with ESMTP id 2FF8A8FC0A; Fri, 24 Aug 2012 09:44:50 +0000 (UTC) Received: from ds4.des.no (smtp.des.no [194.63.250.102]) by smtp.des.no (Postfix) with ESMTP id 62768658B; Fri, 24 Aug 2012 11:44:49 +0200 (CEST) Received: by ds4.des.no (Postfix, from userid 1001) id 27EAA8CA7; Fri, 24 Aug 2012 11:44:49 +0200 (CEST) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: John Baldwin References: <502831B7.1080309@freebsd.org> <86zk5y55rg.fsf@ds4.des.no> <201208141346.12782.jhb@freebsd.org> Date: Fri, 24 Aug 2012 11:44:48 +0200 In-Reply-To: <201208141346.12782.jhb@freebsd.org> (John Baldwin's message of "Tue, 14 Aug 2012 13:46:12 -0400") Message-ID: <86a9xklj3j.fsf@ds4.des.no> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.4 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: alc@freebsd.org, freebsd-current@freebsd.org, Colin Percival Subject: Re: Time to bump default VM_SWZONE_SIZE_MAX? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 24 Aug 2012 09:44:50 -0000 John Baldwin writes: > Hmm, this is not true on i386 where the problem is not just the physical > RAM required, but also address space. (The swap zone is all mapped into = KVA=20 > even if it isn't used.) This is why Alan's e-mail specifically > mentioned amd64, ia64, etc. but not i386 in his list. I think i386 still > needs this limit, and I think your commit jumped the gun a bit. How about we reinstate the limit on i386, but increase it to 64 MB? That would increase the theoretical maximum to ~15 GB. People with 8 GB swap would get a warning, but would be unlikely to run into trouble. (or we could increase the limit to 72351744 bytes, which is the precise amount required to support 16 GB) DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no From owner-freebsd-current@FreeBSD.ORG Fri Aug 24 11:37:03 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D69731065673; Fri, 24 Aug 2012 11:37:02 +0000 (UTC) (envelope-from utisoft@gmail.com) Received: from mail-bk0-f54.google.com (mail-bk0-f54.google.com [209.85.214.54]) by mx1.freebsd.org (Postfix) with ESMTP id 2F63A8FC0A; Fri, 24 Aug 2012 11:37:01 +0000 (UTC) Received: by bkcje9 with SMTP id je9so1142658bkc.13 for ; Fri, 24 Aug 2012 04:37:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=QBFQCd80Ay4QDhCSSiFMLfwJzI3Xl3KqTAFZJen+82U=; b=uDAhP2xOtFx8rT8KnY3u7mPYCrDjVzxQdUL6IY87ouRyMOwR9Rva++63ivDoIIvZzx cl5m1QQGZDL2WlAqYDnvHjI5LpHXXzi9fgatin3RNDSvQSpBdO0ndFEtwghcvuY4m5ww R6C6oea8mY6+9nCDKDvWop3Ivms2TDole8NDFJSQQRPH1gxYQl6JuuBs8CGW2qBQTyF5 bFfu+5CSG4JhPjS/nRYBMQws+tsU7f7TPPkTMCFwaKukG0nzQjEi/3JM6mfaOaixzvpu NKHWezo7/O8oRLcg1u1brUiYpe24P0virvGmwTDZBy2XD7W5kMPkKoMe+Ga8K1rfSMd6 UVbA== MIME-Version: 1.0 Received: by 10.204.157.18 with SMTP id z18mr1809294bkw.16.1345808220878; Fri, 24 Aug 2012 04:37:00 -0700 (PDT) Received: by 10.204.10.141 with HTTP; Fri, 24 Aug 2012 04:37:00 -0700 (PDT) Received: by 10.204.10.141 with HTTP; Fri, 24 Aug 2012 04:37:00 -0700 (PDT) In-Reply-To: <1345802881.43379.YahooMailClassic@web111306.mail.gq1.yahoo.com> References: <1345802881.43379.YahooMailClassic@web111306.mail.gq1.yahoo.com> Date: Fri, 24 Aug 2012 12:37:00 +0100 Message-ID: From: Chris Rees To: Jeffrey Bouquet Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-current , FreeBSD Mailing List Subject: RE: pkgng default release schedule (contd...) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 24 Aug 2012 11:37:03 -0000 On 24 Aug 2012 11:08, "Jeffrey Bouquet" wrote: > > A few more reasons (unless I have not seen some relevant documentation to the contrary) to not mandate pkgng as the default... Why don't you phrase this as "How can one ..." so you sound less negative? > Nowadays, one can save time by installing two ports which officially or unofficially conflict, and have /var/db/pkg entries for both, and even > local workarounds (for instance, moving the duplicate binary elsewhere before the second install) (Perchance removing the line in the Makefile). Currently you can still do this, at least until STAGEDIR. > A failed "make install (register)", one can check the /var/db/pkg/ directory(ies) to double check visually to what extent it did NOT fail. > Similarly for a failed "make deinstall (unregister)"... The error messages are perfectly clear. > pkgdb -F to fixup stale dependencies and resolve dependency information. Unnecessary with pkgng. > A proven method in the portmaster manpage to reinstall all ports. You want to talk to the portmaster author about that. Chris From owner-freebsd-current@FreeBSD.ORG Fri Aug 24 10:08:08 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D3951106566C for ; Fri, 24 Aug 2012 10:08:08 +0000 (UTC) (envelope-from jeffreybouquet@yahoo.com) Received: from nm26.bullet.mail.sp2.yahoo.com (nm26.bullet.mail.sp2.yahoo.com [98.139.91.96]) by mx1.freebsd.org (Postfix) with SMTP id 8FEE08FC08 for ; Fri, 24 Aug 2012 10:08:08 +0000 (UTC) Received: from [98.139.91.62] by nm26.bullet.mail.sp2.yahoo.com with NNFMP; 24 Aug 2012 10:08:02 -0000 Received: from [98.139.91.49] by tm2.bullet.mail.sp2.yahoo.com with NNFMP; 24 Aug 2012 10:08:02 -0000 Received: from [127.0.0.1] by omp1049.mail.sp2.yahoo.com with NNFMP; 24 Aug 2012 10:08:02 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 280108.50494.bm@omp1049.mail.sp2.yahoo.com Received: (qmail 57972 invoked by uid 60001); 24 Aug 2012 10:08:01 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1345802881; bh=TkXAd1ezCwoeyVLE4024odVcuXL388mpyyrElTj0KyQ=; h=X-YMail-OSG:Received:X-Mailer:Message-ID:Date:From:Subject:To:Cc:MIME-Version:Content-Type; b=f2PpU7X8ZrvwWKqFkN3c5YZBYkqgrVKsZKC2htYbOC4yn4Q3zhyJZ8AYodtUh4CO5/CHT69WrqZLOmgIJ//0xh/negc6VMpfHUrx+MnR+iG9pQRKbRqcl73AmUePa+ZywGEFN1yUfqXzuQ8YHZ11gpU73LwU3QigicjpmRkivEw= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:Message-ID:Date:From:Subject:To:Cc:MIME-Version:Content-Type; b=quwonPkQEGzfdJLSlBKU/vBZ0iRmS1FmHNYUiFePex2IxkO+JUpvc6aGAtf+OC9hEeKawS8JU88ZDyRFpsXT8yUTExxsExxDb8suG3hLhpkf+rFNygjWnJr/MfMoZRchNKOKmQcI5u/VCELEw9TLfYPWCIz0EOVvacldcB5g7YQ=; X-YMail-OSG: fp2olosVM1lstND4mBXIgFICHOBk3kDf9UTG9km2ZUsOylC C34EidgOcy2NPZmUbwGh4TcaWqp1DHSbssH0WHCugBsT.0F.wNFsn1..wQ2c NfdnatOARXg8iBeZLIwxpdFkgrwe3QwVnv4Cf7BgZ0du3jZpNiB6_GumgZFa mb8iy0CXT07bIF5LusLfm03PF5Fs31SnkKC0LeWN8mKoCQKeR18SIl51j1pp 6CPwbq97GZslaoshOSTnnt.3izvfscoBxsEp4WYeNgdKCXMMOe05zLeSgcxF sGKzcQBKIUa2DaAoyKhkl54ZGvt6hZS0B9Wrv5UClft43zb_S9ToJsGGiPp5 XIuabv4YlXSHcnIUL4ZTBpCHwNBQicJ_U86g1a6d8UiZzuslI6p5IYPzYFpQ GGFOIIeoFFeR4pmwAlgrn7tXPRYotJLkjedRdcx1K5V6_Sfx4sN.4BeFGR2y 4gaK.2omFCc8Gg.F1I0f_DHoQ Received: from [66.92.43.99] by web111306.mail.gq1.yahoo.com via HTTP; Fri, 24 Aug 2012 03:08:01 PDT X-Mailer: YahooMailClassic/15.0.8 YahooMailWebService/0.8.121.416 Message-ID: <1345802881.43379.YahooMailClassic@web111306.mail.gq1.yahoo.com> Date: Fri, 24 Aug 2012 03:08:01 -0700 (PDT) From: Jeffrey Bouquet To: freebsd-ports@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailman-Approved-At: Fri, 24 Aug 2012 11:37:09 +0000 Cc: freebsd-current@freebsd.org Subject: RE: pkgng default release schedule (contd...) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 24 Aug 2012 10:08:08 -0000 A few more reasons (unless I have not seen some relevant documentation to the contrary) to not mandate pkgng as the default... Nowadays, one can save time by installing two ports which officially or unofficially conflict, and have /var/db/pkg entries for both, and even local workarounds (for instance, moving the duplicate binary elsewhere before the second install) (Perchance removing the line in the Makefile). ... A failed "make install (register)", one can check the /var/db/pkg/ directory(ies) to double check visually to what extent it did NOT fail. Similarly for a failed "make deinstall (unregister)"... ... pkgdb -F to fixup stale dependencies and resolve dependency information. A proven method in the portmaster manpage to reinstall all ports. From owner-freebsd-current@FreeBSD.ORG Fri Aug 24 12:23:59 2012 Return-Path: Delivered-To: current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B65841065670 for ; Fri, 24 Aug 2012 12:23:59 +0000 (UTC) (envelope-from ale@FreeBSD.org) Received: from andxor.it (relay.andxor.it [195.223.2.3]) by mx1.freebsd.org (Postfix) with SMTP id BF2928FC12 for ; Fri, 24 Aug 2012 12:23:55 +0000 (UTC) Received: (qmail 5473 invoked from network); 24 Aug 2012 12:23:47 -0000 Received: from unknown (HELO alex.andxor.it) (192.168.2.30) by andxor.it with SMTP; 24 Aug 2012 12:23:47 -0000 Message-ID: <50377253.103@FreeBSD.org> Date: Fri, 24 Aug 2012 14:23:47 +0200 From: Alex Dupre User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:14.0) Gecko/20120806 Firefox/14.0.1 SeaMonkey/2.11 MIME-Version: 1.0 To: Baptiste Daroussin References: <97612B57-1255-4BB3-A6D3-FC74324C6D67@FreeBSD.org> <20120824081543.GB2998@ithaqua.etoilebsd.net> In-Reply-To: <20120824081543.GB2998@ithaqua.etoilebsd.net> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: ports@FreeBSD.org, Steve Wills , current@FreeBSD.org Subject: Re: pkgng suggestion: renaming /usr/sbin/pkg to /usr/sbin/pkg-bootstrap X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 24 Aug 2012 12:23:59 -0000 Baptiste Daroussin ha scritto: > On of the thing I forgot and kan@ has added is a prompt for the user in case it > is going to bootstrap. So, removing the prompt will make everybody happy? :-) What about a prompt with timeout? "This is the first time pkg is run, I'll start bootstrapping in 10 seconds. Press CTRL-C now to abort" -- Alex Dupre From owner-freebsd-current@FreeBSD.ORG Fri Aug 24 12:36:25 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 93560106566C; Fri, 24 Aug 2012 12:36:25 +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 685228FC16; Fri, 24 Aug 2012 12:36:25 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id C2F00B91E; Fri, 24 Aug 2012 08:36:24 -0400 (EDT) From: John Baldwin To: "Dag-Erling =?utf-8?q?Sm=C3=B8rgrav?=" Date: Fri, 24 Aug 2012 07:48:19 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110714-p17; KDE/4.5.5; amd64; ; ) References: <502831B7.1080309@freebsd.org> <201208141346.12782.jhb@freebsd.org> <86a9xklj3j.fsf@ds4.des.no> In-Reply-To: <86a9xklj3j.fsf@ds4.des.no> MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Message-Id: <201208240748.19737.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Fri, 24 Aug 2012 08:36:24 -0400 (EDT) Cc: alc@freebsd.org, freebsd-current@freebsd.org, Colin Percival Subject: Re: Time to bump default VM_SWZONE_SIZE_MAX? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 24 Aug 2012 12:36:25 -0000 On Friday, August 24, 2012 5:44:48 am Dag-Erling Sm=C3=B8rgrav wrote: > John Baldwin writes: > > Hmm, this is not true on i386 where the problem is not just the physical > > RAM required, but also address space. (The swap zone is all mapped int= o KVA=20 > > even if it isn't used.) This is why Alan's e-mail specifically > > mentioned amd64, ia64, etc. but not i386 in his list. I think i386 sti= ll > > needs this limit, and I think your commit jumped the gun a bit. >=20 > How about we reinstate the limit on i386, but increase it to 64 MB? > That would increase the theoretical maximum to ~15 GB. People with 8 GB > swap would get a warning, but would be unlikely to run into trouble. >=20 > (or we could increase the limit to 72351744 bytes, which is the precise > amount required to support 16 GB) Note that on i386 you can't get more than 4GB of RAM without PAE, and if you have any modern x86 box with > 4GB of RAM, you are most likely running amd64 on it, not i386. I think i386 would be fine to just keep the limit it had. =2D-=20 John Baldwin From owner-freebsd-current@FreeBSD.ORG Fri Aug 24 12:45:46 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2EB68106564A; Fri, 24 Aug 2012 12:45:46 +0000 (UTC) (envelope-from des@des.no) Received: from smtp.des.no (smtp.des.no [194.63.250.102]) by mx1.freebsd.org (Postfix) with ESMTP id E19968FC0C; Fri, 24 Aug 2012 12:45:45 +0000 (UTC) Received: from ds4.des.no (smtp.des.no [194.63.250.102]) by smtp.des.no (Postfix) with ESMTP id 1E5E76638; Fri, 24 Aug 2012 14:45:44 +0200 (CEST) Received: by ds4.des.no (Postfix, from userid 1001) id B43E38CCB; Fri, 24 Aug 2012 14:45:43 +0200 (CEST) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: John Baldwin References: <502831B7.1080309@freebsd.org> <201208141346.12782.jhb@freebsd.org> <86a9xklj3j.fsf@ds4.des.no> <201208240748.19737.jhb@freebsd.org> Date: Fri, 24 Aug 2012 14:45:43 +0200 In-Reply-To: <201208240748.19737.jhb@freebsd.org> (John Baldwin's message of "Fri, 24 Aug 2012 07:48:19 -0400") Message-ID: <866288laq0.fsf@ds4.des.no> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.4 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: alc@freebsd.org, freebsd-current@freebsd.org, Colin Percival Subject: Re: Time to bump default VM_SWZONE_SIZE_MAX? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 24 Aug 2012 12:45:46 -0000 John Baldwin writes: > Note that on i386 you can't get more than 4GB of RAM without PAE, and if = you > have any modern x86 box with > 4GB of RAM, you are most likely running am= d64 > on it, not i386. I think i386 would be fine to just keep the limit it ha= d. The limit we had was insufficient for 8 GB of swap. DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no From owner-freebsd-current@FreeBSD.ORG Fri Aug 24 13:08:05 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 41353106564A; Fri, 24 Aug 2012 13:08:05 +0000 (UTC) (envelope-from fluffy@fluffy.khv.ru) Received: from forward5.mail.yandex.net (forward5.mail.yandex.net [IPv6:2a02:6b8:0:602::5]) by mx1.freebsd.org (Postfix) with ESMTP id B5DF78FC0C; Fri, 24 Aug 2012 13:08:04 +0000 (UTC) Received: from smtp4.mail.yandex.net (smtp4.mail.yandex.net [77.88.46.104]) by forward5.mail.yandex.net (Yandex) with ESMTP id 54466120106C; Fri, 24 Aug 2012 17:08:03 +0400 (MSK) Received: from smtp4.mail.yandex.net (localhost [127.0.0.1]) by smtp4.mail.yandex.net (Yandex) with ESMTP id 1FF005C050A; Fri, 24 Aug 2012 17:08:03 +0400 (MSK) Received: from host85.static2.l2tp.ttkdv.ru (host85.static2.l2tp.ttkdv.ru [46.38.1.85]) by smtp4.mail.yandex.net (nwsmtp/Yandex) with ESMTP id 809KR6NX-819WJnUu; Fri, 24 Aug 2012 17:08:01 +0400 Message-ID: <50377C8A.40000@fluffy.khv.ru> Date: Sat, 25 Aug 2012 00:07:22 +1100 From: Dima Panov User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0 MIME-Version: 1.0 To: Dimitry Andric References: <5036FB4E.4080407@fluffy.khv.ru> <50373763.50608@andric.com> In-Reply-To: <50373763.50608@andric.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Cc: current@freebsd.org, fluffy@FreeBSD.org Subject: Re: build error at rpc code X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: fluffy@FreeBSD.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Aug 2012 13:08:05 -0000 24.08.2012 19:12, Dimitry Andric пишет: > On 2012-08-24 05:55, Dima Panov wrote: >> Does anybody get same error at buildworld with recent -current? > ... >> In file included from /usr/src/lib/libc/../../include/rpc/rpc.h:76: >> /usr/src/lib/libc/../../include/rpc/rpcb_clnt.h:69:8: error: unknown >> type name 'rpcblist' >> extern rpcblist *rpcb_getmaps(const struct netconfig *, const char *); > > You are most likely setting CPP as follows: > > CPP=clang -E > > Don't do that, use the following instead: > > CPP=clang-cpp > > If there is no clang-cpp symlink in /usr/bin yet, just make it manually > for now. It will also be created by installworld. Oh, indeed. Thanks for advice. However, why such different results in preprocessor invocation style? -- Dima Panov (fluffy@FreeBSD.org) (KDE, Office)@FreeBSD team Facebook: http://www.facebook.com/fluffy.khv IRC: fluffy@EFNet, fluffykhv@FreeNode twitter: fluffy_khv | skype: dima.panov From owner-freebsd-current@FreeBSD.ORG Fri Aug 24 13:20:13 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9BEBD106566C; Fri, 24 Aug 2012 13:20:13 +0000 (UTC) (envelope-from dimitry@andric.com) Received: from tensor.andric.com (cl-327.ede-01.nl.sixxs.net [IPv6:2001:7b8:2ff:146::2]) by mx1.freebsd.org (Postfix) with ESMTP id 58B448FC17; Fri, 24 Aug 2012 13:20:13 +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 D93895C59; Fri, 24 Aug 2012 15:20:11 +0200 (CEST) Message-ID: <50377F8F.8000005@andric.com> Date: Fri, 24 Aug 2012 15:20:15 +0200 From: Dimitry Andric User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20120815 Thunderbird/15.0 MIME-Version: 1.0 To: fluffy@FreeBSD.org References: <5036FB4E.4080407@fluffy.khv.ru> <50373763.50608@andric.com> <50377C8A.40000@fluffy.khv.ru> In-Reply-To: <50377C8A.40000@fluffy.khv.ru> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable Cc: Dima Panov , current@freebsd.org Subject: Re: build error at rpc code X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 24 Aug 2012 13:20:13 -0000 On 2012-08-24 15:07, Dima Panov wrote: > 24.08.2012 19:12, Dimitry Andric =D0=BF=D0=B8=D1=88=D0=B5=D1=82: =2E.. >> You are most likely setting CPP as follows: >> >> CPP=3Dclang -E >> >> Don't do that, use the following instead: >> >> CPP=3Dclang-cpp >> >> If there is no clang-cpp symlink in /usr/bin yet, just make it manuall= y >> for now. It will also be created by installworld. > > Oh, indeed. Thanks for advice. > However, why such different results in preprocessor invocation style? When you invoke either clang or gcc with -E, files with unknown extensions are not preprocessed, and considered to be linker input files. When you invoke clang-cpp or cpp, files with unknown extensions are considered to be C instead. Since our RPC-related files use the .x extension, -E doesn't work as expected, and the resulting files will give a compile error later on. From owner-freebsd-current@FreeBSD.ORG Fri Aug 24 14:17:10 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CD6831065673; Fri, 24 Aug 2012 14:17:10 +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 A1B948FC19; Fri, 24 Aug 2012 14:17:10 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 0D9C6B91E; Fri, 24 Aug 2012 10:17:10 -0400 (EDT) From: John Baldwin To: "Dag-Erling =?utf-8?q?Sm=C3=B8rgrav?=" Date: Fri, 24 Aug 2012 10:13:48 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110714-p17; KDE/4.5.5; amd64; ; ) References: <502831B7.1080309@freebsd.org> <201208240748.19737.jhb@freebsd.org> <866288laq0.fsf@ds4.des.no> In-Reply-To: <866288laq0.fsf@ds4.des.no> MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Message-Id: <201208241013.48805.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Fri, 24 Aug 2012 10:17:10 -0400 (EDT) Cc: alc@freebsd.org, freebsd-current@freebsd.org, Colin Percival Subject: Re: Time to bump default VM_SWZONE_SIZE_MAX? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 24 Aug 2012 14:17:10 -0000 On Friday, August 24, 2012 8:45:43 am Dag-Erling Sm=C3=B8rgrav wrote: > John Baldwin writes: > > Note that on i386 you can't get more than 4GB of RAM without PAE, and i= f you > > have any modern x86 box with > 4GB of RAM, you are most likely running = amd64 > > on it, not i386. I think i386 would be fine to just keep the limit it = had. >=20 > The limit we had was insufficient for 8 GB of swap. In absolute or practical terms? Not all swap blocks are fully utilized. At Y! the install script we used would compute the maximum theoretical swap zo= ne needed and then cut it in half, and this worked quite well. Also, keep in = mind, this is for i386, not amd64. At this point i386 is going to be used on sma= ller systems (e.g. netbooks, etc.), not servers that have lots of swap. =2D-=20 John Baldwin From owner-freebsd-current@FreeBSD.ORG Fri Aug 24 14:31:23 2012 Return-Path: Delivered-To: current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AD78A106566C; Fri, 24 Aug 2012 14:31:23 +0000 (UTC) (envelope-from bapt@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 8EAE98FC0A; Fri, 24 Aug 2012 14:31:23 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q7OEVNlH027112; Fri, 24 Aug 2012 14:31:23 GMT (envelope-from bapt@FreeBSD.org) Received: (from bapt@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q7OEVNWh027111; Fri, 24 Aug 2012 14:31:23 GMT (envelope-from bapt@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: bapt set sender to bapt@FreeBSD.org using -f Date: Fri, 24 Aug 2012 16:31:19 +0200 From: Baptiste Daroussin To: Alex Dupre Message-ID: <20120824143119.GA37867@ithaqua.etoilebsd.net> References: <97612B57-1255-4BB3-A6D3-FC74324C6D67@FreeBSD.org> <20120824081543.GB2998@ithaqua.etoilebsd.net> <50377253.103@FreeBSD.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="CE+1k2dSO48ffgeK" Content-Disposition: inline In-Reply-To: <50377253.103@FreeBSD.org> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: ports@FreeBSD.org, Steve Wills , current@FreeBSD.org Subject: Re: pkgng suggestion: renaming /usr/sbin/pkg to /usr/sbin/pkg-bootstrap X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 24 Aug 2012 14:31:23 -0000 --CE+1k2dSO48ffgeK Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Aug 24, 2012 at 02:23:47PM +0200, Alex Dupre wrote: > Baptiste Daroussin ha scritto: >=20 > > On of the thing I forgot and kan@ has added is a prompt for the user in= case it > > is going to bootstrap. >=20 > So, removing the prompt will make everybody happy? :-) >=20 > What about a prompt with timeout? "This is the first time pkg is run, > I'll start bootstrapping in 10 seconds. Press CTRL-C now to abort" >=20 Imho the best is to prompt only if not on a tty, otherwise fail, except if a environment variable is set. regards, Bapt --CE+1k2dSO48ffgeK Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEARECAAYFAlA3kDcACgkQ8kTtMUmk6EwRewCfSiR48mswCrUedcY98cxSFLG+ PIoAoK84J6VYIySduX82TQ9+4S9kd6Sy =oTbt -----END PGP SIGNATURE----- --CE+1k2dSO48ffgeK-- From owner-freebsd-current@FreeBSD.ORG Fri Aug 24 14:38:05 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 16256106564A; Fri, 24 Aug 2012 14:38:05 +0000 (UTC) (envelope-from luigi@onelab2.iet.unipi.it) Received: from onelab2.iet.unipi.it (onelab2.iet.unipi.it [131.114.59.238]) by mx1.freebsd.org (Postfix) with ESMTP id C1EE58FC12; Fri, 24 Aug 2012 14:38:03 +0000 (UTC) Received: by onelab2.iet.unipi.it (Postfix, from userid 275) id 83FB57300A; Fri, 24 Aug 2012 16:57:08 +0200 (CEST) Date: Fri, 24 Aug 2012 16:57:08 +0200 From: Luigi Rizzo To: Alan Cox Message-ID: <20120824145708.GA16557@onelab2.iet.unipi.it> References: <20120822120105.GA63763@onelab2.iet.unipi.it> <20120823163145.GA3999@onelab2.iet.unipi.it> <50366398.2070700@rice.edu> <20120823174504.GB4820@onelab2.iet.unipi.it> <50371485.1020409@rice.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <50371485.1020409@rice.edu> User-Agent: Mutt/1.4.2.3i Cc: alc@freebsd.org, current@freebsd.org Subject: Re: less aggressive contigmalloc ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 24 Aug 2012 14:38:05 -0000 On Fri, Aug 24, 2012 at 12:43:33AM -0500, Alan Cox wrote: > On 08/23/2012 12:45, Luigi Rizzo wrote: > >On Thu, Aug 23, 2012 at 12:08:40PM -0500, Alan Cox wrote: > >... > >>>yes i do see that. > >>> > >>>Maybe less aggressive with M_NOWAIT but still kills processes. > >>Are you compiling world with MALLOC_PRODUCTION? The latest version of > >whatever the default is. But: > > > >>jemalloc uses significantly more memory when debugging options are > >>enabled. This first came up in a thread titled "10-CURRENT and swap > >>usage" back in June. > >> > >>Even at its most aggressive, M_WAITOK, contigmalloc() does not directly > >>kill processes. If process death coincides with the use of > >>contigmalloc(), then it is simply the result of earlier, successful > >>contigmalloc() calls, or for that matter any other physical memory > >>allocation calls, having depleted the pool of free pages to the point > >>that the page daemon runs and invokes vm_pageout_oom(). > >does it mean that those previous allocations relied on memory overbooking ? > > Yes. > > >Is there a way to avoid that, then ? > > I believe that malloc()'s default minimum allocation size is 4MB. You > could reduce that. > > Alternatively, you can enable MALLOC_PRODUCTION. i tried this, and as others mentioned it makes life better and reduces the problem but contigmalloc still triggers random process kills. Thanks for the hints. cheers luigi From owner-freebsd-current@FreeBSD.ORG Fri Aug 24 15:50:14 2012 Return-Path: Delivered-To: current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 70C6E106567A for ; Fri, 24 Aug 2012 15:50:14 +0000 (UTC) (envelope-from bryan@shatow.net) Received: from secure.xzibition.com (secure.xzibition.com [173.160.118.92]) by mx1.freebsd.org (Postfix) with ESMTP id C1BBB8FC1A for ; Fri, 24 Aug 2012 15:50:13 +0000 (UTC) DomainKey-Signature: a=rsa-sha1; c=nofws; d=shatow.net; h=message-id :date:from:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; q=dns; s=sweb; b=ADsuIa OldxNIs7pN/X/JK+AGF5+ca7STZxpPowPrXBL88PWiMD8LW0U8ECuqpbNZ/Dm8nD PnKbUOLUtvZljGWooj68EcU5O+zs8+WGJoeAMAN6AOAQ7onbK4T/mRGZWMprIoUh iiQHEXHPRbd+ZFSTA8vQtTQdkXEd7imMDlmKQ= DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=shatow.net; h=message-id :date:from:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; s=sweb; bh=khnnk0NWx9Nq lGw6dL4cYW6ECViT42kMOlIIBy7AlAQ=; b=uEIpOkQasI5HTZRRkX/0sLlfa8TU tUJNxndETkt9v0Mo/qAUhJ7iZ/NXNjJl/fdAskK8g3y+CdZD8Ux8KoSt5OaKyVdb PxEbzyw5fVtfnK3yIk27yqundzvLuQpuh/ByQOyE/njEWIgaMUe7Y+5OhJoeJ8M0 ntexVyGBgSFSmDg= Received: (qmail 57641 invoked from network); 24 Aug 2012 10:50:04 -0500 Received: from unknown (HELO ?192.168.0.74?) (bryan@shatow.net@74.94.87.209) by sweb.xzibition.com with ESMTPA; 24 Aug 2012 10:50:04 -0500 Message-ID: <5037A2C6.4060200@shatow.net> Date: Fri, 24 Aug 2012 10:50:30 -0500 From: Bryan Drewery User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0 MIME-Version: 1.0 To: Baptiste Daroussin References: <97612B57-1255-4BB3-A6D3-FC74324C6D67@FreeBSD.org> <20120824081543.GB2998@ithaqua.etoilebsd.net> <50377253.103@FreeBSD.org> <20120824143119.GA37867@ithaqua.etoilebsd.net> In-Reply-To: <20120824143119.GA37867@ithaqua.etoilebsd.net> X-Enigmail-Version: 1.4.3 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: ports@FreeBSD.org, Steve Wills , current@FreeBSD.org, Alex Dupre Subject: Re: pkgng suggestion: renaming /usr/sbin/pkg to /usr/sbin/pkg-bootstrap X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 24 Aug 2012 15:50:14 -0000 On 8/24/2012 9:31 AM, Baptiste Daroussin wrote: > On Fri, Aug 24, 2012 at 02:23:47PM +0200, Alex Dupre wrote: >> Baptiste Daroussin ha scritto: >> >>> On of the thing I forgot and kan@ has added is a prompt for the user in case it >>> is going to bootstrap. >> >> So, removing the prompt will make everybody happy? :-) >> >> What about a prompt with timeout? "This is the first time pkg is run, >> I'll start bootstrapping in 10 seconds. Press CTRL-C now to abort" >> > > Imho the best is to prompt only if not on a tty, otherwise fail, except if a > environment variable is set. > > regards, > Bapt > Maybe an ENV variable to auto confirm the prompt too? I'm thinking about scripts using pkg to bootstrap an entire system install. Maybe I'm on a TTY and just want it to confirm auto anyway. Bryan From owner-freebsd-current@FreeBSD.ORG Fri Aug 24 15:51:25 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 52C18106566C for ; Fri, 24 Aug 2012 15:51:25 +0000 (UTC) (envelope-from simon@qxnitro.org) Received: from mail-ob0-f182.google.com (mail-ob0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id 08A348FC20 for ; Fri, 24 Aug 2012 15:51:24 +0000 (UTC) Received: by obbun3 with SMTP id un3so5900054obb.13 for ; Fri, 24 Aug 2012 08:51:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=qxnitro.org; s=google; h=mime-version:sender:x-originating-ip:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type :content-transfer-encoding; bh=72mTIhSEsmdYeImhKkR4ZtlStRj/dkI7FSimwKU4miA=; b=GphMNkMPB3rh/3S3KCDM00ohza4tEzslTpMhChUGSiJVKrnBdtADJRrRCC5YuvZRxa q+Q5MuKxsDUUurt7PdSjgo01ExNp5m/cw2nvRZUxV27LEpM8uQcoXuF7ANq6coBRdrL6 lwYq1VLkYtLsMUUoJmfAJkuBhgodwpE+jPVVU= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:sender:x-originating-ip:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type :content-transfer-encoding:x-gm-message-state; bh=72mTIhSEsmdYeImhKkR4ZtlStRj/dkI7FSimwKU4miA=; b=K3ZaFhy9EF0/NdHhgf5UOVAi5YpGi3aBFb2MT2hg4n3AgD8dbpHVE2/SX2xUyjSce0 ekxQgVQp5+PfsolDm6FB2UzrM489uhDbO6sJuW0hTmmBNEevKQgptGkbWScBkF5p5zDi ObVdYrrsMThOOigV49a7TKrAthcs9DdcINjMGLo7Pk5ZyjACAGlpCgBDWsHzvATuqNRx l6wfgkedCLIKCkVeFgT39UoIPHckWy2bJkotz8BksiUm+Tbid4EQKUtGusbZOMJq7P1x wO6Z5pewY3imMkFdbED+jhrzVV/qPZKUKZnpy9hBq8x9YNEyqW3FMgXdcCftqXQ39FRx i9KA== MIME-Version: 1.0 Received: by 10.60.20.99 with SMTP id m3mr4280282oee.124.1345823484386; Fri, 24 Aug 2012 08:51:24 -0700 (PDT) Sender: simon@qxnitro.org Received: by 10.76.85.135 with HTTP; Fri, 24 Aug 2012 08:51:24 -0700 (PDT) X-Originating-IP: [2620:0:1040:201:9db5:5be0:5543:2221] In-Reply-To: <20120821120537.GL1202@acme.spoerlein.net> References: <5032AB28.9070306@FreeBSD.org> <20120821120537.GL1202@acme.spoerlein.net> Date: Fri, 24 Aug 2012 16:51:24 +0100 X-Google-Sender-Auth: hLKKXpa--7TtOiRvcrLu1pM1G-U Message-ID: From: "Simon L. B. Nielsen" To: freebsd-security@freebsd.org, freebsd-current@freebsd.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Gm-Message-State: ALoCoQmSXFShyirskc3+7rzuQ2tDtVsYVlnccnataCv2a416KxQiiurXs6kGelL/c0ekd44btI1v Cc: Subject: Re: [HEADSUP] geli(4) weak master key generation on -CURRENT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 24 Aug 2012 15:51:25 -0000 On Tue, Aug 21, 2012 at 1:05 PM, Ulrich Sp=C3=B6rlein wro= te: > On Mon, 2012-08-20 at 22:24:56 +0100, Simon L. B. Nielsen wrote: >> Hello, >> >> If you are not using geli(4) on -CURRENT (AKA FreeBSD 10) you can safely >> ignore this mail. If you are, please read on! >> >> -CURRENT users of geli(4) should be advised that, a geli(4) device may >> have weak master key, if the provider is created on -CURRENT system >> built against source code between r238116 (Jul 4 17:54:17 2012 UTC) >> and r239184 (non-inclusive, Aug 10 18:43:29 2012 UTC). >> >> One can verify if its provider was created with weak keys by running: >> >> # geli dump | grep version >> >> If the version is 7 and the system did not include this fix (r239184) >> when provider was initialized, then the data has to be backed up, >> underlying provider overwritten with random data, system upgraded and >> provider recreated. >> >> Thanks to Fabian Keil for reporting the issue, Pawel Jakub Dawidek for >> fixing it, and Xin Li for drafting this text. >> >> PS. This only affects FreeBSD 10 / -CURRENT, and as -CURRENT isn't >> supported by the FreeBSD Security Team, we are not releasing an >> advisory, just this heads up. > > I haven't read commit mails in a very long time, but is there code in > place that will issue a warning upon geli attach if version 7 is > detected? While -CURRENT is not supported, there might be a lot of disks > initialized with version 7 and they'll eventually be upgraded to > 10.0-RELEASE (the OS, not necessarily the geli volumes). No, the bad code was only in head for about a month. I'm fine with having a warning, but somebody has to code it. --=20 Simon L. B. Nielsen From owner-freebsd-current@FreeBSD.ORG Fri Aug 24 16:02:29 2012 Return-Path: Delivered-To: current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A30AB106564A; Fri, 24 Aug 2012 16:02:29 +0000 (UTC) (envelope-from bapt@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 81CA98FC12; Fri, 24 Aug 2012 16:02:29 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q7OG2TdZ035868; Fri, 24 Aug 2012 16:02:29 GMT (envelope-from bapt@FreeBSD.org) Received: (from bapt@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q7OG2T7R035866; Fri, 24 Aug 2012 16:02:29 GMT (envelope-from bapt@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: bapt set sender to bapt@FreeBSD.org using -f Date: Fri, 24 Aug 2012 18:02:26 +0200 From: Baptiste Daroussin To: Bryan Drewery Message-ID: <20120824160226.GC37867@ithaqua.etoilebsd.net> References: <97612B57-1255-4BB3-A6D3-FC74324C6D67@FreeBSD.org> <20120824081543.GB2998@ithaqua.etoilebsd.net> <50377253.103@FreeBSD.org> <20120824143119.GA37867@ithaqua.etoilebsd.net> <5037A2C6.4060200@shatow.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Pk6IbRAofICFmK5e" Content-Disposition: inline In-Reply-To: <5037A2C6.4060200@shatow.net> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: ports@FreeBSD.org, Steve Wills , current@FreeBSD.org, Alex Dupre Subject: Re: pkgng suggestion: renaming /usr/sbin/pkg to /usr/sbin/pkg-bootstrap X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 24 Aug 2012 16:02:29 -0000 --Pk6IbRAofICFmK5e Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Aug 24, 2012 at 10:50:30AM -0500, Bryan Drewery wrote: > On 8/24/2012 9:31 AM, Baptiste Daroussin wrote: > > On Fri, Aug 24, 2012 at 02:23:47PM +0200, Alex Dupre wrote: > >> Baptiste Daroussin ha scritto: > >> > >>> On of the thing I forgot and kan@ has added is a prompt for the user = in case it > >>> is going to bootstrap. > >> > >> So, removing the prompt will make everybody happy? :-) > >> > >> What about a prompt with timeout? "This is the first time pkg is run, > >> I'll start bootstrapping in 10 seconds. Press CTRL-C now to abort" > >> > >=20 > > Imho the best is to prompt only if not on a tty, otherwise fail, except= if a > > environment variable is set. > >=20 > > regards, > > Bapt > >=20 >=20 > Maybe an ENV variable to auto confirm the prompt too? I'm thinking about > scripts using pkg to bootstrap an entire system install. Maybe I'm on a > TTY and just want it to confirm auto anyway. This is already the case (thanks kan@) >=20 > Bryan --Pk6IbRAofICFmK5e Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEARECAAYFAlA3pZIACgkQ8kTtMUmk6EzHiACgicwu0vyhuSOyRrNDAm0CnTTt GVAAniADTmVjp37RwqAAuYFUQJ9b0UFB =tgk5 -----END PGP SIGNATURE----- --Pk6IbRAofICFmK5e-- From owner-freebsd-current@FreeBSD.ORG Fri Aug 24 16:06:22 2012 Return-Path: Delivered-To: current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0C3C3106568A for ; Fri, 24 Aug 2012 16:06:22 +0000 (UTC) (envelope-from bryan@shatow.net) Received: from secure.xzibition.com (secure.xzibition.com [173.160.118.92]) by mx1.freebsd.org (Postfix) with ESMTP id 7F4DE8FC1A for ; Fri, 24 Aug 2012 16:06:20 +0000 (UTC) DomainKey-Signature: a=rsa-sha1; c=nofws; d=shatow.net; h=message-id :date:from:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; q=dns; s=sweb; b=h2dlJw 8vjO0EoBCEWichfIUGo5FsQJDDhVJpmpBb5VvsoJzmpYlztaO8yi6gJw0X0iZXmY MxNARNqa4th5pbP7iiKdViMAKyKDF0nUJzQKAIEacmNqOyWMQdsx7TQjBSI1k3St gnzVHnF9Csu2fUy8cDgy47KKmRwFyzNwt+HFk= DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=shatow.net; h=message-id :date:from:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; s=sweb; bh=5sDOUO1Wx9J1 /MA+SrePJrNHojx/U81wOUeTPzCarTw=; b=ltikgJazKPBYtSmInaf8L3IV7cov 7aLpHQTQ/kxCIecZ7l46Va6oKflGjBD+f9cJ4ZvUfykCIos5Mj7kbkyoFT9xvITn VzwS1N5KAcxUTOpqbfSDKudKI8/L9kcoftzTisE5mOMmiGs55QI4IN9M1V5l2ZM4 5zCHAAQIXMXKlt4= Received: (qmail 16193 invoked from network); 24 Aug 2012 11:06:18 -0500 Received: from unknown (HELO ?192.168.0.74?) (bryan@shatow.net@74.94.87.209) by sweb.xzibition.com with ESMTPA; 24 Aug 2012 11:06:18 -0500 Message-ID: <5037A693.3020502@shatow.net> Date: Fri, 24 Aug 2012 11:06:43 -0500 From: Bryan Drewery User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0 MIME-Version: 1.0 To: Baptiste Daroussin References: <97612B57-1255-4BB3-A6D3-FC74324C6D67@FreeBSD.org> <20120824081543.GB2998@ithaqua.etoilebsd.net> <50377253.103@FreeBSD.org> <20120824143119.GA37867@ithaqua.etoilebsd.net> <5037A2C6.4060200@shatow.net> <20120824160226.GC37867@ithaqua.etoilebsd.net> In-Reply-To: <20120824160226.GC37867@ithaqua.etoilebsd.net> X-Enigmail-Version: 1.4.3 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: ports@FreeBSD.org, Steve Wills , current@FreeBSD.org, Alex Dupre Subject: Re: pkgng suggestion: renaming /usr/sbin/pkg to /usr/sbin/pkg-bootstrap X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 24 Aug 2012 16:06:22 -0000 On 8/24/2012 11:02 AM, Baptiste Daroussin wrote: > On Fri, Aug 24, 2012 at 10:50:30AM -0500, Bryan Drewery wrote: >> On 8/24/2012 9:31 AM, Baptiste Daroussin wrote: >>> On Fri, Aug 24, 2012 at 02:23:47PM +0200, Alex Dupre wrote: >>>> Baptiste Daroussin ha scritto: >>>> >>>>> On of the thing I forgot and kan@ has added is a prompt for the user in case it >>>>> is going to bootstrap. >>>> >>>> So, removing the prompt will make everybody happy? :-) >>>> >>>> What about a prompt with timeout? "This is the first time pkg is run, >>>> I'll start bootstrapping in 10 seconds. Press CTRL-C now to abort" >>>> >>> >>> Imho the best is to prompt only if not on a tty, otherwise fail, except if a >>> environment variable is set. >>> >>> regards, >>> Bapt >>> >> >> Maybe an ENV variable to auto confirm the prompt too? I'm thinking about >> scripts using pkg to bootstrap an entire system install. Maybe I'm on a >> TTY and just want it to confirm auto anyway. > > This is already the case (thanks kan@) >> Perfect. I see it now, ALWAYS_ASSUME_YES. Bryan From owner-freebsd-current@FreeBSD.ORG Fri Aug 24 16:12:53 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id E60731065670; Fri, 24 Aug 2012 16:12:53 +0000 (UTC) (envelope-from alc@rice.edu) Received: from mh10.mail.rice.edu (mh10.mail.rice.edu [128.42.201.30]) by mx1.freebsd.org (Postfix) with ESMTP id B32DC8FC08; Fri, 24 Aug 2012 16:12:53 +0000 (UTC) Received: from mh10.mail.rice.edu (localhost.localdomain [127.0.0.1]) by mh10.mail.rice.edu (Postfix) with ESMTP id EA0FB604CE; Fri, 24 Aug 2012 11:12:52 -0500 (CDT) Received: from mh10.mail.rice.edu (localhost.localdomain [127.0.0.1]) by mh10.mail.rice.edu (Postfix) with ESMTP id E88C1604C3; Fri, 24 Aug 2012 11:12:52 -0500 (CDT) X-Virus-Scanned: by amavis-2.7.0 at mh10.mail.rice.edu, auth channel Received: from mh10.mail.rice.edu ([127.0.0.1]) by mh10.mail.rice.edu (mh10.mail.rice.edu [127.0.0.1]) (amavis, port 10026) with ESMTP id 8v3oOPhad6cW; Fri, 24 Aug 2012 11:12:52 -0500 (CDT) Received: from adsl-216-63-78-18.dsl.hstntx.swbell.net (adsl-216-63-78-18.dsl.hstntx.swbell.net [216.63.78.18]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) (Authenticated sender: alc) by mh10.mail.rice.edu (Postfix) with ESMTPSA id 834E2603DC; Fri, 24 Aug 2012 11:12:52 -0500 (CDT) Message-ID: <5037A803.6030100@rice.edu> Date: Fri, 24 Aug 2012 11:12:51 -0500 From: Alan Cox User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:8.0) Gecko/20111113 Thunderbird/8.0 MIME-Version: 1.0 To: Luigi Rizzo References: <20120822120105.GA63763@onelab2.iet.unipi.it> <20120823163145.GA3999@onelab2.iet.unipi.it> <50366398.2070700@rice.edu> <20120823174504.GB4820@onelab2.iet.unipi.it> <50371485.1020409@rice.edu> <20120824145708.GA16557@onelab2.iet.unipi.it> In-Reply-To: <20120824145708.GA16557@onelab2.iet.unipi.it> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: alc@freebsd.org, current@freebsd.org Subject: Re: less aggressive contigmalloc ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 24 Aug 2012 16:12:54 -0000 On 08/24/2012 09:57, Luigi Rizzo wrote: > On Fri, Aug 24, 2012 at 12:43:33AM -0500, Alan Cox wrote: >> On 08/23/2012 12:45, Luigi Rizzo wrote: >>> On Thu, Aug 23, 2012 at 12:08:40PM -0500, Alan Cox wrote: >>> ... >>>>> yes i do see that. >>>>> >>>>> Maybe less aggressive with M_NOWAIT but still kills processes. >>>> Are you compiling world with MALLOC_PRODUCTION? The latest version of >>> whatever the default is. But: >>> >>>> jemalloc uses significantly more memory when debugging options are >>>> enabled. This first came up in a thread titled "10-CURRENT and swap >>>> usage" back in June. >>>> >>>> Even at its most aggressive, M_WAITOK, contigmalloc() does not directly >>>> kill processes. If process death coincides with the use of >>>> contigmalloc(), then it is simply the result of earlier, successful >>>> contigmalloc() calls, or for that matter any other physical memory >>>> allocation calls, having depleted the pool of free pages to the point >>>> that the page daemon runs and invokes vm_pageout_oom(). >>> does it mean that those previous allocations relied on memory overbooking ? >> Yes. >> >>> Is there a way to avoid that, then ? >> I believe that malloc()'s default minimum allocation size is 4MB. You >> could reduce that. >> >> Alternatively, you can enable MALLOC_PRODUCTION. > i tried this, and as others mentioned it makes life > better and reduces the problem but contigmalloc still triggers > random process kills. I would be curious to see a stack backtrace when vm_pageout_oom() is called. From owner-freebsd-current@FreeBSD.ORG Fri Aug 24 16:35:18 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6B91B1065738; Fri, 24 Aug 2012 16:35:18 +0000 (UTC) (envelope-from luigi@onelab2.iet.unipi.it) Received: from onelab2.iet.unipi.it (onelab2.iet.unipi.it [131.114.59.238]) by mx1.freebsd.org (Postfix) with ESMTP id 2468A8FC12; Fri, 24 Aug 2012 16:35:18 +0000 (UTC) Received: by onelab2.iet.unipi.it (Postfix, from userid 275) id 6330D7300A; Fri, 24 Aug 2012 18:54:28 +0200 (CEST) Date: Fri, 24 Aug 2012 18:54:28 +0200 From: Luigi Rizzo To: Alan Cox Message-ID: <20120824165428.GA17495@onelab2.iet.unipi.it> References: <20120822120105.GA63763@onelab2.iet.unipi.it> <20120823163145.GA3999@onelab2.iet.unipi.it> <50366398.2070700@rice.edu> <20120823174504.GB4820@onelab2.iet.unipi.it> <50371485.1020409@rice.edu> <20120824145708.GA16557@onelab2.iet.unipi.it> <5037A803.6030100@rice.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5037A803.6030100@rice.edu> User-Agent: Mutt/1.4.2.3i Cc: alc@freebsd.org, current@freebsd.org Subject: Re: less aggressive contigmalloc ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 24 Aug 2012 16:35:18 -0000 On Fri, Aug 24, 2012 at 11:12:51AM -0500, Alan Cox wrote: > On 08/24/2012 09:57, Luigi Rizzo wrote: > >On Fri, Aug 24, 2012 at 12:43:33AM -0500, Alan Cox wrote: > >>On 08/23/2012 12:45, Luigi Rizzo wrote: > >>>On Thu, Aug 23, 2012 at 12:08:40PM -0500, Alan Cox wrote: > >>>... > >>>>>yes i do see that. > >>>>> > >>>>>Maybe less aggressive with M_NOWAIT but still kills processes. > >>>>Are you compiling world with MALLOC_PRODUCTION? The latest version of > >>>whatever the default is. But: > >>> > >>>>jemalloc uses significantly more memory when debugging options are > >>>>enabled. This first came up in a thread titled "10-CURRENT and swap > >>>>usage" back in June. > >>>> > >>>>Even at its most aggressive, M_WAITOK, contigmalloc() does not directly > >>>>kill processes. If process death coincides with the use of > >>>>contigmalloc(), then it is simply the result of earlier, successful > >>>>contigmalloc() calls, or for that matter any other physical memory > >>>>allocation calls, having depleted the pool of free pages to the point > >>>>that the page daemon runs and invokes vm_pageout_oom(). > >>>does it mean that those previous allocations relied on memory > >>>overbooking ? > >>Yes. > >> > >>>Is there a way to avoid that, then ? > >>I believe that malloc()'s default minimum allocation size is 4MB. You > >>could reduce that. > >> > >>Alternatively, you can enable MALLOC_PRODUCTION. > >i tried this, and as others mentioned it makes life > >better and reduces the problem but contigmalloc still triggers > >random process kills. > > I would be curious to see a stack backtrace when vm_pageout_oom() is called. you mean a backtrace of the process(es) that get killed ? I'll see if i manage to generate something, not easy because this is a picobsd image and there is barely anything available. I am trying to see if i can remove the memory overcommit, but limited success so far. I have built a kernel with "options NO_SWAPPING" but while it makes vm.swap_enabled: 0 i still see vm.swap_reserved grow beyond available RAM size. As an example, on a VM with 128MB of RAM, of which about 28M used for a MFS root filesystem, i get the following. vm.vmtotal: System wide totals computed every five seconds: (values in kilobytes) =============================================== Processes: (RUNQ: 1 Disk Wait: 1 Page Wait: 0 Sleep: 9) Virtual Memory: (Total: 1074551344K Active: 738328K) Real Memory: (Total: 17208K Active: 13368K) Shared Virtual Memory: (Total: 7788K Active: 7788K) Shared Real Memory: (Total: 5024K Active: 5024K) Free Memory: 68160K # sysctl vm | grep swap vm.swap_enabled: 0 vm.nswapdev: 0 vm.swap_async_max: 4 vm.swap_reserved: 149917696 <--- varies from ~140795904 to 160e6 and up vm.swap_total: 0 vm.stats.vm.v_swappgsout: 0 vm.stats.vm.v_swappgsin: 0 vm.stats.vm.v_swapout: 0 vm.stats.vm.v_swapin: 0 vm.disable_swapspace_pageouts: 0 vm.defer_swapspace_pageouts: 0 vm.swap_idle_enabled: 0 vm.overcommit: 0 -------------- cheers luigi From owner-freebsd-current@FreeBSD.ORG Fri Aug 24 16:56:08 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id DAD8C1065670; Fri, 24 Aug 2012 16:56:08 +0000 (UTC) (envelope-from alc@rice.edu) Received: from mh10.mail.rice.edu (mh10.mail.rice.edu [128.42.201.30]) by mx1.freebsd.org (Postfix) with ESMTP id A72008FC14; Fri, 24 Aug 2012 16:56:08 +0000 (UTC) Received: from mh10.mail.rice.edu (localhost.localdomain [127.0.0.1]) by mh10.mail.rice.edu (Postfix) with ESMTP id 2695060502; Fri, 24 Aug 2012 11:56:08 -0500 (CDT) Received: from mh10.mail.rice.edu (localhost.localdomain [127.0.0.1]) by mh10.mail.rice.edu (Postfix) with ESMTP id 25150604EB; Fri, 24 Aug 2012 11:56:08 -0500 (CDT) X-Virus-Scanned: by amavis-2.7.0 at mh10.mail.rice.edu, auth channel Received: from mh10.mail.rice.edu ([127.0.0.1]) by mh10.mail.rice.edu (mh10.mail.rice.edu [127.0.0.1]) (amavis, port 10026) with ESMTP id LSSo-lDGt7QB; Fri, 24 Aug 2012 11:56:08 -0500 (CDT) Received: from adsl-216-63-78-18.dsl.hstntx.swbell.net (adsl-216-63-78-18.dsl.hstntx.swbell.net [216.63.78.18]) (using TLSv1 with cipher RC4-MD5 (128/128 bits)) (No client certificate requested) (Authenticated sender: alc) by mh10.mail.rice.edu (Postfix) with ESMTPSA id B48EC604FC; Fri, 24 Aug 2012 11:56:07 -0500 (CDT) Message-ID: <5037B226.3000103@rice.edu> Date: Fri, 24 Aug 2012 11:56:06 -0500 From: Alan Cox User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:8.0) Gecko/20111113 Thunderbird/8.0 MIME-Version: 1.0 To: Luigi Rizzo References: <20120822120105.GA63763@onelab2.iet.unipi.it> <20120823163145.GA3999@onelab2.iet.unipi.it> <50366398.2070700@rice.edu> <20120823174504.GB4820@onelab2.iet.unipi.it> <50371485.1020409@rice.edu> <20120824145708.GA16557@onelab2.iet.unipi.it> <5037A803.6030100@rice.edu> <20120824165428.GA17495@onelab2.iet.unipi.it> In-Reply-To: <20120824165428.GA17495@onelab2.iet.unipi.it> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: alc@freebsd.org, current@freebsd.org Subject: Re: less aggressive contigmalloc ? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 24 Aug 2012 16:56:08 -0000 On 08/24/2012 11:54, Luigi Rizzo wrote: > On Fri, Aug 24, 2012 at 11:12:51AM -0500, Alan Cox wrote: >> On 08/24/2012 09:57, Luigi Rizzo wrote: >>> On Fri, Aug 24, 2012 at 12:43:33AM -0500, Alan Cox wrote: >>>> On 08/23/2012 12:45, Luigi Rizzo wrote: >>>>> On Thu, Aug 23, 2012 at 12:08:40PM -0500, Alan Cox wrote: >>>>> ... >>>>>>> yes i do see that. >>>>>>> >>>>>>> Maybe less aggressive with M_NOWAIT but still kills processes. >>>>>> Are you compiling world with MALLOC_PRODUCTION? The latest version of >>>>> whatever the default is. But: >>>>> >>>>>> jemalloc uses significantly more memory when debugging options are >>>>>> enabled. This first came up in a thread titled "10-CURRENT and swap >>>>>> usage" back in June. >>>>>> >>>>>> Even at its most aggressive, M_WAITOK, contigmalloc() does not directly >>>>>> kill processes. If process death coincides with the use of >>>>>> contigmalloc(), then it is simply the result of earlier, successful >>>>>> contigmalloc() calls, or for that matter any other physical memory >>>>>> allocation calls, having depleted the pool of free pages to the point >>>>>> that the page daemon runs and invokes vm_pageout_oom(). >>>>> does it mean that those previous allocations relied on memory >>>>> overbooking ? >>>> Yes. >>>> >>>>> Is there a way to avoid that, then ? >>>> I believe that malloc()'s default minimum allocation size is 4MB. You >>>> could reduce that. >>>> >>>> Alternatively, you can enable MALLOC_PRODUCTION. >>> i tried this, and as others mentioned it makes life >>> better and reduces the problem but contigmalloc still triggers >>> random process kills. >> I would be curious to see a stack backtrace when vm_pageout_oom() is called. > you mean a backtrace of the process(es) that get killed ? No, a backtrace showing who called vm_pageout_oom(). Simply add a kdb_backtrace() call at the start of vm_pageout_oom(). There are two possibilities. I want to know which it is. From owner-freebsd-current@FreeBSD.ORG Fri Aug 24 21:57:53 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx2.freebsd.org (mx2.freebsd.org [IPv6:2001:4f8:fff6::35]) by hub.freebsd.org (Postfix) with ESMTP id 14679106566B; Fri, 24 Aug 2012 21:57:53 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from [127.0.0.1] (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id 4581914DAB9; Fri, 24 Aug 2012 21:57:17 +0000 (UTC) Message-ID: <5037F8BB.9020501@FreeBSD.org> Date: Fri, 24 Aug 2012 14:57:15 -0700 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:14.0) Gecko/20120713 Thunderbird/14.0 MIME-Version: 1.0 To: Eitan Adler References: <97612B57-1255-4BB3-A6D3-FC74324C6D67@FreeBSD.org> <785B5BAD-E015-4624-B3A1-D05E1BD97E51@freebsd.org> <5AC662AA-4874-4BC2-9862-65518B79B840@freebsd.org> <5036EE2E.4040606@FreeBSD.org> In-Reply-To: X-Enigmail-Version: 1.4.3 OpenPGP: id=1A1ABC84 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: ports@freebsd.org, Steve Wills , Baptiste Daroussin , current@freebsd.org Subject: Re: pkgng suggestion: renaming /usr/sbin/pkg to /usr/sbin/pkg-bootstrap X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 24 Aug 2012 21:57:53 -0000 On 8/23/2012 8:03 PM, Eitan Adler wrote: > On 23 August 2012 22:59, Doug Barton wrote: >> I tend to agree with Steve here ... we can't be responsible for other >> people's poorly written docs. > > This isn't about poorly written docs. This is the user expecting a > tool to exist, which doesn't. Take another example of a sysadmin which > rarely installs new systems, installs FreeBSD for the third time, and > then gets confused when "pkg install vim" fails. Aren't we going to install the pkg package on new systems when they are installed? Isn't that (shouldn't that be?) part of the project plan? It would be insane for us not to do that, at least for the releases where pkg is the default. >> You bring up a valid point that we should >> keep in mind for our own however. The bootstrapping issue will be the >> smallest possible annoyance on a long road of the migration process. > > The bootstrapping issue is a factor even after the migration :) I think that the point I'm trying to make is that it shouldn't be. > note that I'm not talking about the mechanism here, I'm trying to > avoid "pkg doesn't seem to be installed on my fresh system" becoming a > FAQ. The way that we avoid that problem is not to create it for ourselves in the first place. :) The role of pkg-bootstrap is for those users who have already-installed systems that need to do the conversion, or if somehow pkg becomes corrupted on the user's system and needs to be reinstalled. That's it. I like that you're thinking through the related issues, but in this particular case I think you're overthinking it. Doug -- I am only one, but I am one. I cannot do everything, but I can do something. And I will not let what I cannot do interfere with what I can do. -- Edward Everett Hale, (1822 - 1909) From owner-freebsd-current@FreeBSD.ORG Fri Aug 24 22:38:38 2012 Return-Path: Delivered-To: current@FreeBSD.org Received: from mx2.freebsd.org (mx2.freebsd.org [IPv6:2001:4f8:fff6::35]) by hub.freebsd.org (Postfix) with ESMTP id A2BA41065675; Fri, 24 Aug 2012 22:38:38 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from [127.0.0.1] (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id DD7CC14DC29; Fri, 24 Aug 2012 22:38:35 +0000 (UTC) Message-ID: <50380269.6020003@FreeBSD.org> Date: Fri, 24 Aug 2012 15:38:33 -0700 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:14.0) Gecko/20120713 Thunderbird/14.0 MIME-Version: 1.0 To: Baptiste Daroussin References: <97612B57-1255-4BB3-A6D3-FC74324C6D67@FreeBSD.org> <20120824081543.GB2998@ithaqua.etoilebsd.net> In-Reply-To: <20120824081543.GB2998@ithaqua.etoilebsd.net> X-Enigmail-Version: 1.4.3 OpenPGP: id=1A1ABC84 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: ports@FreeBSD.org, Steve Wills , current@FreeBSD.org Subject: Re: pkgng suggestion: renaming /usr/sbin/pkg to /usr/sbin/pkg-bootstrap X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 24 Aug 2012 22:38:38 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 8/24/2012 1:15 AM, Baptiste Daroussin wrote: > BTW for people who haven't tested and want to share their opinion, > here is how work /usr/sbin/pkg: > > it first checks if ${LOCALBASE}/sbin/pkg is there - if yes it > directly execute ${LOCALBASE}/sbin/pkg with arguments passed to > /usr/sbin/pkg As others have already pointed out, this is a bad idea for a variety of reasons, not the least of which is security related. It also removes one of the primary benefits of pkg, that it be (fully) hosted in the ports tree. The bootstrap procedure does not need to be simple or transparent because it's only going to exist for a very short period while users are bringing pkg into already-installed systems where pkg is not already the default; and they don't have an existing ports tree. The way that you solve the bootstrap problem for systems where pkg IS the default is to install the pkg package at system install time. Let me rephrase that more simply ... very few users are ever going to need the bootstrapping tool that will be in the base. Making it mandatory for *every* user is therefore not only a bad idea, it's contrary to one of the primary goals of the project. Doug - -- I am only one, but I am one. I cannot do everything, but I can do something. And I will not let what I cannot do interfere with what I can do. -- Edward Everett Hale, (1822 - 1909) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (MingW32) iQEcBAEBCAAGBQJQOAJpAAoJEFzGhvEaGryEY2QH/2Hv+cW20htODBTrFNScd7qS NxBc7YHr3ddoyoui+Qwtl3ErjMOJr+kA3nRSsZ5ewGN5HVQ4gCAWp76bJn75BM71 q2Qmgx7HCnBMJKrmRTvDAA1nJcTKAgXFKK8hYQgiTOhWFaIjJxhDlln5llFcXwBa VN0ErF421FkD8oyHpcQLga1BHLtldOL5itt/4Tp9cKaC5l2P9dBNbyCTxVa4XBiZ tsK+x7XJqwj0NvXLk+b3icLIEeyopa3TJAoAtXZ27igg65norCoh2EPo7aJqP2zY T75PKdbRJprwCpeJXulC02oZu/UERoIMLeaH1JbCZRcLAqaCJQuEGSP95as3hSY= =BEya -----END PGP SIGNATURE----- From owner-freebsd-current@FreeBSD.ORG Sat Aug 25 00:01:53 2012 Return-Path: Delivered-To: current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id F31C51065670; Sat, 25 Aug 2012 00:01:52 +0000 (UTC) (envelope-from bapt@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id B9A248FC08; Sat, 25 Aug 2012 00:01:52 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q7P01qZh091367; Sat, 25 Aug 2012 00:01:52 GMT (envelope-from bapt@FreeBSD.org) Received: (from bapt@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q7P01qTP091366; Sat, 25 Aug 2012 00:01:52 GMT (envelope-from bapt@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: bapt set sender to bapt@FreeBSD.org using -f Date: Sat, 25 Aug 2012 02:01:48 +0200 From: Baptiste Daroussin To: Doug Barton Message-ID: <20120825000148.GF37867@ithaqua.etoilebsd.net> References: <97612B57-1255-4BB3-A6D3-FC74324C6D67@FreeBSD.org> <20120824081543.GB2998@ithaqua.etoilebsd.net> <50380269.6020003@FreeBSD.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="hK8Uo4Yp55NZU70L" Content-Disposition: inline In-Reply-To: <50380269.6020003@FreeBSD.org> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: ports@FreeBSD.org, Steve Wills , current@FreeBSD.org Subject: Re: pkgng suggestion: renaming /usr/sbin/pkg to /usr/sbin/pkg-bootstrap X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 25 Aug 2012 00:01:53 -0000 --hK8Uo4Yp55NZU70L Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Aug 24, 2012 at 03:38:33PM -0700, Doug Barton wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA256 >=20 > On 8/24/2012 1:15 AM, Baptiste Daroussin wrote: > > BTW for people who haven't tested and want to share their opinion, > > here is how work /usr/sbin/pkg: > >=20 > > it first checks if ${LOCALBASE}/sbin/pkg is there - if yes it > > directly execute ${LOCALBASE}/sbin/pkg with arguments passed to > > /usr/sbin/pkg >=20 > As others have already pointed out, this is a bad idea for a variety > of reasons, not the least of which is security related. It also > removes one of the primary benefits of pkg, that it be (fully) hosted > in the ports tree. Can anyone give me he details on the security related problem? Can I also have the details on why it would remove the benefits of being fu= lly hosted in the ports, I have no plan to remove it, currently the ports tree = is also able to bootstrap itself pkg without needing /usr/sbin/pkg. the bootstrap tool is currently just a transparent way to bootstrap pkgng, = it is not mandatory at all, one can leave without it, and it doesn't prevent pkgn= g to fully leave in the ports tree? What do I miss here? Once again I'm not opposed at all to remove it in favour of pkg-bootstrap, = but it currently seems to lacks a bit of detailed arguments. > Let me rephrase that more simply ... very few users are ever going to > need the bootstrapping tool that will be in the base. Making it > mandatory for *every* user is therefore not only a bad idea, it's > contrary to one of the primary goals of the project. >=20 Why would it be mandatory? it is just a transparent kind of helper tool regards, Bapt --hK8Uo4Yp55NZU70L Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEARECAAYFAlA4FewACgkQ8kTtMUmk6EzFnACgvvOVzgLNzx51yzdtlqvX063X K6MAni8S6ev9t5CuWLs76Glyk5BiqaPF =TJIn -----END PGP SIGNATURE----- --hK8Uo4Yp55NZU70L-- From owner-freebsd-current@FreeBSD.ORG Sat Aug 25 00:10:38 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id AD419106564A for ; Sat, 25 Aug 2012 00:10:38 +0000 (UTC) (envelope-from bounces+73574-dfb6-freebsd-current=freebsd.org@sendgrid.me) Received: from o3.shared.sendgrid.net (o3.shared.sendgrid.net [208.117.48.85]) by mx1.freebsd.org (Postfix) with SMTP id 50A8E8FC15 for ; Sat, 25 Aug 2012 00:10:37 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sendgrid.info; h= message-id:date:from:mime-version:to:cc:subject:references :in-reply-to:content-type:content-transfer-encoding; s=smtpapi; bh=m9d/6ER/aud4RdznOPWPYffXPyE=; b=RNG4vGaKObvfQX3oXkS6lT4+C6lb CJwvRt8+AREVdoTUoYf/mvzuw7iMZqWaeK8KSr0RhTFg4PGURTlYejFGwOcZIUzK jRjAMhtfEzIRCTz02/NzDdPsx8GVDHoe0lHWJpznX5bzKUvCDArIBgmZmL4XPxV/ 6AzuY2avFws1BQ4= Received: by 10.4.35.250 with SMTP id mf55.28113.503817FD3 Fri, 24 Aug 2012 19:10:37 -0500 (CDT) Received: from mail.tarsnap.com (unknown [10.41.44.5]) by mi20 (SG) with ESMTP id 503817fd.761a.2d1ed89 for ; Fri, 24 Aug 2012 19:10:37 -0500 (CST) Received: (qmail 7267 invoked from network); 25 Aug 2012 00:10:36 -0000 Received: from unknown (HELO clamshell.daemonology.net) (127.0.0.1) by ec2-107-20-205-189.compute-1.amazonaws.com with ESMTP; 25 Aug 2012 00:10:36 -0000 Received: (qmail 38522 invoked from network); 25 Aug 2012 00:10:01 -0000 Received: from unknown (HELO clamshell.daemonology.net) (127.0.0.1) by clamshell.daemonology.net with SMTP; 25 Aug 2012 00:10:01 -0000 Message-ID: <503817D9.3070006@freebsd.org> Date: Fri, 24 Aug 2012 17:10:01 -0700 From: Colin Percival User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:14.0) Gecko/20120731 Thunderbird/14.0 MIME-Version: 1.0 To: John Baldwin References: <502831B7.1080309@freebsd.org> <201208240748.19737.jhb@freebsd.org> <866288laq0.fsf@ds4.des.no> <201208241013.48805.jhb@freebsd.org> In-Reply-To: <201208241013.48805.jhb@freebsd.org> X-Enigmail-Version: 1.4.3 Content-Type: text/plain; charset=UTF-8 content-transfer-encoding: quoted-printable X-Sendgrid-EID: XhyBwObMhraAR+zdwMupjQ6BIqbhdEfc+6p+uBxS7S9KLomxXxSYkRSDZk/EixPQ+rialnK7iSV4kdm/aZrj7zejpTcS58nMXoMCjIdHUCnyrePMVsg82pzUOZlRyW517V4OVbws+hTOqUnzfEFEtUJYyGjVojrCGgyzLvopIl4= Cc: alc@freebsd.org, =?UTF-8?B?RGFnLUVybGluZyBTbcO4cmdyYXY=?= , freebsd-current@freebsd.org Subject: Re: Time to bump default VM_SWZONE_SIZE_MAX? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 25 Aug 2012 00:10:38 -0000 On 08/24/12 07:13, John Baldwin wrote:=0D > On Friday, August 24, 2012 8:45:43 am Dag-Erling Sm=C3=B8rgrav wrote:=0D >> John Baldwin writes:=0D >>> Note that on i386 you can't get more than 4GB of RAM without PAE, and i= f you=0D >>> have any modern x86 box with > 4GB of RAM, you are most likely running = amd64=0D >>> on it, not i386. I think i386 would be fine to just keep the limit it = had.=0D >>=0D >> The limit we had was insufficient for 8 GB of swap.=0D > =0D > In absolute or practical terms? Not all swap blocks are fully utilized. = At=0D > Y! the install script we used would compute the maximum theoretical swap = zone=0D > needed and then cut it in half, and this worked quite well. Also, keep i= n mind,=0D > this is for i386, not amd64. At this point i386 is going to be used on s= maller=0D > systems (e.g. netbooks, etc.), not servers that have lots of swap.=0D =0D I'd like to see i386 bumped slightly, just so that the rule of "allocate sw= ap=0D space equal to max(RAM, min(2*RAM, 8 GB))" (which I've seen in lots of plac= es)=0D is more likely to be safe. If I'm understanding things correctly, bumping = from=0D 32 MB up to 34.5 MB should give us a theoretical 16 GiB or a "safe" 8 GiB l= imit=0D on swap usage (2^17 structures which are 276 bytes each on i386).=0D =0D But I agree that the real issue was with amd64, not i386.=0D =0D -- =0D Colin Percival=0D Security Officer Emeritus, FreeBSD | The power to serve=0D Founder, Tarsnap | www.tarsnap.com | Online backups for the truly paranoid= =0D From owner-freebsd-current@FreeBSD.ORG Sat Aug 25 00:33:53 2012 Return-Path: Delivered-To: current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2A045106564A; Sat, 25 Aug 2012 00:33:53 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from onyx.glenbarber.us (onyx.glenbarber.us [IPv6:2607:fc50:1000:c200::face]) by mx1.freebsd.org (Postfix) with ESMTP id E525D8FC15; Sat, 25 Aug 2012 00:33:52 +0000 (UTC) Received: from glenbarber.us (unknown [IPv6:2001:470:8:1205:2:2:0:24]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: gjb) by onyx.glenbarber.us (Postfix) with ESMTPSA id 4570F23F641; Fri, 24 Aug 2012 20:33:51 -0400 (EDT) Date: Fri, 24 Aug 2012 20:33:47 -0400 From: Glen Barber To: Jonathan Anderson Message-ID: <20120825003346.GA1345@glenbarber.us> References: <97612B57-1255-4BB3-A6D3-FC74324C6D67@FreeBSD.org> <20120824081543.GB2998@ithaqua.etoilebsd.net> <50380269.6020003@FreeBSD.org> <67BB0A66-A9D2-4257-A91E-C249B8076A87@gmail.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="2oS5YaxWCcQjTEyO" Content-Disposition: inline In-Reply-To: <67BB0A66-A9D2-4257-A91E-C249B8076A87@gmail.com> X-Operating-System: FreeBSD 10.0-CURRENT amd64 User-Agent: Mutt/1.5.21 (2010-09-15) Cc: ports@FreeBSD.org, Steve Wills , Baptiste Daroussin , Doug Barton , current@FreeBSD.org Subject: Re: pkgng suggestion: renaming /usr/sbin/pkg to /usr/sbin/pkg-bootstrap X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 25 Aug 2012 00:33:53 -0000 --2oS5YaxWCcQjTEyO Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Aug 25, 2012 at 01:25:15AM +0100, Jonathan Anderson wrote: > On 24 Aug 2012, at 23:38, Doug Barton wrote: > > Let me rephrase that more simply ... very few users are ever going to > > need the bootstrapping tool that will be in the base. >=20 So, then they won't use it. I fail to see the problem here. > But surely the whole point of pkgng is that people *will* use pkg > as the default method of acquiring third-party software, so they'll > want to "pkg install foo" and have it Just Work. To say either "you > must download the ports tree in order to use binary packages" or > "you must use pkg_add to install pkg" seems to miss the point... >=20 /usr/sbin/pkg installs /usr/local/sbin/pkg without requiring the Ports Collection to be available locally. Glen --2oS5YaxWCcQjTEyO Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iQEcBAEBCAAGBQJQOB1qAAoJEFJPDDeguUajsFEH/j8vvdEx/IVKukZ5/SX/CKTS ZXUvrGdtktWztHSSHicXdKp2Id0JErXv+BikdOftRst4FP2PPZd/N+1UNrlJ42sb 4rSrYxkKVf0ooQTwrfVlETfb5bAdtXZLNUCiNu/WFh/jbCpOgkkuwFr49HUhZCHg 4VL1/wsgYaVkcVNIDscIsKYRNImHosLem4kxKiht60P8SUsOQ07cWFU7olo/QEHw E/b5gW/4TUnWsJpxZH0Xheh5mxw7eJ6l8XbKemdZmtYdq01VrygOI1WR7UgtxYf0 +64ZMf0Zv45opV8Ov7+ArHn0NVBTGe0tUas5cmwvUnsMe2b4xVpoX+VH6JRSBUA= =2fL9 -----END PGP SIGNATURE----- --2oS5YaxWCcQjTEyO-- From owner-freebsd-current@FreeBSD.ORG Sat Aug 25 01:01:00 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 48C64106564A; Sat, 25 Aug 2012 01:01:00 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from onyx.glenbarber.us (onyx.glenbarber.us [IPv6:2607:fc50:1000:c200::face]) by mx1.freebsd.org (Postfix) with ESMTP id 1A32D8FC0A; Sat, 25 Aug 2012 01:01:00 +0000 (UTC) Received: from glenbarber.us (unknown [IPv6:2001:470:8:1205:2:2:0:24]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: gjb) by onyx.glenbarber.us (Postfix) with ESMTPSA id 6C62823F641; Fri, 24 Aug 2012 21:00:57 -0400 (EDT) Date: Fri, 24 Aug 2012 21:00:54 -0400 From: Glen Barber To: Jonathan Anderson Message-ID: <20120825010054.GB1345@glenbarber.us> References: <97612B57-1255-4BB3-A6D3-FC74324C6D67@FreeBSD.org> <20120824081543.GB2998@ithaqua.etoilebsd.net> <50380269.6020003@FreeBSD.org> <67BB0A66-A9D2-4257-A91E-C249B8076A87@gmail.com> <20120825003346.GA1345@glenbarber.us> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="LpQ9ahxlCli8rRTG" Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD 10.0-CURRENT amd64 User-Agent: Mutt/1.5.21 (2010-09-15) Cc: ports@freebsd.org, Steve Wills , Baptiste Daroussin , Doug Barton , current@freebsd.org Subject: Re: pkgng suggestion: renaming /usr/sbin/pkg to /usr/sbin/pkg-bootstrap X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 25 Aug 2012 01:01:00 -0000 --LpQ9ahxlCli8rRTG Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Aug 25, 2012 at 01:47:26AM +0100, Jonathan Anderson wrote: > On Saturday, 25 August 2012 at 01:33, Glen Barber wrote: > > On Sat, Aug 25, 2012 at 01:25:15AM +0100, Jonathan Anderson wrote: > > > On 24 Aug 2012, at 23:38, Doug Barton wrote: > > > > Let me rephrase that more simply ... very few users are ever going = to > > > > need the bootstrapping tool that will be in the base. > > >=20 > >=20 > >=20 > > So, then they won't use it. I fail to see the problem here. >=20 > I also fail to see the problem. :) Just to be clear, my post was > arguing against Doug's assertion that few will use pkg's bootstrapper > (and that this is a problem): I hope that pkgng and package sets > will vastly increase the use of binary packages by FreeBSD consumers. > =20 I was avoiding writing two separate emails about this thread - yes, I did realize we had a similar point of view on this. Sorry if it came out differently. > > /usr/sbin/pkg installs /usr/local/sbin/pkg without requiring the Ports > > Collection to be available locally. >=20 > Which is exactly the behaviour that I want: I view the ports tree > as a last resort to be used only if binary packages fail to fulfil > my needs. Sometimes I don't even bother fetching it. Once again, > we may be in violent agreement here. :) >=20 Understood. I misinterpreted your last sentence. What I would like to know, is why all the anti-progress emails[1] have to wait until the Last Minute(tm) when information on pkgng availability has been available for quite some time now. Welcome to 2012. [1] - Doing the same things we've done keeps us in the same place we've been. Glen --LpQ9ahxlCli8rRTG Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iQEcBAEBCAAGBQJQOCPGAAoJEFJPDDeguUajGhoIALYeuhge8MCmhZ2KwhNBxwvi sNBcE25EtIPkNTe/ikUZ5gRa1tp1LeLXCiPO/yetbsXNlq22m1VmxA/L/vg+Wp2B lku5V97gHSyiJseZdFZx0ZK2EKglM7NbIrLOOKBPK9AtqSqF5Bp+Dpp6niElET+S 6KuEBOuigDKybiDMu8is8/SLiJe9aa0Sf3GPvSDVWcXKoXtE3gnQ6Y4JxsOfA6tn 8oI4GteORJFTrj8zPP6ArifnoWZ9e9bgIrwjdbzkkHotjAykk7e53R+Qu3tD7l7D HGzl/sHFDGBPaI6ewIEuyDVB7svbtETbZSsoxRrPUZ6P+iE03HsR2NU9pcHYgn8= =013n -----END PGP SIGNATURE----- --LpQ9ahxlCli8rRTG-- From owner-freebsd-current@FreeBSD.ORG Sat Aug 25 00:25:19 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 24867106566C; Sat, 25 Aug 2012 00:25:19 +0000 (UTC) (envelope-from jonathan.robert.anderson@gmail.com) Received: from mail-wi0-f172.google.com (mail-wi0-f172.google.com [209.85.212.172]) by mx1.freebsd.org (Postfix) with ESMTP id 0C7568FC12; Sat, 25 Aug 2012 00:25:17 +0000 (UTC) Received: by wicr5 with SMTP id r5so1201904wic.13 for ; Fri, 24 Aug 2012 17:25:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to:x-mailer; bh=5m2kiqw8dgN/bnTmDUtx9XpOQka1Gm6vfhWBqOxJ7N0=; b=o3UFL+mxc88PEE8Fh3EeCKLOVshT+UoGC7cEsV0eSqKyie9mY6xqNt7UN5TkNrf7m9 2NjK4WEZ19xye/J4aQ7uHr8OxT/k1GPnXG17V5clJDBA4J66UvSywQcxhI6etFJHS+DY unEIEoJCh7QW2nsuasgQXPqp9Y2ZmrUpBvxDmBayYoQZP5ST5vdN5f2qe5PZPbsGLtBi v2ZyeH0RUrQmeMyS50MflYFZNJ8EBwtf8xCoi5F44rxD1glRdv76Rp4xsSeYvfznuwO4 ZRY68mMWrIEO2zLkSIzfg/Hg3rMBL+I5w0Kp7bO6CGiONONe5Dh70+f6Mo3vhFLRza3s 8tzA== Received: by 10.216.207.167 with SMTP id n39mr3819489weo.23.1345854317099; Fri, 24 Aug 2012 17:25:17 -0700 (PDT) Received: from [192.168.0.2] (cpc2-cmbg15-2-0-cust323.5-4.cable.virginmedia.com. [86.26.13.68]) by mx.google.com with ESMTPS id o2sm1855613wiz.11.2012.08.24.17.25.15 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 24 Aug 2012 17:25:16 -0700 (PDT) Mime-Version: 1.0 (Mac OS X Mail 6.0 \(1485\)) From: Jonathan Anderson In-Reply-To: <50380269.6020003@FreeBSD.org> Date: Sat, 25 Aug 2012 01:25:15 +0100 Message-Id: <67BB0A66-A9D2-4257-A91E-C249B8076A87@gmail.com> References: <97612B57-1255-4BB3-A6D3-FC74324C6D67@FreeBSD.org> <20120824081543.GB2998@ithaqua.etoilebsd.net> <50380269.6020003@FreeBSD.org> To: Doug Barton X-Mailer: Apple Mail (2.1485) X-Mailman-Approved-At: Sat, 25 Aug 2012 01:24:31 +0000 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: ports@FreeBSD.org, Steve Wills , Baptiste Daroussin , current@FreeBSD.org Subject: Re: pkgng suggestion: renaming /usr/sbin/pkg to /usr/sbin/pkg-bootstrap X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 25 Aug 2012 00:25:19 -0000 On 24 Aug 2012, at 23:38, Doug Barton wrote: > Let me rephrase that more simply ... very few users are ever going to > need the bootstrapping tool that will be in the base. But surely the whole point of pkgng is that people *will* use pkg as the = default method of acquiring third-party software, so they'll want to = "pkg install foo" and have it Just Work. To say either "you must = download the ports tree in order to use binary packages" or "you must = use pkg_add to install pkg" seems to miss the point... Jon -- Jonathan Anderson jonathan@FreeBSD.org http://freebsd.org/~jonathan/= From owner-freebsd-current@FreeBSD.ORG Sat Aug 25 01:36:23 2012 Return-Path: Delivered-To: current@FreeBSD.org Received: from mx2.freebsd.org (mx2.freebsd.org [69.147.83.53]) by hub.freebsd.org (Postfix) with ESMTP id 7634D106564A; Sat, 25 Aug 2012 01:36:23 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from [127.0.0.1] (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id 3103A14D94D; Sat, 25 Aug 2012 01:36:23 +0000 (UTC) Message-ID: <50382C15.5050209@FreeBSD.org> Date: Fri, 24 Aug 2012 18:36:21 -0700 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:14.0) Gecko/20120713 Thunderbird/14.0 MIME-Version: 1.0 To: Glen Barber References: <97612B57-1255-4BB3-A6D3-FC74324C6D67@FreeBSD.org> <20120824081543.GB2998@ithaqua.etoilebsd.net> <50380269.6020003@FreeBSD.org> <67BB0A66-A9D2-4257-A91E-C249B8076A87@gmail.com> <20120825003346.GA1345@glenbarber.us> In-Reply-To: <20120825003346.GA1345@glenbarber.us> X-Enigmail-Version: 1.4.3 OpenPGP: id=1A1ABC84 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Jonathan Anderson , ports@FreeBSD.org, Baptiste Daroussin , current@FreeBSD.org, Steve Wills Subject: Re: pkgng suggestion: renaming /usr/sbin/pkg to /usr/sbin/pkg-bootstrap X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 25 Aug 2012 01:36:23 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 8/24/2012 5:33 PM, Glen Barber wrote: > On Sat, Aug 25, 2012 at 01:25:15AM +0100, Jonathan Anderson wrote: >> On 24 Aug 2012, at 23:38, Doug Barton wrote: >>> Let me rephrase that more simply ... very few users are ever going to >>> need the bootstrapping tool that will be in the base. >> > > So, then they won't use it. I fail to see the problem here. That's because you're not paying attention. :) Which comes first in your PATH, /usr/sbin, or /usr/local/sbin? Which comes first in the default PATH? What Baptiste said is that the way /usr/sbin/pkg works is to take arguments handed to it and pass them through to /usr/local/sbin/pkg. That means that every user who has their PATH configured in the default manner (which is what every security text on Unix has recommended for 30 years) will be using /usr/sbin/pkg every time they type the pkg command. >> But surely the whole point of pkgng is that people *will* use pkg >> as the default method of acquiring third-party software, so they'll >> want to "pkg install foo" and have it Just Work. To say either "you >> must download the ports tree in order to use binary packages" or >> "you must use pkg_add to install pkg" seems to miss the point... >> > > /usr/sbin/pkg installs /usr/local/sbin/pkg without requiring the Ports > Collection to be available locally. It does much more than that. Go read the code. As to the security related problems, they should be obvious. Having 1 binary that is always executed to pass arguments to another binary at minimum doubles your attack surface. Given what /usr/sbin/pkg does, it more than doubles it. Not to mention the flat out wrong-headed design of having a binary that will be run as root whose primary purpose is to pass arguments to another binary. The reason this defeats the purpose of putting pkg in the ports tree is that if there is a bug in /usr/sbin/pkg (which of course, there will be) then it has to be fixed in the base, with all of the consequent drama and delays that this will entail. If there is a bug in /usr/local/bin/pkg, it gets fixed in the ports tree and instantly updated, which is part of the virtue of having it in the ports tree in the first place. Given that if we do the rollout properly the bootstrap function will be limited to a very small percentage of users, it makes sense to split that function out into a separate, limited binary; and not pollute the pkg stream with extra cruft it does not need. > What I would like to know, is why all the anti-progress emails[1] have > to wait until the Last Minute(tm) when information on pkgng availability > has been available for quite some time now. First off, I resent being told that because I'm raising legitimate issues with something that I am being "obstructionist," or "anti-progress." And my concerns are certainly not "last minute." I've been raising concerns about pkg since day 1, and given that there is still no coherent, comprehensive project plan about the migration it's not at all surprising that others are also starting to discover daemons in the details. It's also part and parcel of life in an open source project. Most people don't pay attention about most things until they feel that it will be affecting them. This is doubly true in open source. Given how well-known this issue is, it should be planned for in any kind of big project such as this. It's probably also worth mentioning that there are only so many hours in the day, so one has to prioritize. Doug - -- I am only one, but I am one. I cannot do everything, but I can do something. And I will not let what I cannot do interfere with what I can do. -- Edward Everett Hale, (1822 - 1909) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (MingW32) iQEcBAEBCAAGBQJQOCwUAAoJEFzGhvEaGryEcpgH/2CAPBCldr7HlTjIzErqtbTO S0ZaI0RabwEk85+HuFCmBLTbdKqVjGYcLqIbz7l6wOa20N1rPARtBDy5DkrMrL6s 5YAgWiZ43FyKQ4826VDVBvhPqxXMD0O+sETs2kskFUkV73u/r1/8EpfZgwCDk9F9 G8hqMVTRyoWgoh1HIaBba5/m4D7+UGPYE2w8M3QAGSULePYJLgaRdu+jd2aNBrJD NFjY4lyLbitbIH1/fYHDR90KqlBVP6vr+bWUvdoHFJQ0W0HQw7wMtamo418SlORI qfTaoHL4sA1sggHrlUVvxjgWbAtIcYT2F3K+u34yTaWAoqxoN9pzRy3GWXyFRzM= =PNr3 -----END PGP SIGNATURE----- From owner-freebsd-current@FreeBSD.ORG Sat Aug 25 00:47:31 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B63E1106564A; Sat, 25 Aug 2012 00:47:31 +0000 (UTC) (envelope-from jonathan.robert.anderson@gmail.com) Received: from mail-wi0-f172.google.com (mail-wi0-f172.google.com [209.85.212.172]) by mx1.freebsd.org (Postfix) with ESMTP id 69B518FC0A; Sat, 25 Aug 2012 00:47:30 +0000 (UTC) Received: by wicr5 with SMTP id r5so1209248wic.13 for ; Fri, 24 Aug 2012 17:47:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:cc:message-id:in-reply-to:references:subject:x-mailer :mime-version:content-type:content-transfer-encoding :content-disposition; bh=63HlJcDWcwOkw0vs0jIq1mhPXMLcijyhAknlYEvjm7k=; b=ypTi0d7EQfr4rZPjoYiD393c5UHNQU/XZvbdpclujAT3kOAfZAvDnktlWLKz7L3UeP WfNZ6c3NyPLOmIkYonUhE7IIXXuN33rVm1RWJ3we2aH0kiRyJKts/22gU3c8YWTWrDZi 9QUu2oS7X+hplr7qZtorvQEY0f43tcVBh3PrGlaTKhiAZY7jQJth928ISPNJOLJA0xIE 7Wc41zDN/CHDbootJZxvKPUCoDdCYDR4NvILLNaXz+IC3PaACqhlWubDtGFCHj//vtXW pCTuMA91AH+XAOTKhIej1w9Zyu/5XlUBUtsHDvB9RcBrWT2aH6VqiUCXiFghPzc2tbSN f0QA== Received: by 10.180.86.106 with SMTP id o10mr9158552wiz.22.1345855649261; Fri, 24 Aug 2012 17:47:29 -0700 (PDT) Received: from [192.168.0.2] (cpc2-cmbg15-2-0-cust323.5-4.cable.virginmedia.com. [86.26.13.68]) by mx.google.com with ESMTPS id o2sm91453wiz.11.2012.08.24.17.47.27 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 24 Aug 2012 17:47:28 -0700 (PDT) Date: Sat, 25 Aug 2012 01:47:26 +0100 From: Jonathan Anderson To: Glen Barber Message-ID: In-Reply-To: <20120825003346.GA1345@glenbarber.us> References: <97612B57-1255-4BB3-A6D3-FC74324C6D67@FreeBSD.org> <20120824081543.GB2998@ithaqua.etoilebsd.net> <50380269.6020003@FreeBSD.org> <67BB0A66-A9D2-4257-A91E-C249B8076A87@gmail.com> <20120825003346.GA1345@glenbarber.us> X-Mailer: sparrow 1.6.3 (build 1164) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Mailman-Approved-At: Sat, 25 Aug 2012 01:39:09 +0000 Cc: ports@freebsd.org, Steve Wills , Baptiste Daroussin , Doug Barton , current@freebsd.org Subject: Re: pkgng suggestion: renaming /usr/sbin/pkg to /usr/sbin/pkg-bootstrap X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 25 Aug 2012 00:47:31 -0000 On Saturday, 25 August 2012 at 01:33, Glen Barber wrote: > On Sat, Aug 25, 2012 at 01:25:15AM +0100, Jonathan Anderson wrote: > > On 24 Aug 2012, at 23:38, Doug Barton wrote: > > > Let me rephrase that more simply ... very few users are ever going to > > > need the bootstrapping tool that will be in the base. > > > > > So, then they won't use it. I fail to see the problem here. I also fail to see the problem. :) Just to be clear, my post was arguing against Doug's assertion that few will use pkg's bootstrapper (and that this is a problem): I hope that pkgng and package sets will vastly increase the use of binary packages by FreeBSD consumers. > /usr/sbin/pkg installs /usr/local/sbin/pkg without requiring the Ports > Collection to be available locally. Which is exactly the behaviour that I want: I view the ports tree as a last resort to be used only if binary packages fail to fulfil my needs. Sometimes I don't even bother fetching it. Once again, we may be in violent agreement here. :) Jon -- Jonathan Anderson jonathan@FreeBSD.org From owner-freebsd-current@FreeBSD.ORG Sat Aug 25 09:50:01 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 93772106566C; Sat, 25 Aug 2012 09:50:01 +0000 (UTC) (envelope-from jlaffaye.freebsd@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 590318FC08; Sat, 25 Aug 2012 09:49:59 +0000 (UTC) Received: by eeke52 with SMTP id e52so1031482eek.13 for ; Sat, 25 Aug 2012 02:49:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=898r7Iwki7HA81JNG8SHP8M+Bm2g4Fe0sBNC672Fx8Q=; b=pPZBhWDX3dY1gXE4cC0mYhIX0gwJHD1xZovX6lxzx6hRxxOTLtCQyy61sBtwOImyBZ e4ejKDsogySxpCpVxvpVJUfb56DvJwA5VaJ2A0058T8moIfpVgsEiYwsNnpIY2gsoKxV hid70wnXZ6A4u7EOvfFCfKQ2eP0ggN3/rdsMhRTCQF7sRZNzgq0c7aydXMZ2vcHget5f o2igfCRuNY71pKRuqWk9JfYggHHS0wGhQRtkLUzyL3jeQ6gvUl3urMEW0nI9avCZPN2O XfpPemKIMT9Zv/pK0jwT3NA/ApVmuUpNtFpf+WBK/v8fDt6DtvZU6FGt5vbNiom8XaaO xi+A== Received: by 10.14.198.129 with SMTP id v1mr10190968een.42.1345888192839; Sat, 25 Aug 2012 02:49:52 -0700 (PDT) Received: from [192.168.1.67] (lantea.jlaffaye.net. [109.190.125.169]) by mx.google.com with ESMTPS id h42sm36251755eem.5.2012.08.25.02.49.50 (version=SSLv3 cipher=OTHER); Sat, 25 Aug 2012 02:49:52 -0700 (PDT) Sender: Julien Laffaye Message-ID: <50389FC0.50102@freebsd.org> Date: Sat, 25 Aug 2012 11:49:52 +0200 From: Julien Laffaye User-Agent: Thunderbird/7.0.1 MIME-Version: 1.0 To: Doug Barton References: <97612B57-1255-4BB3-A6D3-FC74324C6D67@FreeBSD.org> <785B5BAD-E015-4624-B3A1-D05E1BD97E51@freebsd.org> <5AC662AA-4874-4BC2-9862-65518B79B840@freebsd.org> <5036EE2E.4040606@FreeBSD.org> <5037F8BB.9020501@FreeBSD.org> In-Reply-To: <5037F8BB.9020501@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: ports@freebsd.org, Eitan Adler , Baptiste Daroussin , current@freebsd.org, Steve Wills Subject: Re: pkgng suggestion: renaming /usr/sbin/pkg to /usr/sbin/pkg-bootstrap X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 25 Aug 2012 09:50:01 -0000 On 8/24/2012 11:57 PM, Doug Barton wrote: > On 8/23/2012 8:03 PM, Eitan Adler wrote: >> On 23 August 2012 22:59, Doug Barton wrote: >>> I tend to agree with Steve here ... we can't be responsible for other >>> people's poorly written docs. >> This isn't about poorly written docs. This is the user expecting a >> tool to exist, which doesn't. Take another example of a sysadmin which >> rarely installs new systems, installs FreeBSD for the third time, and >> then gets confused when "pkg install vim" fails. > Aren't we going to install the pkg package on new systems when they are > installed? Isn't that (shouldn't that be?) part of the project plan? It > would be insane for us not to do that, at least for the releases where > pkg is the default. True. But when you create jails without the installer, you have to install pkgng by hand. Hence the /usr/sbin/pkg bootstrap. > >>> You bring up a valid point that we should >>> keep in mind for our own however. The bootstrapping issue will be the >>> smallest possible annoyance on a long road of the migration process. >> The bootstrapping issue is a factor even after the migration :) > I think that the point I'm trying to make is that it shouldn't be. > >> note that I'm not talking about the mechanism here, I'm trying to >> avoid "pkg doesn't seem to be installed on my fresh system" becoming a >> FAQ. > The way that we avoid that problem is not to create it for ourselves in > the first place. :) > > The role of pkg-bootstrap is for those users who have already-installed > systems that need to do the conversion, or if somehow pkg becomes > corrupted on the user's system and needs to be reinstalled. That's it. > > I like that you're thinking through the related issues, but in this > particular case I think you're overthinking it. > > Doug > From owner-freebsd-current@FreeBSD.ORG Sat Aug 25 10:53:57 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5B8311065670; Sat, 25 Aug 2012 10:53:57 +0000 (UTC) (envelope-from des@des.no) Received: from smtp.des.no (smtp.des.no [194.63.250.102]) by mx1.freebsd.org (Postfix) with ESMTP id 1A0A08FC12; Sat, 25 Aug 2012 10:53:56 +0000 (UTC) Received: from ds4.des.no (smtp.des.no [194.63.250.102]) by smtp.des.no (Postfix) with ESMTP id 7F21F6942; Sat, 25 Aug 2012 12:53:48 +0200 (CEST) Received: by ds4.des.no (Postfix, from userid 1001) id 1FE818DB4; Sat, 25 Aug 2012 12:53:47 +0200 (CEST) From: =?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= To: John Baldwin References: <502831B7.1080309@freebsd.org> <201208240748.19737.jhb@freebsd.org> <866288laq0.fsf@ds4.des.no> <201208241013.48805.jhb@freebsd.org> Date: Sat, 25 Aug 2012 12:53:46 +0200 In-Reply-To: <201208241013.48805.jhb@freebsd.org> (John Baldwin's message of "Fri, 24 Aug 2012 10:13:48 -0400") Message-ID: <86393b8cp1.fsf@ds4.des.no> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.4 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: alc@freebsd.org, freebsd-current@freebsd.org, Colin Percival Subject: Re: Time to bump default VM_SWZONE_SIZE_MAX? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 25 Aug 2012 10:53:57 -0000 John Baldwin writes: > Dag-Erling Sm=C3=B8rgrav writes: > > The limit we had was insufficient for 8 GB of swap. > In absolute or practical terms? This whole thing started because I have a machine with 8 GB swap that ran out of swzone. > At this point i386 is going to be used on smaller systems > (e.g. netbooks, etc.), not servers that have lots of swap. I don't think it's unreasonable for an i386 box to be maxed out on RAM (4 GB) and have twice that amount of swap. DES --=20 Dag-Erling Sm=C3=B8rgrav - des@des.no From owner-freebsd-current@FreeBSD.ORG Sat Aug 25 12:21:59 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0FC5B106566B; Sat, 25 Aug 2012 12:21:59 +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 D07678FC14; Sat, 25 Aug 2012 12:21:58 +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 q7PCLprf025617; Sat, 25 Aug 2012 08:21:51 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-current.sentex.ca (8.14.5/8.14.5/Submit) id q7PCLprX025608; Sat, 25 Aug 2012 12:21:51 GMT (envelope-from tinderbox@freebsd.org) Date: Sat, 25 Aug 2012 12:21:51 GMT Message-Id: <201208251221.q7PCLprX025608@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 , , Precedence: bulk Cc: Subject: [head tinderbox] failure on powerpc/powerpc X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Aug 2012 12:21:59 -0000 TB --- 2012-08-25 09:46:14 - tinderbox 2.9 running on freebsd-current.sentex.ca TB --- 2012-08-25 09:46:14 - 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 --- 2012-08-25 09:46:14 - starting HEAD tinderbox run for powerpc/powerpc TB --- 2012-08-25 09:46:14 - cleaning the object tree TB --- 2012-08-25 09:46:14 - cvsupping the source tree TB --- 2012-08-25 09:46:14 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/powerpc/powerpc/supfile TB --- 2012-08-25 09:47:05 - building world TB --- 2012-08-25 09:47:05 - CROSS_BUILD_TESTING=YES TB --- 2012-08-25 09:47:05 - MAKEOBJDIRPREFIX=/obj TB --- 2012-08-25 09:47:05 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-08-25 09:47:05 - SRCCONF=/dev/null TB --- 2012-08-25 09:47:05 - TARGET=powerpc TB --- 2012-08-25 09:47:05 - TARGET_ARCH=powerpc TB --- 2012-08-25 09:47:05 - TZ=UTC TB --- 2012-08-25 09:47:05 - __MAKE_CONF=/dev/null TB --- 2012-08-25 09:47:05 - cd /src TB --- 2012-08-25 09:47:05 - /usr/bin/make -B buildworld >>> World build started on Sat Aug 25 09:47:06 UTC 2012 >>> 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 Sat Aug 25 12:10:34 UTC 2012 TB --- 2012-08-25 12:10:34 - generating LINT kernel config TB --- 2012-08-25 12:10:34 - cd /src/sys/powerpc/conf TB --- 2012-08-25 12:10:34 - /usr/bin/make -B LINT TB --- 2012-08-25 12:10:34 - cd /src/sys/powerpc/conf TB --- 2012-08-25 12:10:34 - /usr/sbin/config -m LINT TB --- 2012-08-25 12:10:34 - building LINT kernel TB --- 2012-08-25 12:10:34 - CROSS_BUILD_TESTING=YES TB --- 2012-08-25 12:10:34 - MAKEOBJDIRPREFIX=/obj TB --- 2012-08-25 12:10:34 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-08-25 12:10:34 - SRCCONF=/dev/null TB --- 2012-08-25 12:10:34 - TARGET=powerpc TB --- 2012-08-25 12:10:34 - TARGET_ARCH=powerpc TB --- 2012-08-25 12:10:34 - TZ=UTC TB --- 2012-08-25 12:10:34 - __MAKE_CONF=/dev/null TB --- 2012-08-25 12:10:34 - cd /src TB --- 2012-08-25 12:10:34 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Sat Aug 25 12:10:34 UTC 2012 >>> 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 -c -O -pipe -std=c99 -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 -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/libfdt -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -msoft-float -Wa,-many -fno-omit-frame-pointer -msoft-float -mno-altivec -ffreestanding -fstack-protector -Werror /src/sys/libkern/umoddi3.c cc -c -O -pipe -std=c99 -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 -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/libfdt -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -msoft-float -Wa,-many -fno-omit-frame-pointer -msoft-float -mno-altivec -ffreestanding -fstack-protector -Werror /src/sys/powerpc/aim/clock.c cc -c -O -pipe -std=c99 -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 -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/libfdt -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -msoft-float -Wa,-many -fno-omit-frame-pointer -msoft-float -mno-altivec -ffreestanding -fstack-protector -Werror /src/sys/powerpc/aim/copyinout.c cc -c -O -pipe -std=c99 -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 -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/libfdt -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -msoft-float -Wa,-many -fno-omit-frame-pointer -msoft-float -mno-altivec -ffreestanding -fstack-protector -Werror /src/sys/powerpc/aim/interrupt.c cc -c -O -pipe -std=c99 -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 -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/libfdt -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -msoft-float -Wa,-many -fno-omit-frame-pointer -msoft-float -mno-altivec -ffreestanding -fstack-protector -Werror /src/sys/powerpc/aim/machdep.c cc1: warnings being treated as errors /src/sys/powerpc/aim/machdep.c: In function 'powerpc_init': /src/sys/powerpc/aim/machdep.c:261: warning: unused variable 'vers' [-Wunused-variable] *** Error code 1 Stop in /obj/powerpc.powerpc/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2012-08-25 12:21:51 - WARNING: /usr/bin/make returned exit code 1 TB --- 2012-08-25 12:21:51 - ERROR: failed to build LINT kernel TB --- 2012-08-25 12:21:51 - 7422.90 user 961.34 system 9337.58 real http://tinderbox.freebsd.org/tinderbox-head-HEAD-powerpc-powerpc.full From owner-freebsd-current@FreeBSD.ORG Sat Aug 25 13:26:01 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 45CA7106566B; Sat, 25 Aug 2012 13:26:01 +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 1364B8FC19; Sat, 25 Aug 2012 13:26:00 +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 q7PDPx9w058062; Sat, 25 Aug 2012 09:25:59 -0400 (EDT) (envelope-from tinderbox@freebsd.org) Received: (from tinderbox@localhost) by freebsd-current.sentex.ca (8.14.5/8.14.5/Submit) id q7PDPxMi058061; Sat, 25 Aug 2012 13:25:59 GMT (envelope-from tinderbox@freebsd.org) Date: Sat, 25 Aug 2012 13:25:59 GMT Message-Id: <201208251325.q7PDPxMi058061@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 , , Precedence: bulk Cc: Subject: [head tinderbox] failure on powerpc64/powerpc X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Aug 2012 13:26:01 -0000 TB --- 2012-08-25 10:29:08 - tinderbox 2.9 running on freebsd-current.sentex.ca TB --- 2012-08-25 10:29:08 - 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 --- 2012-08-25 10:29:08 - starting HEAD tinderbox run for powerpc64/powerpc TB --- 2012-08-25 10:29:08 - cleaning the object tree TB --- 2012-08-25 10:29:08 - cvsupping the source tree TB --- 2012-08-25 10:29:08 - /usr/bin/csup -z -r 3 -g -L 1 -h cvsup.sentex.ca /tinderbox/HEAD/powerpc64/powerpc/supfile TB --- 2012-08-25 10:29:46 - building world TB --- 2012-08-25 10:29:46 - CROSS_BUILD_TESTING=YES TB --- 2012-08-25 10:29:46 - MAKEOBJDIRPREFIX=/obj TB --- 2012-08-25 10:29:46 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-08-25 10:29:46 - SRCCONF=/dev/null TB --- 2012-08-25 10:29:46 - TARGET=powerpc TB --- 2012-08-25 10:29:46 - TARGET_ARCH=powerpc64 TB --- 2012-08-25 10:29:46 - TZ=UTC TB --- 2012-08-25 10:29:46 - __MAKE_CONF=/dev/null TB --- 2012-08-25 10:29:46 - cd /src TB --- 2012-08-25 10:29:46 - /usr/bin/make -B buildworld >>> World build started on Sat Aug 25 10:29:47 UTC 2012 >>> 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 >>> stage 5.1: building 32 bit shim libraries >>> World build completed on Sat Aug 25 13:15:34 UTC 2012 TB --- 2012-08-25 13:15:34 - generating LINT kernel config TB --- 2012-08-25 13:15:34 - cd /src/sys/powerpc/conf TB --- 2012-08-25 13:15:34 - /usr/bin/make -B LINT TB --- 2012-08-25 13:15:34 - cd /src/sys/powerpc/conf TB --- 2012-08-25 13:15:34 - /usr/sbin/config -m LINT TB --- 2012-08-25 13:15:34 - building LINT kernel TB --- 2012-08-25 13:15:34 - CROSS_BUILD_TESTING=YES TB --- 2012-08-25 13:15:34 - MAKEOBJDIRPREFIX=/obj TB --- 2012-08-25 13:15:34 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2012-08-25 13:15:34 - SRCCONF=/dev/null TB --- 2012-08-25 13:15:34 - TARGET=powerpc TB --- 2012-08-25 13:15:34 - TARGET_ARCH=powerpc64 TB --- 2012-08-25 13:15:34 - TZ=UTC TB --- 2012-08-25 13:15:34 - __MAKE_CONF=/dev/null TB --- 2012-08-25 13:15:34 - cd /src TB --- 2012-08-25 13:15:34 - /usr/bin/make -B buildkernel KERNCONF=LINT >>> Kernel build for LINT started on Sat Aug 25 13:15:34 UTC 2012 >>> 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 -c -O -pipe -std=c99 -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 -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/libfdt -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -msoft-float -Wa,-many -fno-omit-frame-pointer -msoft-float -mno-altivec -mcall-aixdesc -ffreestanding -fstack-protector -Werror /src/sys/libkern/memset.c cc -c -O -pipe -std=c99 -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 -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/libfdt -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -msoft-float -Wa,-many -fno-omit-frame-pointer -msoft-float -mno-altivec -mcall-aixdesc -ffreestanding -fstack-protector -Werror /src/sys/powerpc/aim/clock.c cc -c -O -pipe -std=c99 -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 -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/libfdt -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -msoft-float -Wa,-many -fno-omit-frame-pointer -msoft-float -mno-altivec -mcall-aixdesc -ffreestanding -fstack-protector -Werror /src/sys/powerpc/aim/copyinout.c cc -c -O -pipe -std=c99 -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 -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/libfdt -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -msoft-float -Wa,-many -fno-omit-frame-pointer -msoft-float -mno-altivec -mcall-aixdesc -ffreestanding -fstack-protector -Werror /src/sys/powerpc/aim/interrupt.c cc -c -O -pipe -std=c99 -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 -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/libfdt -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -msoft-float -Wa,-many -fno-omit-frame-pointer -msoft-float -mno-altivec -mcall-aixdesc -ffreestanding -fstack-protector -Werror /src/sys/powerpc/aim/machdep.c cc1: warnings being treated as errors /src/sys/powerpc/aim/machdep.c: In function 'powerpc_init': /src/sys/powerpc/aim/machdep.c:261: warning: unused variable 'vers' [-Wunused-variable] *** Error code 1 Stop in /obj/powerpc.powerpc64/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2012-08-25 13:25:59 - WARNING: /usr/bin/make returned exit code 1 TB --- 2012-08-25 13:25:59 - ERROR: failed to build LINT kernel TB --- 2012-08-25 13:25:59 - 8877.92 user 1192.90 system 10610.91 real http://tinderbox.freebsd.org/tinderbox-head-HEAD-powerpc64-powerpc.full From owner-freebsd-current@FreeBSD.ORG Sat Aug 25 17:26:46 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1FCD61065694 for ; Sat, 25 Aug 2012 17:26:46 +0000 (UTC) (envelope-from jeffreybouquet@yahoo.com) Received: from nm2-vm0.bullet.mail.sp2.yahoo.com (nm2-vm0.bullet.mail.sp2.yahoo.com [98.139.91.248]) by mx1.freebsd.org (Postfix) with SMTP id E87EB8FC1E for ; Sat, 25 Aug 2012 17:26:45 +0000 (UTC) Received: from [72.30.22.92] by nm2.bullet.mail.sp2.yahoo.com with NNFMP; 25 Aug 2012 17:26:45 -0000 Received: from [98.139.91.50] by tm14.bullet.mail.sp2.yahoo.com with NNFMP; 25 Aug 2012 17:26:45 -0000 Received: from [127.0.0.1] by omp1050.mail.sp2.yahoo.com with NNFMP; 25 Aug 2012 17:26:45 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 455795.93460.bm@omp1050.mail.sp2.yahoo.com Received: (qmail 36835 invoked by uid 60001); 25 Aug 2012 17:26:45 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1345915605; bh=brE5BXtnxhHDlLaDtQ9a0A52GxPlXjk69ny0A+AexlM=; h=X-YMail-OSG:Received:X-Mailer:Message-ID:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=JhWJ3w/c0GA63quUxtA37EGxZpUkCb0+Y3anvUPbwAd/lf69vFSudH/y+1Gs6zUdtcp9QQbzsoO8b0ltunhcHmIgc7GCm6UJxto0IXKRJvp5fW9wM3O/Qax2UYWK6gNk46vltS3BNjqAPuS4FMTiZ5TPE6wcd2V8jpyuD49Vgvg= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:Message-ID:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=ctMx+gZz8YRP0K7OLBRcva3pgZkHDr5oRjLCd6SS2fn+ejKGkOwk7I5bgn8DNB1h2J6eDpMLxz53kx5jJoWAUssvL9/uWVmkHhUbiCvb7KG8/fsYTPDqVtImDQ66i+DZy3vNZKjeC/dbGQEE+32+yDZjuwS//Oo3hAu8HGWg3K8=; X-YMail-OSG: W0AqPDgVM1n.OMLf8rPGY1u0lE4VvC8eDgiNcDMRhwRP1gs HFT7c5xyoTBwDGkTcSXudS01G5YdTT0A.kS8nyc43EPD4au30WNkVwtf4w8L LAzREFTlS35FFU3hVAqX4qnjTP48NZWpbcOzP_bNkWWhLrYlnpi7IChI6M5L Hs4V62UbgsLoNihmyG5jpNEfggauCM9kH9gG5ASTUuUuyFdBDHbV4rOVihOo Ax_tMThUMzGhmQVw25LG8fgZ0xuw6ExdpYPdzHF5m6NTbe0HOolapLx2db6B wGOkEjsKZEnWwJTy7Bm3coc73v_Bd9HFf_ShTZophKGdSPNaDF71_e36bXP_ wXHi1CDPrLPQ99qmgNOO1IUy_YmzGBBrMJQpxiZe4dCLi7Nl6lZemirpgguA 2EM0HRGhhbDrGV8EgnrJDRiJeP0mw0pAxhF7yCBnNMgrA2NHpJncu6y_vA4O LSuV6LRhobIX4FEdJohP.gQcd Received: from [66.92.43.99] by web111312.mail.gq1.yahoo.com via HTTP; Sat, 25 Aug 2012 10:26:44 PDT X-Mailer: YahooMailClassic/15.0.8 YahooMailWebService/0.8.121.416 Message-ID: <1345915604.11722.YahooMailClassic@web111312.mail.gq1.yahoo.com> Date: Sat, 25 Aug 2012 10:26:44 -0700 (PDT) From: Jeffrey Bouquet To: Patrick Lamaiziere In-Reply-To: <20120825122417.320da61f@davenulle.org> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Mailman-Approved-At: Sat, 25 Aug 2012 19:07:55 +0000 Cc: freebsd-current@freebsd.org Subject: Re: One more pkg non-default-please edge-case reasoning... X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 25 Aug 2012 17:26:46 -0000 Missing: Three pages of examples (maybe) from "man pkg query"=0A(or some ot= her workaround...=0AUse Case: (one of many variants) follows... =0A=0Apwd = =3D=3D /usr/ports/graphics/exif=0A[alias for make build-depends-list ] ...= one second=0A[needs libexif] # query, is it installed?=0Alookat /var/db/p= kg/libex[tab][tab][tab][tab] #zsh doing the work=0Alookat /var/db/pkg/lib= exif-# , cr # ... 2nd, 3rd and fourth seconds=0A[select +REQ...BY in looka= t's file selection pane ] 5th second=0Aresult: already installed, require= d by 15-20 ports already.=0A=0AI tried to find an equivalent in man pkg-que= ry. Un-exampled=0Aformat string rules, combinations, orders, etc are prese= nted. I=0Apresume that if pkg becomes the default, I'd have to formulate an= =0Aalias to match lookat's *immediate* result with the scenario=0Aabove (wh= ich I use many times weekly...) and hope that it works as=0Awell. [1] Then,= there is the case, that if some reason I am locked=0Ainto the sh shell, or= programming in bash, or something, hours=0Aadditionally (probable) to what= *may* have been way easier (as=0Aabove) is to be reckoned with. =0A[1] Ign= orance, I know, but still... =0A=0A=0A[Not the only reply to this message, = FWIW for those to whom the=0Aother reply was not Cc:'d...]=0A=0AJ. Bouquet= =0A=0A--- On Sat, 8/25/12, Patrick Lamaiziere wrote= :=0A=0A> From: Patrick Lamaiziere =0A> Subject: Re: = One more pkg non-default-please edge-case reasoning...=0A> To: "Jeffrey Bou= quet" =0A> Cc: freebsd-ports@freebsd.org=0A> Date= : Saturday, August 25, 2012, 3:24 AM=0A> Le Fri, 24 Aug 2012 19:44:15 -0700= =0A> (PDT),=0A> Jeffrey Bouquet =0A> a =E9crit := =0A> =0A> > This side of simple. (Additionally, a nice=0A> white-on-blue re= adability).=0A> > Never got used to the search keys in "less" etc.=A0=0A> S= o the flat files=0A> > here serve a purpose I surmise is not that common.= =0A> > And figuring out which=A0 category /editors/ etc=0A> (the pkg-plist= =0A> > equivalent) is way slower in many cases.=0A> > A reason to retain th= at particular usability...=0A> til/when I/someone=0A> > notices a workaroun= d.=0A> =0A> I'm not sure to understand what you want to do, but listing=0A>= the files=0A> owned by an installed pkg packages is easy:=0A> for zip:=0A>= # pkg info -l zip=0A> zip-3.0 owns the following files:=0A> /usr/local/bin= /zip=0A> ...=0A> /usr/local/share/doc/zip/WHERE=0A> =0A> Please have a try = with pkg, is really great.=0A> From owner-freebsd-current@FreeBSD.ORG Sat Aug 25 20:43:28 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id BEE61106564A; Sat, 25 Aug 2012 20:43:28 +0000 (UTC) (envelope-from freebsd-listen@fabiankeil.de) Received: from smtprelay01.ispgateway.de (smtprelay01.ispgateway.de [80.67.31.35]) by mx1.freebsd.org (Postfix) with ESMTP id 4EF098FC12; Sat, 25 Aug 2012 20:43:27 +0000 (UTC) Received: from [78.35.178.199] (helo=fabiankeil.de) by smtprelay01.ispgateway.de with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.68) (envelope-from ) id 1T5NCS-0005Zi-Mb; Sat, 25 Aug 2012 22:43:20 +0200 Date: Sat, 25 Aug 2012 22:33:31 +0200 From: Fabian Keil To: freebsd-security@freebsd.org Message-ID: <20120825223331.39d56334@fabiankeil.de> In-Reply-To: References: <5032AB28.9070306@FreeBSD.org> <20120821120537.GL1202@acme.spoerlein.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=PGP-SHA1; boundary="Sig_/ddw_HLgqahnHezVLZtNCKE1"; protocol="application/pgp-signature" X-Df-Sender: Nzc1MDY3 Cc: freebsd-current@freebsd.org Subject: Re: [HEADSUP] geli(4) weak master key generation on -CURRENT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 25 Aug 2012 20:43:28 -0000 --Sig_/ddw_HLgqahnHezVLZtNCKE1 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable "Simon L. B. Nielsen" wrote: > On Tue, Aug 21, 2012 at 1:05 PM, Ulrich Sp=F6rlein wrot= e: > > On Mon, 2012-08-20 at 22:24:56 +0100, Simon L. B. Nielsen wrote: > >> -CURRENT users of geli(4) should be advised that, a geli(4) device may > >> have weak master key, if the provider is created on -CURRENT system > >> built against source code between r238116 (Jul 4 17:54:17 2012 UTC) > >> and r239184 (non-inclusive, Aug 10 18:43:29 2012 UTC). > >> > >> One can verify if its provider was created with weak keys by running: > >> > >> # geli dump | grep version > >> > >> If the version is 7 and the system did not include this fix (r239184) > >> when provider was initialized, then the data has to be backed up, > >> underlying provider overwritten with random data, system upgraded and > >> provider recreated. > > I haven't read commit mails in a very long time, but is there code in > > place that will issue a warning upon geli attach if version 7 is > > detected? While -CURRENT is not supported, there might be a lot of disks > > initialized with version 7 and they'll eventually be upgraded to > > 10.0-RELEASE (the OS, not necessarily the geli volumes). >=20 > No, the bad code was only in head for about a month. I'm fine with > having a warning, but somebody has to code it. The weak keys weren't stored on disk, but generated at attach-time. A patched kernel will generate different keys which means it shouldn't be backwards compatible to a vulnerable kernel as far as reading and writing geli version 7 is concerned. If a user doesn't follow the recommended mitigation steps and simply updates the kernel without migrating the data first, he shouldn't be able to read the encrypted data written with the previous kernel version, which I consider kinda hard to miss. I believe if there really were "a lot of disks" initialized with affected kernels, there would have been at least a couple of complaints on the mailing lists already. Fabian --Sig_/ddw_HLgqahnHezVLZtNCKE1 Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEARECAAYFAlA5Np4ACgkQBYqIVf93VJ0EpgCfY9jr+hFBRWn1UAMK4x86b5Km nUoAoL8GHxYkNumdBjHTCgZ/tgYJStvz =xTKj -----END PGP SIGNATURE----- --Sig_/ddw_HLgqahnHezVLZtNCKE1-- From owner-freebsd-current@FreeBSD.ORG Sat Aug 25 23:34:51 2012 Return-Path: Delivered-To: current@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0DAFD106566C; Sat, 25 Aug 2012 23:34:51 +0000 (UTC) (envelope-from cyberleo@cyberleo.net) Received: from paka.cyberleo.net (paka.cyberleo.net [66.219.31.21]) by mx1.freebsd.org (Postfix) with ESMTP id A9D6C8FC08; Sat, 25 Aug 2012 23:34:50 +0000 (UTC) Received: from [172.16.44.4] (den.cyberleo.net [216.80.73.130]) by paka.cyberleo.net (Postfix) with ESMTPSA id 879AC284A5; Sat, 25 Aug 2012 19:34:47 -0400 (EDT) Message-ID: <50396113.3080607@cyberleo.net> Date: Sat, 25 Aug 2012 18:34:43 -0500 From: CyberLeo Kitsana User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.6esrpre) Gecko/20120820 Thunderbird/10.0.6 MIME-Version: 1.0 To: Baptiste Daroussin References: <97612B57-1255-4BB3-A6D3-FC74324C6D67@FreeBSD.org> <20120824081543.GB2998@ithaqua.etoilebsd.net> <50380269.6020003@FreeBSD.org> <20120825000148.GF37867@ithaqua.etoilebsd.net> In-Reply-To: <20120825000148.GF37867@ithaqua.etoilebsd.net> X-Enigmail-Version: 1.3.5 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Sat, 25 Aug 2012 23:57:19 +0000 Cc: ports@FreeBSD.org, Steve Wills , Doug Barton , current@FreeBSD.org Subject: Re: pkgng suggestion: renaming /usr/sbin/pkg to /usr/sbin/pkg-bootstrap X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 25 Aug 2012 23:34:51 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 08/24/2012 07:01 PM, Baptiste Daroussin wrote: > Can anyone give me he details on the security related problem? Off the top of my head, it seems to represent a break in the chain of trust: how does the bootstrapper verify that the tarball it just downloaded to bootstrap pkg is genuine, and not, for example, a trojan? The source in usr.sbin/pkg/pkg.c[1] doesn't seem to suggest it cares. [1] http://git.cyberleo.net/?p=FreeBSD/releng/9.1.git;a=blob;f=usr.sbin/pkg/pkg.c;hb=b96b623d8debed8fa8fd7df5af01a350344549c9 - -- Fuzzy love, - -CyberLeo Technical Administrator CyberLeo.Net Webhosting http://www.CyberLeo.Net Furry Peace! - http://wwww.fur.com/peace/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAlA5YRMACgkQi7w8kEi1KHLZhwCgrGb8piGeNb07IryWvoc/JdzH xfAAoNfxm+nLoXU7BUclKqnLGbkxgilX =o9Br -----END PGP SIGNATURE-----