[opensuse] using minicom without beeing root
Is there a way to run minicom without beeing root? Now, when I call minicom, I get the message: minicom: cannot open /dev/ttyS0: Permission denied -- Cristea Bogdan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
I reply to myself. Changing the owner with chmod of the ttySn will do the trick. On 5/16/07, Cristea Bogdan <cristeab@gmail.com> wrote:
Is there a way to run minicom without beeing root? Now, when I call minicom, I get the message:
minicom: cannot open /dev/ttyS0: Permission denied
-- Cristea Bogdan
-- Cristea Bogdan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
sorry, with chown On 5/16/07, Cristea Bogdan <cristeab@gmail.com> wrote:
I reply to myself. Changing the owner with chmod of the ttySn will do the trick.
On 5/16/07, Cristea Bogdan <cristeab@gmail.com> wrote:
Is there a way to run minicom without beeing root? Now, when I call minicom, I get the message:
minicom: cannot open /dev/ttyS0: Permission denied
-- Cristea Bogdan
-- Cristea Bogdan
-- Cristea Bogdan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
You may try adding the relevant user to the uucp group. That worked for me Regards Sean Cristea Bogdan wrote:
sorry, with chown
On 5/16/07, Cristea Bogdan <cristeab@gmail.com> wrote:
I reply to myself. Changing the owner with chmod of the ttySn will do the trick.
On 5/16/07, Cristea Bogdan <cristeab@gmail.com> wrote:
Is there a way to run minicom without beeing root? Now, when I call minicom, I get the message:
minicom: cannot open /dev/ttyS0: Permission denied
-- Cristea Bogdan
-- Cristea Bogdan
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wednesday 16 May 2007 09:19, Sean Craig wrote:
You may try adding the relevant user to the uucp group. That worked for me
Ditto. It's a more flexible method if you have other users that need minicom access as well. BTW, this may be a silly question to ask on a linux list but does anyone know of a way to do this under windows? I have this exact problem with a piece of software that only runs on windows and it seems absurd to me that the only way to get around it is to run the software as an administrator. Cheers, James. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
James Watkins wrote:
On Wednesday 16 May 2007 09:19, Sean Craig wrote:
You may try adding the relevant user to the uucp group. That worked for me
Ditto. It's a more flexible method if you have other users that need minicom access as well. BTW, this may be a silly question to ask on a linux list but does anyone know of a way to do this under windows? I have this exact problem with a piece of software that only runs on windows and it seems absurd to me that the only way to get around it is to run the software as an administrator.
One of the "features" of Windows, is that many of what should be user level apps have to be run as root. With some apps, you can configure them to run as admin, even when the user doesn't have admin privileges. However the appropriate password has to be entered. -- Use OpenOffice.org <http://www.openoffice.org> -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wednesday 16 May 2007 12:39, James Knott wrote:
One of the "features" of Windows, is that many of what should be user level apps have to be run as root. With some apps, you can configure them to run as admin, even when the user doesn't have admin privileges. However the appropriate password has to be entered.
That's the problem, as soon as they get the password they add themselves to the administrators group and before you can say 'malware' they've got 15 search bars in IE and they're complaining that their computer is running slowly. I dare say you might be able to input the password once and have windows remember it for you but how long would it be before it forgot it again? Anyway, this is a bit off topic so guess I should shut up now. Cheers, James. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Cristea Bogdan wrote:
I reply to myself. Changing the owner with chmod of the ttySn will do the trick.
That's the wrong way to do it, as other users still won't be able to use it. The proper method is to add yourself to the group it belongs to, which is uucp. -- Use OpenOffice.org <http://www.openoffice.org> -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Cristea Bogdan wrote:
Is there a way to run minicom without beeing root? Now, when I call minicom, I get the message:
minicom: cannot open /dev/ttyS0: Permission denied
What permissions do you have on ttyS0. On my system is shows crw-rw---- 1 root uucp 4, 64 2006-11-25 06:43 /dev/ttyS0 Try adding yourself the the uucp group and see what happens. You'll have to log out and in after adding yourself to the group. -- Use OpenOffice.org <http://www.openoffice.org> -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wednesday 16 May 2007 01:26, Cristea Bogdan wrote:
Is there a way to run minicom without beeing root? The cool thing about *nix is that there are 100s of ways to do everything...
... I use sudo for this purpose. I used visudo to edit the /etc/sudoers file, to grant my comm group access to the minicom command. The neat thing about this technique is that I have the added advantage of system logging (thru sudo) for the few folks who actually need access to the physical comm port through minicom, and without giving everyone access to uucp. First, add the user to a comm group which you create for this purpose. Then use the visudo command to edit the /etc/sudoers file to give the comm group access to the /usr/bin/minicom command as root. The user can then access the comm port through minicom as root through the sudo command (with logging) by providing "their own" password: sudo /usr/bin/minicom (the user will be prompted for their own password, and the action is logged) There are zillions (I exaggerate) of combinations and permutations on this theme, but the important part for me as an admin is authentication and logging. Sudo works well for this if properly setup. On the other hand, if you're the only user on the system then adding yourself to the uucp group works... but if the machine is shared (or in my case used as a comm tty into the server sitting next to it) then you really need a way to control access with logging. -- Kind regards, M Harris <>< -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (5)
-
Cristea Bogdan -
James Knott -
James Watkins -
M Harris -
Sean Craig