On Fri, 26 Jul 2002 15:59:53 -0400 (EDT) [EMAIL PROTECTED] (Larry Jones) wrote:
> David Koski writes [in very long lines]: > > > > What do you mean "Don't mount the sandbox on the server"? > > I mean, don't share directories between Windows and Unix/Linux; the file > formats and filesystem semantics are different. They're similar enough > that many things will work and fool you into thinking that everything > will work, which it won't. Unless you're using the server strictly as a > server and only access the directory from the client, never directly on > the server, it's a bad idea that will eventually bite you. > > > My sandbox happens to be on a server share (Windows client/workstation, > > linux smb share) but I have observed the same behaviour on a stand-alone > > Windows based sandbox. > > > > cygwin cvs works fine for me. I don't use WinCVS. > > cygwin works fine if you tell it to use DOS line endings by default, or > if you never use any native Windows tools. Anything else will > eventually cause grief. My experience is quite the contrary. I had nothing but headaches when I let cygwin muck with my line endings, which is what it was doing in text mode, ie. using DOS line endings. I use native Windows tools with the same text files almost exclusively. When I switched to binary mode cygwin, no problem. Some files have mixed line endings but the linux based cvs server behaves as if the optional ^M character is like any other character, providing I don't use cygwin in text mode. cygwin in binary mode works great, on a SAMBA share or locally on a Win box, either via pserver or external. I also use linux cvs on the same sandbox on the SAMBA share, mixed/matched line endings. David _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
