Get rid of the pesky humans that might form a union or show initiative. in some sub-optimal way. Replace with robotics. Everybody wins. Especially the shareholders. But also the human who no longer has to deal with a boss yelling at them. That thought will comfort them as they starve to death and we're rid of them once and for all.
There are companies who do "pay for play" Samba development. You pay 'em and tell them what you want in Samba, and they'll write it and upstream it for you.
Might be more than you want to pay though.
Samba does implement DFS, I wrote lots of the code for it and updated it recently
I think you mean it doesn't implement DFS replication in the same way that Windows does.
Samba is only configured one way, via the smb.conf file.
Runtime control can be done via smbcontrol, but the base config file is always smb.conf.
When using local uses passwords *must* be separate as the SMB protocol and Linux passwords use completely different crypto.
Of course if you want synchronised passwords just add the Linux machine into the Active Directory Domain using Samba's winbind and users and passwords are identical of course.
Samba with an the iouring backend is as performant as an in-kernel version.
See Metze's talk this week at SNIA SDC 2023 in Freemont, CA. for details:
This is completely incorrect.
Microsoft do not concern themselves with what SMB versions Samba supports when considering maintenance. At all.
As it should be IMHO. We match current versions of Windows and only keep SMB1 around in an "off-by-default" state for customers who can't or won't update old Windows / DOS clients.
I've been threatening for years to write a wonderful paper called "Why Agile is (Mostly) Bullshit". However without a replacement methodology to give managers a set of pretty charts and the appearance of control, it would do no good. In fact, having been in the industry as both an individual contributor and/or manager for 40+ years, I could safely broaden the title to "Why Methodologies are (Mostly) Bullshit" without much change. I think as long as IC's understand that their management is for the most a bunch of insecure flunkies and that methodologies are (mostly) security blankets to ease these insecurities up the management chain and provide (usually poor) estimates to allow upper management to budget and make (usually inaccurate) promises to customers, everyone can play the game without too much grief. But whatever the methodology, it simply acts as a multiplier for any behavioral pathologies that are in the organization and so can turn life into a living hell if these are not quashed or managed effectively.
... the java guy, he needs a two hour introduction before he even walks on the main stage.
That's not an introduction, it's an apologia.
I was hired for my current individual contributor job at age 65. I guess the cutoff must be 70 now. Of course it helps that I do have three somewhat esoteric skills that were needed by the company that hired me, but it's nothing a relatively good programmer couldn't pick up in a reasonable amount of time.
Let's just say that commonplace skills don't cut it the older you get. Someone who knows ONLY Python and SQL will be out of a job by age 40. Being expert at C++ might keep you in the game until age 50. You might be employable to age 60 if you know OCaml or Haskell.
In the end it's all supply and demand. If your skills are a dime a dozen that's what you'll be paid. And you'll be replaced by a younger, cheaper person as soon as they can find one.
You obviously have little clue as to current compiler technology, that can provide JIT compilers for a variety of languages targeted to just about any platform, These compilers approach or exceed the performance of native-compiled binaries because they can take advantage of run-time information about the data types and values actually being used by the code rather than trying to infer them (usually poorly) at compile time. The fact that Python does not have one of these yet is more a testament to its developers' sloth and seeming abhorrence to linguistic stability rather than any technological factor.
Everyone knows SVO order is much more understandable than SOV. Just ask anyone from Germany.
When it comes to security and Microsoft, why should this day be different from any other day?
Just to add, for this reason I'm only helping out with the C coding, not leading the effort
Happiness is twin floppies.
