From owner-freebsd-amd64@FreeBSD.ORG  Sat Jan  3 02:20:10 2004
Return-Path: <owner-freebsd-amd64@FreeBSD.ORG>
Delivered-To: freebsd-amd64@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id CC98A16A4CE
	for <freebsd-amd64@freebsd.org>; Sat,  3 Jan 2004 02:20:10 -0800 (PST)
Received: from bigtex.jrv.org (rrcs-sw-24-73-246-106.biz.rr.com
	[24.73.246.106])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 9483443D53
	for <freebsd-amd64@freebsd.org>;
	Sat,  3 Jan 2004 02:20:09 -0800 (PST)
	(envelope-from james@bigtex.jrv.org)
Received: from bigtex.jrv.org (localhost [127.0.0.1])
	by bigtex.jrv.org (8.12.1/8.12.1) with ESMTP id i03AK8o8060723
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO)
	for <freebsd-amd64@freebsd.org>; Sat, 3 Jan 2004 04:20:08 -0600 (CST)
Received: (from james@localhost)
	by bigtex.jrv.org (8.12.1/8.12.1/Submit) id i03AK8NC060720;
	Sat, 3 Jan 2004 04:20:08 -0600 (CST)
Date: Sat, 3 Jan 2004 04:20:08 -0600 (CST)
Message-Id: <200401031020.i03AK8NC060720@bigtex.jrv.org>
From: James Van Artsdalen <james-freebsd-amd64@jrv.org>
To: freebsd-amd64@freebsd.org
Subject: SMBFS?
X-BeenThere: freebsd-amd64@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Porting FreeBSD to the AMD64 platform <freebsd-amd64.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-amd64>,
	<mailto:freebsd-amd64-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-amd64>
List-Post: <mailto:freebsd-amd64@freebsd.org>
List-Help: <mailto:freebsd-amd64-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-amd64>,
	<mailto:freebsd-amd64-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 03 Jan 2004 10:20:10 -0000

Is anyone trying to use SMBFS on x86_64?  I'm getting an error I don't
get on the i386 boxes:

smbfs: can't get server address: nberr = no interface to broadcast on and no NBNS server specified

I'm beginning to wonder if there might be a bug instead of just an
incorrect config file.  I added these lines to try to build the right
things into the kernel:

options         NETSMB                  #SMB/CIFS requester
#options         NETSMBCRYPTO            #encrypted password support for SMB
options         LIBMCHAIN               #mchain library.
options         SMBFS                   #SMB/CIFS filesystem
options         LIBICONV