I have no NFS connectivity between these two machines. The older one is behind several NATs.The best way is not to transfer /usr/obj.
Instead do a `make installworld` with DESTDIR set to a NFS export of the intended target dir.
I have no NFS connectivity between these two machines. The older one is behind several NATs.
So is my idea is realistic? Everything what's needed is in /usr/obj, isn't it? No hardware incomparably should occur, should it? (both are amd64 but from different "ages")
O.K. I 'll try it with DESTDIR. And for kernel it's the same?I think /usr/obj will not install on its own. You have to copy over /usr/src as well.
Alternatively, use the build machine with a "DESTDIR" make installworld to a temp dir, and rsync or tar that over.
You could also set up VPN connections for a NFS mount.
O.K. I 'll try it with DESTDIR. And for kernel it's the same?
Thank you, the solution you proposed worked out. But some files like libelf.so.2 hadI think /usr/obj will not install on its own. You have to copy over /usr/src as well.
Alternatively, use the build machine with a "DESTDIR" make installworld to a temp dir, and rsync or tar that over.
You could also set up VPN connections for a NFS mount.
schg
flag on them, so tar
complained it couldn't copy them over existed ones. Luckily, not many of such minor troubles.Not too helpful for me, almost everything's about NFS installation.I am pretty deep into Chapter 26 now and i suggest you look at 26.7 -Tracking for Multiple Machines. It has many hints.
![]()
Chapter 26. Updating and Upgrading FreeBSD
Information about how to keep a FreeBSD system up-to-date with freebsd-update or Git, how to rebuild and reinstall the entire base system, etcdocs.freebsd.org