From owner-freebsd-current Thu Oct 22 12:02:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA09889 for freebsd-current-outgoing; Thu, 22 Oct 1998 12:02:32 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from fani.fidata.fi (fani.fidata.fi [193.64.102.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA09884 for ; Thu, 22 Oct 1998 12:02:30 -0700 (PDT) (envelope-from tomppa@fidata.fi) Received: from zeta.fidata.fi (zeta.fidata.fi [193.64.103.213]) by fani.fidata.fi (8.8.8/8.8.8) with ESMTP id WAA00795 for ; Thu, 22 Oct 1998 22:01:58 +0300 (EET DST) Received: (from tomppa@localhost) by zeta.fidata.fi (8.9.1/8.9.1) id WAA22337; Thu, 22 Oct 1998 22:01:58 +0300 (EET DST) From: Tomi Vainio MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <13871.33062.481564.696745@zeta.fidata.fi> Date: Thu, 22 Oct 1998 22:01:58 +0300 (EET DST) To: freebsd-current@FreeBSD.ORG Subject: 3.0 current mkdir/umask problem X-Mailer: VM 6.47 under 20.4 "Emerald" XEmacs Lucid Reply-To: tomppa@fidata.fi Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I feel little stupid asking this. I just installed 3.0R and compiled latest current over it. If I make new directory with mkdir command it will always get 777 permissions so it won't respect umask setting. I also tried mkdir binary from 2.2-stable and it works correctly. Is this some new nosecure option? Tomppa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message