From owner-freebsd-amd64@FreeBSD.ORG  Mon Jan  5 01:25:56 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 7E09716A4CE; Mon,  5 Jan 2004 01:25:56 -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 18DE343D2F; Mon,  5 Jan 2004 01:25:55 -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 i059Pso8089960
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Mon, 5 Jan 2004 03:25:54 -0600 (CST)
Received: (from james@localhost)
	by bigtex.jrv.org (8.12.1/8.12.1/Submit) id i059PsVY089957;
	Mon, 5 Jan 2004 03:25:54 -0600 (CST)
Date: Mon, 5 Jan 2004 03:25:54 -0600 (CST)
Message-Id: <200401050925.i059PsVY089957@bigtex.jrv.org>
From: James Van Artsdalen <james-freebsd-amd64@jrv.org>
To: freebsd-amd64@FreeBSD.ORG
In-reply-to: <20040105064415.GA49437@hub.freebsd.org> (obrien@FreeBSD.ORG)
References: <200401040714.i047EDbt019471@bigtex.jrv.org>
	<20040105064415.GA49437@hub.freebsd.org>
cc: tjr@FreeBSD.ORG
Subject: Re: 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: Mon, 05 Jan 2004 09:25:56 -0000

I am able to mount a filesystem with SMBFS with the patch given.

I also had to make this change so that the kernel would compile
with the necessary crypto routines.

--- sys/conf/files.amd64.~1~    Mon Nov 17 02:58:16 2003
+++ sys/conf/files.amd64        Mon Jan  5 01:54:19 2004
@@ -123,3 +123,8 @@
 compat/ia32/ia32_sigtramp.S    optional        ia32
 compat/ia32/ia32_sysvec.c      optional        ia32
 kern/imgact_elf32.c            optional        ia32
+#
+crypto/des/des_ecb.c                   optional        netsmbcrypto
+crypto/des/des_enc.c                   optional        netsmbcrypto
+crypto/des/des_setkey.c                        optional        netsmbcrypto
+crypto/blowfish/bf_enc.c               optional        crypto

One of these has an x86 assembly equivalent; I don't know if using
the C version will hurt IPsec badly.  The x86 assembly was generated
by a perl script which can probably be fixed by a perl script to
generate x86-64 code fairly easily if any perl coders want to do it.

> Date: Sun, 4 Jan 2004 22:44:15 -0800
> From: "David O'Brien" <obrien@FreeBSD.ORG>

> Tim Robbins <tjr@freebsd.org>'s done some SMBFS work lately.  He'd like
> it if AMD64 users experiencing this could try:
> 
> http://cvsweb.netbsd.org/bsdweb.cgi/src/dist/smbfs/lib/smb/nb_net.c.diff?r1=1.1&r2=1.2
> 
> and let him know whether he should bring it across to FreeBSD.
> 
> -- David
>