ls -l would hve been better, It will show if this is a symlink and when yes to what and you are then able to do an ls -l of that device file and show it’s permissions. When not it will show permissions directly.
Also saying “when I try to connect/open device” is not very informative. You have to see these things from thje computers interpratation side. And the computer does not know any “I”. It does know loged in users. Also it is always much, much better to not say: “When I …, Then …”, show what you did and what the computer did. Copy/paste from the terminal into a post here. Like you did with those ls commands above.
And that is done in the terminal isn’t it?
So you did do something in the terminal. Though not the program cutecom. And yes, when you would have explained that it is a GUI program that would have been more informative.
As it is we still wait for the ownership and permissions of the device file as asked above. So the ls -l as asked above and when they are symlinks, then allso an ls -l of the file that they point to.
If you should run cutecom as root I do not know. The documentation should tell you. But because “never run anything as root when it is not explicetly needed” you should not do that with the idea: Oh, I can always try as root
cutecom in itself runs fine either as a root or anything else
Perhaps it should, but I didn’t find anything?
Good advice, however my reasons for asking this were not “…I can always try as root …” rather a suspicion that my problems with opening of the device might have something to do with ownership and permissions.
So, I did run cutecom as root and device seems to have opened OK.
What I tried to do until now is finding out if a “normal” user may use the device. By looking at it’s permissions. Not by forcing things jumping in where it is at it deepestt and using root.
Understanding things first is better. Thus when you have such a thing which looks very much like a permission problem, the obvious questions are:
who runs the process?
which file does it try to access?
who owns that file and what are it’s permissions?
Alas it takes some time to find out due to some misunderstandings about my questions. And still instead of providing the information you are runnning loose using root. :’(. The very last thing you should do.
On Wed 22 Jun 2016 03:36:02 PM CDT, bambuko wrote:
> …I am still not convinced that it is a good idea to use root…
Is there an alternative in this particular case?
> …But that maybe due to the fact that I have no idea what the
> application is for…
it’s to use AT commands to modify/set bluetooh module.
If you google it up you will find kids playing with Arduino etc doing
I wanted to do it with my Linux machine.
> …When you think your problem is solved, that is nice for you.
It may not be nice and proper?, but I have been able to connect to the
device and do what I needed.
Why not use the arduino IDE? Anyway, adding your user to the tty
group should have sufficed, else maybe a udev rule to temporarily give
your ‘user’ access.
Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890)
openSUSE Leap 42.1|GNOME 3.16.2|4.1.26-21-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!
I looked briefly at groups etc, but was so out of depth there, that soon abandoned this idea.
udev rule… would probably take me longer to learn, than what the actual job take;)
The reason for not using Arduino etc is that it is a one off job, which takes about 1 minute (once everything is working OK), so the plan was - no additional expenditure etc, just use what is already available to me, plus nothing permanent etc, etc.
I know you “proper” Linux people shudder at my blunderings … but job got done.
I am sure you are right
but I come from the world where there is me and my pc
there are no administrators, superusers, alternative users, groups … etc, etc,
so I wouldn’t even know where to start with groups (or why do I need them?)
I do appreciate how difficult it must be for all you guys trying to help someone like me … lol!
thank you for trying!
In the *NIX world (everything that looks like UNIXR - Linux, Android, Apple Mac OS, BSD, IBM AIX, Sun Solaris, HP-UX, . . . ) groups are a fundamental feature of system security – even for a single user box.
Because the *NIX world splits off system functions and the associated system processes to various pseudo-users with associated Groups and Group-Access-Rights and Group-Privileges, the *NIX systems tend to be inherently robust against attacks via the network. If a user is compromised then, only that user’s data (files) can be damaged by the entity which managed to break into the system.
[HR][/HR]Bottom line: this is one of the reasons why there are not that many Anti-Virus applications on the market for *NIX systems and therefore also Linux systems.