Re: docs/160446: [handbook] Handbook sound setup seems outdated
Synopsis: [handbook] Handbook sound setup seems outdated Responsible-Changed-From-To: freebsd-doc->dru Responsible-Changed-By: dru Responsible-Changed-When: Mon Oct 14 13:41:11 UTC 2013 Responsible-Changed-Why: Assign this to me. http://www.freebsd.org/cgi/query-pr.cgi?pr=160446 ___ freebsd-doc@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
Re: docs/121585: [handbook] Wrong multicast specification
Synopsis: [handbook] Wrong multicast specification Responsible-Changed-From-To: freebsd-doc->dru Responsible-Changed-By: dru Responsible-Changed-When: Fri Mar 7 16:42:59 UTC 2014 Responsible-Changed-Why: I'll take this one. http://www.freebsd.org/cgi/query-pr.cgi?pr=121585 ___ freebsd-doc@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
Re: docs/162404: [handbook] IPv6 link-local address compared with IPv4 loopback address and IPv6 site-local deprecated
Synopsis: [handbook] IPv6 link-local address compared with IPv4 loopback address and IPv6 site-local deprecated Responsible-Changed-From-To: freebsd-doc->dru Responsible-Changed-By: dru Responsible-Changed-When: Fri Mar 7 16:53:51 UTC 2014 Responsible-Changed-Why: I'll take this one. http://www.freebsd.org/cgi/query-pr.cgi?pr=162404 ___ freebsd-doc@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
Re: docs/172743: IPv6 handbooks lacks info about accepting router advertisements
Synopsis: IPv6 handbooks lacks info about accepting router advertisements Responsible-Changed-From-To: freebsd-doc->dru Responsible-Changed-By: dru Responsible-Changed-When: Fri Mar 7 17:11:07 UTC 2014 Responsible-Changed-Why: I'll take this one. http://www.freebsd.org/cgi/query-pr.cgi?pr=172743 ___ freebsd-doc@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
Re: docs/186625: Handbook rebuilding "world" upgrade procedure wrong mergemaster command
Synopsis: Handbook rebuilding "world" upgrade procedure wrong mergemaster command Responsible-Changed-From-To: freebsd-doc->dru Responsible-Changed-By: dru Responsible-Changed-When: Fri Mar 7 18:39:00 UTC 2014 Responsible-Changed-Why: I'll take this one. http://www.freebsd.org/cgi/query-pr.cgi?pr=186625 ___ freebsd-doc@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
Re: docs/148984: [handbook] Mistake in section 16.15.4 of the handbook
Synopsis: [handbook] Mistake in section 16.15.4 of the handbook Responsible-Changed-From-To: freebsd-doc->dri Responsible-Changed-By: dru Responsible-Changed-When: Mon Mar 31 15:04:22 UTC 2014 Responsible-Changed-Why: I'll take this one. http://www.freebsd.org/cgi/query-pr.cgi?pr=148984 ___ freebsd-doc@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
Re: docs/150255: dtrace description should mention makeoptions DEBUG=-g
Synopsis: dtrace description should mention makeoptions DEBUG=-g Responsible-Changed-From-To: freebsd-doc->dru Responsible-Changed-By: dru Responsible-Changed-When: Tue Apr 15 23:36:05 UTC 2014 Responsible-Changed-Why: I'll take this one. http://www.freebsd.org/cgi/query-pr.cgi?pr=150255 ___ freebsd-doc@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
Re: docs/119545: books/arch-handbook/usb/chapter.sgml formatting
Synopsis: books/arch-handbook/usb/chapter.sgml formatting Responsible-Changed-From-To: freebsd-doc->dru Responsible-Changed-By: dru Responsible-Changed-When: Wed Apr 23 13:56:06 UTC 2014 Responsible-Changed-Why: I'll take this one. http://www.freebsd.org/cgi/query-pr.cgi?pr=119545 ___ freebsd-doc@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
Re: docs/189065: [handbook] Handbook example command does not work
Synopsis: [handbook] Handbook example command does not work Responsible-Changed-From-To: freebsd-doc->dru Responsible-Changed-By: dru Responsible-Changed-When: Tue Apr 29 19:37:13 UTC 2014 Responsible-Changed-Why: I'll take this one. http://www.freebsd.org/cgi/query-pr.cgi?pr=189065 ___ freebsd-doc@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
Re: docs/160460: [handbook] Network setup guide suggestion
Synopsis: [handbook] Network setup guide suggestion Responsible-Changed-From-To: freebsd-doc->dru Responsible-Changed-By: dru Responsible-Changed-When: Tue Apr 29 19:49:55 UTC 2014 Responsible-Changed-Why: I'll take this one. http://www.freebsd.org/cgi/query-pr.cgi?pr=160460 ___ freebsd-doc@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
Re: docs/189216: [patch] add a handbook section on hosting VMs with bhyve
Synopsis: [patch] add a handbook section on hosting VMs with bhyve Responsible-Changed-From-To: freebsd-doc->dru Responsible-Changed-By: dru Responsible-Changed-When: Mon May 5 16:03:49 UTC 2014 Responsible-Changed-Why: I'll take http://www.freebsd.org/cgi/query-pr.cgi?pr=189216 ___ freebsd-doc@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
Re: docs/101271: serial console documentation implies kernel rebuild required -- doesn't mention device hints
Synopsis: serial console documentation implies kernel rebuild required -- doesn't mention device hints Responsible-Changed-From-To: freebsd-doc->dru Responsible-Changed-By: dru Responsible-Changed-When: Thu May 8 16:09:59 UTC 2014 Responsible-Changed-Why: I'll take http://www.freebsd.org/cgi/query-pr.cgi?pr=101271 ___ freebsd-doc@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
Re: docs/169544: serial port console documentation changes
Synopsis: serial port console documentation changes Responsible-Changed-From-To: freebsd-doc->dru Responsible-Changed-By: dru Responsible-Changed-When: Thu May 8 16:11:08 UTC 2014 Responsible-Changed-Why: I'll take http://www.freebsd.org/cgi/query-pr.cgi?pr=169544 ___ freebsd-doc@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
Re: docs/189847: Removing Xserves from BSD Handbook
Synopsis: Removing Xserves from BSD Handbook Responsible-Changed-From-To: freebsd-doc->dru Responsible-Changed-By: dru Responsible-Changed-When: Fri May 16 01:55:07 UTC 2014 Responsible-Changed-Why: I'll take http://www.freebsd.org/cgi/query-pr.cgi?pr=189847 ___ freebsd-doc@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
Re: docs/173013: FreeBSD Boot Menu documentation lacks detail
Synopsis: FreeBSD Boot Menu documentation lacks detail Responsible-Changed-From-To: freebsd-doc->dru Responsible-Changed-By: dru Responsible-Changed-When: Tue May 20 17:06:20 UTC 2014 Responsible-Changed-Why: Take http://www.freebsd.org/cgi/query-pr.cgi?pr=173013 ___ freebsd-doc@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
draft agenda for June 17 doc sprint
There will be a doc sprint on Monday, June 17 from 8:00-18:00 EDT (UTC-4) both in person and online. For those attending in person, it will be held at the Garfield Suites Hotel in Cincinnati, OH and will be followed afterwards by a free bourbon tasting (http://openhelpconference.com/bourbon). For those attending online, discussions will be held on #bsddocs and collaborative notes will occur at http://openetherpad.org/p/junedocsprint. A draft agenda is appended. Feel free to add to it. See you on June 17th! Cheers, Dru --- - profiling/merging discussion (and plan forward for where to commit changes) - assign work items for the Handbook and coordinate - commit outstanding changes to FDP Quick Start Guide - hammer out which style of tags to use (e.g. should tags include class="directory", etc.?) - update http://www.freebsd.org/doc/en_US.ISO8859-1/books/fdp-primer/writing-style-word-list.html to reflect our conventions for the commonly found Handbook inconsistencies - commit outstanding additions to the Style Guide - fix and close PRs ___ freebsd-doc@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
June 17 doc sprint
Just a reminder that the next doc sprint is Monday, June 17 from 12:00 - 22:00 UTC. The hosting site for openetherpad seems to be borked, so I've moved the agenda here: https://wiki.freebsd.org/DocSprints If you are able to attend via IRC, please add your availability and any agenda items that you would like to have included. Cheers, Dru ___ freebsd-doc@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
correct way to do links?
I'm updating http://www.freebsd.org/doc/en_US.ISO8859-1/books/fdp-primer/xml-markup-docbook.html, section "4.2.7 Links" to make sure how to do these 3 types of links is crystal clear: 1. Links to another section within the same document. 2. Links to another book or article within the FDP. 3. Links to an external website. What is the correct usage for Docbook 4/5 for each type of link? 1. Links to another section within the same document: Is this a with the description to appear specified or an with the section automatically rendered? 2. Links to another book or article within the FDP: Is this a with the description to appear specified or an with the section automatically rendered? 3. Should links to an external website use a tag, an url=, and the description to appear? For example: http://www.wi-fi.org/";>Wi-Fi alliance Cheers, Dru ___ freebsd-doc@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
Re: RFC: Upgrading to DocBook 5.0
ga> Em 05-06-2013 14:10, Hiroki Sato escreveu: ga> > Gabor Kovesdan wrote ga> >in <519FA4FE.4030305 at FreeBSD.org>: ga> > ga> > ga> username --> systemitem class="username" ga> > ga> groupname --> systemitem class="groupname" ga> > ga> hostid role="fqdn" --> systemitem class="fqdomainname" ga> > ga> hostid role="hostname" --> systemitem class="fqdomainname" ga> > ga> hostid role="domainname" --> systemitem class="fqdomainname" ga> > ga> hostid role="netmask" --> systemitem class="netmask" ga> > ga> hostid role="mac" --> systemitem class="etheraddress" ga> > ga> hostid role="ipaddr" --> systemitem class="ipaddress" ga> > ga> hostid --> systemitem ga> > ga> > Hmm, I do not like to create "a rule" to mark up both a username and ga> > a hostname by using element without attribute. Even if ga> > the rendering results are the same, they are different. Is it ga> > problem with allowing both writing s without attribute ga> > and adding attributes into them later (or at the same time)? I do ga> > not think limiting the vocabulary is useful for learning. Allowing ga> > people who are not familiar with DocBook to mark up by using ga> >only should be enough if it is really an issue. ga> Technically it is easily possible to convert them "correctly", i.e. as ga> described above, it was just my suggestion to leave out class ga> attributes. It is also possible to allow systemitem with and without ga> the class attribute specified. Yes, it is just my preference, too. ga> > ga> This is actually a type of file and the filename class attribute ga> > may ga> > ga> also be devicefile, which expresses its semantics. Again, we ga> > should ga> > ga> consider dropping the class attributes to simplify things: ga> > ga> devicename --> filename class="devicefile" ga> > ga> ga> > ga> These are not actually distinguished in formatting and the package ga> > ga> element expresses them better: ga> > ga> filename role="package" --> package ga> > ga> filename role="port" --> package ga> > ga> > package should support a role to distinguish if it is a port or a ga> > package because the linkend can be different. The following DSSSL ga> > fragment was removed in our XSLT: ga> > ga> > ga> > (element filename ga> >(let* ((class (attribute-string (normalize "role" ga> > (cond ga> > ((equal? class "package") ga> >(let* ((urlurl"http://www.FreeBSD.org/cgi/url.cgi";) ga> > (href (string-append urlurl "?ports/" ga> > (data (current-node)) ga> > "/pkg-descr"))) ga> > (create-link (list (list "HREF" href)) ($mono-seq$ ga> > (else ($mono-seq$) ga> > ga> It's true that I didn't notice this distinction in the rendering. But ga> why not addding this link to both packages and ports? My personal ga> impression is that there are people, who mostly use packages and ga> others, who use ports. This preference is independent from the ga> context. If the text talks about the textproc/docproj ports but I ga> prefer dealing with packages, I will still want to install the package ga> and vice versa. In the essence, they are the same. This is why I would ga> not distinguish them. I think both can have a link, but ftp/wget and wget-1.14.tbz will have different linkends, for example. Although a single linkend like http://.../ports/ftp/wget.html can be applied to the both via XSLT, algorithms of URL generation from the markup text become different between ports and packages. Simplification of markup restricts such a possibility, I think. Can we have a summary for the FDP (and for the benefit of Handbook editors) of when/if systemitem class= should be used? Are there also systemitems for the different types of s which should be used instead? Cheers, Dru ___ freebsd-doc@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
doc sprint follow-up on Sunday, June 23?
This week's doc sprint went well. The notes and action items from the sprint are here: http://openetherpad.org/p/junedocsprint We didn't get to several items needing discussion due to the sprint being held on a work day. It was suggested to have the discussion on #bsddocs on a weekend so I am proposing this Sunday, June 23 beginning at 14:00 UTC. Does that time work for those interested in discussing the following topics? - Warren's profiling demo (http://wonkity.com/~wblock/profiledemo/) and merging suggestions - coordination of pre- and post- release marketing Please indicate if you are able to attend or if you have an alternative date/time. Cheers, Dru ___ freebsd-doc@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
FreeBSD Now! blog
As a result of the latest doc sprint discussion and as promised, the FreeBSD Now! blog has been created at http://freebsdnow.blogspot.com/. The Foundation has granted permission to use the logo and Deb and I discussed an agreeable attribution text that would fit within the confines of the template. Due to the limitations of blogger and my even more limited design skills, it is using a very simple template and clean design. Anyone in the project who has a CFT or would like to bring attention to interesting commits, features, Handbook changes, requests for assistance, etc. is welcome to either request an author account or to send the list or myself the desired text for a post. This is just yet another blog that I keep an eye on for a project and blogger is good at emailing admins whenever a comment or new post is posted so I expect SPAM comments and inappropriate posts to be very limited and short-lived. I'll let it settle for a week or two in the doc teams hands before I announce it to the larger dev mailing list. Hopefully we will have several authors by that time, and if anyone is interested, another admin or two. Cheers, Dru ___ freebsd-doc@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
Re: Doc sprint at vbsdcon
>Date: Mon, 23 Sep 2013 09:26:57 -0400 >From: Tom Rhodes >To: freebsd-doc@FreeBSD.org >Subject: Doc sprint at vbsdcon >Message-ID: <20130923092657.3b542304.trho...@freebsd.org> >Content-Type: text/plain; charset=US-ASCII > >Hey, > >Anyone attending this event? I'm trying to get a head count >and make plans for it. Cheers, I'll be there. Cheers, Dru ___ freebsd-doc@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
Update on Print Edition
Things are starting to move along for the Print Edition of the Handbook. The goal is to have a publishable PDF to the Mall (and an epub/pdf to the Foundation) by the end of the year. It may turn out that having Volume 1 ready by end of year and Volume 2 by end of Q1/14 is more realistic. I've started an editorial doc where I put each day's progress notes. The latest version is uploaded once per day and is available at: http://people.freebsd.org/~dru/handbook_toc.odt The current milestone is to get as much of Chapters 1-11 into a yellow state (i.e. ready for a many-eyes review to make final patches and sign-off as "print-ready") in time for the doc sprints at vBSDCon (October 25-26) as several doc committers will be in attendance. While Internet access is supposed to be good at this event, it is in the evening which will be too late in the day for most European and Asian committers. However, everyone is encouraged to review content, submit patches, and discuss their thoughts on which chapters are good to go. If you have a section you've been thinking about editing and have time to do so in the next few weeks, let us know and we'll mark that chapter as taken and concentrate on other chapters instead. There's still a whole lot of work to do and now is a good time to get it done! Cheers, Dru ___ freebsd-doc@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
11.3. Installing Mathematica®
I downloaded the 30 day trial of Mathematica and surprise of surprises, the installation script "just works". However, the executable fails with: /usr/local/Wolfram/Mathematica/9.0/SystemFiles/FrontEnd/Binaries/Linux/Mathematica: error while loading shared libraries: libaspell.so.1: cannot open shared object file: No such file or directory the choices on the system are: locate libaspell.so.1 /compat/linux/usr/lib/libaspell.so.15 /compat/linux/usr/lib/libaspell.so.15.1.4 /usr/local/Wolfram/Mathematica/9.0/SystemFiles/Libraries/Linux/libaspell.so.1 /usr/local/Wolfram/Mathematica/9.0/SystemFiles/Libraries/Linux-x86-64/libaspell.so.1 I've played around with some symlinks but haven't had any joy yet. If someone has time to take a crack at it, instructions are here (section 11.3.1): http://people.freebsd.org/~dru/linuxemu-mathematica.html The download of Mathematica is ~1.8GB. Cheers, Dru ___ freebsd-doc@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
Proposed Changes to Chapter 27: Electronic Mail
The current layout of this chapter is as follows: 27. Electronic Mail 27.1. Synopsis 27.2. Using Electronic Mail 27.3. Sendmail Configuration 27.4. Changing the Mail Transfer Agent 27.5. Troubleshooting 27.6. Advanced Topics 27.7. Setting Up to Send Only 27.8. Using Mail with a Dialup Connection 27.9. SMTP Authentication 27.10. Mail User Agents 27.11. Using fetchmail 27.12. Using procmail I would like to do the following: Divide the content of this chapter into MUA stuff and MTA stuff. Since the MUA stuff is suited to noobs (Volume 1), move it into the Basics chapter. Since the MTA stuff is suited to admins (Volume 2), move it into the Network Servers chapter. Anyone opposed? Cheers, Dru ___ freebsd-doc@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
updating ports
Currently, there are 2 Handbook sections that deal with upgrading ports: 5.6.3. Upgrading Ports (which describes the use of the portmaster and portupgrade ports) and 23.3. Portsnap: a Ports Collection Update Tool (which describes the built-in portsnap) I would like to combine these into 5.6.3. Do we want to encourage the use of third-party utils or just encourage the use of the built in one? If just the built in one, I'll replace 5.6.3 with the contents of 23.3 and reduce portmaster/portupgrade to a note that these utils are available in the ports collection. If we should describe all three, I'll place 23.3 as the first utility to be described in 5.6.3. Cheers, Dru ___ freebsd-doc@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
updating documentation set
This section: 23.4. Updating the Documentation Set really belongs (and is already mostly duplicated in): http://www.freebsd.org/doc/en_US.ISO8859-1/books/fdp-primer/overview.html#overview-doc Any objections to me doing the following? 1. remove "23.4. Updating the Documentation Set" from the Handbook, replacing it with a NOTE in the updating section that docs can either be updated during an OS upgrade or, at any other time, by following the instructions in the FDP overview (with link) 2. make sure that any points covered by 23.4 and currently missing from the FDP overview are added to the FDP overview Cheers, Dru ___ freebsd-doc@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
Re: updating ports
>> Currently, there are 2 Handbook sections that deal with upgrading ports: >> >> 5.6.3. Upgrading Ports (which describes the use of the portmaster and >> portupgrade ports) >> >> and >> >> 23.3. Portsnap: a Ports Collection Update Tool (which describes the built-in >> portsnap) >> >> I would like to combine these into 5.6.3. >> >> Do we want to encourage the use of third-party utils or just encourage the >> use of the built in one? >> > >I think there are two separate topics here (without having looked at the >Handbook sections yet). I don't think portmaster and portupgrade >actually handle updating the ports tree itself, but handle >upgrading/rebuilding ports within the ports tree. > >Portsnap, on the other hand, does not actually touch the software >installed (meaning, it does not update the installed third-party >software), but only handles updating the ports tree sources themselves. > >> If just the built in one, I'll replace 5.6.3 with the contents of 23.3 and >> reduce portmaster/portupgrade to a note that these utils are available in >> the ports collection. >> >> If we should describe all three, I'll place 23.3 as the first utility to be >> described in 5.6.3. Good catch...and I see that portsnap is already covered in Procedure 5.1 of section 5.6. I'll submit a patch some time this week. Cheers, Dru ___ freebsd-doc@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
docs/187733: line numbers in program listings cycle from 0-9
>Number: 187733 >Category: docs >Synopsis: line numbers in program listings cycle from 0-9 >Confidential: no >Severity: non-critical >Priority: low >Responsible:freebsd-doc >State: open >Quarter: >Keywords: >Date-Required: >Class: doc-bug >Submitter-Id: current-users >Arrival-Date: Wed Mar 19 13:00:00 UTC 2014 >Closed-Date: >Last-Modified: >Originator: Dru Lavigne >Release: >Organization: >Environment: >Description: If a program listing is more than 9 lines long, the line numbers cycle back to 0-9. For example, the first program listing in http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/network-iscsi.html is 15 lines long, but the lines are numbered from 1-9, then from 0-5. >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted: ___ freebsd-doc@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
Re: en/handbook/audit: proposed corrections
___ > From: Taras Korenko >To: freebsd-doc@freebsd.org >Sent: Saturday, March 29, 2014 12:19 PM >Subject: en/handbook/audit: proposed corrections > > > Good day, doc@ folks. > > There're a few things that could be improved within audit chapter of our >handbook. However, those are just notes, which might require more polishing >or wordsmithing. So, can anyone review and/or comment the following *.diff? Thanks, Taras. A slightly modified patch is attached. If it is acceptable to you, I can commit it. Cheers, DruIndex: chapter.xml === --- chapter.xml (revision 44393) +++ chapter.xml (working copy) @@ -196,8 +196,10 @@ Audit Configuration User space support for event auditing is installed as part - of the base &os; operating system. Kernel support can be - enabled by adding the following line to + of the base &os; operating system. Kernel support is available + in the GENERIC kernel by default, + and &man.auditd.8; can be enabled + by adding the following line to /etc/rc.conf: auditd_enable="YES" @@ -217,10 +219,7 @@ Selection expressions are used in a number of places in the audit configuration to determine which events should be audited. Expressions contain a list of event classes to - match, each with a prefix indicating whether matching records - should be accepted or ignored, and optionally to indicate if - the entry is intended to match successful or failed - operations. Selection expressions are evaluated from left to + match. Selection expressions are evaluated from left to right, and two expressions are combined by appending one onto the other. @@ -383,10 +382,10 @@ These audit event classes may be customized by modifying - the audit_class and audit_ - event configuration files. + the audit_class and + audit_event configuration files. - Each audit event class is combined with a prefix + Each audit event class may be combined with a prefix indicating whether successful/failed operations are matched, and whether the entry is adding or removing matching for the class and type. summarizes @@ -650,8 +649,8 @@ Since audit logs may be very large, a subset of records can be selected using auditreduce. This example selects all audit records produced for the user - trhodes stored in - AUDITFILE: + trhodes stored in + AUDITFILE: &prompt.root; auditreduce -u trhodes /var/audit/AUDITFILE | praudit @@ -739,8 +738,8 @@ Automatic rotation of the audit trail file based on file size is possible using filesz in - audit.control as described in . + audit_control as described in . As audit trail files can become very large, it is often desirable to compress or otherwise archive trails once they ___ freebsd-doc@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
Re: Possible mistake on handbook - Section 30.7: Link Aggregation
>Dne 29.3.2014 3:32, Thomas Hoffmann napsal(a): >>> I was reading the handbook and stumbled upon the following sentence: >>> >>> "Failover allows traffic to continue to flow even if an interface becomes >>> available." >> >> Also, does "an interface" convey what we need here? For any given N-way >> aggregation, can't we have N-1 (one or more, but not all) interfaces become >> unavailable and still have a working link? > >And Cpt. Obvious may add an interface is not enough, you can have four >interfaces aggregated in the bond, but there is still no flow without a >link. To add even more chaos, both the physical and virtual interfaces >are mentioned in the sentence preceding the one which Rafael mentions. > >That said, what about something like following? > >Failover allows traffic to continue to flow if at least one aggregated >network interface has link established. I've commited an edit in r44394. Please let me know if further wordsmithing is needed to make it clearer. Thanks Rafael for pointing this out! Cheers, Dru ___ freebsd-doc@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
Re: Mistake in handbook 23.6 Rebuilding world
>Having the -i and -F options is something I would like to see too, or at >least offered in a . Does changing that line to the following make sense? If so, I'll commit it. # mergemaster -piF Cheers, Dru ___ freebsd-doc@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
Re: Mistake in handbook 23.6 Rebuilding world
>> >Having the -i and -F options is something I would like to see too, or at >> >least offered in a . >> >> >> >> Does changing that line to the following make sense? If so, I'll commit it. >> >> # mergemaster -piF > >No, the second mergemaster command should not include the -p option. > ># mergemaster -p > >(make installworld) > ># mergemaster -iF Added in r44504. Thanks for the suggestion! Cheers, Dru ___ freebsd-doc@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
Re: Download FreeBSD Handbook
On Sun, 5/4/14, Hosney Osman wrote: And what if I want to buy a hardcopy for FreeBSD handbook Reference from where I can get it We're working on a hardcopy edition which should be available later this year. When it is, it will be available from freebsdmall.com. Cheers, Dru ___ freebsd-doc@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
Re: New retailer of FreeBSD
> Getlinux wrote freebsd-questi...@freebsd.org: > > Sir, > > > > I am a Linux and BSDretailer named "Getlinux". > > Can you tell me how to be added in the retailers list located at the URL > > : http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/mirrors.html > > > > My details are : > > Getlinux > > 78 Rue de la Croix Rochopt > > 91860 EPINAY SOUS SENART > > FRANCE > > Email : cont...@getlinux.fr > > Web : http://www.getlinux.fr > > > > Regards, > > Ken LE PRADO Hello Ken, Thank you for submitting this listing. It has been committed in r44760 and should show up on the website shortly. Cheers, Dru ___ freebsd-doc@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
Re: cdrecord -> cdrtools
On Mon, 5/5/14, Ken wrote: Subject: cdrecord -> cdrtools To: "freebsd-doc@FreeBSD.org" Date: Monday, May 5, 2014, 5:05 PM Hi, Just wanted to point out the cdrecord package seems to have been replaced by cdrtools. The documentation still refers to sysutils/cdrecord (in section 18.5.5 Procedure 1) Thanks for the heads up, Ken. This has been fixed in r44769 and that was the only remaining reference to that package in the Handbook. Cheers, Dru ___ freebsd-doc@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
Re: 27.7. Setting Up to Send Only
the steps described in Section 27.7 should cover other installation methods than ports, or at least give a hint. I installed ssmtp using the new pkgng system, and the mailer.conf was not touched. The mailer.conf has to be changed manually to the following: sendmail /usr/local/sbin/ssmtp send-mail /usr/local/sbin/ssmtp mailq /usr/libexec/sendmail/sendmail newaliases /usr/libexec/sendmail/sendmail hoststat /usr/libexec/sendmail/sendmail purgestat /usr/libexec/sendmail/sendmail Hello Alex, Thank you for the suggestion. An example has been added in r44820. Cheers, Dru ___ freebsd-doc@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
Re: Error in Documentation
To remove all of the cron jobs in a user crontab: % crontab -l remove crontab for dru? y It should read: To remove all of the cron jobs in a user crontab: % crontab -r remove crontab for dru? y Thanks for the heads up! This has been fixed in r44836. Cheers, Dru ___ freebsd-doc@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
Re: epub / ebook
On Sun, 2/8/15, Cody Chamberlain wrote: > i was just searching around seeing if > there was a version of the freebsd handbook available as an > e-book. i see amazon has an option from the FreeBSD > Documentation Foundation.. is that actively maintained? is > there an ePub / kindlegen version already crreated that just > needs to be maintained? > > i was going to take the handbook page and start getting an > ePub created but didn’t want to reinvent the wheel if its > already spinning. Hello Cody, Sorry for the late reply. It looks like someone uploaded an older version of the Handbook to Amazon. That version has since been removed and we have asked the uploader to improve the quality of the Kindle version and use their own name, rather than the FreeBSD Documentation Project, if they upload it again so as not to confuse readers. Currently, we're not generating an epub or a Kindle version of the Handbook. We spent a lot of time last year getting the Handbook up-to-date and have a bit more work to do on that front. The plan in doing so is to have a modernized, dead tree edition available through the FreeBSD Mall, as the last published version was over 10 years ago, as well as an epub version available for sale where the proceeds go directly to the FreeBSD Foundation. At one point there was a mechanism to automatically generate the Handbook in various formats, but it's my understanding that we are only doing HTML at this time. This is something we'll be discussing at the doc working group and sprints during BSDCan in June. If you happen to be attending that conference, feel free to join the doc sprints each evening :-) Cheers, Dru ___ freebsd-doc@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
Re: The FreeBSD Handbook
Hello David, Where did you purchase the Handbook from? (eg which URL) Cheers, Dru On Mon, 6/29/15, David Lieberman wrote: Subject: The FreeBSD Handbook To: freebsd-doc@FreeBSD.org Date: Monday, June 29, 2015, 1:15 AM Hi, I just purchased a copy of The FreeBSD Handbook, 3rd Edition, Volume 1, after having clicked on 'Handbook' under 'Shortcuts' on the FreeBSD Home page and examining the FreeBSD Handbook to which I was directed. In the Abstract of this FreeBSD Handbook, it states that "If you would prefer to have a hard copy of the handbook, you can purchase one at the FreeBSD Mall". I therefore expected that the Volume 1 that I was purchasing would consist of approximately the first half of the FreeBSD Handbook, Copyright 1995-2015, that I had examined at your website. However, it was immediately evident, from the Table of Contents, that the book I received (last Copyright 2003) was not a hard copy of the FreeBSD Handbook I had examined. If a true hard copy of the FreeBSD Handbook shown at your website exists, I would very much appreciate receiving a copy to replace the book you sent me. If not, then I would appreciate receiving a refund of the $51.50 I paid you. In either case, if you arrange for the postage, I will return the book you sent me. David Lieberman -- David Lieberman dvlieber...@gmail.com ___ freebsd-doc@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org" ___ freebsd-doc@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
Re: Docbook handbook sources
Hello Sebastien, The Quick Start Guide can get you started: https://www.freebsd.org/doc/en_US.ISO8859-1/books/fdp-primer/overview-quick-start.html Cheers, Dru On Tue, 6/30/15, Sébastien Mainand wrote: Subject: Docbook handbook sources To: freebsd-doc@freebsd.org Date: Tuesday, June 30, 2015, 8:32 AM Hello, I'm trying to make a patch to the handbook and I read here: https://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing/article.html that it was written in Docbook format. Were can I get the source code ? I could not find it in the FTP folder. Thanks Seb. ___ freebsd-doc@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org" ___ freebsd-doc@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
Re: ports referenced in handbook but removed...
Any disagreements or enhancement suggestions for the attached patch? Once approved, I'll mark it for commital after August 1 (the EOL for 8.x). Cheers, Dru On Fri, 7/24/15, John-Mark Gurney wrote: Subject: ports referenced in handbook but removed... To: freebsd-doc@freeBSD.org Cc: freebsd-po...@freebsd.org Date: Friday, July 24, 2015, 12:10 AM I was looking at the handbook for localization items to answer a question and came across: https://www.freebsd.org/doc/handbook/using-localization.html#locale-console big5con does not exist anymore zhcon does not exist anymore kon2's link is wrong, the port exists, but w/o a pkg-descr kon2-14dot's link is wrong, the port exists, but w/o a pkg-descr It'd be nice if someone updated our documentation. Thanks. -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not." ___ freebsd-doc@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"Index: chapter.xml === --- chapter.xml (revision 47083) +++ chapter.xml (working copy) @@ -486,58 +486,9 @@ moused - For languages with wide or multibyte characters, install a - console for that language from the &os; Ports Collection. The - available ports are summarized in . Once installed, refer to the - port's pkg-message or man pages for - configuration and usage instructions. + As of &rel2.current;, &man.vt.4; supports wide and + multibyte characters. - - Available Console from Ports Collection - - - - - Language - Port Location - - - - - - Traditional Chinese (BIG-5) - chinese/big5con - - - - Chinese/Japanese/Korean - chinese/cce - - - - Chinese/Japanese/Korean - chinese/zhcon - - - - Japanese - chinese/kon2 - - - - Japanese - japanese/kon2-14dot - - - - Japanese - japanese/kon2-16dot - - - - - If moused is enabled in /etc/rc.conf, additional configuration may be required. By default, the mouse cursor of the ___ freebsd-doc@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
Re: Documentation shortcoming
Apparently, this is only required for link local addresses, which should be clarified in the Handbook. Can someone with more IPv6-clue suggest a clearer wording so that both cases are understood? Cheers, Dru On Thu, 5/21/15, Rüsing, Gerrit wrote: Subject: Documentation shortcoming To: "freebsd-doc@FreeBSD.org" Date: Thursday, May 21, 2015, 8:11 AM Hello guys, my request is referring to IPv6 Documentation: https://www.freebsd.org/doc/en/books/handbook/network-ipv6.html could you please add the interface to that line in your docu? It caused me some headache to find that missing. ipv6_defaultrouter="2001:db8:4672:6565::1%fxp0“ Thanks a lot :-) Kind regards Gerrit ___ freebsd-doc@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
Re: Typo
Thanks, Mark! Fixed in r47100. Cheers, Dru On Tue, 9/23/14, Mark Corbett Wilson wrote: Subject: Typo To: freebsd-doc@freebsd.org Date: Tuesday, September 23, 2014, 1:08 PM Greetings On the FreeBSD Handbook Preface page ( http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/book-preface.html) under Typographic Conventions, shouldn't the *Bold* sentence read; "A *bold* font is used for applications, commands, and keys."? Peace & Resistance Mark Corbett Wilson factotum and communication Peralta Colleges Foundation “In a world of change, the learners shall inherit the earth, while the learned shall find themselves perfectly suited for a world that no longer exists.” ~ Eric Hoffer ___ freebsd-doc@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org" ___ freebsd-doc@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
Re: Faulty link on ipf page
Thanks, Patrick! Fixed in r47101. Cheers, Dru On Tue, 7/22/14, Patrick Lindblad wrote: Subject: Faulty link on ipf page To: freebsd-doc@freebsd.org Date: Tuesday, July 22, 2014, 9:06 AM Hey, On http://www.freebsd.org/doc/handbook/firewalls-ipf.html there is: "For a detailed explanation of the legacy rules processing method, refer to http://coombs.anu.edu.au/~avalon/ip-filter.html."; That link is redirected to http://asiapacific.anu.edu.au/ and has been for the last week that I have tested it. Yours sincerely Patrick ___ freebsd-doc@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org" ___ freebsd-doc@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-doc To unsubscribe, send any mail to "freebsd-doc-unsubscr...@freebsd.org"
Re: Documentation shortcoming
On Sun, 7/26/15, Hiroki Sato wrote: Subject: Re: Documentation shortcoming To: d...@freebsd.org, dru.lavi...@att.net Cc: freebsd-doc@FreeBSD.org, rues...@kdo.de Date: Sunday, July 26, 2015, 4:01 PM Dru Lavigne wrote in <1437908470.22608.yahoomailba...@web184901.mail.gq1.yahoo.com>: dr> Apparently, this is only required for link local addresses, which dr> should be clarified in the Handbook. Can someone with more IPv6-clue dr> suggest a clearer wording so that both cases are understood? > I have a patch including this kind of clarification and other updates > (attached). Can you review this? Thank you for updating this content! I've attached a slightly modified patch, mostly small grammar tuning. Cheers, DruIndex: chapter.xml === --- chapter.xml (revision 47098) +++ chapter.xml (working copy) @@ -4439,10 +4439,10 @@ Anycast These addresses are syntactically indistinguishable - from unicast addresses but they address a group of - interfaces. The packet destined for an anycast address - will arrive at the nearest router interface. Anycast - addresses are only used by routers. + from unicast addresses, except that they address any of + the interfaces belonging to the address. The packet + destined for an anycast address will be received by one + of the interfaces. @@ -4450,13 +4450,8 @@ Multicast These addresses identify a group of interfaces. A - packet destined for a multicast address will arrive at - all interfaces belonging to the multicast group. The - IPv4 broadcast address, usually - xxx.xxx.xxx.255, is - expressed by multicast addresses in - IPv6. + packet destined for a multicast address will be received by + all interfaces belonging to the multicast group. @@ -4484,7 +4479,7 @@ which in turn is equivalent to 2002::a00:1. - To view a &os; system's IPv6 address, + To view a &os; system's IPv6 address, use &man.ifconfig.8;: &prompt.root; ifconfig @@ -4538,16 +4533,8 @@ - ::00:xx:xx:xx:xx + :::xx:xx:xx:xx 96 bits - embedded IPv4 - The lower 32 bits are the compatible - IPv4 address. - - - - ::ff:xx:xx:xx:xx - 96 bits IPv4 mapped IPv6 address The lower 32 bits are the IPv4 @@ -4556,11 +4543,15 @@ - fe80::/10 + fe80::%rl0/10 10 bits link-local Equivalent to 169.254.0.0/16 in - IPv4. + IPv4. An address with a link-local + scope always needs a zone id because it is unique only + on a link. The zone id is an interface name, for + example %rl0, or an interface index + number. @@ -4580,7 +4571,7 @@ - 2000::-3fff:: + 2000::-3fff:: 3 bits global unicast All global unicast addresses are assigned from @@ -4597,21 +4588,23 @@ - Configuring IPv6 + Configuring IPv6 Host To configure a &os; system as an IPv6 - client, add these two lines to + host, add these two lines to rc.conf: - ifconfig_rl0_ipv6="inet6 accept_rtadv" -rtsold_enable="YES" + ifconfig_rl0_ipv6="inet6 accept_rtadv" - The first line enables the specified interface to receive - router solicitation messages. The second line enables the - router solicitation daemon, &man.rtsol.8;. + This line enables the specified interface to receive + Router Advertisement messages. These messages are distributed + by routers on the same link to provide information such as the + subnet prefix, default routers, MTU, + recursive DNS server list, and so + on. - For &os; 8.x, add a third - line: + For &os; 8.x, add the + following line: ipv6_enable="YES" @@ -4619,16 +4612,25 @@ IPv6 address, add an entry to specify the static address and associated prefix length: - ifconfig_rl0_ipv6="inet6 2001:db8:4672:6565:2026:5043:2d42:5344 prefixlen 64" + ifconfig_rl0_ipv6="inet6 2001:db8:4672:6565:2026:5043:2d42:5344/64" On a &os; 8.x system, that line uses this format instead: - ipv6_ifconfig_rl0="2001:db8:4672:6565:2026:5043:2d42:5344" + ipv6_ifconfig_rl0="2001:db8:4672:6565:2026:5043:2d42:5344 prefixlen 64" - To assign a default router, specify its address: + To manually assign a default router, specify its address. + Note that this information is also provided via Router + Advertisement messages and the specified address will not be + overridden. ipv6_defaultrouter="2001:db8:4672:6565::1" + + This can be an link-local a
