[DNG] Firefox >= 57 will NOT support Zoom Page plugin!
Firefox under ASCII is threatening that the plugin ZOOM PAGE will cease to function soon. The reason given is the plugin does not use the WebExtensions API, whatever that is. I am one who needs bigger than normal rendering of pages, why is this happening? What has become of accessibility? It seems advertisers are putting too much pressure on Mozilla to change anything they think can be used to block or hide adverts. It seems today's sole principle is money, money, money and yet more money! To hell with accessibility and individual needs. If someone happens to have an aversion for manipulative advertising, to hell with them! ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Firefox >= 57 will NOT support Zoom Page plugin!
Try https://addons.mozilla.org/en-US/firefox/addon/zoom-page-we/ instead. The Web Extensions API is Mozilla's attempt to get various plugin-related performance problems under control. While Firefox had its own performance problems, the users who complained that Firefox would drain their laptop's battery in 3.14 seconds often had some extension that "helped". So Mozilla made a whitelist of functions plugins can call, took advantage of the compatibility break to make some other improvements, and announced that starting with FF57 plugins can only use the whitelisted functions. It seems possible to modify Zoom Page to the new regime. Anyway there's a working alternative. Arnt ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] systemd-udevd: renamed network interface eth0 to eth1
Hello, I found the message "systemd-udevd[415]: renamed network interface eth0 to eth1" in my dmesg log. 1. why is there a systemd daemon? 2. why is my ethernet device renamed? I would like it as eth0 and wlan0, not eth1 and wlan1. Jochen ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] systemd-udevd: renamed network interface eth0 to eth1
Le 06/10/2017 à 18:12, J. Fahrner a écrit :
Hello,
I found the message
"systemd-udevd[415]: renamed network interface eth0 to eth1"
in my dmesg log.
1. why is there a systemd daemon?
2. why is my ethernet device renamed?
I would like it as eth0 and wlan0, not eth1 and wlan1.
Jochen
If your machine is running Devuan, you shouldn't have Systemd
running. Maybe "Systemd-udev" is just the new name for "Udev". Since the
advent of Udev, the interfaces are renamed automatically, by Udev, when
they are discovered by the kernel. The goal is to have a stable
interface name attached to any given interface, given that there is no
guaranty on the order in which the kernel discovers the interfaces. Udev
remembers the MAC addresses of the interfaces and gives them stable
numbers. For that, it asks the kernel to rename them. When a yet unknown
interface is discovered it is given the lowest unused number.
The rationale behind this is debatable and has been vastly
discussed on this list, but the fact is that it is working like this.
If you aren't satisfied witht the current numbering of your
interfaces, there is a simple way to change the numbering:
find the file /etc/udev/rules.d/70-persistent-net-rules. You will
see there is a line per known interface, containing notably its MAC
address (eg ATTR{address}=="e8:de:27:a8:14:e1") and the name it will be
given (eg NAME="eth0"). You can change the names and/or the MAC
addresses, but take care that a name or a MAC address doesn't appear twice.
You can notice that each rule contains variable names separated
from the value by == , which is a condition and, at the end, NAME=ethX,
which is an assignment. Each "rule" is preceded by a comment line
indicating the PCI address of the device.
You can also let Udev forget all the MAC addresses it knows and
restart numbering the existing interfaces from scratch. For this, just
erase all the lines; only keep the 5 comment lines at the beginning.
HTH.
Didier
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] systemd-udevd: renamed network interface eth0 to eth1
Hi Didier,
Am 2017-10-06 18:36, schrieb Didier Kryn:
If you aren't satisfied witht the current numbering of your
interfaces, there is a simple way to change the numbering:
find the file /etc/udev/rules.d/70-persistent-net-rules. You will
see there is a line per known interface, containing notably its MAC
address (eg ATTR{address}=="e8:de:27:a8:14:e1") and the name it will
be given (eg NAME="eth0"). You can change the names and/or the MAC
addresses, but take care that a name or a MAC address doesn't appear
twice.
Thanks for that explanation. That explains my problems. My Thinkpad was
replaced during repair and I installed my hard drive in the new device.
The logic you described breaks some things, because of new MAC addresses
the devices got new names.
That's a perfect example why renaming devices (to make them "stable") is
not a good idea. Most consumer devices have not more than one ethernet
card and one wireless card. So naming was already "stable". The new
logic makes them unstable when you have to change devices on repair. But
that's typical "behaviour" of systemd devs. :-(
If someone with more than one ethernet/wireless device needs stability,
he can add udev rules manually. This should never be automatic!
Jochen
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] systemd-udevd: renamed network interface eth0 to eth1
Le 06/10/2017 à 18:52, J. Fahrner a écrit :
Hi Didier,
Am 2017-10-06 18:36, schrieb Didier Kryn:
If you aren't satisfied witht the current numbering of your
interfaces, there is a simple way to change the numbering:
find the file /etc/udev/rules.d/70-persistent-net-rules. You will
see there is a line per known interface, containing notably its MAC
address (eg ATTR{address}=="e8:de:27:a8:14:e1") and the name it will
be given (eg NAME="eth0"). You can change the names and/or the MAC
addresses, but take care that a name or a MAC address doesn't appear
twice.
Thanks for that explanation. That explains my problems. My Thinkpad
was replaced during repair and I installed my hard drive in the new
device. The logic you described breaks some things, because of new MAC
addresses the devices got new names.
That's a perfect example why renaming devices (to make them "stable")
is not a good idea. Most consumer devices have not more than one
ethernet card and one wireless card. So naming was already "stable".
The new logic makes them unstable when you have to change devices on
repair. But that's typical "behaviour" of systemd devs. :-(
If someone with more than one ethernet/wireless device needs
stability, he can add udev rules manually. This should never be automatic!
I had the same problem this morning after replacing the OS disk on
a server by a clone of the OS of another server. It contained already
the Udev rules for the 4 interfaces of the other computer. But, in this
case, stability is critical and the admin is acustomed to the trick :-)
I agree that interface renaming is only a disturbance in situations
where there is at most one eth and one wlan, that is nearly every laptop.
Didier
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] Testing post, please ignore
It seems that I cannot get any posts on my mailbox from DNG. Testing posting now, please ignore this message. --- :^) --- :^) --- :^) --- :^) --- :^) --- :^) --- :^) --- :^) --- https://nextchan.org - https://gitgud.io/m712/blazechan I am awake between 7AM-12AM UTC, hit me up if something's wrong signature.asc Description: PGP signature ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] systemd-udevd: renamed network interface eth0 to eth1
J. Fahrner [2017-10-06 18:52]: > That's a perfect example why renaming devices (to make them "stable") is > not a good idea. Most consumer devices have not more than one ethernet > card and one wireless card. So naming was already "stable". The new > logic makes them unstable when you have to change devices on repair. But > that's typical "behaviour" of systemd devs. :-( I totally agree! -- Hilsen Harald ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
