public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pascal Schmidt <der.eremit@email.de>
To: Kalin KOZHUHAROV <kalin@ThinRope.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Too restrictive permissions on some files prevent non-root build  (with KBUILD_OUTPUT) [bug 2669]
Date: Thu, 13 May 2004 15:51:54 +0200	[thread overview]
Message-ID: <E1BOGcs-00006u-7d@localhost> (raw)
In-Reply-To: <1VorQ-6xx-13@gated-at.bofh.it>

On Thu, 13 May 2004 15:30:14 +0200, you wrote in linux.kernel:

> For 2.6.6 the files in question can be found by:
> cd /sometempdir
> tar xjf linux-2.6.6.tar.bz2
> find linux-2.6.6 ! -perm -004 -exec ls -l {} \;

This can only be a problem when unpacking as root, otherwise all
files are owned by the user running tar, anyway. I guess most
people don't do their kernel work as root... and why should they?

The simple workaround is to unpack the tar archive as the user
planning to run the compile.

-- 
Ciao,
Pascal

       reply	other threads:[~2004-05-13 13:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1VorQ-6xx-13@gated-at.bofh.it>
2004-05-13 13:51 ` Pascal Schmidt [this message]
2004-05-13 16:15   ` Too restrictive permissions on some files prevent non-root build (with KBUILD_OUTPUT) [bug 2669] Kalin KOZHUHAROV
2004-05-13 13:18 Kalin KOZHUHAROV

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=E1BOGcs-00006u-7d@localhost \
    --to=der.eremit@email.de \
    --cc=kalin@ThinRope.net \
    --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