cvsup newbie questions

Kevin Smith smithcam at
Fri Dec 17 22:43:05 PST 2004

Thanks for the tips.  For the moment, I'm leaving the OS sources alone 
and I'm updating the ports collection because my goal is to update gnome 
to version 2.8.  The OS seems to be fine - although I'm sure there are 
additional bug fixes I can benefit from - but I'm a little scared to go 
through the build kernel/world thing right now - especially since 
everything is running nicely. (I have not had the OS crash in the 2 
months since I've installed it - it has run continously -yet my linux 
2.6 installation crashed regularly).

I do have a few additional questions...

1) is there a test utility that I can run that will tell me which cvsup 
mirror server will be fastest ?  I did this the manual way by pinging a 
few and looking at the ave times coming back.

2) If I do update (src-all) using 5.3-RELENG tag is my version still 
called 5.3-RELEASE ? - or is it now some new release of that (ie like 
5.3.1 ?)...I guess my question is:  Are all updates of 5.3-RELEASE 
source still called 5.3-RELEASE.

3) After my cvsup of the ports collection completes updating, is there 
any easy way to check which ports were updated ?

Joshua Tinnin wrote:

>Whoops ... I misunderstood you ...
>On Friday 17 December 2004 02:58 pm, Joshua Tinnin 
><krinklyfig at> wrote:
>>On Friday 17 December 2004 01:11 pm, Kevin Smith
>><smithcam at> wrote:
>>>So, if I am just interested in the latest fixes/version for
>>>applications running on 5.3-Release, should I just upgrade the
>>>ports collection ?
>>No, the ports collection is the collection of 3rd-party apps'
>>Makefiles and patches - it just simplifies installing applications.
>So, yes, if you're just interested in fixes for apps, then update the 
>ports collection. Still, I recommend updating to the latest sources for 
>any RELEASE, as most of the time the fixes are truly important for most 
>users, and they won't disrupt your system other than the actual 
>building and installing (well, if it can possibly be avoided, but in 
>this case you won't notice any difference). Also, once you have the 
>source, then updating with src-all with your RELEASE tag will only 
>update critical fixes, not all the sources over again. It's also 
>possible to patch your system manually by fine-tuning the sources you 
>want with cvsup and then just rebuilding that part, or without using 
>cvsup at all (using patch(1)), but if you're not familiar with that, 
>then start with updating the complete system through these steps 
>(briefly): cvsup your source, mergemaster -p, buildworld, build kernel, 
>install kernel, reboot into single user, installworld and mergemaster. 
>It's a bit of a trick the first time if you're not familiar with it, 
>but the handbook walks you through it, and it's not as scary as it 
>might sound. Just do it exactly the way they say, and *don't skip 
>anything*, and you should be fine. If not, you can always ask here. 
>BTW, I personally recommend not using the -j switch when doing 
>buildworld. The handbook warns that it's not supported, although plenty 
>of people use it anyway and later come here with related problems, so 
>it might save headaches if you don't mess with it until and unless you 
>want to try it for testing.
>- jt
>freebsd-questions at mailing list
>To unsubscribe, send any mail to "freebsd-questions-unsubscribe at"

More information about the freebsd-questions mailing list