Re: switch from i386 to AMD64 without a total rebuild?

Starting from scratch made the most sense. After all, I am working in a
virtual environment so no hardware to fool around with, I pulled a list of
installed packages and fed that to a loop on the new system after editing a
few things (php80 -> php81) and that went well. Just to be clear after
reading these replies and hier(7), I should be able to move /usr/local/etc
/usr/local/share across as platform-independent hierarchies? The advice to
dump and restore databases is sound, as well: I would have simply copied
/var/db/mysql /eyeroll

I don't think I understand pkg leaf. And to be fair, I am reluctant to
remove stuff if I don't know what it's doing/why it was installed. Ideally
build dependencies that are not needed at runtime are cleaned up but I bet
there is some cruft, given the very different totals given below.

pkg leaf | wc -l
     184
pkg info | wc -l
     531

Disk space is not an issue, a 64Gb disk image is more than adequate here.



On Mon, Sep 18, 2023 at 1:26 AM Dan Mahoney <danm@prime.gushi.org> wrote:

>
>
> > On Sep 16, 2023, at 7:38 PM, paul beard <paulbeard@gmail.com> wrote:
> >
> > Some of the applications on my system are griping about a lack of 64 bit
> support so I am looking into a switch. I am running it as a virtualbox
> guest OS so cloning the existing disk was my first step. Can I somehow put
> AMD64 on the clone? Or do I have to start from scratch and then add all the
> packages and configs, etc?
>
> Most of the files in /etc and /usr/local/etc will port easily to the new
> system.  I would simply run “pkg leaf” and use that to determine the list
> of what you need to install on the new system.
>
> If you’re running some kind of databases (SQL, bdb, etc), I would look
> into how to dump and restore those on the new system, just as a means of
> caution.
>
> -Dan



-- 
Paul Beard / www.paulbeard.org/