In article <[EMAIL PROTECTED]>,
Trevor Johnson <[EMAIL PROTECTED]> wrote:
> Personally, I use the separate collections because cvsup times out
> otherwise (I guess my connection is too slow).
A slow network won't cause this. There must be some other problem.
The cvsupd server times out a connec
On Fri, Jul 07, 2000 at 09:55:49PM -0700, Thomas D. Dean wrote:
> cvsup7.freebsd.org does not know about cvs-crypto.
>
> What is the correct collection?
Cvs-crypto has been merged into src-all, due to the loosening of U.S.
crypto policy. I believe someone sent a heads-up to this list a few
days
Rodney W. Grimes wrote:
> Oopsss... never mind. I think this has all been folded into
> the baseline cvs target. *-crypto is no more.
Hi, Rodney. This recent message explains what's happening:
> From: John Polstra <[EMAIL PROTECTED]>
> Subject: Re: HEADS UP: Crypto changes coming soon
>
> > cvsup4.freebsd.org does not know about cvs-crypto.
> >
> > What is the correct collection?
>
> src-crypto
Oopsss... never mind. I think this has all been folded into
the baseline cvs target. *-crypto is no more.
--
Rod Grimes - KD7CAX @ CN85sl - (RWG25) [EMAIL PROTECTED]
In article <[EMAIL PROTECTED]>,
Rodney W. Grimes <[EMAIL PROTECTED]> wrote:
> > cvsup4.freebsd.org does not know about cvs-crypto.
> >
> > What is the correct collection?
>
> src-crypto
No, it's src-crypto + src-eBones + src-secure + src-sys-crypto.
Or better yet, just use "src-all" in place of
> cvsup4.freebsd.org does not know about cvs-crypto.
>
> What is the correct collection?
src-crypto
--
Rod Grimes - KD7CAX @ CN85sl - (RWG25) [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
cvsup7.freebsd.org does not know about cvs-crypto.
What is the correct collection?
tomdean
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
cvsup4.freebsd.org does not know about cvs-crypto.
What is the correct collection?
tomdean
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
