SoylentNews is people
SoylentNews
Michael Biebl, long-time maintainer of systemd for Debian (2010 or earlier, based on changelog.Debian.gz), is taking undetermined holidays from packaging it. The e-mail was short:
Will stop maintaining systemd in debian for a while.
What's going on is just too stupid/crazy.
This takes place after he discussed a bug in which he expected systemd to respect local settings, and not rename network devices:
@yuwata a default policy like /lib/systemd/network/99-default.link should never trump explicit user configuration.
Later he seems surprised about how things roll there:
I'm amazed that I have to point this out....
The issue is locked currently, and also archived just in case, so everyone can read the initial report and the replies he got.
Opinion: It seems distribution developers are starting to get the stick too, not just users with their "errors" (taken from a reply). Will distributions finally wake up or is that they don't still grok the attitude of projects like this? [Or is it something else? --Ed.]
(Score: 1, Interesting) by Anonymous Coward on Monday January 21 2019, @09:53PM (2 children)
It's not just "beginners." When you have a server with multiple interfaces and need the names to never change, you can be expected to be someone who knows what they are doing and can enable this feature. On the other hand, most desktops, laptops, and many servers have only one interface, or maybe one ethernet and one wifi, which have different names anyway. "Predictable" network names means that you have no idea what the names are going to be, but traditional names are always eth0/wlan0 regardless of your hardware, as long as you fall into this common case. Predictable depends on your situation and your perspective, not just your experience level.
(Score: 3, Insightful) by jdccdevel on Tuesday January 22 2019, @12:07AM (1 child)
For situations with only one network device I see this as a non-issue. The VAST majority of these users have no idea that their network device is called "eth0" or anything else. They will never even see it, nor will they need to care, the distro install tools and the GUI will hide those details from them.
For the relative few entering commands in a terminal, or following a script of some sort... Those sorts of users are perfectly capable of running a couple of commands to find out what their network device's name is, and substituting that in the commands themselves as required.
Seriously, it's not hard to do. It can almost be automated. Give them instructions to enter "ip link show" or "ifconfig -a", or give them a little script to find out what their network device is called.
Yes, not having the name always be eth0 stops some people from copy/pasting from the Internet. IMHO that's not a bad thing, it encourages a better understanding of what the commands they're running are actually doing if they have to edit them to replace a device name.
Alternatively, If you already have a good understanding of what's going on, adding "ip link show" to the set of commands you're familiar with is probably a good thing.
TLDR: Real novices will never see the device name anyway (It'll hidden behind a gui), and power users can easily adjust.
(Score: 0) by Anonymous Coward on Tuesday January 22 2019, @09:03AM
Thank YOU
This is what keeps me employed and will continue to do so for some time.