difference between cvsup and portsnap
Here at my work we use FreeBSD in production. We have the following debate and wish to know better the differences between cvsup(csup) and portsnap. One of my co-workers think that portsnap should NOT be used and only gets the latest and greatest port collection, no matter what version of FreeBSD is on the server. For example, if you are still running a 5.4 stable box in production and use any of the portsnap, portupgrade, etc utilities, you would pull the current version ports and NOT from teh directory of the 5.4 ports. I.E, risk breaking the production box. So you should not use portsnap ever except for dev boxes. I have always used portsnap to set up a new machine. I have never had it pull a wrong port that I knew of. I think it has to pay attention to the version of the ports it is pulling. which is right? This is a major issue with our production servers. Thanks ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: difference between cvsup and portsnap
On Fri, 29 May 2009, Barry McCormick wrote: Here at my work we use FreeBSD in production. We have the following debate and wish to know better the differences between cvsup(csup) and portsnap. One of my co-workers think that portsnap should NOT be used and only gets the latest and greatest port collection, no matter what version of FreeBSD is on the server. For example, if you are still running a 5.4 stable box in production and use any of the portsnap, portupgrade, etc utilities, you would pull the current version ports and NOT from teh directory of the 5.4 ports. I.E, risk breaking the production box. So you should not use portsnap ever except for dev boxes. The idea that there's a 5.4 ports directory is mistaken. The ports tree isn't branched; note the lack of a tag= entry in the example ports-supfile. csup will let you retrieve from a certain date, but that's not normal usage for the ports tree. So check your ports-supfile. It's probably already retrieving the latest version of ports, just like portsnap. -Warren Block * Rapid City, South Dakota USA ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: difference between cvsup and portsnap
On Fri, May 29, 2009 at 1:09 PM, Barry McCormick ba...@pdc4u.com wrote: Here at my work we use FreeBSD in production. We have the following debate and wish to know better the differences between cvsup(csup) and portsnap. One of my co-workers think that portsnap should NOT be used and only gets the latest and greatest port collection, no matter what version of FreeBSD is on the server. For example, if you are still running a 5.4 stable box in production and use any of the portsnap, portupgrade, etc utilities, you would pull the current version ports and NOT from teh directory of the 5.4 ports. I.E, risk breaking the production box. So you should not use portsnap ever except for dev boxes. I have always used portsnap to set up a new machine. I have never had it pull a wrong port that I knew of. I think it has to pay attention to the version of the ports it is pulling. which is right? This is a major issue with our production servers. Thanks There is no 5.4 branch of the ports collection. If you're running FreeBSD 2, you have the same exact ports collection as FreeBSD 8 does (as long as you get an updated copy of the ports collection, of course). CSup gets the instant CVS revision of the ports collection. Portsnap is a bit delayed because it fetches a tarball of the collection (it doesn't check out from CVS). However, portsnap uses a secure key to verify the integrity of the snapshot retrieved. I personally use portsnap. It's also easier to script. I have this in my crontab; 0 0 * * * root/usr/sbin/portsnap -I cron update /usr/sbin/pkg_version -I -L = -v It updates the index files, not the actual ports collection itself. This way, it wont interrupt any currently running compiles or upgrades. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: difference between cvsup and portsnap
On Fri, May 29, 2009 at 2:03 PM, Glen Barber glen.j.bar...@gmail.com wrote: [snip] Neither one is right, per se. However, if you use one, continue to use _that_one_ to avoid conflicts. Actually meant to say, neither one is wrong or better than the other. Came out wrong. :) -- Glen Barber ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: difference between cvsup and portsnap
On Fri, 29 May 2009 11:09:41 -0600, Barry McCormick ba...@pdc4u.com wrote: For example, if you are still running a 5.4 stable box in production and use any of the portsnap, portupgrade, etc utilities, you would pull the current version ports and NOT from teh directory of the 5.4 ports. I.E, risk breaking the production box. So you should not use portsnap ever except for dev boxes. As far as I understood, the ports tree is always up to date, i. e. ther's no separate tree for 5, 6 and 7 (and 8). If you update your ports tree, using portsnap or c(v)sup, you end up with the latest tree. There isn't a separate ports tree for, ket's say, 5.4-RELEASE, except you use that from the installation media (or from FTP) and DON'T update it. In addition, if you use cvsup to update your sources, you can of course specify the exact release (with patches), the release branch (stable) or the current point in development (head). There's a tool called portdowngrade (if I remember correctly) that lets you fetch ports from an older version. -- Polytropon From Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: difference between cvsup and portsnap
Hi, Barry On Fri, May 29, 2009 at 1:09 PM, Barry McCormick ba...@pdc4u.com wrote: Here at my work we use FreeBSD in production. We have the following debate and wish to know better the differences between cvsup(csup) and portsnap. One of my co-workers think that portsnap should NOT be used and only gets the latest and greatest port collection, no matter what version of FreeBSD is on the server. For example, if you are still running a 5.4 stable box in production and use any of the portsnap, portupgrade, etc utilities, you would pull the current version ports and NOT from teh directory of the 5.4 ports. I.E, risk breaking the production box. So you should not use portsnap ever except for dev boxes. Either way, with 5.X being EOL'd, there is no guarantee current ports will work. I have always used portsnap to set up a new machine. I have never had it pull a wrong port that I knew of. I think it has to pay attention to the version of the ports it is pulling. which is right? This is a major issue with our production servers. Thanks Neither one is right, per se. However, if you use one, continue to use _that_one_ to avoid conflicts. -- Glen Barber ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
