Le 07/10/2017 à 10:39, J. Fahrner a écrit :
Am 2017-10-07 09:43, schrieb Florian Zieboll:
From another point of view one could argue, that your device had
already been unstable... why else would you have had to repair it?
In this case, the modification of your "persistent-net-rules" file
could be seen as (the most easy) part of a successful fix.
Formerly you could put a hard disc with a Linux system in some similar
pc and it would run. The linux kernel detects all hardware and the
basic functionality was given without any modifications (including
networking, which is basic, because without network you cannot install
additional packages).
But nowadays Linux becomes more and more Windows-like. On EFI-systems
it does not boot because EFI needs to know where to find the boot
loader. And network is not available because sytemd'ish networking
changes network devices. A systemd Linux becomes more and more like a
windows system. And this is why we are here at Devuan!
This has nothing to do with Linux becoming Windows-like, nor
Systemd. Udev started doing that a dozen years ago, at least, and
Windows desktop or laptops do not need that feature more than Linux's.
This feature is essentially dedicated to servers with multiple network
connections, which is the domain where Linux dominates.
EFI responds to a need for security, because, without it, it is so
easy, in a few minutes, with a simple USB memory stick to steal and/or
fuck-up the contents of any PC. It's a bad response because, IIUC, it is
enough to have an EFI-compatible boot-loader, but... well tried :-)
Didier
_______________________________________________
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
