Date: Wed, 20 Sep 2023 07:25:15 -0700 From: paul beard <paulbeard@gmail.com> Cc: FreeBSD-questions <freebsd-questions@freebsd.org> Subject: Re: switch from i386 to AMD64 without a total rebuild? Message-ID: <CAMtcK2ruo1mOEngv74qYKqiKxfv2FOcQChiywu3TigM9kAL%2BTQ@mail.gmail.com> In-Reply-To: <B0C044FE-B2CC-479A-8D4B-6F82DBEBE4F8@prime.gushi.org> References: <CAMtcK2o82mGRftTS%2BaKHq8U49ARFFz%2BfDrrfXk8ciMzB1PUqxw@mail.gmail.com> <B0C044FE-B2CC-479A-8D4B-6F82DBEBE4F8@prime.gushi.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--000000000000972fee0605cb2568
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
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=E2=80=AFAM 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 bi=
t
> 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 pu=
t
> AMD64 on the clone? Or do I have to start from scratch and then add all t=
he
> 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 =E2=80=9Cpkg leaf=E2=80=9D and use that to de=
termine the list
> of what you need to install on the new system.
>
> If you=E2=80=99re 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
--=20
Paul Beard / www.paulbeard.org/
--000000000000972fee0605cb2568
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">Starting from scratch made the most sense. After all, I am=
working in a virtual environment so no hardware to fool around with, I pul=
led a list of installed packages and fed that to a loop on the new system a=
fter editing a few things (php80 -> php81) and that went well. Just to b=
e 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 si=
mply copied /var/db/mysql /eyeroll=C2=A0<div><br></div><div>I don't thi=
nk 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 d=
ependencies that are not needed at runtime are cleaned up but I bet there i=
s some cruft, given the very different totals given below.=C2=A0</div><div>=
<br></div>pkg leaf | wc -l<span class=3D"gmail-Apple-converted-space">=C2=
=A0</span><br>=C2=A0 =C2=A0 =C2=A0184<br>pkg info | wc -l<span class=3D"gma=
il-Apple-converted-space">=C2=A0</span><br><div>=C2=A0 =C2=A0 =C2=A0531</di=
v><div><br></div><div>Disk space is not an issue, a 64Gb disk image is more=
than adequate here.=C2=A0</div><div><br></div><div><br></div></div><br><di=
v class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Mon, Sep 1=
8, 2023 at 1:26=E2=80=AFAM Dan Mahoney <<a href=3D"mailto:danm@prime.gus=
hi.org">danm@prime.gushi.org</a>> wrote:<br></div><blockquote class=3D"g=
mail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-=
left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex"><br>
<br>
> On Sep 16, 2023, at 7:38 PM, paul beard <<a href=3D"mailto:paulbear=
d@gmail.com" target=3D"_blank">paulbeard@gmail.com</a>> wrote:<br>
> <br>
> Some of the applications on my system are griping about a lack of 64 b=
it support so I am looking into a switch. I am running it as a virtualbox g=
uest OS so cloning the existing disk was my first step. Can I somehow put A=
MD64 on the clone? Or do I have to start from scratch and then add all the =
packages and configs, etc? <br>
<br>
Most of the files in /etc and /usr/local/etc will port easily to the new sy=
stem.=C2=A0 I would simply run =E2=80=9Cpkg leaf=E2=80=9D and use that to d=
etermine the list of what you need to install on the new system.<br>
<br>
If you=E2=80=99re running some kind of databases (SQL, bdb, etc), I would l=
ook into how to dump and restore those on the new system, just as a means o=
f caution.<br>
<br>
-Dan</blockquote></div><br clear=3D"all"><div><br></div><span class=3D"gmai=
l_signature_prefix">-- </span><br><div dir=3D"ltr" class=3D"gmail_signature=
">Paul Beard / <a href=3D"http://www.paulbeard.org/" target=3D"_blank">www.=
paulbeard.org/</a><br></div>
--000000000000972fee0605cb2568--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAMtcK2ruo1mOEngv74qYKqiKxfv2FOcQChiywu3TigM9kAL%2BTQ>