Bug#337278: problem is cifs related, no sid backport bug
as so often two changes happend at the same time. I had been advised by Andrew
Bartlett (in relation to bug# 320181) to used cifs instead of smbfs. He
wrote:
The problems with smbfs are far more than just the lfs support. It is
depricated, end of life, and work is progressing on having the CIFS VFS
support the remaining (older) servers which currently require keeping
smbfs around.
Prior to my problem I mounted the Mail folder via smbfs which worked. I also
believe that my problem with etsch (kde 3.4) has the same reason: for my test
system I wanted to use cifs anyhow.
BUT THE REAL PROBLEM IS STILL THERE
The samba people seem to know about the colon/cifs problem. But as far as I
understood it could also show up when Mail is on a real Windows server
without SFU (?) being used. And what about some network storage products that
implement smb?
Yours Jürgen
Reply to: