Hi Waldo,

here is a copy of a mail I wrote to the 37495@bugs.kde.org

Greetings,
eva

----------    ----------

Subject: Bug#37495: KDE cannot be started on systems with home on Windows=
=20
server
Date: Sat, 26 Jan 2002 23:31:29 +0100
From: Eva Brucherseifer <eva@kde.org>
To: 37495@bugs.kde.org

> On Saturday, 26. January 2002 14:57, Eva Brucherseifer wrote:
> > > This sounds like an error in your commercial NFS server. It is thei=
r
> > > job to wrap the names if they want to be NFS-complient.
> > > Please file the bug report to them.
> >
> > Well, this is possibly correct, but not very pragmatic :-(
> > Unfortunately this is no option, because the admins won't change a
> > running system by updating the NFS server.
> > Also one of the advantages of linux is, that it most of the time can
> > handle errors in other people's systems (like samba - it handles wind=
ows
> > errors).

Hi Stephan

> AFAIK they're already done in CVS because of the feedback we've got fro=
m
> the cygwin port.

Yes, you are right - there is a new name for the DCOP file. I was confuse=
d by
the link named the old way, which is there for KDE 2.x compatibility reas=
ons.

I tested the system on a common linux box with a file in the old style, o=
wned
by root, non-readable and non-writeable and it was possible to startup KD=
E
this way. In the code symlink() is called and there is no test, if symlin=
k()
is successful and KDE simply continues without the link.

So I think you can close this bug. I'll file a new bug report, if it does=
n't
work on the real system.

Greetings,
eva

> Greetings, Stephan

-------------------------------------------------------


> I fixed most of these already I think. Can you try with a recent snapsh=
ot?
>
> Cheers,
> Waldo
>
> On Saturday 26 January 2002 02:31 am, Stephan Kulow wrote:
> > Just making sure noone misses that mess, we're _not_ facing all day :=
)
> >
> > ----------  Forwarded Message  ----------
> >
> > Subject: Bug#37495: KDE cannot be started on systems with home on Win=
dows
> > server
> > Date: 24 Jan 2002 22:20:51 -0000
> > From: eva@kde.org
> > To: submit@bugs.kde.org
> >
> > Package: dcopserver
> > Version: KDE 2.9.1 CVS/CVSup/Snapshot
> > Severity: normal
> > Installed from:    Compiled sources
> > Compiler:          gcc-2.95.3
> > OS:                Linux
> > OS/Compiler notes: suse 7.3
> >
> > If the home directory of a user is placed on a windows server (i.e. w=
ith
> > a commercial NFS server) KDE cannot be started, because the file
> >  .DCOPserver_konrad_:0 cannot be started. This is because the Windows
> > file system doesn't allow ':' in file names - this character is reser=
ved
> > for drive names.
> >
> > We have this setup at a lab at the university (don't blame me - I am =
not
> > the administrator ;-) and I fixed it for 2.1.2 by patching the source=
s so
> > that the dcop file is named .DCOPserver_konrad__0 instead. This worke=
d
> > very well.
> >
> > Would be nice if you fix this for KDE 3 :-)))
> >
> > Cheers,
> > eva
> >
> > (Submitted via bugs.kde.org)
> >
> > -------------------------------------------------------