Bsrgvty

My 15 year old son is gay. How do I express my feelings about this?

I reverse the source code, you negate the output!

Do the villains know Batman has no superpowers?

The quicker I go up, the sooner I’ll go down - Riddle

Resolving moral conflict

Social leper versus social leopard

Where Does VDD+0.3V Input Limit Come From on IC chips?

Why is the missed-approach course for the "RNAV (GNSS) - A" approach to runway 28 at ENSB shaped all funny?

How to deal with my team leader who keeps calling me about project updates even though I am on leave for personal reasons?

How to manage expenditure when billing cycles and paycheck cycles are not aligned?

Algorithm that spans orthogonal vectors: Python

Does wetting a beer glass change the foam characteristics?

Do we know the situation in Britain before Sealion (summer 1940)?

A drug that allows people to survive on less food

Will Proving or Disproving of any of the following have effects on Chemistry in general?

Examples of "unsuccessful" theories with afterlives

Norwegian refuses EU delay (4.7 hours) compensation because it turned out there was nothing wrong with the aircraft

I feel like most of my characters are the same, what can I do?

Idiom for "I came, I saw, I ate" (or drank)

What are these pixel-level discolored specks? How can I fix it?

Conditionally execute a command if a specific package is loaded

Is it impolite to ask for halal food when traveling to and in Thailand?

What is the need of methods like GET and POST in the HTTP protocol?

Is It Possible to Have Different Sea Levels, Eventually Causing New Landforms to Appear?

WANTED: User-friendly way to assign owner/permission when attaching a new serial devices (USB, BT, etc)

Configure udev to change permissions on USB HID device?Give write access to USB and Serial devices automatically

.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;

0

1

When attaching a serial device (e.g an arduino via USB or Bluetooth), the owner:group is set as root:dialout, e.g:

crw-rw---- 1 root dialout 166, 0 Apr 15 18:08 /dev/ttyACM0

However, even when the regular user is part of the dialout group, it is necessary to change permissions on the device file (to 666).

This is only temporary until the device has been disconnected. A persistent solution is to modify the udev file. See e.g. this link and this link

This can be confusing, not least when the Bluetooth system tool (blueDevil on KDE) can detect USB devices, but not connect to them.

It seems to me, that either the default behaviour should be to grant dialout users write access or at the least this should be part of the GUI system setting tools.

$id
uid=1000(soon) gid=1000(soon) groups=1000(soon),4(adm),20(dialout),24(cdrom),27(sudo),30(dip),46(plugdev),116(lpadmin),126(sambashare)

usb permissions bluetooth udev

share|improve this question

edited Apr 15 at 16:50

Søren ONeill

asked Apr 15 at 16:27

Søren ONeillSøren ONeill

111 bronze badge

• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  Group members have write permission. The permissions is rw for owner and rw for group.
  
  – vidarlo
  Apr 15 at 16:32
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  That's true ... the issue basically remains the same however: the user can not access the device, but root can. Now I can't really see why....
  
  – Søren ONeill
  Apr 15 at 16:42
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Edit your question to include the output of id
  
  – vidarlo
  Apr 15 at 16:45
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Done! I've added id above
  
  – Søren ONeill
  Apr 15 at 17:57
  

  
  
  
  

add a comment
 | 

0

1

When attaching a serial device (e.g an arduino via USB or Bluetooth), the owner:group is set as root:dialout, e.g:

crw-rw---- 1 root dialout 166, 0 Apr 15 18:08 /dev/ttyACM0

However, even when the regular user is part of the dialout group, it is necessary to change permissions on the device file (to 666).

This is only temporary until the device has been disconnected. A persistent solution is to modify the udev file. See e.g. this link and this link

This can be confusing, not least when the Bluetooth system tool (blueDevil on KDE) can detect USB devices, but not connect to them.

It seems to me, that either the default behaviour should be to grant dialout users write access or at the least this should be part of the GUI system setting tools.

$id
uid=1000(soon) gid=1000(soon) groups=1000(soon),4(adm),20(dialout),24(cdrom),27(sudo),30(dip),46(plugdev),116(lpadmin),126(sambashare)

usb permissions bluetooth udev

share|improve this question

edited Apr 15 at 16:50

Søren ONeill

asked Apr 15 at 16:27

Søren ONeillSøren ONeill

111 bronze badge

• 
  
  
  

  
  1
  

  
  
  
  
  
  

  
  
  Group members have write permission. The permissions is rw for owner and rw for group.
  
  – vidarlo
  Apr 15 at 16:32
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  That's true ... the issue basically remains the same however: the user can not access the device, but root can. Now I can't really see why....
  
  – Søren ONeill
  Apr 15 at 16:42
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Edit your question to include the output of id
  
  – vidarlo
  Apr 15 at 16:45
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Done! I've added id above
  
  – Søren ONeill
  Apr 15 at 17:57
  

  
  
  
  

add a comment
 | 

When attaching a serial device (e.g an arduino via USB or Bluetooth), the owner:group is set as root:dialout, e.g:

crw-rw---- 1 root dialout 166, 0 Apr 15 18:08 /dev/ttyACM0

However, even when the regular user is part of the dialout group, it is necessary to change permissions on the device file (to 666).

This is only temporary until the device has been disconnected. A persistent solution is to modify the udev file. See e.g. this link and this link

This can be confusing, not least when the Bluetooth system tool (blueDevil on KDE) can detect USB devices, but not connect to them.

It seems to me, that either the default behaviour should be to grant dialout users write access or at the least this should be part of the GUI system setting tools.

$id
uid=1000(soon) gid=1000(soon) groups=1000(soon),4(adm),20(dialout),24(cdrom),27(sudo),30(dip),46(plugdev),116(lpadmin),126(sambashare)

usb permissions bluetooth udev

share|improve this question

edited Apr 15 at 16:50

Søren ONeill

asked Apr 15 at 16:27

Søren ONeillSøren ONeill

111 bronze badge

crw-rw---- 1 root dialout 166, 0 Apr 15 18:08 /dev/ttyACM0

$id
uid=1000(soon) gid=1000(soon) groups=1000(soon),4(adm),20(dialout),24(cdrom),27(sudo),30(dip),46(plugdev),116(lpadmin),126(sambashare)

share|improve this question

edited Apr 15 at 16:50

Søren ONeill

asked Apr 15 at 16:27

Søren ONeillSøren ONeill

111 bronze badge

share|improve this question

edited Apr 15 at 16:50

Søren ONeill

asked Apr 15 at 16:27

Søren ONeillSøren ONeill

111 bronze badge

asked Apr 15 at 16:27

Søren ONeillSøren ONeill

111 bronze badge

asked Apr 15 at 16:27

Søren ONeillSøren ONeill

111 bronze badge