git: 0a3792d5c576 - main - release: No newaliases when cross-building VMs
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Thu, 31 Jul 2025 17:47:49 UTC
The branch main has been updated by cperciva:
URL: https://cgit.FreeBSD.org/src/commit/?id=0a3792d5c5764945259333db4c66774385f01ba7
commit 0a3792d5c5764945259333db4c66774385f01ba7
Author: Colin Percival <cperciva@FreeBSD.org>
AuthorDate: 2025-07-31 17:44:15 +0000
Commit: Colin Percival <cperciva@FreeBSD.org>
CommitDate: 2025-07-31 17:47:36 +0000
release: No newaliases when cross-building VMs
We've been running newaliases(8) when cross-building VMs for a long
time, and it's not entirely clear why -- especially since we don't
do it when we're building a native VM image.
If someone knows why running newaliases is important we can add it
back later, but only after newaliases gets unbroken: As of last week
(a3d4ae7cf351) newaliases fails with EPERM on /etc/dma/dma.conf.
This should unbreak VM (and cloudware) cross-builds.
With hat: re@
---
release/tools/vmimage.subr | 1 -
1 file changed, 1 deletion(-)
diff --git a/release/tools/vmimage.subr b/release/tools/vmimage.subr
index eb816018e9d3..156987e33457 100644
--- a/release/tools/vmimage.subr
+++ b/release/tools/vmimage.subr
@@ -118,7 +118,6 @@ vm_emulation_setup() {
mkdir -p ${DESTDIR}/dev
mount -t devfs devfs ${DESTDIR}/dev
- chroot ${DESTDIR} ${EMULATOR} /usr/bin/newaliases
chroot ${DESTDIR} ${EMULATOR} /bin/sh /etc/rc.d/ldconfig forcestart
cp /etc/resolv.conf ${DESTDIR}/etc/resolv.conf