info-cvs archive search

51. Re: CVS with a Novell repository (academic environement)? (score: 14)

Author: HIDDEN

Date: Tue, 3 Aug 2004 09:29:22 -0400 (EDT)

Correct. -Larry Jones Start tying the sheets together. We'll go out the window. -- Calvin

/archive/html/info-cvs/2004-08/msg00013.html (4,755 bytes)

52. Re: CVS corrupts binary files ... (score: 14)

Author: HIDDEN

Date: Sat, 5 Jun 2004 20:36:20 -0700

I have personally kept binary files in CVS for many years. (Since before -kb was supported, but at that time all my systems were Unix boxes.) Since -kb and Windows interoperability were introduced,

/archive/html/info-cvs/2004-06/msg00077.html (7,526 bytes)

53. Re: CVS newbie - I want to make a new CVS installation secure... (score: 14)

Author: HIDDEN

Date: Wed, 19 May 2004 09:16:23 -0500

If all you are wanting to protect is the contents of the $CVSROOT/CVSROOT directory, then I agree, Mark's suggestion is overkill. usually, what I believe, you want can be done with directory permissi

/archive/html/info-cvs/2004-05/msg00330.html (10,105 bytes)

54. Re: Error Updating file from the server (score: 14)

Author: HIDDEN

Date: Sat, 10 Jan 2004 01:12:33 -0500 (EST)

It's not just possible, it's almost certain. I strongly suggest running the contrib/check_cvs script to look for other corrupted files in your repository. Using some kind of network filesystem to acc

/archive/html/info-cvs/2004-01/msg00086.html (5,464 bytes)

55. Re: what to do with corrupted ,v files? (score: 14)

Author: HIDDEN

Date: Wed, 26 Mar 2003 09:33:20 -0500 (EST)

First, figure out how the corruption happend and make sure it doesn't happen again. The most common cause is accessing the repository with NFS (or some other network file system), although hardware p

/archive/html/info-cvs/2003-03/msg00288.html (5,132 bytes)

56. Re: Corrupt directory in database (score: 14)

Author: HIDDEN

Date: Tue, 25 Feb 2003 10:09:30 -0700

I'm using a pserver to access the dbase and we're using Solaris 5.8 as our OS with NFS files system. I found a work around for this problem, but have no idea why it ocurred in the first place. The fi

/archive/html/info-cvs/2003-02/msg00290.html (5,858 bytes)

57. Re: Corrupt directory in database (score: 14)

Author: HIDDEN

Date: Tue, 25 Feb 2003 10:54:33 -0500 (EST)

That indicates that there is something wrong with the format of the mentioned file. Can you post the contents? Are you using some kind of network filesystem to access your repository? -Larry Jones In

/archive/html/info-cvs/2003-02/msg00287.html (4,749 bytes)

58. Re: Discouraging :local: (score: 14)

Author: HIDDEN

Date: Mon, 27 Jan 2003 18:20:42 -0500 (EST)

[ On Monday, January 27, 2003 at 02:48:59 (-0800), Kenneth Porter wrote: ] Yes, I think so. As far as I know samba has no locking protocol (I don't think the underlying SMB protocol has locking eithe

/archive/html/info-cvs/2003-01/msg00254.html (8,506 bytes)

59. Re: Discouraging :local: (score: 14)

Author: HIDDEN

Date: Mon, 27 Jan 2003 02:48:59 -0800

The latter, the sharing part, is where the real trouble begins. Ensuring reliable order of operations for various operations which would be "atomic" on a local filesystem is very very difficult (lit

/archive/html/info-cvs/2003-01/msg00241.html (7,962 bytes)

60. Re: CVSROOT write permission vulnerability (score: 14)

Author: HIDDEN

Date: Mon, 20 Jan 2003 10:53:38 -0500 (EST)

That means you're using NFS to access your repository. There have been lots of reports of repository corruption due to NFS interoperability bugs. If all of your machines are running Solaris you proba

/archive/html/info-cvs/2003-01/msg00160.html (6,751 bytes)