tag:blogger.com,1999:blog-4088979.post1989357241641721644..comments2023-10-16T06:06:25.012-04:00Comments on TaoSecurity Blog: Upgrading FreeBSD 7.0 to 7.1Richard Bejtlichhttp://www.blogger.com/profile/13512184196416665417noreply@blogger.comBlogger6125tag:blogger.com,1999:blog-4088979.post-84064091936790101842009-05-08T23:46:00.000-04:002009-05-08T23:46:00.000-04:00This comment has been removed by a blog administrator.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-4088979.post-53229090286957096182009-05-05T04:58:00.000-04:002009-05-05T04:58:00.000-04:00This comment has been removed by a blog administrator.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-4088979.post-80012491116136723242009-04-22T10:14:00.000-04:002009-04-22T10:14:00.000-04:00This comment has been removed by a blog administrator.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-4088979.post-10313305535651301552009-02-03T20:37:00.000-05:002009-02-03T20:37:00.000-05:00Just as an add on, the upgrade seems to require th...Just as an add on, the upgrade seems to require that you recompile your kernel to get to 7.1-RELEASE-p2. <BR/><BR/>After doing the second "freebsd-udpate install", my system reported the version as "7.1-RELEASE FreeBSD 7.1-RELEASE #0"<BR/><BR/>I was using GENERIC on my test box, so I performed<BR/><BR/>[root@freebsd2 ~] make buildkernel KERNCONF=GENERIC<BR/>[root@freebsd2 ~] make installkernel KERNCONF=GENERIC<BR/><BR/>reboot again<BR/><BR/>After this, uname -a reports the system at 7.1-RELEASE-p2.<BR/><BR/>[me@freebsd2 ~]$ uname -a<BR/>FreeBSD freebsd2.foo.com 7.1-RELEASE-p2 FreeBSD 7.1-RELEASE-p2 #1: Tue Feb 3 17:00:46 MST 2009Jason Woodhttps://www.blogger.com/profile/01154638200146139984noreply@blogger.comtag:blogger.com,1999:blog-4088979.post-12189806260247191962009-02-01T23:31:00.000-05:002009-02-01T23:31:00.000-05:00I am new to FreeBSD kernel customization, and I ha...I am new to FreeBSD kernel customization, and I have learned that freebsd-update does not deal with CUSTOM kernels. <BR/><BR/>I had to:<BR/><BR/>cd /usr/src<BR/>make buildkernel KERNCONF=CUSTOM<BR/>make installkernel KERNCONF=CUSTOM<BR/><BR/>after the update to introduce the changes.<BR/><BR/>Reading Chris's post it looks like it may be a good thing to leave kernel stuff alone for now when binary updating...<BR/><BR/>Thanks for the post.Unknownhttps://www.blogger.com/profile/12189889890206676294noreply@blogger.comtag:blogger.com,1999:blog-4088979.post-18709877062535173392009-02-01T05:40:00.000-05:002009-02-01T05:40:00.000-05:00It may be worth noting that from previous personal...It may be worth noting that from previous personal experience this process is not entirely fault free.<BR/><BR/>After updating the system in the usual way and receiving no errors (i.e everything appeared normal) upon reboot the bootloader couldn't find the kernel. The kernel was never created so I attempted to load the previous one but this had also been removed. I searched for the kernel but it was nowhere to be found.<BR/><BR/>I'm not entirely sure what happend but it was a frustrating few hours and it still puzzles me why a backup of the previous version is not created.<BR/><BR/>I had to use the installation disk to create the kernel in the appropriate location but this wasn't as straight forward either.<BR/><BR/>Whilst this problem seems to the be in the minority I've gone back to using CVS and the typical buildworld process.<BR/><BR/>This was from a 7.1 RC2 to 7.1 when it was first released but when I looked into it has happend since its introduction in a handful of cases.Anonymousnoreply@blogger.com