Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 12 Oct 2012 11:02:47 +0200
From:      Bas Smeelen <>
Subject:   Re: problems upgrading from 7.2-RELEASE-p8 to 7.4 or 9.0-RELEASE
Message-ID:  <>
In-Reply-To: <>
References:  <> <> <>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
On 10/12/2012 10=3A53 AM=2C Jamie Paul Griffin wrote=3A
=3E =5B Greg Larkin wrote on Thu 11=2EOct=2712 at 20=3A49=3A19 -0400 =5D
=3E=3E Hi Stuart=2C
=3E=3E If you click the link in this mailing list article
=3E=3E =28http=3A//lists=2Efreebsd=2Eorg/pipermail/freebsd-questions/2010-J=
=3E=3E then follow the rest of the threaded messages=2C you should be able=
=3E=3E the problem once you upgrade to 7=2E4=2E
=3E=3E The issue is that freebsd-update cannot update the ld-elf=2Eso=2E1 b=
=3E=3E on a running system=2C so after the upgrade to 7=2E4 =28or higher=29=
=2C the
=3E=3E system is not completely updated=2E
=3E=3E This message
=3E=3E =28http=3A//lists=2Efreebsd=2Eorg/pipermail/freebsd-questions/2010-J=
=3E=3E has a fix=2C but it involves booting from a liveCD and replacing the=

=3E=3E binary manually=2E
=3E Would it be easier to do an update by building from source=3F I=27ve ne=
ver used freebsd-update myself so not had to troubleshoot these issues befo=

That=27s probably the best way=2E

Bit I am wondering about this=2E
I upgraded several systems =28physical and virtual machines=29 with=20
freebsd-update from 7=2E1 -=3E 7=2E3 -=3E 8=2E1 -=3E 8=2E3 and also one sys=
tem from 7=2E1 -=3E=20
7=2E4 =28with custom kernels=29 and did not encounter this=2E Did I just ge=
t lucky then=3F

This e-mail message=2C including any attachment=28s=29=2C is intended solel=
y for the addressee or addressees=2E Any views or opinions presented herein=
 are solely those of the author and do not necessarily represent those of O=

If you are not the intended recipient of this communication please return t=
his e-mail message and the attachment=28s=29 to the sender and delete and d=
estroy all copies=2E

Want to link to this message? Use this URL: <>