BCsven

Thanks this is helpful. So .local hasn't been reserved for only on local LAN, and .internal would be registered so ot never looks outside of lan?

Can you explaim further: I'm savvy enough to install a custom kernel for a 14 year old arm board and flush drive boot sector with U boot, etc, so I can use it as a dedicated DAAP server, but Networking somehow eludes me

I assumed that was what .local was all about

senchurwion stwike him woughly

I have had zero issues with nVidia on multiple Leap machines. nVidia works great on SUSE / OpenSUSE since nVidia hosts their own repo to support SUSE, OpenSuse, (and maybe REL?) Since it is an nVidia package it works as expected and the nVidia configuration GUI app gives you granular control

Just a disclaimer: nVidia works great on SUSE / OpenSUSE. nVidia hosts their own repo to support SUSE, OpenSuse, (and maybe REL?) Since it is an nVidia package it works great and the nVidia configuration GUI app gives you granular control

Fricken Bixby bullshit.

I believe there is a method to do a 1-1 build copy, but my expertise ends at this point

Yes it is great. For me snapper rollback was an awesome onboarding experience to linux. Being eager to try things I read online for tweaks and general explorarion it brought me back to a working system after some custom kernel compiling gone awry, or deleting the wrong file etc.

That is a caveat with OS disk tools. Even partition resizing gives this warning, as does Windows checkdisk...something about unnessary disk checks ahould be avoided as they can create issues where none might have existed, so only run when you suspect a problem.

But as lemann pointed out in this thread btrfs scrub is less risky

Btrfs is default on OpenSUSE, has worked great for me for 7 years. No issues.

There is btrfs-check --repair to fix corruption