From owner-freebsd-doc@FreeBSD.ORG Mon Nov 4 10:10:01 2013 Return-Path: Delivered-To: freebsd-doc@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 8E35ECF0 for ; Mon, 4 Nov 2013 10:10:01 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 6DC6028F7 for ; Mon, 4 Nov 2013 10:10:01 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id rA4AA1s3035200 for ; Mon, 4 Nov 2013 10:10:01 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id rA4AA1VV035199; Mon, 4 Nov 2013 10:10:01 GMT (envelope-from gnats) Resent-Date: Mon, 4 Nov 2013 10:10:01 GMT Resent-Message-Id: <201311041010.rA4AA1VV035199@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, Björn Heidotting Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id BB728C8A for ; Mon, 4 Nov 2013 10:02:10 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from oldred.freebsd.org (oldred.freebsd.org [8.8.178.121]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id A834828BF for ; Mon, 4 Nov 2013 10:02:10 +0000 (UTC) Received: from oldred.freebsd.org ([127.0.1.6]) by oldred.freebsd.org (8.14.5/8.14.7) with ESMTP id rA4A2A45099055 for ; Mon, 4 Nov 2013 10:02:10 GMT (envelope-from nobody@oldred.freebsd.org) Received: (from nobody@localhost) by oldred.freebsd.org (8.14.5/8.14.5/Submit) id rA4A2Aom099016; Mon, 4 Nov 2013 10:02:10 GMT (envelope-from nobody) Message-Id: <201311041002.rA4A2Aom099016@oldred.freebsd.org> Date: Mon, 4 Nov 2013 10:02:10 GMT From: Björn Heidotting To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-3.1 Subject: docs/183653: [patch] Add some more *BSD releases to the groff_mdoc man page X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Nov 2013 10:10:01 -0000 >Number: 183653 >Category: docs >Synopsis: [patch] Add some more *BSD releases to the groff_mdoc man page >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: Mon Nov 04 10:10:00 UTC 2013 >Closed-Date: >Last-Modified: >Originator: Björn Heidotting >Release: 9.2-RELEASE >Organization: >Environment: >Description: Some *BSD releases were missing here for .Os (operating system). Add them. >How-To-Repeat: read groff_mdoc(7) >Fix: A patch is attached to this PR. Patch attached with submission follows: --- groff_mdoc.7 2013-11-04 10:21:14.000000000 +0100 +++ groff_mdoc.7.work 2013-11-04 10:49:35.000000000 +0100 @@ -870,20 +870,22 @@ 0.8, 0.8a, 0.9, 0.9a, 1.0, 1.0a, 1.1, 1.2, 1.2a, 1.2b, 1.2c, 1.2d, 1.2e, 1.3, 1.3a, 1.4, 1.4.1, 1.4.2, 1.4.3, 1.5, 1.5.1, 1.5.2, 1.5.3, 1.6, 1.6.1, 1.6.2, 1.6.3, 2.0, 2.0.1, 2.0.2, 2.0.3, 2.1, 3.0, 3.0.1, 3.0.2, 3.0.3, -3.1, 3.1.1, 4.0, 4.0.1, 5.0, 5.0.1, 5.0.2, 5.1, 6.0 +3.1, 3.1.1, 4.0, 4.0.1, 5.0, 5.0.1, 5.0.2, 5.1, 5.1.2, 5.1.3, 6.0, 6.0.1, +6.0.2, 6.0.3, 6.1, 6.1.1, 6.1.2 .It FreeBSD 1.0, 1.1, 1.1.5, 1.1.5.1, 2.0, 2.0.5, 2.1, 2.1.5, 2.1.6, 2.1.7, 2.2, 2.2.1, 2.2.2, 2.2.5, 2.2.6, 2.2.7, 2.2.8, 3.0, 3.1, 3.2, 3.3, 3.4, 3.5, 4.0, 4.1, 4.1.1, 4.2, 4.3, 4.4, 4.5, 4.6, 4.6.2, 4.7, 4.8, 4.9, 4.10, 4.11, 5.0, 5.1, 5.2, 5.2.1, 5.3, 5.4, 5.5, 6.0, 6.1, 6.2, 6.3, 6.4, 7.0, 7.1, 7.2, 7.3, 8.0, -8.1, 8.2, 9.0 +8.1, 8.2, 9.0, 9.1, 9.2 .It OpenBSD 2.0, 2.1, 2.2, 2.3, 2.4, 2.5, 2.6, 2.7, 2.8, 2.9, 3.0, 3.1, 3.2, 3.3, 3.4, 3.5, 3.6, 3.7, 3.8, 3.9, 4.0, 4.1, 4.2, 4.3, 4.4, 4.5, 4.6, 4.7, 4.8, 4.9, -5.0 +5.0, 5.1, 5.2, 5.3, 5.4 .It DragonFly 1.0, 1.1, 1.2, 1.3, 1.4, 1.5, 1.6, 1.8, 1.8.1, 1.10, 1.12, 1.12.2, 2.0, 2.2, -2.4, 2.6, 2.8, 2.9, 2.9.1, 2.10, 2.10.1, 2.11 +2.4, 2.6, 2.8, 2.9, 2.9.1, 2.10, 2.10.1, 2.11, 3.0, 3.0.1, 3.0.2, 3.0.3, +3.2.1, 3.2.2, 3.4.1, 3.4.2, 3.4.3 .It Darwin 8.0.0, 8.1.0, 8.2.0, 8.3.0, 8.4.0, 8.5.0, 8.6.0, 8.7.0, 8.8.0, 8.9.0, 8.10.0, 8.11.0, 9.0.0, 9.1.0, 9.2.0, 9.3.0, 9.4.0, 9.5.0, 9.6.0, 9.7.0, >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-doc@FreeBSD.ORG Mon Nov 4 11:06:04 2013 Return-Path: Delivered-To: freebsd-doc@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 6A31F48A for ; Mon, 4 Nov 2013 11:06:04 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 568B52BC2 for ; Mon, 4 Nov 2013 11:06:04 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id rA4B64IC047439 for ; Mon, 4 Nov 2013 11:06:04 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id rA4B63t0047437 for freebsd-doc@FreeBSD.org; Mon, 4 Nov 2013 11:06:03 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 4 Nov 2013 11:06:03 GMT Message-Id: <201311041106.rA4B63t0047437@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 Subject: Current unassigned doc problem reports X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Nov 2013 11:06:04 -0000 (Note: an HTML version of this report is available at http://www.freebsd.org/cgi/query-pr-summary.cgi?category=doc .) 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. S Tracker Resp. Description -------------------------------------------------------------------------------- o docs/183653 doc [patch] Add some more *BSD releases to the groff_mdoc o docs/183427 doc Online man pages don't include latest release + ports o docs/183333 doc Misnamed constant in bpf(4) o docs/183246 doc FreeBSD 8.4-RELEASE Installation Instructions don't pr o docs/183024 doc textdump(4) mentions call doadump, should be textdump o docs/183002 doc Fix instructions in "6.5.3. Anti-Aliased Fonts" regard o docs/182876 doc CURRENT release notes webpage out of date and inconsis o docs/182833 doc [porters-handbook]: document QMake usage, update Qt se o docs/182218 doc Add an ipfilter rc.conf option in handbook for IPv6 o docs/182202 doc Handbook pkgng description doesn't mention there are n o docs/181845 doc Virtualbox Host Setup needs acd0 in /etc/devfs.conf, a o docs/181844 doc FreeBSD Handbook Virtualbox Host Section missing confi o docs/181808 doc Chapter 15.15 (Resource Limits) misses important infor o docs/181785 doc [patch] Man page for tmpfile() is inconsistent o docs/181390 doc seq(1) first appeared in 8th UNIX o docs/181376 doc CLOCK_THREAD_CPUTIME_ID is not documented in clock_get o docs/181280 doc suggestion: split zfs man page in a zfs- way o docs/181134 doc Fix example for boot0cfg utility o docs/180970 doc [request] No manpage for ps_strings o docs/180767 doc [patch] printf.3: fix off-by-one in snprintf descripti o docs/180493 doc [handbook] Single-user mode console confusion o docs/180332 doc SSD Kernel Instructions Out of Date: options MFS throw o docs/180331 doc SSD Kernel Instructions Out of Date: options MD_ROOT a o docs/180330 doc SSD Kernel Instructions Out of Date: pseudo-device no o docs/180027 doc Missing man page entries for callout_reset_sbt in time o docs/179988 doc [faq] [patch] ThwackAFAQ - sandbox p docs/179914 doc remove inactive user dougb from mergemaster maintainer o docs/179832 doc manual page of mac_from_text suggests incorrect freein o docs/179697 doc Handbook incomplete WRT Opera flash usage (linproc) o docs/179497 doc [patch] service.8 add csh completion example o docs/179246 doc [patch] gnome porting updates o docs/178818 doc gmirror(8) says to use rc.early which is no longer ava o docs/178730 doc move roff papers out of src into doc o docs/178677 doc *** [article.html] Error code 1 Stop in /usr/doc. o docs/178286 doc [PATCH] document the LOCAL_* vars in build(7) o docs/178221 doc Addition to handbook jails chapter: warning about make o www/178190 doc myths web page should be updated o docs/178119 doc [ports] Porter's handbook lacks examples for using Opt o docs/177968 doc bpf(4): documentation of BIOCROTZBUF is incomplete o docs/177699 doc Documentation (handbook and manpage) for mac_biba does o docs/177514 doc [handbook] ZFS examples do not cover dataset creation o docs/177457 doc diskinfo(8): diskinfo -v shows inacurate drive size o docs/177431 doc Handbook & Announcements recommend poor dd options for o docs/177429 doc dd(1) man page is unclear about semantics of conv=sync o docs/177215 doc [handbook] [patch] FreeBSD uses SHA512 and no more MD5 o docs/176806 doc recv(2) man page grammatical fixes o docs/176648 doc restore(8) man page is misleading/confusing o docs/176645 doc The example in netmap.4 is wrong o docs/176363 doc Remove mention of 'CVSup' from "Mirroring FreeBSD arti o docs/176355 doc Attribution and correction of quote in fortune o docs/176251 doc FreeBSD Handbook assumes too much pre-knowledge o docs/176127 doc [handbook] add information about all missing mailing l o docs/176125 doc missing summary of freebsd-jail mailing list o docs/176123 doc missing summary of freebsd-sysinstall mailing list o docs/176015 doc [handbook] wrong order in docs for major upgrade o docs/175995 doc Setting MALLOC_PRODUCTION stops buildworld o docs/175983 doc man zfs are missing "hold, release" from "zfs allow" o docs/175712 doc Update 'disk naming' handbook page o docs/175687 doc pthread_setschedparam(3) may fail for undocumented rea o docs/175560 doc ugen(4) man page contains incorrect device node path o docs/175239 doc sem_wait can be interrupted o docs/175123 doc [geom] gpart list/status isn't documented in usage sec o docs/174868 doc mount(2) doesn't do a good job at describing all possi o docs/174792 doc synopsis for nsupdate(1) missing options -L, and -p o docs/174581 doc man page of recvmsg(2) does not mention return value 0 o docs/173710 doc Added section "MTP storage" to handbook o docs/173539 doc [patch] statfs(2) man page missed the error code ENOSY o docs/173321 doc ports(7) man page -- no info on building with debuggin o docs/173013 doc FreeBSD Boot Menu documentation lacks detail o docs/172927 doc ipfw(8): ipfw manual page doesn't show simpliest NAT c o docs/172913 doc [ipsec] [patch] setkey(8) is unclear on anti-replay wi o docs/172869 doc [PATCH] Add in nifty lang icons to index.html (home) o docs/172743 doc IPv6 handbooks lacks info about accepting router adver o docs/172626 doc [PATCH] modify the community/* pages to look more plea o docs/172370 doc [handbook] Handbook should be updated for Blu-Ray driv o docs/172369 doc mkisofs(8)/growisofs(1m) don't specify UDF version o docs/172368 doc mount_udf(8) doesn't specify which versions of UDF are o docs/172367 doc ata(4) man page needs an updated for Blu-Ray o docs/172330 doc [PATCH] Fix some errors introduced to announce.xml by o docs/172144 doc psignal(9) manpage is outdated for FreeBSD-9 systems o docs/172137 doc deprecated information for adduser(8) man pages o docs/171199 doc the GDB man page is outdated o docs/170691 doc Difference between zfs manpages and reality o docs/170119 doc at behaviour and man at inconsistency o docs/169712 doc [patch] porters-handbook zh_TW.Big5 apache section o docs/169711 doc [patch] porters-handbook zh_CN.GB2312 apache section o docs/169544 doc serial port console documentation changes s docs/169401 doc passify dead links in release links, move www to lists o docs/169377 doc [patch] ipmon(8) man page refers to a different facili o docs/169317 doc zfs umount refers to umount(1M) but should to umount(8 o docs/169158 doc [patch] iasl(8) man page is out of date f docs/168939 doc Port upgrade documentation missing from Application Ja o docs/168930 doc map_mincore(9) not up-to-date o docs/168915 doc size of integers used by test(1) and sh(1) is not docu o docs/168823 doc 404s in fr_FR French web pages o docs/168814 doc [patch] remove `d` negative pointer EINVAL requirement o docs/168803 doc Remove outdated smp info o docs/167429 doc geli(8) needs to mention unencrypted /etc/fstab requir o docs/166553 doc find(1): find -delete documentation is misleading o docs/166358 doc No networking in Jail build via: handbook/jail-tuning o conf/166330 doc [rc] [patch] Thin server configuration revision reques o docs/165551 doc ipfw(8): no info in "ipfw pipe show" about ipv6 o docs/165249 doc Multibyte characters in manpages still not displaying o docs/164803 doc Unclear manual page for mount_unionfs(8) o docs/164620 doc Raid 1 issues o docs/164099 doc gparm(8): man page for gparm set is incorrect and inco o docs/164034 doc acl(9) documentation lacking o docs/163879 doc [handbook] handbook does not say about how to force to o docs/163830 doc device smbios: missing documentation, no manpage o docs/163149 doc [patch] Red Hat Linux/i386 9 HTML format sudo man page o docs/162765 doc [patch] lseek(2) may return successful although no see o docs/162587 doc unclear/incomplete description of per-interface statis o docs/162419 doc [request] please document (new) zfs and zpool cmdline o docs/162404 doc [handbook] IPv6 link-local address compared with IPv4 o docs/161754 doc p4tcc(4), est(4) and qpi(4) are not documented o docs/161496 doc zfs(1): Please document that sysctl vfs.usermount must o docs/160460 doc [handbook] Network setup guide suggestion o docs/160399 doc Man page for re(4) missing jumbo frames info o docs/159307 doc [patch] lpd smm chapter unconditionally installed o docs/158388 doc Incorrect documentation of LOCAL_SCRIPT in release(7) o docs/158387 doc The tree(3) man should mention the RB_FOREACH_SAFE() A o docs/157908 doc [handbook] Description of post-install should include o docs/157698 doc [patch] gpart(8) man page contains old/incorrect size o docs/157316 doc [patch] update devstat(9) man page o docs/157049 doc FreeBSD Handbook: Chapter 14 (Security) Inaccuracy o docs/156920 doc isspecial(3) is not helpful o docs/156815 doc chmod(1): manpage should describe that chmod kicks +t o docs/156689 doc stf(4) output-only documentation gives bad configurati f docs/156187 doc [handbook] [patch] Add bsnmpd to handbook o docs/156081 doc troff falls with troff.core with UTF-8 man with incorr o docs/155982 doc [handbook] reaper of the dead: remove reference to flo o docs/155149 doc [patch] don't encourage using xorg.conf outside of PRE o docs/154838 doc update cvs-tags information on releng_* to reflect sup o docs/153958 doc ksu man-page documented, but not installed a docs/153012 doc [patch] iostat(8) requires an argument to -c option o docs/151752 doc pw.conf(5) doesn't define format for file clearly o docs/150991 doc [patch] Install upgtfw using pkg_add as advised in upg o docs/150917 doc [patch] icmp.4, wrong description of icmplim and icmpl o docs/150877 doc ambiguity in newsyslog(8) man page about zfs with comp o docs/150255 doc dtrace description should mention makeoptions DEBUG=-g o docs/149574 doc [patch] update mi_switch(9) man page o docs/148987 doc [patch] {MD[245]|SHA_|SHA1_|SHA256_}{End|File|FileChun o docs/148984 doc [handbook] Mistake in section 16.15.4 of the handbook o docs/148680 doc [sysctl][patch] Document some sys/kern sysctls o docs/148071 doc Failover mode between wired and wireless interfaces o docs/147995 doc elf.5 man page has has missing reference o docs/146521 doc [handbook] Update IPv6 system handbook section to ment o docs/145699 doc hexdump(1) mutes all format qualifier output following o docs/145069 doc Dialup firewalling with FreeBSD article out dated. o docs/145066 doc Update for new uart dev names for serial port. s docs/144818 doc all mailinglist archives dated 19970101 contain traili o docs/144515 doc [handbook] Expand handbook Table of contents o docs/143472 doc gethostname(3) references undefined value: HOST_NAME_M o docs/143416 doc [handbook] IPFW handbook page issues o docs/143408 doc man filedesc(9) is missing o docs/141032 doc misleading documentation for rtadvd.conf(5) raflags se s docs/140847 doc [request] add documentation on ECMP and new route args o docs/140444 doc [patch] New Traditional Chinese translation of custom- o docs/140375 doc [UPDATE] Updated zh_TW.Big5/articles/nanobsd o docs/139336 doc [request] ZFS documentation suggestion o docs/139165 doc gssapi.3 man page out of sync with between crypto and o docs/139018 doc translation of submitting.sgml from docproj/submitting o docs/138845 doc Exceeding kern.ipc.maxpipekva refers to tuning(7) whic o docs/138485 doc bpf(4) and ip(4) man pages missing important corner ca o docs/136712 doc [handbook] [patch] draft new section on gmirror per pa o docs/136666 doc [handbook] Configure serial port for remote kernel deb o docs/136035 doc ftpchroot(5) omits an important option o docs/135516 doc [patch] pax(1) manual not mentioning chflags unawarene o docs/132839 doc [patch] Fix example script in ldap-auth article o docs/132718 doc [handbook] Information about adding a new mirror is ou o docs/132260 doc dhcpd(8) pid not stored in documented location o docs/132190 doc EPERM explanation for send(2), sendto(2), and sendmsg( o docs/131918 doc [patch] Fixes for the BPF(4) man page o docs/131626 doc [patch] dump(8) "recommended" cache option confusing o docs/130238 doc nfs.lockd man page doesn't mention NFSLOCKD option or o docs/129671 doc New TCP chapter for Developer's Handbook (from rwatson o docs/129464 doc using packages system o docs/129095 doc ipfw(8): Can not check that packet originating/destine o docs/128356 doc [request] add Firefox plugin for FreeBSD manual pages s docs/127844 doc Example code skeleton_capture_n.c in meteor(4) manpage o docs/126484 doc libc function res-zonscut2 is not documented f docs/122052 doc minor update on handbook section 20.7.1 o docs/121952 doc Handbook chapter on Network Address Translation wrong o docs/121585 doc [handbook] Wrong multicast specification s docs/121541 doc [request] no man pages for wlan_scan_ap o docs/121312 doc RELNOTES_LANG breaks release if not en_US.ISO8859-1 o docs/121173 doc [patch] mq_getattr(2): mq_flags mistakenly described a s docs/120917 doc [request]: Man pages mising for thr_xxx syscalls o docs/120125 doc [patch] Installing FreeBSD 7.0 via serial console and o docs/120024 doc resolver(5) and hosts(5) need updated for IPv6 o docs/119545 doc books/arch-handbook/usb/chapter.sgml formatting o docs/118214 doc close(2) error returns incomplete o docs/116588 doc No IPFW tables or dummynet in Handbook o docs/116080 doc PREFIX is documented, but not the more important LOCAL o docs/114371 doc [patch] [ip6] rtadvd.con(5) should show how to adverti o docs/114139 doc mbuf(9) has misleading comments on M_DONTWAIT and M_TR o docs/113194 doc [patch] [request] crontab.5: handling of day-in-month o docs/112579 doc [request] No ipv6 related pf examples in /usr/share/ex o docs/111425 doc Missing chunks of text in historical manpages o docs/111265 doc [request] Clarify how to set common shell variables o docs/110999 doc carp(4) should document unsupported interface types o docs/110692 doc wi(4) man page doesn't say WPA is not supported o docs/110376 doc [patch] add some more explanations for the iwi/ipw fir o docs/110062 doc [patch] mount_nfs(8) fails to mention a failure condit o docs/109981 doc No manual entry for post-grohtml o docs/109977 doc No manual entry for ksu o docs/109972 doc No manual entry for zless/bzless f docs/109226 doc [request] No manual entry for sntp o docs/109201 doc [request]: manual for callbootd a docs/108980 doc list of missing man pages o docs/105608 doc fdc(4) debugging description staled o docs/104879 doc Howto: Listen to IMA ADPCM .wav files on FreeBSD box o docs/102719 doc [patch] ng_bpf(4) example leads to unneeded promiscuos o docs/101271 doc serial console documentation implies kernel rebuild re p docs/100196 doc man login.conf does explain not "unlimited" o docs/98974 doc Missing tunables in loader(8) manpage o docs/98115 doc Missing parts after rendering handbook to RTF format o docs/96207 doc Comments of a sockaddr_un structure could confuse one o docs/95408 doc install over serial console does not work as documente o docs/94625 doc [patch] growfs man page -- document "panic: not enough o docs/92626 doc jail manpage should mention disabling some periodic sc o docs/91149 doc read(2) can return EINVAL for unaligned access to bloc o docs/88512 doc [patch] mount_ext2fs(8) man page has no details on lar o docs/87936 doc Handbook chapter on NIS/YP lacks good information on a o docs/87857 doc ifconfig(8) wireless options order matters o docs/85128 doc [patch] loader.conf(5) autoboot_delay incompletly desc o docs/84956 doc [patch] intro(5) manpage doesn't mention API coverage o docs/84932 doc new document: printing with an Epson ALC-3000N on Free o docs/84670 doc [patch] tput(1) manpage missing ENVIRONMENT section wi o docs/84317 doc fdp-primer doesn't show class=USERNAME distinctively o docs/84271 doc [patch] compress(1) doesn't warn about nasty link hand o docs/83820 doc getino(3) manpage not installed o docs/81611 doc [patch] natd runs with -same_ports by default o docs/78480 doc Networked printer setup unnecessarily complex in handb o docs/61301 doc [patch] Manpage patch for aue(4) to enable HomePNA fun o docs/59835 doc ipfw(8) man page does not warn about accepted but mean o docs/59477 doc Outdated Info Documents at http://docs.freebsd.org/inf o docs/57298 doc [patch] add using compact flash cards info to handbook s docs/54752 doc bus_dma explained in ISA section in Handbook: should b o docs/53751 doc bus_dma(9) incorrectly documents BUS_DMA_ALLOCNOW o docs/53596 doc Updates to mt(1) manual page o docs/53271 doc bus_dma(9) fails to document alignment restrictions o docs/51480 doc Multiple undefined references in the FreeBSD manual pa o kern/51341 doc [ipfw] [patch] ipfw rule 'deny icmp from any to any ic o docs/50211 doc [patch] doc.docbook.mk: fix textfile creation o docs/48101 doc [patch] Add documentation on the fixit disk o docs/47594 doc [patch] passwd(5) incorrectly states allowed username o docs/45303 doc Bug in PDF DocBook rendering o docs/43823 doc [patch] update to environ(7) manpage o docs/41089 doc pax(1) -B option does not mention interaction with -z o docs/40423 doc Keyboard(4)'s definition of parameters to GETFKEY/SETF o docs/36724 doc ipnat(5) manpage grammar is incomplete and inconsisten s docs/33589 doc [patch] to doc.docbook.mk to post process .tex files. o docs/26286 doc *printf(3) etc should gain format string warnings o docs/24786 doc missing FILES descriptions in sa(4) s docs/20028 doc ASCII docs should reflect tags in the sourc 256 problems total. From owner-freebsd-doc@FreeBSD.ORG Mon Nov 4 13:30:02 2013 Return-Path: Delivered-To: freebsd-doc@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 3B6F5B2A for ; Mon, 4 Nov 2013 13:30:02 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 0F80C2574 for ; Mon, 4 Nov 2013 13:30:02 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id rA4DU1Ju084446 for ; Mon, 4 Nov 2013 13:30:01 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id rA4DU1G5084445; Mon, 4 Nov 2013 13:30:01 GMT (envelope-from gnats) Date: Mon, 4 Nov 2013 13:30:01 GMT Message-Id: <201311041330.rA4DU1G5084445@freefall.freebsd.org> To: freebsd-doc@FreeBSD.org Cc: From: Bjoern Heidotting Subject: Re: docs/183653: [patch] Add some more *BSD releases to the groff_mdoc man page X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: Bjoern Heidotting List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Nov 2013 13:30:02 -0000 The following reply was made to PR docs/183653; it has been noted by GNATS. From: Bjoern Heidotting To: bug-followup@FreeBSD.org, b.heidotting@yahoo.com Cc: Subject: Re: docs/183653: [patch] Add some more *BSD releases to the groff_mdoc man page Date: Mon, 04 Nov 2013 14:26:51 +0100 Oops. I missed at least FreeBSD 8.3 and 8.4 in the patch. From owner-freebsd-doc@FreeBSD.ORG Mon Nov 4 20:09:59 2013 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 29756681 for ; Mon, 4 Nov 2013 20:09:59 +0000 (UTC) (envelope-from juris.kaminskis@gmail.com) Received: from mail-we0-x22d.google.com (mail-we0-x22d.google.com [IPv6:2a00:1450:400c:c03::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id B8D3A2F44 for ; Mon, 4 Nov 2013 20:09:58 +0000 (UTC) Received: by mail-we0-f173.google.com with SMTP id u57so2560916wes.4 for ; Mon, 04 Nov 2013 12:09:57 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=KgEliMLu9ubbl82j3e004xCnOMof2vOE9Nh28nU7PpA=; b=prM/qylQmY7wvG080uetW3naHh/wJEFx1/Sqa7sWq5tLv/Npf8bPS9c/9eE/y3KAbo lRm0U9Q1fyEqzDA+0/36s42zF1+v1IE8iMoIEWCU7yeHyuWd0Fwr4+LajA/T8p8hgtgd n9elW3WKglcmOxzXZZgDzgDan1EMOh1KJfUDW6mrDnRWqeFtEpB9j2jM6grgodbYgAbm 5M6Rfu9qxl+GBYKqIig67o1QlSj27mbVcmPJWFQdIY/LgGXScvD6HVuhqXo7Q24KoWLv iY8+uY70D+uOP8ar8iIYowpoJRQQHXw5o+koHpcPVxjSK1FPjRm/VSudzaVDwZAGu8EV lIQw== MIME-Version: 1.0 X-Received: by 10.194.93.105 with SMTP id ct9mr14555359wjb.6.1383595797208; Mon, 04 Nov 2013 12:09:57 -0800 (PST) Received: by 10.194.185.101 with HTTP; Mon, 4 Nov 2013 12:09:57 -0800 (PST) In-Reply-To: References: Date: Mon, 4 Nov 2013 22:09:57 +0200 Message-ID: Subject: Re: TODO item: Add info on USB printers From: Juris Kaminskis To: Warren Block Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: freebsd-doc@freebsd.org X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Nov 2013 20:09:59 -0000 > Thank you for working on this. The entire printing chapter really needs a >> rewrite, and I've been meaning to write an outline for what a new printing >> chapter should cover. In the meantime, please look at >> http://www.wonkity.com/~wblock/docs/html/lpdprinting.html and see if it >> is adequate in the meantime. >> > I am not sure I understand what should I do next from this. Can you let me know how can I contribute further? From owner-freebsd-doc@FreeBSD.ORG Tue Nov 5 03:35:18 2013 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 6EB9233B for ; Tue, 5 Nov 2013 03:35:18 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 13ED127D2 for ; Tue, 5 Nov 2013 03:35:17 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.7/8.14.7) with ESMTP id rA53ZGtN054299; Mon, 4 Nov 2013 20:35:16 -0700 (MST) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.7/8.14.7/Submit) with ESMTP id rA53ZG46054296; Mon, 4 Nov 2013 20:35:16 -0700 (MST) (envelope-from wblock@wonkity.com) Date: Mon, 4 Nov 2013 20:35:16 -0700 (MST) From: Warren Block To: Juris Kaminskis Subject: Re: TODO item: Add info on USB printers In-Reply-To: Message-ID: References: User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="3512871622-1629944230-1383622516=:53066" X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (wonkity.com [127.0.0.1]); Mon, 04 Nov 2013 20:35:16 -0700 (MST) Cc: freebsd-doc@freebsd.org X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Nov 2013 03:35:18 -0000 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --3512871622-1629944230-1383622516=:53066 Content-Type: TEXT/PLAIN; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8BIT On Mon, 4 Nov 2013, Juris Kaminskis wrote: > > Thank you for working on this.  The entire printing chapter really needs a rewrite, and I've been meaning to write an outline for what a new printing chapter > should cover.  In the meantime, please look at > http://www.wonkity.com/~wblock/docs/html/lpdprinting.html and see if it is adequate in the meantime. > > > I am not sure I understand what should I do next from this. Can you let me know how can I contribute further? I've done some preliminary work on a rewrite of the printing chapter. Can you look at the article above and see if anything important is left out? Thanks! --3512871622-1629944230-1383622516=:53066-- From owner-freebsd-doc@FreeBSD.ORG Tue Nov 5 05:08:48 2013 Return-Path: Delivered-To: freebsd-doc@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 634CEC51 for ; Tue, 5 Nov 2013 05:08:48 +0000 (UTC) (envelope-from freebsd@allanjude.com) Received: from mx1.scaleengine.net (beauharnois2.bhs1.scaleengine.net [142.4.218.15]) by mx1.freebsd.org (Postfix) with ESMTP id 2C3432BBD for ; Tue, 5 Nov 2013 05:08:47 +0000 (UTC) Received: from [10.1.1.1] (S01060001abad1dea.hm.shawcable.net [50.70.108.129]) (Authenticated sender: allan.jude@scaleengine.com) by mx1.scaleengine.net (Postfix) with ESMTPSA id 4373744C1F for ; Tue, 5 Nov 2013 05:08:45 +0000 (UTC) Message-ID: <52787D62.5020607@allanjude.com> Date: Tue, 05 Nov 2013 00:08:50 -0500 From: Allan Jude User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0 MIME-Version: 1.0 To: freebsd-doc@FreeBSD.org Subject: ZFS Handbook Update X-Enigmail-Version: 1.6 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="sSWk50K8CUtjruQCeBXPH3Rk6OfCLssuk" X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Nov 2013 05:08:48 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --sSWk50K8CUtjruQCeBXPH3Rk6OfCLssuk Content-Type: multipart/mixed; boundary="------------000608030202070600010905" This is a multi-part message in MIME format. --------------000608030202070600010905 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Attached find ~320 new lines and 87 modified lines of the ZFS chapter of the FreeBSD Handbook that I wrote on the plane to and from the FreeBSD 20th Anniversary Party. Note: this is for, and is a patch against, the projects/zfsupdate-201307 branch. --=20 Allan Jude --------------000608030202070600010905 Content-Type: text/plain; charset=windows-1252; name="zfs_freebsdparty_content.patch" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="zfs_freebsdparty_content.patch" Index: projects/zfsupdate-201307/en_US.ISO8859-1/books/handbook/zfs/chapt= er.xml =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- projects/zfsupdate-201307/en_US.ISO8859-1/books/handbook/zfs/chapter.= xml (revision 43100) +++ projects/zfsupdate-201307/en_US.ISO8859-1/books/handbook/zfs/chapter.= xml (working copy) @@ -22,22 +22,35 @@ Reuschling Written by + + Warren + Block + Written by + =20 The Z File System (<acronym>ZFS</acronym>) =20 The Z File System - (ZFS) was developed at &sun; to address many of - the problems with current file systems. There were three major - design goals: + (ZFS) was originally developed at &sun; to + address many of the problems with then current file systems. + Development has since moved to the Open-ZFS Project. For more on + past and future development, see + .. The three major design + goals of ZFS are: =20 - Data integrity: checksums are created when data is written - and checked when data is read. If on-disk data corruption is - detected, the user is notified and recovery methods are - initiated. + Data integrity: All data that is stored on + ZFS includes a checksum of the data. When + data is written the checksum is calculated and written along + with the data. When that data is later read back, the + checksum is calculated again and if the values do not match an + error is returned. ZFS will attempt to + automatically correct the error if there is sufficient + redundancy available. =20 @@ -48,7 +61,13 @@ =20 - Performance: + Performance: ZFS features a number of + optional caching mechanisms to provide increased performance. + In addition to an advanced read cache known as the ARC in memory, there is also the + optional L2ARC read + cache and the ZIL + synchronous write cache. =20 @@ -360,13 +379,15 @@ =20 &prompt.root; zpool status -x =20 - If all pools are healthy and everything is normal, the - message indicates that: + If all pools are Online and everything is + normal, the message indicates that: =20 all pools are healthy =20 - If there is an issue, perhaps a disk has gone offline, - the pool state will look similar to: + If there is an issue, perhaps a disk is in the Offline state, the pool + state will look similar to: =20 pool: storage state: DEGRADED @@ -474,7 +495,14 @@ <command>zpool</command> Administration =20 - + The administration of ZFS is divided between two main + utilities. The zpool utility which controls + the operation of the pool and deals with adding, removing, + replacing and managing disks, and the zfs utility, which + deals with creating, destroying and managing datasets (both + filesystems and volumes). =20 Creating & Destroying Storage Pools @@ -496,7 +524,15 @@ instead the data must be backed up and the pool recreated. =20 - + A ZFS pool that is no longer needed can be destroyed so + that the disks making up the pool can be reused in another + pool or for other purposes. Destroying a pool involves + unmouting all of the datasets in that pool. If the datasets + are in use, the unmount operation will fail and the pool will + not be destroyed. The destruction of the pool can be forced + with the parameter, however this can cause + undefined behavior in the applications which had open files on + those datasets. =20 @@ -504,9 +540,9 @@ =20 Adding disks to a zpool can be broken down into two separate cases: attaching a disk to an - existing vdev with the zpool attach - command, or adding vdevs to the pool with the - zpool add command. Only some + existing vdev with zpool attach, + or adding vdevs to the pool with=20 + zpool add. Only some vdev types allow disks to be added to the vdev after creation. =20 @@ -525,23 +561,16 @@ can only be removed from a mirror if there is enough remaining redundancy. =20 - Creating a ZFS Storage Pool (zpool) - involves making a number of decisions that are relatively - permanent. Although additional vdevs can be added to a pool, - the layout of the pool cannot be changed once the pool has - been created, instead the data must be backed up and the pool - recreated. Currently, devices cannot be removed from a - zpool. =20 - Replacing a Working Devices + Replacing a Functioning Device =20 There are a number of situations in which it may be desirable to replace a disk with a different disk. This process requires connecting the new disk at the same time as - the disk to be replaced. The - zpool replace command will copy all of the + the disk to be replaced. + zpool replace will copy all of the data from the old disk to the new one. After this operation completes, the old disk is disconnected from the vdev. If the new disk is larger than the old disk, it may be possible to grow the zp= ool, using the new space. See @@ -551,12 +580,27 @@ Dealing with Failed Devices =20 - When a disk fails and the physical device is replaced, ZFS - must be told to begin the When a disk in a ZFS pool fails, the vdev that the disk + belongs to will enter the Degraded state. In this + state, all of the data stored on the vdev is still available, + but performance may be impacted because missing data will need + to be calculated from the available redundancy. To restore + the vdev to a fully functional state the failed physical + device will need to be replace replaced, and ZFS must be + instructed to begin the resilver operation, where data that was on the failed device will be recalculated - from the available redundancy and written to the new - device. + from the available redundancy and written to the replacement + device. Once this process has completed the vdev will return + to Online status. If + the vdev does not have any redundancy, or if multiple devices + have failed and there is insufficient redundancy to + compensate, the pool will enter the Faulted state. If a + sufficient number of devices cannot be reconnected to the pool + then the pool will be inoperative, and data will need to be + restored from backups. =20 @@ -565,12 +609,14 @@ The usable size of a redundant ZFS pool is limited by the size of the smallest device in the vdev. If each device in the vdev is= replaced sequentially, after the smallest device - has completed the replace or resilver operation, the pool + has completed the replace or resilver operation, the pool can grow based on the size of the new smallest device. - This expansion can be triggered with the - zpool online command with the -e flag on + This expansion can be triggered by using zpool + online with on each device. After the expansion of each device, - the additional space will be available in the pool. + the additional space will become available in the pool. =20 @@ -585,7 +631,8 @@ &man.zpool.8;). When a dataset has open files, can= be used to force the export of a pool. causes the datasets to be forcibly - unmounted. This can have unexpected side effects. + unmounted, which can cause undefined behavior in the + applications which had open files on those datasets. =20 Importing a pool automatically mounts the datasets. This may not be the desired behavior, and can be prevented with -N. @@ -604,16 +651,17 @@ =20 After upgrading &os;, or if a pool has been imported from a system using an older version of ZFS, the pool - must be manually upgraded to the latest version of ZFS. This - process is unreversible. Consider whether the pool may ever need - to be imported on an older system before upgrading. An upgrade + can be manually upgraded to the latest version of ZFS. + Consider whether the pool may ever need=20 + to be imported on an older system before upgrading. + The upgrade process is unreversible and cannot be undone. =20 The newer features of ZFS will not be available until - the zpool upgrade command has completed. - will the newer features of ZFS be available. + zpool upgrade has completed. can be used to see what new - features will be provided by upgrading. + features will be provided by upgrading, as well as which features are a= lready + supported by the existing version. =20 @@ -627,11 +675,13 @@ =20 ZFS has a built-in monitoring system that can display statistics about I/O happening on the pool in real-time. - Additionally, it shows the free and used space on the pool and - how much I/O bandwidth is currently utilized for read and - write operations. By default, all pools in the system will be - monitored and displayed. A pool name can be provided to monitor - just that single pool. A basic example: + It shows the amount of free and used space on the pool, how + many read and write operations are being performed per second, + and how much I/O bandwidth is currently being utilized for + read and write operations. By default, all pools in the system will be= + monitored and displayed. A pool name can be provided=20 + as part of the command to monitor just that specific + pool. A basic example: =20 &prompt.root; zpool iostat capacity operations bandwidth @@ -639,8 +689,9 @@ ---------- ----- ----- ----- ----- ----- ----- data 288G 1.53T 2 11 11.3K 57.1K =20 - To continuously monitor I/O activity on the pool, specify - a number as the last parameter, indicating the number of seconds + To continuously monitor I/O activity on the pool, + a number can be specified as the last parameter, indicating + the frequency in seconds=20 to wait between updates. ZFS will print the next statistic line after each interval. Press =20 Even more detailed pool I/O statistics can be - displayed with parameter. - Each storage device in the pool will be shown with a - separate statistic line. This is helpful to - determine reads and writes on devices that slow down I/O on - the whole pool. The following example shows a - mirrored pool consisting of two devices. For each of these, - a separate line is shown with the current I/O - activity. + displayed with . In this case=20 + each storage device in the pool will be shown with a + corresponding statistics line. This is helpful to + determine how many read and write operations are being + performed on each device, and can help determine if any + specific device is slowing down I/O on the entire pool. The + following example shows a mirrored pool consisting of two + devices. For each of these, a separate line is shown with + the current I/O activity. =20 &prompt.root; zpool iostat -v capacity operations bandwidth @@ -674,25 +726,86 @@ Splitting a Storage Pool =20 - + A ZFS pool consisting of one or more mirror vdevs can be + split into a second pool. The last member of each mirror + (unless otherwise specified) is detached and used to create a + new pool containing the same data. It is recommended that + the operation first be attempted with the + parameter. This will print out the details of the proposed + operation without actually performancing it. This helps + ensure the operation will happen as expected. =20 <command>zfs</command> Administration =20 - + The zfs utility is responsible for + creating, destroying, and managing all ZFS + datasets that exist within a pool. The pool is managed using + the zpool + command. =20 Creating & Destroying Datasets =20 - + Unlike with traditional disks and volume managers, space + in ZFS is not preallocated, allowing + additional file systems to be created at any time. With + traditional file systems, once all of the space was + partitioned and assigned to a file system, there was no way to + add an additional file system without adding a new disk. + ZFS also allows you to set a number of + properties on each dataset. These properties + include features like compression, deduplication, caching and + quoteas, as well as other useful properties like readonly, + case sensitivity, network file sharing and mount point. Each + separate dataset can be administered, delegated, replicated, snapshoted, jailed, and destroyed as a unit. + This offers many advantages to creating a separate dataset for + each different type or set of files. The only drawback to + having an extremely large number of datasets, is that some + commands like zfs list will be slower, + and the mounting of an extremely large number of datasets + (100s or 1000s) can make the &os; boot process take + longer. + + Destroying a dataset is much quicker than deleting all + of the files that reside on the dataset, as it does not + invole scanning all of the files and updating all of the + corresponding metadata. In modern versions of + ZFS the zfs destroy + operation is asynchronous, the free space may take several + minutes to appear in the pool. The freeing + property, accessible with zpool get freeing + poolname indicates how + many datasets are having their blocks freed in the background. + If there are child datasets, such as snapshots or other + datasets, then the parent cannot be destroyed. To destroy a + dataset and all of its children, use the + parameter to recursively destroy the dataset and all of its + children. The parameters can be used + to not actually perform the destruction, but instead list + which datasets and snapshots would be destroyed and in the + case of snapshots, how much space would be reclaimed by + proceeding with the destruction. =20 Creating & Destroying Volumes =20 - + A volume is special type of ZFS + dataset. Rather than being mounted as a file system, it is + exposed as a block device under + /dev/zvol/poolname/= dataset. + This allows the volume to be used for other file systems, to + back the disks of a virtual machine, or to be exported using + protocols like iSCSI or HAST. =20 A volume can be formatted with any filesystem on top of it. This will appear to the user as if they are working with @@ -714,18 +827,46 @@ /dev/zvol/tank/fat32 249M 24k 249M 0% /mnt &prompt.root; mount | grep fat32 /dev/zvol/tank/fat32 on /mnt (msdosfs, local) + + Destroying a volume is much the same as destroying a + regular filesystem dataset. The operation is nearly + instantaneous, but it make take several minutes for the free + space to be reclaimed in the background. + =20 Renaming a Dataset =20 - + The name of a dataset can be changed using zfs + rename. The rename command can also be used to + change the parent of a dataset. Renaming a dataset to be + under a different parent dataset will change the value of + those properties that are inherited by the child dataset. + When a dataset is renamed, it is unmounted and then remounted + in the new location (inherited from the parent dataset). This + behavior can be prevented using the + parameter. Due to the nature of snapshots, they cannot be + renamed outside of the parent dataset. To rename a recursive + snapshot, specify the parameter, and all + snapshots with the same specified snapshot will be + renamed. =20 Setting Dataset Properties =20 - + Each ZFS dataset has a number of + properties to control its behavior. Most properties are + automatically inherited from the parent dataset, but can be + overridden locally. Set a property on a dataset with + zfs set + property=3Dvalue + dataset. Most properties + have a limited set of valid values, zfs get + will display each possible property and its valid values. + Most properties can be reverted to their inherited values + using zfs inherit. =20 It is possible to set user-defined properties in ZFS. They become part of the dataset configuration and can be used @@ -743,13 +884,55 @@ Managing Snapshots =20 - + Snapshots are one= + of the most powerful features of ZFS. A + snapshot provides a point-in-time copy of the dataset that the + parent dataset can be rolled back to if required. Create a + snapshot with zfs snapshot + dataset@snapshotname. + Specifying the parameter will recursively + create a snapshot with the same name on all child + datasets. + + By default, snapshots are mounted in a hidden directory + under the parent dataset: .zfs/snapshots/snapshotname. + Individual files can easily be restored to a previous state by + copying them from the snapshot back to the parent dataset. It + is also possible to revert the entire dataset back to the + point-in-time of the snapshot using zfs + rollback. + + Snapshots consume space based on how much the parent file + system has changed since the time of the snapshot. The + written property of a snapshot tracks how + much space is being used by a snapshot. + + To destroy a snapshot and recover the space consumed by + the overwritten or deleted files, run zfs destroy + dataset@snapshot<= /command>. + The parameter will recursively remove all + snapshots with the same name under the parent dataset. Adding + the parameters to the destroy command + will display a list of the snapshots that would be deleted and + an estimate of how much space would be reclaimed by proceeding + with the destroy operation. =20 Managing Clones =20 - + A clone is a copy of a snapshot that is treated more like + a regular dataset. Unlike a snapshot, a clone is not read + only, is mounted, and can have its own properties. Once a + clone has been created, the snapshot it was created from + cannot be destroyed. The child/parent relationship between + the clone and the snapshot can be reversed using zfs + promote. After a clone has been promoted, the + snapshot becomes a child of the clone, rather than of the + original parent dataset. This will change how the space is + accounted, but not actually change the amount of space + consumed. =20 @@ -761,6 +944,18 @@ Dataset, User and Group Quotas =20 + Dataset + quotas can be used to restrict the amount of space + that can be consumed by a peticular dataset. Reference Quotas work in + very much the same way, except they only count the space used + by the dataset it self, excluding snapshots and child + datasets. Similarly user and group quotas can be used + to prevent users or groups from consuming all of the available + space in the pool or dataset. + To enforce a dataset quota of 10 GB for storage/home/bob, use the following: @@ -861,7 +1056,13 @@ Reservations =20 - + Reservations + guarantee a minimum amount of space will always be available + to a dataset. The reserved space will not + be available to any other dataset. This feature can be + especially useful to ensure that users cannot comsume all of + the free space, leaving none for an important dataset or log + files. =20 The general format of the reservation property is @@ -878,7 +1079,8 @@ =20 The same principle can be applied to the refreservation property for setting a - refreservation, with the general format + Reference + Reservation, with the general format refreservation=3Dsize. =20 To check if any reservations or refreservations exist on @@ -898,7 +1100,18 @@ Deduplication =20 - + When enabled, Deduplication uses + the checksum of each block to detect duplicate blocks. When a + new block is about to be written and it is determined to be a + duplicate of an existing block, rather than writing the same + data again, ZFS just references the + existing data on disk an additional time. This can offer + tremendous space savings if your data contains many discreet + copies of the file information. Deduplication requires an + extremely large amount of memory, and most of the space + savings can be had without the extra cost by enabling + compression instead. =20 To activate deduplication, you simply need to set the following property on the target pool. @@ -986,6 +1199,22 @@ thumb, compression should be used first before deduplication due to the lower memory requirements. + + + ZFS and Jails + + zfs jail and the corresponding + jailed property are used to delegate a + ZFS dataset to a Jail. zfs jail + jailid attaches a dataset + to the specified jail, and the zfs unjail + detaches it. In order for the dataset to be administered from + within a jail, the jailed property must be + set. Once a dataset is jailed it can no longer be mounted on + the host, because the jail administrator may have set + unacceptable mount points. + =20 @@ -1170,6 +1399,12 @@ Best Practices Guide + + + History of <acronym>ZFS</acronym> + + + =20 @@ -1344,28 +1579,23 @@ Log - ZFS Log Devices, also known as ZFS Intent Log - (ZIL) move the intent log from - the regular pool devices to a dedicated device. - The ZIL accelerates synchronous - transactions by using storage devices (such as - SSDs) that are faster than - those used for the main pool. When data is being - written and the application requests a guarantee - that the data has been safely stored, the data is - written to the faster ZIL - storage, then later flushed out to the regular - disks, greatly reducing the latency of synchronous - writes. Log devices can be mirrored, but - RAID-Z is not supported. If - multiple log devices are used, writes will be load - balanced across them. + (ZIL) mov= e the intent log from + the regular pool devices to a dedicated device, + typically an SSD. + Having a dedicated log + device can significantly improve the performance + of applications with a high volume of synchronous + writes, especially databases. Log devices can be + mirrored, but RAID-Z is not + supported. If multiple log devices are used, + writes will be load balanced across them. =20 Cache - Adding a cache vdev to a zpool will add the storage of the cache to - the L2ARC. Cache devices + the L2ARC. Cache devices cannot be mirrored. Since a cache device only stores additional copies of existing data, there is no risk of data loss. @@ -1446,6 +1676,26 @@ =20 + ZIL + + The ZIL accelerates synchronous + transactions by using storage devices (such as + SSDs) that are faster than those used + for the main storage pool. When data is being written + and the application requests a synchronous write (a + guarantee that the data has been safely stored to disk + rather than only cached to be written later), the data + is written to the faster ZIL storage, + then later flushed out to the regular disks, greatly + reducing the latency and increasing performance. + Only workloads that are synchronous such as databases + will benefit from a ZIL. Regular + asynchronous writes such as copying files will not use + the ZIL at all. + + + Copy-On-Write =20 Unlike a traditional file system, when data is @@ -1481,12 +1731,24 @@ properties on a child to override the defaults inherited from the parents and grandparents. ZFS also allows administration of - datasets and their children to be delegated. + datasets and their children to be delegated. =20 - Volume + Filesystem =20 + A ZFS dataset is most often used + as a file system. Like most other file systems, a + ZFS file system is mounted somewhere + in the systems directory heirarchy and contains files + and directories of its own with permissions, flags and + other metadata. + + + + Volume + In additional to regular file system datasets, ZFS can also create volumes, which are block devices. Volumes have many of the same @@ -1802,6 +2064,63 @@ remaining drives) to the new drive is called resilvering. + + + Online + + A ZFS pool or vdev that is in the + Online state has all of its member + devices connected and fully operational. Individual + devices in the Online state are + functioning normally. + + + + Offline + + Individual devices can be put in an + Offline state by the administrator if + there is sufficient redundancy to avoid putting the pool + or vdev into a Faulted state. An + administrator may choose to offline a disk in + preperation for replacing it, or to make it easier to + identify. + + + + Degraded + + A ZFS pool or vdev that is in the + Degraded state has one or more disks + that have been disconnected or have failed. The pool is + still usable however if additional devices fail the pool + could become unrecoverable. Reconnecting the missing + device(s) or replacing the failed disks will return the + pool to a Online state after + the reconnected or new device has completed the Resilver + process. + + + + Faulted + + A ZFS pool or vdev that is in the + Faulted state is no longer + operational and the data residing on it can no longer + be accessed. A pool or vdev enters the + Faulted state when the number of + missing or failed devices exceeds the level of + redundancy in the vdev. If missing devices can be + reconnected the pool will return to a Online state. If + there is insufficient redundancy to compensate for the + number of failed disks, then the contents of the pool + are lost and will need to be restored from + backups. + --------------000608030202070600010905-- --sSWk50K8CUtjruQCeBXPH3Rk6OfCLssuk Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (MingW32) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJSeH1lAAoJEJrBFpNRJZKfdhgQAKIJ49QJ2ziq+vfxf4crnNIX T4fndNnaFRIZPQvx2lfgSV93XXCnNr+YBplqVnDHEOX/FsnGwwQGOfcrqfxM2Lyb 45DghQkR+siNahKT8v5DrEjM64hvDnEFvQgf6em1lL9XbAAxLc9HqXqS9hAOucIB KAr726OiETVEzWyc5YDJLhDxTy1hN2Kldqeuhasta32D0FOAm3Q7/vsh9yYdX08j Z35/7i534ro/vGDxRhoVRjfJne3c/vTFKDcrfdqVtKqCl3cLolfup+RZxYY5j1Op L7jm4m5OxdqQPXij5c2bYRM/ydxg8UdR2MVo65MWqrsyzAaq+SLpW4Cr3dU1dn2v DLui0PTSj6V5hcTQWjxlRwf1mOYjOjRi2SpNUrvR2NNZwxtfHKSX0T3D1s/cy4z+ 8lHRmHOdQY4ZaR5dWRghvGE711DFhWrd/hrSBW3U3PKA47VBnnVsIwfKRMG7BEzZ kTSxEeNDnmvGXLv4gRpNz1EjYW9PaQ72/jyiQIIiOgPQ6qhTrriyjBxt/3MICn7y SKQs3I5pe9OCHBCt8I2KBHfs3P87+Bsdd02+aL8NlN2mRhBkMd3S/qYvGdiqGcxg mtRj/mTLOxEKEruc6iwjdSNq5gameD/vUoc5PvHbQhBbund2ZeIpOSSfdJnPTvr5 mXmoA+yc08w20WsK/ejG =izMj -----END PGP SIGNATURE----- --sSWk50K8CUtjruQCeBXPH3Rk6OfCLssuk-- From owner-freebsd-doc@FreeBSD.ORG Tue Nov 5 05:14:35 2013 Return-Path: Delivered-To: freebsd-doc@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 1F6F1E05 for ; Tue, 5 Nov 2013 05:14:35 +0000 (UTC) (envelope-from freebsd@allanjude.com) Received: from mx1.scaleengine.net (beauharnois2.bhs1.scaleengine.net [142.4.218.15]) by mx1.freebsd.org (Postfix) with ESMTP id D8C462C0F for ; Tue, 5 Nov 2013 05:14:33 +0000 (UTC) Received: from [10.1.1.1] (S01060001abad1dea.hm.shawcable.net [50.70.108.129]) (Authenticated sender: allan.jude@scaleengine.com) by mx1.scaleengine.net (Postfix) with ESMTPSA id A23CF44C35 for ; Tue, 5 Nov 2013 05:14:32 +0000 (UTC) Message-ID: <52787EBE.5040100@allanjude.com> Date: Tue, 05 Nov 2013 00:14:38 -0500 From: Allan Jude User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0 MIME-Version: 1.0 To: freebsd-doc@FreeBSD.org Subject: Re: ZFS Handbook Update References: <52787D62.5020607@allanjude.com> In-Reply-To: <52787D62.5020607@allanjude.com> X-Enigmail-Version: 1.6 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="EtQxoST8mRoe0mtPQEpKncolooom9QPMo" X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Nov 2013 05:14:35 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --EtQxoST8mRoe0mtPQEpKncolooom9QPMo Content-Type: multipart/mixed; boundary="------------060300010504090803090809" This is a multi-part message in MIME format. --------------060300010504090803090809 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 2013-11-05 00:08, Allan Jude wrote: > Attached find ~320 new lines and 87 modified lines of the ZFS chapter o= f > the FreeBSD Handbook that I wrote on the plane to and from the FreeBSD > 20th Anniversary Party. > > Note: this is for, and is a patch against, the projects/zfsupdate-20130= 7 > branch. > After talking with wblock on IRC, here is a version of the above patch with all my nasty whitespace changes included (since this is an untranslated project branch) --=20 Allan Jude --------------060300010504090803090809 Content-Type: text/plain; charset=windows-1252; name="zfs_freebsdparty_all.patch" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="zfs_freebsdparty_all.patch" Index: projects/zfsupdate-201307/en_US.ISO8859-1/books/handbook/zfs/chapt= er.xml =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- projects/zfsupdate-201307/en_US.ISO8859-1/books/handbook/zfs/chapter.= xml (revision 43100) +++ projects/zfsupdate-201307/en_US.ISO8859-1/books/handbook/zfs/chapter.= xml (working copy) @@ -22,22 +22,35 @@ Reuschling Written by + + Warren + Block + Written by + =20 The Z File System (<acronym>ZFS</acronym>) =20 The Z File System - (ZFS) was developed at &sun; to address many of - the problems with current file systems. There were three major - design goals: + (ZFS) was originally developed at &sun; to + address many of the problems with then current file systems. + Development has since moved to the Open-ZFS Project. For more on + past and future development, see + .. The three major design + goals of ZFS are: =20 - Data integrity: checksums are created when data is written - and checked when data is read. If on-disk data corruption is - detected, the user is notified and recovery methods are - initiated. + Data integrity: All data that is stored on + ZFS includes a checksum of the data. When + data is written the checksum is calculated and written along + with the data. When that data is later read back, the + checksum is calculated again and if the values do not match an + error is returned. ZFS will attempt to + automatically correct the error if there is sufficient + redundancy available. =20 @@ -48,7 +61,13 @@ =20 - Performance: + Performance: ZFS features a number of + optional caching mechanisms to provide increased performance. + In addition to an advanced read cache known as the ARC in memory, there is also the + optional L2ARC read + cache and the ZIL + synchronous write cache. =20 @@ -243,8 +262,8 @@ method of avoiding data loss from disk failure is to implement RAID. ZFS supports this feature in its pool design. - RAID-Z pools require three or more disks but - yield more usable space than mirrored pools. + RAID-Z pools require three or more disks + but yield more usable space than mirrored pools. =20 To create a RAID-Z pool, use this command, specifying the disks to add to the @@ -345,7 +364,8 @@ =20 This completes the RAID-Z configuration. Daily status updates about the file systems - created can be generated as part of the nightly &man.periodic.8; runs:<= /para> + created can be generated as part of the nightly + &man.periodic.8; runs: =20 &prompt.root; echo 'daily_status_zfs_enable=3D"= YES"' >> /etc/periodic.conf @@ -360,13 +380,15 @@ =20 &prompt.root; zpool status -x =20 - If all pools are healthy and everything is normal, the - message indicates that: + If all pools are Online and everything is + normal, the message indicates that: =20 all pools are healthy =20 - If there is an issue, perhaps a disk has gone offline, - the pool state will look similar to: + If there is an issue, perhaps a disk is in the Offline state, the pool + state will look similar to: =20 pool: storage state: DEGRADED @@ -393,10 +415,9 @@ =20 &prompt.root; zpool offline storage da1 =20 - Now the system can be powered down to replace da= 1. - When the system is - back online, the failed disk can replaced - in the pool: + Now the system can be powered down to replace + da1. When the system is back online, + the failed disk can replaced in the pool: =20 &prompt.root; zpool replace storage da1 =20 @@ -418,8 +439,8 @@ da2 ONLINE 0 0 0 =20 errors: No known data errors - In this example, everything is - normal. + + In this example, everything is normal. =20 @@ -441,8 +462,9 @@ =20 &prompt.root; zpool scrub storage =20 - The duration of a scrub depends on the - amount of data stored. Large amounts of data can take a considerable a= mount of time to verify. It is also very I/O + The duration of a scrub depends on the amount of data + stored. Large amounts of data can take a considerable amount + of time to verify. It is also very I/O intensive, so much so that only one scrub> may be run at any given time. After the scrub has completed, the status is updated and may be viewed with a status request: @@ -474,7 +496,14 @@ <command>zpool</command> Administration =20 - + The administration of ZFS is divided between two main + utilities. The zpool utility which controls + the operation of the pool and deals with adding, removing, + replacing and managing disks, and the zfs utility, which + deals with creating, destroying and managing datasets (both + filesystems and volumes). =20 Creating & Destroying Storage Pools @@ -490,33 +519,40 @@ vdev types do not allow additional disks to be added to the vdev. The exceptions are mirrors, which allow additional disks to be added to the vdev, and stripes, which can be - upgraded to mirrors by attaching an additional disk to the vdev. - Although additional vdevs can be added to a pool, the layout - of the pool cannot be changed once the pool has been created, - instead the data must be backed up and the pool + upgraded to mirrors by attaching an additional disk to the + vdev. Although additional vdevs can be added to a pool, the + layout of the pool cannot be changed once the pool has been + created, instead the data must be backed up and the pool recreated. =20 - + A ZFS pool that is no longer needed can be destroyed so + that the disks making up the pool can be reused in another + pool or for other purposes. Destroying a pool involves + unmouting all of the datasets in that pool. If the datasets + are in use, the unmount operation will fail and the pool will + not be destroyed. The destruction of the pool can be forced + with the parameter, however this can cause + undefined behavior in the applications which had open files on + those datasets. =20 Adding & Removing Devices =20 - Adding disks to a zpool can be broken down into - two separate cases: attaching a disk to an - existing vdev with the zpool attach - command, or adding vdevs to the pool with the - zpool add command. Only some - vdev types allow disks to - be added to the vdev after creation. + Adding disks to a zpool can be broken down into two + separate cases: attaching a disk to an existing vdev with + zpool attach, or adding vdevs to the pool + with zpool add. Only some vdev types allow disks to be + added to the vdev after creation. =20 When adding disks to the existing vdev is not an option, as in the case of RAID-Z, the other option is to add a vdev to the pool. It is possible, but discouraged, to mix vdev types. ZFS stripes data across each - of the vdevs. For example, if there are two mirror vdevs, then - this is effectively a RAID 10, striping the writes across the - two sets of mirrors. Because of the way that space is + of the vdevs. For example, if there are two mirror vdevs, + then this is effectively a RAID 10, striping the writes across + the two sets of mirrors. Because of the way that space is allocated in ZFS to attempt to have each vdev reach 100% full at the same time, there is a performance penalty if the vdevs have different amounts of free space. @@ -525,52 +561,63 @@ can only be removed from a mirror if there is enough remaining redundancy. =20 - Creating a ZFS Storage Pool (zpool) - involves making a number of decisions that are relatively - permanent. Although additional vdevs can be added to a pool, - the layout of the pool cannot be changed once the pool has - been created, instead the data must be backed up and the pool - recreated. Currently, devices cannot be removed from a - zpool. =20 - Replacing a Working Devices + Replacing a Functioning Device =20 There are a number of situations in which it may be desirable to replace a disk with a different disk. This process requires connecting the new disk at the same time as - the disk to be replaced. The - zpool replace command will copy all of the - data from the old disk to the new one. After this operation - completes, the old disk is disconnected from the vdev. If the - new disk is larger than the old disk, it may be possible to grow the zp= ool, using the new space. See - Growing a Pool. + the disk to be replaced. zpool replace + will copy all of the data from the old disk to the new one. + After this operation completes, the old disk is disconnected + from the vdev. If the new disk is larger than the old disk, + it may be possible to grow the zpool, using the new space. + See Growing a + Pool. =20 Dealing with Failed Devices =20 - When a disk fails and the physical device is replaced, ZFS - must be told to begin the When a disk in a ZFS pool fails, the vdev that the disk + belongs to will enter the Degraded state. In this + state, all of the data stored on the vdev is still available, + but performance may be impacted because missing data will need + to be calculated from the available redundancy. To restore + the vdev to a fully functional state the failed physical + device will need to be replace replaced, and ZFS must be + instructed to begin the resilver operation, where data that was on the failed device will be recalculated - from the available redundancy and written to the new - device. + from the available redundancy and written to the replacement + device. Once this process has completed the vdev will return + to Online status. If + the vdev does not have any redundancy, or if multiple devices + have failed and there is insufficient redundancy to + compensate, the pool will enter the Faulted state. If a + sufficient number of devices cannot be reconnected to the pool + then the pool will be inoperative, and data will need to be + restored from backups. =20 Growing a Pool =20 The usable size of a redundant ZFS pool is limited by the - size of the smallest device in the vdev. If each device in the vdev is= replaced sequentially, - after the smallest device - has completed the replace or resilver operation, the pool - can grow based on the size of the new smallest device. - This expansion can be triggered with the - zpool online command with the -e flag on - each device. After the expansion of each device, - the additional space will be available in the pool. + size of the smallest device in the vdev. If each device in + the vdev is replaced sequentially, after the smallest device + has completed the replace or resilver operation, the + pool can grow based on the size of the new smallest device. + This expansion can be triggered by using zpool + online with the parameter on + each device. After the expansion of each device, the + additional space will become available in the pool. =20 @@ -582,19 +629,20 @@ by other disk subsystems. This allows pools to be imported on other machines, other operating systems that support ZFS, and even different hardware architectures (with some caveats, see - &man.zpool.8;). When a dataset has open files, can= be used to force the - export of a pool. - causes the datasets to be forcibly - unmounted. This can have unexpected side effects. + &man.zpool.8;). When a dataset has open files, + can be used to force the export + of a pool. causes the datasets to be + forcibly unmounted, which can cause undefined behavior in the + applications which had open files on those datasets. =20 - Importing a pool automatically mounts the datasets. - This may not be the desired behavior, and can be prevented with -N. - sets - temporary properties for this import only. = - allows importing a zpool with a base - mount point instead of the root of the file system. If the - pool was last used on a different system and was not properly - exported, an import might have to be forced with . + Importing a pool automatically mounts the datasets. This + may not be the desired behavior, and can be prevented with + . sets temporary + properties for this import only. + allows importing a zpool with a base mount point instead of + the root of the file system. If the pool was last used on a + different system and was not properly exported, an import + might have to be forced with . imports all pools that do not appear to be in use by another system. @@ -602,18 +650,18 @@ Upgrading a Storage Pool =20 - After upgrading &os;, or if a pool has been - imported from a system using an older version of ZFS, the pool - must be manually upgraded to the latest version of ZFS. This - process is unreversible. Consider whether the pool may ever need - to be imported on an older system before upgrading. An upgrade - cannot be undone. + After upgrading &os;, or if a pool has been imported from + a system using an older version of ZFS, the pool can be + manually upgraded to the latest version of ZFS. Consider + whether the pool may ever need to be imported on an older + system before upgrading. The upgrade process is unreversible + and cannot be undone. =20 The newer features of ZFS will not be available until - the zpool upgrade command has completed. - will the newer features of ZFS be available. - can be used to see what new - features will be provided by upgrading. + zpool upgrade has completed. + can be used to see what new features will + be provided by upgrading, as well as which features are + already supported by the existing version. =20 @@ -627,40 +675,42 @@ =20 ZFS has a built-in monitoring system that can display statistics about I/O happening on the pool in real-time. - Additionally, it shows the free and used space on the pool and - how much I/O bandwidth is currently utilized for read and - write operations. By default, all pools in the system will be - monitored and displayed. A pool name can be provided to monitor - just that single pool. A basic example: + It shows the amount of free and used space on the pool, how + many read and write operations are being performed per second, + and how much I/O bandwidth is currently being utilized for + read and write operations. By default, all pools in the + system will be monitored and displayed. A pool name can be + provided as part of the command to monitor just that specific + pool. A basic example: =20 -&prompt.root; zpool iostat + &prompt.root; zpool iostat capacity operations bandwidth pool alloc free read write read write ---------- ----- ----- ----- ----- ----- ----- data 288G 1.53T 2 11 11.3K 57.1K =20 - To continuously monitor I/O activity on the pool, specify - a number as the last parameter, indicating the number of seconds - to wait between updates. ZFS will print the next - statistic line after each interval. Press - CtrlC - to stop this continuous monitoring. Alternatively, give a second - number on the command line after the - interval to specify the total number of statistics to - display. + To continuously monitor I/O activity on the pool, a + number can be specified as the last parameter, indicating + the frequency in seconds to wait between updates. ZFS will + print the next statistic line after each interval. Press + CtrlC + to stop this continuous monitoring. Alternatively, give a + second number on the command line after the interval to + specify the total number of statistics to display. =20 - Even more detailed pool I/O statistics can be - displayed with parameter. - Each storage device in the pool will be shown with a - separate statistic line. This is helpful to - determine reads and writes on devices that slow down I/O on - the whole pool. The following example shows a - mirrored pool consisting of two devices. For each of these, - a separate line is shown with the current I/O - activity. + Even more detailed pool I/O statistics can be + displayed with . In this case=20 + each storage device in the pool will be shown with a + corresponding statistics line. This is helpful to + determine how many read and write operations are being + performed on each device, and can help determine if any + specific device is slowing down I/O on the entire pool. The + following example shows a mirrored pool consisting of two + devices. For each of these, a separate line is shown with + the current I/O activity. =20 -&prompt.root; zpool iostat -v + &prompt.root; zpool iostat -v capacity operations bandwidth pool alloc free read write read write ----------------------- ----- ----- ----- ----- ----- ----- @@ -674,25 +724,86 @@ Splitting a Storage Pool =20 - + A ZFS pool consisting of one or more mirror vdevs can be + split into a second pool. The last member of each mirror + (unless otherwise specified) is detached and used to create a + new pool containing the same data. It is recommended that + the operation first be attempted with the + parameter. This will print out the details of the proposed + operation without actually performancing it. This helps + ensure the operation will happen as expected. =20 <command>zfs</command> Administration =20 - + The zfs utility is responsible for + creating, destroying, and managing all ZFS + datasets that exist within a pool. The pool is managed using + the zpool + command. =20 Creating & Destroying Datasets =20 - + Unlike with traditional disks and volume managers, space + in ZFS is not preallocated, allowing + additional file systems to be created at any time. With + traditional file systems, once all of the space was + partitioned and assigned to a file system, there was no way to + add an additional file system without adding a new disk. + ZFS also allows you to set a number of + properties on each dataset. These properties + include features like compression, deduplication, caching and + quoteas, as well as other useful properties like readonly, + case sensitivity, network file sharing and mount point. Each + separate dataset can be administered, delegated, replicated, snapshoted, jailed, and destroyed as a unit. + This offers many advantages to creating a separate dataset for + each different type or set of files. The only drawback to + having an extremely large number of datasets, is that some + commands like zfs list will be slower, + and the mounting of an extremely large number of datasets + (100s or 1000s) can make the &os; boot process take + longer. + + Destroying a dataset is much quicker than deleting all + of the files that reside on the dataset, as it does not + invole scanning all of the files and updating all of the + corresponding metadata. In modern versions of + ZFS the zfs destroy + operation is asynchronous, the free space may take several + minutes to appear in the pool. The freeing + property, accessible with zpool get freeing + poolname indicates how + many datasets are having their blocks freed in the background. + If there are child datasets, such as snapshots or other + datasets, then the parent cannot be destroyed. To destroy a + dataset and all of its children, use the + parameter to recursively destroy the dataset and all of its + children. The parameters can be used + to not actually perform the destruction, but instead list + which datasets and snapshots would be destroyed and in the + case of snapshots, how much space would be reclaimed by + proceeding with the destruction. =20 Creating & Destroying Volumes =20 - + A volume is special type of ZFS + dataset. Rather than being mounted as a file system, it is + exposed as a block device under + /dev/zvol/poolname/= dataset. + This allows the volume to be used for other file systems, to + back the disks of a virtual machine, or to be exported using + protocols like iSCSI or HAST. =20 A volume can be formatted with any filesystem on top of it. This will appear to the user as if they are working with @@ -714,18 +825,46 @@ /dev/zvol/tank/fat32 249M 24k 249M 0% /mnt &prompt.root; mount | grep fat32 /dev/zvol/tank/fat32 on /mnt (msdosfs, local) + + Destroying a volume is much the same as destroying a + regular filesystem dataset. The operation is nearly + instantaneous, but it make take several minutes for the free + space to be reclaimed in the background. + =20 Renaming a Dataset =20 - + The name of a dataset can be changed using zfs + rename. The rename command can also be used to + change the parent of a dataset. Renaming a dataset to be + under a different parent dataset will change the value of + those properties that are inherited by the child dataset. + When a dataset is renamed, it is unmounted and then remounted + in the new location (inherited from the parent dataset). This + behavior can be prevented using the + parameter. Due to the nature of snapshots, they cannot be + renamed outside of the parent dataset. To rename a recursive + snapshot, specify the parameter, and all + snapshots with the same specified snapshot will be + renamed. =20 Setting Dataset Properties =20 - + Each ZFS dataset has a number of + properties to control its behavior. Most properties are + automatically inherited from the parent dataset, but can be + overridden locally. Set a property on a dataset with + zfs set + property=3Dvalue + dataset. Most properties + have a limited set of valid values, zfs get + will display each possible property and its valid values. + Most properties can be reverted to their inherited values + using zfs inherit. =20 It is possible to set user-defined properties in ZFS. They become part of the dataset configuration and can be used @@ -743,13 +882,55 @@ Managing Snapshots =20 - + Snapshots are one= + of the most powerful features of ZFS. A + snapshot provides a point-in-time copy of the dataset that the + parent dataset can be rolled back to if required. Create a + snapshot with zfs snapshot + dataset@snapshotname. + Specifying the parameter will recursively + create a snapshot with the same name on all child + datasets. + + By default, snapshots are mounted in a hidden directory + under the parent dataset: .zfs/snapshots/snapshotname. + Individual files can easily be restored to a previous state by + copying them from the snapshot back to the parent dataset. It + is also possible to revert the entire dataset back to the + point-in-time of the snapshot using zfs + rollback. + + Snapshots consume space based on how much the parent file + system has changed since the time of the snapshot. The + written property of a snapshot tracks how + much space is being used by a snapshot. + + To destroy a snapshot and recover the space consumed by + the overwritten or deleted files, run zfs destroy + dataset@snapshot<= /command>. + The parameter will recursively remove all + snapshots with the same name under the parent dataset. Adding + the parameters to the destroy command + will display a list of the snapshots that would be deleted and + an estimate of how much space would be reclaimed by proceeding + with the destroy operation. =20 Managing Clones =20 - + A clone is a copy of a snapshot that is treated more like + a regular dataset. Unlike a snapshot, a clone is not read + only, is mounted, and can have its own properties. Once a + clone has been created, the snapshot it was created from + cannot be destroyed. The child/parent relationship between + the clone and the snapshot can be reversed using zfs + promote. After a clone has been promoted, the + snapshot becomes a child of the clone, rather than of the + original parent dataset. This will change how the space is + accounted, but not actually change the amount of space + consumed. =20 @@ -761,6 +942,18 @@ Dataset, User and Group Quotas =20 + Dataset + quotas can be used to restrict the amount of space + that can be consumed by a peticular dataset. Reference Quotas work in + very much the same way, except they only count the space used + by the dataset it self, excluding snapshots and child + datasets. Similarly user and group quotas can be used + to prevent users or groups from consuming all of the available + space in the pool or dataset. + To enforce a dataset quota of 10 GB for storage/home/bob, use the following: @@ -861,7 +1054,13 @@ Reservations =20 - + Reservations + guarantee a minimum amount of space will always be available + to a dataset. The reserved space will not + be available to any other dataset. This feature can be + especially useful to ensure that users cannot comsume all of + the free space, leaving none for an important dataset or log + files. =20 The general format of the reservation property is @@ -878,7 +1077,8 @@ =20 The same principle can be applied to the refreservation property for setting a - refreservation, with the general format + Reference + Reservation, with the general format refreservation=3Dsize. =20 To check if any reservations or refreservations exist on @@ -898,7 +1098,18 @@ Deduplication =20 - + When enabled, Deduplication uses + the checksum of each block to detect duplicate blocks. When a + new block is about to be written and it is determined to be a + duplicate of an existing block, rather than writing the same + data again, ZFS just references the + existing data on disk an additional time. This can offer + tremendous space savings if your data contains many discreet + copies of the file information. Deduplication requires an + extremely large amount of memory, and most of the space + savings can be had without the extra cost by enabling + compression instead. =20 To activate deduplication, you simply need to set the following property on the target pool. @@ -986,6 +1197,22 @@ thumb, compression should be used first before deduplication due to the lower memory requirements. + + + ZFS and Jails + + zfs jail and the corresponding + jailed property are used to delegate a + ZFS dataset to a Jail. zfs jail + jailid attaches a dataset + to the specified jail, and the zfs unjail + detaches it. In order for the dataset to be administered from + within a jail, the jailed property must be + set. Once a dataset is jailed it can no longer be mounted on + the host, because the jail administrator may have set + unacceptable mount points. + =20 @@ -1170,6 +1397,12 @@ Best Practices Guide + + + History of <acronym>ZFS</acronym> + + + =20 @@ -1344,31 +1577,28 @@ Log - ZFS Log Devices, also known as ZFS Intent Log - (ZIL) move the intent log from - the regular pool devices to a dedicated device. - The ZIL accelerates synchronous - transactions by using storage devices (such as - SSDs) that are faster than - those used for the main pool. When data is being - written and the application requests a guarantee - that the data has been safely stored, the data is - written to the faster ZIL - storage, then later flushed out to the regular - disks, greatly reducing the latency of synchronous - writes. Log devices can be mirrored, but - RAID-Z is not supported. If - multiple log devices are used, writes will be load - balanced across them. + (ZIL) + move the intent log from the regular pool devices + to a dedicated device, typically an + SSD. Having a dedicated log + device can significantly improve the performance + of applications with a high volume of synchronous + writes, especially databases. Log devices can be + mirrored, but RAID-Z is not + supported. If multiple log devices are used, + writes will be load balanced across them. =20 Cache - Adding a cache vdev to a zpool will add the storage of the cache to - the L2ARC. Cache devices - cannot be mirrored. Since a cache device only - stores additional copies of existing data, there - is no risk of data loss. + the L2ARC. + Cache devices cannot be mirrored. Since a cache + device only stores additional copies of existing + data, there is no risk of data loss. @@ -1446,6 +1676,26 @@ =20 + ZIL + + The ZIL accelerates synchronous + transactions by using storage devices (such as + SSDs) that are faster than those used + for the main storage pool. When data is being written + and the application requests a synchronous write (a + guarantee that the data has been safely stored to disk + rather than only cached to be written later), the data + is written to the faster ZIL storage, + then later flushed out to the regular disks, greatly + reducing the latency and increasing performance. + Only workloads that are synchronous such as databases + will benefit from a ZIL. Regular + asynchronous writes such as copying files will not use + the ZIL at all. + + + Copy-On-Write =20 Unlike a traditional file system, when data is @@ -1481,12 +1731,24 @@ properties on a child to override the defaults inherited from the parents and grandparents. ZFS also allows administration of - datasets and their children to be delegated. + datasets and their children to be delegated. =20 - Volume + Filesystem =20 + A ZFS dataset is most often used + as a file system. Like most other file systems, a + ZFS file system is mounted somewhere + in the systems directory heirarchy and contains files + and directories of its own with permissions, flags and + other metadata. + + + + Volume + In additional to regular file system datasets, ZFS can also create volumes, which are block devices. Volumes have many of the same @@ -1802,6 +2064,63 @@ remaining drives) to the new drive is called resilvering. + + + Online + + A ZFS pool or vdev that is in the + Online state has all of its member + devices connected and fully operational. Individual + devices in the Online state are + functioning normally. + + + + Offline + + Individual devices can be put in an + Offline state by the administrator if + there is sufficient redundancy to avoid putting the pool + or vdev into a Faulted state. An + administrator may choose to offline a disk in + preperation for replacing it, or to make it easier to + identify. + + + + Degraded + + A ZFS pool or vdev that is in the + Degraded state has one or more disks + that have been disconnected or have failed. The pool is + still usable however if additional devices fail the pool + could become unrecoverable. Reconnecting the missing + device(s) or replacing the failed disks will return the + pool to a Online state after + the reconnected or new device has completed the Resilver + process. + + + + Faulted + + A ZFS pool or vdev that is in the + Faulted state is no longer + operational and the data residing on it can no longer + be accessed. A pool or vdev enters the + Faulted state when the number of + missing or failed devices exceeds the level of + redundancy in the vdev. If missing devices can be + reconnected the pool will return to a Online state. If + there is insufficient redundancy to compensate for the + number of failed disks, then the contents of the pool + are lost and will need to be restored from + backups. + --------------060300010504090803090809-- --EtQxoST8mRoe0mtPQEpKncolooom9QPMo Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (MingW32) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJSeH7BAAoJEJrBFpNRJZKfnV4P/2dWus+xVy5lVK/5Hn2P/wPH kcYdoEqrPn2gcSy5zrRbL/P/zQ8zd9FZJh0nzo4tqk2OHKkyNH0KlwL9zbKGEOs/ 0B6D3XxeyCTp7KbuR/77iISM+MUUjV+6HToBVs3bunDnLS7N4sQtpU6aspeub6Wx VJOOhJbg2BZZWAjGpptpZUOKLK8vP3d1uP4kH0OpV3x1kExiqqAog3cIlIK6peUq JLW6kubc8cuFsUrwmhdcqP6riqTFyFMNHqbeFsv3kzg50XWIxDDMFqi47JvtfO1F 2SAOCHRhi5rvDE5fHPqYREbVWs2whlRcbQcLF/OZN0yge26q7VsDkHbtmJxzDBQM 7n03lBVt25QOJKn0O4lLEoZee1tJ9unkdHydqcFk5+In6KT8CfdlGsv3ZSivXGXU t2JV3WIV1QyKqHdAZC7jNwqmDneYDPfLBTEjZh7kG6xtUSOiC/KOLIHMRWA01vBM 7wL5VeIsTKhQ97TESBnA+0g+GwDAwXSc5GhwzUo3yq9EGtpCz45jKkgqiptqXT25 Eo4Ls4isuG1XyUBbRStLiQoLSxXvbRTPAf9bsnHkS1clPIKcaGETkuZdx1AtfeNx MQpBvM7qtZHLmJWsmvq2hIz8i8OdtvqVhlnLCA3ziWHQjL4ZR6ILTw7CpDTLayFT Zw0x4PutCuYfjN69bLwE =W/xo -----END PGP SIGNATURE----- --EtQxoST8mRoe0mtPQEpKncolooom9QPMo-- From owner-freebsd-doc@FreeBSD.ORG Tue Nov 5 11:27:11 2013 Return-Path: Delivered-To: freebsd-doc@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 46CCBC56 for ; Tue, 5 Nov 2013 11:27:11 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id F2F342F4E for ; Tue, 5 Nov 2013 11:27:10 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.7/8.14.7) with ESMTP id rA5BR7xG057674; Tue, 5 Nov 2013 04:27:07 -0700 (MST) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.7/8.14.7/Submit) with ESMTP id rA5BR6au057671; Tue, 5 Nov 2013 04:27:07 -0700 (MST) (envelope-from wblock@wonkity.com) Date: Tue, 5 Nov 2013 04:27:06 -0700 (MST) From: Warren Block To: Allan Jude Subject: Re: ZFS Handbook Update In-Reply-To: <52787EBE.5040100@allanjude.com> Message-ID: References: <52787D62.5020607@allanjude.com> <52787EBE.5040100@allanjude.com> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (wonkity.com [127.0.0.1]); Tue, 05 Nov 2013 04:27:07 -0700 (MST) Cc: freebsd-doc@FreeBSD.org X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Nov 2013 11:27:11 -0000 On Tue, 5 Nov 2013, Allan Jude wrote: > On 2013-11-05 00:08, Allan Jude wrote: >> Attached find ~320 new lines and 87 modified lines of the ZFS chapter of >> the FreeBSD Handbook that I wrote on the plane to and from the FreeBSD >> 20th Anniversary Party. >> >> Note: this is for, and is a patch against, the projects/zfsupdate-201307 >> branch. >> > After talking with wblock on IRC, here is a version of the above patch > with all my nasty whitespace changes included (since this is an > untranslated project branch) Yes. Mixing whitespace and content changes in this chapter should not be a problem now because nobody is translating it yet. Still, after this, let's avoid it. igor can help by limiting tests to just content or just whitespace: igor -Rz chapter.xml | less -RS (to just test content) igor -RZ chapter.xml | less -RS (to just test whitespace) That's a lower case "z" for content, upper case for whitespace. Committed, with a few minor edits. Thanks! From owner-freebsd-doc@FreeBSD.ORG Wed Nov 6 00:43:46 2013 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 54925CCF for ; Wed, 6 Nov 2013 00:43:46 +0000 (UTC) (envelope-from thomas@gibfest.dk) Received: from mail.tyknet.dk (mail.tyknet.dk [176.9.9.186]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 1171D22EF for ; Wed, 6 Nov 2013 00:43:45 +0000 (UTC) Received: from [10.10.1.214] (217.71.4.82.static.router4.bolignet.dk [217.71.4.82]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mail.tyknet.dk (Postfix) with ESMTPSA id 0FDDC1B8699 for ; Wed, 6 Nov 2013 01:43:37 +0100 (CET) DKIM-Filter: OpenDKIM Filter v2.8.3 mail.tyknet.dk 0FDDC1B8699 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=gibfest.dk; s=default; t=1383698618; bh=BL4IIJnN0LETS+JlgZvPab+w5iyceVaHB29XMOtmmVs=; h=Date:From:To:Subject; b=VxPRyYAvyP7WR2XvbBxnYkS/p/HSKedCoVuvv6bX5Ytmu9FdFoAW9G4TkFDVq50i1 WOAiCj090aBzz+7yrj78p2EHwmsBOP3POGJUC8aWMZ6FgYRzhWoZ/k/rVlmf4oG1p3 5bkz1uuGSX2CSqobfJILA1G/QCk2vzT5Mg9oBIf8= Message-ID: <527990B7.6080100@gibfest.dk> Date: Wed, 06 Nov 2013 01:43:35 +0100 From: Thomas Steen Rasmussen User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0 MIME-Version: 1.0 To: freebsd-doc@freebsd.org Subject: ifconfig_if_aliases not documented in /etc/defaults/rc.conf or in handbook Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Nov 2013 00:43:46 -0000 Hello there, ifconfig_if_aliases can greatly simplify rc.conf for machines with many IP aliases, since renumbering of all the _aliasN entries is no longer needed. But the syntax is not documented in /etc/defaults/rc.conf or in handbook at http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/configtuning-virtual-hosts.html Consider the example aliases from the handbook link above: ifconfig_fxp0_alias0="inet 10.1.1.2 netmask 255.255.255.255" ifconfig_fxp0_alias1="inet 10.1.1.3 netmask 255.255.255.255" ifconfig_fxp0_alias2="inet 10.1.1.4 netmask 255.255.255.255" ifconfig_fxp0_alias3="inet 10.1.1.5 netmask 255.255.255.255" ifconfig_fxp0_alias4="inet 202.0.75.17 netmask 255.255.255.240" ifconfig_fxp0_alias5="inet 202.0.75.18 netmask 255.255.255.255" ifconfig_fxp0_alias6="inet 202.0.75.19 netmask 255.255.255.255" ifconfig_fxp0_alias7="inet 202.0.75.20 netmask 255.255.255.255" Can now be written as: ifconfig_fxp0_aliases="inet 10.1.1.2-5/32 inet 202.0.75.17-20/28" This should be included both in /etc/defaults/rc.conf and in the handbook :) Thanks and best regards, /Thomas Steen Rasmussen From owner-freebsd-doc@FreeBSD.ORG Wed Nov 6 14:20:02 2013 Return-Path: Delivered-To: freebsd-doc@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 9D4A0952 for ; Wed, 6 Nov 2013 14:20:02 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 8924222D1 for ; Wed, 6 Nov 2013 14:20:02 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id rA6EK1iB083801 for ; Wed, 6 Nov 2013 14:20:01 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id rA6EK1NL083800; Wed, 6 Nov 2013 14:20:01 GMT (envelope-from gnats) Date: Wed, 6 Nov 2013 14:20:01 GMT Message-Id: <201311061420.rA6EK1NL083800@freefall.freebsd.org> To: freebsd-doc@FreeBSD.org Cc: From: The BSD Dreamer Subject: Re: docs/178818: gmirror(8) says to use rc.early which is no longer available X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: The BSD Dreamer List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 Nov 2013 14:20:02 -0000 The following reply was made to PR docs/178818; it has been noted by GNATS. From: The BSD Dreamer To: bug-followup@FreeBSD.org, beastie@tardisi.com Cc: Subject: Re: docs/178818: gmirror(8) says to use rc.early which is no longer available Date: Wed, 06 Nov 2013 07:56:05 -0600 Sorry for not replying sooner, but it didn't quite work for me and forgot to come back later to see why, since what I hacked seemed to be working...until recently. So, I revisited this problem. One change to your diff... http://lkc.me/5D -- Name: Lawrence "The Dreamer" Chen Email: beastie@tardisi.com Snail: 1530 College Ave, A5 Blog: http://lawrencechen.net Manhattan, KS 66502-2768 Phone: 785-789-4132 From owner-freebsd-doc@FreeBSD.ORG Thu Nov 7 15:12:39 2013 Return-Path: Delivered-To: doc@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 9B8CDCAE for ; Thu, 7 Nov 2013 15:12:39 +0000 (UTC) (envelope-from gabor@kovesdan.org) Received: from server.mypc.hu (server.mypc.hu [87.229.73.95]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 51D3126D4 for ; Thu, 7 Nov 2013 15:12:39 +0000 (UTC) Received: from server.mypc.hu (localhost [127.0.0.1]) by server.mypc.hu (Postfix) with ESMTP id C5A9214D2431 for ; Thu, 7 Nov 2013 16:12:20 +0100 (CET) X-Virus-Scanned: amavisd-new at !change-mydomain-variable!.example.com Received: from server.mypc.hu ([127.0.0.1]) by server.mypc.hu (server.mypc.hu [127.0.0.1]) (amavisd-new, port 10024) with LMTP id LKyGG5IREFjg for ; Thu, 7 Nov 2013 16:12:20 +0100 (CET) Received: from [192.168.0.10] (54034B4D.catv.pool.telekom.hu [84.3.75.77]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by server.mypc.hu (Postfix) with ESMTPSA id 6B26414D2403 for ; Thu, 7 Nov 2013 16:12:20 +0100 (CET) Message-ID: <527BADCB.8030308@kovesdan.org> Date: Thu, 07 Nov 2013 16:12:11 +0100 From: =?ISO-8859-1?Q?G=E1bor_K=F6vesd=E1n?= User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 MIME-Version: 1.0 To: doc@FreeBSD.org Subject: [HEADSUP] Merging DocBook 5.0 update Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Nov 2013 15:12:39 -0000 Hi, I will soon merge the DocBook 5.0 updates to head. The tree will temporarily be locked until the merge is done. I will send out another email I have finished. Gabor From owner-freebsd-doc@FreeBSD.ORG Thu Nov 7 16:58:42 2013 Return-Path: Delivered-To: freebsd-doc@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id DFF0EE55 for ; Thu, 7 Nov 2013 16:58:41 +0000 (UTC) (envelope-from www-data@FreeBSD.org) Received: from build-web.stream.freebsd.org (build-web.stream.freebsd.org [IPv6:2001:1900:2254:206a::16:6504]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id BE7B92DC5 for ; Thu, 7 Nov 2013 16:58:41 +0000 (UTC) Received: from build-web.stream.freebsd.org ([127.0.1.2]) by build-web.stream.freebsd.org (8.14.7/8.14.7) with ESMTP id rA7Gwfq3067737 for ; Thu, 7 Nov 2013 16:58:41 GMT (envelope-from www-data@build-web.stream.freebsd.org) Received: (from www-data@localhost) by build-web.stream.freebsd.org (8.14.7/8.14.5/Submit) id rA7GwfZS067735 for freebsd-doc@FreeBSD.org; Thu, 7 Nov 2013 16:58:41 GMT (envelope-from www-data) Date: Thu, 7 Nov 2013 16:58:41 GMT From: User Www-data Message-Id: <201311071658.rA7GwfZS067735@build-web.stream.freebsd.org> To: freebsd-doc@FreeBSD.org Subject: FreeBSD web build failed on build-web.stream.freebsd.org X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Nov 2013 16:58:42 -0000 env XML_CATALOG_FILES="file:///home/www/build/head/en_US.ISO8859-1/htdocs/ports/catalog-cwd.xml file:///home/www/build/head/en_US.ISO8859-1/share/xml/catalog.xml file:///home/www/build/head/share/xml/catalog.xml file:///home/www/build/head/share/xml/catalog-common.xml file:///usr/local/share/xml/catalog" /usr/local/bin/xmllint --xinclude --valid --noout --nonet x11-clocks.xml env XML_CATALOG_FILES="file:///home/www/build/head/en_US.ISO8859-1/htdocs/ports/catalog-cwd.xml file:///home/www/build/head/en_US.ISO8859-1/share/xml/catalog.xml file:///home/www/build/head/share/xml/catalog.xml file:///home/www/build/head/share/xml/catalog-common.xml file:///usr/local/share/xml/catalog" /usr/local/bin/xsltproc --xinclude --nonet --debug -o x11-clocks.html /home/www/build/head/share/xml/xhtml.xsl x11-clocks.xml env XML_CATALOG_FILES="file:///home/www/build/head/en_US.ISO8859-1/htdocs/ports/catalog-cwd.xml file:///home/www/build/head/en_US.ISO8859-1/share/xml/catalog.xml file:///home/www/build/head/share/xml/catalog.xml file:///home/www/build/head/share/xml/catalog-common.xml file:///usr/local/share/xml/catalog" /usr/local/bin/xmllint --xinclude --valid --noout --nonet x11-drivers.xml env XML_CATALOG_FILES="file:///home/www/build/head/en_US.ISO8859-1/htdocs/ports/catalog-cwd.xml file:///home/www/build/head/en_US.ISO8859-1/share/xml/catalog.xml file:///home/www/build/head/share/xml/catalog.xml file:///home/www/build/head/share/xml/catalog-common.xml file:///usr/local/share/xml/catalog" /usr/local/bin/xsltproc --xinclude --nonet --debug -o x11-drivers.html /home/www/build/head/share/xml/xhtml.xsl x11-drivers.xml env XML_CATALOG_FILES="file:///home/www/build/head/en_US.ISO8859-1/htdocs/ports/catalog-cwd.xml file:///home/www/build/head/en_US.ISO8859-1/share/xml/catalog.xml file:///home/www/build/head/share/xml/catalog.xml file:///home/www/build/head/share/xml/catalog-common.xml file:///usr/local/share/xml/catalog" /usr/local/bin/xmllint --xinclude --valid --noout --nonet x11-fm.xml env XML_CATALOG_FILES="file:///home/www/build/head/en_US.ISO8859-1/htdocs/ports/catalog-cwd.xml file:///home/www/build/head/en_US.ISO8859-1/share/xml/catalog.xml file:///home/www/build/head/share/xml/catalog.xml file:///home/www/build/head/share/xml/catalog-common.xml file:///usr/local/share/xml/catalog" /usr/local/bin/xsltproc --xinclude --nonet --debug -o x11-fm.html /home/www/build/head/share/xml/xhtml.xsl x11-fm.xml env XML_CATALOG_FILES="file:///home/www/build/head/en_US.ISO8859-1/htdocs/ports/catalog-cwd.xml file:///home/www/build/head/en_US.ISO8859-1/share/xml/catalog.xml file:///home/www/build/head/share/xml/catalog.xml file:///home/www/build/head/share/xml/catalog-common.xml file:///usr/local/share/xml/catalog" /usr/local/bin/xmllint --xinclude --valid --noout --nonet x11-fonts.xml env XML_CATALOG_FILES="file:///home/www/build/head/en_US.ISO8859-1/htdocs/ports/catalog-cwd.xml file:///home/www/build/head/en_US.ISO8859-1/share/xml/catalog.xml file:///home/www/build/head/share/xml/catalog.xml file:///home/www/build/head/share/xml/catalog-common.xml file:///usr/local/share/xml/catalog" /usr/local/bin/xsltproc --xinclude --nonet --debug -o x11-fonts.html /home/www/build/head/share/xml/xhtml.xsl x11-fonts.xml env XML_CATALOG_FILES="file:///home/www/build/head/en_US.ISO8859-1/htdocs/ports/catalog-cwd.xml file:///home/www/build/head/en_US.ISO8859-1/share/xml/catalog.xml file:///home/www/build/head/share/xml/catalog.xml file:///home/www/build/head/share/xml/catalog-common.xml file:///usr/local/share/xml/catalog" /usr/local/bin/xmllint --xinclude --valid --noout --nonet x11-servers.xml env XML_CATALOG_FILES="file:///home/www/build/head/en_US.ISO8859-1/htdocs/ports/catalog-cwd.xml file:///home/www/build/head/en_US.ISO8859-1/share/xml/catalog.xml file:///home/www/build/head/share/xml/catalog.xml file:///home/www/build/head/share/xml/catalog-common.xml file:///usr/local/share/xml/catalog" /usr/local/bin/xsltproc --xinclude --nonet --debug -o x11-servers.html /home/www/build/head/share/xml/xhtml.xsl x11-servers.xml env XML_CATALOG_FILES="file:///home/www/build/head/en_US.ISO8859-1/htdocs/ports/catalog-cwd.xml file:///home/www/build/head/en_US.ISO8859-1/share/xml/catalog.xml file:///home/www/build/head/share/xml/catalog.xml file:///home/www/build/head/share/xml/catalog-common.xml file:///usr/local/share/xml/catalog" /usr/local/bin/xmllint --xinclude --valid --noout --nonet x11-themes.xml env XML_CATALOG_FILES="file:///home/www/build/head/en_US.ISO8859-1/htdocs/ports/catalog-cwd.xml file:///home/www/build/head/en_US.ISO8859-1/share/xml/catalog.xml file:///home/www/build/head/share/xml/catalog.xml file:///home/www/build/head/share/xml/catalog-common.xml file:///usr/local/share/xml/catalog" /usr/local/bin/xsltproc --xinclude --nonet --debug -o x11-themes.html /home/www/build/head/share/xml/xhtml.xsl x11-themes.xml env XML_CATALOG_FILES="file:///home/www/build/head/en_US.ISO8859-1/htdocs/ports/catalog-cwd.xml file:///home/www/build/head/en_US.ISO8859-1/share/xml/catalog.xml file:///home/www/build/head/share/xml/catalog.xml file:///home/www/build/head/share/xml/catalog-common.xml file:///usr/local/share/xml/catalog" /usr/local/bin/xmllint --xinclude --valid --noout --nonet x11-toolkits.xml env XML_CATALOG_FILES="file:///home/www/build/head/en_US.ISO8859-1/htdocs/ports/catalog-cwd.xml file:///home/www/build/head/en_US.ISO8859-1/share/xml/catalog.xml file:///home/www/build/head/share/xml/catalog.xml file:///home/www/build/head/share/xml/catalog-common.xml file:///usr/local/share/xml/catalog" /usr/local/bin/xsltproc --xinclude --nonet --debug -o x11-toolkits.html /home/www/build/head/share/xml/xhtml.xsl x11-toolkits.xml env XML_CATALOG_FILES="file:///home/www/build/head/en_US.ISO8859-1/htdocs/ports/catalog-cwd.xml file:///home/www/build/head/en_US.ISO8859-1/share/xml/catalog.xml file:///home/www/build/head/share/xml/catalog.xml file:///home/www/build/head/share/xml/catalog-common.xml file:///usr/local/share/xml/catalog" /usr/local/bin/xmllint --xinclude --valid --noout --nonet x11-wm.xml env XML_CATALOG_FILES="file:///home/www/build/head/en_US.ISO8859-1/htdocs/ports/catalog-cwd.xml file:///home/www/build/head/en_US.ISO8859-1/share/xml/catalog.xml file:///home/www/build/head/share/xml/catalog.xml file:///home/www/build/head/share/xml/catalog-common.xml file:///usr/local/share/xml/catalog" /usr/local/bin/xsltproc --xinclude --nonet --debug -o x11-wm.html /home/www/build/head/share/xml/xhtml.xsl x11-wm.xml env XML_CATALOG_FILES="file:///home/www/build/head/en_US.ISO8859-1/htdocs/ports/catalog-cwd.xml file:///home/www/build/head/en_US.ISO8859-1/share/xml/catalog.xml file:///home/www/build/head/share/xml/catalog.xml file:///home/www/build/head/share/xml/catalog-common.xml file:///usr/local/share/xml/catalog" /usr/local/bin/xmllint --xinclude --valid --noout --nonet x11.xml env XML_CATALOG_FILES="file:///home/www/build/head/en_US.ISO8859-1/htdocs/ports/catalog-cwd.xml file:///home/www/build/head/en_US.ISO8859-1/share/xml/catalog.xml file:///home/www/build/head/share/xml/catalog.xml file:///home/www/build/head/share/xml/catalog-common.xml file:///usr/local/share/xml/catalog" /usr/local/bin/xsltproc --xinclude --nonet --debug -o x11.html /home/www/build/head/share/xml/xhtml.xsl x11.xml env XML_CATALOG_FILES="file:///home/www/build/head/en_US.ISO8859-1/htdocs/ports/catalog-cwd.xml file:///home/www/build/head/en_US.ISO8859-1/share/xml/catalog.xml file:///home/www/build/head/share/xml/catalog.xml file:///home/www/build/head/share/xml/catalog-common.xml file:///usr/local/share/xml/catalog" /usr/local/bin/xmllint --xinclude --valid --noout --nonet xfce.xml env XML_CATALOG_FILES="file:///home/www/build/head/en_US.ISO8859-1/htdocs/ports/catalog-cwd.xml file:///home/www/build/head/en_US.ISO8859-1/share/xml/catalog.xml file:///home/www/build/head/share/xml/catalog.xml file:///home/www/build/head/share/xml/catalog-common.xml file:///usr/local/share/xml/catalog" /usr/local/bin/xsltproc --xinclude --nonet --debug -o xfce.html /home/www/build/head/share/xml/xhtml.xsl xfce.xml env XML_CATALOG_FILES="file:///home/www/build/head/en_US.ISO8859-1/htdocs/ports/catalog-cwd.xml file:///home/www/build/head/en_US.ISO8859-1/share/xml/catalog.xml file:///home/www/build/head/share/xml/catalog.xml file:///home/www/build/head/share/xml/catalog-common.xml file:///usr/local/share/xml/catalog" /usr/local/bin/xmllint --xinclude --valid --noout --nonet zope.xml env XML_CATALOG_FILES="file:///home/www/build/head/en_US.ISO8859-1/htdocs/ports/catalog-cwd.xml file:///home/www/build/head/en_US.ISO8859-1/share/xml/catalog.xml file:///home/www/build/head/share/xml/catalog.xml file:///home/www/build/head/share/xml/catalog-common.xml file:///usr/local/share/xml/catalog" /usr/local/bin/xsltproc --xinclude --nonet --debug -o zope.html /home/www/build/head/share/xml/xhtml.xsl zope.xml cd growth; make all cd /home/www/build/head/en_US.ISO8859-1/htdocs/ports/growth/../../../../share/tools/portsgrowth; make DIRPRFX=ports/ all /usr/local/bin/gnuplot ports.plt /usr/local/bin/pngtopnm ports.png | /usr/local/bin/pnmtopng -i > status.png rm ports.png ===> relnotes ===> relnotes/CURRENT/relnotes (all) env XML_CATALOG_FILES="file:///home/www/build/relnotes/doc/en_US.ISO8859-1/relnotes/catalog-cwd.xml file:///home/www/build/head/en_US.ISO8859-1/share/xml/catalog.xml file:///home/www/build/head/share/xml/catalog.xml file:///home/www/build/head/share/xml/catalog-common.xml file:///usr/local/share/xml/catalog file:///home/www/build/relnotes/doc/en_US.ISO8859-1/relnotes/../../en_US.ISO8859-1/share/xml/catalog.xml file:///home/www/build/relnotes/doc/en_US.ISO8859-1/relnotes/../../share/xml/catalog.xml" /usr/local/bin/xmllint --nonet --noent --valid --dropdtd --xinclude /home/www/build/relnotes/doc/en_US.ISO8859-1/relnotes/article.xml > article.parsed.xml.tmp ==> Profiling env XML_CATALOG_FILES="file:///home/www/build/relnotes/doc/en_US.ISO8859-1/relnotes/catalog-cwd.xml file:///home/www/build/head/en_US.ISO8859-1/share/xml/catalog.xml file:///home/www/build/head/share/xml/catalog.xml file:///home/www/build/head/share/xml/catalog-common.xml file:///usr/local/share/xml/catalog file:///home/www/build/relnotes/doc/en_US.ISO8859-1/relnotes/../../en_US.ISO8859-1/share/xml/catalog.xml file:///home/www/build/relnotes/doc/en_US.ISO8859-1/relnotes/../../share/xml/catalog.xml" /usr/local/bin/xsltproc --param profile.attribute "'releasetype'" --param profile.value "'snapshot'" /usr/local/share/xsl/docbook-ns/profiling/profile.xsl article.parsed.xml.tmp > article.parsed.print.xml /bin/rm -f docbook.css /bin/cat /home/www/build/head/share/misc/docbook.css > docbook.css env XML_CATALOG_FILES="file:///home/www/build/relnotes/doc/en_US.ISO8859-1/relnotes/catalog-cwd.xml file:///home/www/build/head/en_US.ISO8859-1/share/xml/catalog.xml file:///home/www/build/head/share/xml/catalog.xml file:///home/www/build/head/share/xml/catalog-common.xml file:///usr/local/share/xml/catalog file:///home/www/build/relnotes/doc/en_US.ISO8859-1/relnotes/../../en_US.ISO8859-1/share/xml/catalog.xml file:///home/www/build/relnotes/doc/en_US.ISO8859-1/relnotes/../../share/xml/catalog.xml" /usr/local/bin/xsltproc --xinclude --nonet /home/www/build/head/en_US.ISO8859-1/share/xsl/freebsd-xhtml.xsl article.parsed.xml > article.html warning: failed to load external entity "article.parsed.xml" unable to parse article.parsed.xml *** [article.html] Error code 6 Stop in /home/www/build/relnotes/doc/en_US.ISO8859-1/relnotes. *** [all] Error code 1 Stop in /home/www/build/relnotes/doc/en_US.ISO8859-1. *** [all] Error code 1 Stop in /home/www/build/head/en_US.ISO8859-1/htdocs/relnotes. *** [all] Error code 1 Stop in /home/www/build/head/en_US.ISO8859-1/htdocs. 480.86 real 441.30 user 38.57 sys From owner-freebsd-doc@FreeBSD.ORG Thu Nov 7 17:05:34 2013 Return-Path: Delivered-To: doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 864E1339 for ; Thu, 7 Nov 2013 17:05:34 +0000 (UTC) (envelope-from root@ms.icomtech.cz) Received: from ms.icomtech.cz (ms.icomtech.cz [217.112.171.66]) (using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 026112E57 for ; Thu, 7 Nov 2013 17:05:33 +0000 (UTC) Received: (from root@localhost) by ms.icomtech.cz id rA7GRssi019066; Thu, 7 Nov 2013 17:27:54 +0100 Date: Thu, 7 Nov 2013 17:27:54 +0100 Message-Id: <201311071627.rA7GRssi019066@ms.icomtech.cz> From: mail-filter@ms.icomtech.cz To: doc@freebsd.org Subject: Zadrzene maily pro 07.11.2013 od 12:01 do 16:00 X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Nov 2013 17:05:34 -0000 CAS ODESILATEL VELIKOST VIRUS SPAM ID -------------------------------------------------------------------------------- 13:55 vf@icomtech.cz 2060 S 1107135520501 Subject: New females found near your area From owner-freebsd-doc@FreeBSD.ORG Thu Nov 7 17:20:19 2013 Return-Path: Delivered-To: freebsd-doc@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 63596D52 for ; Thu, 7 Nov 2013 17:20:19 +0000 (UTC) (envelope-from www-data@FreeBSD.org) Received: from build-web.stream.freebsd.org (build-web.stream.freebsd.org [IPv6:2001:1900:2254:206a::16:6504]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 4A93B2F5F for ; Thu, 7 Nov 2013 17:20:19 +0000 (UTC) Received: from build-web.stream.freebsd.org ([127.0.1.2]) by build-web.stream.freebsd.org (8.14.7/8.14.7) with ESMTP id rA7HKJ71021220 for ; Thu, 7 Nov 2013 17:20:19 GMT (envelope-from www-data@build-web.stream.freebsd.org) Received: (from www-data@localhost) by build-web.stream.freebsd.org (8.14.7/8.14.5/Submit) id rA7HKJGv021218 for freebsd-doc@FreeBSD.org; Thu, 7 Nov 2013 17:20:19 GMT (envelope-from www-data) Date: Thu, 7 Nov 2013 17:20:19 GMT From: User Www-data Message-Id: <201311071720.rA7HKJGv021218@build-web.stream.freebsd.org> To: freebsd-doc@FreeBSD.org Subject: FreeBSD web build failed on build-web.stream.freebsd.org X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Nov 2013 17:20:19 -0000 install -C -o www-data -g www-data -m 444 docbook.css /home/www/build/head/en_US.ISO8859-1/htdocs/doc/en_US.ISO8859-1/books/porters-handbook install -C -o www-data -g www-data -m 444 imagelib/callouts/1.png /home/www/build/head/en_US.ISO8859-1/htdocs/doc/en_US.ISO8859-1/books/porters-handbook/imagelib/callouts install -C -o www-data -g www-data -m 444 imagelib/callouts/2.png /home/www/build/head/en_US.ISO8859-1/htdocs/doc/en_US.ISO8859-1/books/porters-handbook/imagelib/callouts install -C -o www-data -g www-data -m 444 imagelib/callouts/3.png /home/www/build/head/en_US.ISO8859-1/htdocs/doc/en_US.ISO8859-1/books/porters-handbook/imagelib/callouts install -C -o www-data -g www-data -m 444 imagelib/callouts/4.png /home/www/build/head/en_US.ISO8859-1/htdocs/doc/en_US.ISO8859-1/books/porters-handbook/imagelib/callouts install -C -o www-data -g www-data -m 444 imagelib/callouts/5.png /home/www/build/head/en_US.ISO8859-1/htdocs/doc/en_US.ISO8859-1/books/porters-handbook/imagelib/callouts install -C -o www-data -g www-data -m 444 imagelib/callouts/6.png /home/www/build/head/en_US.ISO8859-1/htdocs/doc/en_US.ISO8859-1/books/porters-handbook/imagelib/callouts install -C -o www-data -g www-data -m 444 imagelib/callouts/7.png /home/www/build/head/en_US.ISO8859-1/htdocs/doc/en_US.ISO8859-1/books/porters-handbook/imagelib/callouts install -C -o www-data -g www-data -m 444 imagelib/callouts/8.png /home/www/build/head/en_US.ISO8859-1/htdocs/doc/en_US.ISO8859-1/books/porters-handbook/imagelib/callouts install -C -o www-data -g www-data -m 444 imagelib/callouts/9.png /home/www/build/head/en_US.ISO8859-1/htdocs/doc/en_US.ISO8859-1/books/porters-handbook/imagelib/callouts install -C -o www-data -g www-data -m 444 imagelib/callouts/10.png /home/www/build/head/en_US.ISO8859-1/htdocs/doc/en_US.ISO8859-1/books/porters-handbook/imagelib/callouts install -C -o www-data -g www-data -m 444 imagelib/callouts/11.png /home/www/build/head/en_US.ISO8859-1/htdocs/doc/en_US.ISO8859-1/books/porters-handbook/imagelib/callouts install -C -o www-data -g www-data -m 444 imagelib/callouts/12.png /home/www/build/head/en_US.ISO8859-1/htdocs/doc/en_US.ISO8859-1/books/porters-handbook/imagelib/callouts install -C -o www-data -g www-data -m 444 imagelib/callouts/13.png /home/www/build/head/en_US.ISO8859-1/htdocs/doc/en_US.ISO8859-1/books/porters-handbook/imagelib/callouts install -C -o www-data -g www-data -m 444 imagelib/callouts/14.png /home/www/build/head/en_US.ISO8859-1/htdocs/doc/en_US.ISO8859-1/books/porters-handbook/imagelib/callouts install -C -o www-data -g www-data -m 444 imagelib/callouts/15.png /home/www/build/head/en_US.ISO8859-1/htdocs/doc/en_US.ISO8859-1/books/porters-handbook/imagelib/callouts install -C -o www-data -g www-data -m 444 imagelib/callouts/16.png /home/www/build/head/en_US.ISO8859-1/htdocs/doc/en_US.ISO8859-1/books/porters-handbook/imagelib/callouts install -C -o www-data -g www-data -m 444 imagelib/callouts/17.png /home/www/build/head/en_US.ISO8859-1/htdocs/doc/en_US.ISO8859-1/books/porters-handbook/imagelib/callouts install -C -o www-data -g www-data -m 444 imagelib/callouts/18.png /home/www/build/head/en_US.ISO8859-1/htdocs/doc/en_US.ISO8859-1/books/porters-handbook/imagelib/callouts install -C -o www-data -g www-data -m 444 imagelib/callouts/19.png /home/www/build/head/en_US.ISO8859-1/htdocs/doc/en_US.ISO8859-1/books/porters-handbook/imagelib/callouts install -C -o www-data -g www-data -m 444 imagelib/callouts/20.png /home/www/build/head/en_US.ISO8859-1/htdocs/doc/en_US.ISO8859-1/books/porters-handbook/imagelib/callouts install -C -o www-data -g www-data -m 444 imagelib/callouts/21.png /home/www/build/head/en_US.ISO8859-1/htdocs/doc/en_US.ISO8859-1/books/porters-handbook/imagelib/callouts /home/www/build/head/en_US.ISO8859-1/htdocs/doc/faq -> /home/www/build/head/en_US.ISO8859-1/htdocs/doc/en_US.ISO8859-1/books/faq /home/www/build/head/en_US.ISO8859-1/htdocs/doc/handbook -> /home/www/build/head/en_US.ISO8859-1/htdocs/doc/en_US.ISO8859-1/books/handbook /home/www/build/head/en_US.ISO8859-1/htdocs/doc/en -> /home/www/build/head/en_US.ISO8859-1/htdocs/doc/en_US.ISO8859-1 ===> ports cd /home/www/build/head/en_US.ISO8859-1/htdocs/ports; make -f /home/www/build/head/en_US.ISO8859-1/htdocs/ports/Makefile.inc0 all cd growth; make all cd /home/www/build/head/en_US.ISO8859-1/htdocs/ports/growth/../../../../share/tools/portsgrowth; make DIRPRFX=ports/ all ===> relnotes ===> relnotes/CURRENT/relnotes (all) env XML_CATALOG_FILES="file:///home/www/build/relnotes/doc/en_US.ISO8859-1/relnotes/catalog-cwd.xml file:///home/www/build/head/en_US.ISO8859-1/share/xml/catalog.xml file:///home/www/build/head/share/xml/catalog.xml file:///home/www/build/head/share/xml/catalog-common.xml file:///usr/local/share/xml/catalog file:///home/www/build/relnotes/doc/en_US.ISO8859-1/relnotes/../../en_US.ISO8859-1/share/xml/catalog.xml file:///home/www/build/relnotes/doc/en_US.ISO8859-1/relnotes/../../share/xml/catalog.xml" /usr/local/bin/xmllint --nonet --noent --valid --dropdtd --xinclude /home/www/build/relnotes/doc/en_US.ISO8859-1/relnotes/article.xml > article.parsed.xml.tmp ==> Profiling env XML_CATALOG_FILES="file:///home/www/build/relnotes/doc/en_US.ISO8859-1/relnotes/catalog-cwd.xml file:///home/www/build/head/en_US.ISO8859-1/share/xml/catalog.xml file:///home/www/build/head/share/xml/catalog.xml file:///home/www/build/head/share/xml/catalog-common.xml file:///usr/local/share/xml/catalog file:///home/www/build/relnotes/doc/en_US.ISO8859-1/relnotes/../../en_US.ISO8859-1/share/xml/catalog.xml file:///home/www/build/relnotes/doc/en_US.ISO8859-1/relnotes/../../share/xml/catalog.xml" /usr/local/bin/xsltproc --param profile.attribute "'releasetype'" --param profile.value "'snapshot'" /usr/local/share/xsl/docbook-ns/profiling/profile.xsl article.parsed.xml.tmp > article.parsed.print.xml env XML_CATALOG_FILES="file:///home/www/build/relnotes/doc/en_US.ISO8859-1/relnotes/catalog-cwd.xml file:///home/www/build/head/en_US.ISO8859-1/share/xml/catalog.xml file:///home/www/build/head/share/xml/catalog.xml file:///home/www/build/head/share/xml/catalog-common.xml file:///usr/local/share/xml/catalog file:///home/www/build/relnotes/doc/en_US.ISO8859-1/relnotes/../../en_US.ISO8859-1/share/xml/catalog.xml file:///home/www/build/relnotes/doc/en_US.ISO8859-1/relnotes/../../share/xml/catalog.xml" /usr/local/bin/xsltproc --xinclude --nonet /home/www/build/head/en_US.ISO8859-1/share/xsl/freebsd-xhtml.xsl article.parsed.xml > article.html warning: failed to load external entity "article.parsed.xml" unable to parse article.parsed.xml *** [article.html] Error code 6 Stop in /home/www/build/relnotes/doc/en_US.ISO8859-1/relnotes. *** [all] Error code 1 Stop in /home/www/build/relnotes/doc/en_US.ISO8859-1. *** [all] Error code 1 Stop in /home/www/build/head/en_US.ISO8859-1/htdocs/relnotes. *** [all] Error code 1 Stop in /home/www/build/head/en_US.ISO8859-1/htdocs. 15.10 real 7.34 user 8.25 sys From owner-freebsd-doc@FreeBSD.ORG Thu Nov 7 18:20:19 2013 Return-Path: Delivered-To: freebsd-doc@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 411A9277 for ; Thu, 7 Nov 2013 18:20:19 +0000 (UTC) (envelope-from www-data@FreeBSD.org) Received: from build-web.stream.freebsd.org (build-web.stream.freebsd.org [IPv6:2001:1900:2254:206a::16:6504]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 2D9502347 for ; Thu, 7 Nov 2013 18:20:19 +0000 (UTC) Received: from build-web.stream.freebsd.org ([127.0.1.2]) by build-web.stream.freebsd.org (8.14.7/8.14.7) with ESMTP id rA7IKJNh036229 for ; Thu, 7 Nov 2013 18:20:19 GMT (envelope-from www-data@build-web.stream.freebsd.org) Received: (from www-data@localhost) by build-web.stream.freebsd.org (8.14.7/8.14.5/Submit) id rA7IKJIZ036226 for freebsd-doc@FreeBSD.org; Thu, 7 Nov 2013 18:20:19 GMT (envelope-from www-data) Date: Thu, 7 Nov 2013 18:20:19 GMT From: User Www-data Message-Id: <201311071820.rA7IKJIZ036226@build-web.stream.freebsd.org> To: freebsd-doc@FreeBSD.org Subject: FreeBSD web build failed on build-web.stream.freebsd.org X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Nov 2013 18:20:19 -0000 install -C -o www-data -g www-data -m 444 docbook.css /home/www/build/head/en_US.ISO8859-1/htdocs/doc/en_US.ISO8859-1/books/porters-handbook install -C -o www-data -g www-data -m 444 imagelib/callouts/1.png /home/www/build/head/en_US.ISO8859-1/htdocs/doc/en_US.ISO8859-1/books/porters-handbook/imagelib/callouts install -C -o www-data -g www-data -m 444 imagelib/callouts/2.png /home/www/build/head/en_US.ISO8859-1/htdocs/doc/en_US.ISO8859-1/books/porters-handbook/imagelib/callouts install -C -o www-data -g www-data -m 444 imagelib/callouts/3.png /home/www/build/head/en_US.ISO8859-1/htdocs/doc/en_US.ISO8859-1/books/porters-handbook/imagelib/callouts install -C -o www-data -g www-data -m 444 imagelib/callouts/4.png /home/www/build/head/en_US.ISO8859-1/htdocs/doc/en_US.ISO8859-1/books/porters-handbook/imagelib/callouts install -C -o www-data -g www-data -m 444 imagelib/callouts/5.png /home/www/build/head/en_US.ISO8859-1/htdocs/doc/en_US.ISO8859-1/books/porters-handbook/imagelib/callouts install -C -o www-data -g www-data -m 444 imagelib/callouts/6.png /home/www/build/head/en_US.ISO8859-1/htdocs/doc/en_US.ISO8859-1/books/porters-handbook/imagelib/callouts install -C -o www-data -g www-data -m 444 imagelib/callouts/7.png /home/www/build/head/en_US.ISO8859-1/htdocs/doc/en_US.ISO8859-1/books/porters-handbook/imagelib/callouts install -C -o www-data -g www-data -m 444 imagelib/callouts/8.png /home/www/build/head/en_US.ISO8859-1/htdocs/doc/en_US.ISO8859-1/books/porters-handbook/imagelib/callouts install -C -o www-data -g www-data -m 444 imagelib/callouts/9.png /home/www/build/head/en_US.ISO8859-1/htdocs/doc/en_US.ISO8859-1/books/porters-handbook/imagelib/callouts install -C -o www-data -g www-data -m 444 imagelib/callouts/10.png /home/www/build/head/en_US.ISO8859-1/htdocs/doc/en_US.ISO8859-1/books/porters-handbook/imagelib/callouts install -C -o www-data -g www-data -m 444 imagelib/callouts/11.png /home/www/build/head/en_US.ISO8859-1/htdocs/doc/en_US.ISO8859-1/books/porters-handbook/imagelib/callouts install -C -o www-data -g www-data -m 444 imagelib/callouts/12.png /home/www/build/head/en_US.ISO8859-1/htdocs/doc/en_US.ISO8859-1/books/porters-handbook/imagelib/callouts install -C -o www-data -g www-data -m 444 imagelib/callouts/13.png /home/www/build/head/en_US.ISO8859-1/htdocs/doc/en_US.ISO8859-1/books/porters-handbook/imagelib/callouts install -C -o www-data -g www-data -m 444 imagelib/callouts/14.png /home/www/build/head/en_US.ISO8859-1/htdocs/doc/en_US.ISO8859-1/books/porters-handbook/imagelib/callouts install -C -o www-data -g www-data -m 444 imagelib/callouts/15.png /home/www/build/head/en_US.ISO8859-1/htdocs/doc/en_US.ISO8859-1/books/porters-handbook/imagelib/callouts install -C -o www-data -g www-data -m 444 imagelib/callouts/16.png /home/www/build/head/en_US.ISO8859-1/htdocs/doc/en_US.ISO8859-1/books/porters-handbook/imagelib/callouts install -C -o www-data -g www-data -m 444 imagelib/callouts/17.png /home/www/build/head/en_US.ISO8859-1/htdocs/doc/en_US.ISO8859-1/books/porters-handbook/imagelib/callouts install -C -o www-data -g www-data -m 444 imagelib/callouts/18.png /home/www/build/head/en_US.ISO8859-1/htdocs/doc/en_US.ISO8859-1/books/porters-handbook/imagelib/callouts install -C -o www-data -g www-data -m 444 imagelib/callouts/19.png /home/www/build/head/en_US.ISO8859-1/htdocs/doc/en_US.ISO8859-1/books/porters-handbook/imagelib/callouts install -C -o www-data -g www-data -m 444 imagelib/callouts/20.png /home/www/build/head/en_US.ISO8859-1/htdocs/doc/en_US.ISO8859-1/books/porters-handbook/imagelib/callouts install -C -o www-data -g www-data -m 444 imagelib/callouts/21.png /home/www/build/head/en_US.ISO8859-1/htdocs/doc/en_US.ISO8859-1/books/porters-handbook/imagelib/callouts /home/www/build/head/en_US.ISO8859-1/htdocs/doc/faq -> /home/www/build/head/en_US.ISO8859-1/htdocs/doc/en_US.ISO8859-1/books/faq /home/www/build/head/en_US.ISO8859-1/htdocs/doc/handbook -> /home/www/build/head/en_US.ISO8859-1/htdocs/doc/en_US.ISO8859-1/books/handbook /home/www/build/head/en_US.ISO8859-1/htdocs/doc/en -> /home/www/build/head/en_US.ISO8859-1/htdocs/doc/en_US.ISO8859-1 ===> ports cd /home/www/build/head/en_US.ISO8859-1/htdocs/ports; make -f /home/www/build/head/en_US.ISO8859-1/htdocs/ports/Makefile.inc0 all cd growth; make all cd /home/www/build/head/en_US.ISO8859-1/htdocs/ports/growth/../../../../share/tools/portsgrowth; make DIRPRFX=ports/ all ===> relnotes ===> relnotes/CURRENT/relnotes (all) env XML_CATALOG_FILES="file:///home/www/build/relnotes/doc/en_US.ISO8859-1/relnotes/catalog-cwd.xml file:///home/www/build/head/en_US.ISO8859-1/share/xml/catalog.xml file:///home/www/build/head/share/xml/catalog.xml file:///home/www/build/head/share/xml/catalog-common.xml file:///usr/local/share/xml/catalog file:///home/www/build/relnotes/doc/en_US.ISO8859-1/relnotes/../../en_US.ISO8859-1/share/xml/catalog.xml file:///home/www/build/relnotes/doc/en_US.ISO8859-1/relnotes/../../share/xml/catalog.xml" /usr/local/bin/xmllint --nonet --noent --valid --dropdtd --xinclude /home/www/build/relnotes/doc/en_US.ISO8859-1/relnotes/article.xml > article.parsed.xml.tmp ==> Profiling env XML_CATALOG_FILES="file:///home/www/build/relnotes/doc/en_US.ISO8859-1/relnotes/catalog-cwd.xml file:///home/www/build/head/en_US.ISO8859-1/share/xml/catalog.xml file:///home/www/build/head/share/xml/catalog.xml file:///home/www/build/head/share/xml/catalog-common.xml file:///usr/local/share/xml/catalog file:///home/www/build/relnotes/doc/en_US.ISO8859-1/relnotes/../../en_US.ISO8859-1/share/xml/catalog.xml file:///home/www/build/relnotes/doc/en_US.ISO8859-1/relnotes/../../share/xml/catalog.xml" /usr/local/bin/xsltproc --param profile.attribute "'releasetype'" --param profile.value "'snapshot'" /usr/local/share/xsl/docbook-ns/profiling/profile.xsl article.parsed.xml.tmp > article.parsed.print.xml env XML_CATALOG_FILES="file:///home/www/build/relnotes/doc/en_US.ISO8859-1/relnotes/catalog-cwd.xml file:///home/www/build/head/en_US.ISO8859-1/share/xml/catalog.xml file:///home/www/build/head/share/xml/catalog.xml file:///home/www/build/head/share/xml/catalog-common.xml file:///usr/local/share/xml/catalog file:///home/www/build/relnotes/doc/en_US.ISO8859-1/relnotes/../../en_US.ISO8859-1/share/xml/catalog.xml file:///home/www/build/relnotes/doc/en_US.ISO8859-1/relnotes/../../share/xml/catalog.xml" /usr/local/bin/xsltproc --xinclude --nonet /home/www/build/head/en_US.ISO8859-1/share/xsl/freebsd-xhtml.xsl article.parsed.xml > article.html warning: failed to load external entity "article.parsed.xml" unable to parse article.parsed.xml *** [article.html] Error code 6 Stop in /home/www/build/relnotes/doc/en_US.ISO8859-1/relnotes. *** [all] Error code 1 Stop in /home/www/build/relnotes/doc/en_US.ISO8859-1. *** [all] Error code 1 Stop in /home/www/build/head/en_US.ISO8859-1/htdocs/relnotes. *** [all] Error code 1 Stop in /home/www/build/head/en_US.ISO8859-1/htdocs. 14.94 real 7.04 user 8.38 sys From owner-freebsd-doc@FreeBSD.ORG Thu Nov 7 18:23:21 2013 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 4D0A73A4 for ; Thu, 7 Nov 2013 18:23:21 +0000 (UTC) (envelope-from gabor@kovesdan.org) Received: from server.mypc.hu (server.mypc.hu [87.229.73.95]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 01672237F for ; Thu, 7 Nov 2013 18:23:20 +0000 (UTC) Received: from server.mypc.hu (localhost [127.0.0.1]) by server.mypc.hu (Postfix) with ESMTP id F319614D250C for ; Thu, 7 Nov 2013 19:23:18 +0100 (CET) X-Virus-Scanned: amavisd-new at !change-mydomain-variable!.example.com Received: from server.mypc.hu ([127.0.0.1]) by server.mypc.hu (server.mypc.hu [127.0.0.1]) (amavisd-new, port 10024) with LMTP id IQwXq2-n39qA for ; Thu, 7 Nov 2013 19:23:15 +0100 (CET) Received: from [192.168.0.10] (54034B4D.catv.pool.telekom.hu [84.3.75.77]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by server.mypc.hu (Postfix) with ESMTPSA id CC5FF14D2436 for ; Thu, 7 Nov 2013 19:23:15 +0100 (CET) Message-ID: <527BDA8B.3030908@kovesdan.org> Date: Thu, 07 Nov 2013 19:23:07 +0100 From: =?ISO-8859-1?Q?G=E1bor_K=F6vesd=E1n?= User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 MIME-Version: 1.0 To: freebsd-doc@freebsd.org Subject: Re: [HEADSUP] Merging DocBook 5.0 update References: <527BADCB.8030308@kovesdan.org> In-Reply-To: <527BADCB.8030308@kovesdan.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Nov 2013 18:23:21 -0000 On 2013.11.07. 16:12, Gábor Kövesdán wrote: > Hi, > > I will soon merge the DocBook 5.0 updates to head. The tree will > temporarily be locked until the merge is done. I will send out another > email I have finished. > The merge is done, head is now open again for commits. What you should know about the new infrastructure: - Basically, things work more or less in the same way, except that the tools, that we use for generating the printed output, are different. - Instead of the id attribute, now we use xml:id. - Linking is done with the xlink:href attribute, which can be used on most DocBook elements. Cross-references sill work with the xref element, these generate the link text based on the destination and thus are empty elements. If you want to specify the link text, use the link element with the link text enclosed in the element. - Instead of articleinfo, bookinfo, sect1info etc. now we simply use info. - For a more detailed explanation on the DocBook 5.0 markup changes see this: http://docbook.org/docs/howto/#changes I hope I will have time to update the fdp-primer soon as well. Before you commit, please make sure you run *make lint*. It will validate the documents and tell you about errors in the markup. If they validate fine, rendering should be OK. For this, you don't need Java, only PDF documents require it. There are some element name changes that are meant to reduce and rationalize our DocBook customization layer. I will report these back to the DocBook project, hoping that they will include some of our extensions in further versions: - makevar is now varname - maketarget is now buildtarget - svnref is now revnumber - devicename is now filename - username is now systemitem class="username" - groupname is now systemitem class="groupname" - hostid role=XXX is now systemitem role=YYY - filename role="package" is now package - filename role="port" is now package role="port" Thanks The FreeBSD Foundation for their support on this work and to Hiroki Sato (hrs@) for his comments and review on the pathset and to the rest of people, who commented on the PDF output. Also, big thanks to Glen Barber (gjb@) for updating the cluster to the new dependencies. I hope you will enjoy the new PDF documentation, which looks much better than the old one, yet it still needs some refinements. These adjustments will be done continuously from now on. Gabor From owner-freebsd-doc@FreeBSD.ORG Thu Nov 7 18:30:44 2013 Return-Path: Delivered-To: freebsd-doc@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 9403D4E4 for ; Thu, 7 Nov 2013 18:30:44 +0000 (UTC) (envelope-from www-data@FreeBSD.org) Received: from build-web.stream.freebsd.org (build-web.stream.freebsd.org [IPv6:2001:1900:2254:206a::16:6504]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 7285C240E for ; Thu, 7 Nov 2013 18:30:44 +0000 (UTC) Received: from build-web.stream.freebsd.org ([127.0.1.2]) by build-web.stream.freebsd.org (8.14.7/8.14.7) with ESMTP id rA7IUiWa050066 for ; Thu, 7 Nov 2013 18:30:44 GMT (envelope-from www-data@build-web.stream.freebsd.org) Received: (from www-data@localhost) by build-web.stream.freebsd.org (8.14.7/8.14.5/Submit) id rA7IUiOr050064 for freebsd-doc@FreeBSD.org; Thu, 7 Nov 2013 18:30:44 GMT (envelope-from www-data) Date: Thu, 7 Nov 2013 18:30:44 GMT From: User Www-data Message-Id: <201311071830.rA7IUiOr050064@build-web.stream.freebsd.org> To: freebsd-doc@FreeBSD.org Subject: FreeBSD web build failed on build-web.stream.freebsd.org X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Nov 2013 18:30:44 -0000 ^ /home/www/build/relnotes9/doc/en_US.ISO8859-1/relnotes/article.xml:1248: element para: validity error : No declaration for element para configuration files. ^ /home/www/build/relnotes9/doc/en_US.ISO8859-1/relnotes/article.xml:1249: element important: validity error : No declaration for element important ^ /home/www/build/relnotes9/doc/en_US.ISO8859-1/relnotes/article.xml:1250: element sect2: validity error : No declaration for element sect2 ^ /home/www/build/relnotes9/doc/en_US.ISO8859-1/relnotes/article.xml:1253: element title: validity error : No declaration for attribute id of element title User-visible incompatibilities ^ /home/www/build/relnotes9/doc/en_US.ISO8859-1/relnotes/article.xml:1253: element title: validity error : No declaration for element title User-visible incompatibilities ^ /home/www/build/relnotes9/doc/en_US.ISO8859-1/relnotes/article.xml:1259: element ulink: validity error : No declaration for attribute url of element ulink url="http://www.freebsd.org/releases/9.0R/relnotes-detailed.html#UPGRADE">Upgra ^ /home/www/build/relnotes9/doc/en_US.ISO8859-1/relnotes/article.xml:1260: element ulink: validity error : No declaration for element ulink Section in 9.0-RELEASE Release Notes carefully before ^ /home/www/build/relnotes9/doc/en_US.ISO8859-1/relnotes/article.xml:1262: element emphasis: validity error : No declaration for element emphasis FreeBSD mailing lists. ^ /home/www/build/relnotes9/doc/en_US.ISO8859-1/relnotes/article.xml:1262: element para: validity error : No declaration for element para FreeBSD mailing lists. ^ /home/www/build/relnotes9/doc/en_US.ISO8859-1/relnotes/article.xml:1263: element sect2: validity error : No declaration for element sect2 ^ /home/www/build/relnotes9/doc/en_US.ISO8859-1/relnotes/article.xml:1264: element sect1: validity error : No declaration for element sect1 ^ /home/www/build/relnotes9/doc/en_US.ISO8859-1/relnotes/article.xml:1265: element article: validity error : No declaration for element article ^ *** [article.parsed.xml] Error code 4 Stop in /home/www/build/relnotes9/doc/en_US.ISO8859-1/relnotes. *** [all] Error code 1 Stop in /home/www/build/relnotes9/doc/en_US.ISO8859-1. *** [all] Error code 1 Stop in /home/www/build/head/en_US.ISO8859-1/htdocs/relnotes. *** [all] Error code 1 Stop in /home/www/build/head/en_US.ISO8859-1/htdocs. 484.15 real 444.01 user 40.77 sys From owner-freebsd-doc@FreeBSD.ORG Fri Nov 8 06:09:24 2013 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 1CA17DF0 for ; Fri, 8 Nov 2013 06:09:24 +0000 (UTC) (envelope-from garythomas022@gmail.com) Received: from mail-pd0-x242.google.com (mail-pd0-x242.google.com [IPv6:2607:f8b0:400e:c02::242]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id E61312081 for ; Fri, 8 Nov 2013 06:09:23 +0000 (UTC) Received: by mail-pd0-f194.google.com with SMTP id v10so485541pde.5 for ; Thu, 07 Nov 2013 22:09:23 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:subject:date:message-id:mime-version:content-type :thread-index:content-language; bh=J/AvgmMZ+08O1GQeKQelSghIjXTSesNIDwd08o/oCts=; b=DGX8B+ygvLQ3iiFz550OdlTQ7Wjja+4yybxONUT82+AQG77Nf5HJgXGdKO+/6kdbBv Wd7jZ31WIlrD5B/AZFunXSpPeKN99Ve2kdDmQvJ8iIW5FdUh8+GGzF6Y2GvmG1HzmIP1 BkjUP0iX1oCF9O0KH0KnHfq55gnKWpX/YIJ9Maqi7HeXSUiI+SjRNJFop/ld5MxlO+64 pEvq4DKyMdKZ5kXpIj5EM3v5uIx93/OI3Pa8tCNGP9hjBhT1Yma1xHZkUTL9Sxr17S83 jAWFLqLjLeDfQtb4iY4pAVuCB++c8+Gsm1SUsVr7HtaQgiBQ3RFvoCqRu437tJVOx0F+ kYgg== X-Received: by 10.68.33.100 with SMTP id q4mr12927683pbi.119.1383890963373; Thu, 07 Nov 2013 22:09:23 -0800 (PST) Received: from rnsinfor16 ([182.64.61.47]) by mx.google.com with ESMTPSA id xe9sm11367436pab.0.2013.11.07.22.09.20 for (version=TLSv1 cipher=RC4-SHA bits=128/128); Thu, 07 Nov 2013 22:09:22 -0800 (PST) From: "garythomas022" To: Subject: Website Development Services Date: Fri, 8 Nov 2013 11:39:19 +0530 Message-ID: <019f01cedc49$16965f80$43c31e80$@com> MIME-Version: 1.0 X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: Ac7cSQSam/CQm6smRjea1uQOf/IMww== Content-Language: en-us x-cr-hashedpuzzle: BX4g CLJP CPjo Db/a FjSc FkJB G6bH HlOL IiNN JHh7 JVar J/Y3 KJaH KOSu Kt8K K4U/; 1; ZgByAGUAZQBiAHMAZAAtAGQAbwBjAEAAZgByAGUAZQBiAHMAZAAuAG8AcgBnAA==; Sosha1_v1; 7; {2910C339-6CEA-49FA-B47D-F86B72517EE6}; ZwBhAHIAeQB0AGgAbwBtAGEAcwAwADIAMgBAAGcAbQBhAGkAbAAuAGMAbwBtAA==; Fri, 08 Nov 2013 06:09:00 GMT; VwBlAGIAcwBpAHQAZQAgAEQAZQB2AGUAbABvAHAAbQBlAG4AdAAgAFMAZQByAHYAaQBjAGUAcwA= x-cr-puzzleid: {2910C339-6CEA-49FA-B47D-F86B72517EE6} Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Nov 2013 06:09:24 -0000 Hi, I am Gary Marketing Executive of IT Company Firm based in New Delhi, India. I have gone through your site and found that we can work together, we have 150+ designers,developers,professional content writers and SEO Masters in our company. We deliver quality services within timeframe with economical cost. We have expertise in " Trend MLS ( IDX Search ), Out Trigger, BST, RCI Holiday Network, HotelBEDs, iphone / Android apps". We have experts for PHP /JSP / ASP .NET languages and following open source products :- * Joomla Customization, * Drupal CMS Customization, * Magento, * OS Commerce, * X-Cart, * Zen Cart Customization, * PHPBB, * Wordpress, * Codeigniter, * MVC, * Zend Framework, * Symfony etc.. Please add Mr. Raj ( Technical Head ) for live chat on: -Skype Id: raj30jan, Google talk: raj30jan, Yahoo: raj30jan@ymail.com, MSN: raj30jan@hotmail.com. Email : raj30jan@gmail.com , Mobile : +91-9312639156 Do let me know if you have any question and I would be happy to send in more details. I look forward to hearing from you soon. Gary Thomas IT Company (Your Best Outsourcing Partner) Call : T. +91 93 126 39 156,+44 208 123 7861,+1 360 450 0557,Toll Free : +1 855 216 7791 Disclaimer: The CAN-SPAM Act of 2003 (Controlling the Assault of Non-Solicited Pornography and Marketing Act) establishes requirements for those who send commercial email, spells out penalties for spammers and companies whose products are advertised in spam if they violate the law, and gives consumers the right to ask mailers to stop spamming them. The above mail is in accordance to the Can Spam act of 2003: There are no deceptive subject lines and is a manual process through our efforts on World Wide Web. You can opt out by sending mail to garythomas022@gmail.com and we ensure you will not receive any such. From owner-freebsd-doc@FreeBSD.ORG Fri Nov 8 15:58:53 2013 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 8E6BAE6F for ; Fri, 8 Nov 2013 15:58:53 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 4595F21F0 for ; Fri, 8 Nov 2013 15:58:53 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.7/8.14.7) with ESMTP id rA8FwpeM081917; Fri, 8 Nov 2013 08:58:51 -0700 (MST) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.7/8.14.7/Submit) with ESMTP id rA8Fwn64081914; Fri, 8 Nov 2013 08:58:51 -0700 (MST) (envelope-from wblock@wonkity.com) Date: Fri, 8 Nov 2013 08:58:49 -0700 (MST) From: Warren Block To: =?ISO-8859-15?Q?G=E1bor_K=F6vesd=E1n?= Subject: Re: [HEADSUP] Merging DocBook 5.0 update In-Reply-To: <527BDA8B.3030908@kovesdan.org> Message-ID: References: <527BADCB.8030308@kovesdan.org> <527BDA8B.3030908@kovesdan.org> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="3512871622-301177168-1383926331=:8372" X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (wonkity.com [127.0.0.1]); Fri, 08 Nov 2013 08:58:51 -0700 (MST) Cc: freebsd-doc@freebsd.org X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Nov 2013 15:58:53 -0000 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --3512871622-301177168-1383926331=:8372 Content-Type: TEXT/PLAIN; charset=iso-8859-1; format=flowed Content-Transfer-Encoding: 8BIT On Thu, 7 Nov 2013, Gábor Kövesdán wrote: > On 2013.11.07. 16:12, Gábor Kövesdán wrote: >> Hi, >> >> I will soon merge the DocBook 5.0 updates to head. The tree will >> temporarily be locked until the merge is done. I will send out another >> email I have finished. >> > The merge is done, head is now open again for commits. Thanks for your work on this! In HTML, programlistings used to be a div (
but are now 
.  Likewise for .  The 
existing CSS has no entries for this.

Userinput is also not bold, another CSS issue.

I can fix these in the CSS.  But should they be fixed there, or in the 
generation of the HTML?

Thanks!
--3512871622-301177168-1383926331=:8372--

From owner-freebsd-doc@FreeBSD.ORG  Sat Nov  9 11:29:13 2013
Return-Path: 
Delivered-To: freebsd-doc@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTP id E0FDC997
 for ; Sat,  9 Nov 2013 11:29:12 +0000 (UTC)
 (envelope-from juris.kaminskis@gmail.com)
Received: from mail-wi0-x234.google.com (mail-wi0-x234.google.com
 [IPv6:2a00:1450:400c:c05::234])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (No client certificate requested)
 by mx1.freebsd.org (Postfix) with ESMTPS id 6C84B2824
 for ; Sat,  9 Nov 2013 11:29:12 +0000 (UTC)
Received: by mail-wi0-f180.google.com with SMTP id ey11so471905wid.13
 for ; Sat, 09 Nov 2013 03:29:10 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:in-reply-to:references:date:message-id:subject:from:to
 :cc:content-type;
 bh=thcimkdj2M13gWyYctMVzG0ofQI2UNTdp2Drf2bKdno=;
 b=aH67TrKOuJrAXJCWWZJeInpEU3QEgUJ7q4/lp/mKpLP2pga2l7uXBPeFvq9CoWx3zl
 4H6GCLYOa2OyyhhwSFeTV5EMBV9aapCuGYy7N6H0H7HUexSadg3rTpss/WIIXfTYIHhJ
 C4jWViGb7y/VgqDPHTJpjBhH2BF/gzx2U7KNo0xLiwCXAz6KWMwj6yDJB5pKnSYjB2t/
 ft0bw7zYeBoFASNgVBd7mWQy+/916sNjDTy771SBcRjOLxMqm35PCCgCeELOS7sWcE/0
 3NoGGiWhm9AF5qK1JIwchxJT1GHRV3xgVnn8zXehQ2ZWKaUiTd0rKZe/ZgobHPC7hFtn
 zYAA==
MIME-Version: 1.0
X-Received: by 10.180.37.114 with SMTP id x18mr5729444wij.64.1383996550769;
 Sat, 09 Nov 2013 03:29:10 -0800 (PST)
Received: by 10.194.185.101 with HTTP; Sat, 9 Nov 2013 03:29:10 -0800 (PST)
In-Reply-To: 
References: 
 
 
 
 
Date: Sat, 9 Nov 2013 13:29:10 +0200
Message-ID: 
Subject: Re: TODO item: Add info on USB printers
From: Juris Kaminskis 
To: Warren Block 
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
X-Content-Filtered-By: Mailman/MimeDel 2.1.14
Cc: freebsd-doc@freebsd.org
X-BeenThere: freebsd-doc@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Documentation project 
List-Unsubscribe: ,
 
List-Archive: 
List-Post: 
List-Help: 
List-Subscribe: ,
 
X-List-Received-Date: Sat, 09 Nov 2013 11:29:13 -0000

2013/11/5 Warren Block 

> On Mon, 4 Nov 2013, Juris Kaminskis wrote:
>
>
>>             Thank you for working on this.  The entire printing chapter
>> really needs a rewrite, and I've been meaning to write an outline for wh=
at
>> a new printing chapter
>>             should cover.  In the meantime, please look at
>>             http://www.wonkity.com/~wblock/docs/html/lpdprinting.htmland=
 see if it is adequate in the meantime.
>>
>>
>> I am not sure I understand what should I do next from this. Can you let
>> me know how can I contribute further?
>>
>
> I've done some preliminary work on a rewrite of the printing chapter. Can
> you look at the article above and see if anything important is left out?
>
> Thanks!


Chapter Printing Directly requires some minor update I think:

Printing Directly

A spooler is not required. Sometimes it=92s simpler to just print data
directly to a device or to troubleshoot printing setup:

% cat myfile.txt > /dev/lpt0

   */dev/lpt0*

the standard parallel port

*/dev/ulpt0*

the standard USB printer port

*/dev/unlpt0*

the non-reset USB printer port, use if */dev/ulpt0* does not work correctly

netcat (*nc(1) *) can be used to print
directly to network printers:

% nc nethplaser 9100 < myfile.txt

   *nethplaser*

the DNS name of the network printer

*9100*

the network port used by HP and some other brands

*lpd* printing using the standard *lpr(1) * i=
s
usually more convenient and more versatile than direct printing.


 Many printers use different file transfer protocols, therefore convert
myfile.txt in appropriate format. Several convertors exist to name few:
ghostscript and foo2zjs.

For example for certain types of HP Laserjet use XQX stream:
foo2xqx-wrapper myfile.ps > /dev/ulpt0


and chapter Adding filter first parapgraph would in my mind be better if
like this:
Adding A Filter

Many Unix applications produce *PostScript* output, but not all printers
are Postcript compliant. Verify what file protocol printer accepts and then
proceed adding a specific filter. For example many inexpensive printers
understand  *PCL*This filter uses *Ghostscript* to translate PostScript
code into PCL. Save it in*/usr/local/libexec/ps2pcl* and then make it
executable: