Date: Sun, 30 May 2010 16:15:25 -0400 From: Michael Powell <nightrecon@hotmail.com> To: freebsd-questions@freebsd.org Subject: Re: what would take to allow binary upgrade to amd64? Message-ID: <htuh0p$tfj$1@dough.gmane.org> References: <AANLkTinkGYhDHtGBjyCcWIdG6ePPgqAAxeoTdGZHD4zP@mail.gmail.com> <AANLkTikTmFxYBgJ6-KJ5qINGlHOGRCt_RymgHyBiRBCT@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Rob Farmer wrote: > On Sun, May 30, 2010 at 11:51 AM, Eitan Adler <lists@eitanadler.com> > wrote: >> I know that attempting to change from i386 to amd64 is is not possible > > The proper procedure for such an upgrade is as follows: > > 1) download and burn the relevant amd64 iso > 2) update your backups > 3) reformat and reinstall the OS from the CD > 4) restore your data and system config from the backups > 5) resume normal operation > > If the thought of reformatting your system is scary, because you don't > have backups or aren't sure they are comprehensive or work, then solve > that problem, rather than trying to invent workarounds to cover for > bad system administration. It will serve you much better in the long > run. I agree with this wholeheartedly. I recently posed the question about doing this with a make buildworld/etc dance from i386 to amd64, e.g. if there was a known sane method for accomplishing this. The general consensus was 'well, maybe if you spend enough time mucking with myriad problems as they come up maybe it's possible...'. Basically you will spend less time following the above directions, finish the project and be free to move on to others more quickly. It is easier when dealing with servers as they usually only have a fairly limited number of ports installed. Having the appropriate backups on hand, as if for bare-metal recovery, also allows for rolling it back to the previous state fairly quickly should one get into a stop/no-go/stuck situation. -Mike
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?htuh0p$tfj$1>