Tag Archives: 7.1

How popular is FreeBSD 7.1 and should I proceed with my info?

So i wrote some articles recently for 7.1 and the release-cycle around it to try and provide as much possible information without telling you all things that we as a project cannot make true etc. I see that my “how to upgrade to 7.1″ article is being read a lot, in fact it is one of the most popular items in my entire article-range. Which made me wonder about a few things, which I hope that you (my readers) can answer:

*) Is FreeBSD 7.1 long awaited and popular?
*) Aren’t there enough documents that provide this straight to the point information? (Do this and this and you have 7.1 running)
*) Should I proceed with these kind of articles for the future release-cycle’s?
*) How is 7.1 being received? Do you like it? Do you hate it?

Reasons I want to know this, is whether I should bring in my attention to this area now which I might be doing a ‘difference’ again, and whether it really helps the community or not. And last but not least ofcourse, we tried to work hard to bring you the best release possible, but I personally cannot entirely judge how the community received our work. I think we did great, but I cannot speak for you :)

If you read this, and are willing to help, please respond to this article :-)


FreeBSD 7.1 popular?

After writing my little blog on how to upgrade to 7.1 I got several people telling me that the freebsd-update servers were slow, irresponsive etc. From the information that Colin send to FreeBSD-stable it seems that a lot of people were really waiting for 7.1 to come out, and that they all wanted to upgrade. Colin had made improvements to the system so that it can better deal with the load.

The good thing from this is that a lot of people ARE interested in the latest version, as well as that they use the easy to use application “freebsd-update”. If you run a -RELEASE version, you should use this to easily and quickly upgrade to a later revision.

Keep those bits rolling!

How to upgrade to FreeBSD 7.1

With 7.1 around the corner it might be handy to tell what you need to do in order to upgrade.

First of all you need to understand that I am in no way responsible for the actions you are doing on your system. I can give an advise, but if there is one typo somewhere it could trash your system. That is the case now, and it will forever be as long as there are computers :)

That said: Do you know what kind of user you are?

Did you install via the CD and never heared about CVSup? SVN? and things like that?

Then FreeBSD-update (/usr/sbin/freebsd-update) is the thing for you!
It’s the most simple way to upgrade from a previous -RELEASE (or Security branch) to the current one. Do note that -STABLE or -RC’s are not taken into account and cannot be used to upgrade to 7.1-RELEASE.

In order for you to upgrade please use : /usr/sbin/freebsd-update -r 7.1-RELEASE upgrade && /usr/sbin/freebsd-update -r 7.1-RELEASE install

After this the system will tell you:

Kernel updates have been installed. Please reboot and run
“/usr/sbin/freebsd-update install” again to finish installing updates.

(Thanks richard for the information):

Voila, you will be running 7.1 now!

For people using CVSup: replace the RELENG_7_0 part with RELENG_7_1 (it’s ok if there are other things behind it, as long as you change the zero to a one (0 -> 1)).

Rebuild your kernel as you probably did many times before (cd /usr/src && make buildworld && make buildkernel && make installkernel [reboot in single user mode] mergemaster -p && make installworld && make delete-old && mergemaster [reboot] make delete-old-libs (be careful that ports and things do not depend on older versions. I have been bitten by an account that used the bash shell, with libreadline, which was deleted by make delete-old-libs.. no more bash shell for me!)

If you are doing CVS checkouts you should probably do something with -r RELENG_7_1 or RELENG_7_1_RELEASE to get things going, I would advise the first one since patches will be installed there as well, the _RELEASE branch is static. Then do the tricks like above as well.

If you are a subversion user you should checkout the 7.1 release (all subversion users know how to do this) and perform a bit of magic.

[lang_en]FreeBSD 7.1 release close![/lang_en][lang_nl]FreeBSD 7.1 is bijna daar![/lang_nl]


After some waiting, the FreeBSD team will release the 7.1 version shortly. There were a few showstoppers here and there, a security advisory that popped up and needed attention, but we all overcame that and are ready to do the release. Ofcourse that isn’t being released as we speak, but it’s -very- soon now. 7.1 will kick 2009′s ass to begin with. Then followed by a stunning 8.0-release later that year. It promises to be a very good year for us at the FreeBSD development teams, but also for the users ofcourse!.

Please hold your breath and say “ooeeeee ahhhhh” when the release is there!




Na lang wachten zal het FreeBSD team binnenkort 7.1 vrij geven. Er waren een aantal showstoppers hier en daar, een security advisory die ertussen kwam en aandacht nodig had, maar deze zijn allemaal overkomen en we zijn klaar voor de release. Uiteraard gebeurd dat niet op stel en sprong, maar dat zal -heel- snel nu gebeuren. 7.1 zal 2009′s ass kicken om te beginnen. Daarna zal een geweldige 8.0-release volgen later in het jaar. Dit belooft een schitterend jaar te worden voor ons in het FreeBSD development team, maar uiteraard ook voor de gebruikers!

En nu… de adem inhouden en “Oeeee ahhh” zeggen wanneer de release eenmaal daar is!

Veel plezier!


[lang_en]FreeBSD Ports Tree Unfrozen[/lang_en][lang_nl]FreeBSD Ports Tree vrijgegeven[/lang_nl]

[lang_en]Today the Port management team released the FreeBSD Ports Tree. The Tree is still in a Slush state (no sweeping changes) like the Documentation Tree has, but the tagging for the release is done. Currently the cluster is building the required packages that will be accompanied on the -RELEASE distributions. The next major things is the build of the -RELEASE-CANDIDATE’s which could start any moment ( I am not aware of the most recent planning for them, I will post more info when I know them)[/lang_en]

[lang_nl]Vandaag heeft het FreeBSD Ports management team de FreeBSD Ports Tree vrijgegeven. De Tree is nog wel in een “rustige” status (Waarin geen grote wijzigingen mogen worden aangebracht) net als de Documentatie Tree dat heeft, maar het zogeheten Taggen van de Tree is gedaan. Het cluster wordt nu ingezet om de packages die op de RELEASE versies komen klaar te stomen, zodat deze op tijd meegeleverd kunnen worden. De volgende grote stap is het bouwen van de -RELEASE-CANDIDATE’s, wat elk moment kan gaan gebeuren (Ik ben niet op de hoogte van de meest recente planning hiervoor, zodra ik meer weet post ik de noodzakelijke informatie)[/lang_nl]

[lang_en]FreeBSD Ports tree Frozen by Erwin Lansing[/lang_en][lang_nl]FreeBSD ports tree bevroren door Erwin Lansing[/lang_nl]

[lang_en]Today Erwin Lansing froze the FreeBSD Ports tree in preparation for the 6.4 and 7.1 releases. That basically means that no one can commit to the ports tree without prior approval from the Ports Management team.

The freeze is done to give the machines in the build cluster the time to build packages for both releases, which can be included on the CD’s and uploaded to the various FTP-mirrors so that you (The end user) can use them when you install the versions.

Certain people will get a blanket from the Ports Management team, so that they can improve the current ports and document Security Vulnerabilities where needed, and ofcourse update the packages if that is required.

Stay Tuned :)[/lang_en]

[lang_nl]Vandaag heeft Erwin Lansing de FreeBSD ports tree bevroren in voorbereiding op de 6.4 en 7.1 versies van FreeBSD. Dat betekend in het kort dat niemand nog kan committen in de ports tree zonder expliciete toestemming van het Ports Management team.

De bevriezing wordt gedaan om de machines in het cluster de tijd te geven om packages te maken voor beide releases, zodat deze op de CD bijgevoegd kunnen worden, en op de diverse FTP-mirrors worden gezet, zodat jullie (de eind gebruiker) ze kunnen gebruiken wanneer jullie de versies installeren.

Een aantal mensen zal een vrijbrief krijgen van het Ports Management team, zodat deze de huidige ports kunnen verbeteren, en zodat deze beveiligingswaarschuwingen kunnen documenteren en uiteraard deze updaten als dat nodig is!

Stay tuned :)[/lang_nl]

[lang_en]FreeBSD Also prepares 6.4 release[/lang_en][lang_nl]FreeBSD Start ook met de voorbereidingen voor versie 6.4[/lang_nl]

[lang_en]Several hours after 7.1-PRERELEASE name had been created within 7-STABLE, not branched!, 6.4 had also been named for the time being from 6-STABLE. That means that that branch will also soon split into 6.4-RELEASE (the final branch) to continue for the release. As well as for 7.1.. NO PANIC! It will all be over soon, and you can use a brand new release :-)[/lang_en]

[lang_nl]Enige uren nadat 7.1-PRERELEASE benoemd werd binnen de 7-STABLE tak (niet gebranched, is ook 6.4 benoemd binnen de 6-STABLE. Dat betekend dat de branch binnenkort opgedeeld wordt in 6-STABLE en de 6.4-RELEASE branch welke uiteindelijk zal leiden tot de 6.4-RELEASE versie zoals die gepubliceerd zal worden. Hetzelfde geld voor 7.1. GEEN PANIEK! Het zal snel over zijn, en jullie kunnen dan allemaal snel een nieuwe release gebruiken! :-)[/lang_nl]