*BSDThis forum is for the discussion of all BSD variants.
FreeBSD, OpenBSD, NetBSD, etc.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Yeah, does blow you away as how easy it is. It's so different from Linux way of life. Be sure to always read the src and ports UPDATING after cvsup.
Are you going to follow RELENG_4 or RELENG_4_10? Myself.... I'm using 5.3 and will follow RELENG_5_3. I usually stick with the release installed on my production boxes.
Distribution: Slackware current, FreeBSD 4.10, 5.4, 6.2, Debian, RedHat, CentOS, Sun Cobalt OS
Posts: 66
Original Poster
Rep:
I suppose i'm gonna stick to the RELENG_4 version since it's for production servers and besides i installed it on a slower machine PII-400Mhz, 128MB RAM, 20GB HDD. Later on i'll probably share some space and dual boot my workstation with the New Technology release.
Originally posted by vaworx Watching the console of FreeBSD updating with cvsup and portupgrade is the most sexiest thing i've ever seen. Sexier than compiling kernel "
I've been attempting to learn FreeBSD for about two weeks now. I've been using Slackware on my main computer for about a year so, in general, I don't consider myself a newbie. I've recently and unknowingly updated to FBSD 5.4-STABLE via cvsup and I'm confused about some of the things I see in the documentation, namely buildworld and installworld. What are these and why are they necessary? After several searches I can't seem to find a good explanation anywhere.
I can see by running make buildworld that lots of things are being compiled, but what specifically and why does *BSD work this way? If anyone can point to an explanation of this, I'd appreciate it.
# buildworld - Rebuild *everything*, including glue to help do
# upgrades.
# installworld - Install everything built by "buildworld".
# world - buildworld + installworld.
FreeBSD is a complete OS, meaning it is more than just the kernel. These commands build all the standard utilities and install them, respectively.
The reason it is done in two steps (although you could combine it into one step if you really know what you're doing) is because you are supposed to build, install, and test the new kernel before installing all the other applications. As you do not want to have all the applications installed but no kernel for that version. Weird things can happen to some apps which may be closely tied to the kernel. This provides a way to reduce the amount of time the system is down and/or out of sych with the world/kernel.
During the buildworld, FreeBSD is building the world... basically all the applications which aren't in the ports tree. And the installworld goes about installing them all.
EDIT: Please tell me you did not upgrade to 5.4-STABLE from a 4.x branch. And if you did, that you fully read and understood ALL of /usr/src/UPDATING from the last version of 4.x you had up through the date you grabbed the stable sources.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.