Date: Fri, 4 Jun 2010 01:40:07 -0700 From: Garrett Cooper <yanefbsd@gmail.com> To: Pete French <petefrench@ticketswitch.com> Cc: fbsdmail@dnswatch.com, freebsd-amd64@freebsd.org, yaneurabeya@gmail.com Subject: Re: When will the amd64 be supported? Message-ID: <AANLkTil-dacOqcL9ddAdAWjoZOmTDWLrmIvm4p3yAqij@mail.gmail.com> In-Reply-To: <E1OKSIE-000GYr-C6@dilbert.ticketswitch.com> References: <f6adbf13f35a421249d4122bca6aa3df.dnswclient@www.dnswatch.com> <E1OKSIE-000GYr-C6@dilbert.ticketswitch.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Jun 4, 2010 at 1:30 AM, Pete French <petefrench@ticketswitch.com> wrote: >> I'm /really/ just trying to convert all my i386 boxen to amd64. > > ....this is the source of your problem. What you were trying to > do in builing amd64 is correct, but only if you are already > on an amd64 platform. Those instrcutions are for building the > native architecture. > > If you want to convert an existing system 'in-lace' from i386 > to amd64, then you need to get an install of amd64 on some portable > drive that you can boot from, boot the machine on that, mount the > original drive under '/mnt' or somewhere, and then do an 'installkernel' > and 'installworld' specifying the mountpoint as the destination. That seems to be overcomplicating things a bit, but yes.. the general strategy would be something along those lines. > It does work - but I would do it with a GENERIC kernel first before trying > a custom kernel. Oh, and also you should delete all your ports beforehand > and then rebuild them afterwards so they get rebuilt for amd64. Yeah, that needs to be done. > I would not recommend the above though. You are better off doing > an amd64 install froms cratch. Much less error prone. Wholeheartedly agree. -Garrett
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTil-dacOqcL9ddAdAWjoZOmTDWLrmIvm4p3yAqij>