From: Matthew Frost <artusemrys@sbcglobal.net>
To: Joshua Hudson <joshudson@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernelsources writeable for everyone?!
Date: Sun, 25 Jun 2006 17:16:36 -0500 [thread overview]
Message-ID: <449F0B44.6050407@sbcglobal.net> (raw)
In-Reply-To: <bda6d13a0606251309x3e07e9feoad777d9a062f923f@mail.gmail.com>
Joshua Hudson wrote:
> I feel like asking how they initially get set to world-writable. To me
> it means that the tree that is being tarred up for distribution is
> world-writible. I sure hope that it is a single-user box.
> -
Yeah. Having said, "Take advice", I'm also curious as to just the
why/how of the current configuration and the work patterns that create
it. I get the impression that there *is* a reason for it, because if it
were just a security issue, I can't see this much resistance to changing
it. Sane tar permissions and sensible usage aside.
The kernel untar-and-compile procedure has been documented this way
since at least 2000, from Linus. There's a good recent (and short)
discussion from Jesper Juhl on LXer that references it, as well.
http://uwsg.iu.edu/hypermail/linux/kernel/0007.3/0587.html
http://lxer.com/module/forums/t/22410/
The previous two l-k threads I can find on this topic (one listed
earlier in this thread, one referenced from it) don't seem to be any
more revelatory about why the tarball is as it is. I might guess that
it has to do with how changes get checked in, but I also have the vague
memory that these aren't tar()ed on a development box. I could be
wrong. Consider me seconding the "Why?" aspect, if anybody's still
listening. :)
Matt
next prev parent reply other threads:[~2006-06-25 22:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-24 18:00 Kernelsources writeable for everyone?! Daniel
2006-06-24 18:05 ` Avuton Olrich
2006-06-24 18:14 ` Rene Scharfe
2006-06-24 18:17 ` Al Viro
2006-06-25 1:20 ` Mark Rosenstand
2006-06-25 5:38 ` Matthew Frost
2006-06-25 20:09 ` Joshua Hudson
2006-06-25 22:16 ` Matthew Frost [this message]
2006-06-25 23:05 ` Matthew Frost
2006-06-29 6:11 ` Junio C Hamano
2006-06-29 14:38 ` Bill Davidsen
2006-06-26 7:11 ` Troy Benjegerdes
2006-06-26 13:09 ` Rene Scharfe
[not found] <6rkK4-7Do-1@gated-at.bofh.it>
[not found] ` <6rkTT-7OS-23@gated-at.bofh.it>
[not found] ` <6rrsb-vZ-5@gated-at.bofh.it>
[not found] ` <6rvFs-6xp-3@gated-at.bofh.it>
[not found] ` <6rJ5L-1n7-3@gated-at.bofh.it>
[not found] ` <6rL7C-4oS-41@gated-at.bofh.it>
2006-06-25 23:29 ` Bodo Eggert
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=449F0B44.6050407@sbcglobal.net \
--to=artusemrys@sbcglobal.net \
--cc=joshudson@gmail.com \
--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