From owner-freebsd-current@freebsd.org Fri May 13 10:45:20 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9A906B39559; Fri, 13 May 2016 10:45:20 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "vps1.elischer.org", Issuer "CA Cert Signing Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 6FE841939; Fri, 13 May 2016 10:45:20 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from Julian-MBP3.local (ppp121-45-225-151.lns20.per1.internode.on.net [121.45.225.151]) (authenticated bits=0) by vps1.elischer.org (8.15.2/8.15.2) with ESMTPSA id u4DAjDq9042322 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Fri, 13 May 2016 03:45:17 -0700 (PDT) (envelope-from julian@freebsd.org) To: freebsd-current , freebsd-doc@freebsd.org From: Julian Elischer Subject: documentation looking for a home. (kernel modules and Vimage) Message-ID: <880bb605-00f7-2e13-36c9-306a85345dec@freebsd.org> Date: Fri, 13 May 2016 18:45:07 +0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.0 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.22 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: Fri, 13 May 2016 10:45:20 -0000 Sorry for double posting.. this email addresses two separate groups of people. Some time ago I wrote the following. http://p4web.freebsd.org/@md=d&cd=//depot/projects/vimage/&cdf=//depot/projects/vimage/porting_to_vimage.txt&c=s0G@//depot/projects/vimage/porting_to_vimage.txt?ac=64&rev1=18 It really should get split into bits and put into the handbook or something.. It includes a section that is all about the module load inits that is not specific to vimage, and there is also a good description of vimage in the that the handbook could use somewhere, maybe in the developer's hand book. Firstly are there any doc people that can take a look at it and see if it would fit in somewhere? (Do we have an editor in chief?) and also maybe some kernel people who can go over the part that describes how modules are loaded and check that it is still up to date.. I last changed it in 2010 so it could be in need of updating. If you know about kerle module loading please take a look and see if anything stands out to you.. It is in the second half of the doc. Also anyone lookign at vimage might find it worth a look. Julian