Arch Linux

Weinman

Member

Registered: 2023-12-30

Posts: 6

Messed up with /dev/tty* permissions and ownership

I am experimenting with flipper zero and ESP32S2 wifi dev board.

The thing is, when flashing the firmware to the board, I was asked to have permissions on dialout group in order to flash it.

The group didn't even exist. So I created it and added my user to the group.

Then, I executed

sudo chown :dialout /dev/tty*
   sudo chmod g+rw /dev/tty*

Well, that went really fine. I flashed the firmware neatly and... Kind of biggie messed up.

So I have tried to revert this stuff, changing ownership to :tty and using

chmod a+rw /dev/tty*

...
also tried

chown root:tty and chmod 0666 /dev/tty*

...

Finally, while restarting, seems like I am able to mount pendrives, but I have to remount them for rw mode.

So, my lesson is definitely: 'If I am gonna mess with serious configuration, make a backup'

But, could anyone kindly tell me which permisions and ownership should have /dev/tty* and how to make it for automatically mounting USB devices as before? Now I cannot update my flipper zero

Weinman

Member

Registered: 2023-12-30

Posts: 6

Re: Messed up with /dev/tty* permissions and ownership

I know now that what I should have done is editing an udev rule instead of this mess. Will do it later on.

Weinman

Member

Registered: 2023-12-30

Posts: 6

Re: Messed up with /dev/tty* permissions and ownership

OK, seems like whenever the OS is rebooted, the permissions fall back to normal. However, I still have that very same problem as before: Now, I have to remount any USB device so that they are accessed in rw mode

WorMzy

Administrator

From: Scotland

Registered: 2010-06-16

Posts: 13,554

Website

Re: Messed up with /dev/tty* permissions and ownership

Yes, the pseudo filesystems (like /dev and /sys) are transient and are created at boot time. To understand what is happening, please post a journal from a boot where you needed to remount a filesystem.

https://wiki.archlinux.org/title/List_o … n_services

---

Sakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD

Making lemonade from lemons since 2015.

Weinman

Member

Registered: 2023-12-30

Posts: 6

Re: Messed up with /dev/tty* permissions and ownership

Yes, the pseudo filesystems (like /dev and /sys) are transient and are created at boot time. To understand what is happening, please post a journal from a boot where you needed to remount a filesystem.

https://wiki.archlinux.org/title/List_o … n_services

I will post udevadm and journalctl as soon as I filter a little bit. Thanks for the tip

Weinman

Member

Registered: 2023-12-30

Posts: 6

Re: Messed up with /dev/tty* permissions and ownership

Well... Don't ask me how or why, but after a few restarts and an OS update (yay -Syu)...

It just works well.

I guess that when updating, the configs got corrected.

I have kept the logs (I was going to upload them, now that I had time), and I will extract the latest logs and try to check what happened.

So, well, I guess it is solved.

I changed the group in the udev rules created for flipper zero from 'dialout' to 'uucp' which is what I should have done before. The problem was still persisting, even when restarting the laptop, so my guess this has happened with the OS update, as I said earlier.

Well, got my lessons, and I appreciate the apportation of @WorMzy, since now I know bpaste and I love it.

Thank you very much