From owner-freebsd-doc@FreeBSD.ORG Mon Jun 18 07:50:09 2012 Return-Path: Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A44FF106566B for ; Mon, 18 Jun 2012 07:50:09 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 5ECBF8FC0C for ; Mon, 18 Jun 2012 07:50:09 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q5I7o9Bi008036 for ; Mon, 18 Jun 2012 07:50:09 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q5I7o995008035; Mon, 18 Jun 2012 07:50:09 GMT (envelope-from gnats) Resent-Date: Mon, 18 Jun 2012 07:50:09 GMT Resent-Message-Id: <201206180750.q5I7o995008035@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, Alain AUDEBERT Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 67CF41065672 for ; Mon, 18 Jun 2012 07:42:32 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from red.freebsd.org (red.freebsd.org [IPv6:2001:4f8:fff6::22]) by mx1.freebsd.org (Postfix) with ESMTP id 5381E8FC1B for ; Mon, 18 Jun 2012 07:42:32 +0000 (UTC) Received: from red.freebsd.org (localhost [127.0.0.1]) by red.freebsd.org (8.14.4/8.14.4) with ESMTP id q5I7gVce094762 for ; Mon, 18 Jun 2012 07:42:31 GMT (envelope-from nobody@red.freebsd.org) Received: (from nobody@localhost) by red.freebsd.org (8.14.4/8.14.4/Submit) id q5I7gVc9094761; Mon, 18 Jun 2012 07:42:31 GMT (envelope-from nobody) Message-Id: <201206180742.q5I7gVc9094761@red.freebsd.org> Date: Mon, 18 Jun 2012 07:42:31 GMT From: Alain AUDEBERT To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-3.1 Cc: Subject: docs/169191: Upgrade the mirrors list X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Jun 2012 07:50:09 -0000 >Number: 169191 >Category: docs >Synopsis: Upgrade the mirrors list >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-doc >State: open >Quarter: >Keywords: >Date-Required: >Class: change-request >Submitter-Id: current-users >Arrival-Date: Mon Jun 18 07:50:09 UTC 2012 >Closed-Date: >Last-Modified: >Originator: Alain AUDEBERT >Release: 9.0-p3 >Organization: >Environment: >Description: I have just set up a new 'mirmon' for monitoring the FreeBSD's project FTP mirrors : http://mirmon.hub4.fr It sounds like many mirror are unavaible : ftp6.FreeBSD.org ftp.ar.FreeBSD.org ftp.bg.FreeBSD.org ftp2.bg.FreeBSD.org ftp2.lv.FreeBSD.org ftp3.no.FreeBSD.org ftp.sg.FreeBSD.org ftp2.si.FreeBSD.org ftp2.ua.FreeBSD.org ftp6.uk.FreeBSD.org ftp1.us.FreeBSD.org After discuss, it appear the authoritative mirrors list is : http://svnweb.freebsd.org/doc/head/share/sgml/mirrors.xml And is used for build the Handbook's FTP mirrors list : http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/mirrors-ftp.html >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-doc@FreeBSD.ORG Mon Jun 18 09:20:13 2012 Return-Path: Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id F27D9106566C for ; Mon, 18 Jun 2012 09:20:13 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id C7A168FC12 for ; Mon, 18 Jun 2012 09:20:13 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q5I9KDQX098975 for ; Mon, 18 Jun 2012 09:20:13 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q5I9KDCG098974; Mon, 18 Jun 2012 09:20:13 GMT (envelope-from gnats) Resent-Date: Mon, 18 Jun 2012 09:20:13 GMT Resent-Message-Id: <201206180920.q5I9KDCG098974@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, Alain AUDEBERT Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id BA77B106566B for ; Mon, 18 Jun 2012 09:17:39 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from red.freebsd.org (red.freebsd.org [IPv6:2001:4f8:fff6::22]) by mx1.freebsd.org (Postfix) with ESMTP id 8C6528FC18 for ; Mon, 18 Jun 2012 09:17:39 +0000 (UTC) Received: from red.freebsd.org (localhost [127.0.0.1]) by red.freebsd.org (8.14.4/8.14.4) with ESMTP id q5I9HdEa050449 for ; Mon, 18 Jun 2012 09:17:39 GMT (envelope-from nobody@red.freebsd.org) Received: (from nobody@localhost) by red.freebsd.org (8.14.4/8.14.4/Submit) id q5I9HdtF050448; Mon, 18 Jun 2012 09:17:39 GMT (envelope-from nobody) Message-Id: <201206180917.q5I9HdtF050448@red.freebsd.org> Date: Mon, 18 Jun 2012 09:17:39 GMT From: Alain AUDEBERT To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-3.1 Cc: Subject: docs/169193: Harmonize canadian mirrors X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Jun 2012 09:20:14 -0000 >Number: 169193 >Category: docs >Synopsis: Harmonize canadian mirrors >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 Jun 18 09:20:13 UTC 2012 >Closed-Date: >Last-Modified: >Originator: Alain AUDEBERT >Release: FreeBSD-9.0-p3 >Organization: >Environment: >Description: In http://svnweb.freebsd.org/doc/head/share/sgml/mirrors.xml?view=markup (line 416) : ftp://ftp2.ca.FreeBSD.org/ Can be replace by : ftp://ftp2.ca.FreeBSD.org/pub/FreeBSD/ >How-To-Repeat: >Fix: Change line 416 by : ftp://ftp2.ca.FreeBSD.org/pub/FreeBSD/ >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-doc@FreeBSD.ORG Mon Jun 18 09:44:03 2012 Return-Path: Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 24E78106564A; Mon, 18 Jun 2012 09:44:03 +0000 (UTC) (envelope-from bcr@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id ED2878FC0A; Mon, 18 Jun 2012 09:44:02 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q5I9i2FJ026837; Mon, 18 Jun 2012 09:44:02 GMT (envelope-from bcr@freefall.freebsd.org) Received: (from bcr@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q5I9i2cx026833; Mon, 18 Jun 2012 09:44:02 GMT (envelope-from bcr) Date: Mon, 18 Jun 2012 09:44:02 GMT Message-Id: <201206180944.q5I9i2cx026833@freefall.freebsd.org> To: bcr@FreeBSD.org, freebsd-doc@FreeBSD.org, bcr@FreeBSD.org From: bcr@FreeBSD.org Cc: Subject: Re: docs/169193: Harmonize canadian mirrors X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Jun 2012 09:44:03 -0000 Synopsis: Harmonize canadian mirrors Responsible-Changed-From-To: freebsd-doc->bcr Responsible-Changed-By: bcr Responsible-Changed-When: Mon Jun 18 09:43:43 UTC 2012 Responsible-Changed-Why: Take this one. http://www.freebsd.org/cgi/query-pr.cgi?pr=169193 From owner-freebsd-doc@FreeBSD.ORG Mon Jun 18 11:06:13 2012 Return-Path: Delivered-To: freebsd-doc@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7E42B106566C for ; Mon, 18 Jun 2012 11:06:13 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 667BF8FC16 for ; Mon, 18 Jun 2012 11:06:13 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q5IB6DnD007054 for ; Mon, 18 Jun 2012 11:06:13 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q5IB6CNe007051 for freebsd-doc@FreeBSD.org; Mon, 18 Jun 2012 11:06:12 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 18 Jun 2012 11:06:12 GMT Message-Id: <201206181106.q5IB6CNe007051@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: FreeBSD doc list Cc: Subject: Current unassigned doc problem reports X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Jun 2012 11:06:13 -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/169191 doc Upgrade the mirrors list o docs/169158 doc [patch] iasl(8) man page is out of date o docs/169089 doc [geli] [PATCH] geli(8) needs clarity concerning key sc o docs/169056 doc [patch] sysctl*(3) cannot fail with EFAULT if name con o docs/168962 doc cp(1) & mv(1) pages don't mention ACLs or extended att o 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/168853 doc Obsolete docs in web o docs/168852 doc Obsolete docs should be detached from Makefile at leas o docs/168814 doc [patch] remove `d` negative pointer EINVAL requirement o docs/168803 doc Remove outdated smp info o docs/167742 doc Update documentation for group 5, and newgrp 1 o docs/167741 doc group(5): Group Passwords do not work and are not docu 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 docs/165657 doc Web site Features page aging 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/164800 doc Handbook's installation topic doesn't mention ZFS o docs/164772 doc incorrect ipfw sched parameters in manual 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/162419 doc [request] please document (new) zfs and zpool cmdline o docs/162404 doc [handbook] IPv6 link-local address compared with IPv4 o docs/162380 doc Documentation lacking for getfacl/setfacl 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/160447 doc [handbook] Developer's Handbook contains some outdated o docs/160446 doc [handbook] Handbook sound setup seems outdated o docs/160445 doc [handbook] Handbook does not mention ACL 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/159298 doc [handbook] document Konqueror with Webkit support to i 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/157049 doc FreeBSD Handbook: Chapter 14 (Security) Inaccuracy p docs/156955 doc bug in share/man/man2/setsockopt.2 o docs/156920 doc isspecial(3) is not helpful o docs/156853 doc [patch] Update docs: jail(8) security issues with worl 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/155773 doc dialog(1): dialog manpages not updated 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/146958 doc bad link to "XaQti XMAC II datasheet" in sk(4) manual o docs/146521 doc [handbook] Update IPv6 system handbook section to ment o docs/145719 doc [patch] 7.3 relnotes erroneously describes new getpage o docs/145699 doc hexdump(1) mutes all format qualifier output following o docs/145644 doc Add artical about creating manpage from scratch 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/144630 doc [patch] domainname(1) manpage contains old information o docs/144515 doc [handbook] Expand handbook Table of contents o docs/144488 doc share/examples/etc/make.conf: contains dangerous examp o docs/143850 doc procfs(5) manpage for status > controlling terminal is o docs/143416 doc [handbook] IPFW handbook page issues o docs/143408 doc man filedesc(9) is missing o docs/142168 doc [patch] ld(1): ldd(1) not mentioned in ld(1) manpage 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 p docs/140457 doc [patch] Grammar fix for isspace(3) 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/134123 doc The RUNQUEUE(9) man page is out of date 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/126590 doc [patch] Write routine called forever in Sample Echo Ps o docs/126484 doc libc function res-zonscut2 is not documented o docs/125921 doc lpd(8) talks about blocks in minfree while it is KB in 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/120539 doc Inconsistent ipfw's man page 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/118902 doc [patch] wrong signatures in d2i_RSAPublicKey man pages o docs/118020 doc ipfilter(4): man pages query for man 4 ipfilter return o docs/116080 doc PREFIX is documented, but not the more important LOCAL p docs/115065 doc [patch] sync ps.1 with p_flag and keywords 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/112682 doc Handbook GEOM_GPT explanation does not provide accurat 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 p docs/110061 doc [patch] tuning(7) missing reference to vfs.read_max o docs/109981 doc No manual entry for post-grohtml o docs/109977 doc No manual entry for ksu o docs/109973 doc No manual entry for c++filt 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/106135 doc [request] articles/vinum needs to be updated 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/100196 doc man login.conf does explain not "unlimited" o docs/99506 doc FreeBSD Handbook addition: IPv6 Server Settings 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/94625 doc [patch] growfs man page -- document "panic: not enough o docs/92626 doc jail manpage should mention disabling some periodic sc o docs/91506 doc ndis(4) man page should be more specific about support 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/61605 doc [request] Improve documentation for i386 disk geometry 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/59044 doc [patch] doc.docbook.mk does not properly handle a sour 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 docs/50211 doc [patch] doc.docbook.mk: fix textfile creation o docs/48101 doc [patch] Add documentation on the fixit disk 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/38982 doc [patch] developers-handbook/Jail fix o docs/38556 doc EPS file of beastie, as addition to existing examples s docs/33589 doc [patch] to doc.docbook.mk to post process .tex files. o docs/27605 doc [patch] Cross-document references () 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 193 problems total. From owner-freebsd-doc@FreeBSD.ORG Mon Jun 18 12:50:15 2012 Return-Path: Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 759C8106564A for ; Mon, 18 Jun 2012 12:50:15 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 593E88FC1A for ; Mon, 18 Jun 2012 12:50:15 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q5ICoFmx010354 for ; Mon, 18 Jun 2012 12:50:15 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q5ICoFr6010353; Mon, 18 Jun 2012 12:50:15 GMT (envelope-from gnats) Date: Mon, 18 Jun 2012 12:50:15 GMT Message-Id: <201206181250.q5ICoFr6010353@freefall.freebsd.org> To: freebsd-doc@FreeBSD.org From: "John W. O'Brien" Cc: Subject: Re: docs/169089: [geli] [PATCH] geli(8) needs clarity concerning key scope/type/purpose X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: "John W. O'Brien" List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Jun 2012 12:50:15 -0000 The following reply was made to PR docs/169089; it has been noted by GNATS. From: "John W. O'Brien" To: bug-followup@FreeBSD.org Cc: Subject: Re: docs/169089: [geli] [PATCH] geli(8) needs clarity concerning key scope/type/purpose Date: Mon, 18 Jun 2012 08:46:42 -0400 This is a multi-part message in MIME format. --------------060800050602060505030102 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 See attached patch that includes updates based on feedback from pjd@ on freebsd-geom@. - - /keylen/datakeylen/ change vetoed - - fix markup style -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJP3yMyAAoJEEdKvTwaez9wB6kH/2w6LcLcN5pFqcuDkhzHzNiK vdtTgh2U9So8OcT4emK+86s1EYgS7x6ZEqdoriE13VJSAdPnU00pXkDC5lKm8wO6 +OSK8TUK61xttws87B3ro72dN/2xHSRf003cQz1vRFlLNVSrm2kwlY1SCoM3Zl8S eIy4rbLVKkL2AgMafnK3NmXelH5OtwHt8VXtuqrUVNexkunVip/lAB5n/UUDkdfA KIIa52pyoq/i7e9dojbiwaHDhBGV9t3vnOXWVwbUE+RAPdnHJIk9svChTSSpYefF 3Yq6dgCkHFiMo0PYb5CRNtwetTaaX6AS3Ikm2Bf0o1ktTP+cQY1GhNOSaSqGcAA= =OXKt -----END PGP SIGNATURE----- --------------060800050602060505030102 Content-Type: text/plain; charset=UTF-8; name="patch-head_sbin_geom_class_eli_geli.8-2.txt" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="patch-head_sbin_geom_class_eli_geli.8-2.txt" Index: geli.8 =================================================================== --- geli.8 (revision 236978) +++ geli.8 (working copy) @@ -24,7 +24,7 @@ .\" .\" $FreeBSD$ .\" -.Dd April 28, 2012 +.Dd June 18, 2012 .Dt GELI 8 .Os .Sh NAME @@ -186,14 +186,15 @@ or .Nm HMAC/SHA512 . .It -Can create a key from a couple of components (user entered passphrase, random -bits from a file, etc.). +Can create a User Key from up to two, piecewise components: a passphrase +entered via prompt or read from one or more passfiles; a keyfile read from +one or more files. .It Allows encryption of the root partition. The user will be asked for the passphrase before the root file system is mounted. .It -The passphrase of the user is strengthened with: +Strengthens the passphrase component of the User Key with: .Rs .%A B. Kaliski .%T "PKCS #5: Password-Based Cryptography Specification, Version 2.0." @@ -201,7 +202,7 @@ .%N 2898 .Re .It -Allows the use of two independent keys (e.g., a +Allows the use of two independent User Keys (e.g., a .Qq "user key" and a .Qq "company key" ) . @@ -210,8 +211,8 @@ .Nm performs simple sector-to-sector encryption. .It -Allows Master Keys to be backed up and restored, -so that if a user has to quickly destroy his keys, +Allows the encrypted Master Key to be backed up and restored, +so that if a user has to quickly destroy key material, it is possible to get the data back by restoring keys from backup. .It @@ -219,8 +220,8 @@ (so users do not have to remember to detach providers after unmounting the file systems). .It -Allows attaching a provider with a random, one-time key - useful for swap -partitions and temporary file systems. +Allows attaching a provider with a random, one-time Master Key - +useful for swap partitions and temporary file systems. .It Allows verification of data integrity (data authentication). .It @@ -233,7 +234,8 @@ .Bl -tag -width ".Cm configure" .It Cm init Initialize the provider which needs to be encrypted. -Here you can set up the cryptographic algorithm to use, key length, etc. +Here you can set up the cryptographic algorithm to use, Data Key length, +etc. The last sector of the provider is used to store metadata. The .Cm init @@ -289,37 +291,58 @@ The default and recommended algorithm is .Nm AES-XTS . .It Fl i Ar iterations -Number of iterations to use with PKCS#5v2. +Number of iterations to use with PKCS#5v2 when processing User Key +passphrase component. If this option is not specified, .Nm will find the number of iterations which is equal to 2 seconds of crypto work. If 0 is given, PKCS#5v2 will not be used. +PKCS#5v2 processing is performed once, after all parts of the passphrase +component have been read. .It Fl J Ar newpassfile -Specifies a file which contains the passphrase or its part. +Specifies a file which contains the passphrase component of the User Key +(or part of it). If .Ar newpassfile is given as -, standard input will be used. Only the first line (excluding new-line character) is taken from the given file. -This argument can be specified multiple times. +This argument can be specified multiple times, which has the effect of +reassembling a single passphrase split across multiple files. +Cannot be combined with the +.Fl P +option. .It Fl K Ar newkeyfile -Specifies a file which contains part of the key. +Specifies a file which contains the keyfile component of the User Key +(or part of it). If .Ar newkeyfile is given as -, standard input will be used. -This argument can be specified multiple times. +This argument can be specified multiple times, which has the effect of +reassembling a single keyfile split across multiple keyfile parts. .It Fl l Ar keylen -Key length to use with the given cryptographic algorithm. -If not given, the default key length for the given algorithm is used, which is: -128 for -.Nm AES-XTS , -.Nm AES-CBC , -.Nm Blowfish-CBC -and -.Nm Camellia-CBC -and 192 for -.Nm 3DES-CBC . +Data Key length to use with the given cryptographic algorithm. +If the length is not specified, the selected algorithm uses its +.Em default +key length. +.Bl -ohang -offset indent +.It Nm AES-XTS +.Em 128 , +256 +.It Nm AES-CBC , Nm Camilla-CBC +.Em 128 , +192, +256 +.It Nm Blowfish-CBC +.Em 128 ++ n * 32, for n=[0..10] +.It Nm 3DES-CBC +.Em 192 +.El .It Fl P -Do not use passphrase as the key component. +Do not use a passphrase as a component of the User Key. +Cannot be combined with the +.Fl J +option. .It Fl s Ar sectorsize Change decrypted provider's sector size. Increasing the sector size allows increased performance, @@ -337,9 +360,9 @@ .El .It Cm attach Attach the given provider. -The master key will be decrypted using the given -passphrase/keyfile and a new GEOM provider will be created using the given -provider's name with an +The encrypted Master Key will be loaded from the metadata and decrypted +using the given passphrase/keyfile and a new GEOM provider will be created +using the given provider's name with an .Qq .eli suffix. .Pp @@ -357,28 +380,33 @@ .Cm detach subcommand. .It Fl j Ar passfile -Specifies a file which contains the passphrase or its part. +Specifies a file which contains the passphrase component of the User Key +(or part of it). For more information see the description of the .Fl J option for the .Cm init subcommand. .It Fl k Ar keyfile -Specifies a file which contains part of the key. +Specifies a file which contains the keyfile component of the User Key +(or part of it). For more information see the description of the .Fl K option for the .Cm init subcommand. .It Fl p -Do not use passphrase as the key component. +Do not use a passphrase as a component of the User Key. +Cannot be combined with the +.Fl j +option. .It Fl r Attach read-only provider. It will not be opened for writing. .El .It Cm detach Detach the given providers, which means remove the devfs entry -and clear the keys from memory. +and clear the Master Key and Data Keys from memory. .Pp Additional options include: .Bl -tag -width ".Fl f" @@ -391,7 +419,7 @@ last time even if it was only opened for reading. .El .It Cm onetime -Attach the given providers with random, one-time keys. +Attach the given providers with a random, one-time (ephemeral) Master Key. The command can be used to encrypt swap partitions or temporary file systems. .Pp Additional options include: @@ -415,7 +443,7 @@ .Cm attach subcommand. .It Fl l Ar keylen -Key length to use with the given cryptographic algorithm. +Data Key length to use with the given cryptographic algorithm. For more information, see the description of the .Cm init subcommand. @@ -439,15 +467,18 @@ Remove the BOOT flag from the given providers. .El .It Cm setkey -Change or setup (if not yet initialized) selected key. -There is one master key, which can be encrypted with two independent user keys. +Install a copy of the Master Key into the selected slot, encrypted with +a new User Key. +If the selected slot is populated, replace the existing copy. +A provider has one Master Key, which can be stored in one or both slots, +each encrypted with an independent User Key. With the .Cm init subcommand, only key number 0 is initialized. -The key can always be changed: for an attached provider, +The User Key can be changed at any time: for an attached provider, for a detached provider, or on the backup file. When a provider is attached, the user does not have to provide -an old passphrase/keyfile. +an existing passphrase/keyfile. .Pp Additional options include: .Bl -tag -width ".Fl J Ar newpassfile" @@ -458,44 +489,54 @@ .Cm setkey subcommand, only one key has to be defined and this key must be changed. .It Fl j Ar passfile -Specifies a file which contains the old passphrase or its part. +Specifies a file which contains the passphrase component of a current User Key +(or part of it). .It Fl J Ar newpassfile -Specifies a file which contains the new passphrase or its part. +Specifies a file which contains the passphrase component of the new User Key +(or part of it). .It Fl k Ar keyfile -Specifies a file which contains part of the old key. +Specifies a file which contains the keyfile component of a current User Key +(or part of it). .It Fl K Ar newkeyfile -Specifies a file which contains part of the new key. +Specifies a file which contains the keyfile component of the new User Key +(or part of it). .It Fl n Ar keyno -Specifies the number of the key to change (could be 0 or 1). +Specifies the index number of the Master Key copy to change (could be 0 or 1). If the provider is attached and no key number is given, the key used for attaching the provider will be changed. If the provider is detached (or we are operating on a backup file) -and no key number is given, the key decrypted with the passphrase/keyfile -will be changed. +and no key number is given, the first Master Key copy to be successfully +decrypted with the provided User Key passphrase/keyfile will be changed. .It Fl p -Do not use passphrase as the old key component. +Do not use a passphrase as a component of the current User Key. +Cannot be combined with the +.Fl j +option. .It Fl P -Do not use passphrase as the new key component. +Do not use a passphrase as a component of the new User Key. +Cannot be combined with the +.Fl J +option. .El .It Cm delkey -Destroy (overwrite with random data) the selected key. +Destroy (overwrite with random data) the selected Master Key copy. If one is destroying keys for an attached provider, the provider -will not be detached even if all keys are destroyed. +will not be detached even if all copies of the Master Key are destroyed. It can even be rescued with the .Cm setkey -subcommand. +subcommand because the Master Key is still in memory. .Pp Additional options include: .Bl -tag -width ".Fl a Ar keyno" .It Fl a -Destroy all keys (does not need +Destroy all copies of the Master Key (does not need .Fl f option). .It Fl f Force key destruction. -This option is needed to destroy the last key. +This option is needed to destroy the last copy of the Master Key. .It Fl n Ar keyno -Specifies the key number. +Specifies the index number of the Master Key copy. If the provider is attached and no key number is given, the key used for attaching the provider will be destroyed. If provider is detached (or we are operating on a backup file) the key number @@ -503,8 +544,8 @@ .El .It Cm kill This command should be used only in emergency situations. -It will destroy all the keys on a given provider and will detach it forcibly -(if it is attached). +It will destroy all copies of the Master Key on a given provider and will +detach it forcibly (if it is attached). This is absolutely a one-way command - if you do not have a metadata backup, your data is gone for good. In case the provider was attached with the @@ -542,8 +583,8 @@ .El .It Cm suspend Suspend device by waiting for all inflight requests to finish, clearing all -sensitive information (like keys) from kernel memory, and blocking all -further I/O requests until the +sensitive information (like the Master Key and Data Keys) from kernel memory, +and blocking all further I/O requests until the .Cm resume subcommand is executed. This functionality is useful for laptops: when one wants to suspend a @@ -553,8 +594,8 @@ the .Cm suspend subcommand can be used. -Any access to the encrypted device will be blocked until the keys are -recovered through the +Any access to the encrypted device will be blocked until the Master Key is +reloaded through the .Cm resume subcommand. Thus there is no need to close nor unmount anything. @@ -584,21 +625,26 @@ Additional options include: .Bl -tag -width ".Fl j Ar passfile" .It Fl j Ar passfile -Specifies a file which contains the passphrase or its part. +Specifies a file which contains the passphrase component of the User Key +(or part of it). For more information see the description of the .Fl J option for the .Cm init subcommand. .It Fl k Ar keyfile -Specifies a file which contains part of the key. +Specifies a file which contains the keyfile component of the User Key +(or part of it). For more information see the description of the .Fl K option for the .Cm init subcommand. .It Fl p -Do not use passphrase as the key component. +Do not use a passphrase as a component of the User Key. +Cannot be combined with the +.Fl j +option. .El .It Cm resize Inform @@ -626,6 +672,9 @@ subcommand will print metadata version used by each of them. .It Cm clear Clear metadata from the given providers. +.Em WARNING : +This will erase with zeros the encrypted Master Key copies stored in the +metadata. .It Cm dump Dump metadata stored on the given providers. .It Cm list @@ -647,6 +696,36 @@ .It Fl v Be more verbose. .El +.Sh KEY SUMMARY +.Ss Master Key +Upon +.Cm init , +the +.Nm +utility generates a random Master Key for the provider. +The Master Key never changes during the lifetime of the provider. +Each copy of the provider metadata, active or backed up to a file, can store +up to two, independently-encrypted copies of the Master Key. +.Ss User Key +Each stored copy of the Master Key is encrypted with a User Key, which +is generated by the +.Nm +utility from a passphrase and/or a keyfile. +The +.Nm +utility first reads all parts of the keyfile in the order specified on the +command line, then reads all parts of the stored passphrase in the order +specified on the command line. +If no passphrase parts are specified, the system prompts the user to enter +the passphrase. +The passphrase is optionally strengthened by PKCS#5v2. +The User Key is a digest computed over the concatenated keyfile and passphrase. +.Ss Data Key +During operation, one or more Data Keys are deterministically derived by +the kernel from the Master Key and cached in memory. +The number of Data Keys used by a given provider, and the way they are +derived, depend on the GELI version and whether the provider is configured to +use data authentication. .Sh SYSCTL VARIABLES The following .Xr sysctl 8 @@ -677,7 +756,7 @@ This variable should be set in .Pa /boot/loader.conf . .It Va kern.geom.eli.overwrites : No 5 -Specifies how many times the Master-Key will be overwritten +Specifies how many times the Master Key will be overwritten with random values when it is destroyed. After this operation it is filled with zeros. .It Va kern.geom.eli.visible_passphrase : No 0 @@ -699,18 +778,19 @@ crypto requests with one interrupt. The crypto card and the driver has to support this feature. .It Va kern.geom.eli.key_cache_limit : No 8192 -Specifies how many encryption keys to cache. +Specifies how many Data Keys to cache. The default limit (8192 keys) will allow caching of all keys for a 4TB provider with 512 byte sectors and will take around 1MB of memory. .It Va kern.geom.eli.key_cache_hits -Reports how many times we were looking up a key and it was already in cache. -This sysctl is not updated for providers that need less keys than the limit -specified in +Reports how many times we were looking up a Data Key and it was already in +cache. +This sysctl is not updated for providers that need fewer Data Keys than +the limit specified in .Va kern.geom.eli.key_cache_limit . .It Va kern.geom.eli.key_cache_misses -Reports how many times we were looking up a key and it was not in cache. -This sysctl is not updated for providers that need fewer keys than the limit +Reports how many times we were looking up a Data Key and it was not in cache. +This sysctl is not updated for providers that need fewer Data Keys than the limit specified in .Va kern.geom.eli.key_cache_limit . .El @@ -738,7 +818,7 @@ # geli detach da2.eli .Ed .Pp -Create an encrypted provider, but use two keys: +Create an encrypted provider, but use two User Keys: one for your employee and one for you as the company's security officer (so it's not a tragedy if the employee .Qq accidentally @@ -760,7 +840,7 @@ # dd if=/dev/random of=/mnt/pendrive/keys/`hostname` bs=64 count=1 # geli init -P -K /mnt/pendrive/keys/`hostname` /dev/ad0s1e # geli backup /dev/ad0s1e /mnt/pendrive/backups/`hostname` -(use key number 0, so the encrypted Master Key will be overwritten by this) +(use key number 0, so the encrypted Master Key will be re-encrypted by this) # geli setkey -n 0 -k /mnt/pendrive/keys/`hostname` /dev/ad0s1e (allow the user to enter his passphrase) Enter new passphrase: @@ -776,8 +856,8 @@ .Pp The example below shows how to configure two providers which will be attached on boot (before the root file system is mounted). -One of them is using passphrase and three keyfiles and the other is using only a -keyfile: +One of them is using passphrase and three keyfile parts and the other is +using only a keyfile in one part: .Bd -literal -offset indent # dd if=/dev/random of=/dev/da0 bs=1m # dd if=/dev/random of=/boot/keys/da0.key0 bs=32k count=1 --------------060800050602060505030102 Content-Type: application/octet-stream; name="patch-head_sbin_geom_class_eli_geli.8-2.txt.sig" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="patch-head_sbin_geom_class_eli_geli.8-2.txt.sig" iQEcBAABAgAGBQJP3yMyAAoJEEdKvTwaez9w6hYH/iv36Nu2dRzDqmj9hLErinYNHH0SxNne 5eacGlIwLdukDrYKd9Z8ZSZ+y+YiyQebm7JreiprKCFOmBuk+QmEdwWFL5QcJ/WNFOHQIe0Z XdzC8y4Qipny57/BXSY5/ysWj0P46xJz1UpgnRtOvIWN/zbzyAsAfExcmgfepS4cUZ35DQc6 a6l/ugwsLdFvKZFELlKWFE2lvf2yWkrfU72zXqsATX1gAxkYlDhV6nuOFupFozzhJhZjvKcL 4CudMRGdDNIXwpjbhTGPmz3fiRh2IzPNR9stpTJyOgZu4zSeWbfCbz0HWxS7cxO3mBsn7Bbd PPCRTVydooUpzoBtfJCN3Pk= --------------060800050602060505030102-- From owner-freebsd-doc@FreeBSD.ORG Mon Jun 18 14:58:39 2012 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2F6551065672 for ; Mon, 18 Jun 2012 14:58:39 +0000 (UTC) (envelope-from perrin@apotheon.com) Received: from oproxy5-pub.bluehost.com (oproxy5.bluehost.com [IPv6:2605:dc00:100:2::a5]) by mx1.freebsd.org (Postfix) with SMTP id D93198FC08 for ; Mon, 18 Jun 2012 14:58:38 +0000 (UTC) Received: (qmail 2477 invoked by uid 0); 18 Jun 2012 14:58:37 -0000 Received: from unknown (HELO box543.bluehost.com) (74.220.219.143) by cpoproxy2.bluehost.com with SMTP; 18 Jun 2012 14:58:37 -0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=apotheon.com; s=default; h=Content-Type:MIME-Version:Message-ID:Subject:To:From:Date; bh=U2QSQ58FPil0PPJEU36F3Fl9Mau65DJEeuHGDvZ9Ig0=; b=Q5ZlaeGFwDUJ9AO/9UsolZnhrTwQyCK0N7BnW+PRa3hVbP10+NxTqAKPPBTXtCArlLOZUVy4j7sSC+RRavMHWwWEh4GTQIJzMSP9fo6HN03WA0zimVrhqaJnXZ7s50x/; Received: from [24.8.180.234] (port=62442 helo=localhost) by box543.bluehost.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.76) (envelope-from ) id 1SgdPZ-0000Tb-19 for freebsd-doc@freebsd.org; Mon, 18 Jun 2012 08:58:37 -0600 Date: Mon, 18 Jun 2012 08:58:36 -0600 From: Chad Perrin To: FreeBSD Docs Message-ID: <20120618145836.GB18641@hemlock.hydra> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.21 (2010-09-15) X-Identified-User: {2737:box543.bluehost.com:apotheon:apotheon.com} {sentby:smtp auth 24.8.180.234 authed with perrin@apotheon.com} Subject: PR Documentation X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Jun 2012 14:58:39 -0000 Is there no clear, explicit user documentation for the process of composing and submitting a PR, or is my search skill just very weak? -- Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ] From owner-freebsd-doc@FreeBSD.ORG Mon Jun 18 15:15:16 2012 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4CC12106566B for ; Mon, 18 Jun 2012 15:15:16 +0000 (UTC) (envelope-from db@db.net) Received: from diana.db.net (diana.db.net [66.113.102.10]) by mx1.freebsd.org (Postfix) with ESMTP id 3288A8FC08 for ; Mon, 18 Jun 2012 15:15:16 +0000 (UTC) Received: from night.db.net (localhost [127.0.0.1]) by diana.db.net (Postfix) with ESMTP id C9BCD2AA509; Mon, 18 Jun 2012 09:15:09 -0600 (MDT) Received: by night.db.net (Postfix, from userid 1000) id 57EDF5C60; Mon, 18 Jun 2012 10:15:01 -0500 (EST) Date: Mon, 18 Jun 2012 10:15:01 -0500 From: Diane Bruce To: Chad Perrin Message-ID: <20120618151501.GA70463@night.db.net> References: <20120618145836.GB18641@hemlock.hydra> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20120618145836.GB18641@hemlock.hydra> User-Agent: Mutt/1.4.2.3i Cc: FreeBSD Docs Subject: Re: PR Documentation X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Jun 2012 15:15:16 -0000 On Mon, Jun 18, 2012 at 08:58:36AM -0600, Chad Perrin wrote: > Is there no clear, explicit user documentation for the process of > composing and submitting a PR, or is my search skill just very weak? man send-pr - Diane -- - db@FreeBSD.org db@db.net http://www.db.net/~db Nowadays tar can compress using yesterdays latest technologies! From owner-freebsd-doc@FreeBSD.ORG Mon Jun 18 15:18:10 2012 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 290B21065674 for ; Mon, 18 Jun 2012 15:18:10 +0000 (UTC) (envelope-from cswiger@mac.com) Received: from nk11p00mm-asmtp002.mac.com (nk11p00mm-asmtp002.mac.com [17.158.161.1]) by mx1.freebsd.org (Postfix) with ESMTP id 0BAAC8FC17 for ; Mon, 18 Jun 2012 15:18:10 +0000 (UTC) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; CHARSET=US-ASCII Received: from [10.1.7.42] (96-24-78-202.sfo.clearwire-wmx.net [96.24.78.202]) by nk11p00mm-asmtp002.mac.com (Oracle Communications Messaging Server 7u4-23.01(7.0.4.23.0) 64bit (built Aug 10 2011)) with ESMTPSA id <0M5T00F3LJTWA720@nk11p00mm-asmtp002.mac.com> for freebsd-doc@freebsd.org; Mon, 18 Jun 2012 15:17:57 +0000 (GMT) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.7.7855,1.0.260,0.0.0000 definitions=2012-06-18_01:2012-06-18, 2012-06-18, 1970-01-01 signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 ipscore=0 suspectscore=0 phishscore=0 bulkscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=6.0.2-1012030000 definitions=main-1206180133 From: Chuck Swiger In-reply-to: <20120618145836.GB18641@hemlock.hydra> Date: Mon, 18 Jun 2012 08:17:55 -0700 Message-id: <3534E936-8293-456C-BE58-EB42B51C7CA9@mac.com> References: <20120618145836.GB18641@hemlock.hydra> To: Chad Perrin X-Mailer: Apple Mail (2.1084) Cc: FreeBSD Docs Subject: Re: PR Documentation X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Jun 2012 15:18:10 -0000 On Jun 18, 2012, at 7:58 AM, Chad Perrin wrote: > Is there no clear, explicit user documentation for the process of > composing and submitting a PR, or is my search skill just very weak? The latter. :-) First hit from: http://lmgtfy.com/?q=FreeBSD+send-pr [ ...or... ] http://lmgtfy.com/?q=FreeBSD+submit+pr ...locates the send-pr web form here: http://www.freebsd.org/send-pr.html ...which links to an article about submitting PRs here: http://www.freebsd.org/doc/en_US.ISO8859-1/articles/problem-reports/article.html Regards, -- -Chuck From owner-freebsd-doc@FreeBSD.ORG Mon Jun 18 17:53:33 2012 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0784A10656A6 for ; Mon, 18 Jun 2012 17:53:33 +0000 (UTC) (envelope-from perrin@apotheon.com) Received: from oproxy8-pub.bluehost.com (oproxy8.bluehost.com [IPv6:2605:dc00:100:2::a8]) by mx1.freebsd.org (Postfix) with SMTP id A633A8FC0C for ; Mon, 18 Jun 2012 17:53:32 +0000 (UTC) Received: (qmail 14711 invoked by uid 0); 18 Jun 2012 17:53:32 -0000 Received: from unknown (HELO box543.bluehost.com) (74.220.219.143) by oproxy8.bluehost.com with SMTP; 18 Jun 2012 17:53:32 -0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=apotheon.com; s=default; h=In-Reply-To:Content-Type:MIME-Version:References:Message-ID:Subject:Cc:To:From:Date; bh=5J/yekWv0HZFG/8gcHRcrXQH/PhDa/LNpwZgxe5B9SY=; b=a93qYv6f9CSz7LzV4q9G4T6OrcrkYwgsqommwnHjJGUbI9m4/ju6ryO8sS9uwx0gJx37IG9Nh/0agd4n4LdIiNOK25my06JoOmYmCQux6uNZfqIuGCpSViFzCPkHC5O3; Received: from [24.8.180.234] (port=63607 helo=localhost) by box543.bluehost.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.76) (envelope-from ) id 1Sgg8p-0001JG-De; Mon, 18 Jun 2012 11:53:31 -0600 Date: Mon, 18 Jun 2012 11:53:31 -0600 From: Chad Perrin To: Diane Bruce Message-ID: <20120618175331.GA887@hemlock.hydra> References: <20120618145836.GB18641@hemlock.hydra> <20120618151501.GA70463@night.db.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20120618151501.GA70463@night.db.net> User-Agent: Mutt/1.5.21 (2010-09-15) X-Identified-User: {2737:box543.bluehost.com:apotheon:apotheon.com} {sentby:smtp auth 24.8.180.234 authed with perrin@apotheon.com} Cc: FreeBSD Docs Subject: Re: PR Documentation X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Jun 2012 17:53:33 -0000 On Mon, Jun 18, 2012 at 10:15:01AM -0500, Diane Bruce wrote: > On Mon, Jun 18, 2012 at 08:58:36AM -0600, Chad Perrin wrote: > > Is there no clear, explicit user documentation for the process of > > composing and submitting a PR, or is my search skill just very weak? > > man send-pr Unfortunately, that particular manpage (along with man pr) serves as an excellent example of exactly what I was *not* trying to find when I said "clear, explicit user documentation". It leaves one with almost as many questions as one had to begin with -- if not more. Luckily, Chuck Swiger pointed me at something that I somehow overlooked and appears much more useful; you apparently overlooked it, too. I'll be checking it out to see if it serves the purpose well: http://www.freebsd.org/doc/en_US.ISO8859-1/articles/problem-reports/article.html -- Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ] From owner-freebsd-doc@FreeBSD.ORG Mon Jun 18 17:54:15 2012 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E1EF2106564A for ; Mon, 18 Jun 2012 17:54:15 +0000 (UTC) (envelope-from perrin@apotheon.com) Received: from oproxy1-pub.bluehost.com (oproxy1.bluehost.com [IPv6:2605:dc00:100:2::a1]) by mx1.freebsd.org (Postfix) with SMTP id 8C7EB8FC08 for ; Mon, 18 Jun 2012 17:54:15 +0000 (UTC) Received: (qmail 26722 invoked by uid 0); 18 Jun 2012 17:54:15 -0000 Received: from unknown (HELO box543.bluehost.com) (74.220.219.143) by oproxy1.bluehost.com with SMTP; 18 Jun 2012 17:54:15 -0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=apotheon.com; s=default; h=In-Reply-To:Content-Type:MIME-Version:References:Message-ID:Subject:Cc:To:From:Date; bh=ffrXqRBgIvkGXNBDx7twx3LVfUwDhyc64g2DshHs1yk=; b=kuqIQVEPXg+EYasigeMkEyJCv3h2f/2uLOXMwz8Q4emoPC6/yVqkok2WHSILHWWNLxr9hVUDnmy+dUCktSXSmFlewwu0q4cx95JwgWXBK0nxs2H3m8LyWfIaYXMmzbL1; Received: from [24.8.180.234] (port=63623 helo=localhost) by box543.bluehost.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.76) (envelope-from ) id 1Sgg9W-00048C-Qz; Mon, 18 Jun 2012 11:54:14 -0600 Date: Mon, 18 Jun 2012 11:54:14 -0600 From: Chad Perrin To: Chuck Swiger Message-ID: <20120618175414.GB887@hemlock.hydra> References: <20120618145836.GB18641@hemlock.hydra> <3534E936-8293-456C-BE58-EB42B51C7CA9@mac.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3534E936-8293-456C-BE58-EB42B51C7CA9@mac.com> User-Agent: Mutt/1.5.21 (2010-09-15) X-Identified-User: {2737:box543.bluehost.com:apotheon:apotheon.com} {sentby:smtp auth 24.8.180.234 authed with perrin@apotheon.com} Cc: FreeBSD Docs Subject: Re: PR Documentation X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Jun 2012 17:54:16 -0000 On Mon, Jun 18, 2012 at 08:17:55AM -0700, Chuck Swiger wrote: > On Jun 18, 2012, at 7:58 AM, Chad Perrin wrote: > > Is there no clear, explicit user documentation for the process of > > composing and submitting a PR, or is my search skill just very weak? > > The latter. :-) First hit from: > > http://lmgtfy.com/?q=FreeBSD+send-pr [ ...or... ] > http://lmgtfy.com/?q=FreeBSD+submit+pr > > ...locates the send-pr web form here: > > http://www.freebsd.org/send-pr.html > > ...which links to an article about submitting PRs here: > > http://www.freebsd.org/doc/en_US.ISO8859-1/articles/problem-reports/article.html Thanks. That last URI appears to be exactly the kind of thing I needed. I'll give it a read and see how well it explains things. -- Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ] From owner-freebsd-doc@FreeBSD.ORG Mon Jun 18 18:03:24 2012 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 60EF2106564A for ; Mon, 18 Jun 2012 18:03:24 +0000 (UTC) (envelope-from cswiger@mac.com) Received: from nk11p00mm-asmtp004.mac.com (nk11p00mm-asmtp004.mac.com [17.158.161.3]) by mx1.freebsd.org (Postfix) with ESMTP id 431648FC1A for ; Mon, 18 Jun 2012 18:03:24 +0000 (UTC) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; CHARSET=US-ASCII Received: from cswiger1.apple.com (unknown [17.209.4.71]) by nk11p00mm-asmtp004.mac.com (Oracle Communications Messaging Server 7u4-23.01(7.0.4.23.0) 64bit (built Aug 10 2011)) with ESMTPSA id <0M5T00H31RH91H50@nk11p00mm-asmtp004.mac.com> for freebsd-doc@freebsd.org; Mon, 18 Jun 2012 18:03:11 +0000 (GMT) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.7.7855,1.0.260,0.0.0000 definitions=2012-06-18_04:2012-06-18, 2012-06-18, 1970-01-01 signatures=0 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 ipscore=0 suspectscore=0 phishscore=0 bulkscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=6.0.2-1012030000 definitions=main-1206180174 From: Chuck Swiger In-reply-to: <20120618175414.GB887@hemlock.hydra> Date: Mon, 18 Jun 2012 11:03:08 -0700 Message-id: <45FE38F5-3BE7-44A2-8240-F11BF0AE9559@mac.com> References: <20120618145836.GB18641@hemlock.hydra> <3534E936-8293-456C-BE58-EB42B51C7CA9@mac.com> <20120618175414.GB887@hemlock.hydra> To: Chad Perrin X-Mailer: Apple Mail (2.1084) Cc: FreeBSD Docs Subject: Re: PR Documentation X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Jun 2012 18:03:24 -0000 On Jun 18, 2012, at 10:54 AM, Chad Perrin wrote: >> http://www.freebsd.org/doc/en_US.ISO8859-1/articles/problem-reports/article.html > > Thanks. That last URI appears to be exactly the kind of thing I needed. > I'll give it a read and see how well it explains things. It ought to do a decent job, hopefully.... :-) Regards, -- -Chuck From owner-freebsd-doc@FreeBSD.ORG Mon Jun 18 18:15:17 2012 Return-Path: Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 504AB1065672; Mon, 18 Jun 2012 18:15:17 +0000 (UTC) (envelope-from bcr@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 24EAA8FC0C; Mon, 18 Jun 2012 18:15:17 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q5IIFHad022574; Mon, 18 Jun 2012 18:15:17 GMT (envelope-from bcr@freefall.freebsd.org) Received: (from bcr@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q5IIFHY3022570; Mon, 18 Jun 2012 18:15:17 GMT (envelope-from bcr) Date: Mon, 18 Jun 2012 18:15:17 GMT Message-Id: <201206181815.q5IIFHY3022570@freefall.freebsd.org> To: bcr@FreeBSD.org, freebsd-doc@FreeBSD.org, bcr@FreeBSD.org From: bcr@FreeBSD.org Cc: Subject: Re: docs/168939: Port upgrade documentation missing from Application Jail X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Jun 2012 18:15:17 -0000 Synopsis: Port upgrade documentation missing from Application Jail Responsible-Changed-From-To: freebsd-doc->bcr Responsible-Changed-By: bcr Responsible-Changed-When: Mon Jun 18 18:14:49 UTC 2012 Responsible-Changed-Why: I will work on this one. http://www.freebsd.org/cgi/query-pr.cgi?pr=168939 From owner-freebsd-doc@FreeBSD.ORG Mon Jun 18 22:22:44 2012 Return-Path: Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id BC1001065670; Mon, 18 Jun 2012 22:22:44 +0000 (UTC) (envelope-from brd@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 8FE268FC0C; Mon, 18 Jun 2012 22:22:44 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q5IMMiZ2057843; Mon, 18 Jun 2012 22:22:44 GMT (envelope-from brd@freefall.freebsd.org) Received: (from brd@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q5IMMiV0057839; Mon, 18 Jun 2012 22:22:44 GMT (envelope-from brd) Date: Mon, 18 Jun 2012 22:22:44 GMT Message-Id: <201206182222.q5IMMiV0057839@freefall.freebsd.org> To: brd@FreeBSD.org, freebsd-doc@FreeBSD.org, brd@FreeBSD.org From: brd@FreeBSD.org Cc: Subject: Re: docs/169191: Upgrade the mirrors list X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Jun 2012 22:22:44 -0000 Synopsis: Upgrade the mirrors list Responsible-Changed-From-To: freebsd-doc->brd Responsible-Changed-By: brd Responsible-Changed-When: Mon Jun 18 22:22:28 UTC 2012 Responsible-Changed-Why: Grab. http://www.freebsd.org/cgi/query-pr.cgi?pr=169191 From owner-freebsd-doc@FreeBSD.ORG Tue Jun 19 22:12:22 2012 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5E8651065670 for ; Tue, 19 Jun 2012 22:12:22 +0000 (UTC) (envelope-from bjk@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 459208FC19; Tue, 19 Jun 2012 22:12:22 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q5JMCMXs065675; Tue, 19 Jun 2012 22:12:22 GMT (envelope-from bjk@freebsd.org) Received: from localhost (bjk@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) with ESMTP id q5JMCL1S065672; Tue, 19 Jun 2012 22:12:22 GMT (envelope-from bjk@freebsd.org) X-Authentication-Warning: freefall.freebsd.org: bjk owned process doing -bs Date: Tue, 19 Jun 2012 22:12:21 +0000 (UTC) From: Benjamin Kaduk To: Varuna In-Reply-To: <4FDB7404.1070703@eudaemonicsystems.net> Message-ID: References: <20120609120028.B03851065678@hub.freebsd.org> <4FDB7404.1070703@eudaemonicsystems.net> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-doc@freebsd.org Subject: Re: man page for dhclient.conf(5) error in script location X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Jun 2012 22:12:22 -0000 On Fri, 15 Jun 2012, Varuna wrote: > Hello Folks, > > The man page dhclient.conf(5) under FreeBSD 8.0 has an error in the script > location indicated in the EXAMPLES. The script dhclient-script is indicated to > be under /etc, while it is located under /sbin. I do not believe this is an error. Per dhclient.conf.5, the script directive specifies a DHCP client configuration script, and in the example given in the EXAMPLES section, it is entirely reasonable to have a custom configuration script for that interface. In that case, the default /sbin/dhclient-script would not be appropriate, and a custom version of it needed. Putting such a custom configuration script in /etc is in keeping with the traditional location for system configuration files. -Ben Kaduk From owner-freebsd-doc@FreeBSD.ORG Wed Jun 20 02:31:30 2012 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 606D11065673 for ; Wed, 20 Jun 2012 02:31:30 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from glenbarber.us (onyx.glenbarber.us [199.48.134.227]) by mx1.freebsd.org (Postfix) with SMTP id 1E0828FC0A for ; Wed, 20 Jun 2012 02:31:30 +0000 (UTC) Received: (qmail 40187 invoked by uid 0); 19 Jun 2012 22:31:29 -0400 Received: from unknown (HELO glenbarber.us) (75.97.141.105) by 0 with SMTP; 19 Jun 2012 22:31:29 -0400 Date: Tue, 19 Jun 2012 22:31:27 -0400 From: Glen Barber To: Benjamin Kaduk Message-ID: <20120620023127.GB1554@glenbarber.us> References: <20120609120028.B03851065678@hub.freebsd.org> <4FDB7404.1070703@eudaemonicsystems.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="GRPZ8SYKNexpdSJ7" Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD 10.0-CURRENT amd64 User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-doc@freebsd.org, Varuna Subject: Re: man page for dhclient.conf(5) error in script location X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Jun 2012 02:31:30 -0000 --GRPZ8SYKNexpdSJ7 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Jun 19, 2012 at 10:12:21PM +0000, Benjamin Kaduk wrote: > On Fri, 15 Jun 2012, Varuna wrote: >=20 > > Hello Folks, > > > > The man page dhclient.conf(5) under FreeBSD 8.0 has an error in the scr= ipt > > location indicated in the EXAMPLES. The script dhclient-script is indi= cated to > > be under /etc, while it is located under /sbin. >=20 > I do not believe this is an error. > Per dhclient.conf.5, the script directive specifies a DHCP client=20 > configuration script, and in the example given in the EXAMPLES section, i= t=20 > is entirely reasonable to have a custom configuration script for that=20 > interface. In that case, the default /sbin/dhclient-script would not be= =20 > appropriate, and a custom version of it needed. Putting such a custom=20 > configuration script in /etc is in keeping with the traditional location= =20 > for system configuration files. >=20 I personally feel it should be made more clear in the dhclient.conf(5) manual, maybe by a comment in the sample configuration? Alternatively, it can be updated to /usr/local/etc (for example), but that assumes /usr and its children filessytems are available and mounted at the time the script is run. Glen --GRPZ8SYKNexpdSJ7 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iQEcBAEBCAAGBQJP4TX/AAoJEFJPDDeguUajdRAIALtib0yDkpcOD2XIazVnIv78 WT3Hl3Dv9K54Ac59dUMo1QlcMi716Acnit+hSJ4RjICbgEPMy2tLnCvG/tl6qP8n jGJhL81SXniQab0yjzl7RgxRZ42s5gSIGtiwSZzF+/gknVSRBuZ0ZZbb65f2zSws kCrZh7RO8MzRiUin3LbC1VbhEAU9oEE0hmugz4SDXKMLFyscQ1CcC8cEva7NEKsa E4itWr1zy1HT3TJP/2C5kzx13M+Ks7ZMhWpyEuqSkMyf7/UcKWkQyV2nHyPbRzf6 AYDDxU7YfhUOreecXBetxay5wwsKiM7L2cOlDz9ZO1gSzpDTc1t582upY0a/niE= =5tgj -----END PGP SIGNATURE----- --GRPZ8SYKNexpdSJ7-- From owner-freebsd-doc@FreeBSD.ORG Wed Jun 20 08:04:04 2012 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2978A106564A; Wed, 20 Jun 2012 08:04:04 +0000 (UTC) (envelope-from varuna@eudaemonicsystems.net) Received: from lnx6.securehostdns.com (174.36.194.176-static.reverse.softlayer.com [174.36.194.176]) by mx1.freebsd.org (Postfix) with ESMTP id D33B28FC12; Wed, 20 Jun 2012 08:04:03 +0000 (UTC) Received: from [117.216.172.94] (port=49538 helo=shastry.eudaemonicsystems.net) by lnx6.securehostdns.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.77) (envelope-from ) id 1ShFtM-0002TG-UV; Wed, 20 Jun 2012 13:33:57 +0530 Message-ID: <4FE1841E.2070901@eudaemonicsystems.net> Date: Wed, 20 Jun 2012 13:34:46 +0530 From: Varuna Organization: Eudaemonic Systems User-Agent: Thunderbird 2.0.0.23 (X11/20100716) MIME-Version: 1.0 To: bjk@freebsd.org, gjb@FreeBSD.org References: <20120609120028.B03851065678@hub.freebsd.org> <4FDB7404.1070703@eudaemonicsystems.net> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - lnx6.securehostdns.com X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - eudaemonicsystems.net X-Source: X-Source-Args: X-Source-Dir: Cc: freebsd-doc@freebsd.org Subject: Re: man page for dhclient.conf(5) error in script location X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Jun 2012 08:04:04 -0000 Benjamin Kaduk wrote: > > I do not believe this is an error. > Per dhclient.conf.5, the script directive specifies a DHCP client > configuration script, and in the example given in the EXAMPLES section, > it is entirely reasonable to have a custom configuration script for that > interface. In that case, the default /sbin/dhclient-script would not be > appropriate, and a custom version of it needed. Putting such a custom > configuration script in /etc is in keeping with the traditional location > for system configuration files. > > -Ben Kaduk > Correct me if I am wrong, I have been under the impression that the examples indicated in the man pages will always be for default values. The /sbin/dhclient binary refers to /etc/dhclient.conf which in turn gives the location of the script dhclient-script. The location of the script dhclient-script as seen in the source code tree has been /usr/src/sbin/dhclient/dhclient-script. The dhclient-script is not a configuration file for /sbin/dhclient and is a system related script. Indeed I do agree that nothing stops the user from placing the custom script anywhere in the system with appropriate absolute path in the configuration file. At the same time, I do not see any reason as to why /sbin/dhclient-script would necessitate a change by the user as there are no configuration setting in /sbin/dhclient-script that can be made by the user. Glen Barber wrote: > > I personally feel it should be made more clear in the dhclient.conf(5) > manual, maybe by a comment in the sample configuration? > I definitely agree with this suggestion that the dhclient.conf(5) needs a modification. With regards, Varuna Eudaemonic Systems Simple, Specific & Insightful IT Consultants, Continued Education & Systems Distribution +91-88-92-47-62-63 http://www.eudaemonicsystems.net http://enquiry.eudaemonicsystems.net ------------------------------------------------------------------ This email is confidential, and may be legally privileged. If you are not the intended recipient, you must not use or disseminate this information in any format. If you have received this email in error, please do delete it along with copies of it existing in any other format, and notify the sender immediately. The sender of this email believes it is virus free, and does not accept any liability for any errors or omissions arising thereof. From owner-freebsd-doc@FreeBSD.ORG Wed Jun 20 09:00:33 2012 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 645A5106564A for ; Wed, 20 Jun 2012 09:00:33 +0000 (UTC) (envelope-from varuna@eudaemonicsystems.net) Received: from lnx6.securehostdns.com (174.36.194.176-static.reverse.softlayer.com [174.36.194.176]) by mx1.freebsd.org (Postfix) with ESMTP id 351D48FC16 for ; Wed, 20 Jun 2012 09:00:33 +0000 (UTC) Received: from [117.216.172.94] (port=20195 helo=shastry.eudaemonicsystems.net) by lnx6.securehostdns.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.77) (envelope-from ) id 1ShGm8-0006AB-Ec for freebsd-doc@freebsd.org; Wed, 20 Jun 2012 14:30:32 +0530 Message-ID: <4FE19162.5070907@eudaemonicsystems.net> Date: Wed, 20 Jun 2012 14:31:22 +0530 From: Varuna Organization: Eudaemonic Systems User-Agent: Thunderbird 2.0.0.23 (X11/20100716) MIME-Version: 1.0 To: freebsd-doc@freebsd.org Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - lnx6.securehostdns.com X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - eudaemonicsystems.net X-Source: X-Source-Args: X-Source-Dir: Subject: resolv.conf(5) requires info on what can cause the changes to its contents X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Jun 2012 09:00:33 -0000 Hello Folks, It would help if the man page resolver(5) or resolv.conf(5) contains information about how to ensure the contents of /etc/resolv.conf gets either updated or not modified when dhcp is used. This request stems from the function add_new_resolv_conf() in the script /sbin/dhclient-script that handles the either the update or modification of /etc/resolv.conf. It will be helpful to indicate that the contents of /etc/resolv.conf is also influenced by the keywords in /etc/dhclient.conf, a good reference is the example indicated in dhclient.conf(5). With regards, Varuna Eudaemonic Systems Simple, Specific & Insightful IT Consultants, Continued Education & Systems Distribution +91-88-92-47-62-63 http://www.eudaemonicsystems.net http://enquiry.eudaemonicsystems.net ------------------------------------------------------------------ This email is confidential, and may be legally privileged. If you are not the intended recipient, you must not use or disseminate this information in any format. If you have received this email in error, please do delete it along with copies of it existing in any other format, and notify the sender immediately. The sender of this email believes it is virus free, and does not accept any liability for any errors or omissions arising thereof. From owner-freebsd-doc@FreeBSD.ORG Wed Jun 20 19:59:55 2012 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A32AE106564A for ; Wed, 20 Jun 2012 19:59:55 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) by mx1.freebsd.org (Postfix) with ESMTP id 4606C8FC08 for ; Wed, 20 Jun 2012 19:59:55 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.5/8.14.5) with ESMTP id q5KJxsop064886 for ; Wed, 20 Jun 2012 13:59:54 -0600 (MDT) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.5/8.14.5/Submit) with ESMTP id q5KJxsXG064883 for ; Wed, 20 Jun 2012 13:59:54 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Wed, 20 Jun 2012 13:59:54 -0600 (MDT) From: Warren Block To: freebsd-doc@freebsd.org Message-ID: User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (wonkity.com [127.0.0.1]); Wed, 20 Jun 2012 13:59:54 -0600 (MDT) Subject: gptboot and zfsboot X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Jun 2012 19:59:55 -0000 We have no man pages for gptboot or zfsboot. Are the details of how they work covered anywhere other than the source? There's a need for these. http://forums.freebsd.org/showthread.php?t=32807 http://forums.freebsd.org/showthread.php?t=32886 From owner-freebsd-doc@FreeBSD.ORG Wed Jun 20 20:57:59 2012 Return-Path: Delivered-To: freebsd-doc@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 982A6106564A for ; Wed, 20 Jun 2012 20:57:59 +0000 (UTC) (envelope-from bcr@FreeBSD.org) Received: from mxout1.bln1.prohost.de (mxout3.bln1.prohost.de [213.160.84.49]) by mx1.freebsd.org (Postfix) with ESMTP id 0F41B8FC15 for ; Wed, 20 Jun 2012 20:57:58 +0000 (UTC) Received: from Benedicts-Macbook-Pro.local (p4FC73D79.dip.t-dialin.net [79.199.61.121]) (authenticated bits=0) by mx1.bln1.prohost.de (8.14.1/8.14.1) with ESMTP id q5KKvi5m003116 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 20 Jun 2012 22:57:45 +0200 Message-ID: <4FE2394F.30508@FreeBSD.org> Date: Wed, 20 Jun 2012 22:57:51 +0200 From: Benedict Reuschling Organization: The FreeBSD Project User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:13.0) Gecko/20120614 Thunderbird/13.0.1 MIME-Version: 1.0 To: freebsd-doc@FreeBSD.org References: In-Reply-To: X-Enigmail-Version: 1.4.2 OpenPGP: id=4A819348 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Null-Tag: 696febe8c4ebddf617e2b5ea8db9e6a7 Cc: Subject: Re: gptboot and zfsboot X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: bcr@FreeBSD.org List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Jun 2012 20:57:59 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Am 20.06.12 21:59, schrieb Warren Block: > We have no man pages for gptboot or zfsboot. Are the details of how > they work covered anywhere other than the source? There's a need for > these. > > http://forums.freebsd.org/showthread.php?t=32807 > http://forums.freebsd.org/showthread.php?t=32886 Make sure to add it to the wiki, there is a lot of other man pages that need writing. You might want to ask the people who wrote it (or made recent changes to them). Regards Benedict -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk/iOU8ACgkQTSZQLkqBk0j/BgCgrZDPa+z92e5tw5NyRB54O4f3 TPEAn2aAhD8PZ1L8kYkHNa4mSzJArYay =8IiI -----END PGP SIGNATURE----- From owner-freebsd-doc@FreeBSD.ORG Thu Jun 21 00:28:21 2012 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id A6FEB1065670; Thu, 21 Jun 2012 00:28:21 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) by mx1.freebsd.org (Postfix) with ESMTP id 647118FC08; Thu, 21 Jun 2012 00:28:21 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.5/8.14.5) with ESMTP id q5L0SKfP066515; Wed, 20 Jun 2012 18:28:20 -0600 (MDT) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.5/8.14.5/Submit) with ESMTP id q5L0SKVQ066512; Wed, 20 Jun 2012 18:28:20 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Wed, 20 Jun 2012 18:28:20 -0600 (MDT) From: Warren Block To: Benedict Reuschling In-Reply-To: <4FE2394F.30508@FreeBSD.org> Message-ID: References: <4FE2394F.30508@FreeBSD.org> 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.2.7 (wonkity.com [127.0.0.1]); Wed, 20 Jun 2012 18:28:20 -0600 (MDT) Cc: freebsd-doc@freebsd.org Subject: Re: gptboot and zfsboot X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Jun 2012 00:28:21 -0000 On Wed, 20 Jun 2012, Benedict Reuschling wrote: > Am 20.06.12 21:59, schrieb Warren Block: >> We have no man pages for gptboot or zfsboot. Are the details of how >> they work covered anywhere other than the source? There's a need for >> these. >> >> http://forums.freebsd.org/showthread.php?t=32807 >> http://forums.freebsd.org/showthread.php?t=32886 > > Make sure to add it to the wiki, there is a lot of other man pages that > need writing. Which wiki page? From owner-freebsd-doc@FreeBSD.ORG Thu Jun 21 00:57:40 2012 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 829121065674; Thu, 21 Jun 2012 00:57:40 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) by mx1.freebsd.org (Postfix) with ESMTP id 3D3128FC12; Thu, 21 Jun 2012 00:57:40 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.5/8.14.5) with ESMTP id q5L0vdeo066666; Wed, 20 Jun 2012 18:57:39 -0600 (MDT) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.5/8.14.5/Submit) with ESMTP id q5L0vdXu066663; Wed, 20 Jun 2012 18:57:39 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Wed, 20 Jun 2012 18:57:39 -0600 (MDT) From: Warren Block To: Benedict Reuschling In-Reply-To: Message-ID: References: <4FE2394F.30508@FreeBSD.org> 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.2.7 (wonkity.com [127.0.0.1]); Wed, 20 Jun 2012 18:57:39 -0600 (MDT) Cc: freebsd-doc@freebsd.org Subject: Re: gptboot and zfsboot X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Jun 2012 00:57:40 -0000 On Wed, 20 Jun 2012, Warren Block wrote: > On Wed, 20 Jun 2012, Benedict Reuschling wrote: > >> Am 20.06.12 21:59, schrieb Warren Block: >>> We have no man pages for gptboot or zfsboot. Are the details of how >>> they work covered anywhere other than the source? There's a need for >>> these. >>> >>> http://forums.freebsd.org/showthread.php?t=32807 >>> http://forums.freebsd.org/showthread.php?t=32886 >> >> Make sure to add it to the wiki, there is a lot of other man pages that >> need writing. > > Which wiki page? Found it: MissingManPages From owner-freebsd-doc@FreeBSD.ORG Thu Jun 21 05:12:37 2012 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EF119106564A for ; Thu, 21 Jun 2012 05:12:37 +0000 (UTC) (envelope-from ae@FreeBSD.org) Received: from mail.kirov.so-ups.ru (ns.kirov.so-ups.ru [178.74.170.1]) by mx1.freebsd.org (Postfix) with ESMTP id 992048FC15 for ; Thu, 21 Jun 2012 05:12:37 +0000 (UTC) Received: from kas30pipe.localhost (localhost.kirov.so-ups.ru [127.0.0.1]) by mail.kirov.so-ups.ru (Postfix) with SMTP id 0F855B805E; Thu, 21 Jun 2012 09:12:32 +0400 (MSK) Received: from kirov.so-ups.ru (unknown [172.21.81.1]) by mail.kirov.so-ups.ru (Postfix) with ESMTP id 07866B8027; Thu, 21 Jun 2012 09:12:32 +0400 (MSK) Received: by ns.kirov.so-ups.ru (Postfix, from userid 1010) id 03300BA046; Thu, 21 Jun 2012 09:12:32 +0400 (MSK) Received: from [127.0.0.1] (unknown [10.118.3.52]) by ns.kirov.so-ups.ru (Postfix) with ESMTP id C1070BA051; Thu, 21 Jun 2012 09:12:31 +0400 (MSK) Message-ID: <4FE2AD3F.5030304@FreeBSD.org> Date: Thu, 21 Jun 2012 09:12:31 +0400 From: "Andrey V. Elsukov" User-Agent: Mozilla Thunderbird 1.5 (FreeBSD/20051231) MIME-Version: 1.0 To: Warren Block References: In-Reply-To: X-Enigmail-Version: 1.4.1 Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: 7bit X-SpamTest-Version: SMTP-Filter Version 3.0.0 [0284], KAS30/Release X-SpamTest-Info: Not protected Cc: freebsd-doc@freebsd.org Subject: Re: gptboot and zfsboot X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Jun 2012 05:12:38 -0000 On 20.06.2012 23:59, Warren Block wrote: > We have no man pages for gptboot or zfsboot. Are the details of how they work covered anywhere > other than the source? There's a need for these. Hi, There is "BOOTSTRAPPING" section in the gpart(8). But zfsboot isn't related to any partition tables, so i did not added a note about it. -- WBR, Andrey V. Elsukov From owner-freebsd-doc@FreeBSD.ORG Thu Jun 21 09:02:32 2012 Return-Path: Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1FCD2106564A; Thu, 21 Jun 2012 09:02:32 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id E74908FC0A; Thu, 21 Jun 2012 09:02:31 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q5L92V8r003641; Thu, 21 Jun 2012 09:02:31 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q5L92Vud003633; Thu, 21 Jun 2012 09:02:31 GMT (envelope-from linimon) Date: Thu, 21 Jun 2012 09:02:31 GMT Message-Id: <201206210902.q5L92Vud003633@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-doc@FreeBSD.org From: linimon@FreeBSD.org Cc: Subject: Re: docs/169285: [handbook] Handbook some troubles X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Jun 2012 09:02:32 -0000 Old Synopsis: Handbook some troubles New Synopsis: [handbook] Handbook some troubles Responsible-Changed-From-To: freebsd-bugs->freebsd-doc Responsible-Changed-By: linimon Responsible-Changed-When: Thu Jun 21 09:02:17 UTC 2012 Responsible-Changed-Why: reclassify. http://www.freebsd.org/cgi/query-pr.cgi?pr=169285 From owner-freebsd-doc@FreeBSD.ORG Thu Jun 21 11:30:15 2012 Return-Path: Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A15E31065670 for ; Thu, 21 Jun 2012 11:30:15 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 729148FC0C for ; Thu, 21 Jun 2012 11:30:15 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q5LBUFOp038709 for ; Thu, 21 Jun 2012 11:30:15 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q5LBUFrm038706; Thu, 21 Jun 2012 11:30:15 GMT (envelope-from gnats) Date: Thu, 21 Jun 2012 11:30:15 GMT Message-Id: <201206211130.q5LBUFrm038706@freefall.freebsd.org> To: freebsd-doc@FreeBSD.org From: Niclas Zeising Cc: Subject: Re: docs/169285: [handbook] Handbook some troubles X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Niclas Zeising List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Jun 2012 11:30:15 -0000 The following reply was made to PR docs/169285; it has been noted by GNATS. From: Niclas Zeising To: bug-followup@FreeBSD.org, ExDss@yandex.by Cc: Subject: Re: docs/169285: [handbook] Handbook some troubles Date: Thu, 21 Jun 2012 13:22:59 +0200 Can you please explain in further detail what the issue is exactly? Regards! -- Niclas Zeising From owner-freebsd-doc@FreeBSD.ORG Thu Jun 21 12:22:05 2012 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 112761065670 for ; Thu, 21 Jun 2012 12:22:05 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from bigwig.baldwin.cx (bigknife-pt.tunnel.tserv9.chi1.ipv6.he.net [IPv6:2001:470:1f10:75::2]) by mx1.freebsd.org (Postfix) with ESMTP id D7EDB8FC1B for ; Thu, 21 Jun 2012 12:22:04 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 4A6BDB96B; Thu, 21 Jun 2012 08:22:04 -0400 (EDT) From: John Baldwin To: freebsd-doc@freebsd.org Date: Thu, 21 Jun 2012 07:55:21 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110714-p13; KDE/4.5.5; amd64; ; ) References: In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201206210755.21402.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Thu, 21 Jun 2012 08:22:04 -0400 (EDT) Cc: Subject: Re: gptboot and zfsboot X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Jun 2012 12:22:05 -0000 On Wednesday, June 20, 2012 3:59:54 pm Warren Block wrote: > We have no man pages for gptboot or zfsboot. Are the details of how > they work covered anywhere other than the source? There's a need for > these. > > http://forums.freebsd.org/showthread.php?t=32807 > http://forums.freebsd.org/showthread.php?t=32886 Note that there is no boot2(8) manpage either. Instead there is a boot(8) manpage. I do think boot(8) does not currently handle gptboot and zfsboot (it should be fairly easy to update it for gptboot), but that is the right place to document these I believe. -- John Baldwin From owner-freebsd-doc@FreeBSD.ORG Thu Jun 21 13:16:11 2012 Return-Path: Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E1425106566C; Thu, 21 Jun 2012 13:16:11 +0000 (UTC) (envelope-from issyl0@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id B58578FC0A; Thu, 21 Jun 2012 13:16:11 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q5LDGBsF047557; Thu, 21 Jun 2012 13:16:11 GMT (envelope-from issyl0@freefall.freebsd.org) Received: (from issyl0@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q5LDGBIX047552; Thu, 21 Jun 2012 13:16:11 GMT (envelope-from issyl0) Date: Thu, 21 Jun 2012 13:16:11 GMT Message-Id: <201206211316.q5LDGBIX047552@freefall.freebsd.org> To: ExDss@yandex.by, issyl0@FreeBSD.org, freebsd-doc@FreeBSD.org From: issyl0@FreeBSD.org Cc: Subject: Re: docs/169285: [handbook] Handbook some troubles X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Jun 2012 13:16:12 -0000 Synopsis: [handbook] Handbook some troubles State-Changed-From-To: open->feedback State-Changed-By: issyl0 State-Changed-When: Thu Jun 21 13:15:45 UTC 2012 State-Changed-Why: Awaiting feedback from submitter. http://www.freebsd.org/cgi/query-pr.cgi?pr=169285 From owner-freebsd-doc@FreeBSD.ORG Thu Jun 21 14:38:15 2012 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 94499106566B; Thu, 21 Jun 2012 14:38:15 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) by mx1.freebsd.org (Postfix) with ESMTP id 5026A8FC0C; Thu, 21 Jun 2012 14:38:15 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.5/8.14.5) with ESMTP id q5LEc9ov071283; Thu, 21 Jun 2012 08:38:09 -0600 (MDT) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.5/8.14.5/Submit) with ESMTP id q5LEc9Jp071280; Thu, 21 Jun 2012 08:38:09 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Thu, 21 Jun 2012 08:38:09 -0600 (MDT) From: Warren Block To: John Baldwin In-Reply-To: <201206210755.21402.jhb@freebsd.org> Message-ID: References: <201206210755.21402.jhb@freebsd.org> 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.2.7 (wonkity.com [127.0.0.1]); Thu, 21 Jun 2012 08:38:09 -0600 (MDT) Cc: freebsd-doc@freebsd.org Subject: Re: gptboot and zfsboot X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Jun 2012 14:38:15 -0000 On Thu, 21 Jun 2012, John Baldwin wrote: > On Wednesday, June 20, 2012 3:59:54 pm Warren Block wrote: >> We have no man pages for gptboot or zfsboot. Are the details of how >> they work covered anywhere other than the source? There's a need for >> these. >> >> http://forums.freebsd.org/showthread.php?t=32807 >> http://forums.freebsd.org/showthread.php?t=32886 > > Note that there is no boot2(8) manpage either. Instead there is a boot(8) > manpage. I do think boot(8) does not currently handle gptboot and zfsboot (it > should be fairly easy to update it for gptboot), but that is the right place > to document these I believe. boot(8) is kind of written around the standad boot1/boot2. It will need a rewrite to handle the others. See the Files and Diagnostics sections for what I mean; those are going to be different for each of the different types. There ought to be boot2.8, gptboot.8, and zfsboot.8 links to that page, too. That's all doable, but it seems like a fair amount of work to combine disparate things that would be better separately. So maybe we should split the boot2 information out into boot2(8), create a relatively-trivial gptboot(8) and a possibly-not-so-trivial zfsboot(8). From owner-freebsd-doc@FreeBSD.ORG Thu Jun 21 18:33:28 2012 Return-Path: Delivered-To: doc@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E7A6D1065674 for ; Thu, 21 Jun 2012 18:33:28 +0000 (UTC) (envelope-from gabor@FreeBSD.org) Received: from server.mypc.hu (server.mypc.hu [87.229.73.95]) by mx1.freebsd.org (Postfix) with ESMTP id 99AEC8FC1D for ; Thu, 21 Jun 2012 18:33:28 +0000 (UTC) Received: from server.mypc.hu (localhost [127.0.0.1]) by server.mypc.hu (Postfix) with ESMTP id D6B5614E7A4F for ; Thu, 21 Jun 2012 20:33:27 +0200 (CEST) X-Virus-Scanned: amavisd-new at server.mypc.hu 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 kE4x4yjv21XP for ; Thu, 21 Jun 2012 20:33:23 +0200 (CEST) Received: from [84.225.86.97] (netacc-gpn-5-86-97.pool.telenor.hu [84.225.86.97]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by server.mypc.hu (Postfix) with ESMTPSA id 707C214E7A47 for ; Thu, 21 Jun 2012 20:33:23 +0200 (CEST) Message-ID: <4FE368F6.4030805@FreeBSD.org> Date: Thu, 21 Jun 2012 20:33:26 +0200 From: Gabor Kovesdan User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20120614 Thunderbird/13.0.1 MIME-Version: 1.0 To: doc@FreeBSD.org X-Enigmail-Version: 1.4.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Subject: [HEADS UP] XML migration and opening of projects/ X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Jun 2012 18:33:29 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 - -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Dear Doc Developers, the migration to SVN and the related reorganization seem to have gone seamlessly. However, the planned doc infrastructure improvements are not finished yet. The next item on our TODO list is the long overdue XML migration. Now we have a proper VCS system that supports renames and moves in the tree so we can follow up with bigger reorganizations. (Side note: do not be afraid of the changes, authoring will not be more complicated at all.) This XML migration is quite a complex reorganization and as such, it cannot be done on the mainline of doc development so we decided to do it in a separate branch. Also, this project will be the first experiment on branching and merging back changes to head. To open projects/ for the public we have to carefully evaluate the potential scenarios of merging and choose that one that best suites our development model. We at doceng will work out a draft about using projects/ and merging changes back to head. We will post this to doc@ and once the policies and best practices are established, finally projects/ will be open for the big public. You can expect to see our draft policies in 2-3 weeks, so projects/ may be open around mid-July. Gabor - -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk/i8hUACgkQkC3QTyNzprEZcACfcsln3a86tnlRw1AaUFcz1Tjo Y8cAoIf6kKCT0+lGVxppg9+xjmwpEnxB =1jHv - -----END PGP SIGNATURE----- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk/jaPYACgkQkC3QTyNzprFrfwCePStPmddgd9akqX8yk+FnttzC /HgAnRgC+xVRjXw5A2rhHxDJ5JhsaBfY =S/aW -----END PGP SIGNATURE----- From owner-freebsd-doc@FreeBSD.ORG Thu Jun 21 20:42:04 2012 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E284F1065672 for ; Thu, 21 Jun 2012 20:42:04 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from bigwig.baldwin.cx (bigknife-pt.tunnel.tserv9.chi1.ipv6.he.net [IPv6:2001:470:1f10:75::2]) by mx1.freebsd.org (Postfix) with ESMTP id B79978FC14 for ; Thu, 21 Jun 2012 20:42:04 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 279C6B922; Thu, 21 Jun 2012 16:42:04 -0400 (EDT) From: John Baldwin To: Warren Block Date: Thu, 21 Jun 2012 14:33:56 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110714-p13; KDE/4.5.5; amd64; ; ) References: <201206210755.21402.jhb@freebsd.org> In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201206211433.56632.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Thu, 21 Jun 2012 16:42:04 -0400 (EDT) Cc: freebsd-doc@freebsd.org Subject: Re: gptboot and zfsboot X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Jun 2012 20:42:05 -0000 On Thursday, June 21, 2012 10:38:09 am Warren Block wrote: > On Thu, 21 Jun 2012, John Baldwin wrote: > > > On Wednesday, June 20, 2012 3:59:54 pm Warren Block wrote: > >> We have no man pages for gptboot or zfsboot. Are the details of how > >> they work covered anywhere other than the source? There's a need for > >> these. > >> > >> http://forums.freebsd.org/showthread.php?t=32807 > >> http://forums.freebsd.org/showthread.php?t=32886 > > > > Note that there is no boot2(8) manpage either. Instead there is a boot(8) > > manpage. I do think boot(8) does not currently handle gptboot and zfsboot (it > > should be fairly easy to update it for gptboot), but that is the right place > > to document these I believe. > > boot(8) is kind of written around the standad boot1/boot2. It will need > a rewrite to handle the others. See the Files and Diagnostics sections > for what I mean; those are going to be different for each of the > different types. There ought to be boot2.8, gptboot.8, and zfsboot.8 > links to that page, too. > > That's all doable, but it seems like a fair amount of work to combine > disparate things that would be better separately. > > So maybe we should split the boot2 information out into boot2(8), create > a relatively-trivial gptboot(8) and a possibly-not-so-trivial > zfsboot(8). gptboot is very similar to boot2 (both use /boot.config for example with mostly similar syntax (gptboot uses ad0pX vs ad0sXa in boot2). zfsboot is quite different and probably warrants a separate page. -- John Baldwin From owner-freebsd-doc@FreeBSD.ORG Thu Jun 21 21:00:29 2012 Return-Path: Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id EE67710656B6 for ; Thu, 21 Jun 2012 21:00:28 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id DA3E48FC1C for ; Thu, 21 Jun 2012 21:00:28 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q5LL0SBu093148 for ; Thu, 21 Jun 2012 21:00:28 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q5LL0SM6093147; Thu, 21 Jun 2012 21:00:28 GMT (envelope-from gnats) Date: Thu, 21 Jun 2012 21:00:28 GMT Message-Id: <201206212100.q5LL0SM6093147@freefall.freebsd.org> To: freebsd-doc@FreeBSD.org From: Niclas Zeising Cc: Subject: Re: docs/169285: [handbook] Handbook some troubles X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Niclas Zeising List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Jun 2012 21:00:29 -0000 The following reply was made to PR docs/169285; it has been noted by GNATS. From: Niclas Zeising To: =?UTF-8?B?0KHQtdGA0LPQtdC5INCU0LXQtNGO0LvRjw==?= , bug-followup@FreeBSD.org Cc: Subject: Re: docs/169285: [handbook] Handbook some troubles Date: Thu, 21 Jun 2012 22:53:43 +0200 On 06/21/12 15:34, Сергей Дедюля wrote: > Commiting instead ommiting unused kernel code - syntax error I am still unsure of what the issue you are trying to point out is. As far as I can tell, the sentence "A custom kernel often uses less memory than the GENERIC kernel by omitting unused features and device drivers." is perfectly valid English and it explains that a kernel without unneeded drivers uses less memory. Omitted, or omitting, means to not include. Can you please try to explain in greater detail what the issue is? Regards! -- Niclas Zeising From owner-freebsd-doc@FreeBSD.ORG Thu Jun 21 21:27:19 2012 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 786B7106564A for ; Thu, 21 Jun 2012 21:27:19 +0000 (UTC) (envelope-from tanika752@gmail.com) Received: from sam.nabble.com (sam.nabble.com [216.139.236.26]) by mx1.freebsd.org (Postfix) with ESMTP id 53BEF8FC12 for ; Thu, 21 Jun 2012 21:27:19 +0000 (UTC) Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1ShouH-0003SD-L4 for freebsd-doc@freebsd.org; Thu, 21 Jun 2012 14:27:13 -0700 Date: Thu, 21 Jun 2012 14:27:13 -0700 (PDT) From: tanika To: freebsd-doc@freebsd.org Message-ID: <1340314033645-5720629.post@n5.nabble.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Introduction X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Jun 2012 21:27:19 -0000 Hello everybody , I`m new here I've just joined because i saw that this forum is useful and i hope it will help me to improve my English language ----- Addicting Games -- View this message in context: http://freebsd.1045724.n5.nabble.com/Introduction-tp5720629.html Sent from the freebsd-doc mailing list archive at Nabble.com. From owner-freebsd-doc@FreeBSD.ORG Fri Jun 22 15:38:52 2012 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6960A1065675 for ; Fri, 22 Jun 2012 15:38:52 +0000 (UTC) (envelope-from silent24_2007@yahoo.com) Received: from nm2-vm6.bullet.mail.sg3.yahoo.com (nm2-vm6.bullet.mail.sg3.yahoo.com [106.10.148.109]) by mx1.freebsd.org (Postfix) with SMTP id 9F94A8FC1C for ; Fri, 22 Jun 2012 15:38:51 +0000 (UTC) Received: from [106.10.166.120] by nm2.bullet.mail.sg3.yahoo.com with NNFMP; 22 Jun 2012 15:38:50 -0000 Received: from [106.10.151.251] by tm9.bullet.mail.sg3.yahoo.com with NNFMP; 22 Jun 2012 15:38:50 -0000 Received: from [127.0.0.1] by omp1022.mail.sg3.yahoo.com with NNFMP; 22 Jun 2012 15:38:50 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 456289.57040.bm@omp1022.mail.sg3.yahoo.com Received: (qmail 51925 invoked by uid 60001); 22 Jun 2012 15:38:50 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1340379530; bh=1wOgPwIozwiJNl76tGGeGbkSmMsD3jUZ3W5HdYYoLSY=; h=X-YMail-OSG:Received:X-Mailer:Message-ID:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type; b=V4/7SQMjPBW5uzqZzhi4KYMEdj/22fbzWfs24bVKkfbIUs2w8l6Q+Kq+jdOWm4rJr4bqHTcClwet9jJpATLIMfcCbUTzloLI4Kz0KknFvPn9C5X+J6gALOOtQM39YO0GSqX6SyeE+E8pY8FykiJ3MfcbhGlKAMOROUzVsJj4Hm8= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:Message-ID:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type; b=AA0DmtKLk9AmblrWtNaYmDWGR9DyrOgfXfoTC53II9Zfd9k6x+dDqWTz6HMP/wBTwSqKGbDqNSz/cbk2s8+lP1hupOdJtLg6pMcjtTx2EggwIEqgWLJ+oPPmc1EGKO2T8EDaUJ7SOBkNXbsJpn72AOp7iai5HxwVPxCqouhxlQ4=; X-YMail-OSG: gMKAb1IVM1nFUHgjLQSfGfAVKaTPKTojOX61QP6J7bqUK.K pgByAQh9sEDPd1oo8jG7Yf4N3VcrDQ76JT9jfjphmv31dHld9Ro5TXeIDHCh uFG4EdrUsk2SOcV8UrNZ3OmTsABPUOfzAxcNcP9ATY_MFt5GitYmqIffJ9jg LGz6xUMT2eqCrKsFlkdA3.IPsSa6PKOsCW4DY0lbUOUuOqRGgJ_FDh_X5.YH etAXm8rMYYgY8CEPFjGLCC36A1GbI7ONtNwwuw6amsjxF020yLQGMbNYX749 a1tI0g4rrgcUSeNYOEm8dg9X3RQtM0DOsttZQkGVMIb2Qdtm_APSbF2b9Sh. Y1HANrgNLGiOdb8LY8BhtIgwH_eSK2KiIzs9VfBcedcRtervRpayqHhTPwO9 uRbwXFi8DKEYrS8wSXDlXQAmLpJk3Tu81CBHQ0LMg.9lwElTy.xwF4wmUCke 3EiqVq25Gn_pPbDDB0pANvWZcBLOe4lfQWvUJc4SHreN.kv3o4bnUFRSk_p6 GDild3tQGr7rciMzM37_0G_9yj5IapiyM5vq6c2Ti58he Received: from [121.54.50.52] by web190402.mail.sg3.yahoo.com via HTTP; Fri, 22 Jun 2012 23:38:50 SGT X-Mailer: YahooMailWebService/0.8.118.349524 Message-ID: <1340379530.49640.YahooMailNeo@web190402.mail.sg3.yahoo.com> Date: Fri, 22 Jun 2012 23:38:50 +0800 (SGT) From: RetspaN Code To: "FreeBSD-doc@FreeBSD.org" MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: I have a problem to my server running under FreeBSD 8.1 p-1 release X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: RetspaN Code List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Jun 2012 15:38:52 -0000 Hello FreeBSD,=0A=0AI have a problem to my server.=0A=0AI'm running FreeBSD= 8.1 p-1 release=0A=0AWhen freebsd got a vulnerable called=A0OpenSSL multip= le vulnerabilities i get my server reboot and shutdown many times. when i c= heck the log on wtmp i found user and use root login thru terminal, it look= s like this:=0A~^@^@^@^@^@^@^@reboot^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^= @^@^@^@^@^@^@=D0=ED=C9Lttyv0^@^@^@root^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^= @^@^@^@^@^@^@^@^@^@=0A=0Aand intruder load their exploit due to my server v= ulnerable of openssl but i did patch it but already late coz the intruder a= lready load their exploit. and users start to reboot and shutdown my server= everytime i up. then user also delete my /home/files.=0Aand now i get this= last problem. specially when running application psybnc it auto crash and = auto kill the process.=0A=0A[root@CyberTech /usr/src]# fetch http://securit= y.FreeBSD.org/patches/SA-12:04/sysret-81.patch=0Afetch: http://security.Fre= eBSD.org/patches/SA-12:04/sysret-81.patch: Permission denied=0A[root@CyberT= ech /usr/src]#=0A=0AI got this error.=0A=0AHeres my current process:=0A=0A[= root@CyberTech /usr/src]# ps x=0A=A0 PID =A0TT =A0STAT =A0 =A0 =A0TIME COMM= AND=0A=A0 =A0 0 =A0?? =A0DLs =A0143:51.96 [kernel]=0A=A0 =A0 1 =A0?? =A0SLs= =A0 =A00:28.75 /sbin/init --=0A=A0 =A0 2 =A0?? =A0DL =A0 =A0 2:49.23 [g_ev= ent]=0A=A0 =A0 3 =A0?? =A0DL =A0 =A032:31.52 [g_up]=0A=A0 =A0 4 =A0?? =A0DL= =A0 =A027:26.45 [g_down]=0A=A0 =A0 5 =A0?? =A0DL =A0 =A0 0:00.01 [sctp_ite= rator]=0A=A0 =A0 6 =A0?? =A0DL =A0 =A0 0:00.00 [xpt_thrd]=0A=A0 =A0 7 =A0??= =A0DL =A0 =A016:27.57 [pagedaemon]=0A=A0 =A0 8 =A0?? =A0DL =A0 =A0 0:00.00= [vmdaemon]=0A=A0 =A0 9 =A0?? =A0DL =A0 =A0 0:00.04 [pagezero]=0A=A0 =A010 = =A0?? =A0DL =A0 =A0 0:00.00 [audit]=0A=A0 =A011 =A0?? =A0RL =A0 91515:47.03= [idle]=0A=A0 =A012 =A0?? =A0WL =A0 918:54.59 [intr]=0A=A0 =A013 =A0?? =A0D= L =A0 =A011:18.45 [yarrow]=0A=A0 =A014 =A0?? =A0DL =A0 =A0 0:49.58 [usb]=0A= =A0 =A015 =A0?? =A0DL =A0 =A0 0:45.70 [acpi_thermal]=0A=A0 =A016 =A0?? =A0D= L =A0 =A0 0:13.93 [bufdaemon]=0A=A0 =A017 =A0?? =A0DL =A0 =A041:59.16 [sync= er]=0A=A0 =A018 =A0?? =A0DL =A0 =A0 0:25.69 [vnlru]=0A=A0 =A019 =A0?? =A0DL= =A0 =A0 0:15.91 [softdepflush]=0A=A0 =A020 =A0?? =A0DL =A0 =A0 1:50.31 [fl= owcleaner]=0A=A0 112 =A0?? =A0Is =A0 =A0 0:00.00 adjkerntz -i=0A=A02046 =A0= ?? =A0Is =A0 =A0 0:00.04 /sbin/devd=0A=A02233 =A0?? =A0DL =A0 =A0 0:01.48 [= accounting]=0A=A02256 =A0?? =A0Ss =A0 =A013:51.56 /usr/local/sbin/syslog-ng= -p /var/run/syslog.pid=0A=A02608 =A0?? =A0Ss =A0 =A0 2:54.56 /usr/bin/perl= /usr/local/lib/webmin-1.580/miniserv.pl /usr/local/etc/webmin/miniserv.con= f (perl5.10.1)=0A=A02707 =A0?? =A0Ss =A0 =A0 0:08.02 /usr/sbin/cron -s=0A= =A02718 =A0?? =A0Is =A0 =A0 0:00.27 /usr/local/bin/portsentry -tcp=0A=A0272= 0 =A0?? =A0Is =A0 =A0 0:00.00 /usr/local/bin/portsentry -udp=0A44606 =A0?? = =A0Is =A0 =A0 0:04.40 /usr/local/sbin/oidentd -C /usr/local/etc/oidentd.con= f=0A79728 =A0?? =A0Is =A0 =A0 0:00.01 /usr/sbin/sshd -u0=0A85824 =A0?? =A0S= s =A0 =A0 0:00.70 sshd: root@pts/13 (sshd)=0A=A04756 =A0v0 =A0Is+ =A0 =A00:= 00.01 /usr/libexec/getty Pc ttyv0=0A=A04757 =A0v1 =A0Is+ =A0 =A00:00.01 /us= r/libexec/getty Pc ttyv1=0A=A04758 =A0v2 =A0Is+ =A0 =A00:00.01 /usr/libexec= /getty Pc ttyv2=0A=A04759 =A0v3 =A0Is+ =A0 =A00:00.01 /usr/libexec/getty Pc= ttyv3=0A=A04760 =A0v4 =A0Is+ =A0 =A00:00.01 /usr/libexec/getty Pc ttyv4=0A= =A04761 =A0v5 =A0Is+ =A0 =A00:00.01 /usr/libexec/getty Pc ttyv5=0A=A04762 = =A0v6 =A0Is+ =A0 =A00:00.01 /usr/libexec/getty Pc ttyv6=0A=A04763 =A0v7 =A0= Is+ =A0 =A00:00.01 /usr/libexec/getty Pc ttyv7=0A85841 =A013 =A0Is =A0 =A0 = 0:00.05 -csh (csh)=0A87998 =A013 =A0S =A0 =A0 =A00:00.04 bash=0A88267 =A013= =A0R+ =A0 =A0 0:00.00 ps x=0A[root@CyberTech /usr/src]#=0A=0ACan you help = me to fix and how to repair my server to avoid crash and getting an error "= Error Creating Socket"=0A=0APlease help me Sir, Thanks!=0A=0A=0ARegards,=0A= =0AFredFoxs From owner-freebsd-doc@FreeBSD.ORG Fri Jun 22 16:00:23 2012 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 841C61065696 for ; Fri, 22 Jun 2012 16:00:23 +0000 (UTC) (envelope-from erich@alogreentechnologies.com) Received: from alogreentechnologies.com (alogreentechnologies.com [67.212.224.110]) by mx1.freebsd.org (Postfix) with ESMTP id 740218FC0A for ; Fri, 22 Jun 2012 16:00:18 +0000 (UTC) Received: from x220.ovitrap.com ([122.129.201.75]) (authenticated bits=0) by alogreentechnologies.com (8.13.1/8.13.1) with ESMTP id q5MFxZeO000633; Fri, 22 Jun 2012 09:59:47 -0600 From: Erich Dollansky Organization: ALO Green Technologies To: freebsd-doc@freebsd.org, RetspaN Code Date: Fri, 22 Jun 2012 22:59:33 +0700 User-Agent: KMail/1.13.7 (FreeBSD/10.0-CURRENT; KDE/4.8.3; amd64; ; ) References: <1340379530.49640.YahooMailNeo@web190402.mail.sg3.yahoo.com> In-Reply-To: <1340379530.49640.YahooMailNeo@web190402.mail.sg3.yahoo.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Message-Id: <201206222259.34058.erich@alogreentechnologies.com> Cc: Subject: Re: I have a problem to my server running under FreeBSD 8.1 p-1 release X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Jun 2012 16:00:23 -0000 Hi, I think that the best advice is that you take a fresh install media and mak= e a=20 fresh install as you are not in control of the machine anymore. Erich On Friday 22 June 2012 22:38:50 RetspaN Code wrote: > Hello FreeBSD, >=20 > I have a problem to my server. >=20 > I'm running FreeBSD 8.1 p-1 release >=20 > When freebsd got a vulnerable called OpenSSL multiple vulnerabilities i g= et > my server reboot and shutdown many times. when i check the log on wtmp i > found user and use root login thru terminal, it looks like this: >=20 ~^@^@^@^@^@^@^@reboot^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@=D0 >=20 =ED=C9Lttyv0^@^@^@root^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^= @^@ >=20 > and intruder load their exploit due to my server vulnerable of openssl but > i did patch it but already late coz the intruder already load their > exploit. and users start to reboot and shutdown my server everytime i up. > then user also delete my /home/files. and now i get this last problem. > specially when running application psybnc it auto crash and auto kill the > process. >=20 > [root@CyberTech /usr/src]# fetch > http://security.FreeBSD.org/patches/SA-12:04/sysret-81.patch fetch: > http://security.FreeBSD.org/patches/SA-12:04/sysret-81.patch: Permission > denied [root@CyberTech /usr/src]# >=20 > I got this error. >=20 > Heres my current process: >=20 > [root@CyberTech /usr/src]# ps x > PID TT STAT TIME COMMAND > 0 ?? DLs 143:51.96 [kernel] > 1 ?? SLs 0:28.75 /sbin/init -- > 2 ?? DL 2:49.23 [g_event] > 3 ?? DL 32:31.52 [g_up] > 4 ?? DL 27:26.45 [g_down] > 5 ?? DL 0:00.01 [sctp_iterator] > 6 ?? DL 0:00.00 [xpt_thrd] > 7 ?? DL 16:27.57 [pagedaemon] > 8 ?? DL 0:00.00 [vmdaemon] > 9 ?? DL 0:00.04 [pagezero] > 10 ?? DL 0:00.00 [audit] > 11 ?? RL 91515:47.03 [idle] > 12 ?? WL 918:54.59 [intr] > 13 ?? DL 11:18.45 [yarrow] > 14 ?? DL 0:49.58 [usb] > 15 ?? DL 0:45.70 [acpi_thermal] > 16 ?? DL 0:13.93 [bufdaemon] > 17 ?? DL 41:59.16 [syncer] > 18 ?? DL 0:25.69 [vnlru] > 19 ?? DL 0:15.91 [softdepflush] > 20 ?? DL 1:50.31 [flowcleaner] > 112 ?? Is 0:00.00 adjkerntz -i > 2046 ?? Is 0:00.04 /sbin/devd > 2233 ?? DL 0:01.48 [accounting] > 2256 ?? Ss 13:51.56 /usr/local/sbin/syslog-ng -p /var/run/syslog.pid > 2608 ?? Ss 2:54.56 /usr/bin/perl > /usr/local/lib/webmin-1.580/miniserv.pl > /usr/local/etc/webmin/miniserv.conf (perl5.10.1) 2707 ?? Ss 0:08.02 > /usr/sbin/cron -s > 2718 ?? Is 0:00.27 /usr/local/bin/portsentry -tcp > 2720 ?? Is 0:00.00 /usr/local/bin/portsentry -udp > 44606 ?? Is 0:04.40 /usr/local/sbin/oidentd -C > /usr/local/etc/oidentd.conf 79728 ?? Is 0:00.01 /usr/sbin/sshd -u0 > 85824 ?? Ss 0:00.70 sshd: root@pts/13 (sshd) > 4756 v0 Is+ 0:00.01 /usr/libexec/getty Pc ttyv0 > 4757 v1 Is+ 0:00.01 /usr/libexec/getty Pc ttyv1 > 4758 v2 Is+ 0:00.01 /usr/libexec/getty Pc ttyv2 > 4759 v3 Is+ 0:00.01 /usr/libexec/getty Pc ttyv3 > 4760 v4 Is+ 0:00.01 /usr/libexec/getty Pc ttyv4 > 4761 v5 Is+ 0:00.01 /usr/libexec/getty Pc ttyv5 > 4762 v6 Is+ 0:00.01 /usr/libexec/getty Pc ttyv6 > 4763 v7 Is+ 0:00.01 /usr/libexec/getty Pc ttyv7 > 85841 13 Is 0:00.05 -csh (csh) > 87998 13 S 0:00.04 bash > 88267 13 R+ 0:00.00 ps x > [root@CyberTech /usr/src]# >=20 > Can you help me to fix and how to repair my server to avoid crash and > getting an error "Error Creating Socket" >=20 > Please help me Sir, Thanks! >=20 >=20 > Regards, >=20 > FredFoxs > _______________________________________________ > freebsd-doc@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-doc > To unsubscribe, send any mail to "freebsd-doc-unsubscribe@freebsd.org" From owner-freebsd-doc@FreeBSD.ORG Fri Jun 22 18:28:06 2012 Return-Path: Delivered-To: docs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 737BA1065674 for ; Fri, 22 Jun 2012 18:28:06 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: from mail-ob0-f182.google.com (mail-ob0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id 2DA288FC15 for ; Fri, 22 Jun 2012 18:28:06 +0000 (UTC) Received: by obbun3 with SMTP id un3so2957532obb.13 for ; Fri, 22 Jun 2012 11:28:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eitanadler.com; s=0xdeadbeef; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; bh=wqtfhhIhcZ21Kozf+6hJz1LMfQsuLsLFvgZJCFgl1wc=; b=tU9Wfp8VJYAaPRVhO3Mr9k4BmyxatlMiNnqTDXzSAjUXCBIyTwrAaybxAuy/uLnK3h +xRZsZapHMb/nGa4Je/sjLCoJt2XrDtTPThp2PPolwM6t47LByb05wH8JV0XeLHc7uku SgfZFqqabNYTP7Hp0BaXeDeiyYTI5XApVlp5I= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding:x-gm-message-state; bh=wqtfhhIhcZ21Kozf+6hJz1LMfQsuLsLFvgZJCFgl1wc=; b=L1vHD0es2QEJTVMmSewNTaP6OBY9uHDfrPI/Zw29nT2+1yOXckQBvILYAtlm/1BqFz YqaawFFr+8RndU3WUx09axlNd+mwcb46IK99y/ZiAQxkC/IAiWNYHj7eBCJGFVq5Tyj+ Q4fV42gdjltEwKbYg0xduXM3nrHdhj2POf8bkVErD8ze7Qmqc40meUc0TJmazNrSf8u8 EO9I9dCePnOhQx0xHQP3gTdlfO+K5xeD/k8ogO2N75YZf2b54oLmP405brzeYZuwfCfq wg3CIvrStasZ8QesF/De8ZRLou+87xQ3lvWUKobghnXCzp1PjfRrroVnJTBsotT8R1+i 4ZAQ== Received: by 10.182.187.42 with SMTP id fp10mr2989929obc.30.1340389685628; Fri, 22 Jun 2012 11:28:05 -0700 (PDT) MIME-Version: 1.0 Received: by 10.182.125.70 with HTTP; Fri, 22 Jun 2012 11:27:35 -0700 (PDT) In-Reply-To: References: <20120608083519.GA8252@lonesome.com> <20120608113104.GA1720@night.db.net> <20120612221505.GA77335@night.db.net> <4FD7C615.2020209@FreeBSD.org> From: Eitan Adler Date: Fri, 22 Jun 2012 11:27:35 -0700 Message-ID: To: Gabor Kovesdan Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Gm-Message-State: ALoCoQmfhM6fYLLTAqIWjdtz2VdVM/s7X88L3CHQRF2iM8ZeP993g/mCD/zqTGeCJw9Cp2F2mXFB Cc: Mark Linimon , docs@freebsd.org Subject: Re: Time for a fresh start, it's time folks X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Jun 2012 18:28:06 -0000 On 12 June 2012 15:53, Eitan Adler wrote: > On 12 June 2012 15:43, Gabor Kovesdan wrote: >> On 2012.06.13. 0:15, Diane Bruce wrote: >>> >>> So while we are at it, why not ask for volunteers to redesign our >>> website? There have been a few volunteers in the past. Perhaps we >>> could hold a contest and put it up for a vote? Or we could just sole >>> source from iX systems, it does not matter! =C2=A0It's time. So, is this happening? Can we send iX systems an email on behalf of the project? --=20 Eitan Adler From owner-freebsd-doc@FreeBSD.ORG Fri Jun 22 19:04:11 2012 Return-Path: Delivered-To: freebsd-doc@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D9CED1065670 for ; Fri, 22 Jun 2012 19:04:11 +0000 (UTC) (envelope-from bcr@FreeBSD.org) Received: from mxout1.bln1.prohost.de (mxout1.bln1.prohost.de [213.160.84.47]) by mx1.freebsd.org (Postfix) with ESMTP id 6A04A8FC08 for ; Fri, 22 Jun 2012 19:04:11 +0000 (UTC) Received: from Benedicts-Macbook-Pro.local (p4FC71A92.dip.t-dialin.net [79.199.26.146]) (authenticated bits=0) by mx1.bln1.prohost.de (8.14.1/8.14.1) with ESMTP id q5MIgn4V018071 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 22 Jun 2012 20:42:50 +0200 Message-ID: <4FE4BCAE.3020405@FreeBSD.org> Date: Fri, 22 Jun 2012 20:42:54 +0200 From: Benedict Reuschling Organization: The FreeBSD Project User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:13.0) Gecko/20120614 Thunderbird/13.0.1 MIME-Version: 1.0 To: freebsd-doc@FreeBSD.org References: <20120608083519.GA8252@lonesome.com> <20120608113104.GA1720@night.db.net> <20120612221505.GA77335@night.db.net> <4FD7C615.2020209@FreeBSD.org> In-Reply-To: X-Enigmail-Version: 1.4.2 OpenPGP: id=4A819348 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Null-Tag: d90e00ffb402672094c908903f4a7571 Cc: Subject: Re: Time for a fresh start, it's time folks X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: bcr@FreeBSD.org List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Jun 2012 19:04:12 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Am 22.06.12 20:27, schrieb Eitan Adler: > On 12 June 2012 15:53, Eitan Adler wrote: >> On 12 June 2012 15:43, Gabor Kovesdan wrote: >>> On 2012.06.13. 0:15, Diane Bruce wrote: >>>> >>>> So while we are at it, why not ask for volunteers to redesign our >>>> website? There have been a few volunteers in the past. Perhaps we >>>> could hold a contest and put it up for a vote? Or we could just sole >>>> source from iX systems, it does not matter! It's time. > > So, is this happening? Can we send iX systems an email on behalf of > the project? > I agree with Gabor's statement that we should wait until we are in XML world. Otherwise, we would probably need to throw away anything that gets developed in the meantime or at least require much effort to integrate it into our (then XML-based) build infrastructure. I'm very happy that we finally managed the doc SVN migration. Now that Gabor is also working on XML in a separate branch, I think we are making excellent progress towards a more modern doc infrastructure. Once the foundation is solid enough, I guess there will be plenty of people who are be willing to work together on a new FreeBSD.org webpage. These things take time, but the webpages are not broken at the moment, just outdated. Hence a replacement should not be our top priority (at least, it's not mine). However, I would be interested to see some design studies if someone is interested in doing them to see what can be done. Cheers Benedict -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk/kvK4ACgkQTSZQLkqBk0jiKACfWVi2zimRbtVaLxHjX6Tf6G6W v5UAnR/QPwp3e7ynaEkqR1tu4//dVMFw =iEp/ -----END PGP SIGNATURE----- From owner-freebsd-doc@FreeBSD.ORG Fri Jun 22 20:15:32 2012 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C985A1065674 for ; Fri, 22 Jun 2012 20:15:32 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: from mail-ob0-f182.google.com (mail-ob0-f182.google.com [209.85.214.182]) by mx1.freebsd.org (Postfix) with ESMTP id 32B528FC16 for ; Fri, 22 Jun 2012 20:15:32 +0000 (UTC) Received: by obbun3 with SMTP id un3so3103176obb.13 for ; Fri, 22 Jun 2012 13:15:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eitanadler.com; s=0xdeadbeef; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=avZZl1PpOy0lUg25mH7kuqbQgpuvgxqY6f/l5ZZOGcg=; b=pjYlnwvjSdoVFutRnD6CQyNiW1kD1lHYU6U9R8ofqhMXlJorg9hAseSPwswKsGGC8e L0qid1VgkZH+UluYF7hBCEnPIuHUpnXzosnd+3NpbVMIrB/6eoXBk77jnk6q6/EBv8Vf anpxPuhuiTpcV3Bn6mu5oTWwD+S5yLpy7RjXs= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:x-gm-message-state; bh=avZZl1PpOy0lUg25mH7kuqbQgpuvgxqY6f/l5ZZOGcg=; b=NmQE2XNp7kABysnBNmNDv+yUJ/gHu8PUM4QaaEcRwU76UO51gTGulbRfN0+7bRIzRv jQrFhvBCnYepdVaNweGoVUX/J4qyn+KC2eoS526i8vUf7Q/RP2YDQB9oamMPhgUemk0O TyxkwQ6ImB8ILq2roXnZyPel+na+1sE/wWVmTxF4p8DAt3jILr6oyyhKVonIfOY6VO75 R47Bgs/Fg3dkZeKu7Y2pYXXsLKC6OeECjniYVZoaKC3rNsHPIUsEWugrbBaMi6S3RDwZ zCoOv4Mpm4Fo+9QyMti/8sL4184/1tX5GSowHOPe/vXApHE4LJ+8SQFG0W3X0V3q7vyr fTGA== Received: by 10.182.131.2 with SMTP id oi2mr3274399obb.43.1340396131081; Fri, 22 Jun 2012 13:15:31 -0700 (PDT) MIME-Version: 1.0 Received: by 10.182.125.70 with HTTP; Fri, 22 Jun 2012 13:14:59 -0700 (PDT) In-Reply-To: <4FE4BCAE.3020405@FreeBSD.org> References: <20120608083519.GA8252@lonesome.com> <20120608113104.GA1720@night.db.net> <20120612221505.GA77335@night.db.net> <4FD7C615.2020209@FreeBSD.org> <4FE4BCAE.3020405@FreeBSD.org> From: Eitan Adler Date: Fri, 22 Jun 2012 13:14:59 -0700 Message-ID: To: bcr@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Gm-Message-State: ALoCoQkAtvnGsqyRUtSXb5wiXSiU2FY9xz3fq0UBDXh2rAm9MilEhSvEcmNxduP498Kk7C0A901h Cc: freebsd-doc@freebsd.org Subject: Re: Time for a fresh start, it's time folks X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Jun 2012 20:15:32 -0000 On 22 June 2012 11:42, Benedict Reuschling wrote: > I agree with Gabor's statement that we should wait until we are in XML > world. Otherwise, we would probably need to throw away anything that > gets developed in the meantime or at least require much effort to > integrate it into our (then XML-based) build infrastructure. I'm very > happy that we finally managed the doc SVN migration. Now that Gabor is > also working on XML in a separate branch, I think we are making > excellent progress towards a more modern doc infrastructure. Once the > foundation is solid enough, I guess there will be plenty of people who > are be willing to work together on a new FreeBSD.org webpage. Not at all. Making a mockup does not touch our infrastructure at all. Gabor's work, while quite useful and appreciated, is completely unrelated. > These things take time, but the webpages are not broken at the moment, > just outdated. Hence a replacement should not be our top priority (at > least, it's not mine). However, I would be interested to see some design > studies if someone is interested in doing them to see what can be done. Agreed. It isn't urgent "unbreak it now", but if we can, we do need to update it. -- Eitan Adler From owner-freebsd-doc@FreeBSD.ORG Fri Jun 22 20:48:35 2012 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 3F5DA106564A; Fri, 22 Jun 2012 20:48:35 +0000 (UTC) (envelope-from db@db.net) Received: from diana.db.net (unknown [IPv6:2620:64:0:1:223:7dff:fea2:c8f2]) by mx1.freebsd.org (Postfix) with ESMTP id 192098FC0A; Fri, 22 Jun 2012 20:48:35 +0000 (UTC) Received: from night.db.net (localhost [127.0.0.1]) by diana.db.net (Postfix) with ESMTP id 05AA12AA499; Fri, 22 Jun 2012 14:48:34 -0600 (MDT) Received: by night.db.net (Postfix, from userid 1000) id 64D0F5C62; Fri, 22 Jun 2012 15:48:24 -0500 (EST) Date: Fri, 22 Jun 2012 15:48:24 -0500 From: Diane Bruce To: Eitan Adler Message-ID: <20120622204824.GA51799@night.db.net> References: <20120608083519.GA8252@lonesome.com> <20120608113104.GA1720@night.db.net> <20120612221505.GA77335@night.db.net> <4FD7C615.2020209@FreeBSD.org> <4FE4BCAE.3020405@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i Cc: freebsd-doc@freebsd.org Subject: Re: Time for a fresh start, it's time folks X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Jun 2012 20:48:35 -0000 On Fri, Jun 22, 2012 at 01:14:59PM -0700, Eitan Adler wrote: > On 22 June 2012 11:42, Benedict Reuschling wrote: > > > I agree with Gabor's statement that we should wait until we are in XML > > world. Otherwise, we would probably need to throw away anything that ... > > excellent progress towards a more modern doc infrastructure. Once the > > foundation is solid enough, I guess there will be plenty of people who > > are be willing to work together on a new FreeBSD.org webpage. > > Not at all. Making a mockup does not touch our infrastructure at all. > Gabor's work, while quite useful and appreciated, is completely > unrelated. I agree. It really matters little to the web design folk what form the content is in at this time. A mockup would not get in the way of anything Gabor or anyone else is doing. In fact, bits and pieces of the xml tree can mesh in nicely with the new mockup. > > > These things take time, but the webpages are not broken at the moment, > > just outdated. Hence a replacement should not be our top priority (at > > least, it's not mine). However, I would be interested to see some design > > studies if someone is interested in doing them to see what can be done. > > Agreed. It isn't urgent "unbreak it now", but if we can, we do need to > update it. A good time to do it is *during* the XML conversion, it's quite probable we could present a new face with a new docs system underneath. > > -- > Eitan Adler Diane Bruce -- - db@FreeBSD.org db@db.net http://www.db.net/~db Nowadays tar can compress using yesterdays latest technologies! From owner-freebsd-doc@FreeBSD.ORG Sat Jun 23 12:40:09 2012 Return-Path: Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6A20A1065672 for ; Sat, 23 Jun 2012 12:40:09 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 3F5DF8FC1F for ; Sat, 23 Jun 2012 12:40:09 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q5NCe9If000707 for ; Sat, 23 Jun 2012 12:40:09 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q5NCe92j000706; Sat, 23 Jun 2012 12:40:09 GMT (envelope-from gnats) Resent-Date: Sat, 23 Jun 2012 12:40:09 GMT Resent-Message-Id: <201206231240.q5NCe92j000706@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, Frederic Culot Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4FA8C106566C for ; Sat, 23 Jun 2012 12:30:41 +0000 (UTC) (envelope-from culot@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 3741E8FC0A for ; Sat, 23 Jun 2012 12:30:41 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q5NCUffR091189 for ; Sat, 23 Jun 2012 12:30:41 GMT (envelope-from culot@freefall.freebsd.org) Received: (from culot@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q5NCUfFQ091180; Sat, 23 Jun 2012 12:30:41 GMT (envelope-from culot) Message-Id: <201206231230.q5NCUfFQ091180@freefall.freebsd.org> Date: Sat, 23 Jun 2012 12:30:41 GMT From: Frederic Culot To: FreeBSD-gnats-submit@FreeBSD.org X-Send-Pr-Version: 3.113 Cc: Subject: docs/169342: fr_FR.ISO8859-1/htdocs/projects/projects.sgml: MFen to r39039 X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Frederic Culot List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 Jun 2012 12:40:09 -0000 >Number: 169342 >Category: docs >Synopsis: fr_FR.ISO8859-1/htdocs/projects/projects.sgml: MFen to r39039 >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-doc >State: open >Quarter: >Keywords: >Date-Required: >Class: update >Submitter-Id: current-users >Arrival-Date: Sat Jun 23 12:40:08 UTC 2012 >Closed-Date: >Last-Modified: >Originator: Frederic Culot >Release: FreeBSD 9.0-STABLE i386 >Organization: >Environment: System: FreeBSD freefall.freebsd.org 9.0-STABLE FreeBSD 9.0-STABLE #6 r235139: Tue May 8 21:19:03 UTC 2012 simon@freefall.freebsd.org:/usr/obj/usr/src/sys/FREEFALL i386 >Description: - MFen to r39039 Diff could also be downloaded from http://people.freebsd.org/~culot/doc/projects.sgml.diff >How-To-Repeat: >Fix: --- projects.sgml.diff begins here --- Index: projects.sgml =================================================================== --- projects.sgml (revision 39024) +++ projects.sgml (working copy) @@ -3,6 +3,7 @@ + ]> @@ -23,22 +25,23 @@ ci-dessous pour en apprendre plus sur ces projets passionnants.

Si vous remarquez qu'un projet est manquant, veuillez envoyer l'URL ainsi qu'une courte -description (3 à 10 lignes) à www@FreeBSD.ORG +description (3 à 10 lignes) à www@FreeBSD.org

De plus, certains de ces projets envoient régulièrement un compte rendu sur le statut du développement. Ils peuvent être consultés sur la page des compte-rendus.

@@ -53,21 +56,9 @@
  • Ressources FreeBSD pour les Débutants est une liste de ressources pour aider ceux qui débutent sur FreeBSD et sur UNIX en - général. Il y a également une liste de diffusion freebsd-newbies@FreeBSD.ORG.
    • + général. -
  • Magasins pour FreeBSD - est une liste internationale de revendeurs où l'on peut acheter FreeBSD.
    • - -
  • - Guide de sécurité FreeBSD - FreeBSD est un système d'exploitation très sécurisé. Comme le code source - est librement disponible, le système est constamment examiné et - vérifié. Bien que FreeBSD soit par défaut très sécurisé, il existe de - nombreux moyens pour le rendre encore plus sûr pour ceux d'entre vous - qui sont "paranoïaques". Ce guide décrit plusieurs étapes qui vous aideront - à accroitre la sécurité globale de votre machine.
    • - -
  • +
  • Moteur de recherche de RELEASE/SNAP pour les serveurs FTP. Une ressource qui permettra à quiconque de trouver un serveur FTP contenant une version ("release") ou un instantané ("snap") particulier de FreeBSD. @@ -79,145 +70,48 @@ sous Unix. Le but est de fournir une série de guides décrivant pas-à-pas l'installation et la configuration de divers ports.
    • -
  • Guide - Complet FreeBSD - une tentative de guide plus lisible - et ressemblant davantage à un livre pour expliquer le système - d'exploitation FreeBSD. A l'intention des personnes débutant à la - fois sur FreeBSD et UNIX. Actuellement en cours d'avancement.
    • +
  • +Le guide de référence du Développeur FreeBSD
    • -
  • Guide - FreeBSD pour les Paresseux et les Désespérés est une autre tentative - quelque peu plus légère de fournir un guide plus lisible sur - l'installation et la configuration de FreeBSD.
    • +
  • +Contribuer au catalogue des logiciels portés de FreeBSD
    • -
  • Le - mini-Guide Linux+FreeBSD décrit comment - utiliser Linux et FreeBSD sur un même système. Il présente FreeBSD - et discute sur la façon dont les deux systèmes peuvent coopérer, - par exemple en partageant l'espace de swap.
    • - -
  • - Découverte de l'Installation de FreeBSD 2.2.7 - C'est un guide expliquant le programme d'installation de FreeBSD - pour ceux débutant sous Unix et/ou FreeBSD.
    • - -
  • Projet - de Documentation pour les Développeurs FreeBSD
    • - -
  • - Le Livre de Recettes FreeBSD - OK, vous avez installé FreeBSD, et maintenant ? Voici quelques suggestions - de solutions aux problèmes courants que vous pouvez mettre en oeuvre avec ce - que vous connaissez déjà. Ce document est rédigé à la façon des livres de - cuisine électroniques avec quelques recettes pour les types d'installations les - plus courants. Chaque "recette" inclus des configurations matérielles minimums - recommandées, des logiciels spécifiques à utiliser et, le plus important, les - informations de configuration indispensables pour que le système fonctionne - correctement.
    • - -
  • -"The FreeBSD Corporate Networker's Guide" -Ce site web est un supplément au livre "The FreeBSD Corporate -Networker's Guide", avec comme objectif principal d'améliorer son -utilité. Alors que les livres tels que les romans de science-fiction peuvent -être lus avec plaisir plusieurs centaines d'années après leur première -parution, les manuels techniques comme le "Networker's Guide" sont rendus obsolètes -en quelques années avec les changements concernant les produits dont ils parlent. -
    • - - -

    Promouvoir FreeBSD

    -
      - -
    • - Projet pour Promouvoir FreeBSD - Ce projet est un groupe de personnes responsables de la promotion - de FreeBSD. Notre objectif principal est de développer une image - marketing compétitive pour le projet FreeBSD et d'accroître le - nombre d'utilisateurs FreeBSD. -
      • - -
    • - FreeBSD contre Linux : quelques comparaisons entre FreeBSD et - Linux, qui est un autre système d'exploitation pour PC très proche d'Unix - et qui lui aussi est gratuit et librement distribuable.
      • - -
    • Daemon News - est une publication électronique consacrée aux systèmes d'exploitations BSD en général. - Son but est d'être une ressource pour les communautés FreeBSD, OpenBSD - et NetBSD.
      • - -
    • La Page Compteur de FreeBSD - est le début d'un projet qui va essayer de déterminer le nombre d'utilisateurs - FreeBSD dans le monde entier. L'équipe de développement FreeBSD a pour - l'instant une très vague idée du nombre d'utilisateurs et cela rends - beaucoup plus difficile de persuader les fournisseurs de matériels - et de logiciels de prendre FreeBSD au sérieux.
      • - -
    • Liste des CD BSD à un prix défiant toute concurrence - Si quelqu'un a un CD à donner (le destinataire paye les frais de port) ou à - prêter localement, il peut mettre son adresse e-mail sur la liste. Du matériel - et des livres peuvent aussi être donnés. Nous encourageons tout le monde à donner - leurs CD aux bibliothèques locales et à l'indiquer également sur la liste.
      • - -
    • - Le Bazar du Logiciel Libre est un "marché" conçu pour accroître - le nombre de logiciels libres, pour soutenir les développeurs de logiciels libres - et pour mesurer plus précisément la demande en logiciels libres.
      • - -
    • Fanzine électronique FreeBSD - Le fanzine FreeBSD est un recueil mensuel d'articles faciles à lire (nous l'espérons) - écrits par des utilisateurs et des administrateurs FreeBSD tout comme vous.
      • - -
    • - Le Projet d'Annuaire Public a pour but de créer l'annuaire le plus complet - du web en comptant sur une vaste armée de rédacteurs bénévoles.
      • - -
    • - FreeBSD contre Linux contre Windows NT - Un comparatif entre ces trois systèmes d'exploitations qui comprend - la fiabilité, les performances, les problèmes liés à l'an 2000, le support, - les coûts d'exploitation et plus encore.
      • - -
    • Le - Compteur des Systèmes d'Exploitations sur Internet est une étude concernant - l'utilisation des systèmes d'exploitation sur Internet. Des adresses de machines - sont collectées et "interrogées" par le programme queso pour connaître leurs - systèmes d'exploitation.
      • - -
    • Le téléphone - portable BSD. Housse pour téléphone portable décorée avec le démon FreeBSD. -
      • - -
    • BSDCon 2002, la -3ème exposition et conférence BSD. -
      • -
    -

    Applications

    • Java sur FreeBSD - Contient des informations pour obtenir le dernier JDK pour + Contient des informations pour obtenir le dernier &jdk; pour FreeBSD, savoir comment l'installer et le faire fonctionner ainsi qu'une liste de - logiciels java qui pourrait vous intéresser. Veuillez noter que le JDK n'est pas supporté - pour les versions de FreeBSD antérieures à 2.2.
      • + logiciels &java; qui pourrait vous intéresser. -
    • Groupe Mozilla FreeBSD - cherche à centraliser le travail sur le projet Mozilla de Netscape pour - le monde FreeBSD en fournissant des ressources centralisées comme un serveur - CVS, une liste de diffusion électronique et d'autres outils de développement.
      • +
    • GNOME sur FreeBSD + Contient des informations sur comment obtenir la dernière version de GNOME + pour FreeBSD, comment l'installer et la faire fonctionner, + les dernières informations concernant le projet et ses + mises à jour, la Foire Aux Questions couvrant les problématiques + spécifiques à GNOME sur FreeBSD, les recommandations + pour porter des applications, et bien plus encore.
      • -
    • Multimédia - Un ensemble de liens sur des informations et des logiciels concernant le monde du - multimédia sous Unix.
      • +
    • KDE sur FreeBSD + Contient des liens vers les dernière versions de KDE disponibles + sur FreeBSD, ainsi que de la documentation et des guides relatifs + à l'installation et à l'utilisation de KDE sur FreeBSD. + Les actualités concernant le projet ainsi qu'une Foire Aux + Questions spécifique à FreeBSD sont également + disponibles.
      • +
    • + Mono sur FreeBSD + Contient des informations décrivant la situation de Mono et de C# + sur FreeBSD.
      • + +
    • + OpenOffice.org sur FreeBSD + Contient des informations relatives aux différents portages + d'OpenOffice.org.
      • +
    • Collection de Ports FreeBSD La Collection de Ports FreeBSD fournit un moyen simple de compiler et d'installer un large choix d'applications avec un minimum d'effort. @@ -228,66 +122,63 @@ est une liste qui vérifie la collection de ports pour les fichiers de distributions introuvables et fournit un résumé pour chaque port.
      • -
    • FreshPorts fournit la liste la plus à jour des -ports et des changements sur les ports. Ajouter vos ports favoris à votre liste personnelle et recevez -un courrier électronique si un changement survient.
      • +
    • FreshPorts fournit la liste la plus + récente possible des ports ainsi que l'historique des modifications + qui leurs ont été appliquées. + Ajoutez vos ports favoris à votre liste personnelle et recevez + un courrier électronique vous prévenant dès qu'un + changement survient sur ceux-ci.
      • + +
    • Pointyhat + est un serveur qui vérifie l'état de la Collection des Ports + et conserve les historiques de construction des paquets ainsi que + les rapports d'erreurs pour chacun des ports.

    Réseaux

      -
    • ALTQ : gestion de bande passante pour les applications
      • +
    • Netperf, + une optimisation de la pile réseau pour les noyaux de FreeBSD 5.x et 6.x, + dans la continuité du travail effectué sur le vérouillage + SMPng de la pile réseau pour FreeBSD 5.3. Ce projet explore et + implémente des stratégies d'optimisation pour une pile + réseau multi-threadée.
    • Projet KAME, une pile IPv6/IPsec pour BSD disponible librement.
      • -
    • Protocole Point à Point (PPP)
      • -
    • IP Mobile Sécurisé via IP
      • +
    • SYSLOG-SECURE : + En Août 2001, un standard pour syslog a été établi sous la + dénomination RFC3164. Ce document RFC décrit certaines extensions pour + améliorer la sécurité de syslog. Le projet a débuté + en 2002 pour adapter le RFC3164 à la version FreeBSD de syslog, et pour lui ajouter + des extensions de sécurité (au minimum syslog-sign). La libc et syslogd + seront tous les deux modifiés, et d'autres outils utilisés pour vérifier + ou administrer la sécurité seront potentiellement développés. + Toute aide est la bienvenue. Vous pouvez envoyer un message à albert@ons-huis.net + pour obtenir plus d'informations.
    - -

    Systèmes de Fichiers

    -
      -
    • Arla + +

      Stockage

      +
        +
      • Arla est une implémentation libre d'un client AFS. L'objectif principal est de faire un client pleinement fonctionnel avec toutes les capacités de l'AFS. Les autres choses prévues et implémentées sont tous les outils de gestion usuels et un serveur.
        • +
      • Big Disk + dont le but est de permettre à FreeBSD de supporter les disques, volumes + et systèmes de fichiers de plusieurs teraoctets de capacité.
        • +
      • Coda est un système de fichiers distribués. Au nombre de ses caractéristiques : opérations en mode déconnecté, bon modèle de sécurité, réplications entre serveurs et cache persistant côté client.
        • -
      • -Le Système de Fichier Virtuel crossFS -est basé sur le système de fichier virtuel FreeBSD et fournit un -canevas pour porter les systèmes de fichiers Unix sur les systèmes Windows NT. -
        • - -
      • cryptfs crypte les noms de fichiers et les pages de données en utilisant Blowfish.
        • - -
      • Elephant : Le système de fichier qui n'oublie jamais -
      • Journalisation contre Soft Updates : Protection asynchrone des méta-données dans les systèmes de fichiers
        • -
      • Mode de vérouillage ("Mode locking")
        • -
      • Rendre l'interface namei réflexive
        • -
      • Vérouillage NFS (client et serveur)
        • - -
      • Conception et Implémentation d'un gestionnaire de périphérique DCD pour Unix
        • - -
      • Pilote NTFS pour FreeBSD - Ce pilote permet de monter des partitions Windows NTFS sous FreeBSD. - Actuellement, les partitions NTFS sont uniquement accessibles en lecture seule mais - l'accès en lecture-écriture est prévu.
        • - -
      • Rio (Entrées/Sorties - en RAM) : Le projet Rio cherche comment implémenter et utiliser - une mémoire "fiable". La mémoire "fiable" permets une forte amélioration - de la fiabilité et des performances.
        • - -
      • Soft Updates : Une solution au problème de mise à jour des méta-données dans les systèmes de fichiers.
        • - -
      • TCFS +
      • TCFS est un Système de Fichier Chiffré Transparent ce qui est une solution adaptée au problème des regards indiscrets dans le cas d'un système de fichier distribué. En intégrant totalement le service de cryptage et le système de fichier, il @@ -321,37 +212,18 @@ pour réaliser la conversion entre noms de chemins absolus et noms de chemins relatifs. Il est utile principalement pour les utilisateurs de NFS et de WWW.
        • -
      • - V9FS: système de fichier en mémoire pour FreeBSD Cela deviendra (nous l'espérons) - dans le futur la base des espaces de nommage privés pour FreeBSD. - Il fournit un système de fichier qui utilise uniquement la mémoire vive - pour les répertoires, les i-nodes et les données. Ce n'est pas du tout comme mfs, - car mfs utilise la mémoire pour les "bloques disques" et agit essentiellement - comme un périphérique pour UFS. V9FS est au contraire un "citoyen de premier ordre" - et peut être monté comme un système de fichier. Pas encore de code - pour l'instant.
        • - -
      • -WAFS est un système de fichier simple conçu pour être un service -de logs pour les sous-systèmes du noyau. Les lectures et écritures sont indexées -avec des numéros de séquence de log (LSN). Toutes les écritures sur WAFS sont -séquentielles. Les sous-systèmes du noyau peuvent utiliser ce service LSN pour -forcer une écriture des logs et garantir l'intégrité. -
        • -

      Noyau et sécurité

        -
      • Drawbridge - est un firewall complet qui fut développé à l'Université A&M du Texas et - qui fut conçu en gardant à l'esprit un large environnement de type universitaire. Sa plus - grande force est sa capacité à exécuter le filtrage de paquet très rapidement pour - un grand nombre de machines à l'intérieur d'un intranet.
        • +
      • Entités d'Ordonnancement Noyau +est un projet visant à améliorer le support des processus légers sur FreeBSD +en utilisant un système à l'architecture similaire à celui proposé par +"Scheduler Activations".
      • +href="http://www.cs.cmu.edu/~dpetrou/research.html"> Ordonnancement du noyau par loterie : Ce projet est basé sur l'algorithme d'ordonnancement par loterie de Waldspurger, qui implémente un partage proportionnel des ressources. Les avantages principaux @@ -359,49 +231,58 @@ d'exécution de leurs processus et que les utilisateurs sont isolés les uns des autres ce qui empêche un utilisateur de monopoliser le CPU.
        • -
      • Metacomputing
        • -
      • Configuration DHCP - Comment mettre en oeuvre DHCP sur les systèmes FreeBSD pour une utilisation avec les modems cables, etc...
        • +
      • OpenBSM: +est une implémentation open source de l'API d'Audit du Module de Sécurité Fondamentale +de Sun ("BSM - Basic Security Module") ainsi que de son format de fichier. OpenBSM fournit +les librairies accessibles depuis l'espace utilisateur, les outils, ainsi que la documentation +pour l'implémentation de l'audit de TrustedBSD qui sera intégré à +FreeBSD.
        • -
      • LDAP pour FreeBSD
        • - -
      • Support Multi-Processeurs Symétrique +
      • Support Multi-Processeurs Symétrique Documentations et autres informations pour tirer avantage des systèmes multi-processeurs sous FreeBSD.
        • -
      • Un système de validation pour tester les allocations/désallocations mémoire du noyau.
        • - -
      • SPY -vous permet de surveiller et/ou bloquer certains appels systèmes sur votre -poste. Il peut être utilisé pour une surveillance des périphériques, forcer -une politique de sécurité ou comme outil de debugage.
        • -
      • TrustedBSD fournit un ensemble d'extensions éprouvées au système d'exploitation FreeBSD. Cela inclu notamment des fonctions comme les privilèges que l'on peut définir très précisément ("capabilities"), les listes de contrôles d'accès (ACL) et les -contrôles d'accès obligatoires (MAC).
        • +contrôles d'accès obligatoires (MAC). Ces fonctionnalités sont +réintégrées au système FreeBSD de base, et sont +également portées sur d'autres systèmes dérivés de FreeBSD. -
      +
    • Suite de Tests de Charge du Noyau : +l'objectif de ces tests de charge est de provoquer une défaillance du système. +Le test de charge est composé de petits programmes et scripts de test. Chacun de +ces tests s'attaque à une partie spécifique du noyau. Le concept clé +de cette suite de tests est de provoquer le chaos. Chaque test est mis en veille pendant +un nombre aléatoire de secondes avant de se mettre en action en étant +invoqué un nombre aléatoire de fois.
      • +
    +

    Pilotes de périphériques

      -
    • Base de données des gestionnaires de périphériques BSD -Ce n'est pas parce que vous n'avez pas le temps d'écrire un gestionnaire de périphériques -vous-même que vous ne pouvez pas apporter votre aide. L'idée derrière -la base de données des gestionnaires de périphériques BSD est d'aider les personnes -qui possèdent le matériel à être en contact avec les développeurs de gestionnaire -de périphériques qui ont les connaissances nécessaires pour écrire le code. -Il s'agit d'une liste de gestionnaire de périphériques actuellement en cours de -développement qui pourraient tirer profit du temps ou des ressources que -vous pourriez apporter.
      • +
    • busdma + et conversion de pilote SMPng : + busdma fournit une abstraction portable aux primitives matérielles de la + mémoire à accès direct (DMA) utilisées par + beaucoup de pilotes de périphériques à haute + performance. En utilisant cette abstraction, les auteurs de pilotes + de périphériques n'ont pas à rajouter de code + pour gérer les spécificités de la DMA liées + à la plate-forme considérée, améliorant + par la même la portabilité des pilotes sur des architectures + matérielles hétérogènes. Cette page recense + également les progrès effectués dans le but d'être + compatible avec les systèmes multiprocesseurs ("SMPng-safe").
    • Une Nouvelle Structure pour les Périphériques sous FreeBSD
      • -
    • ATM BSD : une implémentation de ATM sous 4.4BSD : +
    • ATM BSD : une implémentation de ATM sous 4.4BSD : Les nouvelles applications informatique dans les domaines tel que le multimédia, le traitement d'image et le calcul distribué nécessitent de hauts niveaux de performance de la part du réseau. Les solutions de réseaux basées sur l'ATM fournissent une alternative @@ -414,66 +295,27 @@ ATM BSD peut être utilisé à la fois sur du réseau IP et sur de l'ATM "natif".
      • -
    • -Initiative pour un gestionnaire de périphérique NVIDIA sur -FreeBSD - Une initiative dont le but est d'obtenir des gestionnaires de périphériques 3D -pour FreeBSD supportés par NVIDIA. Cela doit être accompli avec l'aide de la communauté -des développeurs FreeBSD et celle de NVIDIA. Veuillez visiter la page web pour des nouvelles -régulièrement mises à jour et pour savoir comment vous pouvez participer.
      • - -
    • Horloge de Haute-précision avec FreeBSD - Comment créer un serveur NTP de niveau 1 avec des performances optimales.
      • -
    • Domotique avec FreeBSD comme par exemple des contrôleurs d'appareils électriques, des contrôleurs infra-rouge, des systèmes téléphoniques automatisés et plus encore.
      • -
    • i4b : ISDN pour FreeBSD - ISDN4BSD (ou i4b pour faire court) est un ensemble de logiciels pour connecter - un ordinateur fonctionnant sous FreeBSD, NetBSD, OpenBSD, ou BSD/OS à ISDN. Le seul protocole - ISDN supporté pour l'instant est le protocole BRI. ISDN4BSD vous permet de réaliser des - connexions réseaux IP en utilisant soit des paquets IP envoyés dans des trames - HDLC "brutes" sur le canal B soit en utilisant PPP en mode synchrone. Pour la - téléphonie, ISDN4BSD peut répondre aux appels entrants tout comme un répondeur - automatique.
      • - -
    • CAM : une nouvelle couche SCSI pour FreeBSD - Détails sur ce qu'est la nouvelle couche SCSI CAM et comment elle fonctionne.
      • - -
    • Le Projet Token-Ring FreeBSD +
    • Le Projet Token-Ring FreeBSD Informations, fichiers, patches et documentations pour ajouter le support Token Ring sous FreeBSD.
      • -
    • Développement de pilotes USB pour FreeBSD - La pile USB pour NetBSD a été portée sur FreeBSD. En collaboration avec NetBSD, nous - avons commencé le développement de pilotes pour les nombreux périphériques utilisant le bus USB. - Jetez un oeil sur la page web si vous voulez vous joindre à nous ou si vous voulez connaître - les périphériques supportés.
      • - -
    • Configuration d'une Soundblaster Awe64 sous - FreeBSD 3.1
      • -
    • Une liste de diffusion existe pour le développement futur du pilote ethernet pour Xircom CEM de Scott Mitchell. Envoyez subscribe freebsd-xircom à majordomo@lovett.com pour vous abonner.
      • -
    • Liste de Mike Smith des cartes -RAID supportées et informations sur ces cartes.
      • -

    Architectures

      -
    • Portage de FreeBSD sur les systèmes Alpha - Contient des informations sur le portage de FreeBSD sur Alpha comme l'état d'avancement, - les informations sur la liste de diffusion électronique, le matériel utilisé et d'autres - projets sur Alpha.
      • -
    • +
    • Portage de FreeBSD sur les systèmes IA-64 Ce projet est responsable du portage de FreeBSD sur l'architecture IA-64. Envoyez toutes les questions spécifiques à ce projet sur @@ -509,72 +351,81 @@ ystème d'exploitation tel que les chargeurs de boot ("boot loaders") ou les serveurs au niveau du système d'exploitation se situant au dessus d'un micro-noyau.
      • -
    • FreeBSD léger et embarqué (PicoBSD) - PicoBSD est une version de FreeBSD tenant sur une seule disquette qui, dans ses différentes - variantes, vous permet d'avoir un accès dial-up sécurisé, un petit routeur sans disque dur - ou même un serveur dial-in. Tout cela sur seulement une disquette standard - de 1.44 Mo. Il a besoin au minimum d'un processeur 386SX avec 8 Mo de mémoire vive - et aucun disque dur n'est nécessaire !
      • - -
    • - BUDS : Unix BSD Distribué "Simplement" - - Fournit un système de clusters à vocation généraliste pour de futurs - développements dans le domaine des multi-processeurs parallèles. Ce système - est destiné à être générique par nature mais puissant. Il n'est pas destiné - aux applications nécessitant des calculs intensifs ni aux applications - interdépendantes extrêmement complexes.
      • - -
    • The Système d'Exploitation Eclipse -est un banc d'essai pour la Qualité de Service (QoS) qui est actuellement -développé au Centre de Recherche des Sciences de l'Information de Bell-Labs, -Lucent Technologies. - -Eclipse fournit un support QoS flexible et hautement configurable pour les -applications. Sa conception permet aux applications spécifiques ou non -de fournir un support QoS sans modification ni recompilation. Une -API simple est fournie pour les (nouvelles) applications qui veulent tirer avantage -du support QoS hautement configurable. - -Actuellement, le projet Eclipse cible le support QoS pour les applications -serveurs, en particulier, pour différencier les performances de -différents sites web hébergés sur une même plate-forme (voir les exemples -avec Apache).
      • -

    Divers

      -
    • GLOBAL +
    • FreeSBIE + est un live CD basé sur le système d'exploitation FreeBSD. + Il inclut un large choix d'applications utiles et peut tourner soit uniquement + à partir du CD, soit servir d'installeur pour installer FreeBSD + sur votre disque dur.
      • + +
    • NanoBSD + est un outil conçu pour créer une image système + de FreeBSD, réduite ou non, qui peut résider sur une + carte Compact Flash (ou autres système de stockage de masse) + de telle sorte qu'il convient à l'utilisation dans le cadre d'un + serveur applicatif ("appliance"). La documentation FreeBSD contient un + article d'introduction à NanoBSD, + qui inclut des indications utiles sur la manière dont on peut mettre + en place, lancer et utiliser NanoBSD.
      • + +
    • GLOBAL est un système de "marquage" ("tag system") de code source commun qui fonctionne de la même manière sous des environnements divers. Actuellement, il supporte l'interpréteur de ligne de commande, l'éditeur nvi, les browser web, l'éditeur emacs et l'éditeur elvis. Les langages supportés sont le C, Yacc, et Java.
      • -
    • PAO : la page de l'Informatique Mobile, les ordinateurs portables fonctionnant sous FreeBSD - PAO permets à FreeBSD d'utiliser de nombreuses cartes PCMCIA (PC-card) et vous permet - aussi d'avoir des PC-card pouvant être connectés "à chaud" sur votre portable fonctionnant - sous FreeBSD. Il contient aussi certaines améliorations et corrections de bugs pour le - pilote APM BIOS.
      • +
    • Enteruser : Un remplacement à Adduser
      • -
    • Réferences croisées FreeBSD. - Une présentation hypertexte avec des références croisées du code source du noyau - FreeBSD. La version indexée est celle de développement (version "-CURRENT") et elle est mise à jour - chaque nuit.
      • +
    • ACPI sur FreeBSD + est un projet visant à obtenir un fonctionnement stable + de l'ACPI sur FreeBSD.
      • -
    • Enteruser : Un remplacement à Adduser
      • -
    • libh. - Libh est un "wrapper" qui permet aux scripts tcl de - tourner dans une sorte de "boîte noire" et de s'interfacer avec d'autres librairies. - Parmi les librairies fournies avec libh qui peuvent être utilisées - depuis des scripts Tcl il existe une librairie générique pour les interfaces utilisateurs, - qui utilise Turbo Vision pour le mode console et Qt pour le mode X11. - Libh inclu également un nouveau système de package qui utilise des archives - Zip et divers scripts par package parmi d'autres choses. Inclu également - le début d'un nouveau sysinstall.
      • +
    • Mise à jour binaire : + FreeBSD Update est un système permettant, et ce de manière + automatique, de construire, distribuer, récupérer et appliquer + des mises à jour de sécurité au format binaire sous FreeBSD. + Cela rend possible de suivre facilement les branches sécurité + de FreeBSD sans avoir besoin de récupérer l'arbre des sources + et recompiler (à l'exception de la machine qui construit les mises + à jour, bien évidemment). Les mises à jour ont une + signature cryptographique et sont distribuées sous forme de + deltas binaires, ce qui réduit drastiquement la bande passante + utilisée.
      • +
    • Le projet FreeBSD de + mise en conformité à C99 & &posix; + est un projet qui vise à implémenter toutes les spécifications + des standards ISO 9899:1999 (C99) et IEEE 1003.1-2001 (POSIX).
      • + +
    • CVSweb + est une interface web pour les dépôts CVS avec laquelle vous + pouvez parcourir une hiérarchie de fichiers en utilisant votre navigateur + et visualiser l'historique des modifications appliquées à un fichier + de manière très pratique.
      • + +
    • La Liste de Compatibilité + des Ordinateurs Portables avec FreeBSD + est une base de données listant les modèles d'ordinateurs + portables et de cartes PCMCIA fonctionnant sous FreeBSD. Ce site contient + des informations détaillées sur les problèmes + matériels et logiciels connus.
      • + +
    • + Intégration TET : + la Boîte à outils pour l'Exécution de Tests ("Test + Execution Toolkit - TET") de l' Open Group + est un système léger et open-source permettant l'exécution + de tests sur des environnements distribués ou non. Cet outil effectue + ses vérifications en utilisant TET ainsi que des suites de tests + open-source, respectant les standards, et existant sous FreeBSD + (VSX-PCTS, VSC-Lite, VSTH-Lite, VSW5 et autres).
      • +
    --- projects.sgml.diff ends here --- >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-doc@FreeBSD.ORG Sat Jun 23 16:30:12 2012 Return-Path: Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 374DA1065672 for ; Sat, 23 Jun 2012 16:30:12 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 09F6D8FC16 for ; Sat, 23 Jun 2012 16:30:12 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q5NGUBw2065243 for ; Sat, 23 Jun 2012 16:30:11 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q5NGUB2N065239; Sat, 23 Jun 2012 16:30:11 GMT (envelope-from gnats) Resent-Date: Sat, 23 Jun 2012 16:30:11 GMT Resent-Message-Id: <201206231630.q5NGUB2N065239@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, Devin Teske Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id CB603106564A for ; Sat, 23 Jun 2012 16:29:24 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from red.freebsd.org (red.freebsd.org [IPv6:2001:4f8:fff6::22]) by mx1.freebsd.org (Postfix) with ESMTP id B5CBB8FC0C for ; Sat, 23 Jun 2012 16:29:24 +0000 (UTC) Received: from red.freebsd.org (localhost [127.0.0.1]) by red.freebsd.org (8.14.4/8.14.4) with ESMTP id q5NGTOCC064550 for ; Sat, 23 Jun 2012 16:29:24 GMT (envelope-from nobody@red.freebsd.org) Received: (from nobody@localhost) by red.freebsd.org (8.14.4/8.14.4/Submit) id q5NGTOm3064549; Sat, 23 Jun 2012 16:29:24 GMT (envelope-from nobody) Message-Id: <201206231629.q5NGTOm3064549@red.freebsd.org> Date: Sat, 23 Jun 2012 16:29:24 GMT From: Devin Teske To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-3.1 Cc: Subject: docs/169354: passwd(5) manual incorrectly documents password-change/account-expire features X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 Jun 2012 16:30:12 -0000 >Number: 169354 >Category: docs >Synopsis: passwd(5) manual incorrectly documents password-change/account-expire features >Confidential: no >Severity: serious >Priority: high >Responsible: freebsd-doc >State: open >Quarter: >Keywords: >Date-Required: >Class: doc-bug >Submitter-Id: current-users >Arrival-Date: Sat Jun 23 16:30:11 UTC 2012 >Closed-Date: >Last-Modified: >Originator: Devin Teske >Release: FreeBSD 9.0-RELEASE i386 >Organization: FIS Global, Inc. >Environment: FreeBSD scribe9.vicor.com 9.0-RELEASE FreeBSD 9.0-RELEASE #0: Tue Jan 3 07:15:25 UTC 2012 root@obrian.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386 >Description: In the passwd(5) manual it states: The change field is the number of seconds from the epoch, UTC, until the password for the account must be changed. This field may be left empty to turn off the password aging feature. The expire field is the number of seconds from the epoch, UTC, until the account expires. This field may be left empty to turn off the account aging feature. This, however, is an incomplete description. The FreeBSD operating system uses a value of zero by-default (for both password-change and account-expire fields) for all default users on a vanilla/freshly-installed system. Meanwhile, the manual says nothing about a value of zero (0) being functionally equivalent to NULL (experienced behavior). Rather, if one takes the manual literally (given above), a value of zero is taken as "number of seconds from the epoch, UTC" and therefore, one would expect that all accounts in a default install are both (a) expired (account-wise) and (b) have expired passwords. The manual should likely be updated to say that zero is functionally equivalent to NULL. >How-To-Repeat: Read passwd(5). Now execute the following to see the password-change and account-expire fields for all users: sudo awk -F: '{print $1 ":" $6 ":" $7}' /etc/master.passwd Notice how all (or nearly all) users have a value of zero, including root and all privilege-separation users. >Fix: Update passwd(5) manual to mention that a value of zero is functionally equivalent to NULL. >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-doc@FreeBSD.ORG Sat Jun 23 17:13:02 2012 Return-Path: Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id BBF7B1065672; Sat, 23 Jun 2012 17:13:02 +0000 (UTC) (envelope-from bjk@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 8F3FC8FC0C; Sat, 23 Jun 2012 17:13:02 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q5NHD2CI010326; Sat, 23 Jun 2012 17:13:02 GMT (envelope-from bjk@freefall.freebsd.org) Received: (from bjk@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q5NHD2BI010322; Sat, 23 Jun 2012 17:13:02 GMT (envelope-from bjk) Date: Sat, 23 Jun 2012 17:13:02 GMT Message-Id: <201206231713.q5NHD2BI010322@freefall.freebsd.org> To: bjk@FreeBSD.org, freebsd-doc@FreeBSD.org, bjk@FreeBSD.org From: bjk@FreeBSD.org Cc: Subject: Re: docs/169354: passwd(5) manual incorrectly documents password-change/account-expire features X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 Jun 2012 17:13:02 -0000 Synopsis: passwd(5) manual incorrectly documents password-change/account-expire features Responsible-Changed-From-To: freebsd-doc->bjk Responsible-Changed-By: bjk Responsible-Changed-When: Sat Jun 23 17:12:45 UTC 2012 Responsible-Changed-Why: take http://www.freebsd.org/cgi/query-pr.cgi?pr=169354 From owner-freebsd-doc@FreeBSD.ORG Sat Jun 23 21:56:10 2012 Return-Path: Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0ED79106564A; Sat, 23 Jun 2012 21:56:10 +0000 (UTC) (envelope-from wblock@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id D61778FC17; Sat, 23 Jun 2012 21:56:09 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q5NLu91S069963; Sat, 23 Jun 2012 21:56:09 GMT (envelope-from wblock@freefall.freebsd.org) Received: (from wblock@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q5NLu94L069959; Sat, 23 Jun 2012 21:56:09 GMT (envelope-from wblock) Date: Sat, 23 Jun 2012 21:56:09 GMT Message-Id: <201206232156.q5NLu94L069959@freefall.freebsd.org> To: wblock@FreeBSD.org, freebsd-doc@FreeBSD.org, wblock@FreeBSD.org From: wblock@FreeBSD.org Cc: Subject: Re: docs/112682: Handbook GEOM_GPT explanation does not provide accurate information X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 Jun 2012 21:56:10 -0000 Synopsis: Handbook GEOM_GPT explanation does not provide accurate information Responsible-Changed-From-To: freebsd-doc->wblock Responsible-Changed-By: wblock Responsible-Changed-When: Sat Jun 23 21:55:29 UTC 2012 Responsible-Changed-Why: Take. http://www.freebsd.org/cgi/query-pr.cgi?pr=112682 From owner-freebsd-doc@FreeBSD.ORG Sat Jun 23 22:05:03 2012 Return-Path: Delivered-To: doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 27F4B1065670; Sat, 23 Jun 2012 22:05:03 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) by mx1.freebsd.org (Postfix) with ESMTP id D563A8FC08; Sat, 23 Jun 2012 22:05:02 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.5/8.14.5) with ESMTP id q5NM52vf087736; Sat, 23 Jun 2012 16:05:02 -0600 (MDT) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.5/8.14.5/Submit) with ESMTP id q5NM529Q087733; Sat, 23 Jun 2012 16:05:02 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Sat, 23 Jun 2012 16:05:01 -0600 (MDT) From: Warren Block To: Gabor Kovesdan In-Reply-To: <4FE368F6.4030805@FreeBSD.org> Message-ID: References: <4FE368F6.4030805@FreeBSD.org> 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.2.7 (wonkity.com [127.0.0.1]); Sat, 23 Jun 2012 16:05:02 -0600 (MDT) Cc: doc@freebsd.org Subject: Re: [HEADS UP] XML migration and opening of projects/ X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 Jun 2012 22:05:03 -0000 On Thu, 21 Jun 2012, Gabor Kovesdan wrote: > the migration to SVN and the related reorganization seem to have gone > seamlessly. However, the planned doc infrastructure improvements are not > finished yet. The next item on our TODO list is the long overdue XML > migration. Now we have a proper VCS system that supports renames and > moves in the tree so we can follow up with bigger reorganizations. > (Side note: do not be afraid of the changes, authoring will not be more > complicated at all.) > > This XML migration is quite a complex reorganization and as such, it > cannot be done on the mainline of doc development so we decided to do it > in a separate branch. Also, this project will be the first > experiment on branching and merging back changes to head. To open > projects/ for the public we have to carefully evaluate the potential > scenarios of merging and choose that one that best suites our > development model. We at doceng will work out a draft about using > projects/ and merging changes back to head. We will post this to doc@ > and once the policies and best practices are established, finally > projects/ will be open for the big public. > > You can expect to see our draft policies in 2-3 weeks, so projects/ may > be open around mid-July. How automated is the conversion? Put another way: should we delay major whitespace or content commits to existing SGML documents? From owner-freebsd-doc@FreeBSD.ORG Sat Jun 23 23:02:09 2012 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id CE6DD1065674; Sat, 23 Jun 2012 23:02:09 +0000 (UTC) (envelope-from raylee012088@gmail.com) Received: from mail-lb0-f182.google.com (mail-lb0-f182.google.com [209.85.217.182]) by mx1.freebsd.org (Postfix) with ESMTP id 190388FC08; Sat, 23 Jun 2012 23:02:08 +0000 (UTC) Received: by lbon10 with SMTP id n10so6151370lbo.13 for ; Sat, 23 Jun 2012 16:02:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=+CX8N0Rn/sXL1INXuSbaErADXDYACeqfM0GJHdivFKs=; b=0vQR1K63rtcG6nuKbAqFOkNOMDRq9Syb4Dr2wsQpXTxjPerPLiQhaFUyExwtm1hDBj FLaI8WPeHhbHYrE52KcZkjSDjWKGJF52p4cW7skQvLJlosM7BsO2v1HeXsXC1rk0T5Tj CP/rUa5rzbZ6mbbtw2m331w8t8K760E1+rpYQWpbbgbE8TVKVOKDEiEy/f6f2oeH3epk ouXszCKZm9pOEwv7cI0smkabMM80vpiluFFiN2XPRvupbDvNH345q4/jF8xPVSyjafbm qujx+3Dpid+1+OGnqf59IHLc1yzgzUlEB0d/BNhkuY0DjHO+9nNyHwzccgA+niQpvOpY rVYw== MIME-Version: 1.0 Received: by 10.112.23.200 with SMTP id o8mr3689307lbf.9.1340492527995; Sat, 23 Jun 2012 16:02:07 -0700 (PDT) Received: by 10.112.75.168 with HTTP; Sat, 23 Jun 2012 16:02:07 -0700 (PDT) Received: by 10.112.75.168 with HTTP; Sat, 23 Jun 2012 16:02:07 -0700 (PDT) In-Reply-To: <201206212100.q5LL0SM6093147@freefall.freebsd.org> References: <201206212100.q5LL0SM6093147@freefall.freebsd.org> Date: Sun, 24 Jun 2012 07:02:07 +0800 Message-ID: From: raylee012088 To: wblock@freebsd.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freebsd-doc@freebsd.org Subject: Re: docs/169285: [handbook] Handbook some troubles X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: raylee012088@gmail.com List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 Jun 2012 23:02:09 -0000 I received more mail in this week ,the mail also post this web site call me to checking .how to change this .I didn't know! 2012-6-22 =E4=B8=8A=E5=8D=885:01 =E6=96=BC "Niclas Zeising" =E5=AF=AB=E9=81=93=EF=BC=9A > > The following reply was made to PR docs/169285; it has been noted by GNATS. > > From: Niclas Zeising > To: =3D?UTF-8?B?0KHQtdGA0LPQtdC5INCU0LXQtNGO0LvRjw=3D=3D?=3D , > bug-followup@FreeBSD.org > Cc: > Subject: Re: docs/169285: [handbook] Handbook some troubles > Date: Thu, 21 Jun 2012 22:53:43 +0200 > > On 06/21/12 15:34, =D0=A1=D0=B5=D1=80=D0=B3=D0=B5=D0=B9 =D0=94=D0=B5=D0= =B4=D1=8E=D0=BB=D1=8F wrote: > > Commiting instead ommiting unused kernel code - syntax error > > I am still unsure of what the issue you are trying to point out is. As > far as I can tell, the sentence "A custom kernel often uses less memory > than the GENERIC kernel by omitting unused features and device drivers." > is perfectly valid English and it explains that a kernel without > unneeded drivers uses less memory. Omitted, or omitting, means to not > include. > Can you please try to explain in greater detail what the issue is? > Regards! > -- > Niclas Zeising > _______________________________________________ > freebsd-doc@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-doc > To unsubscribe, send any mail to "freebsd-doc-unsubscribe@freebsd.org"