From owner-svn-doc-all@FreeBSD.ORG Sun Jan 20 00:28:14 2013 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 3DED1510; Sun, 20 Jan 2013 00:28:14 +0000 (UTC) (envelope-from rene@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id 18B47799; Sun, 20 Jan 2013 00:28:14 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.5/8.14.5) with ESMTP id r0K0SDrO048078; Sun, 20 Jan 2013 00:28:13 GMT (envelope-from rene@svn.freebsd.org) Received: (from rene@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r0K0SDfb048076; Sun, 20 Jan 2013 00:28:13 GMT (envelope-from rene@svn.freebsd.org) Message-Id: <201301200028.r0K0SDfb048076@svn.freebsd.org> From: Rene Ladan Date: Sun, 20 Jan 2013 00:28:13 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40687 - in head/nl_NL.ISO8859-1/books/handbook: dtrace firewalls X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 Jan 2013 00:28:14 -0000 Author: rene Date: Sun Jan 20 00:28:13 2013 New Revision: 40687 URL: http://svnweb.freebsd.org/changeset/doc/40687 Log: MFen the Dutch Handbook: - dtrace r40601 -> r40686 (SRCID bump + igor fix) - firewalls r40647 -> r40685 (SRCID bump) Modified: head/nl_NL.ISO8859-1/books/handbook/dtrace/chapter.xml head/nl_NL.ISO8859-1/books/handbook/firewalls/chapter.xml Modified: head/nl_NL.ISO8859-1/books/handbook/dtrace/chapter.xml ============================================================================== --- head/nl_NL.ISO8859-1/books/handbook/dtrace/chapter.xml Sat Jan 19 21:28:38 2013 (r40686) +++ head/nl_NL.ISO8859-1/books/handbook/dtrace/chapter.xml Sun Jan 20 00:28:13 2013 (r40687) @@ -12,7 +12,7 @@ that might make this chapter too large. $FreeBSD$ %SOURCE% en_US.ISO8859-1/books/handbook/dtrace/chapter.xml - %SRCID% 40601 + %SRCID% 40686 --> @@ -222,7 +222,8 @@ options DDB_CTF Als laatste dient de huidige &dtrace;Toolkit verkregen te worden. Indien u &os; 10 draait, vindt u de &dtrace;Toolkit in /usr/share/dtrace. In andere gevallen kunt u de - &dtrace;Toolkit installeren via de port sysutils/DTraceToolkit. + &dtrace;Toolkit installeren via de port sysutils/DTraceToolkit. Modified: head/nl_NL.ISO8859-1/books/handbook/firewalls/chapter.xml ============================================================================== --- head/nl_NL.ISO8859-1/books/handbook/firewalls/chapter.xml Sat Jan 19 21:28:38 2013 (r40686) +++ head/nl_NL.ISO8859-1/books/handbook/firewalls/chapter.xml Sun Jan 20 00:28:13 2013 (r40687) @@ -5,7 +5,7 @@ $FreeBSD$ %SOURCE% en_US.ISO8859-1/books/handbook/firewalls/chapter.xml - %SRCID% 40647 + %SRCID% 40685 --> From owner-svn-doc-all@FreeBSD.ORG Sun Jan 20 13:31:10 2013 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 5A0BDAA1; Sun, 20 Jan 2013 13:31:10 +0000 (UTC) (envelope-from rene@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id 3279B2A7; Sun, 20 Jan 2013 13:31:10 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.5/8.14.5) with ESMTP id r0KDVAM4081661; Sun, 20 Jan 2013 13:31:10 GMT (envelope-from rene@svn.freebsd.org) Received: (from rene@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r0KDVAxN081660; Sun, 20 Jan 2013 13:31:10 GMT (envelope-from rene@svn.freebsd.org) Message-Id: <201301201331.r0KDVAxN081660@svn.freebsd.org> From: Rene Ladan Date: Sun, 20 Jan 2013 13:31:10 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40688 - head/nl_NL.ISO8859-1/books/handbook/disks X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 Jan 2013 13:31:10 -0000 Author: rene Date: Sun Jan 20 13:31:09 2013 New Revision: 40688 URL: http://svnweb.freebsd.org/changeset/doc/40688 Log: MFen r39908 -> r40676 (+ igor fixes) Modified: head/nl_NL.ISO8859-1/books/handbook/disks/chapter.xml Modified: head/nl_NL.ISO8859-1/books/handbook/disks/chapter.xml ============================================================================== --- head/nl_NL.ISO8859-1/books/handbook/disks/chapter.xml Sun Jan 20 00:28:13 2013 (r40687) +++ head/nl_NL.ISO8859-1/books/handbook/disks/chapter.xml Sun Jan 20 13:31:09 2013 (r40688) @@ -5,7 +5,7 @@ $FreeBSD$ %SOURCE% en_US.ISO8859-1/books/handbook/disks/chapter.xml - %SRCID% 39908 + %SRCID% 40676 --> @@ -1812,7 +1812,7 @@ cd0: Attempt to query device size failed Om bestanden groter dan 4,38GB in de compilatie op te nemen dient een UDF/ISO-9660 hybride bestandssysteem aangemaakt te worden door de aanvullende parameter aan - &man.mkisofs.8; en alle gerelateerde programma's (i.e. + &man.mkisofs.8; en alle gerelateerde programma's (i.e., &man.growisofs.1;) door te geven. Dit is alleen nodig als een ISO beeldbestand wordt aangemaakt, of als bestanden direct naar een schijf worden geschreven. Schijven die op deze manier zijn aangemaakt moeten @@ -2251,255 +2251,92 @@ cd0: Attempt to query device size failed bandmedia - De belangrijkste bandmedia zijn de 4mm, 8mm, QIC, - mini-cartridge en DLT. - - - 4mm (DDS: Digital Data Storage) - - - bandmedia - - DDS (4mm) banden - - - - bandmedia - - QIC banden - - - 4mm-banden vervangen steeds vaker QIC-banden als - back-upmedium voor werkstations. Deze trend werd versneld toen - Connor Archive, een toonaangevende fabrikant van QIC-stations, - overnam en daarna de productie van QIC-stations stopte. - 4mm-stations zijn klein en stil maar genieten niet de - betrouwbaarheidsreputatie van 8mm-stations. De cartridges zijn - minder duur en kleiner (3 x 2 x 0,5 inch, 76 x 51 x 12 mm) dan - 8mm-cartridges. Net zoals bij 8mm hebben de koppen bij 4mm een - vergelijkbaar kort leven, omdat beiden gebruik maken van een - helische scan. - - De gegevensdoorvoer op deze stations begint bij ongeveer - 150 kB/s, met pieken van 500 kB/s. De - opslagcapaciteit begint bij 1,3 GB en eindigt bij - 2,0 GB. Hardwarecompressie, die voor de meeste stations - beschikbaar is, zorgt voor ongeveer een verdubbeling van de - capaciteit. Bibliotheekeenheden van multi-station - bandbiliotheken kunnen 6 stations in een enkel kabinet bevatten - met automatische wisseling van de banden. De capaciteit van - een bibliotheek loopt op tot 240 GB. - - Door de DDS-3-standaard worden bandcapaciteiten van - 12 GB (of 24 GB met compressie) ondersteund. - - Net als 8mm-drives gebruiken 4mm-drives helische scan. - Alle voor- en nadelen van helische scan gelden voor zowel 4mm- - als 8mm-stations. - - Banden dienen na 2.000 maal of 100 volledige back-ups - afgedankt te worden. + Bandtechnologie is zich blijven ontwikkelen maar het is minder + waarschijnlijk dat het in moderne systemen wordt gebruikt. Moderne + back-upsystemen neigen om offsite gecombineerd met technologieën voor + plaatselijke verwisselbare schijfstations te gebruiken. &os; zal nog + steeds elk bandstation dat SCSI gebruikt zoals LTO en oudere apparaten + zoals DAT ondersteunen. Er is ook beperkte ondersteuning voor SATA- en + USB-bandstations. + + + Seriële toegang met &man.sa.4; + + bandstations + + &os; gebruikt het stuurprogramma &man.sa.4;, dat + /dev/sa0, + /dev/nsa0 en + /dev/esa0 aanbiedt. Voor normaal gebruik is + alleen /dev/sa0 nodig. + /dev/nsa0 is fysiek hetzelfde apparaat als + /dev/sa0 maar spoelt de band niet terug nadat + een bestand is geschreven. Dit maakt het mogelijk om meer dan één + bestand naar een band te schrijven. /dev/esa0 + werpt, indien van toepassing, de band uit nadat het apparaat is + gesloten. - - 8mm (Exabyte) + + Het bandstation met &man.mt.1; beheren bandmedia - Exabyte (8mm) banden + mt - 8mm-banden zijn de meest gebruikte SCSI-banden. Ze vormen - de beste keuze met betrekking tot het uitwisselen van banden. - Bijna elk bedrijf heeft een Exabyte 2 GB 8mm-bandstation. - 8mm-stations zijn betrouwbaar, gemakkelijk en stil. Cartridges - zijn niet duur en klein (4,8 x 3,3 x 0,6 inch; 122 x 84 x 15 - mm). Een nadeel van 8mm-banden is de relatief korte levensduur - van de kop en band vanwege de hoge mate van relatieve beweging - tussen de band en de koppen. - - De gegevensdoorvoer varieert van ~250 kB/s tot - ~500 kB/s. De gegevensomvang begint bij 300 MB en - kan oplopen tot 7 GB. Hardwarecompressie, waarmee de - meeste stations van deze soort zijn uitgerust, zorgt voor - ongeveer een verdubbeling van de capaciteit. Deze stations - zijn los of als multi-station bandbiliotheken met 6 stations en - 120 banden in een enkele kast beschikbaar. In het laatste - geval worden banden automatisch per stuk verwisseld. De - capaciteit van een bibliotheek kan oplopen tot meer dan - 840 GB. - - Het model Mammoth van Exabyte ondersteunt - een capaciteit van 12 GB (24 GB met compressie) - per band en kost ongeveer twee maal zoveel als een gewoon - bandstation. - - Gegevens worden door middel van helische scan op de band - gezet en de koppen zijn onder een hoek (ongeveer 6 graden) op - het medium gepositioneerd. De band wordt 270 graden om de - spoel gewikkeld die de koppen vasthoudt. Dit resulteert in een - hoge gegevensdichtheid en dicht bij elkaar staande sporen die - een hoek van de ene naar de andere kant van de band - maken. - - - - QIC + &man.mt.1; is het hulpmiddel van &os; om andere bewerkingen op het + bandstation uit te voeren, zoals bestanden op een band doorzoeken of + controlepunten naar de band schrijven. - - bandmedia - - QIC-150 - + Als voorbeeld kunnen de eerste drie bestanden op een band bewaard + worden door ze over te slaan voordat een nieuw bestand wordt + geschreven: - De banden en stations voor de QIC-150 zijn misschien de - meest voorkomende bandstations en bandmedia. QIC-bandstations - zijn de minst dure serieuze back-upstations. - Het nadeel is de prijs van de media. QIC-banden zijn duur in - vergelijking met 8mm- of 4mm-banden. De prijs per GB - opslagruimte kan tot 5 maal zo hoog zijn. Indien een half - dozijn banden toereikend is, zijn QIC-banden waarschijnlijk de - juiste keuze. QIC is het meest - voorkomende bandstation. Elk bedrijf heeft QIC-stations met - een bepaalde capaciteit. QIC heeft namelijk een groot aantal - capaciteiten per type band, die fysiek vergelijkbaar (soms - identiek) zijn. QIC-banden zijn niet stil. Deze stations - maken een hoorbaar geluid tijdens het zoeken voordat ze - beginnen met het opnemen van gegevens en zijn duidelijk - hoorbaar tijdens het lezen, schrijven en zoeken. QIC-banden - zijn 6 x 4 x 0,7 inch of 152 x 102 x 17 mm - groot. - - De gegevensdoorvoer varieert van ~150 kB/s tot - ~500 kB/s. Hardwarecompressie is mogelijk met veel van de - nieuwere bandstations. QIC-stations worden steeds minder vaak - geïnstalleerd. Ze worden vervangen door DAT-stations. - - Gegevens worden in sporen op de band gezet. De sporen - lopen parallel aan de lange as van het bandmedium van het ene - naar het andere einde. Het aantal sporen, en daarmee de - breedte van een spoor, varieert met de capaciteit van de band. - De meeste, zo niet alle, nieuwe stations bieden achterwaartse - leescompatibiliteit (en vaak ook achterwaartse - schrijfcompabiliteit). QIC heeft een goede reputatie op het - gebied van gegevensveiligheid (de mechanismen zijn eenvoudiger - en robuuster dan die van helische scan-stations). - - Banden dienen na 5.000 back-ups afgedankt te worden. + &prompt.root; mt -f /dev/nsa0 fsf 3 - - DLT + + &man.tar.1; gebruiken om back-ups op banden te + lezen en schrijven - - bandmedia + &man.tar.1; gebruiken om een enkel bestand naar band te + schrijven: - DLT - + &prompt.root; tar cvf /dev/sa0 bestand - DLT-banden hebben de snelste gegevensdoorvoer van alle - hiergenoemde bandstations. De band van 1/2 inch (12,5 mm) zit - in een cartridge (4 x 4 x 1 inch; 100 x 100 x 25 mm) op - één enkele haspel. De cartridge heeft een - opklapbare opening aan één gehele kant van de - cartridge. Het mechanisme van het station opent deze opening - om de bandleider eruit te halen. De bandleider heeft een ovaal - gat dat door het station gebruikt wordt om de band vast - te zetten. De haspel die de band aanpakt is in het - bandstation gesitueerd. Bij alle andere bandcartridges die - hier genoemd zijn (9-sporige banden zijn de enige uitzondering) - zitten zowel de haspel die de band levert als de haspel die de - band aanpakt in de bandcartridge zelf. - - De gegevensdoorvoer bedraagt ongeveer 1.5 MB/s, drie - maal de doorvoer van 4mm-, 8mm-, en QIC-bandstations. De - gegevenscapaciteit varieert van 10 GB tot 20 GB per - stations. Stations zijn als meerdere-bandwisselaars en als - bibliotheken van meerdere banden en meerdere stations - beschikbaar, die 5 tot 900 banden bevatten verspreid over 1 tot - 20 stations, waardoor een opslagcapaciteit van 50 GB tot - 9 TB geleverd wordt. - - Met compressie levert het formaat DLT Type IV tot - 70 GB aan capaciteit. - - Gegevens worden in sporen die parallel aan de looprichting - lopen op de band gezet (net als met QIC-banden). Er worden - twee sporen per keer geschreven. De levensduur van de lees- en - schrijfkoppen is relatief lang. Als de band eenmaal stilstaat, - is er geen relatieve beweging tussen de koppen en de - band. + Bestanden vanuit een &man.tar.1;-archief op band naar de huidige + map herstellen: + + &prompt.root; tar xvf /dev/sa0 - AIT + &man.dump.8; en &man.restore.8; gebruiken + om back-ups aan te maken en te herstellen - - bandmedia + Een eenvoudige back-up van /usr maken met &man.dump.8;: - AIT - + &prompt.root; dump -0aL -b64 -f /dev/nsa0 /usr + + Interactief bestanden van een &man.dump.8;-bestand vanaf band naar + de huidige map herstellen: - AIT is een nieuw formaat van Sony dat (met compressie) tot - 50 GB gegevens per band kan bevatten. De band bevat - geheugenchips die een index van de inhoud van de band bevatten. - Deze index kan snel door het bandstation gelezen worden voor - het bepalen van de positie van bestanden op de band, in plaats - van de enkele minuten die nodig zijn voor andere banden. - Software als SAMS:Alexandria kan - meer dan veertig AIT-bandbibliotheken beheren, waarbij het - direct met de geheugenchip van de band communiceert om de - inhoud op het scherm te tonen, om te bepalen welke bestanden - naar welke band zijn geback-upped en om de correcte band te - vinden, laden en de gegevens ervan terug te zetten. - - Dit soort bibliotheken kosten rond de $ 20.000, - waardoor ze enigszins boven het budget van de hobbyist - liggen. + &prompt.root; restore -i -f /dev/nsa0 - Eerste gebruik van een nieuwe band - - Als de eerste keer van een nieuwe, geheel lege band wordt - gelezen of ernaar wordt geschreven, mislukt dit. Het bericht - op de console zier er analoog aan het volgende uit: - - sa0(ncr1:4:0): NOT READY asc:4,1 -sa0(ncr1:4:0): Logical unit is in process of becoming ready - - De band bevat geen Identifier Block (bloknummer 0). Alle - QIC-bandstations sinds de adoptie van de standaard QIC-525 - schrijven een Identifier Block naar de band. Er zijn twee - oplossingen: + Andere bandsoftware - - - mt fsf 1 zorgt ervoor dat het - bandstation een Identifier Block naar de band - schrijft. - - - - De knop aan de voorkant van het paneel dient gebruikt - te worden om de band uit te werpen. - - De band dient opnieuw in het station gestoken te worden - en met dump worden gegevens naar de band - gedumpt. - - dump geeft DUMP: End of - tape detected en de console laat het volgende - zien:HARDWARE FAILURE info:280 - asc:80,96. - - De band kan met mt rewind - teruggespoeld te worden. - - Hierna zijn alle bandbewerkingen succesvol. - - + Er zijn programma's op hoger niveau beschikbaar om het back-uppen + naar banden eenvoudiger te maken. De populairste zijn + AMANDA en Bacula. + Deze programma's hebben als doel om back-uppen eenvoudiger en + aangenamer te maken, of om complexe back-ups van meerdere machines te + automatiseren. De Portscollectie bevat deze beide en andere + toepassingen om met banden te werken. From owner-svn-doc-all@FreeBSD.ORG Sun Jan 20 15:13:12 2013 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id AD1977DD; Sun, 20 Jan 2013 15:13:12 +0000 (UTC) (envelope-from lme@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id 9506881E; Sun, 20 Jan 2013 15:13:12 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.5/8.14.5) with ESMTP id r0KFDCpE012452; Sun, 20 Jan 2013 15:13:12 GMT (envelope-from lme@svn.freebsd.org) Received: (from lme@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r0KFDCrr012451; Sun, 20 Jan 2013 15:13:12 GMT (envelope-from lme@svn.freebsd.org) Message-Id: <201301201513.r0KFDCrr012451@svn.freebsd.org> From: Lars Engels Date: Sun, 20 Jan 2013 15:13:12 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40689 - head/en_US.ISO8859-1/articles/contributors X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 Jan 2013 15:13:12 -0000 Author: lme (ports committer) Date: Sun Jan 20 15:13:12 2013 New Revision: 40689 URL: http://svnweb.freebsd.org/changeset/doc/40689 Log: Add Yamagi Burmeister Modified: head/en_US.ISO8859-1/articles/contributors/contrib.additional.xml (contents, props changed) Modified: head/en_US.ISO8859-1/articles/contributors/contrib.additional.xml ============================================================================== --- head/en_US.ISO8859-1/articles/contributors/contrib.additional.xml Sun Jan 20 13:31:09 2013 (r40688) +++ head/en_US.ISO8859-1/articles/contributors/contrib.additional.xml Sun Jan 20 15:13:12 2013 (r40689) @@ -10823,6 +10823,11 @@ + Yamagi Burmeister + yamagi@yamagi.org + + + Yanhui Shen shen.elf@gmail.com From owner-svn-doc-all@FreeBSD.ORG Sun Jan 20 16:56:49 2013 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 96FD02BD; Sun, 20 Jan 2013 16:56:49 +0000 (UTC) (envelope-from rene@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id 6AC0EB41; Sun, 20 Jan 2013 16:56:49 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.5/8.14.5) with ESMTP id r0KGunRW043087; Sun, 20 Jan 2013 16:56:49 GMT (envelope-from rene@svn.freebsd.org) Received: (from rene@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r0KGund5043084; Sun, 20 Jan 2013 16:56:49 GMT (envelope-from rene@svn.freebsd.org) Message-Id: <201301201656.r0KGund5043084@svn.freebsd.org> From: Rene Ladan Date: Sun, 20 Jan 2013 16:56:49 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40690 - in head/en_US.ISO8859-1: books/handbook/eresources share/xml X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 Jan 2013 16:56:49 -0000 Author: rene Date: Sun Jan 20 16:56:48 2013 New Revision: 40690 URL: http://svnweb.freebsd.org/changeset/doc/40690 Log: Add the freebsd-ops-announce@ mailing list. PR: docs/175301 Submitted by: dhw Approved by: gjb (mentor) Modified: head/en_US.ISO8859-1/books/handbook/eresources/chapter.xml head/en_US.ISO8859-1/share/xml/mailing-lists.ent Modified: head/en_US.ISO8859-1/books/handbook/eresources/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/handbook/eresources/chapter.xml Sun Jan 20 15:13:12 2013 (r40689) +++ head/en_US.ISO8859-1/books/handbook/eresources/chapter.xml Sun Jan 20 16:56:48 2013 (r40690) @@ -1508,6 +1508,22 @@ + &a.ops-announce.name; + + + Project Infrastructure + Announcements + + This is the mailing list for people interested in + changes and issues related to the FreeBSD.org project + infrastructure. + + This list is strictly for announcements: no replies, + requests, discussions, or opinions. + + + + &a.performance.name; Modified: head/en_US.ISO8859-1/share/xml/mailing-lists.ent ============================================================================== --- head/en_US.ISO8859-1/share/xml/mailing-lists.ent Sun Jan 20 15:13:12 2013 (r40689) +++ head/en_US.ISO8859-1/share/xml/mailing-lists.ent Sun Jan 20 16:56:48 2013 (r40690) @@ -315,6 +315,10 @@ Office applications on FreeBSD"> freebsd-office"> + +Project Infrastructure Announcements"> +freebsd-ops-announce"> + FreeBSD performance mailing list"> freebsd-performance"> From owner-svn-doc-all@FreeBSD.ORG Sun Jan 20 17:07:20 2013 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 966BC681; Sun, 20 Jan 2013 17:07:20 +0000 (UTC) (envelope-from rene@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id 6B8AEC0F; Sun, 20 Jan 2013 17:07:20 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.5/8.14.5) with ESMTP id r0KH7Kkk046449; Sun, 20 Jan 2013 17:07:20 GMT (envelope-from rene@svn.freebsd.org) Received: (from rene@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r0KH7K0l046446; Sun, 20 Jan 2013 17:07:20 GMT (envelope-from rene@svn.freebsd.org) Message-Id: <201301201707.r0KH7K0l046446@svn.freebsd.org> From: Rene Ladan Date: Sun, 20 Jan 2013 17:07:20 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40691 - in head/nl_NL.ISO8859-1: books/handbook/eresources share/xml X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 Jan 2013 17:07:20 -0000 Author: rene Date: Sun Jan 20 17:07:19 2013 New Revision: 40691 URL: http://svnweb.freebsd.org/changeset/doc/40691 Log: MFen the freebsd-ops-announce mailing list. Modified: head/nl_NL.ISO8859-1/books/handbook/eresources/chapter.xml head/nl_NL.ISO8859-1/share/xml/mailing-lists.ent Modified: head/nl_NL.ISO8859-1/books/handbook/eresources/chapter.xml ============================================================================== --- head/nl_NL.ISO8859-1/books/handbook/eresources/chapter.xml Sun Jan 20 16:56:48 2013 (r40690) +++ head/nl_NL.ISO8859-1/books/handbook/eresources/chapter.xml Sun Jan 20 17:07:19 2013 (r40691) @@ -6,7 +6,7 @@ Vertaald door: Siebrand Mazeland / Rene Ladan %SOURCE% en_US.ISO8859-1/books/handbook/eresources/chapter.xml - %SRCID% 40672 + %SRCID% 40690 --> @@ -1661,6 +1661,22 @@ + &a.ops-announce.name; + + + Aankondigingen over de + projectinfrastructuur + + Deze mailinglijst is bedoeld voor mensen die geïnteresseerd + zijn in veranderingen en zaken die te maken hebben met de + infrastructuur van het FreeBSD.org project. + + Deze lijst is strict voor aankondigingen: geen antwoorden, + verzoeken, discussies of meningen. + + + + &a.performance.name; Modified: head/nl_NL.ISO8859-1/share/xml/mailing-lists.ent ============================================================================== --- head/nl_NL.ISO8859-1/share/xml/mailing-lists.ent Sun Jan 20 16:56:48 2013 (r40690) +++ head/nl_NL.ISO8859-1/share/xml/mailing-lists.ent Sun Jan 20 17:07:19 2013 (r40691) @@ -5,7 +5,7 @@ Vertaald door: Siebrand Mazeland / Rene Ladan %SOURCE% en_US.ISO8859-1/share/xml/mailing-lists.ent - %SRCID% 40628 + %SRCID% 40690 --> @@ -319,6 +319,10 @@ Kantoortoepassingen op &os;"> freebsd-office"> + +Aankondigingen over de projectinfrastructuur"> +freebsd-ops-announce"> + &os; prestaties mailinglijst"> freebsd-performance"> From owner-svn-doc-all@FreeBSD.ORG Mon Jan 21 12:11:34 2013 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 8A9E094D; Mon, 21 Jan 2013 12:11:34 +0000 (UTC) (envelope-from rene@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id 7D543D21; Mon, 21 Jan 2013 12:11:34 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.5/8.14.5) with ESMTP id r0LCBYi3094745; Mon, 21 Jan 2013 12:11:34 GMT (envelope-from rene@svn.freebsd.org) Received: (from rene@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r0LCBYGv094744; Mon, 21 Jan 2013 12:11:34 GMT (envelope-from rene@svn.freebsd.org) Message-Id: <201301211211.r0LCBYGv094744@svn.freebsd.org> From: Rene Ladan Date: Mon, 21 Jan 2013 12:11:34 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40692 - head/share/xml X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Jan 2013 12:11:34 -0000 Author: rene Date: Mon Jan 21 12:11:33 2013 New Revision: 40692 URL: http://svnweb.freebsd.org/changeset/doc/40692 Log: Add CARI.net to the commercial gallery. PR: www/171578 Submitted by: Mike Dowdy Approved by: gjb (mentor) Modified: head/share/xml/commercial.isp.xml Modified: head/share/xml/commercial.isp.xml ============================================================================== --- head/share/xml/commercial.isp.xml Sun Jan 20 17:07:19 2013 (r40691) +++ head/share/xml/commercial.isp.xml Mon Jan 21 12:11:33 2013 (r40692) @@ -31,6 +31,16 @@ + + CARI.net + http://www.cari.net/ + + CARI.net provides FreeBSD as a hosting platform for clusters, + clouds, and stand-alone dedicated servers. We have been + supporting the Open Source community for over seventeen years. + + + IFDNRG http://www.ifdnrg.com/ From owner-svn-doc-all@FreeBSD.ORG Mon Jan 21 23:27:12 2013 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id C6E0D848; Mon, 21 Jan 2013 23:27:12 +0000 (UTC) (envelope-from wblock@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id A298A31D; Mon, 21 Jan 2013 23:27:12 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.5/8.14.5) with ESMTP id r0LNRCgJ002422; Mon, 21 Jan 2013 23:27:12 GMT (envelope-from wblock@svn.freebsd.org) Received: (from wblock@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r0LNRCgb002421; Mon, 21 Jan 2013 23:27:12 GMT (envelope-from wblock@svn.freebsd.org) Message-Id: <201301212327.r0LNRCgb002421@svn.freebsd.org> From: Warren Block Date: Mon, 21 Jan 2013 23:27:12 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40712 - head/en_US.ISO8859-1/books/handbook/cutting-edge X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Jan 2013 23:27:12 -0000 Author: wblock Date: Mon Jan 21 23:27:12 2013 New Revision: 40712 URL: http://svnweb.freebsd.org/changeset/doc/40712 Log: Update the freebsd-update section: Define minor and major version upgrades at the start of the section. Mention that installed applications will still run after a minor upgrade. Split the custom kernel portion into 8.X and earlier and 9.X and later. Make the portupgrade instructions specific to major version upgrades. PR: www/175069 Submitted by: George Kontostanos Reviewed by: freebsd-doc mailing list Modified: head/en_US.ISO8859-1/books/handbook/cutting-edge/chapter.xml Modified: head/en_US.ISO8859-1/books/handbook/cutting-edge/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/handbook/cutting-edge/chapter.xml Mon Jan 21 17:45:18 2013 (r40711) +++ head/en_US.ISO8859-1/books/handbook/cutting-edge/chapter.xml Mon Jan 21 23:27:12 2013 (r40712) @@ -352,15 +352,23 @@ MergeChanges /etc/ /var/named/etc/ - Major and Minor Upgrades + Major and Minor Version Upgrades - This process will remove old object files and + Upgrades from one minor version of &os; to another, like + from &os; 9.0 to &os; 9.1, are called + minor version upgrades. Generally, + installed applications will continue to work without problems + after minor version upgrades. + + Major version upgrades are when &os; + is upgraded from one major version to another, like from + &os; 8.X to &os; 9.X. Major version upgrades will remove old object files and libraries which will break most third party applications. It is recommended that all installed ports either be removed - and re-installed or upgraded later using the + and re-installed or upgraded after a major version upgrade by using the ports-mgmt/portupgrade - utility. Most users will want to run a test build using - the following command: + utility. A brute-force rebuild of all installed + applications can be accomplished with this command: &prompt.root; portupgrade -af @@ -371,81 +379,142 @@ MergeChanges /etc/ /var/named/etc/ - If a custom kernel is in use, the upgrade process is - slightly more involved. A copy of the - GENERIC kernel is needed, and it should - be placed in - /boot/GENERIC. If the - GENERIC kernel is not already present in - the system, it may be obtained using one of the following - methods: + + Dealing with Custom Kernels - - - If a custom kernel has only been built once, the - kernel in - /boot/kernel.old is - actually the GENERIC one. Simply - rename this directory to /boot/GENERIC. - - - - Assuming physical access to the machine is possible, a - copy of the GENERIC kernel can be - installed from the CD-ROM media. Insert your installation - disc and use the following commands: + If a custom kernel is in use, the upgrade process is + slightly more involved, and the procedure varies depending on + the version of &os;. + + + Custom Kernels with &os; 8.X and Earlier + + A copy of the + GENERIC kernel is needed, and it should + be placed in + /boot/GENERIC. If the + GENERIC kernel is not already present in + the system, it may be obtained using one of the following + methods: + + + + If a custom kernel has only been built once, the + kernel in + /boot/kernel.old is + actually the GENERIC one. Simply + rename this directory to /boot/GENERIC. + + + + Assuming physical access to the machine is possible, a + copy of the GENERIC kernel can be + installed from the CD-ROM media. Insert your installation + disc and use the following commands: - &prompt.root; mount /cdrom + &prompt.root; mount /cdrom &prompt.root; cd /cdrom/X.Y-RELEASE/kernels &prompt.root; ./install.sh GENERIC - Replace X.Y-RELEASE - with the actual version of the release you are using. The - GENERIC kernel will be installed in - /boot/GENERIC by - default. - - - - Failing all the above, the - GENERIC kernel may be rebuilt and - installed from the sources: + Replace X.Y-RELEASE + with the actual version of the release you are using. The + GENERIC kernel will be installed in + /boot/GENERIC by + default. + + + + Failing all the above, the + GENERIC kernel may be rebuilt and + installed from the sources: - &prompt.root; cd /usr/src + &prompt.root; cd /usr/src &prompt.root; env DESTDIR=/boot/GENERIC make kernel &prompt.root; mv /boot/GENERIC/boot/kernel/* /boot/GENERIC &prompt.root; rm -rf /boot/GENERIC/boot - For this kernel to be picked up as - GENERIC - by freebsd-update, the - GENERIC configuration file must not - have been modified in any way. It is also suggested that - it is built without any other special options (preferably - with an empty /etc/make.conf). - - + For this kernel to be picked up as + GENERIC + by freebsd-update, the + GENERIC configuration file must not + have been modified in any way. It is also suggested that + it is built without any other special options (preferably + with an empty /etc/make.conf). + + + + Rebooting to the GENERIC kernel is + not required at this stage. + - Rebooting to the GENERIC kernel is - not required at this stage. + + Custom Kernels with &os; 9.X and Later - Major and minor version updates may be performed by - providing freebsd-update with a release - version target, for example, the following command will - update to &os; 8.1: - - &prompt.root; freebsd-update -r 8.1-RELEASE upgrade - - After the command has been received, - freebsd-update will evaluate the - configuration file and current system in an attempt to gather - the information necessary to update the system. A screen - listing will display what components have been detected and - what components have not been detected. For example: + + + If a custom kernel has only been built once, the + kernel in + /boot/kernel.old + is actually the GENERIC kernel. + Rename this directory to /boot/kernel. + + + + If physical access to the machine is available, a + copy of the GENERIC kernel can be + installed from the CD-ROM media. Load the + installation disc and use these commands: + + &prompt.root; mount /cdrom +&prompt.root; cd /cdrom/usr/freebsd-dist +&prompt.root; tar -C/ -xvf kernel.txz boot/kernel/kernel + + + + If the options above cannot be used, the + GENERIC kernel may be rebuilt and + installed from the sources: + + &prompt.root; cd /usr/src +&prompt.root; make kernel + + For this kernel to be identified as the + GENERIC kernel by + freebsd-update, the + GENERIC configuration file must + not have been modified in any way. It is also + suggested that the kernel is built without any other + special options, preferably with an empty + /etc/make.conf. + + - Looking up update.FreeBSD.org mirrors... 1 mirrors found. + Rebooting to the GENERIC kernel is + not required at this stage. + + + + + Performing the Upgrade + + Major and minor version upgrades may be performed by + providing freebsd-update with a release + version target, for example, the following command will + update to &os; 8.1: + + &prompt.root; freebsd-update -r 8.1-RELEASE upgrade + + After the command has been received, + freebsd-update will evaluate the + configuration file and current system in an attempt to gather + the information necessary to update the system. A screen + listing will display what components have been detected and + what components have not been detected. For example: + + Looking up update.FreeBSD.org mirrors... 1 mirrors found. Fetching metadata signature for 8.0-RELEASE from update1.FreeBSD.org... done. Fetching metadata index... done. Inspecting system... done. @@ -462,123 +531,128 @@ world/proflibs Does this look reasonable (y/n)? y - At this point, freebsd-update will - attempt to download all files required for the upgrade. In - some cases, the user may be prompted with questions regarding - what to install or how to proceed. + At this point, freebsd-update will + attempt to download all files required for the upgrade. In + some cases, the user may be prompted with questions regarding + what to install or how to proceed. - When using a custom kernel, the above step will produce a - warning similar to the following: + When using a custom kernel, the above step will produce a + warning similar to the following: - WARNING: This system is running a "MYKERNEL" kernel, which is not a + WARNING: This system is running a "MYKERNEL" kernel, which is not a kernel configuration distributed as part of FreeBSD 8.0-RELEASE. This kernel will not be updated: you MUST update the kernel manually before running "/usr/sbin/freebsd-update install" - This warning may be safely ignored at this point. The - updated GENERIC kernel will be used as an - intermediate step in the upgrade process. - - After all patches have been downloaded to the local - system, they will then be applied. This process may take a - while depending on the speed and workload of the machine. - Configuration files will then be merged — this part - of the process requires some user intervention as a file may - be merged or an editor may appear on screen for a manual - merge. The results of every successful merge will be shown to - the user as the process continues. A failed or ignored merge - will cause the process to abort. Users may wish to make a - backup of /etc and - manually merge important files, such as - master.passwd or - group at a later time. + This warning may be safely ignored at this point. The + updated GENERIC kernel will be used as an + intermediate step in the upgrade process. + + After all patches have been downloaded to the local + system, they will then be applied. This process may take a + while depending on the speed and workload of the machine. + Configuration files will then be merged — this part + of the process requires some user intervention as a file may + be merged or an editor may appear on screen for a manual + merge. The results of every successful merge will be shown to + the user as the process continues. A failed or ignored merge + will cause the process to abort. Users may wish to make a + backup of /etc and + manually merge important files, such as + master.passwd or + group at a later time. - - The system is not being altered yet, all patching and - merging is happening in another directory. When all - patches have been applied successfully, all configuration - files have been merged and it seems the process will go - smoothly, the changes will need to be committed by the - user. - + + The system is not being altered yet, all patching and + merging is happening in another directory. When all + patches have been applied successfully, all configuration + files have been merged and it seems the process will go + smoothly, the changes will need to be committed by the + user. + - Once this process is complete, the upgrade may be - committed to disk using the following command. + Once this process is complete, the upgrade may be + committed to disk using the following command. - &prompt.root; freebsd-update install + &prompt.root; freebsd-update install - The kernel and kernel modules will be patched first. At - this point the machine must be rebooted. If the system was - running with a custom kernel, use the &man.nextboot.8; command - to set the kernel for the next boot to - /boot/GENERIC (which - was updated): + The kernel and kernel modules will be patched first. At + this point the machine must be rebooted. If the system was + running with a custom kernel, use the &man.nextboot.8; command + to set the kernel for the next boot to + /boot/GENERIC (which + was updated): - &prompt.root; nextboot -k GENERIC + &prompt.root; nextboot -k GENERIC - - Before rebooting with the GENERIC - kernel, make sure it contains all drivers required for your - system to boot properly (and connect to the network, if the - machine that is being updated is accessed remotely). In - particular, if the previously running custom kernel - contained built-in functionality usually provided by kernel - modules, make sure to temporarily load these modules into - the GENERIC kernel using the - /boot/loader.conf facility. You may - also wish to disable non-essential services, disk and - network mounts, etc. until the upgrade process is - complete. - + + Before rebooting with the GENERIC + kernel, make sure it contains all drivers required for your + system to boot properly (and connect to the network, if the + machine that is being updated is accessed remotely). In + particular, if the previously running custom kernel + contained built-in functionality usually provided by kernel + modules, make sure to temporarily load these modules into + the GENERIC kernel using the + /boot/loader.conf facility. You may + also wish to disable non-essential services, disk and + network mounts, etc. until the upgrade process is + complete. + - The machine should now be restarted with the updated - kernel: + The machine should now be restarted with the updated + kernel: - &prompt.root; shutdown -r now + &prompt.root; shutdown -r now - Once the system has come back online, - freebsd-update will need to be started - again. The state of the process has been saved and thus, - freebsd-update will not start from the - beginning, but will remove all old shared libraries and object - files. To continue to this stage, issue the following - command: + Once the system has come back online, + freebsd-update will need to be started + again. The state of the process has been saved and thus, + freebsd-update will not start from the + beginning, but will remove all old shared libraries and object + files. To continue to this stage, issue the following + command: - &prompt.root; freebsd-update install + &prompt.root; freebsd-update install - - Depending on whether any libraries version numbers got - bumped, there may only be two install phases instead of - three. - + + Depending on whether any libraries version numbers got + bumped, there may only be two install phases instead of + three. + + - All third party software will now need to be rebuilt and - re-installed. This is required as installed software may - depend on libraries which have been removed during the upgrade - process. The - ports-mgmt/portupgrade - command may be used to automate this process. The following - commands may be used to begin this process: + + Rebuilding Ports After a Major Version Upgrade + + After a major version upgrade, all third party software will now need to be rebuilt and + re-installed. This is required as installed software may + depend on libraries which have been removed during the upgrade + process. The + ports-mgmt/portupgrade + command may be used to automate this process. The following + commands may be used to begin this process: - &prompt.root; portupgrade -f ruby + &prompt.root; portupgrade -f ruby &prompt.root; rm /var/db/pkg/pkgdb.db &prompt.root; portupgrade -f ruby18-bdb &prompt.root; rm /var/db/pkg/pkgdb.db /usr/ports/INDEX-*.db &prompt.root; portupgrade -af - Once this has completed, finish the upgrade process with a - final call to freebsd-update. Issue the - following command to tie up all loose ends in the upgrade - process: - - &prompt.root; freebsd-update install - - If the GENERIC kernel was temporarily - used, this is the time to build and install a new custom - kernel in the usual way. + Once this has completed, finish the upgrade process with a + final call to freebsd-update. Issue the + following command to tie up all loose ends in the upgrade + process: + + &prompt.root; freebsd-update install + + If the GENERIC kernel was temporarily + used, this is the time to build and install a new custom + kernel in the usual way. - Reboot the machine into the new &os; version. The process - is complete. + Reboot the machine into the new &os; version. The process + is complete. + From owner-svn-doc-all@FreeBSD.ORG Tue Jan 22 01:34:35 2013 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 11838337; Tue, 22 Jan 2013 01:34:35 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id F188CB60; Tue, 22 Jan 2013 01:34:34 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.5/8.14.5) with ESMTP id r0M1YY9P041251; Tue, 22 Jan 2013 01:34:34 GMT (envelope-from gjb@svn.freebsd.org) Received: (from gjb@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r0M1YYwP041250; Tue, 22 Jan 2013 01:34:34 GMT (envelope-from gjb@svn.freebsd.org) Message-Id: <201301220134.r0M1YYwP041250@svn.freebsd.org> From: Glen Barber Date: Tue, 22 Jan 2013 01:34:34 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40713 - head/en_US.ISO8859-1/htdocs/doc X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Jan 2013 01:34:35 -0000 Author: gjb Date: Tue Jan 22 01:34:34 2013 New Revision: 40713 URL: http://svnweb.freebsd.org/changeset/doc/40713 Log: Remove a bogus comment about a separate www/ tree. Modified: head/en_US.ISO8859-1/htdocs/doc/Makefile Modified: head/en_US.ISO8859-1/htdocs/doc/Makefile ============================================================================== --- head/en_US.ISO8859-1/htdocs/doc/Makefile Mon Jan 21 23:27:12 2013 (r40712) +++ head/en_US.ISO8859-1/htdocs/doc/Makefile Tue Jan 22 01:34:34 2013 (r40713) @@ -1,13 +1,9 @@ # # $FreeBSD$ # -# Build the FreeBSD documentation *outside* of the www tree, and install it +# Build the FreeBSD documentation *outside* of the doc/ tree, and install it # in to the right place as necessary. # -# This assumes that you have the www/ and doc/ trees checked out beside -# one another -- this was always the case anyway, so there are no extra -# requirements here. -# .if exists(../Makefile.conf) .include "../Makefile.conf" From owner-svn-doc-all@FreeBSD.ORG Tue Jan 22 01:44:50 2013 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 1D3F34A8; Tue, 22 Jan 2013 01:44:50 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id E5689C10; Tue, 22 Jan 2013 01:44:49 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.5/8.14.5) with ESMTP id r0M1inRL044157; Tue, 22 Jan 2013 01:44:49 GMT (envelope-from gjb@svn.freebsd.org) Received: (from gjb@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r0M1inMt044154; Tue, 22 Jan 2013 01:44:49 GMT (envelope-from gjb@svn.freebsd.org) Message-Id: <201301220144.r0M1inMt044154@svn.freebsd.org> From: Glen Barber Date: Tue, 22 Jan 2013 01:44:49 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40714 - in head/en_US.ISO8859-1: articles/committers-guide htdocs/internal htdocs/security X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Jan 2013 01:44:50 -0000 Author: gjb Date: Tue Jan 22 01:44:48 2013 New Revision: 40714 URL: http://svnweb.freebsd.org/changeset/doc/40714 Log: Remove 'www/' tree references. Bump copyright date where needed. Modified: head/en_US.ISO8859-1/articles/committers-guide/article.xml head/en_US.ISO8859-1/htdocs/internal/doceng.xml head/en_US.ISO8859-1/htdocs/security/security.xml Modified: head/en_US.ISO8859-1/articles/committers-guide/article.xml ============================================================================== --- head/en_US.ISO8859-1/articles/committers-guide/article.xml Tue Jan 22 01:34:34 2013 (r40713) +++ head/en_US.ISO8859-1/articles/committers-guide/article.xml Tue Jan 22 01:44:48 2013 (r40714) @@ -26,6 +26,7 @@ 2010 2011 2012 + 2013 The FreeBSD Documentation Project @@ -212,7 +213,7 @@ doc doceng@ - doc/, www/, src/ documentation + doc/, src/ documentation Modified: head/en_US.ISO8859-1/htdocs/internal/doceng.xml ============================================================================== --- head/en_US.ISO8859-1/htdocs/internal/doceng.xml Tue Jan 22 01:34:34 2013 (r40713) +++ head/en_US.ISO8859-1/htdocs/internal/doceng.xml Tue Jan 22 01:44:48 2013 (r40714) @@ -46,7 +46,7 @@ with existing MAINTAINERs, to ensure that the documentation toolchains (DocBook, groff, etc.) are in good working order. -
  • To maintain the sanctity of the FreeBSD doc/ and www/ trees. +
  • To maintain the sanctity of the FreeBSD doc/ tree. Due to the visibility of these files and documents to the outside world, doceng@ reserves the right to immediately backout (or fix without waiting for response from the original Modified: head/en_US.ISO8859-1/htdocs/security/security.xml ============================================================================== --- head/en_US.ISO8859-1/htdocs/security/security.xml Tue Jan 22 01:34:34 2013 (r40713) +++ head/en_US.ISO8859-1/htdocs/security/security.xml Tue Jan 22 01:44:48 2013 (r40714) @@ -238,7 +238,7 @@ date listed.

    From owner-svn-doc-all@FreeBSD.ORG Tue Jan 22 01:45:25 2013 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 89F84504; Tue, 22 Jan 2013 01:45:25 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id 64DF2C14; Tue, 22 Jan 2013 01:45:25 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.5/8.14.5) with ESMTP id r0M1jPfZ044291; Tue, 22 Jan 2013 01:45:25 GMT (envelope-from gjb@svn.freebsd.org) Received: (from gjb@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r0M1jPO7044290; Tue, 22 Jan 2013 01:45:25 GMT (envelope-from gjb@svn.freebsd.org) Message-Id: <201301220145.r0M1jPO7044290@svn.freebsd.org> From: Glen Barber Date: Tue, 22 Jan 2013 01:45:25 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40715 - head/en_US.ISO8859-1/htdocs/security X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Jan 2013 01:45:25 -0000 Author: gjb Date: Tue Jan 22 01:45:24 2013 New Revision: 40715 URL: http://svnweb.freebsd.org/changeset/doc/40715 Log: Wrap long line after previous commit. Translators, please ignore. Modified: head/en_US.ISO8859-1/htdocs/security/security.xml Modified: head/en_US.ISO8859-1/htdocs/security/security.xml ============================================================================== --- head/en_US.ISO8859-1/htdocs/security/security.xml Tue Jan 22 01:44:48 2013 (r40714) +++ head/en_US.ISO8859-1/htdocs/security/security.xml Tue Jan 22 01:45:24 2013 (r40715) @@ -238,8 +238,8 @@ date listed.

    From owner-svn-doc-all@FreeBSD.ORG Tue Jan 22 02:39:56 2013 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 5A3B7E30; Tue, 22 Jan 2013 02:39:56 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id 4ADF5DD5; Tue, 22 Jan 2013 02:39:56 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.5/8.14.5) with ESMTP id r0M2dubY060535; Tue, 22 Jan 2013 02:39:56 GMT (envelope-from gjb@svn.freebsd.org) Received: (from gjb@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r0M2dtix060531; Tue, 22 Jan 2013 02:39:55 GMT (envelope-from gjb@svn.freebsd.org) Message-Id: <201301220239.r0M2dtix060531@svn.freebsd.org> From: Glen Barber Date: Tue, 22 Jan 2013 02:39:55 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-svnadmin@freebsd.org Subject: svn commit: r40716 - svnadmin/conf X-SVN-Group: doc-svnadmin MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Jan 2013 02:39:56 -0000 Author: gjb Date: Tue Jan 22 02:39:55 2013 New Revision: 40716 URL: http://svnweb.freebsd.org/changeset/doc/40716 Log: Please welcome Dru Lavigne (dru@) to the ranks of doc/ committers. bcr will be dru's mentor, with hrs as co-mentor and gjb as tertiary mentor. Approved by: doceng (implicit) Modified: svnadmin/conf/access svnadmin/conf/mentors Modified: svnadmin/conf/access ============================================================================== --- svnadmin/conf/access Tue Jan 22 01:45:24 2013 (r40715) +++ svnadmin/conf/access Tue Jan 22 02:39:55 2013 (r40716) @@ -28,6 +28,7 @@ chinsan danger delphij des +dru eadler ebrandi gabor Modified: svnadmin/conf/mentors ============================================================================== --- svnadmin/conf/mentors Tue Jan 22 01:45:24 2013 (r40715) +++ svnadmin/conf/mentors Tue Jan 22 02:39:55 2013 (r40716) @@ -12,6 +12,7 @@ # Mentee Mentor Optional comment bjk hrs des gjb backup mentor: gabor +dru bcr co-mentor: hrs, backup mentor: gjb eadler bcr backup mentor: jkois ebrandi gabor gavin bcr co-mentor: jkois, since 2011-07-18 From owner-svn-doc-all@FreeBSD.ORG Tue Jan 22 03:20:20 2013 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 3E354A5B; Tue, 22 Jan 2013 03:20:20 +0000 (UTC) (envelope-from eadler@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id 25008FB0; Tue, 22 Jan 2013 03:20:20 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.5/8.14.5) with ESMTP id r0M3KK2Y075083; Tue, 22 Jan 2013 03:20:20 GMT (envelope-from eadler@svn.freebsd.org) Received: (from eadler@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r0M3KKf6075082; Tue, 22 Jan 2013 03:20:20 GMT (envelope-from eadler@svn.freebsd.org) Message-Id: <201301220320.r0M3KKf6075082@svn.freebsd.org> From: Eitan Adler Date: Tue, 22 Jan 2013 03:20:19 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40717 - head/en_US.ISO8859-1/books/faq X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Jan 2013 03:20:20 -0000 Author: eadler Date: Tue Jan 22 03:20:19 2013 New Revision: 40717 URL: http://svnweb.freebsd.org/changeset/doc/40717 Log: Remove ed1-timeout as it is ancient and old. Noted by: imp Approved by: bcr (mentor, implicit) Modified: head/en_US.ISO8859-1/books/faq/book.xml Modified: head/en_US.ISO8859-1/books/faq/book.xml ============================================================================== --- head/en_US.ISO8859-1/books/faq/book.xml Tue Jan 22 02:39:55 2013 (r40716) +++ head/en_US.ISO8859-1/books/faq/book.xml Tue Jan 22 03:20:19 2013 (r40717) @@ -2254,30 +2254,6 @@ bindkey ^[[3~ delete-char # for xterm

    - - I keep seeing messages like ed1: - timeout. What do these messages mean? - - - - This is usually caused by an interrupt conflict (e.g., - two boards using the same IRQ). Boot with - and change the - ed0/de0/... - entry to match your board. - - If you are using the BNC connector on your network card, - you may also see device timeouts because of bad termination. - To check this, attach a terminator directly to the NIC (with - no cable) and see if the error messages go away. - - Some NE2000 compatible cards will give this error if - there is no link on the UTP port or if the cable is - disconnected. - - - - Why do my programs occasionally die with Signal 11 errors? From owner-svn-doc-all@FreeBSD.ORG Tue Jan 22 03:20:36 2013 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id CADC4AB8; Tue, 22 Jan 2013 03:20:36 +0000 (UTC) (envelope-from eadler@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id BD2F8FB2; Tue, 22 Jan 2013 03:20:36 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.5/8.14.5) with ESMTP id r0M3Kakf075289; Tue, 22 Jan 2013 03:20:36 GMT (envelope-from eadler@svn.freebsd.org) Received: (from eadler@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r0M3Kagv075288; Tue, 22 Jan 2013 03:20:36 GMT (envelope-from eadler@svn.freebsd.org) Message-Id: <201301220320.r0M3Kagv075288@svn.freebsd.org> From: Eitan Adler Date: Tue, 22 Jan 2013 03:20:36 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40718 - head/en_US.ISO8859-1/books/faq X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Jan 2013 03:20:36 -0000 Author: eadler Date: Tue Jan 22 03:20:36 2013 New Revision: 40718 URL: http://svnweb.freebsd.org/changeset/doc/40718 Log: ahc hardware is too old to be interesting. Noted by: imp Approved by: bcr (mentor, implicit) Modified: head/en_US.ISO8859-1/books/faq/book.xml Modified: head/en_US.ISO8859-1/books/faq/book.xml ============================================================================== --- head/en_US.ISO8859-1/books/faq/book.xml Tue Jan 22 03:20:19 2013 (r40717) +++ head/en_US.ISO8859-1/books/faq/book.xml Tue Jan 22 03:20:36 2013 (r40718) @@ -2489,29 +2489,6 @@ bindkey ^[[3~ delete-char # for xterm

    - - When I boot my system, I get the error ahc0: - illegal cable configuration. My cabling is - correct. What is going on? - - - - Your motherboard lacks the external logic to support - automatic termination. Switch your SCSI BIOS to specify the - correct termination for your configuration rather than - automatic termination. The &man.ahc.4; driver cannot - determine if the external logic for cable detection (and - thus auto-termination) is available. The driver simply - assumes that this support must exist if the configuration - contained in the serial EEPROM is set to automatic - termination. Without the external cable detection - logic the driver will often configure termination - incorrectly, which can compromise the reliability of the - SCSI bus. - - - - Why does sendmail give me an error reading mail loops back to From owner-svn-doc-all@FreeBSD.ORG Tue Jan 22 08:08:53 2013 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 76405CE7; Tue, 22 Jan 2013 08:08:53 +0000 (UTC) (envelope-from koobs@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id 50998BE6; Tue, 22 Jan 2013 08:08:53 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.5/8.14.5) with ESMTP id r0M88rfw069640; Tue, 22 Jan 2013 08:08:53 GMT (envelope-from koobs@svn.freebsd.org) Received: (from koobs@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r0M88qha069634; Tue, 22 Jan 2013 08:08:52 GMT (envelope-from koobs@svn.freebsd.org) Message-Id: <201301220808.r0M88qha069634@svn.freebsd.org> From: Kubilay Kocak Date: Tue, 22 Jan 2013 08:08:52 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40719 - in head: en_US.ISO8859-1/articles/contributors share/xml X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Jan 2013 08:08:53 -0000 Author: koobs (ports committer) Date: Tue Jan 22 08:08:51 2013 New Revision: 40719 URL: http://svnweb.freebsd.org/changeset/doc/40719 Log: My 1st commit! Add myself according to Conventions and Traditions Approved by: rm (mentor) Modified: head/en_US.ISO8859-1/articles/contributors/contrib.additional.xml head/en_US.ISO8859-1/articles/contributors/contrib.committers.xml head/share/xml/authors.ent head/share/xml/developers.ent head/share/xml/news.xml Modified: head/en_US.ISO8859-1/articles/contributors/contrib.additional.xml ============================================================================== --- head/en_US.ISO8859-1/articles/contributors/contrib.additional.xml Tue Jan 22 03:20:36 2013 (r40718) +++ head/en_US.ISO8859-1/articles/contributors/contrib.additional.xml Tue Jan 22 08:08:51 2013 (r40719) @@ -5312,11 +5312,6 @@ - Kubilay Kocak - koobs.freebsd@gmail.com - - - KUNISHIMA Takeo kunishi@c.oka-pu.ac.jp Modified: head/en_US.ISO8859-1/articles/contributors/contrib.committers.xml ============================================================================== --- head/en_US.ISO8859-1/articles/contributors/contrib.committers.xml Tue Jan 22 03:20:36 2013 (r40718) +++ head/en_US.ISO8859-1/articles/contributors/contrib.committers.xml Tue Jan 22 08:08:51 2013 (r40719) @@ -700,6 +700,10 @@ + &a.koobs; + + + &a.jkois; Modified: head/share/xml/authors.ent ============================================================================== --- head/share/xml/authors.ent Tue Jan 22 03:20:36 2013 (r40718) +++ head/share/xml/authors.ent Tue Jan 22 08:08:51 2013 (r40719) @@ -732,6 +732,8 @@ kmoore@FreeBSD.org"> +koobs@FreeBSD.org"> + knu@FreeBSD.org"> koitsu@FreeBSD.org"> Modified: head/share/xml/developers.ent ============================================================================== --- head/share/xml/developers.ent Tue Jan 22 03:20:36 2013 (r40718) +++ head/share/xml/developers.ent Tue Jan 22 08:08:51 2013 (r40719) @@ -352,6 +352,7 @@ $FreeBSD$ + Modified: head/share/xml/news.xml ============================================================================== --- head/share/xml/news.xml Tue Jan 22 03:20:36 2013 (r40718) +++ head/share/xml/news.xml Tue Jan 22 08:08:51 2013 (r40719) @@ -152,6 +152,14 @@ + 24 + +

    New committer: + Kubilay Kocak (ports)

    +     +     + + 20 From owner-svn-doc-all@FreeBSD.ORG Tue Jan 22 12:27:42 2013 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 0D76F27F; Tue, 22 Jan 2013 12:27:42 +0000 (UTC) (envelope-from ryusuke@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id 00357EE8; Tue, 22 Jan 2013 12:27:41 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.5/8.14.5) with ESMTP id r0MCRf5X048347; Tue, 22 Jan 2013 12:27:41 GMT (envelope-from ryusuke@svn.freebsd.org) Received: (from ryusuke@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r0MCRfVt048346; Tue, 22 Jan 2013 12:27:41 GMT (envelope-from ryusuke@svn.freebsd.org) Message-Id: <201301221227.r0MCRfVt048346@svn.freebsd.org> From: Ryusuke SUZUKI Date: Tue, 22 Jan 2013 12:27:41 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40720 - head/ja_JP.eucJP/share/xml X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Jan 2013 12:27:42 -0000 Author: ryusuke Date: Tue Jan 22 12:27:41 2013 New Revision: 40720 URL: http://svnweb.freebsd.org/changeset/doc/40720 Log: - Merge the following from the English version: r40680 -> r40719 head/ja_JP.eucJP/share/xml/news.xml Modified: head/ja_JP.eucJP/share/xml/news.xml Modified: head/ja_JP.eucJP/share/xml/news.xml ============================================================================== --- head/ja_JP.eucJP/share/xml/news.xml Tue Jan 22 08:08:51 2013 (r40719) +++ head/ja_JP.eucJP/share/xml/news.xml Tue Jan 22 12:27:41 2013 (r40720) @@ -20,7 +20,7 @@ the contents of will be preferred over <p>. $FreeBSD$ - Original revision: r40680 + Original revision: r40719 --> <news> <cvs:keyword xmlns:cvs="http://www.FreeBSD.org/XML/CVS"> @@ -150,6 +150,14 @@ </day> <day> + <name>24</name> + <event> + <p>¿·¥³¥ß¥Ã¥¿½¢Ç¤: + <a href="mailto:koobs@FreeBSD.org">Kubilay Kocak</a> (ports)</p> + </event> + </day> + + <day> <name>20</name> <event> From owner-svn-doc-all@FreeBSD.ORG Tue Jan 22 17:36:26 2013 Return-Path: <owner-svn-doc-all@FreeBSD.ORG> Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 1D9FB36D; Tue, 22 Jan 2013 17:36:26 +0000 (UTC) (envelope-from dru@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id F375082E; Tue, 22 Jan 2013 17:36:25 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.5/8.14.5) with ESMTP id r0MHaPUc049459; Tue, 22 Jan 2013 17:36:25 GMT (envelope-from dru@svn.freebsd.org) Received: (from dru@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r0MHaOY3049450; Tue, 22 Jan 2013 17:36:24 GMT (envelope-from dru@svn.freebsd.org) Message-Id: <201301221736.r0MHaOY3049450@svn.freebsd.org> From: Dru Lavigne <dru@FreeBSD.org> Date: Tue, 22 Jan 2013 17:36:24 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40721 - in head: en_US.ISO8859-1/articles/contributors share/pgpkeys share/xml X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" <svn-doc-all.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/svn-doc-all>, <mailto:svn-doc-all-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/svn-doc-all> List-Post: <mailto:svn-doc-all@freebsd.org> List-Help: <mailto:svn-doc-all-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/svn-doc-all>, <mailto:svn-doc-all-request@freebsd.org?subject=subscribe> X-List-Received-Date: Tue, 22 Jan 2013 17:36:26 -0000 Author: dru Date: Tue Jan 22 17:36:24 2013 New Revision: 40721 URL: http://svnweb.freebsd.org/changeset/doc/40721 Log: first commit, add myself as committer Approved by: gjb (mentor) Added: head/share/pgpkeys/dru.key (contents, props changed) Modified: head/en_US.ISO8859-1/articles/contributors/contrib.committers.xml head/share/pgpkeys/pgpkeys-developers.xml head/share/pgpkeys/pgpkeys.ent head/share/xml/authors.ent head/share/xml/developers.ent head/share/xml/news.xml Modified: head/en_US.ISO8859-1/articles/contributors/contrib.committers.xml ============================================================================== --- head/en_US.ISO8859-1/articles/contributors/contrib.committers.xml Tue Jan 22 12:27:41 2013 (r40720) +++ head/en_US.ISO8859-1/articles/contributors/contrib.committers.xml Tue Jan 22 17:36:24 2013 (r40721) @@ -788,6 +788,10 @@ </listitem> <listitem> + <para>&a.dru;</para> + </listitem> + + <listitem> <para>&a.jlh;</para> </listitem> Added: head/share/pgpkeys/dru.key ============================================================================== --- /dev/null 00:00:00 1970 (empty, because file is newly added) +++ head/share/pgpkeys/dru.key Tue Jan 22 17:36:24 2013 (r40721) @@ -0,0 +1,35 @@ +<!-- $FreeBSD$ --> +<!-- +sh ./addkey.sh dru C6AA2E94; +--> +<programlisting role="pgpfingerprint"><![CDATA[ +pub 1024D/C6AA2E94 2013-01-22 + Key fingerprint = 6CC4 2180 F27C 29B6 5A9C EC0D A454 DC05 C6AA 2E94 +uid Dru Lavigne <dru@freebsd.org> +sub 1024g/7FAC82EA 2013-01-22 +]]></programlisting> +<programlisting role="pgpkey"><![CDATA[ +-----BEGIN PGP PUBLIC KEY BLOCK----- + +mQGiBFD+vdwRBAD2rMN1ZfqBN9PCvrGHaatVwfORzhr6gSFFjxk5Z6HhnGsQSO8r +NAmU9wdINOXJ2M9tqpDXV7R9nEHTvcvjZ4Eolc+fNwGTpglpDX8F8bp5VaQ4+aW5 +nwDs+JoLw94MSfbrviXCDe73Eyp4EGMoZ7PlVwvJ8oloIv7T2qtlAeUlRwCgjH4v +BOGZab9uoAqaBzMYk13FM/cD+gKe8+bewQyp8sthXrZWYbyyyIu0MdfMxpRZ45aU +eDrxuZL536qvaiAy3DmnF/nHkZX3/6XTSlkgyQbzLnI9OZVcDFA/Dke5qVk+xUqp +Vyei9HNOsS3u/Nn70HoFijsYUq+hY7aefxoMtJfer+aiJNJRj32DvUP/ZdeJ8jCQ +9ZtdBACEmRZ2UjYYMklBZdp71/HFLc+0+hxl7IU6H609Fqace+aCKRrZZ1QzzNK6 +/DEnR6BYPN3eSzMoLLoAvLIzpfaUx/IfHxbyjCaXi0cYYZ9FkUUt7a3qJLSZGnK2 +tA1Fw3kFBBO60t9T9cQXHv/sd3bXmIP8eUe++5dfJ5UmmK1f6rQdRHJ1IExhdmln +bmUgPGRydUBmcmVlYnNkLm9yZz6IYgQTEQIAIgUCUP693AIbIwYLCQgHAwIGFQgC +CQoLBBYCAwECHgECF4AACgkQpFTcBcaqLpThwQCffhk585hEfh9LHkYzVZIpu3DT +cqAAn2BgkvA9qN6qJnDtpcKoQh+nnjCeuQENBFD+vdwQBACc80FRBODUmXvpVKxZ +ql/tAKl30ij0OVLHLdQQH4W3+LuO0U1Uxle5IbwQHfZh6KtyH1AwafBLZ/lg6ihh +ImtvvlAoPhGqeKi2L08djYYRsaQl8snCPrcwVtUiAPqVXCkIFzmcA1dlFRUg68re +/f8uSKt41FqtkR3v+QsHdflOHwADBQP9GaQUxdrLssRNH/fEkMg8xZYLGOOg8hcX +BwNujIol+Yyq5QZFMZxaFbmdKhCnVH46cOFheHpgRQcwfoMLk4yfZkmw4W1ANyI6 +hzzFHtnSLYG7CGkgQE6NS+bjTAxVWGK48SsUxS2RcxPAQmLqTEHTgoav43L/6gAY +N2QsQo4b3NmISQQYEQIACQUCUP693AIbDAAKCRCkVNwFxqoulMOJAJ9VIUzfi5Y5 +GN4vvJ8KQE4+RZBRLACeOgRRbnd+Xsbu2V6mez1KHF4UUVw= +=lVUC +-----END PGP PUBLIC KEY BLOCK----- +]]></programlisting> Modified: head/share/pgpkeys/pgpkeys-developers.xml ============================================================================== --- head/share/pgpkeys/pgpkeys-developers.xml Tue Jan 22 12:27:41 2013 (r40720) +++ head/share/pgpkeys/pgpkeys-developers.xml Tue Jan 22 17:36:24 2013 (r40721) @@ -941,6 +941,11 @@ &pgpkey.laszlof; </sect2> + <sect2 id="pgpkey-dru"> + <title>&a.dru; + &pgpkey.dru; + + &a.lawrance; &pgpkey.lawrance; Modified: head/share/pgpkeys/pgpkeys.ent ============================================================================== --- head/share/pgpkeys/pgpkeys.ent Tue Jan 22 12:27:41 2013 (r40720) +++ head/share/pgpkeys/pgpkeys.ent Tue Jan 22 17:36:24 2013 (r40721) @@ -105,6 +105,7 @@ + Modified: head/share/xml/authors.ent ============================================================================== --- head/share/xml/authors.ent Tue Jan 22 12:27:41 2013 (r40720) +++ head/share/xml/authors.ent Tue Jan 22 17:36:24 2013 (r40721) @@ -362,6 +362,8 @@ dougb@FreeBSD.org"> +dru@FreeBSD.org"> + dryice@FreeBSD.org"> dt@FreeBSD.org"> Modified: head/share/xml/developers.ent ============================================================================== --- head/share/xml/developers.ent Tue Jan 22 12:27:41 2013 (r40720) +++ head/share/xml/developers.ent Tue Jan 22 17:36:24 2013 (r40721) @@ -175,6 +175,7 @@ $FreeBSD$ + Modified: head/share/xml/news.xml ============================================================================== --- head/share/xml/news.xml Tue Jan 22 12:27:41 2013 (r40720) +++ head/share/xml/news.xml Tue Jan 22 17:36:24 2013 (r40721) @@ -32,6 +32,15 @@ 1 + + + 22 + +

    New committer: + Dru Lavigne (doc)

    +     +     + 16 From owner-svn-doc-all@FreeBSD.ORG Wed Jan 23 02:42:59 2013 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 6595C570; Wed, 23 Jan 2013 02:42:59 +0000 (UTC) (envelope-from eadler@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id 57A672D1; Wed, 23 Jan 2013 02:42:59 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.5/8.14.5) with ESMTP id r0N2gx2K016966; Wed, 23 Jan 2013 02:42:59 GMT (envelope-from eadler@svn.freebsd.org) Received: (from eadler@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r0N2gxer016965; Wed, 23 Jan 2013 02:42:59 GMT (envelope-from eadler@svn.freebsd.org) Message-Id: <201301230242.r0N2gxer016965@svn.freebsd.org> From: Eitan Adler Date: Wed, 23 Jan 2013 02:42:59 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40722 - head/en_US.ISO8859-1/books/faq X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Jan 2013 02:42:59 -0000 Author: eadler Date: Wed Jan 23 02:42:58 2013 New Revision: 40722 URL: http://svnweb.freebsd.org/changeset/doc/40722 Log: List our friends and relatives. Submitted by: Alex Weber Approved by: bcr (mentor) Modified: head/en_US.ISO8859-1/books/faq/book.xml Modified: head/en_US.ISO8859-1/books/faq/book.xml ============================================================================== --- head/en_US.ISO8859-1/books/faq/book.xml Tue Jan 22 17:36:24 2013 (r40721) +++ head/en_US.ISO8859-1/books/faq/book.xml Wed Jan 23 02:42:58 2013 (r40722) @@ -309,7 +309,37 @@ differences between the various projects, called The BSD Family Tree - which goes a fair way to answering this question.     + which goes a fair way to answering this question. + Some of the information is out of date, but the history + portion in particular remains accurate. + + Most of the BSDs share patches and code, even today. + All of the BSDs have common ancestry. + + The design goals of &os; are described in + , above. The design goals + of the other most popular BSDs may be summarized as + follows: + + + + OpenBSD aims for operating system security above + all else. The OpenBSD team wrote &man.ssh.1; and + &man.pf.4;, which have both been ported to &os;. + + + + NetBSD aims to be easily ported to other hardware + platforms. + + + + DragonFlyBSD is a fork of &os; 4.8 that has + since developed many interesting features of its own, + including the HAMMER file system and support for + user-mode vkernels. + +     From owner-svn-doc-all@FreeBSD.ORG Wed Jan 23 02:48:29 2013 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 4609E757; Wed, 23 Jan 2013 02:48:29 +0000 (UTC) (envelope-from eadler@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id 28EFA2FD; Wed, 23 Jan 2013 02:48:29 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.5/8.14.5) with ESMTP id r0N2mT7k017883; Wed, 23 Jan 2013 02:48:29 GMT (envelope-from eadler@svn.freebsd.org) Received: (from eadler@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r0N2mTiX017882; Wed, 23 Jan 2013 02:48:29 GMT (envelope-from eadler@svn.freebsd.org) Message-Id: <201301230248.r0N2mTiX017882@svn.freebsd.org> From: Eitan Adler Date: Wed, 23 Jan 2013 02:48:29 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40723 - head/en_US.ISO8859-1/books/faq X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Jan 2013 02:48:29 -0000 Author: eadler Date: Wed Jan 23 02:48:28 2013 New Revision: 40723 URL: http://svnweb.freebsd.org/changeset/doc/40723 Log: Wes gesund obsolete section: dangerously-dedicated Noted by: nwhitehorn Aproved by: bcr (mentor, implicit) Modified: head/en_US.ISO8859-1/books/faq/book.xml Modified: head/en_US.ISO8859-1/books/faq/book.xml ============================================================================== --- head/en_US.ISO8859-1/books/faq/book.xml Wed Jan 23 02:42:58 2013 (r40722) +++ head/en_US.ISO8859-1/books/faq/book.xml Wed Jan 23 02:48:28 2013 (r40723) @@ -3550,110 +3550,6 @@ kern.sched.name: ULE     - - Will a dangerously dedicated disk - endanger my health? - - - - The installation procedure allows - you to chose two different methods in partitioning your hard - disk(s). The default way makes it compatible with other - operating systems on the same machine, by using - &man.fdisk.8; table entries (called slices in - &os;), with a &os; slice that employs partitions of its own. - Optionally, one can chose to install a boot-selector to - switch between the possible operating systems on the - disk(s). The alternative uses the entire disk for &os;, and - makes no attempt to be compatible with other operating - systems. - - So why it is called dangerous? A disk in - this mode does not contain what normal PC utilities would - consider a valid &man.fdisk.8; table. Depending on how well - they have been designed, they might complain at you once - they are getting in contact with such a disk, or even worse, - they might damage the BSD bootstrap without even asking or - notifying you. In addition, the dangerously - dedicated disk's layout is known to confuse some - BIOSes. - Symptoms of this confusion include the read - error message printed by the &os; bootstrap when - it cannot find itself, as well as system lockups when - booting. - - Why have this mode at all then? It only saves a few - kbytes of disk space, and it can cause real problems for a new - installation. Dangerously dedicated mode's - origins lie in a desire to avoid one of the most common - problems plaguing new &os; installers — matching the - BIOS geometry numbers for a disk to the disk - itself. - - Geometry is an outdated concept, but one - still at the heart of the PC's BIOS and its interaction with - disks. When the &os; installer creates slices, it has to - record the location of these slices on the disk in a fashion - that corresponds with the way the BIOS expects to find them. - If it gets it wrong, you will not be able to boot. - - Dangerously dedicated mode tries to work - around this by making the problem simpler. In some cases, - it gets it right. But it is meant to be used as a - last-ditch alternative — there are better ways to - solve the problem 99 times out of 100. - - So, how do you avoid the need for DD mode - when you are installing? Start by making a note of the - geometry that your BIOS claims to be using for your disks. - You can arrange to have the kernel print this as it boots by - specifying at the - boot: prompt, or using - boot -v in the loader. Just before the - installer starts, the kernel will print a list of BIOS - geometries. Do not panic — wait for the installer to - start and then use scrollback to read the numbers. - Typically the BIOS disk units will be in the same order that - &os; lists your disks, first IDE, then SCSI. - - When you are slicing up your disk, check that the disk - geometry displayed in the FDISK screen is correct (i.e., it - matches the BIOS numbers); if it is wrong, use - G to fix it. You may have to do this - if there is absolutely nothing on the disk, or if the disk - has been moved from another system. Note that this is only - an issue with the disk that you are going to boot from; &os; - will sort itself out just fine with any other disks you may - have. - - Once you have got the BIOS and &os; agreeing about the - geometry of the disk, your problems are almost guaranteed to - be over, and with no need for DD mode at all. - If, however, you are still greeted with the dreaded - read error message when you try to - boot, it is time to cross your fingers and go for it — there - is nothing left to lose. - - To return a dangerously dedicated disk - for normal PC use, there are basically two options. The - first is, you write enough NULL bytes over the MBR to make - any subsequent installation believe this to be a blank disk. - You can do this for example with the following - command: - - &prompt.root; dd if=/dev/zero of=/dev/rda0 count=15 - - Alternatively, the undocumented DOS - feature - - C:\> fdisk /mbr - - will to install a new master boot record as well, thus - clobbering the BSD bootstrap. - - - - Which partitions can safely use Soft Updates? I have heard that Soft Updates on / can cause From owner-svn-doc-all@FreeBSD.ORG Wed Jan 23 08:35:30 2013 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 84DEDE39; Wed, 23 Jan 2013 08:35:30 +0000 (UTC) (envelope-from ryusuke@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id 776D7156; Wed, 23 Jan 2013 08:35:30 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.5/8.14.5) with ESMTP id r0N8ZUxS021702; Wed, 23 Jan 2013 08:35:30 GMT (envelope-from ryusuke@svn.freebsd.org) Received: (from ryusuke@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r0N8ZUiS021701; Wed, 23 Jan 2013 08:35:30 GMT (envelope-from ryusuke@svn.freebsd.org) Message-Id: <201301230835.r0N8ZUiS021701@svn.freebsd.org> From: Ryusuke SUZUKI Date: Wed, 23 Jan 2013 08:35:30 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40724 - head/ja_JP.eucJP/share/xml X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Jan 2013 08:35:30 -0000 Author: ryusuke Date: Wed Jan 23 08:35:29 2013 New Revision: 40724 URL: http://svnweb.freebsd.org/changeset/doc/40724 Log: - Merge the following from the English version: r40719 -> r40721 head/ja_JP.eucJP/share/xml/news.xml Modified: head/ja_JP.eucJP/share/xml/news.xml Modified: head/ja_JP.eucJP/share/xml/news.xml ============================================================================== --- head/ja_JP.eucJP/share/xml/news.xml Wed Jan 23 02:48:28 2013 (r40723) +++ head/ja_JP.eucJP/share/xml/news.xml Wed Jan 23 08:35:29 2013 (r40724) @@ -20,7 +20,7 @@ the contents of will be preferred over <p>. $FreeBSD$ - Original revision: r40719 + Original revision: r40721 --> <news> <cvs:keyword xmlns:cvs="http://www.FreeBSD.org/XML/CVS"> @@ -34,6 +34,14 @@ <name>1</name> <day> + <name>22</name> + <event> + <p>¿·¥³¥ß¥Ã¥¿½¢Ç¤: + <a href="mailto:dru@FreeBSD.org">Dru Lavigne</a> (doc)</p> + </event> + </day> + + <day> <name>16</name> <event> <p>¿·¥³¥ß¥Ã¥¿½¢Ç¤: From owner-svn-doc-all@FreeBSD.ORG Wed Jan 23 12:35:22 2013 Return-Path: <owner-svn-doc-all@FreeBSD.ORG> Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 383929CF; Wed, 23 Jan 2013 12:35:22 +0000 (UTC) (envelope-from ryusuke@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id 1BEE0ECA; Wed, 23 Jan 2013 12:35:22 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.5/8.14.5) with ESMTP id r0NCZMms093299; Wed, 23 Jan 2013 12:35:22 GMT (envelope-from ryusuke@svn.freebsd.org) Received: (from ryusuke@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r0NCZMcG093298; Wed, 23 Jan 2013 12:35:22 GMT (envelope-from ryusuke@svn.freebsd.org) Message-Id: <201301231235.r0NCZMcG093298@svn.freebsd.org> From: Ryusuke SUZUKI <ryusuke@FreeBSD.org> Date: Wed, 23 Jan 2013 12:35:22 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40726 - head/ja_JP.eucJP/books/handbook/cutting-edge X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" <svn-doc-all.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/svn-doc-all>, <mailto:svn-doc-all-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/svn-doc-all> List-Post: <mailto:svn-doc-all@freebsd.org> List-Help: <mailto:svn-doc-all-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/svn-doc-all>, <mailto:svn-doc-all-request@freebsd.org?subject=subscribe> X-List-Received-Date: Wed, 23 Jan 2013 12:35:22 -0000 Author: ryusuke Date: Wed Jan 23 12:35:21 2013 New Revision: 40726 URL: http://svnweb.freebsd.org/changeset/doc/40726 Log: - Merge the following from the English version: r40608 -> r40712 head/ja_JP.eucJP/books/handbook/cutting-edge/chapter.xml Modified: head/ja_JP.eucJP/books/handbook/cutting-edge/chapter.xml Modified: head/ja_JP.eucJP/books/handbook/cutting-edge/chapter.xml ============================================================================== --- head/ja_JP.eucJP/books/handbook/cutting-edge/chapter.xml Wed Jan 23 09:11:13 2013 (r40725) +++ head/ja_JP.eucJP/books/handbook/cutting-edge/chapter.xml Wed Jan 23 12:35:21 2013 (r40726) @@ -3,7 +3,7 @@ The FreeBSD Documentation Project The FreeBSD Japanese Documentation Project - Original revision: r40608 + Original revision: r40712 $FreeBSD$ --> @@ -346,15 +346,26 @@ MergeChanges /etc/ /var/named/etc/</prog </sect2> <sect2 id="freebsdupdate-upgrade"> - <title>¥á¥¸¥ã¡¼¤ª¤è¤Ó¥Þ¥¤¥Ê¡¼¥¢¥Ã¥×¥°¥ì¡¼¥É + ¥á¥¸¥ã¡¼¤ª¤è¤Ó¥Þ¥¤¥Ê¡¼¥Ð¡¼¥¸¥ç¥ó¤Î¥¢¥Ã¥×¥°¥ì¡¼¥É - ¤³¤Î¥×¥í¥»¥¹¤Ç¤Ï¡¢¸Å¤¤¥ª¥Ö¥¸¥§¥¯¥È¥Õ¥¡¥¤¥ë¤ä¥é¥¤¥Ö¥é¥ê¤¬ºï½ü¤µ¤ì¡¢ + &os; ¤Î¥Þ¥¤¥Ê¡¼¥Ð¡¼¥¸¥ç¥ó´Ö¤Î¥¢¥Ã¥×¥°¥ì¡¼¥É¡¢ + ¤¿¤È¤¨¤Ð¡¢&os; 9.0 ¤«¤é &os; 9.1 ¤Ø¤Î¥¢¥Ã¥×¥°¥ì¡¼¥É¤Ï¡¢ + ¥Þ¥¤¥Ê¡¼¥Ð¡¼¥¸¥ç¥ó ¥¢¥Ã¥×¥°¥ì¡¼¥É¤È¸Æ¤Ð¤ì¤Þ¤¹¡£ + Ä̾ï¤Ï¡¢¥Þ¥¤¥Ê¡¼¥Ð¡¼¥¸¥ç¥ó¤Î¥¢¥Ã¥×¥°¥ì¡¼¥É¤ò¹Ô¤Ã¤¿¸å¤Ç¤â¡¢ + ¥¤¥ó¥¹¥È¡¼¥ë¤µ¤ì¤Æ¤¤¤ë¥¢¥×¥ê¥±¡¼¥·¥ç¥ó¤ÏÌäÂê¤Ê¤¯Æ°¤­¤Þ¤¹¡£ + + ¥á¥¸¥ã¡¼¥Ð¡¼¥¸¥ç¥ó ¥¢¥Ã¥×¥°¥ì¡¼¥É¤Ï¡¢ + &os; 8.X ¤«¤é &os; 9.X ¤Ø¤Î¥¢¥Ã¥×¥°¥ì¡¼¥É¤È¤¤¤Ã¤¿¡¢ + &os; ¤Î¥á¥¸¥ã¡¼¥Ð¡¼¥¸¥ç¥ó¤¬ÊѤï¤ë¤è¤¦¤Ê¥¢¥Ã¥×¥°¥ì¡¼¥É¤Î¤³¤È¤Ç¤¹¡£ + ¥á¥¸¥ã¡¼¥Ð¡¼¥¸¥ç¥ó¤Î¥¢¥Ã¥×¥°¥ì¡¼¥É¤Ç¤Ï¡¢ + ¸Å¤¤¥ª¥Ö¥¸¥§¥¯¥È¥Õ¥¡¥¤¥ë¤ä¥é¥¤¥Ö¥é¥ê¤¬ºï½ü¤µ¤ì¡¢ ¤³¤ì¤é¤Ë°Í¸¤¹¤ë¿¤¯¤Î¥µ¡¼¥É¥Ñ¡¼¥Æ¥£À½¥¢¥×¥ê¥±¡¼¥·¥ç¥ó¤Ë±Æ¶Á¤òÍ¿¤¨¤ë²ÄǽÀ­¤¬¤¢¤ê¤Þ¤¹¡£ ¥¤¥ó¥¹¥È¡¼¥ë¤µ¤ì¤Æ¤¤¤ë¤¹¤Ù¤Æ¤Î ports ¤òºï½ü¤·¤ÆºÆ¥¤¥ó¥¹¥È¡¼¥ë¤¹¤ë¤«¡¢ - ¸å¤Ç¡¢ports-mgmt/portupgrade + ¥á¥¸¥ã¡¼¥¢¥Ã¥×¥°¥ì¡¼¥É¸å¡¢ + ports-mgmt/portupgrade ¥æ¡¼¥Æ¥£¥ê¥Æ¥£¤ò»È¤Ã¤Æ¥¢¥Ã¥×¥°¥ì¡¼¥É¤¹¤ë¤³¤È¤¬¿ä¾©¤µ¤ì¤Æ¤¤¤Þ¤¹¡£ - »î¸³Åª¤Ë¥Ó¥ë¥É¤ò¹Ô¤¤¤¿¤¤¤È»×¤Ã¤Æ¤¤¤ë¥æ¡¼¥¶¤Ï¡¢ - °Ê²¼¤Î¥³¥Þ¥ó¥É¤ò¼Â¹Ô¤·¤Æ¤¯¤À¤µ¤¤¡£ + ¥¤¥ó¥¹¥È¡¼¥ë¤µ¤ì¤Æ¤¤¤ë¥¢¥×¥ê¥±¡¼¥·¥ç¥ó¤Î¥Ö¥ë¡¼¥È¥Õ¥©¡¼¥¹Åª¤ÊºÆ¹½Ãۤϡ¢ + °Ê²¼¤Î¥³¥Þ¥ó¥É¤Ë¤è¤ê¹Ô¤¦¤³¤È¤¬¤Ç¤­¤Þ¤¹¡£ &prompt.root; portupgrade -af @@ -365,82 +376,141 @@ MergeChanges /etc/ /var/named/etc/yes ¤ÈÅú¤¨¤ë¤è¤¦¤Ë¤Ê¤ë¤Î¤Ç¡¢ ¥Ó¥ë¥É¥×¥í¥»¥¹¤Ç¤Î¼êÆ°Áàºî¤ò¾Êά¤Ç¤­¤Þ¤¹¡£ - ¥«¥¹¥¿¥à¥«¡¼¥Í¥ë¤ò»ÈÍѤ·¤Æ¤¤¤ë¾ì¹ç¤Ë¤Ï¡¢ - ¥¢¥Ã¥×¥°¥ì¡¼¥É¤Î¥×¥í¥»¥¹¤Ï´öʬʣ»¨¤È¤Ê¤ê¤Þ¤¹¡£ - GENERIC ¥«¡¼¥Í¥ë¤¬ /boot/GENERIC - ¤ËÃÖ¤«¤ì¤Æ¤¤¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£ - ¤â¤· GENERIC - ¥«¡¼¥Í¥ë¤¬¥·¥¹¥Æ¥à¤Ë¸ºß¤·¤Ê¤¤¾ì¹ç¤Ë¤Ï¡¢ - °Ê²¼¤Î¤É¤ì¤«¤ÎÊýË¡¤ÇÍÑ°Õ¤·¤Æ¤¯¤À¤µ¤¤¡£ + + ¥«¥¹¥¿¥à¥«¡¼¥Í¥ë¤Î¼è¤ê°·¤¤ - - - ¤¿¤À°ìÅÙ¤À¤±¥«¥¹¥¿¥à¥«¡¼¥Í¥ë¤ò¹½ÃÛ¤·¤¿¤Î¤Ç¤¢¤ì¤Ð¡¢ - /boot/kernel.old - ¥«¡¼¥Í¥ë¤Ï GENERIC ¤½¤Î¤â¤Î¤Ç¤¹¡£ - ¤¿¤Àñ¤Ë¤³¤Î¥Ç¥£¥ì¥¯¥È¥ê¤Î̾Á°¤ò - /boot/GENERIC - ¤Ø¤ÈÊѹ¹¤·¤Æ¤¯¤À¤µ¤¤¡£ - + ¥«¥¹¥¿¥à¥«¡¼¥Í¥ë¤ò»ÈÍѤ·¤Æ¤¤¤ë¾ì¹ç¤Ë¤Ï¡¢¥¢¥Ã¥×¥°¥ì¡¼¥É¤Î¥×¥í¥»¥¹¤Ï¡¢ + ´öʬʣ»¨¤È¤Ê¤ê¤Þ¤¹¡£ + ¥¢¥Ã¥×¥°¥ì¡¼¥É¤Î¼ê½ç¤Ï &os; ¤Î¥Ð¡¼¥¸¥ç¥ó¤Ë¤è¤Ã¤ÆÊѤï¤ê¤Þ¤¹¡£ - - ¥³¥ó¥Ô¥å¡¼¥¿¤Ø¤ÎʪÍýŪ¤Ê¥¢¥¯¥»¥¹¤¬²Äǽ¤Ç¤¢¤ì¤Ð¡¢ - CD-ROM ¤«¤é GENERIC - ¥«¡¼¥Í¥ë¤ò¥¤¥ó¥¹¥È¡¼¥ë¤Ç¤­¤Þ¤¹¡£ - ¥¤¥ó¥¹¥È¡¼¥ë¥Ç¥£¥¹¥¯¤òÁÞÆþ¤·¤Æ¡¢°Ê²¼¤Î¥³¥Þ¥ó¥É¤ò¼Â¹Ô¤·¤Æ¤¯¤À¤µ¤¤¡£ + + &os; 8.X °ÊÁ°¤Î¥·¥¹¥Æ¥à¤Ë¤ª¤±¤ë¥«¥¹¥¿¥à¥«¡¼¥Í¥ë + + GENERIC ¥«¡¼¥Í¥ë¤¬ + /boot/GENERIC + ¤ËÃÖ¤«¤ì¤Æ¤¤¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£ + ¤â¤· GENERIC + ¥«¡¼¥Í¥ë¤¬¥·¥¹¥Æ¥à¤Ë¸ºß¤·¤Ê¤¤¾ì¹ç¤Ë¤Ï¡¢ + °Ê²¼¤Î¤É¤ì¤«¤ÎÊýË¡¤ÇÍÑ°Õ¤·¤Æ¤¯¤À¤µ¤¤¡£ + + + + ¤¿¤À°ìÅÙ¤À¤±¥«¥¹¥¿¥à¥«¡¼¥Í¥ë¤ò¹½ÃÛ¤·¤¿¤Î¤Ç¤¢¤ì¤Ð¡¢ + /boot/kernel.old + ¤Ï GENERIC ¥«¡¼¥Í¥ë¤½¤Î¤â¤Î¤Ç¤¹¡£ + ¤¿¤Àñ¤Ë¤³¤Î¥Ç¥£¥ì¥¯¥È¥ê¤Î̾Á°¤ò + /boot/GENERIC + ¤Ø¤ÈÊѹ¹¤·¤Æ¤¯¤À¤µ¤¤¡£ + + + + ¥³¥ó¥Ô¥å¡¼¥¿¤Ø¤ÎʪÍýŪ¤Ê¥¢¥¯¥»¥¹¤¬²Äǽ¤Ç¤¢¤ì¤Ð¡¢ + CD-ROM ¥á¥Ç¥£¥¢¤«¤é GENERIC + ¥«¡¼¥Í¥ë¤ò¥¤¥ó¥¹¥È¡¼¥ë¤Ç¤­¤Þ¤¹¡£ + ¥¤¥ó¥¹¥È¡¼¥ë¥Ç¥£¥¹¥¯¤òÁÞÆþ¤·¤Æ¡¢°Ê²¼¤Î¥³¥Þ¥ó¥É¤ò¼Â¹Ô¤·¤Æ¤¯¤À¤µ¤¤¡£ - &prompt.root; mount /cdrom + &prompt.root; mount /cdrom &prompt.root; cd /cdrom/X.Y-RELEASE/kernels &prompt.root; ./install.sh GENERIC - ¤³¤³¤Ç X.Y-RELEASE - ¤ò¼ÂºÝ¤Î¥ê¥ê¡¼¥¹ÈÖ¹æ¤ËÃÖ¤­´¹¤¨¤Æ¤¯¤À¤µ¤¤¡£ - GENERIC ¤Ï¡¢¥Ç¥Õ¥©¥ë¥È¤Ç /boot/GENERIC - ¤Ë¥¤¥ó¥¹¥È¡¼¥ë¤µ¤ì¤Þ¤¹¡£ - - - - ¾åµ­¤ÎÊýË¡¤¬¼ºÇÔ¤¹¤ë¤Î¤Ç¤¢¤ì¤Ð¡¢ - GENERIC ¥«¡¼¥Í¥ë¤ò¥½¡¼¥¹¤«¤éºÆ¹½ÃÛ¤·¤Æ¡¢ - ¥¤¥ó¥¹¥È¡¼¥ë¤·¤Æ¤¯¤À¤µ¤¤¡£ + ¤³¤³¤Ç X.Y-RELEASE + ¤ò¼ÂºÝ¤Î¥ê¥ê¡¼¥¹ÈÖ¹æ¤ËÃÖ¤­´¹¤¨¤Æ¤¯¤À¤µ¤¤¡£ + GENERIC ¤Ï¡¢¥Ç¥Õ¥©¥ë¥È¤Ç /boot/GENERIC + ¤Ë¥¤¥ó¥¹¥È¡¼¥ë¤µ¤ì¤Þ¤¹¡£ + + + + ¾åµ­¤ÎÊýË¡¤¬¤¹¤Ù¤Æ¼ºÇÔ¤¹¤ë¤Î¤Ç¤¢¤ì¤Ð¡¢ + GENERIC ¥«¡¼¥Í¥ë¤ò¥½¡¼¥¹¤«¤éºÆ¹½ÃÛ¤·¤Æ¡¢ + ¥¤¥ó¥¹¥È¡¼¥ë¤·¤Æ¤¯¤À¤µ¤¤¡£ - &prompt.root; cd /usr/src + &prompt.root; cd /usr/src &prompt.root; env DESTDIR=/boot/GENERIC make kernel &prompt.root; mv /boot/GENERIC/boot/kernel/* /boot/GENERIC &prompt.root; rm -rf /boot/GENERIC/boot - freebsd-update ¤Ï¡¢¤³¤Î¥«¡¼¥Í¥ë¤ò - GENERIC ¤È¤·¤Æ°·¤¤¤Þ¤¹¡£ - GENERIC ¥³¥ó¥Õ¥£¥°¥ì¡¼¥·¥ç¥ó¥Õ¥¡¥¤¥ë¤Ï¡¢ - ¤È¤Ë¤«¤¯Êѹ¹¤·¤Æ¤Ï¤¤¤±¤Þ¤»¤ó¡£ - ¤Þ¤¿¡¢ÆÃÊ̤ʥª¥×¥·¥ç¥ó¤ò»ØÄꤷ¤Ê¤¤ - (/etc/make.conf ¤¬¶õ¤Ç¤¢¤ë¤³¤È¤¬Ë¾¤Þ¤·¤¤) - ¤Ç¹½ÃÛ¤·¤Æ¤¯¤À¤µ¤¤¡£ - - + freebsd-update ¤Ï¡¢¤³¤Î¥«¡¼¥Í¥ë¤ò + GENERIC ¥«¡¼¥Í¥ë¤È¤·¤Æ°·¤¤¤Þ¤¹¡£ + GENERIC ¥³¥ó¥Õ¥£¥°¥ì¡¼¥·¥ç¥ó¥Õ¥¡¥¤¥ë¤Ï¡¢ + ¤È¤Ë¤«¤¯Êѹ¹¤·¤Æ¤Ï¤¤¤±¤Þ¤»¤ó¡£ + ¤Þ¤¿¡¢ÆÃÊ̤ʥª¥×¥·¥ç¥ó¤ò»ØÄꤷ¤Ê¤¤ + (/etc/make.conf ¤¬¶õ¤Ç¤¢¤ë¤³¤È¤¬Ë¾¤Þ¤·¤¤) + ¤Ç¹½ÃÛ¤·¤Æ¤¯¤À¤µ¤¤¡£ + + - ¤³¤Î»þÅÀ¤Ç GENERIC - ¥«¡¼¥Í¥ë¤ÇºÆµ¯Æ°¤¹¤ëɬÍפϤ¢¤ê¤Þ¤»¤ó¡£ + ¤³¤Î»þÅÀ¤Ç GENERIC + ¥«¡¼¥Í¥ë¤ÇºÆµ¯Æ°¤¹¤ëɬÍפϤ¢¤ê¤Þ¤»¤ó¡£ + - freebsd-update - ¤Ë¤è¤ë¥á¥¸¥ã¡¼¡¢¤Þ¤¿¤Ï¥Þ¥¤¥Ê¡¼¥Ð¡¼¥¸¥ç¥ó¤Î¥¢¥Ã¥×¥Ç¡¼¥È¤Ç¤Ï¡¢ - ¥ê¥ê¡¼¥¹¥Ð¡¼¥¸¥ç¥ó¤ò¥¿¡¼¥²¥Ã¥È¤Ë¤·¤Æ¼Â¹Ô¤·¤Þ¤¹¡£ - ¤¿¤È¤¨¤Ð¡¢&os; 8.1 - ¤Ë¥¢¥Ã¥×¥Ç¡¼¥È¤¹¤ë¤Ë¤Ï°Ê²¼¤Î¥³¥Þ¥ó¥É¤ò¼Â¹Ô¤·¤Æ¤¯¤À¤µ¤¤¡£ - - &prompt.root; freebsd-update -r 8.1-RELEASE upgrade - - ¥³¥Þ¥ó¥É¤ò¼Â¹Ô¤¹¤ë¤È¡¢freebsd-update - ¤ÏÀßÄê¥Õ¥¡¥¤¥ë¤È¸½ºß¤Î¥·¥¹¥Æ¥à¤òɾ²Á¤·¡¢ - ¥·¥¹¥Æ¥à¤ò¥¢¥Ã¥×¥Ç¡¼¥È¤¹¤ë¤¿¤á¤ËɬÍפʾðÊó¤ò¼ý½¸¤·¤Þ¤¹¡£ - ²èÌ̤ˤϡ¢¤É¤Î¥³¥ó¥Ý¡¼¥Í¥ó¥È¤¬Ç§¼±¤µ¤ì¡¢ - ¤É¤Î¥³¥ó¥Ý¡¼¥Í¥ó¥È¤¬Ç§¼±¤µ¤ì¤Æ¤¤¤Ê¤¤¤«¤È¤¤¤Ã¤¿¥ê¥¹¥È¤¬É½¼¨¤µ¤ì¤Þ¤¹¡£ - ¤¿¤È¤¨¤Ð°Ê²¼¤Î¤è¤¦¤Ëɽ¼¨¤µ¤ì¤Þ¤¹¡£ + + &os; 9.X °Ê¹ß¤Î¥·¥¹¥Æ¥à¤Ë¤ª¤±¤ë¥«¥¹¥¿¥à¥«¡¼¥Í¥ë + + + + ¤¿¤À°ìÅÙ¤À¤±¥«¥¹¥¿¥à¥«¡¼¥Í¥ë¤ò¹½ÃÛ¤·¤¿¤Î¤Ç¤¢¤ì¤Ð¡¢ + /boot/kernel.old + ¤Ï GENERIC ¥«¡¼¥Í¥ë¤½¤Î¤â¤Î¤Ç¤¹¡£ + ¤¿¤Àñ¤Ë¤³¤Î¥Ç¥£¥ì¥¯¥È¥ê¤Î̾Á°¤ò + /boot/kernel + ¤Ø¤ÈÊѹ¹¤·¤Æ¤¯¤À¤µ¤¤¡£ + + + + ¥³¥ó¥Ô¥å¡¼¥¿¤Ø¤ÎʪÍýŪ¤Ê¥¢¥¯¥»¥¹¤¬²Äǽ¤Ç¤¢¤ì¤Ð¡¢ + CD-ROM ¥á¥Ç¥£¥¢¤«¤é GENERIC + ¥«¡¼¥Í¥ë¤ò¥¤¥ó¥¹¥È¡¼¥ë¤Ç¤­¤Þ¤¹¡£ + ¥¤¥ó¥¹¥È¡¼¥ë¥Ç¥£¥¹¥¯¤òÁÞÆþ¤·¤Æ¡¢°Ê²¼¤Î¥³¥Þ¥ó¥É¤ò¼Â¹Ô¤·¤Æ¤¯¤À¤µ¤¤¡£ + + &prompt.root; mount /cdrom +&prompt.root; cd /cdrom/usr/freebsd-dist +&prompt.root; tar -C/ -xvf kernel.txz boot/kernel/kernel + + + + ¾åµ­¤ÎÊýË¡¤¬¼ºÇÔ¤¹¤ë¤Î¤Ç¤¢¤ì¤Ð¡¢ + GENERIC ¥«¡¼¥Í¥ë¤ò¥½¡¼¥¹¤«¤éºÆ¹½ÃÛ¤·¤Æ¡¢ + ¥¤¥ó¥¹¥È¡¼¥ë¤·¤Æ¤¯¤À¤µ¤¤¡£ + + &prompt.root; cd /usr/src +&prompt.root; make kernel + + freebsd-update ¤Ï¡¢¤³¤Î¥«¡¼¥Í¥ë¤ò + GENERIC ¥«¡¼¥Í¥ë¤È¤·¤Æ°·¤¤¤Þ¤¹¡£ + GENERIC ¥³¥ó¥Õ¥£¥°¥ì¡¼¥·¥ç¥ó¥Õ¥¡¥¤¥ë¤Ï¡¢ + ¤È¤Ë¤«¤¯Êѹ¹¤·¤Æ¤Ï¤¤¤±¤Þ¤»¤ó¡£ + ¤Þ¤¿¡¢ÆÃÊ̤ʥª¥×¥·¥ç¥ó¤ò»ØÄꤷ¤Ê¤¤ + (/etc/make.conf ¤¬¶õ¤Ç¤¢¤ë¤³¤È¤¬Ë¾¤Þ¤·¤¤) + ¤Ç¹½ÃÛ¤·¤Æ¤¯¤À¤µ¤¤¡£ + + + + ¤³¤Î»þÅÀ¤Ç GENERIC + ¥«¡¼¥Í¥ë¤ÇºÆµ¯Æ°¤¹¤ëɬÍפϤ¢¤ê¤Þ¤»¤ó¡£ + + + + + ¥¢¥Ã¥×¥°¥ì¡¼¥É¤ò¹Ô¤¦ + + freebsd-update + ¤Ë¤è¤ë¥á¥¸¥ã¡¼¡¢¤Þ¤¿¤Ï¥Þ¥¤¥Ê¡¼¥Ð¡¼¥¸¥ç¥ó¤Î¥¢¥Ã¥×¥Ç¡¼¥È¤Ç¤Ï¡¢ + ¥ê¥ê¡¼¥¹¥Ð¡¼¥¸¥ç¥ó¤ò¥¿¡¼¥²¥Ã¥È¤Ë¤·¤Æ¼Â¹Ô¤·¤Þ¤¹¡£ + ¤¿¤È¤¨¤Ð¡¢&os; 8.1 + ¤Ë¥¢¥Ã¥×¥Ç¡¼¥È¤¹¤ë¤Ë¤Ï°Ê²¼¤Î¥³¥Þ¥ó¥É¤ò¼Â¹Ô¤·¤Æ¤¯¤À¤µ¤¤¡£ + + &prompt.root; freebsd-update -r 8.1-RELEASE upgrade + + ¥³¥Þ¥ó¥É¤ò¼Â¹Ô¤¹¤ë¤È¡¢freebsd-update + ¤ÏÀßÄê¥Õ¥¡¥¤¥ë¤È¸½ºß¤Î¥·¥¹¥Æ¥à¤òɾ²Á¤·¡¢ + ¥·¥¹¥Æ¥à¤ò¥¢¥Ã¥×¥Ç¡¼¥È¤¹¤ë¤¿¤á¤ËɬÍפʾðÊó¤ò¼ý½¸¤·¤Þ¤¹¡£ + ²èÌ̤ˤϡ¢¤É¤Î¥³¥ó¥Ý¡¼¥Í¥ó¥È¤¬Ç§¼±¤µ¤ì¡¢ + ¤É¤Î¥³¥ó¥Ý¡¼¥Í¥ó¥È¤¬Ç§¼±¤µ¤ì¤Æ¤¤¤Ê¤¤¤«¤È¤¤¤Ã¤¿¥ê¥¹¥È¤¬É½¼¨¤µ¤ì¤Þ¤¹¡£ + ¤¿¤È¤¨¤Ð°Ê²¼¤Î¤è¤¦¤Ëɽ¼¨¤µ¤ì¤Þ¤¹¡£ - Looking up update.FreeBSD.org mirrors... 1 mirrors found. + Looking up update.FreeBSD.org mirrors... 1 mirrors found. Fetching metadata signature for 8.0-RELEASE from update1.FreeBSD.org... done. Fetching metadata index... done. Inspecting system... done. @@ -457,116 +527,125 @@ world/proflibs Does this look reasonable (y/n)? y - ¤³¤³¤Ç¡¢freebsd-update - ¤Ï¥¢¥Ã¥×¥°¥ì¡¼¥É¤ËɬÍפʤ¹¤Ù¤Æ¤Î¥Õ¥¡¥¤¥ë¤ò¥À¥¦¥ó¥í¡¼¥É¤·¤Þ¤¹¡£ - ²¿¤ò¥¤¥ó¥¹¥È¡¼¥ë¤·¡¢¤É¤Î¤è¤¦¤Ë¿Ê¤à¤«¤È¤¤¤Ã¤¿¼ÁÌä¤ò¤µ¤ì¤ë¤³¤È¤â¤¢¤ê¤Þ¤¹¡£ + ¤³¤³¤Ç¡¢freebsd-update + ¤Ï¥¢¥Ã¥×¥°¥ì¡¼¥É¤ËɬÍפʤ¹¤Ù¤Æ¤Î¥Õ¥¡¥¤¥ë¤ò¥À¥¦¥ó¥í¡¼¥É¤·¤Þ¤¹¡£ + ²¿¤ò¥¤¥ó¥¹¥È¡¼¥ë¤·¡¢¤É¤Î¤è¤¦¤Ë¿Ê¤à¤«¤È¤¤¤Ã¤¿¼ÁÌä¤ò¤µ¤ì¤ë¤³¤È¤â¤¢¤ê¤Þ¤¹¡£ - ¥«¥¹¥¿¥à¥«¡¼¥Í¥ë¤ò»È¤Ã¤Æ¤¤¤ë¤È¡¢ - ¾åµ­¤Î¥¹¥Æ¥Ã¥×¤Ç°Ê²¼¤Î¤è¤¦¤Ê·Ù¹ð¤¬É½¼¨¤µ¤ì¤Þ¤¹¡£ + ¥«¥¹¥¿¥à¥«¡¼¥Í¥ë¤ò»È¤Ã¤Æ¤¤¤ë¤È¡¢ + ¾åµ­¤Î¥¹¥Æ¥Ã¥×¤Ç°Ê²¼¤Î¤è¤¦¤Ê·Ù¹ð¤¬É½¼¨¤µ¤ì¤Þ¤¹¡£ - WARNING: This system is running a "MYKERNEL" kernel, which is not a + WARNING: This system is running a "MYKERNEL" kernel, which is not a kernel configuration distributed as part of FreeBSD 8.0-RELEASE. This kernel will not be updated: you MUST update the kernel manually before running "/usr/sbin/freebsd-update install" - ¤³¤Î»þÅÀ¤Ç¤Ï¤³¤Î·Ù¹ð¤ò̵»ë¤·¤Æ¤â¤«¤Þ¤¤¤Þ¤»¤ó¡£ - ¥¢¥Ã¥×¥Ç¡¼¥È¤µ¤ì¤¿ GENERIC ¥«¡¼¥Í¥ë¤Ï¡¢ - ¥¢¥Ã¥×¥°¥ì¡¼¥É¥×¥í¥»¥¹¤ÎÅÓÃæ¤ÇÍøÍѤµ¤ì¤Þ¤¹¡£ - - ¤¹¤Ù¤Æ¤Î¥Ñ¥Ã¥Á¤¬¥í¡¼¥«¥ë¥·¥¹¥Æ¥à¤Ø¥À¥¦¥ó¥í¡¼¥É¤µ¤ì¤¿¤é¡¢ - ¼¡¤Ë¥Ñ¥Ã¥Á¤¬Å¬ÍѤµ¤ì¤Þ¤¹¡£ - ¤³¤Î¥×¥í¥»¥¹¤Ë¤«¤«¤ë»þ´Ö¤Ï¥³¥ó¥Ô¥å¡¼¥¿¤ÎÀ­Ç½¤È¥ï¡¼¥¯¥í¡¼¥É¤Ë°Í¸¤·¤Þ¤¹¡£ - ¤½¤Î¸å¡¢ÀßÄê¥Õ¥¡¥¤¥ë¤¬¥Þ¡¼¥¸¤µ¤ì¤Þ¤¹¡£ - ¤³¤Î¥×¥í¥»¥¹¤Ç¤Ï¡¢¥Õ¥¡¥¤¥ë¤ò¥Þ¡¼¥¸¤¹¤ë¤«¡¢ - ²èÌ̾å¤Ë¥¨¥Ç¥£¥¿¤òΩ¤Á¾å¤²¤Æ¼êÆ°¤Ç¥Þ¡¼¥¸¤¹¤ë¤«¤ò¿Ò¤Í¤é¤ì¤Þ¤¹¡£ - ¥×¥í¥»¥¹¤´¤È¤Ë¡¢¥Þ¡¼¥¸¤ËÀ®¸ù¤·¤¿¾ðÊ󤬥桼¥¶¤Ë¼¨¤µ¤ì¤Þ¤¹¡£ - ¥Þ¡¼¥¸¤Ë¼ºÇÔ¤·¤¿¤ê¡¢Ìµ»ë¤·¤¿¾ì¹ç¤Ë¤Ï¡¢¥×¥í¥»¥¹¤¬ÃæÃǤ·¤Þ¤¹¡£ - /etc ¤Î¥Ð¥Ã¥¯¥¢¥Ã¥×¤ò¼è¤ê¡¢ - master.passwd ¤ä group - ¤Î¤è¤¦¤Ê½ÅÍפʥե¡¥¤¥ë¤ò¸å¤Ç¼êÆ°¤Ç¥Þ¡¼¥¸¤¹¤ë¥æ¡¼¥¶¤â¤¤¤ë¤Ç¤·¤ç¤¦¡£ + ¤³¤Î»þÅÀ¤Ç¤Ï¤³¤Î·Ù¹ð¤ò̵»ë¤·¤Æ¤â¤«¤Þ¤¤¤Þ¤»¤ó¡£ + ¥¢¥Ã¥×¥Ç¡¼¥È¤µ¤ì¤¿ GENERIC ¥«¡¼¥Í¥ë¤Ï¡¢ + ¥¢¥Ã¥×¥°¥ì¡¼¥É¥×¥í¥»¥¹¤ÎÅÓÃæ¤ÇÍøÍѤµ¤ì¤Þ¤¹¡£ + + ¤¹¤Ù¤Æ¤Î¥Ñ¥Ã¥Á¤¬¥í¡¼¥«¥ë¥·¥¹¥Æ¥à¤Ø¥À¥¦¥ó¥í¡¼¥É¤µ¤ì¤¿¤é¡¢ + ¼¡¤Ë¥Ñ¥Ã¥Á¤¬Å¬ÍѤµ¤ì¤Þ¤¹¡£ + ¤³¤Î¥×¥í¥»¥¹¤Ë¤«¤«¤ë»þ´Ö¤Ï¥³¥ó¥Ô¥å¡¼¥¿¤ÎÀ­Ç½¤È¥ï¡¼¥¯¥í¡¼¥É¤Ë°Í¸¤·¤Þ¤¹¡£ + ¤½¤Î¸å¡¢ÀßÄê¥Õ¥¡¥¤¥ë¤¬¥Þ¡¼¥¸¤µ¤ì¤Þ¤¹¡£ + ¤³¤Î¥×¥í¥»¥¹¤Ç¤Ï¡¢¥Õ¥¡¥¤¥ë¤ò¥Þ¡¼¥¸¤¹¤ë¤«¡¢ + ²èÌ̾å¤Ë¥¨¥Ç¥£¥¿¤òΩ¤Á¾å¤²¤Æ¼êÆ°¤Ç¥Þ¡¼¥¸¤¹¤ë¤«¤ò¿Ò¤Í¤é¤ì¤Þ¤¹¡£ + ¥×¥í¥»¥¹¤´¤È¤Ë¡¢¥Þ¡¼¥¸¤ËÀ®¸ù¤·¤¿¾ðÊ󤬥桼¥¶¤Ë¼¨¤µ¤ì¤Þ¤¹¡£ + ¥Þ¡¼¥¸¤Ë¼ºÇÔ¤·¤¿¤ê¡¢Ìµ»ë¤·¤¿¾ì¹ç¤Ë¤Ï¡¢¥×¥í¥»¥¹¤¬ÃæÃǤ·¤Þ¤¹¡£ + ¥æ¡¼¥¶¤Ë¤è¤Ã¤Æ¤Ï /etc + ¤Î¥Ð¥Ã¥¯¥¢¥Ã¥×¤ò¼è¤ê¡¢ + master.passwd ¤ä group + ¤Î¤è¤¦¤Ê½ÅÍפʥե¡¥¤¥ë¤ò¸å¤Ç¼êÆ°¤Ç¥Þ¡¼¥¸¤¹¤ëÊý¤â¤¤¤Þ¤¹¡£ - - ¤¹¤Ù¤Æ¤Î¥Ñ¥Ã¥Á¤ÏÊ̤Υǥ£¥ì¥¯¥È¥ê¤Ç¥Þ¡¼¥¸¤µ¤ì¤Æ¤ª¤ê¡¢ - ¤Þ¤À¡¢¥·¥¹¥Æ¥à¤Ë¤ÏÈ¿±Ç¤µ¤ì¤Æ¤¤¤Þ¤»¤ó¡£ - ¥æ¡¼¥¶¤Ë¤è¤ëÊѹ¹ÅÀ¤Î¥³¥ß¥Ã¥È¤ÏɬÍפ¢¤ê¤Þ¤»¤ó¡£ - + + ¤¹¤Ù¤Æ¤Î¥Ñ¥Ã¥Á¤ÏÊ̤Υǥ£¥ì¥¯¥È¥ê¤Ç¥Þ¡¼¥¸¤µ¤ì¤Æ¤ª¤ê¡¢ + ¤Þ¤À¡¢¥·¥¹¥Æ¥à¤Ë¤ÏÈ¿±Ç¤µ¤ì¤Æ¤¤¤Þ¤»¤ó¡£ + ¤¹¤Ù¤Æ¤Î¥Ñ¥Ã¥Á¤¬Àµ¤·¤¯Å¬ÍѤµ¤ì¡¢ + ¤¹¤Ù¤Æ¤ÎÀßÄê¥Õ¥¡¥¤¥ë¤¬¥Þ¡¼¥¸¤µ¤ì¤Æ¥×¥í¥»¥¹¤¬¥¹¥à¡¼¥º¤Ë¿Ê¤ó¤Ç¤¤¤ë»þ¤Ë¤Ï¡¢ + ¥æ¡¼¥¶¤Ë¤è¤ëÊѹ¹ÅÀ¤Î¥³¥ß¥Ã¥È¤ÏɬÍפ¢¤ê¤Þ¤»¤ó¡£ + - ¤³¤Î¥×¥í¥»¥¹¤¬½ª¤ï¤Ã¤¿¤é¡¢ - °Ê²¼¤Î¥³¥Þ¥ó¥É¤òÍѤ¤¤Æ¡¢¥¢¥Ã¥×¥°¥ì¡¼¥É¤ò¥Ç¥£¥¹¥¯¤ËÈ¿±Ç¤·¤Æ¤¯¤À¤µ¤¤¡£ + ¤³¤Î¥×¥í¥»¥¹¤¬½ª¤ï¤Ã¤¿¤é¡¢ + °Ê²¼¤Î¥³¥Þ¥ó¥É¤òÍѤ¤¤Æ¡¢¥¢¥Ã¥×¥°¥ì¡¼¥É¤ò¥Ç¥£¥¹¥¯¤ËÈ¿±Ç¤·¤Æ¤¯¤À¤µ¤¤¡£ - &prompt.root; freebsd-update install + &prompt.root; freebsd-update install - ¥Ñ¥Ã¥Á¤ÏºÇ½é¤Ë¥«¡¼¥Í¥ë¤È¥«¡¼¥Í¥ë¥â¥¸¥å¡¼¥ë¤ËÂФ·¤ÆÅö¤Æ¤é¤ì¤Þ¤¹¡£ - ¤³¤³¤Ç¥³¥ó¥Ô¥å¡¼¥¿¤òºÆµ¯Æ°¤¹¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£ - ¥·¥¹¥Æ¥à¤¬¥«¥¹¥¿¥à¥«¡¼¥Í¥ë¤ò¼Â¹Ô¤·¤Æ¤¤¤¿¾ì¹ç¤Ë¤Ï¡¢ - &man.nextboot.8; ¥³¥Þ¥ó¥É¤ò»È¤Ã¤Æ¼¡²ó¤ÎºÆµ¯Æ°»þ¤Î¥«¡¼¥Í¥ë¤ò - (¥¢¥Ã¥×¥Ç¡¼¥È¤µ¤ì¤¿) ¥Ñ¥Ã¥Á¤ÏºÇ½é¤Ë¥«¡¼¥Í¥ë¤È¥«¡¼¥Í¥ë¥â¥¸¥å¡¼¥ë¤ËÂФ·¤ÆÅö¤Æ¤é¤ì¤Þ¤¹¡£ + ¤³¤³¤Ç¥³¥ó¥Ô¥å¡¼¥¿¤òºÆµ¯Æ°¤¹¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£ + ¥·¥¹¥Æ¥à¤¬¥«¥¹¥¿¥à¥«¡¼¥Í¥ë¤ò¼Â¹Ô¤·¤Æ¤¤¤ë¾ì¹ç¤Ë¤Ï¡¢ + &man.nextboot.8; ¥³¥Þ¥ó¥É¤ò»È¤Ã¤Æ¼¡²ó¤ÎºÆµ¯Æ°»þ¤Î¥«¡¼¥Í¥ë¤ò + (¥¢¥Ã¥×¥Ç¡¼¥È¤µ¤ì¤¿) /boot/GENERIC ¤ËÊѹ¹¤·¤Æ¤¯¤À¤µ¤¤¡£ - &prompt.root; nextboot -k GENERIC + &prompt.root; nextboot -k GENERIC - - GENERIC ¥«¡¼¥Í¥ë¤ÇºÆµ¯Æ°¤¹¤ëÁ°¤Ë¡¢ - ¥·¥¹¥Æ¥à¤¬Å¬Àڤ˵¯Æ°¤¹¤ë¤¿¤á¤ËɬÍ×¤Ê - (¤â¤·¥³¥ó¥Ô¥å¡¼¥¿¤Ë¥ê¥â¡¼¥È¤Ç¥¢¥¯¥»¥¹¤·¤Æ¥¢¥Ã¥×¥Ç¡¼¥È¤·¤Æ¤¤¤¿¤Î¤Ç¤¢¤ì¤Ð¡¢ - ¥Í¥Ã¥È¥ï¡¼¥¯Àܳ¤ËɬÍפÊ) - ¤¹¤Ù¤Æ¤Î¥É¥é¥¤¥Ð¤¬´Þ¤Þ¤ì¤Æ¤¤¤ë¤³¤È¤ò³Îǧ¤·¤Æ¤¯¤À¤µ¤¤¡£ - Æäˡ¢¤³¤ì¤Þ¤Ç¤Ë¼Â¹Ô¤·¤Æ¤¤¤¿¥«¥¹¥¿¥à¥«¡¼¥Í¥ë¤¬ - (Ä̾ï¤Ï¥«¡¼¥Í¥ë¥â¥¸¥å¡¼¥ë¤È¤·¤ÆÄ󶡤µ¤ì¤Æ¤¤¤ë) - ¥Ó¥ë¥ÉºÑ¤ß¤Îµ¡Ç½¤ò´Þ¤ó¤Ç¤¤¤ë¤Î¤Ç¤¢¤ì¤Ð¡¢ - ¤³¤ì¤é¤Î¥â¥¸¥å¡¼¥ë¤ò°ì»þŪ¤Ë /boot/loader.conf - ¤Îµ¡Ç½¤òÍѤ¤¤Æ¡¢ - GENERIC ¤Ø¤ÈÆɤ߹þ¤ó¤Ç¤¯¤À¤µ¤¤¡£ - ¥¢¥Ã¥×¥°¥ì¡¼¥É¥×¥í¥»¥¹¤¬½ª¤ï¤ë¤Þ¤Ç¤Ï¡¢ - ½ÅÍפǤϤʤ¤¥µ¡¼¥Ó¥¹¤ò̵¸ú¤Ë¤·¡¢ - ¥Ç¥£¥¹¥¯¤ä¥Í¥Ã¥È¥ï¡¼¥¯¤Î¥Þ¥¦¥ó¥È¤Ê¤É¤ÏÈò¤±¤Æ¤¯¤À¤µ¤¤¡£ - + + GENERIC ¥«¡¼¥Í¥ë¤ÇºÆµ¯Æ°¤¹¤ëÁ°¤Ë¡¢ + ¥·¥¹¥Æ¥à¤¬Å¬Àڤ˵¯Æ°¤¹¤ë¤¿¤á¤ËɬÍ×¤Ê + (¤â¤·¥³¥ó¥Ô¥å¡¼¥¿¤Ë¥ê¥â¡¼¥È¤Ç¥¢¥¯¥»¥¹¤·¤Æ¥¢¥Ã¥×¥Ç¡¼¥È¤·¤Æ¤¤¤¿¤Î¤Ç¤¢¤ì¤Ð¡¢ + ¥Í¥Ã¥È¥ï¡¼¥¯Àܳ¤ËɬÍפÊ) + ¤¹¤Ù¤Æ¤Î¥É¥é¥¤¥Ð¤¬´Þ¤Þ¤ì¤Æ¤¤¤ë¤³¤È¤ò³Îǧ¤·¤Æ¤¯¤À¤µ¤¤¡£ + Æäˡ¢¤³¤ì¤Þ¤Ç¤Ë¼Â¹Ô¤·¤Æ¤¤¤¿¥«¥¹¥¿¥à¥«¡¼¥Í¥ë¤¬ + (Ä̾ï¤Ï¥«¡¼¥Í¥ë¥â¥¸¥å¡¼¥ë¤È¤·¤ÆÄ󶡤µ¤ì¤Æ¤¤¤ë) + ¥Ó¥ë¥ÉºÑ¤ß¤Îµ¡Ç½¤ò´Þ¤ó¤Ç¤¤¤ë¤Î¤Ç¤¢¤ì¤Ð¡¢ + ¤³¤ì¤é¤Î¥â¥¸¥å¡¼¥ë¤ò°ì»þŪ¤Ë /boot/loader.conf + ¤Îµ¡Ç½¤òÍѤ¤¤Æ¡¢ + GENERIC ¤Ø¤ÈÆɤ߹þ¤ó¤Ç¤¯¤À¤µ¤¤¡£ + ¥¢¥Ã¥×¥°¥ì¡¼¥É¥×¥í¥»¥¹¤¬½ª¤ï¤ë¤Þ¤Ç¤Ï¡¢ + ½ÅÍפǤϤʤ¤¥µ¡¼¥Ó¥¹¤ò̵¸ú¤Ë¤·¡¢ + ¥Ç¥£¥¹¥¯¤ä¥Í¥Ã¥È¥ï¡¼¥¯¤Î¥Þ¥¦¥ó¥È¤Ê¤É¤ÏÈò¤±¤Æ¤¯¤À¤µ¤¤¡£ + + + ¥¢¥Ã¥×¥Ç¡¼¥È¤µ¤ì¤¿¥«¡¼¥Í¥ë¤Ç¥³¥ó¥Ô¥å¡¼¥¿¤òºÆµ¯Æ°¤·¤Æ¤¯¤À¤µ¤¤¡£ + + &prompt.root; shutdown -r now + + ¥·¥¹¥Æ¥à¤¬¥ª¥ó¥é¥¤¥ó¤ËÌá¤Ã¤¿¤é¡¢ + freebsd-update ¤òºÆ¤Ó¼Â¹Ô¤¹¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£ + ¥¢¥Ã¥×¥Ç¡¼¥È¥×¥í¥»¥¹¤Î¾õÂÖ¤ÏÊݸ¤µ¤ì¤Æ¤¤¤ë¤Î¤Ç¡¢ + freebsd-update ¤ò¼Â¹Ô¤¹¤ë¤È¡¢ºÇ½é¤«¤é¤Ç¤Ï¤Ê¤¯¡¢ + ¸Å¤¤¶¦Í­¥é¥¤¥Ö¥é¥ê¤È¥ª¥Ö¥¸¥§¥¯¥È¥Õ¥¡¥¤¥ë¤òºï½ü¤¹¤ë¥×¥í¥»¥¹¤«¤é»Ï¤Þ¤ê¤Þ¤¹¡£ + ¤³¤Î¥¹¥Æ¡¼¥¸¤ò³¹Ô¤¹¤ë¤Ë¤Ï¡¢°Ê²¼¤Î¥³¥Þ¥ó¥É¤ò¼Â¹Ô¤·¤Æ¤¯¤À¤µ¤¤¡£ - ¥¢¥Ã¥×¥Ç¡¼¥È¤µ¤ì¤¿¥«¡¼¥Í¥ë¤Ç¥³¥ó¥Ô¥å¡¼¥¿¤òºÆµ¯Æ°¤·¤Æ¤¯¤À¤µ¤¤¡£ - - &prompt.root; shutdown -r now + &prompt.root; freebsd-update install - ¥·¥¹¥Æ¥à¤¬¥ª¥ó¥é¥¤¥ó¤ËÌá¤Ã¤¿¤é¡¢ - freebsd-update ¤òºÆ¤Ó¼Â¹Ô¤¹¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£ - ¥¢¥Ã¥×¥Ç¡¼¥È¥×¥í¥»¥¹¤Î¾õÂÖ¤ÏÊݸ¤µ¤ì¤Æ¤¤¤ë¤Î¤Ç¡¢ - freebsd-update ¤ò¼Â¹Ô¤¹¤ë¤È¡¢ºÇ½é¤«¤é¤Ç¤Ï¤Ê¤¯¡¢ - ¸Å¤¤¶¦Í­¥é¥¤¥Ö¥é¥ê¤È¥ª¥Ö¥¸¥§¥¯¥È¥Õ¥¡¥¤¥ë¤òºï½ü¤¹¤ë¥×¥í¥»¥¹¤«¤é»Ï¤Þ¤ê¤Þ¤¹¡£ - ¤³¤Î¥¹¥Æ¡¼¥¸¤ò³¹Ô¤¹¤ë¤Ë¤Ï¡¢°Ê²¼¤Î¥³¥Þ¥ó¥É¤ò¼Â¹Ô¤·¤Æ¤¯¤À¤µ¤¤¡£ - - &prompt.root; freebsd-update install + + »ÈÍѤ·¤Æ¤¤¤ë¥é¥¤¥Ö¥é¥ê¤Î¥Ð¡¼¥¸¥ç¥óÈÖ¹æ¤ÎÉÕ¤±¤é¤ìÊý¤Ë¤è¤Ã¤Æ¡¢ + 3 ¤Ä¤Î¥¤¥ó¥¹¥È¡¼¥ë¥Õ¥§¡¼¥º¤¬ 2 ¤Ä¤Ë¤Ê¤ë¾ì¹ç¤â¤¢¤ê¤Þ¤¹¡£ + + - - »ÈÍѤ·¤Æ¤¤¤ë¥é¥¤¥Ö¥é¥ê¤Î¥Ð¡¼¥¸¥ç¥óÈÖ¹æ¤ÎÉÕ¤±¤é¤ìÊý¤Ë¤è¤Ã¤Æ¡¢ - 3 ¤Ä¤Î¥¤¥ó¥¹¥È¡¼¥ë¥Õ¥§¡¼¥º¤¬ 2 ¤Ä¤Ë¤Ê¤ë¾ì¹ç¤â¤¢¤ê¤Þ¤¹¡£ - + + ¥á¥¸¥ã¡¼¥Ð¡¼¥¸¥ç¥ó¥¢¥Ã¥×¥°¥ì¡¼¥É¸å¤Î ports ¤ÎºÆ¹½ÃÛ - ¤¹¤Ù¤Æ¤Î¥µ¡¼¥É¥Ñ¡¼¥Æ¥£À½¤Î¥½¥Õ¥È¥¦¥§¥¢¤òºÆ¹½ÃÛ¤·¡¢ - ºÆ¥¤¥ó¥¹¥È¡¼¥ë¤¹¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£ - ¤³¤Îºî¶È¤¬É¬ÍפʤΤϡ¢¥¤¥ó¥¹¥È¡¼¥ë¤µ¤ì¤Æ¤¤¤ë¥½¥Õ¥È¥¦¥§¥¢¤¬¡¢ - ¥¢¥Ã¥×¥°¥ì¡¼¥É¤ÎºÝ¤Ëºï½ü¤µ¤ì¤¿¥é¥¤¥Ö¥é¥ê¤Ë°Í¸¤·¤Æ¤¤¤ë²ÄǽÀ­¤¬¤¢¤ë¤¿¤á¤Ç¤¹¡£ - ports-mgmt/portupgrade - ¥³¥Þ¥ó¥É¤Ï¡¢¤³¤Î¥×¥í¥»¥¹¤ò¼«Æ°²½¤·¤Þ¤¹¡£ - °Ê²¼¤Î¥³¥Þ¥ó¥É¤Ç¡¢¤³¤Î¥×¥í¥»¥¹¤ò³«»Ï¤·¤Þ¤¹¡£ + ¥á¥¸¥ã¡¼¥Ð¡¼¥¸¥ç¥ó¥¢¥Ã¥×¥°¥ì¡¼¥É¤ò¹Ô¤Ã¤¿¸å¤Ç¤Ï¡¢ + ¤¹¤Ù¤Æ¤Î¥µ¡¼¥É¥Ñ¡¼¥Æ¥£À½¤Î¥½¥Õ¥È¥¦¥§¥¢¤òºÆ¹½ÃÛ¤·¡¢ + ºÆ¥¤¥ó¥¹¥È¡¼¥ë¤¹¤ëɬÍפ¬¤¢¤ê¤Þ¤¹¡£ + ¤³¤Îºî¶È¤¬É¬ÍפʤΤϡ¢¥¤¥ó¥¹¥È¡¼¥ë¤µ¤ì¤Æ¤¤¤ë¥½¥Õ¥È¥¦¥§¥¢¤¬¡¢ + ¥¢¥Ã¥×¥°¥ì¡¼¥É¤ÎºÝ¤Ëºï½ü¤µ¤ì¤¿¥é¥¤¥Ö¥é¥ê¤Ë°Í¸¤·¤Æ¤¤¤ë²ÄǽÀ­¤¬¤¢¤ë¤¿¤á¤Ç¤¹¡£ + ports-mgmt/portupgrade + ¥³¥Þ¥ó¥É¤Ï¡¢¤³¤Î¥×¥í¥»¥¹¤ò¼«Æ°²½¤·¤Þ¤¹¡£ + °Ê²¼¤Î¥³¥Þ¥ó¥É¤Ç¡¢¤³¤Î¥×¥í¥»¥¹¤ò³«»Ï¤·¤Þ¤¹¡£ - &prompt.root; portupgrade -f ruby + &prompt.root; portupgrade -f ruby &prompt.root; rm /var/db/pkg/pkgdb.db &prompt.root; portupgrade -f ruby18-bdb &prompt.root; rm /var/db/pkg/pkgdb.db /usr/ports/INDEX-*.db &prompt.root; portupgrade -af - ¤³¤Îºî¶È¤Î½ªÎ»¸å¡¢ºÇ¸å¤Ë¤â¤¦°ìÅÙ - freebsd-update - ¤ò¼Â¹Ô¤¹¤ë¤È¡¢¥¢¥Ã¥×¥°¥ì¡¼¥É¤Î¥×¥í¥»¥¹¤¬´°Î»¤·¤Þ¤¹¡£ - °Ê²¼¤Î¥³¥Þ¥ó¥É¤Ç¤¹¤Ù¤Æ¤Î¥¢¥Ã¥×¥°¥ì¡¼¥É¥×¥í¥»¥¹¤Î¤ä¤ê»Ä¤·ºî¶È¤¬¹Ô¤ï¤ì¤Þ¤¹¡£ + ¤³¤Îºî¶È¤Î½ªÎ»¸å¡¢ºÇ¸å¤Ë¤â¤¦°ìÅÙ + freebsd-update + ¤ò¼Â¹Ô¤¹¤ë¤È¡¢¥¢¥Ã¥×¥°¥ì¡¼¥É¤Î¥×¥í¥»¥¹¤¬´°Î»¤·¤Þ¤¹¡£ + °Ê²¼¤Î¥³¥Þ¥ó¥É¤Ç¤¹¤Ù¤Æ¤Î¥¢¥Ã¥×¥°¥ì¡¼¥É¥×¥í¥»¥¹¤Î¤ä¤ê»Ä¤·ºî¶È¤¬¹Ô¤ï¤ì¤Þ¤¹¡£ - &prompt.root; freebsd-update install + &prompt.root; freebsd-update install - GENERIC - ¥«¡¼¥Í¥ë¤ò°ì»þŪ¤ËÆɤ߹þ¤ó¤Ç¤¤¤¿¤Î¤Ç¤¢¤ì¤Ð¡¢ - ¤³¤³¤Ç¡¢Ä̾ï¤ÎÊýË¡¤òÍѤ¤¤Æ¿·¤·¤¤¥«¥¹¥¿¥à¤ò¹½ÃÛ¤·¡¢¥¤¥ó¥¹¥È¡¼¥ë¤·¤Æ¤¯¤À¤µ¤¤¡£ + GENERIC + ¥«¡¼¥Í¥ë¤ò°ì»þŪ¤ËÆɤ߹þ¤ó¤Ç¤¤¤¿¤Î¤Ç¤¢¤ì¤Ð¡¢ + ¤³¤³¤Ç¡¢Ä̾ï¤ÎÊýË¡¤òÍѤ¤¤Æ¿·¤·¤¤¥«¥¹¥¿¥à¤ò¹½ÃÛ¤·¡¢¥¤¥ó¥¹¥È¡¼¥ë¤·¤Æ¤¯¤À¤µ¤¤¡£ - ¥³¥ó¥Ô¥å¡¼¥¿¤òºÆµ¯Æ°¤·¡¢¿·¤·¤¤ &os; ¤òΩ¤Á¾å¤²¤Æ¤¯¤À¤µ¤¤¡£ - ¤³¤ì¤Ç¥¢¥Ã¥×¥°¥ì¡¼¥É¤Î¥×¥í¥»¥¹¤Ï´°Î»¤Ç¤¹¡£ + ¥³¥ó¥Ô¥å¡¼¥¿¤òºÆµ¯Æ°¤·¡¢¿·¤·¤¤ &os; ¤òΩ¤Á¾å¤²¤Æ¤¯¤À¤µ¤¤¡£ + ¤³¤ì¤Ç¥¢¥Ã¥×¥°¥ì¡¼¥É¤Î¥×¥í¥»¥¹¤Ï´°Î»¤Ç¤¹¡£ + From owner-svn-doc-all@FreeBSD.ORG Wed Jan 23 18:58:23 2013 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 7E62BB19; Wed, 23 Jan 2013 18:58:23 +0000 (UTC) (envelope-from gkeramidas@gmail.com) Received: from mail-wi0-f172.google.com (mail-wi0-f172.google.com [209.85.212.172]) by mx1.freebsd.org (Postfix) with ESMTP id 94F6484A; Wed, 23 Jan 2013 18:58:22 +0000 (UTC) Received: by mail-wi0-f172.google.com with SMTP id o1so1017703wic.17 for ; Wed, 23 Jan 2013 10:58:21 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:sender:date:from:to:cc:subject:message-id:references :mime-version:content-type:content-disposition:in-reply-to; bh=1HMoxs9wqxDNHFOTdIXP8iUpkFyEo5Yz9iits02qO8I=; b=tMzeNSWD3leWmdeWgvsdmLBVZGXo5OgPJIixtbX8UU7/4SPuWLXldW5UFRHO5REP8I oaAUaIS5y6kmDF9IQLnR9Mz3BnR7wXLpN9IHaio8DIuBtILhINUf1NZIyvDv0IykOYep u7hXbsde1ZXmGJm4q05y6+YGUWm6sNj8YQRyXgMAC5CbNPf9iRTmm/5mpUVZTPFzif6F 6ComxAqeW8jPqGYobSnL6VV1gqD9JqX09qfBPCzjmniFnZAgWJV/BdRDEHCxARRlhEl0 MqZxdqzkMRn5U90PZCj6Sv0PKPMK5zfrfig4nFQEiizuMNcDssZwypVibOwRm7zB/6Ft wAwg== X-Received: by 10.194.71.244 with SMTP id y20mr4555668wju.19.1358967501318; Wed, 23 Jan 2013 10:58:21 -0800 (PST) Received: from saturn (217-162-217-29.dynamic.hispeed.ch. [217.162.217.29]) by mx.google.com with ESMTPS id h19sm28091946wiv.7.2013.01.23.10.58.19 (version=TLSv1.2 cipher=RC4-SHA bits=128/128); Wed, 23 Jan 2013 10:58:20 -0800 (PST) Sender: Giorgos Keramidas Date: Wed, 23 Jan 2013 19:58:17 +0100 From: Giorgos Keramidas To: Glen Barber Subject: Re: svn commit: r40716 - svnadmin/conf Message-ID: <20130123185816.GB23949@saturn> References: <201301220239.r0M2dtix060531@svn.freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <201301220239.r0M2dtix060531@svn.freebsd.org> Cc: svn-doc-all@freebsd.org, doc-committers@freebsd.org, svn-doc-svnadmin@freebsd.org X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Jan 2013 18:58:23 -0000 On 2013-01-22 02:39, Glen Barber wrote: > Author: gjb > Date: Tue Jan 22 02:39:55 2013 > New Revision: 40716 > URL: http://svnweb.freebsd.org/changeset/doc/40716 > > Log: > Please welcome Dru Lavigne (dru@) to the ranks of doc/ committers. > bcr will be dru's mentor, with hrs as co-mentor and gjb as tertiary > mentor. > > Approved by: doceng (implicit) That has been long overdue :-) Congratulations to Dru, and to doc-team for convincing her that FreeBSD doc+www is a nice place to be! From owner-svn-doc-all@FreeBSD.ORG Wed Jan 23 19:00:37 2013 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id A5BA6C20; Wed, 23 Jan 2013 19:00:37 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from onyx.glenbarber.us (onyx.glenbarber.us [IPv6:2607:fc50:1000:c200::face]) by mx1.freebsd.org (Postfix) with ESMTP id 6DB3786A; Wed, 23 Jan 2013 19:00:37 +0000 (UTC) Received: from glenbarber.us (75-146-225-65-Philadelphia.hfc.comcastbusiness.net [75.146.225.65]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: gjb) by onyx.glenbarber.us (Postfix) with ESMTPSA id AC91223F763; Wed, 23 Jan 2013 14:00:31 -0500 (EST) DKIM-Filter: OpenDKIM Filter v2.7.4 onyx.glenbarber.us AC91223F763 Authentication-Results: onyx.glenbarber.us; dkim=none reason="no signature"; dkim-adsp=none (insecure policy) Date: Wed, 23 Jan 2013 14:00:29 -0500 From: Glen Barber To: Giorgos Keramidas Subject: Re: svn commit: r40716 - svnadmin/conf Message-ID: <20130123190029.GB1307@glenbarber.us> References: <201301220239.r0M2dtix060531@svn.freebsd.org> <20130123185816.GB23949@saturn> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="l76fUT7nc3MelDdI" Content-Disposition: inline In-Reply-To: <20130123185816.GB23949@saturn> X-Operating-System: FreeBSD 10.0-CURRENT amd64 User-Agent: Mutt/1.5.21 (2010-09-15) Cc: svn-doc-all@freebsd.org, doc-committers@freebsd.org, svn-doc-svnadmin@freebsd.org X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 23 Jan 2013 19:00:37 -0000 --l76fUT7nc3MelDdI Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Jan 23, 2013 at 07:58:17PM +0100, Giorgos Keramidas wrote: > On 2013-01-22 02:39, Glen Barber wrote: > > Author: gjb > > Date: Tue Jan 22 02:39:55 2013 > > New Revision: 40716 > > URL: http://svnweb.freebsd.org/changeset/doc/40716 > >=20 > > Log: > > Please welcome Dru Lavigne (dru@) to the ranks of doc/ committers. > > bcr will be dru's mentor, with hrs as co-mentor and gjb as tertiary > > mentor. > > =20 > > Approved by: doceng (implicit) >=20 > That has been long overdue :-) >=20 > Congratulations to Dru, and to doc-team for convincing her that FreeBSD > doc+www is a nice place to be! Indeed. :-) Glen --l76fUT7nc3MelDdI Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iQEcBAEBCAAGBQJRADNNAAoJEFJPDDeguUajFd4H/2AfnCyOIBB6Qe/9/Zs1FiWh Nh8bnWeSPpWTkq5SZR2R4BEkHYFt2zGMMrAguYy4o4QPhinueWdqKbUFRtmUwfd/ TvfbcZJaAx12BUcB2KrBSIpBAURaI5eeaV5QXxlGvGikyPnMc2gUB1a9iUr7iAsq VRvv+c+9QYR/F+c8n+gtbcVCovdLyGRZVtxUoPKiQdwROewgGX5LZBVPYT2F/Mj9 hxRTLF6GcIrQS9mHCeb0hPuTgWVrPv3a3y0kDSOUjyzw8IcytTcLJABQhmAkIGV0 UC0flu/3Q5OeOPgzRVthIjN8VzJp5K6RKv9/41ypa8yT287obZ8CNw8B9GsoeBY= =mUC/ -----END PGP SIGNATURE----- --l76fUT7nc3MelDdI-- From owner-svn-doc-all@FreeBSD.ORG Thu Jan 24 10:39:47 2013 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 96323415; Thu, 24 Jan 2013 10:39:47 +0000 (UTC) (envelope-from ryusuke@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id 7CB53D62; Thu, 24 Jan 2013 10:39:47 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.5/8.14.5) with ESMTP id r0OAdlLm096224; Thu, 24 Jan 2013 10:39:47 GMT (envelope-from ryusuke@svn.freebsd.org) Received: (from ryusuke@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r0OAdkEv096217; Thu, 24 Jan 2013 10:39:46 GMT (envelope-from ryusuke@svn.freebsd.org) Message-Id: <201301241039.r0OAdkEv096217@svn.freebsd.org> From: Ryusuke SUZUKI Date: Thu, 24 Jan 2013 10:39:46 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40731 - in head/ja_JP.eucJP: books/handbook/bsdinstall books/handbook/eresources share/xml X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Jan 2013 10:39:47 -0000 Author: ryusuke Date: Thu Jan 24 10:39:46 2013 New Revision: 40731 URL: http://svnweb.freebsd.org/changeset/doc/40731 Log: - Merge the following from the English version: r40628 -> r40690 head/ja_JP.eucJP/share/xml/mailing-lists.ent r40526 -> r40684 head/ja_JP.eucJP/books/handbook/bsdinstall/chapter.xml r40672 -> r40690 head/ja_JP.eucJP/books/handbook/eresources/chapter.xml Modified: head/ja_JP.eucJP/books/handbook/bsdinstall/chapter.xml head/ja_JP.eucJP/books/handbook/eresources/chapter.xml head/ja_JP.eucJP/share/xml/mailing-lists.ent Modified: head/ja_JP.eucJP/books/handbook/bsdinstall/chapter.xml ============================================================================== --- head/ja_JP.eucJP/books/handbook/bsdinstall/chapter.xml Wed Jan 23 13:13:16 2013 (r40730) +++ head/ja_JP.eucJP/books/handbook/bsdinstall/chapter.xml Thu Jan 24 10:39:46 2013 (r40731) @@ -3,7 +3,7 @@ The FreeBSD Documentation Project The FreeBSD Japanese Documentation Project - Original revision: r40526 + Original revision: r40684 $FreeBSD$ --> @@ -752,7 +752,7 @@ Ethernet address 0:3:ba:b:92:d4, Host ID - ok + ok ok {0} Modified: head/ja_JP.eucJP/books/handbook/eresources/chapter.xml ============================================================================== --- head/ja_JP.eucJP/books/handbook/eresources/chapter.xml Wed Jan 23 13:13:16 2013 (r40730) +++ head/ja_JP.eucJP/books/handbook/eresources/chapter.xml Thu Jan 24 10:39:46 2013 (r40731) @@ -1169,6 +1169,20 @@ + &a.ops-announce.name; + + + ¥×¥í¥¸¥§¥¯¥È¤Î¥¤¥ó¥Õ¥é¥¹¥È¥é¥¯¥Á¥ã¤Ë´Ø¤¹¤ë¥¢¥Ê¥¦¥ó¥¹ + + FreeBSD.org + ¥×¥í¥¸¥§¥¯¥È¤Î¥¤¥ó¥Õ¥é¥¹¥È¥é¥¯¥Á¥ã¤ÎÊѹ¹¤ä´ØÏ¢¤·¤¿ÌäÂê¤Ë¤Ä¤¤¤Æ¶½Ì£¤ò»ý¤Ã¤Æ¤¤¤ë¸þ¤±¤Î¥á¡¼¥ê¥ó¥°¥ê¥¹¥È¤Ç¤¹¡£ + + ¤³¤Î¥á¡¼¥ê¥ó¥°¥ê¥¹¥È¤Ï¡¢¥¢¥Ê¥¦¥ó¥¹¤ËÀ©¸Â¤µ¤ì¤Æ¤¤¤Þ¤¹ + (ÊÖÅú¤äÍ׵ᡢµÄÏÀ¡¢°Õ¸«¤ò½Ò¤Ù¤ë¾ì¤Ç¤Ï¤¢¤ê¤Þ¤»¤ó)¡£ + + + + &a.performance.name; Modified: head/ja_JP.eucJP/share/xml/mailing-lists.ent ============================================================================== --- head/ja_JP.eucJP/share/xml/mailing-lists.ent Wed Jan 23 13:13:16 2013 (r40730) +++ head/ja_JP.eucJP/share/xml/mailing-lists.ent Thu Jan 24 10:39:46 2013 (r40731) @@ -2,7 +2,7 @@ The FreeBSD Documentation Project The FreeBSD Japanese Documentation Project - Original revision: r40628 + Original revision: r40690 $FreeBSD$ --> @@ -320,6 +320,10 @@ FreeBSD ¤Ç¤Î¥ª¥Õ¥£¥¹¥¢¥×¥ê¥±¡¼¥·¥ç¥ó"> freebsd-office"> + +¥×¥í¥¸¥§¥¯¥È¤Î¥¤¥ó¥Õ¥é¥¹¥È¥é¥¯¥Á¥ã¤Ë´Ø¤¹¤ë¥¢¥Ê¥¦¥ó¥¹"> +freebsd-ops-announce"> + FreeBSD performance ¥á¡¼¥ê¥ó¥°¥ê¥¹¥È"> freebsd-performance"> From owner-svn-doc-all@FreeBSD.ORG Thu Jan 24 14:28:06 2013 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 87670C25; Thu, 24 Jan 2013 14:28:06 +0000 (UTC) (envelope-from dru@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id 6B3BDAA5; Thu, 24 Jan 2013 14:28:06 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.5/8.14.5) with ESMTP id r0OES6aF065629; Thu, 24 Jan 2013 14:28:06 GMT (envelope-from dru@svn.freebsd.org) Received: (from dru@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r0OES60F065628; Thu, 24 Jan 2013 14:28:06 GMT (envelope-from dru@svn.freebsd.org) Message-Id: <201301241428.r0OES60F065628@svn.freebsd.org> From: Dru Lavigne Date: Thu, 24 Jan 2013 14:28:06 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40732 - head/en_US.ISO8859-1/books/handbook/firewalls X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Jan 2013 14:28:06 -0000 Author: dru Date: Thu Jan 24 14:28:05 2013 New Revision: 40732 URL: http://svnweb.freebsd.org/changeset/doc/40732 Log: Minor content fix which addresses incorrect usage of it's, Let's, and most redundant word errors. Approved by: bcr (mentor) Modified: head/en_US.ISO8859-1/books/handbook/firewalls/chapter.xml Modified: head/en_US.ISO8859-1/books/handbook/firewalls/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/handbook/firewalls/chapter.xml Thu Jan 24 10:39:46 2013 (r40731) +++ head/en_US.ISO8859-1/books/handbook/firewalls/chapter.xml Thu Jan 24 14:28:05 2013 (r40732) @@ -720,7 +720,7 @@ ipnat_rules="/etc/ipnat.rules" # rule as a result of applying the user coded rules against packets going in and out of the firewall since it was last started, or since the last time the accumulators were reset to zero - by the ipf -Z command. + using ipf -Z. See the &man.ipfstat.8; manual page for details. @@ -776,8 +776,8 @@ ipnat_rules="/etc/ipnat.rules" # rule 354727 block out on dc0 from any to any 430918 pass out quick on dc0 proto tcp/udp from any to any keep state - One of the most important functions of the - ipfstat command is the + One of the most important functions of + ipfstat is the flag which displays the state table in a way similar to the way &man.top.1; shows the &os; running process table. When your firewall is under attack, this function gives you the @@ -813,7 +813,7 @@ ipnat_rules="/etc/ipnat.rules" # rule automatically rotate system logs. That is why outputting the log information to &man.syslogd.8; is better than the default of outputting to a regular file. In the default - rc.conf file, the + rc.conf, the ipmon_flags statement uses the flags: @@ -866,8 +866,8 @@ LOG_ERR - packets which have been logged &prompt.root; touch /var/log/ipfilter.log The &man.syslogd.8; function is controlled by definition - statements in the /etc/syslog.conf file. - The syslog.conf file offers considerable + statements in /etc/syslog.conf. + This file offers considerable flexibility in how syslog will deal with system messages issued by software applications like IPF. @@ -915,7 +915,7 @@ LOG_ERR - packets which have been logged - The group and rule number of the rule, e.g. + The group and rule number of the rule, e.g., @0:17. @@ -1053,7 +1053,7 @@ EOF Disable IPFILTER in system startup scripts by adding ipfilter_enable="NO" (this is default - value) into /etc/rc.conf file. + value) to /etc/rc.conf. Add a script like the following to your Any time there are logged messages on a rule with - the log first option, an - ipfstat -hio command should be executed + the log first option, + ipfstat -hio should be executed to evaluate how many times the rule has actually matched. Large number of matches usually indicate that the system is being flooded (i.e.: under attack). @@ -1710,7 +1710,7 @@ block in log first quick on dc0 proto tc block in log first quick on dc0 proto tcp/udp from any to any port = 81 # Allow traffic in from ISP's DHCP server. This rule must contain -# the IP address of your ISP's DHCP server as it's the only +# the IP address of your ISP's DHCP server as it is the only # authorized source to send this packet type. Only necessary for # cable or DSL configurations. This rule is not needed for # 'user ppp' type connection to the public Internet. @@ -1772,7 +1772,7 @@ block in log first quick on dc0 all dynamic IP address is used to identify your system to the public Internet. - Now lets say you have five PCs at home and each one needs + Say you have five PCs at home and each one needs Internet access. You would have to pay your ISP for an individual Internet account for each PC and have five phone lines. @@ -1847,16 +1847,16 @@ block in log first quick on dc0 all ipnat - NAT rules are loaded by using the - ipnat command. Typically the + NAT rules are loaded by using + ipnat. Typically the NAT rules are stored in /etc/ipnat.rules. See &man.ipnat.8; for details. When changing the NAT rules after NAT has been started, make your changes to - the file containing the NAT rules, then run the - ipnat command with the + the file containing the NAT rules, then run + ipnat with the flags to delete the internal in use NAT rules and flush the contents of the translation table of all active entries. @@ -2304,8 +2304,8 @@ net.inet.ip.fw.verbose_limit=5firewall_enable="YES" To select one of the default firewall types provided by - &os;, select one by reading the - /etc/rc.firewall file and place it in + &os;, select one by reading + /etc/rc.firewall and place it in the following: firewall_type="open" @@ -2388,8 +2388,7 @@ ipfw add deny out linkend="firewalls-ipfw-enable"/>). There is no rc.conf variable to set log limitations, but it can be set via sysctl variable, manually - or from the /etc/sysctl.conf - file: + or from /etc/sysctl.conf: net.inet.ip.fw.verbose_limit=5 @@ -2610,8 +2609,7 @@ ipfw add deny out cases, a value of zero removes the logging limit. Once the limit is reached, logging can be re-enabled by clearing the logging counter or the packet counter for - that rule, see the ipfw reset log - command. + that rule, use ipfw reset log. Logging is done after @@ -2779,7 +2777,7 @@ ipfw add deny out down attackers. Even with the logging facility enabled, IPFW will not - generate any rule logging on it's own. The firewall + generate any rule logging on its own. The firewall administrator decides what rules in the ruleset will be logged, and adds the log verb to those rules. Normally only deny rules are logged, like the deny @@ -2816,9 +2814,8 @@ ipfw add deny out last message repeated 45 times All logged packets messages are written by default to - /var/log/security file, which is - defined in the /etc/syslog.conf - file. + /var/log/security, which is + defined in /etc/syslog.conf. @@ -2864,8 +2861,8 @@ ks="keep-state" # just too lazy t in this example, how the symbolic substitution field are populated and used are. - If the above example was in the - /etc/ipfw.rules file, the rules could + If the above example was in + /etc/ipfw.rules, the rules could be reloaded by entering the following on the command line. @@ -3223,7 +3220,7 @@ natd_flags="-dynamic -m" # -m skipto rule 500 for the network address translation. - Lets say a LAN user uses their web browser to get a web + Say a LAN user uses their web browser to get a web page. Web pages are transmitted over port 80. So the packet enters the firewall. It does not match rule 100 because it is headed out rather than in. It passes rule @@ -3231,7 +3228,7 @@ natd_flags="-dynamic -m" # -m posted to the keep-state dynamic table yet. The packet finally comes to rule 125 a matches. It is outbound through the NIC facing the public Internet. The packet still has - it's source IP address as a private LAN IP address. On + its source IP address as a private LAN IP address. On the match to this rule, two actions take place. The keep-state option will post this rule into the keep-state dynamic rules table and the specified @@ -3254,14 +3251,14 @@ natd_flags="-dynamic -m" # -m entry is found, the associated action, skipto 500, is executed. The packet jumps to rule 500 gets NATed and released - on it's way out. + on its way out. On the inbound side, everything coming in that is part of an existing session conversation is being automatically handled by the check-state rule and the properly placed divert natd rules. All we have to address is denying all the bad packets and only - allowing in the authorized services. Lets say there is an + allowing in the authorized services. Say there is an apache server running on the firewall box and we want people on the public Internet to be able to access the local web site. The new inbound start request packet matches rule @@ -3454,7 +3451,7 @@ pif="rl0" # public interface name of $cmd 332 deny tcp from any to any established in via $pif # Allow traffic in from ISP's DHCP server. This rule must contain -# the IP address of your ISP's DHCP server as it's the only +# the IP address of your ISP's DHCP server as it is the only # authorized source to send this packet type. # Only necessary for cable or DSL configurations. # This rule is not needed for 'user ppp' type connection to From owner-svn-doc-all@FreeBSD.ORG Thu Jan 24 14:33:34 2013 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 88182FA; Thu, 24 Jan 2013 14:33:34 +0000 (UTC) (envelope-from ryusuke@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id 15796AF1; Thu, 24 Jan 2013 14:33:34 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.5/8.14.5) with ESMTP id r0OEXXEG068088; Thu, 24 Jan 2013 14:33:33 GMT (envelope-from ryusuke@svn.freebsd.org) Received: (from ryusuke@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r0OEXXTh068087; Thu, 24 Jan 2013 14:33:33 GMT (envelope-from ryusuke@svn.freebsd.org) Message-Id: <201301241433.r0OEXXTh068087@svn.freebsd.org> From: Ryusuke SUZUKI Date: Thu, 24 Jan 2013 14:33:33 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40733 - head/ja_JP.eucJP/htdocs/doc X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Jan 2013 14:33:34 -0000 Author: ryusuke Date: Thu Jan 24 14:33:33 2013 New Revision: 40733 URL: http://svnweb.freebsd.org/changeset/doc/40733 Log: - Merge the following from the English version: r28250 -> r40713 head/ja_JP.eucJP/htdocs/doc/Makefile Modified: head/ja_JP.eucJP/htdocs/doc/Makefile Modified: head/ja_JP.eucJP/htdocs/doc/Makefile ============================================================================== --- head/ja_JP.eucJP/htdocs/doc/Makefile Thu Jan 24 14:28:05 2013 (r40732) +++ head/ja_JP.eucJP/htdocs/doc/Makefile Thu Jan 24 14:33:33 2013 (r40733) @@ -1,14 +1,10 @@ # # $FreeBSD$ -# Original revision: 1.9 +# Original revision: r40713 # -# Build the FreeBSD documentation *outside* of the www tree, and install it +# Build the FreeBSD documentation *outside* of the doc/ tree, and install it # in to the right place as necessary. # -# This assumes that you have the www/ and doc/ trees checked out beside -# one another -- this was always the case anyway, so there are no extra -# requirements here. -# .if exists(../Makefile.conf) .include "../Makefile.conf" From owner-svn-doc-all@FreeBSD.ORG Thu Jan 24 14:57:43 2013 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 1C8EDDE0; Thu, 24 Jan 2013 14:57:43 +0000 (UTC) (envelope-from dru@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id 025CFD34; Thu, 24 Jan 2013 14:57:43 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.5/8.14.5) with ESMTP id r0OEvgd8074490; Thu, 24 Jan 2013 14:57:42 GMT (envelope-from dru@svn.freebsd.org) Received: (from dru@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r0OEvgjp074489; Thu, 24 Jan 2013 14:57:42 GMT (envelope-from dru@svn.freebsd.org) Message-Id: <201301241457.r0OEvgjp074489@svn.freebsd.org> From: Dru Lavigne Date: Thu, 24 Jan 2013 14:57:42 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40734 - head/en_US.ISO8859-1/books/handbook/l10n X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Jan 2013 14:57:43 -0000 Author: dru Date: Thu Jan 24 14:57:42 2013 New Revision: 40734 URL: http://svnweb.freebsd.org/changeset/doc/40734 Log: White space only fix. Translators can ignore. Approved by: gjb (mentor) Modified: head/en_US.ISO8859-1/books/handbook/l10n/chapter.xml Modified: head/en_US.ISO8859-1/books/handbook/l10n/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/handbook/l10n/chapter.xml Thu Jan 24 14:33:33 2013 (r40733) +++ head/en_US.ISO8859-1/books/handbook/l10n/chapter.xml Thu Jan 24 14:57:42 2013 (r40734) @@ -33,29 +33,29 @@ contributors located all over the world. This chapter discusses the internationalization and localization features of FreeBSD that allow non-English speaking users to get real work done. - There are many aspects of the i18n implementation in both the system - and application levels, so where applicable we refer the reader - to more specific sources of documentation. + There are many aspects of the i18n implementation in both the + system and application levels, so where applicable we refer + the reader to more specific sources of documentation. After reading this chapter, you will know: How different languages and locales are encoded - on modern operating systems. + on modern operating systems. How to set the locale for your login - shell. + shell. How to configure your console for non-English - languages. - How to use X Window System effectively with different - languages. + languages. + How to use X Window System effectively with + different languages. Where to find more information about writing - i18n-compliant applications. - + i18n-compliant applications. + Before reading this chapter, you should: Know how to install additional third-party - applications (). + applications (). @@ -64,48 +64,51 @@ What Is I18N/L10N? - - internationalization - localization - - localization - Developers shortened internationalization into the term I18N, - counting the number of letters between the first and the last - letters of internationalization. L10N uses the same naming - scheme, coming from localization. Combined - together, I18N/L10N methods, protocols, and applications allow - users to use languages of their choice. + + internationalization + localization + + localization + + Developers shortened internationalization into the term + I18N, counting the number of letters between the first and + the last letters of internationalization. L10N uses the + same naming scheme, coming from localization. + Combined together, I18N/L10N methods, protocols, and + applications allow users to use languages of their + choice. I18N applications are programmed using I18N kits under - libraries. It allows for developers to write a simple file and - translate displayed menus and texts to each language. We strongly - encourage programmers to follow this convention. + libraries. It allows for developers to write a simple file + and translate displayed menus and texts to each language. + We strongly encourage programmers to follow this + convention. Why Should I Use I18N/L10N? - I18N/L10N is used whenever you wish to either view, input, or - process data in non-English languages. + I18N/L10N is used whenever you wish to either view, + input, or process data in non-English languages. What Languages Are Supported in the I18N Effort? - I18N and L10N are not FreeBSD specific. Currently, one can - choose from most of the major languages of the World, including - but not limited to: Chinese, German, Japanese, Korean, French, - Russian, Vietnamese and others. + I18N and L10N are not FreeBSD specific. Currently, one + can choose from most of the major languages of the World, + including but not limited to: Chinese, German, Japanese, + Korean, French, Russian, Vietnamese and others. Using Localization - In all its splendor, I18N is not FreeBSD-specific and is a - convention. We encourage you to help FreeBSD in following this - convention. + In all its splendor, I18N is not FreeBSD-specific and is + a convention. We encourage you to help FreeBSD in following + this convention. locale Localization settings are based on three main terms: @@ -116,16 +119,18 @@ Language and Country Codes + language codes country codes - In order to localize a FreeBSD system to a specific language - (or any other I18N-supporting &unix; like systems), the user needs to find out - the codes for the specific country and language (country - codes tell applications what variation of given - language to use). In addition, web - browsers, SMTP/POP servers, web servers, etc. make decisions based on - them. The following are examples of language/country codes: + In order to localize a FreeBSD system to a specific + language (or any other I18N-supporting &unix; like systems), + the user needs to find out the codes for the specific country + and language (country codes tell applications what variation + of given language to use). In addition, web browsers, + SMTP/POP servers, web servers, etc. make decisions based on + them. The following are examples of language/country + codes: @@ -164,32 +169,36 @@ Encodings + encodings ASCII - Some languages use non-ASCII encodings that are 8-bit, wide - or multibyte characters, see &man.multibyte.3; for more - details. Older applications do not recognize them - and mistake them for control characters. Newer applications - usually do recognize 8-bit characters. Depending on the - implementation, users may be required to compile an application - with wide or multibyte characters support, or configure it correctly. - To be able to input and process wide or multibyte characters, the FreeBSD Ports Collection has provided - each language with different programs. Refer to the I18N - documentation in the respective FreeBSD Port. + Some languages use non-ASCII encodings that are 8-bit, + wide or multibyte characters, see &man.multibyte.3; for more + details. Older applications do not recognize them and mistake + them for control characters. Newer applications usually do + recognize 8-bit characters. Depending on the implementation, + users may be required to compile an application with wide or + multibyte characters support, or configure it correctly. + To be able to input and process wide or multibyte characters, + the FreeBSD Ports + Collection has provided each language with different + programs. Refer to the I18N documentation in the respective + FreeBSD Port. Specifically, the user needs to look at the application - documentation to decide on how to configure it correctly or to - pass correct values into the configure/Makefile/compiler. + documentation to decide on how to configure it correctly or + to pass correct values into the + configure/Makefile/compiler. Some things to keep in mind are: Language specific single C chars character sets - (see &man.multibyte.3;), e.g. - ISO8859-1, ISO8859-15, KOI8-R, CP437. + (see &man.multibyte.3;), e.g. ISO8859-1, ISO8859-15, + KOI8-R, CP437. @@ -199,10 +208,11 @@ You can check the active list of character sets at the IANA Registry. + url="http://www.iana.org/assignments/character-sets">IANA Registry. - &os; uses X11-compatible locale encodings instead. + &os; uses X11-compatible locale encodings + instead. @@ -211,67 +221,71 @@ I18N Applications In the FreeBSD Ports and Package system, I18N applications - have been named with I18N in their names for - easy identification. However, they do not always support the - language needed. + have been named with I18N in their names + for easy identification. However, they do not always support + the language needed. Setting Locale - Usually it is sufficient to export the value of the locale name - as LANG in the login shell. This could be done in - the user's ~/.login_conf file or in the - startup file of the user's shell (~/.profile, - ~/.bashrc, ~/.cshrc). - There is no need to set the locale subsets such as - LC_CTYPE, LC_CTIME. Please - refer to language-specific FreeBSD documentation for more - information. + Usually it is sufficient to export the value of the + locale name as LANG in the login shell. This + could be done in the user's ~/.login_conf + file or in the startup file of the user's shell + (~/.profile, + ~/.bashrc, + ~/.cshrc). There is no need to set the + locale subsets such as LC_CTYPE, + LC_CTIME. Please refer to language-specific + FreeBSD documentation for more information. - You should set the following two environment variables in your configuration - files: + You should set the following two environment variables + in your configuration files: - POSIX - - LANG for &posix; &man.setlocale.3; family - functions + POSIX + + LANG for &posix; &man.setlocale.3; + family functions MIME - MM_CHARSET for applications' MIME character - set + MM_CHARSET for applications' MIME + character set - This includes the user shell configuration, the specific application - configuration, and the X11 configuration. + This includes the user shell configuration, the specific + application configuration, and the X11 configuration. Setting Locale Methods - locale - login class + + locale + login class There are two methods for setting locale, and both are - described below. The first (recommended one) is by assigning - the environment variables in login - class, and the second is by adding the environment - variable assignments to the system's shell startup file. + described below. The first (recommended one) is by + assigning the environment variables in + login class, and the + second is by adding the environment variable assignments + to the system's shell + startup file. Login Classes Method - This method allows environment variables needed for locale - name and MIME character sets to be assigned once for every - possible shell instead of adding specific shell assignments to - each shell's startup file. User - Level Setup can be done by an user himself and Administrator Level Setup require - superuser privileges. + This method allows environment variables needed for + locale name and MIME character sets to be assigned once + for every possible shell instead of adding specific shell + assignments to each shell's startup file. + User Level Setup can be + done by an user himself and + Administrator Level Setup + require superuser privileges. User Level Setup @@ -285,12 +299,14 @@ :charset=ISO-8859-1:\ :lang=de_DE.ISO8859-1: - Traditional ChineseBIG-5 encoding + Traditional Chinese + BIG-5 encoding Here is an example of a - .login_conf that sets the variables - for Traditional Chinese in BIG-5 encoding. Notice the many - more variables set because some software does not respect - locale variables correctly for Chinese, Japanese, and Korean. + .login_conf that sets the variables + for Traditional Chinese in BIG-5 encoding. Notice the + many more variables set because some software does not + respect locale variables correctly for Chinese, + Japanese, and Korean. #Users who do not wish to use monetary units or time formats #of Taiwan can manually change each variable @@ -307,7 +323,8 @@ me:\ :xmodifiers="@im=gcin": #Set gcin as the XIM Input Server See Administrator Level - Setup and &man.login.conf.5; for more details. + Setup and &man.login.conf.5; for more + details. @@ -323,8 +340,8 @@ me:\ :lang=locale_name:\ :tc=default: - So sticking with our previous example using Latin-1, it - would look like this: + So sticking with our previous example using Latin-1, + it would look like this: german|German Users Accounts:\ :charset=ISO-8859-1:\ @@ -337,58 +354,65 @@ me:\ &prompt.root; cap_mkdb /etc/login.conf to make new configuration in - /etc/login.conf visible to the system. + /etc/login.conf visible to the + system. - Changing Login Classes with &man.vipw.8; + Changing Login Classes with + &man.vipw.8; - vipw - - Use vipw to add new users, and make - the entry look like this: + vipw + + Use vipw to add new users, and + make the entry look like this: user:password:1111:11:language:0:0:User Name:/home/user:/bin/sh - Changing Login Classes with &man.adduser.8; + Changing Login Classes with + &man.adduser.8; - adduser - + adduser + login class - Use adduser to add new users, and do - the following: + Use adduser to add new users, + and do the following: Set defaultclass = - language in - /etc/adduser.conf. Keep in mind - you must enter a default class for - all users of other languages in this case. + language in + /etc/adduser.conf. Keep in + mind you must enter a default + class for all users of other languages in this + case. - An alternative variant is answering the specified - language each time that -Enter login class: default []: + An alternative variant is answering the + specified language each time that + + Enter login class: default []: + appears from &man.adduser.8;. - Another alternative is to use the following for each - user of a different language that you wish to + Another alternative is to use the following for + each user of a different language that you wish to add: &prompt.root; adduser -class language - Changing Login Classes with &man.pw.8; + Changing Login Classes with + &man.pw.8; - pw - - If you use &man.pw.8; for adding new users, call it in - this form: + pw + + If you use &man.pw.8; for adding new users, call + it in this form: &prompt.root; pw useradd user_name -L language @@ -398,19 +422,20 @@ me:\ Shell Startup File Method - This method is not recommended because it requires a - different setup for each possible shell program chosen. Use - the Login Class Method - instead. + This method is not recommended because it requires + a different setup for each possible shell program + chosen. Use the Login Class + Method instead. MIME locale - To add the locale name and MIME character set, just set - the two environment variables shown below in the + To add the locale name and MIME character set, just + set the two environment variables shown below in the /etc/profile and/or - /etc/csh.login shell startup files. We - will use the German language as an example below: + /etc/csh.login shell startup files. + We will use the German language as an example + below: In /etc/profile: @@ -423,11 +448,11 @@ me:\ setenv MM_CHARSET ISO-8859-1 Alternatively, you can add the above instructions to - /usr/share/skel/dot.profile (similar to - what was used in /etc/profile above), or - /usr/share/skel/dot.login (similar to - what was used in /etc/csh.login - above). + /usr/share/skel/dot.profile (similar + to what was used in /etc/profile + above), or /usr/share/skel/dot.login + (similar to what was used in + /etc/csh.login above). For X11: @@ -456,33 +481,37 @@ me:\ font8x14=font_name font8x8=font_name - The font_name here is taken from - the /usr/share/syscons/fonts directory, - without the .fnt suffix. + The font_name here is taken + from the /usr/share/syscons/fonts + directory, without the .fnt + suffix. - sysinstall + sysinstall keymap screenmap If required, set the keymap and screenmap for your single C chars character set through sysinstall. - Once inside sysinstall, choose Configure, then - Console. Alternatively, you can add the - following to /etc/rc.conf: + Once inside sysinstall, choose + Configure, then + Console. Alternatively, you can + add the following to /etc/rc.conf: scrnmap=screenmap_name keymap=keymap_name keychange="fkey_number sequence" - The screenmap_name here is taken - from the /usr/share/syscons/scrnmaps - directory, without the .scm suffix. A - screenmap with a corresponding mapped font is usually needed as a - workaround for expanding bit 8 to bit 9 on a VGA adapter's font - character matrix in pseudographics area, i.e., to move letters out - of that area if screen font uses a bit 8 column. + The screenmap_name here is + taken from the + /usr/share/syscons/scrnmaps directory, + without the .scm suffix. A screenmap + with a corresponding mapped font is usually needed as a + workaround for expanding bit 8 to bit 9 on a VGA adapter's + font character matrix in pseudographics area, i.e., to move + letters out of that area if screen font uses a bit 8 + column. If you have the moused daemon enabled by setting the following @@ -494,29 +523,31 @@ keychange="fkey_number sequ paragraph. - moused + moused - By default the mouse cursor of the &man.syscons.4; driver occupies the - 0xd0-0xd3 range in the character set. If your language uses this - range, you need to move the cursor's range outside of it. To enable - the workaround for &os;, add the following line to - /etc/rc.conf: + By default the mouse cursor of the &man.syscons.4; driver + occupies the 0xd0-0xd3 range in the character set. If your + language uses this range, you need to move the cursor's range + outside of it. To enable the workaround for &os;, add the + following line to /etc/rc.conf: mousechar_start=3 - The keymap_name here is taken from - the /usr/share/syscons/keymaps directory, - without the .kbd suffix. If you are - uncertain which keymap to use, you use can &man.kbdmap.1; to test - keymaps without rebooting. - - The keychange is usually needed to program - function keys to match the selected terminal type because - function key sequences cannot be defined in the key map. - - Also be sure to set the correct console terminal type in - /etc/ttys for all ttyv* - entries. Current pre-defined correspondences are: + The keymap_name here is taken + from the /usr/share/syscons/keymaps + directory, without the .kbd suffix. If + you are uncertain which keymap to use, you use can + &man.kbdmap.1; to test keymaps without rebooting. + + The keychange is usually needed to + program function keys to match the selected terminal type + because function key sequences cannot be defined in the key + map. + + Also be sure to set the correct console terminal type + in /etc/ttys for all + ttyv* entries. Current pre-defined + correspondences are: @@ -566,13 +597,14 @@ keychange="fkey_number sequ - For wide or multibyte characters languages, use the correct - FreeBSD port in your + For wide or multibyte characters languages, use the + correct FreeBSD port in your /usr/ports/language - directory. Some ports appear as console while the system sees it - as serial vtty's, hence you must reserve enough vtty's for both - X11 and the pseudo-serial console. Here is a partial list of - applications for using other languages in console: + directory. Some ports appear as console while the system + sees it as serial vtty's, hence you must reserve enough vtty's + for both X11 and the pseudo-serial console. Here is a partial + list of applications for using other languages in + console: @@ -586,18 +618,22 @@ keychange="fkey_number sequ     Traditional Chinese (BIG-5) - chinese/big5con + chinese/big5con Japanese - japanese/kon2-16dot or - japanese/mule-freewnn + japanese/kon2-16dot or + japanese/mule-freewnn Korean - korean/han + korean/han @@ -610,30 +646,36 @@ keychange="fkey_number sequ Although X11 is not part of the FreeBSD Project, we have included some information here for FreeBSD users. For more details, refer to the &xorg; + url="http://www.x.org/">&xorg; web site or whichever X11 Server you use. - In ~/.Xresources, you can additionally - tune application specific I18N settings (e.g., fonts, menus, - etc.). + In ~/.Xresources, you can + additionally tune application specific I18N settings (e.g., + fonts, menus, etc.). Displaying Fonts - X11 True Type font server + + X11 True Type font + server Install &xorg; server - (x11-servers/xorg-server), - then install the language &truetype; fonts. Setting the correct - locale should allow you to view your selected language in menus - and such. + (x11-servers/xorg-server), + then install the language &truetype; fonts. Setting the + correct locale should allow you to view your selected + language in menus and such. Inputting Non-English Characters - X11 Input Method (XIM) - The X11 Input Method (XIM) Protocol is a new standard for - all X11 clients. All X11 applications should be written as XIM - clients that take input from XIM Input servers. There are - several XIM servers available for different languages. + + X11 Input Method + (XIM) + The X11 Input Method (XIM) Protocol is a new standard + for all X11 clients. All X11 applications should be written + as XIM clients that take input from XIM Input servers. + There are several XIM servers available for different + languages. @@ -641,44 +683,45 @@ keychange="fkey_number sequ Printer Setup Some single C chars character sets are usually hardware - coded into printers. Wide or multibyte - character sets require special setup and we recommend using - apsfilter. You may also convert the - document to &postscript; or PDF formats using language specific - converters. + coded into printers. Wide or multibyte character sets require + special setup and we recommend using + apsfilter. You may also convert + the document to &postscript; or PDF formats using language + specific converters. Kernel and File Systems - The FreeBSD fast filesystem (FFS) is 8-bit clean, so it can be used - with any single C chars character set (see &man.multibyte.3;), - but there is no character set - name stored in the filesystem; i.e., it is raw 8-bit and does not - know anything about encoding order. Officially, FFS does not - support any form of wide or multibyte character sets yet. However, some - wide or multibyte character sets have independent patches for FFS - enabling such support. They are only temporary unportable - solutions or hacks and we have decided to not include them in the - source tree. Refer to respective languages' web sites for more - information and the patch files. + The FreeBSD fast filesystem (FFS) is 8-bit clean, so it + can be used with any single C chars character set (see + &man.multibyte.3;), but there is no character set name stored + in the filesystem; i.e., it is raw 8-bit and does not know + anything about encoding order. Officially, FFS does not + support any form of wide or multibyte character sets yet. + However, some wide or multibyte character sets have + independent patches for FFS enabling such support. They are + only temporary unportable solutions or hacks and we have + decided to not include them in the source tree. Refer to + respective languages' web sites for more information and the + patch files. DOS Unicode - The FreeBSD &ms-dos; filesystem has the configurable ability to - convert between &ms-dos;, Unicode character sets and chosen - FreeBSD filesystem character sets. See &man.mount.msdosfs.8; for - details. + The FreeBSD &ms-dos; filesystem has the configurable + ability to convert between &ms-dos;, Unicode character sets + and chosen FreeBSD filesystem character sets. See + &man.mount.msdosfs.8; for details. Compiling I18N Programs - Many FreeBSD Ports have been ported with I18N support. Some - of them are marked with -I18N in the port name. These and many - other programs have built in support for I18N and need no special - consideration. + Many FreeBSD Ports have been ported with I18N support. + Some of them are marked with -I18N in the port name. These + and many other programs have built in support for I18N and + need no special consideration. MySQL @@ -705,14 +748,15 @@ keychange="fkey_number sequ Russian Language (KOI8-R Encoding) + localization Russian - For more information about KOI8-R encoding, see the KOI8-R References - (Russian Net Character Set). + For more information about KOI8-R encoding, see the + KOI8-R References + (Russian Net Character Set). Locale Setup @@ -724,8 +768,8 @@ keychange="fkey_number sequ :charset=KOI8-R:\ :lang=ru_RU.KOI8-R: - See earlier in this chapter for examples of setting up the - locale. + See earlier in this chapter for examples of setting + up the locale. @@ -758,18 +802,20 @@ font8x8="cp866-8x8" - See earlier in this chapter for examples of setting up the - console. + See earlier in this chapter for examples of setting up + the console. Printer Setup + printers Since most printers with Russian characters come with hardware code page CP866, a special output filter is needed - to convert from KOI8-R to CP866. Such a filter is installed by - default as /usr/libexec/lpr/ru/koi2alt. - A Russian printer /etc/printcap entry + to convert from KOI8-R to CP866. Such a filter is installed + by default as + /usr/libexec/lpr/ru/koi2alt. A + Russian printer /etc/printcap entry should look like: lp|Russian local line printer:\ @@ -782,16 +828,17 @@ font8x8="cp866-8x8" &ms-dos; FS and Russian Filenames - The following example &man.fstab.5; entry enables support - for Russian filenames in mounted &ms-dos; filesystems: + The following example &man.fstab.5; entry enables + support for Russian filenames in mounted &ms-dos; + filesystems: /dev/ad0s2 /dos/c msdos rw,-Wkoi2dos,-Lru_RU.KOI8-R 0 0 The option selects the locale name used, and sets the character conversion table. To use the option, be sure to - mount /usr before the &ms-dos; partition - because the conversion tables are located in + mount /usr before the &ms-dos; + partition because the conversion tables are located in /usr/libdata/msdosfs. For more information, see the &man.mount.msdosfs.8; manual page. @@ -803,30 +850,30 @@ font8x8="cp866-8x8" Do non-X locale - setup first as described. + setup first as described. If you use &xorg;, - install - x11-fonts/xorg-fonts-cyrillic - package. - - Check the "Files" section - in your /etc/X11/xorg.conf file. - The following - line must be added before any other - FontPath entries: + install x11-fonts/xorg-fonts-cyrillic + package. + + Check the "Files" section in + your /etc/X11/xorg.conf file. The + following line must be added before + any other FontPath entries: FontPath "/usr/local/lib/X11/fonts/cyrillic" - See ports for more cyrillic fonts. + See ports for more cyrillic fonts. + - To activate a Russian keyboard, add the following to the - "Keyboard" section of your + To activate a Russian keyboard, add the following + to the "Keyboard" section of your xorg.conf file: Option "XkbLayout" "us,ru" @@ -837,36 +884,38 @@ Option "XkbOptions" "grp:toggle"For grp:toggle the RUS/LAT switch will be Right Alt, - for grp:ctrl_shift_toggle switch will be - CtrlShift. - For grp:caps_toggle - the RUS/LAT switch will be CapsLock. - The old CapsLock function is still - available via ShiftCapsLock (in LAT mode - only). - grp:caps_toggle does not work in - &xorg; for unknown reason. - - If you have &windows; keys on your keyboard, - and notice that some non-alphabetical keys are mapped - incorrectly in RUS mode, add the following line in your - xorg.conf file: + for grp:ctrl_shift_toggle switch + will be CtrlShift. + For grp:caps_toggle the RUS/LAT + switch will be CapsLock. The old + CapsLock function is still available + via ShiftCapsLock + (in LAT mode only). grp:caps_toggle + does not work in &xorg; for + unknown reason. + + If you have &windows; keys on your + keyboard, and notice that some non-alphabetical keys + are mapped incorrectly in RUS mode, add the following + line in your xorg.conf file: Option "XkbVariant" ",winkeys" - The Russian XKB keyboard may not work with non-localized - applications. + The Russian XKB keyboard may not work with + non-localized applications. Minimally localized applications should call a XtSetLanguageProc (NULL, NULL, - NULL); function early in the program. - See - KOI8-R for X Window for more instructions on + NULL); function early in the program. + + See + KOI8-R for X Window for more instructions on localizing X11 applications. @@ -874,27 +923,31 @@ Option "XkbOptions" "grp:toggle" Traditional Chinese Localization for Taiwan + localization Traditional Chinese The FreeBSD-Taiwan Project has an Chinese HOWTO for - FreeBSD at - using many Chinese ports. - Current editor for the FreeBSD Chinese HOWTO is - Shen Chuan-Hsing statue@freebsd.sinica.edu.tw. - - - Chuan-Hsing Shen statue@freebsd.sinica.edu.tw has - created the - Chinese FreeBSD Collection (CFC) using FreeBSD-Taiwan's - zh-L10N-tut. The packages and the script files - are available at . + FreeBSD at + using many Chinese ports. Current editor for the + FreeBSD Chinese HOWTO is Shen Chuan-Hsing + statue@freebsd.sinica.edu.tw. + + Chuan-Hsing Shen + statue@freebsd.sinica.edu.tw has created the + + Chinese FreeBSD Collection (CFC) using + FreeBSD-Taiwan's zh-L10N-tut. The packages + and the script files are available at . German Language Localization (for All ISO 8859-1 Languages) + localization German @@ -902,8 +955,8 @@ Option "XkbOptions" "grp:toggle"Slaven Rezic eserte@cs.tu-berlin.de wrote a tutorial on using umlauts on a FreeBSD machine. The tutorial - is written in German and is available at - . + is written in German and is available at . *** DIFF OUTPUT TRUNCATED AT 1000 LINES *** From owner-svn-doc-all@FreeBSD.ORG Thu Jan 24 15:03:30 2013 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id D70C5EF2; Thu, 24 Jan 2013 15:03:30 +0000 (UTC) (envelope-from dru@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id C707CD89; Thu, 24 Jan 2013 15:03:30 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.5/8.14.5) with ESMTP id r0OF3UWA077014; Thu, 24 Jan 2013 15:03:30 GMT (envelope-from dru@svn.freebsd.org) Received: (from dru@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r0OF3U5J077013; Thu, 24 Jan 2013 15:03:30 GMT (envelope-from dru@svn.freebsd.org) Message-Id: <201301241503.r0OF3U5J077013@svn.freebsd.org> From: Dru Lavigne Date: Thu, 24 Jan 2013 15:03:30 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40735 - head/en_US.ISO8859-1/books/handbook/linuxemu X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Jan 2013 15:03:30 -0000 Author: dru Date: Thu Jan 24 15:03:30 2013 New Revision: 40735 URL: http://svnweb.freebsd.org/changeset/doc/40735 Log: White space fix only. Translators can ignore. Approved by: gjb (mentor) Modified: head/en_US.ISO8859-1/books/handbook/linuxemu/chapter.xml Modified: head/en_US.ISO8859-1/books/handbook/linuxemu/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/handbook/linuxemu/chapter.xml Thu Jan 24 14:57:42 2013 (r40734) +++ head/en_US.ISO8859-1/books/handbook/linuxemu/chapter.xml Thu Jan 24 15:03:30 2013 (r40735) @@ -32,7 +32,9 @@ Synopsis - Linux binary compatibility + + Linux binary + compatibility binary compatibility Linux @@ -41,52 +43,57 @@ FreeBSD provides binary compatibility with several other &unix; like operating systems, including Linux. At this point, you may be asking yourself why exactly, does - FreeBSD need to be able to run Linux binaries? The answer to that - question is quite simple. Many companies and developers develop - only for Linux, since it is the latest hot thing in - the computing world. That leaves the rest of us FreeBSD users - bugging these same companies and developers to put out native - FreeBSD versions of their applications. The problem is, that most - of these companies do not really realize how many people would use - their product if there were FreeBSD versions too, and most continue - to only develop for Linux. So what is a FreeBSD user to do? This - is where the Linux binary compatibility of FreeBSD comes into - play. - - In a nutshell, the compatibility allows FreeBSD users to run - about 90% of all Linux applications without modification. This - includes applications such as &staroffice;, - the Linux version of &netscape;, + FreeBSD need to be able to run Linux binaries? The answer to + that question is quite simple. Many companies and developers + develop only for Linux, since it is the latest hot + thing in the computing world. That leaves the rest + of us FreeBSD users bugging these same companies and developers + to put out native FreeBSD versions of their applications. The + problem is, that most of these companies do not really realize + how many people would use their product if there were FreeBSD + versions too, and most continue to only develop for Linux. + So what is a FreeBSD user to do? This is where the Linux binary + compatibility of FreeBSD comes into play. + + In a nutshell, the compatibility allows FreeBSD users to + run about 90% of all Linux applications without modification. + This includes applications such as + &staroffice;, the Linux version of + &netscape;, &adobe; &acrobat;, &realplayer;, &oracle;, - &wordperfect;, Doom, + &wordperfect;, + Doom, Quake, and more. It is also reported - that in some situations, Linux binaries perform better on FreeBSD - than they do under Linux. + that in some situations, Linux binaries perform better on + FreeBSD than they do under Linux. There are, however, some Linux-specific operating system - features that are not supported under FreeBSD. Linux binaries will - not work on FreeBSD if they overly use &i386; specific + features that are not supported under FreeBSD. Linux binaries + will not work on FreeBSD if they overly use &i386; specific calls, such as enabling virtual 8086 mode. After reading this chapter, you will know: - How to enable Linux binary compatibility on your system. + How to enable Linux binary compatibility on your + system. How to install additional Linux shared libraries. - + - How to install Linux applications on your FreeBSD system. + How to install Linux applications on your FreeBSD + system. - The implementation details of Linux compatibility in FreeBSD. + The implementation details of Linux compatibility in + FreeBSD. @@ -95,7 +102,7 @@ Know how to install additional third-party - software (). + software (). @@ -104,7 +111,8 @@ Installation - KLD (kernel loadable object) + KLD (kernel loadable + object) Linux binary compatibility is not turned on by default. The easiest way to enable this functionality is to load the @@ -127,19 +135,22 @@ Id Refs Address Size Name 1 2 0xc0100000 16bdb8 kernel 7 1 0xc24db000 d000 linux.ko + kernel options COMPAT_LINUX - If for some reason you do not want to or cannot load the KLD, - then you may statically link Linux binary compatibility into the kernel - by adding options COMPAT_LINUX to your kernel - configuration file. Then install your new kernel as described in + If for some reason you do not want to or cannot load the + KLD, then you may statically link Linux binary compatibility + into the kernel by adding options + COMPAT_LINUX to your kernel configuration file. + Then install your new kernel as described in . Installing Linux Runtime Libraries + Linux installing Linux libraries @@ -150,36 +161,38 @@ Id Refs Address Size Name by installing them manually. - - Installing Using the linux_base Port - Ports Collection - - This is by far the easiest method to use when installing the - runtime libraries. It is just like installing any other port - from the Ports Collection: + + Installing Using the linux_base Port - &prompt.root; cd /usr/ports/emulators/linux_base-f10 + Ports Collection + + This is by far the easiest method to use when installing + the runtime libraries. It is just like installing any other + port from the Ports + Collection: + + &prompt.root; cd /usr/ports/emulators/linux_base-f10 &prompt.root; make install distclean On &os; systems prior to &os; 8.0, you will have to use the emulators/linux_base-fc4 port + role="package">emulators/linux_base-fc4 port instead of emulators/linux_base-f10. + role="package">emulators/linux_base-f10. You should now have working Linux binary compatibility. - Some programs may complain about incorrect minor versions of the - system libraries. In general, however, this does not seem to be - a problem. + Some programs may complain about incorrect minor versions + of the system libraries. In general, however, this does + not seem to be a problem. There may be multiple versions of the emulators/linux_base port available, - corresponding to different versions of various Linux distributions. - You should install the port most closely resembling the - requirements of the Linux applications you would like to - install. + role="package">emulators/linux_base port + available, corresponding to different versions of various + Linux distributions. You should install the port most + closely resembling the requirements of the Linux + applications you would like to install. @@ -187,48 +200,52 @@ Id Refs Address Size Name Installing Libraries Manually If you do not have the ports collection - installed, you can install the libraries by hand instead. You - will need the Linux shared libraries that the program depends on - and the runtime linker. Also, you will need to create a - shadow root directory, - /compat/linux, for Linux libraries on your - FreeBSD system. Any shared libraries opened by Linux programs - run under FreeBSD will look in this tree first. So, if a Linux - program loads, for example, /lib/libc.so, - FreeBSD will first try to open - /compat/linux/lib/libc.so, and if that does - not exist, it will then try /lib/libc.so. - Shared libraries should be installed in the shadow tree + installed, you can install the libraries by hand instead. + You will need the Linux shared libraries that the program + depends on and the runtime linker. Also, you will need to + create a shadow root directory, + /compat/linux, for Linux libraries + on your FreeBSD system. Any shared libraries opened by + Linux programs run under FreeBSD will look in this tree + first. So, if a Linux program loads, for example, + /lib/libc.so, FreeBSD will first try + to open /compat/linux/lib/libc.so, + and if that does not exist, it will then try + /lib/libc.so. Shared libraries should + be installed in the shadow tree /compat/linux/lib rather than the paths that the Linux ld.so reports. - Generally, you will need to look for the shared libraries - that Linux binaries depend on only the first few times that you - install a Linux program on your FreeBSD system. After a while, - you will have a sufficient set of Linux shared libraries on your - system to be able to run newly imported Linux binaries without - any extra work. + Generally, you will need to look for the shared + libraries that Linux binaries depend on only the first few + times that you install a Linux program on your FreeBSD + system. After a while, you will have a sufficient set of + Linux shared libraries on your system to be able to run + newly imported Linux binaries without any extra work. How to Install Additional Shared Libraries + shared libraries - What if you install the linux_base port - and your application still complains about missing shared - libraries? How do you know which shared libraries Linux - binaries need, and where to get them? Basically, there are 2 - possibilities (when following these instructions you will need - to be root on your FreeBSD system). + What if you install the linux_base + port and your application still complains about missing + shared libraries? How do you know which shared libraries + Linux binaries need, and where to get them? Basically, + there are 2 possibilities (when following these instructions + you will need to be root on your + FreeBSD system). If you have access to a Linux system, see what shared - libraries the application needs, and copy them to your FreeBSD - system. Look at the following example: + libraries the application needs, and copy them to your + FreeBSD system. Look at the following example: - Let us assume you used FTP to get the Linux binary of - Doom, and put it on a Linux system you have access to. You - then can check which shared libraries it needs by running + Let us assume you used FTP to get the Linux binary + of Doom, and put it on a Linux + system you have access to. You then can check which + shared libraries it needs by running ldd linuxdoom, like so: &prompt.user; ldd linuxdoom @@ -237,10 +254,11 @@ libX11.so.3 (DLL Jump 3.1) => /usr/X1 libc.so.4 (DLL Jump 4.5pl26) => /lib/libc.so.4.6.29 symbolic links - You would need to get all the files from the last column, - and put them under /compat/linux, with - the names in the first column as symbolic links pointing to - them. This means you eventually have these files on your + You would need to get all the files from the last + column, and put them under + /compat/linux, with the names in + the first column as symbolic links pointing to them. + This means you eventually have these files on your FreeBSD system: /compat/linux/usr/X11/lib/libXt.so.3.1.0 @@ -252,15 +270,16 @@ libc.so.4 (DLL Jump 4.5pl26) => /lib/
    - Note that if you already have a Linux shared library - with a matching major revision number to the first column - of the ldd output, you will not need to - copy the file named in the last column to your system, the - one you already have should work. It is advisable to copy - the shared library anyway if it is a newer version, - though. You can remove the old one, as long as you make - the symbolic link point to the new one. So, if you have - these libraries on your system: + Note that if you already have a Linux shared + library with a matching major revision number to the + first column of the ldd output, + you will not need to copy the file named in the last + column to your system, the one you already have should + work. It is advisable to copy the shared library + anyway if it is a newer version, though. You can + remove the old one, as long as you make the symbolic + link point to the new one. So, if you have these + libraries on your system: /compat/linux/lib/libc.so.4.6.27 /compat/linux/lib/libc.so.4 -> libc.so.4.6.27 @@ -271,13 +290,13 @@ libc.so.4 (DLL Jump 4.5pl26) => /lib/ libc.so.4 (DLL Jump 4.5pl26) -> libc.so.4.6.29 - If it is only one or two versions out of date in the - trailing digit then do not worry about copying - /lib/libc.so.4.6.29 too, because the - program should work fine with the slightly older version. - However, if you like, you can decide to replace the - libc.so anyway, and that should leave - you with: + If it is only one or two versions out of date + in the trailing digit then do not worry about copying + /lib/libc.so.4.6.29 too, because + the program should work fine with the slightly older + version. However, if you like, you can decide to + replace the libc.so anyway, and + that should leave you with: /compat/linux/lib/libc.so.4.6.29 /compat/linux/lib/libc.so.4 -> libc.so.4.6.29 @@ -287,10 +306,10 @@ libc.so.4 (DLL Jump 4.5pl26) => /lib/
    The symbolic link mechanism is - only needed for Linux binaries. The - FreeBSD runtime linker takes care of looking for matching - major revision numbers itself and you do not need to worry - about it. + only needed for Linux binaries. + The FreeBSD runtime linker takes care of looking for + matching major revision numbers itself and you do not + need to worry about it.
    @@ -299,21 +318,23 @@ libc.so.4 (DLL Jump 4.5pl26) => /lib/ Installing Linux ELF Binaries + Linux ELF binaries ELF binaries sometimes require an extra step of - branding. If you attempt to run an unbranded ELF - binary, you will get an error message like the following: + branding. If you attempt to run an unbranded + ELF binary, you will get an error message like the + following: &prompt.user; ./my-linux-elf-binary ELF binary type not known Abort - To help the FreeBSD kernel distinguish between a FreeBSD ELF - binary and a Linux binary, use the &man.brandelf.1; + To help the FreeBSD kernel distinguish between a FreeBSD + ELF binary and a Linux binary, use the &man.brandelf.1; utility. &prompt.user; brandelf -t Linux my-linux-elf-binary @@ -327,19 +348,19 @@ Abort Installing a Random Linux RPM Based Application - FreeBSD has its own package database and it is used to track - all ports (&linux; ports as well). So the &linux; RPM database is not - used (not supported). + FreeBSD has its own package database and it is used to + track all ports (&linux; ports as well). So the &linux; RPM + database is not used (not supported). - However if you need to install a random &linux; RPM-based - application it can be achieved by: + However if you need to install a random &linux; + RPM-based application it can be achieved by: &prompt.root; cd /compat/linux &prompt.root; rpm2cpio -q < /path/to/linux.archive.rpm | cpio -id Then brandelf installed ELF binaries (not libraries!). - You will not be able to do a clean uninstall, but it may help you - to do tests. + You will not be able to do a clean uninstall, but it may + help you to do tests. @@ -357,14 +378,16 @@ Abort order hosts, bind multi on - The order here specifies that /etc/hosts - is searched first and DNS is searched second. When + The order here specifies that + /etc/hosts is searched first and DNS + is searched second. When /compat/linux/etc/host.conf is not installed, Linux applications find FreeBSD's /etc/host.conf and complain about the incompatible FreeBSD syntax. You should remove - bind if you have not configured a name server - using the /etc/resolv.conf file. + bind if you have not configured a name + server using the /etc/resolv.conf + file. @@ -389,7 +412,8 @@ multi on version of &mathematica; 5.X onto a FreeBSD system. - The Linux version of &mathematica; + The Linux version of + &mathematica; or &mathematica; for Students can be ordered directly from Wolfram at . @@ -433,9 +457,10 @@ multi on The shell scripts that &mathematica; created during - installation have to be modified before you can use them. If - you chose /usr/local/bin - as the directory to place the + installation have to be modified before you can use them. + If you chose /usr/local/bin as the directory + to place the &mathematica; executables in, you will find symlinks in this directory to files called math, mathematica, @@ -472,10 +497,10 @@ done &mathematica; on different machines. - When you register with Wolfram, either by email, phone or fax, - you will give them the machine ID and they will - respond with a corresponding password consisting of groups of - numbers. + When you register with Wolfram, either by email, phone + or fax, you will give them the machine ID and + they will respond with a corresponding password consisting + of groups of numbers. @@ -483,25 +508,27 @@ done &mathematica; uses some special fonts to display characters not - present in any of the standard font sets (integrals, sums, Greek - letters, etc.). The X protocol requires these fonts to be install - locally. This means you will have to copy - these fonts from the CDROM or from a host with - &mathematica; - installed to your local machine. These fonts are normally stored - in /cdrom/Unix/Files/SystemFiles/Fonts on the - CDROM, or - /usr/local/mathematica/SystemFiles/Fonts on - your hard drive. The actual fonts are in the subdirectories - Type1 and X. There are - several ways to use them, as described below. - - The first way is to copy them into one of the existing font - directories in /usr/X11R6/lib/X11/fonts. - This will require editing the fonts.dir file, - adding the font names to it, and changing the number of fonts on - the first line. Alternatively, you should also just be able to - run &man.mkfontdir.1; in the directory you have copied + present in any of the standard font sets (integrals, sums, + Greek letters, etc.). The X protocol requires these fonts + to be install locally. This means you + will have to copy these fonts from the CDROM or from a host + with &mathematica; installed to + your local machine. These fonts are normally stored in + /cdrom/Unix/Files/SystemFiles/Fonts on + the CDROM, or + /usr/local/mathematica/SystemFiles/Fonts + on your hard drive. The actual fonts are in the + subdirectories Type1 and + X. There are several ways to use them, + as described below. + + The first way is to copy them into one of the existing + font directories in + /usr/X11R6/lib/X11/fonts. This will + require editing the fonts.dir file, + adding the font names to it, and changing the number of fonts + on the first line. Alternatively, you should also just be + able to run &man.mkfontdir.1; in the directory you have copied them to. The second way to do this is to copy the directories to @@ -524,14 +551,16 @@ done &prompt.root; xset fp+ /usr/X11R6/lib/X11/fonts/MathType1 &prompt.root; xset fp rehash - If you are using the &xorg; server, you can have these font - directories loaded automatically by adding them to your + If you are using the &xorg; + server, you can have these font directories loaded + automatically by adding them to your xorg.conf file. fonts - If you do not already have a directory - called /usr/X11R6/lib/X11/fonts/Type1, you + If you do not already have a + directory called + /usr/X11R6/lib/X11/fonts/Type1, you can change the name of the MathType1 directory in the example above to Type1. @@ -564,36 +593,40 @@ done Maple - &maple; is a commercial mathematics program similar to - &mathematica;. You must purchase this software from and then register there - for a license file. To install this software on FreeBSD, please - follow these simple steps. - - - Execute the INSTALL shell - script from the product distribution. Choose the - RedHat option when prompted by the - installation program. A typical installation directory - might be &maple; is a commercial + mathematics program similar to + &mathematica;. You must purchase + this software from and then register + there for a license file. To install this software on FreeBSD, + please follow these simple steps. + + + Execute the INSTALL shell + script from the product distribution. Choose the + RedHat option when prompted by the + installation program. A typical installation directory + might be /usr/local/maple. - If you have not done so, order a license for &maple; - from Maple Waterloo Software () - and copy it to + If you have not done so, order a license for + &maple; from Maple Waterloo + Software () and copy it + to /usr/local/maple/license/license.dat. - Install the FLEXlm + Install the FLEXlm license manager by running the INSTALL_LIC install shell script that comes with &maple;. Specify the primary hostname for your machine for the license server. - Patch the - /usr/local/maple/bin/maple.system.type - file with the following: - ----- snip ------------------ + Patch the + /usr/local/maple/bin/maple.system.type + file with the following: + ----- snip ------------------ *** maple.system.type.orig Sun Jul 8 16:35:33 2001 --- maple.system.type Sun Jul 8 16:35:51 2001 *************** @@ -608,18 +641,19 @@ done # We have two Linux implementations, one for Red Hat and ----- snip end of patch ----- - Please note that after the "FreeBSD"|\ no other - whitespace should be present. - - This patch instructs &maple; to - recognize FreeBSD as a type of Linux system. - The bin/maple shell script calls the - bin/maple.system.type shell script - which in turn calls uname -a to find out the operating - system name. Depending on the OS name it will find out which - binaries to use. + Please note that after the + "FreeBSD"|\ no other whitespace should + be present. + + This patch instructs &maple; + to recognize FreeBSD as a type of Linux + system. The bin/maple shell script + calls the bin/maple.system.type shell + script which in turn calls uname -a to + find out the operating system name. Depending on the OS + name it will find out which binaries to use. - Start the license server. + Start the license server. The following script, installed as /usr/local/etc/rc.d/lmgrd.sh is a @@ -653,29 +687,34 @@ exit 0 ----- snip ------------ - Test-start &maple;: - &prompt.user; cd /usr/local/maple/bin + Test-start + &maple;: + + &prompt.user; cd /usr/local/maple/bin &prompt.user; ./xmaple - You should be up and running. Make sure to write + You should be up and running. Make sure to write Maplesoft to let them know you would like a native FreeBSD version! - + - - Common Pitfalls + + Common Pitfalls - - The FLEXlm license manager can be a difficult - tool to work with. Additional documentation on the subject - can be found at . - - lmgrd is known to be very picky - about the license file and to core dump if there are any - problems. A correct license file should look like this: + + The FLEXlm + license manager can be a difficult tool to work with. + Additional documentation on the subject can be found at + . + + lmgrd is known to be very + picky about the license file and to core dump if there + are any problems. A correct license file should look + like this: -# ======================================================= + # +======================================================= # License File for UNIX Installations ("Pointer File") # ======================================================= SERVER chillig ANY @@ -687,27 +726,27 @@ FEATURE Maple maplelmg 2000.0831 permane ISSUED=11-may-2000 NOTICE=" Technische Universitat Wien" \ SN=XXXXXXXXX - Serial number and key 'X''ed out. chillig is a - hostname. - - Editing the license file works as long as you do not - touch the FEATURE line (which is protected by the - license key). - - - + Serial number and key 'X''ed out. + chillig is a hostname. - - - - - Dan - Pelleg - Contributed by - + Editing the license file works as long as you do not + touch the FEATURE line (which is protected + by the license key). + + + + + + + + + Dan + Pelleg + Contributed by + - - + + Installing &matlab; @@ -721,11 +760,11 @@ FEATURE Maple maplelmg 2000.0831 permane &java.virtual.machine; (see ). - The Linux version of &matlab; can be - ordered directly from The MathWorks at . Make sure you also get - the license file or instructions how to create it. While you - are there, let them know you would like a native &os; + The Linux version of &matlab; + can be ordered directly from The MathWorks at . Make sure you also + get the license file or instructions how to create it. While + you are there, let them know you would like a native &os; version of their software. @@ -746,28 +785,31 @@ FEATURE Maple maplelmg 2000.0831 permane The installer is graphical. If you get errors about not being able to open a display, type - setenv HOME ~USER, - where USER is the user you did a - &man.su.1; as. + setenv HOME + ~USER, + where USER is the user you + did a &man.su.1; as. - When asked for the &matlab; root - directory, type: + When asked for the &matlab; + root directory, type: /compat/linux/usr/local/matlab. For easier typing on the rest of the installation process, type this at your shell prompt: - set MATLAB=/compat/linux/usr/local/matlab + set + MATLAB=/compat/linux/usr/local/matlab Edit the license file as instructed when - obtaining the &matlab; license. + obtaining the &matlab; + license. You can prepare this file in advance using your @@ -789,9 +831,11 @@ FEATURE Maple maplelmg 2000.0831 permane License Manager Startup + - Create symlinks for the license manager scripts: + Create symlinks for the license manager + scripts: &prompt.root; ln -s $MATLAB/etc/lmboot /usr/local/etc/lmboot_TMW &prompt.root; ln -s $MATLAB/etc/lmdown /usr/local/etc/lmdown_TMW @@ -801,9 +845,9 @@ FEATURE Maple maplelmg 2000.0831 permane Create a startup file at /usr/local/etc/rc.d/flexlm.sh. The example below is a modified version of the distributed - $MATLAB/etc/rc.lm.glnx86. The changes - are file locations, and startup of the license manager - under Linux emulation. + $MATLAB/etc/rc.lm.glnx86. The + changes are file locations, and startup of the license + manager under Linux emulation. #!/bin/sh case "$1" in @@ -861,8 +905,7 @@ exit 0 Place the following startup script in - /usr/local/bin/matlab: - + /usr/local/bin/matlab: #!/bin/sh /compat/linux/bin/sh /compat/linux/usr/local/matlab/bin/matlab "$@" @@ -876,9 +919,9 @@ exit 0 Depending on your version of - emulators/linux_base, you - may run into errors when running this script. To avoid that, - edit the file + emulators/linux_base, + you may run into errors when running this script. To avoid + that, edit the file /compat/linux/usr/local/matlab/bin/matlab, and change the line that says: @@ -915,14 +958,14 @@ exit 0 your workspace before quitting. If you use either of them, insert the line above immediately after the save command. - + - - Create a file - $MATLAB/bin/finish.sh, which will - contain the following: + + Create a file + $MATLAB/bin/finish.sh, which will + contain the following: - #!/compat/linux/bin/sh + #!/compat/linux/bin/sh (sleep 5; killall -1 matlab_helper) & exit 0 @@ -963,49 +1006,61 @@ exit 0 Preface - This document describes the process of installing &oracle; 8.0.5 and - &oracle; 8.0.5.1 Enterprise Edition for Linux onto a FreeBSD - machine. + + This document describes the process of installing + &oracle; 8.0.5 and + &oracle; 8.0.5.1 Enterprise Edition + for Linux onto a FreeBSD machine. Installing the Linux Environment - Make sure you have both emulators/linux_base and - devel/linux_devtools from the Ports Collection - installed. If you run into difficulties with these ports, - you may have to use - the packages or older versions available in the Ports Collection. + Make sure you have both emulators/linux_base and + devel/linux_devtools + from the Ports Collection installed. If you run into + difficulties with these ports, you may have to use the + packages or older versions available in the Ports + Collection. If you want to run the intelligent agent, you will also need to install the Red Hat Tcl package: - tcl-8.0.3-20.i386.rpm. The general command - for installing packages with the official RPM port (archivers/rpm) is: + tcl-8.0.3-20.i386.rpm. The general + command for installing packages with the official + RPM port (archivers/rpm) is: &prompt.root; rpm -i --ignoreos --root /compat/linux --dbpath /var/lib/rpm package - Installation of the package should not generate any errors. + Installation of the package + should not generate any errors. Creating the &oracle; Environment - Before you can install &oracle;, you need to set up a proper - environment. This document only describes what to do - specially to run &oracle; for Linux on FreeBSD, not - what has been described in the &oracle; installation guide. + Before you can install + &oracle;, you need to set up a + proper environment. This document only describes what to do + specially to run + &oracle; for Linux on FreeBSD, not + what has been described in the + &oracle; installation guide. - Kernel Tuning + Kernel Tuning + kernel tuning - As described in the &oracle; installation guide, you need to set - the maximum size of shared memory. Do not use - SHMMAX under FreeBSD. SHMMAX - is merely calculated out of SHMMAXPGS and + As described in the &oracle; + installation guide, you need to set the maximum size of + shared memory. Do not use SHMMAX under + FreeBSD. SHMMAX is merely calculated + out of SHMMAXPGS and PGSIZE. Therefore define - SHMMAXPGS. All other options can be used as - described in the guide. For example: + SHMMAXPGS. All other options can be + used as described in the guide. For example: options SHMMAXPGS=10000 options SHMMNI=100 @@ -1014,38 +1069,43 @@ options SEMMNS=200 options SEMMNI=70 options SEMMSL=61 - Set these options to suit your intended use of &oracle;. + Set these options to suit your intended use of + &oracle;. - Also, make sure you have the following options in your kernel - configuration file: + Also, make sure you have the following options in your + kernel configuration file: -options SYSVSHM #SysV shared memory + options SYSVSHM #SysV shared memory options SYSVSEM #SysV semaphores options SYSVMSG #SysV interprocess communication - &oracle; Account + &oracle; Account - Create an oracle account just as you would create any other - account. The oracle account is special only that you need to give - it a Linux shell. Add /compat/linux/bin/bash to - /etc/shells and set the shell for the oracle - account to /compat/linux/bin/bash. + Create an oracle account just as + you would create any other account. The + oracle account is special only that + you need to give it a Linux shell. Add + /compat/linux/bin/bash to + /etc/shells and set the shell for + the oracle account to + /compat/linux/bin/bash. - Environment + Environment - Besides the normal &oracle; variables, such as - ORACLE_HOME and ORACLE_SID you must - set the following environment variables: + Besides the normal &oracle; + variables, such as ORACLE_HOME and + ORACLE_SID you must set the following + environment variables: - - + +
    *** DIFF OUTPUT TRUNCATED AT 1000 LINES *** From owner-svn-doc-all@FreeBSD.ORG Thu Jan 24 17:34:56 2013 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id B3FA0D8C; Thu, 24 Jan 2013 17:34:56 +0000 (UTC) (envelope-from eadler@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id 8E0C197D; Thu, 24 Jan 2013 17:34:56 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.5/8.14.5) with ESMTP id r0OHYuX1022212; Thu, 24 Jan 2013 17:34:56 GMT (envelope-from eadler@svn.freebsd.org) Received: (from eadler@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r0OHYuJe022211; Thu, 24 Jan 2013 17:34:56 GMT (envelope-from eadler@svn.freebsd.org) Message-Id: <201301241734.r0OHYuJe022211@svn.freebsd.org> From: Eitan Adler Date: Thu, 24 Jan 2013 17:34:56 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40736 - head/en_US.ISO8859-1/books/faq X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Jan 2013 17:34:56 -0000 Author: eadler Date: Thu Jan 24 17:34:55 2013 New Revision: 40736 URL: http://svnweb.freebsd.org/changeset/doc/40736 Log: Remove install-bad-blocks: 95% bogus, user-controlled bad block mapping stopped being a thing about 20 years ago Noted by: scottl Approved by: bcr (mentor, implicit) Modified: head/en_US.ISO8859-1/books/faq/book.xml Modified: head/en_US.ISO8859-1/books/faq/book.xml ============================================================================== --- head/en_US.ISO8859-1/books/faq/book.xml Thu Jan 24 15:03:30 2013 (r40735) +++ head/en_US.ISO8859-1/books/faq/book.xml Thu Jan 24 17:34:55 2013 (r40736) @@ -1382,41 +1382,6 @@ - - Can I install on a disk with bad blocks? - - - - You can, but it is a bad idea. - - If you are seeing bad block errors with a modern IDE - drive, chances are the drive is going to die very soon (the - drive's internal remapping functions are no longer - sufficient to fix the bad blocks, which means the disk is - heavily corrupted); we suggest you buy a new hard - drive. - - - - - - Strange things happen when I boot the install disk! - What is happening? - - - - If you are seeing things like the machine grinding to a - halt or spontaneously rebooting when you try to boot the - &os; installer, make sure that the SHA256 hash of - the image matches the one on the website. If you - accidently downloaded the disk image in binary (or - image) mode the will be corrupted. (Do not be embarrassed, - even the best of us have accidentally downloaded a binary - file in ASCII mode at least once!) - - - - I booted from my ATAPI CD-ROM, but the install program says no CD-ROM is found. Where did it go? From owner-svn-doc-all@FreeBSD.ORG Thu Jan 24 17:45:27 2013 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 2C63FC2; Thu, 24 Jan 2013 17:45:27 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id 1F346A00; Thu, 24 Jan 2013 17:45:27 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.5/8.14.5) with ESMTP id r0OHjRXo025151; Thu, 24 Jan 2013 17:45:27 GMT (envelope-from gjb@svn.freebsd.org) Received: (from gjb@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r0OHjQhq025150; Thu, 24 Jan 2013 17:45:26 GMT (envelope-from gjb@svn.freebsd.org) Message-Id: <201301241745.r0OHjQhq025150@svn.freebsd.org> From: Glen Barber Date: Thu, 24 Jan 2013 17:45:26 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-svnadmin@freebsd.org Subject: svn commit: r40737 - svnadmin/conf X-SVN-Group: doc-svnadmin MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Jan 2013 17:45:27 -0000 Author: gjb Date: Thu Jan 24 17:45:26 2013 New Revision: 40737 URL: http://svnweb.freebsd.org/changeset/doc/40737 Log: Per his request, assign mentors to keramida while he becomes familiar with the recent changes to the doc infrastructure. remko and gjb (myself) to mentor. Welcome back, keramida! Approved by: doceng (implicit) Modified: svnadmin/conf/mentors Modified: svnadmin/conf/mentors ============================================================================== --- svnadmin/conf/mentors Thu Jan 24 17:34:55 2013 (r40736) +++ svnadmin/conf/mentors Thu Jan 24 17:45:26 2013 (r40737) @@ -17,5 +17,6 @@ eadler bcr backup mentor: jkois ebrandi gabor gavin bcr co-mentor: jkois, since 2011-07-18 issyl0 gabor backup mentor: gjb +keramida gjb co-mentor: remko rene remko co-mentor: gjb zeising joel From owner-svn-doc-all@FreeBSD.ORG Thu Jan 24 18:07:39 2013 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id B61DB748; Thu, 24 Jan 2013 18:07:39 +0000 (UTC) (envelope-from eadler@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id A893CAFB; Thu, 24 Jan 2013 18:07:39 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.5/8.14.5) with ESMTP id r0OI7ddv031565; Thu, 24 Jan 2013 18:07:39 GMT (envelope-from eadler@svn.freebsd.org) Received: (from eadler@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r0OI7deo031564; Thu, 24 Jan 2013 18:07:39 GMT (envelope-from eadler@svn.freebsd.org) Message-Id: <201301241807.r0OI7deo031564@svn.freebsd.org> From: Eitan Adler Date: Thu, 24 Jan 2013 18:07:39 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40738 - head/en_US.ISO8859-1/books/faq X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Jan 2013 18:07:39 -0000 Author: eadler Date: Thu Jan 24 18:07:39 2013 New Revision: 40738 URL: http://svnweb.freebsd.org/changeset/doc/40738 Log: Remove multiport-serial-share-irq: "likely isn't relevant since everybody uses PCI/PCIe serial cards" Noted by: imp Approved by: bcr (mentor, implicit) Modified: head/en_US.ISO8859-1/books/faq/book.xml Modified: head/en_US.ISO8859-1/books/faq/book.xml ============================================================================== --- head/en_US.ISO8859-1/books/faq/book.xml Thu Jan 24 17:45:26 2013 (r40737) +++ head/en_US.ISO8859-1/books/faq/book.xml Thu Jan 24 18:07:39 2013 (r40738) @@ -7725,18 +7725,6 @@ hint.sio.7.irq="12" - - Can &os; handle multiport serial cards sharing - IRQs? - - - - Not yet. You will have to use a different IRQ for each - card. - - - - Can I set the default serial parameters for a port? From owner-svn-doc-all@FreeBSD.ORG Thu Jan 24 19:52:31 2013 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id BF0C2BF3; Thu, 24 Jan 2013 19:52:31 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from bigwig.baldwin.cx (bigknife-pt.tunnel.tserv9.chi1.ipv6.he.net [IPv6:2001:470:1f10:75::2]) by mx1.freebsd.org (Postfix) with ESMTP id 8F6B0133; Thu, 24 Jan 2013 19:52:31 +0000 (UTC) Received: from pakbsde14.localnet (unknown [38.105.238.108]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 92654B91A; Thu, 24 Jan 2013 14:52:30 -0500 (EST) From: John Baldwin To: Eitan Adler Subject: Re: svn commit: r40167 - head/en_US.ISO8859-1/books/arch-handbook/driverbasics Date: Thu, 24 Jan 2013 10:14:14 -0500 User-Agent: KMail/1.13.5 (FreeBSD/8.2-CBSD-20110714-p22; KDE/4.5.5; amd64; ; ) References: <201211271530.qARFUekl097033@svn.freebsd.org> In-Reply-To: <201211271530.qARFUekl097033@svn.freebsd.org> MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: 7bit Message-Id: <201301241014.14854.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Thu, 24 Jan 2013 14:52:30 -0500 (EST) Cc: svn-doc-head@freebsd.org, svn-doc-all@freebsd.org, doc-committers@freebsd.org X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Jan 2013 19:52:31 -0000 On Tuesday, November 27, 2012 10:30:40 am Eitan Adler wrote: > Author: eadler > Date: Tue Nov 27 15:30:40 2012 > New Revision: 40167 > URL: http://svnweb.freebsd.org/changeset/doc/40167 > > Log: > Modernize the example echo module and fix some style(9) issues in the > code. > > Reviewed by: alfred (code) > Reviewed by: gonzo (code) > Reviewed by: ehaupt (code) > Approved by: bcr (mentor) > > Modified: > head/en_US.ISO8859-1/books/arch-handbook/driverbasics/chapter.xml A few notes: In echo_read(): amt = MIN(uio->uio_resid, echomsg->len - uio->uio_offset); You should probably make 'amt' a ssize_t since uio_resid is now a ssize_t. Also, I'm not sure it is safe to remove the check for uio_offset being > echmosg->len. On 32-bit platforms, uio_offset is an off_t (64-bit), but 'len' is an int and you are assigning it to an int (or ssize_t). I think you can get a uio_offset such that you overflow and when you truncate to 32-bits you end up with a positive value for 'echomsg->len - uio->uio_offset'. This coupled with a uio_resid larger than 'echomsg->len' (easy to do) can result in a buffer overrun. I would probably write this as: amt = MIN(uio->uio_resid, uio->uio_offset >= echomsg->len ? 0 : echomsg->len - uio->uio_offset); Rather than the previous version that tested the result of the subtraction. You should also not adjust uio_offset manually. uiomove() already does that. In echo_write(): The duplicate 'Copy the string in ...' comment at the top of this function should be removed. It's not clear to me why you forbade random access? Though it is fine if you want to do that. style(9) says single-line comments shouldn't span multiple lines, hence: /* * This is new message, reset length */ should be: /* This is a new message, reset length. */ IIRC, It is a null character, not a NULL character (NULL is only for pointers). Also, I think that should be in an else, so putting all that together: /* * For new messages, reset the length. If appending, start * at the existing null terminator. */ if (uio->uio_offset == 0) echomsg->len = 0; else echomsg->len--; Again, do not adjust uio_offset manually, you just did it twice. In fact, this will do the wrong thing if you get an EFAULT error. The right thing to do to handle partial copies, etc. is this: error = uiomove(...); /* Now we need to null terminate, then record the length. */ echomsg->len = uio->uio_offset + 1; echomsg->msg[uio->uio_offset] = '\0'; Other pre-existing nits: This driver shouldn't reference 'kmalloc' in a comment, and that entire comment can probably just be removed. The DEV_MODULE() macro should have spaces after the comma operator. -- John Baldwin From owner-svn-doc-all@FreeBSD.ORG Thu Jan 24 20:27:25 2013 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 2BBF337F; Thu, 24 Jan 2013 20:27:25 +0000 (UTC) (envelope-from wblock@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id EE49A2D5; Thu, 24 Jan 2013 20:27:24 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.5/8.14.5) with ESMTP id r0OKROi0073227; Thu, 24 Jan 2013 20:27:24 GMT (envelope-from wblock@svn.freebsd.org) Received: (from wblock@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r0OKROLb073226; Thu, 24 Jan 2013 20:27:24 GMT (envelope-from wblock@svn.freebsd.org) Message-Id: <201301242027.r0OKROLb073226@svn.freebsd.org> From: Warren Block Date: Thu, 24 Jan 2013 20:27:24 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40739 - head/en_US.ISO8859-1/books/handbook/cutting-edge X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Jan 2013 20:27:25 -0000 Author: wblock Date: Thu Jan 24 20:27:24 2013 New Revision: 40739 URL: http://svnweb.freebsd.org/changeset/doc/40739 Log: Force an empty make.conf in freebsd-update section custom kernel instructions. Modified: head/en_US.ISO8859-1/books/handbook/cutting-edge/chapter.xml Modified: head/en_US.ISO8859-1/books/handbook/cutting-edge/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/handbook/cutting-edge/chapter.xml Thu Jan 24 18:07:39 2013 (r40738) +++ head/en_US.ISO8859-1/books/handbook/cutting-edge/chapter.xml Thu Jan 24 20:27:24 2013 (r40739) @@ -431,7 +431,7 @@ MergeChanges /etc/ /var/named/etc/ &prompt.root; cd /usr/src -&prompt.root; env DESTDIR=/boot/GENERIC make kernel +&prompt.root; env DESTDIR=/boot/GENERIC make kernel __MAKE_CONF=/dev/null &prompt.root; mv /boot/GENERIC/boot/kernel/* /boot/GENERIC &prompt.root; rm -rf /boot/GENERIC/boot @@ -440,8 +440,7 @@ MergeChanges /etc/ /var/named/etc/freebsd-update, the GENERIC configuration file must not have been modified in any way. It is also suggested that - it is built without any other special options (preferably - with an empty /etc/make.conf). + it is built without any other special options. @@ -479,7 +478,7 @@ MergeChanges /etc/ /var/named/etc/ &prompt.root; cd /usr/src -&prompt.root; make kernel +&prompt.root; make kernel __MAKE_CONF=/dev/null For this kernel to be identified as the GENERIC kernel by @@ -487,8 +486,7 @@ MergeChanges /etc/ /var/named/etc/GENERIC configuration file must not have been modified in any way. It is also suggested that the kernel is built without any other - special options, preferably with an empty - /etc/make.conf. + special options. From owner-svn-doc-all@FreeBSD.ORG Thu Jan 24 22:06:19 2013 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 545C1E6C; Thu, 24 Jan 2013 22:06:19 +0000 (UTC) (envelope-from ryusuke@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id 245099D2; Thu, 24 Jan 2013 22:06:19 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.5/8.14.5) with ESMTP id r0OM6JaV002959; Thu, 24 Jan 2013 22:06:19 GMT (envelope-from ryusuke@svn.freebsd.org) Received: (from ryusuke@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r0OM6JXp002958; Thu, 24 Jan 2013 22:06:19 GMT (envelope-from ryusuke@svn.freebsd.org) Message-Id: <201301242206.r0OM6JXp002958@svn.freebsd.org> From: Ryusuke SUZUKI Date: Thu, 24 Jan 2013 22:06:18 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40740 - head/ja_JP.eucJP/books/handbook/cutting-edge X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Jan 2013 22:06:19 -0000 Author: ryusuke Date: Thu Jan 24 22:06:18 2013 New Revision: 40740 URL: http://svnweb.freebsd.org/changeset/doc/40740 Log: - Merge the following from the English version: r40712 -> r40739 head/ja_JP.eucJP/books/handbook/cutting-edge/chapter.xml Modified: head/ja_JP.eucJP/books/handbook/cutting-edge/chapter.xml Modified: head/ja_JP.eucJP/books/handbook/cutting-edge/chapter.xml ============================================================================== --- head/ja_JP.eucJP/books/handbook/cutting-edge/chapter.xml Thu Jan 24 20:27:24 2013 (r40739) +++ head/ja_JP.eucJP/books/handbook/cutting-edge/chapter.xml Thu Jan 24 22:06:18 2013 (r40740) @@ -3,7 +3,7 @@ The FreeBSD Documentation Project The FreeBSD Japanese Documentation Project - Original revision: r40712 + Original revision: r40739 $FreeBSD$ --> @@ -427,7 +427,7 @@ MergeChanges /etc/ /var/named/etc/ &prompt.root; cd /usr/src -&prompt.root; env DESTDIR=/boot/GENERIC make kernel +&prompt.root; env DESTDIR=/boot/GENERIC make kernel __MAKE_CONF=/dev/null &prompt.root; mv /boot/GENERIC/boot/kernel/* /boot/GENERIC &prompt.root; rm -rf /boot/GENERIC/boot @@ -435,9 +435,7 @@ MergeChanges /etc/ /var/named/etc/GENERIC ¥«¡¼¥Í¥ë¤È¤·¤Æ°·¤¤¤Þ¤¹¡£ GENERIC ¥³¥ó¥Õ¥£¥°¥ì¡¼¥·¥ç¥ó¥Õ¥¡¥¤¥ë¤Ï¡¢ ¤È¤Ë¤«¤¯Êѹ¹¤·¤Æ¤Ï¤¤¤±¤Þ¤»¤ó¡£ - ¤Þ¤¿¡¢ÆÃÊ̤ʥª¥×¥·¥ç¥ó¤ò»ØÄꤷ¤Ê¤¤ - (/etc/make.conf ¤¬¶õ¤Ç¤¢¤ë¤³¤È¤¬Ë¾¤Þ¤·¤¤) - ¤Ç¹½ÃÛ¤·¤Æ¤¯¤À¤µ¤¤¡£ + ¤Þ¤¿¡¢ÆÃÊ̤ʥª¥×¥·¥ç¥ó¤ò»ØÄꤷ¤Ê¤¤¤Ç¹½ÃÛ¤·¤Æ¤¯¤À¤µ¤¤¡£ @@ -475,15 +473,13 @@ MergeChanges /etc/ /var/named/etc/ &prompt.root; cd /usr/src -&prompt.root; make kernel +&prompt.root; make kernel __MAKE_CONF=/dev/null freebsd-update ¤Ï¡¢¤³¤Î¥«¡¼¥Í¥ë¤ò GENERIC ¥«¡¼¥Í¥ë¤È¤·¤Æ°·¤¤¤Þ¤¹¡£ GENERIC ¥³¥ó¥Õ¥£¥°¥ì¡¼¥·¥ç¥ó¥Õ¥¡¥¤¥ë¤Ï¡¢ ¤È¤Ë¤«¤¯Êѹ¹¤·¤Æ¤Ï¤¤¤±¤Þ¤»¤ó¡£ - ¤Þ¤¿¡¢ÆÃÊ̤ʥª¥×¥·¥ç¥ó¤ò»ØÄꤷ¤Ê¤¤ - (/etc/make.conf ¤¬¶õ¤Ç¤¢¤ë¤³¤È¤¬Ë¾¤Þ¤·¤¤) - ¤Ç¹½ÃÛ¤·¤Æ¤¯¤À¤µ¤¤¡£ + ¤Þ¤¿¡¢ÆÃÊ̤ʥª¥×¥·¥ç¥ó¤ò»ØÄꤷ¤Ê¤¤¤Ç¹½ÃÛ¤·¤Æ¤¯¤À¤µ¤¤¡£ From owner-svn-doc-all@FreeBSD.ORG Thu Jan 24 23:01:44 2013 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 1A1E7BD6; Thu, 24 Jan 2013 23:01:44 +0000 (UTC) (envelope-from dru@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id D23EDD04; Thu, 24 Jan 2013 23:01:43 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.5/8.14.5) with ESMTP id r0ON1hpD020348; Thu, 24 Jan 2013 23:01:43 GMT (envelope-from dru@svn.freebsd.org) Received: (from dru@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r0ON1hMf020347; Thu, 24 Jan 2013 23:01:43 GMT (envelope-from dru@svn.freebsd.org) Message-Id: <201301242301.r0ON1hMf020347@svn.freebsd.org> From: Dru Lavigne Date: Thu, 24 Jan 2013 23:01:43 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40741 - head/en_US.ISO8859-1/books/handbook/ports X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Jan 2013 23:01:44 -0000 Author: dru Date: Thu Jan 24 23:01:43 2013 New Revision: 40741 URL: http://svnweb.freebsd.org/changeset/doc/40741 Log: White space fix only. Translators can ignore. Approved by: gjb (mentor) Modified: head/en_US.ISO8859-1/books/handbook/ports/chapter.xml Modified: head/en_US.ISO8859-1/books/handbook/ports/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/handbook/ports/chapter.xml Thu Jan 24 22:06:18 2013 (r40740) +++ head/en_US.ISO8859-1/books/handbook/ports/chapter.xml Thu Jan 24 23:01:43 2013 (r40741) @@ -356,7 +356,7 @@ R-deps: feature. For example, searching for lsof would return: - &prompt.root; cd /usr/ports + &prompt.root; cd /usr/ports &prompt.root; make quicksearch name=lsof Port: lsof-4.87.a,7 Path: /usr/ports/sysutils/lsof @@ -683,7 +683,7 @@ docbook = utility for pkgng. The bootstrap utility will download and install pkgng. - + To bootstrap the system, run: &prompt.root; /usr/sbin/pkg @@ -796,7 +796,7 @@ docbook = &prompt.root; pkg info pkg pkg-1.0.2 New generation package manager - + Installing and Removing Packages with @@ -820,7 +820,7 @@ pkg-1.0.2 New generation package manag <command>pkg install</command>. For example, to install <application>curl</application>:</para> - <screen>&prompt.root; <userinput>pkg install curl</userinput> + <screen>&prompt.root; <userinput>pkg install curl</userinput> Updating repository catalogue Repository catalogue is up-to-date, no need to fetch fresh copy The following packages will be installed: @@ -1055,10 +1055,10 @@ Deinstalling ca_root_nss-3.13.5... done< available in &man.ports.7;.</para> <warning> - <para>As of mid 2012, the &os; Ports Project has migrated revision - control systems from CVS to Subversion. The preferred method - for obtaining and maintaining the ports tree is - <application>Portsnap</application>. Users requiring local + <para>As of mid 2012, the &os; Ports Project has migrated + revision control systems from CVS to Subversion. The + preferred method for obtaining and maintaining the ports tree + is <application>Portsnap</application>. Users requiring local customization of ports (that is, maintaining additional local patches) will probably prefer to use Subversion directly. The <application>CVSup</application> service is being phased out From owner-svn-doc-all@FreeBSD.ORG Thu Jan 24 23:02:25 2013 Return-Path: <owner-svn-doc-all@FreeBSD.ORG> Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id F0435C3B; Thu, 24 Jan 2013 23:02:25 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id E31ECD0C; Thu, 24 Jan 2013 23:02:25 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.5/8.14.5) with ESMTP id r0ON2P1c020507; Thu, 24 Jan 2013 23:02:25 GMT (envelope-from gjb@svn.freebsd.org) Received: (from gjb@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r0ON2PI0020506; Thu, 24 Jan 2013 23:02:25 GMT (envelope-from gjb@svn.freebsd.org) Message-Id: <201301242302.r0ON2PI0020506@svn.freebsd.org> From: Glen Barber <gjb@FreeBSD.org> Date: Thu, 24 Jan 2013 23:02:25 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40742 - head/en_US.ISO8859-1/books/porters-handbook X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" <svn-doc-all.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/svn-doc-all>, <mailto:svn-doc-all-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/svn-doc-all> List-Post: <mailto:svn-doc-all@freebsd.org> List-Help: <mailto:svn-doc-all-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/svn-doc-all>, <mailto:svn-doc-all-request@freebsd.org?subject=subscribe> X-List-Received-Date: Thu, 24 Jan 2013 23:02:26 -0000 Author: gjb Date: Thu Jan 24 23:02:25 2013 New Revision: 40742 URL: http://svnweb.freebsd.org/changeset/doc/40742 Log: Document __FreeBSD_version 901000. Submitted by: Patrick Mackinlay (via -doc) Modified: head/en_US.ISO8859-1/books/porters-handbook/book.xml Modified: head/en_US.ISO8859-1/books/porters-handbook/book.xml ============================================================================== --- head/en_US.ISO8859-1/books/porters-handbook/book.xml Thu Jan 24 23:01:43 2013 (r40741) +++ head/en_US.ISO8859-1/books/porters-handbook/book.xml Thu Jan 24 23:02:25 2013 (r40742) @@ -15669,6 +15669,12 @@ Reference: <http://www.freebsd.org/po </row> <row> + <entry>901000</entry> + <entry>August 5, 2012</entry> + <entry>9.1-RELEASE.</entry> + </row> + + <row> <entry>1000000</entry> <entry>September 26, 2011</entry> <entry>10.0-CURRENT.</entry> From owner-svn-doc-all@FreeBSD.ORG Fri Jan 25 00:26:47 2013 Return-Path: <owner-svn-doc-all@FreeBSD.ORG> Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 87C5AADD; Fri, 25 Jan 2013 00:26:47 +0000 (UTC) (envelope-from dru@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id 6D33580; Fri, 25 Jan 2013 00:26:47 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.5/8.14.5) with ESMTP id r0P0QlUU044717; Fri, 25 Jan 2013 00:26:47 GMT (envelope-from dru@svn.freebsd.org) Received: (from dru@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r0P0QlXT044716; Fri, 25 Jan 2013 00:26:47 GMT (envelope-from dru@svn.freebsd.org) Message-Id: <201301250026.r0P0QlXT044716@svn.freebsd.org> From: Dru Lavigne <dru@FreeBSD.org> Date: Fri, 25 Jan 2013 00:26:47 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40743 - head/en_US.ISO8859-1/books/handbook/preface X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" <svn-doc-all.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/svn-doc-all>, <mailto:svn-doc-all-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/svn-doc-all> List-Post: <mailto:svn-doc-all@freebsd.org> List-Help: <mailto:svn-doc-all-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/svn-doc-all>, <mailto:svn-doc-all-request@freebsd.org?subject=subscribe> X-List-Received-Date: Fri, 25 Jan 2013 00:26:47 -0000 Author: dru Date: Fri Jan 25 00:26:46 2013 New Revision: 40743 URL: http://svnweb.freebsd.org/changeset/doc/40743 Log: White space fix only. Translators can ignore. Approved by: gjb (mentor) Modified: head/en_US.ISO8859-1/books/handbook/preface/preface.xml Modified: head/en_US.ISO8859-1/books/handbook/preface/preface.xml ============================================================================== --- head/en_US.ISO8859-1/books/handbook/preface/preface.xml Thu Jan 24 23:02:25 2013 (r40742) +++ head/en_US.ISO8859-1/books/handbook/preface/preface.xml Fri Jan 25 00:26:46 2013 (r40743) @@ -11,10 +11,10 @@ <para>The &os; newcomer will find that the first section of this book guides the user through the &os; installation process and - gently introduces the concepts and conventions that underpin &unix;. - Working through this section requires little more than the desire - to explore, and the ability to take on board new concepts as they - are introduced.</para> + gently introduces the concepts and conventions that underpin + &unix;. Working through this section requires little more than + the desire to explore, and the ability to take on board new + concepts as they are introduced.</para> <para>Once you have traveled this far, the second, far larger, section of the Handbook is a comprehensive reference to all manner @@ -23,11 +23,11 @@ this is noted in the synopsis at the beginning of each chapter.</para> - <para>For a list of additional sources of information, please see <xref - linkend="bibliography"/>.</para> + <para>For a list of additional sources of information, please see + <xref linkend="bibliography"/>.</para> - <bridgehead id="preface-changes-from3" renderas="sect1">Changes from the - Third Edition</bridgehead> + <bridgehead id="preface-changes-from3" renderas="sect1">Changes + from the Third Edition</bridgehead> <para>The current online version of the Handbook represents the cumulative effort of many hundreds of contributors over the past @@ -35,125 +35,129 @@ the two volume third edition was published in 2004:</para> <itemizedlist> - <listitem> - <para><xref linkend="dtrace"/>, &dtrace;, has been added with - information about the powerful &dtrace; performance analysis - tool.</para> - </listitem> - - <listitem> - <para><xref linkend="filesystems"/>, File Systems Support, has - been added with information about non-native file systems in - &os;, such as ZFS from &sun;.</para> - </listitem> - - <listitem> - <para><xref linkend="audit"/>, Security Event Auditing, has - been added to cover the new auditing capabilities in &os; - and explain its use.</para> - </listitem> - - <listitem> - <para><xref linkend="virtualization"/>, Virtualization, has - been added with information about installing &os; on - virtualization software.</para> - </listitem> - - <listitem> - <para><xref linkend="bsdinstall"/>, Installing - &os; 9.<replaceable>x</replaceable> and Later, has been - added to cover installation of &os; using the new - installation utility, - <application>bsdinstall</application>.</para> - </listitem> + <listitem> + <para><xref linkend="dtrace"/>, &dtrace;, has been added with + information about the powerful &dtrace; performance analysis + tool.</para> + </listitem> + + <listitem> + <para><xref linkend="filesystems"/>, File Systems Support, has + been added with information about non-native file systems in + &os;, such as ZFS from &sun;.</para> + </listitem> + + <listitem> + <para><xref linkend="audit"/>, Security Event Auditing, has + been added to cover the new auditing capabilities in &os; + and explain its use.</para> + </listitem> + + <listitem> + <para><xref linkend="virtualization"/>, Virtualization, has + been added with information about installing &os; on + virtualization software.</para> + </listitem> + + <listitem> + <para><xref linkend="bsdinstall"/>, Installing + &os; 9.<replaceable>x</replaceable> and Later, has been + added to cover installation of &os; using the new + installation utility, + <application>bsdinstall</application>.</para> + </listitem> </itemizedlist> - <bridgehead id="preface-changes-from2" renderas="sect1">Changes from the - Second Edition (2004)</bridgehead> + <bridgehead id="preface-changes-from2" renderas="sect1">Changes + from the Second Edition (2004)</bridgehead> <para>The third edition was the culmination of over two years of - work by the dedicated members of the &os; Documentation - Project. The printed edition grew to such a size that it was - necessary to publish as two separate volumes. The following are - the major changes in this new edition:</para> + work by the dedicated members of the &os; Documentation + Project. The printed edition grew to such a size that it was + necessary to publish as two separate volumes. The following are + the major changes in this new edition:</para> <itemizedlist> - <listitem> - <para><xref linkend="config-tuning"/>, Configuration and - Tuning, has been expanded with new information about the - ACPI power and resource management, the <command>cron</command> system utility, - and more kernel tuning options.</para> - </listitem> - - <listitem> - <para><xref linkend="security"/>, Security, has been expanded with - new information about virtual private networks (VPNs), file - system access control lists (ACLs), and security - advisories.</para> - </listitem> - - <listitem> - <para><xref linkend="mac"/>, Mandatory Access Control (MAC), is - a new chapter with this edition. It explains what MAC is - and how this mechanism can be used to secure a &os; - system.</para> - </listitem> - - <listitem> - <para><xref linkend="disks"/>, Storage, has been expanded with - new information about USB storage devices, file system - snapshots, file system quotas, file and network backed - filesystems, and encrypted disk partitions.</para> - </listitem> + <listitem> + <para><xref linkend="config-tuning"/>, Configuration and + Tuning, has been expanded with new information about the + ACPI power and resource management, the + <command>cron</command> system utility, and more kernel + tuning options.</para> + </listitem> + + <listitem> + <para><xref linkend="security"/>, Security, has been expanded + with new information about virtual private networks (VPNs), + file system access control lists (ACLs), and security + advisories.</para> + </listitem> + + <listitem> + <para><xref linkend="mac"/>, Mandatory Access Control (MAC), + is a new chapter with this edition. It explains what MAC is + and how this mechanism can be used to secure a &os; + system.</para> + </listitem> + + <listitem> + <para><xref linkend="disks"/>, Storage, has been expanded with + new information about USB storage devices, file system + snapshots, file system quotas, file and network backed + filesystems, and encrypted disk partitions.</para> + </listitem> - <listitem> - <para><xref linkend="vinum-vinum"/>, Vinum, is a new chapter + <listitem> + <para><xref linkend="vinum-vinum"/>, Vinum, is a new chapter with this edition. It describes how to use Vinum, a logical volume manager which provides device-independent logical disks, and software RAID-0, RAID-1 and RAID-5.</para> - </listitem> + </listitem> - <listitem> - <para>A troubleshooting section has been added to <xref + <listitem> + <para>A troubleshooting section has been added to <xref linkend="ppp-and-slip"/>, PPP and SLIP.</para> - </listitem> - - <listitem> - <para><xref linkend="mail"/>, Electronic Mail, has been - expanded with new information about using alternative - transport agents, SMTP authentication, UUCP, <application>fetchmail</application>, - <application>procmail</application>, and other advanced topics.</para> - </listitem> - - <listitem> - <para><xref linkend="network-servers"/>, Network Servers, is - all new with this edition. This chapter includes - information about setting up the <application>Apache HTTP Server</application>, <application>ftpd</application>, - and setting up a server for µsoft; &windows; clients with - <application>Samba</application>. Some sections from <xref - linkend="advanced-networking"/>, Advanced Networking, were - moved here to improve the presentation.</para> - </listitem> - - <listitem> - <para><xref linkend="advanced-networking"/>, Advanced - Networking, has been expanded with new information about - using &bluetooth; devices with &os;, setting up wireless - networks, and Asynchronous Transfer Mode (ATM) - networking.</para> - </listitem> + </listitem> - <listitem> - <para>A glossary has been added to provide a central location - for the definitions of technical terms used throughout the - book.</para> - </listitem> - - <listitem> - <para>A number of aesthetic improvements have been made to the - tables and figures throughout the book.</para> - </listitem> - </itemizedlist> + <listitem> + <para><xref linkend="mail"/>, Electronic Mail, has been + expanded with new information about using alternative + transport agents, SMTP authentication, UUCP, + <application>fetchmail</application>, + <application>procmail</application>, and other advanced + topics.</para> + </listitem> + + <listitem> + <para><xref linkend="network-servers"/>, Network Servers, is + all new with this edition. This chapter includes + information about setting up the <application>Apache HTTP + Server</application>, <application>ftpd</application>, + and setting up a server for µsoft; &windows; clients + with <application>Samba</application>. Some sections from + <xref linkend="advanced-networking"/>, Advanced Networking, + were moved here to improve the presentation.</para> + </listitem> + + <listitem> + <para><xref linkend="advanced-networking"/>, Advanced + Networking, has been expanded with new information about + using &bluetooth; devices with &os;, setting up wireless + networks, and Asynchronous Transfer Mode (ATM) + networking.</para> + </listitem> + + <listitem> + <para>A glossary has been added to provide a central location + for the definitions of technical terms used throughout the + book.</para> + </listitem> + + <listitem> + <para>A number of aesthetic improvements have been made to the + tables and figures throughout the book.</para> + </listitem> + </itemizedlist> <bridgehead id="preface-changes" renderas="sect1">Changes from the First Edition (2001)</bridgehead> @@ -170,88 +174,99 @@ <para>A complete Index has been added.</para> </listitem> <listitem> - <para>All ASCII figures have been replaced by graphical diagrams.</para> + <para>All ASCII figures have been replaced by graphical + diagrams.</para> </listitem> <listitem> <para>A standard synopsis has been added to each chapter to - give a quick summary of what information the chapter contains, - and what the reader is expected to know.</para> + give a quick summary of what information the chapter + contains, and what the reader is expected to know.</para> </listitem> <listitem> <para>The content has been logically reorganized into three - parts: <quote>Getting Started</quote>, <quote>System Administration</quote>, and - <quote>Appendices</quote>.</para> + parts: <quote>Getting Started</quote>, <quote>System + Administration</quote>, and + <quote>Appendices</quote>.</para> </listitem> <listitem> - <para><xref linkend="install"/> (<quote>Installing &os;</quote>) was completely - rewritten with many screenshots to make it much easier for new - users to grasp the text.</para> + <para><xref linkend="install"/> (<quote>Installing + &os;</quote>) was completely rewritten with many + screenshots to make it much easier for new users to grasp + the text.</para> </listitem> <listitem> - <para><xref linkend="basics"/> (<quote>&unix; Basics</quote>) has been expanded to contain - additional information about processes, daemons, and - signals.</para> + <para><xref linkend="basics"/> (<quote>&unix; Basics</quote>) + has been expanded to contain additional information about + processes, daemons, and signals.</para> </listitem> <listitem> - <para><xref linkend="ports"/> (<quote>Installing Applications</quote>) has been expanded - to contain additional information about binary package - management.</para> + <para><xref linkend="ports"/> (<quote>Installing + Applications</quote>) has been expanded to contain + additional information about binary package + management.</para> </listitem> <listitem> - <para><xref linkend="x11"/> (<quote>The X Window System</quote>) has been completely - rewritten with an emphasis on using modern desktop - technologies such as <application>KDE</application> and <application>GNOME</application> on &xfree86; 4.X.</para> + <para><xref linkend="x11"/> (<quote>The X Window + System</quote>) has been completely rewritten with an + emphasis on using modern desktop technologies such as + <application>KDE</application> and + <application>GNOME</application> on &xfree86; 4.X.</para> </listitem> <listitem> - <para><xref linkend="boot"/> (<quote>The &os; Booting Process</quote>) has been - expanded.</para> + <para><xref linkend="boot"/> (<quote>The &os; Booting + Process</quote>) has been expanded.</para> </listitem> <listitem> - <para><xref linkend="disks"/> (<quote>Storage</quote>) has been written from what used - to be two separate chapters on <quote>Disks</quote> and <quote>Backups</quote>. We feel - that the topics are easier to comprehend when presented as a - single chapter. A section on RAID (both hardware and - software) has also been added.</para> + <para><xref linkend="disks"/> (<quote>Storage</quote>) has + been written from what used to be two separate chapters on + <quote>Disks</quote> and <quote>Backups</quote>. We feel + that the topics are easier to comprehend when presented as + a single chapter. A section on RAID (both hardware and + software) has also been added.</para> </listitem> <listitem> - <para><xref linkend="serialcomms"/> (<quote>Serial Communications</quote>) has been completely - reorganized and updated for &os; 4.X/5.X.</para> + <para><xref linkend="serialcomms"/> (<quote>Serial + Communications</quote>) has been completely + reorganized and updated for &os; 4.X/5.X.</para> </listitem> <listitem> - <para><xref linkend="ppp-and-slip"/> (<quote>PPP and SLIP</quote>) has been substantially - updated.</para> + <para><xref linkend="ppp-and-slip"/> (<quote>PPP and + SLIP</quote>) has been substantially updated.</para> </listitem> <listitem> - <para>Many new sections have been added to <xref linkend="advanced-networking"/> - (<quote>Advanced Networking</quote>).</para> + <para>Many new sections have been added to + <xref linkend="advanced-networking"/> + (<quote>Advanced Networking</quote>).</para> </listitem> <listitem> - <para><xref linkend="mail"/> (<quote>Electronic Mail</quote>) has been expanded to - include more information about configuring - <application>sendmail</application>.</para> + <para><xref linkend="mail"/> (<quote>Electronic Mail</quote>) + has been expanded to include more information about + configuring <application>sendmail</application>.</para> </listitem> <listitem> - <para><xref linkend="linuxemu"/> (<quote>&linux; Compatibility</quote>) has been expanded to - include information about installing + <para><xref linkend="linuxemu"/> (<quote>&linux; + Compatibility</quote>) has been expanded to include + information about installing <application>&oracle;</application> and - <application>&sap.r3;</application>.</para> + <application>&sap.r3;</application>.</para> </listitem> <listitem> <para>The following new topics are covered in this second - edition:</para> + edition:</para> <itemizedlist> <listitem> - <para>Configuration and Tuning (<xref linkend="config-tuning"/>).</para> + <para>Configuration and Tuning (<xref + linkend="config-tuning"/>).</para> </listitem> <listitem> - <para>Multimedia (<xref linkend="multimedia"/>)</para> + <para>Multimedia (<xref linkend="multimedia"/>)</para> </listitem> </itemizedlist> </listitem> </itemizedlist> - <bridgehead id="preface-overview" renderas="sect1">Organization of This - Book</bridgehead> + <bridgehead id="preface-overview" renderas="sect1">Organization of + This Book</bridgehead> <para>This book is split into five logically distinct sections. The first section, <emphasis>Getting Started</emphasis>, covers @@ -276,26 +291,30 @@ <!-- Part I - Introduction --> <varlistentry> - <term><emphasis><xref linkend="introduction"/>, Introduction</emphasis></term> + <term><emphasis><xref linkend="introduction"/>, + Introduction</emphasis></term> <listitem> <para>Introduces &os; to a new user. It describes the - history of the &os; Project, its goals and development model.</para> + history of the &os; Project, its goals and development + model.</para> </listitem> </varlistentry> <varlistentry> <term><emphasis><xref linkend="install"/>, Installation of - &os; 8.<replaceable>x</replaceable> and Earlier</emphasis></term> + &os; 8.<replaceable>x</replaceable> and + Earlier</emphasis></term> <listitem> <para>Walks a user through the entire installation process of &os; 8.<replaceable>x</replaceable> and earlier using - <application>sysinstall</application>. Some advanced installation - topics, such as installing through a serial console, are also - covered.</para> + <application>sysinstall</application>. Some advanced + installation topics, such as installing through a serial + console, are also covered.</para> </listitem> </varlistentry> <varlistentry> <term><emphasis><xref linkend="bsdinstall"/>, Installation of - &os; 9.<replaceable>x</replaceable> and Later</emphasis></term> + &os; 9.<replaceable>x</replaceable> and + Later</emphasis></term> <listitem> <para>Walks a user through the entire installation process of &os; 9.<replaceable>x</replaceable> and later using @@ -303,71 +322,81 @@ </listitem> </varlistentry> <varlistentry> - <term><emphasis><xref linkend="basics"/>, &unix; Basics</emphasis></term> + <term><emphasis><xref linkend="basics"/>, &unix; + Basics</emphasis></term> <listitem> <para>Covers the basic commands and functionality of the - &os; operating system. If you are familiar with &linux; or - another flavor of &unix; then you can probably skip this - chapter.</para> + &os; operating system. If you are familiar with &linux; + or another flavor of &unix; then you can probably skip this + chapter.</para> </listitem> </varlistentry> <varlistentry> - <term><emphasis><xref linkend="ports"/>, Installing Applications</emphasis></term> + <term><emphasis><xref linkend="ports"/>, Installing + Applications</emphasis></term> <listitem> <para>Covers the installation of third-party software with - both &os;'s innovative <quote>Ports Collection</quote> and standard - binary packages.</para> + both &os;'s innovative <quote>Ports Collection</quote> and + standard binary packages.</para> </listitem> </varlistentry> <varlistentry> - <term><emphasis><xref linkend="x11"/>, The X Window System</emphasis></term> + <term><emphasis><xref linkend="x11"/>, The X Window + System</emphasis></term> <listitem> <para>Describes the X Window System in general and using - X11 on &os; in particular. Also describes common - desktop environments such as <application>KDE</application> and <application>GNOME</application>.</para> + X11 on &os; in particular. Also describes common + desktop environments such as <application>KDE</application> + and <application>GNOME</application>.</para> </listitem> </varlistentry> <!-- Part II Common Tasks --> <varlistentry> - <term><emphasis><xref linkend="desktop"/>, Desktop Applications</emphasis></term> + <term><emphasis><xref linkend="desktop"/>, Desktop + Applications</emphasis></term> <listitem> - <para>Lists some common desktop applications, such as web browsers - and productivity suites, and describes how to install them on - &os;.</para> + <para>Lists some common desktop applications, such as web + browsers and productivity suites, and describes how to + install them on &os;.</para> </listitem> </varlistentry> <varlistentry> - <term><emphasis><xref linkend="multimedia"/>, Multimedia</emphasis></term> + <term><emphasis><xref linkend="multimedia"/>, + Multimedia</emphasis></term> <listitem> - <para>Shows how to set up sound and video playback support for your - system. Also describes some sample audio and video applications.</para> + <para>Shows how to set up sound and video playback support + for your system. Also describes some sample audio and video + applications.</para> </listitem> </varlistentry> <varlistentry> - <term><emphasis><xref linkend="kernelconfig"/>, Configuring the &os; - Kernel</emphasis></term> + <term><emphasis><xref linkend="kernelconfig"/>, Configuring + the &os; Kernel</emphasis></term> <listitem> <para>Explains why you might need to configure a new kernel - and provides detailed instructions for configuring, building, - and installing a custom kernel.</para> + and provides detailed instructions for configuring, + building, and installing a custom kernel.</para> </listitem> </varlistentry> <varlistentry> - <term><emphasis><xref linkend="printing"/>, Printing</emphasis></term> + <term><emphasis><xref linkend="printing"/>, + Printing</emphasis></term> <listitem> <para>Describes managing printers on &os;, including - information about banner pages, printer accounting, and - initial setup.</para> + information about banner pages, printer accounting, and + initial setup.</para> </listitem> </varlistentry> <varlistentry> - <term><emphasis><xref linkend="linuxemu"/>, &linux; Binary Compatibility</emphasis></term> + <term><emphasis><xref linkend="linuxemu"/>, &linux; Binary + Compatibility</emphasis></term> <listitem> <para>Describes the &linux; compatibility features of &os;. - Also provides detailed installation instructions for many - popular &linux; applications such as <application>&oracle;</application> and + Also provides detailed installation instructions for many + popular &linux; applications such as + <application>&oracle;</application> and <application>&mathematica;</application>.</para> </listitem> </varlistentry> @@ -375,19 +404,22 @@ <!-- Part III - System Administration --> <varlistentry> - <term><emphasis><xref linkend="config-tuning"/>, Configuration and Tuning</emphasis></term> + <term><emphasis><xref linkend="config-tuning"/>, Configuration + and Tuning</emphasis></term> <listitem> <para>Describes the parameters available for system - administrators to tune a &os; system for optimum - performance. Also describes the various configuration files - used in &os; and where to find them.</para> + administrators to tune a &os; system for optimum + performance. Also describes the various configuration files + used in &os; and where to find them.</para> </listitem> </varlistentry> <varlistentry> - <term><emphasis><xref linkend="boot"/>, Booting Process</emphasis></term> + <term><emphasis><xref linkend="boot"/>, Booting + Process</emphasis></term> <listitem> <para>Describes the &os; boot process and explains - how to control this process with configuration options.</para> + how to control this process with configuration + options.</para> </listitem> </varlistentry> <varlistentry> @@ -400,59 +432,69 @@ </listitem> </varlistentry> <varlistentry> - <term><emphasis><xref linkend="security"/>, Security</emphasis></term> + <term><emphasis><xref linkend="security"/>, + Security</emphasis></term> <listitem> - <para>Describes many different tools available to help keep your - &os; system secure, including Kerberos, IPsec and OpenSSH.</para> + <para>Describes many different tools available to help keep + your &os; system secure, including Kerberos, IPsec and + OpenSSH.</para> </listitem> </varlistentry> <varlistentry> <term><emphasis><xref linkend="jails"/>, Jails</emphasis></term> <listitem> - <para>Describes the jails framework, and the improvements of jails - over the traditional chroot support of &os;.</para> + <para>Describes the jails framework, and the improvements of + jails over the traditional chroot support of &os;.</para> </listitem> </varlistentry> <varlistentry> - <term><emphasis><xref linkend="mac"/>, Mandatory Access Control</emphasis></term> + <term><emphasis><xref linkend="mac"/>, Mandatory Access + Control</emphasis></term> <listitem> - <para>Explains what Mandatory Access Control (MAC) is and how this - mechanism can be used to secure a &os; system.</para> + <para>Explains what Mandatory Access Control (MAC) is and + how this mechanism can be used to secure a &os; + system.</para> </listitem> </varlistentry> <varlistentry> - <term><emphasis><xref linkend="audit"/>, Security Event Auditing</emphasis></term> + <term><emphasis><xref linkend="audit"/>, Security Event + Auditing</emphasis></term> <listitem> - <para>Describes what &os; Event Auditing is, how it can be installed, - configured, and how audit trails can be inspected or monitored.</para> + <para>Describes what &os; Event Auditing is, how it can be + installed, configured, and how audit trails can be inspected + or monitored.</para> </listitem> </varlistentry> <varlistentry> - <term><emphasis><xref linkend="disks"/>, Storage</emphasis></term> + <term><emphasis><xref linkend="disks"/>, + Storage</emphasis></term> <listitem> <para>Describes how to manage storage media and filesystems - with &os;. This includes physical disks, RAID arrays, - optical and tape media, memory-backed disks, and network - filesystems.</para> + with &os;. This includes physical disks, RAID arrays, + optical and tape media, memory-backed disks, and network + filesystems.</para> </listitem> </varlistentry> <varlistentry> - <term><emphasis><xref linkend="GEOM-synopsis"/>, GEOM</emphasis></term> + <term><emphasis><xref linkend="GEOM-synopsis"/>, + GEOM</emphasis></term> <listitem> <para>Describes what the GEOM framework in &os; is and how to configure various supported RAID levels.</para> </listitem> </varlistentry> <varlistentry> - <term><emphasis><xref linkend="filesystems"/>, File Systems Support</emphasis></term> + <term><emphasis><xref linkend="filesystems"/>, File Systems + Support</emphasis></term> <listitem> - <para>Examines support of non-native file systems in &os;, like the Z - File System from &sun;.</para> + <para>Examines support of non-native file systems in &os;, + like the Z File System from &sun;.</para> </listitem> </varlistentry> <varlistentry> - <term><emphasis><xref linkend="vinum-vinum"/>, Vinum</emphasis></term> + <term><emphasis><xref linkend="vinum-vinum"/>, + Vinum</emphasis></term> <listitem> <para>Describes how to use Vinum, a logical volume manager which provides device-independent logical disks, and @@ -460,66 +502,77 @@ </listitem> </varlistentry> <varlistentry> - <term><emphasis><xref linkend="virtualization"/>, Virtualization</emphasis></term> + <term><emphasis><xref linkend="virtualization"/>, + Virtualization</emphasis></term> <listitem> - <para>Describes what virtualization systems offer, and how they - can be used with &os;.</para> + <para>Describes what virtualization systems offer, and how + they can be used with &os;.</para> </listitem> </varlistentry> <varlistentry> - <term><emphasis><xref linkend="l10n"/>, Localization</emphasis></term> + <term><emphasis><xref linkend="l10n"/>, + Localization</emphasis></term> <listitem> <para>Describes how to use &os; in languages other than - English. Covers both system and application level - localization.</para> + English. Covers both system and application level + localization.</para> </listitem> </varlistentry> <varlistentry> - <term><emphasis><xref linkend="updating-upgrading"/>, Updating and Upgrading &os;</emphasis></term> + <term><emphasis><xref linkend="updating-upgrading"/>, Updating + and Upgrading &os;</emphasis></term> <listitem> <para>Explains the differences between &os;-STABLE, - &os;-CURRENT, and &os; releases. Describes which users - would benefit from tracking a development system and outlines - that process. Covers the methods users may take to update their - system to the latest security release.</para> + &os;-CURRENT, and &os; releases. Describes which users + would benefit from tracking a development system and + outlines that process. Covers the methods users may take + to update their system to the latest security + release.</para> </listitem> </varlistentry> <varlistentry> - <term><emphasis><xref linkend="dtrace"/>, &dtrace;</emphasis></term> + <term><emphasis><xref linkend="dtrace"/>, + &dtrace;</emphasis></term> <listitem> - <para>Describes how to configure and use the &dtrace; tool from &sun; - in &os;. Dynamic tracing can help locate performance issues, by - performing real time system analysis.</para> + <para>Describes how to configure and use the &dtrace; tool + from &sun; in &os;. Dynamic tracing can help locate + performance issues, by performing real time system + analysis.</para> </listitem> </varlistentry> <!-- Part IV - Network Communications --> <varlistentry> - <term><emphasis><xref linkend="serialcomms"/>, Serial Communications</emphasis></term> + <term><emphasis><xref linkend="serialcomms"/>, Serial + Communications</emphasis></term> <listitem> <para>Explains how to connect terminals and modems to your - &os; system for both dial in and dial out connections.</para> + &os; system for both dial in and dial out + connections.</para> </listitem> </varlistentry> <varlistentry> - <term><emphasis><xref linkend="ppp-and-slip"/>, PPP and SLIP</emphasis></term> + <term><emphasis><xref linkend="ppp-and-slip"/>, PPP and + SLIP</emphasis></term> <listitem> <para>Describes how to use PPP, SLIP, or PPP over Ethernet to - connect to remote systems with &os;.</para> + connect to remote systems with &os;.</para> </listitem> </varlistentry> <varlistentry> - <term><emphasis><xref linkend="mail"/>, Electronic Mail</emphasis></term> + <term><emphasis><xref linkend="mail"/>, Electronic + Mail</emphasis></term> <listitem> - <para>Explains the different components of an email server and - dives into simple configuration topics for the most popular - mail server software: - <application>sendmail</application>.</para> + <para>Explains the different components of an email server + and dives into simple configuration topics for the most + popular mail server software: + <application>sendmail</application>.</para> </listitem> </varlistentry> <varlistentry> - <term><emphasis><xref linkend="network-servers"/>, Network Servers</emphasis></term> + <term><emphasis><xref linkend="network-servers"/>, Network + Servers</emphasis></term> <listitem> <para>Provides detailed instructions and example configuration files to set up your &os; machine as a network filesystem @@ -528,79 +581,88 @@ </listitem> </varlistentry> <varlistentry> - <term><emphasis><xref linkend="firewalls"/>, Firewalls</emphasis></term> + <term><emphasis><xref linkend="firewalls"/>, + Firewalls</emphasis></term> <listitem> - <para>Explains the philosophy behind software-based firewalls and - provides detailed information about the configuration of the - different firewalls available for &os;.</para> + <para>Explains the philosophy behind software-based firewalls + and provides detailed information about the configuration + of the different firewalls available for &os;.</para> </listitem> </varlistentry> <varlistentry> - <term><emphasis><xref linkend="advanced-networking"/>, Advanced Networking</emphasis></term> + <term><emphasis><xref linkend="advanced-networking"/>, Advanced + Networking</emphasis></term> <listitem> <para>Describes many networking topics, including sharing an - Internet connection with other computers on your LAN, advanced - routing topics, wireless networking, &bluetooth;, ATM, IPv6, and - much more.</para> + Internet connection with other computers on your LAN, + advanced routing topics, wireless networking, &bluetooth;, + ATM, IPv6, and much more.</para> </listitem> </varlistentry> <!-- Part V - Appendices --> <varlistentry> - <term><emphasis><xref linkend="mirrors"/>, Obtaining &os; </emphasis></term> + <term><emphasis><xref linkend="mirrors"/>, Obtaining &os; + </emphasis></term> <listitem> - <para>Lists different sources for obtaining &os; media on CDROM - or DVD as well as different sites on the Internet that allow - you to download and install &os;.</para> + <para>Lists different sources for obtaining &os; media on + CDROM or DVD as well as different sites on the Internet + that allow you to download and install &os;.</para> </listitem> </varlistentry> <varlistentry> - <term><emphasis><xref linkend="bibliography"/>, Bibliography </emphasis></term> + <term><emphasis><xref linkend="bibliography"/>, + Bibliography</emphasis></term> <listitem> <para>This book touches on many different subjects that may - leave you hungry for a more detailed explanation. The - bibliography lists many excellent books that are referenced in - the text.</para> + leave you hungry for a more detailed explanation. The + bibliography lists many excellent books that are referenced + in the text.</para> </listitem> </varlistentry> <varlistentry> - <term><emphasis><xref linkend="eresources"/>, Resources on the Internet</emphasis></term> + <term><emphasis><xref linkend="eresources"/>, Resources on the + Internet</emphasis></term> <listitem> <para>Describes the many forums available for &os; users to - post questions and engage in technical conversations about - &os;.</para> + post questions and engage in technical conversations about + &os;.</para> </listitem> </varlistentry> <varlistentry> - <term><emphasis><xref linkend="pgpkeys"/>, PGP Keys</emphasis></term> + <term><emphasis><xref linkend="pgpkeys"/>, PGP + Keys</emphasis></term> <listitem> - <para>Lists the PGP fingerprints of several &os; Developers.</para> + <para>Lists the PGP fingerprints of several &os; + Developers.</para> </listitem> </varlistentry> </variablelist> <bridgehead id="preface-conv" renderas="sect1">Conventions used - in this book</bridgehead> + in this book</bridgehead> <para>To provide a consistent and easy to read text, several - conventions are followed throughout the book.</para> + conventions are followed throughout the book.</para> - <bridgehead id="preface-conv-typographic" renderas="sect2">Typographic - Conventions</bridgehead> + <bridgehead id="preface-conv-typographic" + renderas="sect2">Typographic + Conventions</bridgehead> <variablelist> <varlistentry> <term><emphasis>Italic</emphasis></term> <listitem> - <para>An <emphasis>italic</emphasis> font is used for filenames, URLs, - emphasized text, and the first usage of technical terms.</para> + <para>An <emphasis>italic</emphasis> font is used for + filenames, URLs, emphasized text, and the first usage of + technical terms.</para> </listitem> </varlistentry> <varlistentry> <term><literal>Monospace</literal></term> <listitem> - <para>A <literal>monospaced</literal> font is + <para>A <literal>monospaced</literal> font is used for error messages, commands, environment variables, names of ports, hostnames, user names, group names, device names, variables, and code fragments.</para> @@ -610,7 +672,7 @@ <term><application>Bold</application></term> <listitem> <para>A <application>bold</application> font is used for - applications, commands, and keys.</para> + applications, commands, and keys.</para> </listitem> </varlistentry> </variablelist> @@ -628,16 +690,14 @@ <keycombo action="simul"> <keycap>Ctrl</keycap> <keycap>Alt</keycap> - <keycap>Del</keycap> - </keycombo> - </para> + <keycap>Del</keycap></keycombo></para> <para>Meaning the user should type the <keycap>Ctrl</keycap>, <keycap>Alt</keycap>, and <keycap>Del</keycap> keys at the same time.</para> - <para>Keys that are meant to be typed in sequence will be separated with - commas, for example:</para> + <para>Keys that are meant to be typed in sequence will be separated + with commas, for example:</para> <para> <keycombo action="simul"> @@ -646,9 +706,7 @@ </keycombo>, <keycombo action="simul"> <keycap>Ctrl</keycap> - <keycap>S</keycap> - </keycombo> - </para> + <keycap>S</keycap></keycombo></para> <para>Would mean that the user is expected to type the <keycap>Ctrl</keycap> and <keycap>X</keycap> keys simultaneously @@ -660,9 +718,10 @@ renderas="sect2">Examples</bridgehead> <para>Examples starting with <devicename>E:\></devicename> - indicate a &ms-dos; command. Unless otherwise noted, these commands - may be executed from a <quote>Command Prompt</quote> window in a modern µsoft.windows; - environment.</para> + indicate a &ms-dos; command. Unless otherwise noted, these + commands may be executed from a <quote>Command Prompt</quote> + window in a modern µsoft.windows; + environment.</para> <screen><prompt>E:\></prompt> <userinput>tools\fdimage floppies\kern.flp A:</userinput></screen> @@ -684,10 +743,10 @@ <bridgehead id="preface-acknowledgements" renderas="sect1">Acknowledgments</bridgehead> - <para>The book you are holding represents the efforts of many hundreds of - people around the world. Whether they sent in fixes for typos, or - submitted complete chapters, all the contributions have been - useful.</para> + <para>The book you are holding represents the efforts of many + hundreds of people around the world. Whether they sent in fixes + for typos, or submitted complete chapters, all the contributions + have been useful.</para> <para>Several companies have supported the development of this document by paying authors to work on it full-time, paying for @@ -697,11 +756,11 @@ improving this book full time leading up to the publication of the first printed edition in March 2000 (ISBN 1-57176-241-8). Wind River Systems then paid several additional authors to make a - number of improvements to the print-output infrastructure and to add - additional chapters to the text. This work culminated in the - publication of the second printed edition in November 2001 (ISBN - 1-57176-303-1). In 2003-2004, <ulink - url="http://www.freebsdmall.com">&os; Mall, Inc</ulink>, paid + number of improvements to the print-output infrastructure and + to add additional chapters to the text. This work culminated in + the publication of the second printed edition in November 2001 + (ISBN 1-57176-303-1). In 2003-2004, <ulink + url="http://www.freebsdmall.com">&os; Mall, Inc</ulink>, paid several contributors to improve the Handbook in preparation for the third printed edition.</para> From owner-svn-doc-all@FreeBSD.ORG Fri Jan 25 00:30:28 2013 Return-Path: <owner-svn-doc-all@FreeBSD.ORG> Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id AF990B60; Fri, 25 Jan 2013 00:30:28 +0000 (UTC) (envelope-from dru@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id 8832E9D; Fri, 25 Jan 2013 00:30:28 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.5/8.14.5) with ESMTP id r0P0USH4046796; Fri, 25 Jan 2013 00:30:28 GMT (envelope-from dru@svn.freebsd.org) Received: (from dru@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r0P0USsO046795; Fri, 25 Jan 2013 00:30:28 GMT (envelope-from dru@svn.freebsd.org) Message-Id: <201301250030.r0P0USsO046795@svn.freebsd.org> From: Dru Lavigne <dru@FreeBSD.org> Date: Fri, 25 Jan 2013 00:30:28 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40744 - head/en_US.ISO8859-1/books/handbook/network-servers X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" <svn-doc-all.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/svn-doc-all>, <mailto:svn-doc-all-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/svn-doc-all> List-Post: <mailto:svn-doc-all@freebsd.org> List-Help: <mailto:svn-doc-all-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/svn-doc-all>, <mailto:svn-doc-all-request@freebsd.org?subject=subscribe> X-List-Received-Date: Fri, 25 Jan 2013 00:30:28 -0000 Author: dru Date: Fri Jan 25 00:30:28 2013 New Revision: 40744 URL: http://svnweb.freebsd.org/changeset/doc/40744 Log: White space fix only. Translators can ignore. Approved by: gjb (mentor) Modified: head/en_US.ISO8859-1/books/handbook/network-servers/chapter.xml Modified: head/en_US.ISO8859-1/books/handbook/network-servers/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/handbook/network-servers/chapter.xml Fri Jan 25 00:26:46 2013 (r40743) +++ head/en_US.ISO8859-1/books/handbook/network-servers/chapter.xml Fri Jan 25 00:30:28 2013 (r40744) @@ -340,22 +340,27 @@ server-program-arguments</programlisting <entry>tcp, tcp4</entry> <entry>TCP IPv4</entry> </row> + <row> <entry>udp, udp4</entry> <entry>UDP IPv4</entry> </row> + <row> <entry>tcp6</entry> <entry>TCP IPv6</entry> </row> + <row> <entry>udp6</entry> <entry>UDP IPv6</entry> </row> + <row> <entry>tcp46</entry> <entry>Both TCP IPv4 and v6</entry> </row> + <row> <entry>udp46</entry> <entry>Both UDP IPv4 and v6</entry> @@ -635,12 +640,14 @@ server-program-arguments</programlisting requests from the <acronym>NFS</acronym> clients.</entry> </row> + <row> <entry><application>mountd</application></entry> <entry>The <acronym>NFS</acronym> mount daemon which carries out the requests that &man.nfsd.8; passes on to it.</entry> </row> + <row> <entry><application>rpcbind</application></entry> <entry> This daemon allows @@ -662,6 +669,7 @@ server-program-arguments</programlisting <sect2 id="network-configuring-nfs"> <title>Configuring <acronym>NFS</acronym> + NFS configuration @@ -799,8 +807,8 @@ mountd_flags="-r" &prompt.root; /etc/rc.d/mountd onereload - Please refer to for more - information about using rc scripts. + Please refer to for + more information about using rc scripts. Alternatively, a reboot will make FreeBSD set everything up properly. A reboot is not necessary though. @@ -1155,6 +1163,7 @@ Exports list on foobar: What Is It? + NIS Solaris HP-UX @@ -1218,8 +1227,8 @@ Exports list on foobar: - - + + @@ -1237,6 +1246,7 @@ Exports list on foobar: domainname does not have anything to do with DNS. + rpcbind @@ -1247,6 +1257,7 @@ Exports list on foobar: will be impossible to run an NIS server, or to act as an NIS client. + ypbind @@ -1259,6 +1270,7 @@ Exports list on foobar: on a client machine, it will not be able to access the NIS server. + ypserv Should only be running on NIS servers; this is @@ -1274,6 +1286,7 @@ Exports list on foobar: ypbind process on the client. + rpc.yppasswdd Another process that should only be running on @@ -1404,21 +1417,25 @@ Exports list on foobar: 10.0.0.2 NIS master + coltrane 10.0.0.3 NIS slave + basie 10.0.0.4 Faculty workstation + bird 10.0.0.5 Client machine + cli[1-11] @@ -1517,6 +1534,7 @@ Exports list on foobar: Setting Up a NIS Master Server + NIS server configuration @@ -1531,18 +1549,23 @@ Exports list on foobar: nisdomainname="test-domain" + This line will set the NIS domainname to test-domain upon network setup (e.g., after reboot). + nis_server_enable="YES" + This will tell FreeBSD to start up the NIS server processes when the networking is next brought up. + nis_yppasswdd_enable="YES" + This will enable the rpc.yppasswdd daemon which, as mentioned above, will allow users to change their NIS password from a client @@ -1570,6 +1593,7 @@ Exports list on foobar: Initializing the NIS Maps + NIS maps @@ -1661,6 +1685,7 @@ ellington has been setup as an YP master Setting up a NIS Slave Server + NIS slave server @@ -1785,9 +1810,11 @@ Don't forget to update map ypservers on another server. - Setting Up a NIS Client + Setting Up a NIS Client + + NIS client - configuration + configuration Setting up a FreeBSD machine to be a NIS client is fairly straightforward. @@ -2006,6 +2033,7 @@ basie&prompt.root; Using Netgroups + netgroups The method shown in the previous section works reasonably @@ -2097,6 +2125,7 @@ basie&prompt.root; employees are allowed to log onto these machines. + pride, greed, @@ -2106,6 +2135,7 @@ basie&prompt.root; department are allowed to login onto these machines. + one, two, three, four, @@ -2509,6 +2539,7 @@ nis_client_flags="-S NIS do Password Formats + NIS password formats @@ -2585,6 +2616,7 @@ nis_client_flags="-S NIS do What Is DHCP? + Dynamic Host Configuration Protocol DHCP @@ -2619,6 +2651,7 @@ nis_client_flags="-S NIS do How It Works + UDP When dhclient, the DHCP client, is executed on the client machine, it begins broadcasting @@ -2644,12 +2677,14 @@ nis_client_flags="-S NIS do dhclient. DHCP client support is provided within both the installer and the base system, obviating the need for detailed knowledge of network configurations on any - network that runs a DHCP server. - sysinstall - + network that runs a DHCP server. + + + sysinstall + - DHCP is supported by - sysinstall. When configuring a + DHCP is supported by + sysinstall. When configuring a network interface within sysinstall, the second question asked is: Do you want to try DHCP configuration of @@ -2745,132 +2780,135 @@ dhclient_flags="" role="package">net/isc-dhcp42-server port in the ports collection. This port contains the ISC DHCP server and documentation. - + - - Files - - DHCP - configuration files - - - - /etc/dhclient.conf - dhclient requires a configuration - file, /etc/dhclient.conf. Typically - the file contains only comments, the defaults being - reasonably sane. This configuration file is described by - the &man.dhclient.conf.5; - manual page. - + + Files - - /sbin/dhclient - dhclient is statically linked and - resides in /sbin. The - &man.dhclient.8; manual page gives more information about - dhclient. - + + DHCP + configuration files + + + + /etc/dhclient.conf + dhclient requires a configuration + file, /etc/dhclient.conf. + Typically the file contains only comments, the defaults + being reasonably sane. This configuration file is + described by the &man.dhclient.conf.5; manual + page. + - - /sbin/dhclient-script - dhclient-script is the - FreeBSD-specific DHCP client configuration script. It is - described in &man.dhclient-script.8;, but should not need - any user modification to function properly. - + + /sbin/dhclient + dhclient is statically linked and + resides in /sbin. The + &man.dhclient.8; manual page gives more information + about dhclient. + - - /var/db/dhclient.leases.interface - The DHCP client keeps a database of valid leases in - this file, which is written as a log. - &man.dhclient.leases.5; gives a slightly longer - description. - - - + + /sbin/dhclient-script + dhclient-script is the + FreeBSD-specific DHCP client configuration script. It + is described in &man.dhclient-script.8;, but should not + need any user modification to function properly. + - - Further Reading + + /var/db/dhclient.leases.interface + The DHCP client keeps a database of valid leases + in this file, which is written as a log. + &man.dhclient.leases.5; gives a slightly longer + description. + + + - The DHCP protocol is fully described in RFC - 2131. An informational resource has also been set up - at . - + + Further Reading - - Installing and Configuring a DHCP Server + The DHCP protocol is fully described in RFC + 2131. An informational resource has also been set + up at . + + + + Installing and Configuring a DHCP Server + + + What This Section Covers + + This section provides information on how to configure + a FreeBSD system to act as a DHCP server using the ISC + (Internet Systems Consortium) implementation of the DHCP + server. - - What This Section Covers + The server is not provided as part of FreeBSD, and so + you will need to install the net/isc-dhcp42-server port to + provide this service. See for + more information on using the Ports Collection. + - This section provides information on how to configure - a FreeBSD system to act as a DHCP server using the ISC - (Internet Systems Consortium) implementation of the DHCP - server. - - The server is not provided as part of FreeBSD, and so - you will need to install the net/isc-dhcp42-server port to - provide this service. See for - more information on using the Ports Collection. - + + DHCP Server Installation - - DHCP Server Installation - - DHCP - installation - - In order to configure your FreeBSD system as a DHCP - server, you will need to ensure that the &man.bpf.4; - device is compiled into your kernel. To do this, add - device bpf to your kernel - configuration file, and rebuild the kernel. For more - information about building kernels, see . - - The bpf device is already - part of the GENERIC kernel that is - supplied with FreeBSD, so you do not need to create a - custom kernel in order to get DHCP working. + + DHCP + installation + + In order to configure your FreeBSD system as a DHCP + server, you will need to ensure that the &man.bpf.4; + device is compiled into your kernel. To do this, add + device bpf to your kernel + configuration file, and rebuild the kernel. For more + information about building kernels, see . + + The bpf device is already + part of the GENERIC kernel that is + supplied with FreeBSD, so you do not need to create a + custom kernel in order to get DHCP working. - - Those who are particularly security conscious - should note that bpf is also - the device that allows packet sniffers to work - correctly (although such programs still need - privileged access). bpf - is required to use DHCP, but if - you are very sensitive about security, you probably - should not include bpf in - your kernel purely because you expect to use DHCP at - some point in the future. - + + Those who are particularly security conscious + should note that bpf is also + the device that allows packet sniffers to work + correctly (although such programs still need + privileged access). bpf + is required to use DHCP, but if + you are very sensitive about security, you probably + should not include bpf in + your kernel purely because you expect to use DHCP at + some point in the future. + - The next thing that you will need to do is edit the - sample dhcpd.conf which was installed - by the net/isc-dhcp42-server port. - By default, this will be - /usr/local/etc/dhcpd.conf.sample, and - you should copy this to - /usr/local/etc/dhcpd.conf before - proceeding to make changes. - + The next thing that you will need to do is edit the + sample dhcpd.conf which was installed + by the net/isc-dhcp42-server port. + By default, this will be + /usr/local/etc/dhcpd.conf.sample, and + you should copy this to + /usr/local/etc/dhcpd.conf before + proceeding to make changes. + - - Configuring the DHCP Server - - DHCP - dhcpd.conf - - dhcpd.conf is comprised of - declarations regarding subnets and hosts, and is perhaps - most easily explained using an example : + + Configuring the DHCP Server + + + DHCP + dhcpd.conf + + dhcpd.conf is comprised of + declarations regarding subnets and hosts, and is perhaps + most easily explained using an example : - option domain-name "example.com"; + option domain-name "example.com"; option domain-name-servers 192.168.4.100; option subnet-mask 255.255.255.0; @@ -2986,6 +3024,7 @@ dhcpd_ifaces="dc0" Files + DHCP configuration files @@ -3063,6 +3102,7 @@ dhcpd_ifaces="dc0" Overview + BIND &os; utilizes, by default, a version of BIND (Berkeley @@ -3272,6 +3312,7 @@ dhcpd_ifaces="dc0" How It Works + In &os;, the BIND daemon is called named. @@ -3725,6 +3766,7 @@ zone "1.168.192.in-addr.arpa" { Zone Files + BIND zone files @@ -3966,6 +4008,7 @@ mail IN A 192.168. Caching Name Server + BIND caching name server @@ -3979,24 +4022,25 @@ mail IN A 192.168. <acronym role="Domain Name Security Extensions">DNSSEC</acronym> + BIND DNS security extensions Domain Name System Security Extensions, or DNSSEC for - short, is a suite of specifications to protect resolving name - servers from forged DNS data, such as - spoofed DNS records. By using digital - signatures, a resolver can verify the integrity of the record. - Note that DNSSEC only - provides integrity via digitally signing the Resource - Records (RRs). It - provides neither confidentiality nor protection against false - end-user assumptions. This means that it cannot protect - against people going to DNSSEC + for short, is a suite of specifications to protect resolving + name servers from forged DNS data, such + as spoofed DNS records. By using digital + signatures, a resolver can verify the integrity of the + record. Note that DNSSEC + only provides integrity via digitally signing the Resource + Records (RRs). + It provides neither confidentiality nor protection against + false end-user assumptions. This means that it cannot + protect against people going to example.net instead of example.com. The only thing DNSSEC does is authenticate that the data @@ -4610,6 +4654,7 @@ $include Kexample.com.+005+nnnnn.ZSK.key following commands: &prompt.root; /usr/local/etc/rc.d/apache22 configtest + &prompt.root; service apache22 configtest @@ -4626,6 +4671,7 @@ $include Kexample.com.+005+nnnnn.ZSK.key mechanisms: &prompt.root; /usr/local/etc/rc.d/apache22 start + &prompt.root; service apache22 start The httpd service can be tested by @@ -5166,6 +5212,7 @@ DocumentRoot /www/someotherdomain.tld Samba: swat stream tcp nowait/400 root /usr/local/sbin/swat swat + As explained in , the inetd configuration must be reloaded after this configuration file is changed. @@ -5289,6 +5336,7 @@ DocumentRoot /www/someotherdomain.tld the following command: &prompt.root; smbpasswd -a username + The recommended backend is now tdbsam, and the following command @@ -5323,6 +5371,7 @@ DocumentRoot /www/someotherdomain.tld Or, for fine grain control: nmbd_enable="YES" + smbd_enable="YES" @@ -5339,8 +5388,8 @@ Starting SAMBA: removing stale tdbs : Starting nmbd. Starting smbd. - Please refer to for more - information about using rc scripts. + Please refer to for + more information about using rc scripts. Samba actually consists of three separate daemons. You should see that both the @@ -5445,6 +5494,7 @@ Starting smbd. Basic Configuration + ntpdate If you only wish to synchronize your clock when the From owner-svn-doc-all@FreeBSD.ORG Fri Jan 25 06:36:03 2013 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id E9320541; Fri, 25 Jan 2013 06:36:03 +0000 (UTC) (envelope-from jgh@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id DA89FB0; Fri, 25 Jan 2013 06:36:03 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.5/8.14.5) with ESMTP id r0P6a3qE056123; Fri, 25 Jan 2013 06:36:03 GMT (envelope-from jgh@svn.freebsd.org) Received: (from jgh@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r0P6a3ib056122; Fri, 25 Jan 2013 06:36:03 GMT (envelope-from jgh@svn.freebsd.org) Message-Id: <201301250636.r0P6a3ib056122@svn.freebsd.org> From: Jason Helfman Date: Fri, 25 Jan 2013 06:36:03 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40745 - head/en_US.ISO8859-1/articles/contributors X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Jan 2013 06:36:04 -0000 Author: jgh (ports committer) Date: Fri Jan 25 06:36:03 2013 New Revision: 40745 URL: http://svnweb.freebsd.org/changeset/doc/40745 Log: - add Joseph Mingrone for deskutils/clipit PR: 175483 Modified: head/en_US.ISO8859-1/articles/contributors/contrib.additional.xml Modified: head/en_US.ISO8859-1/articles/contributors/contrib.additional.xml ============================================================================== --- head/en_US.ISO8859-1/articles/contributors/contrib.additional.xml Fri Jan 25 00:30:28 2013 (r40744) +++ head/en_US.ISO8859-1/articles/contributors/contrib.additional.xml Fri Jan 25 06:36:03 2013 (r40745) @@ -5133,6 +5133,11 @@ + Joseph Mingrone + jrm@ftfl.ca + + + Joseph Scott joseph@randomnetworks.com From owner-svn-doc-all@FreeBSD.ORG Fri Jan 25 14:27:48 2013 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 954C3651; Fri, 25 Jan 2013 14:27:48 +0000 (UTC) (envelope-from eadler@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id 87955E22; Fri, 25 Jan 2013 14:27:48 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.5/8.14.5) with ESMTP id r0PERmXU002595; Fri, 25 Jan 2013 14:27:48 GMT (envelope-from eadler@svn.freebsd.org) Received: (from eadler@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r0PERmBx002594; Fri, 25 Jan 2013 14:27:48 GMT (envelope-from eadler@svn.freebsd.org) Message-Id: <201301251427.r0PERmBx002594@svn.freebsd.org> From: Eitan Adler Date: Fri, 25 Jan 2013 14:27:48 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40746 - head/en_US.ISO8859-1/articles/committers-guide X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Jan 2013 14:27:48 -0000 Author: eadler Date: Fri Jan 25 14:27:47 2013 New Revision: 40746 URL: http://svnweb.freebsd.org/changeset/doc/40746 Log: Make it clear that reverts should contain mergeinfo. Discussed with: brooks Approved by: bcr (mentor) Modified: head/en_US.ISO8859-1/articles/committers-guide/article.xml Modified: head/en_US.ISO8859-1/articles/committers-guide/article.xml ============================================================================== --- head/en_US.ISO8859-1/articles/committers-guide/article.xml Fri Jan 25 06:36:03 2013 (r40745) +++ head/en_US.ISO8859-1/articles/committers-guide/article.xml Fri Jan 25 14:27:47 2013 (r40746) @@ -1721,6 +1721,13 @@ U stable/9/share/man/man4/netmap.4 &prompt.user; svn merge -r179454:179453 svn+ssh://svn.freebsd.org/base/ROADMAP.txt + + It is important to ensure that the mergeinfo + is correct when reverting a file in order to permit + svn mergeinfo --eligible to work as + expected. + + Reverting the deletion of a file is slightly different. Copying the version of the file that predates the deletion is required. For example, to restore a file that was From owner-svn-doc-all@FreeBSD.ORG Fri Jan 25 16:17:44 2013 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 4DE638E4; Fri, 25 Jan 2013 16:17:44 +0000 (UTC) (envelope-from eadler@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id 404EC85D; Fri, 25 Jan 2013 16:17:44 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.5/8.14.5) with ESMTP id r0PGHiRN035464; Fri, 25 Jan 2013 16:17:44 GMT (envelope-from eadler@svn.freebsd.org) Received: (from eadler@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r0PGHhrY035463; Fri, 25 Jan 2013 16:17:43 GMT (envelope-from eadler@svn.freebsd.org) Message-Id: <201301251617.r0PGHhrY035463@svn.freebsd.org> From: Eitan Adler Date: Fri, 25 Jan 2013 16:17:43 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40747 - head/en_US.ISO8859-1/books/faq X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Jan 2013 16:17:44 -0000 Author: eadler Date: Fri Jan 25 16:17:43 2013 New Revision: 40747 URL: http://svnweb.freebsd.org/changeset/doc/40747 Log: Combine the questions on mailing lists and newgroups as they have nearly identical (non-)answers. Approved by: bcr Modified: head/en_US.ISO8859-1/books/faq/book.xml Modified: head/en_US.ISO8859-1/books/faq/book.xml ============================================================================== --- head/en_US.ISO8859-1/books/faq/book.xml Fri Jan 25 14:27:47 2013 (r40746) +++ head/en_US.ISO8859-1/books/faq/book.xml Fri Jan 25 16:17:43 2013 (r40747) @@ -963,22 +963,14 @@ - Where do I find info on the &os; mailing lists? - - - - You can find full information in the Handbook entry on mailing-lists. - - - - - - What &os; news groups are available? + Where do I find info on the &os; mailing lists? + What &os; news groups are available? You can find full information in the Handbook entry on mailing-lists + and the Handbook entry on newsgroups. From owner-svn-doc-all@FreeBSD.ORG Fri Jan 25 16:17:46 2013 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id DB5548E5; Fri, 25 Jan 2013 16:17:46 +0000 (UTC) (envelope-from eadler@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id CD51285E; Fri, 25 Jan 2013 16:17:46 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.5/8.14.5) with ESMTP id r0PGHkv1035500; Fri, 25 Jan 2013 16:17:46 GMT (envelope-from eadler@svn.freebsd.org) Received: (from eadler@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r0PGHkP3035499; Fri, 25 Jan 2013 16:17:46 GMT (envelope-from eadler@svn.freebsd.org) Message-Id: <201301251617.r0PGHkP3035499@svn.freebsd.org> From: Eitan Adler Date: Fri, 25 Jan 2013 16:17:46 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40748 - head/en_US.ISO8859-1/books/faq X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Jan 2013 16:17:46 -0000 Author: eadler Date: Fri Jan 25 16:17:46 2013 New Revision: 40748 URL: http://svnweb.freebsd.org/changeset/doc/40748 Log: Correct the number and identity of the floppies required for pc98. Noted by: nyan Approved by: bcr (mentor) Modified: head/en_US.ISO8859-1/books/faq/book.xml Modified: head/en_US.ISO8859-1/books/faq/book.xml ============================================================================== --- head/en_US.ISO8859-1/books/faq/book.xml Fri Jan 25 16:17:43 2013 (r40747) +++ head/en_US.ISO8859-1/books/faq/book.xml Fri Jan 25 16:17:46 2013 (r40748) @@ -1189,10 +1189,11 @@ - &arch.pc98; users require three floppy images: + &arch.pc98; users require these floppy images: floppies/boot.flp, - floppies/kern1.flp, and - floppies/kern2.flp. These images + floppies/kern1.flp, + floppies/kern2.flp, and + floppies/mfsroot1.flp. These images need to be copied onto floppies by tools like &man.dd.1;. From owner-svn-doc-all@FreeBSD.ORG Fri Jan 25 16:23:49 2013 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 7F5EBB61 for ; Fri, 25 Jan 2013 16:23:49 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: from mail-vc0-f169.google.com (mail-vc0-f169.google.com [209.85.220.169]) by mx1.freebsd.org (Postfix) with ESMTP id 3475789E for ; Fri, 25 Jan 2013 16:23:48 +0000 (UTC) Received: by mail-vc0-f169.google.com with SMTP id n10so398483vcn.14 for ; Fri, 25 Jan 2013 08:23:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eitanadler.com; s=0xdeadbeef; h=x-received:mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type; bh=efiO25GO38y7iJKfeJ95Of5FA0QJ7HcuTQF4Nm5o680=; b=XGTj/44qUB7P+f210t0JAdPOPCzmiAj12H1t+YXBVFnBg/UNOdDF89BZ4+JsErJZ6b RFftZFkCL/prx8asC7QzJ6zepVBOur6oApi/mWV1pKrRG9G1gIKWCylasuUbkEcvWTtP lATwUfHQvco3Vkp4/L4MER9YaZNHtxVxXxw8s= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type :x-gm-message-state; bh=efiO25GO38y7iJKfeJ95Of5FA0QJ7HcuTQF4Nm5o680=; b=mCaTrEvXRSGqBKIOSXuaJJgDc75BTTcE027jXo6Y/JRzXxj47JJ+NM53RYOCouEvjw ZASfgc/9LoWnD0rioqzw+fTsREH+2GZzTZ6zJHZAPUV3H2zSvVyyMs/m6lGp75g04gS0 oh9qiUYTqsYzPXm+yZEczNQdMsAXn0a4++EoMJJeHkXw8SRvl3E+apf7YMSTIbOMXKey LvGAGLLr9fvbyXtWfgmq2y6WCEzBADyBOsYS3cGk+w8XPQbPhfRf4txLp3TNedSB+aHF 3axohdIQ/FAPE2BG7WAt/gZtPUME8Qa/b4hsNL7LY40QWNv8BHxlUKhPvZeWdh0bC2sa eTVQ== X-Received: by 10.52.76.7 with SMTP id g7mr5743459vdw.95.1359131022611; Fri, 25 Jan 2013 08:23:42 -0800 (PST) MIME-Version: 1.0 Sender: lists@eitanadler.com Received: by 10.220.195.70 with HTTP; Fri, 25 Jan 2013 08:23:12 -0800 (PST) In-Reply-To: <201301241014.14854.jhb@freebsd.org> References: <201211271530.qARFUekl097033@svn.freebsd.org> <201301241014.14854.jhb@freebsd.org> From: Eitan Adler Date: Fri, 25 Jan 2013 11:23:12 -0500 X-Google-Sender-Auth: ndqXlW2jjNlivmjv5AVkE4zuBLo Message-ID: Subject: Re: svn commit: r40167 - head/en_US.ISO8859-1/books/arch-handbook/driverbasics To: John Baldwin Content-Type: text/plain; charset=UTF-8 X-Gm-Message-State: ALoCoQkIMmsgrRHywHW0ivR4/lZ0ov4SSkspnQClNzpBBm8Z7qHq07t+UYkwOHrFGj7z7/uVQ6ky Cc: svn-doc-head@freebsd.org, svn-doc-all@freebsd.org, doc-committers@freebsd.org X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Jan 2013 16:23:49 -0000 On 24 January 2013 10:14, John Baldwin wrote: >> Reviewed by: alfred (code) >> Reviewed by: gonzo (code) >> Reviewed by: ehaupt (code) Thanks for the review! I had three people look this over (some multiple times) and still not everything was caught. I'll re-add this file to my "things to fix" list. I'm about to start classes again so I'm not sure when I'll get to it though. -- Eitan Adler Source, Ports, Doc committer Bugmeister, Ports Security teams From owner-svn-doc-all@FreeBSD.ORG Fri Jan 25 17:07:43 2013 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id F34BCB81; Fri, 25 Jan 2013 17:07:42 +0000 (UTC) (envelope-from dru@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id CE6BEA8E; Fri, 25 Jan 2013 17:07:42 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.5/8.14.5) with ESMTP id r0PH7g9F050218; Fri, 25 Jan 2013 17:07:42 GMT (envelope-from dru@svn.freebsd.org) Received: (from dru@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r0PH7g2h050217; Fri, 25 Jan 2013 17:07:42 GMT (envelope-from dru@svn.freebsd.org) Message-Id: <201301251707.r0PH7g2h050217@svn.freebsd.org> From: Dru Lavigne Date: Fri, 25 Jan 2013 17:07:42 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40749 - head/en_US.ISO8859-1/books/handbook/security X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Jan 2013 17:07:43 -0000 Author: dru Date: Fri Jan 25 17:07:42 2013 New Revision: 40749 URL: http://svnweb.freebsd.org/changeset/doc/40749 Log: White space fix only. Translators can ignore. Approved by: gjb (mentor) Modified: head/en_US.ISO8859-1/books/handbook/security/chapter.xml Modified: head/en_US.ISO8859-1/books/handbook/security/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/handbook/security/chapter.xml Fri Jan 25 16:17:46 2013 (r40748) +++ head/en_US.ISO8859-1/books/handbook/security/chapter.xml Fri Jan 25 17:07:42 2013 (r40749) @@ -12,7 +12,7 @@ Matthew Dillon Much of this chapter has been taken from the - security(7) manual page by + security(7) manual page by @@ -1277,7 +1277,7 @@ GAME GAG WELT OUT DOWN CHAT Once you have initialized OPIE and login, you will be presented with a prompt like this: -&prompt.user; telnet example.com + &prompt.user; telnet example.com Trying 10.0.0.1... Connected to example.com Escape character is '^]'. @@ -1534,8 +1534,9 @@ ALL : ALL \ It may be possible to launch a denial of service - attack on the server if an attacker, or group of attackers, - could flood these daemons with connection requests. + attack on the server if an attacker, or group of + attackers, could flood these daemons with connection + requests. Another possibility is to use the From owner-svn-doc-all@FreeBSD.ORG Fri Jan 25 17:11:04 2013 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id B8F36D0D; Fri, 25 Jan 2013 17:11:04 +0000 (UTC) (envelope-from dru@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id A9343ABF; Fri, 25 Jan 2013 17:11:04 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.5/8.14.5) with ESMTP id r0PHB49Q052411; Fri, 25 Jan 2013 17:11:04 GMT (envelope-from dru@svn.freebsd.org) Received: (from dru@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r0PHB4ws052410; Fri, 25 Jan 2013 17:11:04 GMT (envelope-from dru@svn.freebsd.org) Message-Id: <201301251711.r0PHB4ws052410@svn.freebsd.org> From: Dru Lavigne Date: Fri, 25 Jan 2013 17:11:04 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40750 - head/en_US.ISO8859-1/books/handbook/printing X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Jan 2013 17:11:04 -0000 Author: dru Date: Fri Jan 25 17:11:04 2013 New Revision: 40750 URL: http://svnweb.freebsd.org/changeset/doc/40750 Log: White space fix only. Translators can ignore. Approved by: gjb (mentor) Modified: head/en_US.ISO8859-1/books/handbook/printing/chapter.xml Modified: head/en_US.ISO8859-1/books/handbook/printing/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/handbook/printing/chapter.xml Fri Jan 25 17:07:42 2013 (r40749) +++ head/en_US.ISO8859-1/books/handbook/printing/chapter.xml Fri Jan 25 17:11:04 2013 (r40750) @@ -29,21 +29,23 @@ Synopsis + LPD spooling system printing - &os; can be used to print with a wide variety of printers, from the - oldest impact printer to the latest laser printers, and everything in - between, allowing you to produce high-quality printed output from the - applications you run. + &os; can be used to print with a wide variety of printers, + from the oldest impact printer to the latest laser printers, + and everything in between, allowing you to produce high-quality + printed output from the applications you run. &os; can also be configured to act as a print server on a - network; in this capacity &os; can receive print jobs from a variety - of other computers, including other &os; computers, &windows; and - &macos; hosts. &os; will ensure that one job at a time is printed, and - can keep statistics on which users and machines are doing the most - printing, produce banner pages showing whose printout is - whose, and more. + network; in this capacity &os; can receive print jobs from a + varietyof other computers, including other &os; computers, + &windows; and &macos; hosts. &os; will ensure that one job + at a time is printed, and can keep statistics on which users + and machines are doing the most printing, produce + banner pages showing whose printout is whose, + and more. After reading this chapter, you will know: @@ -53,17 +55,19 @@ - How to install print filters, to handle special print jobs - differently, including converting incoming documents to print - formats that your printers understand. + How to install print filters, to handle special print + jobs differently, including converting incoming documents + to print formats that your printers understand. - How to enable header, or banner pages on your printout. + How to enable header, or banner pages on your + printout. - How to print with printers connected to other computers. + How to print with printers connected to other + computers. @@ -72,8 +76,9 @@ - How to control printer restrictions, including limiting the size - of print jobs, and preventing certain users from printing. + How to control printer restrictions, including limiting + the size of print jobs, and preventing certain users from + printing. @@ -99,21 +104,22 @@ Introduction - In order to use printers with &os; you may set - them up to work with the Berkeley line printer spooling system, - also known as the LPD spooling system, - or just LPD. - It is the standard printer control system in &os;. This - chapter introduces LPD and - will guide you through its configuration. + In order to use printers with &os; you may set them up to + work with the Berkeley line printer spooling system, also known + as the LPD spooling system, or just + LPD. It is the standard printer + control system in &os;. This chapter introduces + LPD and will guide you through its + configuration. If you are already familiar with LPD or another printer spooling system, you may wish to skip to section Basic Setup. - LPD controls everything about a - host's printers. It is responsible for a number of things: + LPD controls everything about + a host's printers. It is responsible for a number of + things: @@ -129,16 +135,16 @@ - It prevents multiple users from accessing a printer at the - same time by maintaining a queue for each - printer. + It prevents multiple users from accessing a printer at + the same time by maintaining a queue + for each printer. - It can print header pages (also known - as banner or burst - pages) so users can easily find jobs they have printed in a - stack of printouts. + It can print header pages (also + known as banner or + burst pages) so users can easily find + jobs they have printed in a stack of printouts. @@ -148,12 +154,14 @@ It can send jobs over the network to a - LPD spooler on another host. + LPD spooler on another + host. - It can run special filters to format jobs to be printed for - various printer languages or printer capabilities. + It can run special filters to format jobs to be printed + for various printer languages or printer + capabilities. @@ -162,42 +170,42 @@ Through a configuration file - (/etc/printcap), and by providing the special - filter programs, you can enable the LPD - system to do all or some subset of the above for a great variety of - printer hardware. + (/etc/printcap), and by providing the + special filter programs, you can enable the + LPD system to do all or some subset + of the above for a great variety of printer hardware. Why You Should Use the Spooler - If you are the sole user of your system, you may be wondering - why you should bother with the spooler when you do not need access - control, header pages, or printer accounting. While it is - possible to enable direct access to a printer, you should use the - spooler anyway since: + If you are the sole user of your system, you may be + wondering why you should bother with the spooler when you do + not need access control, header pages, or printer accounting. + While it is possible to enable direct access to a printer, + you should use the spooler anyway since: - LPD prints jobs in the background; - you do not have to wait for data to be copied to the - printer. + LPD prints jobs in the + background; you do not have to wait for data to be copied + to the printer. &tex; - LPD can conveniently run a job - to be printed through filters to add date/time headers or convert - a special file format (such as a &tex; DVI file) into a format - the printer will understand. You will not have to do these steps - manually. + LPD can conveniently run + a job to be printed through filters to add date/time + headers or convert a special file format (such as a &tex; + DVI file) into a format the printer will understand. + You will not have to do these steps manually. Many free and commercial programs that provide a print - feature usually expect to talk to the spooler on your system. - By setting up the spooling system, you will more easily - support other software you may later add or already + feature usually expect to talk to the spooler on your + system. By setting up the spooling system, you will more + easily support other software you may later add or already have. @@ -216,72 +224,74 @@ documentation according to these changes. - To use printers with the LPD spooling - system, you will need to set up both your printer hardware and the - LPD software. This document describes two - levels of setup: + To use printers with the LPD + spooling system, you will need to set up both your printer + hardware and the LPD software. This + document describes two levels of setup: - See section Simple Printer - Setup to learn how to connect a printer, tell - LPD how to communicate with it, and - print plain text files to the printer. + See section Simple + Printer Setup to learn how to connect a printer, + tell LPD how to communicate with + it, and print plain text files to the printer. - See section Advanced Printer - Setup to learn how to print a variety of special file - formats, to print header pages, to print across a network, to - control access to printers, and to do printer accounting. + See section Advanced + Printer Setup to learn how to print a variety of + special file formats, to print header pages, to print across + a network, to control access to printers, and to do printer + accounting. Simple Printer Setup - This section tells how to configure printer hardware and the - LPD software to use the printer. - It teaches the basics: + This section tells how to configure printer hardware + and the LPD software to use the + printer. It teaches the basics: Section Hardware - Setup gives some hints on connecting the printer to a - port on your computer. + Setup gives some hints on connecting the printer + to a port on your computer. Section Software - Setup shows how to set up the + Setup shows how to set up the LPD spooler configuration file (/etc/printcap). - If you are setting up a printer that uses a network protocol - to accept data to print instead of a computer's local interfaces, - see Printers With - Networked Data Stream Interfaces. + If you are setting up a printer that uses a network + protocol to accept data to print instead of a computer's local + interfaces, see Printers With + Networked Data Stream Interfaces. Although this section is called Simple Printer - Setup, it is actually fairly complex. Getting the printer - to work with your computer and the LPD - spooler is the hardest part. The advanced options like header pages - and accounting are fairly easy once you get the printer - working. + Setup, it is actually fairly complex. Getting the + printer to work with your computer and the + LPD spooler is the hardest part. + The advanced options like header pages and accounting are + fairly easy once you get the printer working. Hardware Setup - This section tells about the various ways you can connect a - printer to your PC. It talks about the kinds of ports and - cables, and also the kernel configuration you may need to enable - &os; to speak to the printer. + This section tells about the various ways you can + connect a printer to your PC. It talks about the kinds of + ports and cables, and also the kernel configuration you may + need to enable &os; to speak to the printer. If you have already connected your printer and have - successfully printed with it under another operating system, you - can probably skip to section Software Setup. @@ -300,13 +310,14 @@ Serial interfaces, also known as RS-232 or COM ports, use a serial port on your computer to send data to the printer. Serial - interfaces are common in the computer industry and cables - are readily available and also easy to construct. Serial - interfaces sometimes need special cables and might require - you to configure somewhat complex communications - options. Most PC serial ports have a maximum - transmission rate of 115200 bps, which makes printing - large graphic print jobs with them impractical. + interfaces are common in the computer industry and + cables are readily available and also easy to + construct. Serial interfaces sometimes need special + cables and might require you to configure somewhat + complex communications options. Most PC serial ports + have a maximum transmission rate of 115200 bps, + which makes printing large graphic print jobs with + them impractical. @@ -317,12 +328,12 @@ Parallel interfaces use a parallel port on your computer to send data to the - printer. Parallel interfaces are common in the PC market - and are faster than RS-232 serial. - Cables are readily available but more difficult to - construct by hand. There are usually no communications - options with parallel interfaces, making their - configuration exceedingly simple. + printer. Parallel interfaces are common in the PC + market and are faster than RS-232 serial. Cables are + readily available but more difficult to construct by + hand. There are usually no communications options + with parallel interfaces, making their configuration + exceedingly simple. centronics @@ -341,115 +352,123 @@ USB interfaces, named for the Universal Serial Bus, can run at even faster speeds than parallel or - RS-232 serial interfaces. Cables are simple and cheap. - USB is superior to RS-232 Serial and to Parallel for - printing, but it is not as well supported under &unix; - systems. A way to avoid this problem is to purchase a - printer that has both a USB interface and a Parallel - interface, as many printers do. + RS-232 serial interfaces. Cables are simple and + cheap. USB is superior to RS-232 Serial and to + Parallel for printing, but it is not as well supported + under &unix; systems. A way to avoid this problem is + to purchase a printer that has both a USB interface + and a Parallel interface, as many printers do. In general, Parallel interfaces usually offer just one-way communication (computer to printer) while serial and USB gives you two-way. Newer parallel ports (EPP and - ECP) and printers can communicate in both directions under &os; - when a IEEE-1284-compliant cable is used. + ECP) and printers can communicate in both directions under + &os; when a IEEE-1284-compliant cable is used. PostScript Two-way communication to the printer over a parallel - port is generally done in one of two ways. The first method - uses a custom-built printer driver for &os; that speaks - the proprietary language used by the printer. This is - common with inkjet printers and can be used for reporting - ink levels and other status information. The second - method is used when the printer supports + port is generally done in one of two ways. The first + method uses a custom-built printer driver for &os; that + speaks the proprietary language used by the printer. This + is common with inkjet printers and can be used for + reporting ink levels and other status information. The + second method is used when the printer supports &postscript;. - &postscript; jobs are actually programs sent to the printer; - they need not produce paper at all and may return results - directly to the computer. &postscript; also uses two-way - communication to tell the computer about problems, such as errors - in the &postscript; program or paper jams. Your users may be - appreciative of such information. Furthermore, the best way to - do effective accounting with a &postscript; printer requires - two-way communication: you ask the printer for its page count (how - many pages it has printed in its lifetime), then send the - user's job, then ask again for its page count. Subtract the - two values and you know how much paper to charge to the + &postscript; jobs are actually programs sent to the + printer; they need not produce paper at all and may return + results directly to the computer. &postscript; also uses + two-way communication to tell the computer about problems, + such as errors in the &postscript; program or paper jams. + Your users may be appreciative of such information. + Furthermore, the best way to do effective accounting with + a &postscript; printer requires two-way communication: + you ask the printer for its page count (how many pages + it has printed in its lifetime), then send the user's job, + then ask again for its page count. Subtract the two + values and you know how much paper to charge to the user. Parallel Ports - To hook up a printer using a parallel interface, connect - the Centronics cable between the printer and the computer. - The instructions that came with the printer, the computer, or - both should give you complete guidance. + To hook up a printer using a parallel interface, + connect the Centronics cable between the printer and the + computer. The instructions that came with the printer, + the computer, or both should give you complete + guidance. Remember which parallel port you used on the computer. The first parallel port is - ppc0 to &os;; the second - is ppc1, and so on. The + ppc0 to &os;; + the second is ppc1, and so on. The printer device name uses the same scheme: - /dev/lpt0 for the printer - on the first parallel ports etc. + /dev/lpt0 for + the printer on the first parallel ports etc. Serial Ports - To hook up a printer using a serial interface, connect the - proper serial cable between the printer and the computer. The - instructions that came with the printer, the computer, or both - should give you complete guidance. + To hook up a printer using a serial interface, connect + the proper serial cable between the printer and the + computer. The instructions that came with the printer, + the computer, or both should give you complete + guidance. If you are unsure what the proper serial - cable is, you may wish to try one of the following - alternatives: + cable is, you may wish to try one of the + following alternatives: - A modem cable connects each pin - of the connector on one end of the cable straight through - to its corresponding pin of the connector on the other - end. This type of cable is also known as a + A modem cable connects each + pin of the connector on one end of the cable straight + through to its corresponding pin of the connector on + the other end. This type of cable is also known as a DTE-to-DCE cable. - null-modem cable + null-modem + cable - A null-modem cable connects some - pins straight through, swaps others (send data to receive - data, for example), and shorts some internally in each - connector hood. This type of cable is also known as a - DTE-to-DTE cable. + A null-modem cable connects + some pins straight through, swaps others (send data to + receive data, for example), and shorts some internally + in each connector hood. This type of cable is also + known as a DTE-to-DTE cable. - A serial printer cable, required - for some unusual printers, is like the null-modem cable, - but sends some signals to their counterparts instead of - being internally shorted. + A serial printer cable, + required for some unusual printers, is like the + null-modem cable, but sends some signals to their + counterparts instead of being internally + shorted. baud rate parity - flow control protocol - You should also set up the communications parameters for - the printer, usually through front-panel controls or DIP - switches on the printer. Choose the highest + flow control + protocol + You should also set up the communications parameters + for the printer, usually through front-panel controls or + DIP switches on the printer. Choose the highest bps (bits per second, sometimes baud rate) that both your computer - and the printer can support. Choose 7 or 8 data bits; none, - even, or odd parity; and 1 or 2 stop bits. Also choose a flow - control protocol: either none, or XON/XOFF (also known as - in-band or software) flow control. - Remember these settings for the software configuration that + and the printer can support. Choose 7 or 8 data bits; + none, even, or odd parity; and 1 or 2 stop bits. Also + choose a flow control protocol: either none, or XON/XOFF + (also known as in-band or + software) flow control. Remember these + settings for the software configuration that follows. @@ -457,73 +476,76 @@ Software Setup - This section describes the software setup necessary to print - with the LPD spooling system in &os;. - + This section describes the software setup necessary + to print with the LPD spooling + system in &os;. Here is an outline of the steps involved: - Configure your kernel, if necessary, for the port you - are using for the printer; section Kernel Configuration tells - you what you need to do. + Configure your kernel, if necessary, for the port + you are using for the printer; section Kernel Configuration + tells you what you need to do. - Set the communications mode for the parallel port, if - you are using a parallel port; section Set the communications mode for the parallel port, + if you are using a parallel port; section Setting the Communication Mode for the Parallel Port gives details. - Test if the operating system can send data to the printer. - Section Checking Printer - Communications gives some suggestions on how to do - this. + Test if the operating system can send data to the + printer. Section Checking Printer + Communications gives some suggestions on how to + do this. - Set up LPD for the printer by - modifying the file /etc/printcap. You - will find out how to do this later in this chapter. + Set up LPD for the + printer by modifying the file + /etc/printcap. You will find out + how to do this later in this chapter. Kernel Configuration - The operating system kernel is compiled to work with a - specific set of devices. The serial or parallel interface for - your printer is a part of that set. Therefore, it might be - necessary to add support for an additional serial or parallel - port if your kernel is not already configured for one. + The operating system kernel is compiled to work with + a specific set of devices. The serial or parallel + interface for your printer is a part of that set. + Therefore, it might be necessary to add support for an + additional serial or parallel port if your kernel is not + already configured for one. - To find out if the kernel you are currently using supports - a serial interface, type: + To find out if the kernel you are currently using + supports a serial interface, type: &prompt.root; grep sioN /var/run/dmesg.boot - Where N is the number of the - serial port, starting from zero. If you see output similar to - the following: + Where N is the number of + the serial port, starting from zero. If you see output + similar to the following: sio2 at port 0x3e8-0x3ef irq 5 on isa sio2: type 16550A then the kernel supports the port. - To find out if the kernel supports a parallel interface, - type: + To find out if the kernel supports a parallel + interface, type: &prompt.root; grep ppcN /var/run/dmesg.boot - Where N is the number of the - parallel port, starting from zero. If you see output similar - to the following: + Where N is the number of + the parallel port, starting from zero. If you see output + similar to the following: ppc0: <Parallel port> at port 0x378-0x37f irq 7 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode @@ -531,13 +553,13 @@ ppc0: FIFO with 16/16/8 bytes threshold< then the kernel supports the port. - You might have to reconfigure your kernel in order for the - operating system to recognize and use the parallel or serial - port you are using for the printer. + You might have to reconfigure your kernel in order + for the operating system to recognize and use the parallel + or serial port you are using for the printer. To add support for a serial port, see the section on - kernel configuration. To add support for a parallel port, see - that section and the section that + kernel configuration. To add support for a parallel port, + see that section and the section that follows. @@ -546,8 +568,8 @@ ppc0: FIFO with 16/16/8 bytes threshold< Setting the Communication Mode for the Parallel Port - When you are using the parallel interface, you can choose - whether &os; should use interrupt-driven or polled + When you are using the parallel interface, you can + choose whether &os; should use interrupt-driven or polled communication with the printer. The generic printer device driver (&man.lpt.4;) on &os; uses the &man.ppbus.4; system, which controls the port @@ -555,10 +577,10 @@ ppc0: FIFO with 16/16/8 bytes threshold< - The interrupt-driven method is - the default with the GENERIC kernel. With this method, - the operating system uses an IRQ line to determine when - the printer is ready for data. + The interrupt-driven method + is the default with the GENERIC kernel. With this + method, the operating system uses an IRQ line to + determine when the printer is ready for data. @@ -582,27 +604,27 @@ ppc0: FIFO with 16/16/8 bytes threshold< program. To set the communications mode by configuring - the kernel: + the kernel: Edit your kernel configuration file. Look for an ppc0 entry. If you are setting up the second parallel port, use ppc1 - instead. Use ppc2 for the third port, - and so on. + instead. Use ppc2 for the third + port, and so on. - If you want interrupt-driven mode, edit the following - line: + If you want interrupt-driven mode, edit the + following line: hint.ppc.0.irq="N" - in the /boot/device.hints file - and replace N with the right - IRQ number. The kernel configuration file must - also contain the &man.ppc.4; driver: + in the /boot/device.hints + file and replace N with + the right IRQ number. The kernel configuration file + must also contain the &man.ppc.4; driver: device ppc @@ -626,9 +648,10 @@ ppc0: FIFO with 16/16/8 bytes threshold< - Save the file. Then configure, build, and install the - kernel, then reboot. See kernel - configuration for more details. + Save the file. Then configure, build, and install + the kernel, then reboot. See kernel configuration + for more details. @@ -651,7 +674,7 @@ ppc0: FIFO with 16/16/8 bytes threshold< &prompt.root; lptcontrol /dev/lptN to set polled-mode for - lptN. + lptN. @@ -685,19 +708,19 @@ ppc0: FIFO with 16/16/8 bytes threshold< (Is this thing working?) show showpage - The above &postscript; code can be placed into a file and - used as shown in the examples appearing in the following + The above &postscript; code can be placed into a file + and used as shown in the examples appearing in the following sections. PCL - When this document refers to a printer language, it is - assuming a language like &postscript;, and not Hewlett + When this document refers to a printer language, it + is assuming a language like &postscript;, and not Hewlett Packard's PCL. Although PCL has great functionality, you can intermingle plain text with its escape sequences. - &postscript; cannot directly print plain text, and that is the - kind of printer language for which we must make special - accommodations. + &postscript; cannot directly print plain text, and that + is the kind of printer language for which we must make + special accommodations. @@ -712,11 +735,12 @@ showpage port. To test a printer on a parallel - port: + port: - Become root with &man.su.1;. + Become root with + &man.su.1;. @@ -729,33 +753,35 @@ showpage &prompt.root; lptest > /dev/lptN - Where N is the number - of the parallel port, starting from zero. + Where N is the + number of the parallel port, starting from + zero. - If the printer understands &postscript; or other - printer language, then send a small program to the - printer. Type: + If the printer understands &postscript; or + other printer language, then send a small program + to the printer. Type: &prompt.root; cat > /dev/lptN Then, line by line, type the program - carefully as you cannot edit a - line once you have pressed RETURN - or ENTER. When you have finished + carefully as you cannot edit + a line once you have pressed + RETURN or + ENTER. When you have finished entering the program, press - CONTROL+D, or whatever your end - of file key is. + CONTROL+D, or whatever your + end of file key is. - Alternatively, you can put the program in a file - and type: + Alternatively, you can put the program in a + file and type: &prompt.root; cat file > /dev/lptN Where file is the - name of the file containing the program you want to - send to the printer. + name of the file containing the program you want + to send to the printer. @@ -777,35 +803,37 @@ showpage communicate with a printer on a serial port. To test a printer on a serial - port: + port: - Become root with &man.su.1;. + Become root with + &man.su.1;. - Edit the file /etc/remote. Add - the following entry: + Edit the file /etc/remote. + Add the following entry: printer:dv=/dev/port:br#bps-rate:pa=parity bits-per-second serial port parity - Where port is the device - entry for the serial port (ttyu0, - ttyu1, etc.), - bps-rate is the - bits-per-second rate at which the printer communicates, - and parity is the parity - required by the printer (either even, - odd, none, or + Where port is the + device entry for the serial port + (ttyu0, ttyu1, + etc.), bps-rate is the + bits-per-second rate at which the printer + communicates, and parity + is the parity required by the printer (either + even, odd, + none, or zero). Here is a sample entry for a printer connected via - a serial line to the third serial port at 19200 bps - with no parity: + a serial line to the third serial port at + 19200 bps with no parity: printer:dv=/dev/ttyu2:br#19200:pa=none @@ -818,8 +846,11 @@ showpage If this step does not work, edit the file /etc/remote again and try using - /dev/cuaaN instead of - /dev/ttyuN. + /dev/cuaaN + instead of + /dev/ttyuN. @@ -834,18 +865,19 @@ showpage - If the printer understands &postscript; or other - printer language, then send a small program to the - printer. Type the program, line by line, + If the printer understands &postscript; or + other printer language, then send a small program + to the printer. Type the program, line by line, very carefully as backspacing or other editing keys may be significant to the printer. You may also need to type a special end-of-file key for the printer so it knows it received the whole program. For &postscript; - printers, press CONTROL+D. + printers, press + CONTROL+D. - Alternatively, you can put the program in a file - and type: + Alternatively, you can put the program in a + file and type: &prompt.user; >file @@ -864,43 +896,45 @@ showpage - Enabling the Spooler: the <filename>/etc/printcap</filename> - File + Enabling the Spooler: the + <filename>/etc/printcap</filename> File + + At this point, your printer should be hooked up, your + kernel configured to communicate with it (if necessary), + and you have been able to send some simple data to the + printer. Now, we are ready to configure + LPD to control access to your + printer. - At this point, your printer should be hooked up, your kernel - configured to communicate with it (if necessary), and you have - been able to send some simple data to the printer. Now, we are - ready to configure LPD to control access - to your printer. - - You configure LPD by editing the file - /etc/printcap. The - LPD spooling system - reads this file each time the spooler is used, so updates to the + You configure LPD by editing + the file /etc/printcap. The + LPD spooling system reads this + file each time the spooler is used, so updates to the file take immediate effect. printers capabilities - The format of the &man.printcap.5; file is straightforward. - Use your favorite text editor to make changes to - /etc/printcap. The format is identical to - other capability files like + The format of the &man.printcap.5; file is + straightforward. Use your favorite text editor to make + changes to /etc/printcap. The format + is identical to other capability files like /usr/share/misc/termcap and /etc/remote. For complete information about the format, see the &man.cgetent.3;. - The simple spooler configuration consists of the following - steps: + The simple spooler configuration consists of the + following steps: Pick a name (and a few convenient aliases) for the printer, and put them in the /etc/printcap file; see the *** DIFF OUTPUT TRUNCATED AT 1000 LINES *** From owner-svn-doc-all@FreeBSD.ORG Fri Jan 25 17:36:49 2013 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 45A2B13C; Fri, 25 Jan 2013 17:36:49 +0000 (UTC) (envelope-from kaduk@mit.edu) Received: from dmz-mailsec-scanner-4.mit.edu (DMZ-MAILSEC-SCANNER-4.MIT.EDU [18.9.25.15]) by mx1.freebsd.org (Postfix) with ESMTP id B92DEC12; Fri, 25 Jan 2013 17:36:48 +0000 (UTC) X-AuditID: 1209190f-b7f586d000000915-38-5102c2afec7b Received: from mailhub-auth-4.mit.edu ( [18.7.62.39]) by dmz-mailsec-scanner-4.mit.edu (Symantec Messaging Gateway) with SMTP id FD.2D.02325.FA2C2015; Fri, 25 Jan 2013 12:36:47 -0500 (EST) Received: from outgoing.mit.edu (OUTGOING-AUTH.MIT.EDU [18.7.22.103]) by mailhub-auth-4.mit.edu (8.13.8/8.9.2) with ESMTP id r0PHalu2028918; Fri, 25 Jan 2013 12:36:47 -0500 Received: from multics.mit.edu (SYSTEM-LOW-SIPB.MIT.EDU [18.187.2.37]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.6/8.12.4) with ESMTP id r0PHajeo017218 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Fri, 25 Jan 2013 12:36:46 -0500 (EST) Received: (from kaduk@localhost) by multics.mit.edu (8.12.9.20060308) id r0PHahoN019782; Fri, 25 Jan 2013 12:36:43 -0500 (EST) Date: Fri, 25 Jan 2013 12:36:43 -0500 (EST) From: Benjamin Kaduk To: Eitan Adler Subject: Re: svn commit: r40736 - head/en_US.ISO8859-1/books/faq In-Reply-To: <201301241734.r0OHYuJe022211@svn.freebsd.org> Message-ID: References: <201301241734.r0OHYuJe022211@svn.freebsd.org> User-Agent: Alpine 1.10 (GSO 962 2008-03-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrDIsWRmVeSWpSXmKPExsUixG6nrrv+EFOgwd4/BhY/Ph5istj1dw6z xY1F+5ksdvf3MjuweMz4NJ8lgDGKyyYlNSezLLVI3y6BK2Pa/x7mgn7hitedl5gbGG/zdTFy ckgImEjMejSdHcIWk7hwbz1bFyMXh5DAPkaJh42f2EASQgIbGCX+3a2FSJxgknj4fzYrhNPA KNE8q4Oli5GDg0VAW+LpygKQBjYBFYmZbzaCNYsA2d/3/2QCsZkFoiT2LG1kBbGFBRwkns84 zgJicwpYSUw7d5oJZAwvUPzENA+IvZYSC3d/AjtOVEBHYvX+KWDlvAKCEidnPmGBGGkpce7P dbYJjIKzkKRmIUktYGRaxSibklulm5uYmVOcmqxbnJyYl5dapGuil5tZopeaUrqJERSwnJL8 Oxi/HVQ6xCjAwajEw+uxgClQiDWxrLgy9xCjJAeTkiiv+wGgEF9SfkplRmJxRnxRaU5q8SFG CQ5mJRFeGROgHG9KYmVValE+TEqag0VJnPdqyk1/IYH0xJLU7NTUgtQimKwMB4eSBC8DMDKF BItS01Mr0jJzShDSTBycIMN5gIbfPggyvLggMbc4Mx0if4pRl2Pxie7njEIsefl5qVLivF9A igRAijJK8+DmwBLNK0ZxoLeEeblA1vEAkxTcpFdAS5iAluyf9T8AaElJIkJKqoGx5qmB9OuP JwwiFRU6j397tjkwdtmcIKWwgOdnv5/oO9TM8bRoanOewGHOANGjs+4urr5rUdkefIetfndQ C99UqYznfSkBn/ck6+2aEr4sXP/yelf5zRELPt8SMen8PumQXe3CVwK2pbU3p+3jlvgtvmYn p81zF4nI9CRewyffb3mYOgquFctVYinOSDTUYi4qTgQAMHubXQ8DAAA= Cc: svn-doc-head@freebsd.org, svn-doc-all@freebsd.org, doc-committers@freebsd.org X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Jan 2013 17:36:49 -0000 On Thu, 24 Jan 2013, Eitan Adler wrote: > Author: eadler > Date: Thu Jan 24 17:34:55 2013 > New Revision: 40736 > URL: http://svnweb.freebsd.org/changeset/doc/40736 > > Log: > Remove install-bad-blocks: > > 95% bogus, user-controlled bad block mapping stopped being a > thing about 20 years ago Was the removal of boot-floppy-strangeness intentional as well? It looks quite poorly written regardless... -Ben > > Noted by: scottl > Approved by: bcr (mentor, implicit) > > Modified: > head/en_US.ISO8859-1/books/faq/book.xml > > Modified: head/en_US.ISO8859-1/books/faq/book.xml > ============================================================================== > --- head/en_US.ISO8859-1/books/faq/book.xml Thu Jan 24 15:03:30 2013 (r40735) > +++ head/en_US.ISO8859-1/books/faq/book.xml Thu Jan 24 17:34:55 2013 (r40736) > @@ -1382,41 +1382,6 @@ > > > > - > - Can I install on a disk with bad blocks? > - > - > - > - You can, but it is a bad idea. > - > - If you are seeing bad block errors with a modern IDE > - drive, chances are the drive is going to die very soon (the > - drive's internal remapping functions are no longer > - sufficient to fix the bad blocks, which means the disk is > - heavily corrupted); we suggest you buy a new hard > - drive. > - > - > - > - > - > - Strange things happen when I boot the install disk! > - What is happening? > - > - > - > - If you are seeing things like the machine grinding to a > - halt or spontaneously rebooting when you try to boot the > - &os; installer, make sure that the SHA256 hash of > - the image matches the one on the website. If you > - accidently downloaded the disk image in binary (or > - image) mode the will be corrupted. (Do not be embarrassed, > - even the best of us have accidentally downloaded a binary > - file in ASCII mode at least once!) > - > - > - > - > > I booted from my ATAPI CD-ROM, but the install program > says no CD-ROM is found. Where did it go? > From owner-svn-doc-all@FreeBSD.ORG Fri Jan 25 18:30:42 2013 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id CDCC1CD3 for ; Fri, 25 Jan 2013 18:30:42 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: from mail-vb0-f45.google.com (mail-vb0-f45.google.com [209.85.212.45]) by mx1.freebsd.org (Postfix) with ESMTP id 8CCF4F68 for ; Fri, 25 Jan 2013 18:30:42 +0000 (UTC) Received: by mail-vb0-f45.google.com with SMTP id p1so500147vbi.18 for ; Fri, 25 Jan 2013 10:30:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eitanadler.com; s=0xdeadbeef; h=x-received:mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type; bh=gRb5SWlpa7+Pqq5JykRqhY/gq7HtZnarc1JMUbSohYc=; b=aYtCPcnc0L8+aOkZ5gG+UgkXxThyOjonTwu3eFBF7N6gcgZ9ijPocLV8IdYBMfyBGd eB1jkHly4OdEHDMnQ9Rf7QQXGUaJ655PogpR/qReFJLGYlQkkBdMvJYbEydr5KZXq3UK hkSsRjOru5kqI9ly85Xoo9mK5ybR/cMu/Fjdo= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:cc:content-type :x-gm-message-state; bh=gRb5SWlpa7+Pqq5JykRqhY/gq7HtZnarc1JMUbSohYc=; b=GjqJTtSBhavbleHBmiNJxeeCWBuwMut3g8/VkYQiGnPjIPMrLOl0RUSM/uZkD9kxT3 DO+AqjziM5UiFupNyfv1idwBN+cDt1ILKbD1hD9pNPrUNlYhe7Hsc/QqRG5O/3VPwkwK GO12p3eIjmv16FkloN1ER1OQNHGpzNhQj536Z5GTvqRbiTZjg9JSC4sCrqjRW6bfYlmL hkmsJfyeIsXgigxKP9bXI4CV2mueEIy3LvP1VVlAzf15/XSM/AXa9vKlx3ZqQ64a1tNM p2OMCdLFzbsWiMHH3ny3B51jzK0VUNWYI+Dj2KLqkqJ4ChyRtFsgwE5ZXuU2GF6YPnb0 0t8Q== X-Received: by 10.220.238.139 with SMTP id ks11mr6905454vcb.49.1359138638105; Fri, 25 Jan 2013 10:30:38 -0800 (PST) MIME-Version: 1.0 Sender: lists@eitanadler.com Received: by 10.220.195.70 with HTTP; Fri, 25 Jan 2013 10:30:07 -0800 (PST) In-Reply-To: References: <201301241734.r0OHYuJe022211@svn.freebsd.org> From: Eitan Adler Date: Fri, 25 Jan 2013 13:30:07 -0500 X-Google-Sender-Auth: RdxRwIgZ0BD3Ls-cfwEg4y_ageY Message-ID: Subject: Re: svn commit: r40736 - head/en_US.ISO8859-1/books/faq To: Benjamin Kaduk Content-Type: text/plain; charset=UTF-8 X-Gm-Message-State: ALoCoQl6sa3OIzCUqPnc55XYq7M4zlb5WmZolylgW41vJVcl/7VilYAKXfphaHm5dSIVAotMC0FH Cc: svn-doc-head@freebsd.org, svn-doc-all@freebsd.org, doc-committers@freebsd.org X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Jan 2013 18:30:42 -0000 On 25 January 2013 12:36, Benjamin Kaduk wrote: > On Thu, 24 Jan 2013, Eitan Adler wrote: > Was the removal of boot-floppy-strangeness intentional as well? > It looks quite poorly written regardless... I had intended to remove this was a separate commit message. :-\ -- Eitan Adler Source, Ports, Doc committer Bugmeister, Ports Security teams From owner-svn-doc-all@FreeBSD.ORG Sat Jan 26 01:04:50 2013 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 39868D0F; Sat, 26 Jan 2013 01:04:50 +0000 (UTC) (envelope-from jgh@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id 21566633; Sat, 26 Jan 2013 01:04:50 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.5/8.14.5) with ESMTP id r0Q14ogF091185; Sat, 26 Jan 2013 01:04:50 GMT (envelope-from jgh@svn.freebsd.org) Received: (from jgh@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r0Q14oIa091184; Sat, 26 Jan 2013 01:04:50 GMT (envelope-from jgh@svn.freebsd.org) Message-Id: <201301260104.r0Q14oIa091184@svn.freebsd.org> From: Jason Helfman Date: Sat, 26 Jan 2013 01:04:49 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40751 - head/en_US.ISO8859-1/articles/contributors X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 26 Jan 2013 01:04:50 -0000 Author: jgh (ports committer) Date: Sat Jan 26 01:04:49 2013 New Revision: 40751 URL: http://svnweb.freebsd.org/changeset/doc/40751 Log: - add Matt Stofko for security/libyubikey PR: 175495 Modified: head/en_US.ISO8859-1/articles/contributors/contrib.additional.xml Modified: head/en_US.ISO8859-1/articles/contributors/contrib.additional.xml ============================================================================== --- head/en_US.ISO8859-1/articles/contributors/contrib.additional.xml Fri Jan 25 17:11:04 2013 (r40750) +++ head/en_US.ISO8859-1/articles/contributors/contrib.additional.xml Sat Jan 26 01:04:49 2013 (r40751) @@ -6476,6 +6476,11 @@ + Matt Stofko + matt@mjslabs.com + + + Matt Thomas matt@3am-software.com From owner-svn-doc-all@FreeBSD.ORG Sat Jan 26 10:28:09 2013 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 5976B2E3; Sat, 26 Jan 2013 10:28:09 +0000 (UTC) (envelope-from marck@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id 33570960; Sat, 26 Jan 2013 10:28:09 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.5/8.14.5) with ESMTP id r0QAS9wg058657; Sat, 26 Jan 2013 10:28:09 GMT (envelope-from marck@svn.freebsd.org) Received: (from marck@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r0QAS8xZ058655; Sat, 26 Jan 2013 10:28:08 GMT (envelope-from marck@svn.freebsd.org) Message-Id: <201301261028.r0QAS8xZ058655@svn.freebsd.org> From: Dmitry Morozovsky Date: Sat, 26 Jan 2013 10:28:08 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40752 - head/share/pgpkeys X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 26 Jan 2013 10:28:09 -0000 Author: marck Date: Sat Jan 26 10:28:08 2013 New Revision: 40752 URL: http://svnweb.freebsd.org/changeset/doc/40752 Log: A bit of cleanup: yar's account had been removed per his request a while ago. Remove his PGP key. Deleted: head/share/pgpkeys/yar.key Modified: head/share/pgpkeys/pgpkeys-developers.xml head/share/pgpkeys/pgpkeys.ent Modified: head/share/pgpkeys/pgpkeys-developers.xml ============================================================================== --- head/share/pgpkeys/pgpkeys-developers.xml Sat Jan 26 01:04:49 2013 (r40751) +++ head/share/pgpkeys/pgpkeys-developers.xml Sat Jan 26 10:28:08 2013 (r40752) @@ -1786,11 +1786,6 @@ &pgpkey.flz; - - &a.yar; - &pgpkey.yar; - - &a.jilles; &pgpkey.jilles; Modified: head/share/pgpkeys/pgpkeys.ent ============================================================================== --- head/share/pgpkeys/pgpkeys.ent Sat Jan 26 01:04:49 2013 (r40751) +++ head/share/pgpkeys/pgpkeys.ent Sat Jan 26 10:28:08 2013 (r40752) @@ -402,7 +402,6 @@ - From owner-svn-doc-all@FreeBSD.ORG Sat Jan 26 18:58:04 2013 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 9CDDBC23; Sat, 26 Jan 2013 18:58:04 +0000 (UTC) (envelope-from eadler@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id 78226B46; Sat, 26 Jan 2013 18:58:04 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.5/8.14.5) with ESMTP id r0QIw4Sk013844; Sat, 26 Jan 2013 18:58:04 GMT (envelope-from eadler@svn.freebsd.org) Received: (from eadler@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r0QIw4rU013843; Sat, 26 Jan 2013 18:58:04 GMT (envelope-from eadler@svn.freebsd.org) Message-Id: <201301261858.r0QIw4rU013843@svn.freebsd.org> From: Eitan Adler Date: Sat, 26 Jan 2013 18:58:04 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40753 - head/en_US.ISO8859-1/books/faq X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 26 Jan 2013 18:58:04 -0000 Author: eadler Date: Sat Jan 26 18:58:03 2013 New Revision: 40753 URL: http://svnweb.freebsd.org/changeset/doc/40753 Log: missing-os talks about CHS addressing which has been obsolete for 10-15 years. Noted by: scottl Approved by: bcr (mentor, implicit) Modified: head/en_US.ISO8859-1/books/faq/book.xml Modified: head/en_US.ISO8859-1/books/faq/book.xml ============================================================================== --- head/en_US.ISO8859-1/books/faq/book.xml Sat Jan 26 10:28:08 2013 (r40752) +++ head/en_US.ISO8859-1/books/faq/book.xml Sat Jan 26 18:58:03 2013 (r40753) @@ -1413,22 +1413,6 @@ - - When I boot &os; for the first time after install I get - Missing Operating System. What is - happening? - - - - This is classically a case of &os; and some other - OS conflicting over their ideas of disk - geometry. You will have to - reinstall &os;, but obeying the instructions given above - will almost always get you going. - - - - Do I need to install the source? From owner-svn-doc-all@FreeBSD.ORG Sat Jan 26 19:35:23 2013 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 2F08B354; Sat, 26 Jan 2013 19:35:23 +0000 (UTC) (envelope-from eadler@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id F0AC2CC7; Sat, 26 Jan 2013 19:35:22 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.5/8.14.5) with ESMTP id r0QJZMHT025958; Sat, 26 Jan 2013 19:35:22 GMT (envelope-from eadler@svn.freebsd.org) Received: (from eadler@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r0QJZMEU025957; Sat, 26 Jan 2013 19:35:22 GMT (envelope-from eadler@svn.freebsd.org) Message-Id: <201301261935.r0QJZMEU025957@svn.freebsd.org> From: Eitan Adler Date: Sat, 26 Jan 2013 19:35:22 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40754 - head/en_US.ISO8859-1/books/faq X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 26 Jan 2013 19:35:23 -0000 Author: eadler Date: Sat Jan 26 19:35:22 2013 New Revision: 40754 URL: http://svnweb.freebsd.org/changeset/doc/40754 Log: nlist failed is not an FAQ these days. Noted by: imp Approved by: bcr (mentor, implicit) Modified: head/en_US.ISO8859-1/books/faq/book.xml Modified: head/en_US.ISO8859-1/books/faq/book.xml ============================================================================== --- head/en_US.ISO8859-1/books/faq/book.xml Sat Jan 26 18:58:03 2013 (r40753) +++ head/en_US.ISO8859-1/books/faq/book.xml Sat Jan 26 19:35:22 2013 (r40754) @@ -2530,44 +2530,6 @@ bindkey ^[[3~ delete-char # for xterm

    - - Why do I get the error nlist - failed when running, for example, - top or systat? - - - - The problem is that the application you are trying to - run is looking for a specific kernel symbol, but, for whatever - reason, cannot find it; this error stems from one of two - problems: - - - - Your kernel and userland are not synchronized (i.e., - you built a new kernel but did not do an - installworld, or vice versa), - and thus the symbol table is different from what the - user application thinks it is. If this is the case, - simply complete the upgrade process (see - /usr/src/UPDATING for the correct - sequence). - - - - You are not using /boot/loader to - load your kernel, but doing it directly from - boot2 (see &man.boot.8;). While - there is nothing wrong with bypassing - /boot/loader, it generally does a - better job of making the kernel symbols available to - user applications. - - - - - - Why does it take so long to connect to my computer via ssh or telnet? From owner-svn-doc-all@FreeBSD.ORG Sat Jan 26 19:35:25 2013 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 70211355; Sat, 26 Jan 2013 19:35:25 +0000 (UTC) (envelope-from eadler@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id 3F5E8CC8; Sat, 26 Jan 2013 19:35:25 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.5/8.14.5) with ESMTP id r0QJZPj2025994; Sat, 26 Jan 2013 19:35:25 GMT (envelope-from eadler@svn.freebsd.org) Received: (from eadler@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r0QJZPRx025993; Sat, 26 Jan 2013 19:35:25 GMT (envelope-from eadler@svn.freebsd.org) Message-Id: <201301261935.r0QJZPRx025993@svn.freebsd.org> From: Eitan Adler Date: Sat, 26 Jan 2013 19:35:25 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40755 - head/en_US.ISO8859-1/books/faq X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 26 Jan 2013 19:35:25 -0000 Author: eadler Date: Sat Jan 26 19:35:24 2013 New Revision: 40755 URL: http://svnweb.freebsd.org/changeset/doc/40755 Log: Old ATA devices don't solicit many questions these days. Noted by: rpaulo, imp Approved by: bcr (mentor, implicit) Modified: head/en_US.ISO8859-1/books/faq/book.xml Modified: head/en_US.ISO8859-1/books/faq/book.xml ============================================================================== --- head/en_US.ISO8859-1/books/faq/book.xml Sat Jan 26 19:35:22 2013 (r40754) +++ head/en_US.ISO8859-1/books/faq/book.xml Sat Jan 26 19:35:24 2013 (r40755) @@ -2700,41 +2700,6 @@ kern.timecounter.hardware: TSC -> i82 - - What are UDMA ICRC errors, and - how do I fix them? - - - - The &man.ata.4; driver reports UDMA - ICRC errors when a DMA transfer to or from a drive - is corrupted. The driver will retry the operation a few - times. Should the retries fail, it will switch from DMA to - the slower PIO mode of communication with the device. - - The problem can be caused by many factors, although - perhaps the most common cause is faulty or incorrect - cabling. Check that the ATA cables are undamaged and rated - for the Ultra DMA mode in use. If you are using - removable drive trays, they must also be compatible. Be - sure that all connections are making good contact. Problems - have also been noticed when an old drive is installed on the - same ATA channel as an Ultra DMA 66 (or faster) - drive. Lastly, these errors can indicate that the drive is - failing. Most drive vendors provide testing software for - their drives, so test your drive, and, if necessary, back up - your data and replace it. - - The &man.atacontrol.8; utility can be used to show and - select the DMA or PIO modes used for each ATA device. In - particular, atacontrol mode - channel will show the - modes in use on a particular ATA channel, where the primary - channel is numbered 0, and so on. - - - - What is a lock order reversal? From owner-svn-doc-all@FreeBSD.ORG Sat Jan 26 20:06:41 2013 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 286F18E2; Sat, 26 Jan 2013 20:06:41 +0000 (UTC) (envelope-from wosch@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id 06AE0DE8; Sat, 26 Jan 2013 20:06:41 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.5/8.14.5) with ESMTP id r0QK6efu034977; Sat, 26 Jan 2013 20:06:40 GMT (envelope-from wosch@svn.freebsd.org) Received: (from wosch@localhost) by svn.freebsd.org (8.14.5/8.14.5/Submit) id r0QK6eMi034976; Sat, 26 Jan 2013 20:06:40 GMT (envelope-from wosch@svn.freebsd.org) Message-Id: <201301262006.r0QK6eMi034976@svn.freebsd.org> From: Wolfram Schneider Date: Sat, 26 Jan 2013 20:06:40 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r40756 - head/en_US.ISO8859-1/htdocs/cgi X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 26 Jan 2013 20:06:41 -0000 Author: wosch Date: Sat Jan 26 20:06:40 2013 New Revision: 40756 URL: http://svnweb.freebsd.org/changeset/doc/40756 Log: FreeBSD 9.1-RELEASE is the defautl release cleanup -stable releases Modified: head/en_US.ISO8859-1/htdocs/cgi/man.cgi Modified: head/en_US.ISO8859-1/htdocs/cgi/man.cgi ============================================================================== --- head/en_US.ISO8859-1/htdocs/cgi/man.cgi Sat Jan 26 19:35:24 2013 (r40755) +++ head/en_US.ISO8859-1/htdocs/cgi/man.cgi Sat Jan 26 20:06:40 2013 (r40756) @@ -206,7 +206,7 @@ foreach my $os ( keys %$sectionpath ) { ); $manLocalDir = '/usr/local/www/bsddoc/man'; -$manPathDefault = 'FreeBSD 9.0-RELEASE'; +$manPathDefault = 'FreeBSD 9.1-RELEASE'; %manPath = ( 'FreeBSD 9.0-RELEASE and Ports', @@ -582,6 +582,7 @@ my %valid_arch = map { $_ => 1 } my $default_arch = 'i386'; my %arch = ( +'FreeBSD 9.1-RELEASE' => { 'default' => 'i386', 'arch' => [qw/amd64 arm i386 powerpc sparc64/] } , 'FreeBSD 9.0-RELEASE' => { 'default' => 'i386', 'arch' => [qw/amd64 arm i386 powerpc sparc64/] } , 'FreeBSD 8.3-RELEASE' => { 'default' => 'i386', 'arch' => [qw/amd64 arm i386 powerpc sparc64/] } , 'FreeBSD 8.2-RELEASE' => { 'default' => 'i386', 'arch' => [qw/amd64 arm i386 powerpc sparc64/] } , @@ -613,11 +614,12 @@ while ( ( $key, $val ) = each %manPath ) # keywords must be in lower cases. %manPathAliases = ( - 'freebsd', 'FreeBSD 9.0-RELEASE', - 'freebsd-release', 'FreeBSD 9.0-RELEASE', + 'freebsd', 'FreeBSD 9.1-RELEASE', + 'freebsd-release', 'FreeBSD 9.1-RELEASE', - 'freebsd-stable', 'FreeBSD 8.2-stable', - 'freebsd-stable8', 'FreeBSD 8.2-stable', + 'freebsd-stable', 'FreeBSD 9.1-stable', + 'freebsd-stable9', 'FreeBSD 9.1-stable', + 'freebsd-stable8', 'FreeBSD 8.3-stable', 'freebsd-stable7', 'FreeBSD 7.4-stable', 'freebsd-stable6', 'FreeBSD 6.4-stable',