Why doesn't that developer have his own PC?
If the developer needs to write his own kernel modules, then he needs
root privileges anyway.
But if he just develops applications for an embedded system, which
already has debugged modules, then the devices can be created beforehand
(manually or via udev, as already suggested by someone else).
--- Omer
On Mon, 2008-05-05 at 22:39 +0800, Ohad Levy wrote:
> for embedded platform development, its required to create devices
> which are hardware specific (i.e. our own modules).
>
> any way to reduce the risk?
>
> Thanks
>
>
> On Mon, May 5, 2008 at 10:32 PM, Shachar Shemesh <[EMAIL PROTECTED]>
> wrote:
>
> Ohad Levy wrote:
> Hello All,
>
> Is there any risk to give a user sudo rights of mknod?
> as far as I understand it now, it can only create new
> devices, therefor the risk for a running system is
> minimal.
>
> Thanks,
> Ohad
> As others mentioned, giving someone the right to mknod is
> equivalent to giving them root in a fairly straight forward
> way.
>
> May I ask, though, why you want to allow them to mknod?
>
> Shachar
--
One does not make peace with enemies. One makes peace with former
enemies.
My own blog is at http://www.zak.co.il/tddpirate/
My opinions, as expressed in this E-mail message, are mine alone.
They do not represent the official policy of any organization with which
I may be affiliated in any way.
WARNING TO SPAMMERS: at http://www.zak.co.il/spamwarning.html
=================================================================
To unsubscribe, send mail to [EMAIL PROTECTED] with
the word "unsubscribe" in the message body, e.g., run the command
echo unsubscribe | mail [EMAIL PROTECTED]
