From owner-freebsd-questions Fri Jan 11 6:33: 1 2002 Delivered-To: freebsd-questions@freebsd.org Received: from TheWorld.com (pcls2.std.com [199.172.62.104]) by hub.freebsd.org (Postfix) with ESMTP id A978D37B42A for ; Fri, 11 Jan 2002 06:32:52 -0800 (PST) Received: from shell.TheWorld.com (root@shell01.TheWorld.com [199.172.62.241]) by TheWorld.com (8.9.3/8.9.3) with ESMTP id JAA02688; Fri, 11 Jan 2002 09:32:51 -0500 Received: (from lowell@localhost) by shell.TheWorld.com (8.9.3/8.9.3) id JAA7614268; Fri, 11 Jan 2002 09:32:51 -0500 (EST) To: Tom Kersten Cc: freebsd-questions@freebsd.org Subject: Re: [freebsd-questions] Troubled newbie....PLEASE HELP!!! References: <20020110215045.73282.qmail@web10005.mail.yahoo.com> From: Lowell Gilbert Date: 11 Jan 2002 09:32:51 -0500 In-Reply-To: Tom Kersten's message of "Thu, 10 Jan 2002 13:50:45 -0800 (PST)" Message-ID: Lines: 32 X-Mailer: Gnus v5.7/Emacs 20.7 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Tom Kersten writes: > following also: > 1.) changing my default umask to 022 in my > .bash_profile directory of root's home. This should > take care of it as far as I can tell from bash's > documentation. Only inasmuch as bash would be involved. The system default shell isn't bash, and even if you change root's shell, all the system scripts will still point to /bin/sh (which is a slightly more POSIX-ish shell than bash). > 2.) adding "*default umask=022" to my sup-file. > > I seriously can't come up with a solution to this. I > did update my /src also before. I rebuilt the kernel > fine and thought that I had followed the directions, > but....if something in this process could've messed it > up...???? Hmm..........I have no idea, as I said > before, I am at a loss for words at this point. Any > other ideas???? Well, it's all clutching at straws at this point for me too. If your source tree isn't on an FFS filesystem, that could cause problems (the semantics of permissions vary between types of filesystem). If the directory permissions have sticky bits set (even just on the root directory), that can override the umask. Make sure that you're running cvsup directly, and not through an alias or some other kind of indirection that might be changing its behaviour. Good luck. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message