From: David Brown <dmlb2000@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: linux-2.6.14.tar.bz2 permissions
Date: Sat, 26 Nov 2005 14:27:24 -0800 [thread overview]
Message-ID: <9c21eeae0511261427ld8375bfi1c838b56cab426fb@mail.gmail.com> (raw)
In-Reply-To: <200511262319.15042.norbert-kernel@hipersonik.com>
> The rights on the files should be sufficient for the compiler to go through
> the tree and compile the kernel for you. If it bothers you, you can just run
> chmod -R to correct it.
Yeah but it took me a couple of weeks and a few updates of my kernel
to find it...
Some one could have broke in and changed things without being root and
I wouldn't have noticed it.
> I guess that it will not be corrected.
I just find it odd that I now have to check permissions all over the
place to make sure everything is safe.
- David Brown
next prev parent reply other threads:[~2005-11-26 22:27 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <9c21eeae0511261352u33e32343wf50062ba3038ef06@mail.gmail.com>
2005-11-26 21:58 ` David Brown
2005-11-26 22:19 ` Norbert van Nobelen
2005-11-26 22:27 ` David Brown [this message]
2005-11-26 22:36 ` Michael Frank
2005-11-26 22:41 ` David Brown
2005-11-26 22:53 ` Michael Frank
2005-11-26 23:11 ` David Brown
2005-11-27 8:23 ` Jan Engelhardt
2005-11-27 5:57 ` Willy Tarreau
2005-11-26 23:12 ` Nish Aravamudan
2005-11-26 23:15 ` David Brown
2005-11-26 23:46 ` Alistair John Strachan
[not found] ` <9c21eeae0511261713vacf13f5u5fdf19711635a381@mail.gmail.com>
2005-11-27 1:38 ` Alistair John Strachan
2005-11-27 1:46 ` Nish Aravamudan
2005-11-27 1:51 ` Alistair John Strachan
2005-11-27 1:56 ` David Brown
2005-11-27 2:27 ` Nish Aravamudan
2005-11-27 2:38 ` David Brown
2005-11-27 6:09 ` Willy Tarreau
2005-11-27 9:22 ` David Brown
2005-11-27 10:57 ` Willy Tarreau
2005-11-27 14:39 ` Kyle Moffett
2005-11-27 16:30 ` Jesper Juhl
2005-11-27 1:51 ` David Brown
2005-11-27 6:07 ` Willy Tarreau
2005-11-27 1:47 ` David Brown
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=9c21eeae0511261427ld8375bfi1c838b56cab426fb@mail.gmail.com \
--to=dmlb2000@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
all inboxes | Powered by JetHome®