From: Peter Williams <pwil3058@bigpond.net.au>
To: Coywolf Qi Hunt <coywolf@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
torvalds@osdl.org, sam@ravnborg.org
Subject: Re: [q] make modules_install as non-root?
Date: Fri, 02 Dec 2005 14:04:42 +1100 [thread overview]
Message-ID: <438FB9CA.9050004@bigpond.net.au> (raw)
In-Reply-To: <2cd57c900512011859v7f0db82fg@mail.gmail.com>
Coywolf Qi Hunt wrote:
> 2005/12/2, Peter Williams <pwil3058@bigpond.net.au>:
>
>>Coywolf Qi Hunt wrote:
>>
>>>Hello people,
>>>
>>>I wrote my own installkernel so I can do `make install' as non-root
>>>with the help of sudo. But how can we get to do `make modules_install'
>>>as non-root with sudo as well?
>>>
>>>The works of modules_install seem scattered over several places. Is
>>>it a nice idea to factor out an *installmodules* script for `make
>>>modules_install' to invoke?
>>>
>>>ps:
>>>Linus recommend us to build as non-root and install as root.
>>>I ask if we should install as non-root too.
>>
>>Personally, I just use "sudo make install" or "sudo make
>>modules_install" to do installations as an ordinary user. No need for
>>special scripts or modifications to the build procedure.
>
>
> That's rather insecure. You have to add /usr/bin/make in your sudoers,
> then an malicious Makefile could do harm.
Only if you run it with sudo.
> I'm being paranoid. But we
> all are since we avoid to use root.
> --
> Coywolf Qi Hunt
> http://sosdg.org/~coywolf/
--
Peter Williams pwil3058@bigpond.net.au
"Learning, n. The kind of ignorance distinguishing the studious."
-- Ambrose Bierce
next prev parent reply other threads:[~2005-12-02 3:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-02 2:23 [q] make modules_install as non-root? Coywolf Qi Hunt
2005-12-02 2:46 ` Peter Williams
2005-12-02 2:59 ` Coywolf Qi Hunt
2005-12-02 3:04 ` Peter Williams [this message]
2005-12-02 14:21 ` Horst von Brand
2005-12-02 3:11 ` Keith Owens
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=438FB9CA.9050004@bigpond.net.au \
--to=pwil3058@bigpond.net.au \
--cc=coywolf@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.org \
--cc=torvalds@osdl.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