From owner-freebsd-current@FreeBSD.ORG Tue Jul 1 17:39:38 2014 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E6769C48 for ; Tue, 1 Jul 2014 17:39:38 +0000 (UTC) Received: from wonkity.com (wonkity.com [67.158.26.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "wonkity.com", Issuer "wonkity.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 8F3BE2ADA for ; Tue, 1 Jul 2014 17:39:38 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.9/8.14.9) with ESMTP id s61HdZkD079722 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 1 Jul 2014 11:39:36 -0600 (MDT) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.9/8.14.9/Submit) with ESMTP id s61HdZLS079719; Tue, 1 Jul 2014 11:39:35 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Tue, 1 Jul 2014 11:39:35 -0600 (MDT) From: Warren Block To: dt71@gmx.com Subject: Re: freebsd and utf-8 directory names In-Reply-To: <53B2E78B.9030408@gmx.com> Message-ID: References: <3B0F582294DE3E448963BA62DC306AEE3C7F5FBCEC@exchange.mands.hu> <53B2C8B4.50306@gmx.com> <20140701153053.GA69689@troutmask.apl.washington.edu> <53B2D574.80408@gmx.com> <20140701163400.GA70109@troutmask.apl.washington.edu> <53B2E78B.9030408@gmx.com> User-Agent: Alpine 2.11 (BSF 23 2013-08-11) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (wonkity.com [127.0.0.1]); Tue, 01 Jul 2014 11:39:36 -0600 (MDT) Cc: freebsd-current@freebsd.org, Steve Kargl X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Jul 2014 17:39:39 -0000 On Tue, 1 Jul 2014, dt71@gmx.com wrote: > In other words, "You, the general user, should learn the art of operating > system development (on your own) for the sole purpose of being able to fix > the bug yourself." It's one approach to solving a technical problem, but not the only one. You can fix it yourself, possibly involving a lot of learning. Or you can ask, encourage, or even pay others to fix it. This should all start with a bug report to make sure the problem is documented. If people already know there are bugs in the msdosfs code, those same people should be able to supply details to fill out the bug report.