From owner-freebsd-doc Thu Oct 5 22: 4: 6 2000 Delivered-To: freebsd-doc@freebsd.org Received: from pike.osd.bsdi.com (pike.osd.bsdi.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id 3B2A037B66C for ; Thu, 5 Oct 2000 22:04:04 -0700 (PDT) Received: from laptop.baldwin.cx (john@dhcp248.osd.bsdi.com [204.216.28.248]) by pike.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e9653Ji28294; Thu, 5 Oct 2000 22:03:20 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20001003045523.A43923@mppsystems.com> Date: Thu, 05 Oct 2000 22:03:33 -0700 (PDT) From: John Baldwin To: Mike Pritchard Subject: Re: device hints in manpages Cc: doc@FreeBSD.org, Alexander Langer Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 03-Oct-00 Mike Pritchard wrote: > On Sun, Oct 01, 2000 at 03:40:38PM +0200, Alexander Langer wrote: >> Hello! >> >> How are we going to document the hints-stuff in manpages? >> >> We have to replace many lines like this: >> .Cd "device ed1 at isa? port 0x300 irq 5 flags 0x4 iosiz 16384 iomem >> 0xd8000" >> >> to something way more appreciate. >> >> Alex > > I brought this up at the time was made. I can't find any of the > e-mail in my archives on the subject. Searching the mailing list > archives may turn up something. > > I think I proposed something like: > > .Cd "device ed" > .Cd "hints CONFIG.hints" Err, I wouldn't stick this line in the manpages, as the preferred method is to use dynamic hints from /boot/device.hints that are machine-specific, not kernel-specific. :) This would be better documented in the hints(4) manpage as a separate line item about static hints vs. dynamic hints. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message