From owner-freebsd-stable Sun Feb 10 13:19:52 2002 Delivered-To: freebsd-stable@freebsd.org Received: from sm10.texas.rr.com (sm10.texas.rr.com [24.93.35.222]) by hub.freebsd.org (Postfix) with ESMTP id 267DD37BDDA for ; Sun, 10 Feb 2002 13:17:23 -0800 (PST) Received: from houston.rr.com (cs242233-40.houston.rr.com [24.242.233.40]) by sm10.texas.rr.com (8.12.0.Beta16/8.12.0.Beta16) with ESMTP id g1ALHHlQ028405 for ; Sun, 10 Feb 2002 15:17:18 -0600 Message-ID: <3C66E35E.14617528@houston.rr.com> Date: Sun, 10 Feb 2002 15:17:18 -0600 From: Matt Bettinger X-Mailer: Mozilla 4.79 [en] (X11; U; Linux 2.4.2 i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-stable@FreeBSD.ORG Subject: mount_smbfs + 4.5-STABLE References: <000501c1b09c$89100600$8fd5e0d5@pandora.be> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello, mount_smbfs is broken after I cvsupped to 4.5-RC from 4.4 stable. I recvsupped to 4.5 STABLE last night and still no luck. The error ... Celeste# mount_smbfs //nobody@dani/dani /dani mount_smbfs: vfsload(smbfs): File Exists Celeste# --------------------------------------------------------------------- A kldstat shows the following... Id Refs Address Size Name 1 5 0xc0100000 276ed0 kernel 2 1 0xc2536000 14000 linux.ko 4 2 0xc262d000 3000 libiconv.ko 5 1 0xc2612000 1a000 smbfs.ko 6 1 0xc2632000 3000 libmchain.ko ---------------------------------------------------------------------- My kernel configuration file has these in it... options NETSMB options NETSMBCRYPTO options LIBMCHAIN options LIBICONV I recently built the Samba port and that is when i noticed this mount_smbfs wasn't working but I am not sure if it was samba that did it or if it was the build to 4.5. Does anyone have any ideas? Thanks, Matthew Bettinger To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message