From: Thomas Zehetbauer <thomasz@hostmaster.org>
To: linux-kernel@vger.kernel.org
Subject: Re: linux-2.6.0 kernel distribution non-world-readable files
Date: Wed, 24 Dec 2003 02:10:35 +0100 [thread overview]
Message-ID: <1072228229.1440.56.camel@hostmaster.org> (raw)
In-Reply-To: <37133.219.88.110.193.1072226080.squirrel@mail.med.co.nz>
[-- Attachment #1: Type: text/plain, Size: 560 bytes --]
When you unpack the tar as an unprivileged user you get ownership of the
files and can compile. root on the other hand should have a restrictive
umask setting so you would need to chmod anyways. However I find myself
typing "chown -R 0.0 .; chmod -R u=rwX,go=rX ." quite often so I would
appreciate some kind of a (set|fix)perms target.
Tom
--
T h o m a s Z e h e t b a u e r ( TZ251 )
PGP encrypted mail preferred - KeyID 96FFCB89
mail pgp-key-request@hostmaster.org
Success is, when there is only one opponent left: yourself
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 481 bytes --]
prev parent reply other threads:[~2003-12-24 1:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-24 0:34 linux-2.6.0 kernel distribution non-world-readable files Ross Boswell
2003-12-24 1:10 ` Thomas Zehetbauer [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1072228229.1440.56.camel@hostmaster.org \
--to=thomasz@hostmaster.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox