Bug 26881 - ncr(4) makes no mention of sym(4) or relative virtues
Summary: ncr(4) makes no mention of sym(4) or relative virtues
Status: Closed FIXED
Alias: None
Product: Documentation
Classification: Unclassified
Component: Books & Articles (show other bugs)
Version: Latest
Hardware: Any Any
: Normal Affects Only Me
Assignee: dd
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-04-26 18:20 UTC by Bob Van Valzah
Modified: 2001-05-16 02:59 UTC (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Bob Van Valzah 2001-04-26 18:20:01 UTC 
	The ncr(4) and sym(4) drivers both seem to cover the same
	chip sets.  That begs the question of which driver should be
	used when.  The sym(4) manpage at least mentions ncr(4) but
	never gives any reason why you'd want to use one over the other.
	The ncr(4) manpage doesn't even mention sym(4).

Fix: 

From what I've been able to gleen from the history of these
	drivers, the sym(4) driver is more modern and general
	than ncr(4).  If so, there should be a note to this effect on
	ncr(4).  At the very least, ncr(4) should have a see also
	pointing to sym(4).

	It'd be nice if both pages contained complimentary rationalles
	for choosing one over the other.
How-To-Repeat: 
	man 4 ncr
Comment 1 dd freebsd_committer freebsd_triage 2001-04-29 04:48:40 UTC 
State Changed
From-To: open->analyzed

xref added; rationale which edges on personal bias doesn't really belong in 
man pages, however.
Comment 2 dd freebsd_committer freebsd_triage 2001-04-29 04:48:40 UTC 
Responsible Changed
From-To: freebsd-doc->dd

My MFC reminder.
Comment 3 dd freebsd_committer freebsd_triage 2001-05-16 02:59:36 UTC 
State Changed
From-To: analyzed->closed

MFC'd