From owner-freebsd-hackers Thu Sep 11 17:11:37 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA10827 for hackers-outgoing; Thu, 11 Sep 1997 17:11:37 -0700 (PDT) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA10822 for ; Thu, 11 Sep 1997 17:11:35 -0700 (PDT) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id RAA09162 for ; Thu, 11 Sep 1997 17:02:14 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd009159; Fri Sep 12 00:02:09 1997 Message-ID: <34188660.1CFBAE39@whistle.com> Date: Thu, 11 Sep 1997 17:01:36 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: hackers@freebsd.org Subject: AMD broken in 2.2.2? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk If I just turn on amd in rc.conf and use the standard settings, I get the following: # ls /host/phaser3/data # tail /var/log/messages [old stuff] Sep 11 16:54:40 phaser3 amd.hold[4252]: NIS domain name is not set. NIS ignored Sep 11 16:55:36 phaser3 amd.hold[4550]: /net/phaser3/data: mount: Bad address # mount /dev/wd0a on / (local) /dev/wd1s1e on /data (NFS exported, local) /dev/wd0s1f on /usr (local) /dev/wd0s1e on /var (local) procfs on /proc (local) amd:4252 on /host # kill 4252 # amd.2.2.0 -npr -a /net -c 1800 -k i386 -d whistle.com -l syslog -x all /host /etc/amd.map # mount /dev/wd0a on / (local) /dev/wd1s1e on /data (NFS exported, local) /dev/wd0s1f on /usr (local) /dev/wd0s1e on /var (local) procfs on /proc (local) amd:5191 on /host # !ls ls /host/phaser3/data CVSROOT freebsd oldmod build_envs mod prod # tail /var/log/messages [old stuff] Sep 11 16:59:44 phaser3 amd.2.2.0[5191]: NIS domain name is not set. NIS ignored. in other words, teh binary from a 2.2-current (kinda unknown vintage) works fine, but the binary from 2.2.2 fails miserably. I've looked through the mailing lists etc, but I don't see why the default setting in /etc/rc.conf should fail anyone have any thoughts? was there some security feature added that wasn't documented? the "Bad address" is a rather useless error message. julian