MacBook

[Michael Butash]

My "key" software is generally the Kernel.

One particularly nasty little side note I've found was related to my 
logitech wireless keyboard.  At least twice now, I've run into this 
where I'll upgrade ubuntu's kernel, and I can't unlock my hard drives or 
get to a desktop as my dongle isn't registering. This is something of a 
big issue, though I usually just have to hit the server room for a spare 
usb keyboard temporarily.  Once no keyboard worked to even break grub 
and change kernels.  Now I keep grub on manual from automatically booting.

AMD video is another bastard.  I'll generally get annoyed with something 
else not working, do a dist-upgrade just to get to current, and realize 
a new kernel slid in.  One that broke my video, which seeing intel likes 
to pretend their cpu has a real gpu on it, causes all sorts of chaos 
with where my displays actually pop up on my pci card or mobo until I 
can figure out what newer driver, if any, works with a newer kernel.

Virtualbox is another.  Because lovely windoze is still required always 
intermittently, I'll upgrade, realize after a few days vbox is broken 
when I need to look at a visio, and wonder wtf, having to reverse 
engineer and remember I dared update something.  VMware workstation is 
finicky as all hell usually, I can never update without breaking it.

VPN software, hell even KRDC likes to randomly break with updates, 
remmina occasionally breaks too, which is wonderful when left with no 
working rdp client to manage/use customer services.

My laptop hasn't had a working resolvconf to get working DNS servers 
with a network connection in a year, I have to "sudo dhclient $if" to 
pull them outside of networkmangler.  Better than trying to upgrade and 
break something else

List sort of goes on and on.  Still better than any experience with Mac 
or Windoze of late.

-mb


On 08/25/2016 09:44 PM, Stephen Partington wrote:
>
> I have to say. If an update breaks your key software then you need to 
> manage your damned updates. All os' have the ability to do this. Just 
> implement it already.
>