Sujet : Re: Now I've done it
De : sc (at) *nospam* fiat-linux.fr (Stéphane CARPENTIER)
Groupes : comp.os.linux.advocacyDate : 17. May 2025, 12:14:01
Autres entêtes
Organisation : Mulots' Killer
Message-ID : <68286f79$0$28048$426a34cc@news.free.fr>
References : 1 2 3 4 5 6 7 8 9 10 11 12
User-Agent : slrn/pre1.0.4-9 (Linux)
Le 17-05-2025, rbowman <
bowman@montana.com> a écrit :
On 16 May 2025 20:59:04 GMT, Stéphane CARPENTIER wrote:
>
Le 16-05-2025, Farley Flud <fsquared@fsquared.linux> a écrit :
On Fri, 16 May 2025 01:34:50 +0000, rbowman wrote:
>
>
I certainly didn't need an excursion into udev rules earlier this
week.
>
>
Udev is another piece of unnecessary junk that was foisted on all
distros. For a standalone workstation, static device nodes are the best
solution but the universal opinion is that static nodes are obsolete
and have no place in a modern GNU/Linux.
You are confused. A standalone workstation isn't the same thing as an
unused workstation. Anyone has a lot of reason to plug things on a
started workstation. And being able to do the difference between a well
known usb key and a garbage plugged into a computer is very important.
>
All I really wanted to do is have picotool flash a pico without using
sudo. The Raspberry Pi Pico extension in VS code has a 'Run' button to
flash a device in the BOOTSEL mode and start execution. For some reason it
worked on Ubuntu but failed on Fedora, requiring an invocation with sudo.
>
The strange thing is I couldn't figure out why the difference other than
it is a snap on Ubuntu and not a flatpak on Fedora. The snap may be
working some magic that doesn't require a rule. I see a lot of rules like
70-snap.gnome-mahjongg.rules in /etc/udev/rules.d but nothing for
picotool. It's not in /lib/udev/rules.d either.
>
I stopped digging when I got it to work on Fedora.
I'm not saying it's easy and well managed everywhere. I'm saying that
there are good reasons to have it available.
The difference between Ubuntu and Fedora can be in the rights on the
file system. I don't know about your particular case, but I saw it a few
weeks ago on another issue. That's a fun think about Linux, it's a Unix
system so everything is a file. And it can be cumbersome to find which
file can be opened/executed only by root.
-- Si vous avez du temps à perdre :https://scarpet42.gitlab.io