Re: [OT] CVSUP (was "Re: Was: Re: Why This Infinite Loop??")
On Aug 22, 2006, at 12:19 AM, Erik Trulsson wrote: On Tue, Aug 22, 2006 at 06:38:46AM +0100, Matthew Seaman wrote: Lowell Gilbert wrote: Garrett Cooper <[EMAIL PROTECTED]> writes: Gerard Seibert wrote: IMHO, it might be a lot easier for him to use portsnap. Especially if he is not familiar with the FBSD ports system. Just my opinion though. CVSUP isn't that difficult IMHO to learn, and is a better, more efficient way to download the ports Makefiles. In what way? For typical applications, lower bandwidth usage is supposedly an advantage of portsnap. It will take him all of 10-20 minutes to configure if he reads the documentation and uses the example file. I would think so. And it can be used with arbitrary cvs trees, including the FreeBSD source tree. On the other hand, it doesn't come in the FreeBSD base system, and it doesn't sign the updates. But csup(1) is in the base system for values of base system equal to 6.1-STABLE or better. csup(1) is cvsup(1) reimplemented in plain C and apart from the graphical display stuff is a drop in replacement for cvsup(1). Not quite a drop in replacement. csup(1) does not (yet) support CVS mode which is used to maintain a local copy of the repository. I did a bit of searching and it appears that my thoughts on how CVSUP is implemented are slightly skewed. From the portsnap developer's page: -CVSup is insecure. The protocol uses no encryption or signing, and any attacker who can intercept the connection can insert arbitrary data into the tree you are updating. -CVSup isn't end-to-end. Related to the previous point, this means that anyone who can compromise a CVSup mirror can feed arbitrary data to the people who are using that mirror. -CVSup isn't designed for frequent small updates. While CVSup is very good at distributing CVS trees, and is very efficient for updating a tree which has been significantly changed (eg, by a month or more of commits), it transmits a list of all the files in the tree, which makes it quite inefficient if only a few files have changed. -CVSup uses a custom protocol. This can cause problems for people behind firewalls -- outgoing connections on port 5999 need to be permitted -- and it needs a heavyweight server (cvsupd). The first and fourth points are the ones I noted as the flaw in my original argument of the overall operation of CVSUP vs portsnap. I thought that CVSUP actually used the CVS protocol to transfer data, which can encrypt data using SSH tunneling but it actually doesn't and is very insecure =\. Noting that portsnap fetches all files via fetch with ssl support enabled as well by quickly reading through the portsnap script, it is much more secure than CVSUP is. The only thing to note is that you still need to use CVSUP to update your base package sources, as there isn't a compressed, fetching equivalent like portsnap available for the sources. Although this would have been more efficient for beno because it sounds like his ports tree hasn't been updated in ages, portsnap would be better to use in the future for updating his ports tree. -Garrett ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [OT] CVSUP (was "Re: Was: Re: Why This Infinite Loop??")
On Tue, Aug 22, 2006 at 06:38:46AM +0100, Matthew Seaman wrote: > Lowell Gilbert wrote: > > Garrett Cooper <[EMAIL PROTECTED]> writes: > > > >> Gerard Seibert wrote: > > > >>> IMHO, it might be a lot easier for him to use portsnap. Especially > >>> if he is not familiar with the FBSD ports system. Just my opinion > >>> though. > > > >>CVSUP isn't that difficult IMHO to learn, and is a better, more > >> efficient way to download the ports Makefiles. > > > > In what way? For typical applications, lower bandwidth usage is > > supposedly an advantage of portsnap. > > > >>It will take him all of > >> 10-20 minutes to configure if he reads the documentation and uses the > >> example file. > > > > I would think so. And it can be used with arbitrary cvs trees, > > including the FreeBSD source tree. On the other hand, it doesn't > > come in the FreeBSD base system, and it doesn't sign the updates. > > But csup(1) is in the base system for values of base system equal to > 6.1-STABLE or better. csup(1) is cvsup(1) reimplemented in plain C > and apart from the graphical display stuff is a drop in replacement > for cvsup(1). Not quite a drop in replacement. csup(1) does not (yet) support CVS mode which is used to maintain a local copy of the repository. -- Erik Trulsson [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [OT] CVSUP (was "Re: Was: Re: Why This Infinite Loop??")
Lowell Gilbert wrote: > Garrett Cooper <[EMAIL PROTECTED]> writes: > >> Gerard Seibert wrote: > >>> IMHO, it might be a lot easier for him to use portsnap. Especially >>> if he is not familiar with the FBSD ports system. Just my opinion >>> though. > >>CVSUP isn't that difficult IMHO to learn, and is a better, more >> efficient way to download the ports Makefiles. > > In what way? For typical applications, lower bandwidth usage is > supposedly an advantage of portsnap. > >>It will take him all of >> 10-20 minutes to configure if he reads the documentation and uses the >> example file. > > I would think so. And it can be used with arbitrary cvs trees, > including the FreeBSD source tree. On the other hand, it doesn't > come in the FreeBSD base system, and it doesn't sign the updates. But csup(1) is in the base system for values of base system equal to 6.1-STABLE or better. csup(1) is cvsup(1) reimplemented in plain C and apart from the graphical display stuff is a drop in replacement for cvsup(1). Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
Re: [OT] CVSUP (was "Re: Was: Re: Why This Infinite Loop??")
Garrett Cooper <[EMAIL PROTECTED]> writes: > Gerard Seibert wrote: >> IMHO, it might be a lot easier for him to use portsnap. Especially >> if he is not familiar with the FBSD ports system. Just my opinion >> though. >CVSUP isn't that difficult IMHO to learn, and is a better, more > efficient way to download the ports Makefiles. In what way? For typical applications, lower bandwidth usage is supposedly an advantage of portsnap. >It will take him all of > 10-20 minutes to configure if he reads the documentation and uses the > example file. I would think so. And it can be used with arbitrary cvs trees, including the FreeBSD source tree. On the other hand, it doesn't come in the FreeBSD base system, and it doesn't sign the updates. -- Lowell Gilbert, embedded/networking software engineer, Boston area http://be-well.ilk.org/~lowell/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [OT] CVSUP (was "Re: Was: Re: Why This Infinite Loop??")
On Monday 21 August 2006 15:02, Garrett Cooper wrote: > CVSUP isn't that difficult IMHO to learn, and is a better, more > efficient way to download the ports Makefiles. It will take him all of > 10-20 minutes to configure if he reads the documentation and uses the > example file. I am always willing to learn something new. How is it more efficient at downloading the port's Makefiles? I agree that the first time you run 'portsnap' it might take twenty minutes to fetch and extract the files. However, after that it only requires a fetch and update to complete the job. It appears, to me anyway, to run at least as quick as cvsup plus I do not have to rebuild the index. If he runs cvsup I believe he has to rebuild the index, or am I mistaken? In any case, he has to use one method or the other or he will never get his system updated. -- Gerard Seibert [EMAIL PROTECTED] Every man takes the limits of his own field of vision for the limits of the world. Schopenhauer pgplxJNQYesZ5.pgp Description: PGP signature
[OT] CVSUP (was "Re: Was: Re: Why This Infinite Loop??")
Gerard Seibert wrote: On Monday 21 August 2006 13:55, [EMAIL PROTECTED] wrote: On Mon, 21 Aug 2006 13:14:10 -0400 beno wrote: Gerard Seibert wrote: To update portmanager, assuming you have an up-to-date port system: cd /usr/ports/sysutils/portmanager male install & make clean Well, here's exactly what I'm doing: cd /usr/ports/sysutils/portmanager make install make clean /usr/local/bin/portmanager -u -f -l -y and then it proceeds to go back into its infinite loop!!! This is what I'm trying to avoid!!! I presume the reason it does that is because it HASN'T upgraded and is STILL at version 0.2.0_1 Caution: I am new at answering questions, so someone please chime in if I make a mistake. beno, here is a guess: the reason this is happening is that your ports tree (that is, /usr/ports/*) is probably old. The version numbers, checksums, and much more, for EVERY port is stored in the ports tree. Unless you update your ports tree, just deinstalling and reinstalling a port won't make it any newer. There are a few ways to update your ports tree. Chapter 4 of the handbook describes a few ways. Personally I like to use cvsup(1). If you use cvsup(1) you can either update your entire ports tree or just part of it. Here is text straight out of the handbook (http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/ports-using.html ) "...As root, copy /usr/share/examples/cvsup/ports-supfile to a new location, such as /root or your home directory. Edit ports-supfile. Change CHANGE_THIS.FreeBSD.org to a CVSup server near you. See CVSup Mirrors (Section A.5.7) for a complete listing of mirror sites. And now to run cvsup, use the following: # cvsup -L 2 /root/ports-supfile " This might take awhile. You'll see your ports tree getting files added, changed, and removed. After it is done, THEN try deinstalling, building, and reinstalling portmanager, or portupgrade, or whatever. If you don't want to modify your whole ports tree, you can edit ports-supfile a bit more and restrict the changes to just the sysutils directory -- look inside the file for helpful comments on how to do this. IMHO, it might be a lot easier for him to use portsnap. Especially if he is not familiar with the FBSD ports system. Just my opinion though. CVSUP isn't that difficult IMHO to learn, and is a better, more efficient way to download the ports Makefiles. It will take him all of 10-20 minutes to configure if he reads the documentation and uses the example file. -Garrett ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: (no subject) Was: Re: Why This Infinite Loop??
On Monday 21 August 2006 13:55, [EMAIL PROTECTED] wrote: > On Mon, 21 Aug 2006 13:14:10 -0400 beno wrote: > >Gerard Seibert wrote: > >> To update portmanager, assuming you have an > >> up-to-date port system: > >> > >> cd /usr/ports/sysutils/portmanager > >> male install & make clean > > > >Well, here's exactly what I'm doing: > > > >cd /usr/ports/sysutils/portmanager > > > >make install > >make clean > >/usr/local/bin/portmanager -u -f -l -y > > > >and then it proceeds to go back into its infinite > >loop!!! This is what I'm trying to avoid!!! I > >presume the reason it does that is because it > >HASN'T upgraded and is STILL at version 0.2.0_1 > > Caution: I am new at answering questions, so someone > please chime in if I make a mistake. > > beno, here is a guess: the reason this is happening is > that your ports tree (that is, /usr/ports/*) is probably > old. The version numbers, checksums, and much more, for > EVERY port is stored in the ports tree. Unless you update > your ports tree, just deinstalling and reinstalling a port > won't make it any newer. > > There are a few ways to update your ports tree. Chapter 4 > of the handbook describes a few ways. Personally I like > to use cvsup(1). > > If you use cvsup(1) you can either update your entire > ports tree or just part of it. Here is text straight out > of the handbook > (http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/ports-using.html >) > > "...As root, copy /usr/share/examples/cvsup/ports-supfile > to a new location, such as /root or your home directory. > > Edit ports-supfile. > > Change CHANGE_THIS.FreeBSD.org to a CVSup server near you. > See CVSup Mirrors (Section A.5.7) for a complete listing > of mirror sites. > > And now to run cvsup, use the following: > # cvsup -L 2 /root/ports-supfile > " > > This might take awhile. You'll see your ports tree > getting files added, changed, and removed. After it is > done, THEN try deinstalling, building, and reinstalling > portmanager, or portupgrade, or whatever. > > If you don't want to modify your whole ports tree, you can > edit ports-supfile a bit more and restrict the changes to > just the sysutils directory -- look inside the file for > helpful comments on how to do this. IMHO, it might be a lot easier for him to use portsnap. Especially if he is not familiar with the FBSD ports system. Just my opinion though. -- Gerard Seibert [EMAIL PROTECTED] Woman's advice has little value, but he who won't take it is a fool. Cervantes pgpttyYUUg8mM.pgp Description: PGP signature
Re: Why This Infinite Loop??
On Monday 21 August 2006 13:14, beno wrote: > Gerard Seibert wrote: > > To update portmanager, assuming you have an up-to-date port system: > > > > cd /usr/ports/sysutils/portmanager > > male install & make clean > > Well, here's exactly what I'm doing: > > cd /usr/ports/sysutils/portmanager > > make install > make clean > /usr/local/bin/portmanager -u -f -l -y > > and then it proceeds to go back into its infinite loop!!! This is what > I'm trying to avoid!!! I presume the reason it does that is because it > HASN'T upgraded and is STILL at version 0.2.0_1 > > Please help! > TIA, > beno First, you have to update your ports. Do you know how to use 'portsnap'? You could read the man or do this: /usr/sbin/portsnap fetch /usr/sbin/portsnap extract /usr/sbin/portsnap update /usr/sbin/pkg_version -vIL= Actually, I am not sure if you have to run the update command, but it will not hurt anything to do it. I am assuming that you have never used portsnap before. The last command will list everything that needs updating. Update portmanager first. cd /usr/ports/sysutils/portmanager make deinstall make install && make clean Then update the whole system: portmanager -u -f -l -y That should do it. Obviously, everything is run as root. One more thing, please do not reply to me directly and CC the list. I am getting two copies of your posts. I only need one. Thank you! Ciao! -- Gerard Seibert [EMAIL PROTECTED] Dying is one of the few things that can be done as easily lying down. Woody Allen pgp6BLnL2LZji.pgp Description: PGP signature
Re: Why This Infinite Loop??
beno wrote: Garrett Cooper wrote: cd /usr/ports/sysutils/portmanager && make deinstall && make install I'm afraid that just reinstalled 0.2.0_1 ... if you haven't cvsup'ed lately, I'd try to grab a snapshot of ports first. How? TIA, beno Run "rm -Rf on /usr/ports/" to remove your stale ports, then run... fetch ftp://ftp1.freebsd.org/pub/FreeBSD/ports/ports-current/ports.tar.gz -c /root -f ports.tar.gz && tar -xvzpf /root/ports.tar.gz -C /usr/ Which basically takes a fresh copy of the ports available on the FreeBSD FTP and puts it in place of your existing ports. Now you can update port manager... cd /usr/ports/sysutils/portmanager && make deinstall && make install Please read http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/cvsup.html so you can learn how to use CVSUP properly; it's an incredibly beneficial tool for updating not only your ports, but your system itself. -Garrett ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Why This Infinite Loop??
Gerard Seibert wrote: To update portmanager, assuming you have an up-to-date port system: cd /usr/ports/sysutils/portmanager male install & make clean Well, here's exactly what I'm doing: cd /usr/ports/sysutils/portmanager make install make clean /usr/local/bin/portmanager -u -f -l -y and then it proceeds to go back into its infinite loop!!! This is what I'm trying to avoid!!! I presume the reason it does that is because it HASN'T upgraded and is STILL at version 0.2.0_1 Please help! TIA, beno ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Why This Infinite Loop??
Garrett Cooper wrote: cd /usr/ports/sysutils/portmanager && make deinstall && make install I'm afraid that just reinstalled 0.2.0_1 ... if you haven't cvsup'ed lately, I'd try to grab a snapshot of ports first. How? TIA, beno ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Why This Infinite Loop??
On Monday 21 August 2006 12:03, beno wrote: > Gerard Seibert wrote: > > Run 'portmanager -V' and see if it equals: 0.4.1_6. > > 0.2.0 > > > If not, you have an older > > version of portmanager. Update it just like any other port, only do not > > use portmanager to do it. > > That's my question. How do I update it if I can't use portmanager, > portmaster (which I don't have) or portupdate (ditto)? > beno Are you referring to updating portmanager or updating the ports? To update portmanager, assuming you have an up-to-date port system: cd /usr/ports/sysutils/portmanager male install & make clean -- Gerard Seibert [EMAIL PROTECTED] You shouldn't have to pay for your love with your bones and your flesh. Pat Benatar, "Hell is for Children" pgpLbaq3r3XCy.pgp Description: PGP signature
Re: Why This Infinite Loop??
beno wrote: Gerard Seibert wrote: Run 'portmanager -V' and see if it equals: 0.4.1_6. 0.2.0 If not, you have an older version of portmanager. Update it just like any other port, only do not use portmanager to do it. That's my question. How do I update it if I can't use portmanager, portmaster (which I don't have) or portupdate (ditto)? beno cd /usr/ports/sysutils/portmanager && make deinstall && make install ... if you haven't cvsup'ed lately, I'd try to grab a snapshot of ports first. -Garrett ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Why This Infinite Loop??
Gerard Seibert wrote: Run 'portmanager -V' and see if it equals: 0.4.1_6. 0.2.0 If not, you have an older version of portmanager. Update it just like any other port, only do not use portmanager to do it. That's my question. How do I update it if I can't use portmanager, portmaster (which I don't have) or portupdate (ditto)? beno ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Why This Infinite Loop??
On Monday 21 August 2006 10:40, beno wrote: > How do I upgrade portmanager? Run 'portmanager -V' and see if it equals: 0.4.1_6. If not, you have an older version of portmanager. Update it just like any other port, only do not use portmanager to do it. cd /usr/ports/sysutils/portmanager make install && make clean Be sure to update your ports system first. -- Gerard Seibert [EMAIL PROTECTED] Ma Bell is a mean mother! pgpTSdgka323H.pgp Description: PGP signature
Re: Why This Infinite Loop??
Gerard Seibert wrote: Do you have the latest version of 'portmanager' installed? There was an older version that had this bug, but it was fixed. How do I upgrade portmanager? beno ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Why This Infinite Loop??
On Monday 21 August 2006 09:25, beno wrote: > I successfully rebuilt FreeBSD from 5.3 to 6.1. However, when I ran > portmanager -u > my server went into an infinite loop! It kept reinstalling Bind and I > think Perl. I don't think it installed anything more than that. I had > run this command: > make delete-old-libs > but also had added the lib diff file between 5 and 6 (forget its name) > so I had most of my lib files that I needed, and everything seems to be > running okay. Then again, maybe I've missed something. > > Why did this command create an infinite loop (that lasted 6 hours before > I killed it)? Is there a better program/command I should use? How do I > d/l that program? > TIA, Do you have the latest version of 'portmanager' installed? There was an older version that had this bug, but it was fixed. I would recommend that you update your ports and then make sure you have the latest version of 'portmanager' installed. Then run: portmanager -u -f -l -y That will create a log file "/var/log/portmanager.log" that you can inspect later to see what happened if it goes into an infinite loop again, HTH -- Gerard Seibert [EMAIL PROTECTED] A Riverside, California, health ordinance states that two persons may not kiss each other without first wiping their lips with carbolized rosewater. pgpg4UucsMx21.pgp Description: PGP signature
Why This Infinite Loop??
Hi; I successfully rebuilt FreeBSD from 5.3 to 6.1. However, when I ran portmanager -u my server went into an infinite loop! It kept reinstalling Bind and I think Perl. I don't think it installed anything more than that. I had run this command: make delete-old-libs but also had added the lib diff file between 5 and 6 (forget its name) so I had most of my lib files that I needed, and everything seems to be running okay. Then again, maybe I've missed something. Why did this command create an infinite loop (that lasted 6 hours before I killed it)? Is there a better program/command I should use? How do I d/l that program? TIA, beno ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
