From owner-freebsd-doc@FreeBSD.ORG Mon Sep 19 05:02:28 2011 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 2C699106566C for ; Mon, 19 Sep 2011 05:02:28 +0000 (UTC) (envelope-from royce.williams@gmail.com) Received: from mail-iy0-f182.google.com (mail-iy0-f182.google.com [209.85.210.182]) by mx1.freebsd.org (Postfix) with ESMTP id 000478FC08 for ; Mon, 19 Sep 2011 05:02:27 +0000 (UTC) Received: by iadk27 with SMTP id k27so7698104iad.13 for ; Sun, 18 Sep 2011 22:02:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:from:date:message-id:subject:to:content-type; bh=hnXp64+CMGpXO9aFSPwgr0BDAj58qnJVEfY41vp3p+U=; b=G+C9TqKBvdAW3aCfYCIf87dOu5UGDKPaQHiMNDoLMXUwgoW9YlpUAICLAm3+F0rCHn fBushDLk92+HLuLlK/nBzJ2Ul6R3nno3KlCWgRJkcgkZw/jGmlfCrFA6kaVa+doEFXni KwfYnKBk5Ysqx68pRiuNOu64DLRzbEllGn35g= Received: by 10.42.163.195 with SMTP id d3mr499032icy.158.1316407203116; Sun, 18 Sep 2011 21:40:03 -0700 (PDT) MIME-Version: 1.0 Received: by 10.231.48.67 with HTTP; Sun, 18 Sep 2011 21:39:43 -0700 (PDT) From: Royce Williams Date: Sun, 18 Sep 2011 20:39:43 -0800 Message-ID: To: freebsd-doc@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Subject: hardware Rosetta Stone? X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Sep 2011 05:02:28 -0000 The tl;dr version: Let's start documenting our implicit knowledge about hardware. It will be significant force multiplier. If we start a stub on the wiki, it could become useful relatively quickly without a lot of effort. The long version: I've followed a few list threads that end with "Go talk to Vendor X about that." Developers, vendors and hardware owners are all busy, so this can be hard. Most hardware vendors don't have someone like Intel's Jack Vogel - competent, constructive, and paying close attention to the relevant freebsd-* lists. Even if Jack misses a message, everyone else on the lists knows to say, "Hey, send that to Jack." I've also spent a lot of time painstakingly reconstructing knowledge from multiple forums in order to arrive at The Whole Truth about a specific piece of hardware. Someone knows the answer off of the top of their head, but that person is busy frying bigger fish -- and they should be. Caching the results of that work would be a high-leverage activity. I propose creating a hardware Rosetta Stone of sorts. It would be sort of a cross between the Hardware Compatibility list, parts of Jeremy Chadwick's list of known issues, some FAQs, and a list of FreeBSD folks to coordinate between vendors and the project. As a quick start, I propose a wiki page that would contain something like these tuples: * Hardware family * Name of vendor * Brief advice on how to work with that vendor. * Identifying device info (PCI/USB IDs, etc.) * Links to significant PRs. * Link to a FAQ page/section for that hardware/drivers. * Name of coordinating volunteer(s) I'd bet that there are already some de facto vendor "ambassadors" of sorts who could seed parts of the initial list pretty quickly. Benefits: * Developers (who already get peppered with questions about given hardware) only have to answer a question once, and simply link to the Rosetta Stone thereafter. * Non-developers can take their hard-won research and put it where others can reliably find it. * Newbies spend less time chasing their tails and FAQing the lists. * Vendors get a consistent voice from, and more deliberately connect with, the FreeBSD community. * Developers who want to tackle a hardware family can easily survey the state thereof. * Vendors who are hard to connect with might be swayed by a large list of "this vendor won't work with us, but hey, their competitor is totally helpful" data points. * People could rotate through ambassadorship, to spread knowledge and prevent burnout. * Everyone gets to spend more time doing what matters. If I'm reinventing a wheel, any breadcrumbs appreciated. (I got this idea from a club I'm in that has a semi-official ambassador to eBay -- which has really benefited both eBay and the club -- and also thinking about Jack, and Jeremy's list). Royce From owner-freebsd-doc@FreeBSD.ORG Mon Sep 19 06:22:15 2011 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7C25B106566C for ; Mon, 19 Sep 2011 06:22:15 +0000 (UTC) (envelope-from linimon@lonesome.com) Received: from mail.soaustin.net (pancho.soaustin.net [76.74.250.40]) by mx1.freebsd.org (Postfix) with ESMTP id 5D7068FC13 for ; Mon, 19 Sep 2011 06:22:15 +0000 (UTC) Received: by mail.soaustin.net (Postfix, from userid 502) id 1FC4B5615B; Mon, 19 Sep 2011 01:22:15 -0500 (CDT) Date: Mon, 19 Sep 2011 01:22:15 -0500 From: Mark Linimon To: Kamil Choudhury Message-ID: <20110919062215.GC17611@lonesome.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) Cc: Jack Tang , "freebsd-doc@freebsd.org" Subject: Re: Appeal for updating the java page X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Sep 2011 06:22:15 -0000 I'd be happy to see our docs updated, but don't have time myself to dedicate to the effort. You might try asking on the freebsd-java@ mailing list (http://docs.freebsd.org/mail/archive/freebsd-java.html) to see if anyone has a more current writeup. mcl From owner-freebsd-doc@FreeBSD.ORG Mon Sep 19 11:06:07 2011 Return-Path: Delivered-To: freebsd-doc@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6B7A11065670 for ; Mon, 19 Sep 2011 11:06:07 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 591668FC16 for ; Mon, 19 Sep 2011 11:06:07 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p8JB67P8072700 for ; Mon, 19 Sep 2011 11:06:07 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p8JB66oF072698 for freebsd-doc@FreeBSD.org; Mon, 19 Sep 2011 11:06:06 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 19 Sep 2011 11:06:06 GMT Message-Id: <201109191106.p8JB66oF072698@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: FreeBSD doc list Cc: Subject: Current unassigned doc problem reports X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Sep 2011 11:06:07 -0000 (Note: an HTML version of this report is available at http://www.freebsd.org/cgi/query-pr-summary.cgi?category=doc .) The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o docs/160698 doc Remove outdated FreeBSD Jumpstart guide o docs/160696 doc style(9) should be mentioned in the devs' handbook o docs/160549 doc [handbook] link aggreggation (lagg) page does not have o docs/160491 doc [patch] reaper of the dead: remove ancient FAQ entries o docs/160447 doc [handbook] Developer's Handbook contains some outdated o docs/160446 doc [handbook] Handbook sound setup seems outdated o docs/160445 doc [handbook] Handbook does not mention ACL o docs/160399 doc Man page for re(4) missing jumbo frames info o docs/160269 doc [patch] Handbook wireless section: sand off some rough o docs/159898 doc [patch] libusb.3 whitespace, markup, grammar fixes o docs/159897 doc [handbook] [patch] improve HAST section of Handbook o docs/159854 doc [patch] grammar updates for carp.4 o docs/159551 doc [patch] ports(7) makes no mention of LOCALBASE o docs/159374 doc [handbook] Difficulty following guide on configuring l o docs/159307 doc [patch] lpd smm chapter unconditionally installed o docs/159298 doc [handbook] document Konqueror with Webkit support to i o docs/158813 doc [patch] grammar updates for jme(4) o docs/158388 doc Incorrect documentation of LOCAL_SCRIPT in release(7) o docs/158387 doc The tree(3) man should mention the RB_FOREACH_SAFE() A o docs/158378 doc cpio/bsdcpio(1) man page does not document -0 and --nu o docs/157908 doc [handbook] Description of post-install should include o docs/157698 doc [patch] gpart(8) man page contains old/incorrect size o docs/157453 doc [patch] document 16-fib cap in setfib.2 o docs/157452 doc [patch] grammar and style nits in ipfw.8 o docs/157337 doc [handbook] [patch] Indentation changes to network serv o docs/157316 doc [patch] update devstat(9) man page o docs/157234 doc [patch] nullfs(5): //proc/curproc/file returns "unknow o docs/157049 doc FreeBSD Handbook: Chapter 14 (Security) Inaccuracy o docs/156955 doc bug in share/man/man2/setsockopt.2 a docs/156920 doc isspecial(3) is not helpful o docs/156815 doc chmod(1): manpage should describe that chmod kicks +t o docs/156689 doc stf(4) output-only documentation gives bad configurati f docs/156187 doc [handbook] [patch] Add bsnmpd to handbook o docs/156081 doc troff falls with troff.core with UTF-8 man with incorr o docs/155989 doc [patch] Fix offset in boot.config(5) o docs/155982 doc [handbook] reaper of the dead: remove reference to flo o docs/155773 doc dialog(1): dialog manpages not updated o docs/155149 doc [patch] don't encourage using xorg.conf outside of PRE o docs/154838 doc update cvs-tags information on releng_* to reflect sup o docs/154502 doc xdm authorization failure when used with E17 window ma o docs/153958 doc ksu man-page documented, but not installed o docs/153738 doc [patch] Docuement requirement to alter some sysctls wh a docs/153012 doc [patch] iostat(8) requires an argument to -c option o docs/151752 doc pw.conf(5) doesn't define format for file clearly o docs/151367 doc [patch] Update for puc.4 man page o docs/150991 doc [patch] Install upgtfw using pkg_add as advised in upg o docs/150917 doc [patch] icmp.4, wrong description of icmplim and icmpl o docs/150877 doc ambiguity in newsyslog(8) man page about zfs with comp o docs/150365 doc [make.conf] [patch] remove BDECFLAGS from make.conf(5) o docs/150255 doc dtrace description should mention makeoptions DEBUG=-g o docs/150219 doc zfs(8) manual page misses jail/unjail o docs/149574 doc [patch] update mi_switch(9) man page o docs/149522 doc Russian network article: incorrect translation about n o docs/149051 doc [request] No document for clang or clang++ o docs/149047 doc [patch] tcsh(1) bears no mention of brace expansion in o docs/148987 doc [patch] {MD[245]|SHA_|SHA1_|SHA256_}{End|File|FileChun o docs/148984 doc [handbook] Mistake in section 16.15.4 of the handbook o docs/148680 doc [sysctl][patch] Document some sys/kern sysctls o docs/148071 doc Failover mode between wired and wireless interfaces o docs/147995 doc elf.5 man page has has missing reference o docs/146958 doc bad link to "XaQti XMAC II datasheet" in sk(4) manual o docs/146521 doc [handbook] Update IPv6 system handbook section to ment o docs/145719 doc [patch] 7.3 relnotes erroneously describes new getpage o docs/145699 doc hexdump(1) mutes all format qualifier output following o docs/145644 doc Add artical about creating manpage from scratch o docs/145069 doc Dialup firewalling with FreeBSD article out dated. o docs/145067 doc Remove all reference to floppy installs o docs/145066 doc Update for new uart dev names for serial port. s docs/144818 doc all mailinglist archives dated 19970101 contain traili o docs/144630 doc [patch] domainname(1) manpage contains old information o docs/144537 doc Missing _mdconfig_list and _mdconfig2_list explanation o docs/144515 doc [handbook] Expand handbook Table of contents o docs/144488 doc share/examples/etc/make.conf: contains dangerous examp o docs/144408 doc [patch] update makefs(8) (remove device option) o docs/143850 doc procfs(5) manpage for status > controlling terminal is o docs/143416 doc [handbook] IPFW handbook page issues o docs/143408 doc man filedesc(9) is missing o docs/142168 doc [patch] ld(1): ldd(1) not mentioned in ld(1) manpage o docs/141032 doc misleading documentation for rtadvd.conf(5) raflags se s docs/140847 doc [request] add documentation on ECMP and new route args o docs/140457 doc [patch] Grammar fix for isspace(3) o docs/140444 doc [patch] New Traditional Chinese translation of custom- o docs/140375 doc [UPDATE] Updated zh_TW.Big5/articles/nanobsd o docs/139336 doc [request] ZFS documentation suggestion o docs/139165 doc gssapi.3 man page out of sync with between crypto and o docs/139018 doc translation of submitting.sgml from docproj/submitting o docs/138845 doc Exceeding kern.ipc.maxpipekva refers to tuning(7) whic o docs/138663 doc system(3) man page confuses users about "return value o docs/138485 doc bpf(4) and ip(4) man pages missing important corner ca o docs/136712 doc [handbook] [patch] draft new section on gmirror per pa o docs/136666 doc [handbook] Configure serial port for remote kernel deb o docs/136035 doc ftpchroot(5) omits an important option o docs/135516 doc [patch] pax(1) manual not mentioning chflags unawarene o docs/135475 doc [patch] jot(1) manpage and behaviour differ o docs/134123 doc The RUNQUEUE(9) man page is out of date o docs/132839 doc [patch] Fix example script in ldap-auth article o docs/132718 doc [handbook] Information about adding a new mirror is ou o docs/132260 doc dhcpd(8) pid not stored in documented location o docs/132190 doc EPERM explanation for send(2), sendto(2), and sendmsg( o docs/131918 doc [patch] Fixes for the BPF(4) man page o docs/131626 doc [patch] dump(8) "recommended" cache option confusing o docs/130238 doc nfs.lockd man page doesn't mention NFSLOCKD option or o docs/129671 doc New TCP chapter for Developer's Handbook (from rwatson o docs/129464 doc using packages system o docs/129095 doc ipfw(8): Can not check that packet originating/destine s docs/128356 doc [request] add Firefox plugin for FreeBSD manual pages o docs/127908 doc [patch] readdir(3) error documentation s docs/127844 doc Example code skeleton_capture_n.c in meteor(4) manpage o docs/126590 doc [patch] Write routine called forever in Sample Echo Ps o docs/126484 doc libc function res-zonscut2 is not documented o docs/125921 doc lpd(8) talks about blocks in minfree while it is KB in f docs/122052 doc minor update on handbook section 20.7.1 o docs/121952 doc Handbook chapter on Network Address Translation wrong o docs/121585 doc [handbook] Wrong multicast specification s docs/121541 doc [request] no man pages for wlan_scan_ap o docs/121312 doc RELNOTES_LANG breaks release if not en_US.ISO8859-1 o docs/121173 doc [patch] mq_getattr(2): mq_flags mistakenly described a s docs/120917 doc [request]: Man pages mising for thr_xxx syscalls o docs/120539 doc Inconsistent ipfw's man page o docs/120125 doc [patch] Installing FreeBSD 7.0 via serial console and o docs/120024 doc resolver(5) and hosts(5) need updated for IPv6 o docs/119545 doc books/arch-handbook/usb/chapter.sgml formatting o docs/118902 doc [patch] wrong signatures in d2i_RSAPublicKey man pages o docs/118214 doc close(2) error returns incomplete o docs/118020 doc ipfilter(4): man pages query for man 4 ipfilter return o docs/116116 doc mktemp (3) re/move note o docs/116080 doc PREFIX is documented, but not the more important LOCAL p docs/115065 doc [patch] sync ps.1 with p_flag and keywords o docs/114371 doc [patch] [ip6] rtadvd.con(5) should show how to adverti o docs/114139 doc mbuf(9) has misleading comments on M_DONTWAIT and M_TR o docs/113194 doc [patch] [request] crontab.5: handling of day-in-month o docs/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/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 p docs/110061 doc [patch] tuning(7) missing reference to vfs.read_max o docs/109981 doc No manual entry for post-grohtml o docs/109977 doc No manual entry for ksu o docs/109973 doc No manual entry for c++filt o docs/109972 doc No manual entry for zless/bzless f docs/109226 doc [request] No manual entry for sntp o docs/109201 doc [request]: manual for callbootd a docs/108980 doc list of missing man pages o docs/106135 doc [request] articles/vinum needs to be updated o docs/105608 doc fdc(4) debugging description staled o docs/104879 doc Howto: Listen to IMA ADPCM .wav files on FreeBSD box o docs/102719 doc [patch] ng_bpf(4) example leads to unneeded promiscuos o docs/100196 doc man login.conf does explain not "unlimited" o docs/99506 doc FreeBSD Handbook addition: IPv6 Server Settings o docs/98974 doc Missing tunables in loader(8) manpage o docs/98115 doc Missing parts after rendering handbook to RTF format o docs/96207 doc Comments of a sockaddr_un structure could confuse one o docs/94625 doc [patch] growfs man page -- document "panic: not enough o docs/92626 doc jail manpage should mention disabling some periodic sc o docs/91506 doc ndis(4) man page should be more specific about support o docs/91149 doc read(2) can return EINVAL for unaligned access to bloc o docs/88512 doc [patch] mount_ext2fs(8) man page has no details on lar o docs/87936 doc Handbook chapter on NIS/YP lacks good information on a o docs/87857 doc ifconfig(8) wireless options order matters o docs/85128 doc [patch] loader.conf(5) autoboot_delay incompletly desc o docs/84956 doc [patch] intro(5) manpage doesn't mention API coverage o docs/84932 doc new document: printing with an Epson ALC-3000N on Free o docs/84670 doc [patch] tput(1) manpage missing ENVIRONMENT section wi o docs/84317 doc fdp-primer doesn't show class=USERNAME distinctively o docs/84271 doc [patch] compress(1) doesn't warn about nasty link hand o docs/83820 doc getino(3) manpage not installed o docs/81611 doc [patch] natd runs with -same_ports by default o docs/78480 doc Networked printer setup unnecessarily complex in handb o docs/61605 doc [request] Improve documentation for i386 disk geometry o docs/61301 doc [patch] Manpage patch for aue(4) to enable HomePNA fun o docs/59835 doc ipfw(8) man page does not warn about accepted but mean o docs/59477 doc Outdated Info Documents at http://docs.freebsd.org/inf o docs/59044 doc [patch] doc.docbook.mk does not properly handle a sour s docs/54752 doc bus_dma explained in ISA section in Handbook: should b o docs/53751 doc bus_dma(9) incorrectly documents BUS_DMA_ALLOCNOW o docs/53596 doc Updates to mt(1) manual page o docs/53271 doc bus_dma(9) fails to document alignment restrictions o docs/51480 doc Multiple undefined references in the FreeBSD manual pa o docs/50211 doc [patch] doc.docbook.mk: fix textfile creation o docs/48101 doc [patch] Add documentation on the fixit disk o docs/43823 doc [patch] update to environ(7) manpage o docs/41089 doc pax(1) -B option does not mention interaction with -z o docs/40423 doc Keyboard(4)'s definition of parameters to GETFKEY/SETF o docs/38982 doc [patch] developers-handbook/Jail fix o docs/38556 doc EPS file of beastie, as addition to existing examples s docs/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 198 problems total. From owner-freebsd-doc@FreeBSD.ORG Mon Sep 19 14:10:07 2011 Return-Path: Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 641FF1065672 for ; Mon, 19 Sep 2011 14:10:07 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 3916E8FC0C for ; Mon, 19 Sep 2011 14:10:07 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p8JEA7Tc044673 for ; Mon, 19 Sep 2011 14:10:07 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p8JEA7iY044672; Mon, 19 Sep 2011 14:10:07 GMT (envelope-from gnats) Resent-Date: Mon, 19 Sep 2011 14:10:07 GMT Resent-Message-Id: <201109191410.p8JEA7iY044672@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-doc@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, Frederic Culot Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A343D106568B for ; Mon, 19 Sep 2011 14:07:52 +0000 (UTC) (envelope-from culot@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 9190E8FC12 for ; Mon, 19 Sep 2011 14:07:52 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p8JE7qgT044627 for ; Mon, 19 Sep 2011 14:07:52 GMT (envelope-from culot@freefall.freebsd.org) Received: (from culot@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p8JE7qHn044626; Mon, 19 Sep 2011 14:07:52 GMT (envelope-from culot) Message-Id: <201109191407.p8JE7qHn044626@freefall.freebsd.org> Date: Mon, 19 Sep 2011 14:07:52 GMT From: Frederic Culot To: FreeBSD-gnats-submit@FreeBSD.org X-Send-Pr-Version: 3.113 Cc: Subject: docs/160827: New documentation: French translation for linux-users article X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Frederic Culot List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Sep 2011 14:10:07 -0000 >Number: 160827 >Category: docs >Synopsis: New documentation: French translation for linux-users article >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-doc >State: open >Quarter: >Keywords: >Date-Required: >Class: change-request >Submitter-Id: current-users >Arrival-Date: Mon Sep 19 14:10:06 UTC 2011 >Closed-Date: >Last-Modified: >Originator: Frederic Culot >Release: FreeBSD 8.2-STABLE i386 >Organization: >Environment: System: FreeBSD freefall.freebsd.org 8.2-STABLE FreeBSD 8.2-STABLE #4 r220774: Mon Apr 18 13:56:14 UTC 2011 simon@freefall.freebsd.org:/usr/obj/usr/src/sys/FREEFALL i386 >Description: Hi, Attached is my attempt at translating the linux-users article in French. The sgml source could also be found at: http://people.freebsd.org/~culot/doc/linux-users/article.sgml and the resulting html page is available at: http://people.freebsd.org/~culot/doc/linux-users/article.html Regards, culot@ >How-To-Repeat: >Fix: --- article.sgml begins here --- %man; %freebsd; %urls; %mailing-lists; %trademarks; ]>
Guide rapide pour débuter avec FreeBSD à l'attention des utilisateurs de &linux; John Ferrell 2008 The FreeBSD Documentation Project $FreeBSD$ &tm-attrib.freebsd; &tm-attrib.linux; &tm-attrib.intel; &tm-attrib.redhat; &tm-attrib.unix; &tm-attrib.general; Ce document a pour but de familiariser rapidement les utilisateurs de &linux; de niveau intermédiaire à avancé avec les fondamentaux de FreeBSD. Introduction Ce document met en évidence les différences entre &os; et &linux; de telle sorte que les utilisateurs de &linux; d'un niveau intermédiaire jusqu'à avancé puissent se familiariser rapidement avec les fondamentaux de &os;. Il s'agit ici simplement d'une courte introduction technique qui n'a pas pour objectif d'expliciter les différences philosophiques entre les deux systèmes d'exploitation. Ce document part du principe que vous avez déjà installé &os;. Si vous n'avez pas installé &os; ou que vous avez besoin d'aide pour mener à terme le processus d'installation, vous pouvez vous référer au chapitre Installer FreeBSD du Manuel de Référence &os;. Interpréteurs de commandes: Pas de Bash? Ceux qui ont l'habitude de &linux; sont souvent surpris de voir que Bash n'est pas l'interpréteur de commandes par défaut de &os;. En fait, Bash n'est même pas présent dans l'installation par défaut. À la place, &os; utilise &man.tcsh.1; comme interpréteur par défaut. Cependant, Bash ainsi que vos autres interpréteurs de commandes favoris sont disponibles dans la Collection des Paquets et Portages de &os;. Si vous installez d'autres interpréteurs de commandes vous pouvez utiliser &man.chsh.1; pour définir un interpréteur par défaut pour un utilisateur. Il est cependant recommandé de ne pas modifier l'interpréteur de commandes par défaut de root. La raison en est que les interpréteurs de commandes qui ne sont pas inclus dans la distribution de base sont normalement installés dans /usr/local/bin ou /usr/bin. Dans le cas d'un problème les systèmes de fichiers contenant /usr/local/bin et /usr/bin peuvent ne pas être montés. Dans ce cas root n'aurait pas accès à son interpréteur de commandes par défaut, ce qui empêcherait root de pouvoir se connecter. Pour cette raison un second compte root, le compte toor, a été créé pour l'utilisation avec des interpréteurs de commandes qui ne sont pas ceux par défaut. Vous pouvez consulter les questions fréquemment posées sur la sécurité concernant le compte toor pour plus d'informations. Paquets et Portages: Ajouter des logiciels dans &os; En plus de la traditionnelle méthode &unix; d'installation de logiciels (télécharger les sources, extraire, éditer le code source, et compiler), &os; offre deux autres méthodes pour installer des applications: les paquets et les portages. Une liste complète de tous les portages et paquets disponibles se trouve ici. Paquets Les paquets sont des applications pré-compilées, les équivalents &os; des fichiers .deb pour les systèmes basés sur Debian/Ubuntu et des fichiers .rpm pour les systèmes basés sur Red Hat/Fedora. Par exemple, la commande suivante installe Apache 2.2: &prompt.root; pkg_add /tmp/apache-2.2.6_2.tbz Utiliser l'option indique à &man.pkg.add.1; de télécharger automatiquement le paquet et de l'installer, ainsi que toutes ses dépendances: &prompt.root; pkg_add -r apache22 Fetching ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-6.2-release/Latest/apache22.tbz... Done. Fetching ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-6.2-release/All/expat-2.0.0_1.tbz... Done. Fetching ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-6.2-release/All/perl-5.8.8_1.tbz... Done. [snip] To run apache www server from startup, add apache22_enable="YES" in your /etc/rc.conf. Extra options can be found in startup script. Si vous utilisez une version RELEASE de &os; (6.2, 6.3, 7.0, etc..., générallement installée depuis un CD-ROM) pkg_add -r téléchargera les paquets construits spécifiquement pour cette version. Ces paquets peuvent ne pas être la version la plus récente de l'application. Vous pouvez utiliser la variable PACKAGESITE pour surcharger ce comportement par défaut. Par exemple, assignez à PACKAGESITE pour télécharger les paquets les plus récents construits pour les versions 6.X. Vous pouvez en savoir plus sur les versions de &os; dans l'article Choisir la version de &os; qui vous convient le mieux. Pour plus d'informations concernant les paquets vous pouvez vous référer à la section 4.4 du Manuel &os; : Utiliser le Système des Paquets. Les Portages La Collection des Portages est la seconde méthode proposée par &os; pour installer des applications. La Collection des Portages a pour architecture un ensemble de Makefiles et de fichiers correctifs spécifiquement adaptés pour pouvoir installer depuis les sources des applications diverses sur &os;. Lors de l'installation d'un portage le système téléchargera le code source, appliquera tous les correctifs nécessaires, compilera le code, et installera l'application (et fera de même pour toutes ses dépendances). La Collection des Portages, parfois appelée l'arbre des portages (ports tree en anglais), peut être trouvée dans /usr/ports. Nous partons ici du principe que la Collection des Portages a été installée pendant le processus d'installation de &os;. Si la Collection des Portages n'a pas été installée, elle peut être ajoutée à partir des disques d'installation en utilisant &man.sysinstall.8;, ou bien récupérée depuis les serveurs &os; en utilisant &man.csup.1; ou &man.portsnap.8;. Des instructions détaillées concernant l'installation de la Collection des Portages peuvent être consultées dans la section 4.5.1 du Manuel. Installer un portage est aussi simple (en général) que de se déplacer dans le répertoire du portage et de lancer le processus de construction. L'exemple suivant installe Apache 2.2 depuis la Collection des Portages: &prompt.root; cd /usr/ports/www/apache22 &prompt.root; make install clean Un des avantages majeurs d'utiliser les portages pour installer des logiciels est de pouvoir adapter les options d'installation. Par exemple, lors de l'installation d' Apache 2.2 depuis les portages, il vous est possible d'activer mod_ldap en fixant la variable WITH_LDAP de &man.make.1;: &prompt.root; cd /usr/ports/www/apache22 &prompt.root; make WITH_LDAP="YES" install clean Vous pouvez vous référer à la section 4.5 du Manuel &os;, Utiliser la Collection des Portages, pour obtenir plus d'informations concernant la Collection des Portages. Portages ou Paquets, lequels devrais-je utiliser? Les paquets sont simplement des portages pré-compilés, donc il s'agit vraiment de choisir entre une installation depuis les sources (portages) ou une installation utilisant des paquets binaires. Chaque méthode présente ses avantages: Les Paquets (binaire) Installation plus rapide (compiler de grosses applications peut prendre du temps). Inutile de comprendre comment compiler un logiciel. Inutile d'installer des compilateurs sur votre système. Les Portages (source) Possibilité d'adapter les options d'installation (les Paquets sont normalement construits avec les options standards alors qu'avec les portages vous pouvez adapter diverses options comme la construction de modules additionnels ou le changement du chemin par défaut). Vous pouvez appliquer vos propres fichiers correctifs si vous le souhaitez. Si vous n'avez pas de besoins particuliers, les paquets seront probablement tout à fait adaptés à votre situation. S'il vous arrivait d'avoir des besoins spécifiques, les portages seraient plus appropriés (et n'oubliez pas que si vous devez effectuer des adaptations mais que vous préférez les paquets, vous pouvez toujours construire un paquet personalisé en utilisant make package et en copiant le paquet sur d'autres serveurs). Démarrage Système: où sont les niveaux de mise en marche (<foreignphrase>run-levels</foreignphrase>) ? &linux; utilise le système d'initialisation SysV alors que &os; utilise le style traditionel BSD avec &man.init.8;. Avec &man.init.8; il n'existe pas de niveaux de mise en marche et pas de /etc/inittab, mais à la place le démarrage est contrôlé par l'utilitaire &man.rc.8;. Le script /etc/rc lit /etc/defaults/rc.conf et /etc/rc.conf pour déterminer quels services doivent être démarrés. Les services déclarés sont alors démarrés en lançant les scripts d'initialisation du service considéré que l'on trouve dans /etc/rc.d/ et /usr/local/etc/rc.d/. Ces scripts sont similaires aux scripts que l'on trouve dans /etc/init.d/ sur les systèmes &linux;. Pourquoi existe-t-il deux emplacements distincts pour les scripts d'initialisation de services ? Les scripts que l'on trouve dans /etc/rc.d/ sont pour les applications qui font partie du système de base (&man.cron.8;, &man.sshd.8;, &man.syslog.3;, et d'autres). Les scripts dans /usr/local/etc/rc.d/ sont pour les applications installées par les utilisateurs telles que Apache, Squid, etc. Quelle est la différence entre le système de base et les applications installées par l'utilisateur ? FreeBSD est développé comme un système d'exploitation complet. En d'autres termes, le noyau, les librairies système, et les utilitaires présents dans l'espace utilisateur (tels que &man.ls.1;, &man.cat.1;, &man.cp.1;, etc.) sont développés et distribués conjointement. C'est à cela que l'on fait référence en parlant de système de base. Les applications installées par l'utilisateur sont des applications qui ne font pas partie du système de base, tel que Apache, X11, Mozilla Firefox, etc. Ces applications sont généralement installées en utilisant la Collection des Paquets et Portages de &os;. Afin de les conserver à l'écart du système de base, les applications installées par l'utilisateur sont normalement placées dans /usr/local/. Ainsi les binaires installés par l'utilisateur se trouvent dans /usr/local/bin/, les fichiers de configuration dans /usr/local/etc/, et ainsi de suite. Les services sont activés en spécifiant NomDuService_enable="YES" dans /etc/rc.conf (&man.rc.conf.5;). Pour vous faire une idée, vous pouvez consulter les valeurs par défaut du système dans /etc/defaults/rc.conf, ces valeurs par défaut sont surchargées par celles trouvées dans /etc/rc.conf. De plus, lors de l'installation de logiciels additionels, veillez à consulter leur documentation pour déterminer de quelle manière sont activés les services associés, le cas échéant. Le bout de code suivant extrait de /etc/rc.conf active &man.sshd.8; et Apache 2.2. Il spécifie également que Apache devrait être lancé avec SSL. # enable SSHD sshd_enable="YES" # enable Apache with SSL apache22_enable="YES" apache22_flags="-DSSL" Dès lors qu'un service a été activé dans /etc/rc.conf, ce service peut être démarré depuis la ligne de commande (sans avoir à redémarrer le système): &prompt.root; /etc/rc.d/sshd start Si un service n'a pas été activé il peut être démarré depuis la ligne de commande en utilisant : &prompt.root; /etc/rc.d/sshd forcestart Configuration Réseau Interfaces Réseau À la place d'un identifiant générique ethX que &linux; utilise pour identifier une interface réseau, &os; utilise le nom du pilote suivi d'un nombre en tant qu'identifiant. La sortie suivante de &man.ifconfig.8; montre deux interfaces réseau &intel Pro 1000 (em0 et em1) : &prompt.user; ifconfig em0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500 options=b<RXCSUM,TXCSUM,VLAN_MTU> inet 10.10.10.100 netmask 0xffffff00 broadcast 10.10.10.255 ether 00:50:56:a7:70:b2 media: Ethernet autoselect (1000baseTX <full-duplex>) status: active em1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500 options=b<RXCSUM,TXCSUM,VLAN_MTU> inet 192.168.10.222 netmask 0xffffff00 broadcast 192.168.10.255 ether 00:50:56:a7:03:2b media: Ethernet autoselect (1000baseTX <full-duplex>) status: active Configuration IP Une adresse IP peut être assignée à une interface en utilisant &man.ifconfig.8;. Cependant, pour assurer la persistence même après un redémarrage, la configuration IP doit être enregistrée dans /etc/rc.conf. Dans l'exemple suivant sont spécifiés le nom de la machine, l'adresse IP, et la passerelle par défaut: hostname="server1.example.com" ifconfig_em0="inet 10.10.10.100 netmask 255.255.255.0" defaultrouter="10.10.10.1" Utilisez ceci pour configurer une interface pour DHCP: hostname="server1.example.com" ifconfig_em0="DHCP" Pare-feu Tout comme IPTABLES pour &linux;, &os; offre également un pare-feu au niveau du noyau; en fait &os; offre trois pare-feux distincts: IPFIREWALL IPFILTER PF IPFIREWALL ou IPFW (la commande pour gérer un jeu de règles IPFW est &man.ipfw.8;) est le pare-feu développé et maintenu par les développeurs &os;. IPFW peut être couplé avec &man.dummynet.4; pour fournir des possibilités de formattage de trafic et simuler différents types de connections réseau. Voici un exemple de règle IPFW pour autoriser SSH en entrée : ipfw add allow tcp from any to me 22 in via $ext_if IPFILTER est le pare-feu applicatif développé par Darren Reed. Celui-ce n'est pas spécifique à &os; et a été porté sur de nombreux systèmes d'exploitation tels que NetBSD, OpenBSD, SunOS, HP/UX, et Solaris. Voici un exemple de règle IPFILTER pour autoriser SSH en entrée : pass in on $ext_if proto tcp from any to any port = 22 Le dernier pare-feu, PF, est développé par le projet OpenBSD. PF a été créé pour remplacer IPFILTER, ce qui fait que la syntaxe de PF est très similaire à celle de IPFILTER. PF peut être couplé avec &man.altq.4; pour fournir des possibilités de QoS. Voici un exemple de règle PF pour autoriser SSH en entrée : pass in on $ext_if inet proto tcp from any to ($ext_if) port 22 Mettre à jour &os; Il existe trois méthodes différentes pour mettre à jour un système &os; : à partir des sources, les mises à jour binaires, et les disques d'installation. Mettre à jour depuis les sources est la méthode la plus compliquée mais elle offre la plus grande flexibilité. Le processus implique de synchroniser une copie locale du code source de FreeBSD avec les serveurs CVS (Concurrent Versioning System - Système de gestion de Versions Concurrentes) de &os;. Une fois que le code source local est à jour vous pouvez construire les nouvelles versions du noyau et de l'espace utilisateur. Pour plus d'informations concernant les mises à jour depuis les sources vous pouvez consulter le chapitre sur la mise à jour du manuel &os;. Les mises à jour binaires ressemblent aux commandes yum ou apt-get utilisées pour mettre à jour un système &linux;. La commande &man.freebsd-update.8; téléchargera les nouvelles mises à jour et les installera. Les mises à jour peuvent être programmées par l'intermédiaire de &man.cron.8;. Si vous utilisez &man.cron.8; pour programmer vos mises à jour, assurez-vous d'utiliser la commande freebsd-update cron dans votre &man.crontab.1; pour réduire le nombre de machines récupérant les mises à jour au même moment. 0 3 * * * root /usr/sbin/freebsd-update cron La dernière méthode, qui permet de mettre à jour en utilisant les disques d'installation, est simple : démarrez depuis les disques d'installation et sélectionnez l'option de mise à jour. procfs: Disparu mais pas Oublié Avec &linux;, il vous est peut-être arrivé de consulter /proc/sys/net/ipv4/ip_forward pour déterminer si le transfert IP était activé. Avec &os; vous devriez utiliser &man.sysctl.8; pour voir ce réglage ainsi que d'autres réglages système parce que &man.procfs.5; a été abandonné dans la version courante de &os; (notez que sysctl est disponible aussi sous &linux;). Dans l'exemple du transfert IP voici ce que vous utiliseriez pour déterminer si le transfert IP est activé sur votre système FreeBSD : &prompt.user; sysctl net.inet.ip.forwarding net.inet.ip.forwarding: 0 L'option est utilisée pour lister tous les réglages du système : &prompt.user; sysctl -a kern.ostype: FreeBSD kern.osrelease: 6.2-RELEASE-p9 kern.osrevision: 199506 kern.version: FreeBSD 6.2-RELEASE-p9 #0: Thu Nov 29 04:07:33 UTC 2007 root@i386-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC kern.maxvnodes: 17517 kern.maxproc: 1988 kern.maxfiles: 3976 kern.argmax: 262144 kern.securelevel: -1 kern.hostname: server1 kern.hostid: 0 kern.clockrate: { hz = 1000, tick = 1000, profhz = 666, stathz = 133 } kern.posix1version: 200112 ... Certaines de ces valeurs sysctl sont uniquement accessibles en lecture. procfs est parfois nécessaire comme pour faire fonctionner de vieux logiciels, pour examiner des appels système en utilisant &man.truss.1;, et pour la Compatilibité Binaire avec &linux; (celle-ci utilise cependant son propre procfs, &man.linprocfs.5;). Si vous avez besoin de monter procfs vous pouvez ajouter la ligne suivante dans /etc/fstab : proc /proc procfs rw,noauto 0 0 fera en sorte que /proc ne soit pas monté automatiquement lors du démarrage. Et ensuite montez procfs avec : &prompt.root; mount /proc Commandes Usuelles Gestion des Paquets commande &linux; (Red Hat/Debian) équivalent &os; Objectif yum install paquet / apt-get install paquet pkg_add -r paquet Installation de paquet depuis un dépôt distant rpm -ivh paquet / dpkg -i paquet pkg_add -v paquet Installation de paquet rpm -qa / dpkg -l pkg_info Lister les paquets installés Gestion Système commande &linux; équivalent &os; Objectif lspci pciconf Lister les périphériques PCI lsmod kldstat Lister les modules noyau chargés modprobe kldload / kldunload Charger / Décharger les modules noyau strace truss Examiner les appels système Conclusion Nous ésperons que ce document vous a fourni suffisemment d'informations pour que vous puissiez faire vos premiers pas avec &os;. Vous pouvez consulter le Manuel &os; pour une couverture plus complète des sujets abordés ici ainsi que de tous les autres sujets non couverts dans ce document.
--- article.sgml ends here --- >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-doc@FreeBSD.ORG Mon Sep 19 20:37:25 2011 Return-Path: Delivered-To: freebsd-doc@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B3122106564A for ; Mon, 19 Sep 2011 20:37:25 +0000 (UTC) (envelope-from onlineseorankers@gmail.com) Received: from mail-yx0-f182.google.com (mail-yx0-f182.google.com [209.85.213.182]) by mx1.freebsd.org (Postfix) with ESMTP id 75C418FC14 for ; Mon, 19 Sep 2011 20:37:25 +0000 (UTC) Received: by yxk36 with SMTP id 36so5484425yxk.13 for ; Mon, 19 Sep 2011 13:37:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; bh=hDOwS95qGHS27iL5zxNOfToTgvgSHNJnyIEnqfxuccI=; b=ChVjoSqnhTcH0/m8u+0tUXGalaQILYSHAKjliFoUzGJj6LwSmeFA2wAKVn4OXPuWYk LoiarnxF7+4mAtah5b5jrueIrcHmyqgU/cJZUmS/T4dLhVxeZ1BM8df43n+ZoDR2j0uZ AT8GbIAvTxwTPMTXVZRKreSxKyT+VvIPsJJ6s= MIME-Version: 1.0 Received: by 10.68.46.98 with SMTP id u2mr4950587pbm.31.1316463272113; Mon, 19 Sep 2011 13:14:32 -0700 (PDT) Received: by 10.143.78.17 with HTTP; Mon, 19 Sep 2011 13:14:32 -0700 (PDT) Date: Tue, 20 Sep 2011 01:44:32 +0530 Message-ID: From: ben mulder To: freebsd-doc@FreeBSD.org Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: Organic SEO - Freebsd.org X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Sep 2011 20:37:25 -0000 Freebsd.org Team, I thought you might like to know some of the reasons why you are not gettin= g enough Social Media and Organic search engine traffic for Freebsd.org. 1. Social profile is not available in top Social Media websites. 2. Your SEO score is 95%. We can bring it to 100% by implementing on and off-page factors which will fetch better results in major search engines. 3. Your site has 2500 Google back links, this can be improved further. There are many additional improvements that could be made to your website, and if you would like to learn about them, and are curious to know what our working together would involve, then I would be glad to provide you with a detailed analysis in the form of a *WEBSITE AUDIT REPORT *for FREE. To brief you about our company, we are one of the fastest-growing Internet marketing Company of the world. We give 100% unconditional *money back guarantee*. Our clients consistently tell us that their customers find them because the= y are at the top of the Google search rankings. Being at the top left of Google (#1- #3 organic positions) is the best thing you can do for your company's website traffic and online reputation. Sounds interesting? Feel free to email us or alternatively you can provide me with your phone number and the best time to call you. ----------------------------------------------------------------- Best Regards, Ben Mulder SEO Consultant (315)-332-1942 ------------------------------------------------------------------ *PS1*: This is onetime email and you may ask us to =93*REMOVE*=94 you from = our mailing list. *PS2*: I found your site from online advertising but did not click. *PS3*: We operate 24 x7. I will be happy to send you links to price list, 100% money back guarantee, client rankings, client testimonials, =93How we = are different from others?=94, and =93Why should you choose us?=94 on receiving= a response from you. From owner-freebsd-doc@FreeBSD.ORG Tue Sep 20 17:51:30 2011 Return-Path: Delivered-To: doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 87F29106566B for ; Tue, 20 Sep 2011 17:51:30 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) by mx1.freebsd.org (Postfix) with ESMTP id 3019F8FC08 for ; Tue, 20 Sep 2011 17:51:29 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.5/8.14.5) with ESMTP id p8KHb7HH053290 for ; Tue, 20 Sep 2011 11:37:07 -0600 (MDT) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.5/8.14.5/Submit) with ESMTP id p8KHb69j053287 for ; Tue, 20 Sep 2011 11:37:07 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Tue, 20 Sep 2011 11:37:06 -0600 (MDT) From: Warren Block To: doc@freebsd.org Message-ID: User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (wonkity.com [127.0.0.1]); Tue, 20 Sep 2011 11:37:07 -0600 (MDT) Cc: Subject: FAQ updating: software modems X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Sep 2011 17:51:30 -0000 Just noticed that the FAQ still says FreeBSD supports many software modems via add-on software. For example, the comms/ltmdm port adds support for modems based on the very popular Lucent LT chipsets. comms/ltmdm is gone, removed a year ago as unmaintained. Are there any other software modem drivers in ports or elsewhere, or should this entry be removed entirely? From owner-freebsd-doc@FreeBSD.ORG Thu Sep 22 08:44:18 2011 Return-Path: Delivered-To: doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 757291065677 for ; Thu, 22 Sep 2011 08:44:18 +0000 (UTC) (envelope-from abassett@imagine.ie) Received: from mail.imagine.ie (mail2.mail.imagine.ie [IPv6:2a01:268:4::53]) by mx1.freebsd.org (Postfix) with ESMTP id 113F48FC0A for ; Thu, 22 Sep 2011 08:44:17 +0000 (UTC) Received: from localhost (localhost.localdomain [127.0.0.1]) by mail.imagine.ie (Postfix) with ESMTP id CA51F2AA26F for ; Thu, 22 Sep 2011 09:44:16 +0100 (IST) X-Virus-Scanned: imag!ne mail scanner at mail.imagine.ie Received: from mail.imagine.ie ([127.0.0.1]) by localhost (mail.imagine.ie [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 8VMvFl-0-Ich for ; Thu, 22 Sep 2011 09:44:14 +0100 (IST) Received: from imagine.ie (unknown [41.177.13.145]) (Authenticated sender: abassett@imagine.ie) by mail.imagine.ie (Postfix) with ESMTPA id 0F6122AA2E4 for ; Thu, 22 Sep 2011 09:44:11 +0100 (IST) From: "Igaune Zenija" To: doc@freebsd.org Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset="UTF-8" Date: Thu, 22 Sep 2011 01:44:15 -0700 Message-Id: <20110922084412.0F6122AA2E4@mail.imagine.ie> Cc: Subject: Gusevs Nikolajs =?utf-8?b?aXpqxat0?= to.. X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Igaune Zenija List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Sep 2011 08:44:18 -0000 Čau, čau, Lexa! Kur slēpjas Logaicuka Valentina? Es ļoti vēlējos parādīt kā var neilgā laikā tikt pie pieklājīgas naudas summas.. Ja kas, pats arī vari iečekot: http://www.remainstanding.com/laime Spasibočki! Kozlova Lidija From owner-freebsd-doc@FreeBSD.ORG Thu Sep 22 17:40:10 2011 Return-Path: Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 25B6E106567B for ; Thu, 22 Sep 2011 17:40:10 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id F03EB8FC0A for ; Thu, 22 Sep 2011 17:40:09 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p8MHe9H3023076 for ; Thu, 22 Sep 2011 17:40:09 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.4/8.14.4/Submit) id p8MHe9Ge023075; Thu, 22 Sep 2011 17:40:09 GMT (envelope-from gnats) Date: Thu, 22 Sep 2011 17:40:09 GMT Message-Id: <201109221740.p8MHe9Ge023075@freefall.freebsd.org> To: freebsd-doc@FreeBSD.org From: Kaspars Bankovskis Cc: Subject: Re: docs/98115: Missing parts after rendering handbook to RTF format X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Kaspars Bankovskis List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Sep 2011 17:40:10 -0000 The following reply was made to PR docs/98115; it has been noted by GNATS. From: Kaspars Bankovskis To: bug-followup@FreeBSD.org Cc: Subject: Re: docs/98115: Missing parts after rendering handbook to RTF format Date: Thu, 22 Sep 2011 20:31:17 +0300 This is not a doc problem. Please assign it to ports problems: textproc/fixrtf From owner-freebsd-doc@FreeBSD.ORG Thu Sep 22 19:49:31 2011 Return-Path: Delivered-To: doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 48DCB106564A for ; Thu, 22 Sep 2011 19:49:31 +0000 (UTC) (envelope-from kaduk@mit.edu) Received: from dmz-mailsec-scanner-2.mit.edu (DMZ-MAILSEC-SCANNER-2.MIT.EDU [18.9.25.13]) by mx1.freebsd.org (Postfix) with ESMTP id F0DD08FC08 for ; Thu, 22 Sep 2011 19:49:30 +0000 (UTC) X-AuditID: 1209190d-b7be0ae000000a16-78-4e7b8cdc6bd5 Received: from mailhub-auth-3.mit.edu ( [18.9.21.43]) by dmz-mailsec-scanner-2.mit.edu (Symantec Messaging Gateway) with SMTP id 25.C7.02582.CDC8B7E4; Thu, 22 Sep 2011 15:30:36 -0400 (EDT) Received: from outgoing.mit.edu (OUTGOING-AUTH.MIT.EDU [18.7.22.103]) by mailhub-auth-3.mit.edu (8.13.8/8.9.2) with ESMTP id p8MJYSj3021352; Thu, 22 Sep 2011 15:34:28 -0400 Received: from multics.mit.edu (MULTICS.MIT.EDU [18.187.1.73]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.6/8.12.4) with ESMTP id p8MJYR87014043 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 22 Sep 2011 15:34:28 -0400 (EDT) Received: (from kaduk@localhost) by multics.mit.edu (8.12.9.20060308) id p8MJYQnZ023085; Thu, 22 Sep 2011 15:34:26 -0400 (EDT) Date: Thu, 22 Sep 2011 15:34:26 -0400 (EDT) From: Benjamin Kaduk To: Warren Block In-Reply-To: Message-ID: References: User-Agent: Alpine 1.10 (GSO 962 2008-03-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrBIsWRmVeSWpSXmKPExsUixCmqrXunp9rP4MQfaYupH3eyWvw65eHA 5DHj03wWjyMdjxgDmKK4bFJSczLLUov07RK4Mp7+28FasIet4ui0RawNjJNZuxg5OSQETCRO T2yEssUkLtxbz9bFyMUhJLCPUWLDjznsEM4GRonGxo1QmQNMEoc7fzJCOA2MEm2rVzCB9LMI aEtMun+aBcRmE1CRmPkGpIODQ0RAVWLvGWuQMLOAsMTpS3cZQWxhAS2JD5v+soPYnAJ2El9P 7AEbwytgL3G54TAziC0kYCvxZsNssBpRAR2J1funsEDUCEqcnPmEBWKmpcS/tb9YJzAKzkKS moUktYCRaRWjbEpulW5uYmZOcWqybnFyYl5eapGukV5uZoleakrpJkZwoEry7mB8d1DpEKMA B6MSD+/N2Go/IdbEsuLK3EOMkhxMSqK8Fh1AIb6k/JTKjMTijPii0pzU4kOMEhzMSiK8Jv5A Od6UxMqq1KJ8mJQ0B4uSOG/hDgc/IYH0xJLU7NTUgtQimKwMB4eSBO8HYEQKCRalpqdWpGXm lCCkmTg4QYbzAA1/BVLDW1yQmFucmQ6RP8WoyzHl0dYTjEIsefl5qVLivJy9QEUCIEUZpXlw c2AJ5hWjONBbwrxvQUbxAJMT3KRXQEuYgJYoFVaCLClJREhJNTBGzLi3Y2O4x/o/1vz2r723 WxY0T7E853dNbkYq89P8Tu8j+67tEDHevCt+0Yuarce4XVgSFn+9nflDueh1h7x/fGlaqsHk 5or1P7Z/63x//Pa+li2fjdkdFmx5VprZzjQhla9pUsd0pydsC54HVT5s//WhaFMIR+Ojw/mr bssF6sX6yfQeapBUYinOSDTUYi4qTgQA+4OZlAsDAAA= Cc: doc@freebsd.org Subject: Re: FAQ updating: software modems X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Sep 2011 19:49:31 -0000 On Tue, 20 Sep 2011, Warren Block wrote: > Just noticed that the FAQ still says > > FreeBSD supports many software modems via add-on software. For > example, the comms/ltmdm port adds support for modems based on the > very popular Lucent LT chipsets. > > comms/ltmdm is gone, removed a year ago as unmaintained. Are there any other > software modem drivers in ports or elsewhere, or should this entry be removed > entirely? Grep-ing for 'modem' in ports/*/*/pkg-descr seems to reveal just comms/ib-kmod as providing support for modem hardware. Given that it's just the one manufacturer, and modem use is falling away with increased broadband penetration, I would not mind if the entry just went away. (But then, I was the one advocating for removing PLIP/SLIP from the handbook ...) -Ben Kaduk From owner-freebsd-doc@FreeBSD.ORG Thu Sep 22 22:05:20 2011 Return-Path: Delivered-To: freebsd-docs@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 1233) id 92D8D106567D; Thu, 22 Sep 2011 22:05:20 +0000 (UTC) Date: Thu, 22 Sep 2011 22:05:20 +0000 From: Alexander Best To: freebsd-docs@freebsd.org Message-ID: <20110922220520.GA2364@freebsd.org> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="2fHTh5uZTiUOsy+g" Content-Disposition: inline Cc: Subject: minor fix to smp(4) man page X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Sep 2011 22:05:20 -0000 --2fHTh5uZTiUOsy+g Content-Type: text/plain; charset=us-ascii Content-Disposition: inline hi there, could somebody please commit the following fix? thanks in advance. alex --2fHTh5uZTiUOsy+g Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="smp.4.diff" diff --git a/share/man/man4/smp.4 b/share/man/man4/smp.4 index 5d0d983..612a3ce 100644 --- a/share/man/man4/smp.4 +++ b/share/man/man4/smp.4 @@ -23,7 +23,7 @@ .\" .\" $FreeBSD$ .\" -.Dd May 7, 2008 +.Dd September 23, 2011 .Dt SMP 4 .Os .Sh NAME @@ -124,21 +124,20 @@ Since using logical CPUs can cause performance penalties under certain loads, the logical CPUs can be disabled by setting the .Va machdep.hyperthreading_allowed tunable to zero. -.Xr cpuset 1 . .Sh SEE ALSO +.Xr cpuset 1 . .Xr mptable 1 , +.Xr sched_4bsd 4 , +.Xr sched_ule 4 , .Xr loader 8 , .Xr sysctl 8 , .Xr condvar 9 , .Xr msleep 9 , .Xr mtx_pool 9 , .Xr mutex 9 , -.Xr sema 9 , -.Xr sx 9 , .Xr rwlock 9 , -.Xr sched_4bsd 4 , -.Xr sched_ule 4 , -.Xr cpuset 1 +.Xr sema 9 , +.Xr sx 9 .Sh HISTORY The .Nm --2fHTh5uZTiUOsy+g-- From owner-freebsd-doc@FreeBSD.ORG Thu Sep 22 22:30:53 2011 Return-Path: Delivered-To: freebsd-docs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B5E9E106564A; Thu, 22 Sep 2011 22:30:53 +0000 (UTC) (envelope-from gabor@FreeBSD.org) Received: from server.mypc.hu (server.mypc.hu [87.229.73.95]) by mx1.freebsd.org (Postfix) with ESMTP id 721B38FC08; Thu, 22 Sep 2011 22:30:53 +0000 (UTC) Received: from server.mypc.hu (localhost [127.0.0.1]) by server.mypc.hu (Postfix) with ESMTP id 8172B14E60B5; Fri, 23 Sep 2011 00:15:11 +0200 (CEST) X-Virus-Scanned: amavisd-new at server.mypc.hu Received: from server.mypc.hu ([127.0.0.1]) by server.mypc.hu (server.mypc.hu [127.0.0.1]) (amavisd-new, port 10024) with LMTP id FyRuGrMg5tMv; Fri, 23 Sep 2011 00:15:09 +0200 (CEST) Received: from [192.168.1.106] (catv-80-98-232-12.catv.broadband.hu [80.98.232.12]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by server.mypc.hu (Postfix) with ESMTPSA id 51D7C14E60A0; Fri, 23 Sep 2011 00:15:09 +0200 (CEST) Message-ID: <4E7BB367.8040807@FreeBSD.org> Date: Fri, 23 Sep 2011 00:15:03 +0200 From: Gabor Kovesdan User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:9.0a1) Gecko/20110916 Thunderbird/9.0a1 MIME-Version: 1.0 To: Alexander Best References: <20110922220520.GA2364@freebsd.org> In-Reply-To: <20110922220520.GA2364@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-docs@freebsd.org Subject: Re: minor fix to smp(4) man page X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Sep 2011 22:30:53 -0000 On 2011.09.23. 0:05, Alexander Best wrote: > hi there, > > could somebody please commit the following fix? > Thanks for your patch! I just submitted it to re@ for approval. Note, that we do not bump .Dd for such changes, just for real content change. Also, you had a dot instead of a comma in the reference list, which I fixed in my working copy. :) Gabor From owner-freebsd-doc@FreeBSD.ORG Fri Sep 23 00:13:24 2011 Return-Path: Delivered-To: doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C6FF5106564A for ; Fri, 23 Sep 2011 00:13:24 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) by mx1.freebsd.org (Postfix) with ESMTP id 807F68FC0C for ; Fri, 23 Sep 2011 00:13:24 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.5/8.14.5) with ESMTP id p8N0DNVu014641; Thu, 22 Sep 2011 18:13:23 -0600 (MDT) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.5/8.14.5/Submit) with ESMTP id p8N0DNv1014638; Thu, 22 Sep 2011 18:13:23 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Thu, 22 Sep 2011 18:13:23 -0600 (MDT) From: Warren Block To: Benjamin Kaduk In-Reply-To: Message-ID: References: User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (wonkity.com [127.0.0.1]); Thu, 22 Sep 2011 18:13:23 -0600 (MDT) Cc: doc@freebsd.org Subject: Re: FAQ updating: software modems X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Sep 2011 00:13:24 -0000 On Thu, 22 Sep 2011, Benjamin Kaduk wrote: > On Tue, 20 Sep 2011, Warren Block wrote: > >> Just noticed that the FAQ still says >> >> FreeBSD supports many software modems via add-on software. For >> example, the comms/ltmdm port adds support for modems based on the >> very popular Lucent LT chipsets. >> >> comms/ltmdm is gone, removed a year ago as unmaintained. Are there any >> other software modem drivers in ports or elsewhere, or should this entry be >> removed entirely? > > Grep-ing for 'modem' in ports/*/*/pkg-descr seems to reveal just > comms/ib-kmod as providing support for modem hardware. Given that it's just > the one manufacturer, and modem use is falling away with increased broadband > penetration, I would not mind if the entry just went away. Well, the old bad kind of modem (dialup POTS) is going away. The iBurst and many other new modems are wireless. Whether any wireless ones are host-based, I don't know, but haven't seen any questions about such. > (But then, I was the one advocating for removing PLIP/SLIP from the handbook > ...) This little FAQ question should not be quite as big a deal. From owner-freebsd-doc@FreeBSD.ORG Fri Sep 23 06:17:59 2011 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A8545106566C for ; Fri, 23 Sep 2011 06:17:59 +0000 (UTC) (envelope-from 5109163z14070@bounce.minufcort.net) Received: from mx02.minufcort.net (mx02.minufcort.net [195.43.150.23]) by mx1.freebsd.org (Postfix) with ESMTP id E9DC98FC08 for ; Fri, 23 Sep 2011 06:17:58 +0000 (UTC) Received: by mx02.minufcort.net (Postfix, from userid 0) id 1001B6C21B; Fri, 23 Sep 2011 07:54:37 +0200 (CEST) Content-Disposition: inline Content-Transfer-Encoding: 8bit Date: Fri, 23 Sep 2011 07:54:37 +0200 From: Airchaud Diffusion To: Errors-To: bounce@minufcort.net X-Feas-Surl: http://mx14.minufcort.net X-Mailer: mx02minufcort.net Message-Id: <20110923055449.1001B6C21B@mx02.minufcort.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1"; X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Grandes promos sur chauffages atelier, serre, chantier... X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Sep 2011 06:17:59 -0000 [1]PLUS DE 300 MODELES DE CHAUFFAGE, FIXES OU MOBILES, TOUTES PUISSANCES Anticipez l'hiver : profitez de nos PROMOTIONS* Dlais de livraison : 48 72 h - FRANCO DE PORT (hors Corse) CHAUFFAGES FIXES avec brleur fuel 116 KW 9280 m3/h 186 KW 13 200 m3/h 233 KW 17 850 m3/h 349 KW 24 100 m3/h [2][sf130.jpg] [3][sf190.jpg] [4][sf260.jpg] [5][sf360.jpg] 4698 HT au lieu de : 5526 HT Rf. SF130 5663 HT au lieu de : 6650 HT Rf. SF190 6819 HT au lieu de : 8022 HT Rf. SF260 9424 HT au lieu de : 11086 HT Rf. SF360 CHAUFFAGES MOBILES FUEL avec rservoir 32 KW 1370 m3/h 55 KW 2975 m3/h 85 KW 5500 m3/h 105 KW 5500 m3/h [6][ec32.jpg] [7][ec55.jpg] [8][ec85.jpg] [9][ec110.jpg] 1144 HT au lieu de : 1345 HT Rservoir 42 L Rf. EC32 1611 HT au lieu de : 1895 HT Rservoir 65 L Rf. EC55 1879 HT au lieu de : 2210 HT Rservoir 105 L Rf. EC85 2559 HT au lieu de : 3010 HT Rservoir 120 L Rf. EC110 CHAUFFAGES FIXES FUEL sans rservoir 23 KW 1500 m3/h 35 KW 1700 m3/h 35 KW 2850 m3/h 70 KW 5100 m3/h [10][sf25.jpg] [11][sf35.jpg] [12][sp35.jpg] [13][sp70.jpg] 2051 HT au lieu de : 2412 HT Rf. SF25 2222 HT au lieu de : 2614 HT Rf. SF35 1866 HT au lieu de : 2195 HT Rf. SP35 2270 HT au lieu de : 2670 HT Rf. SP70 CHAUFFAGES MOBILES FUEL sans rservoir 105 KW 6000 m3/h 135 KW 8000 m3/h 175 KW 10500 m3/h 220 KW 12500 m3/h [14][jumbo105h.jpg] [15][jumbo135h.jpg] [16][jumbo175h.jpg] [17][jumbo220h.jpg] 3314 HT au lieu de : 3898 HT Rf. Jumbo 105H 3698 HT au lieu de : 4350 HT Rf. Jumbo 135H 4301 HT au lieu de : 5060 HT Rf. Jumbo 175H 4888 HT au lieu de : 5750 HT Rf. Jumbo 220H CHAUFFAGES FUEL avec rservoir Radiant fuel 35 KW 2850 m3/h 70 KW 5100 m3/h 115 KW 7600 m3/h 42,7 KW [18][f35.jpg] [19][f70.jpg] [20][f115.jpg] [21][star1-star2.jpg] 2134 HT au lieu de : 2510 HT Rservoir 35 L Rf. F35 2567 HT au lieu de : 3020 HT Rservoir 65 L Rf. F70 4301 HT au lieu de : 5060 HT Rservoir 105 L Rf. F115 1458 HT au lieu de : 1715 HT Rservoir 65 L Rf. STAR1 [22]Visitez notre site SARL au capital de 148 500 Siret 444 448 898 00015 35, route de Colmar 67600 Selestat Tl. : 03 88 08 67 05 Fax : 03 88 08 67 39 Un renseignement ? Tl. 03 88 08 67 05 Nous envoyer un message : [23]CLIQUEZ ICI Commande par fax au 03 88 08 67 39 [cale20.gif] [cale141.gif] [cale12.gif] [cale141.gif] [cale12.gif] [cale141.gif] [cale12.gif] [cale20.gif] Ne pas rpondre cet email. Pour nous contacter utilisez le formulaire sur notre site ou appelez-nous au : 03 88 08 67 05 (*) Promotions valables jusqu'au 31/10/2011 Pour envoyer ce message un ami, [24]cliquez ici Si vous ne souhaitez plus recevoir de messages, [25]cliquez ici serial : 467704117 References 1. http://mx14.minufcort.net/467702109-56725-14070.html 2. http://mx14.minufcort.net/467702109-56726-14070.html 3. http://mx14.minufcort.net/467702109-56727-14070.html 4. http://mx14.minufcort.net/467702109-56728-14070.html 5. http://mx14.minufcort.net/467702109-56729-14070.html 6. http://mx14.minufcort.net/467702109-56730-14070.html 7. http://mx14.minufcort.net/467702109-56731-14070.html 8. http://mx14.minufcort.net/467702109-56732-14070.html 9. http://mx14.minufcort.net/467702109-56733-14070.html 10. http://mx14.minufcort.net/467702109-56734-14070.html 11. http://mx14.minufcort.net/467702109-56735-14070.html 12. http://mx14.minufcort.net/467702109-56736-14070.html 13. http://mx14.minufcort.net/467702109-56737-14070.html 14. http://mx14.minufcort.net/467702109-56738-14070.html 15. http://mx14.minufcort.net/467702109-56739-14070.html 16. http://mx14.minufcort.net/467702109-56740-14070.html 17. http://mx14.minufcort.net/467702109-56741-14070.html 18. http://mx14.minufcort.net/467702109-56742-14070.html 19. http://mx14.minufcort.net/467702109-56743-14070.html 20. http://mx14.minufcort.net/467702109-56744-14070.html 21. http://mx14.minufcort.net/467702109-56745-14070.html 22. http://mx14.minufcort.net/467702109-56746-14070.html 23. http://mx14.minufcort.net/467702109-56747-14070.html 24. http://mx14.minufcort.net/467702109-5614-14070-S.html 25. http://mx14.minufcort.net/467702109-17716-14070-W.html From owner-freebsd-doc@FreeBSD.ORG Fri Sep 23 16:03:40 2011 Return-Path: Delivered-To: freebsd-docs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3F7EA106566C for ; Fri, 23 Sep 2011 16:03:40 +0000 (UTC) (envelope-from perrin@apotheon.com) Received: from oproxy9.bluehost.com (oproxy9.bluehost.com [IPv6:2605:dc00:100:2::a2]) by mx1.freebsd.org (Postfix) with SMTP id 033588FC0A for ; Fri, 23 Sep 2011 16:03:39 +0000 (UTC) Received: (qmail 17875 invoked by uid 0); 23 Sep 2011 16:03:39 -0000 Received: from unknown (HELO box543.bluehost.com) (74.220.219.143) by oproxy9.bluehost.com with SMTP; 23 Sep 2011 16:03:39 -0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=apotheon.com; s=default; h=In-Reply-To:Content-Type:Mime-Version:References:Message-ID:Subject:Cc:To:From:Date; bh=wBcKQpdDZD9UmocosS9ZUN+uqkJwlDKJLHKqhnrsMmc=; b=Q3RNPUjzCsuDiCe7GDmNrujf6fHrkqLjjiIZ+8uYAn6LZAee02X4rP51DVtNI5sJoP6NVcKf9o6dyFNa1mkp+eRtn1uEYDSVTnezujtmh4oRHMmxQ2/5xaexpyTr8ygI; Received: from c-24-8-180-234.hsd1.co.comcast.net ([24.8.180.234] helo=kukaburra.hydra) by box543.bluehost.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.76) (envelope-from ) id 1R78Dy-0008Bz-Jq; Fri, 23 Sep 2011 10:03:39 -0600 Received: by kukaburra.hydra (sSMTP sendmail emulation); Fri, 23 Sep 2011 10:03:17 -0600 Date: Fri, 23 Sep 2011 10:03:17 -0600 From: Chad Perrin To: Alexander Best Message-ID: <20110923160317.GB84518@guilt.hydra> References: <20110922220520.GA2364@freebsd.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="4SFOXa2GPu3tIq4H" Content-Disposition: inline In-Reply-To: <20110922220520.GA2364@freebsd.org> User-Agent: Mutt/1.4.2.3i X-Identified-User: {2737:box543.bluehost.com:apotheon:apotheon.org} {sentby:smtp auth 24.8.180.234 authed with ren@apotheon.org} Cc: freebsd-docs@freebsd.org Subject: Re: minor fix to smp(4) man page X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Sep 2011 16:03:40 -0000 --4SFOXa2GPu3tIq4H Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Sep 22, 2011 at 10:05:20PM +0000, Alexander Best wrote: >=20 > @@ -124,21 +124,20 @@ Since using logical CPUs can cause performance pena= lties under certain loads, > the logical CPUs can be disabled by setting the That should be "Because", not "Since". The word "Since" here is roughly synonymous with "After". --=20 Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ] --4SFOXa2GPu3tIq4H Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (FreeBSD) iEYEARECAAYFAk58rcUACgkQ9mn/Pj01uKUH8gCgw88k7FOQGonE99l7siVx1dyW 9UIAn0ZR83E3kACbzfu+VbUHk6Hyy04V =Gb29 -----END PGP SIGNATURE----- --4SFOXa2GPu3tIq4H--