It used to be that when one proclaimed, "Wow, I learn something new every day" that this was a good thing. We are dynamic, even if we do tend to be creatures of habit and ritual.
The thing is, nowadays, it would appear that this "learning something new every day" has grown tired. In other words, we may find ourselves having to learn more and more lifeless technicalities to maneuver in cybernetic ecosystems. When one part of the ecosystem, say, for instance, an operating system such as "Windows 10" updates its system and changes the way it handles SMB1 and NetBios, this has an impact on machines [each a node in the vast network] running different operating systems, such as linux boxes using Samba to share drives or access a shared printer plugged into a machine running "Windows 10".
One finds oneself becoming annoyed at having to "learn something new every day."
Even those who do not necessarily rely on the corporate sparkle of Micro$oft Windows, if the users of other operating systems must interact with machines running "Windows 10," then there is potential for chaotic ramifications after each [FREQUENT] Windows 10 Update.
I presume this example will suffice in making the point that learning something new every day aint what it used to be.
In the old days, from the command line, print to lpr. Now, in the world of multiuser systems like Linux,
the technicalities surely encroach upon the technician and end users, whereby more and more of the burden of operation falls squarely on the shoulders of, who? --- you and me.
Maybe many say, who gives a f--k? Just don't learn it.
Well, at some point each of us must draw the line.
Maybe, instead, it might be better to relearn something old. There's alot I have to go over again and and again.
Aye, Man, I pity us all.
--------------------------------------------------------------------------------------------------------
Footnote:
As for the SMB1 conflict with Windows as Print Server (for Linux clients):
On the command line, you get this (with smbclient):
Reconnecting with SMB1 for workgroup listing.
Connection to 192.168.2.101 failed (Error NT_STATUS_RESOURCE_NAME_NOT_FOUND)
Failed to connect with SMB1 -- no workgroup available[
This is pure and absolute nonsense. Security for the sake of it. Anal-retentive OCD madness that ruins the desktop experience. The reason is, they changed the default protocol version and actually, who cares? People just want to be able to share things with their Windows boxes easily!]
See
Samba shares problem fix [ NOTE TO SELF?: it does not fix what it claims to fix. ]