From: Gregory Shearman <zekeyg@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] sudo in kernel config ?
Date: Sun, 12 Sep 2010 17:29:49 +1000 [thread overview]
Message-ID: <20100912072949.GA17122@pacific.net.au> (raw)
In-Reply-To: <frvbX-6Dv-3@gated-at.bofh.it>
In linux.gentoo.user, you wrote:
>
> Some people, such as myself, use kernel sources outside of portage (I
> follow a git repo) and do so as a non-root user. In this case the
> kernel tree is not owned by root and the config/compile is easily done
> as a non-root user.
>
> If you are super-paranoid. You can make a non-root copy
> of /usr/src/linux and compile it as a non-root user.
>
> But there really isn't any point in using sudo. It's effectively doing
> the same thing that you are trying to avoid.
I agree there's no point in using sudo, but what's the problem? You
don't need to edit the kernel sources merely to build a new kernel. You
can build your kernel outside the tree using for example:
make O=/home/user/kernel/tree/ menuconfig
make O=/home/user/kernel/tree/
All files are put into the user's directory.
All that's need is the KBUILD_OUTPUT environment variable set, so that
drivers can find the kernel .config file etc.
I've built my kernels like this for years now. All kernels are built by
a specific user and then installed as root. No problem, no worries about
permissions and no altering the portage installed kernel sources so that
a purge (emerge -P gentoo-sources) will automatically remove the whole
tree.
--
Regards,
Gregory.
next parent reply other threads:[~2010-09-12 7:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <frufU-519-15@gated-at.bofh.it>
[not found] ` <frvbX-6Dv-3@gated-at.bofh.it>
2010-09-12 7:29 ` Gregory Shearman [this message]
2010-09-12 16:36 ` [gentoo-user] sudo in kernel config ? Bill Longman
2010-09-11 8:24 Stéphane Guedon
2010-09-11 9:46 ` Albert Hopkins
2010-09-11 10:41 ` Stéphane Guedon
2010-09-11 13:43 ` Volker Armin Hemmann
2010-09-11 15:53 ` Albert Hopkins
2010-09-11 20:18 ` Alan McKinnon
2010-09-11 20:35 ` Dale
2010-09-11 20:28 ` Etaoin Shrdlu
2010-09-11 20:49 ` Alan McKinnon
2010-09-11 22:05 ` Peter Humphrey
2010-09-11 22:03 ` Etaoin Shrdlu
2010-09-11 23:06 ` Peter Humphrey
2010-09-12 16:45 ` Al
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=20100912072949.GA17122@pacific.net.au \
--to=zekeyg@gmail.com \
--cc=gentoo-user@lists.gentoo.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