All files have -rw-rw-rw- permission.
Hello,
All files have -rw-rw-rw- permission.(kernel 2.6.15, 2.6.14)
for example,
-rw-rw-rw- 1 root root 65359 Jan 3 12:21 MAINTAINERS
Is this correct?
Best Regards
Komuro
Quoted 8 lines · On Thu, 5 Jan 2006 21:15:11 +0900 (JST) Komuro wrote:
Hello,
All files have -rw-rw-rw- permission.(kernel 2.6.15, 2.6.14)
for example,
-rw-rw-rw- 1 root root 65359 Jan 3 12:21MAINTAINERSIs this correct?
Hi,
We (lkml) have been thru this before.
Don't untar the tarball as root and this won't happen.
---
~Randy
Quoted 2 lines · Randy.Dunlap
We (lkml) have been thru this before.
Don't untar the tarball as root and this won't happen.
or use umask as it is suppsoed to be used with --no-same-permissions
Gruss
Bernd
Hello,
Quoted 3 lines
We (lkml) have been thru this before.
Don't untar the tarball as root and this won't happen.
Thanks for your reply.
But, is there any reason to set -----w--w- bit
by default?
Quoted 3 lines
tar tvjf linux-2.6.15.tar.bz2
?rw------- git/git 52 1970-01-01 09:00:00
pax_global_header>unknown
file type `g'
Review
Quoted 4 lines
drwxr-xr-x git/git 0 2006-01-03 12:21:10 linux-2.6.15/
(quoted diff) +0
-3-rw-rw-rw- git/git 391 2006-01-03 12:21:10 linux-2.6.15/.gitignore -rw-rw-rw- git/git 18693 2006-01-03 12:21:10 linux-2.6.15/COPYING -rw-rw-rw- git/git 89582 2006-01-03 12:21:10 linux-2.6.15/CREDITS
Best Regards
Komuro
Quoted 2 lines · Komuro
But, is there any reason to set -----w--w- bit
by default?
Yes.
Please do not extract the kernel tarball as the root user, especially if you do not know how tar command works for root user by default (hint: --no-same-permissions).
Setting g-w in the archive forces arbitrary policy on people who work with umask 002 as a non-root user. We can let that policy to be controlled by user's umask by being lenient in the tarball. For the same reason, if somebody has umask 0, there is no reason for us (as tarball creator) to impose o-w as a policy on him either, hence git-tar-tree output has 0666 or 0777 modes.
Hello,
Quoted 9 lines
Quoted 2 lines
But, is there any reason to set -----w--w- bit
by default?Yes.
Please do not extract the kernel tarball as the root user, especially if you do not know how tar command works for root user by default (hint: --no-same-permissions).
Quoted 7 lines
Setting g-w in the archive forces arbitrary policy on people who work with umask 002 as a non-root user. We can let that policy to be controlled by user's umask by being lenient in the tarball. For the same reason, if somebody has umask 0, there is no reason for us (as tarball creator) to impose o-w as a policy on him either, hence git-tar-tree output has 0666 or 0777 modes.
O.K.
Thanks,
Komuro