From owner-freebsd-stable  Thu Jul 18  2:40:23 2002
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id DD4A037B400
	for <freebsd-stable@FreeBSD.ORG>; Thu, 18 Jul 2002 02:40:20 -0700 (PDT)
Received: from mile.nevermind.kiev.ua (office.netstyle.com.ua [213.186.199.26])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 711BD43E3B
	for <freebsd-stable@FreeBSD.ORG>; Thu, 18 Jul 2002 02:40:18 -0700 (PDT)
	(envelope-from never@mile.nevermind.kiev.ua)
Received: from mile.nevermind.kiev.ua (never@localhost [127.0.0.1])
	by mile.nevermind.kiev.ua (8.12.3/8.12.3) with ESMTP id g6I9e8pb049951;
	Thu, 18 Jul 2002 12:40:09 +0300 (EEST)
	(envelope-from never@mile.nevermind.kiev.ua)
Received: (from never@localhost)
	by mile.nevermind.kiev.ua (8.12.3/8.12.3/Submit) id g6I9e5JS049949;
	Thu, 18 Jul 2002 12:40:05 +0300 (EEST)
Date: Thu, 18 Jul 2002 12:40:05 +0300
From: Alexandr Kovalenko <never@nevermind.kiev.ua>
To: tech <tech@ib.com.ua>
Cc: freebsd-stable@FreeBSD.ORG, leafy@leafy.idv.tw
Subject: Re: smbfs + libiconv problems
Message-ID: <20020718094005.GD26608@nevermind.kiev.ua>
References: <20020718092027.GA72170@leafy.idv.tw> <200207180924.g6I9OgrQ074758@ib.com.ua>
Mime-Version: 1.0
Content-Type: text/plain; charset=koi8-r
Content-Disposition: inline
In-Reply-To: <200207180924.g6I9OgrQ074758@ib.com.ua>
User-Agent: Mutt/1.5.1i
Sender: owner-freebsd-stable@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-stable.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-stable>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-stable>
X-Loop: FreeBSD.ORG

Hello, tech!

On Thu, Jul 18, 2002 at 12:24:42PM +0300, you wrote:

> > > 	In freebsd 4.6 stable I successfuly mount shared resources with
> > >  smbfs (as dynamic module or built-in). I successfuly use character sets
> > >  	recoding feature. But every directory
> > >  with russian encoding looks like they are empty (really they are not empty).
> > >  is this a known bug?
> > Did you enable kernel LIBICONV?
> >
> Yes, of course :-)
> 
> options SMBFS
> options NETSMB
> options NETSMBCRYPTO
> options LIBMCHAIN
> options LIBICONV
That's correct.

> and libiconv-1.8 from up-to-date ports
It has NOTHING to do with kernel LIBICONV.

-- 
NEVE-RIPE
Ukrainian FreeBSD User Group
http://uafug.org.ua/

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" in the body of the message