Solved If I use freebsd-update, do I still need svn to get source?

horseflesh

horseflesh

After a long hiatus as a lazy non-upgrading admin, I am coming back to FreeBSD and trying to get up to speed with the changes. I have what I hope will be a quick and easy question.

I'm using default freebsd-update settings which seemingly includes updating the source.

Code: 
# Components of the base system which should be kept updated.
Components src world kernel
However, the Handbook refers you to svn for updating source. This seems to be unnecessary if you are using freebsd-update. I would have expected the Handbook to make that clear, though.

I guess I don't need to make the world if I am using freebsd-update but as a guy who started with FreeBSD 4 it makes me nervous not to have a righteous source tree. (I may also wish to compile a custom kernel.) Will I be able to make the world and kernel with the latest -RELEASE source if freebsd-update is my only means of updating the source tree?
 
horseflesh said:
After a long hiatus as a lazy non-upgrading admin, I am coming back to FreeBSD and trying to get up to speed with the changes. I have what I hope will be a quick and easy question.

I'm using default freebsd-update settings which seemingly includes updating the source.

Code: 
# Components of the base system which should be kept updated.
Components src world kernel
However, the Handbook refers you to svn for updating source. This seems to be unnecessary if you are using freebsd-update. I would have expected the Handbook to make that clear, though.

I guess I don't need to make the world if I am using freebsd-update but as a guy who started with FreeBSD 4 it makes me nervous not to have a righteous source tree. (I may also wish to compile a custom kernel.) Will I be able to make the world and kernel with the latest -RELEASE source if freebsd-update is my only means of updating the source tree?
Click to expand...
You don't need to use SVN to update the source if you update with freebsd-update. Remember that when the kernel is patched, you need to rebuild it yourself, since you'll get GENERIC installed with freebsd-update.
 
That all makes sense. Thank you kindly for the confirmation. (I'm on a generic kernel for the moment.)
 
Here is the skinny.
On first run freebsd-update updates kernel, then needs reboot.
Second run it updates base, needs reboot. Notice on screen the critical text. You must upgrade ports/packages before third run.
Section 23.2.3.2 has the details but if you fail to do this, the third run of freebsd-update will delete old library's and things will break.
Follow the directions on screen after each step and you will be fine.
 
I know this thread is solved but the Handbook reference above is pertinent to updating /usr/ports using Subversion. I see the thread is about updating kernel source but I just wanted to make note of this since freebsd-update has nothing to do with updating /usr/ports and that wasn't entirely clear in this post.
 
The Note of the handbook page says it all:
"Depending upon whether any library version numbers were bumped, there may only be two install phases instead of three."

In this case you would not have to worry about ports and packages.
Still to say ports updating has nothing to do with freebsd-update is incorrect.

Are you saying the manual is wrong? That is all I have to go by.
 
Sevendogs said:
I see the thread is about updating kernel source but I just wanted to make note of this since freebsd-update has nothing to do with updating /usr/ports and that wasn't entirely clear in this post.
Click to expand...
Phishfry said:
Still to say ports updating has nothing to do with freebsd-update is incorrect.
Click to expand...
From my understanding both statements are correct. freebsd-update does not update /usr/ports. But after a major version change it is necessary to update all ports. The statement of Sevendogs counts for me as a warning that the admin is responsible for taking care.
 
Perhaps I misspoke. All I meant was that the freebsd-update tool is not used to update /usr/ports. I read the handbook reference and it discusses updating the sources but I incorrectly assumed this was referring to the ports tree. My apologies.

EDIT - I corrected my statement to the red text above.
 
chrbr said:
From my understanding both statements are correct. freebsd-update does not update /usr/ports. But after a major version change it is necessary to update all ports. The statement of Sevendogs counts for me as a warning that the admin is responsible for taking care.
Click to expand...
Correct chrbr, THAT is how I should have put it! Sorry, I misspoke, thank you for clarifying.
 
Didn't mean to be a jerk about it but that seemed incorrect to me. I know I say things that are wrong and I feel like a idiot when I look at some of my earliest posts.
 
Not at all Phishfry, I had the thought in my head and what I put on "paper" doesn't always match. Chrbr paraphrased exactly what I had wanted to say originally ;) Thanks.
 
You must log in or register to reply here.
Back
Top