On Thu, 2025-10-16 at 23:28 +0000, Bob Marčan via users wrote: > Why not complicate everything together, when it is enough just to > change the name chosen by one of the developers, who undoubtedly grew > up in Windows. > The use of space in any names is idiocy. After all, we are not > writers. > If you like it, don't be distracted. I myself will continue to rename > these idiocies.
If I were doing this via the command line, I'd be naming things in a way that was damn easy to type, and minimally error-prone. e.g. normal-lan, test-lan (short, no spaces, no capitals, etc). I do the same with any files/directories that may be accessed via a network or command line. But I'm doing Network Manager things via a GUI, and what they've called a Connection Name I've used as a description, such as: fixed IP 192.168.1.1 (normal LAN) fixed IP 192.168.0.10 (test LAN) DHCP client (full DHCP configuration) With *it* I have given in and used blank spaces. Having said that, I may just make one entry called "normal" for the day I have to debug something on the command line. But it seems, to me, that it would be a good idea if it had separate name *and* description fields in Network Manager. I still hate the very user-unfriendly network device names. e.g. My ethernet is enp0s31f6, it's the only connector on the motherboard, it's not in a slot, so any slot numbers make no sense to me and are completely unguessable. I could give it an alias, but the moment I have to debug a non-working system and that alias isn't working, I'm back to square one of having to discover what it is, then type in that abomination. -- uname -rsvp Linux 3.10.0-1160.119.1.el7.x86_64 #1 SMP Tue Jun 4 14:43:51 UTC 2024 x86_64 (yes, this is the output from uname for this PC when I posted) Boilerplate: All unexpected mail to my mailbox is automatically deleted. I will only get to see the messages that are posted to the mailing list. -- _______________________________________________ users mailing list -- [email protected] To unsubscribe send an email to [email protected] Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/[email protected] Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
