Am Di, Jul 16, 2024 at 13:14:44 +0200 schrieb Lukas Märdian:
On 16.07.24 11:24, Stephan Seitz wrote:
None of my servers are using WLAN. They all work very well with
ifupdown including bonding/vlans.
This might not be your usecase, but I regularly see setups of "embedded
boards", like Raspberry Pi, that use a server image but have the WiFi
adapter as their primary network interface.
Ah, okay, yes, this is a server case as well.
Sorry, I call this bullshit. I’m using Debian exactly because it feels
different like other distros. There wouldn’t be a need for Debian if
not.
As Colin stated, what I said is that Debian should have a congruent
networking story in itself, independent of the context you're using it
in (desktop, server, cloud, etc.).
Ah, sorry, I really misunderstood it.
But I’m not sure I agree.
Desktop, server, cloud are different flavours with different software and
different user interfaces.
I wouldn’t expect to have a desktop environment on a server, so I would
have a different UI on server and desktop. And while I don’t care which
syntax form the configuration files are if I configure thinks via GUI, it
is different when I only have a CLI.
So I wouldn’t have a problem if different flavours would have different
defaults how things like network are to be configured. These flavours
will probably have different users as target as well.
Many greetings,
Stephan
--
| If your life was a horse, you'd have to shoot it. |
