From: Henrik.Carlqvist@deadspam.com   
      
   On Thu, 06 Nov 2025 20:44:44 +1000, noel wrote:   
   > On our internal file server I'm running # smbd -V Version 4.22.6   
      
   That is at the time of this writing the latest version of Samba provided   
   for Slackware 15.0 in the /extra directory.   
      
   > ls -la /etc/samba/smb.conf -rw-r--r-- 1 root root 7118 Dec 10  2020   
   > /etc/samba/smb.conf   
   >   
   > IOW, our config is 5 years last time it was edited, and I'm sure that   
   > was just adding s share so the config used here was probably written   
   > quite some time before that with no changes (YMMV as I recall a recent   
   > incompatability change if using active directory).   
      
   Yes, the fact that they have given themselves the liberty to introduce   
   non backwards compatible changes does not for sure mean that they will in   
   every fixed date release. And some of those non backwards compatible   
   changes might only break things for a few users with rare settings in   
   their smb.conf.   
      
   > and dont get started on php, which is what sparked the audit   
      
   Ouch, php is a beast of its own when it comes to introducing non   
   backwards compatible changes. "LAMP" used  to be a de facto standard when   
   it comes to web servers, where "LAMP" stands for  Linux, Apache, MySQL/   
   MariaDB and PHP. And what did PHP do a few years back? They completely   
   rewrote their interface to MySQL/MariaDB in a non backwards compatible   
   way meaning that anyone who had written a solution for LAMP needed to   
   rewrite his PHP code.   
      
   regards Henrik   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)