From owner-freebsd-doc@FreeBSD.ORG Thu Jun 2 07:15:37 2005 Return-Path: X-Original-To: doc@freebsd.org Delivered-To: freebsd-doc@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 597E416A41C for ; Thu, 2 Jun 2005 07:15:37 +0000 (GMT) (envelope-from marm.mm@t-online.de) Received: from mailout05.sul.t-online.com (mailout05.sul.t-online.com [194.25.134.82]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0B02A43D1D for ; Thu, 2 Jun 2005 07:15:37 +0000 (GMT) (envelope-from marm.mm@t-online.de) Received: from fwd33.aul.t-online.de by mailout05.sul.t-online.com with smtp id 1DdjvT-0003dF-00; Thu, 02 Jun 2005 09:15:35 +0200 Received: from localhost (Vr4v9BZd8eArLmBkY4dgO1ZYiHrYEpgV6ehw3BW6kU4NNJDb7hp3EF@[172.20.101.250]) by fwd33.aul.t-online.de with esmtp id 1DdjvJ-0zSyo40; Thu, 2 Jun 2005 09:15:25 +0200 MIME-Version: 1.0 Date: Thu, 2 Jun 2005 09:15:25 +0200 To: doc@freebsd.org X-UMS: email X-Mailer: TOI Kommunikationscenter V5-1 From: "marm.mm@t-online.de" Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit Message-ID: <1DdjvJ-0zSyo40@fwd33.aul.t-online.de> X-ID: Vr4v9BZd8eArLmBkY4dgO1ZYiHrYEpgV6ehw3BW6kU4NNJDb7hp3EF@t-dialin.net X-TOI-MSGID: 5eb6372b-08ad-448b-bd4e-255cf35ff2ad Cc: Subject: functions reference X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Jun 2005 07:15:37 -0000 Hello doc-team, There are many functions, structs, headers, unions, enums and so on in the freebsd source, does it make sense to distribute a referenve to those functions ? This way freebsd could get more stable and people who want to contr., have a reference to seach for problems in the exisiting system, writing new programs, drivers, modules. The code will get stable and faster. Of course there are manual pages, info, html pages, but writing sections for the problems is better (Yes, manual pages are splitted), because you have all the things on 1 place. For example writing drivers for a network card, requires knowlegde about several things, so creating a section for writing modules and pack all the things which are associated within this sections. Is there a page for such things, please write back, or is this ideas or me just silly, please write too. _________________________________________ martin moeller, marm.mm@t-online.de