Date: Thu, 8 Oct 2009 21:06:20 +0200 From: =?iso-8859-1?Q?Eirik_=D8verby?= <ltning@anduin.net> To: Martin Turgeon <freebsd@optiksecurite.com> Cc: freebsd-jail@freebsd.org Subject: Re: Can't upgrade jails to 8.0 using freebsd-update Message-ID: <F389E50E-1C7B-49D1-BB0F-402C1D49FBFC@anduin.net> In-Reply-To: <4ACE37D6.9040908@optiksecurite.com> References: <4ACE2829.6030804@optiksecurite.com> <295A1256-A620-4DD1-8B7F-22BDB216D164@anduin.net> <4ACE37D6.9040908@optiksecurite.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 8. okt. 2009, at 21.04, Martin Turgeon wrote: > Eirik =D8verby a =E9crit : >> On 8. okt. 2009, at 19.58, Martin Turgeon wrote: >> >>> Hi everyone! >>> >>> I just upgraded a 7.2-REL to 8.0RC1 using freebsd-update. The =20 >>> upgrade >>> went fine on the base system following the procedure written in the >>> announcement email by Ken Smith. My problem is when I try to =20 >>> upgrade my >>> jails, I get this message: >>> >>> # freebsd-update -b /usr/jail/mysql/ fetch install >>> Looking up update.FreeBSD.org mirrors... 3 mirrors found. >>> Fetching metadata signature for 8.0-RC1 from =20 >>> update5.FreeBSD.org... done. >>> Fetching metadata index... done. >>> Inspecting system... done. >>> Preparing to download files... done. >>> >>> No updates needed to update system to 8.0-RC1-p0. >>> No updates are available to install. >>> Run '/usr/sbin/freebsd-update fetch' first. >>> >>> But, if I compare the dates of the files in the base system to the =20= >>> files >>> in the jails, it's obvious that the jails are not up to date. >>> >>> It seems like freebsd-update doesn't care about the basedir I =20 >>> specified. >> >> It does, but if you do a 'uname -a' - inside or outside the jail - =20= >> you'll see that it reports the OS revision of the host. So you =20 >> should have updated your jails first, then the host ... >> > Ok but if I update in the process of upgrading the first jail, the =20 > new kernel will be installed and asked to reboot. After that, I will =20= > have the same problem when upgrading the other jails and the base =20 > system, right? There must be something I don't understand well. =20 > Thanks a lot for your answer. The kernel will be installed inside the jail, and the message about =20 rebooting can be safely ignored. Just run the install command once =20 more, and you're done and can move on to the next jail. :) /Eirik > Martin >> One way to get around it is to replace /usr/bin/uname with a shell =20= >> script, which calls the original uname (which you have renamed) and =20= >> pipes through something like sed to replace the revision with what =20= >> you used to have: >> >> #!/bin/sh >> /usr/bin/uname.org $* | sed s/"8.0-RC1-p0"/"7.2-RELEASE_p3"/g >> >> And this is a seriously butt ugly hack. >> >> /Eirik >> >>> Thanks a lot for your help, >>> >>> Martin >>> >>> _______________________________________________ >>> freebsd-jail@freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-jail >>> To unsubscribe, send any mail to = "freebsd-jail-unsubscribe@freebsd.org=20 >>> " >>> >> > > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?F389E50E-1C7B-49D1-BB0F-402C1D49FBFC>