From owner-freebsd-standards@FreeBSD.ORG Sun Jul 2 22:45:12 2006 Return-Path: X-Original-To: freebsd-standards@FreeBSD.org Delivered-To: freebsd-standards@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B3E5D16A415 for ; Sun, 2 Jul 2006 22:45:12 +0000 (UTC) (envelope-from pfgshield-freebsd@yahoo.com) Received: from web32707.mail.mud.yahoo.com (web32707.mail.mud.yahoo.com [68.142.207.251]) by mx1.FreeBSD.org (Postfix) with SMTP id 3BE4C44514 for ; Sun, 2 Jul 2006 22:45:12 +0000 (GMT) (envelope-from pfgshield-freebsd@yahoo.com) Received: (qmail 26750 invoked by uid 60001); 2 Jul 2006 22:45:10 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type; b=xa9pKM6847CebOppVqL+pLCrUZzbu0xyYNMYIp3iIrfM2PRlGKXDUTo6kSCOLONvYCy5SCc6Hf7z/CoNEomB5bhI5QxgZkAaoJSe6ZgYqG47ABgkSTP7IBk6eVr6iCcWMenbQndkm5yMmoBjKz4VMbTM1Hycl+nrnxc4REHVWfQ= ; Message-ID: <20060702224510.26748.qmail@web32707.mail.mud.yahoo.com> Received: from [69.79.130.177] by web32707.mail.mud.yahoo.com via HTTP; Mon, 03 Jul 2006 00:45:10 CEST Date: Mon, 3 Jul 2006 00:45:10 +0200 (CEST) From: To: freebsd-standards@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Cc: Subject: BeleniX enhances to FreeBSD's math lib. X-BeenThere: freebsd-standards@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: pfgshield-freebsd@yahoo.com List-Id: Standards compliance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Jul 2006 22:45:12 -0000 Hi; Due to some initial license restirctions on the OpenSolaris source code, SchilliX did a port of FreeBSD's libm that was adopted by the other OpenSolaris ditributions. BeleniX did some updates recently to make the math lib more compatible with SUN's: http://sarovar.org/projects/belenix/ Moinak Ghosh kindly sent me a small tarball with changes to infinity.c (it's in libc on FreeBSD but in libm on Solaris) and some updates to libm. He also previously mentioned: "I can remember off the top of my head is the addition of isinf* and nan* functions. The nan* functions are wrappers over the strto* functions." These are part of the C99 & POSIX Conformance Project todo list. Unfortunately I won't be able to look at this stuff as my house was broken into and my computer stolen, I sent a copy to das@ and bde@ but if someone is interested in taking over, I'll be glad to send a copy of the BeleniX patches that survived. cheers, Pedro. Chiacchiera con i tuoi amici in tempo reale! http://it.yahoo.com/mail_it/foot/*http://it.messenger.yahoo.com From owner-freebsd-standards@FreeBSD.ORG Mon Jul 3 11:03:16 2006 Return-Path: X-Original-To: freebsd-standards@freebsd.org Delivered-To: freebsd-standards@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3468C16A6FF for ; Mon, 3 Jul 2006 11:03:16 +0000 (UTC) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id E832643D45 for ; Mon, 3 Jul 2006 11:03:15 +0000 (GMT) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (peter@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k63B3Fnk069997 for ; Mon, 3 Jul 2006 11:03:15 GMT (envelope-from owner-bugmaster@freebsd.org) Received: (from peter@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k63B3E6B069991 for freebsd-standards@freebsd.org; Mon, 3 Jul 2006 11:03:14 GMT (envelope-from owner-bugmaster@freebsd.org) Date: Mon, 3 Jul 2006 11:03:14 GMT Message-Id: <200607031103.k63B3E6B069991@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: peter set sender to owner-bugmaster@freebsd.org using -f From: FreeBSD bugmaster To: freebsd-standards@FreeBSD.org Cc: Subject: Current problem reports assigned to you 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, 03 Jul 2006 11:03:16 -0000 Current FreeBSD problem reports Critical problems Serious problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2001/03/05] bin/25542 standards /bin/sh: null char in quoted string o [2002/12/13] kern/46239 standards posix semaphore implementation errors o [2003/07/12] standards/54410standards one-true-awk not POSIX compliant (no exte o [2005/06/25] standards/82654standards C99 long double math functions are missin o [2006/03/20] standards/94729standards fcntl() throws undocumented ENOTTY 5 problems total. Non-critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- o [2000/09/24] bin/21519 standards sys/dir.h should be deprecated some more o [2001/01/16] bin/24390 standards Replacing old dir-symlinks when using /bi s [2001/01/24] standards/24590standards timezone function not compatible witn Sin s [2001/06/18] kern/28260 standards UIO_MAXIOV needs to be made public s [2002/03/19] standards/36076standards Implementation of POSIX fuser command s [2002/05/07] standards/37843standards manual for pthread_setschedparam(3) is wr o [2002/06/14] standards/39256standards snprintf/vsnprintf aren't POSIX-conforman p [2002/08/12] standards/41576standards POSIX compliance of ln(1) o [2002/10/23] standards/44425standards getcwd() succeeds even if current dir has o [2002/12/09] standards/46119standards Priority problems for SCHED_OTHER using p o [2003/07/25] standards/54833standards [pcvt] more pcvt deficits o [2003/07/25] standards/54839standards [pcvt] pcvt deficits p [2003/07/31] standards/55112standards glob.h, glob_t's gl_pathc should be "size o [2003/09/05] standards/56476standards cd9660 unicode support simple hack o [2003/10/29] standards/58676standards grantpt(3) alters storage used by ptsname s [2004/02/14] standards/62858standards malloc(0) not C99 compliant s [2004/03/29] kern/64875 standards [libc] [patch] [feature request] add a sy o [2004/05/07] standards/66357standards make POSIX conformance problem ('sh -e' & o [2004/05/11] standards/66531standards _gettemp uses a far smaller set of filena o [2004/08/22] standards/70813standards [PATCH] ls(1) not Posix compliant o [2004/09/22] standards/72006standards floating point formating in non-C locales o [2005/03/20] standards/79056standards regex(3) regression tests a [2005/04/23] standards/80293standards sysconf() does not support well-defined u o [2005/05/20] standards/81287standards [PATCH]: fingerd(8) might send a line not o [2005/07/21] standards/83845standards [libm] [patch] add log2() and log2f() sup o [2005/08/18] standards/85080standards output of long double subnormals (with pr o [2006/01/26] standards/92360standards [headers] [patch] Missing TAB3 in kernel o [2006/01/26] standards/92362standards [headers] [patch] Missing SIGPOLL in kern o [2006/02/22] kern/93705 standards [headers] [patch] ENODATA and EGREGIOUS ( o [2006/04/18] standards/96016standards clock_getres et al should be in o [2006/04/23] standards/96236standards [PATCH] [POSIX] sed.1 incorrectly describ o [2006/06/27] standards/99517standards Missing SIGRTMIN and SIGRTMAX signals 32 problems total. From owner-freebsd-standards@FreeBSD.ORG Fri Jul 7 01:20:26 2006 Return-Path: X-Original-To: freebsd-standards@hub.freebsd.org Delivered-To: freebsd-standards@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 963E616A4DD for ; Fri, 7 Jul 2006 01:20:26 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 10A3B43D45 for ; Fri, 7 Jul 2006 01:20:26 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k671KPVJ037151 for ; Fri, 7 Jul 2006 01:20:25 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k671KP77037150; Fri, 7 Jul 2006 01:20:25 GMT (envelope-from gnats) Date: Fri, 7 Jul 2006 01:20:25 GMT Message-Id: <200607070120.k671KP77037150@freefall.freebsd.org> To: freebsd-standards@FreeBSD.org From: Jim Luther Cc: Subject: Re: standards/66531: _gettemp uses a far smaller set of filenames than documented and doesn't range check inputs X-BeenThere: freebsd-standards@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Jim Luther List-Id: Standards compliance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Jul 2006 01:20:26 -0000 The following reply was made to PR standards/66531; it has been noted by GNATS. From: Jim Luther To: bug-followup@FreeBSD.org, luther.j@apple.com Cc: Subject: Re: standards/66531: _gettemp uses a far smaller set of filenames than documented and doesn't range check inputs Date: Thu, 6 Jul 2006 18:10:57 -0700 Hey, are you ever gonna take my patch? Mac OS X has been shipping with this for over a year now with no problems. From owner-freebsd-standards@FreeBSD.ORG Fri Jul 7 14:14:38 2006 Return-Path: X-Original-To: freebsd-standards@freebsd.org Delivered-To: freebsd-standards@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3011C16A4DD for ; Fri, 7 Jul 2006 14:14:38 +0000 (UTC) (envelope-from lchin@datatekcorp.com) Received: from mail.datatekcorp.com (mail.datatekcorp.com [68.167.242.188]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7C6EA43D7E for ; Fri, 7 Jul 2006 14:14:33 +0000 (GMT) (envelope-from lchin@datatekcorp.com) Received: from lchin.datatekcorp.com (proxy.datatekcorp.com [68.167.242.187]) by mail.datatekcorp.com (8.13.3+Sun/8.13.3) with ESMTP id k67EEN7j023354 for ; Fri, 7 Jul 2006 10:14:26 -0400 (EDT) Message-Id: <7.0.1.0.0.20060707101114.01bc9250@datatekcorp.com> X-Mailer: QUALCOMM Windows Eudora Version 7.0.1.0 Date: Fri, 07 Jul 2006 10:15:10 -0400 To: freebsd-standards@freebsd.org From: Lorraine Chin Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Subject: how to know what RFCs supported? 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: Fri, 07 Jul 2006 14:14:38 -0000 Is there a list of supported RFCs available for a given release of FreeBSD? We currently have FreeBSD 5.4 and our customer wants to know what RFCs we're compliant with. We can upgrade but it would only make sense if we knew what new RFCs we would get. Lorraine From owner-freebsd-standards@FreeBSD.ORG Fri Jul 7 17:08:37 2006 Return-Path: X-Original-To: freebsd-standards@freebsd.org Delivered-To: freebsd-standards@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1450C16A4DA for ; Fri, 7 Jul 2006 17:08:37 +0000 (UTC) (envelope-from joseph.koshy@gmail.com) Received: from nf-out-0910.google.com (nf-out-0910.google.com [64.233.182.189]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1A03143D45 for ; Fri, 7 Jul 2006 17:08:35 +0000 (GMT) (envelope-from joseph.koshy@gmail.com) Received: by nf-out-0910.google.com with SMTP id l37so168920nfc for ; Fri, 07 Jul 2006 10:08:34 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=eSHhsFTmzsVb1er5VnJ3aCfRKNCTJa46yZzG9lo97T70xNrOr+7Sav65yv5SVEUtlc6GlkmuE9Obva1KfXp+fIPUz/jQGYyg1S5IzxcaqpBsHY36H2niHdiMDqp/M3Op4TZ/vEZ+dVXzjQyNkp6PC1xGz/7sftOJvnZB0dmh8fo= Received: by 10.78.178.5 with SMTP id a5mr803427huf; Fri, 07 Jul 2006 10:08:34 -0700 (PDT) Received: by 10.78.50.15 with HTTP; Fri, 7 Jul 2006 10:08:34 -0700 (PDT) Message-ID: <84dead720607071008i7183e6a8uecb5dd6a56919c51@mail.gmail.com> Date: Fri, 7 Jul 2006 22:38:34 +0530 From: "Joseph Koshy" To: "Lorraine Chin" In-Reply-To: <7.0.1.0.0.20060707101114.01bc9250@datatekcorp.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <7.0.1.0.0.20060707101114.01bc9250@datatekcorp.com> Cc: freebsd-standards@freebsd.org Subject: Re: how to know what RFCs supported? 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: Fri, 07 Jul 2006 17:08:37 -0000 > Is there a list of supported RFCs available for a given > release of FreeBSD? > We currently have FreeBSD 5.4 and our customer wants to know > what RFCs we're compliant with. > We can upgrade but it would only make sense if we knew what > new RFCs we would get. Our release notes list the new RFCs supported in each release. Other than this we don't have a single comprehensive list of supported RFCs. Perhaps we need a standards(7) manual page that lists all standards-related status in a given release. -- FreeBSD Volunteer, http://people.freebsd.org/~jkoshy From owner-freebsd-standards@FreeBSD.ORG Fri Jul 7 19:24:02 2006 Return-Path: X-Original-To: freebsd-standards@freebsd.org Delivered-To: freebsd-standards@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1909C16A4DA for ; Fri, 7 Jul 2006 19:24:02 +0000 (UTC) (envelope-from jan.grant@bristol.ac.uk) Received: from dirg.bris.ac.uk (dirg.bris.ac.uk [137.222.10.102]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9166E43D73 for ; Fri, 7 Jul 2006 19:24:01 +0000 (GMT) (envelope-from jan.grant@bristol.ac.uk) Received: from mail.ilrt.bris.ac.uk ([137.222.16.62]) by dirg.bris.ac.uk with esmtp (Exim 4.60) (envelope-from ) id 1Fyvvi-0004G3-2Y for freebsd-standards@freebsd.org; Fri, 07 Jul 2006 20:24:00 +0100 Received: from cse-jg.cse.bris.ac.uk ([137.222.12.37]:50767) by mail.ilrt.bris.ac.uk with esmtps (TLSv1:AES256-SHA:256) (Exim 4.50) id 1Fyvvb-0002NT-Cm; Fri, 07 Jul 2006 20:23:57 +0100 Date: Fri, 7 Jul 2006 20:23:50 +0100 (BST) From: Jan Grant X-X-Sender: cmjg@tribble.ilrt.bris.ac.uk To: freebsd-standards@freebsd.org Message-ID: <20060707201402.T14116@tribble.ilrt.bris.ac.uk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spamassassin: mail.ilrt.bris.ac.uk X-Spam-Score: 0.0 X-Spam-Level: / X-Spam-Score: -1.4 X-Spam-Level: - Subject: stdio/sh behaviour guaranteed? 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: Fri, 07 Jul 2006 19:24:02 -0000 Consider the following snippet. [[[ #!/bin/sh echo one > t while read line do echo $line case $line in one) echo two >> t ;; two) echo three >> t ;; esac done X-Original-To: freebsd-standards@freebsd.org Delivered-To: freebsd-standards@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5490416A4DF for ; Fri, 7 Jul 2006 22:24:14 +0000 (UTC) (envelope-from keramida@ceid.upatras.gr) Received: from igloo.linux.gr (igloo.linux.gr [62.1.205.36]) by mx1.FreeBSD.org (Postfix) with ESMTP id 87EFC43D45 for ; Fri, 7 Jul 2006 22:24:12 +0000 (GMT) (envelope-from keramida@ceid.upatras.gr) Received: from gothmog.pc (host5.bedc.ondsl.gr [62.103.39.229]) (authenticated bits=128) by igloo.linux.gr (8.13.7/8.13.7/Debian-1) with ESMTP id k67MNnwu016586 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sat, 8 Jul 2006 01:23:50 +0300 Received: from gothmog.pc (gothmog [127.0.0.1]) by gothmog.pc (8.13.7/8.13.7) with ESMTP id k67MNhxQ010807; Sat, 8 Jul 2006 01:23:44 +0300 (EEST) (envelope-from keramida@ceid.upatras.gr) Received: (from giorgos@localhost) by gothmog.pc (8.13.7/8.13.7/Submit) id k67MNhfd010806; Sat, 8 Jul 2006 01:23:43 +0300 (EEST) (envelope-from keramida@ceid.upatras.gr) Date: Sat, 8 Jul 2006 01:23:43 +0300 From: Giorgos Keramidas To: Jan Grant Message-ID: <20060707222343.GA10756@gothmog.pc> References: <20060707201402.T14116@tribble.ilrt.bris.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060707201402.T14116@tribble.ilrt.bris.ac.uk> X-Hellug-MailScanner: Found to be clean X-Hellug-MailScanner-SpamCheck: not spam, SpamAssassin (score=-3.641, required 5, autolearn=not spam, ALL_TRUSTED -1.80, AWL 0.76, BAYES_00 -2.60) X-Hellug-MailScanner-From: keramida@ceid.upatras.gr X-Spam-Status: No Cc: freebsd-standards@freebsd.org Subject: Re: stdio/sh behaviour guaranteed? 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: Fri, 07 Jul 2006 22:24:14 -0000 On 2006-07-07 20:23, Jan Grant wrote: > Consider the following snippet. > > [[[ > #!/bin/sh > > echo one > t > while read line > do > echo $line > case $line in > one) echo two >> t > ;; > two) echo three >> t > ;; > esac > done ]]] > > This produces three lines of output on FreeBSD: which is what > I'd intuitively expect and it's certainly useful behaviour. > > I'm just trying to determine if that behaviour is one that I > can rely on - in other words, I guess, if stdio performs a > "short read" that fails to fill a buffer, and the underlying > file is then extended outside the process, will another attempt > to read from the FILE* (or a test of feof, say) honour the new, > longer file contents? I think that /bin/sh is not absolutely required to use stdio.h for input (which could pre-read some text and cause the above to fail). Having said that, I think it makes sense to assume that input is line-buffered, otherwise stuff like this could fail: cmd | while read line ; do echo "$line" ; done > And in particular, is the idiom above blessed by appropriate > posix standards? Not sure, but the behavior seems to be the same in Solaris too, with a variety of shells: | kobe % cat /etc/release | Solaris 10 1/06 s10x_u1wos_19a X86 | Copyright 2005 Sun Microsystems, Inc. All Rights Reserved. | Use is subject to license terms. | Assembled 07 December 2005 | kobe % pwd | /tmp/t | kobe % cat -n foo.sh | 1 #!/bin/sh | 2 | 3 echo one > t | 4 while read line | 5 do | 6 echo $line | 7 case $line in | 8 one) echo two >> t | 9 ;; | 10 two) echo three >> t | 11 ;; | 12 esac | 13 done X-Original-To: freebsd-standards@FreeBSD.org Delivered-To: freebsd-standards@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id ED79B16A4DA for ; Sat, 8 Jul 2006 01:05:50 +0000 (UTC) (envelope-from trhodes@FreeBSD.org) Received: from pittgoth.com (ns1.pittgoth.com [216.38.206.188]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9A7F943D45 for ; Sat, 8 Jul 2006 01:05:48 +0000 (GMT) (envelope-from trhodes@FreeBSD.org) Received: from localhost (ip70-177-190-239.dc.dc.cox.net [70.177.190.239]) (authenticated bits=0) by pittgoth.com (8.13.4/8.13.4) with ESMTP id k681Fll2040717 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 7 Jul 2006 21:15:48 -0400 (EDT) (envelope-from trhodes@FreeBSD.org) Date: Fri, 7 Jul 2006 21:05:39 -0400 From: Tom Rhodes To: "Joseph Koshy" Message-Id: <20060707210539.1e18457c.trhodes@FreeBSD.org> In-Reply-To: <84dead720607071008i7183e6a8uecb5dd6a56919c51@mail.gmail.com> References: <7.0.1.0.0.20060707101114.01bc9250@datatekcorp.com> <84dead720607071008i7183e6a8uecb5dd6a56919c51@mail.gmail.com> X-Mailer: Sylpheed version 1.0.6 (GTK+ 1.2.10; i386-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: lchin@datatekcorp.com, freebsd-standards@FreeBSD.org Subject: Re: how to know what RFCs supported? 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: Sat, 08 Jul 2006 01:05:51 -0000 On Fri, 7 Jul 2006 22:38:34 +0530 "Joseph Koshy" wrote: > > Is there a list of supported RFCs available for a given > > release of FreeBSD? > > > We currently have FreeBSD 5.4 and our customer wants to know > > what RFCs we're compliant with. > > > We can upgrade but it would only make sense if we knew what > > new RFCs we would get. > > Our release notes list the new RFCs supported in each release. > Other than this we don't have a single comprehensive list > of supported RFCs. Perhaps we need a standards(7) manual > page that lists all standards-related status in a given > release. Wow, that would be a big manual page if we're not careful. -- Tom Rhodes From owner-freebsd-standards@FreeBSD.ORG Sat Jul 8 02:28:07 2006 Return-Path: X-Original-To: freebsd-standards@freebsd.org Delivered-To: freebsd-standards@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EF1F116A4DA for ; Sat, 8 Jul 2006 02:28:07 +0000 (UTC) (envelope-from list@billxu.com) Received: from sina3-198.sina.net (sina3-199.sina.net [202.108.3.199]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1B21743D46 for ; Sat, 8 Jul 2006 02:28:06 +0000 (GMT) (envelope-from list@billxu.com) Received: (qmail 41498 invoked from network); 8 Jul 2006 02:28:06 -0000 Received: from unknown (HELO ?219.236.2.212?) (219.236.2.212) by 10.54.2.149 with SMTP; 8 Jul 2006 02:28:06 -0000 From: Bill Xu To: Joseph Koshy In-Reply-To: <84dead720607071008i7183e6a8uecb5dd6a56919c51@mail.gmail.com> References: <7.0.1.0.0.20060707101114.01bc9250@datatekcorp.com> <84dead720607071008i7183e6a8uecb5dd6a56919c51@mail.gmail.com> Content-Type: text/plain; charset=utf-8 Organization: BILLXU.COM Date: Sat, 08 Jul 2006 10:27:55 +0800 Message-Id: <1152325675.1192.15.camel@zeuux.zeuux.com> Mime-Version: 1.0 X-Mailer: Evolution 2.6.2 FreeBSD GNOME Team Port Content-Transfer-Encoding: 8bit Cc: Lorraine Chin , freebsd-standards@freebsd.org Subject: Re: how to know what RFCs supported? 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: Sat, 08 Jul 2006 02:28:08 -0000 It's a good advice. ;) 在 2006-07-07五的 22:38 +0530，Joseph Koshy写道： > > Is there a list of supported RFCs available for a given > > release of FreeBSD? > > > We currently have FreeBSD 5.4 and our customer wants to know > > what RFCs we're compliant with. > > > We can upgrade but it would only make sense if we knew what > > new RFCs we would get. > > Our release notes list the new RFCs supported in each release. > Other than this we don't have a single comprehensive list > of supported RFCs. Perhaps we need a standards(7) manual > page that lists all standards-related status in a given > release. > From owner-freebsd-standards@FreeBSD.ORG Sat Jul 8 02:49:23 2006 Return-Path: X-Original-To: freebsd-standards@freebsd.org Delivered-To: freebsd-standards@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 52A0F16A4DD for ; Sat, 8 Jul 2006 02:49:23 +0000 (UTC) (envelope-from bde@zeta.org.au) Received: from mailout2.pacific.net.au (mailout2.pacific.net.au [61.8.0.115]) by mx1.FreeBSD.org (Postfix) with ESMTP id B669943D45 for ; Sat, 8 Jul 2006 02:49:22 +0000 (GMT) (envelope-from bde@zeta.org.au) Received: from mailproxy1.pacific.net.au (mailproxy1.pacific.net.au [61.8.2.162]) by mailout2.pacific.net.au (Postfix) with ESMTP id C1E2D6E058; Sat, 8 Jul 2006 12:49:21 +1000 (EST) Received: from katana.zip.com.au (katana.zip.com.au [61.8.7.246]) by mailproxy1.pacific.net.au (8.13.4/8.13.4/Debian-3sarge1) with ESMTP id k682nFul000664; Sat, 8 Jul 2006 12:49:19 +1000 Date: Sat, 8 Jul 2006 12:49:15 +1000 (EST) From: Bruce Evans X-X-Sender: bde@delplex.bde.org To: Giorgos Keramidas In-Reply-To: <20060707222343.GA10756@gothmog.pc> Message-ID: <20060708120806.U6238@delplex.bde.org> References: <20060707201402.T14116@tribble.ilrt.bris.ac.uk> <20060707222343.GA10756@gothmog.pc> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Jan Grant , freebsd-standards@freebsd.org Subject: Re: stdio/sh behaviour guaranteed? 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: Sat, 08 Jul 2006 02:49:23 -0000 On Sat, 8 Jul 2006, Giorgos Keramidas wrote: > On 2006-07-07 20:23, Jan Grant wrote: >> Consider the following snippet. >> >> [[[ >> #!/bin/sh >> >> echo one > t >> while read line >> do >> echo $line >> case $line in >> one) echo two >> t >> ;; >> two) echo three >> t >> ;; >> esac >> done > ]]] >> >> This produces three lines of output on FreeBSD: which is what >> I'd intuitively expect and it's certainly useful behaviour. >> >> I'm just trying to determine if that behaviour is one that I >> can rely on - in other words, I guess, if stdio performs a >> "short read" that fails to fill a buffer, and the underlying >> file is then extended outside the process, will another attempt >> to read from the FILE* (or a test of feof, say) honour the new, >> longer file contents? > > I think that /bin/sh is not absolutely required to use stdio.h > for input (which could pre-read some text and cause the above to > fail). Having said that, I think it makes sense to assume that > input is line-buffered, otherwise stuff like this could fail: > > cmd | while read line ; do echo "$line" ; done Using stdio for input from pipelines in shells is almost absolutely not possible, since stdio normally does buffering and any buffering breaks pipelines since there is no way to unread characters from a pipe. E.g.: printf "%s\n%s\n" foo bar | sh -c 'read x; echo $$: $x; sh -c "read y; echo \$$: \$y"' This reads "foo\n" in the first shell and "bar\n" in the second shell, and prints the results (after discarding the newlines) with process numbers so that you can see that the reads were done by separate processes. For this to work, the first shell must not read beyond "foo\n". Line buffering might work, but stdio's line buffering only applies to output, and to do input line buffering stdio would have to do the same as shells -- it would have to read a character at a time up to a newline. I think stdio never does this, and shells use their own one-char-at a time input routine for pipes. I think some shells optimize the case of input from seekable files by using buffered reads for such files only, with lseek() to unread input. Stdio might be useable for this. This depends on the file not changing too much underneath. Changes to the file in advance of the current EOF should if if the implementation doesn't do anything stupid. >> And in particular, is the idiom above blessed by appropriate >> posix standards? Stuff like this has to work to satisfy at least defacto standards. Bruce From owner-freebsd-standards@FreeBSD.ORG Sat Jul 8 09:09:32 2006 Return-Path: X-Original-To: freebsd-standards@freebsd.org Delivered-To: freebsd-standards@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4A70616A4DE for ; Sat, 8 Jul 2006 09:09:32 +0000 (UTC) (envelope-from jan.grant@bristol.ac.uk) Received: from diri.bris.ac.uk (diri.bris.ac.uk [137.222.10.112]) by mx1.FreeBSD.org (Postfix) with ESMTP id D3BB443D4C for ; Sat, 8 Jul 2006 09:09:31 +0000 (GMT) (envelope-from jan.grant@bristol.ac.uk) Received: from mail.ilrt.bris.ac.uk ([137.222.16.62]) by diri.bris.ac.uk with esmtp (Exim 4.60) (envelope-from ) id 1Fz8ob-0000ji-1l; Sat, 08 Jul 2006 10:09:30 +0100 Received: from cse-jg.cse.bris.ac.uk ([137.222.12.37]:64462) by mail.ilrt.bris.ac.uk with esmtps (TLSv1:AES256-SHA:256) (Exim 4.50) id 1Fz8oU-0000rk-KK; Sat, 08 Jul 2006 10:09:26 +0100 Date: Sat, 8 Jul 2006 10:09:20 +0100 (BST) From: Jan Grant X-X-Sender: cmjg@tribble.ilrt.bris.ac.uk To: Bruce Evans In-Reply-To: <20060708120806.U6238@delplex.bde.org> Message-ID: <20060708100421.N41181@tribble.ilrt.bris.ac.uk> References: <20060707201402.T14116@tribble.ilrt.bris.ac.uk> <20060707222343.GA10756@gothmog.pc> <20060708120806.U6238@delplex.bde.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spamassassin: mail.ilrt.bris.ac.uk X-Spam-Score: 0.0 X-Spam-Level: / X-Spam-Score: -1.4 X-Spam-Level: - Cc: freebsd-standards@freebsd.org Subject: Re: stdio/sh behaviour guaranteed? 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: Sat, 08 Jul 2006 09:09:32 -0000 On Sat, 8 Jul 2006, Bruce Evans wrote: > Using stdio for input from pipelines in shells is almost absolutely not > possible, since stdio normally does buffering and any buffering breaks > pipelines since there is no way to unread characters from a pipe. E.g.: > > printf "%s\n%s\n" foo bar | > sh -c 'read x; echo $$: $x; sh -c "read y; echo \$$: \$y"' I think yours is a much better example. (I couched my question in terms of stdio behvaiour because it occurred to me that shell behaviour might be expressed (specified) in terms of it, but I'm after the shell behaviour in particular). > > > And in particular, is the idiom above blessed by appropriate > > > posix standards? > > Stuff like this has to work to satisfy at least defacto standards. That was the conclusion I was coming to. Cheers, jan -- jan grant, ISYS, University of Bristol. http://www.bris.ac.uk/ Tel +44 (0)117 3317661 http://ioctl.org/jan/ It's a sad fact that the word "semantics" seems to have lost all meaning. From owner-freebsd-standards@FreeBSD.ORG Sat Jul 8 12:56:32 2006 Return-Path: X-Original-To: freebsd-standards@freebsd.org Delivered-To: freebsd-standards@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B613916A4E0 for ; Sat, 8 Jul 2006 12:56:32 +0000 (UTC) (envelope-from ed@hoeg.nl) Received: from palm.hoeg.nl (mx0.hoeg.nl [83.98.131.211]) by mx1.FreeBSD.org (Postfix) with ESMTP id 62AFE43D45 for ; Sat, 8 Jul 2006 12:56:30 +0000 (GMT) (envelope-from ed@hoeg.nl) Received: by palm.hoeg.nl (Postfix, from userid 1000) id A250F17264; Sat, 8 Jul 2006 14:56:28 +0200 (CEST) Date: Sat, 8 Jul 2006 14:56:28 +0200 From: Ed Schouten To: FreeBSD Standards Message-ID: <20060708125628.GN83179@hoeg.nl> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="8SdtHY/0P4yzaavF" Content-Disposition: inline User-Agent: Mutt/1.5.11 Subject: [Patch] jobs -p 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: Sat, 08 Jul 2006 12:56:32 -0000 --8SdtHY/0P4yzaavF Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hello, While taking a look at the FreeBSD POSIX 2001 Utility Compliance page[1], I saw that the jobs utility in /bin/sh doesn't support the -p flag, therefore not POSIX compliant. I wrote a small patch[2] that adds the -p flag to the jobs utility, by limiting the output to one process and running getpgid() on the pid. According to various sources, getpgid() returns the process group ID, which is also the process group leader. Can anyone confirm this? Yours, --=20 Ed Schouten WWW: http://g-rave.nl/ [1] http://people.freebsd.org/~schweikh/posix-utilities.html [2] http://g-rave.nl/junk/freebsd-sh-jobs-posix.diff --8SdtHY/0P4yzaavF Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (FreeBSD) iD8DBQFEr6t852SDGA2eCwURAg4IAJ4moQ4Bco5iFxz6cs2fPyHFVJ+WowCfX/3p tQ/vblOrJpcoVu2/YMpLDXk= =lpyF -----END PGP SIGNATURE----- --8SdtHY/0P4yzaavF-- From owner-freebsd-standards@FreeBSD.ORG Sat Jul 8 20:30:22 2006 Return-Path: X-Original-To: freebsd-standards@hub.freebsd.org Delivered-To: freebsd-standards@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D54E516A522 for ; Sat, 8 Jul 2006 20:30:22 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4A4B343D5E for ; Sat, 8 Jul 2006 20:30:19 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k68KUJ4u001840 for ; Sat, 8 Jul 2006 20:30:19 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k68KUJ2u001839; Sat, 8 Jul 2006 20:30:19 GMT (envelope-from gnats) Resent-Date: Sat, 8 Jul 2006 20:30:19 GMT Resent-Message-Id: <200607082030.k68KUJ2u001839@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-standards@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, Ed Schouten Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B019F16A4DA for ; Sat, 8 Jul 2006 20:27:19 +0000 (UTC) (envelope-from ed@compy.fxq.nl) Received: from swip.net (mailfe01.swip.net [212.247.154.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1699E43D45 for ; Sat, 8 Jul 2006 20:27:16 +0000 (GMT) (envelope-from ed@compy.fxq.nl) Received: from [83.180.59.125] (HELO compy.fxq.nl) by mailfe01.swip.net (CommuniGate Pro SMTP 5.0.8) with ESMTPS id 210920402 for FreeBSD-gnats-submit@freebsd.org; Sat, 08 Jul 2006 22:27:15 +0200 Received: from compy.fxq.nl (localhost [127.0.0.1]) by compy.fxq.nl (8.13.7/8.13.7) with ESMTP id k68KRCgI040105 for ; Sat, 8 Jul 2006 22:27:12 +0200 (CEST) (envelope-from ed@compy.fxq.nl) Received: (from ed@localhost) by compy.fxq.nl (8.13.7/8.13.7/Submit) id k68KRBYv040104; Sat, 8 Jul 2006 22:27:11 +0200 (CEST) (envelope-from ed) Message-Id: <200607082027.k68KRBYv040104@compy.fxq.nl> Date: Sat, 8 Jul 2006 22:27:11 +0200 (CEST) From: Ed Schouten To: FreeBSD-gnats-submit@FreeBSD.org X-Send-Pr-Version: 3.113 Cc: Subject: standards/99926: [Patch] [sh(1)'s jobs] POSIX compliancy by adding -p switch X-BeenThere: freebsd-standards@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Ed Schouten List-Id: Standards compliance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 08 Jul 2006 20:30:22 -0000 >Number: 99926 >Category: standards >Synopsis: [Patch] [sh(1)'s jobs] POSIX compliancy by adding -p switch >Confidential: no >Severity: non-critical >Priority: medium >Responsible: freebsd-standards >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sat Jul 08 20:30:18 GMT 2006 >Closed-Date: >Last-Modified: >Originator: Ed Schouten >Release: FreeBSD 7.0-CURRENT i386 >Organization: >Environment: System: FreeBSD compy.fxq.nl 7.0-CURRENT FreeBSD 7.0-CURRENT #0: Sun Jul 2 10:55:26 CEST 2006 root@compy.fxq.nl:/usr/obj/usr/src/sys/COMPY i386 >Description: According to the POSIX 2001 standard, the jobs command in sh(1) should implement a -p switch that displays output similar to FreeBSD's -s switch, but only shows PIDs for process group leaders. It isn't available, however. >How-To-Repeat: Run the following commands in sh(1); $ sleep 10 | cat & $ jobs -p The latter command will fail, because the built-in jobs command does not support the -p switch. >Fix: Apply the patch located at: http://g-rave.nl/junk/freebsd-sh-jobs-posix.diff This patch adds an argument 'pformat' the showjob() and showjobs() functions. When set, its output format is the same as when 'sformat' is set, but limited to process group leaders only. The sh(1) manual page has also been updated to reflect the changes. Please note that this patch marks the 'Add missing components to the jobs utility.' task of the C99 project as completed. >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-standards@FreeBSD.ORG Sat Jul 8 20:33:57 2006 Return-Path: X-Original-To: freebsd-standards@freebsd.org Delivered-To: freebsd-standards@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 694E516A4DA for ; Sat, 8 Jul 2006 20:33:57 +0000 (UTC) (envelope-from ed@hoeg.nl) Received: from palm.hoeg.nl (mx0.hoeg.nl [83.98.131.211]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1175C43D46 for ; Sat, 8 Jul 2006 20:33:57 +0000 (GMT) (envelope-from ed@hoeg.nl) Received: by palm.hoeg.nl (Postfix, from userid 1000) id E8B2317264; Sat, 8 Jul 2006 22:33:55 +0200 (CEST) Date: Sat, 8 Jul 2006 22:33:55 +0200 From: Ed Schouten To: FreeBSD Standards Message-ID: <20060708203355.GO83179@hoeg.nl> References: <20060708125628.GN83179@hoeg.nl> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="L/bWm/e7/ricERqM" Content-Disposition: inline In-Reply-To: <20060708125628.GN83179@hoeg.nl> User-Agent: Mutt/1.5.11 Subject: Re: [Patch] jobs -p 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: Sat, 08 Jul 2006 20:33:57 -0000 --L/bWm/e7/ricERqM Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hello, * Ed Schouten wrote: > I wrote a small patch[2] that adds the -p flag to the jobs utility, by > limiting the output to one process and running getpgid() on the pid. >=20 > According to various sources, getpgid() returns the process group ID, > which is also the process group leader. Can anyone confirm this? After reading some more documentation and kernel source code, I found the answer to the question. I did some small cleanup fixes and added a small patch for the manual page as well. I also filed a problem report; standards/99926: http://www.freebsd.org/cgi/query-pr.cgi?pr=3D99926 Yours, --=20 Ed Schouten WWW: http://g-rave.nl/ --L/bWm/e7/ricERqM Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (FreeBSD) iD8DBQFEsBaz52SDGA2eCwURAnQcAJ48zYF0cEHabqlF8j82w+zcd3KKXgCeNI1k ktLbOJoX+IC6AJ1BP2GCP/Q= =eRLi -----END PGP SIGNATURE----- --L/bWm/e7/ricERqM--