NetBSD Problem Report #21358

Received: (qmail 3502 invoked by uid 605); 29 Apr 2003 07:43:02 -0000
Message-Id: <200304290742.h3T7gxd20384@digital.clock.org>
Date: Tue, 29 Apr 2003 00:42:59 -0700 (PDT)
From: fair@netbsd.org
Sender: gnats-bugs-owner@netbsd.org
Reply-To: fair@netbsd.org
To: gnats-bugs@gnats.netbsd.org
Subject: this port is missing its boot(8) man page
X-Send-Pr-Version: 3.95

>Number:         21358
>Category:       port-arc
>Synopsis:       this port is missing its boot(8) man page
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    port-arc-maintainer
>State:          closed
>Class:          doc-bug
>Submitter-Id:   net
>Arrival-Date:   Tue Apr 29 07:44:00 +0000 2003
>Closed-Date:    Sat Nov 25 17:45:14 +0000 2006
>Last-Modified:  Sat Nov 25 22:00:01 +0000 2006
>Originator:     Erik E. Fair
>Release:        NetBSD 1.6.1
>Organization:
The NetBSD Project Picayune Nitpickers
>Environment:
>Description:
	The boot(8) man page describes the platform dependent details
	of how to get NetBSD booted on that platform. It should include
	a general description of the system firmware and its operations,
	relevant settings, etc.

>How-To-Repeat:
	cd /usr/src/share/man/man8
	foreach dir ( man8.* )
		if ( ! -e $dir/boot.8 ) echo $dir/boot.8 missing
	end

>Fix:
	The portmaster or his designee should write the appropriate
	text and commit it to our CVS repository.
>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->closed
State-Changed-By: elad@netbsd.org
State-Changed-When: Sat, 25 Nov 2006 17:45:14 +0000
State-Changed-Why:
dup of 35119


From: "Erik E. Fair" <fair@netbsd.org>
To: gnats-bugs@NetBSD.org
Cc: port-arc-maintainer@netbsd.org
Subject: Re: port-arc/21358 (this port is missing its boot(8) man page) 
Date: Sat, 25 Nov 2006 10:55:21 -0800

 Please re-open this PR and all its siblings until each is resolved.

 1. The later problem report which documents a given problem is the
 "duplicate", not the earlier.

 2. The port-specific individual problem reports of this type are
 more appropriate given that it is the responsibility of the portmaster
 to see that the problem is resolved, and the performance (or lack
 thereof) of the individual portmasters can be tracked in this way.

 	Erik <fair@netbsd.org>

From: "Erik E. Fair" <fair@netbsd.org>
To: gnats-bugs@NetBSD.org
Cc: port-arc-maintainer@netbsd.org, netbsd-bugs@netbsd.org
Subject: Re: port-arc/21358 (this port is missing its boot(8) man page) 
Date: Sat, 25 Nov 2006 10:59:07 -0800

 Further, given that each boot(8) page is expected to contain
 information about the platform-specific firmware commands needed
 to boot that system, e.g. alpha/boot.8, it cannot just be "cut &
 paste" from other ports.

 	Erik <fair@netbsd.org>

From: Elad Efrat <elad@NetBSD.org>
To: gnats-bugs@NetBSD.org
Cc: 
Subject: Re: port-arc/21358 (this port is missing its boot(8) man page)
Date: Sat, 25 Nov 2006 23:59:13 +0200

 Erik E. Fair wrote:

 >  Please re-open this PR and all its siblings until each is resolved.
 >  
 >  1. The later problem report which documents a given problem is the
 >  "duplicate", not the earlier.
 >  
 >  2. The port-specific individual problem reports of this type are
 >  more appropriate given that it is the responsibility of the portmaster
 >  to see that the problem is resolved, and the performance (or lack
 >  thereof) of the individual portmasters can be tracked in this way.

 it's the responsibility of the port-master to do a lot of things, some
 of which are more important than writing an md boot(8) man-page, and
 apparently we're having hard time with that too.

 the spam you added to the pr database does not help, and is ignored.

 I have added a more-or-less mi version of boot(8), and later on we will
 think how to strengthen the connection between the port-master and the
 port.

 -e.

 -- 
 Elad Efrat

>Unformatted:

Home	PR Database Search