From marc at blackend.org Mon Dec 1 00:09:24 2008 From: marc at blackend.org (Marc Fonvieille) Date: Mon Dec 1 00:09:31 2008 Subject: [Sort of RFC] Ports and packages for docs Message-ID: <20081201080917.GA1330@gothic.blackend.org> Hello, Currently, it's difficult for the average user to update his docs. Most of time, the docs are installed during OS install time and are never updated. Another problem is the fact the doc build requires a lot of diskspace and a lot of time on slow architectures/CPUs/etc which is a problem during release process. To sum up, we're lacking of a simple way to install and update docs without any compilation operation. I'm working since a while on ports for doc, so here are the first packages available for test: http://people.freebsd.org/~blackend/pkgs/bn-freebsd-doc-20081130.tbz http://people.freebsd.org/~blackend/pkgs/da-freebsd-doc-20081130.tbz http://people.freebsd.org/~blackend/pkgs/de-freebsd-doc-20081130.tbz http://people.freebsd.org/~blackend/pkgs/el-freebsd-doc-20081130.tbz http://people.freebsd.org/~blackend/pkgs/en-freebsd-doc-20081130.tbz http://people.freebsd.org/~blackend/pkgs/es-freebsd-doc-20081130.tbz http://people.freebsd.org/~blackend/pkgs/fr-freebsd-doc-20081130.tbz http://people.freebsd.org/~blackend/pkgs/hu-freebsd-doc-20081130.tbz http://people.freebsd.org/~blackend/pkgs/it-freebsd-doc-20081130.tbz http://people.freebsd.org/~blackend/pkgs/ja-freebsd-doc-20081130.tbz http://people.freebsd.org/~blackend/pkgs/mn-freebsd-doc-20081130.tbz http://people.freebsd.org/~blackend/pkgs/nl-freebsd-doc-20081130.tbz http://people.freebsd.org/~blackend/pkgs/pl-freebsd-doc-20081130.tbz http://people.freebsd.org/~blackend/pkgs/pt-freebsd-doc-20081130.tbz http://people.freebsd.org/~blackend/pkgs/ru-freebsd-doc-20081130.tbz http://people.freebsd.org/~blackend/pkgs/sr-freebsd-doc-20081130.tbz http://people.freebsd.org/~blackend/pkgs/tr-freebsd-doc-20081130.tbz http://people.freebsd.org/~blackend/pkgs/zh_cn-freebsd-doc-20081130.tbz http://people.freebsd.org/~blackend/pkgs/zh_tw-freebsd-doc-20081130.tbz These packages provide html-split version (of course other formats are possible, I just want to limit the bandwidth) of the 20081130 docset. Another thing to note, the packages install docs in /usr/local/share/doc/freebsd So just: pkg_add -r http://people.freebsd.org/~blackend/pkgs/en-freebsd-doc-20081130.tbz and tell me if you like it :) -- Marc From pav at FreeBSD.org Mon Dec 1 01:18:01 2008 From: pav at FreeBSD.org (Pav Lucistnik) Date: Mon Dec 1 01:18:08 2008 Subject: [Sort of RFC] Ports and packages for docs In-Reply-To: <20081201080917.GA1330@gothic.blackend.org> References: <20081201080917.GA1330@gothic.blackend.org> Message-ID: <1228120711.91796.16.camel@pav.hide.vol.cz> Marc Fonvieille p??e v po 01. 12. 2008 v 09:09 +0100: > Currently, it's difficult for the average user to update his docs. > Most of time, the docs are installed during OS install time and are > never updated. You aware of this? http://www.oook.cz/bsd/docsnap.html I admit it's kind of hidden. -- Pav Lucistnik East or west, ~ is best. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: Toto je =?UTF-8?Q?digit=C3=A1ln=C4=9B?= =?ISO-8859-1?Q?_podepsan=E1?= =?UTF-8?Q?_=C4=8D=C3=A1st?= =?ISO-8859-1?Q?_zpr=E1vy?= Url : http://lists.freebsd.org/pipermail/freebsd-doc/attachments/20081201/e7e009da/attachment.pgp From pgj at FreeBSD.org Mon Dec 1 01:48:39 2008 From: pgj at FreeBSD.org (Gabor PALI) Date: Mon Dec 1 01:48:45 2008 Subject: [Sort of RFC] Ports and packages for docs In-Reply-To: <20081201080917.GA1330@gothic.blackend.org> References: <20081201080917.GA1330@gothic.blackend.org> Message-ID: <4933B2E8.10507@FreeBSD.org> Marc Fonvieille wrote: > I'm working since a while on ports for doc [..] and tell me if you > like it :) I think generally it is a good idea to reanimate the concept documentation packages, however last time I asked about them (May 2008, while fixing the FAQ), I got an interesting answer [1] from Hiroki Sato: "The doc packages are no longer available because the past discussion reached a consensus that generating them is a bit tricky and most of people do not need such packages because the latest documentation is always available on the web." Regards, :g [1] http://lists.freebsd.org/pipermail/freebsd-doc/2008-May/014318.html From blackend at FreeBSD.org Mon Dec 1 01:55:23 2008 From: blackend at FreeBSD.org (Marc Fonvieille) Date: Mon Dec 1 01:55:30 2008 Subject: [Sort of RFC] Ports and packages for docs In-Reply-To: <1228120711.91796.16.camel@pav.hide.vol.cz> References: <20081201080917.GA1330@gothic.blackend.org> <1228120711.91796.16.camel@pav.hide.vol.cz> Message-ID: <20081201095520.GB1330@gothic.blackend.org> On Mon, Dec 01, 2008 at 09:38:31AM +0100, Pav Lucistnik wrote: > Marc Fonvieille p??e v po 01. 12. 2008 v 09:09 +0100: > > > Currently, it's difficult for the average user to update his docs. > > Most of time, the docs are installed during OS install time and are > > never updated. > > You aware of this? > > http://www.oook.cz/bsd/docsnap.html > > I admit it's kind of hidden. It is :) The objective is different, with packages people will be able to easily choose language, update (with portupgrade, portmaster etc.), formats like PDF will be provided, the base system is not touched. Nothing more than a simple pkg_add(1) command should be required. The release rolling job will be easier, and at install time the user could (once implemented) really choose what localized doc to install, etc. -- Marc -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 187 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-doc/attachments/20081201/ca21529c/attachment.pgp From tonycn101 at gmail.com Mon Dec 1 02:34:11 2008 From: tonycn101 at gmail.com (Anthony Aka) Date: Mon Dec 1 02:34:19 2008 Subject: Utterly Confidential.. Message-ID: <20081201094613.753EB21369D@hosted.top.net.ua> Hi, Pardon me for not having the pleasure of knowing your mindset before making you this offer and it is utterly confidential and genuine by virtue of its nature.I write to solicit your assistance in a funds transfer deal involving US$ 3.5M.This fund has been stashed out of the excess profit made last year by my branch office the International Commercial Bank which I am the manager. I have already submitted an approved end of the year report for the year 2005 to my head office here in Accra-Ghana and they will never know of this excess. I have since then, placed this amount on a Non-Investment Account without a beneficiary. Upon your response, I will configure your name on our database as holder of the Non-Investment Account. I will then guide you on how to apply to my head office for the Account Closure/ bank-to-bank remittance of the funds to your designated bank account. If you concur with this proposal, I intend for you to retain 30% of the funds while 70% shall be for me. Kindly forward your response to: tonycn101@aol.com Mobile: +233-24-468-5072 With Regards, Anthony Aka. From blackend at FreeBSD.org Mon Dec 1 02:35:35 2008 From: blackend at FreeBSD.org (Marc Fonvieille) Date: Mon Dec 1 02:35:41 2008 Subject: [Sort of RFC] Ports and packages for docs In-Reply-To: <4933B2E8.10507@FreeBSD.org> References: <20081201080917.GA1330@gothic.blackend.org> <4933B2E8.10507@FreeBSD.org> Message-ID: <20081201103533.GC1330@gothic.blackend.org> On Mon, Dec 01, 2008 at 10:48:24AM +0100, Gabor PALI wrote: > Marc Fonvieille wrote: > > I'm working since a while on ports for doc [..] and tell me if you > > like it :) > > I think generally it is a good idea to reanimate the concept > documentation packages, however last time I asked about them (May 2008, > while fixing the FAQ), I got an interesting answer [1] from Hiroki Sato: > > "The doc packages are no longer available because the past discussion > reached a consensus that generating them is a bit tricky and most of > people do not need such packages because the latest documentation is > always available on the web." > [...] But you cut the last sentence :) Yes, it was difficult to maintain them and we had no real solution to continue to provide them. It's true that the doc is available via the web, but as I said the aim is not only provide packages to the user but also modernize the doc installation and build for the releases. Now, I have a working solution that can be updated, etc. without headaches, so we may have to rethink about the current situation. -- Marc From bugmaster at FreeBSD.org Mon Dec 1 03:06:06 2008 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Dec 1 03:06:37 2008 Subject: Current unassigned doc problem reports Message-ID: <200812011106.mB1B65OG051602@freefall.freebsd.org> (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/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 178 problems total. From trhodes at FreeBSD.org Mon Dec 1 05:41:50 2008 From: trhodes at FreeBSD.org (Tom Rhodes) Date: Mon Dec 1 05:42:02 2008 Subject: [Sort of RFC] Ports and packages for docs In-Reply-To: <20081201080917.GA1330@gothic.blackend.org> References: <20081201080917.GA1330@gothic.blackend.org> Message-ID: <20081201084131.74ecf576.trhodes@FreeBSD.org> On Mon, 1 Dec 2008 09:09:17 +0100 Marc Fonvieille wrote: > Hello, > > Currently, it's difficult for the average user to update his docs. > Most of time, the docs are installed during OS install time and are > never updated. > Another problem is the fact the doc build requires a lot of diskspace > and a lot of time on slow architectures/CPUs/etc which is a problem > during release process. > > To sum up, we're lacking of a simple way to install and update docs > without any compilation operation. > I'm working since a while on ports for doc, so here are the first > packages available for test: > > http://people.freebsd.org/~blackend/pkgs/bn-freebsd-doc-20081130.tbz > http://people.freebsd.org/~blackend/pkgs/da-freebsd-doc-20081130.tbz > http://people.freebsd.org/~blackend/pkgs/de-freebsd-doc-20081130.tbz > http://people.freebsd.org/~blackend/pkgs/el-freebsd-doc-20081130.tbz > http://people.freebsd.org/~blackend/pkgs/en-freebsd-doc-20081130.tbz > http://people.freebsd.org/~blackend/pkgs/es-freebsd-doc-20081130.tbz > http://people.freebsd.org/~blackend/pkgs/fr-freebsd-doc-20081130.tbz > http://people.freebsd.org/~blackend/pkgs/hu-freebsd-doc-20081130.tbz > http://people.freebsd.org/~blackend/pkgs/it-freebsd-doc-20081130.tbz > http://people.freebsd.org/~blackend/pkgs/ja-freebsd-doc-20081130.tbz > http://people.freebsd.org/~blackend/pkgs/mn-freebsd-doc-20081130.tbz > http://people.freebsd.org/~blackend/pkgs/nl-freebsd-doc-20081130.tbz > http://people.freebsd.org/~blackend/pkgs/pl-freebsd-doc-20081130.tbz > http://people.freebsd.org/~blackend/pkgs/pt-freebsd-doc-20081130.tbz > http://people.freebsd.org/~blackend/pkgs/ru-freebsd-doc-20081130.tbz > http://people.freebsd.org/~blackend/pkgs/sr-freebsd-doc-20081130.tbz > http://people.freebsd.org/~blackend/pkgs/tr-freebsd-doc-20081130.tbz > http://people.freebsd.org/~blackend/pkgs/zh_cn-freebsd-doc-20081130.tbz > http://people.freebsd.org/~blackend/pkgs/zh_tw-freebsd-doc-20081130.tbz > > These packages provide html-split version (of course other formats are > possible, I just want to limit the bandwidth) of the 20081130 docset. > Another thing to note, the packages install docs in > /usr/local/share/doc/freebsd > > So just: > > pkg_add -r http://people.freebsd.org/~blackend/pkgs/en-freebsd-doc-20081130.tbz > > and tell me if you like it :) Actually, this seems like a pretty good idea. As long as we can keep it updated for people, I'm sure there are users out there who would love to have updated documentation as time goes on. Thanks! -- Tom Rhodes From sonic2000gr at gmail.com Mon Dec 1 06:02:59 2008 From: sonic2000gr at gmail.com (Manolis Kiagias) Date: Mon Dec 1 06:03:06 2008 Subject: [Sort of RFC] Ports and packages for docs In-Reply-To: <20081201080917.GA1330@gothic.blackend.org> References: <20081201080917.GA1330@gothic.blackend.org> Message-ID: <4933EE8D.4020001@gmail.com> Marc Fonvieille wrote: > Hello, > > Currently, it's difficult for the average user to update his docs. > Most of time, the docs are installed during OS install time and are > never updated. > Another problem is the fact the doc build requires a lot of diskspace > and a lot of time on slow architectures/CPUs/etc which is a problem > during release process. > > To sum up, we're lacking of a simple way to install and update docs > without any compilation operation. > I'm working since a while on ports for doc, so here are the first > packages available for test: > > http://people.freebsd.org/~blackend/pkgs/bn-freebsd-doc-20081130.tbz > http://people.freebsd.org/~blackend/pkgs/da-freebsd-doc-20081130.tbz > http://people.freebsd.org/~blackend/pkgs/de-freebsd-doc-20081130.tbz > http://people.freebsd.org/~blackend/pkgs/el-freebsd-doc-20081130.tbz > > So just: > > pkg_add -r http://people.freebsd.org/~blackend/pkgs/en-freebsd-doc-20081130.tbz > > and tell me if you like it :) > > This is actually a nice idea - in fact it would be great for the Greek documentation set, which is constantly changing as more translations are added. I just tried the el package and it works great. I could even include this in some custom package cd sets I am giving out to people. Having local docs is very important for people without always-on Internet (and I know quite a few) Since as you said you have a way of automating this, my only other question would be how often will these be updated. Are you planning, say, for monthly releases? From pgj at FreeBSD.org Mon Dec 1 06:13:54 2008 From: pgj at FreeBSD.org (Gabor PALI) Date: Mon Dec 1 06:14:26 2008 Subject: [Sort of RFC] Ports and packages for docs In-Reply-To: <1228120711.91796.16.camel@pav.hide.vol.cz> References: <20081201080917.GA1330@gothic.blackend.org> <1228120711.91796.16.camel@pav.hide.vol.cz> Message-ID: <4933F113.4010100@FreeBSD.org> Pav Lucistnik wrote: > http://www.oook.cz/bsd/docsnap.html > > I admit it's kind of hidden. Why have not you documented it? :) I would be happy see a short description of this method in the Handbook, for example, in Chapter "Updating FreeBSD", right next to portsnap. Regards, :g From trhodes at FreeBSD.org Mon Dec 1 06:17:36 2008 From: trhodes at FreeBSD.org (Tom Rhodes) Date: Mon Dec 1 06:17:43 2008 Subject: RFR: A "Boot Time Splash Screens" Section to the Handbook In-Reply-To: <49330A66.8040801@FreeBSD.org> References: <493155ED.8020004@FreeBSD.org> <49316309.1050407@gmail.com> <49330A66.8040801@FreeBSD.org> Message-ID: <20081201091730.0ef555fa.trhodes@FreeBSD.org> On Sun, 30 Nov 2008 22:49:26 +0100 Gabor PALI wrote: > Manolis Kiagias wrote: > > Here are a few nits you may want to act on. > > Thank you for your review. I fixed all the problems you pointed out and > created a new version [1][2]. > > > > I can't tell about technical accuracy. > > Hm, it seems I should really test the description myself :) > > > > "Note that, a 320x200 ___splash screen___ image will be displayed as a > > small block in the center of a solid white background screen." => I > > don't understand what you mean by this. Since the resolution at boot > > will be 320x200, the splash screen will still fill the entire screen. > > Do you mean to compare the size of the image to a typical desktop? > > To be honest, it was (blindly) imported from the original text. As far > as I remember (I used splash screens about three years ago), it wants to > tell you something like "if you have a 320x200 image but the resolution > is higher, then it will be put in the middle of the screen". Anyway, I > removed this sentence, since I do not see any clear connection with the > other sentences. > > > > While discussing text mode screensavers, it might be worth mentioning > > that you can get the list of available savers by ls > > /boot/kernel/*saver.ko or something along that line. > > Instead of this, I simply referenced the splash(4) manual page, it > should be enough. > > > > I also feel some longer sentences could use a few commas. > > I tried to insert those commas, and split some longer sentences up into > smaller ones. > > > > I've only peeked at the SGML, but I am sure there is nothing to fix > > there :) > > Thank you for trusting my SGML skills :) > > > Note for native speakers: please, review! You asked. :P Index: chapter.sgml =================================================================== RCS file: /home/dcvs/doc/en_US.ISO8859-1/books/handbook/boot/chapter.sgml,v retrieving revision 1.65 diff -u -r1.65 chapter.sgml --- chapter.sgml 30 May 2006 23:08:23 -0000 1.65 +++ chapter.sgml 30 Nov 2008 21:53:30 -0000 @@ -507,6 +507,192 @@ + + + + + + Joseph J. + Barbish + Contributed by + + + + + Boot Time Splash Screens + + &os; has a feature to allow the display of a splash + screen in place of showing boot messages. This makes + for a clearer visually experience getting to the legacy What? How about: "The splash screen creates a more visually appealing boot screen comparied to the original boot messages. This screen will be displayed until a console login prompt or X Display Manager offers a login prompt." + virtual console text login prompt and/or the X Display Manager + graphical login screen. + + There are two basic environments available in &os;. The + first is the default legacy virtual console text command line Axe the "text" word here. + environment. After the system finishes booting, a virtual + console text login prompt is presented. The second Probably axe "text" here too - I know you're attempting to describe the look; however, it just sounds odd to me. Similar below. + environment is the X11 Desktop graphical environment. After + X11 and one of the graphical + desktop environments, such as + GNOME, + KDE, or + XFce are installed, the X11 desktop + can be launched from the command line by using the + startx command. + + Some X11 users may select not to stop "may elect" here, but I think this entire bit needs reworded. "Some users prefer the X11 desktop graphical login screen over the traditional text based login prompt." is one example of a better sentence. + at the virtual console login prompt at boot time, but go + directly to the X11 desktop display manager's graphical login + screen. Popular choices are XDM, + the display manager of &xorg;, gdm + for GNOME, and + kdm for + KDE, but any other display manager + found in the Ports Collection could be used. These display Not sure about this sentence either. :( + managers basically provide a graphical login screen in place + of the default legacy virtual console text login prompt. + After a successful login, they present the user with a + graphical desktop. + + In the virtual console text command line environment, the + splash screen would hide all the boot probe messages and task + startup messages before displaying the login prompt. In X11 + environment, the users would get a visually clearer system + start up experience resembling something closer to what a + (µsoft; &windows; or non-unix type system) user would + experience. + + + Splash Screen Function + + The splash screen function only supports + 256-color bitmap (.bmp) or ZSoft + PCX (.pcx) files. + In addition, the splash image files must have a resolution + of 320 by 200 pixels or less to work on standard VGA + adapters. + + To use larger images, up to the maximum resolution + supported by the video card, activate the + VESA support included in &os;. This can + be enabled by loading the VESA module + during system boot, or adding a VESA + kernel configuration option and building a custom kernel + (see ). The + VESA support gives users the ability to + display a splash screen image that fills the + whole display screen. + + While the splash screen is being + displayed during the booting process, it can be turned off + any time by hitting a key. "by hitting any key on the keyboard." + + The splash screen defaults to becoming a + screen saver. After a time period of non-use the screen "also defaults to being a screen saver outside of X11." + will change to the splash screen and cycle + through steps of changing intensity of the image, from + bright intensity to a very dark intensity and over again. + This default splash screen (screen saver) + behavior could be overridden by adding a + saver= line to + /etc/rc.conf. Option + saver= has several built-in screen savers + to choose from, the full list can be found in the + &man.splash.4; manual page. The default splash + screen screen saver is called warp. + Note that, the saver= option specified in "Note that the ..." + /etc/rc.conf only applies to virtual + consoles. It has no effect on X11 display managers. + + At boot time with the splash screen + enabled, a few boot loader messages still could be seen leading + up to and including the boot options menu, and a timed wait + count down prompt before the splash screen is + displayed. This sentence is a bit much. + + Sample splash screen files can be downloaded from the + gallery at . + + + + Enabling the Splash Screen Function + + The splash screen + (.bmp) or (.pcx) + file has to be placed in the /boot directory. + + For default boot display resolution (256-color, 320 by + 200 pixels, or less), edit + /boot/loader.conf, so it contains the + following: + + splash_bmp_load="YES" +bitmap_load="YES" +bitmap_name="/boot/splash.bmp" + + For larger video resolutions up to the maximum of the + video card, edit /boot/loader.conf, so + it contains the following: + + vesa_load="YES" +splash_bmp_load="YES" +bitmap_load="YES" +bitmap_name="/boot/splash.bmp" + + The above assumes that + /boot/splash.bmp + is used for splash screen. When a PCX + file is desired, use the previous statements, plus the + vesa_load="YES" line depending on the + resolution. + + splash_pcx_load="YES" +bitmap_load="YES" +bitmap_name="/boot/splash.pcx" + + The file name is not really restricted to Axe the word "really" here. + splash as shown in the above example. It can + be anything as long as it has type of BMP + or PCX, such as + splash_640x400.bmp + or + blue_wave.pcx. + + There are another two possible interesting + loader.conf options. Not sure about this one. + + + + beastie_disable="YES" + + + This will stop the boot options menu from being + displayed, but the timed wait count down prompt will + still be present. Even with the display of the boot + options menu disabled, entering an option selection at + the timed wait count down prompt will enact the + corresponding boot option. + + + + + loader_logo="beastie" + + + This will replace the default words + &os;, which are displayed to the right + of the boot options menu with the colored beastie logo + like releases in the past had. + + + + + For more information, please see the &man.splash.4;, + &man.loader.conf.5;, and &man.vga.4; manual pages. + + Hope that helps. -- Tom Rhodes From pav at FreeBSD.org Mon Dec 1 06:25:30 2008 From: pav at FreeBSD.org (Pav Lucistnik) Date: Mon Dec 1 06:25:37 2008 Subject: [Sort of RFC] Ports and packages for docs In-Reply-To: <4933F113.4010100@FreeBSD.org> References: <20081201080917.GA1330@gothic.blackend.org> <1228120711.91796.16.camel@pav.hide.vol.cz> <4933F113.4010100@FreeBSD.org> Message-ID: <1228141525.91796.56.camel@pav.hide.vol.cz> Gabor PALI p??e v po 01. 12. 2008 v 15:13 +0100: > Pav Lucistnik wrote: > > http://www.oook.cz/bsd/docsnap.html > > > > I admit it's kind of hidden. > > Why have not you documented it? :) I would be happy see a short > description of this method in the Handbook, for example, in Chapter > "Updating FreeBSD", right next to portsnap. Sounds good. Can you come up with a patch? -- Pav Lucistnik 42.7 percent of all statistics are made up on the spot. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: Toto je =?UTF-8?Q?digit=C3=A1ln=C4=9B?= =?ISO-8859-1?Q?_podepsan=E1?= =?UTF-8?Q?_=C4=8D=C3=A1st?= =?ISO-8859-1?Q?_zpr=E1vy?= Url : http://lists.freebsd.org/pipermail/freebsd-doc/attachments/20081201/cb90b1c9/attachment.pgp From pgj at FreeBSD.org Mon Dec 1 06:57:21 2008 From: pgj at FreeBSD.org (Gabor PALI) Date: Mon Dec 1 06:58:44 2008 Subject: [Sort of RFC] Ports and packages for docs In-Reply-To: <1228141525.91796.56.camel@pav.hide.vol.cz> References: <20081201080917.GA1330@gothic.blackend.org> <1228120711.91796.16.camel@pav.hide.vol.cz> <4933F113.4010100@FreeBSD.org> <1228141525.91796.56.camel@pav.hide.vol.cz> Message-ID: <4933FB47.7050704@FreeBSD.org> Pav Lucistnik wrote: > Gabor PALI p??e v po 01. 12. 2008 v 15:13 +0100: >>> http://www.oook.cz/bsd/docsnap.html >> >> Why have not you documented it? :) I would be happy see a short >> description of this method in the Handbook, for example, in Chapter >> "Updating FreeBSD", right next to portsnap. > > Sounds good. Can you come up with a patch? > Well, originally, I hoped you will do this for us :) But yes, I would be also happy to write a short description on this method for the Handbook. May be end of next week? Regards, :g From pgj at FreeBSD.org Mon Dec 1 07:00:44 2008 From: pgj at FreeBSD.org (Gabor PALI) Date: Mon Dec 1 07:00:50 2008 Subject: [Sort of RFC] Ports and packages for docs In-Reply-To: <4933EE8D.4020001@gmail.com> References: <20081201080917.GA1330@gothic.blackend.org> <4933EE8D.4020001@gmail.com> Message-ID: <4933FC12.1060806@FreeBSD.org> Manolis Kiagias wrote: > Marc Fonvieille wrote: >> [..] I'm working since a while on ports for doc [..] > [..] > Since as you said you have a way of automating this, my only other > question would be how often will these be updated. Are you planning, > say, for monthly releases? Yes, it is a good question indeed. Some other questions in connection with this: - Where are these packages build and stored? - Would they be the part of the Ports Collection? If the answer is yes (a conditional subquestion): - Will they have a separate category? - Will they be maintained separately? - Who should maintain them? (In my opinion, every localized documentation package content should be maintained and regulated by the translators themselves.) Regards, :g From blackend at FreeBSD.org Mon Dec 1 07:03:57 2008 From: blackend at FreeBSD.org (Marc Fonvieille) Date: Mon Dec 1 07:04:06 2008 Subject: [Sort of RFC] Ports and packages for docs In-Reply-To: <4933EE8D.4020001@gmail.com> References: <20081201080917.GA1330@gothic.blackend.org> <4933EE8D.4020001@gmail.com> Message-ID: <20081201150354.GA32597@abigail.blackend.org> On Mon, Dec 01, 2008 at 04:02:53PM +0200, Manolis Kiagias wrote: > This is actually a nice idea - in fact it would be great for the Greek > documentation set, which is constantly changing as more translations are > added. > I just tried the el package and it works great. I could even include > this in some custom package cd sets I am giving out to people. Having > local docs is very important for people without always-on Internet (and > I know quite a few) > I think we don't (well I should check it) provide monthly updated PDF version, this is a part of my objective. > Since as you said you have a way of automating this, my only other > question would be how often will these be updated. Are you planning, > say, for monthly releases? These are ports, so once they are committed they can be updated. An update by month sounds reasonable, but people can update locally the ports if they need more frequent updates. -- Marc From keramida at FreeBSD.org Mon Dec 1 07:25:25 2008 From: keramida at FreeBSD.org (keramida@FreeBSD.org) Date: Mon Dec 1 07:25:31 2008 Subject: docs/122359: times (3) returns system uptime, not epoch time Message-ID: <200812011525.mB1FPObY056413@freefall.freebsd.org> Synopsis: times (3) returns system uptime, not epoch time State-Changed-From-To: closed->open State-Changed-By: keramida State-Changed-When: Mon Dec 1 15:24:59 UTC 2008 State-Changed-Why: Reopen; this seems to be a manpage bug. Responsible-Changed-From-To: freebsd-doc->keramida Responsible-Changed-By: keramida Responsible-Changed-When: Mon Dec 1 15:24:59 UTC 2008 Responsible-Changed-Why: I'll handle this. http://www.freebsd.org/cgi/query-pr.cgi?pr=122359 From blackend at FreeBSD.org Mon Dec 1 11:43:30 2008 From: blackend at FreeBSD.org (Marc Fonvieille) Date: Mon Dec 1 11:43:36 2008 Subject: [Sort of RFC] Ports and packages for docs In-Reply-To: <4933FC12.1060806@FreeBSD.org> References: <20081201080917.GA1330@gothic.blackend.org> <4933EE8D.4020001@gmail.com> <4933FC12.1060806@FreeBSD.org> Message-ID: <20081201194326.GA1030@gothic.blackend.org> On Mon, Dec 01, 2008 at 04:00:34PM +0100, Gabor PALI wrote: > Manolis Kiagias wrote: > > Marc Fonvieille wrote: > >> [..] I'm working since a while on ports for doc [..] > > [..] > > Since as you said you have a way of automating this, my only other > > question would be how often will these be updated. Are you planning, > > say, for monthly releases? > > Yes, it is a good question indeed. Some other questions in connection > with this: > > - Where are these packages build and stored? > For the moment freefall and my desktop box are the build machines. > - Would they be the part of the Ports Collection? If the answer is yes > (a conditional subquestion): > > - Will they have a separate category? > The objective is having dedicaced ports and we may need a specific category. > - Will they be maintained separately? > > - Who should maintain them? (In my opinion, every localized > documentation package content should be maintained and regulated by the > translators themselves.) > doceng@ (and in part re@) should maintain them, as it's done for docproj related ports, etc. A monthly update is planned, if people need more frequent update they should use csup(1) etc. -- Marc From r.c.ladan at gmail.com Mon Dec 1 11:54:27 2008 From: r.c.ladan at gmail.com (Rene Ladan) Date: Mon Dec 1 11:54:34 2008 Subject: [Fwd: PERFORCE change 153905 for review] Message-ID: <49343F34.1010405@gmail.com> Hi, it seems our parser is a bit sloppy about missing semicolons in entity references, which are compulsary according to http://xml.silmaril.ie/faq.sgml So now I'm curious who is right :) Rene -------- Originele bericht -------- Onderwerp: PERFORCE change 153905 for review Datum: Mon, 1 Dec 2008 19:22:26 GMT Van: Rene Ladan Aan: Perforce Change Reviews [...] ==== //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/kernelconfig/chapter.sgml#5 (text+ko) ==== @@ -231,7 +231,7 @@ page: Alternatively, to load the driver as a module at boot time, place the -following line in &man.loader.conf.5: +following line in &man.loader.conf.5;: if_ath_load="YES" -- http://www.rene-ladan.nl/ GPG fingerprint = E738 5471 D185 7013 0EE0 4FC8 3C1D 6F83 12E1 84F6 (subkeys.pgp.net) From sonic2000gr at gmail.com Mon Dec 1 12:13:39 2008 From: sonic2000gr at gmail.com (Manolis Kiagias) Date: Mon Dec 1 12:13:47 2008 Subject: [Fwd: PERFORCE change 153905 for review] In-Reply-To: <49343F34.1010405@gmail.com> References: <49343F34.1010405@gmail.com> Message-ID: <49344568.3060509@gmail.com> Rene Ladan wrote: > Hi, > > it seems our parser is a bit sloppy about missing semicolons in > entity references, which are compulsary according to > http://xml.silmaril.ie/faq.sgml > > So now I'm curious who is right :) > > Rene > > -------- Originele bericht -------- > Onderwerp: PERFORCE change 153905 for review > Datum: Mon, 1 Dec 2008 19:22:26 GMT > Van: Rene Ladan > Aan: Perforce Change Reviews > > [...] > > ==== > //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/kernelconfig/chapter.sgml#5 > (text+ko) ==== > > @@ -231,7 +231,7 @@ > page: > > Alternatively, to load the driver as a module at > boot time, place the > -following line in &man.loader.conf.5: > +following line in &man.loader.conf.5;: > > if_ath_load="YES" > Hey, this is difficult to spot. Even the parser didn't notice :) Seriously, I find it weird that this still renders properly. I am using vim with syntax coloring, and if I forget a semicolon, the lack of color usually reminds me. But I never expected it would render with a colon (esp. since the colon is then kept as part of text) From sonic2000gr at gmail.com Mon Dec 1 12:24:01 2008 From: sonic2000gr at gmail.com (Manolis Kiagias) Date: Mon Dec 1 12:24:07 2008 Subject: [Sort of RFC] Ports and packages for docs In-Reply-To: <20081201194326.GA1030@gothic.blackend.org> References: <20081201080917.GA1330@gothic.blackend.org> <4933EE8D.4020001@gmail.com> <4933FC12.1060806@FreeBSD.org> <20081201194326.GA1030@gothic.blackend.org> Message-ID: <493447DA.1000203@gmail.com> Marc Fonvieille wrote: > >> - Will they be maintained separately? >> >> - Who should maintain them? (In my opinion, every localized >> documentation package content should be maintained and regulated by the >> translators themselves.) >> >> > > doceng@ (and in part re@) should maintain them, as it's done for docproj > related ports, etc. > A monthly update is planned, if people need more frequent update they > should use csup(1) etc. > > In fact, there wouldn't be much for a doc committer to maintain in such a port. You would just perform your usual work on patches, translations etc. and the port would just pick them up from CVS, build and package them. Monthly update also seems very reasonable to me. On average, I translate a chapter per month :) From r.c.ladan at gmail.com Mon Dec 1 12:36:45 2008 From: r.c.ladan at gmail.com (Rene Ladan) Date: Mon Dec 1 12:36:57 2008 Subject: [Fwd: PERFORCE change 153905 for review] In-Reply-To: <49344568.3060509@gmail.com> References: <49343F34.1010405@gmail.com> <49344568.3060509@gmail.com> Message-ID: <49344AD7.5020404@gmail.com> Manolis Kiagias schreef: > Rene Ladan wrote: >> Hi, >> >> it seems our parser is a bit sloppy about missing semicolons in >> entity references, which are compulsary according to >> http://xml.silmaril.ie/faq.sgml >> >> So now I'm curious who is right :) >> >> Rene >> >> -------- Originele bericht -------- >> Onderwerp: PERFORCE change 153905 for review >> Datum: Mon, 1 Dec 2008 19:22:26 GMT >> Van: Rene Ladan >> Aan: Perforce Change Reviews >> >> [...] >> >> ==== >> //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/kernelconfig/chapter.sgml#5 >> (text+ko) ==== >> >> @@ -231,7 +231,7 @@ >> page: >> >> Alternatively, to load the driver as a module at >> boot time, place the >> -following line in &man.loader.conf.5: >> +following line in &man.loader.conf.5;: >> >> if_ath_load="YES" >> > > Hey, this is difficult to spot. Even the parser didn't notice :) > Seriously, I find it weird that this still renders properly. > I am using vim with syntax coloring, and if I forget a semicolon, the > lack of color usually reminds me. But I never expected it would render > with a colon (esp. since the colon is then kept as part of text) > My vim (7.2.29 with SGML highlighting) caught it ;). Maybe the parser is forgiving, like HTML parsers. Regards, Rene -- http://www.rene-ladan.nl/ GPG fingerprint = E738 5471 D185 7013 0EE0 4FC8 3C1D 6F83 12E1 84F6 (subkeys.pgp.net) From gamato at users.sf.net Mon Dec 1 14:19:58 2008 From: gamato at users.sf.net (martinko) Date: Mon Dec 1 14:20:04 2008 Subject: RFR: A "Boot Time Splash Screens" Section to the Handbook In-Reply-To: <493155ED.8020004@FreeBSD.org> References: <493155ED.8020004@FreeBSD.org> Message-ID: <493462FF.3030806@users.sf.net> Gabor PALI wrote: > Hello there, > > A few weeks ago Joseph J. Barbish has contributed a section on boot time > splash screens for the FreeBSD Handbook [1], and after a short > discussion it was requested for comments whether to be really included > it or not [2]. It received a very positive feedback on the topic, so I > created the SGML version of it, that you can study in form of a patch > [3] and a compiled HTML page [4]. > > Please, review, comment and send me your ideas on how to make it better > (and fix it up). Obviously, because I am not a native speaker of > English, it may contain mistakes (I am sure), so review of native > speakers are the most welcome, however review of avid users of the > presented boot time splash screen feature are also important for this patch. > > Thank you for the replies in advance. > > Cheers, > :g > > > PS: For your information, after its commit, I plan to rewrite the > corresponding FAQ entry about splash screens to reference this section > of the Handbook. > > [1] http://lists.freebsd.org/pipermail/freebsd-doc/2008-November/014989.html > [2] http://lists.freebsd.org/pipermail/freebsd-doc/2008-November/015007.html > [3] > http://people.freebsd.org/~pgj/patches/2008/11/29/splash.screen.section.patch.diff > [4] > http://people.freebsd.org/~pgj/patches/2008/11/29/html/boot-blocks.html#BOOT-SPLASH > Hallo Gabor, As I have already written twice, the last time on 20/11/2008 22:22 -- IIRC even with VESA there's a limit of 1024x768 for boot splash images. You may want to mention sysutils/bsd-splash-changer port with which you can have splash image chosen from your collection randomly at each boot. -- Especially the first one -- have you actually checked the claim that you can use any size of splash screen image with VESA ? I checked it, although back in 5.3 era, and I could use max.resolution of 1024x768. Cheers, Martin From gamato at users.sf.net Mon Dec 1 14:25:05 2008 From: gamato at users.sf.net (martinko) Date: Mon Dec 1 14:25:12 2008 Subject: [Sort of RFC] Ports and packages for docs In-Reply-To: <1228141525.91796.56.camel@pav.hide.vol.cz> References: <20081201080917.GA1330@gothic.blackend.org> <1228120711.91796.16.camel@pav.hide.vol.cz> <4933F113.4010100@FreeBSD.org> <1228141525.91796.56.camel@pav.hide.vol.cz> Message-ID: Pav Lucistnik wrote: > Gabor PALI p??e v po 01. 12. 2008 v 15:13 +0100: >> Pav Lucistnik wrote: >>> http://www.oook.cz/bsd/docsnap.html >>> >>> I admit it's kind of hidden. >> Why have not you documented it? :) I would be happy see a short >> description of this method in the Handbook, for example, in Chapter >> "Updating FreeBSD", right next to portsnap. > > Sounds good. Can you come up with a patch? > Well, the thing is that it is not officially supported. Wouldn't it be better to move it to FreeBSD's own infrastructure ? Anyway, I've been using it for long and thanks you all for it. :) M. From trhodes at FreeBSD.org Mon Dec 1 14:44:11 2008 From: trhodes at FreeBSD.org (Tom Rhodes) Date: Mon Dec 1 14:44:17 2008 Subject: [Fwd: PERFORCE change 153905 for review] In-Reply-To: <49344AD7.5020404@gmail.com> References: <49343F34.1010405@gmail.com> <49344568.3060509@gmail.com> <49344AD7.5020404@gmail.com> Message-ID: <20081201174405.09768d58.trhodes@FreeBSD.org> On Mon, 01 Dec 2008 21:36:39 +0100 Rene Ladan wrote: > Manolis Kiagias schreef: > > Rene Ladan wrote: > >> Hi, > >> > >> it seems our parser is a bit sloppy about missing semicolons in > >> entity references, which are compulsary according to > >> http://xml.silmaril.ie/faq.sgml > >> > >> So now I'm curious who is right :) > >> > >> Rene > >> > >> -------- Originele bericht -------- > >> Onderwerp: PERFORCE change 153905 for review > >> Datum: Mon, 1 Dec 2008 19:22:26 GMT > >> Van: Rene Ladan > >> Aan: Perforce Change Reviews > >> > >> [...] > >> > >> ==== > >> //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/kernelconfig/chapter.sgml#5 > >> (text+ko) ==== > >> > >> @@ -231,7 +231,7 @@ > >> page: > >> > >> Alternatively, to load the driver as a module at > >> boot time, place the > >> -following line in &man.loader.conf.5: > >> +following line in &man.loader.conf.5;: > >> > >> if_ath_load="YES" > >> > > > > Hey, this is difficult to spot. Even the parser didn't notice :) > > Seriously, I find it weird that this still renders properly. > > I am using vim with syntax coloring, and if I forget a semicolon, the > > lack of color usually reminds me. But I never expected it would render > > with a colon (esp. since the colon is then kept as part of text) > > > My vim (7.2.29 with SGML highlighting) caught it ;). Maybe the parser > is forgiving, like HTML parsers. My editor would never catch it, but I catch stuff like that when I do the secondary read/scroll through my work. -- Tom Rhodes From mail at ozzmosis.com Tue Dec 2 08:01:08 2008 From: mail at ozzmosis.com (andrew clarke) Date: Tue Dec 2 08:01:14 2008 Subject: [Sort of RFC] Ports and packages for docs In-Reply-To: <20081201080917.GA1330@gothic.blackend.org> References: <20081201080917.GA1330@gothic.blackend.org> Message-ID: <20081202153424.GA28433@ozzmosis.com> On Mon 2008-12-01 09:09:17 UTC+0100, Marc Fonvieille (marc@blackend.org) wrote: > Currently, it's difficult for the average user to update his docs. > Most of time, the docs are installed during OS install time and are > never updated. This is timely as just recently I upgraded from FreeBSD 6.3-REL to 6.4-REL using freebsd-update. After the upgrade I ran "freebsd-update IDS" and discovered I still had the 6.3 docs installed. >From what I can tell, several months ago I must have deleted all the non-English docs to free up disk space, but this seems to have meant that freebsd-update didn't detect that I still had the English docs installed, so didn't bother to upgrade them. Having a package for the docs makes a lot of sense. And there is no risk in having them outside the FreeBSD base. The system should still come up after a reboot even after "pkg_delete -a". > So just: > > pkg_add -r http://people.freebsd.org/~blackend/pkgs/en-freebsd-doc-20081130.tbz > > and tell me if you like it :) Yes, thanks. :) From pgj at FreeBSD.org Tue Dec 2 12:16:22 2008 From: pgj at FreeBSD.org (Gabor PALI) Date: Tue Dec 2 12:16:29 2008 Subject: RFR: A "Boot Time Splash Screens" Section to the Handbook In-Reply-To: <20081201091730.0ef555fa.trhodes@FreeBSD.org> References: <493155ED.8020004@FreeBSD.org> <49316309.1050407@gmail.com> <49330A66.8040801@FreeBSD.org> <20081201091730.0ef555fa.trhodes@FreeBSD.org> Message-ID: <49359784.504@FreeBSD.org> Hello, Tom Rhodes wrote: > Gabor PALI wrote: >> Note for native speakers: please, review! > > You asked. :P Thank you very-very much. I accepted and merged all of your suggestions, so I only answer the parts where I have comments. [..] > + at the virtual console login prompt at boot time, but go > + directly to the X11 desktop display manager's graphical login > + screen. Popular choices are XDM, > + the display manager of &xorg;, gdm > + for GNOME, and > + kdm for > + KDE, but any other display manager > + found in the Ports Collection could be used. These display > > Not sure about this sentence either. :( [..] > + At boot time with the splash screen > + enabled, a few boot loader messages still could be seen leading > + up to and including the boot options menu, and a timed wait > + count down prompt before the splash screen is > + displayed. > > This sentence is a bit much. Okay, I tried to rephrase both of them, I hope you will like it. > + > + Sample splash screen files can be downloaded from the > + gallery at + url="http://www.baldwin.cx/splash/">. > + martinko wrote: > IIRC even with VESA there's a limit of 1024x768 for boot splash images. > > You may want to mention sysutils/bsd-splash-changer port with which you > can have splash image chosen from your collection randomly at each boot. Sorry that I missed it, but this time I added a sentence about this, too. I tested the maximum resolution, and splash screens are supported only up to 1024x768, indeed. I changed the limits to reflect this. > + There are another two possible interesting > + loader.conf options. > > Not sure about this one. Rephrased. > Hope that helps. Of course! Thank you again. Here is the next iteration: (patch version): http://people.freebsd.org/~pgj/patches/2008/12/02/splash.screen.section.patch.diff (HTML version): http://people.freebsd.org/~pgj/patches/2008/12/02/html/boot-blocks.html#BOOT-SPLASH Regards, :g From sonic2000gr at gmail.com Tue Dec 2 12:46:32 2008 From: sonic2000gr at gmail.com (Manolis Kiagias) Date: Tue Dec 2 12:46:39 2008 Subject: RFR: A "Boot Time Splash Screens" Section to the Handbook In-Reply-To: <49359784.504@FreeBSD.org> References: <493155ED.8020004@FreeBSD.org> <49316309.1050407@gmail.com> <49330A66.8040801@FreeBSD.org> <20081201091730.0ef555fa.trhodes@FreeBSD.org> <49359784.504@FreeBSD.org> Message-ID: <49359EA1.3080600@gmail.com> Gabor PALI wrote: > >> Hope that helps. >> > > Of course! Thank you again. > > > Here is the next iteration: > > (patch version): > http://people.freebsd.org/~pgj/patches/2008/12/02/splash.screen.section.patch.diff > > (HTML version): > http://people.freebsd.org/~pgj/patches/2008/12/02/html/boot-blocks.html#BOOT-SPLASH > > > Regards, > :g > > I like the improvements too :) If I were to make a few changes (at the edge of these being doc-bikesheds): - Maybe find another way to describe the console login rather than "legacy virtual console login prompt". Although this may be very accurate I think it can be shortened sowewhat and still carry the same meaning. Esp. since it is mentioned a few times. - The word intensity is mentioned three times in a row "cycle through steps of changing intensity of the image, from bright intensity to a very dark intensity and over again." => I would probably change this to "cycle through steps of changing intensity of the image, from bright to very dark and over again." This is minor stuff of course, and as I said it might just be my own color. (off to find a nice boot screen for my Aspire one :) ) manolis@ From pgj at FreeBSD.org Wed Dec 3 11:43:42 2008 From: pgj at FreeBSD.org (Gabor PALI) Date: Wed Dec 3 11:43:49 2008 Subject: RFR: A "Boot Time Splash Screens" Section to the Handbook In-Reply-To: <49359EA1.3080600@gmail.com> References: <493155ED.8020004@FreeBSD.org> <49316309.1050407@gmail.com> <49330A66.8040801@FreeBSD.org> <20081201091730.0ef555fa.trhodes@FreeBSD.org> <49359784.504@FreeBSD.org> <49359EA1.3080600@gmail.com> Message-ID: <4936E15E.8000804@FreeBSD.org> Manolis Kiagias wrote: > I like the improvements too :) > If I were to make a few changes (at the edge of these being doc-bikesheds): Absolutely not, it IS suggested by the FDP Primer [1]: ``Avoid redundant phrases Try not to use redundant phrases. In particular, "the command", "the file", and "man command" are probably redundant.'' Hopefully, I will reach this section of the FDP Primer in the Hungarian translation soon :) Thanks for the comment! I fixed the parts in question, so you can proof-check the results here: (in HTML:) http://people.freebsd.org/~pgj/patches/2008/12/03/html/boot-blocks.html#BOOT-SPLASH (in unified diff format:) http://people.freebsd.org/~pgj/patches/2008/12/03/splash.screen.section.patch.diff Regards, :g [1] http://www.freebsd.org/doc/en/books/fdp-primer/writing-style.html From gavin at FreeBSD.org Wed Dec 3 12:10:04 2008 From: gavin at FreeBSD.org (Gavin Atkinson) Date: Wed Dec 3 12:10:15 2008 Subject: docs/129398: various tweaks to ddb-related man pages Message-ID: <200812032008.mB3K8glp003278@freefall.freebsd.org> >Number: 129398 >Category: docs >Synopsis: various tweaks to ddb-related man pages >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-doc >State: open >Quarter: >Keywords: >Date-Required: >Class: doc-bug >Submitter-Id: current-users >Arrival-Date: Wed Dec 03 20:10:03 UTC 2008 >Closed-Date: >Last-Modified: >Originator: Gavin Atkinson >Release: FreeBSD 7.1-PRERELEASE i386 >Organization: >Environment: System: FreeBSD freefall.freebsd.org 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #35: Sun Oct 12 12:45:36 UTC 2008 simon@freefall.freebsd.org:/usr/src/sys/i386/compile/FREEFALL i386 >Description: Tweaks to ddb(8), savecore(8) and textdump(4): ddb(8): Remove .Ic from text which is not an interactive command, and add an .El (removes warnings during render) savecore(8): Fix an xref textdump(8): add a useful bit of info and an xref I haven't bumped .Dd on ddb(8) as this shouldn't affect the rendered man page. >How-To-Repeat: N/A >Fix: --- 20081203-manpages-ddb.diff begins here --- Index: src/sbin/ddb/ddb.8 =================================================================== RCS file: /home/ncvs/src/sbin/ddb/ddb.8,v retrieving revision 1.6 diff -u -r1.6 ddb.8 --- src/sbin/ddb/ddb.8 3 Aug 2008 14:27:06 -0000 1.6 +++ src/sbin/ddb/ddb.8 3 Dec 2008 20:05:24 -0000 @@ -87,7 +87,7 @@ The following debugger commands are available from the command line: .Bl -tag -width indent .It Xo -.Ic Cm capture +.Cm capture .Op Fl M Ar core .Op Fl N Ar system .Cm print @@ -96,7 +96,7 @@ .Xr ddb 4 output capture buffer. .It Xo -.Ic Cm capture +.Cm capture .Op Fl M Ar core .Op Fl N Ar system .Cm status @@ -104,6 +104,7 @@ Print the current status of the .Xr ddb 4 output capture buffer. +.El .Sh SCRIPTING The .Nm Index: src/sbin/savecore/savecore.8 =================================================================== RCS file: /home/ncvs/src/sbin/savecore/savecore.8,v retrieving revision 1.26 diff -u -r1.26 savecore.8 --- src/sbin/savecore/savecore.8 26 Dec 2007 11:42:10 -0000 1.26 +++ src/sbin/savecore/savecore.8 3 Dec 2008 19:17:13 -0000 @@ -28,7 +28,7 @@ .\" From: @(#)savecore.8 8.1 (Berkeley) 6/5/93 .\" $FreeBSD: src/sbin/savecore/savecore.8,v 1.26 2007/12/26 11:42:10 rwatson Exp $ .\" -.Dd February 24, 2005 +.Dd December 3, 2008 .Dt SAVECORE 8 .Os .Sh NAME @@ -144,7 +144,7 @@ .Xr gzip 1 , .Xr getbootfile 3 , .Xr textdump 4 , -.Xr tar 4 , +.Xr tar 5 , .Xr dumpon 8 , .Xr syslogd 8 .Sh HISTORY Index: src/share/man/man4/textdump.4 =================================================================== RCS file: /home/ncvs/src/share/man/man4/textdump.4,v retrieving revision 1.5 diff -u -r1.5 textdump.4 --- src/share/man/man4/textdump.4 3 Aug 2008 14:14:43 -0000 1.5 +++ src/share/man/man4/textdump.4 3 Dec 2008 19:17:23 -0000 @@ -27,7 +27,7 @@ .\" .\" $FreeBSD: src/share/man/man4/textdump.4,v 1.5 2008/08/03 14:14:43 rwatson Exp $ .\" -.Dd December 26, 2007 +.Dd December 3, 2008 .Dt textdump 4 .Os .Sh NAME @@ -148,10 +148,15 @@ .Bd -literal -offset indent script kdb.enter.witness=show locks .Ed +.Pp +These scripts may also be configured from userspace using the +.Xr ddb 8 +command. .Sh SEE ALSO .Xr bsdtar 1 , .Xr ddb 4 , .Xr tar 5 , +.Xr ddb 8 , .Xr dumpon 8 , .Xr savecore 8 , .Xr sysctl 8 --- 20081203-manpages-ddb.diff ends here --- >Release-Note: >Audit-Trail: >Unformatted: From gavin at FreeBSD.org Wed Dec 3 12:30:01 2008 From: gavin at FreeBSD.org (Gavin Atkinson) Date: Wed Dec 3 12:30:07 2008 Subject: docs/129400: [patch] Remove comments that have snook into three man pages Message-ID: <200812032024.mB3KOMqK018598@freefall.freebsd.org> >Number: 129400 >Category: docs >Synopsis: [patch] Remove comments that have snook into three man pages >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-doc >State: open >Quarter: >Keywords: >Date-Required: >Class: doc-bug >Submitter-Id: current-users >Arrival-Date: Wed Dec 03 20:30:00 UTC 2008 >Closed-Date: >Last-Modified: >Originator: Gavin Atkinson >Release: FreeBSD 7.1-PRERELEASE i386 >Organization: >Environment: System: FreeBSD freefall.freebsd.org 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #35: Sun Oct 12 12:45:36 UTC 2008 simon@freefall.freebsd.org:/usr/src/sys/i386/compile/FREEFALL i386 >Description: Only three man pages include a comment about bumping .Dd for inon-trivial changes, this is left over from (presumaby) when the man page was created from a clone of the example man pages which also include this comment. Given only three real manpages include it, it may as well be removed - the chance that one of these three man pages is the page somebody edits without understanding .Dd is pretty slim, and it also helps to bring these into the style of all other man pages. Don't bump .Dd as it's a trivial change :) >How-To-Repeat: N/A >Fix: --- 20081201-manpage-date-comment.diff begins here --- Index: src/lib/libc/db/man/dbm.3 =================================================================== RCS file: /home/ncvs/src/lib/libc/db/man/dbm.3,v retrieving revision 1.9 diff -u -r1.9 dbm.3 --- src/lib/libc/db/man/dbm.3 16 Apr 2006 16:33:26 -0000 1.9 +++ src/lib/libc/db/man/dbm.3 1 Dec 2008 22:40:12 -0000 @@ -15,8 +15,6 @@ .\" .\" $FreeBSD: src/lib/libc/db/man/dbm.3,v 1.9 2006/04/16 16:33:26 maxim Exp $ .\" -.\" Note: The date here should be updated whenever a non-trivial -.\" change is made to the manual page. .Dd April 16, 2006 .Dt DBM 3 .Os Index: src/sys/boot/i386/pxeldr/pxeboot.8 =================================================================== RCS file: /home/ncvs/src/sys/boot/i386/pxeldr/pxeboot.8,v retrieving revision 1.8 diff -u -r1.8 pxeboot.8 --- src/sys/boot/i386/pxeldr/pxeboot.8 7 Oct 2006 10:39:34 -0000 1.8 +++ src/sys/boot/i386/pxeldr/pxeboot.8 1 Dec 2008 22:40:19 -0000 @@ -24,8 +24,6 @@ .\" .\" $FreeBSD: src/sys/boot/i386/pxeldr/pxeboot.8,v 1.8 2006/10/07 10:39:34 pav Exp $ .\" -.\" Note: The date here should be updated whenever a non-trivial -.\" change is made to the manual page. .Dd May 1, 2000 .Dt PXEBOOT 8 .Os Index: src/usr.sbin/gssd/gssd.8 =================================================================== RCS file: /home/ncvs/src/usr.sbin/gssd/gssd.8,v retrieving revision 1.2 diff -u -r1.2 gssd.8 --- src/usr.sbin/gssd/gssd.8 5 Nov 2008 09:42:05 -0000 1.2 +++ src/usr.sbin/gssd/gssd.8 1 Dec 2008 22:40:26 -0000 @@ -25,8 +25,6 @@ .\" .\" $FreeBSD: src/usr.sbin/gssd/gssd.8,v 1.2 2008/11/05 09:42:05 keramida Exp $ .\" -.\" Note: The date here should be updated whenever a non-trivial -.\" change is made to the manual page. .Dd November 5, 2008 .Dt GSSD 8 .Os --- 20081201-manpage-date-comment.diff ends here --- >Release-Note: >Audit-Trail: >Unformatted: From sonic2000gr at gmail.com Wed Dec 3 13:26:02 2008 From: sonic2000gr at gmail.com (Manolis Kiagias) Date: Wed Dec 3 13:26:08 2008 Subject: RFR: A "Boot Time Splash Screens" Section to the Handbook In-Reply-To: <4936E15E.8000804@FreeBSD.org> References: <493155ED.8020004@FreeBSD.org> <49316309.1050407@gmail.com> <49330A66.8040801@FreeBSD.org> <20081201091730.0ef555fa.trhodes@FreeBSD.org> <49359784.504@FreeBSD.org> <49359EA1.3080600@gmail.com> <4936E15E.8000804@FreeBSD.org> Message-ID: <4936F963.7040201@gmail.com> Gabor PALI wrote: > Manolis Kiagias wrote: > >> I like the improvements too :) >> If I were to make a few changes (at the edge of these being doc-bikesheds): >> > > Absolutely not, it IS suggested by the FDP Primer [1]: > > ``Avoid redundant phrases > > Try not to use redundant phrases. In particular, "the command", "the > file", and "man command" are probably redundant.'' > > > Hopefully, I will reach this section of the FDP Primer in the Hungarian > translation soon :) Thanks for the comment! > > > I fixed the parts in question, so you can proof-check the results here: > > (in HTML:) > http://people.freebsd.org/~pgj/patches/2008/12/03/html/boot-blocks.html#BOOT-SPLASH > > (in unified diff format:) > http://people.freebsd.org/~pgj/patches/2008/12/03/splash.screen.section.patch.diff > > > Regards, > :g > > [1] http://www.freebsd.org/doc/en/books/fdp-primer/writing-style.html > > Looks fine to me! I also tested the procedure on my Aspire One. Got the "may the source be with you" splash up in no time at all ;) From trhodes at FreeBSD.org Wed Dec 3 16:03:10 2008 From: trhodes at FreeBSD.org (Tom Rhodes) Date: Wed Dec 3 16:03:22 2008 Subject: RFR: A "Boot Time Splash Screens" Section to the Handbook In-Reply-To: <4936F963.7040201@gmail.com> References: <493155ED.8020004@FreeBSD.org> <49316309.1050407@gmail.com> <49330A66.8040801@FreeBSD.org> <20081201091730.0ef555fa.trhodes@FreeBSD.org> <49359784.504@FreeBSD.org> <49359EA1.3080600@gmail.com> <4936E15E.8000804@FreeBSD.org> <4936F963.7040201@gmail.com> Message-ID: <20081203190300.550255b5.trhodes@FreeBSD.org> On Wed, 03 Dec 2008 23:25:55 +0200 Manolis Kiagias wrote: > Gabor PALI wrote: > > Manolis Kiagias wrote: > > > >> I like the improvements too :) > >> If I were to make a few changes (at the edge of these being doc-bikesheds): > >> > > > > Absolutely not, it IS suggested by the FDP Primer [1]: > > > > ``Avoid redundant phrases > > > > Try not to use redundant phrases. In particular, "the command", "the > > file", and "man command" are probably redundant.'' > > > > > > Hopefully, I will reach this section of the FDP Primer in the Hungarian > > translation soon :) Thanks for the comment! > > > > > > I fixed the parts in question, so you can proof-check the results here: > > > > (in HTML:) > > http://people.freebsd.org/~pgj/patches/2008/12/03/html/boot-blocks.html#BOOT-SPLASH > > > > (in unified diff format:) > > http://people.freebsd.org/~pgj/patches/2008/12/03/splash.screen.section.patch.diff > > > > > > Regards, > > :g > > > > [1] http://www.freebsd.org/doc/en/books/fdp-primer/writing-style.html > > > > > Looks fine to me! > I also tested the procedure on my Aspire One. Got the "may the source be > with you" splash up in no time at all ;) > Yes, this looks pretty good over here too. Thanks! -- Tom Rhodes From richard at r3portfolio.com Wed Dec 3 19:55:46 2008 From: richard at r3portfolio.com (Richard Raseley) Date: Wed Dec 3 19:55:52 2008 Subject: Important Omission in FTP Configuration Documentation Message-ID: <000901c955c0$49caf790$dd60e6b0$@com> Documentation Project Owner, Recently I started my first foray into the world of FreeBSD, thus far I have been pleasantly surprised, but I have also found a document on your site that has an important omission. In this document: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/network-ftp.html In section 30.8.2 "Configuration" you list the steps that are required to get ftpd up and running, however you fail to mention that you also have to add "ftpd_enable="YES" to your "/etc/rc.conf" file and reboot the server. Ftpd will not work until you complete this step and it took me hours (being a n00b) of additional research to figure this out. It would be very helpful if you included this in your documentation so that others like myself can find it easily. Thank you for your continued work, so far (coming from a Windows world) I am very impressed. Best Regards, Richard From sonic2000gr at gmail.com Thu Dec 4 07:28:17 2008 From: sonic2000gr at gmail.com (Manolis Kiagias) Date: Thu Dec 4 07:28:22 2008 Subject: Important Omission in FTP Configuration Documentation In-Reply-To: <000901c955c0$49caf790$dd60e6b0$@com> References: <000901c955c0$49caf790$dd60e6b0$@com> Message-ID: <4937F70B.6090901@gmail.com> Richard Raseley wrote: > Documentation Project Owner, > > > > Recently I started my first foray into the world of FreeBSD, thus far I have > been pleasantly surprised, but I have also found a document on your site > that has an important omission. > > > > In this document: > > > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/network-ftp.html > > > > In section 30.8.2 "Configuration" you list the steps that are required to > get ftpd up and running, however you fail to mention that you also have to > add "ftpd_enable="YES" to your "/etc/rc.conf" file and reboot the server. > > > > Ftpd will not work until you complete this step and it took me hours (being > a n00b) of additional research to figure this out. It would be very helpful > if you included this in your documentation so that others like myself can > find it easily. > > > > Thank you for your continued work, so far (coming from a Windows world) I am > very impressed. > > > > Best Regards, > > > > Richard > > First of all, thanks for helping us improve our documentation! The problem with your setup is that you probably missed enabling the inetd server. This is not mentioned explicitly in the section you were reading, but it is mentioned in section 30.2.2. If you add inetd_enable="YES" to your /etc/rc.conf and reboot, and having followed the rest of the instructions, your ftp server will be started (when needed) by inetd. To make things clear, I have added a reference to section 30.2.2 in section 30.8.2 By adding ftpd_enable="YES", the ftp server is started in stand-alone mode. The inetd setting is not required in this case. I have also added a few lines on this alternate way of starting ftpd. These changes will appear on the website in the next 24 hours. Thanks for submitting this! manolis@ From froc at list.ru Thu Dec 4 10:13:57 2008 From: froc at list.ru (Alex Robinovici) Date: Thu Dec 4 10:32:37 2008 Subject: (no subject) Message-ID: Good evening! Where it is possible to download the documentation on FreeBSD in archives? The reference <> on a site www.freebsd.org Does not work. ------------------------------------------------------- ?????? ?????! ??? ????? ??????? ???????????? ?? FreeBSD ? ???????? ?????? <> ?? ????? www.freebsd.org ?? ????????. From sonic2000gr at gmail.com Thu Dec 4 10:44:02 2008 From: sonic2000gr at gmail.com (Manolis Kiagias) Date: Thu Dec 4 10:44:09 2008 Subject: Documentation Download (was: Re: (no subject)) In-Reply-To: References: Message-ID: <493824EA.4050509@gmail.com> Alex Robinovici wrote: > Good evening! > > Where it is possible to download the documentation on FreeBSD in archives? > > The reference <> on a site > > www.freebsd.org Does not work. > > ------------------------------------------------------- > > ?????? ?????! > > ??? ????? ??????? ???????????? ?? FreeBSD ? ???????? > > ?????? <> ?? ????? > > www.freebsd.org ?? ????????. > > > > It works fine here. For example, try the following direct link to the English handbook in zipped pdf format: ftp://ftp.freebsd.org/pub/FreeBSD/doc/en_US.ISO8859-1/books/handbook/book.pdf.zip Failing that, you could also try a mirror site, i.e: ftp://ftp.uk.freebsd.org/pub/FreeBSD/doc/en_US.ISO8859-1/books/handbook/book.pdf.zip In fact, here is a list of mirror sites you can try: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/mirrors-ftp.html From gabor at FreeBSD.org Thu Dec 4 16:07:08 2008 From: gabor at FreeBSD.org (=?ISO-8859-1?Q?G=E1bor_K=F6vesd=E1n?=) Date: Thu Dec 4 16:07:40 2008 Subject: [Sort of RFC] Ports and packages for docs In-Reply-To: <20081201080917.GA1330@gothic.blackend.org> References: <20081201080917.GA1330@gothic.blackend.org> Message-ID: <493870A9.6050604@FreeBSD.org> Marc Fonvieille escribi?: > Hello, > > Currently, it's difficult for the average user to update his docs. > Most of time, the docs are installed during OS install time and are > never updated. > Another problem is the fact the doc build requires a lot of diskspace > and a lot of time on slow architectures/CPUs/etc which is a problem > during release process. > > To sum up, we're lacking of a simple way to install and update docs > without any compilation operation. Hello Marc, I think it is a very good idea. It can happen that someone can't go online to check the documentation so it would be really useful to have a method to install the docs easily. Thanks for working on this! > > These packages provide html-split version (of course other formats are > possible, I just want to limit the bandwidth) of the 20081130 docset. > Another thing to note, the packages install docs in > /usr/local/share/doc/freebsd > Maybe you could also add an option (like OVERWRITE_BASE or something like that) to install them to the usual /usr/share/doc location. In this way, we could avoid duplication between the base and the ports version and keep using the path we got used to. It is not very smart to install things outside from /usr/local, but I think it can be useful in some cases and this particular is such one. A couple of other ports also do this (like BIND, OpenSSH, etc.). Regards, -- Gabor Kovesdan EMAIL: gabor@FreeBSD.org WWW: http://www.kovesdan.org From hrs at FreeBSD.org Thu Dec 4 17:13:46 2008 From: hrs at FreeBSD.org (Hiroki Sato) Date: Thu Dec 4 17:13:52 2008 Subject: [Sort of RFC] Ports and packages for docs In-Reply-To: <20081201103533.GC1330@gothic.blackend.org> References: <20081201080917.GA1330@gothic.blackend.org> <4933B2E8.10507@FreeBSD.org> <20081201103533.GC1330@gothic.blackend.org> Message-ID: <20081205.095843.138450898.hrs@allbsd.org> Marc Fonvieille wrote in <20081201103533.GC1330@gothic.blackend.org>: bl> On Mon, Dec 01, 2008 at 10:48:24AM +0100, Gabor PALI wrote: bl> > Marc Fonvieille wrote: bl> > > I'm working since a while on ports for doc [..] and tell me if you bl> > > like it :) bl> > bl> > I think generally it is a good idea to reanimate the concept bl> > documentation packages, however last time I asked about them (May 2008, bl> > while fixing the FAQ), I got an interesting answer [1] from Hiroki Sato: bl> > bl> > "The doc packages are no longer available because the past discussion bl> > reached a consensus that generating them is a bit tricky and most of bl> > people do not need such packages because the latest documentation is bl> > always available on the web." bl> > bl> [...] bl> bl> But you cut the last sentence :) bl> bl> Yes, it was difficult to maintain them and we had no real solution to bl> continue to provide them. It's true that the doc is available via the bl> web, but as I said the aim is not only provide packages to the user but bl> also modernize the doc installation and build for the releases. bl> Now, I have a working solution that can be updated, etc. without bl> headaches, so we may have to rethink about the current situation. Ah, I certainly wrote the reply to Gabor in May. It is true that the old packages are deprecated for the reason as I explained. However, I do not think generating doc packages itself is a bad thing. The difficulty of the old packages is that they were not from the Ports Collection. I mean they did not have any corresponding ports, so upgrading cannot be done in a straightforward way. Using ports for the doc packages can eliminate the tricky part of the old ones and make the release distribution set simple. I believe it is the right direction. -- | Hiroki SATO -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-doc/attachments/20081205/fd9866ec/attachment.pgp From hrs at FreeBSD.org Thu Dec 4 17:14:04 2008 From: hrs at FreeBSD.org (Hiroki Sato) Date: Thu Dec 4 17:14:09 2008 Subject: [Sort of RFC] Ports and packages for docs In-Reply-To: <493870A9.6050604@FreeBSD.org> References: <20081201080917.GA1330@gothic.blackend.org> <493870A9.6050604@FreeBSD.org> Message-ID: <20081205.101257.142333304.hrs@allbsd.org> G?bor K?vesd?n wrote in <493870A9.6050604@FreeBSD.org>: ga> Marc Fonvieille escribi?: ga> > These packages provide html-split version (of course other formats are ga> > possible, I just want to limit the bandwidth) of the 20081130 docset. ga> > Another thing to note, the packages install docs in ga> > /usr/local/share/doc/freebsd ga> > ga> Maybe you could also add an option (like OVERWRITE_BASE or something ga> like that) to install them to the usual /usr/share/doc location. In ga> this way, we could avoid duplication between the base and the ports ga> version and keep using the path we got used to. It is not very smart ga> to install things outside from /usr/local, but I think it can be ga> useful in some cases and this particular is such one. A couple of ga> other ports also do this (like BIND, OpenSSH, etc.). You have a point, but I prefer eliminating our documentation set from /usr/share/doc and make the doc set can be installed from the pre-compiled packages, not tarball which uses /usr/share/doc, like Xorg to avoid such duplication in the future releases. -- | Hiroki SATO -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-doc/attachments/20081205/fe31ec74/attachment.pgp From gabor at FreeBSD.org Thu Dec 4 17:20:59 2008 From: gabor at FreeBSD.org (=?ISO-8859-1?Q?G=E1bor_K=F6vesd=E1n?=) Date: Thu Dec 4 17:21:05 2008 Subject: [Sort of RFC] Ports and packages for docs In-Reply-To: <20081205.101257.142333304.hrs@allbsd.org> References: <20081201080917.GA1330@gothic.blackend.org> <493870A9.6050604@FreeBSD.org> <20081205.101257.142333304.hrs@allbsd.org> Message-ID: <493881F7.9020706@FreeBSD.org> Hiroki Sato escribi?: > G?bor K?vesd?n wrote > in <493870A9.6050604@FreeBSD.org>: > > ga> Marc Fonvieille escribi?: > ga> > These packages provide html-split version (of course other formats are > ga> > possible, I just want to limit the bandwidth) of the 20081130 docset. > ga> > Another thing to note, the packages install docs in > ga> > /usr/local/share/doc/freebsd > ga> > > ga> Maybe you could also add an option (like OVERWRITE_BASE or something > ga> like that) to install them to the usual /usr/share/doc location. In > ga> this way, we could avoid duplication between the base and the ports > ga> version and keep using the path we got used to. It is not very smart > ga> to install things outside from /usr/local, but I think it can be > ga> useful in some cases and this particular is such one. A couple of > ga> other ports also do this (like BIND, OpenSSH, etc.). > > You have a point, but I prefer eliminating our documentation set from > /usr/share/doc and make the doc set can be installed from the > pre-compiled packages, not tarball which uses /usr/share/doc, like > Xorg to avoid such duplication in the future releases. > Yes, that seems even better. I agree with your idea. Although it wouldn't be nice to leave any installed system without documentation if it is not explicitly intended by the user. Maybe doc packages should be installed automatically during the installation just like Perl? Regards, -- Gabor Kovesdan EMAIL: gabor@FreeBSD.org WWW: http://www.kovesdan.org From p0036343 at brookes.ac.uk Thu Dec 4 17:50:02 2008 From: p0036343 at brookes.ac.uk (Stephen Allen) Date: Thu Dec 4 17:50:07 2008 Subject: docs/129428: ntp.conf(5) is incorrect - you can only use IP address on restrict lines Message-ID: <200812050140.mB51erH9049371@www.freebsd.org> >Number: 129428 >Category: docs >Synopsis: ntp.conf(5) is incorrect - you can only use IP address on restrict lines >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-doc >State: open >Quarter: >Keywords: >Date-Required: >Class: doc-bug >Submitter-Id: current-users >Arrival-Date: Fri Dec 05 01:50:00 UTC 2008 >Closed-Date: >Last-Modified: >Originator: Stephen Allen >Release: 7.0 >Organization: Oxford Brookes University >Environment: FreeBSD 7.0-RELEASE-p6 FreeBSD 7.0-RELEASE-p6 #0: Mon Nov 24 10:59:10 UTC 2008 root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 >Description: In the section "Access Control Commands --> restrict", it says: "The address argument expressed in dotted-quad form is the address of a host or network. Alternatively, the address argument can be a valid host DNS name." I have found that the address argument MUST be an ip address only - it doesn't work with a valid host DNS name. This corroborated by the official documentation at: http://support.ntp.org/bin/view/Support/AccessRestrictions#Section_6.5.1.2.1. which says: "You must use an IP address on the restrict line." >How-To-Repeat: In the restrict line, use host DNS name instead of IP address. >Fix: n/a >Release-Note: >Audit-Trail: >Unformatted: From daniel at dabber.tv Thu Dec 4 19:50:06 2008 From: daniel at dabber.tv (Daniel Daboczy - DABBER) Date: Thu Dec 4 19:50:13 2008 Subject: Intro to a cool new webb-tv solution Message-ID: <125429.PXRJNHPR@dabber.tv> Dabber Newsletter Dabber | Newsletter December 2008 Example player | White paper pdf | IQube our new partner Hi, Since our last update, we have prepared a first example of the kind of online video3-dimensional navigatonline video content: This is the golden age of online video. More and more of us are creating itMainstream media giantsInternet users alike are literamotion. Video on the web is becoming a natuenabling us to do a lot of different things easier, better: discovering what's new and rediscovering the things we'vmissed, telling our stories and communicating our brands, realizing our lOver the last few years, a lot of companies offering online video platforWhereas most ofultimate one-platfoaspect of the enterprise thgetting exactly the kind of product andthat you can afford. Dabber is an Internet start-up, offering online video solutions that are inbackground in the contemporary art scene as well as in web production, we combine the latest in technology with an understanding of what makes Daniel Daboczy & Eric Weber, founders White paper (pdf) For more information about our services, please download the Dabber white paper. IQube is our new partner We're proud to present IQube as a new partner. IQube is one of the Nordic rstage growth compa Dabber's development continues at rapid pace We're still in development, but feel free to contact us in the meanwhile, o www.dabber.tv daniel [at] dabber.tv +46 736 26 9985 To unsubscribe, please forward this email to unsubscribe@dabber.tv From blackend at FreeBSD.org Thu Dec 4 22:29:26 2008 From: blackend at FreeBSD.org (Marc Fonvieille) Date: Thu Dec 4 22:29:38 2008 Subject: [Sort of RFC] Ports and packages for docs In-Reply-To: <493881F7.9020706@FreeBSD.org> References: <20081201080917.GA1330@gothic.blackend.org> <493870A9.6050604@FreeBSD.org> <20081205.101257.142333304.hrs@allbsd.org> <493881F7.9020706@FreeBSD.org> Message-ID: <20081205062922.GA77328@abigail.blackend.org> On Fri, Dec 05, 2008 at 02:20:55AM +0100, G?bor K?vesd?n wrote: > Hiroki Sato escribi?: > >G?bor K?vesd?n wrote > > in <493870A9.6050604@FreeBSD.org>: > > > >ga> Marc Fonvieille escribi?: > >ga> > These packages provide html-split version (of course other formats > >are > >ga> > possible, I just want to limit the bandwidth) of the 20081130 docset. > >ga> > Another thing to note, the packages install docs in > >ga> > /usr/local/share/doc/freebsd > >ga> > > >ga> Maybe you could also add an option (like OVERWRITE_BASE or something > >ga> like that) to install them to the usual /usr/share/doc location. In > >ga> this way, we could avoid duplication between the base and the ports > >ga> version and keep using the path we got used to. It is not very smart > >ga> to install things outside from /usr/local, but I think it can be > >ga> useful in some cases and this particular is such one. A couple of > >ga> other ports also do this (like BIND, OpenSSH, etc.). > > > > You have a point, but I prefer eliminating our documentation set from > > /usr/share/doc and make the doc set can be installed from the > > pre-compiled packages, not tarball which uses /usr/share/doc, like > > Xorg to avoid such duplication in the future releases. > > > Yes, that seems even better. I agree with your idea. Although it > wouldn't be nice to leave any installed system without documentation if > it is not explicitly intended by the user. Maybe doc packages should be > installed automatically during the installation just like Perl? > We plan to have a selection menu for the docs with en_US language selected by default and the possibility to add more languages, a bit like it was the case for Xorg. -- Marc From kralph at gmail.com Fri Dec 5 19:20:01 2008 From: kralph at gmail.com (Kenyon Ralph) Date: Fri Dec 5 19:20:08 2008 Subject: docs/129448: loader(8) manpage typo: two init_script listings, the second one should be init_shell Message-ID: <200812060318.mB63IgCa086350@www.freebsd.org> >Number: 129448 >Category: docs >Synopsis: loader(8) manpage typo: two init_script listings, the second one should be init_shell >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-doc >State: open >Quarter: >Keywords: >Date-Required: >Class: doc-bug >Submitter-Id: current-users >Arrival-Date: Sat Dec 06 03:20:01 UTC 2008 >Closed-Date: >Last-Modified: >Originator: Kenyon Ralph >Release: 8-current >Organization: >Environment: >Description: See http://www.freebsd.org/cgi/man.cgi?query=loader&manpath=FreeBSD+8-current In the BUILTIN ENVIRONMENT VARIABLES section, init_script is listed twice. The second one should be init_shell. See also /boot/defaults/loader.conf to verify. >How-To-Repeat: >Fix: Replace second init_script with init_shell. >Release-Note: >Audit-Trail: >Unformatted: From www at FreeBSD.org Fri Dec 5 19:24:25 2008 From: www at FreeBSD.org (World Wide Web Owner) Date: Fri Dec 5 19:24:32 2008 Subject: FreeBSD web build failed on www.freebsd.org Message-ID: <200812060324.mB63OPru088434@www.freebsd.org> ? relnotes7/doc/share/sgml/dev-auto.sgml ===> FAQ ===> advocacy ===> commercial ===> community ===> copyright ===> developers ===> docproj ===> docs ===> donations ===> events ===> events/2002 ===> events/2003 ===> gnome ===> gnome/docs ===> gnome/images ===> handbook ===> internal /usr/bin/perl5 /w/www/build/www/en/internal/homepage.pl > homepage.inc /usr/bin/sed -e 's///' homepage.sgml > homepage.sgml-tmp /usr/bin/env SGML_CATALOG_FILES= /usr/local/bin/sgmlnorm -d -ifreebsd.urls.absolute -c /usr/local/share/sgml/html/catalog -c /usr/local/share/sgml/catalog -c /w/www/build/www/en/share/sgml/catalog -c /w/www/build/www/share/sgml/catalog -D /w/www/build/www/en/internal homepage.sgml-tmp > homepage.html || (/bin/rm -f homepage.sgml-tmp homepage.html && false) /bin/rm -f homepage.sgml-tmp /usr/local/bin/tidy -wrap 90 -m -raw -preserve -f /dev/null -asxml homepage.html *** Error code 1 (ignored) ===> java ===> java/dists ===> java/docs ===> java/links ===> kse ===> marketing ===> multimedia (test -d output || /bin/mkdir output ) && cd output && /bin/ln -fs ../Makefile.output Makefile && ( for f in multimedia.sgml.intro multimedia.sgml.post multimedia.sgml.pre multimedia.html.intro multimedia.html.post multimedia.html.pre multimedia-input.xml; do /bin/ln -fs ../$f $f; done ) && /usr/bin/perl5 -Tw ../multimedia.pl && /bin/rm -f *.html cd output && make all DIRPRFX=multimedia/output/ "/w/www/build/www/en/multimedia/output/../../..//share/mk/web.site.mk", line 349: warning: Missing closing parenthesis for exists() /usr/bin/sed -e 's///' multimedia.sgml > multimedia.sgml-tmp /usr/bin/env SGML_CATALOG_FILES= /usr/local/bin/sgmlnorm -d -ifreebsd.urls.absolute -c /usr/local/share/sgml/html/catalog -c /usr/local/share/sgml/catalog -c /w/www/build/www/en/share/sgml/catalog -c /w/www/build/www/share/sgml/catalog -D /w/www/build/www/en/multimedia/output multimedia.sgml-tmp > multimedia.html || (/bin/rm -f multimedia.sgml-tmp multimedia.html && false) /usr/local/bin/sgmlnorm:multimedia.sgml-tmp:249:70:E: general entity "type" not defined and no default entity /usr/local/bin/sgmlnorm:multimedia.sgml-tmp:938:33:E: general entity "D" not defined and no default entity /usr/local/bin/sgmlnorm:multimedia.sgml-tmp:1164:67:E: general entity "do" not defined and no default entity /usr/local/bin/sgmlnorm:multimedia.sgml-tmp:1164:74:E: general entity "target" not defined and no default entity *** Error code 1 Stop in /w/www/build/www/en/multimedia/output. *** Error code 1 Stop in /w/www/build/www/en/multimedia. *** Error code 1 Stop in /w/www/build/www/en. 15.07 real 11.67 user 1.69 sys From www at FreeBSD.org Fri Dec 5 19:53:30 2008 From: www at FreeBSD.org (World Wide Web Owner) Date: Fri Dec 5 19:53:36 2008 Subject: FreeBSD web build failed on www.freebsd.org Message-ID: <200812060353.mB63rTjt097602@www.freebsd.org> ? relnotes7/doc/share/sgml/dev-auto.sgml ===> FAQ ===> advocacy ===> commercial ===> community ===> copyright ===> developers ===> docproj ===> docs ===> donations ===> events ===> events/2002 ===> events/2003 ===> gnome ===> gnome/docs ===> gnome/images ===> handbook ===> internal /usr/bin/perl5 /w/www/build/www/en/internal/homepage.pl > homepage.inc /usr/bin/sed -e 's///' homepage.sgml > homepage.sgml-tmp /usr/bin/env SGML_CATALOG_FILES= /usr/local/bin/sgmlnorm -d -ifreebsd.urls.absolute -c /usr/local/share/sgml/html/catalog -c /usr/local/share/sgml/catalog -c /w/www/build/www/en/share/sgml/catalog -c /w/www/build/www/share/sgml/catalog -D /w/www/build/www/en/internal homepage.sgml-tmp > homepage.html || (/bin/rm -f homepage.sgml-tmp homepage.html && false) /bin/rm -f homepage.sgml-tmp /usr/local/bin/tidy -wrap 90 -m -raw -preserve -f /dev/null -asxml homepage.html *** Error code 1 (ignored) ===> java ===> java/dists ===> java/docs ===> java/links ===> kse ===> marketing ===> multimedia (test -d output || /bin/mkdir output ) && cd output && /bin/ln -fs ../Makefile.output Makefile && ( for f in multimedia.sgml.intro multimedia.sgml.post multimedia.sgml.pre multimedia.html.intro multimedia.html.post multimedia.html.pre multimedia-input.xml; do /bin/ln -fs ../$f $f; done ) && /usr/bin/perl5 -Tw ../multimedia.pl && /bin/rm -f *.html cd output && make all DIRPRFX=multimedia/output/ "/w/www/build/www/en/multimedia/output/../../..//share/mk/web.site.mk", line 349: warning: Missing closing parenthesis for exists() /usr/bin/sed -e 's///' multimedia.sgml > multimedia.sgml-tmp /usr/bin/env SGML_CATALOG_FILES= /usr/local/bin/sgmlnorm -d -ifreebsd.urls.absolute -c /usr/local/share/sgml/html/catalog -c /usr/local/share/sgml/catalog -c /w/www/build/www/en/share/sgml/catalog -c /w/www/build/www/share/sgml/catalog -D /w/www/build/www/en/multimedia/output multimedia.sgml-tmp > multimedia.html || (/bin/rm -f multimedia.sgml-tmp multimedia.html && false) /usr/local/bin/sgmlnorm:multimedia.sgml-tmp:249:70:E: general entity "type" not defined and no default entity /usr/local/bin/sgmlnorm:multimedia.sgml-tmp:938:33:E: general entity "D" not defined and no default entity /usr/local/bin/sgmlnorm:multimedia.sgml-tmp:1164:67:E: general entity "do" not defined and no default entity /usr/local/bin/sgmlnorm:multimedia.sgml-tmp:1164:74:E: general entity "target" not defined and no default entity *** Error code 1 Stop in /w/www/build/www/en/multimedia/output. *** Error code 1 Stop in /w/www/build/www/en/multimedia. *** Error code 1 Stop in /w/www/build/www/en. 15.54 real 10.92 user 2.39 sys From www at FreeBSD.org Fri Dec 5 20:24:31 2008 From: www at FreeBSD.org (World Wide Web Owner) Date: Fri Dec 5 20:24:37 2008 Subject: FreeBSD web build failed on www.freebsd.org Message-ID: <200812060424.mB64OU0v004868@www.freebsd.org> ? relnotes7/doc/share/sgml/dev-auto.sgml ===> FAQ ===> advocacy ===> commercial ===> community ===> copyright ===> developers ===> docproj ===> docs ===> donations ===> events ===> events/2002 ===> events/2003 ===> gnome ===> gnome/docs ===> gnome/images ===> handbook ===> internal /usr/bin/perl5 /w/www/build/www/en/internal/homepage.pl > homepage.inc /usr/bin/sed -e 's///' homepage.sgml > homepage.sgml-tmp /usr/bin/env SGML_CATALOG_FILES= /usr/local/bin/sgmlnorm -d -ifreebsd.urls.absolute -c /usr/local/share/sgml/html/catalog -c /usr/local/share/sgml/catalog -c /w/www/build/www/en/share/sgml/catalog -c /w/www/build/www/share/sgml/catalog -D /w/www/build/www/en/internal homepage.sgml-tmp > homepage.html || (/bin/rm -f homepage.sgml-tmp homepage.html && false) /bin/rm -f homepage.sgml-tmp /usr/local/bin/tidy -wrap 90 -m -raw -preserve -f /dev/null -asxml homepage.html *** Error code 1 (ignored) ===> java ===> java/dists ===> java/docs ===> java/links ===> kse ===> marketing ===> multimedia (test -d output || /bin/mkdir output ) && cd output && /bin/ln -fs ../Makefile.output Makefile && ( for f in multimedia.sgml.intro multimedia.sgml.post multimedia.sgml.pre multimedia.html.intro multimedia.html.post multimedia.html.pre multimedia-input.xml; do /bin/ln -fs ../$f $f; done ) && /usr/bin/perl5 -Tw ../multimedia.pl && /bin/rm -f *.html cd output && make all DIRPRFX=multimedia/output/ "/w/www/build/www/en/multimedia/output/../../..//share/mk/web.site.mk", line 349: warning: Missing closing parenthesis for exists() /usr/bin/sed -e 's///' multimedia.sgml > multimedia.sgml-tmp /usr/bin/env SGML_CATALOG_FILES= /usr/local/bin/sgmlnorm -d -ifreebsd.urls.absolute -c /usr/local/share/sgml/html/catalog -c /usr/local/share/sgml/catalog -c /w/www/build/www/en/share/sgml/catalog -c /w/www/build/www/share/sgml/catalog -D /w/www/build/www/en/multimedia/output multimedia.sgml-tmp > multimedia.html || (/bin/rm -f multimedia.sgml-tmp multimedia.html && false) /usr/local/bin/sgmlnorm:multimedia.sgml-tmp:249:70:E: general entity "type" not defined and no default entity /usr/local/bin/sgmlnorm:multimedia.sgml-tmp:938:33:E: general entity "D" not defined and no default entity /usr/local/bin/sgmlnorm:multimedia.sgml-tmp:1164:67:E: general entity "do" not defined and no default entity /usr/local/bin/sgmlnorm:multimedia.sgml-tmp:1164:74:E: general entity "target" not defined and no default entity *** Error code 1 Stop in /w/www/build/www/en/multimedia/output. *** Error code 1 Stop in /w/www/build/www/en/multimedia. *** Error code 1 Stop in /w/www/build/www/en. 15.00 real 11.50 user 1.66 sys From www at FreeBSD.org Fri Dec 5 20:53:35 2008 From: www at FreeBSD.org (World Wide Web Owner) Date: Fri Dec 5 20:53:41 2008 Subject: FreeBSD web build failed on www.freebsd.org Message-ID: <200812060453.mB64rZgc011827@www.freebsd.org> ? relnotes7/doc/share/sgml/dev-auto.sgml ===> FAQ ===> advocacy ===> commercial ===> community ===> copyright ===> developers ===> docproj ===> docs ===> donations ===> events ===> events/2002 ===> events/2003 ===> gnome ===> gnome/docs ===> gnome/images ===> handbook ===> internal /usr/bin/perl5 /w/www/build/www/en/internal/homepage.pl > homepage.inc /usr/bin/sed -e 's///' homepage.sgml > homepage.sgml-tmp /usr/bin/env SGML_CATALOG_FILES= /usr/local/bin/sgmlnorm -d -ifreebsd.urls.absolute -c /usr/local/share/sgml/html/catalog -c /usr/local/share/sgml/catalog -c /w/www/build/www/en/share/sgml/catalog -c /w/www/build/www/share/sgml/catalog -D /w/www/build/www/en/internal homepage.sgml-tmp > homepage.html || (/bin/rm -f homepage.sgml-tmp homepage.html && false) /bin/rm -f homepage.sgml-tmp /usr/local/bin/tidy -wrap 90 -m -raw -preserve -f /dev/null -asxml homepage.html *** Error code 1 (ignored) ===> java ===> java/dists ===> java/docs ===> java/links ===> kse ===> marketing ===> multimedia (test -d output || /bin/mkdir output ) && cd output && /bin/ln -fs ../Makefile.output Makefile && ( for f in multimedia.sgml.intro multimedia.sgml.post multimedia.sgml.pre multimedia.html.intro multimedia.html.post multimedia.html.pre multimedia-input.xml; do /bin/ln -fs ../$f $f; done ) && /usr/bin/perl5 -Tw ../multimedia.pl && /bin/rm -f *.html cd output && make all DIRPRFX=multimedia/output/ "/w/www/build/www/en/multimedia/output/../../..//share/mk/web.site.mk", line 349: warning: Missing closing parenthesis for exists() /usr/bin/sed -e 's///' multimedia.sgml > multimedia.sgml-tmp /usr/bin/env SGML_CATALOG_FILES= /usr/local/bin/sgmlnorm -d -ifreebsd.urls.absolute -c /usr/local/share/sgml/html/catalog -c /usr/local/share/sgml/catalog -c /w/www/build/www/en/share/sgml/catalog -c /w/www/build/www/share/sgml/catalog -D /w/www/build/www/en/multimedia/output multimedia.sgml-tmp > multimedia.html || (/bin/rm -f multimedia.sgml-tmp multimedia.html && false) /usr/local/bin/sgmlnorm:multimedia.sgml-tmp:249:70:E: general entity "type" not defined and no default entity /usr/local/bin/sgmlnorm:multimedia.sgml-tmp:938:33:E: general entity "D" not defined and no default entity /usr/local/bin/sgmlnorm:multimedia.sgml-tmp:1164:67:E: general entity "do" not defined and no default entity /usr/local/bin/sgmlnorm:multimedia.sgml-tmp:1164:74:E: general entity "target" not defined and no default entity *** Error code 1 Stop in /w/www/build/www/en/multimedia/output. *** Error code 1 Stop in /w/www/build/www/en/multimedia. *** Error code 1 Stop in /w/www/build/www/en. 14.62 real 11.53 user 1.90 sys From www at FreeBSD.org Fri Dec 5 21:23:29 2008 From: www at FreeBSD.org (World Wide Web Owner) Date: Fri Dec 5 21:23:36 2008 Subject: FreeBSD web build failed on www.freebsd.org Message-ID: <200812060523.mB65NT64017907@www.freebsd.org> ? relnotes7/doc/share/sgml/dev-auto.sgml ===> FAQ ===> advocacy ===> commercial ===> community ===> copyright ===> developers ===> docproj ===> docs ===> donations ===> events ===> events/2002 ===> events/2003 ===> gnome ===> gnome/docs ===> gnome/images ===> handbook ===> internal /usr/bin/perl5 /w/www/build/www/en/internal/homepage.pl > homepage.inc /usr/bin/sed -e 's///' homepage.sgml > homepage.sgml-tmp /usr/bin/env SGML_CATALOG_FILES= /usr/local/bin/sgmlnorm -d -ifreebsd.urls.absolute -c /usr/local/share/sgml/html/catalog -c /usr/local/share/sgml/catalog -c /w/www/build/www/en/share/sgml/catalog -c /w/www/build/www/share/sgml/catalog -D /w/www/build/www/en/internal homepage.sgml-tmp > homepage.html || (/bin/rm -f homepage.sgml-tmp homepage.html && false) /bin/rm -f homepage.sgml-tmp /usr/local/bin/tidy -wrap 90 -m -raw -preserve -f /dev/null -asxml homepage.html *** Error code 1 (ignored) ===> java ===> java/dists ===> java/docs ===> java/links ===> kse ===> marketing ===> multimedia (test -d output || /bin/mkdir output ) && cd output && /bin/ln -fs ../Makefile.output Makefile && ( for f in multimedia.sgml.intro multimedia.sgml.post multimedia.sgml.pre multimedia.html.intro multimedia.html.post multimedia.html.pre multimedia-input.xml; do /bin/ln -fs ../$f $f; done ) && /usr/bin/perl5 -Tw ../multimedia.pl && /bin/rm -f *.html cd output && make all DIRPRFX=multimedia/output/ "/w/www/build/www/en/multimedia/output/../../..//share/mk/web.site.mk", line 349: warning: Missing closing parenthesis for exists() /usr/bin/sed -e 's///' multimedia.sgml > multimedia.sgml-tmp /usr/bin/env SGML_CATALOG_FILES= /usr/local/bin/sgmlnorm -d -ifreebsd.urls.absolute -c /usr/local/share/sgml/html/catalog -c /usr/local/share/sgml/catalog -c /w/www/build/www/en/share/sgml/catalog -c /w/www/build/www/share/sgml/catalog -D /w/www/build/www/en/multimedia/output multimedia.sgml-tmp > multimedia.html || (/bin/rm -f multimedia.sgml-tmp multimedia.html && false) /usr/local/bin/sgmlnorm:multimedia.sgml-tmp:249:70:E: general entity "type" not defined and no default entity /usr/local/bin/sgmlnorm:multimedia.sgml-tmp:938:33:E: general entity "D" not defined and no default entity /usr/local/bin/sgmlnorm:multimedia.sgml-tmp:1164:67:E: general entity "do" not defined and no default entity /usr/local/bin/sgmlnorm:multimedia.sgml-tmp:1164:74:E: general entity "target" not defined and no default entity *** Error code 1 Stop in /w/www/build/www/en/multimedia/output. *** Error code 1 Stop in /w/www/build/www/en/multimedia. *** Error code 1 Stop in /w/www/build/www/en. 15.13 real 11.35 user 1.67 sys From www at FreeBSD.org Fri Dec 5 21:53:28 2008 From: www at FreeBSD.org (World Wide Web Owner) Date: Fri Dec 5 21:53:35 2008 Subject: FreeBSD web build failed on www.freebsd.org Message-ID: <200812060553.mB65rRxK021518@www.freebsd.org> ? relnotes7/doc/share/sgml/dev-auto.sgml ===> FAQ ===> advocacy ===> commercial ===> community ===> copyright ===> developers ===> docproj ===> docs ===> donations ===> events ===> events/2002 ===> events/2003 ===> gnome ===> gnome/docs ===> gnome/images ===> handbook ===> internal /usr/bin/perl5 /w/www/build/www/en/internal/homepage.pl > homepage.inc /usr/bin/sed -e 's///' homepage.sgml > homepage.sgml-tmp /usr/bin/env SGML_CATALOG_FILES= /usr/local/bin/sgmlnorm -d -ifreebsd.urls.absolute -c /usr/local/share/sgml/html/catalog -c /usr/local/share/sgml/catalog -c /w/www/build/www/en/share/sgml/catalog -c /w/www/build/www/share/sgml/catalog -D /w/www/build/www/en/internal homepage.sgml-tmp > homepage.html || (/bin/rm -f homepage.sgml-tmp homepage.html && false) /bin/rm -f homepage.sgml-tmp /usr/local/bin/tidy -wrap 90 -m -raw -preserve -f /dev/null -asxml homepage.html *** Error code 1 (ignored) ===> java ===> java/dists ===> java/docs ===> java/links ===> kse ===> marketing ===> multimedia (test -d output || /bin/mkdir output ) && cd output && /bin/ln -fs ../Makefile.output Makefile && ( for f in multimedia.sgml.intro multimedia.sgml.post multimedia.sgml.pre multimedia.html.intro multimedia.html.post multimedia.html.pre multimedia-input.xml; do /bin/ln -fs ../$f $f; done ) && /usr/bin/perl5 -Tw ../multimedia.pl && /bin/rm -f *.html cd output && make all DIRPRFX=multimedia/output/ "/w/www/build/www/en/multimedia/output/../../..//share/mk/web.site.mk", line 349: warning: Missing closing parenthesis for exists() /usr/bin/sed -e 's///' multimedia.sgml > multimedia.sgml-tmp /usr/bin/env SGML_CATALOG_FILES= /usr/local/bin/sgmlnorm -d -ifreebsd.urls.absolute -c /usr/local/share/sgml/html/catalog -c /usr/local/share/sgml/catalog -c /w/www/build/www/en/share/sgml/catalog -c /w/www/build/www/share/sgml/catalog -D /w/www/build/www/en/multimedia/output multimedia.sgml-tmp > multimedia.html || (/bin/rm -f multimedia.sgml-tmp multimedia.html && false) /usr/local/bin/sgmlnorm:multimedia.sgml-tmp:249:70:E: general entity "type" not defined and no default entity /usr/local/bin/sgmlnorm:multimedia.sgml-tmp:938:33:E: general entity "D" not defined and no default entity /usr/local/bin/sgmlnorm:multimedia.sgml-tmp:1164:67:E: general entity "do" not defined and no default entity /usr/local/bin/sgmlnorm:multimedia.sgml-tmp:1164:74:E: general entity "target" not defined and no default entity *** Error code 1 Stop in /w/www/build/www/en/multimedia/output. *** Error code 1 Stop in /w/www/build/www/en/multimedia. *** Error code 1 Stop in /w/www/build/www/en. 14.40 real 11.21 user 2.22 sys From www at FreeBSD.org Fri Dec 5 22:23:29 2008 From: www at FreeBSD.org (World Wide Web Owner) Date: Fri Dec 5 22:23:34 2008 Subject: FreeBSD web build failed on www.freebsd.org Message-ID: <200812060623.mB66NSNo025758@www.freebsd.org> ? relnotes7/doc/share/sgml/dev-auto.sgml ===> FAQ ===> advocacy ===> commercial ===> community ===> copyright ===> developers ===> docproj ===> docs ===> donations ===> events ===> events/2002 ===> events/2003 ===> gnome ===> gnome/docs ===> gnome/images ===> handbook ===> internal /usr/bin/perl5 /w/www/build/www/en/internal/homepage.pl > homepage.inc /usr/bin/sed -e 's///' homepage.sgml > homepage.sgml-tmp /usr/bin/env SGML_CATALOG_FILES= /usr/local/bin/sgmlnorm -d -ifreebsd.urls.absolute -c /usr/local/share/sgml/html/catalog -c /usr/local/share/sgml/catalog -c /w/www/build/www/en/share/sgml/catalog -c /w/www/build/www/share/sgml/catalog -D /w/www/build/www/en/internal homepage.sgml-tmp > homepage.html || (/bin/rm -f homepage.sgml-tmp homepage.html && false) /bin/rm -f homepage.sgml-tmp /usr/local/bin/tidy -wrap 90 -m -raw -preserve -f /dev/null -asxml homepage.html *** Error code 1 (ignored) ===> java ===> java/dists ===> java/docs ===> java/links ===> kse ===> marketing ===> multimedia (test -d output || /bin/mkdir output ) && cd output && /bin/ln -fs ../Makefile.output Makefile && ( for f in multimedia.sgml.intro multimedia.sgml.post multimedia.sgml.pre multimedia.html.intro multimedia.html.post multimedia.html.pre multimedia-input.xml; do /bin/ln -fs ../$f $f; done ) && /usr/bin/perl5 -Tw ../multimedia.pl && /bin/rm -f *.html cd output && make all DIRPRFX=multimedia/output/ "/w/www/build/www/en/multimedia/output/../../..//share/mk/web.site.mk", line 349: warning: Missing closing parenthesis for exists() /usr/bin/sed -e 's///' multimedia.sgml > multimedia.sgml-tmp /usr/bin/env SGML_CATALOG_FILES= /usr/local/bin/sgmlnorm -d -ifreebsd.urls.absolute -c /usr/local/share/sgml/html/catalog -c /usr/local/share/sgml/catalog -c /w/www/build/www/en/share/sgml/catalog -c /w/www/build/www/share/sgml/catalog -D /w/www/build/www/en/multimedia/output multimedia.sgml-tmp > multimedia.html || (/bin/rm -f multimedia.sgml-tmp multimedia.html && false) /usr/local/bin/sgmlnorm:multimedia.sgml-tmp:249:70:E: general entity "type" not defined and no default entity /usr/local/bin/sgmlnorm:multimedia.sgml-tmp:938:33:E: general entity "D" not defined and no default entity /usr/local/bin/sgmlnorm:multimedia.sgml-tmp:1164:67:E: general entity "do" not defined and no default entity /usr/local/bin/sgmlnorm:multimedia.sgml-tmp:1164:74:E: general entity "target" not defined and no default entity *** Error code 1 Stop in /w/www/build/www/en/multimedia/output. *** Error code 1 Stop in /w/www/build/www/en/multimedia. *** Error code 1 Stop in /w/www/build/www/en. 14.46 real 10.10 user 2.95 sys From danger at FreeBSD.org Sat Dec 6 03:16:04 2008 From: danger at FreeBSD.org (danger@FreeBSD.org) Date: Sat Dec 6 03:16:10 2008 Subject: docs/129448: loader(8) manpage typo: two init_script listings, the second one should be init_shell Message-ID: <200812061116.mB6BG3cJ053636@freefall.freebsd.org> Synopsis: loader(8) manpage typo: two init_script listings, the second one should be init_shell Responsible-Changed-From-To: freebsd-doc->danger Responsible-Changed-By: danger Responsible-Changed-When: Sat Dec 6 11:15:46 UTC 2008 Responsible-Changed-Why: Take http://www.freebsd.org/cgi/query-pr.cgi?pr=129448 From g71 at laposte.net Sat Dec 6 07:30:08 2008 From: g71 at laposte.net (guillaume) Date: Sat Dec 6 07:30:14 2008 Subject: docs/129464: using packages system Message-ID: <200812061529.mB6FTBEd024942@www.freebsd.org> >Number: 129464 >Category: docs >Synopsis: using packages system >Confidential: no >Severity: serious >Priority: high >Responsible: freebsd-doc >State: open >Quarter: >Keywords: >Date-Required: >Class: doc-bug >Submitter-Id: current-users >Arrival-Date: Sat Dec 06 15:30:07 UTC 2008 >Closed-Date: >Last-Modified: >Originator: guillaume >Release: 7.0 >Organization: >Environment: FreeBSD ordi1.guigui.net 7.0-RELEASE FreeBSD 7.0-RELEASE #0: Sun Feb 24 19:59:52 UTC 2008 root@logan.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386 >Description: 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. when a beginner read the handbook, he lost a lot of hours before he understand that (if, by miracle, he doesn't give up FreeBSD). >How-To-Repeat: see above. >Fix: the good commands are portupgrade and pkg_deinstall. the portupgrade tool must be natively integrated in FreeBSD. example of procedure: 1) it's better to have PACKAGESITE to the last stable branch by default, no? 2) install port collection with csup 3) clean database with pkgdb -aF (is it necessary after the port collection install?) 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... >Release-Note: >Audit-Trail: >Unformatted: From eitanadlerlist at gmail.com Sat Dec 6 19:37:54 2008 From: eitanadlerlist at gmail.com (Eitan Adler) Date: Sat Dec 6 19:38:38 2008 Subject: bc documentation Message-ID: <493B4511.4030905@gmail.com> -----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 sziszi at bsd.hu Sun Dec 7 01:26:25 2008 From: sziszi at bsd.hu (Szilveszter Adam) Date: Sun Dec 7 01:26:31 2008 Subject: docs/129464: using packages system In-Reply-To: <200812061529.mB6FTBEd024942@www.freebsd.org> References: <200812061529.mB6FTBEd024942@www.freebsd.org> Message-ID: <20081207092621.GC2187@baranyfelhocske.buza.adamsfamily.xx> 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 sziszi at bsd.hu Sun Dec 7 01:30:05 2008 From: sziszi at bsd.hu (Szilveszter Adam) Date: Sun Dec 7 01:30:11 2008 Subject: docs/129464: using packages system Message-ID: <200812070930.mB79U4Hb095511@freefall.freebsd.org> 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 g71 at laposte.net Sun Dec 7 15:30:04 2008 From: g71 at laposte.net (guillaume) Date: Sun Dec 7 15:30:13 2008 Subject: docs/129464: using packages system Message-ID: <200812072330.mB7NU4jK048778@freefall.freebsd.org> 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 sziszi at bsd.hu Sun Dec 7 22:50:03 2008 From: sziszi at bsd.hu (Szilveszter Adam) Date: Sun Dec 7 22:50:10 2008 Subject: docs/129464: using packages system Message-ID: <200812080650.mB86o2dM087985@freefall.freebsd.org> 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 bugmaster at FreeBSD.org Mon Dec 8 03:06:06 2008 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Dec 8 03:06:36 2008 Subject: Current unassigned doc problem reports Message-ID: <200812081106.mB8B65AO013304@freefall.freebsd.org> (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 blackend at FreeBSD.org Mon Dec 8 04:24:24 2008 From: blackend at FreeBSD.org (blackend@FreeBSD.org) Date: Mon Dec 8 04:24:32 2008 Subject: docs/129281: Audio CD ripping/duplication shouldn't recommend the use of non endianness safe dd/burncd commands Message-ID: <200812081224.mB8COONv077305@freefall.freebsd.org> 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 toxic at doobie.com Mon Dec 8 10:20:02 2008 From: toxic at doobie.com (Jeff Burchell) Date: Mon Dec 8 10:20:08 2008 Subject: docs/129506: Addition to Additional Contributors. Message-ID: <200812081810.mB8IAWQu052607@www.freebsd.org> >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 fernandotonus at gmail.com Mon Dec 8 12:42:33 2008 From: fernandotonus at gmail.com (Fernando Tonus) Date: Mon Dec 8 12:42:40 2008 Subject: Handbook - Section IPFW Message-ID: 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 cswiger at mac.com Mon Dec 8 13:08:36 2008 From: cswiger at mac.com (Chuck Swiger) Date: Mon Dec 8 13:08:42 2008 Subject: Handbook - Section IPFW In-Reply-To: References: Message-ID: <4E91A5AC-DE5B-4C25-8CA1-F7F35E9F7FDE@mac.com> 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 ricardo.meb.jesus at gmail.com Tue Dec 9 09:20:49 2008 From: ricardo.meb.jesus at gmail.com (Ricardo Jesus) Date: Tue Dec 9 09:20:55 2008 Subject: Handbook section 4.3 Message-ID: <493EA1E0.2040200@gmail.com> 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 fernan.aguero at gmail.com Tue Dec 9 09:50:48 2008 From: fernan.aguero at gmail.com (Fernan Aguero) Date: Tue Dec 9 09:50:55 2008 Subject: update release schedule information? Message-ID: <520894aa0812090927h4034e7ecnff5d05d2d6138554@mail.gmail.com> 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 -------------- next part -------------- A non-text attachment was scrubbed... Name: release.ent.diff Type: text/x-patch Size: 73 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-doc/attachments/20081209/ca5e0b91/release.ent.bin -------------- next part -------------- A non-text attachment was scrubbed... Name: schedule.sgml.diff Type: text/x-patch Size: 632 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-doc/attachments/20081209/ca5e0b91/schedule.sgml.bin From pgj at FreeBSD.org Tue Dec 9 09:57:57 2008 From: pgj at FreeBSD.org (pgj@FreeBSD.org) Date: Tue Dec 9 09:58:03 2008 Subject: docs/129506: Addition to Additional Contributors. Message-ID: <200812091757.mB9HvuMq053598@freefall.freebsd.org> 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 =?UTF-8?B?4Lib4Li44LmL4Lii4LiE4Li44LiT4Lig4Liy4Lie4Lii4Li04LmI4LiH4LmD?= Wed Dec 10 01:01:36 2008 From: =?UTF-8?B?4Lib4Li44LmL4Lii4LiE4Li44LiT4Lig4Liy4Lie4Lii4Li04LmI4LiH4LmD?= (=?UTF-8?B?4Lib4Li44LmL4Lii4LiE4Li44LiT4Lig4Liy4Lie4Lii4Li04LmI4LiH4LmD?=) Date: Wed Dec 10 01:01:43 2008 Subject: =?utf-8?b?4LiC4LmI4Liy4Lin4LiU4Li14Liq4Liz4Lir4Lij4Lix4Lia4LmA?= =?utf-8?b?4LiB4Lip4LiV4Lij4LiB4Lij?= Message-ID: <33443453125259@mail.truemail.co.th> ???????????????????????? ?????????????????????????????????????????? 1. ???????????? ??? ?????????????????? ???????????????????????????? 20% ??????????????????????????????????????????????? ?????????????????????????????????????????????????????????????????????????????????????? (Humic Acid) ????????????????? ???? ?????????? ??? ??????????????? ???? ?????????????? (Guanophosphate) ????????????????????????????????????????????????????????? ????????????????????????????????????????????? 6 ????? ????????????????????????????????????????????????????????? ??????????????????????? 1 ??????? ?????????? : ?????????? 60% ???????????? 20% ?????????? 20% ??????????? : ??????????????????????????????????????? ???????????????????????????? ????? ??????????????????????????????? ??????????????? ?????????????????? ????????????????? ????????? ????????????????? ????????? ???????? ??????? ???????????????????????? ???????????????????????????? 1. ??????????????????????????? (????????? - ???????? - ??????????) 2. ??????????????? (Organicmetter) ?????????????????????? ?????????????? ??? ?????????????????????????????????????????????????? 3. ????????? (Humic Acid) ??????????????????????????????????? ??????? - ????????????????????????? ???????????? (??????????????????????????) - ??????????????????????????????????? ????????????????????????????????????? (???????????????? 3 ???? ??? ???????? 1 ???? ???????????) 2. ??????????????????????????????????????? ???????????????????????????????????????? ??????????????????????? ?????? N,P,K ??????????? ??????????????? ???? ?????????? ??????????????????????????? 2H2O+SI+2O ????????????????? ??????????????????????? 5,667 p.p.m ???????????????????????? ????????????????????????????????????????????????????? 200 ?? ????????????????????????? ???????????????????????????????????????? 50 ??????????????????????????? ?????????????????????????????? ??????????????? ??????????????????/?????????????????????????????????????????????????? ?????????????????????????????????????????????????????????? ????????????????????????????????????????? 1. ??????????????????? 50% ??????????????????????????????????? 2. ??????????????? - ??????? ??? - ??????? ????????????????????????? 3. ?? ?.?. 1848 ????????????????????????????? ?????????????????? 50 - 100% 4. ?????????????? 300 ??????????????? ???????????????????????????? - ???????????????????? ?????? ???????????????????????????????????? 50 - 200% 5. ???????????????? ???????????????????? 30 - 40% ???????????????????? 6. ????????????????????????????????????????????????????????????????? 5 ???? 7. ?????????????????????????????? 40% ????????????????????????? 8. ?????????????????? P,N ??? K ???????????????? ????????????????????????? 9. ????????????????????????????????? (????????????????????????????) 10. ????????????????????????????????????????? 50 - 100% http://www.peopleadoxy.com/wingold.htm ?????????????????????? ??? ???????? ??? 084-9100636 ?????????????????????????????????????? ???????????????????????????? From errol at research.olemiss.edu Wed Dec 10 08:41:24 2008 From: errol at research.olemiss.edu (Errol Sayre) Date: Wed Dec 10 08:41:31 2008 Subject: Missing line on Network File System page Message-ID: <362D5E56-CF69-4194-A799-D3F0412D0C7B@research.olemiss.edu> 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 r.c.ladan at gmail.com Wed Dec 10 08:59:26 2008 From: r.c.ladan at gmail.com (Rene Ladan) Date: Wed Dec 10 08:59:33 2008 Subject: Missing line on Network File System page In-Reply-To: <362D5E56-CF69-4194-A799-D3F0412D0C7B@research.olemiss.edu> References: <362D5E56-CF69-4194-A799-D3F0412D0C7B@research.olemiss.edu> Message-ID: 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 sonic2000gr at gmail.com Wed Dec 10 09:00:14 2008 From: sonic2000gr at gmail.com (Manolis Kiagias) Date: Wed Dec 10 09:00:21 2008 Subject: Missing line on Network File System page In-Reply-To: <362D5E56-CF69-4194-A799-D3F0412D0C7B@research.olemiss.edu> References: <362D5E56-CF69-4194-A799-D3F0412D0C7B@research.olemiss.edu> Message-ID: <493FF598.4020503@gmail.com> 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 keramida at freebsd.org Wed Dec 10 12:56:09 2008 From: keramida at freebsd.org (Giorgos Keramidas) Date: Wed Dec 10 12:56:17 2008 Subject: [PATCH] Adding elements to wlan Handbook section Message-ID: <871vwfn418.fsf@kobe.laptop> 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 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 +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 . @@ -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 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 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 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 %%% -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 194 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-doc/attachments/20081210/be83f6f4/attachment.pgp From murray at stokely.org Wed Dec 10 13:10:32 2008 From: murray at stokely.org (Murray Stokely) Date: Wed Dec 10 13:10:39 2008 Subject: [PATCH] Adding elements to wlan Handbook section In-Reply-To: <871vwfn418.fsf@kobe.laptop> References: <871vwfn418.fsf@kobe.laptop> Message-ID: <2a7894eb0812101310v2123a452q26b0e07630e7f209@mail.gmail.com> 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 sonic2000gr at gmail.com Wed Dec 10 13:12:21 2008 From: sonic2000gr at gmail.com (Manolis Kiagias) Date: Wed Dec 10 13:12:27 2008 Subject: [PATCH] Adding elements to wlan Handbook section In-Reply-To: <871vwfn418.fsf@kobe.laptop> References: <871vwfn418.fsf@kobe.laptop> Message-ID: <494030B1.2080001@gmail.com> 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 keramida at freebsd.org Wed Dec 10 13:20:18 2008 From: keramida at freebsd.org (Giorgos Keramidas) Date: Wed Dec 10 13:20:26 2008 Subject: [PATCH] Adding elements to wlan Handbook section In-Reply-To: <2a7894eb0812101310v2123a452q26b0e07630e7f209@mail.gmail.com> (Murray Stokely's message of "Wed, 10 Dec 2008 13:10:31 -0800") References: <871vwfn418.fsf@kobe.laptop> <2a7894eb0812101310v2123a452q26b0e07630e7f209@mail.gmail.com> Message-ID: <878wqnafso.fsf@kobe.laptop> 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 keramida at freebsd.org Wed Dec 10 13:21:48 2008 From: keramida at freebsd.org (Giorgos Keramidas) Date: Wed Dec 10 13:21:55 2008 Subject: [PATCH] Adding elements to wlan Handbook section In-Reply-To: <494030B1.2080001@gmail.com> (Manolis Kiagias's message of "Wed, 10 Dec 2008 23:12:17 +0200") References: <871vwfn418.fsf@kobe.laptop> <494030B1.2080001@gmail.com> Message-ID: <874p1bafq6.fsf@kobe.laptop> 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 murray at stokely.org Wed Dec 10 13:22:58 2008 From: murray at stokely.org (Murray Stokely) Date: Wed Dec 10 13:23:17 2008 Subject: [PATCH] Adding elements to wlan Handbook section In-Reply-To: <878wqnafso.fsf@kobe.laptop> References: <871vwfn418.fsf@kobe.laptop> <2a7894eb0812101310v2123a452q26b0e07630e7f209@mail.gmail.com> <878wqnafso.fsf@kobe.laptop> Message-ID: <2a7894eb0812101322o77b12fc9k8208f83d62481ad3@mail.gmail.com> 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 keramida at freebsd.org Wed Dec 10 13:32:48 2008 From: keramida at freebsd.org (Giorgos Keramidas) Date: Wed Dec 10 13:32:55 2008 Subject: [PATCH] Adding elements to wlan Handbook section In-Reply-To: <2a7894eb0812101322o77b12fc9k8208f83d62481ad3@mail.gmail.com> (Murray Stokely's message of "Wed, 10 Dec 2008 13:22:57 -0800") References: <871vwfn418.fsf@kobe.laptop> <2a7894eb0812101310v2123a452q26b0e07630e7f209@mail.gmail.com> <878wqnafso.fsf@kobe.laptop> <2a7894eb0812101322o77b12fc9k8208f83d62481ad3@mail.gmail.com> Message-ID: <87prjz67ij.fsf@kobe.laptop> 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 sonic2000gr at gmail.com Wed Dec 10 13:36:26 2008 From: sonic2000gr at gmail.com (Manolis Kiagias) Date: Wed Dec 10 13:36:33 2008 Subject: [PATCH] Adding elements to wlan Handbook section In-Reply-To: <2a7894eb0812101322o77b12fc9k8208f83d62481ad3@mail.gmail.com> References: <871vwfn418.fsf@kobe.laptop> <2a7894eb0812101310v2123a452q26b0e07630e7f209@mail.gmail.com> <878wqnafso.fsf@kobe.laptop> <2a7894eb0812101322o77b12fc9k8208f83d62481ad3@mail.gmail.com> Message-ID: <49403656.4020303@gmail.com> 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 r.c.ladan at gmail.com Thu Dec 11 10:23:07 2008 From: r.c.ladan at gmail.com (Rene Ladan) Date: Thu Dec 11 10:23:19 2008 Subject: [RFC] Committers guide: replace CVS by SVN where appropiate In-Reply-To: <49184BDB.5070707@FreeBSD.org> References: <49174B71.9080800@gmail.com> <49184BDB.5070707@FreeBSD.org> Message-ID: 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) -------------- next part -------------- A non-text attachment was scrubbed... Name: cg-nocd.diff Type: text/x-patch Size: 705 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-doc/attachments/20081211/a15d24c1/cg-nocd.bin From sonic2000gr at gmail.com Thu Dec 11 11:31:32 2008 From: sonic2000gr at gmail.com (Manolis Kiagias) Date: Thu Dec 11 11:31:39 2008 Subject: [RFC] Committers guide: replace CVS by SVN where appropiate In-Reply-To: References: <49174B71.9080800@gmail.com> <49184BDB.5070707@FreeBSD.org> Message-ID: <49416A90.3020300@gmail.com> 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 trhodes at FreeBSD.org Thu Dec 11 18:02:07 2008 From: trhodes at FreeBSD.org (Tom Rhodes) Date: Thu Dec 11 18:02:19 2008 Subject: [PATCH] Adding elements to wlan Handbook section In-Reply-To: <871vwfn418.fsf@kobe.laptop> References: <871vwfn418.fsf@kobe.laptop> Message-ID: <20081211210158.5a37ba32.trhodes@FreeBSD.org> 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 keramida at freebsd.org Thu Dec 11 18:30:30 2008 From: keramida at freebsd.org (Giorgos Keramidas) Date: Thu Dec 11 18:30:37 2008 Subject: [PATCH] Adding elements to wlan Handbook section In-Reply-To: <2a7894eb0812101322o77b12fc9k8208f83d62481ad3@mail.gmail.com> (Murray Stokely's message of "Wed, 10 Dec 2008 13:22:57 -0800") References: <871vwfn418.fsf@kobe.laptop> <2a7894eb0812101310v2123a452q26b0e07630e7f209@mail.gmail.com> <878wqnafso.fsf@kobe.laptop> <2a7894eb0812101322o77b12fc9k8208f83d62481ad3@mail.gmail.com> Message-ID: <87k5a63z2d.fsf@kobe.laptop> 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 keramida at freebsd.org Thu Dec 11 18:51:22 2008 From: keramida at freebsd.org (Giorgos Keramidas) Date: Thu Dec 11 18:51:29 2008 Subject: [PATCH] Adding elements to wlan Handbook section In-Reply-To: <49403656.4020303@gmail.com> (Manolis Kiagias's message of "Wed, 10 Dec 2008 23:36:22 +0200") References: <871vwfn418.fsf@kobe.laptop> <2a7894eb0812101310v2123a452q26b0e07630e7f209@mail.gmail.com> <878wqnafso.fsf@kobe.laptop> <2a7894eb0812101322o77b12fc9k8208f83d62481ad3@mail.gmail.com> <49403656.4020303@gmail.com> Message-ID: <8763lq14yo.fsf@kobe.laptop> 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 sonic2000gr at gmail.com Thu Dec 11 21:28:59 2008 From: sonic2000gr at gmail.com (Manolis Kiagias) Date: Thu Dec 11 21:29:06 2008 Subject: [PATCH] Adding elements to wlan Handbook section In-Reply-To: <8763lq14yo.fsf@kobe.laptop> 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> Message-ID: <4941F694.3040600@gmail.com> 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 keramida at ceid.upatras.gr Thu Dec 11 23:17:15 2008 From: keramida at ceid.upatras.gr (Giorgos Keramidas) Date: Thu Dec 11 23:17:24 2008 Subject: [PATCH] Adding elements to wlan Handbook section In-Reply-To: <87k5a63z2d.fsf@kobe.laptop> (Giorgos Keramidas's message of "Fri, 12 Dec 2008 04:30:18 +0200") References: <871vwfn418.fsf@kobe.laptop> <2a7894eb0812101310v2123a452q26b0e07630e7f209@mail.gmail.com> <878wqnafso.fsf@kobe.laptop> <2a7894eb0812101322o77b12fc9k8208f83d62481ad3@mail.gmail.com> <87k5a63z2d.fsf@kobe.laptop> Message-ID: <87y6ylg9qh.fsf@kobe.laptop> 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 r.c.ladan at gmail.com Thu Dec 11 23:51:09 2008 From: r.c.ladan at gmail.com (Rene Ladan) Date: Thu Dec 11 23:51:16 2008 Subject: [PATCH] Adding elements to wlan Handbook section In-Reply-To: <87k5a63z2d.fsf@kobe.laptop> References: <871vwfn418.fsf@kobe.laptop> <2a7894eb0812101310v2123a452q26b0e07630e7f209@mail.gmail.com> <878wqnafso.fsf@kobe.laptop> <2a7894eb0812101322o77b12fc9k8208f83d62481ad3@mail.gmail.com> <87k5a63z2d.fsf@kobe.laptop> Message-ID: 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 pgj at FreeBSD.org Fri Dec 12 00:58:49 2008 From: pgj at FreeBSD.org (Gabor PALI) Date: Fri Dec 12 00:58:56 2008 Subject: [PATCH] Adding elements to wlan Handbook section In-Reply-To: References: <871vwfn418.fsf@kobe.laptop> <2a7894eb0812101310v2123a452q26b0e07630e7f209@mail.gmail.com> <878wqnafso.fsf@kobe.laptop> <2a7894eb0812101322o77b12fc9k8208f83d62481ad3@mail.gmail.com> <87k5a63z2d.fsf@kobe.laptop> Message-ID: <494227B4.3070504@FreeBSD.org> 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 keramida at freebsd.org Fri Dec 12 01:04:51 2008 From: keramida at freebsd.org (Giorgos Keramidas) Date: Fri Dec 12 01:04:58 2008 Subject: [PATCH] Adding elements to wlan Handbook section In-Reply-To: (Rene Ladan's message of "Fri, 12 Dec 2008 08:51:07 +0100") References: <871vwfn418.fsf@kobe.laptop> <2a7894eb0812101310v2123a452q26b0e07630e7f209@mail.gmail.com> <878wqnafso.fsf@kobe.laptop> <2a7894eb0812101322o77b12fc9k8208f83d62481ad3@mail.gmail.com> <87k5a63z2d.fsf@kobe.laptop> Message-ID: <871vwdahna.fsf@kobe.laptop> 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 pgj at FreeBSD.org Fri Dec 12 01:05:28 2008 From: pgj at FreeBSD.org (Gabor PALI) Date: Fri Dec 12 01:05:34 2008 Subject: [RFC] Committers guide: replace CVS by SVN where appropiate In-Reply-To: References: <49174B71.9080800@gmail.com> <49184BDB.5070707@FreeBSD.org> Message-ID: <4942293B.6080404@FreeBSD.org> 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 r.c.ladan at gmail.com Fri Dec 12 03:34:51 2008 From: r.c.ladan at gmail.com (Rene Ladan) Date: Fri Dec 12 03:34:58 2008 Subject: [RFC] Committers guide: replace CVS by SVN where appropiate In-Reply-To: <4942293B.6080404@FreeBSD.org> References: <49174B71.9080800@gmail.com> <49184BDB.5070707@FreeBSD.org> <4942293B.6080404@FreeBSD.org> Message-ID: 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 pgj at FreeBSD.org Fri Dec 12 05:08:51 2008 From: pgj at FreeBSD.org (Gabor PALI) Date: Fri Dec 12 05:08:57 2008 Subject: [RFC] Committers guide: replace CVS by SVN where appropiate In-Reply-To: References: <49174B71.9080800@gmail.com> <49184BDB.5070707@FreeBSD.org> <4942293B.6080404@FreeBSD.org> Message-ID: <4942624F.3030302@FreeBSD.org> 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 r.c.ladan at gmail.com Fri Dec 12 05:21:14 2008 From: r.c.ladan at gmail.com (Rene Ladan) Date: Fri Dec 12 05:21:21 2008 Subject: [RFC] Committers guide: replace CVS by SVN where appropiate In-Reply-To: <4942624F.3030302@FreeBSD.org> References: <49174B71.9080800@gmail.com> <49184BDB.5070707@FreeBSD.org> <4942293B.6080404@FreeBSD.org> <4942624F.3030302@FreeBSD.org> Message-ID: 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 hrs at FreeBSD.org Fri Dec 12 08:47:38 2008 From: hrs at FreeBSD.org (Hiroki Sato) Date: Fri Dec 12 08:47:50 2008 Subject: [PATCH] Adding elements to wlan Handbook section In-Reply-To: <4941F694.3040600@gmail.com> References: <49403656.4020303@gmail.com> <8763lq14yo.fsf@kobe.laptop> <4941F694.3040600@gmail.com> Message-ID: <20081213.014325.183748569.hrs@allbsd.org> 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 -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-doc/attachments/20081212/a7c447bf/attachment.pgp From hrs at FreeBSD.org Fri Dec 12 08:47:38 2008 From: hrs at FreeBSD.org (Hiroki Sato) Date: Fri Dec 12 08:47:51 2008 Subject: [PATCH] Adding elements to wlan Handbook section In-Reply-To: <871vwdahna.fsf@kobe.laptop> References: <87k5a63z2d.fsf@kobe.laptop> <871vwdahna.fsf@kobe.laptop> Message-ID: <20081213.014606.247395509.hrs@allbsd.org> Skipped content of type multipart/mixed-------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-doc/attachments/20081212/054784b3/attachment.pgp From murray at stokely.org Fri Dec 12 09:09:02 2008 From: murray at stokely.org (Murray Stokely) Date: Fri Dec 12 09:09:07 2008 Subject: [PATCH] Adding elements to wlan Handbook section In-Reply-To: <871vwdahna.fsf@kobe.laptop> 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> Message-ID: <2a7894eb0812120836l4010d213y373f38d544468274@mail.gmail.com> 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 bill at shakespeare-nyc.com Fri Dec 12 15:07:52 2008 From: bill at shakespeare-nyc.com (Bill Kurland) Date: Fri Dec 12 15:07:59 2008 Subject: errata? 3.3.1 Symbolic Permissions Message-ID: <4942EB33.5080504@shakespeare-nyc.com> 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 danger at FreeBSD.org Fri Dec 12 17:59:26 2008 From: danger at FreeBSD.org (Daniel Gerzo) Date: Fri Dec 12 17:59:32 2008 Subject: errata? 3.3.1 Symbolic Permissions In-Reply-To: <4942EB33.5080504@shakespeare-nyc.com> References: <4942EB33.5080504@shakespeare-nyc.com> Message-ID: <403849365.20081213024023@rulez.sk> 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 > 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" ? I think the description is correct, maybe I'm missing something? -- Best regards, Daniel mailto:danger@FreeBSD.org From pgj at FreeBSD.org Fri Dec 12 22:53:26 2008 From: pgj at FreeBSD.org (Gabor PALI) Date: Fri Dec 12 22:53:32 2008 Subject: [PATCH] Adding elements to wlan Handbook section In-Reply-To: <20081213.014606.247395509.hrs@allbsd.org> References: <87k5a63z2d.fsf@kobe.laptop> <871vwdahna.fsf@kobe.laptop> <20081213.014606.247395509.hrs@allbsd.org> Message-ID: <49435BD3.9030400@FreeBSD.org> 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 From minimarmot at gmail.com Sat Dec 13 20:50:01 2008 From: minimarmot at gmail.com (Ben Kaduk) Date: Sat Dec 13 20:50:08 2008 Subject: docs/129623: suser(9) claims that the interface is still exported, though deprecated Message-ID: <200812140449.mBE4nf2R087003@www.freebsd.org> >Number: 129623 >Category: docs >Synopsis: suser(9) claims that the interface is still exported, though deprecated >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-doc >State: open >Quarter: >Keywords: >Date-Required: >Class: doc-bug >Submitter-Id: current-users >Arrival-Date: Sun Dec 14 04:50:00 UTC 2008 >Closed-Date: >Last-Modified: >Originator: Ben Kaduk >Release: 8-current >Organization: MIT SIPB >Environment: pleonasm# uname -a FreeBSD pleonasm.mit.edu 8.0-CURRENT FreeBSD 8.0-CURRENT #6: Fri Dec 12 18:37:53 UTC 2008 kaduk@pleonasm.mit.edu:/usr/obj/usr/src/sys/PLEONASM i386 >Description: compare the contents of suser(9) and /usr/include/sys/priv.h ... the latter no longer has the definition of the function. It's not clear to me if the man page for suser(9) should just be removed, or retained as a pointer to priv_check(9). >How-To-Repeat: Try to compile a module that uses suser, and get "No such file or directory" when trying to load it. >Fix: Remove the suser(9) manpage? >Release-Note: >Audit-Trail: >Unformatted: From murray at stokely.org Sat Dec 13 21:46:06 2008 From: murray at stokely.org (Murray Stokely) Date: Sat Dec 13 21:46:13 2008 Subject: Preface need update. In-Reply-To: <20081113185333.25a73ebf.trhodes@FreeBSD.org> References: <1226494693.1809.10.camel@localhost> <491B4F01.9020403@gmail.com> <2a7894eb0811121605k1310bf8avf7a69363fc504905@mail.gmail.com> <20081112200755.66c52a48.trhodes@FreeBSD.org> <491C39E7.7040609@gmail.com> <20081113185333.25a73ebf.trhodes@FreeBSD.org> Message-ID: <2a7894eb0812132146w42722ce5n809cd5d0a9c451eb@mail.gmail.com> Hi Tom, I've just committed a new section to the preface with pointers to the Filesystems and DTrace chapters you committed, and also the Virtualization chapter I committed in 2007. There are others (e.g. updating) but I wasn't sure if some of that content was moved from other chapters (cutting edge?) as if so we'd want to mention that in the preface item for that new chapter. Please take a look when you get a chance and add a few more items to this section about some of the work you've done recently. We presumably also need something about the security event auditing chapter. Thanks, - Murray On Thu, Nov 13, 2008 at 3:53 PM, Tom Rhodes wrote: > On Thu, 13 Nov 2008 16:29:59 +0200 > Manolis Kiagias wrote: > >> Tom Rhodes wrote: >> > On Wed, 12 Nov 2008 16:05:55 -0800 >> > "Murray Stokely" wrote: >> > >> > >> >> Thanks Manolis. Maybe we should add a comment to the Makefile so that >> >> when authors commit new chapters they remember to also update the >> >> preface summary. Or alternatively, we could put some kind of one >> >> sentence chapter description in of each chapter and pull >> >> it out of each file dynamically when building the preface. I'd >> >> probably recommend the low tech first suggestion as good enough. >> >> >> >> - Murray >> >> >> > >> > Yea, because I forget this every time I add a new chapter. :( >> > >> > >> > >> To take this idea one step further, I suggest we add the following >> comment to the Makefile: >> >> ----------------------------------------------------------------------------------------------------------------- >> To add a new chapter to the Handbook: >> >> - Update this Makefile, chapters.ent and book.sgml >> - Add a descriptive entry for the new chapter in preface/preface.sgml >> ----------------------------------------------------------------------------------------------------------------- >> >> Do you think this is good enough? > > Yes. And I need to look at the "changes since the third > edition" data as well. :) > > -- > Tom Rhodes > From ganbold at micom.mng.net Sat Dec 13 21:50:04 2008 From: ganbold at micom.mng.net (Ganbold) Date: Sat Dec 13 21:50:10 2008 Subject: docs/129623: suser(9) claims that the interface is still exported, though deprecated Message-ID: <200812140550.mBE5o3Ya029742@freefall.freebsd.org> The following reply was made to PR docs/129623; it has been noted by GNATS. From: Ganbold To: Ben Kaduk Cc: bug-followup@FreeBSD.org Subject: Re: docs/129623: suser(9) claims that the interface is still exported, though deprecated Date: Sun, 14 Dec 2008 13:01:21 +0800 Ben Kaduk wrote: -- A person forgives only when they are in the wrong. >> Number: 129623 >> Category: docs >> Synopsis: suser(9) claims that the interface is still exported, though deprecated >> Confidential: no >> Severity: non-critical >> Priority: low >> Responsible: freebsd-doc >> State: open >> Quarter: >> Keywords: >> Date-Required: >> Class: doc-bug >> Submitter-Id: current-users >> Arrival-Date: Sun Dec 14 04:50:00 UTC 2008 >> Closed-Date: >> Last-Modified: >> Originator: Ben Kaduk >> Release: 8-current >> Organization: >> > MIT SIPB > >> Environment: >> > pleonasm# uname -a > FreeBSD pleonasm.mit.edu 8.0-CURRENT FreeBSD 8.0-CURRENT #6: Fri Dec 12 18:37:53 UTC 2008 kaduk@pleonasm.mit.edu:/usr/obj/usr/src/sys/PLEONASM i386 > > >> Description: >> > compare the contents of suser(9) and /usr/include/sys/priv.h ... > the latter no longer has the definition of the function. > > It's not clear to me if the man page for suser(9) should just > be removed, or retained as a pointer to priv_check(9). > >> How-To-Repeat: >> > Try to compile a module that uses suser, and get "No such file or directory" when trying to load it. > >> Fix: >> > Remove the suser(9) manpage? > I don't see suser(9) man page in my CURRENT (FreeBSD devil.micom.mng.net 8.0-CURRENT FreeBSD 8.0-CURRENT #13 r185928: Thu Dec 11 21:12:36 ULAT 2008), but I see it in RELENG_7. Are you sure that it is in CURRENT not a leftover from RELENG_X? thanks, Ganbold > >> Release-Note: >> Audit-Trail: >> Unformatted: >> > _______________________________________________ > freebsd-doc@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-doc > To unsubscribe, send any mail to "freebsd-doc-unsubscribe@freebsd.org" > > > > From minimarmot at gmail.com Sun Dec 14 06:20:07 2008 From: minimarmot at gmail.com (Ben Kaduk) Date: Sun Dec 14 06:20:21 2008 Subject: docs/129623: suser(9) claims that the interface is still exported, though deprecated Message-ID: <200812141420.mBEEK6dV062722@freefall.freebsd.org> The following reply was made to PR docs/129623; it has been noted by GNATS. From: "Ben Kaduk" To: Ganbold Cc: bug-followup@freebsd.org Subject: Re: docs/129623: suser(9) claims that the interface is still exported, though deprecated Date: Sun, 14 Dec 2008 08:52:52 -0500 On Sun, Dec 14, 2008 at 12:01 AM, Ganbold wrote: > Ben Kaduk wrote: > -- > A person forgives only when they are in the wrong. >>> Number: 129623 >>> Category: docs >>> Synopsis: suser(9) claims that the interface is still exported, though deprecated >>> Confidential: no >>> Severity: non-critical >>> Priority: low >>> Responsible: freebsd-doc >>> State: open >>> Quarter: >>> Keywords: >>> Date-Required: >>> Class: doc-bug >>> Submitter-Id: current-users >>> Arrival-Date: Sun Dec 14 04:50:00 UTC 2008 >>> Closed-Date: >>> Last-Modified: >>> Originator: Ben Kaduk >>> Release: 8-current >>> Organization: >>> >> MIT SIPB >> >>> Environment: >>> >> pleonasm# uname -a >> FreeBSD pleonasm.mit.edu 8.0-CURRENT FreeBSD 8.0-CURRENT #6: Fri Dec 12 18:37:53 UTC 2008 kaduk@pleonasm.mit.edu:/usr/obj/usr/src/sys/PLEONASM i386 >> >> >>> Description: >>> >> compare the contents of suser(9) and /usr/include/sys/priv.h ... >> the latter no longer has the definition of the function. >> >> It's not clear to me if the man page for suser(9) should just >> be removed, or retained as a pointer to priv_check(9). >> >>> How-To-Repeat: >>> >> Try to compile a module that uses suser, and get "No such file or directory" when trying to load it. >> >>> Fix: >>> >> Remove the suser(9) manpage? >> > > I don't see suser(9) man page in my CURRENT (FreeBSD devil.micom.mng.net > 8.0-CURRENT FreeBSD 8.0-CURRENT #13 r185928: Thu Dec 11 21:12:36 ULAT > 2008), but I see it in RELENG_7. > Are you sure that it is in CURRENT not a leftover from RELENG_X? > > thanks, > Ah, yes, it would be a leftover ... this is an old box. Sorry for the noise. -Ben From linimon at FreeBSD.org Sun Dec 14 11:32:46 2008 From: linimon at FreeBSD.org (linimon@FreeBSD.org) Date: Sun Dec 14 11:32:51 2008 Subject: docs/129623: suser(9) claims that the interface is still exported, though deprecated Message-ID: <200812141932.mBEJWjb7011560@freefall.freebsd.org> Synopsis: suser(9) claims that the interface is still exported, though deprecated State-Changed-From-To: open->closed State-Changed-By: linimon State-Changed-When: Sun Dec 14 19:32:02 UTC 2008 State-Changed-Why: Closed at submitter's request. http://www.freebsd.org/cgi/query-pr.cgi?pr=129623 From trhodes at FreeBSD.org Sun Dec 14 15:51:06 2008 From: trhodes at FreeBSD.org (Tom Rhodes) Date: Sun Dec 14 15:51:12 2008 Subject: Preface need update. In-Reply-To: <2a7894eb0812132146w42722ce5n809cd5d0a9c451eb@mail.gmail.com> References: <1226494693.1809.10.camel@localhost> <491B4F01.9020403@gmail.com> <2a7894eb0811121605k1310bf8avf7a69363fc504905@mail.gmail.com> <20081112200755.66c52a48.trhodes@FreeBSD.org> <491C39E7.7040609@gmail.com> <20081113185333.25a73ebf.trhodes@FreeBSD.org> <2a7894eb0812132146w42722ce5n809cd5d0a9c451eb@mail.gmail.com> Message-ID: <20081214185058.48a7c2c2.trhodes@FreeBSD.org> Hi Murray, On Sat, 13 Dec 2008 21:46:04 -0800 "Murray Stokely" wrote: > Hi Tom, I've just committed a new section to the preface with pointers > to the Filesystems and DTrace chapters you committed, and also the > Virtualization chapter I committed in 2007. There are others (e.g. > updating) but I wasn't sure if some of that content was moved from > other chapters (cutting edge?) as if so we'd want to mention that in > the preface item for that new chapter. Please take a look when you > get a chance and add a few more items to this section about some of > the work you've done recently. > > We presumably also need something about the security event auditing chapter. Thanks for that! I definitely slacked here, but I'll keep this in mind for the future. About the updating chapter, I am unable to find any information on portsnap in my printed copy of the Handbook (third edition). They could have existed (I see a 2006 commit date for freebsd-update in src) but seem to have not been documented in the handbook. Anyway, how does this patch look to you?: diff -u -r1.44 preface.sgml --- preface.sgml 14 Dec 2008 05:42:48 -0000 1.44 +++ preface.sgml 14 Dec 2008 23:45:05 -0000 @@ -47,6 +47,19 @@ + , Updating, has been added to + cover various methods of keeping the system up to date with + the latest in security patches and changes in the Ports + Collection. + + + + , Security Event Auditing, has + been added to cover the new auditing capabilities in &os; + and explain its use. + + + , Virtualization, has been added with information about installing &os; on virtualization software. Thanks, > > Thanks, > > - Murray > > On Thu, Nov 13, 2008 at 3:53 PM, Tom Rhodes wrote: > > On Thu, 13 Nov 2008 16:29:59 +0200 > > Manolis Kiagias wrote: > > > >> Tom Rhodes wrote: > >> > On Wed, 12 Nov 2008 16:05:55 -0800 > >> > "Murray Stokely" wrote: > >> > > >> > > >> >> Thanks Manolis. Maybe we should add a comment to the Makefile so that > >> >> when authors commit new chapters they remember to also update the > >> >> preface summary. Or alternatively, we could put some kind of one > >> >> sentence chapter description in of each chapter and pull > >> >> it out of each file dynamically when building the preface. I'd > >> >> probably recommend the low tech first suggestion as good enough. > >> >> > >> >> - Murray > >> >> > >> > > >> > Yea, because I forget this every time I add a new chapter. :( > >> > > >> > > >> > > >> To take this idea one step further, I suggest we add the following > >> comment to the Makefile: > >> > >> ----------------------------------------------------------------------------------------------------------------- > >> To add a new chapter to the Handbook: > >> > >> - Update this Makefile, chapters.ent and book.sgml > >> - Add a descriptive entry for the new chapter in preface/preface.sgml > >> ----------------------------------------------------------------------------------------------------------------- > >> > >> Do you think this is good enough? > > > > Yes. And I need to look at the "changes since the third > > edition" data as well. :) > > > > -- > > Tom Rhodes > > > -- Tom Rhodes From murray at FreeBSD.org Sun Dec 14 16:32:30 2008 From: murray at FreeBSD.org (murray@FreeBSD.org) Date: Sun Dec 14 16:32:36 2008 Subject: docs/119404: [request] events page should list only last 2 years worth of events, link to archives Message-ID: <200812150032.mBF0WUTg047659@freefall.freebsd.org> Synopsis: [request] events page should list only last 2 years worth of events, link to archives State-Changed-From-To: suspended->closed State-Changed-By: murray State-Changed-When: Mon Dec 15 00:31:29 UTC 2008 State-Changed-Why: I committed this functionality back with r1.15 of www/en/events/Makefile in June of 2008 but forgot to close this PR. http://www.freebsd.org/cgi/query-pr.cgi?pr=119404 From rene at freebsd.org Sun Dec 14 16:43:45 2008 From: rene at freebsd.org (Rene Ladan) Date: Sun Dec 14 16:44:18 2008 Subject: Committer's Guide: fix nits Message-ID: <4945A83B.7020302@freebsd.org> Hi, below is a patch which fixes a lot of tiny nits in the Committer's Guide, based on revision 1.279 + perforce change 154510 (http://perforce.freebsd.org/chv.cgi?CH=154510) Would this be suitable to commit? Thanks, Rene -------- Originele bericht -------- Onderwerp: PERFORCE change 154670 for review Datum: Mon, 15 Dec 2008 00:20:25 GMT Van: Rene Ladan Aan: Perforce Change Reviews http://perforce.freebsd.org/chv.cgi?CH=154670 Change 154670 by rene@rene_self on 2008/12/15 00:20:10 Fix a lot of nits in the Committers Guide, like capitalization, entity usage, language fixes, and some tiny content fixes. Affected files ... .. //depot/projects/docproj_nl/en_US.ISO8859-1/articles/committers-guide/article.sgml#8 edit Differences ... ==== //depot/projects/docproj_nl/en_US.ISO8859-1/articles/committers-guide/article.sgml#8 (text+ko) ==== @@ -9,7 +9,7 @@ - The FreeBSD Documentation Project + The &os; Documentation Project @@ -25,7 +25,8 @@ 2005 2006 2007 - The FreeBSD Documentation Project + 2008 + The &os; Documentation Project @@ -39,18 +40,18 @@ - This document provides information for the FreeBSD committer + This document provides information for the &os; committer community. All new committers should read this document before they start, and existing committers are strongly encouraged to review it from time to time. - Almost all FreeBSD developers have commmit rights to one or + Almost all &os; developers have commmit rights to one or more repositories. However, a few developers do not, and some of the information here applies to them as well. (For instance, some people only have rights to work with the Problem Report database). Please see for more information. - This document may also be of interest to members of the FreeBSD + This document may also be of interest to members of the &os; community who want to learn more about how the project works. @@ -86,7 +87,7 @@ &a.bugmeister; - &a.ceri; &a.linimon;, and &a.remko + &a.ceri; &a.linimon;, and &a.remko; @@ -139,10 +140,10 @@ Commit Bit Types - The FreeBSD CVS repository has a number of components which, + The &os; CVS repository has a number of components which, when combined, support the basic operating system source, documentation, third party application ports infrastructure, and - various maintained utilities. When FreeBSD commit bits are + various maintained utilities. When &os; commit bits are allocated, the areas of the tree where the bit may be used are specified. Generally, the areas associated with a bit reflect who authorized the allocation of the commit bit. Additional areas of @@ -185,9 +186,9 @@ Commit bits allocated prior to the development of the notion of areas of authority may be appropriate for use in many parts of the tree. However, common sense dictates that a committer who has not - previously worked in an area of the tree seek review prior to - committing, seek approval from the appropriate responsible party, - and/or work with a mentor. Since the rules regarding code + previously worked in an area of the tree seeks review prior to + committing, seeks approval from the appropriate responsible party, + and/or works with a mentor. Since the rules regarding code maintenance differ by area of the tree, this is as much for the benefit of the committer working in an area of less familiarity as it is for others working on the tree. @@ -281,7 +282,7 @@ via CVSup for the convenience of our users. Note that the www module containing sources - for the FreeBSD website is + for the &os; website is contained within the doc repository. The CVS repositories are hosted on the repository machines. @@ -382,7 +383,7 @@ linkend="repomeisters">repomeister will copy the file(s) to their new name and/or location and let you know when it is done. The purpose of a repository copy is to preserve file - change history, or logs. We in the FreeBSD Project greatly + change history, or logs. We in the &os; Project greatly value the change history that CVS gives to the project. CVS reference information, tutorials, and FAQs can be found at: @@ -435,7 +436,7 @@ - Practical FreeBSD examples: + Practical &os; examples: @@ -690,7 +691,7 @@ Merging is what happens if you check out a copy of - some source code, modify it, then someone else commits a + some file, modify it, then someone else commits a change, and you run cvs update. CVS notices that you have made local changes, and tries to merge your changes with the changes between the version you originally @@ -750,7 +751,7 @@ You will almost certainly get a conflict because - of the $Id$ (or in FreeBSD's case, + of the $Id$ (or in &os;'s case, $FreeBSD$) lines, so you will have to edit the file to resolve the conflict (remove the marker lines and the second $Id$ line, @@ -1187,7 +1188,7 @@ will have any idea who you are or what you are working on. You do not have to write a comprehensive biography, just write a paragraph or two about who you are and what you plan to be working on as a - developer in FreeBSD. (You should also mention who your mentor + developer in &os;. (You should also mention who your mentor will be). Email this to the &a.developers; and you will be on your way! @@ -1213,7 +1214,7 @@ check in place but that may change. Some people blame these checks for bouncing valid email. If you want these checks turned off for your email you can place a file named - ~/.spam_lover in your home directory + ~/.spam_lover on freefall.FreeBSD.org to disable the checks for your email. @@ -1232,7 +1233,7 @@ All new developers also have a mentor assigned to them for the first few months. Your mentor is responsible for teaching you the rules and conventions of the project and guiding your - first steps in the developer community. He or she is also + first steps in the developer community. Your mentor is also personally responsible for your actions during this initial period. @@ -1339,7 +1340,7 @@ person has made. It can be found on freefall at ~fenner/bin/whodid. If your queries go unanswered or the committer otherwise indicates a lack of - proprietary interest in the area affected, go ahead and commit + interest in the area affected, go ahead and commit it. If you are unsure about a commit for any reason at @@ -1355,7 +1356,7 @@ If they see a different solution to a problem than you, or even a different problem, it is not because they are stupid, because they have questionable parentage, or because they are trying to - destroy your hard work, personal image, or FreeBSD, but simply + destroy your hard work, personal image, or &os;, but simply because they have a different outlook on the world. Different is good. @@ -1379,7 +1380,7 @@ GNATS - The FreeBSD Project utilizes + The &os; Project utilizes GNATS for tracking bugs and change requests. Be sure that if you commit a fix or suggestion found in a GNATS PR, you use @@ -1408,8 +1409,8 @@ - You can run a local copy of GNATS, and then integrate the FreeBSD - GNATS tree in to it using CVSup. Then you can run GNATS commands + You can run a local copy of GNATS, and then integrate the &os; + GNATS tree in to it using CVSup. Then you can run the GNATS commands locally. This lets you query the PR database without needing to be connected to the Internet. @@ -1427,7 +1428,7 @@ gnats release=current prefix=/usr - This will place the FreeBSD GNATS tree in + This will place the &os; GNATS tree in /usr/gnats. You can use a refuse file to control which categories to receive. For example, to only receive docs PRs, @@ -1471,7 +1472,7 @@ # This category is mandatory pending:Category for faulty PRs:gnats-admin: # -# FreeBSD categories +# &os; categories # docs:Documentation Bug:freebsd-doc: @@ -1511,7 +1512,7 @@ Who's Who Besides the repository - meisters, there are other FreeBSD project members and teams whom you will + meisters, there are other &os; project members and teams whom you will probably get to know in your role as a committer. Briefly, and by no means all-inclusively, these are: @@ -1524,7 +1525,7 @@ John is the manager of the SMPng Project, and has authority over the architectural design and implementation of the move to fine-grained kernel threading and locking. - He's also the editor of the SMPng Architecture Document. + He is also the editor of the SMPng Architecture Document. If you are working on fine-grained SMP and locking, please coordinate with John. You can learn more about the SMPng Project on its home page: @@ -1538,7 +1539,7 @@ doceng is the group responsible for the documentation build infrastructure, approving new documentation committers, and - ensuring that the FreeBSD website and documentation on the FTP + ensuring that the &os; website and documentation on the FTP site is up to date with respect to the CVS tree. It is not a conflict resolution body. The vast majority of documentation related discussion takes place on the &a.doc;. More details regarding the doceng team can be found in its charter. Committers @@ -1567,7 +1568,7 @@ When you do a commit that could have been done better, Bruce will be there to tell you. Be thankful that someone is. Bruce is also very knowledgeable on the various - standards applicable to FreeBSD. + standards applicable to &os;. @@ -1603,7 +1604,7 @@ Colin is the - FreeBSD Security + &os; Security Officer and oversees the &a.security-officer;. @@ -1618,7 +1619,7 @@ are not sure of some potential change to the networking subsystem you have in mind, Garrett is someone to talk to. Garrett is also very knowledgeable on the various - standards applicable to FreeBSD. + standards applicable to &os;. @@ -1643,12 +1644,12 @@ voting, announcements, etc. The &a.developers; is for the exclusive use of - FreeBSD committers. In order to develop FreeBSD, committers must + &os; committers. In order to develop &os;, committers must have the ability to openly discuss matters that will be resolved before they are publicly announced. Frank discussions of work in - progress are not suitable for open publication and may harm FreeBSD. + progress are not suitable for open publication and may harm &os;. - All FreeBSD committers are reminded to obey the copyright of the + All &os; committers are reminded to obey the copyright of the original author(s) of &a.developers; mail. Do not publish or forward messages from the &a.developers; outside the list membership without permission of all of the authors. @@ -1661,12 +1662,12 @@ This list is not intended as a place for code reviews or a replacement for the &a.arch; or the &a.audit;. In fact - using it as such hurts the FreeBSD Project as it gives a sense of a - closed list where general decisions affecting all of the FreeBSD + using it as such hurts the &os; Project as it gives a sense of a + closed list where general decisions affecting all of the &os; using community are made without being open. Last, but not least never, never ever, email - the &a.developers; and CC:/BCC: another FreeBSD list. - Never, ever email another FreeBSD email list and CC:/BCC: + the &a.developers; and CC:/BCC: another &os; list. + Never, ever email another &os; email list and CC:/BCC: the &a.developers;. Doing so can greatly diminish the benefits of this list. @@ -1679,7 +1680,7 @@ - If you do not wish to type your password in every + If you do not wish to type in your password every time you use &man.ssh.1;, and you use RSA or DSA keys to authenticate, &man.ssh-agent.1; is there for your convenience. If you want to use &man.ssh-agent.1;, make @@ -1702,7 +1703,7 @@ ($HOME/.ssh/id_dsa.pub or $HOME/.ssh/id_rsa.pub) to the person setting you up as a committer so it can be put - into yourlogin file in + into yourlogin in /etc/ssh-keys/ on freefall. @@ -1789,7 +1790,7 @@ - The FreeBSD Committers' Big List of Rules + The &os; Committers' Big List of Rules @@ -1858,7 +1859,7 @@ Do not commit to anything under the src/contrib, - src/crypto, and + src/crypto, or src/sys/contrib trees without explicit approval from the respective maintainer(s). @@ -1997,7 +1998,7 @@ Respect existing maintainers if listed. - Many parts of FreeBSD are not owned in + Many parts of &os; are not owned in the sense that any specific individual will jump up and yell if you commit a change to their area, but it still pays to check first. One convention we use @@ -2016,8 +2017,8 @@ question and see if someone has been working recently or predominantly in that area. - Other areas of FreeBSD fall under the control of - someone who manages an overall category of FreeBSD + Other areas of &os; fall under the control of + someone who manages an overall category of &os; evolution, such as internationalization or networking. See @@ -2111,7 +2112,7 @@ flame-o-gram at least had the grace to send it privately, then have the grace to keep it private yourself. If you feel you are being unfairly treated by another developer, - and it is causing you anguish, bring the matter up with + and it is causing you anguish, bring up the matter with core rather than taking it public. Core will do its best to play peace makers and get things back to sanity. In cases where the dispute involves a change to the codebase and @@ -2134,7 +2135,7 @@ and committing 10 megabytes worth of accumulated stuff. People who abuse this on a regular basis will have their commit privileges suspended until they get back from the - FreeBSD Happy Reeducation Camp we run in Greenland. + &os; Happy Reeducation Camp we run in Greenland. @@ -2167,9 +2168,9 @@ running that code. If you have a change which also may break another architecture, be sure and test on all supported architectures. Please refer to the FreeBSD Internal + url="http://www.FreeBSD.org/internal/">&os; Internal Page for a list of available resources. As other - architectures are added to the FreeBSD supported platforms + architectures are added to the &os; supported platforms list, the appropriate shared testing resources will be made available. @@ -2194,7 +2195,7 @@ Please note that this does not mean you should not try to improve the software in question; you are still more than welcome to do so. Ideally, you should submit your patches to - the vendor. If your changes are FreeBSD-specific, talk to the + the vendor. If your changes are &os;-specific, talk to the maintainer; they may be willing to apply them locally. But whatever you do, do not commit there by yourself! @@ -2208,9 +2209,9 @@ Policy on Multiple Architectures - FreeBSD has added several new arch ports during recent + &os; has added several new architecture ports during recent release cycles and is truly no longer an &i386; centric operating - system. In an effort to make it easier to keep FreeBSD portable + system. In an effort to make it easier to keep &os; portable across the platforms we support, core has developed the following mandate: @@ -2223,7 +2224,7 @@ to the source tree. - The i386 and Sparc64 platforms were chosen due to being more + The Sparc64 and i386 platforms were chosen due to being more readily available to developers and as representatives of more diverse processor and system designs - big vs little endian, register file vs register stack, different DMA and cache @@ -2306,39 +2307,39 @@ Support for Multiple Architectures - FreeBSD is a highly portable operating system intended to + &os; is a highly portable operating system intended to function on many different types of hardware architectures. Maintaining clean separation of Machine Dependent (MD) and Machine Independent (MI) code, as well as minimizing MD code, is an important part of our strategy to remain agile with regards to current hardware trends. Each new hardware architecture supported by - FreeBSD adds substantially to the cost of code maintenance, + &os; adds substantially to the cost of code maintenance, toolchain support, and release engineering. It also dramatically increases the cost of effective testing of kernel changes. As such, there is strong motivation to differentiate between classes of support for various architectures while remaining strong in a few - key architectures that are seen as the FreeBSD "target audience". + key architectures that are seen as the &os; "target audience". Statement of General Intent - The FreeBSD Project targets "production quality commercial + The &os; Project targets "production quality commercial off-the-shelf (COTS) workstation, server, and high-end embedded systems". By retaining a focus on a narrow set of architectures - of interest in these environments, the FreeBSD Project is able + of interest in these environments, the &os; Project is able to maintain high levels of quality, stability, and performance, as well as minimize the load on various support teams on the project, such as the ports team, documentation team, security officer, and release engineering teams. Diversity in - hardware support broadens the options for FreeBSD consumers by + hardware support broadens the options for &os; consumers by offering new features and usage opportunities (such as support - for 64-bit CPUs, use in embedded environments, etc.), but these + for 64 bit CPUs, use in embedded environments, etc.), but these benefits must always be carefully considered in terms of the real-world maintenance cost associated with additional platform support. - The FreeBSD Project differentiates platform targets into + The &os; Project differentiates platform targets into four tiers. Each tier includes a specification of the requirements for an architecture to be in that tier, as well as specifying the obligations of developers with @@ -2357,13 +2358,13 @@ (features which are inherently architecture-specific, such as support for hardware device drivers, may be exempt from this requirement). In general, all Tier 1 platforms must have build - and tinderbox support either in the FreeBSD.org cluster, or + and Tinderbox support either in the FreeBSD.org cluster, or be easily available for all developers. Embedded platforms may - substitute an emulator available in the FreeBSD cluster for + substitute an emulator available in the &os; cluster for actual hardware. Tier 1 architectures are expected to be Production Quality - with respects to all aspects of the FreeBSD operating system, + with respects to all aspects of the &os; operating system, including installation and development environments. Tier 1 architectures are expected to be completely @@ -2377,12 +2378,12 @@ platform, or have the appropriate filters to prevent the inappropriate ones from building there. The packaging system must support all Tier 1 architectures. To ensure an - architectures Tier 1 status, proponents of that architecture + architecture's Tier 1 status, proponents of that architecture must show that all relevant packages can be built on that platform. Tier 1 embedded architectures must be able to cross-build - packages on at least one other tier 1 architecture. The + packages on at least one other Tier 1 architecture. The packages must be the most relevant for the platform, but may be a non-empty subset of those that build natively. @@ -2403,19 +2404,19 @@ maintainer is expected to work with the platform maintainers to refine these changes. Major new toolchain components are allowed to break support for Tier 2 architectures if the - FreeBSD-local changes haven't been incorporated upstream. The + &os;-local changes have not been incorporated upstream. The toolchain maintainers are expected to provide prompt review of any proposed changes and cannot block, through their inaction, - changes going into the tree. New features added to FreeBSD + changes going into the tree. New features added to &os; should be feasible to implement on these platforms, but an implementation is not required before the feature may be added - to the FreeBSD source tree. New features that may be difficult + to the &os; source tree. New features that may be difficult to implement on Tier 2 architectures should provide a means of disabling them on those architectures. The implementation of - a Tier 2 architecture may be committed to the main FreeBSD + a Tier 2 architecture may be committed to the main &os; tree as long as it does not interfere with production work on Tier 1 platforms, or substantially with other Tier 2 platforms. - Before a Tier 2 platform can be added to the FreeBSD base + Before a Tier 2 platform can be added to the &os; base source tree, the platform must be able to boot multi-user on actual hardware. Generally, there must be at least three active developers working on the platform. @@ -2425,22 +2426,22 @@ reaching end of life may also be moved from Tier 1 status to Tier 2 status as the availability of resources to continue to maintain the system in a Production Quality state diminishes. Well supported - niche architectures may also be tier 2. + niche architectures may also be Tier 2. Tier 2 architectures may have some support for them integrated into the ports infrastructure. They may have cross compilation support added, at the discretion of portmgr. Some - ports must built natively, into packages if the package system + ports must built natively into packages if the package system supports that architecture. If not integrated into the base system, some external patches for the architecture for ports must be available. - Tier 2 architectures can be integrated into the FreeBSD + Tier 2 architectures can be integrated into the &os; handbook. The basics for how to get a system running must be documented, although not necessarily for every single board or - system a tier 2 architecture supports. The supported hardware + system a Tier 2 architecture supports. The supported hardware list must exist and should be no more than a couple of months - old. It should be integrated into the FreeBSD + old. It should be integrated into the &os; documentation. Current Tier 2 platforms are ARM, PowerPC, ia64, Sparc64 and @@ -2456,13 +2457,13 @@ Tier 3 platforms are architectures in the early stages of development, for non-mainstream hardware platforms, or which are considered legacy systems unlikely to see broad future - use. New tier 3 systems will not be committed to the base + use. New Tier 3 systems will not be committed to the base source tree. Support for Tier 3 systems may be worked on in - the FreeBSD Perforce Repository, providing source control and - easier change integration from the main FreeBSD tree. + the &os; Perforce Repository, providing source control and + easier change integration from the main &os; tree. Platforms that transition to Tier 3 status may be removed from the tree if they are no longer actively supported by the - FreeBSD developer community at the discretion of the release + &os; developer community at the discretion of the release engineer. Tier 3 platforms may have ports support, either integrated @@ -2471,7 +2472,7 @@ Tier 3 platforms must have the basics documented for how to build a kernel and how to boot it on at least one target hardware or emulation environment. This documentation need - not be integrated into the FreeBSD tree. + not be integrated into the &os; tree. Current Tier 3 platforms are MIPS and &s390;. @@ -2490,7 +2491,7 @@ Policy on Changing the Tier of an Architecture Systems may only be moved from one tier to another by - approval of the FreeBSD Core Team, which shall make that + approval of the &os; Core Team, which shall make that decision in collaboration with the Security Officer, Release Engineering, and toolchain maintenance teams. @@ -2555,10 +2556,10 @@ make sure you have fixed the simple ones. If the port came from a submitter who has not - contributed to the project before, add that person's + contributed to the Project before, add that person's name to the Additional - Contributors section of the FreeBSD Contributors + Contributors section of the &os; Contributors List. Close the PR if the port came in as a PR. To close @@ -3232,7 +3233,7 @@ Issues Specific To Developers Who Are Not Committers - A few people who have access to the FreeBSD machines do not + A few people who have access to the &os; machines do not have commit bits. For instance, the project is willing to give access to the GNATS database to contributors who have shown interest and dedication in working on Problem Reports. @@ -3276,7 +3277,7 @@ - The FreeBSD Committers' Big List of Rules + The &os; Committers' Big List of Rules @@ -3392,7 +3393,7 @@ well. This information consists of one or more lines containing the - key word or phrase, a colon, tabs for formatting, and then the + key word or phrase, a colon, tabs and/or spaces for formatting, and then the additional information. The key words or phrases are: @@ -3410,14 +3411,14 @@ Submitted by: The name and e-mail address of the person that submitted the fix; for committers, just the username on - the FreeBSD cluster. + the &os; cluster. Reviewed by: The name and e-mail address of the person or people that reviewed the change; for committers, just the - username on the FreeBSD cluster. If a patch was + username on the &os; cluster. If a patch was submitted to a mailing list for review, and the review was favorable, then just include the list name. @@ -3426,7 +3427,7 @@ Approved by: The name and e-mail address of the person or people that approved the change; for committers, just the - username on the FreeBSD cluster. It is customary to get + username on the &os; cluster. It is customary to get prior approval for a commit if it is to an area of the tree to which you do not usually commit. In addition, during the run up to a new release all commits @@ -3586,7 +3587,7 @@ The mailing lists are archived under /g/mail which will show up as /hub/g/mail with &man.pwd.1;. - This location is accessible from any machine on the FreeBSD cluster. + This location is accessible from any machine on the &os; cluster. -- http://www.rene-ladan.nl/ GPG fingerprint = ADBC ECCD EB5F A6B4 549F 600D 8C9E 647A E564 2BFC (subkeys.pgp.net) From murray at FreeBSD.org Sun Dec 14 16:52:37 2008 From: murray at FreeBSD.org (murray@FreeBSD.org) Date: Sun Dec 14 16:52:44 2008 Subject: docs/128325: README.snapshots still refers to snaphots as "alpha-test" code Message-ID: <200812150052.mBF0qa0M063074@freefall.freebsd.org> Synopsis: README.snapshots still refers to snaphots as "alpha-test" code Responsible-Changed-From-To: freebsd-doc->mckusick Responsible-Changed-By: murray Responsible-Changed-When: Mon Dec 15 00:51:55 UTC 2008 Responsible-Changed-Why: Kirk, can you take a look at this readme and suggest some new text about snapshots? Things have progressed quite a bit since 2000 I am sure. http://www.freebsd.org/cgi/query-pr.cgi?pr=128325 From murray at FreeBSD.org Sun Dec 14 16:55:10 2008 From: murray at FreeBSD.org (murray@FreeBSD.org) Date: Sun Dec 14 16:55:16 2008 Subject: docs/128768: Missing documentation about tmpfs mount options Message-ID: <200812150055.mBF0tARQ063312@freefall.freebsd.org> Synopsis: Missing documentation about tmpfs mount options Responsible-Changed-From-To: freebsd-doc->delphij Responsible-Changed-By: murray Responsible-Changed-When: Mon Dec 15 00:54:41 UTC 2008 Responsible-Changed-Why: Xin LI wrote the tmpfs man page. Can you take a look at this PR about the appropriate section and mount options? http://www.freebsd.org/cgi/query-pr.cgi?pr=128768 From murray at FreeBSD.org Sun Dec 14 17:05:11 2008 From: murray at FreeBSD.org (murray@FreeBSD.org) Date: Sun Dec 14 17:05:21 2008 Subject: docs/129263: Obsolete info on collecting a crash dump prior to "dumpon" Message-ID: <200812150105.mBF15BFN070665@freefall.freebsd.org> Synopsis: Obsolete info on collecting a crash dump prior to "dumpon" State-Changed-From-To: open->closed State-Changed-By: murray State-Changed-When: Mon Dec 15 01:04:17 UTC 2008 State-Changed-Why: This obsolete note has been removed from the chapter. Thanks for the submission. The website will be updated within 6 hours to reflect this change. http://www.freebsd.org/cgi/query-pr.cgi?pr=129263 From dfilter at FreeBSD.ORG Sun Dec 14 17:10:08 2008 From: dfilter at FreeBSD.ORG (dfilter service) Date: Sun Dec 14 17:10:14 2008 Subject: docs/129263: commit references a PR Message-ID: <200812150110.mBF1A7R7070957@freefall.freebsd.org> The following reply was made to PR docs/129263; it has been noted by GNATS. From: dfilter@FreeBSD.ORG (dfilter service) To: bug-followup@FreeBSD.org Cc: Subject: Re: docs/129263: commit references a PR Date: Mon, 15 Dec 2008 01:04:16 +0000 (UTC) murray 2008-12-15 01:04:07 UTC FreeBSD doc repository Modified files: en_US.ISO8859-1/books/developers-handbook/kerneldebug chapter.sgml Log: The config dump syntax for hard-coding the dump location before dumpon(8) can be executed has been deprecated since FreeBSD 4.x and no longer works. Use the loader instead. PR: docs/129263 Revision Changes Path 1.78 +0 -5 doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug/chapter.sgml _______________________________________________ cvs-all@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/cvs-all To unsubscribe, send any mail to "cvs-all-unsubscribe@freebsd.org" From murray.stokely at gmail.com Sun Dec 14 17:20:05 2008 From: murray.stokely at gmail.com (Murray Stokely) Date: Sun Dec 14 17:20:11 2008 Subject: docs/128356: [request] add Firefox plugin for FreeBSD manual pages Message-ID: <200812150120.mBF1K4Qh079450@freefall.freebsd.org> The following reply was made to PR docs/128356; it has been noted by GNATS. From: "Murray Stokely" To: bug-followup@freebsd.org, alexander.pohoyda@gmx.net Cc: Subject: Re: docs/128356: [request] add Firefox plugin for FreeBSD manual pages Date: Sun, 14 Dec 2008 17:10:39 -0800 I like this, and I think it would make sense to host something like this somewhere on freebsd.org, but I'm not sure this is the best solution. This provides me with a dropdown freebsd icon on the search box in my Firefox browser. I expect to be able to type search terms that match single-line fields of open PRs in such a field, but instead it only works if I enter the exact PR number of something I am looking for. I don't think that is what people would expect from a search bar. Can you update the patch to search single-line fields of open PRs instead? - Murray From murray at FreeBSD.org Sun Dec 14 17:26:54 2008 From: murray at FreeBSD.org (murray@FreeBSD.org) Date: Sun Dec 14 17:26:59 2008 Subject: docs/128129: Sysinstall color problem in xterm Message-ID: <200812150126.mBF1Qr4H086919@freefall.freebsd.org> Synopsis: Sysinstall color problem in xterm State-Changed-From-To: open->closed State-Changed-By: murray State-Changed-When: Mon Dec 15 01:26:03 UTC 2008 State-Changed-Why: I've added a Q/A entry to the troubleshooting section about this. Thanks for the submission. The website may take up to 6 hours before it reflects this change. Responsible-Changed-From-To: freebsd-doc->murray Responsible-Changed-By: murray Responsible-Changed-When: Mon Dec 15 01:26:03 UTC 2008 Responsible-Changed-Why: I've added a Q/A entry to the troubleshooting section about this. Thanks for the submission. The website may take up to 6 hours before it reflects this change. http://www.freebsd.org/cgi/query-pr.cgi?pr=128129 From murray at FreeBSD.org Sun Dec 14 17:28:41 2008 From: murray at FreeBSD.org (murray@FreeBSD.org) Date: Sun Dec 14 17:28:47 2008 Subject: docs/127923: Please mention qemu in the FreeBSD Handbook Message-ID: <200812150128.mBF1Sehd094548@freefall.freebsd.org> Synopsis: Please mention qemu in the FreeBSD Handbook Responsible-Changed-From-To: freebsd-doc->loader Responsible-Changed-By: murray Responsible-Changed-When: Mon Dec 15 01:28:02 UTC 2008 Responsible-Changed-Why: Loader, didn't you have some patchecs to add qemu here? Can you add something about it to the virtualization chapter? http://www.freebsd.org/cgi/query-pr.cgi?pr=127923 From murray at FreeBSD.org Sun Dec 14 17:50:50 2008 From: murray at FreeBSD.org (murray@FreeBSD.org) Date: Sun Dec 14 17:50:56 2008 Subject: docs/128128: Sysinstall not mentioned in 4.4 "Using the Packages System" Message-ID: <200812150150.mBF1onJL021871@freefall.freebsd.org> Synopsis: Sysinstall not mentioned in 4.4 "Using the Packages System" State-Changed-From-To: open->closed State-Changed-By: murray State-Changed-When: Mon Dec 15 01:49:59 UTC 2008 State-Changed-Why: I've just submitted an introduction to this section which also mentions sysinstall and links to the post installation section of chapter 2. Thanks for the submission. The website may take up to 6 hours before it reflects this change. Responsible-Changed-From-To: freebsd-doc->murray Responsible-Changed-By: murray Responsible-Changed-When: Mon Dec 15 01:49:59 UTC 2008 Responsible-Changed-Why: I've just submitted an introduction to this section which also mentions sysinstall and links to the post installation section of chapter 2. Thanks for the submission. The website may take up to 6 hours before it reflects this change. http://www.freebsd.org/cgi/query-pr.cgi?pr=128128 From murray at FreeBSD.org Sun Dec 14 17:55:32 2008 From: murray at FreeBSD.org (murray@FreeBSD.org) Date: Sun Dec 14 17:55:39 2008 Subject: docs/127406: [patch] update umodem man page: Sony Ericsson W810i Message-ID: <200812150155.mBF1tWUf035158@freefall.freebsd.org> Synopsis: [patch] update umodem man page: Sony Ericsson W810i State-Changed-From-To: open->patched State-Changed-By: murray State-Changed-When: Mon Dec 15 01:55:00 UTC 2008 State-Changed-Why: Nick already submitted this to HEAD, this is his MFC reminder. Responsible-Changed-From-To: freebsd-doc->n_hibma Responsible-Changed-By: murray Responsible-Changed-When: Mon Dec 15 01:55:00 UTC 2008 Responsible-Changed-Why: Nick already submitted this to HEAD, this is his MFC reminder. http://www.freebsd.org/cgi/query-pr.cgi?pr=127406 From murray at FreeBSD.org Sun Dec 14 17:58:11 2008 From: murray at FreeBSD.org (murray@FreeBSD.org) Date: Sun Dec 14 17:58:17 2008 Subject: docs/122470: [patch] exit status on fetch(1) manual page Message-ID: <200812150158.mBF1wBxl035367@freefall.freebsd.org> Synopsis: [patch] exit status on fetch(1) manual page Responsible-Changed-From-To: freebsd-doc->murray Responsible-Changed-By: murray Responsible-Changed-When: Mon Dec 15 01:57:39 UTC 2008 Responsible-Changed-Why: I have an outstanding patch to fetch out for review. I will make this change in a follow up submit. http://www.freebsd.org/cgi/query-pr.cgi?pr=122470 From murray at stokely.org Sun Dec 14 18:32:09 2008 From: murray at stokely.org (Murray Stokely) Date: Sun Dec 14 18:32:16 2008 Subject: Preface need update. In-Reply-To: <20081214185058.48a7c2c2.trhodes@FreeBSD.org> References: <1226494693.1809.10.camel@localhost> <491B4F01.9020403@gmail.com> <2a7894eb0811121605k1310bf8avf7a69363fc504905@mail.gmail.com> <20081112200755.66c52a48.trhodes@FreeBSD.org> <491C39E7.7040609@gmail.com> <20081113185333.25a73ebf.trhodes@FreeBSD.org> <2a7894eb0812132146w42722ce5n809cd5d0a9c451eb@mail.gmail.com> <20081214185058.48a7c2c2.trhodes@FreeBSD.org> Message-ID: <2a7894eb0812141832u20af4821h121a520fab746c7c@mail.gmail.com> On Sun, Dec 14, 2008 at 3:50 PM, Tom Rhodes wrote: > Thanks for that! I definitely slacked here, but I'll keep this > in mind for the future. About the updating chapter, I am unable > to find any information on portsnap in my printed copy of the > Handbook (third edition). They could have existed (I see a > 2006 commit date for freebsd-update in src) but seem to have > not been documented in the handbook. Ahh, I see, nothing was moved over from the Cutting Edge chapter. This chapter has just about the exact same purpose as the new Updating chapter, they just describe different tools. The first chapter Updating, even references the latter chapter (Cutting Edge) as a pre-requisite in the synopsis by saying one needs to read it to learn about Mergemaster. There should only be one updating chapter. Cutting Edge was there first, but updating is maybe a better name. How do you feel about merging them back into one chapter? > Anyway, how does this patch look to you?: Everything else looks good, except I don't like that we now have two chapters for updating instead of one. I wasn't paying attention when that happened. =) Maybe just submit the new item for auditing while we sort out what to do about updating? - Murray From murray.stokely at gmail.com Sun Dec 14 20:00:12 2008 From: murray.stokely at gmail.com (Murray Stokely) Date: Sun Dec 14 20:00:19 2008 Subject: docs/102148: The description of which Intel chips have EM64T is out of date Message-ID: <200812150400.mBF40Ba5029326@freefall.freebsd.org> The following reply was made to PR docs/102148; it has been noted by GNATS. From: "Murray Stokely" To: bug-followup@freebsd.org, mwm@mired.org Cc: Subject: Re: docs/102148: The description of which Intel chips have EM64T is out of date Date: Sun, 14 Dec 2008 19:51:36 -0800 After 2 years the description is even more out of date. Here is a proposed patch : http://people.freebsd.org/~murray/patches/hardware-amd64.diff - Murray From no-reply at tradeandstock.it Mon Dec 15 02:30:36 2008 From: no-reply at tradeandstock.it (1click1stock) Date: Mon Dec 15 02:30:43 2008 Subject: Comunicato Sampa 1clik1stok Message-ID: <984620743361995473@lorenzo> Se non riesc visualizzarlo con un browser [1]www.1click1stoc [2]3D1click1 [xma=] Alcune delle nostre offerte per i tuoi re [3]3D"Nautica [4]3D"Brail [5]3D"Sector [6]3D"Entra < Ti preghiam presa in considera utente registrato 1click1 sito e clicca su "[7]Contattaci". Se dati person References 1. 3D"http://www.1click1stock.it/newsletter/2008_1 2. 3D"http://1click1stock.com/" 3. 3D"http://www.1click1stock.it/products/43/nautica-challenge-a235 4. 3D"http://www.1click1stock.it/products/80/breil-griffe-el 5. 3D"http://www.1click1stock.it/products/83/sec 6. 3D"http://1click1stock.com/" 7. 3D"http: 8. 3D"http://www.1click1stock.it/priva From bugmaster at FreeBSD.org Mon Dec 15 03:06:05 2008 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Dec 15 03:06:36 2008 Subject: Current unassigned doc problem reports Message-ID: <200812151106.mBFB65Ye003336@freefall.freebsd.org> (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/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/128356 doc [request] add Firefox plugin for FreeBSD manual pages o docs/128222 doc [patch] man page truss(1) claims that init(8) can be t 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/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/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/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) 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 172 problems total. From trhodes at FreeBSD.org Mon Dec 15 03:29:06 2008 From: trhodes at FreeBSD.org (Tom Rhodes) Date: Mon Dec 15 03:29:18 2008 Subject: Preface need update. In-Reply-To: <2a7894eb0812141832u20af4821h121a520fab746c7c@mail.gmail.com> References: <1226494693.1809.10.camel@localhost> <491B4F01.9020403@gmail.com> <2a7894eb0811121605k1310bf8avf7a69363fc504905@mail.gmail.com> <20081112200755.66c52a48.trhodes@FreeBSD.org> <491C39E7.7040609@gmail.com> <20081113185333.25a73ebf.trhodes@FreeBSD.org> <2a7894eb0812132146w42722ce5n809cd5d0a9c451eb@mail.gmail.com> <20081214185058.48a7c2c2.trhodes@FreeBSD.org> <2a7894eb0812141832u20af4821h121a520fab746c7c@mail.gmail.com> Message-ID: <20081215062858.6c76fb33.trhodes@FreeBSD.org> On Sun, 14 Dec 2008 18:32:07 -0800 "Murray Stokely" wrote: > On Sun, Dec 14, 2008 at 3:50 PM, Tom Rhodes wrote: > > Thanks for that! I definitely slacked here, but I'll keep this > > in mind for the future. About the updating chapter, I am unable > > to find any information on portsnap in my printed copy of the > > Handbook (third edition). They could have existed (I see a > > 2006 commit date for freebsd-update in src) but seem to have > > not been documented in the handbook. > > Ahh, I see, nothing was moved over from the Cutting Edge chapter. > > This chapter has just about the exact same purpose as the new Updating > chapter, they just describe different tools. The first chapter > Updating, even references the latter chapter (Cutting Edge) as a > pre-requisite in the synopsis by saying one needs to read it to learn > about Mergemaster. > > There should only be one updating chapter. Cutting Edge was there > first, but updating is maybe a better name. > > How do you feel about merging them back into one chapter? > > > Anyway, how does this patch look to you?: > > Everything else looks good, except I don't like that we now have two > chapters for updating instead of one. I wasn't paying attention when > that happened. =) Maybe just submit the new item for auditing while > we sort out what to do about updating? > > - Murray > Works for me. Let me work over a patch today (I should have enough time) and get it out. :) -- Tom Rhodes From loader at freebsdmall.com Mon Dec 15 05:03:04 2008 From: loader at freebsdmall.com (loader) Date: Mon Dec 15 05:03:11 2008 Subject: docs/127923: Please mention qemu in the FreeBSD Handbook In-Reply-To: <200812150128.mBF1Sehd094548@freefall.freebsd.org> (murray@freebsd.org's message of "Mon\, 15 Dec 2008 01\:28\:40 GMT") References: <200812150128.mBF1Sehd094548@freefall.freebsd.org> Message-ID: <20081215130236.B5E051D703EF@mail.freebsdmall.com> murray@FreeBSD.org wrote: > Synopsis: Please mention qemu in the FreeBSD Handbook > > Responsible-Changed-From-To: freebsd-doc->loader > Responsible-Changed-By: murray > Responsible-Changed-When: Mon Dec 15 01:28:02 UTC 2008 > Responsible-Changed-Why: > Loader, didn't you have some patchecs to add qemu here? Can you add > something about it to the virtualization chapter? > > > http://www.freebsd.org/cgi/query-pr.cgi?pr=127923 Okay, I will try to add a section about Qemu these days. Regards, loader From trhodes at FreeBSD.org Mon Dec 15 06:36:15 2008 From: trhodes at FreeBSD.org (Tom Rhodes) Date: Mon Dec 15 06:36:21 2008 Subject: Committer's Guide: fix nits In-Reply-To: <4945A83B.7020302@freebsd.org> References: <4945A83B.7020302@freebsd.org> Message-ID: <20081215093607.71a509f8.trhodes@FreeBSD.org> On Mon, 15 Dec 2008 01:43:39 +0100 Rene Ladan wrote: > Hi, > > below is a patch which fixes a lot of tiny nits in the Committer's Guide, > based on revision 1.279 + perforce change 154510 (http://perforce.freebsd.org/chv.cgi?CH=154510) > > Would this be suitable to commit? You may want to investigate, but I believe Ceri has run out of available time for FreeBSD. So he may not be part of the bugmeister team any longer. Also, I agree with a lot of the wording changes, in the future though, can simple FreeBSD->&os; changes be done outside of wording changes? I know it's still whitespace, but those changes need no real review beyond your normal second glance, and make diffs longer to read. :) Thanks, -- Tom Rhodes From trhodes at FreeBSD.org Mon Dec 15 10:49:27 2008 From: trhodes at FreeBSD.org (Tom Rhodes) Date: Mon Dec 15 10:49:33 2008 Subject: Preface need update. In-Reply-To: <20081215062858.6c76fb33.trhodes@FreeBSD.org> References: <1226494693.1809.10.camel@localhost> <491B4F01.9020403@gmail.com> <2a7894eb0811121605k1310bf8avf7a69363fc504905@mail.gmail.com> <20081112200755.66c52a48.trhodes@FreeBSD.org> <491C39E7.7040609@gmail.com> <20081113185333.25a73ebf.trhodes@FreeBSD.org> <2a7894eb0812132146w42722ce5n809cd5d0a9c451eb@mail.gmail.com> <20081214185058.48a7c2c2.trhodes@FreeBSD.org> <2a7894eb0812141832u20af4821h121a520fab746c7c@mail.gmail.com> <20081215062858.6c76fb33.trhodes@FreeBSD.org> Message-ID: <20081215134919.51a88d90.trhodes@FreeBSD.org> On Mon, 15 Dec 2008 06:28:58 -0500 Tom Rhodes wrote: > On Sun, 14 Dec 2008 18:32:07 -0800 > "Murray Stokely" wrote: > > > On Sun, Dec 14, 2008 at 3:50 PM, Tom Rhodes wrote: > > > Thanks for that! I definitely slacked here, but I'll keep this > > > in mind for the future. About the updating chapter, I am unable > > > to find any information on portsnap in my printed copy of the > > > Handbook (third edition). They could have existed (I see a > > > 2006 commit date for freebsd-update in src) but seem to have > > > not been documented in the handbook. > > > > Ahh, I see, nothing was moved over from the Cutting Edge chapter. > > > > This chapter has just about the exact same purpose as the new Updating > > chapter, they just describe different tools. The first chapter > > Updating, even references the latter chapter (Cutting Edge) as a > > pre-requisite in the synopsis by saying one needs to read it to learn > > about Mergemaster. > > > > There should only be one updating chapter. Cutting Edge was there > > first, but updating is maybe a better name. > > > > How do you feel about merging them back into one chapter? > > > > > Anyway, how does this patch look to you?: > > > > Everything else looks good, except I don't like that we now have two > > chapters for updating instead of one. I wasn't paying attention when > > that happened. =) Maybe just submit the new item for auditing while > > we sort out what to do about updating? > > > > - Murray > > > > Works for me. Let me work over a patch today (I should have > enough time) and get it out. :) This patch merges both chapters in a way I thought worked out best. Could probably use a bit of text in the intro but I'm not 100% sure. http://people.freebsd.org/~trhodes/patches/cutting-edge.diff Though I do remember why I started another chapter though, primarily because cutting-edge came off to me as "using CURRENT and/or test versions" rather than stable with bug fixes. :) Thanks, -- Tom Rhodes From sonic2000gr at gmail.com Mon Dec 15 11:07:09 2008 From: sonic2000gr at gmail.com (Manolis Kiagias) Date: Mon Dec 15 11:07:16 2008 Subject: Preface need update. In-Reply-To: <20081215134919.51a88d90.trhodes@FreeBSD.org> References: <1226494693.1809.10.camel@localhost> <491B4F01.9020403@gmail.com> <2a7894eb0811121605k1310bf8avf7a69363fc504905@mail.gmail.com> <20081112200755.66c52a48.trhodes@FreeBSD.org> <491C39E7.7040609@gmail.com> <20081113185333.25a73ebf.trhodes@FreeBSD.org> <2a7894eb0812132146w42722ce5n809cd5d0a9c451eb@mail.gmail.com> <20081214185058.48a7c2c2.trhodes@FreeBSD.org> <2a7894eb0812141832u20af4821h121a520fab746c7c@mail.gmail.com> <20081215062858.6c76fb33.trhodes@FreeBSD.org> <20081215134919.51a88d90.trhodes@FreeBSD.org> Message-ID: <4946AAD6.6050300@gmail.com> Tom Rhodes wrote: >> >> Works for me. Let me work over a patch today (I should have >> enough time) and get it out. :) >> > > This patch merges both chapters in a way I thought worked out > best. Could probably use a bit of text in the intro but I'm > not 100% sure. > > http://people.freebsd.org/~trhodes/patches/cutting-edge.diff > > Though I do remember why I started another chapter though, > primarily because cutting-edge came off to me as "using CURRENT > and/or test versions" rather than stable with bug fixes. :) > > Thanks, > > If these chapters are merged, I think we will have to rethink the "The Cutting Edge" title. The title is by itself intimidating for the beginning-intermediate user who is already convinced it is best for him to use "RELEASE" until he is comfortable with the system. And using freebsd-update is essential (and a rather easy task) at any user level. How about changing the chapter to something like "Updating and Upgrading FreeBSD"? The first sections could deal with security updates and minor / major version upgrades using freebsd-update. Later sections could deal with -STABLE and -CURRENT It would probably need more than a few rewrites and reorganization though From trhodes at FreeBSD.org Mon Dec 15 15:36:45 2008 From: trhodes at FreeBSD.org (Tom Rhodes) Date: Mon Dec 15 15:36:56 2008 Subject: Preface need update. In-Reply-To: <4946AAD6.6050300@gmail.com> References: <1226494693.1809.10.camel@localhost> <491B4F01.9020403@gmail.com> <2a7894eb0811121605k1310bf8avf7a69363fc504905@mail.gmail.com> <20081112200755.66c52a48.trhodes@FreeBSD.org> <491C39E7.7040609@gmail.com> <20081113185333.25a73ebf.trhodes@FreeBSD.org> <2a7894eb0812132146w42722ce5n809cd5d0a9c451eb@mail.gmail.com> <20081214185058.48a7c2c2.trhodes@FreeBSD.org> <2a7894eb0812141832u20af4821h121a520fab746c7c@mail.gmail.com> <20081215062858.6c76fb33.trhodes@FreeBSD.org> <20081215134919.51a88d90.trhodes@FreeBSD.org> <4946AAD6.6050300@gmail.com> Message-ID: <20081215183632.553d194b.trhodes@FreeBSD.org> On Mon, 15 Dec 2008 21:07:02 +0200 Manolis Kiagias wrote: > Tom Rhodes wrote: > >> > >> Works for me. Let me work over a patch today (I should have > >> enough time) and get it out. :) > >> > > > > This patch merges both chapters in a way I thought worked out > > best. Could probably use a bit of text in the intro but I'm > > not 100% sure. > > > > http://people.freebsd.org/~trhodes/patches/cutting-edge.diff > > > > Though I do remember why I started another chapter though, > > primarily because cutting-edge came off to me as "using CURRENT > > and/or test versions" rather than stable with bug fixes. :) > > > > Thanks, > > > > > If these chapters are merged, I think we will have to rethink the "The > Cutting Edge" title. The title is by itself intimidating for the > beginning-intermediate user who is already convinced it is best for him > to use "RELEASE" until he is comfortable with the system. And using > freebsd-update is essential (and a rather easy task) at any user level. > > How about changing the chapter to something like "Updating and Upgrading > FreeBSD"? > The first sections could deal with security updates and minor / major > version upgrades using freebsd-update. > Later sections could deal with -STABLE and -CURRENT > It would probably need more than a few rewrites and reorganization though I'm all about that. -- Tom Rhodes From murray at stokely.org Mon Dec 15 18:35:54 2008 From: murray at stokely.org (Murray Stokely) Date: Mon Dec 15 18:36:04 2008 Subject: Preface need update. In-Reply-To: <4946AAD6.6050300@gmail.com> References: <1226494693.1809.10.camel@localhost> <20081112200755.66c52a48.trhodes@FreeBSD.org> <491C39E7.7040609@gmail.com> <20081113185333.25a73ebf.trhodes@FreeBSD.org> <2a7894eb0812132146w42722ce5n809cd5d0a9c451eb@mail.gmail.com> <20081214185058.48a7c2c2.trhodes@FreeBSD.org> <2a7894eb0812141832u20af4821h121a520fab746c7c@mail.gmail.com> <20081215062858.6c76fb33.trhodes@FreeBSD.org> <20081215134919.51a88d90.trhodes@FreeBSD.org> <4946AAD6.6050300@gmail.com> Message-ID: <2a7894eb0812151835g51d3f64bg5c60d6f8e4fd2497@mail.gmail.com> On Mon, Dec 15, 2008 at 11:07 AM, Manolis Kiagias wrote: > If these chapters are merged, I think we will have to rethink the "The > Cutting Edge" title. The title is by itself intimidating for the > beginning-intermediate user who is already convinced it is best for him > to use "RELEASE" until he is comfortable with the system. And using > freebsd-update is essential (and a rather easy task) at any user level. > > How about changing the chapter to something like "Updating and Upgrading > FreeBSD"? > The first sections could deal with security updates and minor / major > version upgrades using freebsd-update. > Later sections could deal with -STABLE and -CURRENT > It would probably need more than a few rewrites and reorganization though Yea I think this sounds good. Tom, can you include a link to the HTML with your next diff -- I find it easier to review big reorganizations in the built html form rather than the diffs. If there is really just too much content for one chapter then maybe the updating and upgrading chapter could still be split into two adjacent chapters -- one for the basics of updrading between releases with mergemaster and such, and a second with more complicated source upgrades to -CURRENT. - Murray From keramida at freebsd.org Mon Dec 15 18:47:48 2008 From: keramida at freebsd.org (Giorgos Keramidas) Date: Mon Dec 15 18:47:54 2008 Subject: [PATCH] Adding elements to wlan Handbook section In-Reply-To: <20081213.014606.247395509.hrs@allbsd.org> (Hiroki Sato's message of "Sat, 13 Dec 2008 01:46:06 +0900 (JST)") References: <87k5a63z2d.fsf@kobe.laptop> <871vwdahna.fsf@kobe.laptop> <20081213.014606.247395509.hrs@allbsd.org> Message-ID: <87myewygxo.fsf@kobe.laptop> On Sat, 13 Dec 2008 01:46:06 +0900 (JST), Hiroki Sato wrote: > Giorgos Keramidas wrote > in <871vwdahna.fsf@kobe.laptop>: > 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. Very nice, thank you! :-) I like the idea of moving content from role="xxx" attributes to real content too. What would our next steps be for this? Perhaps something like this? * Commit this to doc/share/sgml/freebsd.dsl * Add share/sgml/acronyms.ent with some of the common entities * Update the existing role="" attributes to use the entities for those acronyms that need a tooltip, but a plain FOO for all the rest. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 194 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-doc/attachments/20081216/2921048c/attachment.pgp From claymore at eml.cc Tue Dec 16 01:11:10 2008 From: claymore at eml.cc (mr g) Date: Tue Dec 16 01:11:17 2008 Subject: handbook question Message-ID: <1229417680.20949.1290294601@webmail.messagingengine.com> Why isn't part 26 included in part4? Both seem to have to do with adding the latest code to freebsd. I don't get why part 26 is near networking? I only say because I was hunting around and then fond it with help of a friend on chat. I think it might be a good idea to roll it into part 4 so all updating of programs and the os are covered together. Thanks. -g -- http://www.fastmail.fm - I mean, what is it about a decent email service? From murray at FreeBSD.org Tue Dec 16 01:20:02 2008 From: murray at FreeBSD.org (Murray Stokely) Date: Tue Dec 16 01:20:08 2008 Subject: docs/129671: New TCP chapter for Developer's Handbook (from rwatson meetbsd slides) Message-ID: <200812160915.mBG9FYYg098684@www.freebsd.org> >Number: 129671 >Category: docs >Synopsis: New TCP chapter for Developer's Handbook (from rwatson meetbsd slides) >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-doc >State: open >Quarter: >Keywords: >Date-Required: >Class: change-request >Submitter-Id: current-users >Arrival-Date: Tue Dec 16 09:20:01 UTC 2008 >Closed-Date: >Last-Modified: >Originator: Murray Stokely >Release: >Organization: FreeBSD Project >Environment: >Description: The Slides from Robert Watson's networking talk at MeetBSD 2008 would make the start of a nice TCP chapter to the Developer's Handbook. This should probably go in the Interprocess Communication of the book. Robert is exporting the diagrams from his slides into EPS so they could be used for this purpose. If someone has time to work with Robert, and to a lesser extent, myself, I think this would be a great addition to our online documentation corpus. http://www.watson.org/~robert/freebsd/2008meetbsd/ The arrival of high CPU core density, with commodity quad-core notebooks and 32-core servers, combined with 10gbps networking have transformed network design principles for operating systems. This talk will describe changes in the FreeBSD 6.x, 7.x, and forthcoming 8.x network stacks required to exploit multiple cores and serve 10gbps networks. The goal of the session will be to introduce the audience to general strategies used to improve performance, their rationales, and their impact on applications and users: Introduction to the SMPng Project and the follow-on Netperf Project Workloads and performance measurement Efficient primitives to support modern network stacks Multi-core and cache-aware network memory allocator Fine-grained network stack locking Load-balancing and contention-avoidance across multiple CPUs CPU affinity for network stack data structures TCP performance enhancements including TSO, LRO, and TOE Zero-copy Berkely Packet Filter (BPF) buffers Direct network stack dispatch from interrupt handlers Multiple input and output queues >How-To-Repeat: >Fix: Take the content from those slides, mark it up in DocBook, and submit it as a new chapter to the developers handbook covering TCP. >Release-Note: >Audit-Trail: >Unformatted: From sonic2000gr at gmail.com Tue Dec 16 01:47:35 2008 From: sonic2000gr at gmail.com (Manolis Kiagias) Date: Tue Dec 16 01:47:41 2008 Subject: handbook question In-Reply-To: <1229417680.20949.1290294601@webmail.messagingengine.com> References: <1229417680.20949.1290294601@webmail.messagingengine.com> Message-ID: <49477925.50902@gmail.com> mr g wrote: > Why isn't part 26 included in part4? Both seem to have to do with > adding the latest code to freebsd. I don't get why part 26 is > near networking? I only say because I was hunting around and then > fond it with help of a friend on chat. I think it might be a good > idea to roll it into part 4 so all updating of programs and the > os are covered together. Thanks. -g > > Chapter 4 refers to upgrading and ports and packages, which are third party applications as fas as FreeBSD is concerned. Chapter 26 deals with freebsd-update which updates the base system and portsnap which updates the Ports tree (but not installed programs). There is currently a discussion on merging chapter 26 with "The Cutting Edge" which also refers to base system upgrades. The resulting chapter will also be more appropriately named (something like Updating and Upgrading FreeBSD). From gfritz at gmail.com Tue Dec 16 09:30:01 2008 From: gfritz at gmail.com (Geoff Fritz) Date: Tue Dec 16 09:30:07 2008 Subject: docs/129684: gcache.8 man page missing Message-ID: <200812161726.mBGHQ0QV004669@www.freebsd.org> >Number: 129684 >Category: docs >Synopsis: gcache.8 man page missing >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-doc >State: open >Quarter: >Keywords: >Date-Required: >Class: doc-bug >Submitter-Id: current-users >Arrival-Date: Tue Dec 16 17:30:00 UTC 2008 >Closed-Date: >Last-Modified: >Originator: Geoff Fritz >Release: 7.1-RC1 >Organization: >Environment: FreeBSD dev.null 7.1-RC1 FreeBSD 7.1-RC1 #0: Sun Dec 14 17:51:25 MST 2008 root@dev.null:/usr/obj/usr/src/sys/DESKTOP amd64 >Description: The man page, or any documentation, for the geom_cache/gcache program appears to be missing. >How-To-Repeat: type "man gcache" >Fix: I was able to locate a man page in the posted tarball attachment: http://lists.freebsd.org/pipermail/freebsd-geom/attachments/20060704/9c368150/geom_cache.obj gcache.8 is dated Jul 04, 2006 The man page as it exists in that archive could be more informative, maybe including more of its stated purpose. Information about gcache can be found in the following thread: http://lists.freebsd.org/pipermail/freebsd-geom/2006-July/001342.html and also in the following commit message: http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/geom/cache/g_cache.c#rev1.1 >Release-Note: >Audit-Trail: >Unformatted: From murray at FreeBSD.org Tue Dec 16 19:19:38 2008 From: murray at FreeBSD.org (murray@FreeBSD.org) Date: Tue Dec 16 19:19:44 2008 Subject: docs/127842: list of hardware devices missing from the relnotes Message-ID: <200812170319.mBH3JbS8000911@freefall.freebsd.org> Synopsis: list of hardware devices missing from the relnotes Responsible-Changed-From-To: freebsd-doc->murray Responsible-Changed-By: murray Responsible-Changed-When: Wed Dec 17 03:19:26 UTC 2008 Responsible-Changed-Why: Will take a look. http://www.freebsd.org/cgi/query-pr.cgi?pr=127842 From murray at FreeBSD.org Tue Dec 16 19:20:45 2008 From: murray at FreeBSD.org (murray@FreeBSD.org) Date: Tue Dec 16 19:20:51 2008 Subject: docs/127840: [patch] fix entity references in release/doc/en_US.ISO8859-1/hardware/article.sgml Message-ID: <200812170320.mBH3KilY007406@freefall.freebsd.org> Synopsis: [patch] fix entity references in release/doc/en_US.ISO8859-1/hardware/article.sgml Responsible-Changed-From-To: freebsd-doc->murray Responsible-Changed-By: murray Responsible-Changed-When: Wed Dec 17 03:20:16 UTC 2008 Responsible-Changed-Why: Will build test this patch and submit to head after I get another pending change in. http://www.freebsd.org/cgi/query-pr.cgi?pr=127840 From murray at FreeBSD.org Tue Dec 16 19:25:43 2008 From: murray at FreeBSD.org (murray@FreeBSD.org) Date: Tue Dec 16 19:25:49 2008 Subject: docs/102148: The description of which Intel chips have EM64T is out of date Message-ID: <200812170325.mBH3PgqA007894@freefall.freebsd.org> Synopsis: The description of which Intel chips have EM64T is out of date State-Changed-From-To: open->patched State-Changed-By: murray State-Changed-When: Wed Dec 17 03:25:08 UTC 2008 State-Changed-Why: Commited to head. Will insta-mfc to 7.x and 7.1 branches momentarily. Responsible-Changed-From-To: freebsd-doc->murray Responsible-Changed-By: murray Responsible-Changed-When: Wed Dec 17 03:25:08 UTC 2008 Responsible-Changed-Why: Commited to head. Will insta-mfc to 7.x and 7.1 branches momentarily. http://www.freebsd.org/cgi/query-pr.cgi?pr=102148 From hrs at allbsd.org Tue Dec 16 21:14:41 2008 From: hrs at allbsd.org (Hiroki Sato) Date: Tue Dec 16 21:14:47 2008 Subject: [PATCH] Adding elements to wlan Handbook section In-Reply-To: <87myewygxo.fsf@kobe.laptop> References: <871vwdahna.fsf@kobe.laptop> <20081213.014606.247395509.hrs@allbsd.org> <87myewygxo.fsf@kobe.laptop> Message-ID: <20081217.140658.33303067.hrs@allbsd.org> Giorgos Keramidas wrote in <87myewygxo.fsf@kobe.laptop>: ke> What would our next steps be for this? ke> ke> Perhaps something like this? ke> ke> * Commit this to doc/share/sgml/freebsd.dsl ke> ke> * Add share/sgml/acronyms.ent with some of the common entities ke> ke> * Update the existing role="" attributes to use the entities for those ke> acronyms that need a tooltip, but a plain FOO for ke> all the rest. Yes, after committing the bits to freebsd.dsl, generating title="foo" attr from will be stopped but no build error should occur. Adding acronyms.ent and updating existing elements must be atomic. I will send you another patch of freebsd.dsl tonight since the previous one is not commit-ready. -- | Hiroki SATO -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-doc/attachments/20081217/55f7dd4d/attachment.pgp From loader at FreeBSD.org Wed Dec 17 08:22:07 2008 From: loader at FreeBSD.org (loader) Date: Wed Dec 17 08:22:13 2008 Subject: docs/127923: Please mention qemu in the FreeBSD Handbook In-Reply-To: <20081215130236.B5E051D703EF@mail.freebsdmall.com> (loader@freebsdmall.com's message of "Mon\, 15 Dec 2008 05\:02\:36 -0800 \(PST\)") References: <200812150128.mBF1Sehd094548@freefall.freebsd.org> <20081215130236.B5E051D703EF@mail.freebsdmall.com> Message-ID: <200812171622.mBHGM6b5035016@freefall.freebsd.org> loader wrote: > murray@FreeBSD.org wrote: > >> Synopsis: Please mention qemu in the FreeBSD Handbook >> >> Responsible-Changed-From-To: freebsd-doc->loader >> Responsible-Changed-By: murray >> Responsible-Changed-When: Mon Dec 15 01:28:02 UTC 2008 >> Responsible-Changed-Why: >> Loader, didn't you have some patchecs to add qemu here? Can you add >> something about it to the virtualization chapter? >> >> >> http://www.freebsd.org/cgi/query-pr.cgi?pr=127923 > > Okay, I will try to add a section about Qemu these days. Juergen Lock sent me a patch. -------------- next part -------------- A non-text attachment was scrubbed... Name: virtualization.diff Type: text/x-diff Size: 18801 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-doc/attachments/20081217/e1bdd282/virtualization.bin From loader at FreeBSD.org Wed Dec 17 08:26:24 2008 From: loader at FreeBSD.org (loader) Date: Wed Dec 17 08:26:30 2008 Subject: docs/127923: Please mention qemu in the FreeBSD Handbook In-Reply-To: <20081215130236.B5E051D703EF@mail.freebsdmall.com> (loader@freebsdmall.com's message of "Mon\, 15 Dec 2008 05\:02\:36 -0800 \(PST\)") References: <200812150128.mBF1Sehd094548@freefall.freebsd.org> <20081215130236.B5E051D703EF@mail.freebsdmall.com> Message-ID: <200812171626.mBHGQL0K035212@freefall.freebsd.org> loader wrote: >> http://www.freebsd.org/cgi/query-pr.cgi?pr=127923 And I reworded some parts of Juergen's patch with the help of murray@. -------------- next part -------------- A non-text attachment was scrubbed... Name: virtualization.diff Type: text/x-diff Size: 16010 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-doc/attachments/20081217/9fb45379/virtualization.bin From amdmi3 at FreeBSD.org Wed Dec 17 14:30:03 2008 From: amdmi3 at FreeBSD.org (Dmitry Marakasov) Date: Wed Dec 17 14:30:09 2008 Subject: docs/129723: [PATCH] fix 5 typos Message-ID: <20081217222747.C42191702D@hades.panopticon> >Number: 129723 >Category: docs >Synopsis: [PATCH] fix 5 typos >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-doc >State: open >Quarter: >Keywords: >Date-Required: >Class: doc-bug >Submitter-Id: current-users >Arrival-Date: Wed Dec 17 22:30:02 UTC 2008 >Closed-Date: >Last-Modified: >Originator: Dmitry Marakasov >Release: FreeBSD 7.0-RELEASE-p1 i386 >Organization: >Environment: System: FreeBSD hades.panopticon 7.0-RELEASE-p1 FreeBSD 7.0-RELEASE-p1 #1: Wed Jun 25 15:36:22 MSD 2008 root@hades.panopticon:/usr/obj/usr/src/sys/HADES i386 >Description: Fix 2 typos in English docs and 3 typos in Russian. >How-To-Repeat: >Fix: --- doc.patch begins here --- Index: en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml =================================================================== RCS file: /home/amdmi3/projects/freebsd/FreeBSD.cvs/doc/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml,v retrieving revision 1.417 diff -u -r1.417 chapter.sgml --- en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml 12 Dec 2008 06:06:03 -0000 1.417 +++ en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml 17 Dec 2008 21:47:27 -0000 @@ -1719,7 +1719,7 @@ 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 + B we will just need to choose two IP addresses and a SSID. On the box A: Index: en_US.ISO8859-1/books/handbook/network-servers/chapter.sgml =================================================================== RCS file: /home/amdmi3/projects/freebsd/FreeBSD.cvs/doc/en_US.ISO8859-1/books/handbook/network-servers/chapter.sgml,v retrieving revision 1.110 diff -u -r1.110 chapter.sgml --- en_US.ISO8859-1/books/handbook/network-servers/chapter.sgml 4 Dec 2008 15:21:04 -0000 1.110 +++ en_US.ISO8859-1/books/handbook/network-servers/chapter.sgml 17 Dec 2008 21:47:47 -0000 @@ -4175,7 +4175,7 @@ www/mod_perl and a statically compiled version is available in www/apache13-modperl. - mod_perl 2.0 is avaliable in + mod_perl 2.0 is available in www/mod_perl2. Index: ru_RU.KOI8-R/articles/multi-os/article.sgml =================================================================== RCS file: /home/amdmi3/projects/freebsd/FreeBSD.cvs/doc/ru_RU.KOI8-R/articles/multi-os/article.sgml,v retrieving revision 1.1 diff -u -r1.1 article.sgml --- ru_RU.KOI8-R/articles/multi-os/article.sgml 10 Jun 2005 08:26:32 -0000 1.1 +++ ru_RU.KOI8-R/articles/multi-os/article.sgml 17 Dec 2008 22:17:45 -0000 @@ -654,7 +654,7 @@ ÓÒÁÚÕ ÐÏÓÌÅ MBR (0 ÃÉÌÉÎÄÒ, 0 ÇÏÌÏ×ËÁ, 2 ÓÅËÔÏÒ). åÓÌÉ × ÐÒÏÇÒÁÍÍÅ sysinstall ×Ù ÕËÁÖÉÔÅ ÐÏÌÎÏÓÔØÀ Ó×ÏÂÏÄÎÙÊ ÄÉÓË ÉÌÉ Ó Ó×ÏÂÏÄÎÙÍ ÐÒÏÓÔÒÁÎÓÔ×ÏÍ × ÎÁÞÁÌÅ, ÔÏ FreeBSD ÓÏÚÄÁÓÔ - ÒÁÄÅÌ, ÎÁÞÉÎÁÀÝÉÊÓÑ ÉÍÅÎÎÏ Ó ÓÁÍÏÇÏ ÎÁÞÁÌÁ ÄÉÓËÁ (ÔÁË ÂÙÌÏ, + ÒÁÚÄÅÌ, ÎÁÞÉÎÁÀÝÉÊÓÑ ÉÍÅÎÎÏ Ó ÓÁÍÏÇÏ ÎÁÞÁÌÁ ÄÉÓËÁ (ÔÁË ÂÙÌÏ, ËÏÇÄÁ Ñ × ÐÏÓÌÅÄÎÉÊ ÒÁÚ ÚÁÎÉÍÁÌÓÑ ÜÔÉÍ ×ÏÐÒÏÓÏÍ). úÁÔÅÍ, ËÏÇÄÁ ×Ù ÂÕÄÅÔÅ ÕÓÔÁÎÁ×ÌÉ×ÁÔØ ÍÅÎÅÄÖÅÒ ÚÁÇÒÕÚËÉ, ÔÒÅÂÕÀÝÉÊ ÎÅÓËÏÌØËÏ ÄÏÐÏÌÎÉÔÅÌØÎÙÈ ÓÅËÔÏÒÏ×, ÔÏ ×Ù ÚÁÔÒÅÔÅ ÎÁÞÁÌØÎÙÅ Index: ru_RU.KOI8-R/books/fdp-primer/tools/chapter.sgml =================================================================== RCS file: /home/amdmi3/projects/freebsd/FreeBSD.cvs/doc/ru_RU.KOI8-R/books/fdp-primer/tools/chapter.sgml,v retrieving revision 1.2 diff -u -r1.2 chapter.sgml --- ru_RU.KOI8-R/books/fdp-primer/tools/chapter.sgml 6 May 2005 18:56:15 -0000 1.2 +++ ru_RU.KOI8-R/books/fdp-primer/tools/chapter.sgml 17 Dec 2008 22:15:40 -0000 @@ -49,7 +49,7 @@ ÏÞÅÎØ ÓÉÌØÎÏ ÕÐÒÏÝÁÅÔ ÒÁÂÏÔÕ ÐÏ ÉÈ ÕÓÔÁÎÏ×ËÅ . ðÅÒÅÄ ÔÅÍ, ËÁË ×Ù ÓÍÏÖÅÔÅ ÒÁÂÏÔÁÔØ Ó ËÁËÉÍÉ-ÌÉÂÏ ÐÒÉÍÅÒÁÍÉ ÉÚ - ÐÏÓÌÅÄÕÀÝÉÈ ÇÌÁ×, ×ÁÍ ÎÕÄÎÏ ÕÓÔÁÎÏ×ÉÔØ ÜÔÉ ÐÒÏÇÒÁÍÍÎÙÅ ÓÒÅÄÓÔ×Á. òÅÁÌØÎÏÅ + ÐÏÓÌÅÄÕÀÝÉÈ ÇÌÁ×, ×ÁÍ ÎÕÖÎÏ ÕÓÔÁÎÏ×ÉÔØ ÜÔÉ ÐÒÏÇÒÁÍÍÎÙÅ ÓÒÅÄÓÔ×Á. òÅÁÌØÎÏÅ ÉÓÐÏÌØÚÏ×ÁÎÉÅ ÜÔÉÈ ÉÎÓÔÒÕÍÅÎÔÏ× ÏÓ×ÅÝÅÎÏ × ÓÌÅÄÕÀÝÉÈ ÇÌÁ×ÁÈ. Index: ru_RU.KOI8-R/books/porters-handbook/book.sgml =================================================================== RCS file: /home/amdmi3/projects/freebsd/FreeBSD.cvs/doc/ru_RU.KOI8-R/books/porters-handbook/book.sgml,v retrieving revision 1.25 diff -u -r1.25 book.sgml --- ru_RU.KOI8-R/books/porters-handbook/book.sgml 20 Oct 2006 09:24:16 -0000 1.25 +++ ru_RU.KOI8-R/books/porters-handbook/book.sgml 17 Dec 2008 22:13:18 -0000 @@ -7078,7 +7078,7 @@ - 5.1-CURRENT aÐÏÓÌÅ ÄÏÂÁ×ÌÅÎÉÑ ÐÏÌÅÊ lockfunc É lockfuncarg + 5.1-CURRENT ÐÏÓÌÅ ÄÏÂÁ×ÌÅÎÉÑ ÐÏÌÅÊ lockfunc É lockfuncarg × &man.bus.dma.tag.create.9;. 501102 --- doc.patch ends here --- >Release-Note: >Audit-Trail: >Unformatted: From trhodes at FreeBSD.org Wed Dec 17 20:22:17 2008 From: trhodes at FreeBSD.org (Tom Rhodes) Date: Wed Dec 17 20:22:28 2008 Subject: Cutting edge -> Upgrading (was: Re: Preface need update.) In-Reply-To: <2a7894eb0812151835g51d3f64bg5c60d6f8e4fd2497@mail.gmail.com> References: <1226494693.1809.10.camel@localhost> <20081112200755.66c52a48.trhodes@FreeBSD.org> <491C39E7.7040609@gmail.com> <20081113185333.25a73ebf.trhodes@FreeBSD.org> <2a7894eb0812132146w42722ce5n809cd5d0a9c451eb@mail.gmail.com> <20081214185058.48a7c2c2.trhodes@FreeBSD.org> <2a7894eb0812141832u20af4821h121a520fab746c7c@mail.gmail.com> <20081215062858.6c76fb33.trhodes@FreeBSD.org> <20081215134919.51a88d90.trhodes@FreeBSD.org> <4946AAD6.6050300@gmail.com> <2a7894eb0812151835g51d3f64bg5c60d6f8e4fd2497@mail.gmail.com> Message-ID: <20081217232207.53615962.trhodes@FreeBSD.org> Hi Murray, Manolis, On Mon, 15 Dec 2008 18:35:51 -0800 "Murray Stokely" wrote: > On Mon, Dec 15, 2008 at 11:07 AM, Manolis Kiagias wrote: > > If these chapters are merged, I think we will have to rethink the "The > > Cutting Edge" title. The title is by itself intimidating for the > > beginning-intermediate user who is already convinced it is best for him > > to use "RELEASE" until he is comfortable with the system. And using > > freebsd-update is essential (and a rather easy task) at any user level. > > > > How about changing the chapter to something like "Updating and Upgrading > > FreeBSD"? > > The first sections could deal with security updates and minor / major > > version upgrades using freebsd-update. > > Later sections could deal with -STABLE and -CURRENT > > It would probably need more than a few rewrites and reorganization though > > Yea I think this sounds good. Tom, can you include a link to the HTML > with your next diff -- I find it easier to review big reorganizations > in the built html form rather than the diffs. > > If there is really just too much content for one chapter then maybe > the updating and upgrading chapter could still be split into two > adjacent chapters -- one for the basics of updrading between releases > with mergemaster and such, and a second with more complicated source > upgrades to -CURRENT. > > - Murray > Apologies for this tardy reply, but I've recently come down with some kind of a bug. Anyway, this is what I have right now: http://people.freebsd.org/~trhodes/doc/latest-handbook.diff http://people.freebsd.org/~trhodes/doc/handbook/ The diff contains my Updating chapter placed above the current cutting-edge content along with some alterations to make the documentation flow a bit. Surely another update or two will be needed to perfect this version, but I think it looks pretty decent as it is now. This also contains some things I've been working on lately: o Added a warning about loss of data in GEOM chapter, covers a PR about gmirror; o Add a new section on syslog network monitoring to network-servers; o Add the Audit chapter to preface.sgml and mark up DTrace with &dtrace. The "additional" parts have already been reviewed by rene and pgj. An earlier version of the preface.sgml part was reviewed by Murray already. The handbook/ directory has a built version of the handbook with that diff applied. If there are no objections I'm perfectly cool with: Patching the preface, geom, and network-servers chapters; Putting in a repo copy request for cutting-edge/chapter.sgml to upgrading/chapter.sgml; Commit follow up to note the repocopy; Commit this version of cutting edge to upgrading/chapter.sgml; Final commit to remove cutting-edge and updating chapters from the build and the like. I'm positive someone will come up with a better way of handling this but I'm tired and a bit off. -- Tom Rhodes From maxim at FreeBSD.org Thu Dec 18 01:34:54 2008 From: maxim at FreeBSD.org (maxim@FreeBSD.org) Date: Thu Dec 18 01:35:04 2008 Subject: docs/129723: [PATCH] fix 5 typos Message-ID: <200812180934.mBI9YswM023726@freefall.freebsd.org> Synopsis: [PATCH] fix 5 typos State-Changed-From-To: open->closed State-Changed-By: maxim State-Changed-When: Thu Dec 18 09:34:38 UTC 2008 State-Changed-Why: Fixed. Thanks! http://www.freebsd.org/cgi/query-pr.cgi?pr=129723 From dfilter at FreeBSD.ORG Thu Dec 18 01:40:04 2008 From: dfilter at FreeBSD.ORG (dfilter service) Date: Thu Dec 18 01:40:16 2008 Subject: docs/129723: commit references a PR Message-ID: <200812180940.mBI9e3xv024260@freefall.freebsd.org> The following reply was made to PR docs/129723; it has been noted by GNATS. From: dfilter@FreeBSD.ORG (dfilter service) To: bug-followup@FreeBSD.org Cc: Subject: Re: docs/129723: commit references a PR Date: Thu, 18 Dec 2008 09:31:04 +0000 (UTC) maxim 2008-12-18 09:30:50 UTC FreeBSD doc repository Modified files: ru_RU.KOI8-R/articles/multi-os article.sgml ru_RU.KOI8-R/books/fdp-primer/tools chapter.sgml ru_RU.KOI8-R/books/porters-handbook book.sgml Log: o Fix typos. PR: docs/129723 (a part of) Submitted by: Dmitry Marakasov Obtained from: FreeBSD Russian Doc Project Revision Changes Path 1.2 +1 -1 doc/ru_RU.KOI8-R/articles/multi-os/article.sgml 1.3 +1 -1 doc/ru_RU.KOI8-R/books/fdp-primer/tools/chapter.sgml 1.26 +1 -1 doc/ru_RU.KOI8-R/books/porters-handbook/book.sgml _______________________________________________ cvs-all@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/cvs-all To unsubscribe, send any mail to "cvs-all-unsubscribe@freebsd.org" From dfilter at FreeBSD.ORG Thu Dec 18 01:40:06 2008 From: dfilter at FreeBSD.ORG (dfilter service) Date: Thu Dec 18 01:40:17 2008 Subject: docs/129723: commit references a PR Message-ID: <200812180940.mBI9e6cS024284@freefall.freebsd.org> The following reply was made to PR docs/129723; it has been noted by GNATS. From: dfilter@FreeBSD.ORG (dfilter service) To: bug-followup@FreeBSD.org Cc: Subject: Re: docs/129723: commit references a PR Date: Thu, 18 Dec 2008 09:34:36 +0000 (UTC) maxim 2008-12-18 09:34:23 UTC FreeBSD doc repository Modified files: en_US.ISO8859-1/books/handbook/advanced-networking chapter.sgml en_US.ISO8859-1/books/handbook/network-servers chapter.sgml Log: o Grammar. PR: docs/129723 Submitted by: amdmi3 Revision Changes Path 1.418 +1 -1 doc/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml 1.111 +1 -1 doc/en_US.ISO8859-1/books/handbook/network-servers/chapter.sgml _______________________________________________ cvs-all@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/cvs-all To unsubscribe, send any mail to "cvs-all-unsubscribe@freebsd.org" From management at methodeefficace.com Thu Dec 18 03:31:12 2008 From: management at methodeefficace.com (=?UTF-8?B?Si4gUmVldmVz?=) Date: Thu Dec 18 03:31:19 2008 Subject: Reduce Excess Inventory Message-ID: <5aded8c1158c21245c62d628c7cc0602@www.mailingm.co.uk> Your email client cannot read this email. To view it online, please go here: http://www.mailingm.co.uk/2/display.php?M=563873&C=ed43102b6c204e3b5b5d25cf9acf393d&S=1638&L=210&N=1290 To stop receiving these emails:http://www.mailingm.co.uk/2/unsubscribe.php?M=563873&N=1638&L=210&C=ed43102b6c204e3b5b5d25cf9acf393d From sonic2000gr at gmail.com Thu Dec 18 11:07:39 2008 From: sonic2000gr at gmail.com (Manolis Kiagias) Date: Thu Dec 18 11:07:46 2008 Subject: Cutting edge -> Upgrading In-Reply-To: <20081217232207.53615962.trhodes@FreeBSD.org> References: <1226494693.1809.10.camel@localhost> <20081112200755.66c52a48.trhodes@FreeBSD.org> <491C39E7.7040609@gmail.com> <20081113185333.25a73ebf.trhodes@FreeBSD.org> <2a7894eb0812132146w42722ce5n809cd5d0a9c451eb@mail.gmail.com> <20081214185058.48a7c2c2.trhodes@FreeBSD.org> <2a7894eb0812141832u20af4821h121a520fab746c7c@mail.gmail.com> <20081215062858.6c76fb33.trhodes@FreeBSD.org> <20081215134919.51a88d90.trhodes@FreeBSD.org> <4946AAD6.6050300@gmail.com> <2a7894eb0812151835g51d3f64bg5c60d6f8e4fd2497@mail.gmail.com> <20081217232207.53615962.trhodes@FreeBSD.org> Message-ID: <494A9F76.2020401@gmail.com> Tom Rhodes wrote: > Hi Murray, Manolis, > > > On Mon, 15 Dec 2008 18:35:51 -0800 > "Murray Stokely" wrote: > > >> On Mon, Dec 15, 2008 at 11:07 AM, Manolis Kiagias wrote: >> >>> If these chapters are merged, I think we will have to rethink the "The >>> Cutting Edge" title. The title is by itself intimidating for the >>> beginning-intermediate user who is already convinced it is best for him >>> to use "RELEASE" until he is comfortable with the system. And using >>> freebsd-update is essential (and a rather easy task) at any user level. >>> >>> How about changing the chapter to something like "Updating and Upgrading >>> FreeBSD"? >>> The first sections could deal with security updates and minor / major >>> version upgrades using freebsd-update. >>> Later sections could deal with -STABLE and -CURRENT >>> It would probably need more than a few rewrites and reorganization though >>> >> Yea I think this sounds good. Tom, can you include a link to the HTML >> with your next diff -- I find it easier to review big reorganizations >> in the built html form rather than the diffs. >> >> If there is really just too much content for one chapter then maybe >> the updating and upgrading chapter could still be split into two >> adjacent chapters -- one for the basics of updrading between releases >> with mergemaster and such, and a second with more complicated source >> upgrades to -CURRENT. >> >> - Murray >> >> > > Apologies for this tardy reply, but I've recently come down > with some kind of a bug. Anyway, this is what I have right now: > > http://people.freebsd.org/~trhodes/doc/latest-handbook.diff > > http://people.freebsd.org/~trhodes/doc/handbook/ > > The diff contains my Updating chapter placed above the current > cutting-edge content along with some alterations to make the > documentation flow a bit. Surely another update or two will > be needed to perfect this version, but I think it looks pretty > decent as it is now. > > Thanks Tom, this is more or less what I had in mind for the updating-upgrading chapter :) Having read the synopsis, I feel we need to change it a bit so it matches more closely the updated content. Something like this: http://people.freebsd.org/~manolis/updating-upgrading.html#UPDATING-UPGRADING-SYNOPSIS and the patch: http://people.freebsd.org/~manolis/cutting-edge.txt Basically this rephrases the original a bit, and also reorders the itemized list to more or less match the order the info is presented in the chapter. Feel free to change it as you see fit ;) Thanks, manolis From trhodes at FreeBSD.org Thu Dec 18 19:03:14 2008 From: trhodes at FreeBSD.org (Tom Rhodes) Date: Thu Dec 18 19:03:21 2008 Subject: Cutting edge -> Upgrading In-Reply-To: <494A9F76.2020401@gmail.com> References: <1226494693.1809.10.camel@localhost> <20081112200755.66c52a48.trhodes@FreeBSD.org> <491C39E7.7040609@gmail.com> <20081113185333.25a73ebf.trhodes@FreeBSD.org> <2a7894eb0812132146w42722ce5n809cd5d0a9c451eb@mail.gmail.com> <20081214185058.48a7c2c2.trhodes@FreeBSD.org> <2a7894eb0812141832u20af4821h121a520fab746c7c@mail.gmail.com> <20081215062858.6c76fb33.trhodes@FreeBSD.org> <20081215134919.51a88d90.trhodes@FreeBSD.org> <4946AAD6.6050300@gmail.com> <2a7894eb0812151835g51d3f64bg5c60d6f8e4fd2497@mail.gmail.com> <20081217232207.53615962.trhodes@FreeBSD.org> <494A9F76.2020401@gmail.com> Message-ID: <20081218220303.36017fa2.trhodes@FreeBSD.org> On Thu, 18 Dec 2008 21:07:34 +0200 Manolis Kiagias wrote: > Tom Rhodes wrote: > > Hi Murray, Manolis, > > > > > > On Mon, 15 Dec 2008 18:35:51 -0800 > > "Murray Stokely" wrote: > > > > > >> On Mon, Dec 15, 2008 at 11:07 AM, Manolis Kiagias wrote: > >> > >>> If these chapters are merged, I think we will have to rethink the "The > >>> Cutting Edge" title. The title is by itself intimidating for the > >>> beginning-intermediate user who is already convinced it is best for him > >>> to use "RELEASE" until he is comfortable with the system. And using > >>> freebsd-update is essential (and a rather easy task) at any user level. > >>> > >>> How about changing the chapter to something like "Updating and Upgrading > >>> FreeBSD"? > >>> The first sections could deal with security updates and minor / major > >>> version upgrades using freebsd-update. > >>> Later sections could deal with -STABLE and -CURRENT > >>> It would probably need more than a few rewrites and reorganization though > >>> > >> Yea I think this sounds good. Tom, can you include a link to the HTML > >> with your next diff -- I find it easier to review big reorganizations > >> in the built html form rather than the diffs. > >> > >> If there is really just too much content for one chapter then maybe > >> the updating and upgrading chapter could still be split into two > >> adjacent chapters -- one for the basics of updrading between releases > >> with mergemaster and such, and a second with more complicated source > >> upgrades to -CURRENT. > >> > >> - Murray > >> > >> > > > > Apologies for this tardy reply, but I've recently come down > > with some kind of a bug. Anyway, this is what I have right now: > > > > http://people.freebsd.org/~trhodes/doc/latest-handbook.diff > > > > http://people.freebsd.org/~trhodes/doc/handbook/ > > > > The diff contains my Updating chapter placed above the current > > cutting-edge content along with some alterations to make the > > documentation flow a bit. Surely another update or two will > > be needed to perfect this version, but I think it looks pretty > > decent as it is now. > > > > > Thanks Tom, this is more or less what I had in mind for the > updating-upgrading chapter :) > Having read the synopsis, I feel we need to change it a bit so it > matches more closely the updated content. > Something like this: > > http://people.freebsd.org/~manolis/updating-upgrading.html#UPDATING-UPGRADING-SYNOPSIS > > and the patch: > > http://people.freebsd.org/~manolis/cutting-edge.txt > > Basically this rephrases the original a bit, and also reorders > the itemized list to more or less match the order the info is presented > in the chapter. Feel free to change it as you see fit ;) This version of the patch has been applied to my try, and integrated with the latest changes done by Murray today. The latest patch and build handbook version is up here: http://people.FreeBSD.org/~trhodes/doc Please let me know how you feel about it. Other than the directory name issue (cutting edge v. updating-upgrading), I think it's pretty nice. We should consider moving forward should no one object. Thanks, -- Tom Rhodes From sonic2000gr at gmail.com Thu Dec 18 22:15:19 2008 From: sonic2000gr at gmail.com (Manolis Kiagias) Date: Thu Dec 18 22:15:25 2008 Subject: Cutting edge -> Upgrading In-Reply-To: <20081218220303.36017fa2.trhodes@FreeBSD.org> References: <1226494693.1809.10.camel@localhost> <20081112200755.66c52a48.trhodes@FreeBSD.org> <491C39E7.7040609@gmail.com> <20081113185333.25a73ebf.trhodes@FreeBSD.org> <2a7894eb0812132146w42722ce5n809cd5d0a9c451eb@mail.gmail.com> <20081214185058.48a7c2c2.trhodes@FreeBSD.org> <2a7894eb0812141832u20af4821h121a520fab746c7c@mail.gmail.com> <20081215062858.6c76fb33.trhodes@FreeBSD.org> <20081215134919.51a88d90.trhodes@FreeBSD.org> <4946AAD6.6050300@gmail.com> <2a7894eb0812151835g51d3f64bg5c60d6f8e4fd2497@mail.gmail.com> <20081217232207.53615962.trhodes@FreeBSD.org> <494A9F76.2020401@gmail.com> <20081218220303.36017fa2.trhodes@FreeBSD.org> Message-ID: <494B3BF2.8050600@gmail.com> Tom Rhodes wrote: > On Thu, 18 Dec 2008 21:07:34 +0200 > Manolis Kiagias wrote: > > >> Tom Rhodes wrote: >> >>> Hi Murray, Manolis, >>> >>> >>> On Mon, 15 Dec 2008 18:35:51 -0800 >>> "Murray Stokely" wrote: >>> >>> >>> >>>> On Mon, Dec 15, 2008 at 11:07 AM, Manolis Kiagias wrote: >>>> >>>> >>>>> If these chapters are merged, I think we will have to rethink the "The >>>>> Cutting Edge" title. The title is by itself intimidating for the >>>>> beginning-intermediate user who is already convinced it is best for him >>>>> to use "RELEASE" until he is comfortable with the system. And using >>>>> freebsd-update is essential (and a rather easy task) at any user level. >>>>> >>>>> How about changing the chapter to something like "Updating and Upgrading >>>>> FreeBSD"? >>>>> The first sections could deal with security updates and minor / major >>>>> version upgrades using freebsd-update. >>>>> Later sections could deal with -STABLE and -CURRENT >>>>> It would probably need more than a few rewrites and reorganization though >>>>> >>>>> >>>> Yea I think this sounds good. Tom, can you include a link to the HTML >>>> with your next diff -- I find it easier to review big reorganizations >>>> in the built html form rather than the diffs. >>>> >>>> If there is really just too much content for one chapter then maybe >>>> the updating and upgrading chapter could still be split into two >>>> adjacent chapters -- one for the basics of updrading between releases >>>> with mergemaster and such, and a second with more complicated source >>>> upgrades to -CURRENT. >>>> >>>> - Murray >>>> >>>> >>>> >>> Apologies for this tardy reply, but I've recently come down >>> with some kind of a bug. Anyway, this is what I have right now: >>> >>> http://people.freebsd.org/~trhodes/doc/latest-handbook.diff >>> >>> http://people.freebsd.org/~trhodes/doc/handbook/ >>> >>> The diff contains my Updating chapter placed above the current >>> cutting-edge content along with some alterations to make the >>> documentation flow a bit. Surely another update or two will >>> be needed to perfect this version, but I think it looks pretty >>> decent as it is now. >>> >>> >>> >> Thanks Tom, this is more or less what I had in mind for the >> updating-upgrading chapter :) >> Having read the synopsis, I feel we need to change it a bit so it >> matches more closely the updated content. >> Something like this: >> >> http://people.freebsd.org/~manolis/updating-upgrading.html#UPDATING-UPGRADING-SYNOPSIS >> >> and the patch: >> >> http://people.freebsd.org/~manolis/cutting-edge.txt >> >> Basically this rephrases the original a bit, and also reorders >> the itemized list to more or less match the order the info is presented >> in the chapter. Feel free to change it as you see fit ;) >> > > This version of the patch has been applied to my try, and > integrated with the latest changes done by Murray today. > > The latest patch and build handbook version is up here: > > http://people.FreeBSD.org/~trhodes/doc > > Please let me know how you feel about it. Other than the > directory name issue (cutting edge v. updating-upgrading), I > think it's pretty nice. We should consider moving forward > should no one object. Thanks, > > Yes, it looks fine to me. As a final touch, maybe it would be nice to change the title of section 24.4 from: 24.4 FreeBSD-CURRENT vs. FreeBSD-STABLE to 24.4 Tracking a Development Branch I think this flows better now that the chapter does not exclusively deal with CURRENT and STABLE. From eitanadlerlist at gmail.com Fri Dec 19 05:12:45 2008 From: eitanadlerlist at gmail.com (Eitan Adler) Date: Fri Dec 19 05:12:52 2008 Subject: Additional Contributers - questions && suggestions Message-ID: <494B9DC4.8040301@gmail.com> I have some questions comments about the "additional contributers" page. I am aware that some (if not all) of these are bikeshed questions and I urge you to IGNORE them if you feel that they are. No need to flood the mailing list. I'm just putting out some thoughts I had when looking through the article. 1) Who goes on it? Port maintainers? People who send patches? Only if they are very active? 2) If its more than one of the above should we indicate what each person did to make it on the list? (starting now) 3) Should we should have a list at the top with A B C... which links to the first person in that list that starts with the letter. 5) The last 5 entries are out of order (my guess is that someone used "sort" as they begin with a lowercase letter. 5.5) The first three names are out of order for the same reason. 6) All the "No Name"s should be at the end in alphabetical order by email address 7) Section 5 should be the last section. 8) We should have a list like http://www.openbsd.org/donations.html which lists people that donate. Section 1 only lists major donors. 9) There should be links to "how to contribute" for code and documentation. If I come to this page I have no clue how to contribute. -- Eitan Adler GNU Key fingerprint: 2E13 BC16 5F54 0FBD 62ED 42B6 B65F 24AB E9C2 CCD1 From bootiack at yahoo.com Fri Dec 19 01:55:37 2008 From: bootiack at yahoo.com (G) Date: Fri Dec 19 06:07:57 2008 Subject: section 4.5.1 Message-ID: <329017.49550.qm@web110608.mail.gq1.yahoo.com> I was schooled in IRC about how 'portsnap fetch update' is the best way to update ports, not 'portsnap update' as listed in section 4.5.1. Perhaps that section could be changed to 'portsnap fetch update'. Just an idea. thx From freebsd at bengrimm.net Fri Dec 19 09:00:07 2008 From: freebsd at bengrimm.net (Ben C. O. Grimm) Date: Fri Dec 19 09:00:14 2008 Subject: docs/129765: man 8 shutdown does not explain operation without command-line options Message-ID: <200812191657.mBJGvRCn068123@www.freebsd.org> >Number: 129765 >Category: docs >Synopsis: man 8 shutdown does not explain operation without command-line options >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-doc >State: open >Quarter: >Keywords: >Date-Required: >Class: doc-bug >Submitter-Id: current-users >Arrival-Date: Fri Dec 19 17:00:02 UTC 2008 >Closed-Date: >Last-Modified: >Originator: Ben C. O. Grimm >Release: 7.1-PRERELEASE >Organization: None >Environment: FreeBSD hail.bengrimm.net 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #0: Mon Dec 1 17:04:32 CET 2008 root@hail.bengrimm.net:/usr/obj/usr/src/sys/HAIL i386 >Description: The manual for shutdown(8) describes how the command behaves using command-line options like -h or -p, but not the behavior when omitting these options, like in 'shutdown now'. There is a brief mention of 'bringing the system down to single-user state' (which is what 'shutdown now' actually does), but it is not explained. See how this might confuse users: http://forums.freebsd.org/showthread.php?p=6273 >How-To-Repeat: >Fix: Add a one-liner to the manual about the effect of not using command-line switches in the shutdown command. >Release-Note: >Audit-Trail: >Unformatted: From trhodes at FreeBSD.org Fri Dec 19 16:28:02 2008 From: trhodes at FreeBSD.org (Tom Rhodes) Date: Fri Dec 19 16:28:14 2008 Subject: section 4.5.1 In-Reply-To: <329017.49550.qm@web110608.mail.gq1.yahoo.com> References: <329017.49550.qm@web110608.mail.gq1.yahoo.com> Message-ID: <20081219192747.1edea542.trhodes@FreeBSD.org> Hi, On Fri, 19 Dec 2008 01:28:55 -0800 (PST) G wrote: > I was schooled in IRC about how 'portsnap fetch update' is the best way to update ports, not 'portsnap update' as listed in section 4.5.1. Perhaps that section could be changed to 'portsnap fetch update'. > > Just an idea. > thx Looking at my local source, I am unable to find an actual "portsnap update" in the section; however, I have appened the following to the end of that section: To run both processes consecutively, issue the following command: &prompt.root; portsnap fetch update This change is in my local tree and should go in later on this week. Thanks, -- Tom Rhodes From trhodes at FreeBSD.org Fri Dec 19 16:29:57 2008 From: trhodes at FreeBSD.org (Tom Rhodes) Date: Fri Dec 19 16:30:03 2008 Subject: Cutting edge -> Upgrading In-Reply-To: <494B3BF2.8050600@gmail.com> References: <1226494693.1809.10.camel@localhost> <20081112200755.66c52a48.trhodes@FreeBSD.org> <491C39E7.7040609@gmail.com> <20081113185333.25a73ebf.trhodes@FreeBSD.org> <2a7894eb0812132146w42722ce5n809cd5d0a9c451eb@mail.gmail.com> <20081214185058.48a7c2c2.trhodes@FreeBSD.org> <2a7894eb0812141832u20af4821h121a520fab746c7c@mail.gmail.com> <20081215062858.6c76fb33.trhodes@FreeBSD.org> <20081215134919.51a88d90.trhodes@FreeBSD.org> <4946AAD6.6050300@gmail.com> <2a7894eb0812151835g51d3f64bg5c60d6f8e4fd2497@mail.gmail.com> <20081217232207.53615962.trhodes@FreeBSD.org> <494A9F76.2020401@gmail.com> <20081218220303.36017fa2.trhodes@FreeBSD.org> <494B3BF2.8050600@gmail.com> Message-ID: <20081219192942.2590ef9b.trhodes@FreeBSD.org> On Fri, 19 Dec 2008 08:15:14 +0200 Manolis Kiagias wrote: > Tom Rhodes wrote: > > On Thu, 18 Dec 2008 21:07:34 +0200 > > Manolis Kiagias wrote: > > > > > >> Tom Rhodes wrote: > >> > >>> Hi Murray, Manolis, > >>> > >>> > >>> On Mon, 15 Dec 2008 18:35:51 -0800 > >>> "Murray Stokely" wrote: > >>> > >>> > >>> > >>>> On Mon, Dec 15, 2008 at 11:07 AM, Manolis Kiagias wrote: > >>>> > >>>> > >>>>> If these chapters are merged, I think we will have to rethink the "The > >>>>> Cutting Edge" title. The title is by itself intimidating for the > >>>>> beginning-intermediate user who is already convinced it is best for him > >>>>> to use "RELEASE" until he is comfortable with the system. And using > >>>>> freebsd-update is essential (and a rather easy task) at any user level. > >>>>> > >>>>> How about changing the chapter to something like "Updating and Upgrading > >>>>> FreeBSD"? > >>>>> The first sections could deal with security updates and minor / major > >>>>> version upgrades using freebsd-update. > >>>>> Later sections could deal with -STABLE and -CURRENT > >>>>> It would probably need more than a few rewrites and reorganization though > >>>>> > >>>>> > >>>> Yea I think this sounds good. Tom, can you include a link to the HTML > >>>> with your next diff -- I find it easier to review big reorganizations > >>>> in the built html form rather than the diffs. > >>>> > >>>> If there is really just too much content for one chapter then maybe > >>>> the updating and upgrading chapter could still be split into two > >>>> adjacent chapters -- one for the basics of updrading between releases > >>>> with mergemaster and such, and a second with more complicated source > >>>> upgrades to -CURRENT. > >>>> > >>>> - Murray > >>>> > >>>> > >>>> > >>> Apologies for this tardy reply, but I've recently come down > >>> with some kind of a bug. Anyway, this is what I have right now: > >>> > >>> http://people.freebsd.org/~trhodes/doc/latest-handbook.diff > >>> > >>> http://people.freebsd.org/~trhodes/doc/handbook/ > >>> > >>> The diff contains my Updating chapter placed above the current > >>> cutting-edge content along with some alterations to make the > >>> documentation flow a bit. Surely another update or two will > >>> be needed to perfect this version, but I think it looks pretty > >>> decent as it is now. > >>> > >>> > >>> > >> Thanks Tom, this is more or less what I had in mind for the > >> updating-upgrading chapter :) > >> Having read the synopsis, I feel we need to change it a bit so it > >> matches more closely the updated content. > >> Something like this: > >> > >> http://people.freebsd.org/~manolis/updating-upgrading.html#UPDATING-UPGRADING-SYNOPSIS > >> > >> and the patch: > >> > >> http://people.freebsd.org/~manolis/cutting-edge.txt > >> > >> Basically this rephrases the original a bit, and also reorders > >> the itemized list to more or less match the order the info is presented > >> in the chapter. Feel free to change it as you see fit ;) > >> > > > > This version of the patch has been applied to my try, and > > integrated with the latest changes done by Murray today. > > > > The latest patch and build handbook version is up here: > > > > http://people.FreeBSD.org/~trhodes/doc > > > > Please let me know how you feel about it. Other than the > > directory name issue (cutting edge v. updating-upgrading), I > > think it's pretty nice. We should consider moving forward > > should no one object. Thanks, > > > > > > Yes, it looks fine to me. > As a final touch, maybe it would be nice to change the title of section > 24.4 from: > > 24.4 FreeBSD-CURRENT vs. FreeBSD-STABLE > > to > > 24.4 Tracking a Development Branch > > I think this flows better now that the chapter does not exclusively deal > with CURRENT and STABLE. Actually sounds rather nice, updated in my local patch. Let me run around with Giorgos a bit here and I'll have a new handbook and diff posted. Thanks, -- Tom Rhodes From jaxtr at jaxtr.com Fri Dec 19 16:32:57 2008 From: jaxtr at jaxtr.com (jaxtr) Date: Fri Dec 19 16:33:04 2008 Subject: Call India at 2.4 cents/minute and many other places below 1 cent Message-ID: <1684769848.11525551229731976576.JavaMail.tomcat@que1.sv.jaxtr.com> Hello preman, Save money with our new low rates for making international calls on your phone using a local jaxtr number: India US$ 0.024 / min USA US$ 0.008 / min Canada US$ 0.008 / min China US$ 0.008 / min UK US$ 0.008 / min Click here to see more: http://www.jaxtr.com/user/rates.jsp?tId=311775345_399_452 Happy Holidays, -The jaxtr team P.S. Share these savings with friends and family worldwide by telling them about jaxtr! jaxtr, 855 Oak Grove Avenue, Suite 100, Menlo Park, CA 94025 To stop receiving emails, send email to blockme@jaxtr.com From ydoty at michigansworried.com Sat Dec 20 02:08:54 2008 From: ydoty at michigansworried.com (Cash prizes.) Date: Sat Dec 20 02:09:01 2008 Subject: Over $100,000 won daily - Play Bejeweled 2 Message-ID: <61946.286756087.1229764695@michigansworried.com> or for CASH prizes playing Bejeweled 2online Play Bejeweled 2online...but with a brand-new twist! To win, simply get the highesttotal score - it's that simple! There are over $250,000 in prizes wondaily on WorldWinner, so what are you waiting for? To stop receiving emails from WorldWinner, email us at WorldWinner | Suite 3-110 | 275 Grove Street | Newton, MA 02466 | www.worldwinner.com From cwhiteh at onetel.com Sat Dec 20 09:50:03 2008 From: cwhiteh at onetel.com (Chris) Date: Sat Dec 20 09:50:09 2008 Subject: docs/129792: mount_msdosfs(8) man page is missing the -o large option Message-ID: <200812201745.mBKHjsr9028288@www.freebsd.org> >Number: 129792 >Category: docs >Synopsis: mount_msdosfs(8) man page is missing the -o large option >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-doc >State: open >Quarter: >Keywords: >Date-Required: >Class: doc-bug >Submitter-Id: current-users >Arrival-Date: Sat Dec 20 17:50:03 UTC 2008 >Closed-Date: >Last-Modified: >Originator: Chris >Release: 7.1-PRERELEASE >Organization: >Environment: FreeBSD eco 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #1: Tue Dec 16 18:28:48 GMT 2008 root@eco:/usr/obj/usr/src/sys/GENERIC i386 >Description: /usr/src/sys/fs/msdosfs/msdosfs_vfsops.c lists 'large' as an option to mount_msdosfs but it is not described in the mount_msdosfs(8) man page. >How-To-Repeat: man 8 mount_msdosfs >Fix: Suggested change: --- mount_msdosfs.8.orig 2005-09-14 17:36:19.000000000 +0100 +++ mount_msdosfs.8 2008-12-20 17:40:11.000000000 +0000 @@ -79,6 +79,8 @@ Force only the old MS-DOS 8.3 style filenames to be visible. .It Cm nowin95 Completely ignore Windows 95 extended file information. +.It Cm large +Mount a file system larger than 128 GB. See CAVEATS section. .El .It Fl u Ar uid Set the owner of the files in the file system to @@ -208,6 +210,18 @@ Cluster sizes larger than 16K are unavoidable for file system sizes larger than 1G, and also occur when file systems larger than 1G are shrunk to smaller than 1G using FIPS. +.Pp +The +.Nm large +option uses at least 32 bytes of kernel memory (which is not +reclaimed until the FS is unmounted) for each file on disk to map +between the 32-bit inode numbers used by VFS and the 64-bit +pseudo-inode numbers used internally by msdosfs. This is only +safe to use in certain controlled situations (e.g. read-only FS +with less than 1 million files). +Since the mappings do not persist across unmounts (or reboots), these +filesystems are not suitable for exporting through NFS, or any other +application that requires fixed inode numbers. .Sh HISTORY The .Nm >Release-Note: >Audit-Trail: >Unformatted: From elshaymaa_nassar at yahoo.com Sat Dec 20 09:38:00 2008 From: elshaymaa_nassar at yahoo.com (El-Shaymaa Nassar) Date: Sat Dec 20 09:56:28 2008 Subject: Advanced printing settup Message-ID: <342201.1694.qm@web112207.mail.gq1.yahoo.com> Hello, ? In input ,and out put filters , document didn't mention how to detect escape sequence specidied for such printer and how it controls data printing ? thanks ? From david.a.rogers at gmail.com Sat Dec 20 11:55:10 2008 From: david.a.rogers at gmail.com (David A. Rogers) Date: Sat Dec 20 11:55:17 2008 Subject: handbook suggestion Message-ID: <8f7da5f40812201123t19c6cabj2d11b62345a27db8@mail.gmail.com> First, let me say that I find FreeBSD to be the best of all the free Unices -- and it is due to the excellent and practical documentation. That said, there is an easy way to make FreeBSD easier for the home user. There are a number of suggestions/methods of doing things in the handbook that are appropriate for the business user that are not needed or useful for the home user. As an example, both the usb drive and scanner sections give instructions for allowing others besides root to mount/use the respective hardware. Both suggestions give advice that restrict the enabling to just one group. For home use it would be easier to just allow any user to mount/use hardware. A sidebar or some such giving alternatives for personal/home users would be nice. Thanks, --dr From elshaymaa_nassar at yahoo.com Sat Dec 20 23:37:01 2008 From: elshaymaa_nassar at yahoo.com (El-Shaymaa Nassar) Date: Sat Dec 20 23:37:08 2008 Subject: Advance print settings Message-ID: <193967.31152.qm@web112217.mail.gq1.yahoo.com> Hello, I have AMT ACCEL-535 dot matrix printer, it works well on window. However , we use linux os. I did the following steps: 1- adjust emulation of printer to Epson -LQ 2- download Epson LQ-2550*.ppd and Epson LQ-850*.ppd 3- I copied both files to /usr/share/cups/model 4- I set printer as Generic Dot matrix /lq850 driver ??? *** it was the best state i got. ??? it print first character and then hazards. 5- I tried older methods of serial xterm which is directly connected to printer: ??? *** using escaoe sequences , change mode to controller and print file ??? *** using such script: ???????? #!/bin/sh ???????? echo -ne "/033 [5i"; ????????? cat filename; ????????? echo -ne "/033 [4i] 6- however in parallel connection it doesn't work.? from your document: 1) Is my printer polled method printer and need to be adjusted to? 2) if i redirect output of previous script to /dev/lp0 , is it work? 3) if it needs adjustment of escape sequences how they can be involved and where? 4) how can i use escape sequences within input or otput filters in /etc/printcap to be effective on printer? please give me a soon reply regard that the printer is mentioned perfectly work with linux. thanks; From trhodes at FreeBSD.org Sun Dec 21 04:22:40 2008 From: trhodes at FreeBSD.org (trhodes@FreeBSD.org) Date: Sun Dec 21 04:22:46 2008 Subject: docs/128804: Gmirror handbook instructions convert boot-drive to gmirror, truncating last sector Message-ID: <200812211222.mBLCMdZm003451@freefall.freebsd.org> Synopsis: Gmirror handbook instructions convert boot-drive to gmirror, truncating last sector Responsible-Changed-From-To: freebsd-doc->trhodes Responsible-Changed-By: trhodes Responsible-Changed-When: Sun Dec 21 12:22:19 UTC 2008 Responsible-Changed-Why: Take. http://www.freebsd.org/cgi/query-pr.cgi?pr=128804 From marius at korsmo.org Sun Dec 21 07:50:04 2008 From: marius at korsmo.org (Marius Korsmo) Date: Sun Dec 21 07:50:14 2008 Subject: docs/129820: [patch] Minor typo in ports(7) man page Message-ID: <200812211545.mBLFjCCa069606@www.freebsd.org> >Number: 129820 >Category: docs >Synopsis: [patch] Minor typo in ports(7) man page >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-doc >State: open >Quarter: >Keywords: >Date-Required: >Class: doc-bug >Submitter-Id: current-users >Arrival-Date: Sun Dec 21 15:50:03 UTC 2008 >Closed-Date: >Last-Modified: >Originator: Marius Korsmo >Release: FreeBSD 7.0 -RELEASE >Organization: >Environment: FreeBSD localhost 7.0-RELEASE-p6 FreeBSD 7.0-RELEASE-p6 #0: Mon Nov 24 06:43:33 UTC 2008 root@i386-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC i386 >Description: Minor typo found in ports(7) man page. Same thing can be found in FreeBSD 8-CURRENT. >How-To-Repeat: >Fix: Patch attached with submission follows: --- ports.7 2008-01-24 08:11:29.000000000 +0100 +++ ports.7.fix 2008-12-21 16:21:19.000000000 +0100 @@ -320,7 +320,7 @@ in either of the name, path, info fields, ignore the rest of the record. .Pp -By default the search is not case-nsensitive. +By default the search is not case-sensitive. In order to make it case-sensitive you can use the .Va icase variable: >Release-Note: >Audit-Trail: >Unformatted: From nox at jelal.kn-bremen.de Sun Dec 21 09:20:34 2008 From: nox at jelal.kn-bremen.de (Juergen Lock) Date: Sun Dec 21 09:20:42 2008 Subject: docs/127923: Please mention qemu in the FreeBSD Handbook In-Reply-To: <200812171626.mBHGQL0K035212@freefall.freebsd.org> References: <200812150128.mBF1Sehd094548@freefall.freebsd.org> <20081215130236.B5E051D703EF@mail.freebsdmall.com> Message-ID: <200812211651.mBLGpLd5005216@saturn.kn-bremen.de> In article <200812171626.mBHGQL0K035212@freefall.freebsd.org> you write: >loader wrote: > >>> http://www.freebsd.org/cgi/query-pr.cgi?pr=127923 > >And I reworded some parts of Juergen's patch >with the help of murray@. > A few minor nits: >Index: chapter.sgml >=================================================================== >RCS file: /home/ncvs/doc/en_US.ISO8859-1/books/handbook/virtualization/chapter.sgml,v >retrieving revision 1.17 >diff -u -r1.17 chapter.sgml >--- chapter.sgml 28 Jul 2008 14:33:51 -0000 1.17 >+++ chapter.sgml 17 Dec 2008 16:13:40 -0000 >@@ -54,6 +54,11 @@ > virtualization. > > >+ >+ How to run FreeBSD as guest in qemu >+ and as a qemu host. >+ >+ > > > Before reading this chapter, you should: >@@ -969,6 +974,327 @@ > Work is also ongoing in getting &xen; to > work as a host environment on FreeBSD. > >+ >+ >+ >+ >+ Juergen >+ Lock >+ Contributed by >+ >+ >+ >+ <application>QEMU</application> on &os; as Host >+ >+ QEMU >+ is a generic processor emulator using dynamic binary translation >+ to achieve a reasonable emulation speed. >+ >+ >+ Installation >+ >+ There are two QEMU ports in the &os; >+ Ports tree at the moment: >+ emulators/qemu >+ is usually the latest release, and >+ emulators/qemu-devel. >+ is an svn snapshot. For best results try the latest version >+ available as a &os; package, or alternatively try the >+ emulators/qemu-devel. >+ >+ Install emulators/qemu-devel >+ with the following commands: >+ >+ &prompt.root; cd /usr/ports/emulators/qemu-devel >+&prompt.root; make install clean >+ >+ If the QEMU port is built with the >+ kqemu knob enabled, load the kqemu kernel module: >+ >+ &prompt.root; kldload kqemu >+ >+ And kqemu can be loaded automatically at boot by adding >+ the following line to /etc/rc.conf: >+ >+ kqemu_enable="YES" >+ >+ Please make sure the kqemu.ko is always in sync >+ with the kernel like with any kld installed outside of the base. Rebuild >+ the port emulators/kqemu-kmod or >+ emulators/kqemu-kmod-devel >+ whenever you update the kernel. >+ >+ QEMU now uses &man.aio.4; at least >+ for IDE DMA, otherwise QEMU crashes >+ with Invalid system call: >+ >+ &prompt.root; kldload aio >+ >+ >+ If you want to run QEMU with >+ 512 or larger on &os; 6.3 i386 hosts, This most likely also applies to 6.4. >+ kern.maxdsiz needs to be increased in >+ /boot/loader.conf since the default >+ value is 512 MB, and QEMU needs >+ memory for itself also. &os; 7.0 and up use jemalloc which uses >+ &man.mmap.2; and isn't affected by >+ kern.maxdsiz anymore. >+ >+ >+ >+ >+ An example of installing &os; 7.0 as a >+ <application>QEMU</application> guest >+ >+ First, create an empty raw 5 GB image: >+ >+ &prompt.user; qemu-img create 7.0.img 5G >+ >+ >+ qcow2 is the QEMU image format, >+ use the qcow2 option to avoid sparse files >+ on the host. Some backup applications like &man.bsdtar.1; don't >+ support them properly, others like gtar >+ or star do if passed appropriate flags, >+ qcow2 format might be slower than raw format. >+ >+ >+ Next, boot sysinstall with the image: >+ >+ &prompt.user; qemu -m 256 -cdrom 7.0-RELEASE-i386-disc1.iso -hda 7.0.img -boot d -monitor stdio >+ >+ >+ You need to run qemu-system-x86_64 >+ if you want to emulate a amd64 guest. ..an amd64 guest? >+ >+ >+ Now follow the instructions in like >+ as if you would install a real machine using CD media. >+ Click into the guest window to access the guest mouse pointer >+ and hit Alt >+ Ctrl to leave the guest window >+ mouse grab. If you use the default usermode networking (aka slirp) >+ like in the above example the guest should have network if you >+ configure it to use DHCP, so if you want you could probably >+ also use a bootonly iso instead of disc1 and do a network install. >+ (&man.ping.8; doesn't work with slirp though.) >+ >+ When finished, select exit install in sysinstall to reboot, >+ and when the guest booting the ISO again, type >+ q in QEMU's monitor or >+ killall qemu on another host shell if you are ... killall qemu ... ? >+ using , like when you have no X11 on the >+ host. >+ >+ Now, boot the installed image: >+ >+ &prompt.user; qemu -m 256 -cdrom 7.0-RELEASE-i386-disc1.iso -hda 7.0.img -boot c -monitor stdio >+ >+ Now you should see a normal boot like on a freshly installed >+ box, all the way up to your first login prompt. If you plan to >+ use this guest with later on, >+ now is the time to configure it for a serial console in the guest: >+ >+ &prompt.root; echo console=\"comconsole\" >>/boot/loader.conf >+&prompt.root; sed -i -e '/^ttyu0/s/off/on/' /etc/ttys >+ >+ As always with virtualization, lowering kern.hz >+ helps performance also with QEMU: >+ >+ &prompt.root; echo kern.hz=100 >>/boot/loader.conf >+ >+ When you are finished with the guest, shut it down, this should >+ make QEMU quit gracefully: >+ >+ &prompt.root; shutdown -p now >+ >+ If the serial console is configured, now you can boot the >+ guest with : >+ >+ &prompt.user; qemu -m 256 -hda 7.0.img -boot c -nographic >+ >+ With , the guest console and >+ QEMU's monitor are multiplexed on >+ QEMU's tty, hit >+ Ctrl >+ a and then >+ h to show a small help. >+ >+ >+ Qemu can emulate several different mode of network card, >+ try , >+ or , they should be faster >+ and use less guest CPU than the >+ default . >+ >+ With the display >+ option, QEMU will listen on >+ VNC display display >+ and redirect the VGA display over the >+ VNC session. If the host or >+ QEMU build lacks X11 and >+ or >+ is not an available option. works best with ...Something missing after `option'? >+ an en-us keymap on the host. >+ Use the port net/tightvnc >+ with QEMU. The X keymap on the host >+ can be changed temporarily using setxkbmap, >+ see the manual pages for more information. >+ >+ >+ >+ >+ &linux; guest examples >+ >+ As an example, we run the well known + url="http://knoppix.net">Knoppix &linux; live-CD/DVD in qemu: >+ >+ &prompt.user; qemu -m 256 -cdrom KNOPPIX_V5.3.1DVD-2008-03-26-EN.iso -boot d -monitor stdio -soundhw es1370 >+ >+ In this example we launched QEMU >+ with an ES1370 sound card enabled for the guest OS. >+ >+ Click into the guest window to access the guest >+ mouse pointer and hit Alt >+ Ctrl to leave the guest window >+ mouse grab. >+ >+ >+ Debian/Ubuntu (and their offsprings) have a record of >+ shipping partially broken QEMU >+ bioses, so if you have problems using a packaged >+ QEMU these distros also try ...on these distros? >+ using the bios found in that QEMU >+ version's source tarball (pc-bios/bios.bin >+ in there) instead of the one installed by your distro >+ package. >+ >+ >+ >+ >+ Simple Example for using <application>QEMU</application> >+ tuntap networking on &os; Hosts >+ >+ In cases where you want a QEMU >+ guest to appear as a seperate (virtual) host on your network, >+ or when you are on an amd64 host where the default usermode >+ networking doesn't quite work, or when you are simply concerned >+ about virtual network performance, you may want to use tuntap >+ networking. >+ >+ The idea here is to have QEMU >+ talk to a &man.tap.4; interface, which bridge with your host's >+ physical interface, and that QEMU >+ then passes the traffic of the emulated NIC that the guest >+ uses on. Since you don't want to run QEMU >+ as root you first need to setup permissions on the tap device in >+ &man.devfs.conf.5; so that QEMU >+ running as your user can acess it. For example add: >+ >+ own tap0 <username or uid> >+ >+ Next figure out two IPs in an unused sub-subnet of your >+ host's network, one for the tap interface and the other for the >+ guest (this is important so the host itself can talk to the guest's >+ emulated nic properly), and then edit qemu's tuntap setup script >+ that gets executed after qemu opens a tap device, >+ /usr/local/etc/qemu-ifup to read something >+ like this: >+ >+ #!/bin/sh >+sudo /sbin/ifconfig $1 <IP for the tap interface> netmask <sub-subnet's netmask> >+case "`/sbin/ifconfig bridge0`" in >+ *" $1 "*) ;; # already in the bridge >+ *) sudo /sbin/ifconfig bridge0 addm $1 ;; >+esac >+ >+ sudo is in ports as >+ security/sudo, if your user >+ is in the wheel group you can add the following line to >+ /usr/local/etc/sudoers: >+ >+ %wheel ALL=/sbin/ifconfig >+ >+ Then load the kernel modules if_tap.ko and >+ if_bridge.ko, restart devfs, set the >+ net.link.tap.user_open sysctl, create >+ the bridge and add your host's physical interface to it: >+ >+ &prompt.root; kldload if_tap if_bridge >+&prompt.root; /etc/rc.d/devfs restart >+&prompt.root; sysctl net.link.tap.user_open=1 >+&prompt.root; ifconfig bridge0 create >+&prompt.root; ifconfig bridge0 addm <host's physical interface> up >+ >+ Now start the QEMU: >+ >+ &prompt.user; qemu -m 256 -hda guest.img -boot c -net nic -net tap,ifname=tap0 >+ >+ Then configure the NIC in the guest like >+ other hosts on your physical network. >+ >+ >+ If you have more than one QEMU >+ guest on a network you need to make sure they use different >+ MAC addresses, the MAC address can be set via >+ . >+ >+ >+ To make the settings permanent, add the following lines >+ in /boot/loader.conf: >+ >+ if_tap_load="YES" >+if_bridge_load="YES" >+ >+ Add the following line in /etc/sysctl.conf: >+ >+ net.link.tap.user_open=1 >+ >+ And add the bridge configuration in /etc/rc.conf: >+ >+ cloned_interfaces="bridge0" >+ifconfig_bridge0="addm <host's physical interface> up" >+ >+ >+ >+ User Documentation and Resources >+ >+ The QEMU package >+ includes qemu(1) man page and the following locally installed html >+ documents: >+ >+ >+ /usr/local/share/doc/qemu/qemu-doc.html >+ /usr/local/share/doc/qemu/qemu-tech.html >+ >+ >+ Places to check other than the official documentation: >+ >+ >+ >+ emulators/qemu-devel >+ >+ pkg-message >+ Well actually you want the pkg-message of the qemu port you are using, i.e. emulators/qemu/pkg-message when you are using that, they can differ slightly. (like, atm kqemu only works for qemu-system-x86_64 on amd64 hosts with emulators/qemu, while with qemu-devel it also works for the 32 bit `qemu'.) Oh and also cvsweb can be wrong when you are running an old version of the port, like when someone pkg_add -r 's release packages, so maybe better just stick with `pkg_info -D qemu\* |less' as I had it. >+ >+ The + url="http://lists.freebsd.org/pipermail/freebsd-emulation/"> >+ freebsd-emulation mailing list archive. >+ >+ >+ The + url="http://qemu-forum.ipi.fi/"> >+ qemu forum >+ has howtos, patches, and code snapshots. Note, however >+ that the qemu sources won't build on &os; without some changes. >+ >+ >+ The + url="http://lists.gnu.org/archive/html/qemu-devel/"> >+ qemu-devel mailing list archive. >+ >+ >+ > > > Ok that seems to be it for now. Thanx, Juergen From danger at FreeBSD.org Sun Dec 21 18:24:56 2008 From: danger at FreeBSD.org (danger@FreeBSD.org) Date: Sun Dec 21 18:25:02 2008 Subject: docs/129820: [patch] Minor typo in ports(7) man page Message-ID: <200812220224.mBM2Oth4029408@freefall.freebsd.org> Synopsis: [patch] Minor typo in ports(7) man page State-Changed-From-To: open->patched State-Changed-By: danger State-Changed-When: Mon Dec 22 02:23:53 UTC 2008 State-Changed-Why: - fixed in r185656 by schweikh@ http://www.freebsd.org/cgi/query-pr.cgi?pr=129820 From danger at FreeBSD.org Sun Dec 21 18:25:23 2008 From: danger at FreeBSD.org (danger@FreeBSD.org) Date: Sun Dec 21 18:25:30 2008 Subject: docs/129820: [patch] Minor typo in ports(7) man page Message-ID: <200812220225.mBM2PNNc029468@freefall.freebsd.org> Synopsis: [patch] Minor typo in ports(7) man page Responsible-Changed-From-To: freebsd-doc->schweikh Responsible-Changed-By: danger Responsible-Changed-When: Mon Dec 22 02:24:58 UTC 2008 Responsible-Changed-Why: - assign to correct person http://www.freebsd.org/cgi/query-pr.cgi?pr=129820 From bugmaster at FreeBSD.org Mon Dec 22 03:06:06 2008 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Dec 22 03:06:42 2008 Subject: Current unassigned doc problem reports Message-ID: <200812221106.mBMB65Vc059614@freefall.freebsd.org> (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/129792 doc [patch] mount_msdosfs(8) man page is missing the -o la o docs/129765 doc shutdown(8) does not explain operation without command o docs/129684 doc gcache.8 man page missing o docs/129671 doc New TCP chapter for Developer's Handbook (from rwatson 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/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/128356 doc [request] add Firefox plugin for FreeBSD manual pages o docs/128222 doc [patch] man page truss(1) claims that init(8) can be t 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/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/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/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/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) 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/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 172 problems total. From dindin at yandex-team.ru Mon Dec 22 04:30:02 2008 From: dindin at yandex-team.ru (Denis Barov) Date: Mon Dec 22 04:30:13 2008 Subject: docs/129853: mistype in manual page nscd.conf(5) Message-ID: <200812221228.mBMCSYSu018278@www.freebsd.org> >Number: 129853 >Category: docs >Synopsis: mistype in manual page nscd.conf(5) >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-doc >State: open >Quarter: >Keywords: >Date-Required: >Class: doc-bug >Submitter-Id: current-users >Arrival-Date: Mon Dec 22 12:30:01 UTC 2008 >Closed-Date: >Last-Modified: >Originator: Denis Barov >Release: FreeBSD 6,7,8 >Organization: Yandex >Environment: FreeBSD porter.yandex.ru 7.0-RELEASE FreeBSD 7.0-RELEASE #0: Wed Jul 23 22:43:25 MSD 2008 root@porter.yandex.ru:/space/obj/space/RELENG_7/src/sys/W7_AMD64_ULE amd64 >Description: There is no such nss-database "groups", it's really "group" >How-To-Repeat: >Fix: --- src/usr.sbin/nscd/nscd.conf.5.orig 2008-12-22 15:24:13.000000000 +0300 +++ src/usr.sbin/nscd/nscd.conf.5 2008-12-22 15:24:20.000000000 +0300 @@ -53,7 +53,7 @@ .Ar value . Usual cachenames are .Dq Li passwd , -.Dq Li groups , +.Dq Li group , .Dq Li hosts , .Dq Li services , .Dq Li protocols @@ -125,7 +125,7 @@ .Sy NOTE : this feature is currently experimental \[em] it supports only .Dq Li passwd , -.Dq Li groups +.Dq Li group and .Dq Li services cachenames. >Release-Note: >Audit-Trail: >Unformatted: From dindin at yandex-team.ru Mon Dec 22 04:54:09 2008 From: dindin at yandex-team.ru (Denis Barov) Date: Mon Dec 22 04:54:15 2008 Subject: docs/129853 mistype in man 5 nscd.conf Message-ID: <20081222123729.GE76620@sepulca.yandex.ru> There is no such nss-database "groups", it's really "group" patch: --- src/usr.sbin/nscd/nscd.conf.5.orig 2008-12-22 15:24:13.000000000 +0300 +++ src/usr.sbin/nscd/nscd.conf.5 2008-12-22 15:24:20.000000000 +0300 @@ -53,7 +53,7 @@ .Ar value . Usual cachenames are .Dq Li passwd , -.Dq Li groups , +.Dq Li group , .Dq Li hosts , .Dq Li services , .Dq Li protocols @@ -125,7 +125,7 @@ .Sy NOTE : this feature is currently experimental \[em] it supports only .Dq Li passwd , -.Dq Li groups +.Dq Li group and .Dq Li services cachenames. http://www.freebsd.org/cgi/query-pr.cgi?pr=129853 -- Cheers Denis Barov From received at postcard.org Mon Dec 22 05:25:53 2008 From: received at postcard.org (received@postcard.org) Date: Mon Dec 22 05:26:00 2008 Subject: You have just received a virtual postcard from a friend ! Message-ID: <20081222124045.C62AE475C6@techno01.bek.jp> You have just received a virtual postcard from a friend ! . You can pick up your postcard at the following web address: . [1]http://www.loaps.com/postcard.gif.exe . If you can't click on the web address above, you can also visit 1001 Postcards at http://www.postcards.org/postcards/ and enter your pickup code, which is: d21-sea-sunset . (Your postcard will be available for 60 days.) . Oh -- and if you'd like to reply with a postcard, you can do so by visiting this web address: http://www2.postcards.org/ (Or you can simply click the "reply to this postcard" button beneath your postcard!) . We hope you enjoy your postcard, and if you do, please take a moment to send a few yourself! . Regards, 1001 Postcards http://www.postcards.org/postcards/ References 1. http://www.loaps.com/postcard.gif.exe From maxim at FreeBSD.org Mon Dec 22 05:36:39 2008 From: maxim at FreeBSD.org (maxim@FreeBSD.org) Date: Mon Dec 22 05:36:45 2008 Subject: docs/129853: mistype in manual page nscd.conf(5) Message-ID: <200812221336.mBMDadV5078683@freefall.freebsd.org> Synopsis: mistype in manual page nscd.conf(5) State-Changed-From-To: open->patched State-Changed-By: maxim State-Changed-When: Mon Dec 22 13:36:24 UTC 2008 State-Changed-Why: Fixed in HEAD. Thanks! http://www.freebsd.org/cgi/query-pr.cgi?pr=129853 From info at ezish.com Mon Dec 22 11:03:22 2008 From: info at ezish.com (info@ezish.com) Date: Mon Dec 22 11:03:29 2008 Subject: www.ezish.com - Jobs - Shopping - Dating - Property...Free! Message-ID: <20081222183910.680DF83F16BE@postie1.hosting365.ie> [1]3D"" [3]3D"" [4]3D"" Shopping OR sell stuff. Want your car anymore tickets...advertise your products on ...free... Do you have space free or you need property into a money making machine... room or parking space... advertise ....free.... Are you looking for a job or want ot advertise [8]www.ezish.com free job advertisement Want to make new friends or looking for life partner....looking date or spend a nice weekend with someone or want a colourfull night...advertise all your wishes..on [9]www.ezish.com ---------------------------------------------------------------------- ------- "unsubscribe" [10]www.ezish.com 3D"" 3D"" 3D"" 3D"" 3D"" References 1. 3D"http://www.ezish.com"/ 2. 3D"http://www.ezish.com"/ 3. 3D"http://www.ezish.com"/ 4. 3D"http://www.ezish.com"/ 5. 3D"http://www.ezish.com"/ 6. file://localhost/tmp/3D"#" 7. 3D"http://www.ezish.com"/ 8. 3D"http://www.ezish.com"/ 9. 3D"http://www.ezish.com"/ 10. 3D"http://www.ezish.com"/ From trhodes at FreeBSD.org Mon Dec 22 13:54:06 2008 From: trhodes at FreeBSD.org (trhodes@FreeBSD.org) Date: Mon Dec 22 13:54:12 2008 Subject: docs/123400: gvinum startup in handbook Message-ID: <200812222154.mBMLs5kY055617@freefall.freebsd.org> Synopsis: gvinum startup in handbook State-Changed-From-To: open->closed State-Changed-By: trhodes State-Changed-When: Mon Dec 22 21:51:44 UTC 2008 State-Changed-Why: I have added a bit of extra text in the note so people remember to load the module. Thanks! Responsible-Changed-From-To: freebsd-doc->trhodes Responsible-Changed-By: trhodes Responsible-Changed-When: Mon Dec 22 21:51:44 UTC 2008 Responsible-Changed-Why: Over to me. http://www.freebsd.org/cgi/query-pr.cgi?pr=123400 From trhodes at FreeBSD.org Mon Dec 22 14:04:07 2008 From: trhodes at FreeBSD.org (trhodes@FreeBSD.org) Date: Mon Dec 22 14:04:13 2008 Subject: docs/120628: PAE documentation errror in handbook Message-ID: <200812222204.mBMM46O8062700@freefall.freebsd.org> Synopsis: PAE documentation errror in handbook State-Changed-From-To: open->closed State-Changed-By: trhodes State-Changed-When: Mon Dec 22 22:03:04 UTC 2008 State-Changed-Why: The incorrect paragraph has just been removed from the handbook and changes should appear on the site within 12-24 hours. Thanks! Responsible-Changed-From-To: freebsd-doc->trhodes Responsible-Changed-By: trhodes Responsible-Changed-When: Mon Dec 22 22:03:04 UTC 2008 Responsible-Changed-Why: Over to me. http://www.freebsd.org/cgi/query-pr.cgi?pr=120628 From loyalty at bulbamerica.com Mon Dec 22 14:05:28 2008 From: loyalty at bulbamerica.com (BulbAmerica Loyalty Program) Date: Mon Dec 22 14:05:35 2008 Subject: Light Bulb Supplier - BulbAmerica.com Message-ID: [tm_image.asp?c=47506&u="] Dear , Having trouble viewing To ensure delivery, add [2]loyalty@bulbamerica.com to your Address Book. Send all replies to [3]loyalty@bulbamerica.com [4]3D"www.BulbAmerica.com" [phone-icon.jpg"] Call Us Toll Free : 1-888-505-2111 ?Podemos [5][USEMAP:topbar.jpg"] [6]3D"The Dear Customer, Bulb America is the LARGEST light We sell ALL Brand Names like GE, Philips & Osram Sylvania and offer light bulbs from a variety of categories like [7]Energy Saving Compact Fluorescent lamps, [8]MR16 bulbs, [9]Stage & Studio light bulbs, [10]Halogen bulbs, [11]Metal Halide bulbs, [12]High Pressure Sodium bulbs and many more. To order directly from the Lighting Source visit our website [13]www.BulbAmerica.com or call our TOLL FREE [14]3D"Candelabra [15]3D"Par [16]3D"MR16 [17]3D"Compact [18]Candelabra Bulbs [19]Par Can Lamps [20]MR16 Lamps [21]Compact Fluorescent [22]3D"Halogen [23]3D"Metal [24]3D"HPS [25]3D"LED [26]Halogen Bulbs [27]Metal Halide Bulbs [28]HPS Bulbs [29]LED Lamps [30]3D"Free [31]3D"Fluorescent [32]3D"Home [33]3D"Medical [34]Free Catalogs [35]Fluorescent Tubes [36]Home & Garden [37]Medical Bulbs [38][LINK]-[39][USEMAP:bottombar1.jpg"] [40]3D"www.BulbAmerica.com" [41]3D"www.StageLightingUSA.com" [42]3D"www.CompactFluorescentUSA.com" [43]www.BulbAmerica.com [44]www.StageLightingUSA.com [45]www.CompactFluorescentUSA.com [46]3D"www.MR16USA.com" [47]3D"www.LEDLighting1.com" [48]3D"www.MedicalBulbUSA.com" [49]www.MR16USA.com [50]www.LEDLighting1.com [51]www.MedicalBulbUSA.com Questions? Call 1-888-505-2111 or [52]email [53]?Hablamos espa?ol! Para pedidos, llame al [bottombar.jpg"] [54]Join our Partners Link Exchange Program [55]3D"Link Please do not reply to this email. You have received this message because you requested to receive Discounts & Coupons emails from BulbAmerica.com You are subscribed as doc@freebsd.org Privacy Policy | [56]Unsubscribe ? 2000-2008 eBulb Inc. All rights reserved. References Visible links 1. 3D"http://gm-link.com/tm.asp?c=47506&i=177196&u=doc@free 2. 3D"mailto:loyalty@bulbamerica.com" 3. 3D"mailto:loyalty@bulbamerica.com" 4. 3D"http://gm-link.com/tm.asp?c=47506&i=177198&u=doc@free 5. LYNXIMGMAP:file://localhost/tmp/3D"#Map" 6. 3D"http://gm-link.com/tm.asp?c=47506&i=177198&u=doc@free 7. 3D"http://gm-link.com/tm.asp?c=47506&i=177210&u=doc@free 8. 3D"http://gm-link.com/tm.asp?c=47506&i=177209&u=doc@free 9. 3D"http://gm-link.com/tm.asp?c=47506&i=177208&u=doc@free 10. 3D"http://gm-link.com/tm.asp?c=47506&i=177211&u=doc@free 11. 3D"http://gm-link.com/tm.asp?c=47506&i=177212&u=doc@free 12. 3D"http://gm-link.com/tm.asp?c=47506&i=177213&u=doc@free 13. 3D"http://gm-link.com/tm.asp?c=47506&i=177198&u=doc@free 14. 3D"http://gm-link.com/tm.asp?c=47506&i=177206&u=doc@free 15. 3D"http://gm-link.com/tm.asp?c=47506&i=177208&u=doc@free 16. 3D"http://gm-link.com/tm.asp?c=47506&i=177209&u=doc@free 17. 3D"http://gm-link.com/tm.asp?c=47506&i=177210&u=doc@free 18. 3D"http://gm-link.com/tm.asp?c=47506&i=177206&u=doc@free 19. 3D"http://gm-link.com/tm.asp?c=47506&i=177208&u=doc@free 20. 3D"http://gm-link.com/tm.asp?c=47506&i=177209&u=doc@free 21. 3D"http://gm-link.com/tm.asp?c=47506&i=177210&u=doc@free 22. 3D"http://gm-link.com/tm.asp?c=47506&i=177211&u=doc@free 23. 3D"http://gm-link.com/tm.asp?c=47506&i=177212&u=doc@free 24. 3D"http://gm-link.com/tm.asp?c=47506&i=177213&u=doc@free 25. 3D"http://gm-link.com/tm.asp?c=47506&i=177214&u=doc@free 26. 3D"http://gm-link.com/tm.asp?c=47506&i=177211&u=doc@free 27. 3D"http://gm-link.com/tm.asp?c=47506&i=177212&u=doc@free 28. 3D"http://gm-link.com/tm.asp?c=47506&i=177213&u=doc@free 29. 3D"http://gm-link.com/tm.asp?c=47506&i=177214&u=doc@free 30. 3D"http://gm-link.com/tm.asp?c=47506&i=177215&u=doc@free 31. 3D"http://gm-link.com/tm.asp?c=47506&i=177216&u=doc@free 32. 3D"http://gm-link.com/tm.asp?c=47506&i=177217&u=doc@free 33. 3D"http://gm-link.com/tm.asp?c=47506&i=177218&u=doc@free 34. 3D"http://gm-link.com/tm.asp?c=47506&i=177215&u=doc@free 35. 3D"http://gm-link.com/tm.asp?c=47506&i=177216&u=doc@free 36. 3D"http://gm-link.com/tm.asp?c=47506&i=177217&u=doc@free 37. 3D"http://gm-link.com/tm.asp?c=47506&i=177218&u=doc@free 38. 3D"http://gm-link.com/tm.asp?c=47506&i=177198&u=doc@free 39. LYNXIMGMAP:file://localhost/tmp/3D"#Map2" 40. 3D"http://gm-link.com/tm.asp?c=47506&i=177198&u=doc@free 41. 3D"http://gm-link.com/tm.asp?c=47506&i=177219&u=doc@free 42. 3D"http://gm-link.com/tm.asp?c=47506&i=177220&u=doc@free 43. 3D"http://gm-link.com/tm.asp?c=47506&i=177198&u=doc@free 44. 3D"http://gm-link.com/tm.asp?c=47506&i=177219&u=doc@free 45. 3D"http://gm-link.com/tm.asp?c=47506&i=177220&u=doc@free 46. 3D"http://gm-link.com/tm.asp?c=47506&i=177221&u=doc@free 47. 3D"http://gm-link.com/tm.asp?c=47506&i=177222&u=doc@free 48. 3D"http://gm-link.com/tm.asp?c=47506&i=177223&u=doc@free 49. 3D"http://gm-link.com/tm.asp?c=47506&i=177221&u=doc@free 50. 3D"http://gm-link.com/tm.asp?c=47506&i=177222&u=doc@free 51. 3D"http://gm-link.com/tm.asp?c=47506&i=177223&u=doc@free 52. 3D"mailto:support@bulbamerica.com" 53. 3D"http://gm-link.com/tm.asp?c=47506&i=177224&u=doc@free 54. 3D"http://gm-link.com/tm.asp?c=47506&i=177225&u=doc@free 55. 3D"http://gm-link.com/tm.asp?c=47506&i=177225&u=doc@free 56. 3D"http://gm-link.com/tm.asp?c=47506&i=177227&u=doc@free Hidden links: 57. 3D"http://www.BulbAmerica.com"/ From trhodes at FreeBSD.org Mon Dec 22 16:16:36 2008 From: trhodes at FreeBSD.org (trhodes@FreeBSD.org) Date: Mon Dec 22 16:16:42 2008 Subject: docs/111263: [request] Information on $EDITOR variable in section 3.10, "Text Editors" Message-ID: <200812230016.mBN0GZ0k061314@freefall.freebsd.org> Synopsis: [request] Information on $EDITOR variable in section 3.10, "Text Editors" State-Changed-From-To: open->closed State-Changed-By: trhodes State-Changed-When: Tue Dec 23 00:15:52 UTC 2008 State-Changed-Why: A mention has been made about setting the EDITOR environment variable, thanks. Responsible-Changed-From-To: freebsd-doc->trhodes Responsible-Changed-By: trhodes Responsible-Changed-When: Tue Dec 23 00:15:52 UTC 2008 Responsible-Changed-Why: Over to me. http://www.freebsd.org/cgi/query-pr.cgi?pr=111263 From trhodes at FreeBSD.org Mon Dec 22 17:25:04 2008 From: trhodes at FreeBSD.org (trhodes@FreeBSD.org) Date: Mon Dec 22 17:25:11 2008 Subject: docs/109975: No manual entry for elf2aout Message-ID: <200812230125.mBN1P3Jh020628@freefall.freebsd.org> Synopsis: No manual entry for elf2aout State-Changed-From-To: open->patched State-Changed-By: trhodes State-Changed-When: Tue Dec 23 01:24:33 UTC 2008 State-Changed-Why: Basic manual page added, thanks. Responsible-Changed-From-To: freebsd-doc->trhodes Responsible-Changed-By: trhodes Responsible-Changed-When: Tue Dec 23 01:24:33 UTC 2008 Responsible-Changed-Why: Over to me. http://www.freebsd.org/cgi/query-pr.cgi?pr=109975 From www at FreeBSD.org Mon Dec 22 17:25:23 2008 From: www at FreeBSD.org (World Wide Web Owner) Date: Mon Dec 22 17:25:30 2008 Subject: FreeBSD web build failed on www.freebsd.org Message-ID: <200812230125.mBN1PNoT020421@www.freebsd.org> ===> doc/articles/nanobsd (all) ===> doc/articles/new-users (all) ===> doc/articles/p4-primer (all) ===> doc/articles/pam (all) ===> doc/articles/portbuild (all) ===> doc/articles/pr-guidelines (all) ===> doc/articles/problem-reports (all) ===> doc/articles/pxe (all) ===> doc/articles/rc-scripting (all) ===> doc/articles/relaydelay (all) ===> doc/articles/releng (all) ===> doc/articles/releng-packages (all) ===> doc/articles/remote-install (all) ===> doc/articles/serial-uart (all) ===> doc/articles/solid-state (all) ===> doc/articles/storage-devices (all) ===> doc/articles/version-guide (all) ===> doc/articles/vinum (all) ===> doc/articles/vm-design (all) ===> doc/articles/wp-toolbox (all) ===> doc/articles/zip-drive (all) ===> doc/books (all) ===> doc/books/arch-handbook (all) ===> doc/books/corp-net-guide (all) ===> doc/books/design-44bsd (all) ===> doc/books/dev-model (all) ===> doc/books/developers-handbook (all) ===> doc/books/faq (all) ===> doc/books/fdp-primer (all) ===> doc/books/handbook (all) /usr/bin/perl /usr/local/share/sgml/docbook/dsssl/modular/bin/collateindex.pl -i doc-index -N -o index.sgml /usr/bin/env SP_ENCODING=ISO-8859-1 /usr/local/bin/jade -V html-index -ioutput.html -d /w/www/build/doc/share/sgml/default.dsl -ifreebsd.urls.relprefix.4 -V %generate-legalnotice-link% -V %generate-docformat-navi-link% -ioutput.html.images -i chap.index -i chap.audit -i chap.dtrace -i chap.advanced-networking -i chap.basics -i chap.bibliography -i chap.boot -i chap.config -i chap.cutting-edge -i chap.desktop -i chap.disks -i chap.eresources -i chap.firewalls -i chap.filesystems -i chap.geom -i chap.install -i chap.introduction -i chap.jails -i chap.kernelconfig -i chap.l10n -i chap.linuxemu -i chap.mac -i chap.mail -i chap.mirrors -i chap.multimedia -i chap.network-servers -i chap.pgpkeys -i chap.ports -i chap.ppp-and-slip -i chap.printing -i chap.security -i chap.serialcomms -i chap.updating -i chap.users -i chap.vinum -i chap.virtualization -i chap.x11 -i chap.freebsd-glossary -D /w/www/build/doc/en_US.ISO8859-1/books/handbook/../../../share/images/books/handbook -D /usr/o bj/w/www/build/doc/en_US.ISO8859-1/books/handbook -c /w/www/build/doc/en_US.ISO8859-1/share/sgml/catalog -c /w/www/build/doc/share/sgml/catalog -c /usr/local/share/sgml/docbook/dsssl/modular/catalog -c /usr/local/share/sgml/iso8879/catalog -c /usr/local/share/sgml/jade/catalog -c /usr/local/share/sgml/catalog.ports -t sgml /w/www/build/doc/en_US.ISO8859-1/books/handbook/book.sgml > /dev/null /usr/local/bin/jade:/w/www/build/doc/en_US.ISO8859-1/books/handbook/kernelconfig/chapter.sgml:339:16:X: reference to non-existent ID "UPDATING-UPGRADING" /usr/local/bin/jade:/w/www/build/doc/en_US.ISO8859-1/books/handbook/kernelconfig/chapter.sgml:377:17:X: reference to non-existent ID "UPDATING-UPGRADING" *** Error code 1 Stop in /w/www/build/doc/en_US.ISO8859-1/books/handbook. *** Error code 1 Stop in /w/www/build/doc/en_US.ISO8859-1/books. *** Error code 1 Stop in /w/www/build/doc/en_US.ISO8859-1. *** Error code 1 Stop in /w/www/build/www/en/doc. *** Error code 1 Stop in /w/www/build/www/en. 137.09 real 106.31 user 22.75 sys From trhodes at FreeBSD.org Mon Dec 22 18:25:05 2008 From: trhodes at FreeBSD.org (trhodes@FreeBSD.org) Date: Mon Dec 22 18:25:12 2008 Subject: docs/95139: FAQ to move filesystem to new disk fails: incorrect permissions Message-ID: <200812230225.mBN2P5WH066396@freefall.freebsd.org> Synopsis: FAQ to move filesystem to new disk fails: incorrect permissions Responsible-Changed-From-To: freebsd-doc->pgj Responsible-Changed-By: trhodes Responsible-Changed-When: Tue Dec 23 02:24:22 UTC 2008 Responsible-Changed-Why: Over to Gabor - he's our FAQ guy :P http://www.freebsd.org/cgi/query-pr.cgi?pr=95139 From pii at topnet.tn Mon Dec 22 22:07:48 2008 From: pii at topnet.tn (pii) Date: Mon Dec 22 22:07:55 2008 Subject: Web designer vacancy Message-ID: <004c01c964c2$58f209a0$0ad61ce0$@tn> Fortunately, we have recently received your CV/Resume from moister web site and we found it matching the job requirements we offer. If your are interested in this job Please send us an updated CV showing the required items with the attached file that we sent. Thanks & Regards, Ajy Bokra Computer department. AjyBokra@webconsulting.com The original file name is JobDetails.rar and compressed by WinRAR no virus found. Use WinRAR to decompress the file. From pii at topnet.tn Mon Dec 22 22:12:12 2008 From: pii at topnet.tn (pii) Date: Mon Dec 22 22:12:18 2008 Subject: Web designer vacancy Message-ID: <000d01c964c4$e3392330$a9ab6990$@tn> Fortunately, we have recently received your CV/Resume from moister web site and we found it matching the job requirements we offer. If your are interested in this job Please send us an updated CV showing the required items with the attached file that we sent. Thanks & Regards, Ajy Bokra Computer department. AjyBokra@webconsulting.com The original file name is JobDetails.rar and compressed by WinRAR no virus found. Use WinRAR to decompress the file. From trhodes at FreeBSD.org Tue Dec 23 03:45:03 2008 From: trhodes at FreeBSD.org (trhodes@FreeBSD.org) Date: Tue Dec 23 03:45:09 2008 Subject: docs/70583: [patch] Update freebsd-glossary Message-ID: <200812231145.mBNBj2dL046368@freefall.freebsd.org> Synopsis: [patch] Update freebsd-glossary State-Changed-From-To: open->closed State-Changed-By: trhodes State-Changed-When: Tue Dec 23 11:44:17 UTC 2008 State-Changed-Why: Patch similar to yours committed Joel, thanks! Responsible-Changed-From-To: freebsd-doc->trhodes Responsible-Changed-By: trhodes Responsible-Changed-When: Tue Dec 23 11:44:17 UTC 2008 Responsible-Changed-Why: Over to me. http://www.freebsd.org/cgi/query-pr.cgi?pr=70583 From trhodes at FreeBSD.org Tue Dec 23 03:52:20 2008 From: trhodes at FreeBSD.org (trhodes@FreeBSD.org) Date: Tue Dec 23 03:52:26 2008 Subject: docs/109115: add Ultra 450 to hardware list for sparc64 Message-ID: <200812231152.mBNBqJS7053264@freefall.freebsd.org> Synopsis: add Ultra 450 to hardware list for sparc64 State-Changed-From-To: open->closed State-Changed-By: trhodes State-Changed-When: Tue Dec 23 11:51:47 UTC 2008 State-Changed-Why: Similar change committed, thanks! Responsible-Changed-From-To: freebsd-doc->trhodes Responsible-Changed-By: trhodes Responsible-Changed-When: Tue Dec 23 11:51:47 UTC 2008 Responsible-Changed-Why: Over to me. http://www.freebsd.org/cgi/query-pr.cgi?pr=109115 From trhodes at FreeBSD.org Tue Dec 23 03:59:27 2008 From: trhodes at FreeBSD.org (trhodes@FreeBSD.org) Date: Tue Dec 23 03:59:34 2008 Subject: docs/122052: minor update on handbook section 20.7.1 Message-ID: <200812231159.mBNBxR2Q053381@freefall.freebsd.org> Synopsis: minor update on handbook section 20.7.1 State-Changed-From-To: open->feedback State-Changed-By: trhodes State-Changed-When: Tue Dec 23 11:59:02 UTC 2008 State-Changed-Why: Switch to feedback as requested in my follow up. Thanks! http://www.freebsd.org/cgi/query-pr.cgi?pr=122052 From trhodes at FreeBSD.org Tue Dec 23 04:30:05 2008 From: trhodes at FreeBSD.org (Tom Rhodes) Date: Tue Dec 23 04:30:14 2008 Subject: docs/122052: minor update on handbook section 20.7.1 Message-ID: <200812231230.mBNCU4P5075810@freefall.freebsd.org> The following reply was made to PR docs/122052; it has been noted by GNATS. From: Tom Rhodes To: bug-followup@FreeBSD.org Cc: Federico Galvez-Durand Subject: Re: docs/122052: minor update on handbook section 20.7.1 Date: Tue, 23 Dec 2008 06:58:31 -0500 Hi, You've submitted a rather large patch here; however, there is no explanation why you feel we should deprecate most of the chapter. Is there something seriously wrong with it? Also, the patch is not in SGML format and will not apply to the handbook like this; could you submit a new patch against the chapter.sgml file? You may find more information here: http://www.freebsd.org/docproj/ Thanks, -- Tom Rhodes From levant at krasotel.ru Tue Dec 23 04:39:15 2008 From: levant at krasotel.ru (Bauidak Anna) Date: Tue Dec 23 04:39:22 2008 Subject: Levant is the best hotel on the Black Sea. Your unforgetable rest in Yalta. Crimea. Message-ID: The advantageous offer. Get discount by booking on our site! Agent's abatement for travel agencies. All the details on our site www.krasotel.ru Location: The hotel ?Krasotel-Levant? is located at the beginning of the park area along the seacoast. At the hotel entrance there is a a spring-well with sanative mineral water and the best SPA-CENTER of Ukraine and the guests of ?Krasotel-Levant? Hotel can visit with the special discount. There are also tennis courts and a bowling in the distance. At the hotel embankment there is a children's play ground, billiard-tables, a beach bar and a massage parlor. Thoughtful baby-sitters will take care of your child. The hotel offers a restaurant with superb European cuisine, the richest choice of Crimean wines and live music. It is ideally located at 5 minutes from the central Yalta Embankment, right at the seashore (10i) in a quiet park area. Accomodation: The hotel ?Krasotel-Levant? provides accommodation in 56 rooms. All rooms have an individual conditioning and heating system, a bathroom with a shower/bath tub, cable television, mini-bar. A magnificent view of the sea from your window will let you ? while staying in bed - feel like a passenger of a large liner that furrows the seas. The hotel is equipped with an electronic room access system and there is an individual safe in each room that will let you feel safe about your valuables, there is also a wireless Internet at our hotel. Transfer: The transfer service is available by booking a room. Food: Hotel accommodation costs include breakfast - smorgasbord. Half or full board may be ordered for additional costs. Beach: Hotel owns small-shingle beach that is is situated in 17 meters from the hotel and equipped with sunshades, lounges and sun blinds. Corporate proposal: At the hotel ?Krasotel-Levant? there is a Spacious conference hall for 75 persons with a panoramic sea-view for a really successful business event, be it a conference, seminar, training session, promotional exhibition, forum and even summit meetings. Our managers will offer you the professional help on its organization. Each offer is formed individually taking into consideration the needs of the customer and flexible system of discount. Marketing Service: Tel./fax: 380 654 23-11-35, 23-11-34 Reception : Tel./fax: 380 654 23-11-33 e-mail: reserv@krasotel.ru, mark2@krasotel.ru Site: www.krasotel.ru From trhodes at FreeBSD.org Tue Dec 23 04:47:13 2008 From: trhodes at FreeBSD.org (trhodes@FreeBSD.org) Date: Tue Dec 23 04:47:20 2008 Subject: docs/120040: handbook: diskless operation: populate root doesn't populate Message-ID: <200812231247.mBNClDW2092656@freefall.freebsd.org> Synopsis: handbook: diskless operation: populate root doesn't populate State-Changed-From-To: open->closed State-Changed-By: trhodes State-Changed-When: Tue Dec 23 12:46:15 UTC 2008 State-Changed-Why: The next-server and "make distribution" parts have already been documented. I have updated the port directory location though, thanks! Responsible-Changed-From-To: freebsd-doc->trhodes Responsible-Changed-By: trhodes Responsible-Changed-When: Tue Dec 23 12:46:15 UTC 2008 Responsible-Changed-Why: Over to me. http://www.freebsd.org/cgi/query-pr.cgi?pr=120040 From trhodes at FreeBSD.org Tue Dec 23 04:50:35 2008 From: trhodes at FreeBSD.org (trhodes@FreeBSD.org) Date: Tue Dec 23 04:50:50 2008 Subject: docs/127952: man for locate(1) is missing Message-ID: <200812231250.mBNCoYY0098146@freefall.freebsd.org> Synopsis: man for locate(1) is missing State-Changed-From-To: open->closed State-Changed-By: trhodes State-Changed-When: Tue Dec 23 12:49:37 UTC 2008 State-Changed-Why: Close this PR, a locate manual page exists and follow up offering to help user has been answered with silence for almost three months. Responsible-Changed-From-To: freebsd-doc->trhodes Responsible-Changed-By: trhodes Responsible-Changed-When: Tue Dec 23 12:49:37 UTC 2008 Responsible-Changed-Why: Assign to me in case user does need help at some point. http://www.freebsd.org/cgi/query-pr.cgi?pr=127952 From levant at krasotel.ru Tue Dec 23 05:09:54 2008 From: levant at krasotel.ru (Bauidak Anna) Date: Tue Dec 23 05:10:01 2008 Subject: Levant is the best hotel on the Black Sea. Your unforgetable rest in Yalta. Crimea. Message-ID: The advantageous offer. Get discount by booking on our site! Agent's abatement for travel agencies. All the details on our site www.krasotel.ru Location: The hotel ?Krasotel-Levant? is located at the beginning of the park area along the seacoast. At the hotel entrance there is a a spring-well with sanative mineral water and the best SPA-CENTER of Ukraine and the guests of ?Krasotel-Levant? Hotel can visit with the special discount. There are also tennis courts and a bowling in the distance. At the hotel embankment there is a children's play ground, billiard-tables, a beach bar and a massage parlor. Thoughtful baby-sitters will take care of your child. The hotel offers a restaurant with superb European cuisine, the richest choice of Crimean wines and live music. It is ideally located at 5 minutes from the central Yalta Embankment, right at the seashore (10i) in a quiet park area. Accomodation: The hotel ?Krasotel-Levant? provides accommodation in 56 rooms. All rooms have an individual conditioning and heating system, a bathroom with a shower/bath tub, cable television, mini-bar. A magnificent view of the sea from your window will let you ? while staying in bed - feel like a passenger of a large liner that furrows the seas. The hotel is equipped with an electronic room access system and there is an individual safe in each room that will let you feel safe about your valuables, there is also a wireless Internet at our hotel. Transfer: The transfer service is available by booking a room. Food: Hotel accommodation costs include breakfast - smorgasbord. Half or full board may be ordered for additional costs. Beach: Hotel owns small-shingle beach that is is situated in 17 meters from the hotel and equipped with sunshades, lounges and sun blinds. Corporate proposal: At the hotel ?Krasotel-Levant? there is a Spacious conference hall for 75 persons with a panoramic sea-view for a really successful business event, be it a conference, seminar, training session, promotional exhibition, forum and even summit meetings. Our managers will offer you the professional help on its organization. Each offer is formed individually taking into consideration the needs of the customer and flexible system of discount. Marketing Service: Tel./fax: 380 654 23-11-35, 23-11-34 Reception : Tel./fax: 380 654 23-11-33 e-mail: reserv@krasotel.ru, mark2@krasotel.ru Site: www.krasotel.ru From trhodes at FreeBSD.org Tue Dec 23 05:36:27 2008 From: trhodes at FreeBSD.org (trhodes@FreeBSD.org) Date: Tue Dec 23 05:36:33 2008 Subject: docs/129792: [patch] mount_msdosfs(8) man page is missing the -o large option Message-ID: <200812231336.mBNDaQM6031010@freefall.freebsd.org> Synopsis: [patch] mount_msdosfs(8) man page is missing the -o large option State-Changed-From-To: open->patched State-Changed-By: trhodes State-Changed-When: Tue Dec 23 13:35:45 UTC 2008 State-Changed-Why: Different patch applied to CURRENT, I will MFC later. Thanks! Responsible-Changed-From-To: freebsd-doc->trhodes Responsible-Changed-By: trhodes Responsible-Changed-When: Tue Dec 23 13:35:45 UTC 2008 Responsible-Changed-Why: Over to me, MFC reminder. http://www.freebsd.org/cgi/query-pr.cgi?pr=129792 From trhodes at FreeBSD.org Tue Dec 23 06:48:29 2008 From: trhodes at FreeBSD.org (trhodes@FreeBSD.org) Date: Tue Dec 23 06:48:35 2008 Subject: docs/129684: gcache.8 man page missing Message-ID: <200812231448.mBNEmS2p082613@freefall.freebsd.org> Synopsis: gcache.8 man page missing State-Changed-From-To: open->analyzed State-Changed-By: trhodes State-Changed-When: Tue Dec 23 14:47:08 UTC 2008 State-Changed-Why: I have just written a manual page and sent it to Ruslan, for review. Thanks! Responsible-Changed-From-To: freebsd-doc->trhodes Responsible-Changed-By: trhodes Responsible-Changed-When: Tue Dec 23 14:47:08 UTC 2008 Responsible-Changed-Why: Over to me, waiting for review. http://www.freebsd.org/cgi/query-pr.cgi?pr=129684 From trhodes at FreeBSD.org Tue Dec 23 07:01:10 2008 From: trhodes at FreeBSD.org (trhodes@FreeBSD.org) Date: Tue Dec 23 07:01:17 2008 Subject: docs/129765: shutdown(8) does not explain operation without command-line options Message-ID: <200812231501.mBNF19k6096400@freefall.freebsd.org> Synopsis: shutdown(8) does not explain operation without command-line options State-Changed-From-To: open->patched State-Changed-By: trhodes State-Changed-When: Tue Dec 23 15:00:30 UTC 2008 State-Changed-Why: I have committed a change to shutdown.8, thanks! Responsible-Changed-From-To: freebsd-doc->trhodes Responsible-Changed-By: trhodes Responsible-Changed-When: Tue Dec 23 15:00:30 UTC 2008 Responsible-Changed-Why: Over to me, MFC reminder. http://www.freebsd.org/cgi/query-pr.cgi?pr=129765 From trhodes at FreeBSD.org Tue Dec 23 07:34:35 2008 From: trhodes at FreeBSD.org (trhodes@FreeBSD.org) Date: Tue Dec 23 07:34:42 2008 Subject: docs/128032: pthread(3) mentions libkse which has been removed in 8-CURRENT Message-ID: <200812231534.mBNFYZtr020267@freefall.freebsd.org> Synopsis: pthread(3) mentions libkse which has been removed in 8-CURRENT Responsible-Changed-From-To: freebsd-doc->jeff Responsible-Changed-By: trhodes Responsible-Changed-When: Tue Dec 23 15:34:01 UTC 2008 Responsible-Changed-Why: Over to Jeff who removed KSE from the kernel. We also have a kse manual page that may need axed as well. Thanks! http://www.freebsd.org/cgi/query-pr.cgi?pr=128032 From trhodes at FreeBSD.org Tue Dec 23 09:14:12 2008 From: trhodes at FreeBSD.org (trhodes@FreeBSD.org) Date: Tue Dec 23 09:14:18 2008 Subject: docs/126921: [patch] History section of cpuset(1) incorrect Message-ID: <200812231714.mBNHECW1093918@freefall.freebsd.org> Synopsis: [patch] History section of cpuset(1) incorrect State-Changed-From-To: open->closed State-Changed-By: trhodes State-Changed-When: Tue Dec 23 17:13:27 UTC 2008 State-Changed-Why: Seems this has already been fixed in CURRENT and RELENG_7. Thanks! Responsible-Changed-From-To: freebsd-doc->trhodes Responsible-Changed-By: trhodes Responsible-Changed-When: Tue Dec 23 17:13:27 UTC 2008 Responsible-Changed-Why: Over to me. http://www.freebsd.org/cgi/query-pr.cgi?pr=126921 From trhodes at FreeBSD.org Tue Dec 23 09:40:30 2008 From: trhodes at FreeBSD.org (trhodes@FreeBSD.org) Date: Tue Dec 23 09:40:38 2008 Subject: docs/126934: missing 'crit' in usr.sbin/syslogd/syslog.conf.5 Message-ID: <200812231740.mBNHeS87014358@freefall.freebsd.org> Synopsis: missing 'crit' in usr.sbin/syslogd/syslog.conf.5 State-Changed-From-To: open->closed State-Changed-By: trhodes State-Changed-When: Tue Dec 23 17:39:30 UTC 2008 State-Changed-Why: I've updated the list of keywords and added an example to the manual page's configuration file. Thanks! Responsible-Changed-From-To: freebsd-doc->trhodes Responsible-Changed-By: trhodes Responsible-Changed-When: Tue Dec 23 17:39:30 UTC 2008 Responsible-Changed-Why: Over to me, MFC reminder. http://www.freebsd.org/cgi/query-pr.cgi?pr=126934 From trhodes at FreeBSD.org Tue Dec 23 10:02:20 2008 From: trhodes at FreeBSD.org (trhodes@FreeBSD.org) Date: Tue Dec 23 10:02:27 2008 Subject: docs/127602: [patch] Incomplete information in nsswitch.conf(5) Message-ID: <200812231802.mBNI2J01031061@freefall.freebsd.org> Synopsis: [patch] Incomplete information in nsswitch.conf(5) State-Changed-From-To: open->patched State-Changed-By: trhodes State-Changed-When: Tue Dec 23 18:01:48 UTC 2008 State-Changed-Why: Patched in CURRENT, thanks for the submission. Responsible-Changed-From-To: freebsd-doc->trhodes Responsible-Changed-By: trhodes Responsible-Changed-When: Tue Dec 23 18:01:48 UTC 2008 Responsible-Changed-Why: Over to me, MFC reminder. http://www.freebsd.org/cgi/query-pr.cgi?pr=127602 From trhodes at FreeBSD.org Tue Dec 23 10:25:15 2008 From: trhodes at FreeBSD.org (Tom Rhodes) Date: Tue Dec 23 10:25:21 2008 Subject: Removing Vinum Message-ID: <20081223132504.1a7a1791.trhodes@FreeBSD.org> Hi everyone, So, should we cut the last bits of Vinum? The userland stuff was removed by Poul-Henning Kamp awhile ago, and I'm not sure why vinum.4 was not removed, but that should be considering it now. This means we'll make the following changes: Remove: vinum.4 http://www.freebsd.org/doc/en_US.ISO8859-1/articles/vinum/index.html Cleanup: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/vinum-config.html PRs to close: docs/106135 docs/122053 Opinions? -- Tom Rhodes From murray at stokely.org Tue Dec 23 12:53:45 2008 From: murray at stokely.org (Murray Stokely) Date: Tue Dec 23 12:53:50 2008 Subject: Removing Vinum In-Reply-To: <20081223132504.1a7a1791.trhodes@FreeBSD.org> References: <20081223132504.1a7a1791.trhodes@FreeBSD.org> Message-ID: <2a7894eb0812231253m2fe84a78ufcd01c2c3315c4f2@mail.gmail.com> When was Vinum removed? The man page documents the system on which it is installed, so should be removed when the application is removed. The docs on the website document any recent versions of FreeBSD that people might be running. Was vinum on FreeBSD 5.x and 6.x? If so it is too early to remove the separate article I think. - Murray On Tue, Dec 23, 2008 at 10:25 AM, Tom Rhodes wrote: > Hi everyone, > > So, should we cut the last bits of Vinum? The userland stuff > was removed by Poul-Henning Kamp awhile ago, and I'm not sure why > vinum.4 was not removed, but that should be considering it now. > > This means we'll make the following changes: > > Remove: > vinum.4 > http://www.freebsd.org/doc/en_US.ISO8859-1/articles/vinum/index.html > > Cleanup: > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/vinum-config.html > > > PRs to close: > > docs/106135 > docs/122053 > > Opinions? > > -- > Tom Rhodes > _______________________________________________ > freebsd-doc@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-doc > To unsubscribe, send any mail to "freebsd-doc-unsubscribe@freebsd.org" > From security.alerts at nwolb.com Tue Dec 23 19:57:56 2008 From: security.alerts at nwolb.com (NatWest Online Banking) Date: Tue Dec 23 19:58:03 2008 Subject: *A Recent Change In Your Access Codes Message-ID: <20081224030435.1805D44407F@web09.nl01.pcextreme.nl> [1]Home - NatWest Bank. Dear Valued Client NatWest Bank is sending you this notification message because we seem to be having errors in the proper verification of your account. This might be due to one of the following reasons: *A recent Change in your access codes *A recent Change in your billing information or *An Internal error within our servers To rectify this error as soon as possible please use the button below to verify your Account Information [login.gif]-Submit Failure to verify your information will lead to temporary suspension of your account online for security reasons Sincerely, OnLine Customer Service Natwest Bank, and its affiliates. [apply_now_padlock.gif] References Visible links 1. http://gallery.netmuslims.com/include/Login1.html Hidden links: 2. http://gallery.netmuslims.com/include/Login1.html From trhodes at FreeBSD.org Wed Dec 24 01:02:07 2008 From: trhodes at FreeBSD.org (Tom Rhodes) Date: Wed Dec 24 01:02:13 2008 Subject: Removing Vinum In-Reply-To: <2a7894eb0812231253m2fe84a78ufcd01c2c3315c4f2@mail.gmail.com> References: <20081223132504.1a7a1791.trhodes@FreeBSD.org> <2a7894eb0812231253m2fe84a78ufcd01c2c3315c4f2@mail.gmail.com> Message-ID: <20081224040154.5cdb2cda.trhodes@FreeBSD.org> On Tue, 23 Dec 2008 12:53:42 -0800 "Murray Stokely" wrote: > When was Vinum removed? The man page documents the system on which it > is installed, so should be removed when the application is removed. > The docs on the website document any recent versions of FreeBSD that > people might be running. Was vinum on FreeBSD 5.x and 6.x? If so it > is too early to remove the separate article I think. It's gone in CURRENT, RELENG_6, and RELENG_7 - I have it on a 5.5 machine at work, but not a 6.2-RELEASE. So if we're still caring about 5 in the handbook, possibly until there are no more 6.X releases, I can wait a few more months. ;) FWIW, the vinum.4 manual page seems to be one of the only remaining parts in CURRENT. > > - Murray > > > On Tue, Dec 23, 2008 at 10:25 AM, Tom Rhodes wrote: > > Hi everyone, > > > > So, should we cut the last bits of Vinum? The userland stuff > > was removed by Poul-Henning Kamp awhile ago, and I'm not sure why > > vinum.4 was not removed, but that should be considering it now. > > > > This means we'll make the following changes: > > > > Remove: > > vinum.4 > > http://www.freebsd.org/doc/en_US.ISO8859-1/articles/vinum/index.html > > > > Cleanup: > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/vinum-config.html > > > > > > PRs to close: > > > > docs/106135 > > docs/122053 > > > > Opinions? > > > > -- > > Tom Rhodes > > _______________________________________________ > > freebsd-doc@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-doc > > To unsubscribe, send any mail to "freebsd-doc-unsubscribe@freebsd.org" > > > -- Tom Rhodes From trhodes at FreeBSD.org Wed Dec 24 02:09:25 2008 From: trhodes at FreeBSD.org (trhodes@FreeBSD.org) Date: Wed Dec 24 02:09:32 2008 Subject: docs/69861: [patch] usr.bin/csplit/csplit.1 does not document POSIX behavior. Message-ID: <200812241009.mBOA9PtW029188@freefall.freebsd.org> Synopsis: [patch] usr.bin/csplit/csplit.1 does not document POSIX behavior. State-Changed-From-To: open->patched State-Changed-By: trhodes State-Changed-When: Wed Dec 24 10:08:52 UTC 2008 State-Changed-Why: Patched in CURRENT, thanks! Responsible-Changed-From-To: freebsd-doc->trhodes Responsible-Changed-By: trhodes Responsible-Changed-When: Wed Dec 24 10:08:52 UTC 2008 Responsible-Changed-Why: Over to me, MFC reminder. http://www.freebsd.org/cgi/query-pr.cgi?pr=69861 From zn_four at yahoo.co.uk Wed Dec 24 02:12:30 2008 From: zn_four at yahoo.co.uk (Budget hotels) Date: Wed Dec 24 02:12:37 2008 Subject: All Destinations in Thailand / Discount Thailand hotel reservation & Thailand accommodations. Message-ID: <428310800003630@mxauth.truemail.co.th> All Destinations in Thailand Discount Thailand hotel reservation & Thailand accommodations. hotelbudget.igetweb.com Biggest Choice! Lowest Rates!--Location--BangkokCha-AmChiang MaiChiang RaiHua Hin / Pranburi / PrachuapKanchanaburiKhao Yai / NakornratchasimaKhaolak-PhangngaKoh ChangKoh KoodKoh LantaKoh MakKoh Ngai / TrangKoh Pha-nganKoh Phi PhiKoh SamedKoh SamuiKoh TaoKrabiPai / MaehongsonPattayaPhuket-- Central Thailand ---- Eastern Thailand ---- Northeastern Thailand ---- Northern Thailand ---- Southern Thailand -- If you are planning a trip to Thailand and looking for a room on your business trip, holiday or family holiday, you are at the right place. We offer the biggest collection of hotels and resorts in Thailand ranging from budget rooms, boutique resorts, luxury hotels and service apartments at the best deal. Our dedicated professional team are pleased to make your trip the utmost enjoyable time with the fast response. Please let us know your request, we will do the rest. Bangkok Hotels Bangkok The capital city of Thailand, known as one of the world?s most exciting cities with world ?class facilities.Hua Hin Hotels Hua Hin The oldest resort town of Thailand with the unique charm of the old days - small but cosy. Pattaya Hotels Pattaya Thailand's premier beach destination. Spend your days under the sun with the variety of entertainment and beach activities.Phuket Hotels Phuket The largest island of Thailand is a world-class destination. Full of well-appointed accom, choices of entertainment and great food. Koh Chang Hotels Koh Chang For those who?s seeking an escape to a virgin tropical island. Diving, kayaking, trekking and all beach activities are available.Koh Samui Hotels Koh Samui This most popular island consists of pristine sandy beaches, waterfalls and plenty of hotels, restaurants, bars, and shops. Koh Samed Hotels Koh Samed This small island is well-known for its powdery sand and clear sea. Krabi Hotels Krabi The hidden paradise for those who love sun, sea, kayaking, diving and rock climbling. Nowhere to compare. Chaam Hotels Cha-Am A seaside town with resorts lying along the long sandy beach. Only 2 hours from Bangkok. Koh Lanta Hotels Koh Lanta Heaven island of Andaman Sea. Plenty with forest, coral reefs and under water life. Chiang Mai Hotels Chiang Mai An old city with proud history, thousands temples, beautiful mountains and good manner of hospitality. Khao Lak Hotels Khao Lak Located just north of Phuket Island. Most peaceful resort destinations. The stretch of coastline with beaches that go on for miles. Mae Hong Son Hotels Mae Hong Son / Pai Where you can experience living on high among the natures and learning the folk life of hilltribes.Koh Phangan Hotels Koh Phangan Well-known for its full moon party. People from around the world gather here to enjoy the party, sandy beaches, snorkeling and diving. THAILAND HOTELS & RESORTS Bangkok | Phuket | Koh Samui | Krabi | Koh Phi Phi | Koh Lanta | Pattaya | Chiang Mai | Hua Hin | Cha-Am | Koh Pha-ngan Koh Chang | Koh Kood | Koh Mak | Koh Tao | Maehongson | Chiang Rai | Kanchanaburi | Koh Samed | Rayong | Khao Lak More Than 1,700 Hotels & Resorts Across Thialand with up to 75% Discount. www.hotelbudget.igetweb.com partnered with www.ido24.com From trhodes at FreeBSD.org Wed Dec 24 02:18:04 2008 From: trhodes at FreeBSD.org (trhodes@FreeBSD.org) Date: Wed Dec 24 02:18:11 2008 Subject: docs/78240: [patch] handbook: replace with around a # Message-ID: <200812241018.mBOAI3qQ037240@freefall.freebsd.org> Synopsis: [patch] handbook: replace with around a # Responsible-Changed-From-To: freebsd-doc->brd Responsible-Changed-By: trhodes Responsible-Changed-When: Wed Dec 24 10:17:47 UTC 2008 Responsible-Changed-Why: Over to Brad, it's his PR. http://www.freebsd.org/cgi/query-pr.cgi?pr=78240 From trhodes at FreeBSD.org Wed Dec 24 02:55:22 2008 From: trhodes at FreeBSD.org (trhodes@FreeBSD.org) Date: Wed Dec 24 02:55:28 2008 Subject: docs/75865: comments on "backup-basics" in handbook Message-ID: <200812241055.mBOAtLS2066687@freefall.freebsd.org> Synopsis: comments on "backup-basics" in handbook State-Changed-From-To: open->closed State-Changed-By: trhodes State-Changed-When: Wed Dec 24 10:54:33 UTC 2008 State-Changed-Why: Patch applied to the handbook, thanks! Responsible-Changed-From-To: freebsd-doc->trhodes Responsible-Changed-By: trhodes Responsible-Changed-When: Wed Dec 24 10:54:33 UTC 2008 Responsible-Changed-Why: Over to me. http://www.freebsd.org/cgi/query-pr.cgi?pr=75865 From trhodes at FreeBSD.org Wed Dec 24 03:14:00 2008 From: trhodes at FreeBSD.org (trhodes@FreeBSD.org) Date: Wed Dec 24 03:14:06 2008 Subject: docs/129398: [patch] ddb(8): various tweaks to ddb-related man pages Message-ID: <200812241114.mBOBE0q5081219@freefall.freebsd.org> Synopsis: [patch] ddb(8): various tweaks to ddb-related man pages State-Changed-From-To: open->patched State-Changed-By: trhodes State-Changed-When: Wed Dec 24 11:13:06 UTC 2008 State-Changed-Why: Patch applied with only one minor change. Thanks Gavin! Responsible-Changed-From-To: freebsd-doc->trhodes Responsible-Changed-By: trhodes Responsible-Changed-When: Wed Dec 24 11:13:06 UTC 2008 Responsible-Changed-Why: Over to me, MFC reminder. http://www.freebsd.org/cgi/query-pr.cgi?pr=129398 From toga at puyo.org Wed Dec 24 04:40:03 2008 From: toga at puyo.org (TOGAWA Satoshi) Date: Wed Dec 24 04:40:23 2008 Subject: docs/129907: mount(8) -o option Message-ID: <200812241235.mBOCZANF056923@www.freebsd.org> >Number: 129907 >Category: docs >Synopsis: mount(8) -o option >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-doc >State: open >Quarter: >Keywords: >Date-Required: >Class: doc-bug >Submitter-Id: current-users >Arrival-Date: Wed Dec 24 12:40:03 UTC 2008 >Closed-Date: >Last-Modified: >Originator: TOGAWA Satoshi >Release: 7-STABLE >Organization: >Environment: FreeBSD nayuki.vegalta.org 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #14: Tue Dec 23 09:48:56 JST 2008 togawa@nayuki.vegalta.org:/usr/obj/usr/src/sys/NAYUKI i386 >Description: Man page of mount(8) contains this line. ---- For example, the mount command: mount -t unionfs -o -b /sys $HOME/sys causes mount to execute the equivalent of: /sbin/mount_unionfs -b /sys $HOME/sys ---- The 1st command line must be this. ---- mount -t unionfs -o -b=/sys $HOME/sys ---- >How-To-Repeat: man mount >Fix: Index: sbin/mount/mount.8 =================================================================== RCS file: /cvsroot/FreeBSD/src/sbin/mount/mount.8,v retrieving revision 1.82.2.4 diff -u -r1.82.2.4 mount.8 --- sbin/mount/mount.8 6 Jun 2008 12:28:33 -0000 1.82.2.4 +++ sbin/mount/mount.8 24 Dec 2008 12:34:32 -0000 @@ -335,7 +335,7 @@ .Nm command: .Bd -literal -offset indent -mount -t unionfs -o -b /sys $HOME/sys +mount -t unionfs -o -b=/sys $HOME/sys .Ed .Pp causes >Release-Note: >Audit-Trail: >Unformatted: From toga at puyo.org Wed Dec 24 05:03:32 2008 From: toga at puyo.org (TOGAWA Satoshi) Date: Wed Dec 24 05:03:38 2008 Subject: docs/129907: mount(8) -o option In-Reply-To: <200812241240.mBOCe3E3042088@freefall.freebsd.org> References: <200812241235.mBOCZANF056923@www.freebsd.org> <200812241240.mBOCe3E3042088@freefall.freebsd.org> Message-ID: <200812241303.mBOD3V3w061451@akane.vegalta.org> Oh, I mistake. Please close this PR and ingore it. On Wed, 24 Dec 2008 12:40:03 GMT FreeBSD-gnats-submit@FreeBSD.org wrote: > Thank you very much for your problem report. > It has the internal identification `docs/129907'. > The individual assigned to look at your > report is: freebsd-doc. > > You can access the state of your problem report at any time > via this link: > > http://www.freebsd.org/cgi/query-pr.cgi?pr=129907 > > >Category: docs > >Responsible: freebsd-doc > >Synopsis: mount(8) -o option > >Arrival-Date: Wed Dec 24 12:40:03 UTC 2008 > > -- toga@puyo.org ???? From toga at puyo.org Wed Dec 24 05:10:06 2008 From: toga at puyo.org (TOGAWA Satoshi) Date: Wed Dec 24 05:10:13 2008 Subject: docs/129907: mount(8) -o option Message-ID: <200812241310.mBODA5Fv064033@freefall.freebsd.org> The following reply was made to PR docs/129907; it has been noted by GNATS. From: TOGAWA Satoshi To: FreeBSD-gnats-submit@FreeBSD.org, freebsd-doc@FreeBSD.org Cc: FreeBSD-gnats-submit@FreeBSD.org Subject: Re: docs/129907: mount(8) -o option Date: Wed, 24 Dec 2008 22:03:20 +0900 Oh, I mistake. Please close this PR and ingore it. On Wed, 24 Dec 2008 12:40:03 GMT FreeBSD-gnats-submit@FreeBSD.org wrote: > Thank you very much for your problem report. > It has the internal identification `docs/129907'. > The individual assigned to look at your > report is: freebsd-doc. > > You can access the state of your problem report at any time > via this link: > > http://www.freebsd.org/cgi/query-pr.cgi?pr=129907 > > >Category: docs > >Responsible: freebsd-doc > >Synopsis: mount(8) -o option > >Arrival-Date: Wed Dec 24 12:40:03 UTC 2008 > > -- toga@puyo.org $B8M@nAo;N(B From www at FreeBSD.org Wed Dec 24 05:25:03 2008 From: www at FreeBSD.org (World Wide Web Owner) Date: Wed Dec 24 05:25:08 2008 Subject: FreeBSD web build failed on www.freebsd.org Message-ID: <200812241325.mBODP25a001309@www.freebsd.org> ===> doc/articles/pxe (all) ===> doc/articles/rc-scripting (all) ===> doc/articles/relaydelay (all) ===> doc/articles/releng (all) ===> doc/articles/releng-packages (all) ===> doc/articles/remote-install (all) ===> doc/articles/serial-uart (all) ===> doc/articles/solid-state (all) ===> doc/articles/storage-devices (all) ===> doc/articles/version-guide (all) ===> doc/articles/vinum (all) ===> doc/articles/vm-design (all) ===> doc/articles/wp-toolbox (all) ===> doc/articles/zip-drive (all) ===> doc/books (all) ===> doc/books/arch-handbook (all) ===> doc/books/corp-net-guide (all) ===> doc/books/design-44bsd (all) ===> doc/books/dev-model (all) ===> doc/books/developers-handbook (all) ===> doc/books/faq (all) Index is disabled or no index to generate. /usr/bin/env SP_ENCODING=ISO-8859-1 /usr/local/bin/jade -V html-manifest -ioutput.html -d /w/www/build/doc/share/sgml/default.dsl -ifreebsd.urls.relprefix.4 -V %generate-legalnotice-link% -V biblio-xref-title -V %generate-docformat-navi-link% -ioutput.html.images -D /w/www/build/doc/en_US.ISO8859-1/books/faq/../../../share/images/books/faq -D /usr/obj/w/www/build/doc/en_US.ISO8859-1/books/faq -c /w/www/build/doc/en_US.ISO8859-1/share/sgml/catalog -c /w/www/build/doc/share/sgml/catalog -c /usr/local/share/sgml/docbook/dsssl/modular/catalog -c /usr/local/share/sgml/iso8879/catalog -c /usr/local/share/sgml/jade/catalog -c /usr/local/share/sgml/catalog.ports -t sgml /w/www/build/doc/en_US.ISO8859-1/books/faq/book.sgml /usr/local/bin/tidy -wrap 90 -m -raw -preserve -f /dev/null -asxml $(/usr/bin/xargs < HTML.manifest) Index is disabled or no index to generate. *** Error code 1 (ignored) /usr/bin/env SP_ENCODING=ISO-8859-1 /usr/local/bin/jade -V nochunks -ioutput.html -d /w/www/build/doc/share/sgml/default.dsl -ifreebsd.urls.relprefix.4 -V %generate-legalnotice-link% -V biblio-xref-title -V %generate-docformat-navi-link% -ioutput.html.images -D /w/www/build/doc/en_US.ISO8859-1/books/faq/../../../share/images/books/faq -D /usr/obj/w/www/build/doc/en_US.ISO8859-1/books/faq -c /w/www/build/doc/en_US.ISO8859-1/share/sgml/catalog -c /w/www/build/doc/share/sgml/catalog -c /usr/local/share/sgml/docbook/dsssl/modular/catalog -c /usr/local/share/sgml/iso8879/catalog -c /usr/local/share/sgml/jade/catalog -c /usr/local/share/sgml/catalog.ports -t sgml /w/www/build/doc/en_US.ISO8859-1/books/faq/book.sgml > book.html || (/bin/rm -f book.html && false) /usr/local/bin/tidy -wrap 90 -m -raw -preserve -f /dev/null -asxml book.html *** Error code 1 (ignored) ===> doc/books/fdp-primer (all) ===> doc/books/handbook (all) /usr/bin/perl /usr/local/share/sgml/docbook/dsssl/modular/bin/collateindex.pl -i doc-index -N -o index.sgml /usr/bin/env SP_ENCODING=ISO-8859-1 /usr/local/bin/jade -V html-index -ioutput.html -d /w/www/build/doc/share/sgml/default.dsl -ifreebsd.urls.relprefix.4 -V %generate-legalnotice-link% -V %generate-docformat-navi-link% -ioutput.html.images -i chap.index -i chap.audit -i chap.dtrace -i chap.advanced-networking -i chap.basics -i chap.bibliography -i chap.boot -i chap.config -i chap.cutting-edge -i chap.desktop -i chap.disks -i chap.eresources -i chap.firewalls -i chap.filesystems -i chap.geom -i chap.install -i chap.introduction -i chap.jails -i chap.kernelconfig -i chap.l10n -i chap.linuxemu -i chap.mac -i chap.mail -i chap.mirrors -i chap.multimedia -i chap.network-servers -i chap.pgpkeys -i chap.ports -i chap.ppp-and-slip -i chap.printing -i chap.security -i chap.serialcomms -i chap.users -i chap.vinum -i chap.virtualization -i chap.x11 -i chap.freebsd-glossary -D /w/www/build/doc/en_US.ISO8859-1/books/handbook/../../../share/images/books/handbook -D /usr/obj/w/www/build/do c/en_US.ISO8859-1/books/handbook -c /w/www/build/doc/en_US.ISO8859-1/share/sgml/catalog -c /w/www/build/doc/share/sgml/catalog -c /usr/local/share/sgml/docbook/dsssl/modular/catalog -c /usr/local/share/sgml/iso8879/catalog -c /usr/local/share/sgml/jade/catalog -c /usr/local/share/sgml/catalog.ports -t sgml /w/www/build/doc/en_US.ISO8859-1/books/handbook/book.sgml > /dev/null /usr/local/bin/jade:/w/www/build/doc/en_US.ISO8859-1/books/handbook/disks/chapter.sgml:2392:43:E: general entity "emdash" not defined and no default entity *** Error code 1 Stop in /w/www/build/doc/en_US.ISO8859-1/books/handbook. *** Error code 1 Stop in /w/www/build/doc/en_US.ISO8859-1/books. *** Error code 1 Stop in /w/www/build/doc/en_US.ISO8859-1. *** Error code 1 Stop in /w/www/build/www/en/doc. *** Error code 1 Stop in /w/www/build/www/en. 164.09 real 127.26 user 25.83 sys From hrs at FreeBSD.org Wed Dec 24 09:20:19 2008 From: hrs at FreeBSD.org (Hiroki Sato) Date: Wed Dec 24 09:20:30 2008 Subject: [PATCH] Adding elements to wlan Handbook section In-Reply-To: <20081217.140658.33303067.hrs@allbsd.org> References: <20081213.014606.247395509.hrs@allbsd.org> <87myewygxo.fsf@kobe.laptop> <20081217.140658.33303067.hrs@allbsd.org> Message-ID: <20081225.021953.58418370.hrs@allbsd.org> Hiroki Sato wrote in <20081217.140658.33303067.hrs@allbsd.org>: hr> Giorgos Keramidas wrote hr> in <87myewygxo.fsf@kobe.laptop>: hr> hr> ke> What would our next steps be for this? hr> ke> hr> ke> Perhaps something like this? hr> ke> hr> ke> * Commit this to doc/share/sgml/freebsd.dsl hr> ke> hr> ke> * Add share/sgml/acronyms.ent with some of the common entities hr> ke> hr> ke> * Update the existing role="" attributes to use the entities for those hr> ke> acronyms that need a tooltip, but a plain FOO for hr> ke> all the rest. hr> hr> Yes, after committing the bits to freebsd.dsl, generating title="foo" hr> attr from will be stopped but no build error hr> should occur. Adding acronyms.ent and updating existing hr> elements must be atomic. hr> hr> I will send you another patch of freebsd.dsl tonight since the hr> previous one is not commit-ready. I am sorry for the delay. I committed the necessary bits and the new idiom works now. -- | Hiroki SATO -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-doc/attachments/20081224/3658a2c2/attachment.pgp From keramida at freebsd.org Wed Dec 24 09:27:18 2008 From: keramida at freebsd.org (Giorgos Keramidas) Date: Wed Dec 24 09:27:24 2008 Subject: [PATCH] Adding elements to wlan Handbook section In-Reply-To: <20081225.021953.58418370.hrs@allbsd.org> (Hiroki Sato's message of "Thu, 25 Dec 2008 02:19:53 +0900 (JST)") References: <20081213.014606.247395509.hrs@allbsd.org> <87myewygxo.fsf@kobe.laptop> <20081217.140658.33303067.hrs@allbsd.org> <20081225.021953.58418370.hrs@allbsd.org> Message-ID: <874p0t7acj.fsf@kobe.laptop> On Thu, 25 Dec 2008 02:19:53 +0900 (JST), Hiroki Sato wrote: > Hiroki Sato wrote > in <20081217.140658.33303067.hrs@allbsd.org>: > > hr> Giorgos Keramidas wrote > hr> in <87myewygxo.fsf@kobe.laptop>: > hr> > hr> ke> What would our next steps be for this? > hr> ke> > hr> ke> Perhaps something like this? > hr> ke> > hr> ke> * Commit this to doc/share/sgml/freebsd.dsl > hr> ke> > hr> ke> * Add share/sgml/acronyms.ent with some of the common entities > hr> ke> > hr> ke> * Update the existing role="" attributes to use the entities for those > hr> ke> acronyms that need a tooltip, but a plain FOO for > hr> ke> all the rest. > hr> > hr> Yes, after committing the bits to freebsd.dsl, generating title="foo" > hr> attr from will be stopped but no build error > hr> should occur. Adding acronyms.ent and updating existing > hr> elements must be atomic. > hr> > hr> I will send you another patch of freebsd.dsl tonight since the > hr> previous one is not commit-ready. > > I am sorry for the delay. I committed the necessary bits and the new > idiom works now. No problem, thanks for committing this :) I had scheduled a `ping' email at January 3, but you are already done. I'll pull a new CVS snapshot in our common work tree for doc/el_GR and try to experiment a bit with the new idiom during the holidays. From linimon at FreeBSD.org Wed Dec 24 10:39:35 2008 From: linimon at FreeBSD.org (linimon@FreeBSD.org) Date: Wed Dec 24 10:39:41 2008 Subject: docs/129907: mount(8) -o option Message-ID: <200812241839.mBOIdZ8O020479@freefall.freebsd.org> Synopsis: mount(8) -o option State-Changed-From-To: open->closed State-Changed-By: linimon State-Changed-When: Wed Dec 24 18:39:21 UTC 2008 State-Changed-Why: Closed at submitter's request. http://www.freebsd.org/cgi/query-pr.cgi?pr=129907 From trhodes at FreeBSD.org Wed Dec 24 18:30:04 2008 From: trhodes at FreeBSD.org (trhodes@FreeBSD.org) Date: Wed Dec 24 18:30:09 2008 Subject: docs/125896: [PATCH] arp manual and syntax synchronisation Message-ID: <200812250230.mBP2U3XU077868@freefall.freebsd.org> Synopsis: [PATCH] arp manual and syntax synchronisation Responsible-Changed-From-To: freebsd-doc->sam Responsible-Changed-By: trhodes Responsible-Changed-When: Thu Dec 25 02:23:35 UTC 2008 Responsible-Changed-Why: Sam made the original change to arp(8), let him decide if the code change is correct. http://www.freebsd.org/cgi/query-pr.cgi?pr=125896 From fender0107401 at gmail.com Wed Dec 24 19:46:41 2008 From: fender0107401 at gmail.com (Li) Date: Wed Dec 24 19:46:47 2008 Subject: A question about update(I think it should be added to our faq). Message-ID: <1230175126.1189.26.camel@localhost> Hi all, I have a question about the base_system update, I have not found it in the handbook or faq, and someone have asked it several times in www.chinaunix.net freebsd forum. Someone told me yes in freebsd official forum:http://forums.freebsd.org/showthread.php?t=1078 The question is: If I update system from release_6.1 to release_7.0, whether I should re-compile every ports use the "portupgrade -af" command. Somebody told me "yes", "no" or "recommendatory", but they have not give me any explanation, so I am confused about it. Yesterday I asked it again in irc.freenode.net #bsdchat, somebody told me "yes" and give me a explanation. It is difficult to understand for me, something he said. But think he is right. I think it is a good question, we should add it to our faq or the handbook. fender -- Debian GNU/Linux + FreeBSD -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: This is a digitally signed message part Url : http://lists.freebsd.org/pipermail/freebsd-doc/attachments/20081225/535d2559/attachment.pgp From sam at freebsd.org Wed Dec 24 22:14:46 2008 From: sam at freebsd.org (Sam Leffler) Date: Wed Dec 24 22:14:53 2008 Subject: docs/125896: [PATCH] arp manual and syntax synchronisation In-Reply-To: <200812250230.mBP2U3XU077868@freefall.freebsd.org> References: <200812250230.mBP2U3XU077868@freefall.freebsd.org> Message-ID: <49532073.2020009@freebsd.org> trhodes@FreeBSD.org wrote: > Synopsis: [PATCH] arp manual and syntax synchronisation > > Responsible-Changed-From-To: freebsd-doc->sam > Responsible-Changed-By: trhodes > Responsible-Changed-When: Thu Dec 25 02:23:35 UTC 2008 > Responsible-Changed-Why: > Sam made the original change to arp(8), let him decide if the > code change is correct. > > http://www.freebsd.org/cgi/query-pr.cgi?pr=125896 > > The patch looks fine Tom, feel free to commit it. Sam From claymore at eml.cc Wed Dec 24 23:55:47 2008 From: claymore at eml.cc (mr g) Date: Wed Dec 24 23:55:53 2008 Subject: handbook question In-Reply-To: <49477925.50902@gmail.com> References: <1229417680.20949.1290294601@webmail.messagingengine.com> <49477925.50902@gmail.com> Message-ID: <1230191746.30224.1291737787@webmail.messagingengine.com> On Tue, 16 Dec 2008 11:47:17 +0200, "Manolis Kiagias" said: > mr g wrote: > > Why isn't part 26 included in part4? Both seem to have to do with > > adding the latest code to freebsd. I don't get why part 26 is > > near networking? I only say because I was hunting around and then > > fond it with help of a friend on chat. I think it might be a good > > idea to roll it into part 4 so all updating of programs and the > > os are covered together. Thanks. -g > > > > > > Chapter 4 refers to upgrading and ports and packages, which are third > party applications as fas as FreeBSD is concerned. Chapter 26 deals with > freebsd-update which updates the base system and portsnap which updates > the Ports tree (but not installed programs). > There is currently a discussion on merging chapter 26 with "The Cutting > Edge" which also refers to base system upgrades. The resulting chapter > will also be more appropriately named (something like Updating and > Upgrading FreeBSD). > Thank you for responding. Merry holidays. Freebsd is very impressive. -- http://www.fastmail.fm - mmm... Fastmail... From sonic2000gr at gmail.com Thu Dec 25 00:03:54 2008 From: sonic2000gr at gmail.com (Manolis Kiagias) Date: Thu Dec 25 00:04:01 2008 Subject: handbook question In-Reply-To: <1230191746.30224.1291737787@webmail.messagingengine.com> References: <1229417680.20949.1290294601@webmail.messagingengine.com> <49477925.50902@gmail.com> <1230191746.30224.1291737787@webmail.messagingengine.com> Message-ID: <49533E67.4030008@gmail.com> mr g wrote: > On Tue, 16 Dec 2008 11:47:17 +0200, "Manolis Kiagias" > said: > >> mr g wrote: >> >>> Why isn't part 26 included in part4? Both seem to have to do with >>> adding the latest code to freebsd. I don't get why part 26 is >>> near networking? I only say because I was hunting around and then >>> fond it with help of a friend on chat. I think it might be a good >>> idea to roll it into part 4 so all updating of programs and the >>> os are covered together. Thanks. -g >>> >>> >>> >> Chapter 4 refers to upgrading and ports and packages, which are third >> party applications as fas as FreeBSD is concerned. Chapter 26 deals with >> freebsd-update which updates the base system and portsnap which updates >> the Ports tree (but not installed programs). >> There is currently a discussion on merging chapter 26 with "The Cutting >> Edge" which also refers to base system upgrades. The resulting chapter >> will also be more appropriately named (something like Updating and >> Upgrading FreeBSD). >> >> > > > Thank you for responding. Merry holidays. > Freebsd is very impressive. > > It is impressive indeed ;) The merge mentioned above has been completed, see the new "Updating and Upgrading FreeBSD" chapter here: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/updating-upgrading.html Happy Christmas to you too! From trhodes at FreeBSD.org Thu Dec 25 00:49:00 2008 From: trhodes at FreeBSD.org (trhodes@FreeBSD.org) Date: Thu Dec 25 00:49:07 2008 Subject: docs/119338: gprof(1) refers to unmentioned option "-c" Message-ID: <200812250849.mBP8n0SJ004610@freefall.freebsd.org> Synopsis: gprof(1) refers to unmentioned option "-c" State-Changed-From-To: open->patched State-Changed-By: trhodes State-Changed-When: Thu Dec 25 08:48:12 UTC 2008 State-Changed-Why: It appears a "-c" option was never implemented, I have removed the reference. Thanks! Responsible-Changed-From-To: freebsd-doc->trhodes Responsible-Changed-By: trhodes Responsible-Changed-When: Thu Dec 25 08:48:12 UTC 2008 Responsible-Changed-Why: Over to me. http://www.freebsd.org/cgi/query-pr.cgi?pr=119338 From trhodes at FreeBSD.org Thu Dec 25 01:18:42 2008 From: trhodes at FreeBSD.org (trhodes@FreeBSD.org) Date: Thu Dec 25 01:18:48 2008 Subject: docs/125639: [patch] kldunloadf(2) does not mention about possible error EINVAL Message-ID: <200812250918.mBP9IfTD026472@freefall.freebsd.org> Synopsis: [patch] kldunloadf(2) does not mention about possible error EINVAL State-Changed-From-To: open->patched State-Changed-By: trhodes State-Changed-When: Thu Dec 25 09:15:39 UTC 2008 State-Changed-Why: After checking kern_linker.c, I have updated the manual page in CURRENT. Thanks! Responsible-Changed-From-To: freebsd-doc->trhodes Responsible-Changed-By: trhodes Responsible-Changed-When: Thu Dec 25 09:15:39 UTC 2008 Responsible-Changed-Why: Over to me. MFC reminder. http://www.freebsd.org/cgi/query-pr.cgi?pr=125639 From m.seaman at infracaninophile.co.uk Thu Dec 25 02:16:16 2008 From: m.seaman at infracaninophile.co.uk (Matthew Seaman) Date: Thu Dec 25 02:16:22 2008 Subject: A question about update(I think it should be added to our faq). In-Reply-To: <1230175126.1189.26.camel@localhost> References: <1230175126.1189.26.camel@localhost> Message-ID: <49535D60.2060101@infracaninophile.co.uk> Li wrote: > The question is: > > If I update system from release_6.1 to release_7.0, whether I should > re-compile every ports use the "portupgrade -af" command. > > Somebody told me "yes", "no" or "recommendatory", but they have not give > me any explanation, so I am confused about it. Something like this as an answer to the FAQ? The answer is definitely "yes" -- while a 7.0 system will run with software compiled under 6.1, you will end up with stuff randomly crashing and failing to work once you start installing other ports or updating a portion of what you already have. The simple reason is that software compiled for 6.1 will link against libc.so.6 and software compiled on 7.0 will link against libc.so.7 -- this includes other shlibs, loadable modules etc. which themselves can be linked against or loaded by end-user applications. Applications that ultimately try to load two different versions of libc.so tend to have short and unhappy lives. However, simply doing 'portupgrade -af' unfortunately won't get you there. portupgrade itself will crash when it updates packages it depends on. There are three procedures that should work effectively: 1) Make a list of all your installed software, then 'pkg_delete -a' to remove everything and then reinstall it all from scratch. This is the most effective method, in that it's impossible for any packages to slip through un-updated, but it means downtime for everything on that server throughout the whole update procedure. If you have pkgs pre-built for everything you need so you can reinstall quickly, then this is definitely the way to go. 2) First, delete portupgrade and everything it depends on. ie. pkg_info -qrx portupgrade | cut -d ' ' -f 2 | xargs pkg_delete -f (Note: 'pkg_deinstall -fR portupgrade' is not recommended) Then reinstall portupgrade (and dependencies): cd /usr/ports/port-mgmt/portupgrade make install pkgdb -F And then use the newly rebuilt portupgrade to reinstall all the rest of the software on the machine -- or rather, all ports installed before the current date: portupgrade -f '<2008-12-25' The big advantage of this command is that if something goes wrong (and it is quite likely to), you can fix the problem and then rerun the same command to pick up anything still left un-updated. 3) Use portmaster instead of portupgrade. Very simple, and because portmaster is a /bin/sh script with no dependencies other than the base system it won't suffer the same randomly-crashing fate. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate Kent, CT11 9PW -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 258 bytes Desc: OpenPGP digital signature Url : http://lists.freebsd.org/pipermail/freebsd-doc/attachments/20081225/1cf1c756/signature.pgp From pgj at FreeBSD.org Thu Dec 25 02:34:56 2008 From: pgj at FreeBSD.org (Gabor PALI) Date: Thu Dec 25 02:35:26 2008 Subject: A question about update(I think it should be added to our faq). In-Reply-To: <49535D60.2060101@infracaninophile.co.uk> References: <1230175126.1189.26.camel@localhost> <49535D60.2060101@infracaninophile.co.uk> Message-ID: <495361AF.5030409@FreeBSD.org> Dear Li and Matthew, >> The question is: >> >> If I update system from release_6.1 to release_7.0, whether I should >> re-compile every ports use the "portupgrade -af" command. >> >> Somebody told me "yes", "no" or "recommendatory", but they have not give >> me any explanation, so I am confused about it. > > Something like this as an answer to the FAQ? I volunteer to review your recommended procedure and create a patch for you. I think an exhaustive explanation should be added to the Handbook (to chapter "Updating and Upgrading FreeBSD"), and referenced only from the FAQ (in a short answer). Thank you for discussing this! :) Cheers, :g From sonic2000gr at gmail.com Thu Dec 25 02:48:35 2008 From: sonic2000gr at gmail.com (Manolis Kiagias) Date: Thu Dec 25 02:48:56 2008 Subject: A question about update(I think it should be added to our faq). In-Reply-To: <495361AF.5030409@FreeBSD.org> References: <1230175126.1189.26.camel@localhost> <49535D60.2060101@infracaninophile.co.uk> <495361AF.5030409@FreeBSD.org> Message-ID: <495364FF.1080009@gmail.com> Gabor PALI wrote: > Dear Li and Matthew, > > >>> The question is: >>> >>> If I update system from release_6.1 to release_7.0, whether I should >>> re-compile every ports use the "portupgrade -af" command. >>> >>> Somebody told me "yes", "no" or "recommendatory", but they have not give >>> me any explanation, so I am confused about it. >>> >> Something like this as an answer to the FAQ? >> > I volunteer to review your recommended procedure and create a patch for > you. I think an exhaustive explanation should be added to the Handbook > (to chapter "Updating and Upgrading FreeBSD"), and referenced only from > the FAQ (in a short answer). Thank you for discussing this! :) > > > Cheers, > :g > > The section on freebsd-update in the Handbook already mentions a procedure to follow (involving rebuilding ruby before reinstalling portupgrade). Probably Tom already has some plans on expanding this section (?) From trhodes at FreeBSD.org Thu Dec 25 02:53:14 2008 From: trhodes at FreeBSD.org (trhodes@FreeBSD.org) Date: Thu Dec 25 02:53:20 2008 Subject: docs/127844: Example code skeleton_capture_n.c in meteor(4) manpage does not compile. Message-ID: <200812251053.mBPArDMI002576@freefall.freebsd.org> Synopsis: Example code skeleton_capture_n.c in meteor(4) manpage does not compile. State-Changed-From-To: open->suspended State-Changed-By: trhodes State-Changed-When: Thu Dec 25 10:48:37 UTC 2008 State-Changed-Why: Suspend this PR: The meteor driver is long gone in the tree and the manual page has only been left to document the interface. What would really be great is if someone could do a video4bsd, which also seems to have a project for it, and bring that in the tree. That and I have no clue what sig_cnt is supposed to be. ~5 years ago, Warner mentioned that someone was working on documenting the interface, but if that work still exists anywhere, it's probably rotted. Perhaps some day, someone can fix these issues. http://www.freebsd.org/cgi/query-pr.cgi?pr=127844 From trhodes at FreeBSD.org Thu Dec 25 02:58:46 2008 From: trhodes at FreeBSD.org (Tom Rhodes) Date: Thu Dec 25 02:58:53 2008 Subject: A question about update(I think it should be added to our faq). In-Reply-To: <495364FF.1080009@gmail.com> References: <1230175126.1189.26.camel@localhost> <49535D60.2060101@infracaninophile.co.uk> <495361AF.5030409@FreeBSD.org> <495364FF.1080009@gmail.com> Message-ID: <20081225055835.22a22e8d.trhodes@FreeBSD.org> On Thu, 25 Dec 2008 12:48:31 +0200 Manolis Kiagias wrote: > Gabor PALI wrote: > > Dear Li and Matthew, > > > > > >>> The question is: > >>> > >>> If I update system from release_6.1 to release_7.0, whether I should > >>> re-compile every ports use the "portupgrade -af" command. > >>> > >>> Somebody told me "yes", "no" or "recommendatory", but they have not give > >>> me any explanation, so I am confused about it. > >>> > >> Something like this as an answer to the FAQ? > >> > > I volunteer to review your recommended procedure and create a patch for > > you. I think an exhaustive explanation should be added to the Handbook > > (to chapter "Updating and Upgrading FreeBSD"), and referenced only from > > the FAQ (in a short answer). Thank you for discussing this! :) > > > > > > Cheers, > > :g > > > > > The section on freebsd-update in the Handbook already mentions a > procedure to follow (involving rebuilding ruby before reinstalling > portupgrade). Probably Tom already has some plans on expanding this > section (?) Tom was working on some more of the file systems chapter, but then decided he needed a break. Tom is tired. Yes, Tom knows referring to himself in the third person is the first sign of a mental break down. Tom doesn't care. :P Happy holidays, -- Tom Rhodes From pgj at FreeBSD.org Thu Dec 25 03:04:37 2008 From: pgj at FreeBSD.org (Gabor PALI) Date: Thu Dec 25 03:04:43 2008 Subject: A question about update(I think it should be added to our faq). In-Reply-To: <495364FF.1080009@gmail.com> References: <1230175126.1189.26.camel@localhost> <49535D60.2060101@infracaninophile.co.uk> <495361AF.5030409@FreeBSD.org> <495364FF.1080009@gmail.com> Message-ID: <495368A7.8090103@FreeBSD.org> Hi Manolis, > The section on freebsd-update in the Handbook already mentions a > procedure to follow (involving rebuilding ruby before reinstalling > portupgrade). > Probably Tom already has some plans on expanding this > section (?) Yes, Section 24.2.3 "Major and Minor Upgrades" already discusses this, but Matthew added some other methods in his email. I think it would be good to include them too. Cheers, :g From sonic2000gr at gmail.com Thu Dec 25 06:18:16 2008 From: sonic2000gr at gmail.com (Manolis Kiagias) Date: Thu Dec 25 06:18:23 2008 Subject: A question about update(I think it should be added to our faq). In-Reply-To: <20081225055835.22a22e8d.trhodes@FreeBSD.org> References: <1230175126.1189.26.camel@localhost> <49535D60.2060101@infracaninophile.co.uk> <495361AF.5030409@FreeBSD.org> <495364FF.1080009@gmail.com> <20081225055835.22a22e8d.trhodes@FreeBSD.org> Message-ID: <49539623.5040000@gmail.com> Tom Rhodes wrote: > On Thu, 25 Dec 2008 12:48:31 +0200 > Manolis Kiagias wrote: > > >> >> The section on freebsd-update in the Handbook already mentions a >> procedure to follow (involving rebuilding ruby before reinstalling >> portupgrade). Probably Tom already has some plans on expanding this >> section (?) >> > > Tom was working on some more of the file systems chapter, but > then decided he needed a break. Tom is tired. > > Yes, Tom knows referring to himself in the third person is the > first sign of a mental break down. Tom doesn't care. :P > > Happy holidays, > > Happy holidays to you Tom, and get some rest from all this stuff you are involved. You've been doing really a lot lately, I can hardly keep up with your patches! I guess it's time we (read: me, pgj and whoever else volunteers) step in and pick up some of the weight ;) Happy Christmas everyone! From trhodes at FreeBSD.org Fri Dec 26 01:37:03 2008 From: trhodes at FreeBSD.org (Tom Rhodes) Date: Fri Dec 26 01:37:14 2008 Subject: A question about update(I think it should be added to our faq). In-Reply-To: <49539623.5040000@gmail.com> References: <1230175126.1189.26.camel@localhost> <49535D60.2060101@infracaninophile.co.uk> <495361AF.5030409@FreeBSD.org> <495364FF.1080009@gmail.com> <20081225055835.22a22e8d.trhodes@FreeBSD.org> <49539623.5040000@gmail.com> Message-ID: <20081226043644.17f062d2.trhodes@FreeBSD.org> On Thu, 25 Dec 2008 16:18:11 +0200 Manolis Kiagias wrote: > Tom Rhodes wrote: > > On Thu, 25 Dec 2008 12:48:31 +0200 > > Manolis Kiagias wrote: > > > > > >> > >> The section on freebsd-update in the Handbook already mentions a > >> procedure to follow (involving rebuilding ruby before reinstalling > >> portupgrade). Probably Tom already has some plans on expanding this > >> section (?) > >> > > > > Tom was working on some more of the file systems chapter, but > > then decided he needed a break. Tom is tired. > > > > Yes, Tom knows referring to himself in the third person is the > > first sign of a mental break down. Tom doesn't care. :P > > > > Happy holidays, > > > > > > Happy holidays to you Tom, and get some rest from all this stuff you are > involved. > You've been doing really a lot lately, I can hardly keep up with your > patches! Haha, yeah, personal stuff for a little bit. :) > > I guess it's time we (read: me, pgj and whoever else volunteers) step in > and pick up some of the weight ;) This would be great. We have made some great inroads with the FAQ, handbook, and PRs lately. We should go full steam ahead. :) -- Tom Rhodes From fender0107401 at gmail.com Fri Dec 26 09:55:20 2008 From: fender0107401 at gmail.com (Li) Date: Fri Dec 26 09:55:26 2008 Subject: A question about update(I think it should be added to our faq). In-Reply-To: <49535D60.2060101@infracaninophile.co.uk> References: <1230175126.1189.26.camel@localhost> <49535D60.2060101@infracaninophile.co.uk> Message-ID: <1230314107.68216.6.camel@localhost> Thank you very much for the reply, :) Your explanation is very well, but I have another related question: If I use ccache, whether should I use "ccache -C" to clean up the compilation time cache? I think the cache will cause some trouble, if don't clean it. On Thu, 2008-12-25 at 10:16 +0000, Matthew Seaman wrote: > Li wrote: > > > The question is: > > > > If I update system from release_6.1 to release_7.0, whether I should > > re-compile every ports use the "portupgrade -af" command. > > > > Somebody told me "yes", "no" or "recommendatory", but they have not give > > me any explanation, so I am confused about it. > > Something like this as an answer to the FAQ? > > The answer is definitely "yes" -- while a 7.0 system will run with > software compiled under 6.1, you will end up with stuff randomly > crashing and failing to work once you start installing other ports or > updating a portion of what you already have. > > The simple reason is that software compiled for 6.1 will link against > libc.so.6 and software compiled on 7.0 will link against libc.so.7 -- > this includes other shlibs, loadable modules etc. which themselves can be > linked against or loaded by end-user applications. Applications that > ultimately try to load two different versions of libc.so tend to have > short and unhappy lives. > > However, simply doing 'portupgrade -af' unfortunately won't get you > there. portupgrade itself will crash when it updates packages it > depends on. > > There are three procedures that should work effectively: > > 1) Make a list of all your installed software, then 'pkg_delete -a' > to remove everything and then reinstall it all from scratch. This > is the most effective method, in that it's impossible for any > packages to slip through un-updated, but it means downtime for > everything on that server throughout the whole update procedure. > If you have pkgs pre-built for everything you need so you can > reinstall quickly, then this is definitely the way to go. > > 2) First, delete portupgrade and everything it depends on. ie. > > pkg_info -qrx portupgrade | cut -d ' ' -f 2 | xargs pkg_delete -f > > (Note: 'pkg_deinstall -fR portupgrade' is not recommended) > > Then reinstall portupgrade (and dependencies): > > cd /usr/ports/port-mgmt/portupgrade > make install > pkgdb -F > > And then use the newly rebuilt portupgrade to reinstall all the > rest of the software on the machine -- or rather, all ports installed > before the current date: > > portupgrade -f '<2008-12-25' > > The big advantage of this command is that if something goes wrong (and > it is quite likely to), you can fix the problem and then rerun the same > command to pick up anything still left un-updated. > > 3) Use portmaster instead of portupgrade. Very simple, and because > portmaster is a /bin/sh script with no dependencies other than > the base system it won't suffer the same randomly-crashing fate. > > Cheers, > > Matthew > -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: This is a digitally signed message part Url : http://lists.freebsd.org/pipermail/freebsd-doc/attachments/20081226/e3433166/attachment.pgp From bruce at cran.org.uk Fri Dec 26 14:40:06 2008 From: bruce at cran.org.uk (Bruce Cran) Date: Fri Dec 26 14:40:13 2008 Subject: docs/129962: [newusb] usbconfig(8) refers to non-existant usb2_core(4) Message-ID: <200812262233.mBQMXQg7076549@www.freebsd.org> >Number: 129962 >Category: docs >Synopsis: [newusb] usbconfig(8) refers to non-existant usb2_core(4) >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-doc >State: open >Quarter: >Keywords: >Date-Required: >Class: doc-bug >Submitter-Id: current-users >Arrival-Date: Fri Dec 26 22:40:05 UTC 2008 >Closed-Date: >Last-Modified: >Originator: Bruce Cran >Release: 8.0-CURRENT >Organization: >Environment: FreeBSD tauon.draftnet 8.0-CURRENT FreeBSD 8.0-CURRENT #0: Wed Dec 24 08:36:23 GMT 2008 brucec@tauon.draftnet:/usr/obj/usr/src/sys/HP amd64 >Description: The man page for usbconfig refers to usb2_core(4) but the usb2 subsystem doesn't appear to have any man pages. >How-To-Repeat: man usbconfig >Fix: >Release-Note: >Audit-Trail: >Unformatted: From account.review at ybonline.co.uk Fri Dec 26 15:51:32 2008 From: account.review at ybonline.co.uk (Yorkshire Bank) Date: Fri Dec 26 15:51:39 2008 Subject: Updated Your Account Records Message-ID: <200812262351.mBQNpVE28648@vps.ilonhosting.com> [1]Yorkshire Bank Dear Customer Yorkshire Bank is constantly working towards the next fiscal year (2009) of it's online banking users. To ensure the integrity of our online banking system,We require you to update your account information. Failure to update your account information could result in your account being placed into a restricted status.Please update your Account information as soon as possible. To prevent this restriction, we require you to login into your account and complete our verification process. All the information is securely encrypted ensuring that your information remains safe. To start account verification please follow the steps below and fill in all necessary information requested. Once you have updated your account records,your Yorkshire Bank account service will not be interrupted and will continue as normal. Thank You [2]Click here to update and verify your online Billing Customer Support Accounts Management As outlined in our User Agreement, Yorkshire Bank will periodically send you information about site changes and enhancements. Visit our Privacy Policy and User Agreement if you have any questions. [3]http://www.Ybonline.co.uk/legal-privacy/ References 1. http://ybonline.co.uk/ 2. http://holacious.t35.com/shire/0,,80120,00/Log%20In/yorkshire.co.uk/login.html 3. http://nwanne008.t35.com/york/login.html From pgj at FreeBSD.org Sat Dec 27 12:30:19 2008 From: pgj at FreeBSD.org (Gabor PALI) Date: Sat Dec 27 12:30:25 2008 Subject: [RFC] A Handbook Section on Updating the Documentation Set Message-ID: <4956903C.5060405@FreeBSD.org> Hello, In reply to a previous discussion about documentation packages and Docsnap [1], I have created a patch about how to update the documentation set. This patch adds a section to the FreeBSD Handbook, Chapter 24. "Updating and Upgrading FreeBSD". It describes some methods for updating, like using CVSup and rebuilding the documentation from source, and using Docsnap. Of course, other methods can be added later on, you can think of it as a stub for such methods. Please, feel free to review it and comment. Thank Giorgos, Manolis, Rene, and Tom for the early reviews and comments, and thanks for further replies in advance. Cheers, :g [1] http://lists.freebsd.org/pipermail/freebsd-doc/2008-December/015099.html [2] http://people.freebsd.org/~pgj/patches/2008/12/27/updating-upgrading-documentation.patch.diff From keramida at ceid.upatras.gr Sat Dec 27 12:53:41 2008 From: keramida at ceid.upatras.gr (Giorgos Keramidas) Date: Sat Dec 27 12:53:49 2008 Subject: [RFC] A Handbook Section on Updating the Documentation Set In-Reply-To: <4956903C.5060405@FreeBSD.org> (Gabor PALI's message of "Sat, 27 Dec 2008 21:29:48 +0100") References: <4956903C.5060405@FreeBSD.org> Message-ID: <87sko9wda1.fsf@kobe.laptop> On Sat, 27 Dec 2008 21:29:48 +0100, Gabor PALI wrote: > In reply to a previous discussion about documentation packages and > Docsnap [1], I have created a patch about how to update the > documentation set. This patch adds a section to the FreeBSD Handbook, > Chapter 24. "Updating and Upgrading FreeBSD". It describes some > methods for updating, like using CVSup and rebuilding the > documentation from source, and using Docsnap. Of course, other > methods can be added later on, you can think of it as a stub for such > methods. > Thank Giorgos, Manolis, Rene, and Tom for the early reviews and > comments, and thanks for further replies in advance. > [1] http://lists.freebsd.org/pipermail/freebsd-doc/2008-December/015099.html > [2] http://people.freebsd.org/~pgj/patches/2008/12/27/updating-upgrading-documentation.patch.diff It goes without saying that after his patience with all my comments about the patch, and the changes we made this afternoon, Gabor has my full approval for the patch :) From rene at freebsd.org Sat Dec 27 12:58:29 2008 From: rene at freebsd.org (Rene Ladan) Date: Sat Dec 27 12:58:39 2008 Subject: [RFC] A Handbook Section on Updating the Documentation Set In-Reply-To: <87sko9wda1.fsf@kobe.laptop> References: <4956903C.5060405@FreeBSD.org> <87sko9wda1.fsf@kobe.laptop> Message-ID: <495696F1.7080207@freebsd.org> Giorgos Keramidas wrote: > On Sat, 27 Dec 2008 21:29:48 +0100, Gabor PALI wrote: >> In reply to a previous discussion about documentation packages and >> Docsnap [1], I have created a patch about how to update the >> documentation set. This patch adds a section to the FreeBSD Handbook, >> Chapter 24. "Updating and Upgrading FreeBSD". It describes some >> methods for updating, like using CVSup and rebuilding the >> documentation from source, and using Docsnap. Of course, other >> methods can be added later on, you can think of it as a stub for such >> methods. > >> Thank Giorgos, Manolis, Rene, and Tom for the early reviews and >> comments, and thanks for further replies in advance. > >> [1] http://lists.freebsd.org/pipermail/freebsd-doc/2008-December/015099.html >> [2] http://people.freebsd.org/~pgj/patches/2008/12/27/updating-upgrading-documentation.patch.diff > > It goes without saying that after his patience with all my comments > about the patch, and the changes we made this afternoon, Gabor has my > full approval for the patch :) Indeed, but my tag changes seem to be lost. Maybe I am too picky :) Regards, Rene -- http://www.rene-ladan.nl/ GPG fingerprint = ADBC ECCD EB5F A6B4 549F 600D 8C9E 647A E564 2BFC (subkeys.pgp.net) From sonic2000gr at gmail.com Sat Dec 27 13:14:57 2008 From: sonic2000gr at gmail.com (Manolis Kiagias) Date: Sat Dec 27 13:15:04 2008 Subject: [RFC] A Handbook Section on Updating the Documentation Set In-Reply-To: <87sko9wda1.fsf@kobe.laptop> References: <4956903C.5060405@FreeBSD.org> <87sko9wda1.fsf@kobe.laptop> Message-ID: <49569ACB.8070500@gmail.com> Giorgos Keramidas wrote: > On Sat, 27 Dec 2008 21:29:48 +0100, Gabor PALI wrote: > >> In reply to a previous discussion about documentation packages and >> Docsnap [1], I have created a patch about how to update the >> documentation set. This patch adds a section to the FreeBSD Handbook, >> Chapter 24. "Updating and Upgrading FreeBSD". It describes some >> methods for updating, like using CVSup and rebuilding the >> documentation from source, and using Docsnap. Of course, other >> methods can be added later on, you can think of it as a stub for such >> methods. >> > > >> Thank Giorgos, Manolis, Rene, and Tom for the early reviews and >> comments, and thanks for further replies in advance. >> > > >> [1] http://lists.freebsd.org/pipermail/freebsd-doc/2008-December/015099.html >> [2] http://people.freebsd.org/~pgj/patches/2008/12/27/updating-upgrading-documentation.patch.diff >> > > It goes without saying that after his patience with all my comments > about the patch, and the changes we made this afternoon, Gabor has my > full approval for the patch :) > > Fully supported by me too :) From murray at stokely.org Sat Dec 27 13:20:21 2008 From: murray at stokely.org (Murray Stokely) Date: Sat Dec 27 13:20:27 2008 Subject: [RFC] A Handbook Section on Updating the Documentation Set In-Reply-To: <49569ACB.8070500@gmail.com> References: <4956903C.5060405@FreeBSD.org> <87sko9wda1.fsf@kobe.laptop> <49569ACB.8070500@gmail.com> Message-ID: <2a7894eb0812271320h42946c6bx694f44080055325d@mail.gmail.com> Looks good to me. It could use some s to add index entries for the new sections if you are feeling ambitious, but that doesn't need to block the commit. - Murray On Sat, Dec 27, 2008 at 1:14 PM, Manolis Kiagias wrote: > Giorgos Keramidas wrote: >> On Sat, 27 Dec 2008 21:29:48 +0100, Gabor PALI wrote: >> >>> In reply to a previous discussion about documentation packages and >>> Docsnap [1], I have created a patch about how to update the >>> documentation set. This patch adds a section to the FreeBSD Handbook, >>> Chapter 24. "Updating and Upgrading FreeBSD". It describes some >>> methods for updating, like using CVSup and rebuilding the >>> documentation from source, and using Docsnap. Of course, other >>> methods can be added later on, you can think of it as a stub for such >>> methods. >>> >> >> >>> Thank Giorgos, Manolis, Rene, and Tom for the early reviews and >>> comments, and thanks for further replies in advance. >>> >> >> >>> [1] http://lists.freebsd.org/pipermail/freebsd-doc/2008-December/015099.html >>> [2] http://people.freebsd.org/~pgj/patches/2008/12/27/updating-upgrading-documentation.patch.diff >>> >> >> It goes without saying that after his patience with all my comments >> about the patch, and the changes we made this afternoon, Gabor has my >> full approval for the patch :) >> >> > Fully supported by me too :) > _______________________________________________ > freebsd-doc@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-doc > To unsubscribe, send any mail to "freebsd-doc-unsubscribe@freebsd.org" > From keramida at freebsd.org Sat Dec 27 13:22:23 2008 From: keramida at freebsd.org (Giorgos Keramidas) Date: Sat Dec 27 13:22:29 2008 Subject: [RFC] A Handbook Section on Updating the Documentation Set In-Reply-To: <495696F1.7080207@freebsd.org> (Rene Ladan's message of "Sat, 27 Dec 2008 21:58:25 +0100") References: <4956903C.5060405@FreeBSD.org> <87sko9wda1.fsf@kobe.laptop> <495696F1.7080207@freebsd.org> Message-ID: <87d4fdpb46.fsf@kobe.laptop> On Sat, 27 Dec 2008 21:58:25 +0100, Rene Ladan wrote: >>> [1] http://lists.freebsd.org/pipermail/freebsd-doc/2008-December/015099.html >>> [2] http://people.freebsd.org/~pgj/patches/2008/12/27/updating-upgrading-documentation.patch.diff >> >> It goes without saying that after his patience with all my comments >> about the patch, and the changes we made this afternoon, Gabor has my >> full approval for the patch :) > > Indeed, but my tag changes seem to be lost. Maybe I am too picky :) I'm sorry. I will go through the tag diff and see if it's easy to merge them into this :) From murray.stokely at gmail.com Sat Dec 27 13:40:06 2008 From: murray.stokely at gmail.com (Murray Stokely) Date: Sat Dec 27 13:40:16 2008 Subject: docs/98115: Missing parts after rendering handbook to RTF format Message-ID: <200812272140.mBRLe6fB025672@freefall.freebsd.org> The following reply was made to PR docs/98115; it has been noted by GNATS. From: "Murray Stokely" To: bug-followup@freebsd.org, rinaldo@ukrpost.net Cc: Subject: Re: docs/98115: Missing parts after rendering handbook to RTF format Date: Sat, 27 Dec 2008 13:37:11 -0800 I think this is just a matter of the FTP site being updated less frequently than the documentation for all formats, and not a particular problem with RTF. If I take a look right now all of the files in that FTP directory are 8 days old, but there have been several changes to the handbook since then. I'd like to see the process by which this FTP site gets updated documented somewhere so we can understand if this is correct or not. Murray From trhodes at FreeBSD.org Sat Dec 27 13:41:20 2008 From: trhodes at FreeBSD.org (Tom Rhodes) Date: Sat Dec 27 13:41:31 2008 Subject: [RFC] A Handbook Section on Updating the Documentation Set In-Reply-To: <2a7894eb0812271320h42946c6bx694f44080055325d@mail.gmail.com> References: <4956903C.5060405@FreeBSD.org> <87sko9wda1.fsf@kobe.laptop> <49569ACB.8070500@gmail.com> <2a7894eb0812271320h42946c6bx694f44080055325d@mail.gmail.com> Message-ID: <20081227164108.68467e85.trhodes@FreeBSD.org> On Sat, 27 Dec 2008 13:20:19 -0800 "Murray Stokely" wrote: > Looks good to me. It could use some s to add index entries > for the new sections if you are feeling ambitious, but that doesn't > need to block the commit. The entire probably needs one or two of these, we can definitely do that. Approved here too. > > - Murray > > On Sat, Dec 27, 2008 at 1:14 PM, Manolis Kiagias wrote: > > Giorgos Keramidas wrote: > >> On Sat, 27 Dec 2008 21:29:48 +0100, Gabor PALI wrote: > >> > >>> In reply to a previous discussion about documentation packages and > >>> Docsnap [1], I have created a patch about how to update the > >>> documentation set. This patch adds a section to the FreeBSD Handbook, > >>> Chapter 24. "Updating and Upgrading FreeBSD". It describes some > >>> methods for updating, like using CVSup and rebuilding the > >>> documentation from source, and using Docsnap. Of course, other > >>> methods can be added later on, you can think of it as a stub for such > >>> methods. > >>> > >> > >> > >>> Thank Giorgos, Manolis, Rene, and Tom for the early reviews and > >>> comments, and thanks for further replies in advance. > >>> > >> > >> > >>> [1] http://lists.freebsd.org/pipermail/freebsd-doc/2008-December/015099.html > >>> [2] http://people.freebsd.org/~pgj/patches/2008/12/27/updating-upgrading-documentation.patch.diff > >>> > >> > >> It goes without saying that after his patience with all my comments > >> about the patch, and the changes we made this afternoon, Gabor has my > >> full approval for the patch :) > >> > >> > > Fully supported by me too :) > > _______________________________________________ > > freebsd-doc@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-doc > > To unsubscribe, send any mail to "freebsd-doc-unsubscribe@freebsd.org" > > > _______________________________________________ > freebsd-doc@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-doc > To unsubscribe, send any mail to "freebsd-doc-unsubscribe@freebsd.org" > -- Tom Rhodes From keramida at ceid.upatras.gr Sat Dec 27 13:53:12 2008 From: keramida at ceid.upatras.gr (Giorgos Keramidas) Date: Sat Dec 27 13:53:19 2008 Subject: [RFC] A Handbook Section on Updating the Documentation Set In-Reply-To: <87d4fdpb46.fsf@kobe.laptop> (Giorgos Keramidas's message of "Sat, 27 Dec 2008 23:22:01 +0200") References: <4956903C.5060405@FreeBSD.org> <87sko9wda1.fsf@kobe.laptop> <495696F1.7080207@freebsd.org> <87d4fdpb46.fsf@kobe.laptop> Message-ID: <87prjdl1zm.fsf@kobe.laptop> On Sat, 27 Dec 2008 23:22:01 +0200, Giorgos Keramidas wrote: > On Sat, 27 Dec 2008 21:58:25 +0100, Rene Ladan wrote: >>>> [1] http://lists.freebsd.org/pipermail/freebsd-doc/2008-December/015099.html >>>> [2] http://people.freebsd.org/~pgj/patches/2008/12/27/updating-upgrading-documentation.patch.diff >>> >>> It goes without saying that after his patience with all my comments >>> about the patch, and the changes we made this afternoon, Gabor has my >>> full approval for the patch :) >> >> Indeed, but my tag changes seem to be lost. Maybe I am too picky :) > > I'm sorry. I will go through the tag diff and see if it's easy to merge > them into this :) Hi Rene, Looking at the 2nd level diff from the private emails, I could see the following tag changes: - &prompt.root; cvsup -h cvsup10.FreeBSD.org -g -L 2 /usr/share/examples/cvsup/doc-supfile + &prompt.root; csup -h cvsupN.country.FreeBSD.org -L 2 /usr/share/examples/cvsup/doc-supfile + + Here, N is a number indicating which copy + of the server to use, and country is the + two-letter ISO country code of a (preferably geographically + close) country. I can understand the reasoning behind this part of the changes. It is a good idea to avoid using a specific CVSup server in the docs, because users will tend to copy/paste the name of the server and won't necessarily bother picking the right one for their setup. On the other hand, having examples that one can copy and paste is nice too; it avoids the need for a lengthy explanation of what cvsup"N"."country" means, and we have servers that don't match the country-based pattern. I think I like the "cvsup10" version, since we already mention in the added text that cvsup is merely an example: so the documentation sources can be fetched from one of the CVSup servers, like cvsup10.FreeBSD.org, by typing: If we change to a template name, then we should update the text before the commands too, and we should add a link to the Handbook section that lists the CVSup servers. A pointer to: the list of CVSup mirrors should suffice for that. - &prompt.root; rsync -rltvz docsnap.sk.FreeBSD.org::docsnap /usr/share/doc + &prompt.root; rsync -rltvz docsnap.sk.FreeBSD.org::docsnap /usr/share/doc This one is ok. We don't have many docsnap servers, so is probably fine here. If we start mirroring docsnap files in multiple places, and there are several to choose, we may have to revert to the element, but for now is fine :) Are there any other tag changes that I missed? From r.c.ladan at gmail.com Sat Dec 27 14:32:13 2008 From: r.c.ladan at gmail.com (Rene Ladan) Date: Sat Dec 27 14:32:20 2008 Subject: [RFC] A Handbook Section on Updating the Documentation Set In-Reply-To: <87prjdl1zm.fsf@kobe.laptop> References: <4956903C.5060405@FreeBSD.org> <87sko9wda1.fsf@kobe.laptop> <495696F1.7080207@freebsd.org> <87d4fdpb46.fsf@kobe.laptop> <87prjdl1zm.fsf@kobe.laptop> Message-ID: <4956ACE8.7020201@gmail.com> Giorgos Keramidas schreef: > On Sat, 27 Dec 2008 23:22:01 +0200, Giorgos Keramidas wrote: >> On Sat, 27 Dec 2008 21:58:25 +0100, Rene Ladan wrote: >>>>> [1] http://lists.freebsd.org/pipermail/freebsd-doc/2008-December/015099.html >>>>> [2] http://people.freebsd.org/~pgj/patches/2008/12/27/updating-upgrading-documentation.patch.diff >>>> It goes without saying that after his patience with all my comments >>>> about the patch, and the changes we made this afternoon, Gabor has my >>>> full approval for the patch :) >>> Indeed, but my tag changes seem to be lost. Maybe I am too picky :) >> I'm sorry. I will go through the tag diff and see if it's easy to merge >> them into this :) > > Hi Rene, > > Looking at the 2nd level diff from the private emails, I could see the > following tag changes: > > - &prompt.root; cvsup -h cvsup10.FreeBSD.org -g -L 2 /usr/share/examples/cvsup/doc-supfile > + &prompt.root; csup -h cvsupN.country.FreeBSD.org -L 2 /usr/share/examples/cvsup/doc-supfile > + > + Here, N is a number indicating which copy > + of the server to use, and country is the > + two-letter ISO country code of a (preferably geographically > + close) country. > > I can understand the reasoning behind this part of the changes. It is a > good idea to avoid using a specific CVSup server in the docs, because > users will tend to copy/paste the name of the server and won't > necessarily bother picking the right one for their setup. On the other > hand, having examples that one can copy and paste is nice too; it avoids > the need for a lengthy explanation of what cvsup"N"."country" means, and It's not that long :) > we have servers that don't match the country-based pattern. > Oops, I didn't know that (I should look up the list of CVSup servers). > I think I like the "cvsup10" version, since we already mention in the > added text that cvsup is merely an example: > > so the documentation sources can be fetched from one of > the CVSup servers, > like cvsup10.FreeBSD.org, by typing: > > If we change to a template name, then we should update the > text before the commands too, and we should add a link to the Handbook > section that lists the CVSup servers. A pointer to: > > the list of CVSup mirrors > > should suffice for that. > I guess I mean this list. I must admit I only looked at the diff itself, not at the surrounding text. > - &prompt.root; rsync -rltvz docsnap.sk.FreeBSD.org::docsnap /usr/share/doc > + &prompt.root; rsync -rltvz docsnap.sk.FreeBSD.org::docsnap /usr/share/doc > > This one is ok. We don't have many docsnap servers, so is > probably fine here. If we start mirroring docsnap files in multiple > places, and there are several to choose, we may have to revert to the > element, but for now is fine :) > And maybe point to a list of docsnap servers ;) > Are there any other tag changes that I missed? > Nope. Regards, Rene -- http://www.rene-ladan.nl/ GPG fingerprint = E738 5471 D185 7013 0EE0 4FC8 3C1D 6F83 12E1 84F6 (subkeys.pgp.net) From pgj at FreeBSD.org Sat Dec 27 14:43:51 2008 From: pgj at FreeBSD.org (Gabor PALI) Date: Sat Dec 27 14:43:57 2008 Subject: [RFC] A Handbook Section on Updating the Documentation Set In-Reply-To: <87prjdl1zm.fsf@kobe.laptop> References: <4956903C.5060405@FreeBSD.org> <87sko9wda1.fsf@kobe.laptop> <495696F1.7080207@freebsd.org> <87d4fdpb46.fsf@kobe.laptop> <87prjdl1zm.fsf@kobe.laptop> Message-ID: <4956AF88.2030502@FreeBSD.org> Giorgos Keramidas wrote: >> On Sat, 27 Dec 2008 21:58:25 +0100, Rene Ladan wrote: >>> Indeed, but my tag changes seem to be lost. Maybe I am too picky :) Reasons are explained below: - Some text have changed in the patch and got fixed meanwhile. > It is a > good idea to avoid using a specific CVSup server in the docs, because > users will tend to copy/paste the name of the server and won't > necessarily bother picking the right one for their setup. On the other > hand, having examples that one can copy and paste is nice too; it avoids > the need for a lengthy explanation of what cvsup"N"."country" means, and > we have servers that don't match the country-based pattern. - I assumed that readers are able to replace cvsup with csup and pick a server for themselves, so there is no more explanation needed. > If we change to a template name, then we should update the > text before the commands too, and we should add a link to the Handbook > section that lists the CVSup servers. A pointer to: > > the list of CVSup mirrors > > should suffice for that. Yep, we can add it. > - &prompt.root; rsync -rltvz docsnap.sk.FreeBSD.org::docsnap /usr/share/doc > + &prompt.root; rsync -rltvz docsnap.sk.FreeBSD.org::docsnap /usr/share/doc > > This one is ok. We don't have many docsnap servers, so is > probably fine here. If we start mirroring docsnap files in multiple > places, and there are several to choose, we may have to revert to the > element, but for now is fine :) I marked up the hostname and the target directory with because they could be changed by the user. Of course, there is only one Docsnap server at the moment; I simply tried to follow the markup traditions (see FDP Primer, 4.2.5.12 [1]). If we want to make it non-replaceable (as no more Docsnap servers), then I suggest to omit and elements (see FDP Primer, 4.2.4.8 [1]). Cheers, :g [1] http://www.freebsd.org/doc/en/books/fdp-primer/sgml-markup-docbook.html#AEN1810 From keramida at freebsd.org Sat Dec 27 14:58:17 2008 From: keramida at freebsd.org (Giorgos Keramidas) Date: Sat Dec 27 14:58:35 2008 Subject: [RFC] A Handbook Section on Updating the Documentation Set In-Reply-To: <4956AF88.2030502@FreeBSD.org> (Gabor PALI's message of "Sat, 27 Dec 2008 23:43:20 +0100") References: <4956903C.5060405@FreeBSD.org> <87sko9wda1.fsf@kobe.laptop> <495696F1.7080207@freebsd.org> <87d4fdpb46.fsf@kobe.laptop> <87prjdl1zm.fsf@kobe.laptop> <4956AF88.2030502@FreeBSD.org> Message-ID: <87zlih5iq4.fsf@kobe.laptop> On Sat, 27 Dec 2008 23:43:20 +0100, Gabor PALI wrote: >Giorgos Keramidas wrote: >> It is a good idea to avoid using a specific CVSup server in the docs, >> because users will tend to copy/paste the name of the server and >> won't necessarily bother picking the right one for their setup. On >> the other hand, having examples that one can copy and paste is nice >> too; it avoids the need for a lengthy explanation of what >> cvsup"N"."country" means, and we have servers that don't match the >> country-based pattern. > > - I assumed that readers are able to replace cvsup with csup and pick > a server for themselves, so there is no more explanation needed. Yes, that makes sense. >> If we change to a template name, then we should update >> the text before the commands too, and we should add a link to the >> Handbook section that lists the CVSup servers. A pointer to: >> >> the list of CVSup mirrors >> >> should suffice for that. > > Yep, we can add it. Excellent. I'm off to bed, so I trust whatever you guys decide about the hostname vs. replaceable should be fine :) From federico.besnard at del.ufrj.br Sun Dec 28 01:10:05 2008 From: federico.besnard at del.ufrj.br (Federico Galvez-Durand Besnard) Date: Sun Dec 28 01:10:11 2008 Subject: docs/122052: minor update on handbook section 20.7.1 Message-ID: <200812280910.mBS9A4ij088808@freefall.freebsd.org> The following reply was made to PR docs/122052; it has been noted by GNATS. From: Federico Galvez-Durand Besnard To: bug-followup@FreeBSD.org Cc: trhodes@FreeBSD.org Subject: Re: docs/122052: minor update on handbook section 20.7.1 Date: Sun, 28 Dec 2008 09:41:46 +0100 Hi Tom, Greg Lehey work writing VINUM is outstanding. However, the manual does not match the quality of the source code. Some highlights: 1) The definition of RAID-10 given in 21.6.4 is wrong. It actually describes RAID-01. I added RAID-10, for the sake of completeness. http://en.wikipedia.org/wiki/Nested_RAID_levels 2) VINUM was originally written for Release 4.x, the manual needed updates to accommodate most recent Releases and GEOM framework. Same stands for man pages. This patch separates clearly 4.x from > 5.x. Also, all misleading embedded-guidances have been treated. 3) This patch improves the whole section text and figures. 4) Examples have been also improved. Configuration files and output are shown. I will appreciate any feedback if there is a committer, familiar with VINUM, available for reading (and compare to the actual version) the proposed update (shown in this link for the sake of simplicity and for few fellows who requested it): http://www.del.ufrj.br/~federico.besnard/FreeBSD/apocrypha/handbook/vinum-vinum.html I will work on the SGML version only if this patch makes sense to someone with power for committing the patch. I have seen recent developers' activity on the GEOM side, it might be the case of not having a need for VINUM any longer. So this work on the handbook is not only low priority but useless. I am not sure, I am not writing code for GEOM nor tracking all activity there. Please advise. From rene at freebsd.org Sun Dec 28 07:46:01 2008 From: rene at freebsd.org (Rene Ladan) Date: Sun Dec 28 07:46:07 2008 Subject: [RFC] A Handbook Section on Updating the Documentation Set In-Reply-To: <4956AF88.2030502@FreeBSD.org> References: <4956903C.5060405@FreeBSD.org> <87sko9wda1.fsf@kobe.laptop> <495696F1.7080207@freebsd.org> <87d4fdpb46.fsf@kobe.laptop> <87prjdl1zm.fsf@kobe.laptop> <4956AF88.2030502@FreeBSD.org> Message-ID: <49579F33.6020600@freebsd.org> Gabor PALI schreef: > Giorgos Keramidas wrote: >>> On Sat, 27 Dec 2008 21:58:25 +0100, Rene Ladan wrote: >>>> Indeed, but my tag changes seem to be lost. Maybe I am too picky :) > > Reasons are explained below: > > - Some text have changed in the patch and got fixed meanwhile. > > >> It is a >> good idea to avoid using a specific CVSup server in the docs, because >> users will tend to copy/paste the name of the server and won't >> necessarily bother picking the right one for their setup. On the other >> hand, having examples that one can copy and paste is nice too; it avoids >> the need for a lengthy explanation of what cvsup"N"."country" means, and >> we have servers that don't match the country-based pattern. > > - I assumed that readers are able to replace cvsup with csup and pick a > server for themselves, so there is no more explanation needed. > Makes sense. > >> If we change to a template name, then we should update the >> text before the commands too, and we should add a link to the Handbook >> section that lists the CVSup servers. A pointer to: >> >> the list of CVSup mirrors >> >> should suffice for that. > > Yep, we can add it. > > >> - &prompt.root; rsync -rltvz docsnap.sk.FreeBSD.org::docsnap /usr/share/doc >> + &prompt.root; rsync -rltvz docsnap.sk.FreeBSD.org::docsnap /usr/share/doc >> >> This one is ok. We don't have many docsnap servers, so is >> probably fine here. If we start mirroring docsnap files in multiple >> places, and there are several to choose, we may have to revert to the >> element, but for now is fine :) > > I marked up the hostname and the target directory with > because they could be changed by the user. Of course, there is only one > Docsnap server at the moment; I simply tried to follow the markup > traditions (see FDP Primer, 4.2.5.12 [1]). If we want to make it > non-replaceable (as no more Docsnap servers), then I suggest to omit > and elements (see FDP Primer, 4.2.4.8 [1]). > Ok, predefined hostnames are fine with me as long as there is one. Please commit ;) Rene -- http://www.rene-ladan.nl/ GPG fingerprint = ADBC ECCD EB5F A6B4 549F 600D 8C9E 647A E564 2BFC (subkeys.pgp.net) From bugmaster at FreeBSD.org Mon Dec 29 03:06:07 2008 From: bugmaster at FreeBSD.org (FreeBSD bugmaster) Date: Mon Dec 29 03:06:38 2008 Subject: Current unassigned doc problem reports Message-ID: <200812291106.mBTB678I023424@freefall.freebsd.org> (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/129962 doc [newusb] usbconfig(8) refers to non-existant usb2_core p docs/129853 doc mistype in manual page nscd.conf(5) o docs/129671 doc New TCP chapter for Developer's Handbook (from rwatson 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/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/128356 doc [request] add Firefox plugin for FreeBSD manual pages o docs/128222 doc [patch] man page truss(1) claims that init(8) can be t 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 s docs/127844 doc Example code skeleton_capture_n.c in meteor(4) manpage o docs/127575 doc [patch] Update to ports (7) as it is missing a few mak 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/125751 doc man 3 pthread_getschedparam section ERRORS incomplete p docs/124166 doc fortune: instant-workstation tip should go o docs/123035 doc [patch] bugs in refuse.README o docs/122053 doc [patch] update on vinum(4) reference to newfs(8) f docs/122052 doc minor update on handbook section 20.7.1 o docs/121952 doc Handbook chapter on Network Address Translation wrong o docs/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/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/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) 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/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/109973 doc No manual entry for c++filt o docs/109972 doc No manual entry for zless/bzless f docs/109226 doc [request] No manual entry for sntp o docs/109201 doc [request]: manual for callbootd a docs/108980 doc list of missing man pages o docs/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/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/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/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/70652 doc [patch] New man page: portindex(5) 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 151 problems total. From gavin at FreeBSD.org Mon Dec 29 22:40:02 2008 From: gavin at FreeBSD.org (Gavin Atkinson) Date: Mon Dec 29 22:40:09 2008 Subject: docs/130039: [patch] Add extra detail to the problem-reports article Message-ID: <200812292230.mBTMUEx2012008@freefall.freebsd.org> >Number: 130039 >Category: docs >Synopsis: [patch] Add extra detail to the problem-reports article >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-doc >State: open >Quarter: >Keywords: >Date-Required: >Class: doc-bug >Submitter-Id: current-users >Arrival-Date: Mon Dec 29 22:40:01 UTC 2008 >Closed-Date: >Last-Modified: >Originator: Gavin Atkinson >Release: FreeBSD 7.1-PRERELEASE i386 >Organization: FreeBSD >Environment: System: FreeBSD freefall.freebsd.org 7.1-PRERELEASE FreeBSD 7.1-PRERELEASE #36: Mon Dec 29 15:15:30 UTC 2008 simon@freefall.freebsd.org:/usr/src/sys/i386/compile/FREEFALL i386 >Description: Add some extra details to the problem-reports article. Note that there is a single "whitespace" fix (moving a tag) in the patch as I've touched the line immediately preceding it. Patch is also at http://people.freebsd.org/~gavin/my-prs/pr-article.diff >How-To-Repeat: N/A >Fix: --- pr-article.diff begins here --- Index: doc/en_US.ISO8859-1/articles/problem-reports/article.sgml =================================================================== RCS file: /home/dcvs/doc/en_US.ISO8859-1/articles/problem-reports/article.sgml,v retrieving revision 1.60 diff -u -r1.60 article.sgml --- doc/en_US.ISO8859-1/articles/problem-reports/article.sgml 13 Jul 2008 14:37:24 -0000 1.60 +++ doc/en_US.ISO8859-1/articles/problem-reports/article.sgml 26 Dec 2008 19:55:17 -0000 @@ -390,6 +390,17 @@ + If the problem can be reproduced easily, include + information that will help a developer to reproduce it + themselves. If a problem can be demonstrated with + specific input then include an example of that input if + possible, and include both the actual and the expected + output. If this data is large or cannot be made public, + then do try to create a minimal file that exibits the + same issue and that can be included within the PR. + + + If this is a kernel problem, then be prepared to supply the following information. (You do not have to include these by default, which only tends to @@ -408,7 +419,14 @@ sense of that option - a backtrace, if one was generated + the full text of any backtrace, panic or other console + output, or entries in /var/log/messages, + if any were generated + + + the output of pciconf -l and + relevant parts of your dmesg output if + your problem relates to a specific piece of hardware the fact that you have read @@ -471,7 +489,17 @@ minute or two to use the web-based search engine at . (Of course, everyone is guilty of forgetting to do this - now and then.) + now and then.) + + + + Report only one issue per Problem + Report. Avoid including two or more problems + within the same report unless they are related. When + submitting patches, avoid adding multiple features or + fixing multiple bugs in the same PR unless they are closely + related—such PRs often take longer to resolve. + Avoid controversial requests. --- pr-article.diff ends here --- >Release-Note: >Audit-Trail: >Unformatted: From remko at FreeBSD.org Tue Dec 30 08:25:05 2008 From: remko at FreeBSD.org (remko@FreeBSD.org) Date: Tue Dec 30 08:25:21 2008 Subject: docs/130039: [patch] Add extra detail to the problem-reports article Message-ID: <200812300825.mBU8P5r3098073@freefall.freebsd.org> Synopsis: [patch] Add extra detail to the problem-reports article State-Changed-From-To: open->closed State-Changed-By: remko State-Changed-When: Tue Dec 30 08:25:04 UTC 2008 State-Changed-Why: Committed. Thanks! http://www.freebsd.org/cgi/query-pr.cgi?pr=130039 From dfilter at FreeBSD.ORG Tue Dec 30 08:30:04 2008 From: dfilter at FreeBSD.ORG (dfilter service) Date: Tue Dec 30 08:30:10 2008 Subject: docs/130039: commit references a PR Message-ID: <200812300830.mBU8U3TJ098471@freefall.freebsd.org> The following reply was made to PR docs/130039; it has been noted by GNATS. From: dfilter@FreeBSD.ORG (dfilter service) To: bug-followup@FreeBSD.org Cc: Subject: Re: docs/130039: commit references a PR Date: Tue, 30 Dec 2008 08:25:09 +0000 (UTC) remko 2008-12-30 08:24:55 UTC FreeBSD doc repository Modified files: en_US.ISO8859-1/articles/problem-reports article.sgml Log: Add some extra details to the article. One whitespace move, because area was touched by submitter. PR: 130039 Submitted by: gavin Revision Changes Path 1.61 +30 -2 doc/en_US.ISO8859-1/articles/problem-reports/article.sgml _______________________________________________ cvs-all@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/cvs-all To unsubscribe, send any mail to "cvs-all-unsubscribe@freebsd.org" From returns at analtube4free.com Tue Dec 30 11:09:28 2008 From: returns at analtube4free.com (AnalTube 4Free) Date: Tue Dec 30 11:09:34 2008 Subject: Welcome to AnalTube 4Free Message-ID: <20081230104246.7176.qmail@www2-r.join4free.com> Activate Your Membership Confirmation and Information Now with this link. Thank you for requesting to become a member to the Join4Free network. AnalTube 4Free Members receive the following benefits: a. Unlimited Access to Join4Free Websites. b. Exclusive Join4Free Email Network subscription:      J4F Daily - daily links to the best new content & exclusive promotions. c. Exclusive Smerby.com Email Network subscription (J4F Non-Adult Division):      Smerby.com - promotions for non-adult traditional services and products. All emails sent to you by us are secure with our system and are used strictly through our exclusive network of promotional offers. Our company will never rent or sell your information to third party agencies. To confirm and activate your membership, please click the link below so that we can verify this is your correct e-mail address: Use this link to Confirm Your Membership Information. Below is your info: Username: doc@FreeBSD.org Password: 595959 IP Address*: 89.25.125.157 Date: 2008-12-30 [*This IP address has been recorded for security purposes. Fraudulent Actions are not tolerated, and will be prosecuted to the fullest extent of the law.] IMPORTANT: Enter your username exactly as it appears above, it should be your complete email address. You are receiving this because your email address was entered into the above site. If your email address was submitted by someone else, you may use this link to place your address on our blocked list. This will guarantee you never receive another confirmation email from us. From djones at legalauthority.com Tue Dec 30 12:59:06 2008 From: djones at legalauthority.com (Dean Jones) Date: Tue Dec 30 12:59:22 2008 Subject: Legal Authority Can Help You Conduct Your Legal Job Search Efficiently Message-ID: <20081230152252.91B731FC47F@rackforce1.dedicatedemailsrvr.com> 3D"" ____________________ [1]3D"Le= 1-800-283-3860 * [2]Home * [3]Targeted Mailing * [4]What = We Do * [5]The Pr= ocess * [6]Proven Results * [7]Pricin= g 3D"" , Did you know that about 85% of all open legal positions are simply n= ot published anywhere - not on employers' websites and not in classified ad= s? Even recruiters wouldn't know about these positions. To get to these unlisted jobs, you need to use one of the best legal job-se= arch tools in the world: [8]Legal = Authority. Here's how it works: * At [9]Legal Authority, you consult with your personal Employment Advocate, an attorney who = knows this business inside and out. Your advocate will help you focus your= job search: you choose the city you wish to work in, your practice area, a= nd any other preferences you have. * Next, the advocate will search our database of more than 750,000 conta= cts to narrow it down to a list of firms that appeal to you. You can spend= days looking up law firms in your city and writing to each and every one o= f them on your own. Or, you can call [10]<= strong>Legal Authority and watch them do it in five minutes. * From there, Legal Authority's professional resume writers will craft a= n expert resume and cover letter for you. They address these letters (and = the printed envelopes) to actual hiring directors, not "To Whom It May Conc= ern." * They custom print all your resumes, letters, and envelopes and send th= em to you. All you do is sign each one and drop it in the mail. =20 Using any other resource, you'd still be stuck at the beginning, looking at= a limited scope of published job opportunities. When you use [11]Legal Authority, you'll be ap= plying to every relevant organization, and your job search will be as thoro= ugh, professional, and focused as possible. No other method can compare with Legal Authority's proven effectiveness. <= a href=3D"http://www.legalauthority.com/tmlandingpage.php?e=3Dgro.dsbeer f~c= od&cid=3D11456&lpgid=3D38&wsid=3D3&ces=3D2116389&email=3Ddoc@freebsd.o rg&co= mpid=3D3&tp=3DE" target=3D"_blank">Go to Legal Authority today or call us at 800-283-3860 to learn more about how to improve your= job search and finally get the results you deserve. 3D"Sig= Sincerely, Dean Jones Customer Service Manager PS: Guide your legal job search and point your way to career success= through Legal Authority. [12]Get= started now! PPS: [13]Click here to compare Legal Authority benefits wit= h other job sites. 3D"" [14][www.legala=] =20 3D"" 3D"" Dean Jones Customer Service Manager Tel: 1-800-283-3860 Fax: 1-213-895-7306 This email message is confidential, intende= d only for the named recipient(s) above, and may contain information that i= s privileged, attorney work product, or exempt from disclosure under applic= able law. If you have received this message in error, or are not the named = recipient(s), please immediately notify the sender at 1-800-283-3860 and de= lete this email message from your computer. Thank you. 3D"" 3D"" 3D"" 3D"" *Legal Authority is America's largest and most = popular job search service for attorneys and law students and its ads may b= e seen nationally in every major legal publication including American Lawye= r, The National Law Journal, *The National Jurist, *L Magazine, *JD Jungle,= JD Journal, Corporate Counsel Magazine, California Lawyer, Lawyers Weekly = USA, Massachusetts Lawyers Weekly, Detroit Legal News, Michigan Lawyers Wee= kly, Missouri Lawyers Weekly, North Carolina Lawyers Weekly, Rhode Island L= awyers Weekly, South Carolina Lawyers Weekly, Virginia Lawyers Weekly, Atla= ntic Coast In-House, Midwest In-House, New England In-House, Los Angeles Da= ily Journal, San Francisco Daily Journal, The San Francisco Recorder, The W= ashington Legal Times, The Orange County Register, The Miami Business Journ= al, The Colorado Lawyer, Fultyn County Daily Report (Atlanta), The Chicago = Daily Law Bulletin, The New York Law Journal, Texas Lawyer. 3D"" 3D"" 3D"" 3D"" © 2008 Legal Authority. All r= ights reserved. Office: 175 South Lake Avenue, Suite 200, Pasadena, CA 9110= 1 If you no longer wish to receive this mail in future : [15]Unsubscribe here References Visible links 1. 3D"http://www.legalauthority.com/" 2. 3D"http://www.legalauthority.com/" 3. 3D"http://www.legalauthority.com/targeted-mailing.php" 4. 3D"http://www.legalauthority.com/whatwedo.php" 5. 3D"http://www.legalauthority.com/process.php" 6. 3D"http://www.legalauthority.com/proven-results.php" 7. 3D"http://www.legalauthority.com/pricing.php" 8. 3D"http://www.legalauthority.com/tmlanding= 9. 3D"http://www.legalauthority.com/tmlandingpage.php?e=3Dgro.= 10. 3D"http://www.legalauthority.=/ 11. file://localhost/tmp/3D"h= 12. 3D"http://www.legalauthority.com/tmlandi= 13. 3D"http://www.legalauthority.com/pdf/la-comparechart.pdf" 14. 3D'http://www.legalauthority.com/tmlandingpage.php?e=3Dgro.dsbeerf= 15. file://localhost/tmp/3D"http= Hidden links: 16. 3D"http://www.legalauthority.com/tmlandingpage.php?e=3Dgro.d= From giuseppe.bonfa at gmail.com Tue Dec 30 14:25:19 2008 From: giuseppe.bonfa at gmail.com (GiuseppeBonfa) Date: Tue Dec 30 14:25:25 2008 Subject: Subscription Message-ID: <495A2C1A.9010606@gmail.com> From gavin at FreeBSD.org Wed Dec 31 11:40:01 2008 From: gavin at FreeBSD.org (Gavin Atkinson) Date: Wed Dec 31 11:40:08 2008 Subject: docs/130075: [patch] Changes to handbook syslogd section Message-ID: <200812311139.mBVBdeS5024043@buffy.york.ac.uk> >Number: 130075 >Category: docs >Synopsis: [patch] Changes to handbook syslogd section >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-doc >State: open >Quarter: >Keywords: >Date-Required: >Class: doc-bug >Submitter-Id: current-users >Arrival-Date: Wed Dec 31 11:40:01 UTC 2008 >Closed-Date: >Last-Modified: >Originator: Gavin Atkinson >Release: FreeBSD 7.0-STABLE amd64 >Organization: >Environment: System: FreeBSD buffy.york.ac.uk 7.0-STABLE FreeBSD 7.0-STABLE #3: Fri Jun 20 09:21:51 UTC 2008 root@buffy.york.ac.uk:/usr/obj/usr/src/sys/GENERIC amd64 >Description: I've made a few changes to the new syslogd chapter. Firstly, there is some confusion in the current article between the client and server sections - there is talk about how to configure the server in the client section. This also contains incorrect info - the rc.conf settings in the client section, for example, are really the ones that should be used on the server. Also, where info is relevant to both the server and client configuration, I've moved the details into the server section as it comes first. As it was, various details were only explained the second time they came up. Lastly, I've just clarified a couple of bits, and added further info. >How-To-Repeat: N/A >Fix: --- handbook-syslog.diff begins here --- Index: doc/en_US.ISO8859-1/books/handbook/network-servers/chapter.sgml =================================================================== RCS file: /home/dcvs/doc/en_US.ISO8859-1/books/handbook/network-servers/chapter.sgml,v retrieving revision 1.113 diff -u -r1.113 chapter.sgml --- doc/en_US.ISO8859-1/books/handbook/network-servers/chapter.sgml 26 Dec 2008 03:19:02 -0000 1.113 +++ doc/en_US.ISO8859-1/books/handbook/network-servers/chapter.sgml 30 Dec 2008 14:37:15 -0000 @@ -5040,6 +5040,26 @@ be logged to the file specified previously, /var/log/logclient.log. + The server machine must also have the following listing + placed inside /etc/rc.conf: + + syslogd_enable="YES" +syslogd_flags="-a logclient.example.com -vv" + + The first option will enable the syslogd + daemon on boot up, and the second option allows data from the + specified client to be accepted on this server. The latter + part, using , will increase the verbosity + of logged messages. This is extremely useful for tweaking + facilities as administrators are able to see what type of + messages are being logged under which facility. + + Multiple options may be specified to + allow logging from multiple clients. IP + addresses and whole netblocks may also be specified, see the + &man.syslog.3; manual page for a full list of possible + options. + Finally, the log file should be created. The method used does not matter, but &man.touch.1; works great for situations such as this: @@ -5066,7 +5086,7 @@ to a logging server in addition to keeping local copies. Similar to log servers, clients must also meet a few minimum - requirements. + requirements: @@ -5088,20 +5108,18 @@ Client configuration is a bit more relaxed when compared - to that of the servers. The client machine must also have the + to that of the servers. The client machine must have the following listing placed inside /etc/rc.conf: syslogd_enable="YES" -syslogd_flags="-a logclient.example.com -vv" +syslogd_flags="-s -vv" - The first option will enable the syslogd - daemon on boot up, and the second line allows data from the - client to be accepted on this server. The latter part, using - , will increase the verbosity of logged - messages. This is extremely useful for tweaking facilities as - administrators are able to see what type of messages are being - logged under which facility. + As before, these entries will enable the + syslogd daemon on boot up, and increases + the verbosity of logged messages. The + option prevents logs from being accepted by this client from + other hosts. Facilities describe the system part for which a message is generated. For an example, ftp and @@ -5128,14 +5146,15 @@ &prompt.root; /etc/rc.d/syslogd restart To test that log messages are being sent across the network, - use &man.logger.1; to send a message to + use &man.logger.1; on the client to send a message to syslogd: &prompt.root; logger "Test message from logclient" - This message should now exist in - /var/log/messages on both the client - and the server. + This message should now exist both in + /var/log/messages on the client, and + /var/log/logclient.log on the + log server. --- handbook-syslog.diff ends here --- >Release-Note: >Audit-Trail: >Unformatted: From remko at FreeBSD.org Wed Dec 31 11:53:05 2008 From: remko at FreeBSD.org (remko@FreeBSD.org) Date: Wed Dec 31 11:53:11 2008 Subject: docs/130075: [patch] Changes to handbook syslogd section Message-ID: <200812311153.mBVBr47p049275@freefall.freebsd.org> Synopsis: [patch] Changes to handbook syslogd section State-Changed-From-To: open->closed State-Changed-By: remko State-Changed-When: Wed Dec 31 11:53:04 UTC 2008 State-Changed-Why: Committed. Thanks! http://www.freebsd.org/cgi/query-pr.cgi?pr=130075 From dfilter at FreeBSD.ORG Wed Dec 31 12:00:08 2008 From: dfilter at FreeBSD.ORG (dfilter service) Date: Wed Dec 31 12:00:20 2008 Subject: docs/130075: commit references a PR Message-ID: <200812311200.mBVC04eb049408@freefall.freebsd.org> The following reply was made to PR docs/130075; it has been noted by GNATS. From: dfilter@FreeBSD.ORG (dfilter service) To: bug-followup@FreeBSD.org Cc: Subject: Re: docs/130075: commit references a PR Date: Wed, 31 Dec 2008 11:52:41 +0000 (UTC) remko 2008-12-31 11:52:26 UTC FreeBSD doc repository Modified files: en_US.ISO8859-1/books/handbook/network-servers chapter.sgml Log: Import a few changes to the new syslogd chapter which clarifies some confusion. PR: 130075 Submitted by: Gavin Revision Changes Path 1.115 +33 -14 doc/en_US.ISO8859-1/books/handbook/network-servers/chapter.sgml _______________________________________________ cvs-all@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/cvs-all To unsubscribe, send any mail to "cvs-all-unsubscribe@freebsd.org" From brucec at FreeBSD.org Wed Dec 31 14:49:17 2008 From: brucec at FreeBSD.org (brucec@FreeBSD.org) Date: Wed Dec 31 14:49:23 2008 Subject: docs/129962: [newusb] usbconfig(8) refers to non-existant usb2_core(4) Message-ID: <200812311449.mBVEnGVl081836@freefall.freebsd.org> Synopsis: [newusb] usbconfig(8) refers to non-existant usb2_core(4) Responsible-Changed-From-To: freebsd-doc->freebsd-usb Responsible-Changed-By: brucec Responsible-Changed-When: Wed Dec 31 14:48:47 UTC 2008 Responsible-Changed-Why: reassign http://www.freebsd.org/cgi/query-pr.cgi?pr=129962 From murray at stokely.org Wed Dec 31 22:27:17 2008 From: murray at stokely.org (Murray Stokely) Date: Wed Dec 31 22:27:23 2008 Subject: Volunteers Needed to add Subtitles to Conference Videos Message-ID: <2a7894eb0812311427q7125e48dr8d4c2b5c5abee2b2@mail.gmail.com> We now have over 23 videos uploaded to the BSD Conferences video channel from MeetBSD, NYCBSDCon, and other BSD conferences. I'd really like to add subtitles to the YouTube metadata as this has been requested by several users. Once we have subtitles they will be autotmatically machine translated so that users can choose captions in the language they are most comfortable with. There are a variety of tools you can use to record a transcription of the video. One that I tried recently was the webservice Overstream : http://www.overstream.net You simply give it the URL for the YouTube video as it is playing and it lets you add caption overlays and modify the timings to sync it up properly. The end result should be a text file with caption and timings which we can then upload to different video services to provide the captioning on demand. If you have any experience with this, or if you'd like to try to caption one of the videos, please let me know. Thanks and happy new year! - Murray From murray at stokely.org Wed Dec 31 22:32:59 2008 From: murray at stokely.org (Murray Stokely) Date: Wed Dec 31 22:33:05 2008 Subject: Volunteers Needed to add Subtitles to Conference Videos In-Reply-To: <2a7894eb0812311427q7125e48dr8d4c2b5c5abee2b2@mail.gmail.com> References: <2a7894eb0812311427q7125e48dr8d4c2b5c5abee2b2@mail.gmail.com> Message-ID: <2a7894eb0812311432o4ac4ac88g49fd59ab63ea2457@mail.gmail.com> I forgot to include two additional help topics / videos that provide more background about adding subtitles : http://help.youtube.com/support/youtube/bin/answer.py?answer=100079 http://help.youtube.com/support/youtube/bin/answer.py?answer=100077&cbid=-187pqdnf2wsk7&src=cb&lev=answer There are standard formats for these things so the subtitles could be used by other video hosting services as well. - Murray On Wed, Dec 31, 2008 at 2:27 PM, Murray Stokely wrote: > We now have over 23 videos uploaded to the BSD Conferences video > channel from MeetBSD, NYCBSDCon, and other BSD conferences. > > I'd really like to add subtitles to the YouTube metadata as this has > been requested by several users. Once we have subtitles they will be > autotmatically machine translated so that users can choose captions in > the language they are most comfortable with. > > There are a variety of tools you can use to record a transcription of > the video. One that I tried recently was the webservice Overstream : > > http://www.overstream.net > > You simply give it the URL for the YouTube video as it is playing and > it lets you add caption overlays and modify the timings to sync it up > properly. > > The end result should be a text file with caption and timings which we > can then upload to different video services to provide the captioning > on demand. > > If you have any experience with this, or if you'd like to try to > caption one of the videos, please let me know. Thanks and happy new > year! > > - Murray >