From owner-freebsd-standards@FreeBSD.ORG Sun Mar 22 15:04:34 2009 Return-Path: Delivered-To: standards@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EA4711065670 for ; Sun, 22 Mar 2009 15:04:34 +0000 (UTC) (envelope-from wxs@atarininja.org) Received: from syn.atarininja.org (syn.csh.rit.edu [129.21.60.158]) by mx1.freebsd.org (Postfix) with ESMTP id C949C8FC0A for ; Sun, 22 Mar 2009 15:04:34 +0000 (UTC) (envelope-from wxs@atarininja.org) Received: by syn.atarininja.org (Postfix, from userid 1001) id 09EE35C17; Sun, 22 Mar 2009 10:47:53 -0400 (EDT) Date: Sun, 22 Mar 2009 10:47:53 -0400 From: Wesley Shields To: standards@freebsd.org Message-ID: <20090322144753.GA48259@atarininja.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.19 (2009-01-05) Cc: peff@peff.net Subject: FW: shell choice freebsd git port X-BeenThere: freebsd-standards@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Standards compliance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Mar 2009 15:04:35 -0000 As the maintainer of devel/git I'd like this port to do the right thing, but I'm not sure if this is a legitimate bug in our /bin/sh or not. Anyone care to comment on this? -- WXS ----- Forwarded message from Jeff King ----- Date: Sun, 22 Mar 2009 05:37:10 -0400 From: Jeff King To: wxs@freebsd.org Subject: shell choice freebsd git port Hi, I'm one of the upstream developers of git, and it looks like you are the git ports maintainer for FreeBSD. I wanted to discuss an issue which you may run into while packaging git 1.6.2.1. It seems that FreeBSD's /bin/sh treats blank lines in an eval as a successful command. E.g., (the output is from FreeBSD 6.1, but I built the current HEAD from anoncvs and it seems to have the same problem): $ /bin/sh $ eval 'false ' $ echo $? 0 (whereas bash and dash would print '1'). This is problematic for our test suite, which consists of a lot of eval'ing. Failing tests may be missed if their status is ignored, one test in 1.6.2.1 which expects a non-zero exit status actually does report failure when it actually succeeded. On top of that, some of the scripts (like bisect and filter-branch) care about the exit status of evals at run-time to determine whether an error occurred. There is some discussion on the git list here: http://thread.gmane.org/gmane.comp.version-control.git/112519/focus=112621 I don't know if you want to do anything to the port to work around this. The obvious solution is requiring bash, and setting SHELL_PATH appropriately in the Makefile. You may also want to see if anyone is interested in treating this like a bug in /bin/sh and fixing it (I consider it a bug, but others may consider it historical behavior, I suppose). -Peff ----- End forwarded message ----- From owner-freebsd-standards@FreeBSD.ORG Sun Mar 22 15:17:44 2009 Return-Path: Delivered-To: freebsd-standards@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3FFF8106564A for ; Sun, 22 Mar 2009 15:17:44 +0000 (UTC) (envelope-from mikolas.janota@gmail.com) Received: from mail-fx0-f167.google.com (mail-fx0-f167.google.com [209.85.220.167]) by mx1.freebsd.org (Postfix) with ESMTP id C98F58FC0A for ; Sun, 22 Mar 2009 15:17:43 +0000 (UTC) (envelope-from mikolas.janota@gmail.com) Received: by fxm11 with SMTP id 11so1375958fxm.43 for ; Sun, 22 Mar 2009 08:17:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type:content-transfer-encoding; bh=FerDBb18RJQj16vjX9m4rVZZxkYh9OSgOGJr8nEULUQ=; b=hAX7euK9HGUoPZ5gEtSTbcnWUDbr4EhOxD9YIl7dbtgjtdd5n6LwvOh+mcZS/e3/JF n4RCEGPCxLrrKSPYbmM+h2RTL76prPlxYDXRea3XDxL9x74b866Gg0Kezqb8sG1fhYUc mUiLgCv7WnyGNdU2HNydzRzs0uNLs567vxcFI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; b=KBN+mVlI7t+8DGebniVxkZ7mG88gZmCCvjC3fwJeeF/R6WeJZg/ZIL2xZvuZnIkPFj hHYzW99/xLOat3ZYe0GpakB6i4UHOhF7iEiQdUOJO+Y1hO0QNyHRsDIPWqcUH5NHcdqh gx65yH8WJHez9J3XiadtF5qptqkDJezRedJjM= MIME-Version: 1.0 Received: by 10.223.122.15 with SMTP id j15mr5092674far.74.1237733640478; Sun, 22 Mar 2009 07:54:00 -0700 (PDT) Date: Sun, 22 Mar 2009 14:54:00 +0000 Message-ID: <682003a60903220754g6c653582lb346f8e8d6bf63cf@mail.gmail.com> From: =?UTF-8?B?TWlrb2zDocWhIEphbm90YQ==?= To: freebsd-standards@freebsd.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: POSIX conformance of ls -l -1 X-BeenThere: freebsd-standards@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Standards compliance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Mar 2009 15:17:45 -0000 For the command ls, the POSIX standard, says that "When -l (ell) is specified, -1 (one) shall be assumed." (http://www.opengroup.org/onlinepubs/000095399/utilities/ls.html) In the FreeBSD implementation, however, -1 and -l override one another. I can't see how this could be POSIX compliant. I'm on Mac OS X which I believe is using FreeBSD port and the man page claims POSIX compliance. Where can I find more information about this? --=20 Mikol=C3=A1=C5=A1 Janota M. Sc. School of Computer Science and Informatics, University College Dublin, Belfield, Dublin 4, Ireland From owner-freebsd-standards@FreeBSD.ORG Sun Mar 22 16:57:13 2009 Return-Path: Delivered-To: freebsd-standards@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A23D5106564A for ; Sun, 22 Mar 2009 16:57:13 +0000 (UTC) (envelope-from das@FreeBSD.ORG) Received: from zim.MIT.EDU (ZIM.MIT.EDU [18.95.3.101]) by mx1.freebsd.org (Postfix) with ESMTP id 6210A8FC1A for ; Sun, 22 Mar 2009 16:57:13 +0000 (UTC) (envelope-from das@FreeBSD.ORG) Received: from zim.MIT.EDU (localhost [127.0.0.1]) by zim.MIT.EDU (8.14.3/8.14.2) with ESMTP id n2MGW0eS075126; Sun, 22 Mar 2009 12:32:00 -0400 (EDT) (envelope-from das@FreeBSD.ORG) Received: (from das@localhost) by zim.MIT.EDU (8.14.3/8.14.2/Submit) id n2MGW0Pw075125; Sun, 22 Mar 2009 12:32:00 -0400 (EDT) (envelope-from das@FreeBSD.ORG) Date: Sun, 22 Mar 2009 12:32:00 -0400 From: David Schultz To: =?utf-8?B?TWlrb2zDocWh?= Janota Message-ID: <20090322163200.GA74989@zim.MIT.EDU> Mail-Followup-To: =?utf-8?B?TWlrb2zDocWh?= Janota , freebsd-standards@FreeBSD.ORG References: <682003a60903220754g6c653582lb346f8e8d6bf63cf@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <682003a60903220754g6c653582lb346f8e8d6bf63cf@mail.gmail.com> Cc: freebsd-standards@FreeBSD.ORG Subject: Re: POSIX conformance of ls -l -1 X-BeenThere: freebsd-standards@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Standards compliance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Mar 2009 16:57:13 -0000 On Sun, Mar 22, 2009, Mikoláš Janota wrote: > For the command ls, the POSIX standard, says that "When -l (ell) is > specified, -1 (one) shall be assumed." > (http://www.opengroup.org/onlinepubs/000095399/utilities/ls.html) > > In the FreeBSD implementation, however, -1 and -l override one > another. I can't see how this could be POSIX compliant. > > I'm on Mac OS X which I believe is using FreeBSD port and the man page > claims POSIX compliance. Where can I find more information about this? Perhaps it's a bug. Comments in the source seem to indicate that it was done this way on purpose, though. If you have `ls' aliased to `ls -laG', for example, you can still use `ls -1' on the command line to force the single-line output (as if the options were `ls -aG'.) I'm not sure what we ought to do about it. From owner-freebsd-standards@FreeBSD.ORG Sun Mar 22 22:01:47 2009 Return-Path: Delivered-To: freebsd-standards@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7DBF41065670 for ; Sun, 22 Mar 2009 22:01:47 +0000 (UTC) (envelope-from mikolas.janota@gmail.com) Received: from mail-fx0-f167.google.com (mail-fx0-f167.google.com [209.85.220.167]) by mx1.freebsd.org (Postfix) with ESMTP id DE4508FC0A for ; Sun, 22 Mar 2009 22:01:46 +0000 (UTC) (envelope-from mikolas.janota@gmail.com) Received: by fxm11 with SMTP id 11so1465811fxm.43 for ; Sun, 22 Mar 2009 15:01:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=XrAR6HeSnudVzN9lHE+xl0qT8CaUfO/XLX/MHx3w2/w=; b=iUBLbK+FGmncZFDCWWAsSVMnNCnkgoWGdFJB0jfSAerd59pH5pb2RiT2YGndVMTsF8 gS1IVgCWCVNZuvWGpGuwJFmkl4X1vTSFj+jvnDlD/QmJ7gmSknGDMUcddCDCiY/4Ror/ 2CfxHhySWNicxxyqQyVkmHf81Ho+Hg46rrhL8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=jkn7g1Gfp1ohmvIGiSXsYLgMrG5K84gvl+HSMGAPSSsUJ+L8ciNHpVZeMzdd8zDrkU S4dHIglW6AjUNK4aJbOFs/lMo5HV21ayZv/36it+RoVKbUuRbBq42FPUtb0D4cxW8rPR /o9vabb/CZiG+DS2LCxMdnHwGOmf4YuAvufe8= MIME-Version: 1.0 Received: by 10.223.108.211 with SMTP id g19mr5444681fap.39.1237759306046; Sun, 22 Mar 2009 15:01:46 -0700 (PDT) In-Reply-To: <20090322163200.GA74989@zim.MIT.EDU> References: <682003a60903220754g6c653582lb346f8e8d6bf63cf@mail.gmail.com> <20090322163200.GA74989@zim.MIT.EDU> Date: Sun, 22 Mar 2009 22:01:46 +0000 Message-ID: <682003a60903221501i31d93f58r845c9e3f18ab9695@mail.gmail.com> From: =?UTF-8?B?TWlrb2zDocWhIEphbm90YQ==?= To: =?UTF-8?B?TWlrb2zDocWhIEphbm90YQ==?= , freebsd-standards@freebsd.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: Subject: Re: POSIX conformance of ls -l -1 X-BeenThere: freebsd-standards@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Standards compliance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Mar 2009 22:01:47 -0000 On Sun, Mar 22, 2009 at 4:32 PM, David Schultz wrote: > On Sun, Mar 22, 2009, Mikol=C3=A1=C5=A1 Janota wrote: >> For the command ls, the POSIX standard, says that "When -l (ell) is >> specified, -1 (one) shall be assumed." >> (http://www.opengroup.org/onlinepubs/000095399/utilities/ls.html) >> >> In the FreeBSD implementation, however, -1 and -l override one >> another. I can't see how this could be POSIX compliant. >> >> I'm on Mac OS X which I believe is using FreeBSD port and the man page >> claims POSIX compliance. Where can I find more information about this? > > Perhaps it's a bug. Comments in the source seem to indicate that > it was done this way on purpose, though. If you have `ls' aliased > to `ls -laG', for example, you can still use `ls -1' on the command > line to force the single-line output (as if the options were `ls -aG'.) > I'm not sure what we ought to do about it. > I think the problem is that -1 is interpreted sometimes as "single-column" and sometimes as "one-per-line". The gnu implementation of ls follows the POSIX standard and ls -l -1 is the same as ls -l, but if you write --format=3Dlong --format=3Dsingle-column, long is overriden. Even though --format=3Dsingle-column and -1 should be the same. --=20 Mikol=C3=A1=C5=A1 From owner-freebsd-standards@FreeBSD.ORG Sun Mar 22 22:04:00 2009 Return-Path: Delivered-To: standards@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 31FA1106564A; Sun, 22 Mar 2009 22:04:00 +0000 (UTC) (envelope-from jilles@stack.nl) Received: from mx1.stack.nl (meestal-mk5.stack.nl [131.155.140.149]) by mx1.freebsd.org (Postfix) with ESMTP id E4A9C8FC08; Sun, 22 Mar 2009 22:03:59 +0000 (UTC) (envelope-from jilles@stack.nl) Received: by mx1.stack.nl (Postfix, from userid 65534) id F36383FA6B; Sun, 22 Mar 2009 22:48:05 +0100 (CET) X-Spam-DCC: : X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on meestal-mk5.stack.nl X-Spam-Level: X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00,J_CHICKENPOX_43, NO_RELAYS autolearn=no version=3.2.3 X-Spam-Relay-Country: Received: from snail.stack.nl (snail.stack.nl [IPv6:2001:610:1108:5010::131]) by mx1.stack.nl (Postfix) with ESMTP id 9707F3F698; Sun, 22 Mar 2009 22:47:54 +0100 (CET) Received: by snail.stack.nl (Postfix, from userid 1677) id E07BD22892; Sun, 22 Mar 2009 22:47:41 +0100 (CET) Date: Sun, 22 Mar 2009 22:47:41 +0100 From: Jilles Tjoelker To: Wesley Shields Message-ID: <20090322214741.GA50879@stack.nl> References: <20090322144753.GA48259@atarininja.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20090322144753.GA48259@atarininja.org> X-Operating-System: FreeBSD 7.1-PRERELEASE i386 User-Agent: Mutt/1.5.18 (2008-05-17) Cc: standards@freebsd.org Subject: Re: FW: shell choice freebsd git port X-BeenThere: freebsd-standards@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Standards compliance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Mar 2009 22:04:00 -0000 On Sun, Mar 22, 2009 at 10:47:53AM -0400, Wesley Shields wrote: > As the maintainer of devel/git I'd like this port to do the right thing, > but I'm not sure if this is a legitimate bug in our /bin/sh or not. > Anyone care to comment on this? > ----- Forwarded message from Jeff King ----- > Date: Sun, 22 Mar 2009 05:37:10 -0400 > From: Jeff King > To: wxs@freebsd.org > Subject: shell choice freebsd git port > Hi, > I'm one of the upstream developers of git, and it looks like you are the > git ports maintainer for FreeBSD. I wanted to discuss an issue which you > may run into while packaging git 1.6.2.1. > It seems that FreeBSD's /bin/sh treats blank lines in an eval as a > successful command. E.g., (the output is from FreeBSD 6.1, but I built > the current HEAD from anoncvs and it seems to have the same problem): > $ /bin/sh > $ eval 'false > > ' > $ echo $? > 0 > (whereas bash and dash would print '1'). > This is problematic for our test suite, which consists of a lot of > eval'ing. Failing tests may be missed if their status is ignored, one > test in 1.6.2.1 which expects a non-zero exit status actually does > report failure when it actually succeeded. On top of that, some of the > scripts (like bisect and filter-branch) care about the exit status of > evals at run-time to determine whether an error occurred. > There is some discussion on the git list here: > http://thread.gmane.org/gmane.comp.version-control.git/112519/focus=112621 > I don't know if you want to do anything to the port to work around this. > The obvious solution is requiring bash, and setting SHELL_PATH > appropriately in the Makefile. You may also want to see if anyone is > interested in treating this like a bug in /bin/sh and fixing it (I > consider it a bug, but others may consider it historical behavior, I > suppose). As discussed on IRC, I think this is a bug in /bin/sh. Just from reading the code, NetBSD does not seem to have fixed this. The following patch seems to fix the problem: http://www.stack.nl/~jilles/unix/sh-eval-emptyline.patch Apart from 'eval', also 'trap', 'fc' and strings passed with '-c' are affected. Empty lines inside {}, if or similar constructs are treated differently and work fine even without the patch. -- Jilles Tjoelker From owner-freebsd-standards@FreeBSD.ORG Sun Mar 22 22:32:02 2009 Return-Path: Delivered-To: freebsd-standards@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BA137106564A for ; Sun, 22 Mar 2009 22:32:02 +0000 (UTC) (envelope-from stefan@fafoe.narf.at) Received: from viefep16-int.chello.at (viefep16-int.chello.at [62.179.121.36]) by mx1.freebsd.org (Postfix) with ESMTP id F0A318FC13 for ; Sun, 22 Mar 2009 22:32:01 +0000 (UTC) (envelope-from stefan@fafoe.narf.at) Received: from edge01.upc.biz ([192.168.13.236]) by viefep18-int.chello.at (InterMail vM.7.09.01.00 201-2219-108-20080618) with ESMTP id <20090322221542.XKFP28039.viefep18-int.chello.at@edge01.upc.biz>; Sun, 22 Mar 2009 23:15:42 +0100 Received: from lizard.fafoe.narf.at ([213.47.85.26]) by edge01.upc.biz with edge id WNFh1b00l0a5KZh01NFi2A; Sun, 22 Mar 2009 23:15:42 +0100 X-SourceIP: 213.47.85.26 Received: by lizard.fafoe.narf.at (Postfix, from userid 1001) id 08498B9F2; Sun, 22 Mar 2009 23:15:40 +0100 (CET) Date: Sun, 22 Mar 2009 23:15:40 +0100 From: Stefan Farfeleder To: Jilles Tjoelker Message-ID: <20090322221540.GA1269@lizard.fafoe.narf.at> Mail-Followup-To: Jilles Tjoelker , Oliver Fromme , freebsd-standards@FreeBSD.ORG References: <200903181213.n2ICDPpT042350@lurza.secnetix.de> <200903191412.n2JECdbl011120@lurza.secnetix.de> <20090321214634.GA36395@stack.nl> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20090321214634.GA36395@stack.nl> User-Agent: Mutt/1.5.17 (2007-11-01) Cc: freebsd-standards@FreeBSD.ORG, Oliver Fromme Subject: Re: Suspecting bug in /bin/sh's IFS X-BeenThere: freebsd-standards@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Standards compliance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Mar 2009 22:32:03 -0000 On Sat, Mar 21, 2009 at 10:46:34PM +0100, Jilles Tjoelker wrote: > > The code is wrong, but your patched code is also wrong. The read builtin > should use the same logic as normal field splitting, with additional > rules if there are more fields in the input than variables. > > I have noticed that NetBSD has already fixed this. I have ported these > fixes over: http://www.stack.nl/~jilles/unix/sh-read-split.patch > The patch is against RELENG_7, I hope it applies to -CURRENT as well. > > The NetBSD commit message also refers to > http://www.research.att.com/~gsf/public/ifs.sh > Just like their /bin/sh, our /bin/sh with the patch now passes the > 'read' tests from there (there are still many other failures though). > > By the way, to avoid all processing by read, one must IFS= read -r VAR. > Without the IFS specification, leading and trailing whitespace will > still be stripped. Thank you, I have committed this patch. From owner-freebsd-standards@FreeBSD.ORG Mon Mar 23 11:07:05 2009 Return-Path: Delivered-To: freebsd-standards@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DC9A6106566B for ; Mon, 23 Mar 2009 11:07:04 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id C98608FC2B for ; Mon, 23 Mar 2009 11:07:04 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n2NB74ra004163 for ; Mon, 23 Mar 2009 11:07:04 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n2NB74Fu004159 for freebsd-standards@FreeBSD.org; Mon, 23 Mar 2009 11:07:04 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 23 Mar 2009 11:07:04 GMT Message-Id: <200903231107.n2NB74Fu004159@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-standards@FreeBSD.org Cc: Subject: Current problem reports assigned to freebsd-standards@FreeBSD.org X-BeenThere: freebsd-standards@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Standards compliance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Mar 2009 11:07:05 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o stand/130067 standards Wrong numeric limits in system headers? o stand/129554 standards lp(1) [patch] Implement -m and -t options o stand/129524 standards FreeBSD 7.0 isnt detecting my hardrives with raid5 o stand/128546 standards ls -p does not follow symlinks o bin/125855 standards sh(1) allows for multiline, non-escaped control struct o stand/124860 standards flockfile(3) doesn't work when the memory has been exh o stand/123688 standards POSIX standard changes in unistd.h and grp.h o stand/121921 standards [patch] Add leap second support to at(1), atrun(8) o stand/121568 standards [patch] ln(1): wrong "ln -s" behaviour o stand/120947 standards xsm ignores system.xsm and .xsmstartup o stand/119804 standards [locale] [patch] Invalid (long)date format in pl_PL.IS o stand/116826 standards [patch] sh support for POSIX character classes o stand/116477 standards rm(1): rm behaves unexpectedly when using -r and relat o bin/116413 standards incorrect getconf(1) handling of unsigned constants gi o stand/116081 standards make does not work with the directive sinclude p stand/107561 standards [libc] [patch] [request] Missing SUS function tcgetsid o stand/104743 standards [headers] [patch] Wrong values for _POSIX_ minimal lim o stand/100017 standards [Patch] Add fuser(1) functionality to fstat(1) o stand/96236 standards [patch] [posix] sed(1) incorrectly describes a functio o stand/96016 standards [headers] clock_getres et al should be in o stand/94729 standards [libc] fcntl() throws undocumented ENOTTY o kern/93705 standards [headers] [patch] ENODATA and EGREGIOUS (for glibc com o stand/92362 standards [headers] [patch] Missing SIGPOLL in kernel headers a stand/86484 standards [patch] mkfifo(1) uses wrong permissions o stand/83845 standards [libm] [patch] add log2() and log2f() support for libm o stand/82654 standards C99 long double math functions are missing o stand/81287 standards [patch] fingerd(8) might send a line not ending in CRL a stand/80293 standards sysconf() does not support well-defined unistd values o stand/79056 standards [feature request] [atch] regex(3) regression tests o stand/70813 standards [patch] ls(1) not Posix compliant o stand/66357 standards make POSIX conformance problem ('sh -e' & '+' command- s kern/64875 standards [libc] [patch] [request] add a system call: fdatasync( s stand/62858 standards malloc(0) not C99 compliant o stand/56476 standards cd9660 unicode support simple hack p stand/55112 standards glob.h, glob_t's gl_pathc should be "size_t", not "int o stand/54839 standards [pcvt] pcvt deficits o stand/54833 standards [pcvt] more pcvt deficits o stand/54410 standards one-true-awk not POSIX compliant (no extended REs) o stand/46119 standards Priority problems for SCHED_OTHER using pthreads o stand/44425 standards getcwd() succeeds even if current dir has perm 000. p stand/41576 standards POSIX compliance of ln(1) o stand/39256 standards snprintf/vsnprintf aren't POSIX-conformant for strings s stand/36076 standards Implementation of POSIX fuser command o kern/27835 standards [libc] execve() doesn't conform to execve(2) spec in s a docs/26003 standards getgroups(2) lists NGROUPS_MAX but not syslimits.h o stand/25777 standards [kernel] [patch] atime not updated on exec o bin/25542 standards sh(1) null char in quoted string s stand/24590 standards timezone function not compatible witn Single Unix Spec o bin/24390 standards ln(1) Replacing old dir-symlinks when using /bin/ln o stand/21519 standards sys/dir.h should be deprecated some more s bin/14925 standards getsubopt isn't poisonous enough 51 problems total. From owner-freebsd-standards@FreeBSD.ORG Tue Mar 24 10:55:57 2009 Return-Path: Delivered-To: freebsd-standards@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CA1F81065675 for ; Tue, 24 Mar 2009 10:55:57 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (lurza.secnetix.de [IPv6:2a01:170:102f::2]) by mx1.freebsd.org (Postfix) with ESMTP id 48A998FC1C for ; Tue, 24 Mar 2009 10:55:57 +0000 (UTC) (envelope-from olli@lurza.secnetix.de) Received: from lurza.secnetix.de (localhost [127.0.0.1]) by lurza.secnetix.de (8.14.3/8.14.3) with ESMTP id n2OAtRZ3035648; Tue, 24 Mar 2009 11:55:54 +0100 (CET) (envelope-from oliver.fromme@secnetix.de) Received: (from olli@localhost) by lurza.secnetix.de (8.14.3/8.14.3/Submit) id n2OAtQKr035646; Tue, 24 Mar 2009 11:55:26 +0100 (CET) (envelope-from olli) From: Oliver Fromme Message-Id: <200903241055.n2OAtQKr035646@lurza.secnetix.de> To: stefan@fafoe.narf.at (Stefan Farfeleder) Date: Tue, 24 Mar 2009 11:55:26 +0100 (CET) In-Reply-To: <20090322221540.GA1269@lizard.fafoe.narf.at> X-Mailer: ELM [version 2.5 PL8] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.1.2 (lurza.secnetix.de [127.0.0.1]); Tue, 24 Mar 2009 11:55:54 +0100 (CET) Cc: freebsd-standards@FreeBSD.ORG, Jilles Tjoelker Subject: Re: Suspecting bug in /bin/sh's IFS X-BeenThere: freebsd-standards@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Standards compliance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Mar 2009 10:55:58 -0000 Stefan Farfeleder wrote: > Jilles Tjoelker wrote: > > The code is wrong, but your patched code is also wrong. The read builtin > > should use the same logic as normal field splitting, with additional > > rules if there are more fields in the input than variables. > > > > I have noticed that NetBSD has already fixed this. I have ported these > > fixes over: http://www.stack.nl/~jilles/unix/sh-read-split.patch > > The patch is against RELENG_7, I hope it applies to -CURRENT as well. > > > > The NetBSD commit message also refers to > > http://www.research.att.com/~gsf/public/ifs.sh > > Just like their /bin/sh, our /bin/sh with the patch now passes the > > 'read' tests from there (there are still many other failures though). > > > > By the way, to avoid all processing by read, one must IFS= read -r VAR. > > Without the IFS specification, leading and trailing whitespace will > > still be stripped. > > Thank you, I have committed this patch. Cool, thanks! -- Oliver Fromme, secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing b. M. Handelsregister: Registergericht Muenchen, HRA 74606, Geschäftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsregister: Registergericht Mün- chen, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen, -Produkte und mehr: http://www.secnetix.de/bsd "A misleading benchmark test can accomplish in minutes what years of good engineering can never do." -- Dilbert (2009-03-02)