3 ms·

Thanks -- I really appreciate a detailed answer like that. :-) I am no fan of Wayland either, but nobody seems willing to step up and bring us X11R8 or X12, sa

Thanks -- I really appreciate a detailed answer like that. :-) I am no fan of Wayland either, but nobody seems willing to step up and bring us X11R8 or X12, sadly. I think the Linux world needs it. Most of the world is little-endian now, rightly or not. x86-64, POWERLE, Arm64, they can all handle it. So if the choice becomes "X dies" or "we have to brutally cut a lot of stuff to keep this alive", let's prune hard. No client font server support any more, only 24-bit colour or higher, no byte-swapped clients, etc. Gods, maybe even IPv6 only. :-) > its all cheeky on my laptop What does that mean? I don't recognise the word in that context. (To me "cheeky" means "slightly rude, mildly hostile and uncooperative".) Netplan... ahaa! Some of the people on the Ubuntu Users mailing list kept complaining about this. I told them not to fight it: let everything DHCP, get your router resolving names however it wants. They wouldn't have it. They wanted old-school fixed IPs and DNS. I let networking do its thing and don't fight it. I find it makes life much easier.

croutonwagon 4y ago
Cheeky=fine. Yeah im not one to care much about the tools. Ie:systemd av upstart/init.d And the networking change isn’t ENTIRELY on canonical. The dhcp rfc says to use a machine identifier over MAC address when possible. The hiccup is that when you upgrade 18.04 to 20.04, net plan is there but unconfigured. But they now generate machine ids so any dhcp reservations are broken. And I’m not aware of the override that goes into /etc/networking/interfaces. And if there is one like ClientIdentifier=Mac, it’s not easily documented. So I had to comment out the interface configs and migrate to netplan manually where I can specify the override.
- lproven 4y ago
  > Cheeky=fine. Oh right! I never would have guessed. Is that a regional thing? If so -- just curious -- where from? Aussie? > so any dhcp reservations are broken. Ouch!
  - croutonwagon 4y ago
    Haha. Definitely not Aussie, I'm in the US. But i do hang around with some....Honestly don't even know what possessed me to phrase it that way :?
    - lproven 4y ago
      :-D

croutonwagon 4y ago

Cheeky=fine. Yeah im not one to care much about the tools. Ie:systemd av upstart/init.d And the networking change isn’t ENTIRELY on canonical. The dhcp rfc says to use a machine identifier over MAC address when possible. The hiccup is that when you upgrade 18.04 to 20.04, net plan is there but unconfigured. But they now generate machine ids so any dhcp reservations are broken. And I’m not aware of the override that goes into /etc/networking/interfaces. And if there is one like ClientIdentifier=Mac, it’s not easily documented. So I had to comment out the interface configs and migrate to netplan manually where I can specify the override.

lproven 4y ago
> Cheeky=fine. Oh right! I never would have guessed. Is that a regional thing? If so -- just curious -- where from? Aussie? > so any dhcp reservations are broken. Ouch!
- croutonwagon 4y ago
  Haha. Definitely not Aussie, I'm in the US. But i do hang around with some....Honestly don't even know what possessed me to phrase it that way :?
  - lproven 4y ago
    :-D