An ansible deployment would do the trick if the initial deployment would have be made uppon it ;)
Sorry for the chicken and egg...
But might be some well spent time if you move it from time to time...
Good luck :)
De : owner-misc@openbsd.org <owner-misc@openbsd.org> de la part de Stuart Henderson <stu.lists@spacehopper.org>
Envoyé : vendredi, février 27, 2026 5:06:39 PM
À : misc@openbsd.org <misc@openbsd.org>
Objet : Re: Port a machine from arm64 to amd64
Envoyé : vendredi, février 27, 2026 5:06:39 PM
À : misc@openbsd.org <misc@openbsd.org>
Objet : Re: Port a machine from arm64 to amd64
On 2026-02-27, Heinrich Rebehn <Heinrich.Rebehn@rebehn.net> wrote:
> Thank you very much for all your replies!
>
> I never took a look at sysmerge. I never used it before, because when upgrading to a new OpenBSD version I always took the path that Peter suggested.
> This time however, because im am only switching architectures and not versions, I figured there should be an easier way. I had hoped for a tool that would simply replace all arm64 binaries with the corresponding amd64 ones.
> Nevertheless, sysmerge looks quite promising, at least by identifying the files that I will have to take care of.
>>> I have a mailserver that runs OpenBSD 7.8 arm64. I want to transfer this installation to a amd64 machine. Do you know of an easy way other than manually copying the config files to a blank amd64 installation?
>>> Maybe automatically select all architecture-independent files and use them to overwrite the corresponding files on the amd machine?
Depends on the way you configure things, but on my mailservers, there
are a bunch of config files other than the ones which are @sample'd in
the packages, so the sysmerge commands are of limited use.
Typically when I've done this, I install the same set of packages,
then scp /etc from the origin machine to /tmp/etc, and go through
manually with diff and decide whether to copy or manually merge the
various files. Same as if I am building on a new machine without
changing arch.
One thing to be aware of is that binary data files may have a
different format depending on the arch. Less likely to be a problem
with amd64 / aarch64, but that's definitely happened with i386 / amd64.
--
Please keep replies on the mailing list.
> Thank you very much for all your replies!
>
> I never took a look at sysmerge. I never used it before, because when upgrading to a new OpenBSD version I always took the path that Peter suggested.
> This time however, because im am only switching architectures and not versions, I figured there should be an easier way. I had hoped for a tool that would simply replace all arm64 binaries with the corresponding amd64 ones.
> Nevertheless, sysmerge looks quite promising, at least by identifying the files that I will have to take care of.
>>> I have a mailserver that runs OpenBSD 7.8 arm64. I want to transfer this installation to a amd64 machine. Do you know of an easy way other than manually copying the config files to a blank amd64 installation?
>>> Maybe automatically select all architecture-independent files and use them to overwrite the corresponding files on the amd machine?
Depends on the way you configure things, but on my mailservers, there
are a bunch of config files other than the ones which are @sample'd in
the packages, so the sysmerge commands are of limited use.
Typically when I've done this, I install the same set of packages,
then scp /etc from the origin machine to /tmp/etc, and go through
manually with diff and decide whether to copy or manually merge the
various files. Same as if I am building on a new machine without
changing arch.
One thing to be aware of is that binary data files may have a
different format depending on the arch. Less likely to be a problem
with amd64 / aarch64, but that's definitely happened with i386 / amd64.
--
Please keep replies on the mailing list.
No comments:
Post a Comment