> Speaking of which, why is /home/ncvs on beast not pointing to
> the current CVS repository? I got bit by the same error after
> doing (what I thought) was a correct `cvs update' on beast.
Sorry, "my bad"; the alpha releases were falling over on some sort of
NFS bogon (and cvs checkouts using ssh weren't working either) so I
was forced to copy the repository over to /j on beast and start using
cvsup to synchronize it. Now that 4.0-RELEASE is behind us and we
don't have another coming up for a few months, I'll point it back.
Done!
- Jordan
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
