Why writing a Windows compatible file server is (still) hard
Aug 03, 2009, 11:01 (7 Talkback[s])
(Other stories by Jeremy Allison)
"I went into one of my colleague's office and kicked the hell
out of one of the much loved Google beanbags, all the while
screaming obscenities into the air for a good five minutes. He
looked on with bemused amusement. I finally calmed down enough to
explain the problem. One packet being returned at the wrong time.
One single mis-timed packet caused a ripple effect in the Windows
client file system software that was seen all the way up in the
complex user interface of only that particular version of Excel,
when interacting with the "Offline Files" feature, only on Windows
Vista.
"The remaining task was to add a regression test into our test
suite, so that this specific bug is tested for before we release
any new versions of Samba. The code isn't done until it's properly
tested. But at least the user is now happy."
Complete
Story
Related Stories:
- Fedora 10 Samba Standalone Server With tdbsam Backend(Jun 04, 2009)
- Joining a Windows 7 system to a Samba domain(May 20, 2009)
- Plugging Away: DIY File Server Using Samba(May 19, 2009)
- Microsoft sabotaging GPL, claims Samba(Mar 11, 2009)
- Samba - The Interoperability Dance(Feb 18, 2009)
- Active Directory comes to Linux with Samba 4(Jan 19, 2009)
- Create an Encrypted Samba Share(Jan 05, 2009)
- Enabling Samba Shares Across Subnets, Part 2(Nov 28, 2008)
- Enabling Samba Shares Across Subnets, Part 1(Nov 28, 2008)
