From: Willy Tarreau <willy@w.ods.org>
To: David Brown <dmlb2000@gmail.com>
Cc: 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 07:07:34 +0100 [thread overview]
Message-ID: <20051127060734.GM11266@alpha.home.local> (raw)
In-Reply-To: <9c21eeae0511261751p6741ad4fgd3f3d762e4c377f6@mail.gmail.com>
On Sat, Nov 26, 2005 at 05:51:34PM -0800, David Brown wrote:
> > Maybe you are untarring as non-root and David is untarring as root?
>
> Yeah you can't very well compile and install a kernel without
> permissions to /boot ;)
I disagree with you David. It's been years since I last compiled a
kernel as root, and even longer without untarring it as root ! I have
/usr/src chmod g+w for group "linux" to which I belong. I untar new
kernels there, compile them, etc... as my own user. Then I only do:
$ sudo make modules_install
$ sudo cp arch/i386/boot/bzImage System.map .config /boot/<version>
$ sudo vi /etc/lilo.conf
$ sudo lilo
And it brings me real advantages : during all the compilation phase,
I can use everything I have in *my* environment, aliases, functions,
scripts, tools, etc... that I would not necessarily have as root.
Believe me, for no reason I would switch back to the old age when
I did all this as root !
Regards,
Willy
next prev parent reply other threads:[~2005-11-27 6:07 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
2005-11-27 1:51 ` David Brown
2005-11-27 6:07 ` Willy Tarreau [this message]
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=20051127060734.GM11266@alpha.home.local \
--to=willy@w.ods.org \
--cc=dmlb2000@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nish.aravamudan@gmail.com \
--cc=s0348365@sms.ed.ac.uk \
/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®