NetBSD Problem Report #3977

Received: (qmail 29766 invoked from network); 13 Aug 1997 01:31:37 -0000
Message-Id: <199708130131.SAA10746@atomic.clock.org>
Date: Tue, 12 Aug 1997 18:31:35 -0700 (PDT)
From: "Erik E. Fair" <fair@atomic.clock.org>
Reply-To: fair@atomic.clock.org
To: gnats-bugs@gnats.netbsd.org
Subject: intro(4) missing for NetBSD/alpha
X-Send-Pr-Version: 3.95

>Number:         3977
>Category:       port-alpha
>Synopsis:       intro(4) missing in NetBSD/alpha
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    gmcgarry
>State:          closed
>Class:          doc-bug
>Submitter-Id:   net
>Arrival-Date:   Tue Aug 12 18:35:06 +0000 1997
>Closed-Date:    Sun Feb 10 01:31:17 +0000 2002
>Last-Modified:  Sun Feb 10 01:31:17 +0000 2002
>Originator:     Erik E. Fair
>Release:        NetBSD-current of August 12, 1997
>Organization:
International Organization of Internet Clock Watchers
>Environment:

	NetBSD/alpha

>Description:
	The intro(4) page which describes what device drivers are
	available for NetBSD/alpha is missing.

	In addition, it might be nice for the intro(4) page to
	document which models of alpha NetBSD runs on, as seen in
	the NetBSD/pmax intro(4) man page.

>How-To-Repeat:
	cd /usr/src/share/man4/man4.alpha
	ls intro.4
	note that intro(4) is missing.
>Fix:
	Someone with appropriate understanding of what devices 
	NetBSD/alpha supports should write the intro(4) page.
>Release-Note:
>Audit-Trail:

From: "Chris G. Demetriou" <cgd@pa.dec.com>
To: fair@atomic.clock.org
Cc: gnats-bugs@gnats.netbsd.org, netbsd-bugs@netbsd.org
Subject: Re: port-alpha/3977: intro(4) missing for NetBSD/alpha 
Date: Tue, 12 Aug 97 18:52:31 -0700

 I (and others) have been documenting these things on the web pages.
 See http://www.netbsd.org/Ports/alpha/supported/index.html for more
 information.

 Eventually, someone should turn this into manual pages, yes.

 cgd

From: "Erik E. Fair" (Timekeeper) <fair@clock.org>
To: "Chris G. Demetriou" <cgd@pa.dec.com>
Cc: gnats-bugs@gnats.netbsd.org, netbsd-bugs@NetBSD.ORG
Subject: Re: port-alpha/3977: intro(4) missing for NetBSD/alpha 
Date: Tue, 12 Aug 1997 19:03:35 -0700

 I was poking through doc-bugs, and looking into PR#1586.
 I'm writing one the for sparc (which will close that PR),
 but, as you note, the other ports ought to have one too.

 Ideally, an mdoc to HTML translator ought to be written
 so that the man pages can be on the NetBSD web site;
 then the support pages can point directly to the HTML
 version of the intro(4) for each port...

 	Erik E. Fair	fair@clock.org

From: "Chris G. Demetriou" <cgd@pa.dec.com>
To: "Erik E. Fair" (Timekeeper) <fair@clock.org>
Cc: "Chris G. Demetriou" <cgd@pa.dec.com>, gnats-bugs@gnats.netbsd.org,
        netbsd-bugs@netbsd.org
Subject: Re: port-alpha/3977: intro(4) missing for NetBSD/alpha 
Date: Tue, 12 Aug 97 19:14:45 -0700

 I'd agree, but at least I find HTML much more expressive and much
 easier to use than any kind of roff macros.  8-)


 chris

From: Scott Reynolds <scottr@Plexus.COM>
To: "Erik E. Fair" <fair@clock.org>
Cc: gnats-bugs@gnats.netbsd.org, www@netbsd.org
Subject: Re: port-alpha/3977: intro(4) missing for NetBSD/alpha 
Date: Tue, 19 Aug 1997 12:40:50 -0500 (CDT)

 On Tue, 12 Aug 1997, Erik E. Fair wrote:

 > Ideally, an mdoc to HTML translator ought to be written
 > so that the man pages can be on the NetBSD web site;
 > then the support pages can point directly to the HTML
 > version of the intro(4) for each port...

 There are already quite a number of them written.  I personally like how
 PolyglotMan (formerly RosettaMan) and rman.pl work together, from a user's
 standpoint.  I've never had to set them up, but it doesn't appear to be
 extraordinarily difficult.

 	http://www.cs.berkeley.edu/~phelps/tcltk/index.html
 	http://www.jinr.dubna.su/~gagin/rman.pl.html

 Online web pages would be a big bonus!

 --scott


From: "Erik E. Fair" (Timekeeper) <fair@clock.org>
To: Scott Reynolds <scottr@plexus.com>
Cc: gnats-bugs@gnats.netbsd.org, www@NetBSD.ORG
Subject: Re: port-alpha/3977: intro(4) missing for NetBSD/alpha 
Date: Tue, 19 Aug 1997 10:54:17 -0700

 No, those are not the right thing; look carefully and you'll see
 they work on the *output* from nroff. Wrong. I'm looking for (or
 will write) one that converts the *input* (i.e.  mdoc documents).

 	Erik E. Fair	fair@clock.org

From: "Perry E. Metzger" <perry@piermont.com>
To: "Erik E. Fair" (Timekeeper) <fair@clock.org>
Cc: Scott Reynolds <scottr@plexus.com>, gnats-bugs@gnats.netbsd.org,
        www@netbsd.org
Subject: Re: port-alpha/3977: intro(4) missing for NetBSD/alpha 
Date: Tue, 19 Aug 1997 13:58:37 -0400

 It should be trivial -- mdoc already breaks things down functionally
 instead of by format...

 Of course, perhaps the FreeBSD people already have such a thing --
 they have lots of neat documentation tools these days.

 .pm

From: Scott Reynolds <scottr@Plexus.COM>
To: "Perry E. Metzger" <perry@piermont.com>
Cc: "Erik E. Fair" <fair@clock.org>, gnats-bugs@gnats.netbsd.org,
        www@netbsd.org
Subject: Re: port-alpha/3977: intro(4) missing for NetBSD/alpha 
Date: Tue, 19 Aug 1997 14:23:56 -0500 (CDT)

 Funny that I got Perry's response first. :-)

 I'm reasoning that a good chunk of time is taken to go from mdoc to
 formatted text.  What's the problem with using the nroff-formatted output?
 The chance that it's going to be too aggressive -- or too passive -- about
 finding other pages to link to?  The use of the <pre> tag?  (I seem to
 recall PolyglotMan avoiding this last.)

 Note that the rman.pl script doesn't require a preconverted man page, only
 the nroff-formatted document.

 Would something like this be an acceptable interim solution?

 --scott


From: Michael Graff <explorer@flame.org>
To: Scott Reynolds <scottr@Plexus.COM>
Cc: "Erik E. Fair" <fair@clock.org>, gnats-bugs@gnats.netbsd.org,
  www@netbsd.org
Subject: Re: port-alpha/3977: intro(4) missing for NetBSD/alpha
Date: 20 Aug 1997 13:54:33 -0400

 Scott Reynolds <scottr@Plexus.COM> writes:

 > Online web pages would be a big bonus!

 You mean online man pages?

 Have a quick look at http://www.flame.org/cgi-bin/uncgi/hman and tell me
 what you think.

 I'm using a fairly old version of RosettaMan or whatever is was called,
 but it does pull the info out of the running system on www.flame.org.

 If I were to get lots of hits on those pages, I would set things up to
 build the pages only when needed and cache the ones created...

 --Michael
Responsible-Changed-From-To: gnats-admin->port-alpha-maintainer 
Responsible-Changed-By: fair 
Responsible-Changed-When: Mon Dec 28 09:32:11 PST 1998 
Responsible-Changed-Why:  
This PR is the responsibility of the portmaster, 
not the GNATS database administrator. 
State-Changed-From-To: open->feedback 
State-Changed-By: ross 
State-Changed-When: Tue Dec 4 23:05:45 PST 2001 
State-Changed-Why:  
Gregory McGarry wrote alpha/intro.4 (yay) 
By the way, the man->html tool discussed is in-tree in NetBSD now as 
the mdoc2html macro package. 


Responsible-Changed-From-To: port-alpha-maintainer->gmcgarry 
Responsible-Changed-By: ross 
Responsible-Changed-When: Tue Dec 4 23:05:45 PST 2001 
Responsible-Changed-Why:  
Gregory McGarry wrote alpha/intro.4 (yay)    

From: "Erik E. Fair" <fair@clock.org>
To: Ross Harvey <ross@ghs.com>
Cc: gmcgarry@netbsd.org, port-alpha-maintainer@netbsd.org,
        NetBSD GNATS Problem Report Tracking System <gnats-bugs@gnats.netbsd.org>
Subject: Re: port-alpha/3977
Date: Wed, 12 Dec 2001 00:47:41 -0800

 You guys are gonna think I'm never satisfied. What's there is a good 
 start, but I'd be happier to see something broken down by CPU, e.g.

 21064 (EV?, 50 - 100 MHz)
 	Multia UDB
 	etc.

 21066 (EV?, ? MHz)
 	systems.

 21164 (EV?, 200 - 600 MHz)
 	Personal Workstation
 	EB164 (PC164, PC164LX, PC164SX)
 	AlphaServer 800 (DigitalServer 3300)
 	etc.

 21264 (EV?, ? MHz )
 	APi XP1000
 	etc.

 21364 (does this even exist?)
 	etc.


 Would be a good idea to mention the systems' principal expansion bus 
 (e.g. TURBObus, PCI) and motherboard/system code names, too; the 
 kernel config options for paring down the configuration to just the 
 hardware in a given system are, alas, listed by codename. Those 
 codenames are also used freely by the Alpha developers and DECcies 
 (current and former) on the port-alpha mailing list; for those of us 
 who don't have clue, we need a scorecard so we can tell the players...

 I did this sort of breakdown for the sun3 and sparc intro(4) pages 
 because I know that hardware. I don't know the Alpha hardware, or I'd 
 do it here too.

 	please?

 	Erik <fair@clock.org>

From: "R.o.s.s  H.a.r.v.e.y" <ross@ghs.com>
To: fair@clock.org
Cc: gmcgarry@netbsd.org, gnats-bugs@gnats.netbsd.org,
   port-alpha-maintainer@netbsd.org
Subject: Re: port-alpha/3977
Date: Wed, 12 Dec 2001 09:34:30 -0800 (PST)

 Hmm, I see your point, though I would rather make it through
 the outstanding pr's without getting too bogged down. I guess
 we should leave this one in state==feedback for now.

From: "Erik E. Fair" <fair@clock.org>
To: gnats-bugs@netbsd.org
Cc:  
Subject: Re: port-alpha/3977
Date: Fri, 08 Feb 2002 00:42:17 -0800

 Bingo! http://www.support.compaq.com/alpha-tools/info/system-codes.html

 Now all I need are the CPU clock rate ranges for each CPU.

 I've got something rough written; shall I commit it?

 	Erik <fair@clock.org>


From: Gregory McGarry <g.mcgarry@ieee.org>
To: "Erik E. Fair" <fair@clock.org>
Cc:  
Subject: Re: port-alpha/3977
Date: Sun, 10 Feb 2002 13:06:17 +1300

 Ross put my name down as being responsible for this PR.  I only
 did the pages: I don't even have an alpha!  Feel free to make
 all the changes you please.

 	-- Gregory McGarry <g.mcgarry@ieee.org>

State-Changed-From-To: feedback->closed 
State-Changed-By: fair 
State-Changed-When: Sat Feb 9 17:28:49 PST 2002 
State-Changed-Why:  
After some research, I've committed a CPU and system list which, 
while probably not complete, is a very good start. The later models 
based on the 21264 and the higher-end stuff like the TurboLaser 
should be filled out more, but I think we can finally close this 
PR as resolved, since NetBSD/alpha has an intro(4). 

>Unformatted:

Home	PR Database Search