From owner-freebsd-current Thu Oct 22 14:24:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA03368 for freebsd-current-outgoing; Thu, 22 Oct 1998 14:24:28 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA03361 for ; Thu, 22 Oct 1998 14:24:27 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id OAA01027; Thu, 22 Oct 1998 14:28:00 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810222128.OAA01027@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: tomppa@fidata.fi cc: freebsd-current@FreeBSD.ORG Subject: Re: 3.0 current mkdir/umask problem In-reply-to: Your message of "Thu, 22 Oct 1998 22:01:58 +0300." <13871.33062.481564.696745@zeta.fidata.fi> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 22 Oct 1998 14:28:00 -0700 From: Mike Smith 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? No, it's a bug in the "fixes" I committed from Apple via NetBSD. I'm working on doing it "right" (preserving the ability to set the mode properly, but also respecting the umask if you're not). -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message