mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jesper Juhl <jesper.juhl@gmail.com>
To: David Brown <dmlb2000@gmail.com>
Cc: Willy Tarreau <willy@w.ods.org>,
	Nish Aravamudan <nish.aravamudan@gmail.com>,
	Alistair John Strachan <s0348365@sms.ed.ac.uk>,
	linux-kernel@vger.kernel.org
Subject: Re: linux-2.6.14.tar.bz2 permissions
Date: Sun, 27 Nov 2005 17:30:15 +0100	[thread overview]
Message-ID: <9a8748490511270830m4bf88fd7v2617f4d2280cc10e@mail.gmail.com> (raw)
In-Reply-To: <9c21eeae0511270122h38cfb4a4y5d242347cbf9a21e@mail.gmail.com>

On 11/27/05, David Brown <dmlb2000@gmail.com> wrote:
> > It certainly is not an excuse, but at least it my explain why nobody
> > noticed it before you :-)
>
> Thanks for the info and suggestions ;)
> I trust Linus enough to compile a kernel as root... but maybe that's just me ;)

Well, Linus makes mistakes like everyone else. Besides, he himself
also recommends that people build kernels as non-root :

"I would suggest that people who compile new kernels should:
...
 - compile the kernel in their own home directory, as their very own
   selves. No need to be root to compile the kernel. You need to be root
   to _install_ the kernel, but that's different. "

see http://uwsg.iu.edu/hypermail/linux/kernel/0007.3/0587.html for the
source of that quote.


> (or maybe I trust that I can fix anything that can fsck up my system
> even with root perms ;))
>
> I agree compiling the kernel as a non-root user is perfered but
> sometimes it doesn't happen that way...
>
> - David Brown


--
Jesper Juhl <jesper.juhl@gmail.com>
Don't top-post  http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please      http://www.expita.com/nomime.html

  parent reply	other threads:[~2005-11-27 16:30 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
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 [this message]
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=9a8748490511270830m4bf88fd7v2617f4d2280cc10e@mail.gmail.com \
    --to=jesper.juhl@gmail.com \
    --cc=dmlb2000@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nish.aravamudan@gmail.com \
    --cc=s0348365@sms.ed.ac.uk \
    --cc=willy@w.ods.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®