From owner-freebsd-doc@FreeBSD.ORG Sun Mar 23 03:00:09 2008
Return-Path:
Delivered-To: freebsd-doc@hub.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 8E45F1065671
for ; Sun, 23 Mar 2008 03:00:09 +0000 (UTC)
(envelope-from gnats@FreeBSD.org)
Received: from freefall.freebsd.org (freefall.freebsd.org
[IPv6:2001:4f8:fff6::28])
by mx1.freebsd.org (Postfix) with ESMTP id 7E9E28FC1C
for ; Sun, 23 Mar 2008 03:00:09 +0000 (UTC)
(envelope-from gnats@FreeBSD.org)
Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1])
by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m2N309PK078892
for ; Sun, 23 Mar 2008 03:00:09 GMT
(envelope-from gnats@freefall.freebsd.org)
Received: (from gnats@localhost)
by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m2N309pX078891;
Sun, 23 Mar 2008 03:00:09 GMT (envelope-from gnats)
Date: Sun, 23 Mar 2008 03:00:09 GMT
Message-Id: <200803230300.m2N309pX078891@freefall.freebsd.org>
To: freebsd-doc@FreeBSD.org
From: John Ferrell
Cc:
Subject: Re: docs/121838: [patch] add portmaster(8) section to ports chapter
of the handbook
X-BeenThere: freebsd-doc@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: John Ferrell
List-Id: Documentation project
List-Unsubscribe: ,
List-Archive:
List-Post:
List-Help:
List-Subscribe: ,
X-List-Received-Date: Sun, 23 Mar 2008 03:00:09 -0000
The following reply was made to PR docs/121838; it has been noted by GNATS.
From: John Ferrell
To: bug-followup@FreeBSD.org, jdferrell3@yahoo.com, dougb@FreeBSD.org
Cc:
Subject: Re: docs/121838: [patch] add portmaster(8) section to ports chapter
of the handbook
Date: Sat, 22 Mar 2008 22:25:01 -0400
Doug,
Thanks for reviewing the portmaster section. I have revised the diff
based on your comments. And thanks for developing a great utility!
John
--- chapter.sgml.orig 2008-03-11 12:46:26.000000000 -0400
+++ chapter.sgml 2008-03-22 11:48:15.000000000 -0400
@@ -1293,6 +1293,97 @@
For further information see &man.portmanager.1;.
+
+
+ Upgrading Ports using Portmaster
+
+
+ portmaster
+
+
+ Portmaster is another utility for
+ upgrading installed ports. Portmaster
+ was designed make use of the tools found in the base
+ system (it does not depend upon any other ports) and uses the
+ information in /var/db/pkg/
+ to determine which ports to upgrade. It is available from the
+ ports-mgmt/portmaster port:
+
+ &prompt.root; cd /usr/ports/ports-mgmt/portmaster
+&prompt.root; make install clean
+
+ Portmaster groups ports into four
+ categories:
+
+
+
+ Root ports (no dependencies, not depended on)
+
+
+ Trunk ports (no dependencies, are depended on)
+
+
+ Branch ports (have dependencies, are depended on)
+
+
+ Leaf ports (have dependencies, not depended on)
+
+
+
+ You can list all the installed ports and search
+ for updates using the option:
+
+&prompt.root; portmaster -L
+===>>> Root ports (No dependencies, not depended on)
+===>>> ispell-3.2.06_18
+===>>> screen-4.0.3
+ ===>>> New version available: screen-4.0.3_1
+===>>> tcpflow-0.21_1
+===>>> 7 root ports
+...
+===>>> Branch ports (Have dependencies, are depended on)
+===>>> apache-2.2.3
+ ===>>> New version available: apache-2.2.8
+...
+===>>> Leaf ports (Have dependencies, not depended on)
+===>>> automake-1.9.6_2
+===>>> bash-3.1.17
+ ===>>> New version available: bash-3.2.33
+...
+===>>> 32 leaf ports
+
+===>>> 137 total installed ports
+ ===>>> 83 have new versions available
+
+
+ All the installed ports can be upgraded using this simple
+ command:
+
+ &prompt.root; portmaster -a
+
+ By default, Portmaster
+ will make a backup package before deleting the existing port. If
+ the installation of the new version is successful,
+ Portmaster will delete the backup.
+ Using the will instruct
+ Portmaster not to automatically delete
+ the backup. Also, adding the option will start
+ Portmaster in interactive mode, prompting
+ you before upgrading each port.
+
+ If you encounter errors during the upgrade process, you can use
+ the option to upgrade/rebuild all ports:
+
+ &prompt.root; portmaster -af
+
+ You can also use Portmaster to
+ install new ports on the system, upgrading all dependencies
+ before building and installing the new port:
+
+ &prompt.root; portmaster shells/bash
+
+ Please see &man.portmaster.8; from more information.
+
From owner-freebsd-doc@FreeBSD.ORG Sun Mar 23 09:01:34 2008
Return-Path:
Delivered-To: freebsd-doc@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id E2DA7106564A;
Sun, 23 Mar 2008 09:01:34 +0000 (UTC)
(envelope-from netchild@freebsd.org)
Received: from redbull.bpaserver.net (redbullneu.bpaserver.net
[213.198.78.217])
by mx1.freebsd.org (Postfix) with ESMTP id 5B5D48FC17;
Sun, 23 Mar 2008 09:01:34 +0000 (UTC)
(envelope-from netchild@freebsd.org)
Received: from outgoing.leidinger.net (p54A547F5.dip.t-dialin.net
[84.165.71.245])
by redbull.bpaserver.net (Postfix) with ESMTP id 7C53F2E0FE;
Sun, 23 Mar 2008 10:01:27 +0100 (CET)
Received: from deskjail (unknown [192.168.1.109])
by outgoing.leidinger.net (Postfix) with ESMTP id 17BA99DE59;
Sun, 23 Mar 2008 09:59:08 +0100 (CET)
Date: Sun, 23 Mar 2008 09:52:57 +0100
From: Alexander Leidinger
To: "Murray Stokely"
Message-ID: <20080323095257.1cb6f242@deskjail>
In-Reply-To: <2a7894eb0803221426t10f552a7n1a1f84b8f31956f6@mail.gmail.com>
References: <2a7894eb0803220016m2b20b042x54456da9ec260043@mail.gmail.com>
<20080322094225.5bcdd5f5@deskjail>
<2a7894eb0803221426t10f552a7n1a1f84b8f31956f6@mail.gmail.com>
Organization: FreeBSD
X-Mailer: Claws Mail 3.3.1 (GTK+ 2.12.8; i686-portbld-freebsd8.0)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-BPAnet-MailScanner-Information: Please contact the ISP for more information
X-BPAnet-MailScanner: Found to be clean
X-BPAnet-MailScanner-SpamCheck: not spam, SpamAssassin (not cached,
score=-14.8, required 6, BAYES_00 -15.00, NO_RDNS 0.50,
RDNS_DYNAMIC 0.10, SARE_FROM_SPAM_WORD3 0.10, SMILEY -0.50)
X-BPAnet-MailScanner-From: netchild@freebsd.org
X-Spam-Status: No
Cc: freebsd-doc@freebsd.org
Subject: Re: Please Review: design doc for Project Ideas web application
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: Sun, 23 Mar 2008 09:01:35 -0000
Quoting "Murray Stokely" (Sat, 22 Mar 2008 14:26:35 -0700):
> On Sat, Mar 22, 2008 at 1:42 AM, Alexander Leidinger
> wrote:
> > My overall opinion: great! Improvement suggestions below.
>
> Thanks for the many suggestions, comments below.
>
> > > * Strict XML schema requires careful text editing in a tedious
> > > file format to add new ideas to the list.
> > > * Anyone can propose an idea, but there is no feedback mechanism
> > > to separate the good ideas from the very bad ideas on the list.
> > > o Some very senior developers have vehement objections to
> > > prominently placed items on the current list, but have no avenue of
> > > listing their alternate point of views on the project.
> >
> > That's a shame. Unfortunately this needs a change in the behavior of
> > such developers, not a change in the presentation layer. So it is not
> > really a drawback of the current system. Please fix this part in the
> > wiki.
>
> I reworded it. How is this:
>
> "Many senior developers have very different opinions about technical
> ideas. The current system does not provide an avenue for them to list
> alternate points of view, add detailed technical comments of
> suggestions or criticism, etc.."
I never rejected to add technical stuff to entries. I think the same is
true for Joel. So far we either got technical comments, or not. So I
don't think this text reflects the reality. I don't mind if you write
the the current system doesn't have a rating system where people can
see personalized comments/opinions.
> > > * There is no notification mechanism when new ideas are added to the list.
> >
> > Sorry, this is not entirely true. Committers should have no problem to
> > get a notification in case they are interested. Either with their own
> > mailfilter, or by using our dfilter (or how the name if this thing is).
>
> Ok, but non-committers may also be interested in this. And a
> notification with all other CVS changes isn't that useful. The new
Yes, there's why I wrote 'entirely'... :)
> system would allow one to have RSS feeds for specific searches for
> example, so one could only get a notification when a new filesystem
> project with difficulty <= 3 and at least one positive comment has
> been posted.
Wow, this is a very nice feature.
> I updated this on the wiki to be more clear.
Thanks.
> > > * Allow anyone to propose a new idea online.
> > > * Allow anyone to comment and vote on previously proposed ideas.
> >
> > What is this voting supposed to tell us? If users vote for features
> > they want to see, then I think it's a great idea. We would get feedback
> > what is the most desired stuff.
>
> Yes, users and developers.
>
> > If developers vote against an entry, it's a bad idea. Voting (which is
>
> I think there are entries on our current list that some developers
> think are a bad idea, and others think are a great idea. At least
> that has been the case in the past and I don't think necessarily that
> 100% of the ideas need to be agreed upon by 100% of committers,
> especially once we have a mechanism for alternate points of view to be
> attached as comments and votes to the ideas.
Yes. I just moaned about "voting", but what you seem to have
implemented is "rating with comments". That's what we need here. Good!
> > by definition a binary pro/con for an item) is not what we need to do
> > here. Developers need to review with a technical (or legal) argument
> > against something. Just a "I don't like this" or "this is bullshit" or
> > "this is not a good idea" without an explanation why will result in a
> > very negative image and people will refuse to submit ideas.
>
> Yes I agree. We can put up some text on the vote/comment submission
> form reminding people of this, and if necessary we can more strongly
> moderate the comments, and certainly at least warn users that
> profanity is not helpful.
Sounds ok.
> > The screenshot suggests you want to use it for rating by developers. As
> > said, in this case a simple voting is not enough. The Google SoC webapp
> > seems to better in this regard, it allows to give comments. The rest is
>
> I was confused why we had a miscommunication at this point, then I
> realized I didn't post a screen shot of the actual individual idea
> page. Everything you proposed about linking comments with the votes
> is already implemented. I've added a new screen shot to the wiki.
Great. Looks ok.
> The main UI change is now we only show idea summaries on the main
> page. You have to click on the summary to get to the full idea page
> which includes the full text body about the idea, and all comments and
> votes that have been left about that idea. With the inclusion of
> comments and voting there is far too much content to all be put on one
> page once I import all of the existing ideas from ideas.xml.
Looks ok.
> > So basically my comment for this is: an "interest" value for users (simple
> > voting), instead of rating would be better for the voting part. To rate
> > an entry by developers there needs to be more than a simple voting
> > interface.
>
> Yes I agree with all of this and I'm sorry I didn't post more
> screenshots to make it clearer. I think we are in complete agreement
> about this. Let me know if there is more.
As it looks currently, the developer rating and the user voting is done
in the same "slot". Shouldn't we separate this into two slots, so that
we have a rating value by developers, and an interest value from users?
> > What about email notification? Personally I prefer email over RSS for
> > something like this (I can read email from more places than I can read
> > RSS stuff).
>
> Sure, we can have the web app send out some emails (I've Avoided this
> so that I don't have to think of all the abuse cases) or at the very
> least have a script in cron download the rss and turn it into an email
> and send it out.
I don't think I care much about the format (except maybe when I can not
determine what the change is to the previous status, but we will see).
> > It may also be better to have a separate text field for the
> > requirements. All entries need the requirements section, and we could
> > check this way if someone entered some requirements or not (ok, would
> > be very simple, like "is there more than only whitespace"), but at
> > least we can give feedback that it is a requirement to list
> > requirements.
>
> There are two approaches we can take with the different text areas for
> requirements, difficulty level, time estimates, etc. We can either
> have separate text fields for all of them, or one large text field
> pre-filled in with something like
>
> "Your project idea here
>
> Requirements:
> * example: Familiarity with C language.
> * Familiarity with TCP/IP RFCs.
>
> Difficultly level: moderate
> "
>
> I lean more towards having a single text field, pre-filled in the way
> we'd like to see it, rather than having many different text boxes we
> must deal with.
We can refine this later when we see how usable the current approach
is. Just take care that we can extend the app later without roadblocks.
> > Augment until we think it is ready for public consumption, then
> > replace. This way we can fix the rough edges while getting a benefit
> > already out of it.
>
> Sounds good. I think in fact we can very easily augment it like this :
>
> 1. Import all ideas.xml into this system, so that all existing ideas
> are open for comment/voting.
> 2. Implement export to ideas.xml feature.
> 3. Change the xsl file in the static web build to include a link next
> to each idea that says "Leave a comment about this idea." or, if
> comments have been made, "View comments by others about this idea."
> and just have those links go to the relevant idea in this app. That
> just means we need to add an "idea_id" integer field to the existing
> ideas.xml file, so it knows how to construct the appropriate links for
> that idea (http://webapp/ideas/).
No objections... :)
Bye,
Alexander.
--
...and that is how we know the Earth to be banana-shaped.
http://www.Leidinger.net Alexander @ Leidinger.net: PGP ID = B0063FE7
http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID = 72077137
From owner-freebsd-doc@FreeBSD.ORG Mon Mar 24 10:37:03 2008
Return-Path:
Delivered-To: doc@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 6D5F8106564A
for ; Mon, 24 Mar 2008 10:37:03 +0000 (UTC)
(envelope-from st41ker@megacom.ua)
Received: from ferry.megacom.ua (ferry.megacom.ua [193.28.177.2])
by mx1.freebsd.org (Postfix) with ESMTP id 3623C8FC14
for ; Mon, 24 Mar 2008 10:37:03 +0000 (UTC)
(envelope-from st41ker@megacom.ua)
Received: from localhost (localhost [127.0.0.1])
by localhost (Postfix) with ESMTP id C32F3C9A64
for ; Mon, 24 Mar 2008 12:04:56 +0200 (EET)
Received: from ferry.megacom.ua ([127.0.0.1])
by localhost (ferry [127.0.0.1]) (amavisd-new, port 10025) with ESMTP
id 77250-04 for ; Mon, 24 Mar 2008 12:04:55 +0200 (EET)
Received: from cyber.megacom.ua (cyber.megacom.ua [193.28.177.17])
by ferry.megacom.ua (Postfix) with ESMTP id C123EC9A30
for ; Mon, 24 Mar 2008 12:04:55 +0200 (EET)
From: st41ker
To: doc@FreeBSD.org
Content-Type: text/plain
Organization: Megacom ltd.
Date: Mon, 24 Mar 2008 12:04:54 +0200
Message-Id: <1206353094.9067.1.camel@cyber.megacom.ua>
Mime-Version: 1.0
X-Mailer: Evolution 2.6.3
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by clamav at megacom dot biz
Cc:
Subject: (no subject)
X-BeenThere: freebsd-doc@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: st41ker@megacom.ua
List-Id: Documentation project
List-Unsubscribe: ,
List-Archive:
List-Post:
List-Help:
List-Subscribe: ,
X-List-Received-Date: Mon, 24 Mar 2008 10:37:03 -0000
Hi.
http://www.freebsd.org/releases/6.3R/errata.html contains mistyped word
It was merged to the 6-STABLE codeline after the release branch was
created. This utility will be >>>incldued<< subsequent
This mistype could be in other files.
From owner-freebsd-doc@FreeBSD.ORG Mon Mar 24 10:54:46 2008
Return-Path:
Delivered-To: freebsd-doc@hub.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 7712C1065671;
Mon, 24 Mar 2008 10:54:46 +0000 (UTC)
(envelope-from remko@FreeBSD.org)
Received: from freefall.freebsd.org (freefall.freebsd.org
[IPv6:2001:4f8:fff6::28])
by mx1.freebsd.org (Postfix) with ESMTP id 5E4CE8FC26;
Mon, 24 Mar 2008 10:54:46 +0000 (UTC)
(envelope-from remko@FreeBSD.org)
Received: from freefall.freebsd.org (remko@localhost [127.0.0.1])
by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m2OAskJE086421;
Mon, 24 Mar 2008 10:54:46 GMT
(envelope-from remko@freefall.freebsd.org)
Received: (from remko@localhost)
by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m2OAskUj086417;
Mon, 24 Mar 2008 10:54:46 GMT (envelope-from remko)
Date: Mon, 24 Mar 2008 10:54:46 GMT
Message-Id: <200803241054.m2OAskUj086417@freefall.freebsd.org>
To: remko@FreeBSD.org, freebsd-doc@FreeBSD.org, remko@FreeBSD.org
From: remko@FreeBSD.org
Cc:
Subject: Re: docs/121838: [patch] add portmaster(8) section to ports chapter
of the handbook
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: Mon, 24 Mar 2008 10:54:46 -0000
Synopsis: [patch] add portmaster(8) section to ports chapter of the handbook
Responsible-Changed-From-To: freebsd-doc->remko
Responsible-Changed-By: remko
Responsible-Changed-When: Mon Mar 24 10:54:45 UTC 2008
Responsible-Changed-Why:
I'll take it.
http://www.freebsd.org/cgi/query-pr.cgi?pr=121838
From owner-freebsd-doc@FreeBSD.ORG Mon Mar 24 11:06:07 2008
Return-Path:
Delivered-To: freebsd-doc@hub.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 27AC71065675
for ; Mon, 24 Mar 2008 11:06:07 +0000 (UTC)
(envelope-from owner-bugmaster@FreeBSD.org)
Received: from freefall.freebsd.org (freefall.freebsd.org
[IPv6:2001:4f8:fff6::28])
by mx1.freebsd.org (Postfix) with ESMTP id 257158FC1B
for ; Mon, 24 Mar 2008 11:06:07 +0000 (UTC)
(envelope-from owner-bugmaster@FreeBSD.org)
Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1])
by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m2OB66Cc086841
for ; Mon, 24 Mar 2008 11:06:06 GMT
(envelope-from owner-bugmaster@FreeBSD.org)
Received: (from gnats@localhost)
by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m2OB66fp086837
for freebsd-doc@FreeBSD.org; Mon, 24 Mar 2008 11:06:06 GMT
(envelope-from owner-bugmaster@FreeBSD.org)
Date: Mon, 24 Mar 2008 11:06:06 GMT
Message-Id: <200803241106.m2OB66fp086837@freefall.freebsd.org>
X-Authentication-Warning: freefall.freebsd.org: gnats set sender to
owner-bugmaster@FreeBSD.org using -f
From: FreeBSD bugmaster
To: FreeBSD doc list
Cc:
Subject: Current unassigned doc problem reports
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: Mon, 24 Mar 2008 11:06:07 -0000
Current FreeBSD problem reports
The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases.
Bugs can be in one of several states:
o - open
A problem report has been submitted, no sanity checking performed.
a - analyzed
The problem is understood and a solution is being sought.
f - feedback
Further work requires additional information from the
originator or the community - possibly confirmation of
the effectiveness of a proposed solution.
p - patched
A patch has been committed, but some issues (MFC and / or
confirmation from originator) are still open.
r - repocopy
The resolution of the problem report is dependent on
a repocopy operation within the CVS repository which
is awaiting completion.
s - suspended
The problem is not being worked on, due to lack of information
or resources. This is a prime candidate
for somebody who is looking for a project to do.
If the problem cannot be solved at all,
it will be closed, rather than suspended.
c - closed
A problem report is closed when any changes have been integrated,
documented, and tested -- or when fixing the problem is abandoned.
Critical problems
Serious problems
S Tracker Resp. Description
--------------------------------------------------------------------------------
o docs/27605 doc [patch] Cross-document references ()
s docs/35678 doc docproj Makefiles for web are broken for paths with sp
o docs/61605 doc [request] Improve documentation for i386 disk geometry
o docs/84932 doc new document: printing with an Epson ALC-3000N on Free
o docs/98115 doc Missing parts after rendering handbook to RTF format
o docs/106135 doc [request] articles/vinum needs to be updated
o docs/110253 doc [patch] rtprio(1): remove processing starvation commen
p docs/112935 doc [patch] newfs_msdos(8): document 4.3g limit on files w
o docs/116080 doc PREFIX is documented, but not the more important LOCAL
o docs/118902 doc [patch] wrong signatures in d2i_RSAPublicKey man pages
o docs/119545 doc books/arch-handbook/usb/chapter.sgml formatting
o docs/120456 doc ath(4) needs to specify requirement on wlan_scan_sta
o docs/121193 doc Err in Release notes (twa driver number wrong)
o docs/121312 doc RELNOTES_LANG breaks release if not en_US.ISO8859-1
14 problems total.
Non-critical problems
S Tracker Resp. Description
--------------------------------------------------------------------------------
s docs/20028 doc ASCII docs should reflect tags in the sourc
o docs/24786 doc missing FILES descriptions in sa(4)
o docs/26286 doc *printf(3) etc should gain format string warnings
a docs/30008 doc [patch] French softupdates document should be translat
s docs/33589 doc [patch] to doc.docbook.mk to post process .tex files.
o docs/36432 doc Proposal for doc/share/mk: make folded books using psu
o docs/36449 doc symlink(7) manual doesn't mention trailing slash, etc.
o docs/38982 doc [patch] developers-handbook/Jail fix
o docs/40423 doc Keyboard(4)'s definition of parameters to GETFKEY/SETF
o docs/41089 doc pax(1) -B option does not mention interaction with -z
o docs/43823 doc [PATCH] update to environ(7) manpage
o docs/47818 doc [patch] ln(1) manpage is confusing
o docs/48101 doc [patch] add documentation on the fixit disk to the FAQ
o docs/50211 doc [PATCH] doc.docbook.mk: fix textfile creation
o docs/53271 doc bus_dma(9) fails to document alignment restrictions
o docs/53596 doc Updates to mt(1) manual page
o docs/53751 doc bus_dma(9) incorrectly documents BUS_DMA_ALLOCNOW
s docs/54752 doc bus_dma explained in ISA section in Handbook: should b
o docs/57388 doc [patch] INSTALL.TXT enhancement: mention ok prompt
o docs/59044 doc [patch] doc.docbook.mk does not properly handle a sour
o docs/59477 doc Outdated Info Documents at http://docs.freebsd.org/inf
o docs/59835 doc ipfw(8) man page does not warn about accepted but mean
o docs/61301 doc [patch] Manpage patch for aue(4) to enable HomePNA fun
o docs/69861 doc [patch] usr.bin/csplit/csplit.1 does not document POSI
o docs/70652 doc [patch] New man page: portindex(5)
o docs/75865 doc comments on "backup-basics" in handbook
o docs/75995 doc hcreate(3) documentation(?) bug
o docs/76333 doc [patch] ferror(3): EOF indicator can be cleared by not
o docs/78138 doc [patch] Error in pre-installation section of installat
o docs/78240 doc [patch] handbook: replace with aroun
o docs/78480 doc Networked printer setup unnecessarily complex in handb
o docs/82595 doc 25.5.3 Configuring a bridge section of the handbook ne
o docs/84265 doc [patch] chmod(1) manpage omits implication of setting
o docs/84268 doc chmod(1) manpage's BUGS entry is either wrong or too c
o docs/84317 doc fdp-primer doesn't show class=USERNAME distinctively
o docs/84670 doc [patch] tput(1) manpage missing ENVIRONMENT section wi
o docs/84806 doc mdoc(7) manpage has section ordering problems
o docs/84956 doc [patch] intro(5) manpage doesn't mention API coverage
o docs/85118 doc [PATCH] opiekey(1) references non-existing opiegen(1)
o docs/85128 doc loader.conf(5) autoboot_delay incompletly described
o docs/85187 doc [patch] find(1) manpage missing block info for -ls
o docs/86342 doc bikeshed entry of Handbook is wrong
o docs/87857 doc ifconfig(8) wireless options order matters
o docs/87936 doc Handbook chapter on NIS/YP lacks good information on a
o docs/88512 doc [patch] mount_ext2fs(8) man page has no details on lar
o docs/91149 doc read(2) can return EINVAL for unaligned access to bloc
o docs/91506 doc ndis(4) man page should be more specific about support
o docs/92626 doc jail manpage should mention disabling some periodic sc
o docs/94625 doc [patch] growfs man page -- document "panic: not enough
o docs/95139 doc FAQ to move filesystem to new disk fails: incorrect pe
o docs/96207 doc Comments of a sockaddr_un structure could confuse one
o docs/98974 doc Missing tunables in loader(8) manpage
o docs/99506 doc FreeBSD Handbook addition: IPv6 Server Settings
o docs/100196 doc man login.conf does explain not "unlimited"
o docs/100242 doc sysctl(3) description of KERN_PROC is not correct anym
o docs/101464 doc sync ru_RU.KOI8-R/articles/portbuild/article.html with
o docs/102148 doc The description of which Intel chips have EM64T is out
o docs/102719 doc [patch] ng_bpf(4) example leads to unneeded promiscuos
o docs/104403 doc man security should mention that the usage of the X Wi
o docs/104879 doc Howto: Listen to IMA ADPCM .wav files on FreeBSD box
o docs/105608 doc fdc(4) debugging description staled
o docs/105997 doc sys/kern/sys_pipe.c refer to tuning(7), but there is n
o docs/107432 doc Handbook's default partitioning schema is out-of-date
o docs/108101 doc /boot/default/loader.conf contains an incorrect commen
a docs/108980 doc list of missing man pages
o docs/109115 doc add Ultra 450 to hardware list for sparc64
o docs/109201 doc [request]: manual for callbootd
f docs/109226 doc [request] No manual entry for sntp
o docs/109972 doc No manual entry for zless/bzless
o docs/109973 doc No manual entry for c++filt
o docs/109975 doc No manual entry for elf2aout
o docs/109977 doc No manual entry for ksu
o docs/109981 doc No manual entry for post-grohtml
o docs/109983 doc No manual entry for protoize
o docs/110061 doc [PATCH] tuning(7) missing reference to vfs.read_max
o docs/110062 doc [patch] mount_nfs(8) fails to mention a failure condit
o docs/110376 doc [patch] add some more explanations for the iwi/ipw fir
o docs/110692 doc wi(4) man page doesn't say WPA is not supported
o docs/110999 doc carp(4) should document unsupported interface types
o docs/111147 doc hostapd.conf is not documented
o docs/111263 doc [request] Information on $EDITOR variable in section 3
o docs/111265 doc [request] Clarify how to set common shell variables
o docs/111425 doc Missing chunks of text in historical manpages
o docs/112481 doc bug in ppp.linkup example
o docs/112682 doc Handbook GEOM_GPT explanation does not provide accurat
o docs/112804 doc groff(1) command should be called to explicitly use "p
o docs/113194 doc [patch] [request] crontab.5: handling of day-in-month
o docs/114139 doc mbuf(9) has misleading comments on M_DONTWAIT and M_TR
o docs/114184 doc [patch] [ndis]: add info to man 4 ndis
o docs/114371 doc [patch][ipv6] rtadvd.con(5) should show how to adverti
o docs/115000 doc [PATCH] nits and updates to FAQs (part 1)
o docs/115065 doc [patch] sync ps.1 with p_flag and keywords
o docs/115921 doc Booting from pst(4) is not supported
o docs/116116 doc mktemp (3) re/move note
o docs/116480 doc sysctl(3) description of kern.file no longer applies s
o docs/117013 doc mount_smbfs(8) doesn't document -U (username) argument
f docs/117308 doc Clarification of /etc/defaults/devfs.rules status
o docs/117747 doc 'break' system call needs a man page
o docs/117798 doc formatting oddity in sysmouse(4)
o docs/118214 doc close(2) error returns incomplete
f docs/118332 doc man page for top does not describe STATE column wait e
o docs/118545 doc loader tunables kern.dfldsiz and friends nearly undocu
o docs/119329 doc [patch] Fix misleading man 1 split
o docs/119338 doc gprof(1) refers to unmentioned option "-c"
s docs/119404 doc [request] events page should list only last 2 years wo
a docs/119536 doc a few typos in French handbook (basics)
o docs/119746 doc l10n chapter of handbook (Russian Language)
o docs/119907 doc Ports compatibility
o docs/120024 doc resolver(5) and hosts(5) need updated for IPv6
o docs/120040 doc handbook: diskless operation: populate root doesn't po
o docs/120125 doc [patch] Installing FreeBSD 7.0 via serial console and
o docs/120248 doc [patch] getaddrinfo() implementation on FreeBSD 7 is i
o docs/120357 doc [patch] zone.9 - document also the _arg versions of th
o docs/120539 doc Inconsistent ipfw's man page
o docs/120628 doc PAE documentation errror in handbook
s docs/120917 doc [request]: Man pages mising for thr_xxx syscalls
o docs/121173 doc [patch] mq_getattr(2): mq_flags mistakenly described a
o docs/121197 doc [patch] edits to books/porters-handbook
o docs/121321 doc Handbook should reflect new pf.conf defaults
s docs/121541 doc [request] no man pages for wlan_scan_ap
o docs/121565 doc dhcp-options(5) manpage incorrectly formatted omitting
o docs/121585 doc [handbook] Wrong multicast specification
o docs/121648 doc [patch] add portmaster(8) to man-refs.ent
o docs/121713 doc man page for su contains errornous example.
o docs/121721 doc telnetd(8) not describing -X authentication types
o docs/121821 doc [patch] wpa_supplicant.conf.5 - provide pointer to sam
o docs/121863 doc IPSEC handbook update for FreeBSD 7 and later
o docs/121871 doc ftpd does not interpret configuration files as documen
o docs/121952 doc Handbook chapter on Network Address Translation wrong
129 problems total.
From owner-freebsd-doc@FreeBSD.ORG Mon Mar 24 15:40:04 2008
Return-Path:
Delivered-To: freebsd-doc@hub.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 69F471065677
for ; Mon, 24 Mar 2008 15:40:04 +0000 (UTC)
(envelope-from gnats@FreeBSD.org)
Received: from freefall.freebsd.org (freefall.freebsd.org
[IPv6:2001:4f8:fff6::28])
by mx1.freebsd.org (Postfix) with ESMTP id 3ADD38FC3D
for ; Mon, 24 Mar 2008 15:40:04 +0000 (UTC)
(envelope-from gnats@FreeBSD.org)
Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1])
by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m2OFe4QY016631
for ; Mon, 24 Mar 2008 15:40:04 GMT
(envelope-from gnats@freefall.freebsd.org)
Received: (from gnats@localhost)
by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m2OFe4ZE016630;
Mon, 24 Mar 2008 15:40:04 GMT (envelope-from gnats)
Resent-Date: Mon, 24 Mar 2008 15:40:04 GMT
Resent-Message-Id: <200803241540.m2OFe4ZE016630@freefall.freebsd.org>
Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer)
Resent-To: freebsd-doc@FreeBSD.org
Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org,
Fico
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 3402B1065670
for ;
Mon, 24 Mar 2008 15:38:51 +0000 (UTC)
(envelope-from nobody@FreeBSD.org)
Received: from www.freebsd.org (www.freebsd.org [IPv6:2001:4f8:fff6::21])
by mx1.freebsd.org (Postfix) with ESMTP id 169398FC47
for ;
Mon, 24 Mar 2008 15:38:51 +0000 (UTC)
(envelope-from nobody@FreeBSD.org)
Received: from www.freebsd.org (localhost [127.0.0.1])
by www.freebsd.org (8.14.2/8.14.2) with ESMTP id m2OFcfhs058332
for ; Mon, 24 Mar 2008 15:38:41 GMT
(envelope-from nobody@www.freebsd.org)
Received: (from nobody@localhost)
by www.freebsd.org (8.14.2/8.14.1/Submit) id m2OFceJn058331;
Mon, 24 Mar 2008 15:38:40 GMT (envelope-from nobody)
Message-Id: <200803241538.m2OFceJn058331@www.freebsd.org>
Date: Mon, 24 Mar 2008 15:38:40 GMT
From: Fico
To: freebsd-gnats-submit@FreeBSD.org
X-Send-Pr-Version: www-3.1
Cc:
Subject: docs/122052: minor update on handbook section 20.7.1
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: Mon, 24 Mar 2008 15:40:04 -0000
>Number: 122052
>Category: docs
>Synopsis: minor update on handbook section 20.7.1
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: freebsd-doc
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: update
>Submitter-Id: current-users
>Arrival-Date: Mon Mar 24 15:40:03 UTC 2008
>Closed-Date:
>Last-Modified:
>Originator: Fico
>Release: release 7.0
>Organization:
UFRJ
>Environment:
FreeBSD jwww.local 7.0-RELEASE FreeBSD 7.0-RELEASE #0: Fri Feb 29 17:08:36 CET 2008 root@trinity.local:/usr/obj/usr/src/sys/TRINITY i386
>Description:
confusing statement regarding newfs(8) on vinum(4) volumes.
>How-To-Repeat:
>Fix:
Patch attached with submission follows:
diff -r -u handbook.orig/vinum-object-naming.html handbook/vinum-object-naming.html
--- handbook.orig/vinum-object-naming.html 2008-03-22 05:43:54.000000000 +0100
+++ handbook/vinum-object-naming.html 2008-03-24 16:27:00.000000000 +0100
@@ -157,15 +157,6 @@
Vinum volume might be called /dev/gvinum/concat, a name which
has no relationship with a partition name.
-
Normally, newfs(8) interprets
-the name of the disk and complains if it cannot understand it. For example:
-
-
-#newfs /dev/gvinum/concat
-newfs: /dev/gvinum/concat: can't figure out file system partition
-
-
In order to create a file system on this volume, use newfs(8):
>Release-Note:
>Audit-Trail:
>Unformatted:
From owner-freebsd-doc@FreeBSD.ORG Mon Mar 24 16:10:03 2008
Return-Path:
Delivered-To: freebsd-doc@hub.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 0D9011065686
for ; Mon, 24 Mar 2008 16:10:03 +0000 (UTC)
(envelope-from gnats@FreeBSD.org)
Received: from freefall.freebsd.org (freefall.freebsd.org
[IPv6:2001:4f8:fff6::28])
by mx1.freebsd.org (Postfix) with ESMTP id B36AA8FC26
for ; Mon, 24 Mar 2008 16:10:02 +0000 (UTC)
(envelope-from gnats@FreeBSD.org)
Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1])
by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m2OGA252018390
for ; Mon, 24 Mar 2008 16:10:02 GMT
(envelope-from gnats@freefall.freebsd.org)
Received: (from gnats@localhost)
by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m2OGA23n018389;
Mon, 24 Mar 2008 16:10:02 GMT (envelope-from gnats)
Resent-Date: Mon, 24 Mar 2008 16:10:02 GMT
Resent-Message-Id: <200803241610.m2OGA23n018389@freefall.freebsd.org>
Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer)
Resent-To: freebsd-doc@FreeBSD.org
Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org,
Fico
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 50630106567E
for ;
Mon, 24 Mar 2008 16:08:52 +0000 (UTC)
(envelope-from nobody@FreeBSD.org)
Received: from www.freebsd.org (www.freebsd.org [IPv6:2001:4f8:fff6::21])
by mx1.freebsd.org (Postfix) with ESMTP id 0CDD98FC38
for ;
Mon, 24 Mar 2008 16:08:52 +0000 (UTC)
(envelope-from nobody@FreeBSD.org)
Received: from www.freebsd.org (localhost [127.0.0.1])
by www.freebsd.org (8.14.2/8.14.2) with ESMTP id m2OG8f6w065034
for ; Mon, 24 Mar 2008 16:08:41 GMT
(envelope-from nobody@www.freebsd.org)
Received: (from nobody@localhost)
by www.freebsd.org (8.14.2/8.14.1/Submit) id m2OG8fbN065033;
Mon, 24 Mar 2008 16:08:41 GMT (envelope-from nobody)
Message-Id: <200803241608.m2OG8fbN065033@www.freebsd.org>
Date: Mon, 24 Mar 2008 16:08:41 GMT
From: Fico
To: freebsd-gnats-submit@FreeBSD.org
X-Send-Pr-Version: www-3.1
Cc:
Subject: docs/122053: updaze on vinum(4) reference to newfs(8)
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: Mon, 24 Mar 2008 16:10:03 -0000
>Number: 122053
>Category: docs
>Synopsis: updaze on vinum(4) reference to newfs(8)
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: freebsd-doc
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Mon Mar 24 16:10:02 UTC 2008
>Closed-Date:
>Last-Modified:
>Originator: Fico
>Release: release 7.0
>Organization:
UFRJ
>Environment:
FreeBSD jwww.local 7.0-RELEASE FreeBSD 7.0-RELEASE #0: Fri Feb 29 17:08:36 CET 2008 root@trinity.local:/usr/obj/usr/src/sys/TRINITY i386
>Description:
MAKING FILE SYSTEM sub-section on vinum(4) need update on how to use newfs(8).
>How-To-Repeat:
>Fix:
Patch attached with submission follows:
--- man.orig/man4/vinum.4 2006-06-11 21:41:07.000000000 +0200
+++ man/man4/vinum.4 2008-03-24 17:01:39.000000000 +0100
@@ -428,18 +428,20 @@
For a physical disk partition, the
last letter of the device name specifies the partition identifier (a to h).
.Nm
-volumes need not conform to this convention, but if they do not,
-.Xr newfs 8
-will complain that it cannot determine the partition.
-To solve this problem,
-use the
-.Fl v
-flag to
-.Xr newfs 8 .
+volumes does not need to conform with this convention.
For example, if you have a volume
.Pa concat ,
use the following command to create a UFS file system on it:
.Pp
+.Dl "newfs /dev/gvinum/concat"
+.Pp
+.Ss Note:
+On FreeBSD versions prior to 5.0
+.Xr newfs 8
+requires an additional
+.Fl v
+flag and the old device naming scheme:
+.Pp
.Dl "newfs -v /dev/vinum/concat"
.Sh OBJECT NAMING
.Nm
>Release-Note:
>Audit-Trail:
>Unformatted:
From owner-freebsd-doc@FreeBSD.ORG Mon Mar 24 16:40:05 2008
Return-Path:
Delivered-To: freebsd-doc@hub.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
by hub.freebsd.org (Postfix) with ESMTP id 7B2551065673
for ; Mon, 24 Mar 2008 16:40:05 +0000 (UTC)
(envelope-from gnats@FreeBSD.org)
Received: from freefall.freebsd.org (freefall.freebsd.org
[IPv6:2001:4f8:fff6::28])
by mx1.freebsd.org (Postfix) with ESMTP id 53B508FC15
for ; Mon, 24 Mar 2008 16:40:05 +0000 (UTC)
(envelope-from gnats@FreeBSD.org)
Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1])
by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m2OGe5GK021531
for ; Mon, 24 Mar 2008 16:40:05 GMT
(envelope-from gnats@freefall.freebsd.org)
Received: (from gnats@localhost)
by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m2OGe5XD021530;
Mon, 24 Mar 2008 16:40:05 GMT (envelope-from gnats)
Date: Mon, 24 Mar 2008 16:40:05 GMT
Message-Id: <200803241640.m2OGe5XD021530@freefall.freebsd.org>
To: freebsd-doc@FreeBSD.org
From: "Remko Lodder"
Cc:
Subject: Re: docs/122052: minor update on handbook section 20.7.1
X-BeenThere: freebsd-doc@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Remko Lodder
List-Id: Documentation project
List-Unsubscribe: ,
List-Archive:
List-Post:
List-Help:
List-Subscribe: ,
X-List-Received-Date: Mon, 24 Mar 2008 16:40:05 -0000
The following reply was made to PR docs/122052; it has been noted by GNATS.
From: "Remko Lodder"
To: "Fico"
Cc: freebsd-gnats-submit@freebsd.org
Subject: Re: docs/122052: minor update on handbook section 20.7.1
Date: Mon, 24 Mar 2008 17:32:22 +0100 (CET)
> confusing statement regarding newfs(8) on vinum(4) volumes.
> Patch attached with submission follows:
>
> diff -r -u handbook.orig/vinum-object-naming.html
> handbook/vinum-object-naming.html
> --- handbook.orig/vinum-object-naming.html 2008-03-22 05:43:54.000000000
> +0100
> +++ handbook/vinum-object-naming.html 2008-03-24 16:27:00.000000000 +0100
> @@ -157,15 +157,6 @@
> Vinum volume might be called class="FILENAME">/dev/gvinum/concat, a name which
> has no relationship with a partition name.
>
> -