From owner-freebsd-arch Fri Sep 1 8:13: 9 2000 Delivered-To: freebsd-arch@freebsd.org Received: from relay.butya.kz (butya-gw.butya.kz [212.154.129.94]) by hub.freebsd.org (Postfix) with ESMTP id 144DE37B423 for ; Fri, 1 Sep 2000 08:13:06 -0700 (PDT) Received: by relay.butya.kz (Postfix, from userid 1000) id 004B128775; Fri, 1 Sep 2000 22:13:02 +0700 (ALMST) Received: from localhost (localhost [127.0.0.1]) by relay.butya.kz (Postfix) with ESMTP id EAE4A28677 for ; Fri, 1 Sep 2000 22:13:02 +0700 (ALMST) Date: Fri, 1 Sep 2000 22:13:02 +0700 (ALMST) From: Boris Popov To: freebsd-arch@freebsd.org Subject: Shared kernel code Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, Currently I'm preparing smbfs bits for import into main tree. Since both nwfs and smbfs contains common parts I've tried to unify them in order to share code. Currently there are two common parts: kernel side of iconv library and encapsulation of mbuf management functions. Both can be statically compiled in the kernel or loaded as KLDs. But there is an interesting question arises - where to put source code for those modules which don't represent any device and may consists from multiple source files ? Historically such files were placed in the kern and libkern directories. But it seems that both aren't suitable for newly added interfaces because of the flat name space. So, my suggestion is to create sys/lib directory which should be organized as src/lib directory. Eg: sys/lib libiconv/ libmbuf/ etc... Basically, sys/libkern also can be moved under lib directory. Comments are welcome. -- Boris Popov http://www.butya.kz/~bp/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message