From owner-freebsd-doc@FreeBSD.ORG Sun Dec 7 03:37:54 2008 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3ED0E1065676 for ; Sun, 7 Dec 2008 03:37:54 +0000 (UTC) (envelope-from eitanadlerlist@gmail.com) Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.169]) by mx1.freebsd.org (Postfix) with ESMTP id 118A48FC14 for ; Sun, 7 Dec 2008 03:37:53 +0000 (UTC) (envelope-from eitanadlerlist@gmail.com) Received: by wf-out-1314.google.com with SMTP id 24so684570wfg.7 for ; Sat, 06 Dec 2008 19:37:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:user-agent :mime-version:to:subject:x-enigmail-version:openpgp:content-type :content-transfer-encoding:from; bh=vCMapHbktpjxt1qFqaXBWrBf1Y+RnSC8OzwVdcO0WDY=; b=es3l9Hewlk7qIYzVkis2eHt/edFF/kvd9+JAC9CoWd6D7nypVGXVVTeXqolBe36xCB R4w93Svh8T/Egz50Gxwpl2KHL1Of83wW8NHYJMgdGbCgfH9lcmguQojtFLqV96NU/NgM x1OdVupli39gBAOcvJnn+IjX9IWuLHK56j7T4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:user-agent:mime-version:to:subject :x-enigmail-version:openpgp:content-type:content-transfer-encoding :from; b=nwT4Sal3wMVOB6bWmSscdEDtnh2C/yKqFNYBRPqnkArubClmV+GkstfgldL2D9kCcu B+l1pcM/jvgOmUP6nGnvOKzPM+a89iE1PQyc7RCAabMaVHviRCjj+Qy2K4cokWK+6h4d FovQuZAV1AD67mQUw5+RlaI6Ga2qg3CND+tvA= Received: by 10.142.162.5 with SMTP id k5mr804541wfe.113.1228621073660; Sat, 06 Dec 2008 19:37:53 -0800 (PST) Received: from aargh.lan (ool-182fcc8b.dyn.optonline.net [24.47.204.139]) by mx.google.com with ESMTPS id 30sm4422377wfa.1.2008.12.06.19.37.51 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sat, 06 Dec 2008 19:37:52 -0800 (PST) Message-ID: <493B4511.4030905@gmail.com> Date: Sat, 06 Dec 2008 22:37:53 -0500 User-Agent: Mozilla (X11; U; FreeBSD i386; en-US; ) Gecko Thunderbird Mnenhy/0.7.5.666 MIME-Version: 1.0 To: freebsd-doc@freebsd.org X-Enigmail-Version: 0.95.7 OpenPGP: id=E9C2CCD1; url=pgp.mit.edu Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit From: Eitan Adler Subject: bc 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: Sun, 07 Dec 2008 03:37:54 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 bc is a language that supports arbitrary precision numbers with interactive execution of statements. - -->This sentence does not make sense. I'm not even sure what its trying to say. A standard math library is available by command line option. - --> The ?? command line option allows you to use a standard math library or something like that? - -- Eitan Adler GNU Key fingerptrint: 2E13 BC16 5F54 0FBD 62ED 42B6 B65F 24AB E9C2 CCD1 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAkk7RREACgkQtl8kq+nCzNH9nQCghu9oXUfN0G+6sUbPy9XjEv1u s2wAn0tAByRpj4ifLRjpMf1ErIGDuQ6k =1fmm -----END PGP SIGNATURE----- From owner-freebsd-doc@FreeBSD.ORG Sun Dec 7 09:26:24 2008 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E58B11065691; Sun, 7 Dec 2008 09:26:24 +0000 (UTC) (envelope-from sziszi@bsd.hu) Received: from mail.rubicom.hu (mail.rubicom.hu [89.147.80.28]) by mx1.freebsd.org (Postfix) with ESMTP id 6D2538FC12; Sun, 7 Dec 2008 09:26:24 +0000 (UTC) (envelope-from sziszi@bsd.hu) Received: from localhost ([127.0.0.1] helo=mail.rubicom.hu) by mail.rubicom.hu with smtp (Exim 4.63) (envelope-from ) id 1L9FuA-0004n5-0H; Sun, 07 Dec 2008 10:26:22 +0100 Received: from ip5993549e.rubicom.hu ([89.147.84.158] helo=baranyfelhocske.buza.adamsfamily.xx) by mail.rubicom.hu with esmtp (Exim 4.63) (envelope-from ) id 1L9Fu9-0004mx-Oy; Sun, 07 Dec 2008 10:26:21 +0100 Received: from baranyfelhocske.buza.adamsfamily.xx (localhost [127.0.0.1]) by baranyfelhocske.buza.adamsfamily.xx (8.14.3/8.14.3) with ESMTP id mB79QLM3003600; Sun, 7 Dec 2008 10:26:21 +0100 (CET) (envelope-from sziszi@bsd.hu) Received: (from sziszi@localhost) by baranyfelhocske.buza.adamsfamily.xx (8.14.3/8.14.3/Submit) id mB79QLD0003599; Sun, 7 Dec 2008 10:26:21 +0100 (CET) (envelope-from sziszi@bsd.hu) X-Authentication-Warning: baranyfelhocske.buza.adamsfamily.xx: sziszi set sender to sziszi@bsd.hu using -f Date: Sun, 7 Dec 2008 10:26:21 +0100 From: Szilveszter Adam To: freebsd-doc@freebsd.org, freebsd-gnats-submit@freebsd.org Message-ID: <20081207092621.GC2187@baranyfelhocske.buza.adamsfamily.xx> References: <200812061529.mB6FTBEd024942@www.freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200812061529.mB6FTBEd024942@www.freebsd.org> User-Agent: Mutt/1.5.18 (2008-05-17) Cc: Subject: Re: docs/129464: using packages system X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Dec 2008 09:26:25 -0000 On Sat, Dec 06, 2008 at 03:29:11PM +0000, guillaume wrote: > in the FreeBSD handbook, 4.4 (Using the Packages System), pkg_add and pkg_delete are obsolete commands to manage packages. it's quasi-impossible to control requirements packages with these commands. On this, I tend to agree. However, when starting out with a new system, these are the only commands that are available. > >Fix: > the good commands are portupgrade and pkg_deinstall. > the portupgrade tool must be natively integrated in FreeBSD. This is not possible with the current state of affairs, because portupgrade has external dependencies. It must rewritten first (like it happened with cvsup). > example of procedure: > > 1) it's better to have PACKAGESITE to the last stable branch by default, no? No. Those packages were specifically made for the stable branch, not the release that you are trying to install. In most cases, it would probably work (but only, if you upgrade all packages at the same time and from tha same branch) but not always (eg if a component of the base has already been upgraded in the stable branch compared to your release and eg a library version has been bumped) The trouble is, that on FreeBSD using packages was not the way to install third-party software. It was provided more as a quick aid or a convenience, but the recommended method was to use the ports and compile yourself. This procedure is well-tested and works fine today as well. Packages, by contrast, are trickier. Not just for FreeBSD: on most Linux distros, there is no option to eg only upgrade Firefox, unless the maintainer has specifically made a new package for the distro and release you are using; otherwise you must wait until the next release. On FreeBSD, by contrast, there was no problem with upgrading eg Firefox or even complex stuff like the whole KDE environment although the new FreeBSD release was still months away, since the ports system did the trick. > 2) install port collection with csup > 3) clean database with pkgdb -aF (is it necessary after the port collection install?) Not really, you did not install anything yet, so there is no database. > 4) to install the xfce package: portinstall -RPP xfce > 5) to upgrade the xfce package: portupgrade -RPP xfce > 6) to delete the xfce package: pkg_deinstall -r xfce > > > > PS: it's not convenient to install the port collection if one only use packages. a solution to this will be good for the future... Only, if there will be a decision that binary packages will be the primary method of installing third-party software on FreeBSD. This is not the case today. -- Regards: Szilveszter ADAM Budapest Hungary From owner-freebsd-doc@FreeBSD.ORG Sun Dec 7 09:30:04 2008 Return-Path: Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E49951065673 for ; Sun, 7 Dec 2008 09:30:04 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id D34CB8FC1C for ; Sun, 7 Dec 2008 09:30:04 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id mB79U4xm095515 for ; Sun, 7 Dec 2008 09:30:04 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id mB79U4Hb095511; Sun, 7 Dec 2008 09:30:04 GMT (envelope-from gnats) Date: Sun, 7 Dec 2008 09:30:04 GMT Message-Id: <200812070930.mB79U4Hb095511@freefall.freebsd.org> To: freebsd-doc@FreeBSD.org From: Szilveszter Adam Cc: Subject: Re: docs/129464: using packages system X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Szilveszter Adam List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Dec 2008 09:30:05 -0000 The following reply was made to PR docs/129464; it has been noted by GNATS. From: Szilveszter Adam To: freebsd-doc@freebsd.org, freebsd-gnats-submit@freebsd.org Cc: Subject: Re: docs/129464: using packages system Date: Sun, 7 Dec 2008 10:26:21 +0100 On Sat, Dec 06, 2008 at 03:29:11PM +0000, guillaume wrote: > in the FreeBSD handbook, 4.4 (Using the Packages System), pkg_add and pkg_delete are obsolete commands to manage packages. it's quasi-impossible to control requirements packages with these commands. On this, I tend to agree. However, when starting out with a new system, these are the only commands that are available. > >Fix: > the good commands are portupgrade and pkg_deinstall. > the portupgrade tool must be natively integrated in FreeBSD. This is not possible with the current state of affairs, because portupgrade has external dependencies. It must rewritten first (like it happened with cvsup). > example of procedure: > > 1) it's better to have PACKAGESITE to the last stable branch by default, no? No. Those packages were specifically made for the stable branch, not the release that you are trying to install. In most cases, it would probably work (but only, if you upgrade all packages at the same time and from tha same branch) but not always (eg if a component of the base has already been upgraded in the stable branch compared to your release and eg a library version has been bumped) The trouble is, that on FreeBSD using packages was not the way to install third-party software. It was provided more as a quick aid or a convenience, but the recommended method was to use the ports and compile yourself. This procedure is well-tested and works fine today as well. Packages, by contrast, are trickier. Not just for FreeBSD: on most Linux distros, there is no option to eg only upgrade Firefox, unless the maintainer has specifically made a new package for the distro and release you are using; otherwise you must wait until the next release. On FreeBSD, by contrast, there was no problem with upgrading eg Firefox or even complex stuff like the whole KDE environment although the new FreeBSD release was still months away, since the ports system did the trick. > 2) install port collection with csup > 3) clean database with pkgdb -aF (is it necessary after the port collection install?) Not really, you did not install anything yet, so there is no database. > 4) to install the xfce package: portinstall -RPP xfce > 5) to upgrade the xfce package: portupgrade -RPP xfce > 6) to delete the xfce package: pkg_deinstall -r xfce > > > > PS: it's not convenient to install the port collection if one only use packages. a solution to this will be good for the future... Only, if there will be a decision that binary packages will be the primary method of installing third-party software on FreeBSD. This is not the case today. -- Regards: Szilveszter ADAM Budapest Hungary From owner-freebsd-doc@FreeBSD.ORG Sun Dec 7 23:30:04 2008 Return-Path: Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A5B051065670 for ; Sun, 7 Dec 2008 23:30:04 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 952E88FC1A for ; Sun, 7 Dec 2008 23:30:04 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id mB7NU4O3048781 for ; Sun, 7 Dec 2008 23:30:04 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id mB7NU4jK048778; Sun, 7 Dec 2008 23:30:04 GMT (envelope-from gnats) Date: Sun, 7 Dec 2008 23:30:04 GMT Message-Id: <200812072330.mB7NU4jK048778@freefall.freebsd.org> To: freebsd-doc@FreeBSD.org From: guillaume Cc: Subject: Re: docs/129464: using packages system X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: guillaume List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Dec 2008 23:30:04 -0000 The following reply was made to PR docs/129464; it has been noted by GNATS. From: guillaume To: bug-followup@FreeBSD.org, g71@laposte.net Cc: sziszi@bsd.hu Subject: Re: docs/129464: using packages system Date: Mon, 08 Dec 2008 00:12:27 +0100 it will be good to integrate the keys features of your explanation in the handbook: - it isn't recommended to override PACKAGESITE because packages are specifically made for a branch. - pkg_add and pkg_delete are obsolete, use the portupgrade tool. it is recommended to install it before you try to manage package. portupgrade use the port tree, so you must have the port tree installed. examples: - install the xfce package: portinstall -RPP xfce - upgrade your xfce with the ports: portupgrade -R xfce - uninstalll your xfce: pkg_deinstall -r xfce (and if the user can access to internet, it seems recommended to not install the port tree from the distribution media, but directly from internet after the FreeBSD installation (with csup), no?) regards From owner-freebsd-doc@FreeBSD.ORG Mon Dec 8 06:50:03 2008 Return-Path: Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 503701065672 for ; Mon, 8 Dec 2008 06:50:03 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 3F8B48FC0C for ; Mon, 8 Dec 2008 06:50:03 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id mB86o266087986 for ; Mon, 8 Dec 2008 06:50:02 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id mB86o2dM087985; Mon, 8 Dec 2008 06:50:02 GMT (envelope-from gnats) Date: Mon, 8 Dec 2008 06:50:02 GMT Message-Id: <200812080650.mB86o2dM087985@freefall.freebsd.org> To: freebsd-doc@FreeBSD.org From: Szilveszter Adam Cc: Subject: Re: docs/129464: using packages system X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Szilveszter Adam List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 08 Dec 2008 06:50:03 -0000 The following reply was made to PR docs/129464; it has been noted by GNATS. From: Szilveszter Adam To: guillaume Cc: bug-followup@freebsd.org Subject: Re: docs/129464: using packages system Date: Mon, 8 Dec 2008 07:03:35 +0100 Dear guillaume, On Mon, Dec 08, 2008 at 12:12:27AM +0100, guillaume wrote: > it will be good to integrate the keys features of your explanation in > the handbook: I am ok with this :-) > - it isn't recommended to override PACKAGESITE because packages are > specifically made for a branch. Yes. > - pkg_add and pkg_delete are obsolete, use the portupgrade tool. it is > recommended to install it before you try to manage package. portupgrade > use the port tree, so you must have the port tree installed. > examples: > - install the xfce package: portinstall -RPP xfce > - upgrade your xfce with the ports: portupgrade -R xfce > - uninstalll your xfce: pkg_deinstall -r xfce Yes. (Although I am not sure what happens if you use -PP and do not have the ports tree. I will try it sometime.) > (and if the user can access to internet, it seems recommended to not > install the port tree from the distribution media, but directly from > internet after the FreeBSD installation (with csup), no?) Yes, this is a good recommendation. I do it like this all the time. -- Regards: Szilveszter ADAM Budapest Hungary From owner-freebsd-doc@FreeBSD.ORG Mon Dec 8 11:06:06 2008 Return-Path: Delivered-To: freebsd-doc@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 46C851065677 for ; Mon, 8 Dec 2008 11:06:06 +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 338538FC2A for ; Mon, 8 Dec 2008 11:06:06 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id mB8B66Kh013308 for ; Mon, 8 Dec 2008 11:06:06 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id mB8B65AO013304 for freebsd-doc@FreeBSD.org; Mon, 8 Dec 2008 11:06:05 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 8 Dec 2008 11:06:05 GMT Message-Id: <200812081106.mB8B65AO013304@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, 08 Dec 2008 11:06:06 -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/129464 doc using packages system o docs/129428 doc ntp.conf(5) is incorrect - you can only use IP address o docs/129400 doc [patch] Remove comments that have snook into three man o docs/129398 doc [patch] ddb(8): various tweaks to ddb-related man page o docs/129281 doc Audio CD ripping/duplication shouldn't recommend the u o docs/129263 doc Obsolete info on collecting a crash dump prior to "dum o docs/129196 doc Inconsistent errno in strtol() o docs/129095 doc ipfw(8): Can not check that packet originating/destine o docs/129024 doc [patch] ipfw(8) improvements p docs/128968 doc [patch] rwlock(9) man page typo o docs/128804 doc Gmirror handbook instructions convert boot-drive to gm o docs/128768 doc Missing documentation about tmpfs mount options o docs/128356 doc [request] add Firefox plugin for FreeBSD manual pages o docs/128325 doc README.snapshots still refers to snaphots as "alpha-te o docs/128222 doc [patch] man page truss(1) claims that init(8) can be t o docs/128129 doc Sysinstall color problem in xterm o docs/128128 doc Sysinstall not mentioned in 4.4 "Using the Packages Sy o docs/128032 doc pthread(3) mentions libkse which has been removed in 8 o docs/127952 doc man for locate(1) is missing o docs/127923 doc Please mention qemu in the FreeBSD Handbook o docs/127908 doc [PATCH] readdir(3) error documentation o docs/127890 doc socket(2) man page should explain that protocol can be p docs/127866 doc Typos found in ifconfig(8) man page o docs/127844 doc Example code skeleton_capture_n.c in meteor(4) manpage o docs/127842 doc list of hardware devices missing from the relnotes o docs/127840 doc [patch] fix entity references in release/doc/en_US.ISO o docs/127602 doc [patch] Incomplete information in nsswitch.conf(5) o docs/127575 doc [patch] Update to ports (7) as it is missing a few mak o docs/127406 doc [patch] update umodem man page: Sony Ericsson W810i o docs/126934 doc missing 'crit' in usr.sbin/syslogd/syslog.conf.5 o docs/126921 doc [patch] History section of cpuset(1) incorrect o docs/126590 doc [patch] Write routine called forever in Sample Echo Ps o docs/126487 doc fix language on atol(3) manpage o docs/126484 doc libc function res-zonscut2 is not documented o docs/126445 doc discussion on WEP settings in wpa_supplicant.conf(5) m o docs/126227 doc [patch] kthread(9) refers to non-existent manpage, des o docs/125921 doc lpd(8) talks about blocks in minfree while it is KB in o docs/125896 doc [PATCH] arp manual and syntax synchronisation o docs/125751 doc man 3 pthread_getschedparam section ERRORS incomplete o docs/125639 doc [patch] kldunloadf(2) does not mention about possible p docs/124166 doc fortune: instant-workstation tip should go o docs/123400 doc gvinum startup in handbook o docs/123035 doc [patch] bugs in refuse.README o docs/122470 doc [patch] exit status on fetch(1) manual page o docs/122053 doc [patch] update on vinum(4) reference to newfs(8) o docs/122052 doc minor update on handbook section 20.7.1 o docs/121952 doc Handbook chapter on Network Address Translation wrong o docs/121871 doc ftpd does not interpret configuration files as documen o docs/121585 doc [handbook] Wrong multicast specification o docs/121565 doc dhcp-options(5) manpage incorrectly formatted omitting 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/121197 doc [patch] edits to books/porters-handbook 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/120628 doc PAE documentation errror in handbook o docs/120539 doc Inconsistent ipfw's man page o docs/120456 doc ath(4) needs to specify requirement on wlan_scan_sta o docs/120125 doc [patch] Installing FreeBSD 7.0 via serial console and o docs/120040 doc handbook: diskless operation: populate root doesn't po o docs/120024 doc resolver(5) and hosts(5) need updated for IPv6 o docs/119907 doc Ports compatibility o docs/119746 doc l10n chapter of handbook (Russian Language) o docs/119545 doc books/arch-handbook/usb/chapter.sgml formatting a docs/119536 doc a few typos in French handbook (basics) s docs/119404 doc [request] events page should list only last 2 years wo o docs/119338 doc gprof(1) refers to unmentioned option "-c" o docs/119329 doc [patch] Fix misleading man 1 split o docs/118902 doc [patch] wrong signatures in d2i_RSAPublicKey man pages o docs/118545 doc loader tunables kern.dfldsiz and friends nearly undocu o docs/118332 doc man page for top does not describe STATE column wait e o docs/118214 doc close(2) error returns incomplete o docs/118020 doc ipfilter(4): man pages query for man 4 ipfilter return o docs/117798 doc formatting oddity in sysmouse(4) o docs/117747 doc 'break' system call needs a man page o docs/117013 doc mount_smbfs(8) doesn't document -U (username) argument o docs/116480 doc sysctl(3) description of kern.file no longer applies s o docs/116116 doc mktemp (3) re/move note o docs/116080 doc PREFIX is documented, but not the more important LOCAL o docs/115921 doc Booting from pst(4) is not supported o 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/114184 doc [patch] [ndis]: add info to man 4 ndis 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/112804 doc groff(1) command should be called to explicitly use "p o docs/112682 doc Handbook GEOM_GPT explanation does not provide accurat o docs/112481 doc bug in ppp.linkup example 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/111263 doc [request] Information on $EDITOR variable in section 3 o docs/111147 doc hostapd.conf is not documented 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/110253 doc [patch] rtprio(1): remove processing starvation commen o docs/110062 doc [patch] mount_nfs(8) fails to mention a failure condit o docs/110061 doc [PATCH] tuning(7) missing reference to vfs.read_max o docs/109983 doc No manual entry for protoize o docs/109981 doc No manual entry for post-grohtml o docs/109977 doc No manual entry for ksu o docs/109975 doc No manual entry for elf2aout 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 o docs/109115 doc add Ultra 450 to hardware list for sparc64 a docs/108980 doc list of missing man pages o docs/108101 doc /boot/default/loader.conf contains an incorrect commen o docs/106135 doc [request] articles/vinum needs to be updated o docs/105997 doc sys/kern/sys_pipe.c refer to tuning(7), but there is n 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/104403 doc man security should mention that the usage of the X Wi o docs/102719 doc [patch] ng_bpf(4) example leads to unneeded promiscuos o docs/102148 doc The description of which Intel chips have EM64T is out o docs/101464 doc sync ru_RU.KOI8-R/articles/portbuild/article.html with o docs/100242 doc sysctl(3) description of KERN_PROC is not correct anym 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/98759 doc [patch] sbp_targ(4) man page missing reference to devi 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/95139 doc FAQ to move filesystem to new disk fails: incorrect pe 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/91174 doc [REQUEST] Handbook: Addition of Oracle 9i installation 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/86342 doc bikeshed entry of Handbook is wrong o docs/85187 doc [patch] find(1) manpage missing block info for -ls o docs/85128 doc [patch] loader.conf(5) autoboot_delay incompletly desc o docs/85118 doc [PATCH] opiekey(1) references non-existing opiegen(1) o docs/85100 doc NOTES: ICH audio device support statement is ambiguous 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/84806 doc mdoc(7) manpage has section ordering problems o docs/84670 doc [patch] tput(1) manpage missing ENVIRONMENT section wi o docs/84538 doc [patch] sk(4) driver supports Marvell 88E800x chip too o docs/84317 doc fdp-primer doesn't show class=USERNAME distinctively o docs/84268 doc chmod(1) manpage's BUGS entry is either wrong or too c o docs/84265 doc [patch] chmod(1) manpage omits implication of setting f docs/82595 doc 25.5.3 Configuring a bridge section of the handbook ne o docs/78480 doc Networked printer setup unnecessarily complex in handb o docs/78240 doc [patch] handbook: replace with aroun o docs/78138 doc [patch] Error in pre-installation section of installat o docs/76333 doc [patch] ferror(3): EOF indicator can be cleared by not o docs/75865 doc comments on "backup-basics" in handbook o docs/70652 doc [patch] New man page: portindex(5) o docs/70583 doc [patch] Update freebsd-glossary o docs/69861 doc [patch] usr.bin/csplit/csplit.1 does not document POSI o docs/63570 doc [patch] Language cleanup for the Handbook's DNS sectio 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/57388 doc [patch] INSTALL.TXT enhancement: mention ok prompt 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/50211 doc [PATCH] doc.docbook.mk: fix textfile creation o docs/48101 doc [patch] add documentation on the fixit disk to the FAQ o docs/47818 doc [patch] ln(1) manpage is confusing 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 o docs/36449 doc symlink(7) manual doesn't mention trailing slash, etc. s docs/35678 doc docproj Makefiles for web are broken for paths with sp s docs/33589 doc [patch] to doc.docbook.mk to post process .tex files. a docs/30008 doc [patch] French softupdates document should be translat 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 182 problems total. From owner-freebsd-doc@FreeBSD.ORG Mon Dec 8 12:24:24 2008 Return-Path: Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A075F1065675; Mon, 8 Dec 2008 12:24:24 +0000 (UTC) (envelope-from blackend@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 770A28FC0C; Mon, 8 Dec 2008 12:24:24 +0000 (UTC) (envelope-from blackend@FreeBSD.org) Received: from freefall.freebsd.org (blackend@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id mB8COOSK077309; Mon, 8 Dec 2008 12:24:24 GMT (envelope-from blackend@freefall.freebsd.org) Received: (from blackend@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id mB8COONv077305; Mon, 8 Dec 2008 12:24:24 GMT (envelope-from blackend) Date: Mon, 8 Dec 2008 12:24:24 GMT Message-Id: <200812081224.mB8COONv077305@freefall.freebsd.org> To: blackend@FreeBSD.org, freebsd-doc@FreeBSD.org, blackend@FreeBSD.org From: blackend@FreeBSD.org Cc: Subject: Re: docs/129281: Audio CD ripping/duplication shouldn't recommend the use of non endianness safe dd/burncd commands 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, 08 Dec 2008 12:24:24 -0000 Synopsis: Audio CD ripping/duplication shouldn't recommend the use of non endianness safe dd/burncd commands Responsible-Changed-From-To: freebsd-doc->blackend Responsible-Changed-By: blackend Responsible-Changed-When: Mon Dec 8 12:23:54 UTC 2008 Responsible-Changed-Why: Take care of it. http://www.freebsd.org/cgi/query-pr.cgi?pr=129281 From owner-freebsd-doc@FreeBSD.ORG Mon Dec 8 18:20:02 2008 Return-Path: Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 183E11065679 for ; Mon, 8 Dec 2008 18:20:02 +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 E99998FC1D for ; Mon, 8 Dec 2008 18:20:01 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id mB8IK18J040498 for ; Mon, 8 Dec 2008 18:20:01 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id mB8IK10l040497; Mon, 8 Dec 2008 18:20:01 GMT (envelope-from gnats) Resent-Date: Mon, 8 Dec 2008 18:20:01 GMT Resent-Message-Id: <200812081820.mB8IK10l040497@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, Jeff Burchell Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A7E0C1065675 for ; Mon, 8 Dec 2008 18:10:32 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (www.freebsd.org [IPv6:2001:4f8:fff6::21]) by mx1.freebsd.org (Postfix) with ESMTP id 96A158FC0C for ; Mon, 8 Dec 2008 18:10:32 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from www.freebsd.org (localhost [127.0.0.1]) by www.freebsd.org (8.14.3/8.14.3) with ESMTP id mB8IAWBm052608 for ; Mon, 8 Dec 2008 18:10:32 GMT (envelope-from nobody@www.freebsd.org) Received: (from nobody@localhost) by www.freebsd.org (8.14.3/8.14.3/Submit) id mB8IAWQu052607; Mon, 8 Dec 2008 18:10:32 GMT (envelope-from nobody) Message-Id: <200812081810.mB8IAWQu052607@www.freebsd.org> Date: Mon, 8 Dec 2008 18:10:32 GMT From: Jeff Burchell To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-3.1 Cc: Subject: docs/129506: Addition to Additional Contributors. 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, 08 Dec 2008 18:20:02 -0000 >Number: 129506 >Category: docs >Synopsis: Addition to Additional Contributors. >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-doc >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Mon Dec 08 18:20:01 UTC 2008 >Closed-Date: >Last-Modified: >Originator: Jeff Burchell >Release: 7.1-RC1 >Organization: >Environment: FreeBSD kvmfbsd.zyxyz.org 7.1-RC1 FreeBSD 7.1-RC1 #5: Sun Dec 7 10:29:22 PST 2008 root@kvmfbsd.zyxyz.org:/usr/obj/usr/src/sys/GENERIC amd64 >Description: I contributed archivers/libpar2 to the ports tree. I also maintain news/nzbget, and will likely start picking up additional ports that have been abandoned by their maintainers. It's my understanding that I should be listed in the Additional Contributors section of the documentation and web site. If that's true, please add me. If that's not true, then please kindly correct me (and either I or someone else should make that more clear in the Porter's Handbook) A patch to doc/en_US.ISO8859-1/articles/contributors/contrib.additional.sgml is attached. >How-To-Repeat: >Fix: Patch attached with submission follows: Index: contrib.additional.sgml =================================================================== RCS file: /home/ncvs/doc/en_US.ISO8859-1/articles/contributors/contrib.additional.sgml,v retrieving revision 1.827 diff -d -u -r1.827 contrib.additional.sgml --- contrib.additional.sgml 30 Nov 2008 12:44:20 -0000 1.827 +++ contrib.additional.sgml 7 Dec 2008 22:56:57 -0000 @@ -4167,6 +4167,11 @@ + Jeff Burchell + toxic@doobie.com + + + Jeff Forys jeff@forys.cranbury.nj.us >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-doc@FreeBSD.ORG Mon Dec 8 20:42:33 2008 Return-Path: Delivered-To: doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BD774106564A for ; Mon, 8 Dec 2008 20:42:33 +0000 (UTC) (envelope-from fernandotonus@gmail.com) Received: from mail-gx0-f19.google.com (mail-gx0-f19.google.com [209.85.217.19]) by mx1.freebsd.org (Postfix) with ESMTP id 767608FC19 for ; Mon, 8 Dec 2008 20:42:33 +0000 (UTC) (envelope-from fernandotonus@gmail.com) Received: by gxk12 with SMTP id 12so1229937gxk.19 for ; Mon, 08 Dec 2008 12:42:32 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:mime-version:content-type; bh=4nPRFHgoFLc46KHpTZUmWrmV67fhx9HMeF9KFLVzOUY=; b=W6DsxXnwBPzj2CGNv/EEa6sMxI3g3DN9pKXq8IZUdEtyrOAIuX51fF+hKB8697/HNZ g7yNDWWTpFfN1NSZoH7JUEopoBas7wsy7yoaiPenbtM2TMDzxjV/+JV01oANJUvxg7bJ dq4mtD12u4ocSnWX7euRpwgLowpVMu0tEeO3o= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type; b=iFX9+JCJ/T52NiHS1g3423xQhTFaldHsW9lq8iUS8fKQn5hPdwnKkzzLa8ftPZB87u kOsxCjcclZzMGs8nUsEfOwf2lwrdNWPg+CyTEUkaJ3UuaHEd4pK9HfaWYkbdlYKr6+8X Y/MldUht2oEfe+DKHt8etqCiFrtEMPhR0rJcQ= Received: by 10.90.94.3 with SMTP id r3mr1446463agb.18.1228767479320; Mon, 08 Dec 2008 12:17:59 -0800 (PST) Received: by 10.90.115.4 with HTTP; Mon, 8 Dec 2008 12:17:59 -0800 (PST) Message-ID: Date: Mon, 8 Dec 2008 17:17:59 -0300 From: "Fernando Tonus" To: doc@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: Handbook - Section IPFW 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, 08 Dec 2008 20:42:33 -0000 I found an error in the last script called "Example Ruleset #2". The error is in the rule number 020. Wrong: $cmd 020 $skip *tcp* from any to x.x.x.x 53 out via $pif setup keep-state Right: $cmd 020 $skip *udp* from any to x.x.x.x 53 out via $pif setup keep-state Thanks. Regards, Fernando Tonus. From owner-freebsd-doc@FreeBSD.ORG Mon Dec 8 21:08:36 2008 Return-Path: Delivered-To: doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A436D106564A for ; Mon, 8 Dec 2008 21:08:36 +0000 (UTC) (envelope-from cswiger@mac.com) Received: from mail-out4.apple.com (mail-out4.apple.com [17.254.13.23]) by mx1.freebsd.org (Postfix) with ESMTP id 8AA2A8FC19 for ; Mon, 8 Dec 2008 21:08:36 +0000 (UTC) (envelope-from cswiger@mac.com) Received: from relay12.apple.com (relay12.apple.com [17.128.113.53]) by mail-out4.apple.com (Postfix) with ESMTP id 484E949D6834; Mon, 8 Dec 2008 12:50:04 -0800 (PST) Received: from relay12.apple.com (unknown [127.0.0.1]) by relay12.apple.com (Symantec Brightmail Gateway) with ESMTP id C7297464004; Mon, 8 Dec 2008 12:50:03 -0800 (PST) X-AuditID: 11807135-ab861bb000000e1f-77-493d8879e6c1 Received: from cswiger1.apple.com (cswiger1.apple.com [17.227.140.124]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by relay12.apple.com (Apple SCV relay) with ESMTP id 25B0B420004; Mon, 8 Dec 2008 12:50:01 -0800 (PST) Message-Id: <4E91A5AC-DE5B-4C25-8CA1-F7F35E9F7FDE@mac.com> From: Chuck Swiger To: Fernando Tonus In-Reply-To: Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v929.2) Date: Mon, 8 Dec 2008 12:50:01 -0800 References: X-Mailer: Apple Mail (2.929.2) X-Brightmail-Tracker: AAAAAA== Cc: doc@freebsd.org Subject: Re: Handbook - Section IPFW 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, 08 Dec 2008 21:08:36 -0000 On Dec 8, 2008, at 12:17 PM, Fernando Tonus wrote: > I found an error in the last script called "Example Ruleset #2". > The error is in the rule number 020. > > Wrong: > $cmd 020 $skip *tcp* from any to x.x.x.x 53 out via $pif setup keep- > state > > Right: > $cmd 020 $skip *udp* from any to x.x.x.x 53 out via $pif setup keep- > state Actually, you want to allow *both* udp/53 and tcp/53 out if you want to properly pass DNS requests through: $cmd 020 $skip tcp from any to x.x.x.x 53 out via $pif setup keep-state $cmd 020 $skip udp from any to x.x.x.x 53 out via $pif keep-state Regards, -- -Chuck From owner-freebsd-doc@FreeBSD.ORG Tue Dec 9 17:20:49 2008 Return-Path: Delivered-To: doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9A7471065679 for ; Tue, 9 Dec 2008 17:20:49 +0000 (UTC) (envelope-from ricardo.meb.jesus@gmail.com) Received: from gate.criticalsoftware.com (gate.criticalsoftware.com [212.13.37.242]) by mx1.freebsd.org (Postfix) with ESMTP id 5C84A8FC13 for ; Tue, 9 Dec 2008 17:20:49 +0000 (UTC) (envelope-from ricardo.meb.jesus@gmail.com) Received: from [192.168.1.52] (unknown [192.168.1.52]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by gate.criticalsoftware.com (Postfix) with ESMTP id 30A51E848B for ; Tue, 9 Dec 2008 16:50:40 +0000 (WET) Message-ID: <493EA1E0.2040200@gmail.com> Date: Tue, 09 Dec 2008 16:50:40 +0000 From: Ricardo Jesus User-Agent: Thunderbird 2.0.0.18 (Windows/20081105) MIME-Version: 1.0 To: doc@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: Handbook section 4.3 X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: ricardo.m.jesus@criticalsoftware.com List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Dec 2008 17:20:49 -0000 Hi, I've noticed that in section 4.3 "Finding your application" make search=program-name is introduced without referring the need of doing a make fetch on /usr/ports. Noticed this on a fresh 6.4. Hope it helped. Best regards, Ricardo Jesus. From owner-freebsd-doc@FreeBSD.ORG Tue Dec 9 17:50:48 2008 Return-Path: Delivered-To: doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9119810656D4 for ; Tue, 9 Dec 2008 17:50:48 +0000 (UTC) (envelope-from fernan.aguero@gmail.com) Received: from mail-qy0-f18.google.com (mail-qy0-f18.google.com [209.85.221.18]) by mx1.freebsd.org (Postfix) with ESMTP id 226B58FC28 for ; Tue, 9 Dec 2008 17:50:48 +0000 (UTC) (envelope-from fernan.aguero@gmail.com) Received: by qyk11 with SMTP id 11so204139qyk.19 for ; Tue, 09 Dec 2008 09:50:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:mime-version:content-type; bh=kFued+pZrm4PfO+9pR5paxHr7XgXv3A5gzmsLFW1M9Y=; b=qd62hleZjttLIA+eeV2DO+D0nupaByQlCp8XEXapxSFll0lwMWBzCa5T8WLqJrKJnF +9Fwh+9k052viGJ0PBy/vQ/7AsV7x/bR+LA+Sxn7n1lmAAOv+D/EbhQG4L03omuXB/xO 3ySXVKzNTm8HC6iiA77phYPzMDtoUfQs61kAs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type; b=eDmrMtGbLTumLDWjxEgfP+GtW3KiiZi+lKHqpsfinASloRXO8p9GxpNCjq5tmoO7Ak 6flVZyjPWYVSEXGQYzQVxQNYwz4wXLG/aSD7B0+9bWSfA/2m7U/0HVq/8cFlI3xQeFfY ryzabrDK15CQm6nQfD25XhERFwR4nV9ZXkW8A= Received: by 10.214.12.6 with SMTP id 6mr520446qal.359.1228843661275; Tue, 09 Dec 2008 09:27:41 -0800 (PST) Received: by 10.214.150.15 with HTTP; Tue, 9 Dec 2008 09:27:41 -0800 (PST) Message-ID: <520894aa0812090927h4034e7ecnff5d05d2d6138554@mail.gmail.com> Date: Tue, 9 Dec 2008 15:27:41 -0200 From: "Fernan Aguero" To: freebsd-stable@freebsd.org, re@freebsd.org, doc@freebsd.org MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_52492_14039423.1228843661256" Cc: Subject: update release schedule 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: Tue, 09 Dec 2008 17:50:48 -0000 ------=_Part_52492_14039423.1228843661256 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Hi, the release schedule information available in http://www.freebsd.org/releases/7.1R/schedule.html is outdated. You probably already know about this ... and I also know 7.1-RELEASE is delayed, but the schedule page does not provide any useful information on what's going to happen next. BETA2 has already passed but it has not been mentioned in this document. The front page for the project (www.freebsd.org) links to ftp://ftp.freebsd.org/pub/FreeBSD/releases/amd64/ISO-IMAGES/7.1/ with the text 'Upcoming Release 7.1 - BETA2' (but BETA2 is not mentioned in schedule.html) If you navigate to the FTP site using that link now, you'll find that the images for the RC1 are already available (Dec 7th). But the 'actual' dates for the RC1 builds are missing from schedule.html. I'm not familiar with the docproj procedures, but have tried to help by editing the release.ent and schedule.sgml files (patches attached), which looked as the obvious candidates to me. If someone can check them, complete the missing dates in schedule.sgml, and commit the changes, that would be great! Cheers, -- fernan ------=_Part_52492_14039423.1228843661256 Content-Type: text/x-patch; name=release.ent.diff Content-Transfer-Encoding: base64 X-Attachment-Id: f_foisjmg20 Content-Disposition: attachment; filename=release.ent.diff MzRjMzQKPCA8IUVOVElUWSBiZXRhcmVsLnZlcnMgJ0JFVEEyJz4KLS0tCj4gPCFFTlRJVFkgYmV0 YXJlbC52ZXJzICdSQzEnPgo= ------=_Part_52492_14039423.1228843661256 Content-Type: text/x-patch; name=schedule.sgml.diff Content-Transfer-Encoding: base64 X-Attachment-Id: f_foiskep52 Content-Disposition: attachment; filename=schedule.sgml.diff LS0tIHd3dy9lbi9yZWxlYXNlcy83LjFSL3NjaGVkdWxlLnNnbWwub3JpZwkyMDA4LTEyLTA5IDEz OjM0OjIyLjAwMDAwMDAwMCAtMDMwMAorKysgd3d3L2VuL3JlbGVhc2VzLzcuMVIvc2NoZWR1bGUu c2dtbAkyMDA4LTEyLTA5IDEzOjM4OjQ1LjAwMDAwMDAwMCAtMDMwMApAQCAtMTEwLDYgKzExMCwx MyBAQAogICAgICAgPHRkPkJlZ2luIEJFVEExIGJ1aWxkcy48L3RkPgogICAgIDwvdHI+CiAKKyAg ICA8dHI+CisgICAgICA8dGQ+PHR0PkJFVEEyPC90dD4gYnVpbGRzPC90ZD4KKyAgICAgIDx0ZD4t LTwvdGQ+CisgICAgICA8dGQ+LS08L3RkPgorICAgICAgPHRkPkJlZ2luIEJFVEEyIGJ1aWxkcy48 L3RkPgorICAgIDwvdHI+CisKIAogICAgIDx0cj4KICAgICAgIDx0ZD48dHQ+UkVMRU5HXzdfMTwv dHQ+IGJyYW5jaDwvdGQ+CkBAIC0xMjIsNyArMTI5LDcgQEAKICAgICA8dHI+CiAgICAgICA8dGQ+ PHR0PlJDMTwvdHQ+IGJ1aWxkczwvdGQ+CiAgICAgICA8dGQ+MTUmbmJzcDtTZXB0ZW1iZXImbmJz cDsyMDA4PC90ZD4KLSAgICAgIDx0ZD4tLTwvdGQ+CisgICAgICA8dGQ+NyZuYnNwO0RlY2VtYmVy Jm5ic3A7MjAwODwvdGQ+CiAgICAgICA8dGQ+QmVnaW4gUkMxIGJ1aWxkcy48L3RkPgogICAgIDwv dHI+CiAK ------=_Part_52492_14039423.1228843661256-- From owner-freebsd-doc@FreeBSD.ORG Tue Dec 9 17:57:57 2008 Return-Path: Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3598B1065676; Tue, 9 Dec 2008 17:57:57 +0000 (UTC) (envelope-from pgj@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 0ED6F8FC16; Tue, 9 Dec 2008 17:57:57 +0000 (UTC) (envelope-from pgj@FreeBSD.org) Received: from freefall.freebsd.org (pgj@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id mB9HvuVf053602; Tue, 9 Dec 2008 17:57:56 GMT (envelope-from pgj@freefall.freebsd.org) Received: (from pgj@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id mB9HvuMq053598; Tue, 9 Dec 2008 17:57:56 GMT (envelope-from pgj) Date: Tue, 9 Dec 2008 17:57:56 GMT Message-Id: <200812091757.mB9HvuMq053598@freefall.freebsd.org> To: pgj@FreeBSD.org, freebsd-doc@FreeBSD.org, pgj@FreeBSD.org From: pgj@FreeBSD.org Cc: Subject: Re: docs/129506: Addition to Additional Contributors. 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, 09 Dec 2008 17:57:57 -0000 Synopsis: Addition to Additional Contributors. Responsible-Changed-From-To: freebsd-doc->pgj Responsible-Changed-By: pgj Responsible-Changed-When: Tue Dec 9 17:57:36 UTC 2008 Responsible-Changed-Why: Take http://www.freebsd.org/cgi/query-pr.cgi?pr=129506 From owner-freebsd-doc@FreeBSD.ORG Wed Dec 10 09:01:36 2008 Return-Path: Delivered-To: doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 971C6106567C for ; Wed, 10 Dec 2008 09:01:36 +0000 (UTC) (envelope-from mimiwaengwan@yahoo.co.nz) Received: from irga2.truemail.co.th (irga2.truemail.co.th [203.144.173.202]) by mx1.freebsd.org (Postfix) with ESMTP id 62BF88FC30 for ; Wed, 10 Dec 2008 09:01:33 +0000 (UTC) (envelope-from mimiwaengwan@yahoo.co.nz) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Aq0EAJIRP0k6Clds/2dsb2JhbACCbwXABAiNMoMHgWM X-IronPort-AV: E=Sophos;i="4.33,746,1220202000"; d="gif'147?scan'147,208,217,147";a="43140244" Received: from ppp-58-10-87-108.revip2.asianet.co.th (HELO HOME-71152C7123) ([58.10.87.108]) by irp2.truemail.co.th with ESMTP; 10 Dec 2008 15:50:32 +0700 From: =?UTF-8?B?4Lib4Li44LmL4Lii4LiE4Li44LiT4Lig4Liy4Lie4Lii4Li04LmI4LiH4LmD?= =?UTF-8?B?4LiK4LmJ4Lii4Li04LmI4LiH4Lij4Lin4Lii?= To: doc@freebsd.org Content-Type: multipart/related; charset="UTF-8"; boundary="y4TGl=_LjxV66uFExXpOcRSUgmu4Na6vLv0" MIME-Version: 1.0 Date: Wed, 10 Dec 2008 15:50:27 +0700 Message-ID: <33443453125259@mail.truemail.co.th> X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: =?utf-8?b?4LiC4LmI4Liy4Lin4LiU4Li14Liq4Liz4Lir4Lij4Lix4Lia4LmA?= =?utf-8?b?4LiB4Lip4LiV4Lij4LiB4Lij?= X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: mimiwaengwan@yahoo.co.nz List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Dec 2008 09:01:36 -0000 This is a multi-part message in MIME format --y4TGl=_LjxV66uFExXpOcRSUgmu4Na6vLv0 Content-Type: text/plain ; charset="UTF-8" Content-Transfer-Encoding: quoted-printable =E0=B8=97=E0=B8=B3=E0=B9=84=E0=B8=A1=E0=B8=95=E0=B9=89=E0=B8=AD=E0=B8=87= =E0=B9=83=E0=B8=8A=E0=B9=89=E0=B8=9B=E0=B8=B8=E0=B9=8B=E0=B8=A2=E0=B8=A7= =E0=B8=B4=E0=B8=99=E0=B9=82=E0=B8=81=E0=B8=A5=E0=B8=94=E0=B9=8C? =E0=B9= =80=E0=B8=9E=E0=B8=A3=E0=B8=B2=E0=B8=B0=E0=B9=80=E0=B8=9B=E0=B9=87=E0=B8= =99=E0=B8=97=E0=B8=B2=E0=B8=87=E0=B9=80=E0=B8=A5=E0=B8=B7=E0=B8=AD=E0=B8= =81=E0=B9=83=E0=B8=AB=E0=B8=A1=E0=B9=88=E0=B8=82=E0=B8=AD=E0=B8=87=E0=B9= =80=E0=B8=81=E0=B8=A9=E0=B8=95=E0=B8=A3=E0=B8=81=E0=B8=A3=E0=B8=97=E0=B8= =B5=E0=B9=88=E0=B8=94=E0=B8=B5=E0=B8=97=E0=B8=B5=E0=B9=88=E0=B8=AA=E0=B8= =B8=E0=B8=94 =20 =20 1. =E0=B8=9B=E0=B8=B8=E0=B9=8B=E0=B8=A2=E0=B8=A7=E0=B8=B4=E0=B8=99=E0=B9= =82=E0=B8=81=E0=B8=A5=E0=B8=94=E0=B9=8C =E0=B8=84=E0=B8=B7=E0=B8=AD =E0= =B8=9B=E0=B8=B8=E0=B9=8B=E0=B8=A2=E0=B8=AD=E0=B8=B4=E0=B8=99=E0=B8=97=E0= =B8=A3=E0=B8=B5=E0=B8=A2=E0=B9=8C=E0=B8=84=E0=B8=B8=E0=B8=93=E0=B8=A0=E0= =B8=B2=E0=B8=9E =20 =E0=B8=9C=E0=B8=A5=E0=B8=B4=E0=B8=95=E0=B8=88=E0=B8=B2=E0=B8=81=E0=B8=AA= =E0=B8=B2=E0=B8=A3=E0=B9=80=E0=B8=9E=E0=B8=B4=E0=B9=88=E0=B8=A1=E0=B8=9C= =E0=B8=A5=E0=B8=9C=E0=B8=A5=E0=B8=B4=E0=B8=95=E0=B8=8B=E0=B8=B4=E0=B8=A5= =E0=B8=B4=E0=B8=84=E0=B8=AD=E0=B8=99 20% =E0=B8=9C=E0=B8=AA=E0=B8=A1=E0=B8=9B=E0=B8=B8=E0=B9=8B=E0=B8=A2=E0= =B8=AD=E0=B8=B4=E0=B8=99=E0=B8=97=E0=B8=A3=E0=B8=B5=E0=B8=A2=E0=B9=8C=E0= =B8=97=E0=B8=B5=E0=B9=88=E0=B8=9C=E0=B8=A5=E0=B8=B4=E0=B8=95=E0=B8=82=E0= =B8=B6=E0=B9=89=E0=B8=99=E0=B8=A1=E0=B8=B2=E0=B8=88=E0=B8=B2=E0=B8=81=E0= =B8=81=E0=B8=B2=E0=B8=A3=E0=B8=99=E0=B8=B3=E0=B8=AA=E0=B8=B2=E0=B8=A3=E0= =B8=AD=E0=B8=B4=E0=B8=99=E0=B8=97=E0=B8=A3=E0=B8=B5=E0=B8=A2=E0=B9=8C=20= =20 =E0=B9=81=E0=B8=A5=E0=B8=B0=E0=B9=80=E0=B8=8A=E0=B8=B7=E0=B9=89=E0=B8=AD= =E0=B8=88=E0=B8=B8=E0=B8=A5=E0=B8=B4=E0=B8=99=E0=B8=97=E0=B8=A3=E0=B8=B5= =E0=B8=A2=E0=B9=8C=E0=B9=80=E0=B8=9B=E0=B9=87=E0=B8=99=E0=B8=9B=E0=B8=A3= =E0=B8=B0=E0=B9=82=E0=B8=A2=E0=B8=8A=E0=B8=99=E0=B9=8C=E0=B8=95=E0=B9=88= =E0=B8=AD=E0=B8=9E=E0=B8=B7=E0=B8=8A=E0=B8=A1=E0=B8=B2=E0=B8=AB=E0=B8=A1= =E0=B8=B1=E0=B8=81=E0=B8=A3=E0=B8=A7=E0=B8=A1=E0=B8=81=E0=B8=B1=E0=B8=99= =E0=B8=88=E0=B8=99=E0=B9=80=E0=B8=81=E0=B8=B4=E0=B8=94=E0=B8=81=E0=B8=B2= =E0=B8=A3=E0=B8=A2=E0=B9=88=E0=B8=AD=E0=B8=A2=E0=B8=AA=E0=B8=A5=E0=B8=B2= =E0=B8=A2=E0=B8=97=E0=B8=B5=E0=B9=88=E0=B8=97=E0=B8=B3=E0=B9=83=E0=B8=AB= =E0=B9=89=E0=B9=80=E0=B8=81=E0=B8=B4=E0=B8=94=E0=B8=81=E0=B8=A3=E0=B8=94= =E0=B8=AE=E0=B8=B4=E0=B8=A7=E0=B8=A1=E0=B8=B4=E0=B8=84 (Humic Acid) =E0= =B9=80=E0=B8=A1=E0=B8=B7=E0=B9=88=E0=B8=AD=E0=B8=A3=E0=B8=A7=E0=B8=A1=E0= =B8=81=E0=B8=B1=E0=B8=9A=E0=B8=8B=E0=B8=B2=E0=B8=81=E0=B8=9E=E0=B8=B7=E0= =B8=8A =E0=B9=80=E0=B8=8A=E0=B9=88=E0=B8=99 =E0=B8=96=E0=B8=B1=E0=B9=88= =E0=B8=A7=E0=B9=80=E0=B8=AB=E0=B8=A5=E0=B8=B7=E0=B8=AD=E0=B8=87 =E0=B8= =AF=E0=B8=A5=E0=B8=AF =E0=B9=81=E0=B8=A5=E0=B8=B0=E0=B8=A1=E0=B8=B9=E0= =B8=A5=E0=B8=AA=E0=B8=B1=E0=B8=95=E0=B8=A7=E0=B9=8C=E0=B8=AB=E0=B8=A1=E0= =B8=B1=E0=B8=81 =E0=B9=80=E0=B8=8A=E0=B9=88=E0=B8=99 =E0=B8=A1=E0=B8=B9= =E0=B8=A5=E0=B8=84=E0=B9=89=E0=B8=B2=E0=B8=87=E0=B8=84=E0=B8=B2=E0=B8=A7= =E0=B8=AB=E0=B8=A1=E0=B8=B1=E0=B8=81 (Guanophosphate) =E0=B8=88=E0=B8=B0= =E0=B9=84=E0=B8=9B=E0=B8=AA=E0=B8=81=E0=B8=B1=E0=B8=94=E0=B8=98=E0=B8=B2= =E0=B8=95=E0=B8=B8=E0=B8=AD=E0=B8=B2=E0=B8=AB=E0=B8=B2=E0=B8=A3=E0=B8=97= =E0=B8=B5=E0=B9=88=E0=B9=80=E0=B8=9B=E0=B9=87=E0=B8=99=E0=B8=9B=E0=B8=A3= =E0=B8=B0=E0=B9=82=E0=B8=A2=E0=B8=8A=E0=B8=99=E0=B9=8C=E0=B8=95=E0=B9=88= =E0=B8=AD=E0=B8=9E=E0=B8=B7=E0=B8=8A=E0=B9=83=E0=B8=AB=E0=B9=89=E0=B9=80= =E0=B8=9E=E0=B8=B4=E0=B9=88=E0=B8=A1=E0=B8=A1=E0=B8=B2=E0=B8=81=E0=B8=A2= =E0=B8=B4=E0=B9=88=E0=B8=87=E0=B8=82=E0=B8=B6=E0=B9=89=E0=B8=99 =E0=B8= =97=E0=B8=B3=E0=B9=83=E0=B8=AB=E0=B9=89=E0=B8=9E=E0=B8=B7=E0=B8=8A=E0=B8= =AA=E0=B8=B2=E0=B8=A1=E0=B8=B2=E0=B8=A3=E0=B8=96=E0=B8=99=E0=B8=B3=E0=B9= =84=E0=B8=9B=E0=B9=83=E0=B8=8A=E0=B9=89=E0=B9=84=E0=B8=94=E0=B9=89=E0=B8= =97=E0=B8=B1=E0=B8=99=E0=B8=97=E0=B8=B5=E0=B9=81=E0=B8=A5=E0=B8=B0=E0=B8= =AD=E0=B8=A2=E0=B8=B9=E0=B9=88=E0=B9=84=E0=B8=94=E0=B9=89=E0=B8=99=E0=B8= =B2=E0=B8=99=E0=B8=96=E0=B8=B6=E0=B8=87 6 =E0=B9=80=E0=B8=94=E0=B8=B7=E0= =B8=AD=E0=B8=99 =E0=B8=AD=E0=B8=B5=E0=B8=81=E0=B8=97=E0=B8=B1=E0=B9=89= =E0=B8=87=E0=B8=A2=E0=B8=B1=E0=B8=87=E0=B8=AA=E0=B8=B2=E0=B8=A1=E0=B8=B2= =E0=B8=A3=E0=B8=96=E0=B8=9B=E0=B9=89=E0=B8=AD=E0=B8=87=E0=B8=81=E0=B8=B1= =E0=B8=99=E0=B9=82=E0=B8=A3=E0=B8=84=E0=B8=9E=E0=B8=B7=E0=B8=8A=E0=B9=81= =E0=B8=A5=E0=B8=B0=E0=B9=81=E0=B8=A1=E0=B8=A5=E0=B8=87=E0=B9=84=E0=B8=94= =E0=B9=89=E0=B8=AD=E0=B8=A2=E0=B9=88=E0=B8=B2=E0=B8=87=E0=B8=A1=E0=B8=B5= =E0=B8=9B=E0=B8=A3=E0=B8=B0=E0=B8=AA=E0=B8=B4=E0=B8=97=E0=B8=98=E0=B8=B4= =E0=B8=A0=E0=B8=B2=E0=B8=9E =E0=B8=97=E0=B8=B3=E0=B9=83=E0=B8=AB=E0=B9= =89=E0=B8=9C=E0=B8=A5=E0=B8=9C=E0=B8=A5=E0=B8=B4=E0=B8=95=E0=B9=80=E0=B8= =9E=E0=B8=B4=E0=B9=88=E0=B8=A1=E0=B8=82=E0=B8=B6=E0=B9=89=E0=B8=99=E0=B8= =96=E0=B8=B6=E0=B8=87 1 =E0=B9=80=E0=B8=97=E0=B9=88=E0=B8=B2=E0=B8=95=E0= =B8=B1=E0=B8=A7=20 =20 =20 =E0=B8=AA=E0=B9=88=E0=B8=A7=E0=B8=99=E0=B8=9B=E0=B8=A3=E0=B8=B0=E0=B8=81= =E0=B8=AD=E0=B8=9A : =E0=B8=8B=E0=B8=B2=E0=B8=81=E0=B8=9E=E0=B8=B7=E0=B8= =8A=E0=B8=AB=E0=B8=A1=E0=B8=B1=E0=B8=81 60% =E0=B8=A1=E0=B8=B9=E0=B8=A5= =E0=B8=AA=E0=B8=B1=E0=B8=95=E0=B8=A7=E0=B9=8C=E0=B8=AB=E0=B8=A1=E0=B8=B1= =E0=B8=81 20% =E0=B9=81=E0=B8=A3=E0=B9=88=E0=B8=8B=E0=B8=B4=E0=B8=A5=E0= =B8=B4=E0=B8=84=E0=B8=AD=E0=B8=99 20% =E0=B8=9B=E0=B8=A3=E0=B8=B0=E0=B8=AA=E0=B8=B4=E0=B8=97=E0=B8=98=E0=B8=B4= =E0=B8=A0=E0=B8=B2=E0=B8=9E : =E0=B8=AB=E0=B8=A5=E0=B8=B1=E0=B8=87=E0=B8= =81=E0=B8=B2=E0=B8=A3=E0=B9=83=E0=B8=8A=E0=B9=89=E0=B8=97=E0=B8=B3=E0=B9= =83=E0=B8=AB=E0=B9=89=E0=B8=84=E0=B8=B7=E0=B8=99=E0=B8=84=E0=B8=A7=E0=B8= =B2=E0=B8=A1=E0=B8=AA=E0=B8=A1=E0=B8=9A=E0=B8=B9=E0=B8=A3=E0=B8=93=E0=B9= =8C=E0=B8=AA=E0=B8=B9=E0=B9=88=E0=B9=81=E0=B8=9C=E0=B9=88=E0=B8=99=E0=B8= =94=E0=B8=B4=E0=B8=99 =E0=B8=88=E0=B8=B2=E0=B8=81=E0=B8=9C=E0=B8=A5=E0= =B8=A7=E0=B8=B4=E0=B9=80=E0=B8=84=E0=B8=A3=E0=B8=B2=E0=B8=B0=E0=B8=AB=E0= =B9=8C=E0=B8=97=E0=B8=B3=E0=B9=83=E0=B8=AB=E0=B9=89=E0=B9=80=E0=B8=9E=E0= =B8=B4=E0=B9=88=E0=B8=A1=E0=B8=98=E0=B8=B2=E0=B8=95=E0=B8=B8 =E0=B8=AD= =E0=B8=B2=E0=B8=AB=E0=B8=B2=E0=B8=A3 =E0=B8=AD=E0=B8=B4=E0=B8=99=E0=B8= =97=E0=B8=A3=E0=B8=B5=E0=B8=A2=E0=B9=8C=E0=B8=A7=E0=B8=B1=E0=B8=95=E0=B8= =96=E0=B8=B8=E0=B9=81=E0=B8=A5=E0=B8=B0=E0=B8=88=E0=B8=B8=E0=B8=A5=E0=B8= =B4=E0=B8=99=E0=B8=97=E0=B8=A3=E0=B8=B5=E0=B8=A2=E0=B9=8C=E0=B9=83=E0=B8= =99=E0=B8=94=E0=B8=B4=E0=B8=99 =E0=B8=97=E0=B8=B3=E0=B9=83=E0=B8=AB=E0= =B9=89=E0=B8=94=E0=B8=B4=E0=B8=99=E0=B8=A3=E0=B9=88=E0=B8=A7=E0=B8=99=E0= =B8=8B=E0=B8=B8=E0=B8=A2 =E0=B8=AD=E0=B8=B8=E0=B9=89=E0=B8=A1=E0=B8=98= =E0=B8=B2=E0=B8=95=E0=B8=B8=E0=B8=AD=E0=B8=B2=E0=B8=AB=E0=B8=B2=E0=B8=A3= =E0=B9=84=E0=B8=94=E0=B9=89=E0=B8=94=E0=B8=B5 =E0=B8=8A=E0=B9=88=E0=B8= =A7=E0=B8=A2=E0=B9=83=E0=B8=AB=E0=B9=89=E0=B8=9E=E0=B8=B7=E0=B8=8A=E0=B9= =81=E0=B8=82=E0=B9=87=E0=B8=87=E0=B9=81=E0=B8=A3=E0=B8=87 =E0=B8=9C=E0= =B8=A5=E0=B8=AA=E0=B8=A1=E0=B8=9A=E0=B8=B9=E0=B8=A3=E0=B8=93=E0=B9=8C = =E0=B8=84=E0=B8=87=E0=B8=84=E0=B8=A7=E0=B8=B2=E0=B8=A1=E0=B8=AA=E0=B8=94= =E0=B9=84=E0=B8=A7=E0=B9=89=E0=B9=84=E0=B8=94=E0=B9=89=E0=B8=99=E0=B8=B2= =E0=B8=99 =E0=B8=9C=E0=B8=A5=E0=B8=9C=E0=B8=A5=E0=B8=B4=E0=B8=95=E0=B8= =AA=E0=B8=B9=E0=B8=87 =E0=B8=84=E0=B8=B8=E0=B8=93=E0=B8=A0=E0=B8=B2=E0= =B8=9E=E0=B8=94=E0=B8=B5 =E0=B8=81=E0=B8=B3=E0=B9=84=E0=B8=A3=E0=B8=87= =E0=B8=B2=E0=B8=A1 =E0=B9=80=E0=B8=9B=E0=B9=87=E0=B8=99=E0=B8=97=E0=B8= =B5=E0=B9=88=E0=B8=95=E0=B9=89=E0=B8=AD=E0=B8=87=E0=B8=81=E0=B8=B2=E0=B8= =A3=E0=B8=82=E0=B8=AD=E0=B8=87=E0=B8=95=E0=B8=A5=E0=B8=B2=E0=B8=94=E0=B9= =82=E0=B8=A5=E0=B8=81 =20 =E0=B8=84=E0=B8=B8=E0=B8=93=E0=B8=AA=E0=B8=A1=E0=B8=9A=E0=B8=B1=E0=B8= =95=E0=B8=B4=E0=B9=80=E0=B8=94=E0=B9=88=E0=B8=99=E0=B8=82=E0=B8=AD=E0=B8= =87=E0=B8=9B=E0=B8=B8=E0=B9=8B=E0=B8=A2=E0=B8=A7=E0=B8=B4=E0=B8=99=E0=B9= =82=E0=B8=81=E0=B8=A5=E0=B8=94=E0=B9=8C 1. =E0=B8=A1=E0=B8=B5=E0=B8=98=E0=B8=B2=E0=B8=95=E0=B8=B8=E0=B8=AD=E0=B8= =B2=E0=B8=AB=E0=B8=B2=E0=B8=A3=E0=B8=84=E0=B8=A3=E0=B8=9A=E0=B8=96=E0=B9= =89=E0=B8=A7=E0=B8=99=E0=B8=AA=E0=B8=B3=E0=B8=AB=E0=B8=A3=E0=B8=B1=E0=B8= =9A=E0=B8=9E=E0=B8=B7=E0=B8=8A (=E0=B8=AD=E0=B8=B2=E0=B8=AB=E0=B8=B2=E0= =B8=A3=E0=B8=AB=E0=B8=A5=E0=B8=B1=E0=B8=81 - =E0=B8=AD=E0=B8=B2=E0=B8=AB= =E0=B8=B2=E0=B8=A3=E0=B8=A3=E0=B8=AD=E0=B8=87 - =E0=B8=AD=E0=B8=B2=E0=B8= =AB=E0=B8=B2=E0=B8=A3=E0=B9=80=E0=B8=AA=E0=B8=A3=E0=B8=B4=E0=B8=A1) 2. =E0=B8=A1=E0=B8=B5=E0=B8=AD=E0=B8=B4=E0=B8=99=E0=B8=97=E0=B8=A3=E0=B8= =B5=E0=B8=A2=E0=B9=8C=E0=B8=A7=E0=B8=B1=E0=B8=95=E0=B8=96=E0=B8=B8 (Or= ganicmetter) =E0=B8=95=E0=B8=B2=E0=B8=A1=E0=B8=A1=E0=B8=B2=E0=B8=95=E0= =B8=A3=E0=B8=90=E0=B8=B2=E0=B8=99=E0=B8=9B=E0=B8=B8=E0=B9=8B=E0=B8=A2=E0= =B8=AD=E0=B8=B4=E0=B8=99=E0=B8=97=E0=B8=A3=E0=B8=B5=E0=B8=A2=E0=B9=8C = =E0=B8=A1=E0=B8=B5=E0=B8=AB=E0=B8=99=E0=B9=89=E0=B8=B2=E0=B8=97=E0=B8=B5= =E0=B9=88=E0=B8=AA=E0=B8=B3=E0=B8=84=E0=B8=B1=E0=B8=8D =E0=B8=84=E0=B8= =B7=E0=B8=AD =E0=B8=8A=E0=B9=88=E0=B8=A7=E0=B8=A2=E0=B8=9B=E0=B8=A3=E0= =B8=B1=E0=B8=9A=E0=B9=82=E0=B8=84=E0=B8=A3=E0=B8=87=E0=B8=AA=E0=B8=A3=E0= =B9=89=E0=B8=B2=E0=B8=87=E0=B9=83=E0=B8=AB=E0=B9=89=E0=B8=94=E0=B8=B4=E0= =B8=99=E0=B8=9B=E0=B8=A5=E0=B8=94=E0=B8=9B=E0=B8=A5=E0=B9=88=E0=B8=AD=E0= =B8=A2=E0=B8=98=E0=B8=B2=E0=B8=95=E0=B8=B8=E0=B8=AD=E0=B8=B2=E0=B8=AB=E0= =B8=B2=E0=B8=A3=E0=B9=84=E0=B8=94=E0=B9=89=E0=B8=A1=E0=B8=B2=E0=B8=81=E0= =B8=82=E0=B8=B6=E0=B9=89=E0=B8=99 3. =E0=B8=A1=E0=B8=B5=E0=B8=AE=E0=B8=AD=E0=B8=A3=E0=B9=8C=E0=B9=82=E0=B8= =A1=E0=B8=99 (Humic Acid) =E0=B8=8A=E0=B9=88=E0=B8=A7=E0=B8=A2=E0=B8=81= =E0=B8=A3=E0=B8=B0=E0=B8=95=E0=B8=B8=E0=B9=89=E0=B8=99=E0=B8=81=E0=B8=B2= =E0=B8=A3=E0=B9=81=E0=B8=95=E0=B8=81=E0=B8=95=E0=B8=B1=E0=B8=A7=E0=B9=83= =E0=B8=99=E0=B8=97=E0=B8=B8=E0=B8=81=E0=B8=A3=E0=B8=B0=E0=B8=A2=E0=B8=B0= =E0=B8=82=E0=B8=AD=E0=B8=87=E0=B8=9E=E0=B8=B7=E0=B8=8A =E0=B8=A7=E0=B8=B4=E0=B8=98=E0=B8=B5=E0=B9=83=E0=B8=8A=E0=B9=89 - =E0=B8=AA=E0=B8=B2=E0=B8=A1=E0=B8=B2=E0=B8=A3=E0=B8=96=E0=B9=83=E0=B8= =8A=E0=B9=89=E0=B9=84=E0=B8=94=E0=B9=89=E0=B8=81=E0=B8=B1=E0=B8=9A=E0=B8= =9E=E0=B8=B7=E0=B8=8A=E0=B8=97=E0=B8=B8=E0=B8=81=E0=B8=8A=E0=B8=99=E0=B8= =B4=E0=B8=94 =E0=B8=94=E0=B8=B4=E0=B8=99=E0=B8=97=E0=B8=B8=E0=B8=81=E0= =B8=9B=E0=B8=A3=E0=B8=B0=E0=B9=80=E0=B8=A0=E0=B8=97 (=E0=B8=94=E0=B8=B9= =E0=B8=A7=E0=B8=B4=E0=B8=98=E0=B8=B5=E0=B8=81=E0=B8=B2=E0=B8=A3=E0=B9=83= =E0=B8=8A=E0=B9=89=E0=B8=94=E0=B9=89=E0=B8=B2=E0=B8=99=E0=B8=AB=E0=B8=A5= =E0=B8=B1=E0=B8=87=E0=B8=81=E0=B8=A3=E0=B8=B0=E0=B8=AA=E0=B8=AD=E0=B8=9A= ) - =E0=B8=81=E0=B8=A3=E0=B8=93=E0=B8=B5=E0=B8=95=E0=B9=89=E0=B8=AD=E0=B8= =87=E0=B8=81=E0=B8=B2=E0=B8=A3=E0=B9=80=E0=B8=A3=E0=B9=88=E0=B8=87=E0=B8= =81=E0=B8=B2=E0=B8=A3=E0=B9=80=E0=B8=88=E0=B8=A3=E0=B8=B4=E0=B8=8D=E0=B9= =80=E0=B8=95=E0=B8=B4=E0=B8=9A=E0=B9=82=E0=B8=95=E0=B8=82=E0=B8=AD=E0=B8= =87=E0=B8=9E=E0=B8=B7=E0=B8=8A =E0=B9=83=E0=B8=AB=E0=B9=89=E0=B9=83=E0= =B8=8A=E0=B9=89=E0=B8=A3=E0=B9=88=E0=B8=A7=E0=B8=A1=E0=B8=81=E0=B8=B1=E0= =B8=9A=E0=B8=9B=E0=B8=B8=E0=B9=8B=E0=B8=A2=E0=B9=80=E0=B8=84=E0=B8=A1=E0= =B8=B5=E0=B9=84=E0=B8=94=E0=B9=89=E0=B8=95=E0=B8=B2=E0=B8=A1=E0=B8=AA=E0= =B8=A0=E0=B8=B2=E0=B8=9E=E0=B8=82=E0=B8=AD=E0=B8=87=E0=B8=94=E0=B8=B4=E0= =B8=99 (=E0=B8=AB=E0=B8=A3=E0=B8=B7=E0=B8=AD=E0=B8=9B=E0=B8=B8=E0=B9=8B= =E0=B8=A2=E0=B8=A7=E0=B8=B4=E0=B8=99=E0=B9=82=E0=B8=81=E0=B8=A5=E0=B8=94= =E0=B9=8C 3 =E0=B8=AA=E0=B9=88=E0=B8=A7=E0=B8=99=20 =E0=B8=95=E0=B9=88=E0=B8=AD =E0=B8=9B=E0=B8=B8=E0=B9=8B=E0=B8=A2=E0= =B9=80=E0=B8=84=E0=B8=A1=E0=B8=B5 1 =E0=B8=AA=E0=B9=88=E0=B8=A7=E0=B8=99= =E0=B9=83=E0=B8=99=E0=B8=8A=E0=B9=88=E0=B8=A7=E0=B8=87=E0=B8=9B=E0=B8= =B5=E0=B9=81=E0=B8=A3=E0=B8=81) =20 =20 =20 2. =E0=B8=9B=E0=B8=B8=E0=B9=8B=E0=B8=A2=E0=B8=A7=E0=B8=B4=E0=B8=99=E0=B9= =82=E0=B8=81=E0=B8=A5=E0=B8=94=E0=B9=8C=E0=B8=9C=E0=B8=AA=E0=B8=A1=E0=B8= =AA=E0=B8=B2=E0=B8=A3=E0=B9=80=E0=B8=9E=E0=B8=B4=E0=B9=88=E0=B8=A1=E0=B8= =9C=E0=B8=A5=E0=B8=9C=E0=B8=A5=E0=B8=B4=E0=B8=95=E0=B9=81=E0=B8=A3=E0=B9= =88=E0=B8=8B=E0=B8=B4=E0=B8=A5=E0=B8=B4=E0=B8=84=E0=B8=AD=E0=B8=99 =20 =E0=B8=88=E0=B8=B2=E0=B8=81=E0=B8=81=E0=B8=B2=E0=B8=A3=E0=B8=A7=E0=B8=B4= =E0=B8=88=E0=B8=B1=E0=B8=A2=E0=B8=82=E0=B8=AD=E0=B8=87=E0=B8=99=E0=B8=B1= =E0=B8=81=E0=B8=A7=E0=B8=B4=E0=B8=88=E0=B8=B1=E0=B8=A2=E0=B8=97=E0=B8=B2= =E0=B8=87=E0=B8=81=E0=B8=B2=E0=B8=A3=E0=B9=80=E0=B8=81=E0=B8=A9=E0=B8=95= =E0=B8=A3=E0=B9=81=E0=B8=9C=E0=B8=99=E0=B9=83=E0=B8=AB=E0=B8=A1=E0=B9=88= =E0=B8=9E=E0=B8=9A=E0=B8=A7=E0=B9=88=E0=B8=B2=E0=B8=98=E0=B8=B2=E0=B8= =95=E0=B8=B8=E0=B8=AD=E0=B8=B2=E0=B8=AB=E0=B8=B2=E0=B8=A3=E0=B8=AA=E0=B8= =B3=E0=B8=AB=E0=B8=A3=E0=B8=B1=E0=B8=9A=E0=B8=9E=E0=B8=B7=E0=B8=8A =E0= =B8=99=E0=B8=AD=E0=B8=81=E0=B8=88=E0=B8=B2=E0=B8=81 N,P,K =E0=B9=81=E0= =B8=A5=E0=B9=89=E0=B8=A7=E0=B9=81=E0=B8=A3=E0=B9=88=E0=B8=98=E0=B8=B2=E0= =B8=95=E0=B8=B8 =E0=B8=AD=E0=B8=B2=E0=B8=AB=E0=B8=B2=E0=B8=A3=E0=B9=80=E0=B8=AA=E0=B8=A3= =E0=B8=B4=E0=B8=A1=E0=B8=AD=E0=B8=B7=E0=B9=88=E0=B8=99=E0=B9=86 =E0=B9= =80=E0=B8=8A=E0=B9=88=E0=B8=99 =E0=B9=81=E0=B8=A3=E0=B9=88=E0=B8=8B=E0= =B8=B4=E0=B8=A5=E0=B8=B4=E0=B8=84=E0=B8=AD=E0=B8=99=20 =E0=B9=80=E0=B8=A1=E0=B8=B7=E0=B9=88=E0=B8=AD=E0=B8=96=E0=B8=B9=E0=B8=81= =E0=B8=99=E0=B9=89=E0=B8=B3=E0=B9=81=E0=B8=A5=E0=B9=89=E0=B8=A7=E0=B8=88= =E0=B8=B0=E0=B9=81=E0=B8=95=E0=B8=81=E0=B8=95=E0=B8=B1=E0=B8=A7=E0=B9=80= =E0=B8=9B=E0=B9=87=E0=B8=99 2H2O+SI+2O =E0=B8=8B=E0=B8=B6=E0=B9=88=E0=B8= =87=E0=B8=AA=E0=B8=B2=E0=B8=A1=E0=B8=B2=E0=B8=A3=E0=B8=96=E0=B9=83=E0=B8= =AB=E0=B9=89=E0=B8=98=E0=B8=B2=E0=B8=95=E0=B8=B8 =E0=B8=8B=E0=B8=B4=E0=B8=A5=E0=B8=B4=E0=B8=84=E0=B8=AD=E0=B8=99=E0=B9=81= =E0=B8=81=E0=B9=88=E0=B8=9E=E0=B8=B7=E0=B8=8A=E0=B9=84=E0=B8=94=E0=B9=89= =E0=B8=AA=E0=B8=B9=E0=B8=87=E0=B8=81=E0=B8=A7=E0=B9=88=E0=B8=B2 5,667 = p.p.m =E0=B8=9E=E0=B8=B7=E0=B8=8A=E0=B8=AA=E0=B8=B2=E0=B8=A1=E0=B8=B2=E0= =B8=A3=E0=B8=96=E0=B8=99=E0=B8=B3=E0=B9=84=E0=B8=9B=E0=B9=83=E0=B8=8A=E0= =B9=89=E0=B9=84=E0=B8=94=E0=B9=89=E0=B8=97=E0=B8=B1=E0=B8=99=E0=B8=97=E0= =B8=B5 =E0=B9=80=E0=B8=9E=E0=B8=A3=E0=B8=B2=E0=B8=B0=E0=B9=80=E0=B8=9B= =E0=B9=87=E0=B8=99=E0=B8=AA=E0=B8=B2=E0=B8=A3=E0=B8=AA=E0=B8=81=E0=B8=B1= =E0=B8=94=E0=B8=88=E0=B8=B2=E0=B8=81=E0=B8=A5=E0=B8=B2=E0=B8=A7=E0=B8=B2= =E0=B8=A0=E0=B8=B9=E0=B9=80=E0=B8=82=E0=B8=B2=E0=B9=84=E0=B8=9F=E0=B8=97= =E0=B8=B5=E0=B9=88=E0=B8=96=E0=B8=B9=E0=B8=81=E0=B9=81=E0=B8=8A=E0=B9=88= =E0=B9=83=E0=B8=99=E0=B8=99=E0=B9=89=E0=B8=B3=E0=B8=A1=E0=B8=B2=E0=B8=99= =E0=B8=B2=E0=B8=99=E0=B8=81=E0=B8=A7=E0=B9=88=E0=B8=B2 200 =E0=B8=9B=E0= =B8=B5 =E0=B8=8B=E0=B8=B6=E0=B9=88=E0=B8=87=E0=B8=99=E0=B8=B3=E0=B8=A1= =E0=B8=B2=E0=B8=9C=E0=B8=AA=E0=B8=A1=E0=B9=83=E0=B8=99=E0=B8=9B=E0=B8=B8= =E0=B9=8B=E0=B8=A2=E0=B8=A7=E0=B8=B4=E0=B8=99=E0=B9=82=E0=B8=81=E0=B8=A5= =E0=B8=94=E0=B9=8C =E0=B8=97=E0=B8=B3=E0=B9=83=E0=B8=AB=E0=B9=89=E0=B8= =A1=E0=B8=B5=E0=B8=98=E0=B8=B2=E0=B8=95=E0=B8=B8=E0=B8=AD=E0=B8=B2=E0=B8= =AB=E0=B8=B2=E0=B8=A3=E0=B9=80=E0=B8=AA=E0=B8=A3=E0=B8=B4=E0=B8=A1=E0=B8= =97=E0=B8=B5=E0=B9=88=E0=B8=88=E0=B8=B3=E0=B9=80=E0=B8=9B=E0=B9=87=E0=B8= =99=E0=B9=81=E0=B8=81=E0=B9=88=E0=B8=9E=E0=B8=B7=E0=B8=8A=E0=B8=81=E0=B8= =A7=E0=B9=88=E0=B8=B2 50 =E0=B8=8A=E0=B8=99=E0=B8=B4=E0=B8=94=E0=B8=97= =E0=B8=B5=E0=B9=88=E0=B9=81=E0=B8=95=E0=B8=81=E0=B8=95=E0=B9=88=E0=B8=B2= =E0=B8=87=E0=B8=88=E0=B8=B2=E0=B8=81=E0=B8=9B=E0=B8=B8=E0=B9=8B=E0=B8=A2= =E0=B8=97=E0=B8=B1=E0=B9=88=E0=B8=A7=E0=B9=84=E0=B8=9B =E0=B8=97=E0=B8= =B5=E0=B9=88=E0=B8=AA=E0=B8=B3=E0=B8=84=E0=B8=B1=E0=B8=8D=E0=B8=AD=E0=B8= =A2=E0=B9=88=E0=B8=B2=E0=B8=87=E0=B8=A2=E0=B8=B4=E0=B9=88=E0=B8=87=E0=B9= =83=E0=B8=99=E0=B8=A0=E0=B8=B2=E0=B8=84=E0=B8=81=E0=B8=B2=E0=B8=A3=E0=B9= =80=E0=B8=81=E0=B8=A9=E0=B8=95=E0=B8=A3 =E0=B8=8A=E0=B9=88=E0=B8=A7=E0= =B8=A2=E0=B8=9B=E0=B8=A3=E0=B8=B1=E0=B8=9A=E0=B8=AA=E0=B8=A0=E0=B8=B2=E0= =B8=9E=E0=B8=94=E0=B8=B4=E0=B8=99 =E0=B8=9B=E0=B8=A3=E0=B8=B1=E0=B8=9A= =E0=B8=84=E0=B9=88=E0=B8=B2=E0=B8=84=E0=B8=A7=E0=B8=B2=E0=B8=A1=E0=B9=80= =E0=B8=9B=E0=B9=87=E0=B8=99=E0=B8=81=E0=B8=A3=E0=B8=94/=E0=B8=94=E0=B9= =88=E0=B8=B2=E0=B8=87=E0=B8=82=E0=B8=AD=E0=B8=87=E0=B8=94=E0=B8=B4=E0=B8= =99=E0=B9=83=E0=B8=AB=E0=B9=89=E0=B9=80=E0=B8=AB=E0=B8=A1=E0=B8=B2=E0=B8= =B0=E0=B8=AA=E0=B8=A1=E0=B8=AB=E0=B8=B2=E0=B8=81=E0=B8=9E=E0=B8=B7=E0=B9= =89=E0=B8=99=E0=B8=97=E0=B8=B5=E0=B9=88=E0=B9=83=E0=B8=94=E0=B8=82=E0=B8= =B2=E0=B8=94=E0=B8=98=E0=B8=B2=E0=B8=95=E0=B8=B8=E0=B8=8B=E0=B8=B4=E0=B8= =A5=E0=B8=B4=E0=B8=84=E0=B8=AD=E0=B8=99=E0=B9=81=E0=B8=A5=E0=B9=89=E0=B8= =A7 =E0=B8=9E=E0=B8=B7=E0=B8=8A=E0=B8=97=E0=B8=B5=E0=B9=88=E0=B8=9B=E0= =B8=A5=E0=B8=B9=E0=B8=81=E0=B8=88=E0=B8=B0=E0=B8=AD=E0=B9=88=E0=B8=AD=E0= =B8=99=E0=B9=81=E0=B8=AD=E0=B8=95=E0=B9=88=E0=B8=AD=E0=B9=82=E0=B8=A3=E0= =B8=84=E0=B9=81=E0=B8=A1=E0=B8=A5=E0=B8=87=E0=B9=81=E0=B8=A5=E0=B8=B0=E0= =B8=97=E0=B8=B3=E0=B9=83=E0=B8=AB=E0=B9=89=E0=B8=9C=E0=B8=A5=E0=B8=9C=E0= =B8=A5=E0=B8=B4=E0=B8=95=E0=B8=A5=E0=B8=94=E0=B8=A5=E0=B8=87=E0=B8=96=E0= =B8=B6=E0=B8=87=E0=B8=81=E0=B8=A7=E0=B9=88=E0=B8=B2=E0=B8=84=E0=B8=A3=E0= =B8=B6=E0=B9=88=E0=B8=87 =E0=B8=84=E0=B8=B8=E0=B8=93=E0=B8=AA=E0=B8=A1=E0=B8=9A=E0=B8=B1=E0=B8=95= =E0=B8=B4=E0=B9=80=E0=B8=94=E0=B9=88=E0=B8=99=E0=B9=80=E0=B8=9E=E0=B8=B4= =E0=B9=88=E0=B8=A1=E0=B8=9B=E0=B8=A3=E0=B8=B0=E0=B8=AA=E0=B8=B4=E0=B8=97= =E0=B8=98=E0=B8=B4=E0=B8=A0=E0=B8=B2=E0=B8=9E=E0=B8=9B=E0=B8=B8=E0=B9=8B= =E0=B8=A2=E0=B8=A7=E0=B8=B4=E0=B8=99=E0=B9=82=E0=B8=81=E0=B8=A5=E0=B8=94= =E0=B9=8C 1. =E0=B8=8A=E0=B9=88=E0=B8=A7=E0=B8=A2=E0=B8=9B=E0=B8=A3=E0=B8=B0=E0=B8= =AB=E0=B8=A2=E0=B8=B1=E0=B8=94=E0=B8=9B=E0=B8=B8=E0=B9=8B=E0=B8=A2=E0=B9= =80=E0=B8=84=E0=B8=A1=E0=B8=B5 50% =E0=B9=81=E0=B8=A5=E0=B8=B0=E0=B8=8A= =E0=B9=88=E0=B8=A7=E0=B8=A2=E0=B8=88=E0=B8=B1=E0=B8=9A=E0=B8=9B=E0=B8=B8= =E0=B9=8B=E0=B8=A2=E0=B9=84=E0=B8=A7=E0=B9=89=E0=B9=84=E0=B8=94=E0=B9=89= =E0=B8=99=E0=B8=B2=E0=B8=99=E0=B8=82=E0=B8=B6=E0=B9=89=E0=B8=99=E0=B8=81= =E0=B8=A7=E0=B9=88=E0=B8=B2=E0=B8=9B=E0=B8=81=E0=B8=95=E0=B8=B4 2. =E0=B8=8A=E0=B9=88=E0=B8=A7=E0=B8=A2=E0=B8=9B=E0=B9=89=E0=B8=AD=E0=B8= =87=E0=B8=81=E0=B8=B1=E0=B8=99=E0=B9=81=E0=B8=A1=E0=B8=A5=E0=B8=87 - =E0= =B9=80=E0=B8=8A=E0=B8=B7=E0=B9=89=E0=B8=AD=E0=B8=A3=E0=B8=B2 =E0=B9=82= =E0=B8=84=E0=B8=99 - =E0=B8=A3=E0=B8=B2=E0=B8=81=E0=B9=80=E0=B8=99=E0=B9= =88=E0=B8=B2 =E0=B9=81=E0=B8=A5=E0=B8=B0=E0=B8=81=E0=B8=B3=E0=B8=88=E0= =B8=B1=E0=B8=94=E0=B8=AB=E0=B8=AD=E0=B8=A2=E0=B9=80=E0=B8=8A=E0=B8=AD=E0= =B8=A3=E0=B8=B5=E0=B9=88=E0=B9=84=E0=B8=94=E0=B9=89=E0=B8=94=E0=B8=B5=E0= =B8=A1=E0=B8=B2=E0=B8=81 3. =E0=B8=9B=E0=B8=B5 =E0=B8=84.=E0=B8=A8. 1848 =E0=B8=9C=E0=B8=A5=E0=B8= =97=E0=B8=94=E0=B8=A5=E0=B8=AD=E0=B8=87=E0=B8=8B=E0=B8=B4=E0=B8=A5=E0=B8= =B4=E0=B8=84=E0=B8=AD=E0=B8=99=E0=B8=8A=E0=B9=88=E0=B8=A7=E0=B8=A2=E0=B9= =80=E0=B8=9E=E0=B8=B4=E0=B9=88=E0=B8=A1=E0=B8=9B=E0=B8=A3=E0=B8=B4=E0=B8= =A1=E0=B8=B2=E0=B8=93 =E0=B9=81=E0=B8=A5=E0=B8=B0=E0=B8=84=E0=B8=B8=E0= =B8=93=E0=B8=A0=E0=B8=B2=E0=B8=9E=E0=B8=82=E0=B8=AD=E0=B8=87=E0=B8=9C=E0= =B8=A5=E0=B8=9C=E0=B8=A5=E0=B8=B4=E0=B8=95 50 - 100% 4. =E0=B8=9C=E0=B8=A5=E0=B8=81=E0=B8=B2=E0=B8=A3=E0=B8=97=E0=B8=94=E0=B8= =A5=E0=B8=AD=E0=B8=87=E0=B8=81=E0=B8=A7=E0=B9=88=E0=B8=B2 300 =E0=B8=AD= =E0=B8=B3=E0=B9=80=E0=B8=A0=E0=B8=AD=E0=B8=97=E0=B8=B1=E0=B9=88=E0=B8=A7= =E0=B8=9B=E0=B8=A3=E0=B8=B0=E0=B9=80=E0=B8=97=E0=B8=A8 =E0=B8=97=E0=B8= =B3=E0=B9=83=E0=B8=AB=E0=B9=89=E0=B8=8A=E0=B9=88=E0=B8=A7=E0=B8=A2=E0=B8= =9B=E0=B8=A3=E0=B8=B1=E0=B8=9A=E0=B9=82=E0=B8=84=E0=B8=A3=E0=B8=87=E0=B8= =AA=E0=B8=A3=E0=B9=89=E0=B8=B2=E0=B8=87=E0=B8=82=E0=B8=AD=E0=B8=87=E0=B8= =94=E0=B8=B4=E0=B8=99 - =E0=B8=81=E0=B8=B2=E0=B8=A3=E0=B8=8A=E0=B8=B0=E0= =B8=A5=E0=B9=89=E0=B8=B2=E0=B8=87=E0=B8=82=E0=B8=AD=E0=B8=87=E0=B8=94=E0= =B8=B4=E0=B8=99=E0=B8=88=E0=B8=B2=E0=B8=81=E0=B8=A5=E0=B8=A1 =E0=B9=81=E0=B8=A5=E0=B8=B0=E0=B8=99=E0=B9=89=E0=B8=B3 =E0=B8=8A=E0= =B9=88=E0=B8=A7=E0=B8=A2=E0=B9=80=E0=B8=9E=E0=B8=B4=E0=B9=88=E0=B8=A1=E0= =B8=99=E0=B9=89=E0=B8=B3=E0=B8=AB=E0=B8=99=E0=B8=B1=E0=B8=81=E0=B8=A3=E0= =B8=B2=E0=B8=81=E0=B9=81=E0=B8=A5=E0=B8=B0=E0=B9=80=E0=B8=88=E0=B8=A3=E0= =B8=B4=E0=B8=8D=E0=B8=82=E0=B8=AD=E0=B8=87=E0=B8=A3=E0=B8=B2=E0=B8=81=E0= =B9=84=E0=B8=94=E0=B9=89 50 - 200% 5. =E0=B8=8A=E0=B9=88=E0=B8=A7=E0=B8=A2=E0=B9=83=E0=B8=AB=E0=B9=89=E0=B8= =9E=E0=B8=B7=E0=B8=8A=E0=B8=97=E0=B8=99=E0=B9=81=E0=B8=A5=E0=B9=89=E0=B8= =87 =E0=B8=AA=E0=B8=B2=E0=B8=A1=E0=B8=B2=E0=B8=A3=E0=B8=96=E0=B8=A5=E0= =B8=94=E0=B8=81=E0=B8=B2=E0=B8=A3=E0=B9=83=E0=B8=AB=E0=B9=89=E0=B8=99=E0= =B9=89=E0=B8=B3=E0=B9=84=E0=B8=94=E0=B9=89 30 - 40% =E0=B9=82=E0=B8=94= =E0=B8=A2=E0=B9=84=E0=B8=A1=E0=B9=88=E0=B8=A1=E0=B8=B5=E0=B8=9C=E0=B8=A5= =E0=B9=80=E0=B8=AA=E0=B8=B5=E0=B8=A2=E0=B8=95=E0=B9=88=E0=B8=AD=E0=B8=9E= =E0=B8=B7=E0=B8=8A 6. =E0=B8=8A=E0=B9=88=E0=B8=A7=E0=B8=A2=E0=B8=A5=E0=B8=94=E0=B8=84=E0=B8= =A7=E0=B8=B2=E0=B8=A1=E0=B9=80=E0=B8=9B=E0=B9=87=E0=B8=99=E0=B8=9E=E0=B8= =B4=E0=B8=A9=E0=B8=82=E0=B8=AD=E0=B8=87=E0=B8=AD=E0=B8=A5=E0=B8=B9=E0=B8= =A1=E0=B8=B4=E0=B9=80=E0=B8=99=E0=B8=B5=E0=B8=A2=E0=B8=A1=E0=B9=83=E0=B8= =99=E0=B8=94=E0=B8=B4=E0=B8=99=E0=B8=81=E0=B8=A3=E0=B8=94=E0=B9=84=E0=B8= =94=E0=B9=89=E0=B8=94=E0=B8=B5=E0=B8=81=E0=B8=A7=E0=B9=88=E0=B8=B2=E0=B8= =9B=E0=B8=B9=E0=B8=99=E0=B8=82=E0=B8=B2=E0=B8=A7=E0=B8=AB=E0=B8=A3=E0=B8= =B7=E0=B8=AD=E0=B9=82=E0=B8=84=E0=B9=82=E0=B8=A5=E0=B9=84=E0=B8=A1=E0=B8= =97=E0=B9=8C 5 =E0=B9=80=E0=B8=97=E0=B9=88=E0=B8=B2 7. =E0=B8=8A=E0=B9=88=E0=B8=A7=E0=B8=A2=E0=B9=80=E0=B8=9E=E0=B8=B4=E0=B9= =88=E0=B8=A1=E0=B8=98=E0=B8=B2=E0=B8=95=E0=B8=B8=E0=B8=9F=E0=B8=AD=E0=B8= =AA=E0=B8=9F=E0=B8=AD=E0=B8=A3=E0=B8=B1=E0=B8=AA=E0=B9=83=E0=B8=AB=E0=B9= =89=E0=B8=9E=E0=B8=B7=E0=B8=8A=E0=B9=84=E0=B8=94=E0=B9=89 40% =E0=B9=82= =E0=B8=94=E0=B8=A2=E0=B9=84=E0=B8=A1=E0=B9=88=E0=B8=95=E0=B9=89=E0=B8=AD= =E0=B8=87=E0=B9=83=E0=B8=AA=E0=B9=88=E0=B8=9B=E0=B8=B8=E0=B9=8B=E0=B8=A2= =E0=B8=9F=E0=B8=AD=E0=B8=AA=E0=B8=9F=E0=B8=AD=E0=B8=A3=E0=B8=B1=E0=B8=AA= 8. =E0=B8=8A=E0=B9=88=E0=B8=A7=E0=B8=A2=E0=B8=A5=E0=B8=94=E0=B8=81=E0=B8= =B2=E0=B8=A3=E0=B8=8A=E0=B8=B0=E0=B8=A5=E0=B9=89=E0=B8=B2=E0=B8=87=E0=B8= =82=E0=B8=AD=E0=B8=87 P,N =E0=B9=81=E0=B8=A5=E0=B8=B0 K =E0=B8=88=E0=B8= =B2=E0=B8=81=E0=B9=81=E0=B8=AB=E0=B8=A5=E0=B9=88=E0=B8=87=E0=B9=80=E0=B8= =9E=E0=B8=B2=E0=B8=B0=E0=B8=9B=E0=B8=A5=E0=B8=B9=E0=B8=81 =E0=B9=81=E0= =B8=A5=E0=B8=B0=E0=B8=84=E0=B8=87=E0=B8=98=E0=B8=B2=E0=B8=95=E0=B8=B8=E0= =B8=97=E0=B8=B5=E0=B9=88=E0=B8=9E=E0=B8=B7=E0=B8=8A=E0=B8=99=E0=B8=B3=E0= =B9=84=E0=B8=9B=E0=B9=83=E0=B8=8A=E0=B9=89=E0=B9=84=E0=B8=94=E0=B9=89 9. =E0=B8=8A=E0=B9=88=E0=B8=A7=E0=B8=A2=E0=B9=83=E0=B8=AB=E0=B9=89=E0=B8= =AA=E0=B8=B2=E0=B8=A1=E0=B8=B2=E0=B8=A3=E0=B8=96=E0=B9=83=E0=B8=8A=E0=B9= =89=E0=B8=9B=E0=B8=A3=E0=B8=B0=E0=B9=82=E0=B8=A2=E0=B8=8A=E0=B8=99=E0=B9= =8C=E0=B8=88=E0=B8=B2=E0=B8=81=E0=B8=8A=E0=B8=B5=E0=B8=A7=E0=B8=A1=E0=B8= =B9=E0=B8=A5 (=E0=B8=A1=E0=B8=B9=E0=B8=A5=E0=B8=AA=E0=B8=B1=E0=B8=95=E0= =B8=A7=E0=B9=8C=E0=B9=81=E0=B8=A5=E0=B8=B0=E0=B8=82=E0=B8=AD=E0=B8=87=E0= =B9=80=E0=B8=AB=E0=B8=A5=E0=B8=B7=E0=B8=AD=E0=B8=88=E0=B8=B2=E0=B8=81=E0= =B9=80=E0=B8=97=E0=B8=A8=E0=B8=9A=E0=B8=B2=E0=B8=A5) 10. =E0=B8=8A=E0=B9=88=E0=B8=A7=E0=B8=A2=E0=B8=A5=E0=B8=94=E0=B8=95=E0= =B9=89=E0=B8=99=E0=B8=97=E0=B8=B8=E0=B8=99=E0=B9=81=E0=B8=A5=E0=B8=B0=E0= =B9=80=E0=B8=9E=E0=B8=B4=E0=B9=88=E0=B8=A1=E0=B8=9C=E0=B8=A5=E0=B8=9C=E0= =B8=A5=E0=B8=B4=E0=B8=95=E0=B9=83=E0=B8=99=E0=B8=81=E0=B8=B2=E0=B8=A3=E0= =B8=81=E0=B8=AA=E0=B8=B4=E0=B8=81=E0=B8=A3=E0=B8=A3=E0=B8=A1=E0=B8=96=E0= =B8=B6=E0=B8=87 50 - 100%=20 http://www.peopleadoxy.com/wingold.htm =20 =E0=B8=95=E0=B8=B4=E0=B8=94=E0=B8=95=E0=B9=88=E0=B8=AD=E0=B8=A3=E0=B8=B1= =E0=B8=9A=E0=B8=9B=E0=B8=B8=E0=B9=8B=E0=B8=A2=E0=B8=9F=E0=B8=A3=E0=B8=B5= =E0=B9=84=E0=B8=94=E0=B9=89=E0=B8=97=E0=B8=B5=E0=B9=88 =E0=B8=84=E0=B8= =B8=E0=B8=93 =E0=B8=AD=E0=B8=A0=E0=B8=B4=E0=B8=A7=E0=B8=B1=E0=B8=8A=E0= =B8=A3=E0=B9=8C =E0=B9=82=E0=B8=97=E0=B8=A3 084-9100636 =20 =E0=B8=82=E0=B8=AD=E0=B8=AD=E0=B8=A0=E0=B8=B1=E0=B8=A2=E0=B8=94=E0=B9=89= =E0=B8=A7=E0=B8=A2=E0=B8=96=E0=B9=89=E0=B8=B2=E0=B8=AD=E0=B8=B5=E0=B9=80= =E0=B8=A1=E0=B8=A5=E0=B9=8C=E0=B8=99=E0=B8=B5=E0=B9=89=E0=B9=80=E0=B8=9B= =E0=B9=87=E0=B8=99=E0=B8=81=E0=B8=B2=E0=B8=A3=E0=B8=A3=E0=B8=9A=E0=B8=81= =E0=B8=A7=E0=B8=99=E0=B8=97=E0=B9=88=E0=B8=B2=E0=B8=99 =E0=B9=80=E0=B8= =9E=E0=B8=A3=E0=B8=B2=E0=B8=B0=E0=B8=AD=E0=B8=B5=E0=B9=80=E0=B8=A1=E0=B8= =A5=E0=B9=8C=E0=B8=88=E0=B8=B0=E0=B8=96=E0=B8=B9=E0=B8=81=E0=B8=AA=E0=B9= =88=E0=B8=87=E0=B8=AD=E0=B8=B1=E0=B8=95=E0=B9=82=E0=B8=99=E0=B8=A1=E0=B8= =B1=E0=B8=95=E0=B8=B4 =20 =20 =20 =20 --y4TGl=_LjxV66uFExXpOcRSUgmu4Na6vLv0-- From owner-freebsd-doc@FreeBSD.ORG Wed Dec 10 16:41:24 2008 Return-Path: Delivered-To: doc@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AD29B1065677 for ; Wed, 10 Dec 2008 16:41:24 +0000 (UTC) (envelope-from errol@research.olemiss.edu) Received: from research.gs.olemiss.edu (research.gs.olemiss.edu [130.74.94.201]) by mx1.freebsd.org (Postfix) with ESMTP id 51D1C8FC22 for ; Wed, 10 Dec 2008 16:41:24 +0000 (UTC) (envelope-from errol@research.olemiss.edu) Received: from errol.gs.olemiss.edu (praetor.gs.olemiss.edu [130.74.94.200]) (authenticated bits=0) by research.gs.olemiss.edu (8.14.3/8.14.3) with ESMTP id mBAGJIT4045451 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT) for ; Wed, 10 Dec 2008 10:19:18 -0600 (CST) (envelope-from errol@research.olemiss.edu) Message-Id: <362D5E56-CF69-4194-A799-D3F0412D0C7B@research.olemiss.edu> From: Errol Sayre To: doc@FreeBSD.org Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v929.2) Date: Wed, 10 Dec 2008 10:19:18 -0600 X-Mailer: Apple Mail (2.929.2) Cc: Subject: Missing line on Network File System page 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, 10 Dec 2008 16:41:24 -0000 I think the documentation at http://www.freebsd.org/doc/en/books/handbook/network-nfs.html is missing a line under section 30.3.2 The options to configure in /etc/rc.conf does not include mountd_enable="YES" despite having the mount flags for it. From owner-freebsd-doc@FreeBSD.ORG Wed Dec 10 16:59:26 2008 Return-Path: Delivered-To: doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 91D331065673 for ; Wed, 10 Dec 2008 16:59:26 +0000 (UTC) (envelope-from r.c.ladan@gmail.com) Received: from yx-out-2324.google.com (yx-out-2324.google.com [74.125.44.29]) by mx1.freebsd.org (Postfix) with ESMTP id 43BAD8FC1B for ; Wed, 10 Dec 2008 16:59:25 +0000 (UTC) (envelope-from r.c.ladan@gmail.com) Received: by yx-out-2324.google.com with SMTP id 8so262925yxb.13 for ; Wed, 10 Dec 2008 08:59:25 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=1gQH/6D/XzfHsEebl3tN/lc76lmuENnfp9osIGrd2vg=; b=sKRRL07R6ZBHV3VFoORULXDu9HA3VfwGziUUHT1LiIU0sd2i5042l+4sW/TvyEh0UY 8+rQJMqzNEpGox13GTkH7TkzOFQxXUJm7UsuHI375zfXUxi7AT6fkzN/YJu6XJVnYUca 6JtDRYn1+6czQzScN7X+9qXUgGPFDTmjzfLdw= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=NN/qUMDj54VuHxGgKQPeTiVl9s2ommPEE7sYZprynHzu9z/z/9qD+nUZbV6ZSoFyuN 4Rg3hYsPOVUQ257S4zIqSd8v+LTTMsHIXJSR+YtKjQqTwREHc/0Aio4QetoDMuSJbdK/ n6Se5Ly8/GX8oB/ZbJdy8Y+XCljlc87120BZs= Received: by 10.151.41.21 with SMTP id t21mr2455945ybj.110.1228928365322; Wed, 10 Dec 2008 08:59:25 -0800 (PST) Received: by 10.150.225.9 with HTTP; Wed, 10 Dec 2008 08:59:25 -0800 (PST) Message-ID: Date: Wed, 10 Dec 2008 17:59:25 +0100 From: "Rene Ladan" To: "Errol Sayre" In-Reply-To: <362D5E56-CF69-4194-A799-D3F0412D0C7B@research.olemiss.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <362D5E56-CF69-4194-A799-D3F0412D0C7B@research.olemiss.edu> Cc: doc@freebsd.org Subject: Re: Missing line on Network File System page 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, 10 Dec 2008 16:59:26 -0000 2008/12/10 Errol Sayre : > I think the documentation at > http://www.freebsd.org/doc/en/books/handbook/network-nfs.html is missing a > line under section 30.3.2 > > The options to configure in /etc/rc.conf does not include > mountd_enable="YES" despite having the mount flags for it. > No, because at the next line (!) it says: > mountd runs automatically whenever the NFS server is enabled. Rene -- http://www.rene-ladan.nl/ GPG fingerprint = E738 5471 D185 7013 0EE0 4FC8 3C1D 6F83 12E1 84F6 (subkeys.pgp.net) From owner-freebsd-doc@FreeBSD.ORG Wed Dec 10 17:00:14 2008 Return-Path: Delivered-To: doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8246A10656D6 for ; Wed, 10 Dec 2008 17:00:14 +0000 (UTC) (envelope-from sonic2000gr@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.172]) by mx1.freebsd.org (Postfix) with ESMTP id 156D88FC2D for ; Wed, 10 Dec 2008 17:00:13 +0000 (UTC) (envelope-from sonic2000gr@gmail.com) Received: by ug-out-1314.google.com with SMTP id 30so130938ugs.39 for ; Wed, 10 Dec 2008 09:00:12 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=nNhkfVMZRZ9qFvJ8dug3lbioBQA67YdWggZECTns5Xc=; b=ukvxIv5nspB+CnPT9/lp0u18k8+1RSgo4k8MiNzg4YKsKN3hjbSoxX/9B7nHNdcRhZ NgngYFXA3uK0aC/UoOijrAg2C2+XFmyN4LuJomn1GFAVVm747wUgM87YWvGe6lJo1GS0 SSfocm6Y6/xeFV/O0guSkAdBJqnYhWN28DyU8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=vHdYYz7MXZFQO0YGYSQd+odDAX9idMcFYeNr/ieB2U2KbpvAI0nZnt7n4KajMbx299 ab96cDJQB6vY90tg+T6SO8Fedydd2Mbg2fC78kM8cfZD0QYkXgRzeCDTrvnBp8ZQ8UMb 6/NG+FllzuV/2mRZ6Shkfyo5Rocc9fXUJR1og= Received: by 10.66.255.1 with SMTP id c1mr1995712ugi.44.1228928412824; Wed, 10 Dec 2008 09:00:12 -0800 (PST) Received: from atlantis.dyndns.org (athedsl-4448612.home.otenet.gr [79.129.209.84]) by mx.google.com with ESMTPS id k1sm13949274ugf.3.2008.12.10.09.00.09 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 10 Dec 2008 09:00:10 -0800 (PST) Message-ID: <493FF598.4020503@gmail.com> Date: Wed, 10 Dec 2008 19:00:08 +0200 From: Manolis Kiagias User-Agent: Thunderbird 2.0.0.17 (X11/20081011) MIME-Version: 1.0 To: Errol Sayre References: <362D5E56-CF69-4194-A799-D3F0412D0C7B@research.olemiss.edu> In-Reply-To: <362D5E56-CF69-4194-A799-D3F0412D0C7B@research.olemiss.edu> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: doc@FreeBSD.org Subject: Re: Missing line on Network File System page 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, 10 Dec 2008 17:00:14 -0000 Errol Sayre wrote: > I think the documentation at > http://www.freebsd.org/doc/en/books/handbook/network-nfs.html is > missing a line under section 30.3.2 > > The options to configure in /etc/rc.conf does not include > mountd_enable="YES" despite having the mount flags for it. > Read the line exactly after the sample rc.conf entries: "mountd runs automatically whenever the NFS server is enabled." While technically the mountd_enable option exists (as can be verified by reading /etc/defaults/rc.conf) it is not required if nfs_server_enable is set in rc.conf. From owner-freebsd-doc@FreeBSD.ORG Wed Dec 10 20:56:09 2008 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C529B1065677 for ; Wed, 10 Dec 2008 20:56:09 +0000 (UTC) (envelope-from keramida@freebsd.org) Received: from igloo.linux.gr (igloo.linux.gr [62.1.205.36]) by mx1.freebsd.org (Postfix) with ESMTP id DCAA18FC26 for ; Wed, 10 Dec 2008 20:56:08 +0000 (UTC) (envelope-from keramida@freebsd.org) Received: from kobe.laptop (adsl22-219.kln.forthnet.gr [77.49.149.219]) (authenticated bits=128) by igloo.linux.gr (8.14.3/8.14.3/Debian-5) with ESMTP id mBAKttS7002011 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Wed, 10 Dec 2008 22:56:00 +0200 Received: from kobe.laptop (kobe.laptop [127.0.0.1]) by kobe.laptop (8.14.3/8.14.3) with ESMTP id mBAKtt5f006095 for ; Wed, 10 Dec 2008 22:55:55 +0200 (EET) (envelope-from keramida@freebsd.org) Received: (from keramida@localhost) by kobe.laptop (8.14.3/8.14.3/Submit) id mBAKtsge006094; Wed, 10 Dec 2008 22:55:54 +0200 (EET) (envelope-from keramida@freebsd.org) From: Giorgos Keramidas To: freebsd-doc@freebsd.org Date: Wed, 10 Dec 2008 22:55:47 +0200 Message-ID: <871vwfn418.fsf@kobe.laptop> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.60 (berkeley-unix) MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature" X-MailScanner-ID: mBAKttS7002011 X-Hellug-MailScanner: Found to be clean X-Hellug-MailScanner-SpamCheck: not spam, SpamAssassin (not cached, score=-4.304, required 5, autolearn=not spam, ALL_TRUSTED -1.80, AWL 0.10, BAYES_00 -2.60) X-Hellug-MailScanner-From: keramida@freebsd.org X-Spam-Status: No Subject: [PATCH] Adding elements to wlan Handbook section 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, 10 Dec 2008 20:56:09 -0000 --=-=-= Content-Transfer-Encoding: quoted-printable The wireless networking section is one of those I've been translating lately, and I noticed that it includes *many* acronyms (AP, BSS, SSID, IBSS, WPA, WEP, PSK, TKIP, and so on). The acronyms are practically everywhere, so adding tags to them directly into CVS may not be a very gentle thing to do. So here it is, in diff format for your pleasure. Does anyone have objections to the patch attached below? [NOTE: I haven't wrapped any lines, to keep the patch more readable, but I know already that some of the touched lines may need a bit of wrap & filling after the patch goes in.] %%% diff -r 749797edbbed en_US.ISO8859-1/books/handbook/advanced-networking/cha= pter.sgml =2D-- a/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml Wed= Dec 10 22:03:19 2008 +0200 +++ b/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml Wed D= ec 10 22:50:29 2008 +0200 @@ -21,7 +21,7 @@ =20 =2D How to set up IEEE 802.11 and &bluetooth; devices. + How to set up IEEE 802.11 and &bluetooth; device= s. =20 @@ -700,7 +700,7 @@ Wireless Networking Basics =20 =2D Most wireless networks are based on the IEEE 802.11 + Most wireless networks are based on the IEEE 802.11 standards. A basic wireless network consists of multiple stations communicating with radios that broadcast in either the 2.4GHz or 5GHz band (though this varies according to the @@ -710,19 +710,19 @@ 802.11 networks are organized in two ways: in infrastructure mode one station acts as a master with all the other stations associating to it; the =2D network is known as a BSS and the master station is termed an =2D access point (AP). In a BSS all communication passes through =2D the AP; even when one station wants to communicate with =2D another wireless station messages must go through the AP. In + network is known as a BSS and the master station is te= rmed an + access point (AP). In a BSS all co= mmunication passes through + the AP; even when one station wants to communicate with + another wireless station messages must go through the AP. In the second form of network there is no master and stations =2D communicate directly. This form of network is termed an IBSS + communicate directly. This form of network is termed an IBSS and is commonly known as an ad-hoc network. =20 802.11 networks were first deployed in the 2.4GHz band =2D using protocols defined by the IEEE 802.11 and 802.11b + using protocols defined by the IEEE 802.11 and 802.11b standard. These specifications include the operating =2D frequencies, MAC layer characteristics including framing and + frequencies, MAC layer characteristics including frami= ng and transmission rates (communication can be done at various rates). Later the 802.11a standard defined operation in the 5GHz band, including different signalling mechanisms and @@ -734,51 +734,51 @@ Separate from the underlying transmission techniques 802.11 networks have a variety of security mechanisms. The original 802.11 specifications defined a simple security =2D protocol called WEP. This protocol uses a fixed pre-shared key + protocol called WEP. This protocol uses a fixed pre-sh= ared key and the RC4 cryptographic cipher to encode data transmitted on a network. Stations must all agree on the fixed key in order to communicate. This scheme was shown to be easily broken and is now rarely used except to discourage transient users from joining networks. Current security practice is given by the =2D IEEE 802.11i specification that defines new cryptographic + IEEE 802.11i specification that defines new cryptograp= hic ciphers and an additional protocol to authenticate stations to an access point and exchange keys for doing data communication. Further, cryptographic keys are periodically refreshed and there are mechanisms for detecting intrusion attempts (and for countering intrusion attempts). Another security protocol specification commonly used in wireless =2D networks is termed WPA. This was a precursor to 802.11i + networks is termed WPA. This was a precursor to 802.1= 1i defined by an industry group as an interim measure while =2D waiting for 802.11i to be ratified. WPA specifies a subset of + waiting for 802.11i to be ratified. WPA specifies a s= ubset of the requirements found in 802.11i and is designed for =2D implementation on legacy hardware. Specifically WPA requires =2D only the TKIP cipher that is derived from the original WEP =2D cipher. 802.11i permits use of TKIP but also requires support =2D for a stronger cipher, AES-CCM, for encrypting data. (The AES =2D cipher was not required in WPA because it was deemed too + implementation on legacy hardware. Specifically WPA r= equires + only the TKIP cipher that is derived from the original= WEP + cipher. 802.11i permits use of TKIP but also requires= support + for a stronger cipher, AES-CCM, for encrypting data. = (The AES + cipher was not required in WPA because it was deemed t= oo computationally costly to be implemented on legacy hardware.) =20 Other than the above protocol standards the other important standard to be aware of is 802.11e. This defines protocols for deploying multi-media applications such as =2D streaming video and voice over IP (VoIP) in an 802.11 network. + streaming video and voice over IP (VoIP) in an 802.11 = network. Like 802.11i, 802.11e also has a precursor specification =2D termed WME (later renamed WMM) that has been defined by an + termed WME (later renamed WMM) that= has been defined by an industry group as a subset of 802.11e that can be deployed now to enable multi-media applications while waiting for the final ratification of 802.11e. The most important thing to know =2D about 802.11e and WME/WMM is that it enables prioritized + about 802.11e and WME/WMM is that i= t enables prioritized traffic use of a wireless network through Quality of Service (QoS) protocols and enhanced media access protocols. Proper implementation of these protocols enable high speed bursting of data and prioritized traffic flow. =20 Since the 6.0 version, &os; supports networks that operate =2D using 802.11a, 802.11b, and 802.11g. The WPA and 802.11i + using 802.11a, 802.11b, and 802.11g. The WPA and 802.= 11i security protocols are likewise supported (in conjunction with any of 11a, 11b, and 11g) and QoS and traffic prioritization =2D required by the WME/WMM protocols are supported for a limited + required by the WME/WMM protocols a= re supported for a limited set of wireless devices. =20 @@ -901,7 +901,7 @@ Infrastructure Mode =20 =2D The infrastructure mode or BSS mode is the mode that is + The infrastructure mode or BSS mode is the = mode that is typically used. In this mode, a number of wireless access points are connected to a wired network. Each wireless network has its own name, this name is called the SSID of the @@ -935,7 +935,7 @@ The output of a scan request lists each BSS/IBSS network found. Beside the name of the network, SSID, we find the =2D BSSID which is the MAC address of the + BSSID which is the MAC address = of the access point. The CAPS field identifies the type of each network and the capabilities of the stations operating there: @@ -945,9 +945,9 @@ E =20 =2D Extended Service Set (ESS). Indicates that the + Extended Service Set (ESS). Indicates that the station is part of an infrastructure network (in =2D contrast to an IBSS/ad-hoc network). + contrast to an IBSS/ad-hoc network). =20 @@ -955,8 +955,8 @@ I =20 =2D IBSS/ad-hoc network. Indicates that the station =2D is part of an ad-hoc network (in contrast to an ESS + IBSS/ad-hoc network. Indicates that the station + is part of an ad-hoc network (in contrast to an ESS network). @@ -966,9 +966,9 @@ =20 Privacy. Data confidentiality is required for =2D all data frames exchanged within the BSS. This means =2D that this BSS requires the station to use =2D cryptographic means such as WEP, TKIP or AES-CCMP to + all data frames exchanged within the BSS. This mea= ns + that this BSS requires the station to use + cryptographic means such as WEP, TKIP or AES-CCMP to encrypt/decrypt data frames being exchanged with others. @@ -1037,7 +1037,7 @@ =20 If there are multiple access points and you want to select a specific one, you can select it by its =2D SSID: + SSID: =20 ifconfig_ath0=3D"ssid your_ssid_here DHCP" =20 @@ -1045,8 +1045,8 @@ points with the same SSID (often done to simplify roaming) it may be necessary to associate to one specific device. In this case you can also specify the =2D BSSID of the access point (you can also leave off the =2D SSID): + BSSID of the access point (you can also leave of= f the + SSID): =20 ifconfig_ath0=3D"ssid your_ssid_here bssid xx:xx:xx:xx:xx:xx DHCP" =20 @@ -1084,16 +1084,16 @@ Other schemes require cryptographic handshakes be completed before data traffic can flow; either using pre-shared keys or secrets, or more complex schemes that =2D involve backend services such as RADIUS. Most users + involve backend services such as RADIUS. Most u= sers will use open authentication which is the default =2D setting. Next most common setup is WPA-PSK, also known =2D as WPA Personal, which is described WPA-PSK, als= o known + as WPA Personal, which is described below. =20 If you have an &apple; &airport; Extreme base station for an access point you may need to configure =2D shared-key authentication together with a WEP key. + shared-key authentication together with a WEP key. This can be done in the /etc/rc.conf file or using the &man.wpa.supplicant.8; program. If you have a single @@ -1103,12 +1103,12 @@ ifconfig_ath0=3D"authmode shared wepmode on weptxke= y 1 wepkey 01234567 D= HCP" =20 In general shared key authentication is to be =2D avoided because it uses the WEP key material in a + avoided because it uses the WEP key material in a highly-constrained manner making it even easier to =2D crack the key. If WEP must be used (e.g., for + crack the key. If WEP must be used (e.g., for compatibility with legacy devices) it is better to use =2D WEP with open authentication. More =2D information regarding WEP can be found in the WEP with open authentication. More + information regarding WEP can be found in the . @@ -1119,7 +1119,7 @@ Once you have selected an access point and set the authentication parameters, you will have to get an IP address to communicate. Most of time you will obtain =2D your wireless IP address via DHCP. To achieve that, + your wireless IP address via DHCP. To achieve t= hat, simply edit /etc/rc.conf and add DHCP to the configuration for your device as shown in various examples above: @@ -1149,7 +1149,7 @@ are connected to the wireless network (to the dlinkap network in our case). The bssid 00:13:46:49:41:76 part is the =2D MAC address of your access point; the + MAC address of your access point; the authmode line informs you that the communication is not encrypted (OPEN). @@ -1159,7 +1159,7 @@ Static IP Address =20 In the case you cannot obtain an IP address from a =2D DHCP server, you can set a fixed IP address. Replace + DHCP server, you can set a fixed IP address. Re= place the DHCP keyword shown above with the address information. Be sure to retain any other parameters you have set up for selecting an access @@ -1172,34 +1172,34 @@ WPA =20 =2D WPA (Wi-Fi Protected Access) is a security protocol + WPA (Wi-Fi Protected Access) is a security pro= tocol used together with 802.11 networks to address the lack of proper authentication and the weakness of WEP. WPA leverages + linkend=3D"network-wireless-wep">WEP. WPA = leverages the 802.1X authentication protocol and uses one of several =2D ciphers instead of WEP for data integrity. The only =2D cipher required by WPA is TKIP (Temporary Key Integrity + ciphers instead of WEP for data integrity. The on= ly + cipher required by WPA is TKIP = (Temporary Key Integrity Protocol) which is a cipher that extends the basic RC4 =2D cipher used by WEP by adding integrity checking, tamper + cipher used by WEP by adding integrity checking, t= amper detection, and measures for responding to any detected =2D intrusions. TKIP is designed to work on legacy hardware + intrusions. TKIP is designed to work on legacy ha= rdware with only software modification; it represents a compromise that improves security but is still not =2D entirely immune to attack. WPA also specifies the =2D AES-CCMP cipher as an alternative to TKIP and that is + entirely immune to attack. WPA also specifies the + AES-CCMP cipher as an alternative to TKIP= and that is preferred when possible; for this specification the term =2D WPA2 (or RSN) is commonly used. =2D =2D WPA defines authentication and encryption protocols. + WPA2 (or RSN) is commonly used.= + + WPA defines authentication and encryption prot= ocols. Authentication is most commonly done using one of two techniques: by 802.1X and a backend authentication service =2D such as RADIUS, or by a minimal handshake between the + such as RADIUS, or by a minimal handshake between = the station and the access point using a pre-shared secret. =2D The former is commonly termed WPA Enterprise with the =2D latter known as WPA Personal. Since most people will not =2D set up a RADIUS backend server for wireless network, =2D WPA-PSK is by far the most commonly encountered =2D configuration for WPA. + The former is commonly termed WPA Enterprise with = the + latter known as WPA Personal. Since most people w= ill not + set up a RADIUS backend server for wireless networ= k, + WPA-PSK is by far the most commonly encountered + configuration for WPA. =20 The control of the wireless connection and the authentication (key negotiation or authentication with a @@ -1212,11 +1212,11 @@ WPA-PSK =20 =2D WPA-PSK also known as WPA-Personal is based on a =2D pre-shared key (PSK) generated from a given password and + WPA-PSK also known as WPA-Personal is based = on a + pre-shared key (PSK) generated from a given pass= word and that will be used as the master key in the wireless network. This means every wireless user will share the =2D same key. WPA-PSK is intended for small networks where + same key. WPA-PSK is intended for small network= s where the use of an authentication server is not possible or desired. =20 @@ -1237,8 +1237,8 @@ =20 Then, in /etc/rc.conf, we indicate that the wireless device configuration will be =2D done with WPA and the IP address will be obtained with =2D DHCP: + done with WPA and the IP address will be obtaine= d with + DHCP: =20 ifconfig_ath0=3D"WPA DHCP" =20 @@ -1274,7 +1274,7 @@ =20 The next operation is the launch of the dhclient command to get the IP =2D address from the DHCP server: + address from the DHCP server: =20 &prompt.root; dhclient ath0 DHCPREQUEST on ath0 to 255.255.255.255 port 67 @@ -1301,7 +1301,7 @@ keys. =20 =2D In the case where the use of DHCP is not possible, + In the case where the use of DHCP is not pos= sible, you can set a static IP address after wpa_supplicant has authenticated the station: @@ -1318,7 +1318,7 @@ authmode WPA privacy ON deftxkey UNDEF TKIP 2:128-bit txpowmax 36 protmode CTS roaming MANUAL bintval 100 =20 =2D When DHCP is not used, you also have to manually set + When DHCP is not used, you also have to manu= ally set up the default gateway and the nameserver: =20 &prompt.root; route add default your_= default_router @@ -1328,29 +1328,29 @@ WPA with EAP-TLS =20 =2D The second way to use WPA is with an 802.1X backend =2D authentication server, in this case WPA is called =2D WPA-Enterprise to make difference with the less secure =2D WPA-Personal with its pre-shared key. The =2D authentication in WPA-Enterprise is based on EAP + The second way to use WPA is with an 802.1X = backend + authentication server, in this case WPA is called + WPA-Enterprise to make difference with the less = secure + WPA-Personal with its pre-shared key. The + authentication in WPA-Enterprise is based on EAP (Extensible Authentication Protocol). =20 =2D EAP does not come with an encryption method, it was =2D decided to embed EAP inside an encrypted tunnel. Many =2D types of EAP authentication methods have been designed, =2D the most common methods are EAP-TLS, EAP-TTLS and =2D EAP-PEAP. =2D =2D EAP-TLS (EAP with Transport Layer Security) is a + EAP does not come with an encryption method,= it was + decided to embed EAP inside an encrypted tunnel.= Many + types of EAP authentication methods have been de= signed, + the most common methods are EAP-TLS, EA= P-TTLS and + EAP-PEAP. + + EAP-TLS (EAP with Transpo= rt Layer Security) is a very well-supported authentication protocol in the =2D wireless world since it was the first EAP method to be + wireless world since it was the first EAP method= to be certified by the Wi-Fi alliance. =2D EAP-TLS will require three certificates to run: the CA + EAP-TLS will require three certificates to run: = the CA certificate (installed on all machines), the server certificate for your authentication server, and one client certificate for each wireless client. In this =2D EAP method, both authentication server and wireless + EAP method, both authentication server and wirel= ess client authenticate each other in presenting their respective certificates, and they verify that these certificates were signed by your organization's @@ -1378,30 +1378,30 @@ =20 =2D Here, we use RSN (IEEE 802.11i) protocol, i.e., + Here, we use RSN (IEEE 802.1= 1i) protocol, i.e., WPA2. =20 The key_mgmt line refers to the key management protocol we use. In our case it =2D is WPA using EAP authentication: + is WPA using EAP authentication: WPA-EAP. =20 =2D In this field, we mention the EAP method for our + In this field, we mention the EAP method for our connection. =20 The identity field contains =2D the identity string for EAP. + the identity string for EAP. =20 The ca_cert field indicates =2D the pathname of the CA certificate file. This file + the pathname of the CA certificate file. This file is needed to verify the server certificat. =20 @@ -1457,13 +1457,13 @@ WPA with EAP-TTLS =20 =2D With EAP-TLS both the authentication server and the =2D client need a certificate, with EAP-TTLS (EAP-Tunneled + With EAP-TLS both the authentication server = and the + client need a certificate, with EAP-TTLS (EAP-Tunneled Transport Layer Security) a client certificate is optional. This method is close to what some secure web =2D sites do , where the web server can create a secure SSL + sites do, where the web server can create a secure SSL tunnel even if the visitors do not have client-side =2D certificates. EAP-TTLS will use the encrypted TLS + certificates. EAP-TTLS will use the encrypted <= acronym>TLS tunnel for safe transport of the authentication data. =20 @@ -1484,31 +1484,31 @@ =20 =2D In this field, we mention the EAP method for our + In this field, we mention the EAP method for our connection. =20 The identity field contains =2D the identity string for EAP authentication inside =2D the encrypted TLS tunnel. + the identity string for EAP authentication inside + the encrypted TLS tunnel. =20 The password field contains =2D the passphrase for the EAP authentication. + the passphrase for the EAP authentication. =20 The ca_cert field indicates =2D the pathname of the CA certificate file. This file + the pathname of the CA certificate file. This file is needed to verify the server certificat. =20 In this field, we mention the authentication =2D method used in the encrypted TLS tunnel. In our =2D case, EAP with MD5-Challenge has been used. The + method used in the encrypted TLS tunnel. In our + case, EAP with MD5-Challenge has= been used. The inner authentication phase is often called phase2. @@ -1542,29 +1542,29 @@ WPA with EAP-PEAP =20 =2D PEAP (Protected EAP) has been designed as an =2D alternative to EAP-TTLS. There are two types of PEAP =2D methods, the most common one is PEAPv0/EAP-MSCHAPv2. In =2D the rest of this document, we will use the PEAP term to =2D refer to that EAP method. PEAP is the most used EAP =2D standard after EAP-TLS, in other words if you have a =2D network with mixed OSes, PEAP should be the most =2D supported standard after EAP-TLS. =2D =2D PEAP is similar to EAP-TTLS: it uses a server-side + PEAP (Protected EAP) has = been designed as an + alternative to EAP-TTLS. There are two types of= PEAP + methods, the most common one is PEAPv0/= EAP-MSCHAPv2. In + the rest of this document, we will use the PEAP = term to + refer to that EAP method. PEAP is the most used EAP + standard after EAP-TLS, in other words if you ha= ve a + network with mixed OSes, PEAP should be the most + supported standard after EAP-TLS. + + PEAP is similar to EAP-TTLS: it uses a server-side certificate to authenticate clients by creating an =2D encrypted TLS tunnel between the client and the + encrypted TLS tunnel between the client and the authentication server, which protects the ensuing exchange of authentication information. In term of =2D security the difference between EAP-TTLS and PEAP is =2D that PEAP authentication broadcasts the username in =2D clear, only the password is sent in the encrypted TLS =2D tunnel. EAP-TTLS will use the TLS tunnel for both + security the difference between EAP-TTLS and PEAP is + that PEAP authentication broadcasts the username= in + clear, only the password is sent in the encrypted TLS + tunnel. EAP-TTLS will use the TLS tunnel for both username and password. =20 We have to edit the /etc/wpa_supplicant.conf file and =2D add the EAP-PEAP related settings: + add the EAP-PEAP related settings: =20 network=3D{ ssid=3D"freebsdap" @@ -1580,30 +1580,30 @@ =20 =2D In this field, we mention the EAP method for our + In this field, we mention the EAP method for our connection. =20 The identity field contains =2D the identity string for EAP authentication inside =2D the encrypted TLS tunnel. + the identity string for EAP authentication inside + the encrypted TLS tunnel. =20 The password field contains =2D the passphrase for the EAP authentication. + the passphrase for the EAP authentication. =20 The ca_cert field indicates =2D the pathname of the CA certificate file. This file + the pathname of the CA certificate file. This file is needed to verify the server certificat. =20 This field contains the parameters for the =2D first phase of the authentication (the TLS + first phase of the authentication (the TLS tunnel). According to the authentication server used, you will have to specify a specific label for the authentication. Most of time, the label @@ -1615,8 +1615,8 @@ =20 In this field, we mention the authentication =2D protocol used in the encrypted TLS tunnel. In the =2D case of PEAP, it is + protocol used in the encrypted TLS tunnel. In the + case of PEAP, it is auth=3DMSCHAPV2. @@ -1650,7 +1650,7 @@ WEP =20 =2D WEP (Wired Equivalent Privacy) is part of the original + WEP (Wired Equivalent Privacy) is part of the = original 802.11 standard. There is no authentication mechanism, only a weak form of access control, and it is easily to be cracked. @@ -1663,7 +1663,7 @@ =20 =2D The weptxkey means which WEP + The weptxkey means which WEP key will be used in the transmission. Here we used the third key. This must match the setting in the access point. If you do not have any idea of what is the key @@ -1674,7 +1674,7 @@ =20 The wepkey means setting the =2D selected WEP key. It should in the format + selected WEP key. It should in the format index:key, if the index is not given, key 1 is set. That is to say we need to set the index if we use keys other @@ -1692,7 +1692,7 @@ page for further information. =20 The wpa_supplicant facility also =2D can be used to configure your wireless interface with WEP. + can be used to configure your wireless interface with WEP. The example above can be set up by adding the following lines to /etc/wpa_supplicant.conf: @@ -1716,11 +1716,11 @@ Ad-hoc Mode =20 =2D IBSS mode, also called ad-hoc mode, is designed for point + IBSS mode, also called ad-hoc mode, is desi= gned for point to point connections. For example, to establish an ad-hoc network between the machine A and the machine B we will just need to choose two IP adresses =2D and a SSID. + and a SSID. =20 On the box A: =20 @@ -1736,7 +1736,7 @@ authmode OPEN privacy OFF txpowmax 36 protmode CTS bintval 100 =20 The adhoc parameter indicates the =2D interface is running in the IBSS mode. + interface is running in the IBSS mode. =20 On B, we should be able to detect A: @@ -1769,14 +1769,14 @@ &os; Host Access Points =20 &os; can act as an Access Point (AP) which eliminates the =2D need to buy a hardware AP or run an ad-hoc network. This can be + need to buy a hardware AP or run an ad-hoc network. T= his can be particularly useful when your &os; machine is acting as a gateway to another network (e.g., the Internet). =20 Basic Settings =20 =2D Before configuring your &os; machine as an AP, the + Before configuring your &os; machine as an AP, t= he kernel must be configured with the appropriate wireless networking support for your wireless card. You also have to add the support for the security protocols you intend to @@ -1785,8 +1785,8 @@ =20 The use of the NDIS driver wrapper and the &windows; =2D drivers do not allow currently the AP operation. Only =2D native &os; wireless drivers support AP mode. + drivers do not allow currently the AP operation. = Only + native &os; wireless drivers support AP mode. =20 Once the wireless networking support is loaded, you can @@ -1799,12 +1799,12 @@ This output displays the card capabilities; the HOSTAP word confirms this wireless card can act as an Access Point. Various supported ciphers are =2D also mentioned: WEP, TKIP, WPA2, etc., these informations + also mentioned: WEP, TKIP, WPA2, etc., these informations are important to know what security protocols could be set on the Access Point. =20 The wireless device can now be put into hostap mode and =2D configured with the correct SSID and IP address: + configured with the correct SSID and IP address: =20 &prompt.root; ifconfig ath0= ssid freebsdap mode 11g mediaopt hostap inet 192.168.0.1 netmask 255.2= 55.255.0 =20 @@ -1836,12 +1836,12 @@ Host-based Access Point without Authentication or Encryption =20 =2D Although it is not recommended to run an AP without any + Although it is not recommended to run an AP with= out any authentication or encryption, this is a simple way to check =2D if your AP is working. This configuration is also important + if your AP is working. This configuration is also i= mportant for debugging client issues. =20 =2D Once the AP configured as previously shown, it is + Once the AP configured as previously shown, it is possible from another wireless machine to initiate a scan to find the AP: =20 @@ -1868,17 +1868,17 @@ WPA Host-based Access Point =20 This section will focus on setting up &os; Access Point =2D using the WPA security protocol. More details regarding WPA =2D and the configuration of WPA-based wireless clients can be + using the WPA security protocol. More details regar= ding WPA + and the configuration of WPA-based wireless clients = can be found in the . =20 The hostapd daemon is used to deal with client authentication and keys management on the =2D WPA enabled Access Point. + WPA enabled Access Point. =20 In the following, all the configuration operations will =2D be performed on the &os; machine acting as AP. Once the =2D AP is correctly working, hostapd + be performed on the &os; machine acting as AP. Once= the + AP is correctly working, hostapd should be automatically enabled at boot with the following line in /etc/rc.conf: =20 @@ -1892,7 +1892,7 @@ WPA-PSK =20 =2D WPA-PSK is intended for small networks where the use + WPA-PSK is intended for small networks where t= he use of an backend authentication server is not possible or desired. =20 @@ -1944,14 +1944,14 @@ =20 The wpa field enables WPA and =2D specifies which WPA authentication protocol will be + specifies which WPA authentication protocol will be required. A value of 1 configures the AP for WPA-PSK. =20 The wpa_passphrase field =2D contains the ASCII passphrase for the WPA + contains the ASCII passphrase for the WPA authentication. =20 @@ -1964,17 +1964,17 @@ The wpa_key_mgmt line refers to the key management protocol we use. In our case it is =2D WPA-PSK. + WPA-PSK. =20 The wpa_pairwise field indicates the set of accepted encryption algorithms by =2D the Access Point. Here both TKIP (WPA) and CCMP =2D (WPA2) ciphers are accepted. CCMP cipher is an =2D alternative to TKIP and that is strongly preferred =2D when possible; TKIP should be used solely for stations =2D incapable of doing CCMP. + the Access Point. Here both TKIP (WPA) and CCMP + (WPA2) ciphers are accepted. CCMP= cipher is an + alternative to TKIP and that is strongly preferred + when possible; TKIP should be used solely for stations + incapable of doing CCMP. =20 @@ -1996,7 +1996,7 @@ The Access Point is running, the clients can now be associated with it, see for more details. It is =2D possible to see the stations associated with the AP using + possible to see the stations associated with the AP = using the ifconfig ath0 list sta command. @@ -2005,22 +2005,22 @@ WEP Host-based Access Point =20 =2D It is not recommended to use WEP for setting up an + It is not recommended to use WEP for setting up = an Access Point since there is no authentication mechanism and it is easily to be cracked. Some legacy wireless cards only =2D support WEP as security protocol, these cards will only =2D allow to set up AP without authentication or encryption or =2D using the WEP protocol. + support WEP as security protocol, these cards will o= nly + allow to set up AP without authentication or encrypt= ion or + using the WEP protocol. =20 The wireless device can now be put into hostap mode and =2D configured with the correct SSID and IP address: + configured with the correct SSID and IP address: =20 &prompt.root; ifconfig ath0= ssid freebsdap wepmode on weptxkey 3 wepkey 3:0= x3456789012 mode 11g mediaopt hostap \ inet 192.168.0.1 netmask 255.255.= 255.0 =20 =2D The weptxkey means which WEP + The weptxkey means which WEP key will be used in the transmission. Here we used the third key (note that the key numbering starts with 1). This parameter must be specified @@ -2029,7 +2029,7 @@ =20 The wepkey means setting the =2D selected WEP key. It should in the format + selected WEP key. It should in the format index:key, if the index is not given, key 1 is set. That is to say we need to set the index if we use keys other @@ -2084,7 +2084,7 @@ access point. This includes the authentication scheme and any security protocols. Simplify your configuration as much as possible. If you are using a security protocol =2D such as WPA or WEP configure the access point for open + such as WPA or WEP configure th= e access point for open authentication and no security to see if you can get traffic to pass. @@ -3245,7 +3245,7 @@ lacp =20 =2D Supports the IEEE 802.3ad Link Aggregation Control Protocol + Supports the IEEE 802.3ad Link Aggregation Contr= ol Protocol (LACP) and the Marker Protocol. LACP will negotiate a set of aggregable links with the peer in to one or more Link Aggregated Groups. Each LAG is composed of ports of the same speed, set to %%% --=-=-= Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (FreeBSD) iEYEARECAAYFAklALNoACgkQ1g+UGjGGA7ZefQCglaTBlUE99vJNTJ9dS6RGnA0h YrMAnjtcsxCvoCxHc05JqGKYVQ6EIapU =UEDQ -----END PGP SIGNATURE----- --=-=-=-- From owner-freebsd-doc@FreeBSD.ORG Wed Dec 10 21:10:32 2008 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 056B41065675; Wed, 10 Dec 2008 21:10:32 +0000 (UTC) (envelope-from murray@stokely.org) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.230]) by mx1.freebsd.org (Postfix) with ESMTP id C9B308FC18; Wed, 10 Dec 2008 21:10:31 +0000 (UTC) (envelope-from murray@stokely.org) Received: by rv-out-0506.google.com with SMTP id b25so543881rvf.43 for ; Wed, 10 Dec 2008 13:10:31 -0800 (PST) Received: by 10.140.132.4 with SMTP id f4mr849816rvd.291.1228943431428; Wed, 10 Dec 2008 13:10:31 -0800 (PST) Received: by 10.141.151.6 with HTTP; Wed, 10 Dec 2008 13:10:31 -0800 (PST) Message-ID: <2a7894eb0812101310v2123a452q26b0e07630e7f209@mail.gmail.com> Date: Wed, 10 Dec 2008 13:10:31 -0800 From: "Murray Stokely" To: "Giorgos Keramidas" In-Reply-To: <871vwfn418.fsf@kobe.laptop> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <871vwfn418.fsf@kobe.laptop> Cc: freebsd-doc@freebsd.org Subject: Re: [PATCH] Adding elements to wlan Handbook section 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, 10 Dec 2008 21:10:32 -0000 Is the stylesheet now smart enough to only markup the first occurrence differently? I seem to recall these could get distracting if all instances of an acronym are replaced (either with hyperlinks to definition, or bold, or however we are currently rendering them). - Murray On Wed, Dec 10, 2008 at 12:55 PM, Giorgos Keramidas wrote: > The wireless networking section is one of those I've been translating > lately, and I noticed that it includes *many* acronyms (AP, BSS, SSID, > IBSS, WPA, WEP, PSK, TKIP, and so on). The acronyms are practically > everywhere, so adding tags to them directly into CVS may not > be a very gentle thing to do. > > So here it is, in diff format for your pleasure. Does anyone have > objections to the patch attached below? > > [NOTE: I haven't wrapped any lines, to keep the patch more readable, but > I know already that some of the touched lines may need a bit of wrap & > filling after the patch goes in.] > > %%% > diff -r 749797edbbed en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml > --- a/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml Wed Dec 10 22:03:19 2008 +0200 > +++ b/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml Wed Dec 10 22:50:29 2008 +0200 > @@ -21,7 +21,7 @@ > > > > - How to set up IEEE 802.11 and &bluetooth; devices. > + How to set up IEEE 802.11 and &bluetooth; devices. > > > > @@ -700,7 +700,7 @@ > > Wireless Networking Basics > > - Most wireless networks are based on the IEEE 802.11 > + Most wireless networks are based on the IEEE 802.11 > standards. A basic wireless network consists of multiple > stations communicating with radios that broadcast in either > the 2.4GHz or 5GHz band (though this varies according to the > @@ -710,19 +710,19 @@ > 802.11 networks are organized in two ways: in > infrastructure mode one station acts as a > master with all the other stations associating to it; the > - network is known as a BSS and the master station is termed an > - access point (AP). In a BSS all communication passes through > - the AP; even when one station wants to communicate with > - another wireless station messages must go through the AP. In > + network is known as a BSS and the master station is termed an > + access point (AP). In a BSS all communication passes through > + the AP; even when one station wants to communicate with > + another wireless station messages must go through the AP. In > the second form of network there is no master and stations > - communicate directly. This form of network is termed an IBSS > + communicate directly. This form of network is termed an IBSS > and is commonly known as an ad-hoc > network. > > 802.11 networks were first deployed in the 2.4GHz band > - using protocols defined by the IEEE 802.11 and 802.11b > + using protocols defined by the IEEE 802.11 and 802.11b > standard. These specifications include the operating > - frequencies, MAC layer characteristics including framing and > + frequencies, MAC layer characteristics including framing and > transmission rates (communication can be done at various > rates). Later the 802.11a standard defined operation in the > 5GHz band, including different signalling mechanisms and > @@ -734,51 +734,51 @@ > Separate from the underlying transmission techniques > 802.11 networks have a variety of security mechanisms. The > original 802.11 specifications defined a simple security > - protocol called WEP. This protocol uses a fixed pre-shared key > + protocol called WEP. This protocol uses a fixed pre-shared key > and the RC4 cryptographic cipher to encode data transmitted on > a network. Stations must all agree on the fixed key in order > to communicate. This scheme was shown to be easily broken and > is now rarely used except to discourage transient users from > joining networks. Current security practice is given by the > - IEEE 802.11i specification that defines new cryptographic > + IEEE 802.11i specification that defines new cryptographic > ciphers and an additional protocol to authenticate stations to > an access point and exchange keys for doing data > communication. Further, cryptographic keys are periodically > refreshed and there are mechanisms for detecting intrusion > attempts (and for countering intrusion attempts). Another > security protocol specification commonly used in wireless > - networks is termed WPA. This was a precursor to 802.11i > + networks is termed WPA. This was a precursor to 802.11i > defined by an industry group as an interim measure while > - waiting for 802.11i to be ratified. WPA specifies a subset of > + waiting for 802.11i to be ratified. WPA specifies a subset of > the requirements found in 802.11i and is designed for > - implementation on legacy hardware. Specifically WPA requires > - only the TKIP cipher that is derived from the original WEP > - cipher. 802.11i permits use of TKIP but also requires support > - for a stronger cipher, AES-CCM, for encrypting data. (The AES > - cipher was not required in WPA because it was deemed too > + implementation on legacy hardware. Specifically WPA requires > + only the TKIP cipher that is derived from the original WEP > + cipher. 802.11i permits use of TKIP but also requires support > + for a stronger cipher, AES-CCM, for encrypting data. (The AES > + cipher was not required in WPA because it was deemed too > computationally costly to be implemented on legacy > hardware.) > > Other than the above protocol standards the other > important standard to be aware of is 802.11e. This defines > protocols for deploying multi-media applications such as > - streaming video and voice over IP (VoIP) in an 802.11 network. > + streaming video and voice over IP (VoIP) in an 802.11 network. > Like 802.11i, 802.11e also has a precursor specification > - termed WME (later renamed WMM) that has been defined by an > + termed WME (later renamed WMM) that has been defined by an > industry group as a subset of 802.11e that can be deployed now > to enable multi-media applications while waiting for the final > ratification of 802.11e. The most important thing to know > - about 802.11e and WME/WMM is that it enables prioritized > + about 802.11e and WME/WMM is that it enables prioritized > traffic use of a wireless network through Quality of Service > (QoS) protocols and enhanced media access protocols. Proper > implementation of these protocols enable high speed bursting > of data and prioritized traffic flow. > > Since the 6.0 version, &os; supports networks that operate > - using 802.11a, 802.11b, and 802.11g. The WPA and 802.11i > + using 802.11a, 802.11b, and 802.11g. The WPA and 802.11i > security protocols are likewise supported (in conjunction with > any of 11a, 11b, and 11g) and QoS and traffic prioritization > - required by the WME/WMM protocols are supported for a limited > + required by the WME/WMM protocols are supported for a limited > set of wireless devices. > > > @@ -901,7 +901,7 @@ > > Infrastructure Mode > > - The infrastructure mode or BSS mode is the mode that is > + The infrastructure mode or BSS mode is the mode that is > typically used. In this mode, a number of wireless access > points are connected to a wired network. Each wireless > network has its own name, this name is called the SSID of the > @@ -935,7 +935,7 @@ > The output of a scan request lists each BSS/IBSS > network found. Beside the name of the network, > SSID, we find the > - BSSID which is the MAC address of the > + BSSID which is the MAC address of the > access point. The CAPS field > identifies the type of each network and the capabilities > of the stations operating there: > @@ -945,9 +945,9 @@ > E > > > - Extended Service Set (ESS). Indicates that the > + Extended Service Set (ESS). Indicates that the > station is part of an infrastructure network (in > - contrast to an IBSS/ad-hoc network). > + contrast to an IBSS/ad-hoc network). > > > > @@ -955,8 +955,8 @@ > I > > > - IBSS/ad-hoc network. Indicates that the station > - is part of an ad-hoc network (in contrast to an ESS > + IBSS/ad-hoc network. Indicates that the station > + is part of an ad-hoc network (in contrast to an ESS > network). > > > @@ -966,9 +966,9 @@ > > > Privacy. Data confidentiality is required for > - all data frames exchanged within the BSS. This means > - that this BSS requires the station to use > - cryptographic means such as WEP, TKIP or AES-CCMP to > + all data frames exchanged within the BSS. This means > + that this BSS requires the station to use > + cryptographic means such as WEP, TKIP or AES-CCMP to > encrypt/decrypt data frames being exchanged with > others. > > @@ -1037,7 +1037,7 @@ > > If there are multiple access points and you want to > select a specific one, you can select it by its > - SSID: > + SSID: > > ifconfig_ath0="ssid your_ssid_here DHCP" > > @@ -1045,8 +1045,8 @@ > points with the same SSID (often done to simplify > roaming) it may be necessary to associate to one > specific device. In this case you can also specify the > - BSSID of the access point (you can also leave off the > - SSID): > + BSSID of the access point (you can also leave off the > + SSID): > > ifconfig_ath0="ssid your_ssid_here bssid xx:xx:xx:xx:xx:xx DHCP" > > @@ -1084,16 +1084,16 @@ > Other schemes require cryptographic handshakes be > completed before data traffic can flow; either using > pre-shared keys or secrets, or more complex schemes that > - involve backend services such as RADIUS. Most users > + involve backend services such as RADIUS. Most users > will use open authentication which is the default > - setting. Next most common setup is WPA-PSK, also known > - as WPA Personal, which is described + setting. Next most common setup is WPA-PSK, also known > + as WPA Personal, which is described linkend="network-wireless-wpa-wpa-psk">below. > > > If you have an &apple; &airport; Extreme base > station for an access point you may need to configure > - shared-key authentication together with a WEP key. > + shared-key authentication together with a WEP key. > This can be done in the > /etc/rc.conf file or using the > &man.wpa.supplicant.8; program. If you have a single > @@ -1103,12 +1103,12 @@ > ifconfig_ath0="authmode shared wepmode on weptxkey 1 wepkey 01234567 DHCP" > > In general shared key authentication is to be > - avoided because it uses the WEP key material in a > + avoided because it uses the WEP key material in a > highly-constrained manner making it even easier to > - crack the key. If WEP must be used (e.g., for > + crack the key. If WEP must be used (e.g., for > compatibility with legacy devices) it is better to use > - WEP with open authentication. More > - information regarding WEP can be found in the + WEP with open authentication. More > + information regarding WEP can be found in the linkend="network-wireless-wep">. > > > @@ -1119,7 +1119,7 @@ > Once you have selected an access point and set the > authentication parameters, you will have to get an IP > address to communicate. Most of time you will obtain > - your wireless IP address via DHCP. To achieve that, > + your wireless IP address via DHCP. To achieve that, > simply edit /etc/rc.conf and add > DHCP to the configuration for your > device as shown in various examples above: > @@ -1149,7 +1149,7 @@ > are connected to the wireless network (to the > dlinkap network in our case). The > bssid 00:13:46:49:41:76 part is the > - MAC address of your access point; the > + MAC address of your access point; the > authmode line informs you that the > communication is not encrypted > (OPEN). > @@ -1159,7 +1159,7 @@ > Static IP Address > > In the case you cannot obtain an IP address from a > - DHCP server, you can set a fixed IP address. Replace > + DHCP server, you can set a fixed IP address. Replace > the DHCP keyword shown above with the > address information. Be sure to retain any other > parameters you have set up for selecting an access > @@ -1172,34 +1172,34 @@ > > WPA > > - WPA (Wi-Fi Protected Access) is a security protocol > + WPA (Wi-Fi Protected Access) is a security protocol > used together with 802.11 networks to address the lack of > proper authentication and the weakness of - linkend="network-wireless-wep">WEP. WPA leverages > + linkend="network-wireless-wep">WEP. WPA leverages > the 802.1X authentication protocol and uses one of several > - ciphers instead of WEP for data integrity. The only > - cipher required by WPA is TKIP (Temporary Key Integrity > + ciphers instead of WEP for data integrity. The only > + cipher required by WPA is TKIP (Temporary Key Integrity > Protocol) which is a cipher that extends the basic RC4 > - cipher used by WEP by adding integrity checking, tamper > + cipher used by WEP by adding integrity checking, tamper > detection, and measures for responding to any detected > - intrusions. TKIP is designed to work on legacy hardware > + intrusions. TKIP is designed to work on legacy hardware > with only software modification; it represents a > compromise that improves security but is still not > - entirely immune to attack. WPA also specifies the > - AES-CCMP cipher as an alternative to TKIP and that is > + entirely immune to attack. WPA also specifies the > + AES-CCMP cipher as an alternative to TKIP and that is > preferred when possible; for this specification the term > - WPA2 (or RSN) is commonly used. > - > - WPA defines authentication and encryption protocols. > + WPA2 (or RSN) is commonly used. > + > + WPA defines authentication and encryption protocols. > Authentication is most commonly done using one of two > techniques: by 802.1X and a backend authentication service > - such as RADIUS, or by a minimal handshake between the > + such as RADIUS, or by a minimal handshake between the > station and the access point using a pre-shared secret. > - The former is commonly termed WPA Enterprise with the > - latter known as WPA Personal. Since most people will not > - set up a RADIUS backend server for wireless network, > - WPA-PSK is by far the most commonly encountered > - configuration for WPA. > + The former is commonly termed WPA Enterprise with the > + latter known as WPA Personal. Since most people will not > + set up a RADIUS backend server for wireless network, > + WPA-PSK is by far the most commonly encountered > + configuration for WPA. > > The control of the wireless connection and the > authentication (key negotiation or authentication with a > @@ -1212,11 +1212,11 @@ > > WPA-PSK > > - WPA-PSK also known as WPA-Personal is based on a > - pre-shared key (PSK) generated from a given password and > + WPA-PSK also known as WPA-Personal is based on a > + pre-shared key (PSK) generated from a given password and > that will be used as the master key in the wireless > network. This means every wireless user will share the > - same key. WPA-PSK is intended for small networks where > + same key. WPA-PSK is intended for small networks where > the use of an authentication server is not possible or > desired. > > @@ -1237,8 +1237,8 @@ > > Then, in /etc/rc.conf, we > indicate that the wireless device configuration will be > - done with WPA and the IP address will be obtained with > - DHCP: > + done with WPA and the IP address will be obtained with > + DHCP: > > ifconfig_ath0="WPA DHCP" > > @@ -1274,7 +1274,7 @@ > > The next operation is the launch of the > dhclient command to get the IP > - address from the DHCP server: > + address from the DHCP server: > > &prompt.root; dhclient ath0 > DHCPREQUEST on ath0 to 255.255.255.255 port 67 > @@ -1301,7 +1301,7 @@ > keys. > > > - In the case where the use of DHCP is not possible, > + In the case where the use of DHCP is not possible, > you can set a static IP address after > wpa_supplicant has authenticated the > station: > @@ -1318,7 +1318,7 @@ > authmode WPA privacy ON deftxkey UNDEF TKIP 2:128-bit txpowmax 36 > protmode CTS roaming MANUAL bintval 100 > > - When DHCP is not used, you also have to manually set > + When DHCP is not used, you also have to manually set > up the default gateway and the nameserver: > > &prompt.root; route add default your_default_router > @@ -1328,29 +1328,29 @@ > > WPA with EAP-TLS > > - The second way to use WPA is with an 802.1X backend > - authentication server, in this case WPA is called > - WPA-Enterprise to make difference with the less secure > - WPA-Personal with its pre-shared key. The > - authentication in WPA-Enterprise is based on EAP > + The second way to use WPA is with an 802.1X backend > + authentication server, in this case WPA is called > + WPA-Enterprise to make difference with the less secure > + WPA-Personal with its pre-shared key. The > + authentication in WPA-Enterprise is based on EAP > (Extensible Authentication Protocol). > > - EAP does not come with an encryption method, it was > - decided to embed EAP inside an encrypted tunnel. Many > - types of EAP authentication methods have been designed, > - the most common methods are EAP-TLS, EAP-TTLS and > - EAP-PEAP. > - > - EAP-TLS (EAP with Transport Layer Security) is a > + EAP does not come with an encryption method, it was > + decided to embed EAP inside an encrypted tunnel. Many > + types of EAP authentication methods have been designed, > + the most common methods are EAP-TLS, EAP-TTLS and > + EAP-PEAP. > + > + EAP-TLS (EAP with Transport Layer Security) is a > very well-supported authentication protocol in the > - wireless world since it was the first EAP method to be > + wireless world since it was the first EAP method to be > certified by the url="http://www.wi-fi.org/">Wi-Fi alliance. > - EAP-TLS will require three certificates to run: the CA > + EAP-TLS will require three certificates to run: the CA > certificate (installed on all machines), the server > certificate for your authentication server, and one > client certificate for each wireless client. In this > - EAP method, both authentication server and wireless > + EAP method, both authentication server and wireless > client authenticate each other in presenting their > respective certificates, and they verify that these > certificates were signed by your organization's > @@ -1378,30 +1378,30 @@ > > > > - Here, we use RSN (IEEE 802.11i) protocol, i.e., > + Here, we use RSN (IEEE 802.11i) protocol, i.e., > WPA2. > > > > The key_mgmt line refers to > the key management protocol we use. In our case it > - is WPA using EAP authentication: > + is WPA using EAP authentication: > WPA-EAP. > > > > - In this field, we mention the EAP method for our > + In this field, we mention the EAP method for our > connection. > > > > The identity field contains > - the identity string for EAP. > + the identity string for EAP. > > > > The ca_cert field indicates > - the pathname of the CA certificate file. This file > + the pathname of the CA certificate file. This file > is needed to verify the server certificat. > > > @@ -1457,13 +1457,13 @@ > > WPA with EAP-TTLS > > - With EAP-TLS both the authentication server and the > - client need a certificate, with EAP-TTLS (EAP-Tunneled > + With EAP-TLS both the authentication server and the > + client need a certificate, with EAP-TTLS (EAP-Tunneled > Transport Layer Security) a client certificate is > optional. This method is close to what some secure web > - sites do , where the web server can create a secure SSL > + sites do, where the web server can create a secure SSL > tunnel even if the visitors do not have client-side > - certificates. EAP-TTLS will use the encrypted TLS > + certificates. EAP-TTLS will use the encrypted TLS > tunnel for safe transport of the authentication > data. > > @@ -1484,31 +1484,31 @@ > > > > - In this field, we mention the EAP method for our > + In this field, we mention the EAP method for our > connection. > > > > The identity field contains > - the identity string for EAP authentication inside > - the encrypted TLS tunnel. > + the identity string for EAP authentication inside > + the encrypted TLS tunnel. > > > > The password field contains > - the passphrase for the EAP authentication. > + the passphrase for the EAP authentication. > > > > The ca_cert field indicates > - the pathname of the CA certificate file. This file > + the pathname of the CA certificate file. This file > is needed to verify the server certificat. > > > > In this field, we mention the authentication > - method used in the encrypted TLS tunnel. In our > - case, EAP with MD5-Challenge has been used. The > + method used in the encrypted TLS tunnel. In our > + case, EAP with MD5-Challenge has been used. The > inner authentication phase is often > called phase2. > > @@ -1542,29 +1542,29 @@ > > WPA with EAP-PEAP > > - PEAP (Protected EAP) has been designed as an > - alternative to EAP-TTLS. There are two types of PEAP > - methods, the most common one is PEAPv0/EAP-MSCHAPv2. In > - the rest of this document, we will use the PEAP term to > - refer to that EAP method. PEAP is the most used EAP > - standard after EAP-TLS, in other words if you have a > - network with mixed OSes, PEAP should be the most > - supported standard after EAP-TLS. > - > - PEAP is similar to EAP-TTLS: it uses a server-side > + PEAP (Protected EAP) has been designed as an > + alternative to EAP-TTLS. There are two types of PEAP > + methods, the most common one is PEAPv0/EAP-MSCHAPv2. In > + the rest of this document, we will use the PEAP term to > + refer to that EAP method. PEAP is the most used EAP > + standard after EAP-TLS, in other words if you have a > + network with mixed OSes, PEAP should be the most > + supported standard after EAP-TLS. > + > + PEAP is similar to EAP-TTLS: it uses a server-side > certificate to authenticate clients by creating an > - encrypted TLS tunnel between the client and the > + encrypted TLS tunnel between the client and the > authentication server, which protects the ensuing > exchange of authentication information. In term of > - security the difference between EAP-TTLS and PEAP is > - that PEAP authentication broadcasts the username in > - clear, only the password is sent in the encrypted TLS > - tunnel. EAP-TTLS will use the TLS tunnel for both > + security the difference between EAP-TTLS and PEAP is > + that PEAP authentication broadcasts the username in > + clear, only the password is sent in the encrypted TLS > + tunnel. EAP-TTLS will use the TLS tunnel for both > username and password. > > We have to edit the > /etc/wpa_supplicant.conf file and > - add the EAP-PEAP related settings: > + add the EAP-PEAP related settings: > > network={ > ssid="freebsdap" > @@ -1580,30 +1580,30 @@ > > > > - In this field, we mention the EAP method for our > + In this field, we mention the EAP method for our > connection. > > > > The identity field contains > - the identity string for EAP authentication inside > - the encrypted TLS tunnel. > + the identity string for EAP authentication inside > + the encrypted TLS tunnel. > > > > The password field contains > - the passphrase for the EAP authentication. > + the passphrase for the EAP authentication. > > > > The ca_cert field indicates > - the pathname of the CA certificate file. This file > + the pathname of the CA certificate file. This file > is needed to verify the server certificat. > > > > This field contains the parameters for the > - first phase of the authentication (the TLS > + first phase of the authentication (the TLS > tunnel). According to the authentication server > used, you will have to specify a specific label > for the authentication. Most of time, the label > @@ -1615,8 +1615,8 @@ > > > In this field, we mention the authentication > - protocol used in the encrypted TLS tunnel. In the > - case of PEAP, it is > + protocol used in the encrypted TLS tunnel. In the > + case of PEAP, it is > auth=MSCHAPV2. > > > @@ -1650,7 +1650,7 @@ > > WEP > > - WEP (Wired Equivalent Privacy) is part of the original > + WEP (Wired Equivalent Privacy) is part of the original > 802.11 standard. There is no authentication mechanism, > only a weak form of access control, and it is easily to be > cracked. > @@ -1663,7 +1663,7 @@ > > > > - The weptxkey means which WEP > + The weptxkey means which WEP > key will be used in the transmission. Here we used the > third key. This must match the setting in the access > point. If you do not have any idea of what is the key > @@ -1674,7 +1674,7 @@ > > > The wepkey means setting the > - selected WEP key. It should in the format > + selected WEP key. It should in the format > index:key, if the index is > not given, key 1 is set. That is > to say we need to set the index if we use keys other > @@ -1692,7 +1692,7 @@ > page for further information. > > The wpa_supplicant facility also > - can be used to configure your wireless interface with WEP. > + can be used to configure your wireless interface with WEP. > The example above can be set up by adding the following > lines to > /etc/wpa_supplicant.conf: > @@ -1716,11 +1716,11 @@ > > Ad-hoc Mode > > - IBSS mode, also called ad-hoc mode, is designed for point > + IBSS mode, also called ad-hoc mode, is designed for point > to point connections. For example, to establish an ad-hoc > network between the machine A and the machine > B we will just need to choose two IP adresses > - and a SSID. > + and a SSID. > > On the box A: > > @@ -1736,7 +1736,7 @@ > authmode OPEN privacy OFF txpowmax 36 protmode CTS bintval 100 > > The adhoc parameter indicates the > - interface is running in the IBSS mode. > + interface is running in the IBSS mode. > > On B, we should be able to detect > A: > @@ -1769,14 +1769,14 @@ > &os; Host Access Points > > &os; can act as an Access Point (AP) which eliminates the > - need to buy a hardware AP or run an ad-hoc network. This can be > + need to buy a hardware AP or run an ad-hoc network. This can be > particularly useful when your &os; machine is acting as a > gateway to another network (e.g., the Internet). > > > Basic Settings > > - Before configuring your &os; machine as an AP, the > + Before configuring your &os; machine as an AP, the > kernel must be configured with the appropriate wireless > networking support for your wireless card. You also have to > add the support for the security protocols you intend to > @@ -1785,8 +1785,8 @@ > > > The use of the NDIS driver wrapper and the &windows; > - drivers do not allow currently the AP operation. Only > - native &os; wireless drivers support AP mode. > + drivers do not allow currently the AP operation. Only > + native &os; wireless drivers support AP mode. > > > Once the wireless networking support is loaded, you can > @@ -1799,12 +1799,12 @@ > This output displays the card capabilities; the > HOSTAP word confirms this wireless card > can act as an Access Point. Various supported ciphers are > - also mentioned: WEP, TKIP, WPA2, etc., these informations > + also mentioned: WEP, TKIP, WPA2, etc., these informations > are important to know what security protocols could be set > on the Access Point. > > The wireless device can now be put into hostap mode and > - configured with the correct SSID and IP address: > + configured with the correct SSID and IP address: > > &prompt.root; ifconfig ath0 ssid freebsdap mode 11g mediaopt hostap inet 192.168.0.1 netmask 255.255.255.0 > > @@ -1836,12 +1836,12 @@ > Host-based Access Point without Authentication or > Encryption > > - Although it is not recommended to run an AP without any > + Although it is not recommended to run an AP without any > authentication or encryption, this is a simple way to check > - if your AP is working. This configuration is also important > + if your AP is working. This configuration is also important > for debugging client issues. > > - Once the AP configured as previously shown, it is > + Once the AP configured as previously shown, it is > possible from another wireless machine to initiate a scan to > find the AP: > > @@ -1868,17 +1868,17 @@ > WPA Host-based Access Point > > This section will focus on setting up &os; Access Point > - using the WPA security protocol. More details regarding WPA > - and the configuration of WPA-based wireless clients can be > + using the WPA security protocol. More details regarding WPA > + and the configuration of WPA-based wireless clients can be > found in the . > > The hostapd daemon is used to > deal with client authentication and keys management on the > - WPA enabled Access Point. > + WPA enabled Access Point. > > In the following, all the configuration operations will > - be performed on the &os; machine acting as AP. Once the > - AP is correctly working, hostapd > + be performed on the &os; machine acting as AP. Once the > + AP is correctly working, hostapd > should be automatically enabled at boot with the following > line in /etc/rc.conf: > > @@ -1892,7 +1892,7 @@ > > WPA-PSK > > - WPA-PSK is intended for small networks where the use > + WPA-PSK is intended for small networks where the use > of an backend authentication server is not possible or > desired. > > @@ -1944,14 +1944,14 @@ > > > The wpa field enables WPA and > - specifies which WPA authentication protocol will be > + specifies which WPA authentication protocol will be > required. A value of 1 configures the > AP for WPA-PSK. > > > > The wpa_passphrase field > - contains the ASCII passphrase for the WPA > + contains the ASCII passphrase for the WPA > authentication. > > > @@ -1964,17 +1964,17 @@ > > The wpa_key_mgmt line refers to > the key management protocol we use. In our case it is > - WPA-PSK. > + WPA-PSK. > > > > The wpa_pairwise field > indicates the set of accepted encryption algorithms by > - the Access Point. Here both TKIP (WPA) and CCMP > - (WPA2) ciphers are accepted. CCMP cipher is an > - alternative to TKIP and that is strongly preferred > - when possible; TKIP should be used solely for stations > - incapable of doing CCMP. > + the Access Point. Here both TKIP (WPA) and CCMP > + (WPA2) ciphers are accepted. CCMP cipher is an > + alternative to TKIP and that is strongly preferred > + when possible; TKIP should be used solely for stations > + incapable of doing CCMP. > > > > @@ -1996,7 +1996,7 @@ > The Access Point is running, the clients can now be > associated with it, see linkend="network-wireless-wpa"> for more details. It is > - possible to see the stations associated with the AP using > + possible to see the stations associated with the AP using > the ifconfig ath0 list > sta command. > > @@ -2005,22 +2005,22 @@ > > WEP Host-based Access Point > > - It is not recommended to use WEP for setting up an > + It is not recommended to use WEP for setting up an > Access Point since there is no authentication mechanism and > it is easily to be cracked. Some legacy wireless cards only > - support WEP as security protocol, these cards will only > - allow to set up AP without authentication or encryption or > - using the WEP protocol. > + support WEP as security protocol, these cards will only > + allow to set up AP without authentication or encryption or > + using the WEP protocol. > > The wireless device can now be put into hostap mode and > - configured with the correct SSID and IP address: > + configured with the correct SSID and IP address: > > &prompt.root; ifconfig ath0 ssid freebsdap wepmode on weptxkey 3 wepkey 3:0x3456789012 mode 11g mediaopt hostap \ > inet 192.168.0.1 netmask 255.255.255.0 > > > > - The weptxkey means which WEP > + The weptxkey means which WEP > key will be used in the transmission. Here we used the > third key (note that the key numbering starts with > 1). This parameter must be specified > @@ -2029,7 +2029,7 @@ > > > The wepkey means setting the > - selected WEP key. It should in the format > + selected WEP key. It should in the format > index:key, if the index is > not given, key 1 is set. That is > to say we need to set the index if we use keys other > @@ -2084,7 +2084,7 @@ > access point. This includes the authentication scheme and > any security protocols. Simplify your configuration as > much as possible. If you are using a security protocol > - such as WPA or WEP configure the access point for open > + such as WPA or WEP configure the access point for open > authentication and no security to see if you can get > traffic to pass. > > @@ -3245,7 +3245,7 @@ > lacp > > > - Supports the IEEE 802.3ad Link Aggregation Control Protocol > + Supports the IEEE 802.3ad Link Aggregation Control Protocol > (LACP) and the Marker Protocol. LACP will negotiate a set of > aggregable links with the peer in to one or more Link Aggregated > Groups. Each LAG is composed of ports of the same speed, set to > %%% > From owner-freebsd-doc@FreeBSD.ORG Wed Dec 10 21:12:21 2008 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9BC391065672 for ; Wed, 10 Dec 2008 21:12:21 +0000 (UTC) (envelope-from sonic2000gr@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.169]) by mx1.freebsd.org (Postfix) with ESMTP id 292FF8FC27 for ; Wed, 10 Dec 2008 21:12:20 +0000 (UTC) (envelope-from sonic2000gr@gmail.com) Received: by ug-out-1314.google.com with SMTP id 30so154164ugs.39 for ; Wed, 10 Dec 2008 13:12:19 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=R/xCn9wb2SzzvqXQ7hB/3EbD+AIJqUOyAhl0jeUBqW8=; b=aM2JQ8XJb5HC5cL6xWdO254izCn4vcMZ1+7HMRAQbPTxsRYhA2x2hXI5JLGrbG8INc wzbi5yK5cuLG2rOwp6CMaK8xFGaO/6/npcYZHykk2y028MPbW+zgYrLmQ8qSlqDbzhHz 1hKFGyDa8HIQqwvLBpPuUtZfLlU7LLFB20Eps= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=AelcRcSdQ1p4jLmSvOX8G4/UxlyZFuwMFFxQ5k1f3G56bPBKNHBRwVLL/JOTQ5wKiD cNyqXoMOZg1Pwy3yW5nqRfKYjAOBZthTDzU62695jhQ+ndlgalfbfsGbFhTnOnYdc8tS 7ByVsSCn5OMqyK3uk22QGvp2Ido0x5mBfHezk= Received: by 10.67.115.3 with SMTP id s3mr4406230ugm.60.1228943539855; Wed, 10 Dec 2008 13:12:19 -0800 (PST) Received: from atlantis.dyndns.org (athedsl-4448612.home.otenet.gr [79.129.209.84]) by mx.google.com with ESMTPS id g30sm14468331ugd.32.2008.12.10.13.12.18 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 10 Dec 2008 13:12:19 -0800 (PST) Message-ID: <494030B1.2080001@gmail.com> Date: Wed, 10 Dec 2008 23:12:17 +0200 From: Manolis Kiagias User-Agent: Thunderbird 2.0.0.17 (X11/20081011) MIME-Version: 1.0 To: Giorgos Keramidas References: <871vwfn418.fsf@kobe.laptop> In-Reply-To: <871vwfn418.fsf@kobe.laptop> Content-Type: text/plain; charset=ISO-8859-7 Content-Transfer-Encoding: 7bit Cc: freebsd-doc@freebsd.org Subject: Re: [PATCH] Adding elements to wlan Handbook section 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, 10 Dec 2008 21:12:21 -0000 Giorgos Keramidas wrote: > The wireless networking section is one of those I've been translating > lately, and I noticed that it includes *many* acronyms (AP, BSS, SSID, > IBSS, WPA, WEP, PSK, TKIP, and so on). The acronyms are practically > everywhere, so adding tags to them directly into CVS may not > be a very gentle thing to do. > > So here it is, in diff format for your pleasure. Does anyone have > objections to the patch attached below? > > [NOTE: I haven't wrapped any lines, to keep the patch more readable, but > I know already that some of the touched lines may need a bit of wrap & > filling after the patch goes in.] > No objection here, but just an idea: It is also possible to use something like: WEP when this is rendered in HTML, the text in "role" appears on mouse-over (what most would call a tool tip). Maybe we could use this the first time the acronym is used (except if it is already expanded in the preceeding text of course). From owner-freebsd-doc@FreeBSD.ORG Wed Dec 10 21:20:18 2008 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 74B29106564A for ; Wed, 10 Dec 2008 21:20:18 +0000 (UTC) (envelope-from keramida@freebsd.org) Received: from igloo.linux.gr (igloo.linux.gr [62.1.205.36]) by mx1.freebsd.org (Postfix) with ESMTP id E157B8FC1E for ; Wed, 10 Dec 2008 21:20:17 +0000 (UTC) (envelope-from keramida@freebsd.org) Received: from kobe.laptop (adsl22-219.kln.forthnet.gr [77.49.149.219]) (authenticated bits=128) by igloo.linux.gr (8.14.3/8.14.3/Debian-5) with ESMTP id mBALK8dB004029 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 10 Dec 2008 23:20:14 +0200 Received: from kobe.laptop (kobe.laptop [127.0.0.1]) by kobe.laptop (8.14.3/8.14.3) with ESMTP id mBALK8qh006791; Wed, 10 Dec 2008 23:20:08 +0200 (EET) (envelope-from keramida@freebsd.org) Received: (from keramida@localhost) by kobe.laptop (8.14.3/8.14.3/Submit) id mBALK7JK006790; Wed, 10 Dec 2008 23:20:07 +0200 (EET) (envelope-from keramida@freebsd.org) From: Giorgos Keramidas To: "Murray Stokely" References: <871vwfn418.fsf@kobe.laptop> <2a7894eb0812101310v2123a452q26b0e07630e7f209@mail.gmail.com> Date: Wed, 10 Dec 2008 23:20:07 +0200 In-Reply-To: <2a7894eb0812101310v2123a452q26b0e07630e7f209@mail.gmail.com> (Murray Stokely's message of "Wed, 10 Dec 2008 13:10:31 -0800") Message-ID: <878wqnafso.fsf@kobe.laptop> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.60 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-MailScanner-ID: mBALK8dB004029 X-Hellug-MailScanner: Found to be clean X-Hellug-MailScanner-SpamCheck: not spam, SpamAssassin (not cached, score=-4.304, required 5, autolearn=not spam, ALL_TRUSTED -1.80, AWL 0.10, BAYES_00 -2.60) X-Hellug-MailScanner-From: keramida@freebsd.org X-Spam-Status: No Cc: freebsd-doc@freebsd.org Subject: Re: [PATCH] Adding elements to wlan Handbook section 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, 10 Dec 2008 21:20:18 -0000 On Wed, 10 Dec 2008 13:10:31 -0800, "Murray Stokely" wrote: > Is the stylesheet now smart enough to only markup the first occurrence > differently? I seem to recall these could get distracting if all > instances of an acronym are replaced (either with hyperlinks to > definition, or bold, or however we are currently rendering them). All the instances of am are rendered in HTML as FOO with the current DSSSL code. We don't color or otherwise reformat either 'acronym' or '#acronym' in our current docbook.css stylesheet, so they are not distracting if the patch goes in. We might have to make DSSSL a bit smarter about what to send to the output HTML text if we start colorizing acronyms in CSS though. From owner-freebsd-doc@FreeBSD.ORG Wed Dec 10 21:21:48 2008 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DD5381065672 for ; Wed, 10 Dec 2008 21:21:48 +0000 (UTC) (envelope-from keramida@freebsd.org) Received: from igloo.linux.gr (igloo.linux.gr [62.1.205.36]) by mx1.freebsd.org (Postfix) with ESMTP id 538DB8FC12 for ; Wed, 10 Dec 2008 21:21:48 +0000 (UTC) (envelope-from keramida@freebsd.org) Received: from kobe.laptop (adsl22-219.kln.forthnet.gr [77.49.149.219]) (authenticated bits=128) by igloo.linux.gr (8.14.3/8.14.3/Debian-5) with ESMTP id mBALLcQB004062 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 10 Dec 2008 23:21:43 +0200 Received: from kobe.laptop (kobe.laptop [127.0.0.1]) by kobe.laptop (8.14.3/8.14.3) with ESMTP id mBALLcd7006800; Wed, 10 Dec 2008 23:21:38 +0200 (EET) (envelope-from keramida@freebsd.org) Received: (from keramida@localhost) by kobe.laptop (8.14.3/8.14.3/Submit) id mBALLcli006799; Wed, 10 Dec 2008 23:21:38 +0200 (EET) (envelope-from keramida@freebsd.org) From: Giorgos Keramidas To: Manolis Kiagias References: <871vwfn418.fsf@kobe.laptop> <494030B1.2080001@gmail.com> Date: Wed, 10 Dec 2008 23:21:37 +0200 In-Reply-To: <494030B1.2080001@gmail.com> (Manolis Kiagias's message of "Wed, 10 Dec 2008 23:12:17 +0200") Message-ID: <874p1bafq6.fsf@kobe.laptop> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.60 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-MailScanner-ID: mBALLcQB004062 X-Hellug-MailScanner: Found to be clean X-Hellug-MailScanner-SpamCheck: not spam, SpamAssassin (not cached, score=-4.304, required 5, autolearn=not spam, ALL_TRUSTED -1.80, AWL 0.10, BAYES_00 -2.60) X-Hellug-MailScanner-From: keramida@freebsd.org X-Spam-Status: No Cc: freebsd-doc@freebsd.org Subject: Re: [PATCH] Adding elements to wlan Handbook section 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, 10 Dec 2008 21:21:48 -0000 On Wed, 10 Dec 2008 23:12:17 +0200, Manolis Kiagias wrote: > Giorgos Keramidas wrote: >> The wireless networking section is one of those I've been translating >> lately, and I noticed that it includes *many* acronyms (AP, BSS, SSID, >> IBSS, WPA, WEP, PSK, TKIP, and so on). The acronyms are practically >> everywhere, so adding tags to them directly into CVS may not >> be a very gentle thing to do. >> >> So here it is, in diff format for your pleasure. Does anyone have >> objections to the patch attached below? >> >> [NOTE: I haven't wrapped any lines, to keep the patch more readable, but >> I know already that some of the touched lines may need a bit of wrap & >> filling after the patch goes in.] > > No objection here, but just an idea: It is also possible to use > something like: > > WEP > > when this is rendered in HTML, the text in "role" appears on > mouse-over (what most would call a tool tip). Maybe we could use this > the first time the acronym is used (except if it is already expanded > in the preceeding text of course). That sounds nice. I'll try to see where it would fit in our DSSSL formatting code, because we don't (normally) write the fully expanded form of acronyms in the SGML source now. :) From owner-freebsd-doc@FreeBSD.ORG Wed Dec 10 21:22:58 2008 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 441F91065679; Wed, 10 Dec 2008 21:22:58 +0000 (UTC) (envelope-from murray@stokely.org) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.232]) by mx1.freebsd.org (Postfix) with ESMTP id 1BC338FC17; Wed, 10 Dec 2008 21:22:58 +0000 (UTC) (envelope-from murray@stokely.org) Received: by rv-out-0506.google.com with SMTP id b25so548486rvf.43 for ; Wed, 10 Dec 2008 13:22:57 -0800 (PST) Received: by 10.141.63.20 with SMTP id q20mr871729rvk.106.1228944177740; Wed, 10 Dec 2008 13:22:57 -0800 (PST) Received: by 10.141.151.6 with HTTP; Wed, 10 Dec 2008 13:22:57 -0800 (PST) Message-ID: <2a7894eb0812101322o77b12fc9k8208f83d62481ad3@mail.gmail.com> Date: Wed, 10 Dec 2008 13:22:57 -0800 From: "Murray Stokely" To: "Giorgos Keramidas" In-Reply-To: <878wqnafso.fsf@kobe.laptop> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <871vwfn418.fsf@kobe.laptop> <2a7894eb0812101310v2123a452q26b0e07630e7f209@mail.gmail.com> <878wqnafso.fsf@kobe.laptop> Cc: freebsd-doc@freebsd.org Subject: Re: [PATCH] Adding elements to wlan Handbook section 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, 10 Dec 2008 21:22:58 -0000 In that case this looks great to me. I agree with Manolis that adding the role="definition" for the first instance of each acronym is helpful. I really thought we were already doing this in parts of the Handbook, but I may be misremembering. - Murray On Wed, Dec 10, 2008 at 1:20 PM, Giorgos Keramidas wrote: > On Wed, 10 Dec 2008 13:10:31 -0800, "Murray Stokely" wrote: >> Is the stylesheet now smart enough to only markup the first occurrence >> differently? I seem to recall these could get distracting if all >> instances of an acronym are replaced (either with hyperlinks to >> definition, or bold, or however we are currently rendering them). > > All the instances of am are rendered in HTML as > > FOO > > with the current DSSSL code. We don't color or otherwise reformat > either 'acronym' or '#acronym' in our current docbook.css stylesheet, so > they are not distracting if the patch goes in. > > We might have to make DSSSL a bit smarter about what to send to the > output HTML text if we start colorizing acronyms in CSS though. > > From owner-freebsd-doc@FreeBSD.ORG Wed Dec 10 21:32:48 2008 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3C3501065675 for ; Wed, 10 Dec 2008 21:32:48 +0000 (UTC) (envelope-from keramida@freebsd.org) Received: from igloo.linux.gr (igloo.linux.gr [62.1.205.36]) by mx1.freebsd.org (Postfix) with ESMTP id A46438FC12 for ; Wed, 10 Dec 2008 21:32:47 +0000 (UTC) (envelope-from keramida@freebsd.org) Received: from kobe.laptop (adsl22-219.kln.forthnet.gr [77.49.149.219]) (authenticated bits=128) by igloo.linux.gr (8.14.3/8.14.3/Debian-5) with ESMTP id mBALWbED004499 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 10 Dec 2008 23:32:43 +0200 Received: from kobe.laptop (kobe.laptop [127.0.0.1]) by kobe.laptop (8.14.3/8.14.3) with ESMTP id mBALWbBx007006; Wed, 10 Dec 2008 23:32:37 +0200 (EET) (envelope-from keramida@freebsd.org) Received: (from keramida@localhost) by kobe.laptop (8.14.3/8.14.3/Submit) id mBALWbHr007005; Wed, 10 Dec 2008 23:32:37 +0200 (EET) (envelope-from keramida@freebsd.org) From: Giorgos Keramidas To: "Murray Stokely" References: <871vwfn418.fsf@kobe.laptop> <2a7894eb0812101310v2123a452q26b0e07630e7f209@mail.gmail.com> <878wqnafso.fsf@kobe.laptop> <2a7894eb0812101322o77b12fc9k8208f83d62481ad3@mail.gmail.com> Date: Wed, 10 Dec 2008 23:32:36 +0200 In-Reply-To: <2a7894eb0812101322o77b12fc9k8208f83d62481ad3@mail.gmail.com> (Murray Stokely's message of "Wed, 10 Dec 2008 13:22:57 -0800") Message-ID: <87prjz67ij.fsf@kobe.laptop> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.60 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-MailScanner-ID: mBALWbED004499 X-Hellug-MailScanner: Found to be clean X-Hellug-MailScanner-SpamCheck: not spam, SpamAssassin (not cached, score=-4.299, required 5, autolearn=not spam, ALL_TRUSTED -1.80, AWL 0.10, BAYES_00 -2.60) X-Hellug-MailScanner-From: keramida@freebsd.org X-Spam-Status: No Cc: freebsd-doc@freebsd.org Subject: Re: [PATCH] Adding elements to wlan Handbook section 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, 10 Dec 2008 21:32:48 -0000 On Wed, 10 Dec 2008 13:22:57 -0800, "Murray Stokely" wrote: > In that case this looks great to me. I agree with Manolis that adding > the role="definition" for the first instance of each acronym is > helpful. I really thought we were already doing this in parts of the > Handbook, but I may be misremembering. Ah! I misunderstood Manolis then. I think I can add the role="" bits before committing this :) From owner-freebsd-doc@FreeBSD.ORG Wed Dec 10 21:36:26 2008 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 44716106564A for ; Wed, 10 Dec 2008 21:36:26 +0000 (UTC) (envelope-from sonic2000gr@gmail.com) Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.171]) by mx1.freebsd.org (Postfix) with ESMTP id C32658FC18 for ; Wed, 10 Dec 2008 21:36:25 +0000 (UTC) (envelope-from sonic2000gr@gmail.com) Received: by ug-out-1314.google.com with SMTP id 30so155936ugs.39 for ; Wed, 10 Dec 2008 13:36:24 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=YJ4t6tKBT9KxACuMvGPJMoLrQpgA3+EMQPROnO44GuA=; b=hOUsX++IaheRWSzw+pwrypS4kkOW3oKFrv24yKuSsB+k/RPlpMWvTSd1zw8+4aSgFs LRAGqnrbyHB6LZOcNDgA56gTs4/G+uGmdP/HxmMBEk9oC3MJRIQf4fiBQTkOT0rI9S3A RhHLNmBzwfbW75BLDLOYZDkp4hp/upkp7lPgQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=ro1A5BAW8T3f1F7QyduqFy+S2BDAvgbNGTKNpVHTsfqkIiz2g8Zp2Lo5uHnplQ9iaj fXSZMMXLF0zYRUCHEdULZiBORiSXSjbuoj8Q949y1lqoMAiC9thWakDrbE5JSyNAdTfK Hn6NEGdSskQ355vrU1r15caMrik3JOV0HbreA= Received: by 10.66.250.1 with SMTP id x1mr4461482ugh.4.1228944984637; Wed, 10 Dec 2008 13:36:24 -0800 (PST) Received: from atlantis.dyndns.org (athedsl-4448612.home.otenet.gr [79.129.209.84]) by mx.google.com with ESMTPS id b39sm14518117ugf.38.2008.12.10.13.36.23 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 10 Dec 2008 13:36:24 -0800 (PST) Message-ID: <49403656.4020303@gmail.com> Date: Wed, 10 Dec 2008 23:36:22 +0200 From: Manolis Kiagias User-Agent: Thunderbird 2.0.0.17 (X11/20081011) MIME-Version: 1.0 To: Murray Stokely References: <871vwfn418.fsf@kobe.laptop> <2a7894eb0812101310v2123a452q26b0e07630e7f209@mail.gmail.com> <878wqnafso.fsf@kobe.laptop> <2a7894eb0812101322o77b12fc9k8208f83d62481ad3@mail.gmail.com> In-Reply-To: <2a7894eb0812101322o77b12fc9k8208f83d62481ad3@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-doc@freebsd.org, Giorgos Keramidas Subject: Re: [PATCH] Adding elements to wlan Handbook section 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, 10 Dec 2008 21:36:26 -0000 Murray Stokely wrote: > In that case this looks great to me. I agree with Manolis that adding > the role="definition" for the first instance of each acronym is > helpful. I really thought we were already doing this in parts of the > Handbook, but I may be misremembering. > > - Murray > > I've seen it in the Handbook, but in very few parts. It is also rendered very nicely, and is not at all distracting. (A lightweight, dotted underline). See here for an example: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/network-ftp.html From owner-freebsd-doc@FreeBSD.ORG Thu Dec 11 18:23:07 2008 Return-Path: Delivered-To: doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 534FF1065672; Thu, 11 Dec 2008 18:23:07 +0000 (UTC) (envelope-from r.c.ladan@gmail.com) Received: from mail-gx0-f12.google.com (mail-gx0-f12.google.com [209.85.217.12]) by mx1.freebsd.org (Postfix) with ESMTP id 5F90B8FC23; Thu, 11 Dec 2008 18:23:06 +0000 (UTC) (envelope-from r.c.ladan@gmail.com) Received: by gxk5 with SMTP id 5so550547gxk.19 for ; Thu, 11 Dec 2008 10:23:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type:references; bh=26DQY4EccNdBzmHU69KjaIqA2PjBa114VraSarcAQaY=; b=jZMh2v0WZ277mZh0X4gBy/xWn6CVxoMcdSqR2kvCB/xuOWulTzbcDViH4EHr54yG7z aZUwRrF+D4HlfSvZRX5dq3g0+xoFOwaiNwWASdPFNQGP4QqztRr8gWWm3Ha/iA0Up7ta KLiTs/yFi8wAilJHGpbm9rs/yuE/04qaay4uE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:references; b=mj2eFITMYZqbfO++NTCKcBSf9dRkKSSbEUUQkIeHH4RAN63Cq/rqfTgsYq54qWwx2W VM7cQ7tp/5hftRdeMj2jV4//73aQ/LU4IEEEAy5qLpV7ueEVEaOsaUtMbxeT1/DiTcJL OZ2WU3ZIECYWJoqGOvjo6QuZdSp7+lxQn9qFM= Received: by 10.150.97.19 with SMTP id u19mr2452721ybb.135.1229019784944; Thu, 11 Dec 2008 10:23:04 -0800 (PST) Received: by 10.150.225.9 with HTTP; Thu, 11 Dec 2008 10:23:04 -0800 (PST) Message-ID: Date: Thu, 11 Dec 2008 19:23:04 +0100 From: "Rene Ladan" To: "Gabor PALI" In-Reply-To: <49184BDB.5070707@FreeBSD.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_9770_23187709.1229019784885" References: <49174B71.9080800@gmail.com> <49184BDB.5070707@FreeBSD.org> Cc: doc@freebsd.org Subject: Re: [RFC] Committers guide: replace CVS by SVN where appropiate 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, 11 Dec 2008 18:23:07 -0000 ------=_Part_9770_23187709.1229019784885 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline 2008/11/10 Gabor PALI : > Hello, > > Rene Ladan wrote: >> the current version of the Committers Guide (1.278 2008-08-16 21:42:35 pgj) >> uses CVS for everything, but as of last June the src repository uses SVN. > [...] > I also wanted to revise some other sections of the committers-guide, for > example (without the claim of completeness): > [..] > - I am not sure that "A Free 4-CD Set or DVD Subscription" is still > available for committers. > Doesn't seem to be the case (at least for 6.4) :( I've created the first (trivial) patch for this. I'll create more patches for different things (nits, cvs->svn, who's who, ...) Regards, Rene -- http://www.rene-ladan.nl/ GPG fingerprint = E738 5471 D185 7013 0EE0 4FC8 3C1D 6F83 12E1 84F6 (subkeys.pgp.net) ------=_Part_9770_23187709.1229019784885 Content-Type: text/x-patch; name=cg-nocd.diff Content-Transfer-Encoding: base64 X-Attachment-Id: f_folqmuec0 Content-Disposition: attachment; filename=cg-nocd.diff LS0tIGNvbW1pdHRlcnNndWlkZS0xLjI3OS5zZ21sCTIwMDgtMTItMDggMjM6Mjg6MDQuMDAwMDAw MDAwICswMTAwCisrKyBjZy1ub2NkLnNnbWwJMjAwOC0xMi0xMSAwMDoyODozNC4wMDAwMDAwMDAg KzAxMDAKQEAgLTMzMDksMjAgKzMzMDgsNiBAQAogCSAgICBhIGJ1c3kgbWFjaGluZS48L3BhcmE+ CiAJPC9saXN0aXRlbT4KICAgICAgIDwvdmFybGlzdGVudHJ5PgotCi0gICAgICA8dmFybGlzdGVu dHJ5PgotCTx0ZXJtPkEgRnJlZSA0LUNEIFNldCBvciBEVkQgU3Vic2NyaXB0aW9uPC90ZXJtPgot Ci0JPGxpc3RpdGVtPgotCSAgPHBhcmE+PHVsaW5rIHVybD0iaHR0cDovL3d3dy5mcmVlYnNkbWFs bC5jb20iPkZyZWVCU0QgTWFsbCwKLQkgICAgSW5jLjwvdWxpbms+IG9mZmVycyBhIGZyZWUgc3Vi c2NyaXB0aW9uIG9mIHRoZSA0LUNEIHNldCBvcgotCSAgICB0aGUgRFZEIHByb2R1Y3QgdG8gYWxs IEZyZWVCU0QgY29tbWl0dGVycy4gIEluZm9ybWF0aW9uIGFib3V0IGhvdwotCSAgICB0byBvYnRh aW4geW91ciBmcmVlIG1lZGlhIGlzIG1haWxlZCB0bwotCSAgICA8ZW1haWw+ZGV2ZWxvcGVyc0BG cmVlQlNELm9yZzwvZW1haWw+IGZvbGxvd2luZyBlYWNoIG1ham9yCi0JICAgIHJlbGVhc2UuPC9w YXJhPgotCTwvbGlzdGl0ZW0+Ci0gICAgICA8L3Zhcmxpc3RlbnRyeT4KLQogICAgIDwvdmFyaWFi bGVsaXN0PgogICA8L3NlY3QxPgogCg== ------=_Part_9770_23187709.1229019784885-- From owner-freebsd-doc@FreeBSD.ORG Thu Dec 11 19:31:32 2008 Return-Path: Delivered-To: doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 826EA1065672 for ; Thu, 11 Dec 2008 19:31:32 +0000 (UTC) (envelope-from sonic2000gr@gmail.com) Received: from mail-ew0-f21.google.com (mail-ew0-f21.google.com [209.85.219.21]) by mx1.freebsd.org (Postfix) with ESMTP id E348F8FC14 for ; Thu, 11 Dec 2008 19:31:31 +0000 (UTC) (envelope-from sonic2000gr@gmail.com) Received: by ewy14 with SMTP id 14so1683183ewy.19 for ; Thu, 11 Dec 2008 11:31:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=EoRLrKtUSIBQQnpef9wPDDEyBJFmg1MajJVwkTVVeNE=; b=fd1KTh8pPIbBDcI7nxfQz8kzc+FdHD1/FusDDEv6KZy5cVUH23VjW4HJtorKkMde6V 9ZQK/5wMa8Fub+bO8QV4M8dQT+FjkC65+UtsUdun8wh/5M6ncTUyawt0OhIQhcIXOZXw X1E1Z6I/5Alw6qWSygnqExU205QtZHixhCV6o= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=jte6wDndLbByb4bl9KxFg5gL7fcCXUkmH5SdCvc4xMYwbKzo8YYv+VMhaqkvQu9xv/ aN9dCKprXH6B9x+IwHEkuLuFr5rf4EYlRbjyCeTIxc0zmLFWkoMtlw3MEI6XZRoxNEEr wP5BOa/DdKtz8ppX2pIT7GNHmbtQ3DB1x0emU= Received: by 10.67.106.13 with SMTP id i13mr5257656ugm.7.1229023890655; Thu, 11 Dec 2008 11:31:30 -0800 (PST) Received: from atlantis.dyndns.org (athedsl-4448612.home.otenet.gr [79.129.209.84]) by mx.google.com with ESMTPS id q40sm17142576ugc.1.2008.12.11.11.31.29 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 11 Dec 2008 11:31:30 -0800 (PST) Message-ID: <49416A90.3020300@gmail.com> Date: Thu, 11 Dec 2008 21:31:28 +0200 From: Manolis Kiagias User-Agent: Thunderbird 2.0.0.17 (X11/20081011) MIME-Version: 1.0 To: Rene Ladan References: <49174B71.9080800@gmail.com> <49184BDB.5070707@FreeBSD.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-7 Content-Transfer-Encoding: 7bit Cc: Gabor PALI , doc@freebsd.org Subject: Re: [RFC] Committers guide: replace CVS by SVN where appropiate 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, 11 Dec 2008 19:31:32 -0000 Rene Ladan wrote: > 2008/11/10 Gabor PALI : > >> Hello, >> >> Rene Ladan wrote: >> >>> the current version of the Committers Guide (1.278 2008-08-16 21:42:35 pgj) >>> uses CVS for everything, but as of last June the src repository uses SVN. >>> > [...] > > >> I also wanted to revise some other sections of the committers-guide, for >> example (without the claim of completeness): >> >> > [..] > >> - I am not sure that "A Free 4-CD Set or DVD Subscription" is still >> available for committers. >> >> > Doesn't seem to be the case (at least for 6.4) :( > True. But then, it is better to buy them and support the Project anyway :) > I've created the first (trivial) patch for this. I'll create more patches > for different things (nits, cvs->svn, who's who, ...) > > Regards, > Rene > I think it is alright to go ahead with this... Manolis From owner-freebsd-doc@FreeBSD.ORG Fri Dec 12 02:02:07 2008 Return-Path: Delivered-To: freebsd-doc@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9ABD7106564A; Fri, 12 Dec 2008 02:02:07 +0000 (UTC) (envelope-from trhodes@FreeBSD.org) Received: from pittgoth.com (pittgoth.com [205.134.163.206]) by mx1.freebsd.org (Postfix) with ESMTP id 604038FC12; Fri, 12 Dec 2008 02:02:07 +0000 (UTC) (envelope-from trhodes@FreeBSD.org) Received: from localhost.fbsdsecure.org (net-ix.gw.ai.net [205.134.160.6]) (authenticated bits=0) by pittgoth.com (8.14.3/8.14.3) with ESMTP id mBC226ks003740 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 11 Dec 2008 21:02:06 -0500 (EST) (envelope-from trhodes@FreeBSD.org) Date: Thu, 11 Dec 2008 21:01:58 -0500 From: Tom Rhodes To: Giorgos Keramidas Message-Id: <20081211210158.5a37ba32.trhodes@FreeBSD.org> In-Reply-To: <871vwfn418.fsf@kobe.laptop> References: <871vwfn418.fsf@kobe.laptop> X-Mailer: Sylpheed version 1.0.6 (GTK+ 1.2.10; i386-portbld-freebsd8.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-doc@FreeBSD.org Subject: Re: [PATCH] Adding elements to wlan Handbook section 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, 12 Dec 2008 02:02:07 -0000 On Wed, 10 Dec 2008 22:55:47 +0200 Giorgos Keramidas wrote: > The wireless networking section is one of those I've been translating > lately, and I noticed that it includes *many* acronyms (AP, BSS, SSID, > IBSS, WPA, WEP, PSK, TKIP, and so on). The acronyms are practically > everywhere, so adding tags to them directly into CVS may not > be a very gentle thing to do. > > So here it is, in diff format for your pleasure. Does anyone have > objections to the patch attached below? > > [NOTE: I haven't wrapped any lines, to keep the patch more readable, but > I know already that some of the touched lines may need a bit of wrap & > filling after the patch goes in.] Looks good to me. -- Tom Rhodes From owner-freebsd-doc@FreeBSD.ORG Fri Dec 12 02:30:30 2008 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0938B1065670 for ; Fri, 12 Dec 2008 02:30:30 +0000 (UTC) (envelope-from keramida@freebsd.org) Received: from igloo.linux.gr (igloo.linux.gr [62.1.205.36]) by mx1.freebsd.org (Postfix) with ESMTP id 8ED9C8FC08 for ; Fri, 12 Dec 2008 02:30:29 +0000 (UTC) (envelope-from keramida@freebsd.org) Received: from kobe.laptop (adsl179-214.kln.forthnet.gr [77.49.0.214]) (authenticated bits=128) by igloo.linux.gr (8.14.3/8.14.3/Debian-5) with ESMTP id mBC2UJpc031453 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 12 Dec 2008 04:30:25 +0200 Received: from kobe.laptop (kobe.laptop [127.0.0.1]) by kobe.laptop (8.14.3/8.14.3) with ESMTP id mBC2UIiD005574; Fri, 12 Dec 2008 04:30:18 +0200 (EET) (envelope-from keramida@freebsd.org) Received: (from keramida@localhost) by kobe.laptop (8.14.3/8.14.3/Submit) id mBC2UIQq005573; Fri, 12 Dec 2008 04:30:18 +0200 (EET) (envelope-from keramida@freebsd.org) From: Giorgos Keramidas To: "Murray Stokely" References: <871vwfn418.fsf@kobe.laptop> <2a7894eb0812101310v2123a452q26b0e07630e7f209@mail.gmail.com> <878wqnafso.fsf@kobe.laptop> <2a7894eb0812101322o77b12fc9k8208f83d62481ad3@mail.gmail.com> Date: Fri, 12 Dec 2008 04:30:18 +0200 In-Reply-To: <2a7894eb0812101322o77b12fc9k8208f83d62481ad3@mail.gmail.com> (Murray Stokely's message of "Wed, 10 Dec 2008 13:22:57 -0800") Message-ID: <87k5a63z2d.fsf@kobe.laptop> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.60 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-MailScanner-ID: mBC2UJpc031453 X-Hellug-MailScanner: Found to be clean X-Hellug-MailScanner-SpamCheck: not spam, SpamAssassin (not cached, score=-4.296, required 5, autolearn=not spam, ALL_TRUSTED -1.80, AWL 0.10, BAYES_00 -2.60) X-Hellug-MailScanner-From: keramida@freebsd.org X-Spam-Status: No Cc: freebsd-doc@freebsd.org Subject: Re: [PATCH] Adding elements to wlan Handbook section 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, 12 Dec 2008 02:30:30 -0000 On Wed, 10 Dec 2008 13:22:57 -0800, "Murray Stokely" wrote: > In that case this looks great to me. I agree with Manolis that adding > the role="definition" for the first instance of each acronym is > helpful. I really thought we were already doing this in parts of the > Handbook, but I may be misremembering. I started adding a role="" at the first instance of each WLAN-specific acronym and I noticed that I was typing the same expansions again and again all over the place. This is a bit error prone, so it seemed more natural to add a ``set of "standard" acronym expansions''. Does something like this look useful for other sorts of acronyms too? %%% # HG changeset patch # User keramida # Date 1229048467 -7200 # Node ID c8a6e126654fba80e290d6c93568d551a0c10473 # Parent 669337240ff11759179bde192d61b69a6be769ea Add support for a set of 'standard' acronym expansions. I got a bit sick of typing role="the same text" all the time, and this gives us an easy point to redefine an acronym expansion without having to crawl the entire doc/ tree, so here it is. diff -r 669337240ff1 -r c8a6e126654f share/sgml/acronyms.ent --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/share/sgml/acronyms.ent Fri Dec 12 04:21:07 2008 +0200 @@ -0,0 +1,21 @@ + + + + + + + + + + + + diff -r 669337240ff1 -r c8a6e126654f share/sgml/articles.ent --- a/share/sgml/articles.ent Wed Dec 10 22:51:06 2008 +0200 +++ b/share/sgml/articles.ent Fri Dec 12 04:21:07 2008 +0200 @@ -8,6 +8,8 @@ %man; %freebsd; + +%acronyms; %authors; diff -r 669337240ff1 -r c8a6e126654f share/sgml/books.ent --- a/share/sgml/books.ent Wed Dec 10 22:51:06 2008 +0200 +++ b/share/sgml/books.ent Fri Dec 12 04:21:07 2008 +0200 @@ -10,6 +10,8 @@ %bookinfo; %freebsd; + +%acronyms; %authors; diff -r 669337240ff1 -r c8a6e126654f share/sgml/catalog --- a/share/sgml/catalog Wed Dec 10 22:51:06 2008 +0200 +++ b/share/sgml/catalog Fri Dec 12 04:21:07 2008 +0200 @@ -23,6 +23,9 @@ PUBLIC "-//FreeBSD//DOCUMENT DocBook Language Neutral Stylesheet//EN" "freebsd.dsl" +PUBLIC "-//FreeBSD//ENTITIES DocBook FreeBSD Acronyms Entity Set//EN" + "acronyms.ent" + PUBLIC "-//FreeBSD//ENTITIES DocBook FreeBSD Articles Entity Set//EN" "articles.ent" %%% I have only added a few acronym expansions now, but this already makes it possible to write things like: Using WEP encryption is not really safe anymore, but a lot of people use it anyway. We can probably go a step further and define: WEP'> but I wanted to ask the rest of doc@ first what they think about a list of acronym expansions that is shared like this? If yes, which form of entity would you prefer to have? One that expands to the "Name of the Acronym" or one that expands to the full element? Giorgos From owner-freebsd-doc@FreeBSD.ORG Fri Dec 12 02:51:22 2008 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 9A35D1065672 for ; Fri, 12 Dec 2008 02:51:22 +0000 (UTC) (envelope-from keramida@freebsd.org) Received: from igloo.linux.gr (igloo.linux.gr [62.1.205.36]) by mx1.freebsd.org (Postfix) with ESMTP id EA0348FC25 for ; Fri, 12 Dec 2008 02:51:21 +0000 (UTC) (envelope-from keramida@freebsd.org) Received: from kobe.laptop (adsl179-214.kln.forthnet.gr [77.49.0.214]) (authenticated bits=128) by igloo.linux.gr (8.14.3/8.14.3/Debian-5) with ESMTP id mBC2pCc0032167 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 12 Dec 2008 04:51:17 +0200 Received: from kobe.laptop (kobe.laptop [127.0.0.1]) by kobe.laptop (8.14.3/8.14.3) with ESMTP id mBC2pBL1005699; Fri, 12 Dec 2008 04:51:11 +0200 (EET) (envelope-from keramida@freebsd.org) Received: (from keramida@localhost) by kobe.laptop (8.14.3/8.14.3/Submit) id mBC2pBLe005698; Fri, 12 Dec 2008 04:51:11 +0200 (EET) (envelope-from keramida@freebsd.org) From: Giorgos Keramidas To: Manolis Kiagias References: <871vwfn418.fsf@kobe.laptop> <2a7894eb0812101310v2123a452q26b0e07630e7f209@mail.gmail.com> <878wqnafso.fsf@kobe.laptop> <2a7894eb0812101322o77b12fc9k8208f83d62481ad3@mail.gmail.com> <49403656.4020303@gmail.com> Date: Fri, 12 Dec 2008 04:51:11 +0200 In-Reply-To: <49403656.4020303@gmail.com> (Manolis Kiagias's message of "Wed, 10 Dec 2008 23:36:22 +0200") Message-ID: <8763lq14yo.fsf@kobe.laptop> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.60 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-MailScanner-ID: mBC2pCc0032167 X-Hellug-MailScanner: Found to be clean X-Hellug-MailScanner-SpamCheck: not spam, SpamAssassin (not cached, score=-4.295, required 5, autolearn=not spam, ALL_TRUSTED -1.80, AWL 0.10, BAYES_00 -2.60) X-Hellug-MailScanner-From: keramida@freebsd.org X-Spam-Status: No Cc: freebsd-doc@freebsd.org Subject: Re: [PATCH] Adding elements to wlan Handbook section 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, 12 Dec 2008 02:51:22 -0000 On Wed, 10 Dec 2008 23:36:22 +0200, Manolis Kiagias wrote: > I've seen it in the Handbook, but in very few parts. It is also rendered > very nicely, and is not at all distracting. (A lightweight, dotted > underline). See here for an example: > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/network-ftp.html That looks good. I've started pushing to hg.hellug.gr some commits that add this sort of role="" attribute to the wlan section :-) Manolis, I have a question that is mostly a style issue though. There are some compound acronyms in the wlan section, i.e. "WPA-TLS". Would you prefer a separate for "WPA" and "TLS" like WPA-TLS or a single element like WPA-TLS The first seems more logical, and it would fit nicely with the set of acronym entities (acronyms.ent) I proposed in another email of the thread (eg. we won't have to introduce a new, special entity for &acronym.wlan.wpa-tls; but we can reuse the WPA and TLS entities). I am not sure if it would result in aesthetically pleasing output when the dotted underlines appear in separate words though. From owner-freebsd-doc@FreeBSD.ORG Fri Dec 12 05:28:59 2008 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8B9581065678 for ; Fri, 12 Dec 2008 05:28:59 +0000 (UTC) (envelope-from sonic2000gr@gmail.com) Received: from mail-ew0-f21.google.com (mail-ew0-f21.google.com [209.85.219.21]) by mx1.freebsd.org (Postfix) with ESMTP id E69398FC12 for ; Fri, 12 Dec 2008 05:28:58 +0000 (UTC) (envelope-from sonic2000gr@gmail.com) Received: by ewy14 with SMTP id 14so1849561ewy.19 for ; Thu, 11 Dec 2008 21:28:57 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=BShnJhjz980m22wT1QTzgaYzkbPfy6GafQmlBtYgcQ4=; b=CAVkyKn4Pqys4bYgvcBYaGlMwpX+yVU9nSucq2F5c+HIVgx0LRuol9tjo5x85333oE dDuqf0LKAnIwNox8i+44lA7wmJH//Rbv/KLjNu9bb3ZfcEIvy9NcqZ45ETT3CdsdANLr 5YVtRMCp5kmOElk0aTovXnfR43YwIw2MTHKCM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=VU7agpjLU9O9ZhrizJ4g8uKXdIB/BU4ez3sga6E+1YSaoykhhLKaoKb3jmzBvbKM4w 0ezscu3eK4U4QOrTYd5DYRTo6eyBYk9G1fVZQtuRfLACh/9UbZXgqtF/5BfWrpJ+VVck tO6EW0Voc4DZ+MLZaHEk7l5pYNhtr9BMB4VyE= Received: by 10.210.66.1 with SMTP id o1mr1470438eba.0.1229059737784; Thu, 11 Dec 2008 21:28:57 -0800 (PST) Received: from atlantis.dyndns.org (athedsl-323937.home.otenet.gr [85.72.120.255]) by mx.google.com with ESMTPS id 1sm5071261nfv.9.2008.12.11.21.28.54 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 11 Dec 2008 21:28:57 -0800 (PST) Message-ID: <4941F694.3040600@gmail.com> Date: Fri, 12 Dec 2008 07:28:52 +0200 From: Manolis Kiagias User-Agent: Thunderbird 2.0.0.17 (X11/20081011) MIME-Version: 1.0 To: Giorgos Keramidas References: <871vwfn418.fsf@kobe.laptop> <2a7894eb0812101310v2123a452q26b0e07630e7f209@mail.gmail.com> <878wqnafso.fsf@kobe.laptop> <2a7894eb0812101322o77b12fc9k8208f83d62481ad3@mail.gmail.com> <49403656.4020303@gmail.com> <8763lq14yo.fsf@kobe.laptop> In-Reply-To: <8763lq14yo.fsf@kobe.laptop> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-doc@freebsd.org Subject: Re: [PATCH] Adding elements to wlan Handbook section 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, 12 Dec 2008 05:28:59 -0000 Giorgos Keramidas wrote: > On Wed, 10 Dec 2008 23:36:22 +0200, Manolis Kiagias wrote: > >> I've seen it in the Handbook, but in very few parts. It is also rendered >> very nicely, and is not at all distracting. (A lightweight, dotted >> underline). See here for an example: >> >> http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/network-ftp.html >> > > That looks good. I've started pushing to hg.hellug.gr some commits that > add this sort of role="" attribute to the wlan section :-) > > Manolis, I have a question that is mostly a style issue though. > > There are some compound acronyms in the wlan section, i.e. "WPA-TLS". > Would you prefer a separate for "WPA" and "TLS" like > > WPA- role="Transport Layer Security">TLS > > or a single element like > > WPA-TLS > > The first seems more logical, and it would fit nicely with the set of > acronym entities (acronyms.ent) I proposed in another email of the > thread (eg. we won't have to introduce a new, special entity for > &acronym.wlan.wpa-tls; but we can reuse the WPA and TLS entities). I am > not sure if it would result in aesthetically pleasing output when the > dotted underlines appear in separate words though. > > > I agree that the first seems more logical and more effective as the entities can be reused. However the difference is really very small, so go along with the one you prefer. As for the dotted lines, they are so subtle anyway that it won't make much of a difference if they appear in separate words. From owner-freebsd-doc@FreeBSD.ORG Fri Dec 12 07:17:15 2008 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E8439106564A for ; Fri, 12 Dec 2008 07:17:14 +0000 (UTC) (envelope-from keramida@ceid.upatras.gr) Received: from igloo.linux.gr (igloo.linux.gr [62.1.205.36]) by mx1.freebsd.org (Postfix) with ESMTP id D2F898FC1B for ; Fri, 12 Dec 2008 07:17:13 +0000 (UTC) (envelope-from keramida@ceid.upatras.gr) Received: from kobe.laptop (adsl179-214.kln.forthnet.gr [77.49.0.214]) (authenticated bits=128) by igloo.linux.gr (8.14.3/8.14.3/Debian-5) with ESMTP id mBC6x3ED014033 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 12 Dec 2008 08:59:09 +0200 Received: from kobe.laptop (kobe.laptop [127.0.0.1]) by kobe.laptop (8.14.3/8.14.3) with ESMTP id mBC6x3Sp008943; Fri, 12 Dec 2008 08:59:03 +0200 (EET) (envelope-from keramida@ceid.upatras.gr) Received: (from keramida@localhost) by kobe.laptop (8.14.3/8.14.3/Submit) id mBC6x2Mn008942; Fri, 12 Dec 2008 08:59:02 +0200 (EET) (envelope-from keramida@ceid.upatras.gr) From: Giorgos Keramidas To: "Murray Stokely" References: <871vwfn418.fsf@kobe.laptop> <2a7894eb0812101310v2123a452q26b0e07630e7f209@mail.gmail.com> <878wqnafso.fsf@kobe.laptop> <2a7894eb0812101322o77b12fc9k8208f83d62481ad3@mail.gmail.com> <87k5a63z2d.fsf@kobe.laptop> Date: Fri, 12 Dec 2008 08:59:02 +0200 In-Reply-To: <87k5a63z2d.fsf@kobe.laptop> (Giorgos Keramidas's message of "Fri, 12 Dec 2008 04:30:18 +0200") Message-ID: <87y6ylg9qh.fsf@kobe.laptop> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.60 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-MailScanner-ID: mBC6x3ED014033 X-Hellug-MailScanner: Found to be clean X-Hellug-MailScanner-SpamCheck: not spam, SpamAssassin (not cached, score=-3.859, required 5, autolearn=not spam, ALL_TRUSTED -1.80, AWL 0.54, BAYES_00 -2.60) X-Hellug-MailScanner-From: keramida@ceid.upatras.gr X-Spam-Status: No Cc: freebsd-doc@freebsd.org Subject: Re: [PATCH] Adding elements to wlan Handbook section 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, 12 Dec 2008 07:17:15 -0000 On Fri, 12 Dec 2008 04:30:18 +0200, Giorgos Keramidas wrote: > On Wed, 10 Dec 2008 13:22:57 -0800, "Murray Stokely" wrote: >> In that case this looks great to me. I agree with Manolis that adding >> the role="definition" for the first instance of each acronym is >> helpful. I really thought we were already doing this in parts of the >> Handbook, but I may be misremembering. > > I started adding a role="" at the first instance of each WLAN-specific > acronym and I noticed that I was typing the same expansions again and > again all over the place. This is a bit error prone, so it seemed more > natural to add a ``set of "standard" acronym expansions''. > > Does something like this look useful for other sorts of acronyms too? Here is the full patch, including the role="" attributes for the wireless networking section. If there are no serious objections, I'll commit this in 1-2 days :) %%% diff -r 1649440b3588 -r 56b69b866c6f en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml --- a/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml Fri Dec 12 06:06:03 2008 +0000 +++ b/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml Fri Dec 12 08:37:20 2008 +0200 @@ -21,7 +21,7 @@ - How to set up IEEE 802.11 and &bluetooth; devices. + How to set up IEEE 802.11 and &bluetooth; devices. @@ -700,7 +700,8 @@ Wireless Networking Basics - Most wireless networks are based on the IEEE 802.11 + Most wireless networks are based on + the IEEE 802.11 standards. A basic wireless network consists of multiple stations communicating with radios that broadcast in either the 2.4GHz or 5GHz band (though this varies according to the @@ -710,19 +711,19 @@ 802.11 networks are organized in two ways: in infrastructure mode one station acts as a master with all the other stations associating to it; the - network is known as a BSS and the master station is termed an - access point (AP). In a BSS all communication passes through - the AP; even when one station wants to communicate with - another wireless station messages must go through the AP. In + network is known as a BSS and the master station is termed an + access point (AP). In a BSS all communication passes through + the AP; even when one station wants to communicate with + another wireless station messages must go through the AP. In the second form of network there is no master and stations - communicate directly. This form of network is termed an IBSS + communicate directly. This form of network is termed an IBSS and is commonly known as an ad-hoc network. 802.11 networks were first deployed in the 2.4GHz band - using protocols defined by the IEEE 802.11 and 802.11b + using protocols defined by the IEEE 802.11 and 802.11b standard. These specifications include the operating - frequencies, MAC layer characteristics including framing and + frequencies, MAC layer characteristics including framing and transmission rates (communication can be done at various rates). Later the 802.11a standard defined operation in the 5GHz band, including different signalling mechanisms and @@ -734,51 +735,52 @@ Separate from the underlying transmission techniques 802.11 networks have a variety of security mechanisms. The original 802.11 specifications defined a simple security - protocol called WEP. This protocol uses a fixed pre-shared key + protocol called WEP. This protocol uses a fixed pre-shared key and the RC4 cryptographic cipher to encode data transmitted on a network. Stations must all agree on the fixed key in order to communicate. This scheme was shown to be easily broken and is now rarely used except to discourage transient users from joining networks. Current security practice is given by the - IEEE 802.11i specification that defines new cryptographic + IEEE 802.11i specification that defines new cryptographic ciphers and an additional protocol to authenticate stations to an access point and exchange keys for doing data communication. Further, cryptographic keys are periodically refreshed and there are mechanisms for detecting intrusion attempts (and for countering intrusion attempts). Another security protocol specification commonly used in wireless - networks is termed WPA. This was a precursor to 802.11i + networks is termed WPA. This was a precursor to 802.11i defined by an industry group as an interim measure while - waiting for 802.11i to be ratified. WPA specifies a subset of + waiting for 802.11i to be ratified. WPA specifies a subset of the requirements found in 802.11i and is designed for - implementation on legacy hardware. Specifically WPA requires - only the TKIP cipher that is derived from the original WEP - cipher. 802.11i permits use of TKIP but also requires support - for a stronger cipher, AES-CCM, for encrypting data. (The AES - cipher was not required in WPA because it was deemed too + implementation on legacy hardware. Specifically WPA requires + only the TKIP cipher that is derived from the original WEP + cipher. 802.11i permits use of TKIP but also requires support + for a stronger cipher, AES-CCM, for encrypting data. (The AES + cipher was not required in WPA because it was deemed too computationally costly to be implemented on legacy hardware.) Other than the above protocol standards the other important standard to be aware of is 802.11e. This defines protocols for deploying multi-media applications such as - streaming video and voice over IP (VoIP) in an 802.11 network. + streaming video and voice over IP (VoIP) in an 802.11 network. Like 802.11i, 802.11e also has a precursor specification - termed WME (later renamed WMM) that has been defined by an + termed WME + (later renamed WMM) that has been defined by an industry group as a subset of 802.11e that can be deployed now to enable multi-media applications while waiting for the final ratification of 802.11e. The most important thing to know - about 802.11e and WME/WMM is that it enables prioritized + about 802.11e and WME/WMM is that it enables prioritized traffic use of a wireless network through Quality of Service (QoS) protocols and enhanced media access protocols. Proper implementation of these protocols enable high speed bursting of data and prioritized traffic flow. Since the 6.0 version, &os; supports networks that operate - using 802.11a, 802.11b, and 802.11g. The WPA and 802.11i + using 802.11a, 802.11b, and 802.11g. The WPA and 802.11i security protocols are likewise supported (in conjunction with any of 11a, 11b, and 11g) and QoS and traffic prioritization - required by the WME/WMM protocols are supported for a limited + required by the WME/WMM protocols are supported for a limited set of wireless devices. @@ -901,10 +903,10 @@ Infrastructure Mode - The infrastructure mode or BSS mode is the mode that is + The infrastructure mode or BSS mode is the mode that is typically used. In this mode, a number of wireless access points are connected to a wired network. Each wireless - network has its own name, this name is called the SSID of the + network has its own name, this name is called the SSID of the network. Wireless clients connect to the wireless access points. @@ -935,7 +937,7 @@ The output of a scan request lists each BSS/IBSS network found. Beside the name of the network, SSID, we find the - BSSID which is the MAC address of the + BSSID which is the MAC address of the access point. The CAPS field identifies the type of each network and the capabilities of the stations operating there: @@ -945,9 +947,9 @@ E - Extended Service Set (ESS). Indicates that the + Extended Service Set (ESS). Indicates that the station is part of an infrastructure network (in - contrast to an IBSS/ad-hoc network). + contrast to an IBSS/ad-hoc network). @@ -955,8 +957,8 @@ I - IBSS/ad-hoc network. Indicates that the station - is part of an ad-hoc network (in contrast to an ESS + IBSS/ad-hoc network. Indicates that the station + is part of an ad-hoc network (in contrast to an ESS network). @@ -966,10 +968,12 @@ Privacy. Data confidentiality is required for - all data frames exchanged within the BSS. This means - that this BSS requires the station to use - cryptographic means such as WEP, TKIP or AES-CCMP to - encrypt/decrypt data frames being exchanged with + all data frames exchanged within the BSS. This means + that this BSS requires the station to use + cryptographic means such as WEP, + TKIP or + AES-CCMP + to encrypt/decrypt data frames being exchanged with others. @@ -1037,16 +1041,17 @@ If there are multiple access points and you want to select a specific one, you can select it by its - SSID: + SSID: ifconfig_ath0="ssid your_ssid_here DHCP" In an environment where there are multiple access - points with the same SSID (often done to simplify + points with the same SSID (often done to simplify roaming) it may be necessary to associate to one specific device. In this case you can also specify the - BSSID of the access point (you can also leave off the - SSID): + BSSID + of the access point (you can also leave off the + SSID): ifconfig_ath0="ssid your_ssid_here bssid xx:xx:xx:xx:xx:xx DHCP" @@ -1084,16 +1089,20 @@ Other schemes require cryptographic handshakes be completed before data traffic can flow; either using pre-shared keys or secrets, or more complex schemes that - involve backend services such as RADIUS. Most users + involve backend services such as + RADIUS. + Most users will use open authentication which is the default - setting. Next most common setup is WPA-PSK, also known - as WPA Personal, which is described WPA-PSK, + also known + as WPA Personal, which is described below. If you have an &apple; &airport; Extreme base station for an access point you may need to configure - shared-key authentication together with a WEP key. + shared-key authentication together with a WEP key. This can be done in the /etc/rc.conf file or using the &man.wpa.supplicant.8; program. If you have a single @@ -1103,12 +1112,12 @@ ifconfig_ath0="authmode shared wepmode on weptxkey 1 wepkey 01234567 DHCP" In general shared key authentication is to be - avoided because it uses the WEP key material in a + avoided because it uses the WEP key material in a highly-constrained manner making it even easier to - crack the key. If WEP must be used (e.g., for + crack the key. If WEP must be used (e.g., for compatibility with legacy devices) it is better to use - WEP with open authentication. More - information regarding WEP can be found in the WEP with open authentication. More + information regarding WEP can be found in the . @@ -1119,7 +1128,7 @@ Once you have selected an access point and set the authentication parameters, you will have to get an IP address to communicate. Most of time you will obtain - your wireless IP address via DHCP. To achieve that, + your wireless IP address via DHCP. To achieve that, simply edit /etc/rc.conf and add DHCP to the configuration for your device as shown in various examples above: @@ -1149,7 +1158,7 @@ are connected to the wireless network (to the dlinkap network in our case). The bssid 00:13:46:49:41:76 part is the - MAC address of your access point; the + MAC address of your access point; the authmode line informs you that the communication is not encrypted (OPEN). @@ -1159,7 +1168,8 @@ Static IP Address In the case you cannot obtain an IP address from a - DHCP server, you can set a fixed IP address. Replace + DHCP + server, you can set a fixed IP address. Replace the DHCP keyword shown above with the address information. Be sure to retain any other parameters you have set up for selecting an access @@ -1172,34 +1182,37 @@ WPA - WPA (Wi-Fi Protected Access) is a security protocol + WPA (Wi-Fi Protected Access) is a security protocol used together with 802.11 networks to address the lack of - proper authentication and the weakness of WEP. WPA leverages + proper authentication and the weakness of + WEP. + WPA leverages the 802.1X authentication protocol and uses one of several - ciphers instead of WEP for data integrity. The only - cipher required by WPA is TKIP (Temporary Key Integrity + ciphers instead of WEP for data integrity. The only + cipher required by WPA is TKIP (Temporary Key Integrity Protocol) which is a cipher that extends the basic RC4 - cipher used by WEP by adding integrity checking, tamper + cipher used by WEP by adding integrity checking, tamper detection, and measures for responding to any detected - intrusions. TKIP is designed to work on legacy hardware + intrusions. TKIP is designed to work on legacy hardware with only software modification; it represents a compromise that improves security but is still not - entirely immune to attack. WPA also specifies the - AES-CCMP cipher as an alternative to TKIP and that is + entirely immune to attack. WPA also specifies the + AES-CCMP + cipher as an alternative to TKIP and that is preferred when possible; for this specification the term - WPA2 (or RSN) is commonly used. - - WPA defines authentication and encryption protocols. + WPA2 (or RSN) is commonly used. + + WPA defines authentication and encryption protocols. Authentication is most commonly done using one of two techniques: by 802.1X and a backend authentication service - such as RADIUS, or by a minimal handshake between the + such as RADIUS, + or by a minimal handshake between the station and the access point using a pre-shared secret. - The former is commonly termed WPA Enterprise with the - latter known as WPA Personal. Since most people will not - set up a RADIUS backend server for wireless network, - WPA-PSK is by far the most commonly encountered - configuration for WPA. + The former is commonly termed WPA Enterprise with the + latter known as WPA Personal. Since most people will not + set up a RADIUS backend server for wireless network, + WPA-PSK is by far the most commonly encountered + configuration for WPA. The control of the wireless connection and the authentication (key negotiation or authentication with a @@ -1212,11 +1225,12 @@ WPA-PSK - WPA-PSK also known as WPA-Personal is based on a - pre-shared key (PSK) generated from a given password and + WPA-PSK + also known as WPA-Personal is based on a + pre-shared key (PSK) generated from a given password and that will be used as the master key in the wireless network. This means every wireless user will share the - same key. WPA-PSK is intended for small networks where + same key. WPA-PSK is intended for small networks where the use of an authentication server is not possible or desired. @@ -1228,7 +1242,8 @@ The first step is the configuration of the /etc/wpa_supplicant.conf file with - the SSID and the pre-shared key of your network: + the SSID and + the pre-shared key of your network: network={ ssid="freebsdap" @@ -1237,8 +1252,8 @@ Then, in /etc/rc.conf, we indicate that the wireless device configuration will be - done with WPA and the IP address will be obtained with - DHCP: + done with WPA and the IP address will be obtained with + DHCP: ifconfig_ath0="WPA DHCP" @@ -1274,7 +1289,7 @@ The next operation is the launch of the dhclient command to get the IP - address from the DHCP server: + address from the DHCP server: &prompt.root; dhclient ath0 DHCPREQUEST on ath0 to 255.255.255.255 port 67 @@ -1301,7 +1316,7 @@ keys. - In the case where the use of DHCP is not possible, + In the case where the use of DHCP is not possible, you can set a static IP address after wpa_supplicant has authenticated the station: @@ -1318,7 +1333,7 @@ authmode WPA privacy ON deftxkey UNDEF TKIP 2:128-bit txpowmax 36 protmode CTS roaming MANUAL bintval 100 - When DHCP is not used, you also have to manually set + When DHCP is not used, you also have to manually set up the default gateway and the nameserver: &prompt.root; route add default your_default_router @@ -1328,29 +1343,32 @@ WPA with EAP-TLS - The second way to use WPA is with an 802.1X backend - authentication server, in this case WPA is called - WPA-Enterprise to make difference with the less secure - WPA-Personal with its pre-shared key. The - authentication in WPA-Enterprise is based on EAP + The second way to use WPA is with an 802.1X backend + authentication server, in this case WPA is called + WPA-Enterprise to make difference with the less secure + WPA-Personal with its pre-shared key. The + authentication in WPA-Enterprise is based on EAP (Extensible Authentication Protocol). - EAP does not come with an encryption method, it was - decided to embed EAP inside an encrypted tunnel. Many - types of EAP authentication methods have been designed, - the most common methods are EAP-TLS, EAP-TTLS and - EAP-PEAP. - - EAP-TLS (EAP with Transport Layer Security) is a + EAP does not come with an encryption method, it was + decided to embed EAP inside an encrypted tunnel. Many + types of EAP authentication methods have been designed, + the most common methods are + EAP-TLS, + EAP-TTLS + and + EAP-PEAP. + + EAP-TLS (EAP with Transport Layer Security) is a very well-supported authentication protocol in the - wireless world since it was the first EAP method to be + wireless world since it was the first EAP method to be certified by the Wi-Fi alliance. - EAP-TLS will require three certificates to run: the CA + EAP-TLS will require three certificates to run: the CA certificate (installed on all machines), the server certificate for your authentication server, and one client certificate for each wireless client. In this - EAP method, both authentication server and wireless + EAP method, both authentication server and wireless client authenticate each other in presenting their respective certificates, and they verify that these certificates were signed by your organization's @@ -1374,35 +1392,35 @@ This field indicates the network name - (SSID). + (SSID). - Here, we use RSN (IEEE 802.11i) protocol, i.e., - WPA2. + Here, we use RSN + (IEEE 802.11i) protocol, i.e., WPA2. The key_mgmt line refers to the key management protocol we use. In our case it - is WPA using EAP authentication: + is WPA using EAP authentication: WPA-EAP. - In this field, we mention the EAP method for our + In this field, we mention the EAP method for our connection. The identity field contains - the identity string for EAP. + the identity string for EAP. The ca_cert field indicates - the pathname of the CA certificate file. This file - is needed to verify the server certificate. + the pathname of the CA certificate file. This file + is needed to verify the server certificat. @@ -1457,13 +1475,17 @@ WPA with EAP-TTLS - With EAP-TLS both the authentication server and the - client need a certificate, with EAP-TTLS (EAP-Tunneled - Transport Layer Security) a client certificate is + With EAP-TLS + both the authentication server and the + client need a certificate, with + EAP-TTLS + (EAP-Tunneled Transport Layer Security) + a client certificate is optional. This method is close to what some secure web - sites do , where the web server can create a secure SSL + sites do, where the web server can create a secure SSL tunnel even if the visitors do not have client-side - certificates. EAP-TTLS will use the encrypted TLS + certificates. EAP-TTLS will use the + encrypted TLS tunnel for safe transport of the authentication data. @@ -1484,31 +1506,31 @@ - In this field, we mention the EAP method for our + In this field, we mention the EAP method for our connection. The identity field contains - the identity string for EAP authentication inside - the encrypted TLS tunnel. + the identity string for EAP authentication inside + the encrypted TLS tunnel. The password field contains - the passphrase for the EAP authentication. + the passphrase for the EAP authentication. The ca_cert field indicates - the pathname of the CA certificate file. This file - is needed to verify the server certificat. + the pathname of the CA certificate file. This file + is needed to verify the server certificate. In this field, we mention the authentication - method used in the encrypted TLS tunnel. In our - case, EAP with MD5-Challenge has been used. The + method used in the encrypted TLS tunnel. In our + case, EAP with MD5-Challenge has been used. The inner authentication phase is often called phase2. @@ -1542,29 +1564,33 @@ WPA with EAP-PEAP - PEAP (Protected EAP) has been designed as an - alternative to EAP-TTLS. There are two types of PEAP - methods, the most common one is PEAPv0/EAP-MSCHAPv2. In - the rest of this document, we will use the PEAP term to - refer to that EAP method. PEAP is the most used EAP - standard after EAP-TLS, in other words if you have a - network with mixed OSes, PEAP should be the most - supported standard after EAP-TLS. - - PEAP is similar to EAP-TTLS: it uses a server-side + PEAP + (Protected EAP) has been designed as an + alternative to + EAP-TTLS. + There are two types of PEAP + methods, the most common one is + PEAPv0/EAPMSCHAPv2. + In the rest of this document, we will use the PEAP term to + refer to that EAP method. PEAP is the most used EAP + standard after EAP-TLS, in other words if you have a + network with mixed OSes, PEAP should be the most + supported standard after EAP-TLS. + + PEAP is similar to EAP-TTLS: it uses a server-side certificate to authenticate clients by creating an - encrypted TLS tunnel between the client and the + encrypted TLS tunnel between the client and the authentication server, which protects the ensuing exchange of authentication information. In term of - security the difference between EAP-TTLS and PEAP is - that PEAP authentication broadcasts the username in - clear, only the password is sent in the encrypted TLS - tunnel. EAP-TTLS will use the TLS tunnel for both + security the difference between EAP-TTLS and PEAP is + that PEAP authentication broadcasts the username in + clear, only the password is sent in the encrypted TLS + tunnel. EAP-TTLS will use the TLS tunnel for both username and password. We have to edit the /etc/wpa_supplicant.conf file and - add the EAP-PEAP related settings: + add the EAP-PEAP related settings: network={ ssid="freebsdap" @@ -1580,30 +1606,30 @@ - In this field, we mention the EAP method for our + In this field, we mention the EAP method for our connection. The identity field contains - the identity string for EAP authentication inside - the encrypted TLS tunnel. + the identity string for EAP authentication inside + the encrypted TLS tunnel. The password field contains - the passphrase for the EAP authentication. + the passphrase for the EAP authentication. The ca_cert field indicates - the pathname of the CA certificate file. This file + the pathname of the CA certificate file. This file is needed to verify the server certificat. This field contains the parameters for the - first phase of the authentication (the TLS + first phase of the authentication (the TLS tunnel). According to the authentication server used, you will have to specify a specific label for the authentication. Most of time, the label @@ -1615,8 +1641,8 @@ In this field, we mention the authentication - protocol used in the encrypted TLS tunnel. In the - case of PEAP, it is + protocol used in the encrypted TLS tunnel. In the + case of PEAP, it is auth=MSCHAPV2. @@ -1650,7 +1676,7 @@ WEP - WEP (Wired Equivalent Privacy) is part of the original + WEP (Wired Equivalent Privacy) is part of the original 802.11 standard. There is no authentication mechanism, only a weak form of access control, and it is easily to be cracked. @@ -1663,7 +1689,7 @@ - The weptxkey means which WEP + The weptxkey means which WEP key will be used in the transmission. Here we used the third key. This must match the setting in the access point. If you do not have any idea of what is the key @@ -1674,7 +1700,7 @@ The wepkey means setting the - selected WEP key. It should in the format + selected WEP key. It should in the format index:key, if the index is not given, key 1 is set. That is to say we need to set the index if we use keys other @@ -1692,7 +1718,7 @@ page for further information. The wpa_supplicant facility also - can be used to configure your wireless interface with WEP. + can be used to configure your wireless interface with WEP. The example above can be set up by adding the following lines to /etc/wpa_supplicant.conf: @@ -1716,11 +1742,11 @@ Ad-hoc Mode - IBSS mode, also called ad-hoc mode, is designed for point + IBSS mode, also called ad-hoc mode, is designed for point to point connections. For example, to establish an ad-hoc network between the machine A and the machine B we will just need to choose two IP adresses - and a SSID. + and a SSID. On the box A: @@ -1736,7 +1762,7 @@ authmode OPEN privacy OFF txpowmax 36 protmode CTS bintval 100 The adhoc parameter indicates the - interface is running in the IBSS mode. + interface is running in the IBSS mode. On B, we should be able to detect A: @@ -1768,15 +1794,15 @@ &os; Host Access Points - &os; can act as an Access Point (AP) which eliminates the - need to buy a hardware AP or run an ad-hoc network. This can be + &os; can act as an Access Point (AP) which eliminates the + need to buy a hardware AP or run an ad-hoc network. This can be particularly useful when your &os; machine is acting as a gateway to another network (e.g., the Internet). Basic Settings - Before configuring your &os; machine as an AP, the + Before configuring your &os; machine as an AP, the kernel must be configured with the appropriate wireless networking support for your wireless card. You also have to add the support for the security protocols you intend to @@ -1785,8 +1811,8 @@ The use of the NDIS driver wrapper and the &windows; - drivers do not allow currently the AP operation. Only - native &os; wireless drivers support AP mode. + drivers do not allow currently the AP operation. Only + native &os; wireless drivers support AP mode. Once the wireless networking support is loaded, you can @@ -1799,12 +1825,16 @@ This output displays the card capabilities; the HOSTAP word confirms this wireless card can act as an Access Point. Various supported ciphers are - also mentioned: WEP, TKIP, WPA2, etc., these informations + also mentioned: + WEP, + TKIP, + WPA2, etc., these informations are important to know what security protocols could be set on the Access Point. The wireless device can now be put into hostap mode and - configured with the correct SSID and IP address: + configured with the correct + SSID and IP address: &prompt.root; ifconfig ath0 ssid freebsdap mode 11g mediaopt hostap inet 192.168.0.1 netmask 255.255.255.0 @@ -1836,12 +1866,13 @@ Host-based Access Point without Authentication or Encryption - Although it is not recommended to run an AP without any + Although it is not recommended to run an + AP without any authentication or encryption, this is a simple way to check - if your AP is working. This configuration is also important + if your AP is working. This configuration is also important for debugging client issues. - Once the AP configured as previously shown, it is + Once the AP configured as previously shown, it is possible from another wireless machine to initiate a scan to find the AP: @@ -1868,17 +1899,18 @@ WPA Host-based Access Point This section will focus on setting up &os; Access Point - using the WPA security protocol. More details regarding WPA - and the configuration of WPA-based wireless clients can be + using the WPA security protocol. + More details regarding WPA + and the configuration of WPA-based wireless clients can be found in the . The hostapd daemon is used to deal with client authentication and keys management on the - WPA enabled Access Point. + WPA enabled Access Point. In the following, all the configuration operations will - be performed on the &os; machine acting as AP. Once the - AP is correctly working, hostapd + be performed on the &os; machine acting as AP. Once the + AP is correctly working, hostapd should be automatically enabled at boot with the following line in /etc/rc.conf: @@ -1892,7 +1924,8 @@ WPA-PSK - WPA-PSK is intended for small networks where the use + WPA-PSK + is intended for small networks where the use of an backend authentication server is not possible or desired. @@ -1944,14 +1977,14 @@ The wpa field enables WPA and - specifies which WPA authentication protocol will be + specifies which WPA authentication protocol will be required. A value of 1 configures the AP for WPA-PSK. The wpa_passphrase field - contains the ASCII passphrase for the WPA + contains the ASCII passphrase for the WPA authentication. @@ -1964,17 +1997,19 @@ The wpa_key_mgmt line refers to the key management protocol we use. In our case it is - WPA-PSK. + WPA-PSK. The wpa_pairwise field indicates the set of accepted encryption algorithms by - the Access Point. Here both TKIP (WPA) and CCMP - (WPA2) ciphers are accepted. CCMP cipher is an - alternative to TKIP and that is strongly preferred - when possible; TKIP should be used solely for stations - incapable of doing CCMP. + the Access Point. Here both + TKIP (WPA) and + CCMP WPA2) ciphers are accepted. + CCMP cipher is an + alternative to TKIP and that is strongly preferred + when possible; TKIP should be used solely for stations + incapable of doing CCMP. @@ -1996,7 +2031,7 @@ The Access Point is running, the clients can now be associated with it, see for more details. It is - possible to see the stations associated with the AP using + possible to see the stations associated with the AP using the ifconfig ath0 list sta command. @@ -2005,22 +2040,22 @@ WEP Host-based Access Point - It is not recommended to use WEP for setting up an + It is not recommended to use WEP for setting up an Access Point since there is no authentication mechanism and it is easily to be cracked. Some legacy wireless cards only - support WEP as security protocol, these cards will only - allow to set up AP without authentication or encryption or - using the WEP protocol. + support WEP as security protocol, these cards will only + allow to set up AP without authentication or encryption or + using the WEP protocol. The wireless device can now be put into hostap mode and - configured with the correct SSID and IP address: + configured with the correct SSID and IP address: &prompt.root; ifconfig ath0 ssid freebsdap wepmode on weptxkey 3 wepkey 3:0x3456789012 mode 11g mediaopt hostap \ inet 192.168.0.1 netmask 255.255.255.0 - The weptxkey means which WEP + The weptxkey means which WEP key will be used in the transmission. Here we used the third key (note that the key numbering starts with 1). This parameter must be specified @@ -2029,7 +2064,7 @@ The wepkey means setting the - selected WEP key. It should in the format + selected WEP key. It should in the format index:key, if the index is not given, key 1 is set. That is to say we need to set the index if we use keys other @@ -2084,7 +2119,8 @@ access point. This includes the authentication scheme and any security protocols. Simplify your configuration as much as possible. If you are using a security protocol - such as WPA or WEP configure the access point for open + such as WPA + or WEP configure the access point for open authentication and no security to see if you can get traffic to pass. @@ -3245,7 +3281,7 @@ lacp - Supports the IEEE 802.3ad Link Aggregation Control Protocol + Supports the IEEE 802.3ad Link Aggregation Control Protocol (LACP) and the Marker Protocol. LACP will negotiate a set of aggregable links with the peer in to one or more Link Aggregated Groups. Each LAG is composed of ports of the same speed, set to diff -r 1649440b3588 -r 56b69b866c6f share/sgml/acronyms.ent --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/share/sgml/acronyms.ent Fri Dec 12 08:37:20 2008 +0200 @@ -0,0 +1,41 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff -r 1649440b3588 -r 56b69b866c6f share/sgml/articles.ent --- a/share/sgml/articles.ent Fri Dec 12 06:06:03 2008 +0000 +++ b/share/sgml/articles.ent Fri Dec 12 08:37:20 2008 +0200 @@ -8,6 +8,8 @@ %man; %freebsd; + +%acronyms; %authors; diff -r 1649440b3588 -r 56b69b866c6f share/sgml/books.ent --- a/share/sgml/books.ent Fri Dec 12 06:06:03 2008 +0000 +++ b/share/sgml/books.ent Fri Dec 12 08:37:20 2008 +0200 @@ -10,6 +10,8 @@ %bookinfo; %freebsd; + +%acronyms; %authors; diff -r 1649440b3588 -r 56b69b866c6f share/sgml/catalog --- a/share/sgml/catalog Fri Dec 12 06:06:03 2008 +0000 +++ b/share/sgml/catalog Fri Dec 12 08:37:20 2008 +0200 @@ -23,6 +23,9 @@ PUBLIC "-//FreeBSD//DOCUMENT DocBook Language Neutral Stylesheet//EN" "freebsd.dsl" +PUBLIC "-//FreeBSD//ENTITIES DocBook FreeBSD Acronyms Entity Set//EN" + "acronyms.ent" + PUBLIC "-//FreeBSD//ENTITIES DocBook FreeBSD Articles Entity Set//EN" "articles.ent" %%% From owner-freebsd-doc@FreeBSD.ORG Fri Dec 12 07:51:09 2008 Return-Path: Delivered-To: doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 59DF61065672; Fri, 12 Dec 2008 07:51:09 +0000 (UTC) (envelope-from r.c.ladan@gmail.com) Received: from yw-out-2324.google.com (yw-out-2324.google.com [74.125.46.29]) by mx1.freebsd.org (Postfix) with ESMTP id F0AA18FC08; Fri, 12 Dec 2008 07:51:08 +0000 (UTC) (envelope-from r.c.ladan@gmail.com) Received: by yw-out-2324.google.com with SMTP id 9so609750ywe.13 for ; Thu, 11 Dec 2008 23:51:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=d5oGzky7BPhNhokvjkiNw3BHexZ5wZRKstN9vPXDgEE=; b=fXQgxvGYpmayzR2HBSwj4wx3MkQyLN5Q2rOqMy+fAO7+pOLRHPPFhS1eAI85ORi2TQ LtQMuqILmjCHkWfQ2ZsjOttlNzYlnglHmc6NyOUGcVjMOAqCfoKHouP+0mBgN2dj2iqh FbItnD961DrCq6qiq2To1V7/1iU/NrpaOllHo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=mgx65k/vniKoS0QrtSirkxxAZGzDLo9Cm/FdHk4Tazy49yXrusCUSJ9ihr1UAL5b2F 3YG4fTpoVVAugwE/ovCUhvbGCuvZQm/evxQlYg9ohZKlmYUMzugB4J7x32Mcb73Rz6Zs 32eCkNQxdFMtp+I74qneAFjtPzIC7YOFq/pvQ= Received: by 10.150.145.20 with SMTP id s20mr5222926ybd.30.1229068268192; Thu, 11 Dec 2008 23:51:08 -0800 (PST) Received: by 10.150.225.9 with HTTP; Thu, 11 Dec 2008 23:51:07 -0800 (PST) Message-ID: Date: Fri, 12 Dec 2008 08:51:07 +0100 From: "Rene Ladan" To: "Giorgos Keramidas" In-Reply-To: <87k5a63z2d.fsf@kobe.laptop> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <871vwfn418.fsf@kobe.laptop> <2a7894eb0812101310v2123a452q26b0e07630e7f209@mail.gmail.com> <878wqnafso.fsf@kobe.laptop> <2a7894eb0812101322o77b12fc9k8208f83d62481ad3@mail.gmail.com> <87k5a63z2d.fsf@kobe.laptop> Cc: doc@freebsd.org Subject: Re: [PATCH] Adding elements to wlan Handbook section 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, 12 Dec 2008 07:51:09 -0000 2008/12/12 Giorgos Keramidas : > On Wed, 10 Dec 2008 13:22:57 -0800, "Murray Stokely" wrote: >> In that case this looks great to me. I agree with Manolis that adding >> the role="definition" for the first instance of each acronym is >> helpful. I really thought we were already doing this in parts of the >> Handbook, but I may be misremembering. > > I started adding a role="" at the first instance of each WLAN-specific > acronym and I noticed that I was typing the same expansions again and > again all over the place. This is a bit error prone, so it seemed more > natural to add a ``set of "standard" acronym expansions''. > > Does something like this look useful for other sorts of acronyms too? > > %%% > # HG changeset patch > # User keramida > # Date 1229048467 -7200 > # Node ID c8a6e126654fba80e290d6c93568d551a0c10473 > # Parent 669337240ff11759179bde192d61b69a6be769ea > Add support for a set of 'standard' acronym expansions. > > I got a bit sick of typing role="the same text" all the time, and > this gives us an easy point to redefine an acronym expansion > without having to crawl the entire doc/ tree, so here it is. > > diff -r 669337240ff1 -r c8a6e126654f share/sgml/acronyms.ent > --- /dev/null Thu Jan 01 00:00:00 1970 +0000 > +++ b/share/sgml/acronyms.ent Fri Dec 12 04:21:07 2008 +0200 > @@ -0,0 +1,21 @@ > + > + > + > + > + > + > + > + > + > + > + > + > diff -r 669337240ff1 -r c8a6e126654f share/sgml/articles.ent > --- a/share/sgml/articles.ent Wed Dec 10 22:51:06 2008 +0200 > +++ b/share/sgml/articles.ent Fri Dec 12 04:21:07 2008 +0200 > @@ -8,6 +8,8 @@ > %man; > > %freebsd; > + > +%acronyms; > > %authors; > > diff -r 669337240ff1 -r c8a6e126654f share/sgml/books.ent > --- a/share/sgml/books.ent Wed Dec 10 22:51:06 2008 +0200 > +++ b/share/sgml/books.ent Fri Dec 12 04:21:07 2008 +0200 > @@ -10,6 +10,8 @@ > %bookinfo; > > %freebsd; > + > +%acronyms; > > %authors; > > diff -r 669337240ff1 -r c8a6e126654f share/sgml/catalog > --- a/share/sgml/catalog Wed Dec 10 22:51:06 2008 +0200 > +++ b/share/sgml/catalog Fri Dec 12 04:21:07 2008 +0200 > @@ -23,6 +23,9 @@ > PUBLIC "-//FreeBSD//DOCUMENT DocBook Language Neutral Stylesheet//EN" > "freebsd.dsl" > > +PUBLIC "-//FreeBSD//ENTITIES DocBook FreeBSD Acronyms Entity Set//EN" > + "acronyms.ent" > + > PUBLIC "-//FreeBSD//ENTITIES DocBook FreeBSD Articles Entity Set//EN" > "articles.ent" > > %%% > > I have only added a few acronym expansions now, but this already makes > it possible to write things like: > > Using WEP > encryption is not really safe anymore, but a lot of people use it > anyway. > > We can probably go a step further and define: > > WEP'> > > but I wanted to ask the rest of doc@ first what they think about a list > of acronym expansions that is shared like this? > > If yes, which form of entity would you prefer to have? One that expands > to the "Name of the Acronym" or one that expands to the full > element? > I am in favour of the full expansion, so that you can write Using &acronym.wlan.wep; encryption is not really safe anymore, but a lot of people use it anyway. This form is shorter and we don't have to write the word "acronym" three times. Maybe the acronyms can link to the glossary of the Handbook as well? Regards, Rene -- http://www.rene-ladan.nl/ GPG fingerprint = E738 5471 D185 7013 0EE0 4FC8 3C1D 6F83 12E1 84F6 (subkeys.pgp.net) From owner-freebsd-doc@FreeBSD.ORG Fri Dec 12 08:58:49 2008 Return-Path: Delivered-To: doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D3C2B106564A for ; Fri, 12 Dec 2008 08:58:49 +0000 (UTC) (envelope-from pali.gabor@googlemail.com) Received: from mail-ew0-f21.google.com (mail-ew0-f21.google.com [209.85.219.21]) by mx1.freebsd.org (Postfix) with ESMTP id 3865D8FC1D for ; Fri, 12 Dec 2008 08:58:49 +0000 (UTC) (envelope-from pali.gabor@googlemail.com) Received: by ewy14 with SMTP id 14so1913766ewy.19 for ; Fri, 12 Dec 2008 00:58:48 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:received:received:sender:message-id:date:from :organization:user-agent:mime-version:to:cc:subject:references :in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; bh=9ppBvkHOzi/eYF52AsYc9Mxg/YOXC5xcU+9I2IZG1BM=; b=gm1Pzk8Hg1eYc85y2uk/8jGGZykoT0VzZm1GGXpgtKK+E+gwNJ39rlB50bCTuGK9EZ +CpwpFJK/3qCqsYXym11aiZeVOBQPRC9M0+BHDFeHHjfBy9ywCgiv3cA1GmyIGmX9hVZ jpF4ZK4WON06ynnqfpKrsdKpDLd0FcjZQhWnU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=sender:message-id:date:from:organization:user-agent:mime-version:to :cc:subject:references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; b=Csfuxz9Xc264l2pTXXObrulPKOt+FMbd1qB3QOBaotGbmHGtj//gv4zLrMMKSbUj6l rrrnKJPjfPuAF7mMV2TamceaacAKu6oi//+gRojHb3GzEf1QQmIKbN8YFCagKrJuYqzc RY4o0hVzRwrmcnoLv3oWtSii24AhbVsAUHrwY= Received: by 10.210.52.15 with SMTP id z15mr533109ebz.28.1229072328121; Fri, 12 Dec 2008 00:58:48 -0800 (PST) Received: from ?192.168.1.18? (oktnb24.inf.elte.hu [157.181.167.24]) by mx.google.com with ESMTPS id 34sm3245579nfu.33.2008.12.12.00.58.46 (version=TLSv1/SSLv3 cipher=RC4-MD5); Fri, 12 Dec 2008 00:58:47 -0800 (PST) Sender: =?UTF-8?B?UMOBTEkgR8OhYm9yIErDoW5vcw==?= Message-ID: <494227B4.3070504@FreeBSD.org> Date: Fri, 12 Dec 2008 09:58:28 +0100 From: Gabor PALI Organization: The FreeBSD Project User-Agent: Thunderbird 2.0.0.17 (X11/20081023) MIME-Version: 1.0 To: Rene Ladan References: <871vwfn418.fsf@kobe.laptop> <2a7894eb0812101310v2123a452q26b0e07630e7f209@mail.gmail.com> <878wqnafso.fsf@kobe.laptop> <2a7894eb0812101322o77b12fc9k8208f83d62481ad3@mail.gmail.com> <87k5a63z2d.fsf@kobe.laptop> In-Reply-To: X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: doc@freebsd.org, Giorgos Keramidas Subject: Re: [PATCH] Adding elements to wlan Handbook section 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, 12 Dec 2008 08:58:49 -0000 Rene Ladan wrote: > 2008/12/12 Giorgos Keramidas : >> I have only added a few acronym expansions now, but this already makes >> it possible to write things like: >> >> Using WEP >> encryption is not really safe anymore, but a lot of people use it >> anyway. >> >> We can probably go a step further and define: >> >> WEP'> >> >> but I wanted to ask the rest of doc@ first what they think about a list >> of acronym expansions that is shared like this? >> >> If yes, which form of entity would you prefer to have? One that expands >> to the "Name of the Acronym" or one that expands to the full >> element? >> > I am in favour of the full expansion, so that you can write > > Using &acronym.wlan.wep; encryption is not really safe anymore, > but a lot of people use it anyway. > > This form is shorter and we don't have to write the word "acronym" three times. Maybe you can have different versions in the .ent file, like you did in case of mailing lists (defer the design decisions :)): WEP'> WEP'> > Maybe the acronyms can link to the glossary of the Handbook as well? Hm, sounds interesting. I think it is a good idea. Add another entity, for example: WEP'> So the documentation writer has the freedom of choice how to mark up acronyms. It could be useful when one does not want to link all instances of an acronym, only the first in the section, for example. Thanks for saving us from lot of typing, Giorgos! :) Cheers, :g From owner-freebsd-doc@FreeBSD.ORG Fri Dec 12 09:04:51 2008 Return-Path: Delivered-To: doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 752E01065673 for ; Fri, 12 Dec 2008 09:04:51 +0000 (UTC) (envelope-from keramida@freebsd.org) Received: from igloo.linux.gr (igloo.linux.gr [62.1.205.36]) by mx1.freebsd.org (Postfix) with ESMTP id DC35E8FC13 for ; Fri, 12 Dec 2008 09:04:50 +0000 (UTC) (envelope-from keramida@freebsd.org) Received: from kobe.laptop (adsl179-214.kln.forthnet.gr [77.49.0.214]) (authenticated bits=128) by igloo.linux.gr (8.14.3/8.14.3/Debian-5) with ESMTP id mBC94grB021911 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 12 Dec 2008 11:04:48 +0200 Received: from kobe.laptop (kobe.laptop [127.0.0.1]) by kobe.laptop (8.14.3/8.14.3) with ESMTP id mBC94g34013994; Fri, 12 Dec 2008 11:04:42 +0200 (EET) (envelope-from keramida@freebsd.org) Received: (from keramida@localhost) by kobe.laptop (8.14.3/8.14.3/Submit) id mBC94ghO013993; Fri, 12 Dec 2008 11:04:42 +0200 (EET) (envelope-from keramida@freebsd.org) From: Giorgos Keramidas To: "Rene Ladan" References: <871vwfn418.fsf@kobe.laptop> <2a7894eb0812101310v2123a452q26b0e07630e7f209@mail.gmail.com> <878wqnafso.fsf@kobe.laptop> <2a7894eb0812101322o77b12fc9k8208f83d62481ad3@mail.gmail.com> <87k5a63z2d.fsf@kobe.laptop> Date: Fri, 12 Dec 2008 11:04:41 +0200 In-Reply-To: (Rene Ladan's message of "Fri, 12 Dec 2008 08:51:07 +0100") Message-ID: <871vwdahna.fsf@kobe.laptop> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.60 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-MailScanner-ID: mBC94grB021911 X-Hellug-MailScanner: Found to be clean X-Hellug-MailScanner-SpamCheck: not spam, SpamAssassin (not cached, score=-4.294, required 5, autolearn=not spam, ALL_TRUSTED -1.80, AWL 0.10, BAYES_00 -2.60) X-Hellug-MailScanner-From: keramida@freebsd.org X-Spam-Status: No Cc: doc@freebsd.org Subject: Re: [PATCH] Adding elements to wlan Handbook section 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, 12 Dec 2008 09:04:51 -0000 On Fri, 12 Dec 2008 08:51:07 +0100, "Rene Ladan" wrote: > I am in favour of the full expansion, so that you can write > > Using &acronym.wlan.wep; encryption is not really safe anymore, > but a lot of people use it anyway. > > This form is shorter and we don't have to write the word "acronym" > three times. > > Maybe the acronyms can link to the glossary of the Handbook as well? That's an interesting idea :-) On Fri, 12 Dec 2008 09:58:28 +0100, Gabor PALI wrote: > Maybe you can have different versions in the .ent file, like you did > in case of mailing lists (defer the design decisions :)): > > WEP'> > WEP'> Heh, cool! I'll try to update the patch to include entities like this. Thank you both for the ideas. From owner-freebsd-doc@FreeBSD.ORG Fri Dec 12 09:05:27 2008 Return-Path: Delivered-To: doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DAD001065670 for ; Fri, 12 Dec 2008 09:05:27 +0000 (UTC) (envelope-from pali.gabor@googlemail.com) Received: from mail-ew0-f21.google.com (mail-ew0-f21.google.com [209.85.219.21]) by mx1.freebsd.org (Postfix) with ESMTP id 415368FC20 for ; Fri, 12 Dec 2008 09:05:27 +0000 (UTC) (envelope-from pali.gabor@googlemail.com) Received: by ewy14 with SMTP id 14so1916458ewy.19 for ; Fri, 12 Dec 2008 01:05:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:received:received:sender:message-id:date:from :organization:user-agent:mime-version:to:cc:subject:references :in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; bh=OniWLpJGUwahSrtHQtT7tSgUI0ZEuQrdA2Au4bspwwI=; b=RQFcjCRGEYAyOn0ad49sUAmlMtYkbXbbfzy6PIGzcIPoK10Az80kEEXtgaWOOi5NaA 3HGhdLA6KjPJBL9y2rbM2JNvBu5sCkXyNJzm4NmbExziDTWwxCoKdEjUeIlpNQwGQzSw ENr8k4vZxwQb5l51u/tNzt8OzI6LchIKdiINo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=sender:message-id:date:from:organization:user-agent:mime-version:to :cc:subject:references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; b=T8EAI/zyf2MjWiHTQxEs1vK8nQVrAuyKgKLfCJTS186a73oewflLn6SJ2Z0rBWQcZ9 xyC9G1mu/embUdxAIk8qwVBolyGcX8EQbmJpQ6Nm+uBXxhBVeyYrPyE7gBO/CqCRqF3T 9FZi9pvYhNYqSIteXDbWrGHbBZ5TMeUPHouXA= Received: by 10.210.70.14 with SMTP id s14mr1643777eba.151.1229072726312; Fri, 12 Dec 2008 01:05:26 -0800 (PST) Received: from ?192.168.1.18? (oktnb24.inf.elte.hu [157.181.167.24]) by mx.google.com with ESMTPS id 3sm31025eyi.40.2008.12.12.01.05.24 (version=TLSv1/SSLv3 cipher=RC4-MD5); Fri, 12 Dec 2008 01:05:25 -0800 (PST) Sender: =?UTF-8?B?UMOBTEkgR8OhYm9yIErDoW5vcw==?= Message-ID: <4942293B.6080404@FreeBSD.org> Date: Fri, 12 Dec 2008 10:04:59 +0100 From: Gabor PALI Organization: The FreeBSD Project User-Agent: Thunderbird 2.0.0.17 (X11/20081023) MIME-Version: 1.0 To: Rene Ladan References: <49174B71.9080800@gmail.com> <49184BDB.5070707@FreeBSD.org> In-Reply-To: X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: doc@freebsd.org Subject: Re: [RFC] Committers guide: replace CVS by SVN where appropiate 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, 12 Dec 2008 09:05:28 -0000 Rene Ladan wrote: > 2008/11/10 Gabor PALI : >> - I am not sure that "A Free 4-CD Set or DVD Subscription" is still >> available for committers. >> > Doesn't seem to be the case (at least for 6.4) :( > I think we should ask Murray Stokely to get an "official" answer. Murray? > I've created the first (trivial) patch for this. Technically it looks fine to me, however I am not so happy with this too :( Maybe any other option to mention? I do not believe there is no other perks of the job these days... > I'll create more patches for different things (nits, cvs->svn, who's who, ...) Okay, I would be happy to review them. Cheers, :g From owner-freebsd-doc@FreeBSD.ORG Fri Dec 12 11:34:51 2008 Return-Path: Delivered-To: doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AA6CA106564A; Fri, 12 Dec 2008 11:34:51 +0000 (UTC) (envelope-from r.c.ladan@gmail.com) Received: from yx-out-2324.google.com (yx-out-2324.google.com [74.125.44.29]) by mx1.freebsd.org (Postfix) with ESMTP id 4D39F8FC0C; Fri, 12 Dec 2008 11:34:51 +0000 (UTC) (envelope-from r.c.ladan@gmail.com) Received: by yx-out-2324.google.com with SMTP id 8so629327yxb.13 for ; Fri, 12 Dec 2008 03:34:50 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=i/o8cl0dGOsZIDS7CSmcJ1TqNVaXe6C1fqn3+7Hbe5E=; b=SXHtew/u8tgmJXdqsAyykUFS4g4R0ILCJcCrgHburxZHlgBYJcky46lISXAoM9t7/q IAtT+849WTgfn2rdWXA/buCcnGtiiWp+jekzz57dAovlPc8zcmqPQW+Moy6ehSz9r+GD DjHHi02GUWp5RUDSVd1EBnsc7vrsRz3xgaYtQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=XS9i07FPBwSSo9SMkWX09SZjlvuJQ8OsVf+RcqDLbJY1lzny3RPc2++jWhArHkZWbp U0SAikmTK8laA2/SjM6qZNwTNXulbRAIYxxu0UHR8Xb6OHvw/GASVlcvJ/ZsegTZ0jEw 3z4x7FXX0DtQUKbJbN2EShKB+c59wRmpaQnYY= Received: by 10.150.220.19 with SMTP id s19mr3724503ybg.103.1229081690653; Fri, 12 Dec 2008 03:34:50 -0800 (PST) Received: by 10.150.225.9 with HTTP; Fri, 12 Dec 2008 03:34:50 -0800 (PST) Message-ID: Date: Fri, 12 Dec 2008 12:34:50 +0100 From: "Rene Ladan" To: "Gabor PALI" In-Reply-To: <4942293B.6080404@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <49174B71.9080800@gmail.com> <49184BDB.5070707@FreeBSD.org> <4942293B.6080404@FreeBSD.org> Cc: doc@freebsd.org Subject: Re: [RFC] Committers guide: replace CVS by SVN where appropiate 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, 12 Dec 2008 11:34:51 -0000 2008/12/12 Gabor PALI : > Rene Ladan wrote: >> 2008/11/10 Gabor PALI : >>> - I am not sure that "A Free 4-CD Set or DVD Subscription" is still >>> available for committers. >>> >> Doesn't seem to be the case (at least for 6.4) :( >> > > I think we should ask Murray Stokely to get an "official" answer. Murray? > > >> I've created the first (trivial) patch for this. > > Technically it looks fine to me, however I am not so happy with this too > :( Maybe any other option to mention? I do not believe there is no > other perks of the job these days... > You can always brag to your friends/colleagues :-p I've committed the patch to Perforce, see http://perforce.freebsd.org/chv.cgi?CH=154510 Besides Murray's answer I also need mentor approval for this. Is Murray associated with FreeBSDMall ? > >> I'll create more patches for different things (nits, cvs->svn, who's > who, ...) > > Okay, I would be happy to review them. > Thanks :) Regards, Rene -- http://www.rene-ladan.nl/ GPG fingerprint = E738 5471 D185 7013 0EE0 4FC8 3C1D 6F83 12E1 84F6 (subkeys.pgp.net) From owner-freebsd-doc@FreeBSD.ORG Fri Dec 12 13:08:51 2008 Return-Path: Delivered-To: doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 0AF2E1065673 for ; Fri, 12 Dec 2008 13:08:51 +0000 (UTC) (envelope-from pali.gabor@googlemail.com) Received: from mail-ew0-f21.google.com (mail-ew0-f21.google.com [209.85.219.21]) by mx1.freebsd.org (Postfix) with ESMTP id 88A018FC24 for ; Fri, 12 Dec 2008 13:08:50 +0000 (UTC) (envelope-from pali.gabor@googlemail.com) Received: by ewy14 with SMTP id 14so2028635ewy.19 for ; Fri, 12 Dec 2008 05:08:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:received:received:sender:message-id:date:from :organization:user-agent:mime-version:to:cc:subject:references :in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; bh=pO/GuMti79zyT446Vqhkt/WwBBdMCptDairnyNXMk2E=; b=ZmufjLmLqrOtq9qSjVi1Pn/2Xl/XKENTjNCubhMBuEVAhVGYhyQsonyezHC+72RNMi fjIWWtPA5KqCdmTyWNXFr9DpVmyth8zAbkGOkoZ9Zj8k1JyKFfFQFjueUdxsB9qbWj8G iv95MdQE+KKcjX20ZYnY46FnosxQn36dh59vo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=sender:message-id:date:from:organization:user-agent:mime-version:to :cc:subject:references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; b=qp5/ZmaWdNwiGdwptMd88LRcoMGC64YByTjbzPQthz8AoONGfXDdr7l7vVJKgTMQyW 8frnZLJNX+NxetP/fVLeluCII/YU62MCxeXH4SsnGOKQvr7MJH2Bki2zukvdmg5KYKNP xb/4wlGwNesZYP6xXb1V2SaJ7/1K0nMjZDYkQ= Received: by 10.210.56.7 with SMTP id e7mr4072933eba.67.1229087329550; Fri, 12 Dec 2008 05:08:49 -0800 (PST) Received: from ?192.168.1.18? (oktnb24.inf.elte.hu [157.181.167.24]) by mx.google.com with ESMTPS id d23sm3769399nfh.63.2008.12.12.05.08.48 (version=TLSv1/SSLv3 cipher=RC4-MD5); Fri, 12 Dec 2008 05:08:48 -0800 (PST) Sender: =?UTF-8?B?UMOBTEkgR8OhYm9yIErDoW5vcw==?= Message-ID: <4942624F.3030302@FreeBSD.org> Date: Fri, 12 Dec 2008 14:08:31 +0100 From: Gabor PALI Organization: The FreeBSD Project User-Agent: Thunderbird 2.0.0.17 (X11/20081023) MIME-Version: 1.0 To: Rene Ladan References: <49174B71.9080800@gmail.com> <49184BDB.5070707@FreeBSD.org> <4942293B.6080404@FreeBSD.org> In-Reply-To: X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: doc@freebsd.org Subject: Re: [RFC] Committers guide: replace CVS by SVN where appropiate 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, 12 Dec 2008 13:08:51 -0000 Rene Ladan wrote: > 2008/12/12 Gabor PALI : >> Maybe any other option to mention? I do not believe there is no >> other perks of the job these days... >> > You can always brag to your friends/colleagues :-p Yeah, but you cannot write this into the committers-guide :) > Besides Murray's answer I also need mentor approval for this. Do you still have a mentor for the en_US tree, do not you? :) > Is Murray associated with FreeBSDMall ? As far as I know, he was associated because he sent these announcements to freebsd-announce until February 2005 [1]. In November 2005, Bob Bruce sent an announcement [2] about 6.0-RELEASE, however no other announcements were made after then (and no reduced price options were mentioned in that message). Based on this, Bob Bruce or anybody else at FreeBSDMall should be interviewed about the status of the statement in question. I will do this. Cheers, :g [1] http://lists.freebsd.org/pipermail/freebsd-announce/2005-February/000980.html [2] http://lists.freebsd.org/pipermail/freebsd-announce/2005-November/001025.html From owner-freebsd-doc@FreeBSD.ORG Fri Dec 12 13:21:14 2008 Return-Path: Delivered-To: doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BF2D91065678; Fri, 12 Dec 2008 13:21:14 +0000 (UTC) (envelope-from r.c.ladan@gmail.com) Received: from yw-out-2324.google.com (yw-out-2324.google.com [74.125.46.30]) by mx1.freebsd.org (Postfix) with ESMTP id 5EB148FC1D; Fri, 12 Dec 2008 13:21:14 +0000 (UTC) (envelope-from r.c.ladan@gmail.com) Received: by yw-out-2324.google.com with SMTP id 9so640411ywe.13 for ; Fri, 12 Dec 2008 05:21:13 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=5YPXDlSioOkr6+n9MjGC45HAbIV5j8rp9mThtaLcnvs=; b=apjwRI9qJGxc3WHQNS8OFbzXITRt/YPbuW1W7+zCK3o+t00uYqaf0wJzKzt2fZDgHN 6NSSe2ZzDiZMWjvLcgCgiiczvELkFXb0zuUIZY+QtMT2/pDBkzebMGD5h/ur3EsQtQZ3 Lj+oIzjiWfgOR7lNpI8V7MgL2hK5J3/a9TR2k= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=nFf75UAjfxbr0xykWqAY+wTAO+EJWZFcDEhdyqMG0LEj/g6P9+FOUt/5IOnU6nKQpY TXBG1ZTgj6uaRXv2VkvcxzririSvcyB4yfnQDPXkOpePlmn6QnwQ0XaY4eDyaansoV4T KOPOr1mWPGtNhe/cAJY6vyWXsPLHdFZ7Njh6U= Received: by 10.151.109.11 with SMTP id l11mr6329384ybm.162.1229088073792; Fri, 12 Dec 2008 05:21:13 -0800 (PST) Received: by 10.151.13.3 with HTTP; Fri, 12 Dec 2008 05:21:13 -0800 (PST) Message-ID: Date: Fri, 12 Dec 2008 14:21:13 +0100 From: "Rene Ladan" To: "Gabor PALI" In-Reply-To: <4942624F.3030302@FreeBSD.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <49174B71.9080800@gmail.com> <49184BDB.5070707@FreeBSD.org> <4942293B.6080404@FreeBSD.org> <4942624F.3030302@FreeBSD.org> Cc: doc@freebsd.org Subject: Re: [RFC] Committers guide: replace CVS by SVN where appropiate 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, 12 Dec 2008 13:21:14 -0000 2008/12/12 Gabor PALI : > Rene Ladan wrote: >> 2008/12/12 Gabor PALI : >>> Maybe any other option to mention? I do not believe there is no >>> other perks of the job these days... >>> >> You can always brag to your friends/colleagues :-p > > Yeah, but you cannot write this into the committers-guide :) > > >> Besides Murray's answer I also need mentor approval for this. > > Do you still have a mentor for the en_US tree, do not you? :) > Yes, remko. > >> Is Murray associated with FreeBSDMall ? > > As far as I know, he was associated because he sent these announcements > to freebsd-announce until February 2005 [1]. In November 2005, Bob > Bruce sent an announcement [2] about 6.0-RELEASE, however no other > announcements were made after then (and no reduced price options were > mentioned in that message). > > Based on this, Bob Bruce or anybody else at FreeBSDMall should be > interviewed about the status of the statement in question. I will do this. > Ok. > > [1] > http://lists.freebsd.org/pipermail/freebsd-announce/2005-February/000980.html > [2] > http://lists.freebsd.org/pipermail/freebsd-announce/2005-November/001025.html > Regards, Rene -- http://www.rene-ladan.nl/ GPG fingerprint = E738 5471 D185 7013 0EE0 4FC8 3C1D 6F83 12E1 84F6 (subkeys.pgp.net) From owner-freebsd-doc@FreeBSD.ORG Fri Dec 12 16:47:38 2008 Return-Path: Delivered-To: freebsd-doc@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 02FD1106564A; Fri, 12 Dec 2008 16:47:38 +0000 (UTC) (envelope-from hrs@FreeBSD.org) Received: from mail.allbsd.org (unknown [IPv6:2001:2f0:104:e001::32]) by mx1.freebsd.org (Postfix) with ESMTP id B9E4B8FC08; Fri, 12 Dec 2008 16:47:37 +0000 (UTC) (envelope-from hrs@FreeBSD.org) Received: from delta.allbsd.org (p2191-ipbf1403funabasi.chiba.ocn.ne.jp [118.7.161.191]) (authenticated bits=128) by mail.allbsd.org (8.14.2/8.14.2) with ESMTP id mBCGlPAE010816; Sat, 13 Dec 2008 01:47:36 +0900 (JST) (envelope-from hrs@FreeBSD.org) Received: from localhost (alph.allbsd.org [192.168.0.10]) (authenticated bits=0) by delta.allbsd.org (8.13.4/8.13.4) with ESMTP id mBCGlFJa090153; Sat, 13 Dec 2008 01:47:19 +0900 (JST) (envelope-from hrs@FreeBSD.org) Date: Sat, 13 Dec 2008 01:43:25 +0900 (JST) Message-Id: <20081213.014325.183748569.hrs@allbsd.org> To: sonic2000gr@gmail.com From: Hiroki Sato In-Reply-To: <4941F694.3040600@gmail.com> References: <49403656.4020303@gmail.com> <8763lq14yo.fsf@kobe.laptop> <4941F694.3040600@gmail.com> X-PGPkey-fingerprint: BDB3 443F A5DD B3D0 A530 FFD7 4F2C D3D8 2793 CF2D X-Mailer: Mew version 6.1 on Emacs 22.2 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Multipart/Signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="--Security_Multipart(Sat_Dec_13_01_43_25_2008_690)--" Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV version 0.93.3, clamav-milter version 0.93.3 on gatekeeper.allbsd.org X-Virus-Status: Clean X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (mail.allbsd.org [133.31.130.32]); Sat, 13 Dec 2008 01:47:36 +0900 (JST) Cc: freebsd-doc@FreeBSD.org, keramida@FreeBSD.org Subject: Re: [PATCH] Adding elements to wlan Handbook section 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, 12 Dec 2008 16:47:38 -0000 ----Security_Multipart(Sat_Dec_13_01_43_25_2008_690)-- Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Manolis Kiagias wrote in <4941F694.3040600@gmail.com>: so> Giorgos Keramidas wrote: so> > On Wed, 10 Dec 2008 23:36:22 +0200, Manolis Kiagias wrote: so> > so> >> I've seen it in the Handbook, but in very few parts. It is also rendered so> >> very nicely, and is not at all distracting. (A lightweight, dotted so> >> underline). See here for an example: so> >> so> >> http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/network-ftp.html so> >> so> > so> > That looks good. I've started pushing to hg.hellug.gr some commits that so> > add this sort of role="" attribute to the wlan section :-) so> > so> > Manolis, I have a question that is mostly a style issue though. so> > so> > There are some compound acronyms in the wlan section, i.e. "WPA-TLS". so> > Would you prefer a separate for "WPA" and "TLS" like so> > so> > WPA- > role="Transport Layer Security">TLS so> > so> > or a single element like so> > so> > WPA-TLS so> > so> > The first seems more logical, and it would fit nicely with the set of so> > acronym entities (acronyms.ent) I proposed in another email of the so> > thread (eg. we won't have to introduce a new, special entity for so> > &acronym.wlan.wpa-tls; but we can reuse the WPA and TLS entities). I am so> > not sure if it would result in aesthetically pleasing output when the so> > dotted underlines appear in separate words though. so> > so> > so> > so> I agree that the first seems more logical and more effective as the so> entities can be reused. However the difference is really very small, so so> go along with the one you prefer. so> As for the dotted lines, they are so subtle anyway that it won't make so> much of a difference if they appear in separate words. This decision depends on the context, I think. "EAP" and "TLS" are words describing individual elemental technologies, and "EAP-TLS" describes a different one using these technologies, not simple combination of the two. In such a case, we should not reuse the definition in a way that it looks a combination of two acronyms. -- | Hiroki SATO ----Security_Multipart(Sat_Dec_13_01_43_25_2008_690)-- Content-Type: application/pgp-signature Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iEYEABECAAYFAklClK0ACgkQTyzT2CeTzy0WAwCgumGQs2NR0ZQ4D5CSpSc09bMo 4GEAoNQemKJq2meNuZBV0d7bn53BScxM =Pvx1 -----END PGP SIGNATURE----- ----Security_Multipart(Sat_Dec_13_01_43_25_2008_690)---- From owner-freebsd-doc@FreeBSD.ORG Fri Dec 12 16:47:38 2008 Return-Path: Delivered-To: doc@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5407F1065676; Fri, 12 Dec 2008 16:47:38 +0000 (UTC) (envelope-from hrs@FreeBSD.org) Received: from mail.allbsd.org (unknown [IPv6:2001:2f0:104:e001::32]) by mx1.freebsd.org (Postfix) with ESMTP id C554E8FC12; Fri, 12 Dec 2008 16:47:37 +0000 (UTC) (envelope-from hrs@FreeBSD.org) Received: from delta.allbsd.org (p2191-ipbf1403funabasi.chiba.ocn.ne.jp [118.7.161.191]) (authenticated bits=128) by mail.allbsd.org (8.14.2/8.14.2) with ESMTP id mBCGlPAG010816; Sat, 13 Dec 2008 01:47:36 +0900 (JST) (envelope-from hrs@FreeBSD.org) Received: from localhost (alph.allbsd.org [192.168.0.10]) (authenticated bits=0) by delta.allbsd.org (8.13.4/8.13.4) with ESMTP id mBCGlFJb090153; Sat, 13 Dec 2008 01:47:19 +0900 (JST) (envelope-from hrs@FreeBSD.org) Date: Sat, 13 Dec 2008 01:46:06 +0900 (JST) Message-Id: <20081213.014606.247395509.hrs@allbsd.org> To: keramida@FreeBSD.org From: Hiroki Sato In-Reply-To: <871vwdahna.fsf@kobe.laptop> References: <87k5a63z2d.fsf@kobe.laptop> <871vwdahna.fsf@kobe.laptop> X-PGPkey-fingerprint: BDB3 443F A5DD B3D0 A530 FFD7 4F2C D3D8 2793 CF2D X-Mailer: Mew version 6.1 on Emacs 22.2 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Multipart/Signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="--Security_Multipart0(Sat_Dec_13_01_46_06_2008_990)--" Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV version 0.93.3, clamav-milter version 0.93.3 on gatekeeper.allbsd.org X-Virus-Status: Clean X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (mail.allbsd.org [133.31.130.32]); Sat, 13 Dec 2008 01:47:36 +0900 (JST) Cc: doc@FreeBSD.org Subject: Re: [PATCH] Adding elements to wlan Handbook section 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, 12 Dec 2008 16:47:38 -0000 ----Security_Multipart0(Sat_Dec_13_01_46_06_2008_990)-- Content-Type: Multipart/Mixed; boundary="--Next_Part(Sat_Dec_13_01_46_06_2008_632)--" Content-Transfer-Encoding: 7bit ----Next_Part(Sat_Dec_13_01_46_06_2008_632)-- Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Giorgos Keramidas wrote in <871vwdahna.fsf@kobe.laptop>: ke> On Fri, 12 Dec 2008 08:51:07 +0100, "Rene Ladan" wrote: ke> > I am in favour of the full expansion, so that you can write ke> > ke> > Using &acronym.wlan.wep; encryption is not really safe anymore, ke> > but a lot of people use it anyway. ke> > ke> > This form is shorter and we don't have to write the word "acronym" ke> > three times. ke> > ke> > Maybe the acronyms can link to the glossary of the Handbook as well? ke> ke> That's an interesting idea :-) ke> ke> On Fri, 12 Dec 2008 09:58:28 +0100, Gabor PALI wrote: ke> > Maybe you can have different versions in the .ent file, like you did ke> > in case of mailing lists (defer the design decisions :)): ke> > ke> > WEP'> ke> > WEP'> ke> ke> Heh, cool! I'll try to update the patch to include entities like this. Hmm, this is not directly related to your idea, but I did not noticed that role attrib is used for adding the description so far. I think this is incorrect from viewpoint of DocBook because it is for classification of the element, not real content. In DocBook vocabulary, cannot have such a expanded text, unfortunately. As a workaround, how about using the following phrase: WEPWired Equivalent Privacy I use with role attrib here (probably this is the only option which looks reasonable). The necessary changes to the stylesheet and an SGML example of vm-design/article.sgml are attached (indentation is incomplete, though). We need to rewrite the existing elements, too. For entity definition, I like the following: FOODESC OF FOO'> Generating link to glossary, suppressing rendering of , or so on can be controlled by stylesheet, so multiple definitions are not needed at the level, IMHO. -- | Hiroki SATO ----Next_Part(Sat_Dec_13_01_46_06_2008_632)-- Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="acronym.diff" Index: share/sgml/freebsd.dsl =================================================================== RCS file: /home/ncvs/doc/share/sgml/freebsd.dsl,v retrieving revision 1.94 diff -d -u -I\$FreeBSD:.*\$ -I\$NetBSD:.*\$ -I\$OpenBSD:.*\$ -I\$DragonFly:.*\$ -I\$Id:.*\$ -I\$Translation:.*\$ -I\$hrs:.*\$ -r1.94 freebsd.dsl --- share/sgml/freebsd.dsl 24 May 2008 16:16:20 -0000 1.94 +++ share/sgml/freebsd.dsl 12 Dec 2008 16:13:56 -0000 @@ -78,19 +78,25 @@ ;; Taken from Norm's stylesheets; modified to add support for TITLE so ;; that we get a mouse over definition for acronyms in HTML output. - (define ($acronym-seq$ #!optional (sosofo (process-children))) - ;; FIXME: html4 only - (let ((title (attribute-string (normalize "role") (current-node)))) - (if title - (make element gi: "ACRONYM" - attributes: (list - (list "TITLE" title) - (list "CLASS" (gi))) - sosofo) - (make element gi: "ACRONYM" - attributes: (list - (list "CLASS" (gi))) - sosofo)))) +(define ($acronym-seq$ #!optional (sosofo (process-children))) + (let* ((acronym-remark (select-elements + (children (current-node)) + (normalize "remark")))) + (let* ((title (if (and acronym-remark + (equal? (attribute-string (normalize "role") acronym-remark) "acronym")) + (data acronym-remark) + ""))) + (make element gi: "ACRONYM" + attributes: (list + (list "CLASS" (gi)) + (list "TITLE" title)) + sosofo)))) + +(element (acronym remark) + (let* ((role (attribute-string (normalize "role")))) + (if (not (equal? role "acronym")) + ($charseq$) + (empty-sosofo)))) (define (book-titlepage-recto-elements) (list (normalize "title") @@ -305,6 +311,7 @@ (if (not (last-sibling? (current-node))) (literal ", ") (empty-sosofo)))) + ]]> Index: en_US.ISO8859-1/articles/vm-design/article.sgml =================================================================== RCS file: /home/ncvs/doc/en_US.ISO8859-1/articles/vm-design/article.sgml,v retrieving revision 1.16 diff -d -u -I\$FreeBSD:.*\$ -I\$NetBSD:.*\$ -I\$OpenBSD:.*\$ -I\$DragonFly:.*\$ -I\$Id:.*\$ -I\$Translation:.*\$ -I\$hrs:.*\$ -r1.16 article.sgml --- en_US.ISO8859-1/articles/vm-design/article.sgml 24 Sep 2006 13:36:59 -0000 1.16 +++ en_US.ISO8859-1/articles/vm-design/article.sgml 12 Dec 2008 16:25:08 -0000 @@ -34,7 +34,7 @@ The title is really just a fancy way of saying that I am going to - attempt to describe the whole VM enchilada, hopefully in a way that + attempt to describe the whole VMVirtual Memory enchilada, hopefully in a way that everyone can follow. For the last year I have concentrated on a number of major kernel subsystems within FreeBSD, with the VM and Swap subsystems being the most interesting and NFS being a necessary ----Next_Part(Sat_Dec_13_01_46_06_2008_632)---- ----Security_Multipart0(Sat_Dec_13_01_46_06_2008_990)-- Content-Type: application/pgp-signature Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iEYEABECAAYFAklClU4ACgkQTyzT2CeTzy01sACdHFFABUM+GFAfUH4/7WN2ROui KxYAnjuO7RXs2GxfHmTcq/+uOF2uR+0X =jvdq -----END PGP SIGNATURE----- ----Security_Multipart0(Sat_Dec_13_01_46_06_2008_990)---- From owner-freebsd-doc@FreeBSD.ORG Fri Dec 12 17:09:02 2008 Return-Path: Delivered-To: doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 213331065672 for ; Fri, 12 Dec 2008 17:09:02 +0000 (UTC) (envelope-from murray@stokely.org) Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.228]) by mx1.freebsd.org (Postfix) with ESMTP id F30A68FC23 for ; Fri, 12 Dec 2008 17:09:01 +0000 (UTC) (envelope-from murray@stokely.org) Received: by rv-out-0506.google.com with SMTP id f9so2362233rvb.3 for ; Fri, 12 Dec 2008 09:09:01 -0800 (PST) Received: by 10.141.128.19 with SMTP id f19mr1772977rvn.9.1229099811832; Fri, 12 Dec 2008 08:36:51 -0800 (PST) Received: by 10.141.151.6 with HTTP; Fri, 12 Dec 2008 08:36:51 -0800 (PST) Message-ID: <2a7894eb0812120836l4010d213y373f38d544468274@mail.gmail.com> Date: Fri, 12 Dec 2008 08:36:51 -0800 From: "Murray Stokely" To: "Giorgos Keramidas" In-Reply-To: <871vwdahna.fsf@kobe.laptop> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <871vwfn418.fsf@kobe.laptop> <2a7894eb0812101310v2123a452q26b0e07630e7f209@mail.gmail.com> <878wqnafso.fsf@kobe.laptop> <2a7894eb0812101322o77b12fc9k8208f83d62481ad3@mail.gmail.com> <87k5a63z2d.fsf@kobe.laptop> <871vwdahna.fsf@kobe.laptop> Cc: doc@freebsd.org Subject: Re: [PATCH] Adding elements to wlan Handbook section 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, 12 Dec 2008 17:09:02 -0000 On Fri, Dec 12, 2008 at 1:04 AM, Giorgos Keramidas wrote: >> Maybe the acronyms can link to the glossary of the Handbook as well? > > That's an interesting idea :-) I think the popups are less distracting. We've experimented with things like linking to the glossary, and the New York Times took it to the extreme for years with a weird javascript send-to-dictionary for any selected text, and I think it is a net loss personally. Subtle pop up definition for first occurrence of each acronym per chapter is the best of both worlds I think. - Murray From owner-freebsd-doc@FreeBSD.ORG Fri Dec 12 23:07:52 2008 Return-Path: Delivered-To: doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 07B641065675 for ; Fri, 12 Dec 2008 23:07:52 +0000 (UTC) (envelope-from bill@shakespeare-nyc.com) Received: from mx1.triple8.net (mx1.triple8.net [208.80.181.30]) by mx1.freebsd.org (Postfix) with ESMTP id DF4998FC14 for ; Fri, 12 Dec 2008 23:07:51 +0000 (UTC) (envelope-from bill@shakespeare-nyc.com) Received: from static-64-115-169-50.isp.broadviewnet.net [64.115.169.50] by mx1.triple8.net with SMTP; Fri, 12 Dec 2008 14:52:44 -0800 Message-ID: <4942EB33.5080504@shakespeare-nyc.com> Date: Fri, 12 Dec 2008 17:52:35 -0500 From: Bill Kurland User-Agent: Thunderbird 2.0.0.18 (Windows/20081105) MIME-Version: 1.0 To: doc@FreeBSD.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: errata? 3.3.1 Symbolic Permissions 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, 12 Dec 2008 23:07:52 -0000 I don't know if this is the proper way to advise you of possible errors in the documentation, but ... > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/permissions.html A comma separated list can be provided when more than one set of changes to a file must be made. For example the following command will remove the group and "world" write permission on /FILE/, then it adds the execute permissions for everyone: ^^^^^ % chmod go-w,a+x /FILE Should not this read "other" ? / -- Bill Kurland Shakespeare & Co 137 E 23 Street New York, NY 10010 212-505-2021 -- The difference between the almost right word & the right word is really a large matter --it's the difference between the lightning bug and the lightning. - Mark Twain Letter to George Bainton, 10/15/1888 From owner-freebsd-doc@FreeBSD.ORG Sat Dec 13 01:59:26 2008 Return-Path: Delivered-To: doc@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 766BF1065675 for ; Sat, 13 Dec 2008 01:59:26 +0000 (UTC) (envelope-from danger@FreeBSD.org) Received: from services.rulez.sk (services.rulez.sk [92.240.234.125]) by mx1.freebsd.org (Postfix) with ESMTP id 2ECC58FC12 for ; Sat, 13 Dec 2008 01:59:26 +0000 (UTC) (envelope-from danger@FreeBSD.org) Received: from localhost (services.rulez.sk [92.240.234.125]) by services.rulez.sk (Postfix) with ESMTP id E2142133449B; Sat, 13 Dec 2008 02:40:34 +0100 (CET) X-Virus-Scanned: amavisd-new at rulez.sk Received: from services.rulez.sk ([92.240.234.125]) by localhost (services.rulez.sk [92.240.234.125]) (amavisd-new, port 10024) with ESMTP id BHz-L6RFUOH9; Sat, 13 Dec 2008 02:40:34 +0100 (CET) Received: from DANGER-PC (danger.mcrn.sk [84.16.37.254]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: danger@rulez.sk) by services.rulez.sk (Postfix) with ESMTPSA id 35539133442A; Sat, 13 Dec 2008 02:40:34 +0100 (CET) Date: Sat, 13 Dec 2008 02:40:23 +0100 From: Daniel Gerzo Organization: The FreeBSD Project X-Priority: 3 (Normal) Message-ID: <403849365.20081213024023@rulez.sk> To: Bill Kurland In-Reply-To: <4942EB33.5080504@shakespeare-nyc.com> References: <4942EB33.5080504@shakespeare-nyc.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Cc: doc@FreeBSD.org Subject: Re: errata? 3.3.1 Symbolic Permissions X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Daniel Gerzo List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Dec 2008 01:59:26 -0000 Hello Bill, Friday, December 12, 2008, 11:52:35 PM, you wrote: > A comma separated list can be provided when more than one set of changes > to a file must be made. For example the following command will remove=20 > the group and "world" write permission on /FILE/, then it adds the=20 > execute permissions for everyone: > ^^^^^ > % chmod go-w,a+x /FILE > Should not this read "other" ? I think the description is correct, maybe I'm missing something? --=20 Best regards, Daniel mailto:danger@FreeBSD.org From owner-freebsd-doc@FreeBSD.ORG Sat Dec 13 06:53:26 2008 Return-Path: Delivered-To: doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 816E81065676 for ; Sat, 13 Dec 2008 06:53:26 +0000 (UTC) (envelope-from pali.gabor@googlemail.com) Received: from mail-bw0-f14.google.com (mail-bw0-f14.google.com [209.85.218.14]) by mx1.freebsd.org (Postfix) with ESMTP id BC2448FC12 for ; Sat, 13 Dec 2008 06:53:25 +0000 (UTC) (envelope-from pali.gabor@googlemail.com) Received: by bwz7 with SMTP id 7so4128946bwz.19 for ; Fri, 12 Dec 2008 22:53:24 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:received:received:sender:message-id:date:from :organization:user-agent:mime-version:to:cc:subject:references :in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; bh=DnDJ3TxtOCjH57RWh9wqeJF12e3+KKuu1JZpdXLSQMQ=; b=GCLL5AMI0XvydQ/ETFMEb1ZVftf0N+aGs0lhm503qqfeca+8/GyRZACZQpt9XxC2bk FJoTh1MP6J+GmbhhUYDJNeY5nSiH/LnvAKG1a6k4C/lHGtlTEwbYzaZLYbiM5yG/vrBb tdf8YBaemclK+Lhw5alxSPwINxhBDC7WCxOYo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=sender:message-id:date:from:organization:user-agent:mime-version:to :cc:subject:references:in-reply-to:x-enigmail-version:content-type :content-transfer-encoding; b=p3S8fFSXzK7X/9uUybH4n3rSZnW2vcQqXxcE/pXWNynVPrBUC6Xe20XR1FS+4UxdcS KnMEpqktbNgZvJ9IlfauJSoGv+hs4Q86af3NFmOJO5ck6p+ojz7Ew7xIiMiMR7lYZtNT GaGC4naQnUsJBWws4QdpMwgHa+gDPu8LakIY0= Received: by 10.181.204.4 with SMTP id g4mr1590478bkq.114.1229151204073; Fri, 12 Dec 2008 22:53:24 -0800 (PST) Received: from ?192.168.1.110? (catv-89-132-186-236.catv.broadband.hu [89.132.186.236]) by mx.google.com with ESMTPS id z15sm2484407fkz.8.2008.12.12.22.53.22 (version=TLSv1/SSLv3 cipher=RC4-MD5); Fri, 12 Dec 2008 22:53:22 -0800 (PST) Sender: =?UTF-8?B?UMOBTEkgR8OhYm9yIErDoW5vcw==?= Message-ID: <49435BD3.9030400@FreeBSD.org> Date: Sat, 13 Dec 2008 07:53:07 +0100 From: Gabor PALI Organization: The FreeBSD Project User-Agent: Thunderbird 2.0.0.17 (X11/20081023) MIME-Version: 1.0 To: Hiroki Sato References: <87k5a63z2d.fsf@kobe.laptop> <871vwdahna.fsf@kobe.laptop> <20081213.014606.247395509.hrs@allbsd.org> In-Reply-To: <20081213.014606.247395509.hrs@allbsd.org> X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: doc@FreeBSD.org, keramida@FreeBSD.org Subject: Re: [PATCH] Adding elements to wlan Handbook section 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, 13 Dec 2008 06:53:26 -0000 Hiroki Sato wrote: > Hmm, this is not directly related to your idea, but I did not noticed > that role attrib is used for adding the description so far. True, you are right :) > I use with role attrib here (probably this is the only > option which looks reasonable). Great! > We need to rewrite the existing elements, too. I happily volunteer to do this, if there is an accepted solution. > For entity definition, I like the following: > > FOODESC OF FOO'> > > Generating link to glossary, suppressing rendering of , or so > on can be controlled by stylesheet, so multiple definitions are not > needed at the level, IMHO. I think that is a perfect solution, I like it too. Regards, :g