From owner-freebsd-standards@FreeBSD.ORG Mon Nov 8 05:31:37 2010 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 3D2A51065679 for ; Mon, 8 Nov 2010 05:31:37 +0000 (UTC) (envelope-from yanegomi@gmail.com) Received: from mail-wy0-f182.google.com (mail-wy0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id C97458FC0C for ; Mon, 8 Nov 2010 05:31:36 +0000 (UTC) Received: by wyb34 with SMTP id 34so3049016wyb.13 for ; Sun, 07 Nov 2010 21:31:35 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:sender:received:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=Mi4XOokHsNWcm0f7/jWIGObDYStv0UTHlZRvWNJueq0=; b=QZ81XgF8ZcScMZHQ9Tyrs2+tgZsduSjoxzTfI2t7Rt78T8yOq2ubXOYpZfydxA5Bom SPbqx5uS2sj/ZUGSVWokR5jikoD7KivNj7TFAXkrQLQms7EAl51/2b5ldFiWG7RjtXJx pmQp3C7AmuFWi3NoVSRQ5QacPMA5o82qd4IT8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type; b=Q1u2JyZw2IZzNZe2nhCV23LvCH+wRDgVhOQo0RTWsIhLCcDeyjmMCEOwT1xr2X2J9j FScUcnXXB9WyAAcJ7+AjGUiYwboyhlA0j8rGNr3WcBvHlehibMyTDaGMQjw1UH3v9I3S yHnoPoOytN1eHHYAe2pSMhmmLSCn+xYgG4Apw= MIME-Version: 1.0 Received: by 10.216.7.210 with SMTP id 60mr3861699wep.30.1289192705094; Sun, 07 Nov 2010 21:05:05 -0800 (PST) Sender: yanegomi@gmail.com Received: by 10.216.198.27 with HTTP; Sun, 7 Nov 2010 21:05:05 -0800 (PST) Date: Sun, 7 Nov 2010 21:05:05 -0800 X-Google-Sender-Auth: xLOyDj-oQ5ONB1LpnjWxylC-6Dk Message-ID: From: Garrett Cooper To: standards@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Cc: Subject: Question about non-__BSD_VISIBLE guarded CLOCK_* constants 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, 08 Nov 2010 05:31:37 -0000 None of the following constants in time.h are guarded by __BSD_VISIBLE, __FreeBSD__, etc, even though other sections of the file are blocked off that way (and the comments suggest that they're FreeBSD-specific). I was wondering why that's the case... #define CLOCK_UPTIME 5 /* FreeBSD-specific. */ #define CLOCK_UPTIME_PRECISE 7 /* FreeBSD-specific. */ #define CLOCK_UPTIME_FAST 8 /* FreeBSD-specific. */ #define CLOCK_REALTIME_PRECISE 9 /* FreeBSD-specific. */ #define CLOCK_REALTIME_FAST 10 /* FreeBSD-specific. */ #define CLOCK_MONOTONIC_PRECISE 11 /* FreeBSD-specific. */ #define CLOCK_MONOTONIC_FAST 12 /* FreeBSD-specific. */ #define CLOCK_SECOND 13 /* FreeBSD-specific. */ Also, they're blocked off by #if !defined(CLOCK_REALTIME) && __POSIX_VISIBLE >= 200112 , which doesn't seem to make sense, given that it's an "advanced realtime" feature, according to POSIX 2008. Thanks! -Garrett From owner-freebsd-standards@FreeBSD.ORG Mon Nov 8 11:07:06 2010 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 3C57010656A4 for ; Mon, 8 Nov 2010 11:07:06 +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 28B9D8FC1E for ; Mon, 8 Nov 2010 11:07:06 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id oA8B76DM088218 for ; Mon, 8 Nov 2010 11:07:06 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id oA8B75JR088216 for freebsd-standards@FreeBSD.org; Mon, 8 Nov 2010 11:07:05 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 8 Nov 2010 11:07:05 GMT Message-Id: <201011081107.oA8B75JR088216@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, 08 Nov 2010 11:07:06 -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/151316 standards lib/libc/string/strerror.c r1.9 breaks POSIX o stand/150093 standards C++ std::locale support is broken a stand/149980 standards [libc] [patch] negative value integer to nanosleep(2) o stand/147210 standards xmmintrin.h and cstdlib conflicts with each other with p stand/145517 standards POSIX getline() missing o stand/144231 standards bind/connect/sendto too strict about sockaddr length o stand/143358 standards [libm] nearbyint(3) raises spurious inexact exception o stand/142803 standards j0 Bessel function inaccurate near zeros of the functi s stand/141705 standards [libc] [request] libc lacks cexp (and friends) 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/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/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 o stand/114633 standards /etc/rc.subr: line 511: omits a quotation mark: "force 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 [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 f stand/41576 standards ln(1): replacing old dir-symlinks o stand/39256 standards snprintf/vsnprintf aren't POSIX-conformant for strings 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 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 47 problems total. From owner-freebsd-standards@FreeBSD.ORG Mon Nov 8 17:56:36 2010 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 4D1061065673 for ; Mon, 8 Nov 2010 17:56:36 +0000 (UTC) (envelope-from brde@optusnet.com.au) Received: from fallbackmx08.syd.optusnet.com.au (fallbackmx08.syd.optusnet.com.au [211.29.132.10]) by mx1.freebsd.org (Postfix) with ESMTP id D79C48FC1B for ; Mon, 8 Nov 2010 17:56:35 +0000 (UTC) Received: from mail01.syd.optusnet.com.au (mail01.syd.optusnet.com.au [211.29.132.182]) by fallbackmx08.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id oA8FxZi7003418 for ; Tue, 9 Nov 2010 02:59:35 +1100 Received: from c122-107-121-73.carlnfd1.nsw.optusnet.com.au (c122-107-121-73.carlnfd1.nsw.optusnet.com.au [122.107.121.73]) by mail01.syd.optusnet.com.au (8.13.1/8.13.1) with ESMTP id oA8FxVKr016833 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 9 Nov 2010 02:59:32 +1100 Date: Tue, 9 Nov 2010 02:59:31 +1100 (EST) From: Bruce Evans X-X-Sender: bde@besplex.bde.org To: Garrett Cooper In-Reply-To: Message-ID: <20101109015704.L1243@besplex.bde.org> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: standards@FreeBSD.org Subject: Re: Question about non-__BSD_VISIBLE guarded CLOCK_* constants 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, 08 Nov 2010 17:56:36 -0000 On Sun, 7 Nov 2010, Garrett Cooper wrote: > None of the following constants in time.h are guarded by > __BSD_VISIBLE, __FreeBSD__, etc, even though other sections of the > file are blocked off that way (and the comments suggest that they're > FreeBSD-specific). I was wondering why that's the case... It is because the other sections were written by standards-aware persons. > #define CLOCK_UPTIME 5 /* FreeBSD-specific. */ > #define CLOCK_UPTIME_PRECISE 7 /* FreeBSD-specific. */ > #define CLOCK_UPTIME_FAST 8 /* FreeBSD-specific. */ > #define CLOCK_REALTIME_PRECISE 9 /* FreeBSD-specific. */ > #define CLOCK_REALTIME_FAST 10 /* FreeBSD-specific. */ > #define CLOCK_MONOTONIC_PRECISE 11 /* FreeBSD-specific. */ > #define CLOCK_MONOTONIC_FAST 12 /* FreeBSD-specific. */ > #define CLOCK_SECOND 13 /* FreeBSD-specific. */ Defining these without using __BSD_VISBLE is just a style bug, since the CLOCK_ prefix is reserved in , but FreeBSD normally ifdefs extensions that use reserved prefixes anyway (e.g., FreeBSD-specific signal numbers at least used to be ifdefed to a fault in . The definitions themselves have lots of style bugs: - space instead of tab after #define (all tabs were corrupted in the mail, except these are corrupt in the file) - macro values don't line up, although they are indented with tabs - comment duplicated ad nauseum - there is now an id 14. It is missing the comment, and seems to be undocumented. > Also, they're blocked off by #if !defined(CLOCK_REALTIME) && > __POSIX_VISIBLE >= 200112 , which doesn't seem to make sense, given > that it's an "advanced realtime" feature, according to POSIX 2008. Re-quoting everything to get more context. % /* These macros are also in sys/time.h. */ is considerably more broken than here. It defines all of these macros unconditionally, and also includes in the !_KERNEL case. Thus including the POSIX header gives massive namespace pollution. % #if !defined(CLOCK_REALTIME) && __POSIX_VISIBLE >= 200112 % #define CLOCK_REALTIME 0 % #ifdef __BSD_VISIBLE % #define CLOCK_VIRTUAL 1 % #define CLOCK_PROF 2 % #endif % #define CLOCK_MONOTONIC 4 /* These macros are also in sys/time.h. */ #define CLOCK_MONOTONIC 4 #define CLOCK_UPTIME 5 /* FreeBSD-specific. */ #define ... #endif /* !defined(CLOCK_REALTIME) && __POSIX_VISIBLE >= 200112 */ The CLOCK_REALTIME part of this does nothing except partially break automatic checking that the defines here are the same as the ones in : - if is not included before here, then CLOCK_REALTIME shouldn't be defined yet, so it has no effect in this ifdef - if is included before here, then CLOCK_REALTIME is defined now, so its effect in this ifdef is to prevent repeating ifdefs that should be the same. Repeated ifdefs are a very small part of header bloat, so it is hardly worth avoiding them, and not avoiding them gives the feature of checking that they really are repeated. I think the repetitions are all indentical, including their style bugs and whitespace that would not be checked. - if is not included before here, but is included later, then CLOCK_REALTIME etc. gets declared here, and since has no similar ifdefs, it gets defined again later. Thus the automatic checking is only partially broken. As you noticed, the __POSIX_VISIBLE part of this has the wrong version number at best. CLOCK_REALTIME dates from POSIX.4 in ~1994 (it is in my POSIX.4 book published in 1995, and in the 1996 POSIX standard). FreeBSD doesn't try to track old versions of POSIX very carefully, except original POSIX, but it normally makes features that appeared in in-between POSIXes visible by default by putting them under __BSD_VISIBLE. So the correct ifdefs here aresomething like __BSD_VISIBLE || POSIX_VISIBLE >= 199309 (check the latter) for the whole block, and __BSD_VISIBLE for the sub-block consisting of FreeBSD extensions. Since the organization is poor (historical, giving random alphabetical and numericl order), there are actually several sub-blocks: - CLOCK_MONOTONIC seems to be new in POSIX.1-2001. Thus the current ifdef is partially correct for it. The rest of the file has careful ifdefs for 1993 POSIX, so perhaps it is worth being equally careful for CLOCK_REALTIME. - the BSD extensions CLOCK_VIRTUAL and CLOCK_PROF are already in a __BSD_VISIBLE block. Then there seems to be space for expansion (a whole 1 id = 3). Then there is the whole 1 new id = 4 for 2001 POSIX. Then there is a FreeBSD-specific block (ids 5-14). Too much bloat for me. Bruce From owner-freebsd-standards@FreeBSD.ORG Tue Nov 9 12:14:25 2010 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 91FF01065670 for ; Tue, 9 Nov 2010 12:14:25 +0000 (UTC) (envelope-from jau@oxit.fi) Received: from smtp.oxit.fi (smtp.oxit.fi [193.185.41.132]) by mx1.freebsd.org (Postfix) with ESMTP id 483948FC1E for ; Tue, 9 Nov 2010 12:14:25 +0000 (UTC) Received: from box4.thunderbolt.fi ([::ffff:193.64.26.116]) (AUTH: LOGIN jau) by smtp.oxit.fi with esmtp; Tue, 09 Nov 2010 14:04:20 +0200 id 0063C006.4CD938C4.00002000 Message-ID: <4CD938C3.6090009@oxit.fi> Date: Tue, 09 Nov 2010 14:04:19 +0200 From: "Jukka A. Ukkonen" User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-GB; rv:1.9.2.12) Gecko/20101027 Thunderbird/3.1.6 MIME-Version: 1.0 To: freebsd-standards@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Portability question - waitid() missing 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, 09 Nov 2010 12:14:25 -0000 Greetings everybody, Would there be enough interest in the community to merge a new system call to FreeBSD? A the moment there is no waitid() which is anyhow part of the current POSIX specification... http://www.unix.com/man-page/POSIX/3posix/waitid/ #include int waitid(idtype_t idtype, id_t id, siginfo_t *infop, int options) I implemented waitid() already on 7.0, and I have kept it as a part of my system all the time through all 7.x updates. If there were enough interest in the community to merge the implementation to the common core, I could port the changes to 8.x and donate it. So, are there committers willing to try the code in their own kernels and then, if everything seems to be stable after the change, commit the change to the common source tree? Cheers, // jau From owner-freebsd-standards@FreeBSD.ORG Tue Nov 9 13:28:18 2010 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 2876D106564A for ; Tue, 9 Nov 2010 13:28:18 +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 8F3D88FC08 for ; Tue, 9 Nov 2010 13:28:17 +0000 (UTC) Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by mail.zoral.com.ua (8.14.2/8.14.2) with ESMTP id oA9DPlIO006909 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 9 Nov 2010 15:25:47 +0200 (EET) (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.4/8.14.4) with ESMTP id oA9DPlmg027008; Tue, 9 Nov 2010 15:25:47 +0200 (EET) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.14.4/8.14.4/Submit) id oA9DPl2n027007; Tue, 9 Nov 2010 15:25:47 +0200 (EET) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Tue, 9 Nov 2010 15:25:47 +0200 From: Kostik Belousov To: "Jukka A. Ukkonen" Message-ID: <20101109132547.GS2392@deviant.kiev.zoral.com.ua> References: <4CD938C3.6090009@oxit.fi> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="m2kArsPQXLuAjrrZ" Content-Disposition: inline In-Reply-To: <4CD938C3.6090009@oxit.fi> 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=-3.4 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00, DNS_FROM_OPENWHOIS autolearn=no version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on skuns.kiev.zoral.com.ua Cc: freebsd-standards@freebsd.org Subject: Re: Portability question - waitid() missing 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, 09 Nov 2010 13:28:18 -0000 --m2kArsPQXLuAjrrZ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Nov 09, 2010 at 02:04:19PM +0200, Jukka A. Ukkonen wrote: >=20 > Greetings everybody, >=20 > Would there be enough interest in the community to merge a new system call > to FreeBSD? A the moment there is no waitid() which is anyhow part of the > current POSIX specification... >=20 > http://www.unix.com/man-page/POSIX/3posix/waitid/ >=20 > #include >=20 > int waitid(idtype_t idtype, id_t id, siginfo_t *infop, int options) >=20 >=20 > I implemented waitid() already on 7.0, and I have kept it as a part of my > system all the time through all 7.x updates. > If there were enough interest in the community to merge the implementation > to the common core, I could port the changes to 8.x and donate it. > So, are there committers willing to try the code in their own kernels and > then, if everything seems to be stable after the change, commit the change > to the common source tree? The proper implementation of waitid(2) definitely will be committed (consider this the promise from me). --m2kArsPQXLuAjrrZ Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (FreeBSD) iEYEARECAAYFAkzZS9oACgkQC3+MBN1Mb4iVCACgpY3Xz/YpIJhZYslxq9BM+Yr2 BCIAoLzgGF+qdSJMMQGVDmtYwoelievD =0RlZ -----END PGP SIGNATURE----- --m2kArsPQXLuAjrrZ-- From owner-freebsd-standards@FreeBSD.ORG Sat Nov 13 11:33:31 2010 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 78A78106566B; Sat, 13 Nov 2010 11:33:31 +0000 (UTC) (envelope-from arundel@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 4E2058FC0A; Sat, 13 Nov 2010 11:33:31 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id oADBXVe2037668; Sat, 13 Nov 2010 11:33:31 GMT (envelope-from arundel@freefall.freebsd.org) Received: (from arundel@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id oADBXU99037664; Sat, 13 Nov 2010 11:33:30 GMT (envelope-from arundel) Date: Sat, 13 Nov 2010 11:33:30 GMT Message-Id: <201011131133.oADBXU99037664@freefall.freebsd.org> To: l.ertl@univie.ac.at, arundel@FreeBSD.org, freebsd-standards@FreeBSD.org From: arundel@FreeBSD.org Cc: Subject: Re: standards/41576: ln(1): replacing old dir-symlinks 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, 13 Nov 2010 11:33:31 -0000 Synopsis: ln(1): replacing old dir-symlinks State-Changed-From-To: feedback->analyzed State-Changed-By: arundel State-Changed-When: Sat Nov 13 11:32:33 UTC 2010 State-Changed-Why: It appears FreeBSD's ln(1) command does in fact confirm to POSIX.1-2008 and the SUSv3. http://www.freebsd.org/cgi/query-pr.cgi?pr=41576