From owner-freebsd-arch@FreeBSD.ORG Tue Jan 7 14:57:25 2014 Return-Path: Delivered-To: freebsd-arch@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 0BF629FC for ; Tue, 7 Jan 2014 14:57:25 +0000 (UTC) Received: from mail-qa0-x232.google.com (mail-qa0-x232.google.com [IPv6:2607:f8b0:400d:c00::232]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id C01CD1F0D for ; Tue, 7 Jan 2014 14:57:24 +0000 (UTC) Received: by mail-qa0-f50.google.com with SMTP id k4so613720qaq.23 for ; Tue, 07 Jan 2014 06:57:23 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=GYOKsb20luxCvG7L0+h3/Lm3Xb9lxWJvDXIxF/yN2pM=; b=mUwNTBeClkLy+XlSJQS8IP92XT8miFyUpLHX7Fc/PhFO9vUgfoFGBtwRyALz/Yhcjo Rd8Wa2AM9Klc/EKlUrdRhr6QATWwhrcQd5iAGm6fv64KR3WIWMd/rmP/Ze+0eeaoh3sK cB62YNC/njhpbaVn6yGbt98FUIU9/uZsPOj1pYwFdmzEaSbBSr6teDuVzBvTi9tysoHN vu880X6fis1VXAIGt5DEiUvd1U8NmEYuvS7sY8Fhv2mlpdqQTjqG1o1Mp5LHXdPjbaBF VW3Lmll52gnuaQExrxshGW021xsVKAm0NHuWpXpO9mdGjSSltdBTFn83t/zTXDwgCbZM vx8w== MIME-Version: 1.0 X-Received: by 10.224.121.193 with SMTP id i1mr94564910qar.28.1389106643871; Tue, 07 Jan 2014 06:57:23 -0800 (PST) Sender: carpeddiem@gmail.com Received: by 10.224.134.196 with HTTP; Tue, 7 Jan 2014 06:57:23 -0800 (PST) In-Reply-To: <52C02E6C.2080704@bitfrost.no> References: <52C02E6C.2080704@bitfrost.no> Date: Tue, 7 Jan 2014 09:57:23 -0500 X-Google-Sender-Auth: qfJN20G70jcWuWJiImzi_1odxA8 Message-ID: Subject: Re: [RFC] Should CUSE4BSD move to the FreeBSD source tree? From: Ed Maste To: Hans Petter Selasky Content-Type: text/plain; charset=ISO-8859-1 Cc: "freebsd-arch@freebsd.org" X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Jan 2014 14:57:25 -0000 On 29 December 2013 09:15, Hans Petter Selasky wrote: > Hi, > > The CUSE4BSD, character device in userspace, library and kernel module, has > become an extremely popular driver choice for supporting a whole lot of USB > devices under FreeBSD. In my opinion it's a similar case to fuse, which moved from ports to src in 2012. If a kernel module is going to be kept up to date and doesn't have to be a port (e.g. for license reasons) I think it ought to go in src/sys. > Of course this puts more > restrictions on the API, and CUSE4BSD sometime has API additions. Also that > might mean that CUSE4BSD will go through some API changes, as input from > other FreeBSD developers. One change might be to change lengths from "int" > to "ssize_t" although, it is very unlikely to read more than a few megabytes > at a time from a character device. Well, hopefully that can be resolved before an import, but certainly before being enabled by default and considered a standard feature. In any case as additional consumers start to depend on it API changes will be an issue regardless of where it's located. How does the API compare to Linux cuse? > Some other questions are: Where should CUSE4BSD reside in svn? Should it > have it's own vendor branch or simply just @ head + MFC to xxx-stable? I suspect the effort of a vendor branch and sys/contrib/ magic doesn't make sense, unless you expect you'd continue maintaining an upstream repository with significant non-FreeBSD development. -Ed