From owner-freebsd-current Thu Oct 26 21: 4:55 2000 Delivered-To: freebsd-current@freebsd.org Received: from winston.osd.bsdi.com (winston.osd.bsdi.com [204.216.27.229]) by hub.freebsd.org (Postfix) with ESMTP id 1504137B479 for ; Thu, 26 Oct 2000 21:04:54 -0700 (PDT) Received: from winston.osd.bsdi.com (jkh@localhost [127.0.0.1]) by winston.osd.bsdi.com (8.11.1/8.9.3) with ESMTP id e9R44j452803 for ; Thu, 26 Oct 2000 21:04:46 -0700 (PDT) (envelope-from jkh@winston.osd.bsdi.com) To: current@freebsd.org Subject: AMD broken in -current? Date: Thu, 26 Oct 2000 21:04:45 -0700 Message-ID: <52799.972619485@winston.osd.bsdi.com> From: Jordan Hubbard Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It use to work in early October, but now I get the following using the stock (/etc/defaults/rc.conf) amd flags: amd[321]: /host: mount: Operation not supported by device amd[322]: /net: mount: Operation not supported by device amd[321]: /host: mount: No such file or directory amd[322]: /net: mount: No such file or directory amd[321]: extra mkdirs required for /host amd[321]: mount_amfs_toplvl: Operation not supported by device amd[322]: extra mkdirs required for /net amd[322]: mount_amfs_toplvl: Operation not supported by device amd[320]: /host: mount (amfs_auto_cont): Operation not supported by device amd[320]: /net: mount (amfs_auto_cont): Operation not supported by device After which amd continues to run but is essentially useless since it has no hooks into the filesystem. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message