Date: Thu, 17 Aug 1995 08:10:09 +0800 (WST) From: Peter Wemm <peter@haywire.dialix.com> To: Ollivier Robert <roberto@blaise.ibp.fr> Cc: "Rodney W. Grimes" <rgrimes@gndrsh.aac.dev.com>, CVS-commiters@freefall.FreeBSD.org, cvs-gnu@freefall.FreeBSD.org Subject: Re: cvs commit: src/gnu/usr.bin/cvs/cvs import.c Message-ID: <Pine.SV4.3.91.950817072120.3060F-100000@haywire.DIALix.COM> In-Reply-To: <199508162223.AAA18008@blaise.ibp.fr>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 17 Aug 1995, Ollivier Robert wrote: > > Now, let me see if I can compile and install this bloody thing on Freefall > > without too much pain :-). > > How about importing CVS 1.5 ? > > The remote support is nice to have... Umm.. I think this will suprise Rod, who has probably figured out I'm a "right at the bleeding edge kinga guy", but I think we'd really be opening up a pandoras box of problems if we enabled remote access... I'd be having nightmares, Rod would probably be having kittens... :-) The main things I'm worried about is the commit process.. In the remote case, the commit text is prepared on the client, *before* the server even knows which files are being changed. The server no longer gets to supply a commit template file, because this is prepared offline now. There's no longer the visual check of which files you are actually writing the log message for - you're flying blind unless you've just done a cvs-update. I know the NetBSD people use it, and I know cgd had a bumpy ride getting it running from the early days when remote access was "new". So far as I can tell, most of the problems have been ironed out, and I have it running on our systems internally, and I'm not quite happy with it yet.. It still seems to me that it has a habit of leaving behind more stray locks in the face of network problems than I'd like... Considering the frequency of problems between barrnet and *.cdrom.com, we'd get covered with locks before we knew it.. The other complication is that it uses either KRB4 authentication, or rsh/.rhosts authentication. In order to commit without KRB4/eBones, we'd have to have a whole swag of .rhosts files... And since FreeBSD currently has bind-4.9.3-beta9, which is *known* to be able to have it's cache corrupted, there could be security issues too.. (probably not that bad, because it's not too hard to get an account on freefall by going through normal channels, but you never know....) I don't know.. Is it time to start thinking about this sort of thing a bit more seriously? -Peter > -- > Ollivier ROBERT -=- The daemon is FREE! -=- roberto@FreeBSD.ORG > FreeBSD 2.2-CURRENT #5: Fri Jul 14 12:28:04 MET DST 1995 >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.SV4.3.91.950817072120.3060F-100000>