From owner-freebsd-standards@FreeBSD.ORG Mon Jun 25 11:07:29 2012 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 D871310656EB for ; Mon, 25 Jun 2012 11:07:29 +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 A89BE8FC23 for ; Mon, 25 Jun 2012 11:07: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 q5PB7T3N078474 for ; Mon, 25 Jun 2012 11:07:29 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q5PB7Tof078472 for freebsd-standards@FreeBSD.org; Mon, 25 Jun 2012 11:07:29 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 25 Jun 2012 11:07:29 GMT Message-Id: <201206251107.q5PB7Tof078472@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, 25 Jun 2012 11:07:30 -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/166349 standards Support the assignment-allocation character for fscanf o stand/165236 standards The NONE Wi-Fi regulatory restricts use of channels 12 o stand/164787 standards dirfd() function not available when _POSIX_C_SOURCE is o kern/164674 standards [patch] [libc] vfprintf/vfwprintf return error (EOF) o o stand/162434 standards getaddrinfo: addrinfo.ai_family is an address family, o stand/154842 standards invalid request authenticator in the second and subseq o stand/150093 standards C++ std::locale support is broken o stand/130067 standards Wrong numeric limits in system headers? o stand/124860 standards flockfile(3) doesn't work when the memory has been exh o stand/121921 standards [patch] Add leap second support to at(1), atrun(8) 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/100017 standards [Patch] Add fuser(1) functionality to fstat(1) a stand/86484 standards [patch] mkfifo(1) uses wrong permissions 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( o stand/56476 standards [patch] cd9660 unicode support simple hack 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/44365 standards [headers] [patch] [request] introduce ulong and unchar a stand/41576 standards ln(1): replacing old dir-symlinks a docs/26003 standards getgroups(2) lists NGROUPS_MAX but not syslimits.h s stand/24590 standards timezone function not compatible witn Single Unix Spec o stand/21519 standards sys/dir.h should be deprecated some more s bin/14925 standards getsubopt isn't poisonous enough 32 problems total. From owner-freebsd-standards@FreeBSD.ORG Thu Jun 28 06:26:42 2012 Return-Path: Delivered-To: freebsd-standards@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 07F44106566B; Thu, 28 Jun 2012 06:26:42 +0000 (UTC) (envelope-from eadler@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id CEBD38FC08; Thu, 28 Jun 2012 06:26:41 +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 q5S6Qfml073625; Thu, 28 Jun 2012 06:26:41 GMT (envelope-from eadler@freefall.freebsd.org) Received: (from eadler@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q5S6QfDn073621; Thu, 28 Jun 2012 06:26:41 GMT (envelope-from eadler) Date: Thu, 28 Jun 2012 06:26:41 GMT Message-Id: <201206280626.q5S6QfDn073621@freefall.freebsd.org> To: eadler@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-standards@FreeBSD.org From: eadler@FreeBSD.org Cc: Subject: Re: bin/169500: expr(1) improperly requires forward slash to be escaped 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: Thu, 28 Jun 2012 06:26:42 -0000 Synopsis: expr(1) improperly requires forward slash to be escaped Responsible-Changed-From-To: freebsd-bugs->freebsd-standards Responsible-Changed-By: eadler Responsible-Changed-When: Thu Jun 28 06:25:59 UTC 2012 Responsible-Changed-Why: over to you http://www.freebsd.org/cgi/query-pr.cgi?pr=169500 From owner-freebsd-standards@FreeBSD.ORG Thu Jun 28 17:22:45 2012 Return-Path: Delivered-To: freebsd-standards@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7E92C106566C; Thu, 28 Jun 2012 17:22:45 +0000 (UTC) (envelope-from wollman@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 505E48FC0C; Thu, 28 Jun 2012 17:22:45 +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 q5SHMjeX001548; Thu, 28 Jun 2012 17:22:45 GMT (envelope-from wollman@freefall.freebsd.org) Received: (from wollman@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q5SHMiLE001544; Thu, 28 Jun 2012 17:22:44 GMT (envelope-from wollman) Date: Thu, 28 Jun 2012 17:22:44 GMT Message-Id: <201206281722.q5SHMiLE001544@freefall.freebsd.org> To: rfg@tristatelogic.com, wollman@FreeBSD.org, freebsd-standards@FreeBSD.org From: wollman@FreeBSD.org Cc: Subject: Re: bin/169500: expr(1) improperly requires forward slash to be escaped 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: Thu, 28 Jun 2012 17:22:45 -0000 Synopsis: expr(1) improperly requires forward slash to be escaped State-Changed-From-To: open->closed State-Changed-By: wollman State-Changed-When: Thu Jun 28 17:21:35 UTC 2012 State-Changed-Why: expr(1) behaves as the Standard says it is supposed to. '/' is an operator and thus not parsed as a possible string value. http://www.freebsd.org/cgi/query-pr.cgi?pr=169500 From owner-freebsd-standards@FreeBSD.ORG Thu Jun 28 22:20:13 2012 Return-Path: Delivered-To: freebsd-standards@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9CEAA106564A for ; Thu, 28 Jun 2012 22:20:13 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 843688FC0C for ; Thu, 28 Jun 2012 22:20:13 +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 q5SMKDMi069885 for ; Thu, 28 Jun 2012 22:20:13 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q5SMKDVs069884; Thu, 28 Jun 2012 22:20:13 GMT (envelope-from gnats) Date: Thu, 28 Jun 2012 22:20:13 GMT Message-Id: <201206282220.q5SMKDVs069884@freefall.freebsd.org> To: freebsd-standards@FreeBSD.org From: "Ronald F. Guilmette" Cc: Subject: Re: bin/169500: /bin/expr improperly requires forward slash to be escaped X-BeenThere: freebsd-standards@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: "Ronald F. Guilmette" List-Id: Standards compliance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Jun 2012 22:20:13 -0000 The following reply was made to PR bin/169500; it has been noted by GNATS. From: "Ronald F. Guilmette" To: Garrett Wollman Cc: freebsd-gnats-submit@freebsd.org Subject: Re: bin/169500: /bin/expr improperly requires forward slash to be escaped Date: Thu, 28 Jun 2012 15:11:55 -0700 In message <201206280136.q5S1aOQO093902@hergotha.csail.mit.edu>, you wrote: >In article <20120627214105.A1EA35081B@segfault.tristatelogic.com>, >rfg@tristatelogic.com writes: > >>According to my reading of Sections 2.8.3.1.1 and 2.8.3.1.2 of the ANSI/IEEE >>standard 1003.2, a forward slash character (/) is an "ordinary" basic >>regular expression (BRE) character, and as such can be used in a BRE alone >>to match itself. > >IEEE Std.1003.2 was obsoleted by the publication of IEEE >Std.1003.1-2001; your reference is at least fifteen years old. Yes. My bad. Sorry. (These publications are quite expensive, as you may know, and thus, I have not updated mine in quite some time.) >>As far as I can tell, backslash-escaping of this specific character >>should not be required within BREs. > >Nothing to do with the BRE-ness. As the 2001 edition of the standard >states (page 429, lines 16598-16599): > > A string argument is an argument that cannot be identified as > an integer argument or as one of the expression operator > symbols shown in the OPERANDS section. Humm... OK. How do I retract my PR? From owner-freebsd-standards@FreeBSD.ORG Thu Jun 28 22:28:03 2012 Return-Path: Delivered-To: freebsd-standards@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D98D1106564A for ; Thu, 28 Jun 2012 22:28:03 +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 5BA698FC0A for ; Thu, 28 Jun 2012 22:28:03 +0000 (UTC) Received: by bkwj5 with SMTP id j5so1182532bkw.13 for ; Thu, 28 Jun 2012 15:28:02 -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=1JItDsVTzdVrJGUUCm2Qq2cQyctgS2w6f+VtuQKoHNE=; b=Hy9DH6oK0ZAS5zIf9XeojJNGLTLGk1jvL+iDLgH1dmuaEQNbu2pwRYl1zkgfdwmJXL 0jAB1FSd6UfDtlQ44PN8amGaV6oZ/EiT32BsF6RO1f8Lvy+jv6mV9ul1VHVit2HO1ycr h5XmKhE21PSVrvDHa9tWdRnI8UoyzAUPmi9eX/C404dPIIFb6MPMseY7jGzij0Wl6OOE ZMJatFsGY8HgMvCJ5pGEB4nIxdCVO6CnZSqz1/VcLVTq8VUR1CbQ540kO4qGDKoH4npc 6WJyAKGbm8Z+9p/8borSvm46698rHDDzGONlUh/c1EyNvXFiVljAuuD+rSTrR6eNhG0u +sEg== Received: by 10.204.152.13 with SMTP id e13mr2192157bkw.46.1340922482312; Thu, 28 Jun 2012 15:28:02 -0700 (PDT) MIME-Version: 1.0 Sender: utisoft@gmail.com Received: by 10.204.49.87 with HTTP; Thu, 28 Jun 2012 15:27:32 -0700 (PDT) In-Reply-To: <201206282220.q5SMKDVs069884@freefall.freebsd.org> References: <201206282220.q5SMKDVs069884@freefall.freebsd.org> From: Chris Rees Date: Thu, 28 Jun 2012 23:27:32 +0100 X-Google-Sender-Auth: yLNAfyhe5AV-NJOxaJFKMTg94D8 Message-ID: To: "Ronald F. Guilmette" Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-standards@freebsd.org Subject: Re: bin/169500: /bin/expr improperly requires forward slash to be escaped 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: Thu, 28 Jun 2012 22:28:03 -0000 On 28 June 2012 23:20, Ronald F. Guilmette wrote: > The following reply was made to PR bin/169500; it has been noted by GNATS= . > > From: "Ronald F. Guilmette" > To: Garrett Wollman > Cc: freebsd-gnats-submit@freebsd.org > Subject: Re: bin/169500: /bin/expr improperly requires forward slash to b= e escaped > Date: Thu, 28 Jun 2012 15:11:55 -0700 > > =A0In message <201206280136.q5S1aOQO093902@hergotha.csail.mit.edu>, you w= rote: > > =A0>In article <20120627214105.A1EA35081B@segfault.tristatelogic.com>, > =A0>rfg@tristatelogic.com writes: > =A0> > =A0>>According to my reading of Sections 2.8.3.1.1 and 2.8.3.1.2 of the A= NSI/IEEE > =A0>>standard 1003.2, a forward slash character (/) is an "ordinary" basi= c > =A0>>regular expression (BRE) character, and as such can be used in a BRE= alone > =A0>>to match itself. > =A0> > =A0>IEEE Std.1003.2 was obsoleted by the publication of IEEE > =A0>Std.1003.1-2001; your reference is at least fifteen years old. > > =A0Yes. =A0My bad. =A0Sorry. > > =A0(These publications are quite expensive, as you may know, and thus, I = have > =A0not updated mine in quite some time.) > > =A0>>As far as I can tell, backslash-escaping of this specific character > =A0>>should not be required within BREs. > =A0> > =A0>Nothing to do with the BRE-ness. =A0As the 2001 edition of the standa= rd > =A0>states (page 429, lines 16598-16599): > =A0> > =A0> =A0 =A0 =A0A string argument is an argument that cannot be identifie= d as > =A0> =A0 =A0 =A0an integer argument or as one of the expression operator > =A0> =A0 =A0 =A0symbols shown in the OPERANDS section. > > =A0Humm... OK. =A0How do I retract my PR? No need, it's closed. Don't worry about it :) Chris From owner-freebsd-standards@FreeBSD.ORG Thu Jun 28 22:34:31 2012 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 9BE27106566C for ; Thu, 28 Jun 2012 22:34:31 +0000 (UTC) (envelope-from wollman@khavrinen.csail.mit.edu) Received: from khavrinen.csail.mit.edu (khavrinen.csail.mit.edu [IPv6:2001:470:8b2d:1e1c:21b:21ff:feb8:d7b0]) by mx1.freebsd.org (Postfix) with ESMTP id 4D3D38FC12 for ; Thu, 28 Jun 2012 22:34:31 +0000 (UTC) Received: from khavrinen.csail.mit.edu (localhost [127.0.0.1]) by khavrinen.csail.mit.edu (8.14.5/8.14.5) with ESMTP id q5SMYUw8098411 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL CN=khavrinen.csail.mit.edu issuer=Client+20CA); Thu, 28 Jun 2012 18:34:30 -0400 (EDT) (envelope-from wollman@khavrinen.csail.mit.edu) Received: (from wollman@localhost) by khavrinen.csail.mit.edu (8.14.5/8.14.5/Submit) id q5SMYU4d098408; Thu, 28 Jun 2012 18:34:30 -0400 (EDT) (envelope-from wollman) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <20460.56310.495134.157954@khavrinen.csail.mit.edu> Date: Thu, 28 Jun 2012 18:34:30 -0400 From: Garrett Wollman To: "Ronald F. Guilmette" In-Reply-To: <201206282220.q5SMKDVs069884@freefall.freebsd.org> References: <201206282220.q5SMKDVs069884@freefall.freebsd.org> X-Mailer: VM 7.17 under 21.4 (patch 22) "Instant Classic" XEmacs Lucid X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (khavrinen.csail.mit.edu [127.0.0.1]); Thu, 28 Jun 2012 18:34:30 -0400 (EDT) Cc: freebsd-standards@freebsd.org Subject: Re: bin/169500: /bin/expr improperly requires forward slash to be escaped 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: Thu, 28 Jun 2012 22:34:31 -0000 < said: > (These publications are quite expensive, as you may know, and thus, I have > not updated mine in quite some time.) The current, complete POSIX specifications are available free by registration at . This is The Open Group's version of it; you can also pay lots of money to get a printed document from ISO (ISO/IEC 9945:2009) or IEEE (IEEE Std.1003.1-2008). -GAWollman