From owner-freebsd-bugs@FreeBSD.ORG Sat Feb 1 06:30:01 2014 Return-Path: Delivered-To: freebsd-bugs@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 9E1D4676 for ; Sat, 1 Feb 2014 06:30:01 +0000 (UTC) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 8A3C512C6 for ; Sat, 1 Feb 2014 06:30:01 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id s116U1gM036310 for ; Sat, 1 Feb 2014 06:30:01 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id s116U1pL036309; Sat, 1 Feb 2014 06:30:01 GMT (envelope-from gnats) Date: Sat, 1 Feb 2014 06:30:01 GMT Message-Id: <201402010630.s116U1pL036309@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Norbert Grundmann Subject: Re: bin/186293: tar(1): Problems with tar on FreeBSD 10.0 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list Reply-To: Norbert Grundmann List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 01 Feb 2014 06:30:01 -0000 The following reply was made to PR bin/186293; it has been noted by GNATS. From: Norbert Grundmann To: bug-followup@FreeBSD.org, ngrundmann@gmx.de Cc: Subject: Re: bin/186293: tar(1): Problems with tar on FreeBSD 10.0 Date: Sat, 01 Feb 2014 07:20:17 +0100 I should note, that this behaviour is not only related to tar. For example, if I compile software manually, using clang, the generated *.o files have no rights. Doing the same with gcc46, the results are ok, which means the *.o files have the permissions what they should have... See: [clang/samtools-0.1.19] > ll *.o ---------- 1 appl admin 74232 Feb 1 07:11 bam.o ---------- 1 appl admin 56496 Feb 1 07:11 bam2bcf.o ---------- 1 appl admin 104392 Feb 1 07:11 bam2bcf_indel.o ---------- 1 appl admin 21832 Feb 1 07:11 bam2depth.o ---------- 1 appl admin 46512 Feb 1 07:11 bam_aux.o and: [gcc/samtools-0.1.19] > ll *.o -rw-r--r-- 1 appl admin 90488 Feb 1 07:10 bam.o -rw-r--r-- 1 appl admin 57864 Feb 1 07:10 bam2bcf.o -rw-r--r-- 1 appl admin 88256 Feb 1 07:10 bam2bcf_indel.o -rw-r--r-- 1 appl admin 22400 Feb 1 07:10 bam2depth.o -rw-r--r-- 1 appl admin 52272 Feb 1 07:10 bam_aux.o -rw-r--r-- 1 appl admin 17128 Feb 1 07:10 bam_cat.o and another thing related to this: untar a package on a mounted NFS/ZFS volumne which resides in a FreeBSD 10.0 computer gives me no problem. I think the whole thing is realted to: FreeBSD 10 NFS client <---> Solaris 11 NFS Server Hopefully someone could help me :-) Norbert