On Feb 9, 2009, at 11:49 PM, Kris Tilford wrote:
> > I was unaware Apple messed with Samba. It appears you're correct, the > needed "patches" for OS X are evidently available here: > <http://www.opensource.apple.com/darwinsource/10.5.6/samba-187.8/patches/ >> > > According to: > > <http://news.samba.org/releases/> > > version 3.0.25b was a "normal" release from June 26th, 2007. > > I count these as standard "stable" releases since then: > > 3.0.25c, 3.0.26, 3.0.26a, 3.0.27, 3.0.27a, 3.0.28, 3.0.28a, 3.0.29, > 3.0.30, 3.0.33, 3.0.34, 3.2.0, 3.2.3, 3.2.4, 3.2.5, 3.2.6, 3.2.7, > 3.2.8, 3.2.9 and the current stable release 3.3.0. > > This means Apple is not 5 updates behind, but a staggering 20 updates > behind. Remember, these are only counting standard stable releases, > not any alpha, beta releases, or release candidates. The current > bleeding edge is version 4.0.0 alpha 3. there's also the question of "What are you gaining with the updates?" Some projects release a new version for every damn bug fix. The key is to go through the changelog and see what, if any, functionality you're gaining, and if it even applies to you. I can't count the number of various program updates I've run into, with a new version number that were "fixed XYZ with Red Hat and ABC with Solaris". Like the sign that used to live above our server bench, back when we had 4 different Unix systems: "You are in a maze of twisty little unixes, each slightly different" It's fine for some hobbyist to mess around and try the latest&greatest of everything, but when you're dealing with an OS with a thousand interlinking 3rd party parts (which is, after all, pretty much what Unix is) being installed on millions of devices, well, you approach change a little bit more carefully, especially when it's a piece as deeply tied to the user experience as smb. Finally, Apple also has a bad habit of compiling diffs into their code without updating the version number reported. I've run into this a couple of times. I will admit, in 10.5 I've not had any of the problems that used to plague SMB connections in the early days: no more "choked down to 5 bits per second" file transfers, no more infuriating "I just can't seem to connect any more" -32 errors that required rebooting to clear. Windows shares will no longer slip into a coma when the system sleeps (Something that is directly attributable to Windows, my smb shares on our Linux boxes are rock-solid). I've been a sysadmin long enough to appreciate the wisdom of "If it ain't broke, don't fix it!" school of thought. -- Bruce Johnson University of Arizona College of Pharmacy Information Technology Group Institutions do not have opinions, merely customs --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed Low End Mac's G3-5 List, a group for those using G3, G4, and G5 desktop Macs - with a particular focus on Power Macs. The list FAQ is at http://lowendmac.com/lists/g-list.shtml and our netiquette guide is at http://www.lowendmac.com/lists/netiquette.shtml To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/g3-5-list?hl=en Low End Mac RSS feed at feed://lowendmac.com/feed.xml -~----------~----~----~----~------~----~------~--~---
