From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Cc: Dale <rdalek1967@gmail.com>
Subject: Re: [gentoo-user] Re: sudo in kernel config ?
Date: Sun, 12 Sep 2010 01:17:22 +0200 [thread overview]
Message-ID: <201009120117.22392.alan.mckinnon@gmail.com> (raw)
In-Reply-To: <4C8BF8DB.7030502@gmail.com>
Apparently, though unproven, at 23:47 on Saturday 11 September 2010, Dale did
opine thusly:
> >> My point was, if the sources are say in the user group, then any user
> >> can edit them? Right now, they are in the root group and owned my root
> >> which for security reasons is a good idea. That way a regular user can't
> >> edit or modify the kernel sources.
> >
> > The group can only write if the files have the group write permission
> > set. Still in Unix 101 domain, hehe :)
>
> I know that. Why would a person want anyone BUT root to be able to
> access and change the kernel sources? Lets see if asking it this way
> makes more sense. lol
Gentoo does things different. If you read Documentation/* in the kernel
sources, you will not find there what Gentoo has.
/usr/src/linux was intended by the kernel devs[1] to be where the system
headers are stored - what glibc uses to build. Like everything else in /usr/
this is obviously writeable for root only (usually).
The intent is that you download kernel sources to ~, build there and sudo make
install.
Gentoo needs a kernel tree (not just headers) for all manner of stuff to build
against. These days many distros also do it this way to accommodate the needs
of getting nvidia-drivers and vm products to build their drivers etc. This
must obviously also be writeable only for root.
So, the ancient "advice" about not building as root is bullshit. It might have
been good advice once but like all advice it's time is past.
To answer your question:
"You wouldn't. Anything else is just daft."
[1] this itself might be ancient cruft and hopelessly out of date
--
alan dot mckinnon at gmail dot com
next prev parent reply other threads:[~2010-09-11 23:17 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-11 8:24 [gentoo-user] sudo in kernel config ? 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:34 ` [gentoo-user] " Nikos Chantziaras
2010-09-11 20:51 ` Alan McKinnon
2010-09-11 21:05 ` Nikos Chantziaras
2010-09-12 8:14 ` Stéphane Guedon
2010-09-11 20:35 ` [gentoo-user] " 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-11 23:15 ` [gentoo-user] Re: [OT] " Etaoin Shrdlu
2010-09-12 9:16 ` Peter Humphrey
2010-09-12 10:24 ` Etaoin Shrdlu
2010-09-12 16:45 ` [gentoo-user] " Al
2010-09-11 20:42 ` [gentoo-user] " Nikos Chantziaras
2010-09-11 20:49 ` Dale
2010-09-11 21:01 ` Nikos Chantziaras
2010-09-11 21:30 ` Alan McKinnon
2010-09-11 21:47 ` Dale
2010-09-11 23:17 ` Alan McKinnon [this message]
2010-09-12 16:59 ` walt
2010-09-11 17:59 ` Nikos Chantziaras
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=201009120117.22392.alan.mckinnon@gmail.com \
--to=alan.mckinnon@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
--cc=rdalek1967@gmail.com \
/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