From: Daniel <damage@rooties.de>
To: linux-kernel@vger.kernel.org
Subject: Kernelsources writeable for everyone?!
Date: Sat, 24 Jun 2006 20:00:50 +0200 [thread overview]
Message-ID: <200606242000.51024.damage@rooties.de> (raw)
Hi,
may be this was reported/asked 999999999 times, but here ist the 1000000000th:
I have downloaded linux-2.6.17.1 10 min ago and I noticed that every file is
writeable by everyone. What's going on there?
coffee src # tar -jtvf linux-2.6.17.1.tar.bz2
drwxrwxrwx git/git 0 2006-06-20 11:31:55 linux-2.6.17.1/
-rw-rw-rw- git/git 462 2006-06-20 11:31:55 linux-2.6.17.1/.gitignore
-rw-rw-rw- git/git 18693 2006-06-20 11:31:55 linux-2.6.17.1/COPYING
-rw-rw-rw- git/git 89536 2006-06-20 11:31:55 linux-2.6.17.1/CREDITS
drwxrwxrwx git/git 0 2006-06-20 11:31:55
linux-2.6.17.1/Documentation/
-rw-rw-rw- git/git 10581 2006-06-20 11:31:55
linux-2.6.17.1/Documentation/00-INDEX
[...]
regards
Daniel Buschke
next reply other threads:[~2006-06-24 18:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-24 18:00 Daniel [this message]
2006-06-24 18:05 ` Kernelsources writeable for everyone?! 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
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=200606242000.51024.damage@rooties.de \
--to=damage@rooties.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.