Re: Ports collection issue
Lane wrote: On Friday 27 October 2006 07:16, Roger 'Rocky' Vetterberg wrote: Lane wrote: Adrian, Use /usr/ports/net/cvsup-without-gui and create a cvsupfile. You can then selectively install src-all, src-contrib, ports-all and any of the various ports sub-trees that you need (but stick with ports-all). cvsup will get the proper Makefiles and whatnot for you. Email me if you need help setting that up. lane I would recommend using csup instead of cvsup. It has fewer dependencies, is very lightweight and works very well if you just want to occasionally checkout ports or src. I believe that csup is also part of the basesystem in newer releases. -- R OMG! I totally missed csup. Thanks for the tip! You might look into portsnap. I find it much easier and faster to use than c[v]sup: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/portsnap.html -- Jonathan Arnold (mailto:[EMAIL PROTECTED]) Daemon Dancing in the Dark, a FreeBSD weblog: http://freebsd.amazingdev.com/blog/ UNIX is user-friendly. It's just a bit picky about who its friends are. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Ports collection issue
On 10/27/06, Roger 'Rocky' Vetterberg <[EMAIL PROTECTED]> wrote: Andy Greenwood wrote: > Is it possible to use csup with my existing cvsup files? I skimmed the > man page and it looks very similar. Is there any advantage to using > cvsup over csup? I use the same files for csup as I used for cvsup. You should not have to change anything except removing the 'v' after the 'c' in 'cvsup' on the command-line. :) Csup is basically cvsup rewritten in C instead of Modula-3. While cvsup is an excellent program that certainly makes exactly what it was designed to do, it unfortunately has some dependencies that are not common on most installations. I do not know of any advantages that cvsup might have over csup, more then the fact that it is a thoroughly tested program that has performed well for several years, while csup is a relatively new program. AFAIK there has not been any reports of problem with csup though, so I would say its safe to use. Thanks for the info! Anything I can do to reduce dependancies on my underpowered frankenstein box is a good thing! -- R -- I'm nerdy in the extreme and whiter than sour cream ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Ports collection issue
Andy Greenwood wrote: > Is it possible to use csup with my existing cvsup files? I skimmed the > man page and it looks very similar. Is there any advantage to using > cvsup over csup? I use the same files for csup as I used for cvsup. You should not have to change anything except removing the 'v' after the 'c' in 'cvsup' on the command-line. :) Csup is basically cvsup rewritten in C instead of Modula-3. While cvsup is an excellent program that certainly makes exactly what it was designed to do, it unfortunately has some dependencies that are not common on most installations. I do not know of any advantages that cvsup might have over csup, more then the fact that it is a thoroughly tested program that has performed well for several years, while csup is a relatively new program. AFAIK there has not been any reports of problem with csup though, so I would say its safe to use. -- R ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Ports collection issue
On Friday 27 October 2006 07:16, Roger 'Rocky' Vetterberg wrote: > Lane wrote: > > Adrian, > > > > Use /usr/ports/net/cvsup-without-gui and create a cvsupfile. You can > > then selectively install src-all, src-contrib, ports-all and any of the > > various ports sub-trees that you need (but stick with ports-all). > > > > cvsup will get the proper Makefiles and whatnot for you. > > > > Email me if you need help setting that up. > > > > lane > > I would recommend using csup instead of cvsup. > It has fewer dependencies, is very lightweight and works very well > if you just want to occasionally checkout ports or src. > I believe that csup is also part of the basesystem in newer releases. > > -- > R > OMG! I totally missed csup. Thanks for the tip! lane ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Ports collection issue
Is it possible to use csup with my existing cvsup files? I skimmed the man page and it looks very similar. Is there any advantage to using cvsup over csup? On 10/27/06, Roger 'Rocky' Vetterberg <[EMAIL PROTECTED]> wrote: Lane wrote: > Adrian, > > Use /usr/ports/net/cvsup-without-gui and create a cvsupfile. You can then > selectively install src-all, src-contrib, ports-all and any of the various > ports sub-trees that you need (but stick with ports-all). > > cvsup will get the proper Makefiles and whatnot for you. > > Email me if you need help setting that up. > > lane I would recommend using csup instead of cvsup. It has fewer dependencies, is very lightweight and works very well if you just want to occasionally checkout ports or src. I believe that csup is also part of the basesystem in newer releases. -- R ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]" -- I'm nerdy in the extreme and whiter than sour cream ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Ports collection issue
Lane wrote: > Adrian, > > Use /usr/ports/net/cvsup-without-gui and create a cvsupfile. You can then > selectively install src-all, src-contrib, ports-all and any of the various > ports sub-trees that you need (but stick with ports-all). > > cvsup will get the proper Makefiles and whatnot for you. > > Email me if you need help setting that up. > > lane I would recommend using csup instead of cvsup. It has fewer dependencies, is very lightweight and works very well if you just want to occasionally checkout ports or src. I believe that csup is also part of the basesystem in newer releases. -- R ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Ports collection issue
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Lane wrote: > On Thursday 26 October 2006 23:16, Garrett Cooper wrote: >> Lane wrote: >>> On Thursday 26 October 2006 19:07, Rik Davis wrote: Guys, I'm a die hard freebsd user, but I am finding myself becomeing quite frustrated with why you completely pulled the 5.4 ports collection off of your ftp sites. When I try to use my /stand/sysinstall now and attempt to connect to you ftp server, I ge the error that it cannot locate the 5.4-RELEASE packages. Why would you remove a collection that is still in such high demand by those of us that have yet to upgrade our binaries to a later version? I depend on that being there, but this is not leaving a very pleasant taste in my mouth. Also, this is not the first time I have seen you do this. What am I supposed to do now that I no longer have access to those packages? Sincerely, Adrian Brooks >>> Adrian, >>> >>> Use /usr/ports/net/cvsup-without-gui and create a cvsupfile. You can >>> then selectively install src-all, src-contrib, ports-all and any of the >>> various ports sub-trees that you need (but stick with ports-all). >>> >>> cvsup will get the proper Makefiles and whatnot for you. >>> >>> Email me if you need help setting that up. >>> >>> lane >> Adrian, >> Please note the fact that a lot of software distributors, >> regardless of whether you pay for the product or not, have a limited set >> of supported versions of their software for a reason. >> In this case FreeBSD did phase out their old versions of >> software for a reason, and that was supportability and space as Kris >> mentioned. So, please upgrade to the latest version of your major >> version fork (5.5 I believe). >> That is all. >> -Garrett > > Just a note for clarification: > > While the source and ports collection for 5.X may NOT be available using > sysinstall, it should be recognized that sysinstall is really only reliable > for initial installation of whatever is the current version (give or take a > release or two). > > cvsup and portupgrade are the preferred methods for maintaining the software. > > Just for verification I have recently used cvsup to download the entire > FreeBSD-3.4 system, including ports (That's right, 3.4). While the ports may > not be tied directly to the kernel version, they are there as well. > > So, space considerations may be important to the maintainers, but I think > they > put a premium on continuity. And being able to go backward three different > versions is pretty darned cool! > > lane Well, fair enough.. the only thing is that the number of people who can reply with a "Hey, I can help you with that particular issue" response is much greater for more recent versions. Plus, if you do run into a seriously issue with a driver or interface, you're sort of stuck into upgrading anyhow.. Backwards compatibility is good though, even at the cost of going into unknown territory by yourself as (almost) everyone else has updated their versions to something a bit more current :). Plus, I'd be sure that any issues that existed security-wise do or don't affect the version you currently have if it's out of date. For instance, the OpenSSL buffer overrun issue that was discovered 2 months ago I think. I believe that the issue was fixed and patched in a few CVS source trees, but not in others. So related to my previous comments, in general these are 2 important questions to consider when administering your system: 1. Is it or is it not secure, due to lack of support? 2. If not, how much is it worth to me to manually update and patch the source (assuming it's possible) to fix the vulnerabilities present in my system instead of just upgrading? - -Garrett -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFQa5q6CkrZkzMC68RAv1rAJ94e4hw5HLL4cAvvwUuzD7xqwVAWwCeJxKp ZRfmjACmNZ6C4485/BGdtuQ= =dt+I -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Ports collection issue
On Thursday 26 October 2006 23:16, Garrett Cooper wrote: > Lane wrote: > > On Thursday 26 October 2006 19:07, Rik Davis wrote: > >> Guys, > >> > >> I'm a die hard freebsd user, but I am finding myself becomeing quite > >> frustrated with why you completely pulled the 5.4 ports collection off > >> of your ftp sites. > >> > >> When I try to use my /stand/sysinstall now and attempt to connect to > >> you ftp server, I ge the error that it cannot locate the 5.4-RELEASE > >> packages. Why would you remove a collection that is still in such high > >> demand by those of us that have yet to upgrade our binaries to a later > >> version? > >> > >> I depend on that being there, but this is not leaving a very pleasant > >> taste in my mouth. Also, this is not the first time I have seen you do > >> this. What am I supposed to do now that I no longer have access to those > >> packages? > >> > >> Sincerely, > >> > >> Adrian Brooks > > > > Adrian, > > > > Use /usr/ports/net/cvsup-without-gui and create a cvsupfile. You can > > then selectively install src-all, src-contrib, ports-all and any of the > > various ports sub-trees that you need (but stick with ports-all). > > > > cvsup will get the proper Makefiles and whatnot for you. > > > > Email me if you need help setting that up. > > > > lane > > Adrian, > Please note the fact that a lot of software distributors, > regardless of whether you pay for the product or not, have a limited set > of supported versions of their software for a reason. > In this case FreeBSD did phase out their old versions of > software for a reason, and that was supportability and space as Kris > mentioned. So, please upgrade to the latest version of your major > version fork (5.5 I believe). > That is all. > -Garrett Just a note for clarification: While the source and ports collection for 5.X may NOT be available using sysinstall, it should be recognized that sysinstall is really only reliable for initial installation of whatever is the current version (give or take a release or two). cvsup and portupgrade are the preferred methods for maintaining the software. Just for verification I have recently used cvsup to download the entire FreeBSD-3.4 system, including ports (That's right, 3.4). While the ports may not be tied directly to the kernel version, they are there as well. So, space considerations may be important to the maintainers, but I think they put a premium on continuity. And being able to go backward three different versions is pretty darned cool! lane ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Ports collection issue
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Lane wrote: > On Thursday 26 October 2006 19:07, Rik Davis wrote: >> Guys, >> >> I'm a die hard freebsd user, but I am finding myself becomeing quite >> frustrated with why you completely pulled the 5.4 ports collection off of >> your ftp sites. >> >> When I try to use my /stand/sysinstall now and attempt to connect to you >> ftp server, I ge the error that it cannot locate the 5.4-RELEASE packages. >> Why would you remove a collection that is still in such high demand by >> those of us that have yet to upgrade our binaries to a later version? >> >> I depend on that being there, but this is not leaving a very pleasant >> taste in my mouth. Also, this is not the first time I have seen you do >> this. What am I supposed to do now that I no longer have access to those >> packages? >> >> Sincerely, >> >> Adrian Brooks >> >> > Adrian, > > Use /usr/ports/net/cvsup-without-gui and create a cvsupfile. You can then > selectively install src-all, src-contrib, ports-all and any of the various > ports sub-trees that you need (but stick with ports-all). > > cvsup will get the proper Makefiles and whatnot for you. > > Email me if you need help setting that up. > > lane Adrian, Please note the fact that a lot of software distributors, regardless of whether you pay for the product or not, have a limited set of supported versions of their software for a reason. In this case FreeBSD did phase out their old versions of software for a reason, and that was supportability and space as Kris mentioned. So, please upgrade to the latest version of your major version fork (5.5 I believe). That is all. - -Garrett -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFQYgg6CkrZkzMC68RAg61AJ4n0Xly1rzorhV1aBe2/lyoSGUeAACfcdou rycJyS0SfUh/1RmvOhPGyjY= =+fPm -END PGP SIGNATURE- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Ports collection issue
On Thu, Oct 26, 2006 at 05:07:54PM -0700, Rik Davis wrote: > Guys, > > I'm a die hard freebsd user, but I am finding myself becomeing quite > frustrated with why you completely pulled the 5.4 ports collection > off of your ftp sites. Because 5.4 was released nearly 18 months ago and disk space is finite. Note that even after moving aside the 5.4 packages to make enough room to fit the forthcoming 6.2 packages, the FTP site takes up close to half a terabyte of space. > When I try to use my /stand/sysinstall now and attempt to connect to > you ftp server, I ge the error that it cannot locate the 5.4-RELEASE > packages. Why would you remove a collection that is still in such > high demand by those of us that have yet to upgrade our binaries to > a later version? > > I depend on that being there, but this is not leaving a very > pleasant taste in my mouth. Also, this is not the first time I have > seen you do this. What am I supposed to do now that I no longer have > access to those packages? Use an alternative mirror which still carries the old releases. For example ftp-archive.freebsd.org, and probably others. In future you might like to consider alternative explanations than malicious intent on the part of FreeBSD to harm you, before posting. Kris pgpJLU5SvLR7Y.pgp Description: PGP signature
Re: Ports collection issue
On Thursday 26 October 2006 19:07, Rik Davis wrote: > Guys, > > I'm a die hard freebsd user, but I am finding myself becomeing quite > frustrated with why you completely pulled the 5.4 ports collection off of > your ftp sites. > > When I try to use my /stand/sysinstall now and attempt to connect to you > ftp server, I ge the error that it cannot locate the 5.4-RELEASE packages. > Why would you remove a collection that is still in such high demand by > those of us that have yet to upgrade our binaries to a later version? > > I depend on that being there, but this is not leaving a very pleasant > taste in my mouth. Also, this is not the first time I have seen you do > this. What am I supposed to do now that I no longer have access to those > packages? > > Sincerely, > > Adrian Brooks > > Adrian, Use /usr/ports/net/cvsup-without-gui and create a cvsupfile. You can then selectively install src-all, src-contrib, ports-all and any of the various ports sub-trees that you need (but stick with ports-all). cvsup will get the proper Makefiles and whatnot for you. Email me if you need help setting that up. lane ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
