cvsup from inetd ???

I was editing /etc/inetd.conf for pop3 and founf these entries

#cvspserver stream tcp nowait root /usr/bin/cvs cvs --allow-root=/your/cvsroot/here pserver
#cvs stream tcp nowait root /usr/bin/cvs cvs --allow-root=/your/cvsroot/here kserver

does that mean that when I copy the sources to some dir I can cvsup from that machine or do I have to build some kind of repository with some script or something like that. Freebsd opted using nfs, but this looks nice too if it works this simple.

Marc

>> Freebsd opted using nfs

Yes for several simple reasons:

1) What kind of bandwidth do you have? Why waste your bandwidth to do mirroring?
2) How many boxes need to buildworld?
3) How often? Do you buildworld several times a day?

Running a cvsup mirror site is not suitable for home users. Even you administer 1000 FreeBSD boxes, cvsupd still is not for you. I doubt you really understand what cvsup can do for you.

Why don't you start here -> http://www.onlamp.com/pub/a/bsd/200...ry_Daemons.html

well ok, you're making your point clear, I was just wondering. What to do with cvsup, just keep my system up to date actually.

But nfs also seems to work good, I was just wondering about the cvsupd, that's all. I now mount /usr/src and /usr/ports from a certain machine and copy it to the local machine and compile from there.

Marc

You'd use NFS when your target machine (the one that needs buildworld) is short of disk space. Even if your boxes are not short of disk space, you should keep a master /usr/ports/distfiles somewhere and export it to other boxes. I do this all the time on over 10 Free/Net/Open boxes and have a centralize distfiles dir.

You also should use NFS if you are running multiple identical boxes (tracking same branch). This way, you only need to buildworld once on your source machine (the box where actual /usr/src resides), then installworld on each boxes.

Well, I do the installworld in single user mode, just to be sure.....so I'll copy the source from one certain machine to the other machines and compile it on every machine, it does give some overhead andsoforth, but it works for me.

Marc