From: Eduardo Pereira Habkost <ehabkost@conectiva.com.br>
To: linux-8086@vger.kernel.org
Subject: Re: MAKEDEV patch
Date: Tue, 15 Jun 2004 10:35:11 -0300 [thread overview]
Message-ID: <20040615133511.GU26330@duckman.distro.conectiva> (raw)
In-Reply-To: <20040611201338.71829.qmail@web51305.mail.yahoo.com>
[-- Attachment #1: Type: text/plain, Size: 1294 bytes --]
Hi, Tommy,
On Fri, Jun 11, 2004 at 01:13:38PM -0700, Tommy McCabe wrote:
> This patch uses sudo to do the mknods in MAKEDEV.
>
>
> --- ./elkscurr/elkscmd/rootfs_template/dev/MAKEDEV
> 2004-06-11 16:01:53.000000000 -0400
> +++ ./elks/elkscmd/rootfs_template/dev/MAKEDEV
> 2004-06-11 15:54:50.000000000 -0400
> @@ -13,7 +13,7 @@
> # Refer to the MAKESET command, also in this
> directory, for usage details.
>
> LINK=ln
> -MKDEV=mknod
> +MKDEV=sudo -u root mknod
> MKSET=./MAKESET
I think that making everybody use sudo to build the disk images *and*
breaking the MAKEDEV script (that is supposed to run inside elks, too),
is not a good thing.
We should instruct the users to build the disk images as root (or better:
find a way to build the disk images without the need of root privileges,
some day), but not inserting 'sudo' everywhere on the buildsystem. We
can have users that:
- Don't like sudo
- Don't use sudo, and don't want to configure it
- Don't know how to configure sudo
- Use sudo, and have a small password timeout, and don't wat to be asked
for the password many times during the disk images building
If you want to use sudo to build the disk images, please use
'sudo make <sometarget>', it is easier and simpler.
--
Eduardo
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-06-15 13:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-11 20:13 MAKEDEV patch Tommy McCabe
2004-06-15 13:35 ` Eduardo Pereira Habkost [this message]
2004-06-28 15:50 ` Miguel Bolanos
-- strict thread matches above, loose matches on Subject: below --
2004-06-03 15:40 Pat Gilliland
2004-06-02 21:04 Tommy McCabe
2004-06-03 12:21 ` Eduardo Pereira Habkost
2004-06-03 13:52 ` Tommy McCabe
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=20040615133511.GU26330@duckman.distro.conectiva \
--to=ehabkost@conectiva.com.br \
--cc=linux-8086@vger.kernel.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