Date: Wed, 01 Jan 2014 20:41:36 -0700 From: Gary Aitken <freebsd@dreamchaser.org> To: Erich Dollansky <erichsfreebsdlist@alogt.com> Cc: FreeBSD Mailing List <freebsd-questions@freebsd.org> Subject: Re: updating /sys/sys Message-ID: <52C4DFF0.2030108@dreamchaser.org> In-Reply-To: <20140102074837.564f662f@X220.alogt.com> References: <52C37801.8010001@dreamchaser.org> <20140101114745.3a3e37fb@X220.alogt.com> <52C3CC18.30407@dreamchaser.org> <20140101184142.5f11b3f6@X220.alogt.com> <52C4530F.3070405@dreamchaser.org> <20140102074837.564f662f@X220.alogt.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 01/01/14 16:48, Erich Dollansky wrote: >> Unfortunately, it is not possible to rerun freebsd-update on the same >> version to correct a problem such as this. >> >> I am not sure whether /usr/src/sys is considered part of the "world" >> or "kernel" components or not; if it is not, then the above would >> explain the behavior. If it is considered part of "world" or >> "kernel", then it would not explain it. > > You need the header files - which are included there - to compile any > piece of software. This could be the reason why they are there. I understand that! > I am a bit confused about how you update and why. If you compile your > own kernel, just use svn to keep the sources current. If you do not > compile your own kernel, just ignore there things as they will not > affect you. I don't compile my own kernel on this system. However, I can't "just ignore these things". The header files are needed, as you point out, to compile anything. As I described earlier, the header files did in fact change with the dot releases of release 9, and in a manner such that some of the ports would not compile if the header files were not also updated. In particular, sysutils/lsof. So the header files have to be updated with each dot release update. Since the header files were not updated by my "freebsd-update -r 9.2-RELEASE upgrade" command, I had to update them separately. I *suspect* that problem could have been avoided if my /etc/freebsd-update.conf had "StrictComponents yes" set. If freebsd-update allowed updating the current install to itself, I could have changed the StrictComponents flag and rerun it, but freebsd-update does not allow that. So one is left with having to update the source in some other way, such as the one I used. In any case, the system is now consistent and I've changed the StrictComponents flag so it should, I hope, update properly in the future. Gary
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?52C4DFF0.2030108>