public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Bill Longman <bill.longman@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] sudo in kernel config ?
Date: Sun, 12 Sep 2010 09:36:44 -0700	[thread overview]
Message-ID: <AANLkTimYc=jezS0k6aKmGaeYny3GfT31XrKOjmLjottQ@mail.gmail.com> (raw)
In-Reply-To: <20100912072949.GA17122@pacific.net.au>

[-- Attachment #1: Type: text/plain, Size: 526 bytes --]

> 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/
>
>
This is how I do it, too, when testing the kernel before I do it for real.
This way, the code stays owned by root and I can make to my hearts content,
with different kernels going into different directories that I control.

-- 
Bill Longman

[-- Attachment #2: Type: text/html, Size: 766 bytes --]

  reply	other threads:[~2010-09-12 16:37 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   ` [gentoo-user] sudo in kernel config ? Gregory Shearman
2010-09-12 16:36     ` Bill Longman [this message]
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='AANLkTimYc=jezS0k6aKmGaeYny3GfT31XrKOjmLjottQ@mail.gmail.com' \
    --to=bill.longman@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