Joi Ellis <[EMAIL PROTECTED]> wrote:
> I just searched through samba.org's mail archive, and there are reports
> there of NT blue-screening during a smbtar pull from Unix hosts.
I can at least confirm this with Windows 95, seems to not happen that
quickly with Windows 98 (ie: it's impossible to differenciate from
`normal', `usual' crashes).
This is *definitely* a bug in the Windows implementation of SMB. Or
one of. One of the things which gets unnoticed if you use the
`proper' (read: Microsoft-only) clients. In other worlds,
Windows doesn't interoperate, and is full of assumptions that
will make your system break. Especially the kind of weakness
that Internet crackers love.
Read the smbfs documentation and you will see the quite big amount of
work-around that are required in order to not crash Microsoft SMB
servers ... often at the price of speed.
What is good in the UNIX world is that it is indeed usually quite
possible to isolate a failure cause: in the Windows world you
just need to modify your setup back and forth, install various
service packs, until everything *seems* to stabilize. Thinking
might sometimes be easier, but Microsoft doesn't encourage
thinking. Installing one mouse driver might make your
database crash because of an incompatibility (read: bug) in
a previously installed, and seemingly working, printer
driver. Dependancies and unstability.
... and all of this has absolutely no link to Amanda.
