From owner-svn-doc-head@FreeBSD.ORG Sun Apr 5 15:21:57 2015
Return-Path:
Delivered-To: svn-doc-head@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
[IPv6:2001:1900:2254:206a::19:1])
(using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
(No client certificate requested)
by hub.freebsd.org (Postfix) with ESMTPS id 02A3D54D;
Sun, 5 Apr 2015 15:21:57 +0000 (UTC)
Received: from svn.freebsd.org (svn.freebsd.org
[IPv6:2001:1900:2254:2068::e6a:0])
(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
(Client did not present a certificate)
by mx1.freebsd.org (Postfix) with ESMTPS id E09308DC;
Sun, 5 Apr 2015 15:21:56 +0000 (UTC)
Received: from svn.freebsd.org ([127.0.1.70])
by svn.freebsd.org (8.14.9/8.14.9) with ESMTP id t35FLukL087190;
Sun, 5 Apr 2015 15:21:56 GMT (envelope-from bcr@FreeBSD.org)
Received: (from bcr@localhost)
by svn.freebsd.org (8.14.9/8.14.9/Submit) id t35FLtVR087186;
Sun, 5 Apr 2015 15:21:55 GMT (envelope-from bcr@FreeBSD.org)
Message-Id: <201504051521.t35FLtVR087186@svn.freebsd.org>
X-Authentication-Warning: svn.freebsd.org: bcr set sender to bcr@FreeBSD.org
using -f
From: Benedict Reuschling
Date: Sun, 5 Apr 2015 15:21:55 +0000 (UTC)
To: doc-committers@freebsd.org, svn-doc-all@freebsd.org,
svn-doc-head@freebsd.org
Subject: svn commit: r46472 - in head/de_DE.ISO8859-1/books/handbook: . zfs
X-SVN-Group: doc-head
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
X-BeenThere: svn-doc-head@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: SVN commit messages for the doc tree for head
List-Unsubscribe: ,
List-Archive:
List-Post:
List-Help:
List-Subscribe: ,
X-List-Received-Date: Sun, 05 Apr 2015 15:21:57 -0000
Author: bcr
Date: Sun Apr 5 15:21:54 2015
New Revision: 46472
URL: https://svnweb.freebsd.org/changeset/doc/46472
Log:
This is a complete re-translation of the current HEAD-revision of the
ZFS chapter. Some ZFS terms were translated into german where appropriate,
but most of them (vdev, pool states and such) were left to make it easier
to relate to the ZFS outputs of FreeBSD.
Obtained from: The FreeBSD German Documentation Project
Added:
head/de_DE.ISO8859-1/books/handbook/zfs/
head/de_DE.ISO8859-1/books/handbook/zfs/chapter.xml (contents, props changed)
Modified:
head/de_DE.ISO8859-1/books/handbook/Makefile
head/de_DE.ISO8859-1/books/handbook/book.xml
head/de_DE.ISO8859-1/books/handbook/chapters.ent
Modified: head/de_DE.ISO8859-1/books/handbook/Makefile
==============================================================================
--- head/de_DE.ISO8859-1/books/handbook/Makefile Sat Apr 4 23:40:15 2015 (r46471)
+++ head/de_DE.ISO8859-1/books/handbook/Makefile Sun Apr 5 15:21:54 2015 (r46472)
@@ -243,6 +243,7 @@ SRCS+= dtrace/chapter.xml
SRCS+= eresources/chapter.xml
SRCS+= filesystems/chapter.xml
SRCS+= firewalls/chapter.xml
+SRCS+= zfs/chapter.xml
SRCS+= geom/chapter.xml
SRCS+= install/chapter.xml
SRCS+= introduction/chapter.xml
Modified: head/de_DE.ISO8859-1/books/handbook/book.xml
==============================================================================
--- head/de_DE.ISO8859-1/books/handbook/book.xml Sat Apr 4 23:40:15 2015 (r46471)
+++ head/de_DE.ISO8859-1/books/handbook/book.xml Sun Apr 5 15:21:54 2015 (r46472)
@@ -252,6 +252,7 @@
&chap.audit;
&chap.disks;
&chap.geom;
+ &chap.zfs;
&chap.filesystems;
&chap.vinum;
&chap.virtualization;
Modified: head/de_DE.ISO8859-1/books/handbook/chapters.ent
==============================================================================
--- head/de_DE.ISO8859-1/books/handbook/chapters.ent Sat Apr 4 23:40:15 2015 (r46471)
+++ head/de_DE.ISO8859-1/books/handbook/chapters.ent Sun Apr 5 15:21:54 2015 (r46472)
@@ -43,6 +43,7 @@
+
Added: head/de_DE.ISO8859-1/books/handbook/zfs/chapter.xml
==============================================================================
--- /dev/null 00:00:00 1970 (empty, because file is newly added)
+++ head/de_DE.ISO8859-1/books/handbook/zfs/chapter.xml Sun Apr 5 15:21:54 2015 (r46472)
@@ -0,0 +1,4769 @@
+
+
+
+
+
+
+ Das Z-Dateisystem (ZFS)
+
+
+
+
+ Tom
+ Rhodes
+
+ Geschrieben von
+
+
+
+ Allan
+ Jude
+
+ Geschrieben von
+
+
+
+ Benedict
+ Reuschling
+
+ Geschrieben von
+
+
+
+ Warren
+ Block
+
+ Geschrieben von
+
+
+
+
+
+ Benedict
+ Reuschling
+
+ Übersetzt von
+
+
+
+
+ Das Z-Dateisystem, oder kurz
+ ZFS, ist ein fortgeschrittenes Dateisystem, das
+ entwickelt wurde, um viele der grossen Probleme in vorherigen
+ Entwicklungen zu überwinden.
+
+ Ursprünglich von &sun; entworfen, wird die weitere Entwicklung
+ von ZFS heutzutage als Open Source vom OpenZFS Projekt
+ vorangetrieben.
+
+ ZFS hat drei grosse Entwurfsziele:
+
+
+
+ Datenintegrität: Alle Daten enthalten eine Prüfsumme
+ (checksum) der Daten.
+ Wenn Daten geschrieben werden, wird die Prüfsumme berechnet
+ und zusammen mit den Daten gespeichert. Wenn diese Daten
+ später wieder eingelesen werden, wird diese Prüfsumme erneut
+ berechnet. Falls die Prüfsummen nicht übereinstimmen, wurde
+ ein Datenfehler festgestellt. ZFS wird
+ versuchen, diesen Fehler automatisch zu korrigieren, falls
+ genug Datenredundanz vorhanden ist.
+
+
+
+ Gepoolter Speicher: physikalische Speichermedien werden zu
+ einem Pool zusammengefasst und der Speicherplatz wird von
+ diesem gemeinsam genutzten Pool allokiert. Der Speicherplatz
+ steht allen Dateisystemen zur Verfügung und kann durch das
+ Hinzufügen von neuen Speichermedien vergrössert werden.
+
+
+
+ Geschwindigkeit: mehrere Zwischenspeichermechanismen
+ sorgen für erhöhte Geschwindigkeit. Der ARC ist ein weiterentwickelter,
+ hauptspeicherbasierter Zwischenspeicher für Leseanfragen. Auf
+ einer zweiten Stufe kann ein plattenbasierter L2ARC-Lesezwischenspeicher
+ hinzugefügt werden. Zusätzlich ist auch noch ein
+ plattenbasierter, synchroner Schreibzwischenspeicher
+ verfügbar, der sog. ZIL.
+
+
+
+ Eine vollständige Liste aller Eigenschaften und der
+ dazugehörigen Terminologie ist in zu
+ sehen.
+
+
+ Was ZFS anders macht
+
+ ZFS ist signifikant unterschiedlich zu
+ allen bisherigen Dateisystemen, weil es mehr als nur ein
+ Dateisystem ist. Durch die Kombination von traditionell
+ getrennten Rollen von Volumenmanager und Dateisystem ist
+ ZFS mit einzigartigen Vorteilen ausgestattet.
+ Das Dateisystem besitzt jetzt Kentniss von der zugrundeliegenden
+ Struktur der Speichermedien. Traditionelle Dateisysteme konnten
+ nur auf einer einzigen Platte gleichzeitig angelegt werden.
+ Falls es zwei Festplatten gab, mussten auch zwei getrennte
+ Dateisysteme erstellt werden. In einer traditionellen
+ Hardware-RAID-Konfiguration wurde dieses
+ Problem umgangen, indem dem Betriebssystem nur eine einzige
+ logische Platte angezeigt wurde, die sich aus dem Speicherplatz
+ von der Anzahl an physischen Platten zusammensetzte, auf dem
+ dann das Betriebssystem ein Dateisystem erstellte. Sogar im
+ Fall von Software-RAID-Lösungen, wie die, die
+ von GEOM bereitgestellt werden, war das
+ UFS-Dateisystem der Ansicht, dass es auf nur
+ einem einzigen Gerät angelegt wurde. ZFS'
+ Kombination eines Volumenmanagers und eines Dateisystems löst
+ dies und erlaubt das Erstellen von vielen Dateisystemen, die
+ sich alle den darunterliegenden Pool aus verfügbarem Speicher
+ teilen. Einer der grössten Vorteile von ZFS'
+ Kentniss des physikalischen Layouts der Platten ist, dass
+ existierende Dateisysteme automatisch wachsen können, wenn
+ zusätzliche Platten zum Pool hinzugefügt werden. Dieser neue
+ Speicherplatz wird dann allen Dateisystemen zur Verfügung
+ gestellt. ZFS besitzt ebenfalls eine Menge
+ an unterschiedlichen Eigenschaften, die für jedes Dateisystem
+ angepasst werden könnnen, was viele Vorteile bringt, wenn man
+ unterschiedliche Dateisysteme und Datasets anlegt, anstatt ein
+ einziges, monolitisches Dateisystem zu erzeugen.
+
+
+
+ Schnellstartanleitung
+
+ Es existiert ein Startmechanismus, der es &os; erlaubt,
+ ZFS-Pools während der Systeminitialisierung
+ einzubinden. Um diesen zu aktivieren, fügen Sie diese Zeile
+ in /etc/rc.conf ein:
+
+ zfs_enable="YES"
+
+ Starten Sie dann den Dienst:
+
+ &prompt.root; service zfs start
+
+ Die Beispiele in diesem Abschnitt gehen von drei
+ SCSI-Platten mit den Gerätenamen
+ da0,
+ da1 und
+ da2 aus. Nutzer
+ von SATA-Hardware sollten stattdessen die
+ Bezeichnung ada
+ als Gerätenamen verwenden.
+
+
+ Pools mit einer Platte
+
+ Um einen einfachen, nicht-redundanten Pool mit einem
+ einzigen Gerät anzulegen, geben Sie folgendes ein:
+
+ &prompt.root; zpool create example/dev/da0
+
+ Um den neuen Pool anzuzeigen, prüfen Sie die Ausgabe von
+ df:
+
+ &prompt.root; df
+Filesystem 1K-blocks Used Avail Capacity Mounted on
+/dev/ad0s1a 2026030 235230 1628718 13% /
+devfs 1 1 0 100% /dev
+/dev/ad0s1d 54098308 1032846 48737598 2% /usr
+example 17547136 0 17547136 0% /example
+
+ Diese Ausgabe zeigt, dass der
+ example-Pool erstellt und eingehängt wurde.
+ Er ist nun als Dateisystem verfügbar. Dateien können darauf
+ angelegt werden und Anwender können sich den Inhalt
+ ansehen:
+
+ &prompt.root; cd /example
+&prompt.root; ls
+&prompt.root; touch testfile
+&prompt.root; ls -al
+total 4
+drwxr-xr-x 2 root wheel 3 Aug 29 23:15 .
+drwxr-xr-x 21 root wheel 512 Aug 29 23:12 ..
+-rw-r--r-- 1 root wheel 0 Aug 29 23:15 testfile
+
+ Allerdings nutzt dieser Pool noch keine der Vorteile von
+ ZFS. Um ein Dataset auf diesem Pool mit
+ aktivierter Komprimierung zu erzeugen, geben Sie ein:
+
+ &prompt.root; zfs create example/compressed
+&prompt.root; zfs set compression=gzip example/compressed
+
+ Das example/compressed-Dataset ist nun
+ ein komprimiertes ZFS-Dateisystem.
+ Versuchen Sie, ein paar grosse Dateien auf
+ /example/compressed zu kopieren.
+
+ Deaktivieren lässt sich die Komprimierung durch:
+
+ &prompt.root; zfs set compression=off example/compressed
+
+ Um ein Dateisystem abzuhängen, verwenden Sie
+ zfs umount und überprüfen Sie dies
+ anschliessend mit df:
+
+ &prompt.root; zfs umount example/compressed
+&prompt.root; df
+Filesystem 1K-blocks Used Avail Capacity Mounted on
+/dev/ad0s1a 2026030 235232 1628716 13% /
+devfs 1 1 0 100% /dev
+/dev/ad0s1d 54098308 1032864 48737580 2% /usr
+example 17547008 0 17547008 0% /example
+
+ Um das Dateisystem wieder einzubinden und erneut verfügbar
+ zu machen, verwenden Sie zfs mount und
+ prüfen Sie erneut mit df:
+
+ &prompt.root; zfs mount example/compressed
+&prompt.root; df
+Filesystem 1K-blocks Used Avail Capacity Mounted on
+/dev/ad0s1a 2026030 235234 1628714 13% /
+devfs 1 1 0 100% /dev
+/dev/ad0s1d 54098308 1032864 48737580 2% /usr
+example 17547008 0 17547008 0% /example
+example/compressed 17547008 0 17547008 0% /example/compressed
+
+ Den Pool und die Dateisysteme können Sie auch über die
+ Ausgabe von mount prüfen:
+
+ &prompt.root; mount
+/dev/ad0s1a on / (ufs, local)
+devfs on /dev (devfs, local)
+/dev/ad0s1d on /usr (ufs, local, soft-updates)
+example on /example (zfs, local)
+example/compressed on /example/compressed (zfs, local)
+
+ Nach der Erstellung können ZFS-Datasets
+ wie jedes undere Dateisystem verwendet werden. Jedoch sind
+ jede Menge undere Besonderheiten verfügbar, die individuell
+ auf Dataset-Basis eingestellt sein können. Im Beispiel unten
+ wird ein neues Dateisystem namens data
+ angelegt. Wichtige Dateien werden dort abgespeichert, deshalb
+ wird es so konfiguriert, dass zwei Kopien jedes Datenblocks
+ vorgehalten werden.
+
+ &prompt.root; zfs create example/data
+&prompt.root; zfs set copies=2 example/data
+
+ Es ist jetzt möglich, den Speicherplatzverbrauch der Daten
+ durch die Eingabe von df zu sehen:
+
+ &prompt.root; df
+Filesystem 1K-blocks Used Avail Capacity Mounted on
+/dev/ad0s1a 2026030 235234 1628714 13% /
+devfs 1 1 0 100% /dev
+/dev/ad0s1d 54098308 1032864 48737580 2% /usr
+example 17547008 0 17547008 0% /example
+example/compressed 17547008 0 17547008 0% /example/compressed
+example/data 17547008 0 17547008 0% /example/data
+
+ Sie haben vermutlich bemerkt, dass jedes Dateisystem auf
+ dem Pool die gleiche Menge an verfügbarem Speicherplatz
+ besitzt. Das ist der Grund dafür, dass in diesen Beispielen
+ df verwendet wird, um zu zeigen, dass die
+ Dateisysteme nur die Menge an Speicher verbrauchen, den sie
+ benötigen und alle den gleichen Pool verwenden.
+ ZFS eliminiert Konzepte wie Volumen und
+ Partitionen und erlaubt es mehreren Dateisystemen den gleichen
+ Pool zu belegen.
+
+ Um das Dateisystem zu zerstören und anschliessend den
+ Pool, da dieser nicht mehr benötigt wird, geben Sie
+ ein:
+
+ &prompt.root; zfs destroy example/compressed
+&prompt.root; zfs destroy example/data
+&prompt.root; zpool destroy example
+
+
+
+ RAID-Z
+
+ Platten fallen aus. Eine Methode, um Datenverlust durch
+ Festplattenausfall zu vermeiden, ist die Verwendung von
+ RAID. ZFS unterstützt
+ dies in seiner Poolgestaltung. Pools mit
+ RAID-Z benötigen drei oder mehr Platten,
+ bieten aber auch mehr nutzbaren Speicher als gespiegelte
+ Pools.
+
+ Dieses Beispiel erstellt einen
+ RAID-Z-Pool, indem es die Platten angibt,
+ die dem Pool hinzugefügt werden sollen:
+
+ &prompt.root; zpool create storage raidz da0 da1 da2
+
+
+ &sun; empfiehlt, dass die Anzahl der Geräte in einer
+ RAID-Z Konfiguration zwischen drei und
+ neun beträgt. Für Umgebungen, die einen einzelnen Pool
+ enötigen, der aus 10 oder mehr Platten besteht, sollten Sie
+ in Erwägung ziehen, diesen in kleinere
+ RAID-Z-Gruppen aufzuteilen. Falls nur
+ zwei Platten verfügbar sind und Redundanz benötigt wird,
+ ziehen Sie die Verwendung eines
+ ZFS-Spiegels (mirror) in Betracht. Lesen
+ Sie dazu &man.zpool.8;, um weitere Details zu
+ erhalten.
+
+
+ Das vorherige Beispiel erstellte einen ZPool namens
+ storage. Dieses Beispiel erzeugt ein neues
+ Dateisystem, genannt home, in diesem
+ Pool:
+
+ &prompt.root; zfs create storage/home
+
+ Komprimierung und das Vorhalten von mehreren Kopien von
+ Dateien und Verzeichnissen kann aktiviert werden:
+
+ &prompt.root; zfs set copies=2 storage/home
+&prompt.root; zfs set compression=gzip storage/home
+
+ Um dies als das neue Heimatverzeichnis für Anwender zu
+ setzen, kopieren Sie die Benutzerdaten in dieses Verzeichnis
+ und erstellen passende symbolische Verknüpfungen:
+
+ &prompt.root; cp -rp /home/* /storage/home
+&prompt.root; rm -rf /home /usr/home
+&prompt.root; ln -s /storage/home /home
+&prompt.root; ln -s /storage/home /usr/home
+
+ Daten von Anwendern werden nun auf dem frisch erstellten
+ /storage/home abgelegt. Überprüfen Sie
+ dies durch das Anlegen eines neuen Benutzers und das
+ anschliessende Anmelden als dieser Benutzer.
+
+ Versuchen Sie, einen Dateisystemschnappschuss anzulegen,
+ den Sie später wieder zurückrollen können:
+
+ &prompt.root; zfs snapshot storage/home@08-30-08
+
+ Schnappschüsse können nur auf einem Dateisystem angelegt
+ werden, nicht auf einem einzelnen Verzeichnis oder einer
+ Datei.
+
+ Das Zeichen @ ist der Trenner zwischen
+ dem Dateisystem- oder dem Volumennamen. Wenn ein wichtiges
+ Verzeichnis aus Versehen gelöscht wurde, kann das Dateisystem
+ gesichert und dann zu einem früheren Schnappschuss
+ zurückgerollt werden, in welchem das Verzeichnis noch
+ existiert:
+
+ &prompt.root; zfs rollback storage/home@08-30-08
+
+ Um all verfügbaren Schnappschüsse aufzulisten, geben Sie
+ ls im Verzeichnis
+ .zfs/snapshot dieses Dateisystems ein.
+ Beispielsweise lässt sich der zuvor angelegte Schnappschuss
+ wie folgt anzeigen:
+
+ &prompt.root; ls /storage/home/.zfs/snapshot
+
+ Es ist möglich, ein Skript zu schreiben, um regelmässig
+ Schnappschüsse von Benutzerdaten anzufertigen. Allerdings
+ verbrauchen Schnappschüsse über lange Zeit eine grosse Menge
+ an Speicherplatz. Der zuvor angelegte Schnappschuss kann
+ durch folgendes Kommundo wieder entfernt werden:
+
+ &prompt.root; zfs destroy storage/home@08-30-08
+
+ Nach erfolgreichen Tests kann
+ /storage/home zum echten
+ /home-Verzeichnis werden, mittels:
+
+ &prompt.root; zfs set mountpoint=/home storage/home
+
+ Prüfen Sie mit df und
+ mount, um zu bestätigen, dass das System
+ das Dateisystem nun als /home
+ verwendet:
+
+ &prompt.root; mount
+/dev/ad0s1a on / (ufs, local)
+devfs on /dev (devfs, local)
+/dev/ad0s1d on /usr (ufs, local, soft-updates)
+storage on /storage (zfs, local)
+storage/home on /home (zfs, local)
+&prompt.root; df
+Filesystem 1K-blocks Used Avail Capacity Mounted on
+/dev/ad0s1a 2026030 235240 1628708 13% /
+devfs 1 1 0 100% /dev
+/dev/ad0s1d 54098308 1032826 48737618 2% /usr
+storage 26320512 0 26320512 0% /storage
+storage/home 26320512 0 26320512 0% /home
+
+ Damit ist die RAID-Z Konfiguration
+ abgeschlossen. Tägliche Informationen über den Status der
+ erstellten Dateisysteme können als Teil des nächtlichen
+ &man.periodic.8;-Berichts generiert werden. Fügen Sie dazu
+ die folgende Zeile in die Datei
+ /etc/periodic.conf ein:
+
+ daily_status_zfs_enable="YES"
+
+
+
+ RAID-Z wiederherstellen
+
+ Jedes Software-RAID besitzt eine
+ Methode, um den Zustund (state) zu
+ überprüfen. Der Status von RAID-Z Geräten
+ wird mit diesem Befehl angezeigt:
+
+ &prompt.root; zpool status -x
+
+ Wenn alle Pools
+ Online sind und alles
+ normal ist, zeigt die Meldung folgendes an:
+
+ all pools are healthy
+
+ Wenn es ein Problem gibt, womöglich ist eine Platte
+ im Zustund Offline,
+ dann wird der Poolzustund ähnlich wie dieser aussehen:
+
+ pool: storage
+ state: DEGRADED
+status: One or more devices has been taken offline by the administrator.
+ Sufficient replicas exist for the pool to continue functioning in a
+ degraded state.
+action: Online the device using 'zpool online' or replace the device with
+ 'zpool replace'.
+ scrub: none requested
+config:
+
+ NAME STATE READ WRITE CKSUM
+ storage DEGRADED 0 0 0
+ raidz1 DEGRADED 0 0 0
+ da0 ONLINE 0 0 0
+ da1 OFFLINE 0 0 0
+ da2 ONLINE 0 0 0
+
+errors: No known data errors
+
+ Dies zeigt an, dass das Gerät zuvor vom Administrator mit
+ diesem Befehl abgeschaltet wurde:
+
+ &prompt.root; zpool offline storage da1
+
+ Jetzt kann das System heruntergefahren werden, um
+ da1 zu ersetzen. Wenn das System wieder
+ eingeschaltet wird, kann die fehlerhafte Platte im Pool
+ ersetzt werden:
+
+ &prompt.root; zpool replace storage da1
+
+ Von diesem Punkt an kann der Status erneut geprüft werden.
+ Dieses Mal ohne die Option , damit alle
+ Pools angezeigt werden:
+
+ &prompt.root; zpool status storage
+ pool: storage
+ state: ONLINE
+ scrub: resilver completed with 0 errors on Sat Aug 30 19:44:11 2008
+config:
+
+ NAME STATE READ WRITE CKSUM
+ storage ONLINE 0 0 0
+ raidz1 ONLINE 0 0 0
+ da0 ONLINE 0 0 0
+ da1 ONLINE 0 0 0
+ da2 ONLINE 0 0 0
+
+errors: No known data errors
+
+ In diesem Beispiel ist alles normal.
+
+
+
+ Daten verifizieren
+
+ ZFS verwendet Prüfsummen, um die
+ Integrität der gespeicherten Daten zu gewährleisten. Dies
+ wird automatisch beim Erstellen von Dateisystemen
+ aktiviert.
+
+
+ Prüfsummen können deaktiviert werden, dies wird jedoch
+ nicht empfohlen! Prüfsummen
+ verbrauchen nur sehr wenig Speicherplatz und sichern die
+ Integrität der Daten. Viele Eigenschaften vom
+ ZFS werden nicht richtig funktionieren,
+ wenn Prüfsummen deaktiviert sind. Es gibt keinen merklichen
+ Geschwindigkeitsunterschied durch das Deaktivieren dieser
+ Prüfsummen.
+
+
+ Prüfsummenverifikation ist unter der Bezeichnung
+ scrubbing bekannt. Verifizieren Sie die
+ Integrität der Daten des storage-Pools mit
+ diesem Befehl:
+
+ &prompt.root; zpool scrub storage
+
+ Die Laufzeit einer Überprüfung hängt ab von der Menge an
+ Daten, die gespeichert sind. Grössere Mengen an Daten
+ benötigen proportional mehr Zeit zum überprüfen. Diese
+ Überprüfungen sind sehr I/O-intensiv und
+ es kann auch nur eine Überprüfung zur gleichen Zeit
+ durchgeführt werden. Nachdem eine Prüfung beendet ist, kann
+ der Status mit dem Unterkommundo status
+ angezeigt werden:
+
+ &prompt.root; zpool status storage
+ pool: storage
+ state: ONLINE
+ scrub: scrub completed with 0 errors on Sat Jan 26 19:57:37 2013
+config:
+
+ NAME STATE READ WRITE CKSUM
+ storage ONLINE 0 0 0
+ raidz1 ONLINE 0 0 0
+ da0 ONLINE 0 0 0
+ da1 ONLINE 0 0 0
+ da2 ONLINE 0 0 0
+
+errors: No known data errors
+
+ Das Datum der letzten Prüfoperation wird angezeigt, um zu
+ verfolgen, wann die nächste Prüfung benötigt wird.
+ Routinemässige Überprüfungen helfen dabei, Daten vor stiller
+ Korrumpierung zu schützen und die Integrität des Pools sicher
+ zu stellen.
+
+ Lesen Sie &man.zfs.8; und &man.zpool.8;, um über
+ weitere ZFS-Optionen zu erfahren.
+
+
+
+
+ zpool Administration
+
+ Administration von ZFS ist unterteilt
+ zwischen zwei Hauptkommandos. Das
+ zpool-Wekzeug steuert die Operationen des
+ Pools und kümmert sich um das Hinzufügen, entfernen, ersetzen
+ und verwalten von Platten. Mit dem zfs-Befehl können
+ Datasets erstellt, zerstört und verwaltet werden, sowohl
+ Dateisysteme als
+ auch Volumes.
+
+
+ Pools anlegen und zerstören
+
+ Einen ZFS-Pool
+ (zpool) anzulegen beinhaltet das Treffen
+ von einer Reihe von Entscheidungen, die relativ dauerhaft
+ sind, weil die Struktur des Pools nachdem er angelegt wurde,
+ nicht mehr geändert werden kann. Die wichtigste Entscheidung
+ ist, welche Arten von vdevs als physische Platten
+ zusammengefasst werden soll. Sehen Sie sich dazu die Liste
+ von vdev-Arten an, um
+ Details zu möglichen Optionen zu bekommen. Nachdem der Pool
+ angelegt wurde, erlauben die meisten vdev-Arten es nicht mehr,
+ weitere Geräte zu diesem vdev hinzuzufügen. Die Ausnahme sind
+ Spiegel, die das Hinzufügen von weiteren Platten zum vdev
+ gestatten, sowie stripes, die zu Spiegeln umgewandelt werden
+ können, indem man zusätzliche Platten zum vdev anhängt.
+ Obwohl weitere vdevs eingefügt werden können, um einen Pool zu
+ vergrössern, kann das Layout des Pools nach dem Anlegen nicht
+ mehr verändert werden. Stattdessen müssen die Daten
+ gesichert, der Pool zerstört und danach neu erstellt
+ werden.
+
+ Erstellen eines einfachen gespiegelten Pools:
+
+ &prompt.root; zpool create mypool mirror /dev/ada1/dev/ada2
+&prompt.root; zpool status
+ pool: mypool
+ state: ONLINE
+ scan: none requested
+config:
+
+ NAME STATE READ WRITE CKSUM
+ mypool ONLINE 0 0 0
+ mirror-0 ONLINE 0 0 0
+ ada1 ONLINE 0 0 0
+ ada2 ONLINE 0 0 0
+
+errors: No known data errors
+
+ Mehrere vdevs können gleichzeitig angelegt werden. Geben
+ Sie zusätzliche Gruppen von Platten, getrennt durch das
+ vdev-Typ Schlüsselwort, in diesem Beispiel
+ mirror, an:
+
+ &prompt.root; zpool create mypool mirror /dev/ada1/dev/ada2 mirror /dev/ada3/dev/ada4
+ pool: mypool
+ state: ONLINE
+ scan: none requested
+config:
+
+ NAME STATE READ WRITE CKSUM
+ mypool ONLINE 0 0 0
+ mirror-0 ONLINE 0 0 0
+ ada1 ONLINE 0 0 0
+ ada2 ONLINE 0 0 0
+ mirror-1 ONLINE 0 0 0
+ ada3 ONLINE 0 0 0
+ ada4 ONLINE 0 0 0
+
+errors: No known data errors
+
+ Pools lassen sich auch durch die Angabe von Partitionen
+ anstatt von ganzen Platten erzeugen. Durch die Verwendung von
+ ZFS in einer separaten Partition ist es
+ möglich, dass die gleiche Platte andere Partitionen für andere
+ Zwecke besitzen kann. Dies ist besonders von Interesse, wenn
+ Partitionen mit Bootcode und Dateisysteme, die zum starten
+ benötigt werden, hinzugefügt werden können. Das erlaubt es,
+ von Platten zu booten, die auch Teil eines Pools sind. Es
+ gibt keinen Geschwindigkeitsnachteil unter &os; wenn eine
+ Partition anstatt einer ganzen Platte verwendet wird. Durch
+ den Einsatz von Partitionen kann der Administrator die Platten
+ unter provisionieren, indem weniger als
+ die volle Kapazität Verwendung findet. Wenn in Zukunft ein
+ Ersatzfestplatte mit der gleichen Grösse als die
+ Originalplatte eine kleinere Kapazität aufweist, passt die
+ kleinere Partition immer noch passen und die Ersatzplatte
+ immer noch verwendet werden.
+
+ Erstellen eines RAID-Z2-Pools mit
+ Partitionen:
+
+ &prompt.root; zpool create mypool raidz2 /dev/ada0p3/dev/ada1p3/dev/ada2p3/dev/ada3p3/dev/ada4p3/dev/ada5p3
+&prompt.root; zpool status
+ pool: mypool
+ state: ONLINE
+ scan: none requested
+config:
+
+ NAME STATE READ WRITE CKSUM
+ mypool ONLINE 0 0 0
+ raidz2-0 ONLINE 0 0 0
+ ada0p3 ONLINE 0 0 0
+ ada1p3 ONLINE 0 0 0
+ ada2p3 ONLINE 0 0 0
+ ada3p3 ONLINE 0 0 0
+ ada4p3 ONLINE 0 0 0
+ ada5p3 ONLINE 0 0 0
+
+errors: No known data errors
+
+ Ein Pool, der nicht länger benötigt wird, kann zerstört
+ werden, so dass die Platten für einen anderen Einsatzzweck
+ Verwendung finden können. Um einen Pool zu zerstören, müssen
+ zuerst alle Datasets in diesem Pool abgehängt werden. Wenn
+ die Datasets verwendet werden, wird das Abhängen fehlschlagen
+ und der Pool nicht zerstört. Die Zerstörung des Pools kann
+ erzwungen werden durch die Angabe der Option
+ , jedoch kann dies undefiniertes Verhalten
+ in den Anwendungen auslösen, die noch offene Dateien auf
+ diesen Datasets hatten.
+
+
+
+ Hinzufügen und Löschen von Geräten
+
+ Es gibt zwei Fälle für das Hinzufügen von Platten zu einem
+ Pool: einhängen einer Platte zu einem existierenden vdev mit
+ zpool attach oder einbinden von vdevs zum
+ Pool mit zpool add. Nur manche vdev-Arten gestatten es,
+ Platten zum vdev hinzuzufügen, nachdem diese angelegt
+ wurden.
+
+ Ein Pool mit nur einer einzigen Platte besitzt keine
+ Redundanz. Datenverfälschung kann erkannt, aber nicht
+ repariert werden, weil es keine weiteren Kopien der Daten
+ gibt. Die Eigenschaft copies kann genutzt werden,
+ um einen geringen Fehler wie einen beschädigtem Sektor
+ auszumerzen, enthält aber nicht die gleiche Art von Schutz,
+ die Spiegelung oder RAID-Z bieten. Wenn
+ man mit einem Pool startet, der nur aus einer einzigen
+ vdev-Platte besteht, kann mit dem Kommando
+ zpool attach eine zustätzliche Platte dem
+ vdev hinzugefügt werden, um einen Spiegel zu erzeugen. Mit
+ zpool attach können auch zusätzliche
+ Platten zu einer Spiegelgruppe eingefügt werden, was die
+ Redundanz und Lesegeschwindigkeit steigert. Wenn die Platten,
+ aus denen der Pool besteht, aus partitioniert sind,
+ replizieren Sie das Layout der ersten Platte auf die Zweite
+ und verwenden dann gpart backup, gefolgt
+ von gpart restore, um diesen Vorgang
+ einfacher zu gestalten.
+
+ Umwandeln eines (stripe) vdevs namens
+ ada0p3 mit einer einzelnen Platte
+ zu einem Spiegel durch das Einhängen von
+ ada1p3:
+
+ &prompt.root; zpool status
+ pool: mypool
+ state: ONLINE
+ scan: none requested
+config:
+
+ NAME STATE READ WRITE CKSUM
+ mypool ONLINE 0 0 0
+ ada0p3 ONLINE 0 0 0
+
+errors: No known data errors
+&prompt.root; zpool attach mypoolada0p3ada1p3
+Make sure to wait until resilver is done before rebooting.
+
+If you boot from pool 'mypool', you may need to update
+boot code on newly attached disk 'ada1p3'.
+
+Assuming you use GPT partitioning und 'da0' is your new boot disk
+you may use the following command:
+
+ gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 da0
+&prompt.root; gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 ada1
+bootcode written to ada1
+&prompt.root; zpool status
+ pool: mypool
+ state: ONLINE
+status: One or more devices is currently being resilvered. The pool will
+ continue to function, possibly in a degraded state.
+action: Wait for the resilver to complete.
+ scan: resilver in progress since Fri May 30 08:19:19 2014
+ 527M scanned out of 781M at 47.9M/s, 0h0m to go
+ 527M resilvered, 67.53% done
+config:
+
+ NAME STATE READ WRITE CKSUM
+ mypool ONLINE 0 0 0
+ mirror-0 ONLINE 0 0 0
+ ada0p3 ONLINE 0 0 0
+ ada1p3 ONLINE 0 0 0 (resilvering)
+
+errors: No known data errors
+&prompt.root; zpool status
+ pool: mypool
+ state: ONLINE
+ scan: resilvered 781M in 0h0m with 0 errors on Fri May 30 08:15:58 2014
+config:
+
+ NAME STATE READ WRITE CKSUM
+ mypool ONLINE 0 0 0
+ mirror-0 ONLINE 0 0 0
+ ada0p3 ONLINE 0 0 0
+ ada1p3 ONLINE 0 0 0
+
+errors: No known data errors
+
+ Wenn das Hinzufügen von Platten zu einem vdev keine Option
+ wie für RAID-Z ist, gibt es eine
+ Alternative, nämlich einen anderen vdev zum Pool hinzuzufügen.
+ Zusätzliche vdevs bieten höhere Geschwindigkeit, indem
+ Schreibvorgänge über die vdevs verteilt werden. Jedes vdev
+ ist dafür verantwortlich, seine eigene Redundanz
+ sicherzustellen. Es ist möglich, aber nicht empfohlen,
+ vdev-Arten zu mischen, wie zum Beispiel
+ mirror und RAID-Z.
+ Durch das Einfügen eines nicht-redundanten vdev zu einem
+ gespiegelten Pool oder einem RAID-Z vdev
+ riskiert man die Daten des gesamten Pools. Schreibvorgänge
+ werden verteilt, deshalb ist der Ausfall einer
+ nicht-redundanten Platte mit dem Verlust eines Teils von jedem
+ Block verbunden, der auf den Pool geschrieben wird.
+
+ Daten werden über jedes vdev gestriped. Beispielsweise
+ sind zwei Spiegel-vdevs effektiv ein RAID
+ 10, dass über zwei Sets von Spiegeln die Daten schreibt.
+ Speicherplatz wird so allokiert, dass jedes vdev zur gleichen
+ Zeit vollgeschrieben wird. Es gibt einen
+ Geschwindigkeitsnachteil wenn die vdevs unterschiedliche Menge
+ von freiem Speicher aufweisen, wenn eine
+ unproportionale Menge an Daten auf das weniger volle vdev
+ geschrieben wird.
+
+ Wenn zusätzliche Geräte zu einem Pool, von dem gebootet
+ wird, hinzugefügt werden, muss der Bootcode aktualisiert
+ werden.
+
+ Einbinden einer zweiten Spiegelgruppe
+ (ada2p3 und ada3p3)
+ zu einem bestehenden Spiegel:
+
+ &prompt.root; zpool status
+ pool: mypool
+ state: ONLINE
+ scan: resilvered 781M in 0h0m with 0 errors on Fri May 30 08:19:35 2014
+config:
+
+ NAME STATE READ WRITE CKSUM
+ mypool ONLINE 0 0 0
+ mirror-0 ONLINE 0 0 0
+ ada0p3 ONLINE 0 0 0
+ ada1p3 ONLINE 0 0 0
+
+errors: No known data errors
+&prompt.root; zpool add mypool mirror ada2p3ada3p3
+&prompt.root; gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 ada2
+bootcode written to ada2
+&prompt.root; gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 ada3
+bootcode written to ada3
+&prompt.root; zpool status
+ pool: mypool
+ state: ONLINE
+ scan: scrub repaired 0 in 0h0m with 0 errors on Fri May 30 08:29:51 2014
+config:
+
+ NAME STATE READ WRITE CKSUM
+ mypool ONLINE 0 0 0
+ mirror-0 ONLINE 0 0 0
+ ada0p3 ONLINE 0 0 0
+ ada1p3 ONLINE 0 0 0
+ mirror-1 ONLINE 0 0 0
+ ada2p3 ONLINE 0 0 0
+ ada3p3 ONLINE 0 0 0
+
+errors: No known data errors
+
+ Momentan können vdevs nicht von einem Pool entfernt und
+ Platten nur von einem Spiegel ausgehängt werden, wenn genug
+ Redundanz übrig bleibt. Wenn auch nur eine Platte in einer
+ Spiegelgruppe bestehen bleibt, hört der Spiegel auf zu
+ existieren und wird zu einem stripe, was den gesamten Pool
+ riskiert, falls diese letzte Platte ausfällt.
+
+ Entfernen einer Platte aus einem Spiegel mit drei
+ Platten:
+
+ &prompt.root; zpool status
+ pool: mypool
+ state: ONLINE
+ scan: scrub repaired 0 in 0h0m with 0 errors on Fri May 30 08:29:51 2014
+config:
+
+ NAME STATE READ WRITE CKSUM
+ mypool ONLINE 0 0 0
+ mirror-0 ONLINE 0 0 0
+ ada0p3 ONLINE 0 0 0
+ ada1p3 ONLINE 0 0 0
+ ada2p3 ONLINE 0 0 0
+
+errors: No known data errors
+&prompt.root; zpool detach mypoolada2p3
+&prompt.root; zpool status
+ pool: mypool
+ state: ONLINE
+ scan: scrub repaired 0 in 0h0m with 0 errors on Fri May 30 08:29:51 2014
+config:
+
+ NAME STATE READ WRITE CKSUM
+ mypool ONLINE 0 0 0
+ mirror-0 ONLINE 0 0 0
+ ada0p3 ONLINE 0 0 0
+ ada1p3 ONLINE 0 0 0
+
+errors: No known data errors
+
+
+
+ Den Status eines Pools überprüfen
+
+ Der Status eines Pools ist wichtig. Wenn ein Gerät sich
+ abschaltet oder ein Lese-, Schreib- oder Prüfsummenfehler
+ festgestellt wird, wird der dazugehörige Fehlerzähler erhöht.
+ Die status-Ausgabe zeigt die Konfiguration
+ und den Status von jedem Gerät im Pool und den Gesamtstatus
+ des Pools. Aktionen, die durchgeführt werden sollten und
+ Details zum letzten scrub
+ werden ebenfalls angezeigt.
+
+ &prompt.root; zpool status
+ pool: mypool
+ state: ONLINE
+ scan: scrub repaired 0 in 2h25m with 0 errors on Sat Sep 14 04:25:50 2013
+config:
+
+ NAME STATE READ WRITE CKSUM
+ mypool ONLINE 0 0 0
+ raidz2-0 ONLINE 0 0 0
+ ada0p3 ONLINE 0 0 0
+ ada1p3 ONLINE 0 0 0
+ ada2p3 ONLINE 0 0 0
+ ada3p3 ONLINE 0 0 0
+ ada4p3 ONLINE 0 0 0
+ ada5p3 ONLINE 0 0 0
+
+errors: No known data errors
+
+
+
+ Clearing Errors
+
+ Wenn ein Fehler erkannt wurde, werden die Lese-, Schreib-
+ oder Prüfsummenzähler erhöht. Die Fehlermeldung kann
+ beseitigt und der Zähler zurückgesetzt werden mit
+ zpool clear
+ mypool. Den
+ Fehlerzustand zurückzusetzen kann wichtig sein, wenn
+ automatisierte Skripte ablaufen, die den Administrator
+ informieren, sobald der Pool Fehler anzeigt. Weitere Fehler
+ werden nicht gemeldet, wenn der alte Fehlerbericht nicht
+ entfernt wurde.
+
+
+
+ Ein defektes Gerät entfernen
+
+ Es gibt eine Reihe von Situationen, in denen es nötig
+ wird, eine defekte Platte mit einer anderen auszutauschen.
+ Wenn eine funktionierende Platte ersetzt wird, hält der
+ Prozess die alte Platte während des Ersetzungsvorganges noch
+ aktiv. Der Pool wird nie den Zustand degraded erhalten, was
+ das Risiko eines Datenverlustes minimiert. Alle Daten der
+ alten Platte werden durch das Kommando
+ zpool replace auf die Neue übertragen.
+ Nachdem die Operation abgeschlossen ist, wird die alte Platte
+ vom vdev getrennt. Falls die neue Platte grösser ist als die
+ alte Platte , ist es möglich den Pool zu vergrössern, um den
+ neuen Platz zu nutzen. Lesen Sie dazu Einen Pool vergrössern.
+
+ Ersetzen eines funktionierenden Geräts in einem
+ Pool:
+
+ &prompt.root; zpool status
+ pool: mypool
+ state: ONLINE
+ scan: none requested
+config:
+
+ NAME STATE READ WRITE CKSUM
+ mypool ONLINE 0 0 0
+ mirror-0 ONLINE 0 0 0
+ ada0p3 ONLINE 0 0 0
+ ada1p3 ONLINE 0 0 0
+
+errors: No known data errors
+&prompt.root; zpool replace mypoolada1p3ada2p3
*** DIFF OUTPUT TRUNCATED AT 1000 LINES ***
From owner-svn-doc-head@FreeBSD.ORG Sun Apr 5 15:45:35 2015
Return-Path:
Delivered-To: svn-doc-head@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
(using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
(No client certificate requested)
by hub.freebsd.org (Postfix) with ESMTPS id 533A190E;
Sun, 5 Apr 2015 15:45:35 +0000 (UTC)
Received: from svn.freebsd.org (svn.freebsd.org
[IPv6:2001:1900:2254:2068::e6a:0])
(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
(Client did not present a certificate)
by mx1.freebsd.org (Postfix) with ESMTPS id 3BE1BA8F;
Sun, 5 Apr 2015 15:45:35 +0000 (UTC)
Received: from svn.freebsd.org ([127.0.1.70])
by svn.freebsd.org (8.14.9/8.14.9) with ESMTP id t35FjZWJ097464;
Sun, 5 Apr 2015 15:45:35 GMT (envelope-from eadler@FreeBSD.org)
Received: (from eadler@localhost)
by svn.freebsd.org (8.14.9/8.14.9/Submit) id t35FjXJ3097460;
Sun, 5 Apr 2015 15:45:33 GMT (envelope-from eadler@FreeBSD.org)
Message-Id: <201504051545.t35FjXJ3097460@svn.freebsd.org>
X-Authentication-Warning: svn.freebsd.org: eadler set sender to
eadler@FreeBSD.org using -f
From: Eitan Adler
Date: Sun, 5 Apr 2015 15:45:33 +0000 (UTC)
To: doc-committers@freebsd.org, svn-doc-all@freebsd.org,
svn-doc-head@freebsd.org
Subject: svn commit: r46473 - in head: en_US.ISO8859-1/articles
en_US.ISO8859-1/articles/console-server en_US.ISO8859-1/htdocs/docs
ru_RU.KOI8-R/articles ru_RU.KOI8-R/articles/console-server 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-head@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: SVN commit messages for the doc tree for head
List-Unsubscribe: ,
List-Archive:
List-Post:
List-Help:
List-Subscribe: ,
X-List-Received-Date: Sun, 05 Apr 2015 15:45:35 -0000
Author: eadler
Date: Sun Apr 5 15:45:33 2015
New Revision: 46473
URL: https://svnweb.freebsd.org/changeset/doc/46473
Log:
articles/console-server: remove it
- references mostly outdated hardware
- doesn't use modern technologies (IPMI, nmdm, bhyve)
- the SUN hardware peculiarities are not useful anymore
- there are other better references on crimping custom serial cables
- MAKEDEV is no a thing anymore
there might be room for a modern version of this article in the handbook
but there is little that is salvageable from this article.
Discussed with: bcr, xmj, sbruno, cem
Deleted:
head/en_US.ISO8859-1/articles/console-server/
head/ru_RU.KOI8-R/articles/console-server/
Modified:
head/en_US.ISO8859-1/articles/Makefile
head/en_US.ISO8859-1/htdocs/docs/books.xml
head/ru_RU.KOI8-R/articles/Makefile
head/share/xml/urls.ent
Modified: head/en_US.ISO8859-1/articles/Makefile
==============================================================================
--- head/en_US.ISO8859-1/articles/Makefile Sun Apr 5 15:21:54 2015 (r46472)
+++ head/en_US.ISO8859-1/articles/Makefile Sun Apr 5 15:45:33 2015 (r46473)
@@ -4,7 +4,6 @@ SUBDIR =
SUBDIR+= bsdl-gpl
SUBDIR+= building-products
SUBDIR+= committers-guide
-SUBDIR+= console-server
SUBDIR+= contributing
SUBDIR+= contributing-ports
SUBDIR+= contributors
Modified: head/en_US.ISO8859-1/htdocs/docs/books.xml
==============================================================================
--- head/en_US.ISO8859-1/htdocs/docs/books.xml Sun Apr 5 15:21:54 2015 (r46472)
+++ head/en_US.ISO8859-1/htdocs/docs/books.xml Sun Apr 5 15:45:33 2015 (r46473)
@@ -104,11 +104,6 @@
Committer's Guide (committers-guide)
Introductory information for FreeBSD committers.
-
Console
- Server Tutorial (console-server)
- How to setup a FreeBSD based console server with a cheap
- multi-port serial card.
Modified: head/share/xml/urls.ent
==============================================================================
--- head/share/xml/urls.ent Sun Apr 5 15:49:41 2015 (r46474)
+++ head/share/xml/urls.ent Sun Apr 5 15:57:52 2015 (r46475)
@@ -120,5 +120,3 @@
-
-
From owner-svn-doc-head@FreeBSD.ORG Sun Apr 5 16:07:26 2015
Return-Path:
Delivered-To: svn-doc-head@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
[IPv6:2001:1900:2254:206a::19:1])
(using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
(No client certificate requested)
by hub.freebsd.org (Postfix) with ESMTPS id 4FBD9EB4;
Sun, 5 Apr 2015 16:07:26 +0000 (UTC)
Received: from svn.freebsd.org (svn.freebsd.org
[IPv6:2001:1900:2254:2068::e6a:0])
(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
(Client did not present a certificate)
by mx1.freebsd.org (Postfix) with ESMTPS id 381B9C8D;
Sun, 5 Apr 2015 16:07:26 +0000 (UTC)
Received: from svn.freebsd.org ([127.0.1.70])
by svn.freebsd.org (8.14.9/8.14.9) with ESMTP id t35G7PDq007802;
Sun, 5 Apr 2015 16:07:25 GMT (envelope-from eadler@FreeBSD.org)
Received: (from eadler@localhost)
by svn.freebsd.org (8.14.9/8.14.9/Submit) id t35G7NQR007796;
Sun, 5 Apr 2015 16:07:23 GMT (envelope-from eadler@FreeBSD.org)
Message-Id: <201504051607.t35G7NQR007796@svn.freebsd.org>
X-Authentication-Warning: svn.freebsd.org: eadler set sender to
eadler@FreeBSD.org using -f
From: Eitan Adler
Date: Sun, 5 Apr 2015 16:07:23 +0000 (UTC)
To: doc-committers@freebsd.org, svn-doc-all@freebsd.org,
svn-doc-head@freebsd.org
Subject: svn commit: r46476 - in head: de_DE.ISO8859-1/articles
el_GR.ISO8859-7/articles el_GR.ISO8859-7/articles/cvs-freebsd
es_ES.ISO8859-1/articles es_ES.ISO8859-1/articles/cvs-freebsd
ru_RU.KOI8-R/artic...
X-SVN-Group: doc-head
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
X-BeenThere: svn-doc-head@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: SVN commit messages for the doc tree for head
List-Unsubscribe: ,
List-Archive:
List-Post:
List-Help:
List-Subscribe: ,
X-List-Received-Date: Sun, 05 Apr 2015 16:07:26 -0000
Author: eadler
Date: Sun Apr 5 16:07:22 2015
New Revision: 46476
URL: https://svnweb.freebsd.org/changeset/doc/46476
Log:
cvs-freebsd: fully remove it
the cvs-freebsd article was removed from the English version some time
ago. Fully remove it from the doc tree now
Deleted:
head/el_GR.ISO8859-7/articles/cvs-freebsd/
head/es_ES.ISO8859-1/articles/cvs-freebsd/
head/ru_RU.KOI8-R/articles/cvs-freebsd/
head/zh_CN.UTF-8/articles/cvs-freebsd/
head/zh_TW.UTF-8/articles/cvs-freebsd/
Modified:
head/de_DE.ISO8859-1/articles/Makefile
head/el_GR.ISO8859-7/articles/Makefile
head/es_ES.ISO8859-1/articles/Makefile
head/ru_RU.KOI8-R/articles/Makefile
head/share/xml/urls.ent
head/zh_TW.UTF-8/articles/Makefile
Modified: head/de_DE.ISO8859-1/articles/Makefile
==============================================================================
--- head/de_DE.ISO8859-1/articles/Makefile Sun Apr 5 15:57:52 2015 (r46475)
+++ head/de_DE.ISO8859-1/articles/Makefile Sun Apr 5 16:07:22 2015 (r46476)
@@ -6,7 +6,7 @@
# basiert auf: 1.42
SUBDIR = contributing
-SUBDIR+= contributing-ports
+gUBDIR+= contributing-ports
SUBDIR+= explaining-bsd
SUBDIR+= freebsd-update-server
SUBDIR+= nanobsd
Modified: head/el_GR.ISO8859-7/articles/Makefile
==============================================================================
--- head/el_GR.ISO8859-7/articles/Makefile Sun Apr 5 15:57:52 2015 (r46475)
+++ head/el_GR.ISO8859-7/articles/Makefile Sun Apr 5 16:07:22 2015 (r46476)
@@ -5,7 +5,6 @@
SUBDIR = bsdl-gpl
SUBDIR+= contributing
-SUBDIR+= cvs-freebsd
SUBDIR+= explaining-bsd
SUBDIR+= freebsd-questions
SUBDIR+= gjournal-desktop
Modified: head/es_ES.ISO8859-1/articles/Makefile
==============================================================================
--- head/es_ES.ISO8859-1/articles/Makefile Sun Apr 5 15:57:52 2015 (r46475)
+++ head/es_ES.ISO8859-1/articles/Makefile Sun Apr 5 16:07:22 2015 (r46476)
@@ -4,7 +4,6 @@
SUBDIR =
SUBDIR+= casestudy-argentina.com
SUBDIR+= contributing
-SUBDIR+= cvs-freebsd
SUBDIR+= explaining-bsd
SUBDIR+= fdp-es
SUBDIR+= linux-users
Modified: head/ru_RU.KOI8-R/articles/Makefile
==============================================================================
--- head/ru_RU.KOI8-R/articles/Makefile Sun Apr 5 15:57:52 2015 (r46475)
+++ head/ru_RU.KOI8-R/articles/Makefile Sun Apr 5 16:07:22 2015 (r46476)
@@ -12,7 +12,6 @@ SUBDIR+= committers-guide
SUBDIR+= contributing
#SUBDIR+= contributors
SUBDIR+= cups
-SUBDIR+= cvs-freebsd
SUBDIR+= explaining-bsd
#SUBDIR+= filtering-bridges
SUBDIR+= fonts
Modified: head/share/xml/urls.ent
==============================================================================
--- head/share/xml/urls.ent Sun Apr 5 15:57:52 2015 (r46475)
+++ head/share/xml/urls.ent Sun Apr 5 16:07:22 2015 (r46476)
@@ -60,8 +60,6 @@
-
-
Modified: head/zh_TW.UTF-8/articles/Makefile
==============================================================================
--- head/zh_TW.UTF-8/articles/Makefile Sun Apr 5 15:57:52 2015 (r46475)
+++ head/zh_TW.UTF-8/articles/Makefile Sun Apr 5 16:07:22 2015 (r46476)
@@ -2,7 +2,6 @@
SUBDIR =
SUBDIR+= contributing
-SUBDIR+= cvs-freebsd
SUBDIR+= freebsd-questions
SUBDIR+= hubs
SUBDIR+= mailing-list-faq
From owner-svn-doc-head@FreeBSD.ORG Sun Apr 5 16:23:58 2015
Return-Path:
Delivered-To: svn-doc-head@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
(using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
(No client certificate requested)
by hub.freebsd.org (Postfix) with ESMTPS id AA6BA20F;
Sun, 5 Apr 2015 16:23:58 +0000 (UTC)
Received: from svn.freebsd.org (svn.freebsd.org
[IPv6:2001:1900:2254:2068::e6a:0])
(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
(Client did not present a certificate)
by mx1.freebsd.org (Postfix) with ESMTPS id 7A4B9E12;
Sun, 5 Apr 2015 16:23:58 +0000 (UTC)
Received: from svn.freebsd.org ([127.0.1.70])
by svn.freebsd.org (8.14.9/8.14.9) with ESMTP id t35GNwT4016944;
Sun, 5 Apr 2015 16:23:58 GMT (envelope-from eadler@FreeBSD.org)
Received: (from eadler@localhost)
by svn.freebsd.org (8.14.9/8.14.9/Submit) id t35GNw2U016943;
Sun, 5 Apr 2015 16:23:58 GMT (envelope-from eadler@FreeBSD.org)
Message-Id: <201504051623.t35GNw2U016943@svn.freebsd.org>
X-Authentication-Warning: svn.freebsd.org: eadler set sender to
eadler@FreeBSD.org using -f
From: Eitan Adler
Date: Sun, 5 Apr 2015 16:23:58 +0000 (UTC)
To: doc-committers@freebsd.org, svn-doc-all@freebsd.org,
svn-doc-head@freebsd.org
Subject: svn commit: r46477 - in head: el_GR.ISO8859-7/articles/java-tomcat
ru_RU.KOI8-R/articles/java-tomcat
X-SVN-Group: doc-head
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
X-BeenThere: svn-doc-head@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: SVN commit messages for the doc tree for head
List-Unsubscribe: ,
List-Archive:
List-Post:
List-Help:
List-Subscribe: ,
X-List-Received-Date: Sun, 05 Apr 2015 16:23:58 -0000
Author: eadler
Date: Sun Apr 5 16:23:57 2015
New Revision: 46477
URL: https://svnweb.freebsd.org/changeset/doc/46477
Log:
remove empty directories for an article which was removed in 2006
Deleted:
head/el_GR.ISO8859-7/articles/java-tomcat/
head/ru_RU.KOI8-R/articles/java-tomcat/
From owner-svn-doc-head@FreeBSD.ORG Sun Apr 5 16:36:09 2015
Return-Path:
Delivered-To: svn-doc-head@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
[IPv6:2001:1900:2254:206a::19:1])
(using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
(No client certificate requested)
by hub.freebsd.org (Postfix) with ESMTPS id 43EAA44C;
Sun, 5 Apr 2015 16:36:09 +0000 (UTC)
Received: from svn.freebsd.org (svn.freebsd.org
[IPv6:2001:1900:2254:2068::e6a:0])
(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
(Client did not present a certificate)
by mx1.freebsd.org (Postfix) with ESMTPS id 25333EE8;
Sun, 5 Apr 2015 16:36:09 +0000 (UTC)
Received: from svn.freebsd.org ([127.0.1.70])
by svn.freebsd.org (8.14.9/8.14.9) with ESMTP id t35Ga9eS022047;
Sun, 5 Apr 2015 16:36:09 GMT (envelope-from eadler@FreeBSD.org)
Received: (from eadler@localhost)
by svn.freebsd.org (8.14.9/8.14.9/Submit) id t35Ga74g022042;
Sun, 5 Apr 2015 16:36:07 GMT (envelope-from eadler@FreeBSD.org)
Message-Id: <201504051636.t35Ga74g022042@svn.freebsd.org>
X-Authentication-Warning: svn.freebsd.org: eadler set sender to
eadler@FreeBSD.org using -f
From: Eitan Adler
Date: Sun, 5 Apr 2015 16:36:07 +0000 (UTC)
To: doc-committers@freebsd.org, svn-doc-all@freebsd.org,
svn-doc-head@freebsd.org
Subject: svn commit: r46478 - in head: es_ES.ISO8859-1/articles
es_ES.ISO8859-1/articles/casestudy-argentina.com fr_FR.ISO8859-1/articles
fr_FR.ISO8859-1/articles/mh pt_BR.ISO8859-1/articles pt_BR.ISO8859-1...
X-SVN-Group: doc-head
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
X-BeenThere: svn-doc-head@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: SVN commit messages for the doc tree for head
List-Unsubscribe: ,
List-Archive:
List-Post:
List-Help:
List-Subscribe: ,
X-List-Received-Date: Sun, 05 Apr 2015 16:36:09 -0000
Author: eadler
Date: Sun Apr 5 16:36:06 2015
New Revision: 46478
URL: https://svnweb.freebsd.org/changeset/doc/46478
Log:
multiple:
clean up for other older articles which were already deleted.
tested with a top-level 'make'
Deleted:
head/es_ES.ISO8859-1/articles/casestudy-argentina.com/
head/fr_FR.ISO8859-1/articles/mh/
head/pt_BR.ISO8859-1/articles/portbuild/
head/ru_RU.KOI8-R/articles/mh/
head/ru_RU.KOI8-R/articles/portbuild/
Modified:
head/es_ES.ISO8859-1/articles/Makefile
head/fr_FR.ISO8859-1/articles/Makefile
head/pt_BR.ISO8859-1/articles/Makefile
head/ru_RU.KOI8-R/articles/Makefile
head/zh_CN.UTF-8/articles/Makefile
Modified: head/es_ES.ISO8859-1/articles/Makefile
==============================================================================
--- head/es_ES.ISO8859-1/articles/Makefile Sun Apr 5 16:23:57 2015 (r46477)
+++ head/es_ES.ISO8859-1/articles/Makefile Sun Apr 5 16:36:06 2015 (r46478)
@@ -2,7 +2,6 @@
# $FreeBSDes: doc/es_ES.ISO8859-1/articles/Makefile,v 1.3 2004/10/09 02:01:17 jesusr Exp $
SUBDIR =
-SUBDIR+= casestudy-argentina.com
SUBDIR+= contributing
SUBDIR+= explaining-bsd
SUBDIR+= fdp-es
Modified: head/fr_FR.ISO8859-1/articles/Makefile
==============================================================================
--- head/fr_FR.ISO8859-1/articles/Makefile Sun Apr 5 16:23:57 2015 (r46477)
+++ head/fr_FR.ISO8859-1/articles/Makefile Sun Apr 5 16:36:06 2015 (r46478)
@@ -16,7 +16,6 @@ SUBDIR+= filtering-bridges
SUBDIR+= fonts
SUBDIR+= ipsec-must
SUBDIR+= linux-users
-SUBDIR+= mh
SUBDIR+= nanobsd
SUBDIR+= new-users
SUBDIR+= pam
Modified: head/pt_BR.ISO8859-1/articles/Makefile
==============================================================================
--- head/pt_BR.ISO8859-1/articles/Makefile Sun Apr 5 16:23:57 2015 (r46477)
+++ head/pt_BR.ISO8859-1/articles/Makefile Sun Apr 5 16:36:06 2015 (r46478)
@@ -18,7 +18,6 @@ SUBDIR+= freebsd-update-server
SUBDIR+= hubs
SUBDIR+= linux-users
SUBDIR+= new-users
-SUBDIR+= portbuild
SUBDIR+= problem-reports
DOC_PREFIX?= ${.CURDIR}/../..
Modified: head/ru_RU.KOI8-R/articles/Makefile
==============================================================================
--- head/ru_RU.KOI8-R/articles/Makefile Sun Apr 5 16:23:57 2015 (r46477)
+++ head/ru_RU.KOI8-R/articles/Makefile Sun Apr 5 16:36:06 2015 (r46478)
@@ -21,10 +21,8 @@ SUBDIR+= gjournal-desktop
SUBDIR+= hubs
SUBDIR+= ipsec-must
SUBDIR+= mailing-list-faq
-SUBDIR+= mh
SUBDIR+= new-users
SUBDIR+= pam
-SUBDIR+= portbuild
SUBDIR+= pr-guidelines
SUBDIR+= problem-reports
SUBDIR+= relaydelay
Modified: head/zh_CN.UTF-8/articles/Makefile
==============================================================================
--- head/zh_CN.UTF-8/articles/Makefile Sun Apr 5 16:23:57 2015 (r46477)
+++ head/zh_CN.UTF-8/articles/Makefile Sun Apr 5 16:36:06 2015 (r46478)
@@ -6,7 +6,6 @@
SUBDIR =
SUBDIR+= contributing
-SUBDIR+= cvs-freebsd
SUBDIR+= linux-users
SUBDIR+= nanobsd
SUBDIR+= rc-scripting
From owner-svn-doc-head@FreeBSD.ORG Sun Apr 5 16:46:30 2015
Return-Path:
Delivered-To: svn-doc-head@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
(using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
(No client certificate requested)
by hub.freebsd.org (Postfix) with ESMTPS id F1884510;
Sun, 5 Apr 2015 16:46:29 +0000 (UTC)
Received: from svn.freebsd.org (svn.freebsd.org
[IPv6:2001:1900:2254:2068::e6a:0])
(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
(Client did not present a certificate)
by mx1.freebsd.org (Postfix) with ESMTPS id DCEB5FB5;
Sun, 5 Apr 2015 16:46:29 +0000 (UTC)
Received: from svn.freebsd.org ([127.0.1.70])
by svn.freebsd.org (8.14.9/8.14.9) with ESMTP id t35GkTR0026822;
Sun, 5 Apr 2015 16:46:29 GMT (envelope-from eadler@FreeBSD.org)
Received: (from eadler@localhost)
by svn.freebsd.org (8.14.9/8.14.9/Submit) id t35GkTls026821;
Sun, 5 Apr 2015 16:46:29 GMT (envelope-from eadler@FreeBSD.org)
Message-Id: <201504051646.t35GkTls026821@svn.freebsd.org>
X-Authentication-Warning: svn.freebsd.org: eadler set sender to
eadler@FreeBSD.org using -f
From: Eitan Adler
Date: Sun, 5 Apr 2015 16:46:29 +0000 (UTC)
To: doc-committers@freebsd.org, svn-doc-all@freebsd.org,
svn-doc-head@freebsd.org
Subject: svn commit: r46479 - 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-head@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: SVN commit messages for the doc tree for head
List-Unsubscribe: ,
List-Archive:
List-Post:
List-Help:
List-Subscribe: ,
X-List-Received-Date: Sun, 05 Apr 2015 16:46:30 -0000
Author: eadler
Date: Sun Apr 5 16:46:29 2015
New Revision: 46479
URL: https://svnweb.freebsd.org/changeset/doc/46479
Log:
urls.ent: remove url.main
- it says 'XXX will be removed soon' from 2004
I grepped, didn't find any reference. tested with a top level make
Modified:
head/share/xml/urls.ent
Modified: head/share/xml/urls.ent
==============================================================================
--- head/share/xml/urls.ent Sun Apr 5 16:36:06 2015 (r46478)
+++ head/share/xml/urls.ent Sun Apr 5 16:46:29 2015 (r46479)
@@ -8,9 +8,6 @@
-
-
-
From owner-svn-doc-head@FreeBSD.ORG Sun Apr 5 16:49:34 2015
Return-Path:
Delivered-To: svn-doc-head@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
(using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
(No client certificate requested)
by hub.freebsd.org (Postfix) with ESMTPS id 1D30F592;
Sun, 5 Apr 2015 16:49:34 +0000 (UTC)
Received: from svn.freebsd.org (svn.freebsd.org
[IPv6:2001:1900:2254:2068::e6a:0])
(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
(Client did not present a certificate)
by mx1.freebsd.org (Postfix) with ESMTPS id 08E8CFC9;
Sun, 5 Apr 2015 16:49:34 +0000 (UTC)
Received: from svn.freebsd.org ([127.0.1.70])
by svn.freebsd.org (8.14.9/8.14.9) with ESMTP id t35GnXoj027224;
Sun, 5 Apr 2015 16:49:33 GMT (envelope-from eadler@FreeBSD.org)
Received: (from eadler@localhost)
by svn.freebsd.org (8.14.9/8.14.9/Submit) id t35GnXBP027223;
Sun, 5 Apr 2015 16:49:33 GMT (envelope-from eadler@FreeBSD.org)
Message-Id: <201504051649.t35GnXBP027223@svn.freebsd.org>
X-Authentication-Warning: svn.freebsd.org: eadler set sender to
eadler@FreeBSD.org using -f
From: Eitan Adler
Date: Sun, 5 Apr 2015 16:49:33 +0000 (UTC)
To: doc-committers@freebsd.org, svn-doc-all@freebsd.org,
svn-doc-head@freebsd.org
Subject: svn commit: r46480 - 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-head@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: SVN commit messages for the doc tree for head
List-Unsubscribe: ,
List-Archive:
List-Post:
List-Help:
List-Subscribe: ,
X-List-Received-Date: Sun, 05 Apr 2015 16:49:34 -0000
Author: eadler
Date: Sun Apr 5 16:49:33 2015
New Revision: 46480
URL: https://svnweb.freebsd.org/changeset/doc/46480
Log:
urls.ent: remove url.books.corp-net-guide which isn't referenced anywhere
Modified:
head/share/xml/urls.ent
Modified: head/share/xml/urls.ent
==============================================================================
--- head/share/xml/urls.ent Sun Apr 5 16:46:29 2015 (r46479)
+++ head/share/xml/urls.ent Sun Apr 5 16:49:33 2015 (r46480)
@@ -24,8 +24,6 @@
-
-
From owner-svn-doc-head@FreeBSD.ORG Mon Apr 6 04:47:44 2015
Return-Path:
Delivered-To: svn-doc-head@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
[IPv6:2001:1900:2254:206a::19:1])
(using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
(No client certificate requested)
by hub.freebsd.org (Postfix) with ESMTPS id 471407ED;
Mon, 6 Apr 2015 04:47:44 +0000 (UTC)
Received: from svn.freebsd.org (svn.freebsd.org
[IPv6:2001:1900:2254:2068::e6a:0])
(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
(Client did not present a certificate)
by mx1.freebsd.org (Postfix) with ESMTPS id 2EB87E7D;
Mon, 6 Apr 2015 04:47:44 +0000 (UTC)
Received: from svn.freebsd.org ([127.0.1.70])
by svn.freebsd.org (8.14.9/8.14.9) with ESMTP id t364lhe0078937;
Mon, 6 Apr 2015 04:47:43 GMT (envelope-from eadler@FreeBSD.org)
Received: (from eadler@localhost)
by svn.freebsd.org (8.14.9/8.14.9/Submit) id t364lfK5078929;
Mon, 6 Apr 2015 04:47:41 GMT (envelope-from eadler@FreeBSD.org)
Message-Id: <201504060447.t364lfK5078929@svn.freebsd.org>
X-Authentication-Warning: svn.freebsd.org: eadler set sender to
eadler@FreeBSD.org using -f
From: Eitan Adler
Date: Mon, 6 Apr 2015 04:47:41 +0000 (UTC)
To: doc-committers@freebsd.org, svn-doc-all@freebsd.org,
svn-doc-head@freebsd.org
Subject: svn commit: r46481 - in head: el_GR.ISO8859-7/articles
el_GR.ISO8859-7/articles/releng-packages en_US.ISO8859-1/articles
en_US.ISO8859-1/articles/releng en_US.ISO8859-1/articles/releng-packages
en_...
X-SVN-Group: doc-head
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
X-BeenThere: svn-doc-head@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: SVN commit messages for the doc tree for head
List-Unsubscribe: ,
List-Archive:
List-Post:
List-Help:
List-Subscribe: ,
X-List-Received-Date: Mon, 06 Apr 2015 04:47:44 -0000
Author: eadler
Date: Mon Apr 6 04:47:40 2015
New Revision: 46481
URL: https://svnweb.freebsd.org/changeset/doc/46481
Log:
releng-packages: remove it
- remove article about releng packages
- we no longer produce multi-cd releases
- CVS is not our VCS system
- we havn't releaseed with xfree86 is years
- section 1 about the 'ports cluster' is now entirely untrue and
been disclaimed by portmgr
Discussed with: peter, bdrewery, Daniel O'Connor
Deleted:
head/el_GR.ISO8859-7/articles/releng-packages/
head/en_US.ISO8859-1/articles/releng-packages/
head/fr_FR.ISO8859-1/articles/releng-packages/
head/ru_RU.KOI8-R/articles/releng-packages/
Modified:
head/el_GR.ISO8859-7/articles/Makefile
head/en_US.ISO8859-1/articles/Makefile
head/en_US.ISO8859-1/articles/releng/article.xml
head/en_US.ISO8859-1/htdocs/docs/books.xml
head/fr_FR.ISO8859-1/articles/Makefile
head/ja_JP.eucJP/articles/Makefile
head/ru_RU.KOI8-R/articles/Makefile
head/share/xml/urls.ent
Modified: head/el_GR.ISO8859-7/articles/Makefile
==============================================================================
--- head/el_GR.ISO8859-7/articles/Makefile Sun Apr 5 16:49:33 2015 (r46480)
+++ head/el_GR.ISO8859-7/articles/Makefile Mon Apr 6 04:47:40 2015 (r46481)
@@ -15,7 +15,6 @@ SUBDIR+= nanobsd
SUBDIR+= new-users
SUBDIR+= problem-reports
SUBDIR+= releng
-SUBDIR+= releng-packages
DOC_PREFIX?= ${.CURDIR}/../..
.include "${DOC_PREFIX}/share/mk/doc.project.mk"
Modified: head/en_US.ISO8859-1/articles/Makefile
==============================================================================
--- head/en_US.ISO8859-1/articles/Makefile Sun Apr 5 16:49:33 2015 (r46480)
+++ head/en_US.ISO8859-1/articles/Makefile Mon Apr 6 04:47:40 2015 (r46481)
@@ -32,7 +32,6 @@ SUBDIR+= problem-reports
SUBDIR+= rc-scripting
SUBDIR+= relaydelay
SUBDIR+= releng
-SUBDIR+= releng-packages
SUBDIR+= remote-install
SUBDIR+= serial-uart
SUBDIR+= solid-state
Modified: head/en_US.ISO8859-1/articles/releng/article.xml
==============================================================================
--- head/en_US.ISO8859-1/articles/releng/article.xml Sun Apr 5 16:49:33 2015 (r46480)
+++ head/en_US.ISO8859-1/articles/releng/article.xml Mon Apr 6 04:47:40 2015 (r46481)
@@ -1,7 +1,6 @@
The Release Engineering of Third Party Packages'>
]>
@@ -728,12 +727,6 @@
is responsible for maintaining a consistent ports tree that can be used
to create the binary packages that accompany official &os;
releases.
-
- The release engineering activities for our collection of
- third-party packages is beyond the scope of this document. A
- separate article, &art.re.pkgs;, covers this topic
- in depth.
-
@@ -797,17 +790,6 @@
- Discs 3 and 4
-
- The remaining two discs contain additional software
- packages for &os;. The packages should be clustered so that
- a package and all of its dependencies are
- included on the same disc. More information about the
- creation of these discs is provided in the &art.re.pkgs;
- article.
-
-
- Multi-volume supportSysinstall supports multiple
Modified: head/en_US.ISO8859-1/htdocs/docs/books.xml
==============================================================================
--- head/en_US.ISO8859-1/htdocs/docs/books.xml Sun Apr 5 16:49:33 2015 (r46480)
+++ head/en_US.ISO8859-1/htdocs/docs/books.xml Mon Apr 6 04:47:40 2015 (r46481)
@@ -247,18 +247,6 @@
interested in producing customized FreeBSD releases for
corporate rollouts or commercial productization.
-
FreeBSD
- Release Engineering for Third Party Packages
- (releng-packages)
- Describes the approach used by the FreeBSD ports management team
- to produce a high quality package set suitable for official
- FreeBSD release media. This document is a work in progress, but
- eventually it will cover the process used to build a clean
- package set on the FreeBSD.org "Ports Cluster", how to configure
- any other set of machines as a ports cluster, how to split up
- the packages for the release media, and how to verify that a
- package set is consistent.
-
Remote
Installation of the &os; Operating System without a
Remote Console (remote-install)
Modified: head/fr_FR.ISO8859-1/articles/Makefile
==============================================================================
--- head/fr_FR.ISO8859-1/articles/Makefile Sun Apr 5 16:49:33 2015 (r46480)
+++ head/fr_FR.ISO8859-1/articles/Makefile Mon Apr 6 04:47:40 2015 (r46481)
@@ -21,7 +21,6 @@ SUBDIR+= new-users
SUBDIR+= pam
SUBDIR+= pr-guidelines
SUBDIR+= problem-reports
-SUBDIR+= releng-packages
ROOT_SYMLINKS+= new-users
Modified: head/ja_JP.eucJP/articles/Makefile
==============================================================================
--- head/ja_JP.eucJP/articles/Makefile Sun Apr 5 16:49:33 2015 (r46480)
+++ head/ja_JP.eucJP/articles/Makefile Mon Apr 6 04:47:40 2015 (r46481)
@@ -34,7 +34,6 @@ SUBDIR+= problem-reports
#SUBDIR+= rc-scripting
#SUBDIR+= relaydelay
#SUBDIR+= releng
-#SUBDIR+= releng-packages
#SUBDIR+= remote-install
#SUBDIR+= serial-uart
#SUBDIR+= solid-state
Modified: head/ru_RU.KOI8-R/articles/Makefile
==============================================================================
--- head/ru_RU.KOI8-R/articles/Makefile Sun Apr 5 16:49:33 2015 (r46480)
+++ head/ru_RU.KOI8-R/articles/Makefile Mon Apr 6 04:47:40 2015 (r46481)
@@ -27,7 +27,6 @@ SUBDIR+= pr-guidelines
SUBDIR+= problem-reports
SUBDIR+= relaydelay
SUBDIR+= releng
-SUBDIR+= releng-packages
#SUBDIR+= serial-uart
SUBDIR+= solid-state
#SUBDIR+= vinum
Modified: head/share/xml/urls.ent
==============================================================================
--- head/share/xml/urls.ent Sun Apr 5 16:49:33 2015 (r46480)
+++ head/share/xml/urls.ent Mon Apr 6 04:47:40 2015 (r46481)
@@ -104,7 +104,6 @@
-
From owner-svn-doc-head@FreeBSD.ORG Mon Apr 6 05:11:52 2015
Return-Path:
Delivered-To: svn-doc-head@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
(using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
(No client certificate requested)
by hub.freebsd.org (Postfix) with ESMTPS id 87195928;
Mon, 6 Apr 2015 05:11:52 +0000 (UTC)
Received: from svn.freebsd.org (svn.freebsd.org
[IPv6:2001:1900:2254:2068::e6a:0])
(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
(Client did not present a certificate)
by mx1.freebsd.org (Postfix) with ESMTPS id 6E02528;
Mon, 6 Apr 2015 05:11:52 +0000 (UTC)
Received: from svn.freebsd.org ([127.0.1.70])
by svn.freebsd.org (8.14.9/8.14.9) with ESMTP id t365BqGC090401;
Mon, 6 Apr 2015 05:11:52 GMT (envelope-from eadler@FreeBSD.org)
Received: (from eadler@localhost)
by svn.freebsd.org (8.14.9/8.14.9/Submit) id t365BoFL090394;
Mon, 6 Apr 2015 05:11:50 GMT (envelope-from eadler@FreeBSD.org)
Message-Id: <201504060511.t365BoFL090394@svn.freebsd.org>
X-Authentication-Warning: svn.freebsd.org: eadler set sender to
eadler@FreeBSD.org using -f
From: Eitan Adler
Date: Mon, 6 Apr 2015 05:11:50 +0000 (UTC)
To: doc-committers@freebsd.org, svn-doc-all@freebsd.org,
svn-doc-head@freebsd.org
Subject: svn commit: r46482 - in head: de_DE.ISO8859-1/articles
de_DE.ISO8859-1/articles/contributing-ports en_US.ISO8859-1/articles
en_US.ISO8859-1/articles/contributing en_US.ISO8859-1/articles/contributi...
X-SVN-Group: doc-head
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
X-BeenThere: svn-doc-head@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: SVN commit messages for the doc tree for head
List-Unsubscribe: ,
List-Archive:
List-Post:
List-Help:
List-Subscribe: ,
X-List-Received-Date: Mon, 06 Apr 2015 05:11:52 -0000
Author: eadler
Date: Mon Apr 6 05:11:49 2015
New Revision: 46482
URL: https://svnweb.freebsd.org/changeset/doc/46482
Log:
contributing and contributing-ports: combine them
- combine the 'how to contribute' doc and the 'contributing to ports' doc.
- modernize the 'contributing to ports' doc
- use &os;
- prefer poudriere to tinderbox
Reviewed by: crees, bapt, mat
No objections from: bdrewery, gavin, wblock
Deleted:
head/de_DE.ISO8859-1/articles/contributing-ports/
head/en_US.ISO8859-1/articles/contributing-ports/
head/fr_FR.ISO8859-1/articles/contributing-ports/
head/nl_NL.ISO8859-1/articles/contributing-ports/
head/pt_BR.ISO8859-1/articles/contributing-ports/
Modified:
head/de_DE.ISO8859-1/articles/Makefile
head/en_US.ISO8859-1/articles/Makefile
head/en_US.ISO8859-1/articles/contributing/article.xml
head/fr_FR.ISO8859-1/articles/Makefile
head/ja_JP.eucJP/articles/Makefile
head/nl_NL.ISO8859-1/articles/Makefile
head/pt_BR.ISO8859-1/articles/Makefile
Modified: head/de_DE.ISO8859-1/articles/Makefile
==============================================================================
--- head/de_DE.ISO8859-1/articles/Makefile Mon Apr 6 04:47:40 2015 (r46481)
+++ head/de_DE.ISO8859-1/articles/Makefile Mon Apr 6 05:11:49 2015 (r46482)
@@ -6,7 +6,6 @@
# basiert auf: 1.42
SUBDIR = contributing
-gUBDIR+= contributing-ports
SUBDIR+= explaining-bsd
SUBDIR+= freebsd-update-server
SUBDIR+= nanobsd
Modified: head/en_US.ISO8859-1/articles/Makefile
==============================================================================
--- head/en_US.ISO8859-1/articles/Makefile Mon Apr 6 04:47:40 2015 (r46481)
+++ head/en_US.ISO8859-1/articles/Makefile Mon Apr 6 05:11:49 2015 (r46482)
@@ -5,7 +5,6 @@ SUBDIR+= bsdl-gpl
SUBDIR+= building-products
SUBDIR+= committers-guide
SUBDIR+= contributing
-SUBDIR+= contributing-ports
SUBDIR+= contributors
SUBDIR+= cups
SUBDIR+= explaining-bsd
Modified: head/en_US.ISO8859-1/articles/contributing/article.xml
==============================================================================
--- head/en_US.ISO8859-1/articles/contributing/article.xml Mon Apr 6 04:47:40 2015 (r46481)
+++ head/en_US.ISO8859-1/articles/contributing/article.xml Mon Apr 6 05:11:49 2015 (r46482)
@@ -12,7 +12,9 @@
- JordanHubbardContributed by
+ JordanHubbard
+ SamLawrance
+ MarkLinimon
@@ -28,20 +30,22 @@
contributing
- So you want to contribute to FreeBSD? That is great! FreeBSD
+ So you want to contribute to &os;? That is great! &os;
relies on the contributions of its user base
to survive. Your contributions are not only appreciated, they are
- vital to FreeBSD's continued growth.
+ vital to &os;'s continued growth.
- Contrary to what some people might have you believe, you do
- not need to be a hot-shot programmer or a close personal friend of
- the FreeBSD core team to have your contributions accepted. A
- large and growing number of international contributors, of greatly
- varying ages and areas of technical expertise, develop FreeBSD.
- There is always more work to be done than there are people
+ A large and growing number of international contributors, of
+ greatly varying ages and areas of technical expertise, develop
+ &os;. There is always more work to be done than there are people
available to do it, and more help is always appreciated.
- The FreeBSD project is responsible for an entire operating
+ As a volunteer, what you do is limited only by what you want
+ to do. However, we do ask that you are aware of what other
+ members of the &os; community will expect of you. You may want
+ to take this into account before deciding to volunteer.
+
+ The &os; project is responsible for an entire operating
system environment, rather than just a kernel or a few scattered
utilities. As such, our TODO lists span a
very wide range of tasks: from documentation, beta testing and
@@ -218,8 +222,53 @@
- Pick one of the items from the Ideas
- page
+ Ongoing Ports Tasks
+
+ The Ports Collection is a perpetual work in progress. We
+ want to provide our users with an easy to use, up to date, high
+ quality repository of third party software. We need people to
+ donate some of their time and effort to help us achieve this
+ goal.
+
+ Anyone can get involved, and there are lots of different
+ ways to do so. Contributing to ports is an excellent way to
+ help give back something to the project.
+ Whether you are looking for an ongoing role, or a fun challenge
+ for a rainy day, we would love to have your help!
+
+ There are a number of easy ways you can contribute to
+ keeping the ports tree up to date and in good working
+ order:
+
+
+
+ Find some cool or useful software and
+ create a port
+ for it.
+
+
+
+ There are a large number of ports that have no
+ maintainer. Become a maintainer and
+ adopt a port.
+
+
+
+ If you have created or adopted a port, be
+ aware of what you need to do
+ as a maintainer.
+
+
+
+ When you are looking for a quick challenge you
+ could fix a bug or a broken
+ port.
+
+
+
+
+
+ Pick one of the items from the Ideas pageThe &os;
list of projects and ideas for volunteers is also
@@ -441,5 +490,711 @@
+
+ Contributing to ports
+
+
+ Adopting an unmaintained port
+
+
+ Choosing an unmaintained port
+
+ Taking over maintainership of ports that are
+ unmaintained is a great way to get involved. Unmaintained
+ ports are only updated and fixed when somebody volunteers to
+ work on them. There are a large number of unmaintained
+ ports. It is a good idea to start with adopting a port that
+ you use regularly.
+
+ Unmaintained ports have their
+ MAINTAINER set to
+ ports@FreeBSD.org. A list of unmaintained
+ ports and their current errors and problem reports can be seen
+ at the &os;
+ Ports Monitoring System.
+
+ Some ports affect a large number of others due to
+ dependencies and slave port relationships. Generally, we
+ want people to have some experience before they maintain such
+ ports.
+
+ You can find out whether or not a port has dependencies
+ or slave ports by looking at a master index of ports called
+ INDEX. (The name of the file varies
+ by release of &os;; for instance,
+ INDEX-8.) Some ports have conditional
+ dependencies that are not included in a default
+ INDEX build. We expect you to be able to
+ recognize such ports by looking through other ports'
+ Makefiles.
+
+
+
+ How to adopt the port
+
+ First make sure you understand your
+ responsibilities as a
+ maintainer. Also read the
+ Porter's
+ Handbook. Please do not commit yourself
+ to more than you feel you can comfortably
+ handle.
+
+ You may request maintainership of any unmaintained port
+ as soon as you wish. Simply set MAINTAINER
+ to your own email address and send a PR (Problem Report) with
+ the change. If the port has build errors or needs updating,
+ you may wish to include any other changes in the same PR.
+ This will help because many committers are less willing to
+ assign maintainership to someone who does not have a known
+ track record with &os;. Submitting PRs that fix build errors
+ or update ports are the best ways to establish one.
+
+ File your PR with category ports and
+ class change-request. A committer will
+ examine your PR, commit the changes, and finally close the
+ PR. Sometimes this process can take a little while
+ (committers are volunteers, too :).
+
+
+
+
+ The challenge for port maintainers
+
+ This section will give you an idea of why ports need to be
+ maintained and outline the responsibilities of a port
+ maintainer.
+
+
+ Why ports require maintenance
+
+ Creating a port is a once-off task. Ensuring that a
+ port is up to date and continues to build and run requires
+ an ongoing maintenance effort. Maintainers are the people
+ who dedicate some of their time to meeting these goals.
+
+ The foremost reason ports need maintenance is to bring
+ the latest and greatest in third party software to the &os;
+ community. An additional challenge is to keep individual
+ ports working within the Ports Collection framework as it
+ evolves.
+
+ As a maintainer, you will need to manage the following
+ challenges:
+
+
+
+
+ New software versions and updates.
+
+ New versions and updates of existing ported
+ software become available all the time, and these need
+ to be incorporated into the Ports Collection in order
+ to provide up-to-date software.
+
+
+
+
+
+ Changes to dependencies.
+
+ If significant changes are made to the dependencies
+ of your port, it may need to be updated so that it will
+ continue to work correctly.
+
+
+
+
+
+ Changes affecting dependent ports.
+
+ If other ports depend on a port that you maintain,
+ changes to your port may require coordination with
+ other maintainers.
+
+
+
+
+
+ Interaction with other users, maintainers and
+ developers.
+
+ Part of being a maintainer is taking on a support
+ role. You are not expected to provide general support
+ (but we welcome it if you choose to do so). What you
+ should provide is a point of coordination for
+ &os;-specific issues regarding your ports.
+
+
+
+
+
+ Bug hunting.
+
+ A port may be affected by bugs which are specific
+ to &os;. You will need to investigate, find, and fix
+ these bugs when they are reported. Thoroughly testing
+ a port to identify problems before they make their way
+ into the Ports Collection is even better.
+
+
+
+
+
+ Changes to ports infrastructure and policy.
+
+ Occasionally the systems that are used to build
+ ports and packages are updated or a new recommendation
+ affecting the infrastructure is made. You should be
+ aware of these changes in case your ports are affected
+ and require updating.
+
+
+
+
+
+ Changes to the base system.
+
+ &os; is under constant development. Changes to
+ software, libraries, the kernel or even policy changes
+ can cause flow-on change requirements to ports.
+
+
+
+
+
+
+ Maintainer responsibilities
+
+
+ Keep your ports up to date
+
+ This section outlines the process to follow to keep your
+ ports up to date.
+
+ This is an overview. More information about upgrading a
+ port is available in the
+
+ Porter's Handbook.
+
+
+
+ Watch for updates
+
+ Monitor the upstream vendor for new versions,
+ updates and security fixes for the software.
+ Announcement mailing lists or news web pages are useful
+ for doing this. Sometimes users will contact you and
+ ask when your port will be updated. If you are busy
+ with other things or for any reason just cannot update
+ it at the moment, ask if they will help you by
+ submitting an update.
+
+ You may also receive automated email from the
+ &os; Ports Version Check informing
+ you that a newer version of your port's distfile is
+ available. More information about that system
+ (including how to stop future emails) will be provided
+ in the message.
+
+
+
+ Incorporate changes
+
+ When they become available, incorporate the changes
+ into the port. You need to be able to generate a patch
+ between the original port and your updated port.
+
+
+
+ Review and test
+
+ Thoroughly review and test your changes:
+
+
+
+ Build, install and test your port on as many
+ platforms and architectures as you can. It is
+ common for a port to work on one branch or platform
+ and fail on another.
+
+
+
+ Make sure your port's dependencies are complete.
+ The recommended way of doing this is by installing
+ your own ports tinderbox.
+ See resources
+ for more information.
+
+
+
+ Check that the packing list is up to date. This
+ involves adding in any new files and directories and
+ removing unused entries.
+
+
+
+ Verify your port using &man.portlint.1; as a
+ guide. See resources for important
+ information about using
+ portlint.
+
+
+
+ Consider whether changes to your port might
+ cause any other ports to break. If this is the
+ case, coordinate the changes with the maintainers of
+ those ports. This is especially important if your
+ update changes the shared library version; in this
+ case, at the very least, the dependent ports will
+ need to get a PORTREVISION bump
+ so that they will automatically be upgraded by
+ automated tools such as
+ portmaster or
+ &man.portupgrade.1;.
+
+
+
+
+
+ Submit changes
+
+ Send your update by submitting a PR with an
+ explanation of the changes and a patch containing the
+ differences between the original port and the updated
+ one. Please refer to Writing FreeBSD
+ Problem Reports for information on how to
+ write a really good PR.
+
+
+ Please do not submit a &man.shar.1; archive of the
+ entire port; instead, use &man.diff.1;
+ -ruN. In this way, committers can
+ much more easily see exactly what changes are being
+ made. The Porter's Handbook section on Upgrading
+ has more information.
+
+
+
+
+ Wait
+
+ At some stage a committer will deal with your PR.
+ It may take minutes, or it may take weeks — so
+ please be patient.
+
+
+
+ Give feedback
+
+ If a committer finds a problem with your changes,
+ they will most likely refer it back to you. A prompt
+ response will help get your PR committed faster, and
+ is better for maintaining a thread of conversation
+ when trying to resolve any problems.
+
+
+
+ And Finally
+
+ Your changes will be committed and your port will
+ have been updated. The PR will then be closed by the
+ committer. That's it!
+
+
+
+
+
+ Ensure your ports continue to build correctly
+
+ This section is about discovering and fixing problems
+ that stop your ports from building correctly.
+
+ &os; only guarantees that the Ports Collection works on
+ the -STABLE branches.
+ In
+ theory, you should be able to get by with running the latest
+ release of each stable branch (since the ABIs are not
+ supposed to change) but if you can run the branch, that is
+ even better.
+
+ Since the majority of &os; installations run on
+ PC-compatible machines (what is termed the
+ i386 architecture), we expect you to keep
+ the port working on that architecture. We prefer that ports
+ also work on the amd64 architecture
+ running native. It is completely fair to ask for help if
+ you do not have one of these machines.
+
+
+ The usual failure modes for
+ non-x86 machines are that the original
+ programmers assumed that, for instance, pointers are
+ ints, or that a relatively lax older
+ gcc compiler was being used.
+ More and more, application authors are reworking their
+ code to remove these assumptions — but if the author
+ is not actively maintaining their code, you may need to do
+ this yourself.
+
+
+ These are the tasks you need to perform to ensure your
+ port is able to be built:
+
+
+
+ Watch for build failures
+
+ Check your mail for mail from
+ pkg-fallout@FreeBSD.org
+ and the distfiles scanner
+ to see if any of the port which are failing to build
+ are out of date.
+
+
+
+ Collect information
+
+ Once you are aware of a problem, collect information
+ to help you fix it. Build errors reported by
+ pkg-fallout are accompanied by logs
+ which will show you where the build failed. If the
+ failure was reported to you by a user, ask them to send
+ you information which may help in diagnosing the
+ problem, such as:
+
+
+
+ Build logs
+
+
+
+ The commands and options used to build the
+ port (including options set in
+ /etc/make.conf)
+
+
+
+ A list of packages installed on their system
+ as shown by &man.pkg.info.1;
+
+
+
+ The version of &os; they are running as
+ shown by &man.uname.1; -a
+
+
+
+ When their ports collection was last
+ updated
+
+
+
+ When their ports tree amd
+ INDEX was last updated
+
+
+
+
+
+ Investigate and find a solution
+
+ Unfortunately there is no straightforward process to
+ follow to do this. Remember, though: if you are stuck,
+ ask for help! The &a.ports; is a good place to start,
+ and the upstream developers are often very
+ helpful.
+
+
+
+ Submit changes
+
+ Just as with updating a port, you should now
+ incorporate changes, review and test, submit your
+ changes in a PR, and provide feedback if
+ required.
+
+
+
+ Send patches to upstream authors
+
+ In some cases, you will have to make patches to the
+ port to make it run on FreeBSD. Some (but not all)
+ upstream authors will accept such patches back into
+ their code for the next release. If so, this may even
+ help their users on other BSD-based systems as well and
+ perhaps save duplicated effort. Please consider sending
+ any applicable patches to the authors as a
+ courtesy.
+
+
+
+
+
+
+ Investigate bug reports and PRs related to your
+ port
+
+ This section is about discovering and fixing
+ bugs.
+
+ &os;-specific bugs are generally caused by assumptions
+ about the build and runtime environments that do not apply
+ to &os;. You are less likely to encounter a problem of this
+ type, but it can be more subtle and difficult to
+ diagnose.
+
+ These are the tasks you need to perform to ensure your
+ port continues to work as intended:
+
+
+
+ Respond to bug reports
+
+ Bugs may be reported to you through email via the
+
+ Problem Report database. Bugs may also be
+ reported directly to you by users.
+
+ You should respond to PRs and other reports within
+ 14 days, but please try not to take that long. Try to
+ respond as soon as possible, even if it is just to say
+ you need some more time before you can work on the
+ PR.
+
+ If you have not responded after 14 days, any
+ committer may commit from a PR that you have not
+ responded to via a
+ maintainer-timeout.
+
+
+
+ Collect information
+
+ If the person reporting the bug has not also
+ provided a fix, you need to collect the information that
+ will allow you to generate one.
+
+ If the bug is reproducible, you can collect most of
+ the required information yourself. If not, ask the
+ person who reported the bug to collect the information
+ for you, such as:
+
+
+
+ A detailed description of their actions,
+ expected program behavior and actual behavior
+
+
+
+ Copies of input data used to trigger the
+ bug
+
+
+
+ Information about their build and execution
+ environment — for example, a list of installed
+ packages and the output of &man.env.1;
+
+
+
+ Core dumps
+
+
+
+ Stack traces
+
+
+
+
+
+ Eliminate incorrect reports
+
+ Some bug reports may be incorrect. For example,
+ the user may have simply misused the program; or their
+ installed packages may be out of date and require
+ updating. Sometimes a reported bug is not specific to
+ &os;. In this case report the bug to the upstream
+ developers. If the bug is within your capabilities to
+ fix, you can also patch the port so that the fix is
+ applied before the next upstream release.
+
+
+
+ Find a solution
+
+ As with build errors, you will need to sort out a
+ fix to the problem. Again, remember to ask if you are
+ stuck!
+
+
+
+ Submit or approve changes
+
+ Just as with updating a port, you should now
+ incorporate changes, review and test, and submit your
+ changes in a PR (or send a follow-up if a PR already
+ exists for the problem). If another user has submitted
+ changes in the PR, you can also send a follow-up saying
+ whether or not you approve the changes.
+
+
+
+
+
+ Providing support
+
+ Part of being a maintainer is providing support —
+ not for the software in general — but for the port and
+ any &os;-specific quirks and problems. Users may contact
+ you with questions, suggestions, problems and patches. Most
+ of the time their correspondence will be specific to
+ &os;.
+
+ Occasionally you may have to invoke your skills in
+ diplomacy, and kindly point users seeking general support to
+ the appropriate resources. Less frequently you will
+ encounter a person asking why the RPMs
+ are not up to date or how can they get the software to run
+ under Foo Linux. Take the opportunity to tell them that
+ your port is up to date (if it is, of course!), and suggest
+ that they try &os;.
+
+ Sometimes users and developers will decide that you are
+ a busy person whose time is valuable and do some of the work
+ for you. For example, they might:
+
+
+
+ submit a PR or send you patches to update your
+ port,
+
+
+
+ investigate and perhaps provide a fix to a PR,
+ or
+
+
+
+ otherwise submit changes to your port.
+
+
+
+ In these cases your main obligation is to respond in a
+ timely manner. Again, the timeout for non-responsive
+ maintainers is 14 days. After this period changes may be
+ committed unapproved. They have taken the trouble to do
+ this for you; so please try to at least respond promptly.
+ Then review, approve, modify or discuss their changes with
+ them as soon as possible.
+
+ If you can make them feel that their contribution is
+ appreciated (and it should be) you will have a better chance
+ persuading them to do more things for you in the future
+ :-).
+
+
+
+
+
+ Finding and fixing a broken port
+
+ There are two really good places to find a port that needs
+ some attention.
+
+ You can use the web
+ interface to the Problem Report database to search
+ through and view unresolved PRs. The majority of ports PRs are
+ updates, but with a little searching and skimming over synopses
+ you should be able to find something interesting to work on (the
+ sw-bug class is a good place to
+ start).
+
+ The other place is the &os; Ports Monitoring
+ System. In particular look for unmaintained ports
+ with build errors and ports that are marked
+ BROKEN. It is OK to send changes for a
+ maintained port as well, but remember to ask the maintainer in
+ case they are already working on the problem.
+
+ Once you have found a bug or problem, collect information,
+ investigate and fix! If there is an existing PR, follow up to
+ that. Otherwise create a new PR. Your changes will be reviewed
+ and, if everything checks out, committed.
+
+
+
+ When to call it quits
+
+ As your interests and commitments change, you may find that
+ you no longer have time to continue some (or all) of your ports
+ contributions. That is fine! Please let us know if you are no
+ longer using a port or have otherwise lost time or interest in
+ being a maintainer. In this way we can go ahead and allow other
+ people to try to work on existing problems with the port without
+ waiting for your response. Remember, &os; is a volunteer
+ project, so if maintaining a port is no fun anymore, it is
+ probably time to let someone else do it!
+
+ In any case, the Ports Management Team
+ (portmgr) reserves the right to reset your
+ maintainership if you have not actively maintained your port in
+ some time. (Currently, this is set to 3 months.) By this, we
+ mean that there are unresolved problems or pending updates that
+ have not been worked on during that time.
+
+
+
+ Resources for ports maintainers and contributors
+
+ The Porter's
+ Handbook is your hitchhiker's guide to the ports
+ system. Keep it handy!
+
+ Writing FreeBSD
+ Problem Reports describes how to best formulate and
+ submit a PR. In 2005 more than eleven thousand ports PRs were
+ submitted! Following this article will greatly assist us in
+ reducing the time needed to handle your PRs.
+
+ The
+ Problem Report database.
+
+ The FreeBSD Ports
+ Monitoring System can show you cross-referenced
+ information about ports such as build errors and problem
+ reports. If you are a maintainer you can use it to check on the
+ build status of your ports. As a contributor you can use it to
+ find broken and unmaintained ports that need to be fixed.
+
+ The FreeBSD Ports
+ distfile scanner can show you ports for which the
+ distfiles are not fetchable. You can check on your own ports or
+ use it to find ports that need their
+ MASTER_SITES updated.
+
+ ports-mgmt/poudriere is the most
+ thorough way to test a port through the entire cycle of
+ installation, packaging, and deinstallation.
+ documentation is located at the
+ poudriere home page
+
+ &man.portlint.1; is an application which can be used to
+ verify that your port conforms to many important stylistic and
+ functional guidelines. portlint is a
+ simple heuristic application, so you should use it
+ only as a guide. If
+ portlint suggests changes which seem
+ unreasonable, consult the Porter's Handbook
+ or ask for advice.
+
+ The &a.ports; is for general ports-related discussion. It
+ is a good place to ask for help. You can subscribe, or
+ read and search the list archives. Reading the
+ archives of the &a.ports-bugs; and the &a.cvs-ports; may also be
+ of interest.
+
+
+
Modified: head/fr_FR.ISO8859-1/articles/Makefile
==============================================================================
--- head/fr_FR.ISO8859-1/articles/Makefile Mon Apr 6 04:47:40 2015 (r46481)
+++ head/fr_FR.ISO8859-1/articles/Makefile Mon Apr 6 05:11:49 2015 (r46482)
@@ -9,7 +9,6 @@
SUBDIR = building-products
SUBDIR+= committers-guide
SUBDIR+= contributing
-SUBDIR+= contributing-ports
SUBDIR+= contributors
SUBDIR+= explaining-bsd
SUBDIR+= filtering-bridges
Modified: head/ja_JP.eucJP/articles/Makefile
==============================================================================
--- head/ja_JP.eucJP/articles/Makefile Mon Apr 6 04:47:40 2015 (r46481)
+++ head/ja_JP.eucJP/articles/Makefile Mon Apr 6 05:11:49 2015 (r46482)
@@ -7,7 +7,6 @@ SUBDIR =
#SUBDIR+= committers-guide
#SUBDIR+= console-server
SUBDIR+= contributing
-#SUBDIR+= contributing-ports
SUBDIR+= contributors
#SUBDIR+= cups
#SUBDIR+= explaining-bsd
Modified: head/nl_NL.ISO8859-1/articles/Makefile
==============================================================================
--- head/nl_NL.ISO8859-1/articles/Makefile Mon Apr 6 04:47:40 2015 (r46481)
+++ head/nl_NL.ISO8859-1/articles/Makefile Mon Apr 6 05:11:49 2015 (r46482)
@@ -5,7 +5,6 @@
SUBDIR =
SUBDIR+= contributing
-SUBDIR+= contributing-ports
SUBDIR+= explaining-bsd
SUBDIR+= problem-reports
SUBDIR+= solid-state
Modified: head/pt_BR.ISO8859-1/articles/Makefile
==============================================================================
--- head/pt_BR.ISO8859-1/articles/Makefile Mon Apr 6 04:47:40 2015 (r46481)
+++ head/pt_BR.ISO8859-1/articles/Makefile Mon Apr 6 05:11:49 2015 (r46482)
@@ -11,7 +11,6 @@
SUBDIR =
SUBDIR+= building-products
SUBDIR+= contributing
-SUBDIR+= contributing-ports
SUBDIR+= explaining-bsd
SUBDIR+= freebsd-questions
SUBDIR+= freebsd-update-server
From owner-svn-doc-head@FreeBSD.ORG Mon Apr 6 05:16:10 2015
Return-Path:
Delivered-To: svn-doc-head@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
(using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
(No client certificate requested)
by hub.freebsd.org (Postfix) with ESMTPS id 60574A3E;
Mon, 6 Apr 2015 05:16:10 +0000 (UTC)
Received: from svn.freebsd.org (svn.freebsd.org
[IPv6:2001:1900:2254:2068::e6a:0])
(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
(Client did not present a certificate)
by mx1.freebsd.org (Postfix) with ESMTPS id 4B3EA127;
Mon, 6 Apr 2015 05:16:10 +0000 (UTC)
Received: from svn.freebsd.org ([127.0.1.70])
by svn.freebsd.org (8.14.9/8.14.9) with ESMTP id t365GAQV092868;
Mon, 6 Apr 2015 05:16:10 GMT (envelope-from eadler@FreeBSD.org)
Received: (from eadler@localhost)
by svn.freebsd.org (8.14.9/8.14.9/Submit) id t365GA0D092867;
Mon, 6 Apr 2015 05:16:10 GMT (envelope-from eadler@FreeBSD.org)
Message-Id: <201504060516.t365GA0D092867@svn.freebsd.org>
X-Authentication-Warning: svn.freebsd.org: eadler set sender to
eadler@FreeBSD.org using -f
From: Eitan Adler
Date: Mon, 6 Apr 2015 05:16:10 +0000 (UTC)
To: doc-committers@freebsd.org, svn-doc-all@freebsd.org,
svn-doc-head@freebsd.org
Subject: svn commit: r46483 - head/en_US.ISO8859-1/articles/releng
X-SVN-Group: doc-head
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
X-BeenThere: svn-doc-head@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: SVN commit messages for the doc tree for head
List-Unsubscribe: ,
List-Archive:
List-Post:
List-Help:
List-Subscribe: ,
X-List-Received-Date: Mon, 06 Apr 2015 05:16:10 -0000
Author: eadler
Date: Mon Apr 6 05:16:09 2015
New Revision: 46483
URL: https://svnweb.freebsd.org/changeset/doc/46483
Log:
Migrate www/ repo to htdocs/
Modified:
head/en_US.ISO8859-1/articles/releng/article.xml
Modified: head/en_US.ISO8859-1/articles/releng/article.xml
==============================================================================
--- head/en_US.ISO8859-1/articles/releng/article.xml Mon Apr 6 05:11:49 2015 (r46482)
+++ head/en_US.ISO8859-1/articles/releng/article.xml Mon Apr 6 05:16:09 2015 (r46483)
@@ -445,6 +445,15 @@
+ doc/en_US.ISO8859-1/htdocs/cgi/ports.cgi
+
+
+
+ ports/Tools/scripts/release/config
+
+
+
+ doc/share/xml/freebsd.ent
@@ -489,17 +498,8 @@
- www/en/docs/man.xml
+ doc/en_US.ISO8859-1/htdocs/search/opensearch/man.xml
-
-
- www/en/cgi/ports.cgi
-
-
-
- ports/Tools/scripts/release/config
-
-
The release notes and errata files also need to be adjusted for the
From owner-svn-doc-head@FreeBSD.ORG Mon Apr 6 05:30:42 2015
Return-Path:
Delivered-To: svn-doc-head@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
[IPv6:2001:1900:2254:206a::19:1])
(using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
(No client certificate requested)
by hub.freebsd.org (Postfix) with ESMTPS id EE79D17D;
Mon, 6 Apr 2015 05:30:42 +0000 (UTC)
Received: from svn.freebsd.org (svn.freebsd.org
[IPv6:2001:1900:2254:2068::e6a:0])
(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
(Client did not present a certificate)
by mx1.freebsd.org (Postfix) with ESMTPS id D84BB2D3;
Mon, 6 Apr 2015 05:30:42 +0000 (UTC)
Received: from svn.freebsd.org ([127.0.1.70])
by svn.freebsd.org (8.14.9/8.14.9) with ESMTP id t365UgHU098506;
Mon, 6 Apr 2015 05:30:42 GMT (envelope-from eadler@FreeBSD.org)
Received: (from eadler@localhost)
by svn.freebsd.org (8.14.9/8.14.9/Submit) id t365UgOi098505;
Mon, 6 Apr 2015 05:30:42 GMT (envelope-from eadler@FreeBSD.org)
Message-Id: <201504060530.t365UgOi098505@svn.freebsd.org>
X-Authentication-Warning: svn.freebsd.org: eadler set sender to
eadler@FreeBSD.org using -f
From: Eitan Adler
Date: Mon, 6 Apr 2015 05:30:42 +0000 (UTC)
To: doc-committers@freebsd.org, svn-doc-all@freebsd.org,
svn-doc-head@freebsd.org
Subject: svn commit: r46484 - head/en_US.ISO8859-1/articles/releng
X-SVN-Group: doc-head
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
X-BeenThere: svn-doc-head@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: SVN commit messages for the doc tree for head
List-Unsubscribe: ,
List-Archive:
List-Post:
List-Help:
List-Subscribe: ,
X-List-Received-Date: Mon, 06 Apr 2015 05:30:43 -0000
Author: eadler
Date: Mon Apr 6 05:30:41 2015
New Revision: 46484
URL: https://svnweb.freebsd.org/changeset/doc/46484
Log:
releng: strip some old things
There is a two year old warning that this document is partly outdated
and that re@ is working on updating it.
I don't see many substantive commits updating this doc, so just do a
drive-by and remove the obviously wrong and outdated things.
- sysinstall has been replaced (and so scripting it is meaningless)
- cross building is possible
- drop support for disk2 and on
- remove empty sections, such as the one on cd-rom replication
Modified:
head/en_US.ISO8859-1/articles/releng/article.xml
Modified: head/en_US.ISO8859-1/articles/releng/article.xml
==============================================================================
--- head/en_US.ISO8859-1/articles/releng/article.xml Mon Apr 6 05:16:09 2015 (r46483)
+++ head/en_US.ISO8859-1/articles/releng/article.xml Mon Apr 6 05:30:41 2015 (r46484)
@@ -5,14 +5,6 @@
&os; Release Engineering
-
-
-
-
- November 2001
- BSDCon Europe
-
-
MurrayStokelyI've been involved in the development of &os; based products
@@ -746,64 +738,6 @@
command:/stage/cdrom&prompt.root; find . -type f | sed -e 's/^\.\///' | sort > filename.txt
-
- The specific requirements of each CD are outlined below.
-
-
- Disc 1
-
- The first disc is almost completely created by
- make
- release. The only changes
- that should be made to the disc1 directory are the addition of
- a tools directory, and as many popular
- third party software packages as will fit on the disc. The
- tools directory contains software that allow users to create
- installation floppies from other operating systems. This disc
- should be made bootable so that users of modern PCs do not
- need to create installation floppy disks.
-
- If a custom kernel of &os; is to be included, then
- &man.sysinstall.8; and &man.release.7; must be updated to
- include installation instructions. The relevant code is contained
- in src/release and src/usr.sbin/sysinstall.
- Specifically, the file src/release/Makefile, and
- dist.c, dist.h,
- menus.c, install.c, and
- Makefile will need to be updated under
- src/usr.sbin/sysinstall. Optionally, you may choose
- to update sysinstall.8.
-
-
-
-
- Disc 2
-
- The second disc is also largely created by make
- release. This disc contains a live
- filesystem that can be used from &man.sysinstall.8; to
- troubleshoot a &os; installation. This disc should be
- bootable and should also contain a compressed copy of the CVS
- repository in the CVSROOT directory and
- commercial software demos in the commerce
- directory.
-
-
-
- Multi-volume support
-
- Sysinstall supports multiple
- volume package installations. This requires that each disc
- have an INDEX file containing all of the
- packages on all volumes of a set, along with an extra field
- that indicates which volume that particular package is on.
- Each volume in the set must also have the
- CD_VOLUME variable set in the
- cdrom.inf file so that sysinstall can
- tell which volume is which. When a user attempts to install a
- package that is not on the current disc, sysinstall will
- prompt the user to insert the appropriate one.
-
@@ -882,13 +816,6 @@
time, for example make it relative to GMT.
-
- CD-ROM Replication
-
- Coming soon: Tips for sending &os; ISOs to a replicator
- and quality assurance measures to be taken.
-
-
@@ -907,25 +834,8 @@
certainly encourage innovation in the form of advanced
installation and administration tools, for example, but we cannot
be expected to answer questions about it.
-
-
- Scripting sysinstall
-
- The &os; system installation and configuration tool,
- &man.sysinstall.8;, can be scripted to provide automated installs
- for large sites. This functionality can be used in conjunction
- with &intel; PXE
-
-
- &url.books.handbook;/network-pxe-nfs.html
-
-
- to bootstrap systems from the network.
-
-
-
Lessons Learned from &os; 4.4
@@ -968,33 +878,12 @@
using multiple processors in speeding up the make
release process. If multiple disks are used for
different hierarchies in the &man.chroot.2;
- environment, then the CVS checkout of the ports and doc trees
+ environment, then the subversion checkout of the ports and doc trees
can be happening simultaneously as the make
world on another disk. Using a
RAID solution (hardware or software) can
significantly decrease the overall build time.
-
-
- Cross-building releases - Building
- IA-64 or Alpha release on x86 hardware? make
- TARGET=ia64 release.
-
-
-
-
- Regression Testing - We need better
- automated correctness testing for &os;.
-
-
-
- Installation Tools - Our installation
- program has long since outlived its intended life span.
- Several projects are under development to provide a more
- advanced installation mechanism. The libh project was one
- such project that aimed to provide an intelligent new package
- framework and GUI installation program.
-
From owner-svn-doc-head@FreeBSD.ORG Mon Apr 6 05:33:29 2015
Return-Path:
Delivered-To: svn-doc-head@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
[IPv6:2001:1900:2254:206a::19:1])
(using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
(No client certificate requested)
by hub.freebsd.org (Postfix) with ESMTPS id 82AAA1D1;
Mon, 6 Apr 2015 05:33:29 +0000 (UTC)
Received: from svn.freebsd.org (svn.freebsd.org
[IPv6:2001:1900:2254:2068::e6a:0])
(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
(Client did not present a certificate)
by mx1.freebsd.org (Postfix) with ESMTPS id 534202E6;
Mon, 6 Apr 2015 05:33:29 +0000 (UTC)
Received: from svn.freebsd.org ([127.0.1.70])
by svn.freebsd.org (8.14.9/8.14.9) with ESMTP id t365XT0t001959;
Mon, 6 Apr 2015 05:33:29 GMT (envelope-from eadler@FreeBSD.org)
Received: (from eadler@localhost)
by svn.freebsd.org (8.14.9/8.14.9/Submit) id t365XTGY001958;
Mon, 6 Apr 2015 05:33:29 GMT (envelope-from eadler@FreeBSD.org)
Message-Id: <201504060533.t365XTGY001958@svn.freebsd.org>
X-Authentication-Warning: svn.freebsd.org: eadler set sender to
eadler@FreeBSD.org using -f
From: Eitan Adler
Date: Mon, 6 Apr 2015 05:33:29 +0000 (UTC)
To: doc-committers@freebsd.org, svn-doc-all@freebsd.org,
svn-doc-head@freebsd.org
Subject: svn commit: r46485 - head/en_US.ISO8859-1/articles/releng
X-SVN-Group: doc-head
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
X-BeenThere: svn-doc-head@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: SVN commit messages for the doc tree for head
List-Unsubscribe: ,
List-Archive:
List-Post:
List-Help:
List-Subscribe: ,
X-List-Received-Date: Mon, 06 Apr 2015 05:33:29 -0000
Author: eadler
Date: Mon Apr 6 05:33:28 2015
New Revision: 46485
URL: https://svnweb.freebsd.org/changeset/doc/46485
Log:
releng: strip some old things
There is a two year old warning that this document is partly outdated
and that re@ is working on updating it.
I don't see many substantive commits updating this doc, so just do a
drive-by and remove the obviously wrong and outdated things.
the article can use some additional work from someone more clueful about
the current re@ process.
- remove sysinstall references
Modified:
head/en_US.ISO8859-1/articles/releng/article.xml
Modified: head/en_US.ISO8859-1/articles/releng/article.xml
==============================================================================
--- head/en_US.ISO8859-1/articles/releng/article.xml Mon Apr 6 05:30:41 2015 (r46484)
+++ head/en_US.ISO8859-1/articles/releng/article.xml Mon Apr 6 05:33:28 2015 (r46485)
@@ -510,18 +510,6 @@
- Sysinstall should be updated to note
- the number of available ports and the amount of disk space required
- for the Ports Collection.
-
-
- &os; Ports Collection
- http://www.FreeBSD.org/ports
-
-
- This information is currently kept in
- src/usr.sbin/sysinstall/dist.c.
-
After the release has been built, a number of files should
be updated to announce the release to the world. These files
are relative to head/ within the
@@ -720,25 +708,6 @@
to create the binary packages that accompany official &os;
releases.
-
-
- Release ISOs
-
- Starting with &os; 4.4, the &os; Project decided to
- release all four ISO images that were previously sold on the
- BSDi/Wind River Systems/FreeBSD Mall
- official CDROM distributions. Each of the four
- discs must contain a README.TXT file that
- explains the contents of the disc, a
- CDROM.INF file that provides meta-data for
- the disc so that &man.sysinstall.8; can validate and use the
- contents, and a filename.txt file that
- provides a manifest for the disc. This
- manifest can be created with a simple
- command:
-
- /stage/cdrom&prompt.root; find . -type f | sed -e 's/^\.\///' | sort > filename.txt
-
From owner-svn-doc-head@FreeBSD.ORG Mon Apr 6 05:52:25 2015
Return-Path:
Delivered-To: svn-doc-head@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
(using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
(No client certificate requested)
by hub.freebsd.org (Postfix) with ESMTPS id 1DDAF47B;
Mon, 6 Apr 2015 05:52:25 +0000 (UTC)
Received: from svn.freebsd.org (svn.freebsd.org
[IPv6:2001:1900:2254:2068::e6a:0])
(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
(Client did not present a certificate)
by mx1.freebsd.org (Postfix) with ESMTPS id 089B866C;
Mon, 6 Apr 2015 05:52:25 +0000 (UTC)
Received: from svn.freebsd.org ([127.0.1.70])
by svn.freebsd.org (8.14.9/8.14.9) with ESMTP id t365qOOp010988;
Mon, 6 Apr 2015 05:52:24 GMT (envelope-from eadler@FreeBSD.org)
Received: (from eadler@localhost)
by svn.freebsd.org (8.14.9/8.14.9/Submit) id t365qOZS010986;
Mon, 6 Apr 2015 05:52:24 GMT (envelope-from eadler@FreeBSD.org)
Message-Id: <201504060552.t365qOZS010986@svn.freebsd.org>
X-Authentication-Warning: svn.freebsd.org: eadler set sender to
eadler@FreeBSD.org using -f
From: Eitan Adler
Date: Mon, 6 Apr 2015 05:52:24 +0000 (UTC)
To: doc-committers@freebsd.org, svn-doc-all@freebsd.org,
svn-doc-head@freebsd.org
Subject: svn commit: r46486 - head/en_US.ISO8859-1/articles/contributing
X-SVN-Group: doc-head
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
X-BeenThere: svn-doc-head@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: SVN commit messages for the doc tree for head
List-Unsubscribe: ,
List-Archive:
List-Post:
List-Help:
List-Subscribe: ,
X-List-Received-Date: Mon, 06 Apr 2015 05:52:25 -0000
Author: eadler
Date: Mon Apr 6 05:52:24 2015
New Revision: 46486
URL: https://svnweb.freebsd.org/changeset/doc/46486
Log:
Just reference the mailing lists, not newgroups
Modified:
head/en_US.ISO8859-1/articles/contributing/article.xml
Modified: head/en_US.ISO8859-1/articles/contributing/article.xml
==============================================================================
--- head/en_US.ISO8859-1/articles/contributing/article.xml Mon Apr 6 05:33:28 2015 (r46485)
+++ head/en_US.ISO8859-1/articles/contributing/article.xml Mon Apr 6 05:52:24 2015 (r46486)
@@ -105,7 +105,7 @@
- Read the &a.questions; and &ng.misc; occasionally (or
+ Read the &a.questions; occasionally (or
even regularly). It can be very satisfying to share your
expertise and help people solve their problems; sometimes
you may even learn something new yourself! These forums
From owner-svn-doc-head@FreeBSD.ORG Mon Apr 6 06:04:56 2015
Return-Path:
Delivered-To: svn-doc-head@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
(using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
(No client certificate requested)
by hub.freebsd.org (Postfix) with ESMTPS id 631856D0;
Mon, 6 Apr 2015 06:04:56 +0000 (UTC)
Received: from svn.freebsd.org (svn.freebsd.org
[IPv6:2001:1900:2254:2068::e6a:0])
(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
(Client did not present a certificate)
by mx1.freebsd.org (Postfix) with ESMTPS id 3437D7A4;
Mon, 6 Apr 2015 06:04:56 +0000 (UTC)
Received: from svn.freebsd.org ([127.0.1.70])
by svn.freebsd.org (8.14.9/8.14.9) with ESMTP id t3664tD5016066;
Mon, 6 Apr 2015 06:04:55 GMT (envelope-from eadler@FreeBSD.org)
Received: (from eadler@localhost)
by svn.freebsd.org (8.14.9/8.14.9/Submit) id t3664taQ016065;
Mon, 6 Apr 2015 06:04:55 GMT (envelope-from eadler@FreeBSD.org)
Message-Id: <201504060604.t3664taQ016065@svn.freebsd.org>
X-Authentication-Warning: svn.freebsd.org: eadler set sender to
eadler@FreeBSD.org using -f
From: Eitan Adler
Date: Mon, 6 Apr 2015 06:04:55 +0000 (UTC)
To: doc-committers@freebsd.org, svn-doc-all@freebsd.org,
svn-doc-head@freebsd.org
Subject: svn commit: r46487 - head/share/tools
X-SVN-Group: doc-head
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
X-BeenThere: svn-doc-head@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: SVN commit messages for the doc tree for head
List-Unsubscribe: ,
List-Archive:
List-Post:
List-Help:
List-Subscribe: ,
X-List-Received-Date: Mon, 06 Apr 2015 06:04:56 -0000
Author: eadler
Date: Mon Apr 6 06:04:55 2015
New Revision: 46487
URL: https://svnweb.freebsd.org/changeset/doc/46487
Log:
buildpnms.sh couldn't possibly work due to a bad path to gozer
also this script is for send-pr which is dead
Deleted:
head/share/tools/buildpnms.sh
From owner-svn-doc-head@FreeBSD.ORG Mon Apr 6 08:47:10 2015
Return-Path:
Delivered-To: svn-doc-head@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
[IPv6:2001:1900:2254:206a::19:1])
(using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
(No client certificate requested)
by hub.freebsd.org (Postfix) with ESMTPS id DB0CBDCC;
Mon, 6 Apr 2015 08:47:09 +0000 (UTC)
Received: from svn.freebsd.org (svn.freebsd.org
[IPv6:2001:1900:2254:2068::e6a:0])
(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
(Client did not present a certificate)
by mx1.freebsd.org (Postfix) with ESMTPS id BC170910;
Mon, 6 Apr 2015 08:47:09 +0000 (UTC)
Received: from svn.freebsd.org ([127.0.1.70])
by svn.freebsd.org (8.14.9/8.14.9) with ESMTP id t368l98r092790;
Mon, 6 Apr 2015 08:47:09 GMT (envelope-from ryusuke@FreeBSD.org)
Received: (from ryusuke@localhost)
by svn.freebsd.org (8.14.9/8.14.9/Submit) id t368l9Wq092789;
Mon, 6 Apr 2015 08:47:09 GMT (envelope-from ryusuke@FreeBSD.org)
Message-Id: <201504060847.t368l9Wq092789@svn.freebsd.org>
X-Authentication-Warning: svn.freebsd.org: ryusuke set sender to
ryusuke@FreeBSD.org using -f
From: Ryusuke SUZUKI
Date: Mon, 6 Apr 2015 08:47:09 +0000 (UTC)
To: doc-committers@freebsd.org, svn-doc-all@freebsd.org,
svn-doc-head@freebsd.org
Subject: svn commit: r46488 - head/ja_JP.eucJP/htdocs/docs
X-SVN-Group: doc-head
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
X-BeenThere: svn-doc-head@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: SVN commit messages for the doc tree for head
List-Unsubscribe: ,
List-Archive:
List-Post:
List-Help:
List-Subscribe: ,
X-List-Received-Date: Mon, 06 Apr 2015 08:47:10 -0000
Author: ryusuke
Date: Mon Apr 6 08:47:08 2015
New Revision: 46488
URL: https://svnweb.freebsd.org/changeset/doc/46488
Log:
- Merge the following from the English version:
r46451 -> r46481 head/ja_JP.eucJP/htdocs/docs/books.xml
Modified:
head/ja_JP.eucJP/htdocs/docs/books.xml
Modified: head/ja_JP.eucJP/htdocs/docs/books.xml
==============================================================================
--- head/ja_JP.eucJP/htdocs/docs/books.xml Mon Apr 6 06:04:55 2015 (r46487)
+++ head/ja_JP.eucJP/htdocs/docs/books.xml Mon Apr 6 08:47:08 2015 (r46488)
@@ -9,7 +9,7 @@
]>
-
+
@@ -102,16 +102,6 @@
Committer's Guide (committers-guide) (±Ñ¸ìÈǤΤß)
FreeBSD committers ¤Î¤¿¤á¤ÎÆþÌç½ñ¤Ç¤¹¡£
-
Installing
- and using Compiz Fusion (compiz-fusion) (±Ñ¸ìÈǤΤß)
- Compiz Fusion ¥³¥ó¥Ý¥¸¥Ã¥È¥¦¥£¥ó¥É¥¦¥Þ¥Í¡¼¥¸¥ã¤ò FreeBSD
- ¤Ë¥¤¥ó¥¹¥È¡¼¥ë¤·¤ÆÍøÍѤ¹¤ëÊýË¡¤Î¾Ò²ð¤Ç¤¹¡£
From owner-svn-doc-head@FreeBSD.ORG Wed Apr 8 11:41:19 2015
Return-Path:
Delivered-To: svn-doc-head@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
[IPv6:2001:1900:2254:206a::19:1])
(using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
(No client certificate requested)
by hub.freebsd.org (Postfix) with ESMTPS id 78B8D886;
Wed, 8 Apr 2015 11:41:19 +0000 (UTC)
Received: from svn.freebsd.org (svn.freebsd.org
[IPv6:2001:1900:2254:2068::e6a:0])
(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
(Client did not present a certificate)
by mx1.freebsd.org (Postfix) with ESMTPS id 625F6984;
Wed, 8 Apr 2015 11:41:19 +0000 (UTC)
Received: from svn.freebsd.org ([127.0.1.70])
by svn.freebsd.org (8.14.9/8.14.9) with ESMTP id t38BfJQW065889;
Wed, 8 Apr 2015 11:41:19 GMT (envelope-from mat@FreeBSD.org)
Received: (from mat@localhost)
by svn.freebsd.org (8.14.9/8.14.9/Submit) id t38BfJuW065888;
Wed, 8 Apr 2015 11:41:19 GMT (envelope-from mat@FreeBSD.org)
Message-Id: <201504081141.t38BfJuW065888@svn.freebsd.org>
X-Authentication-Warning: svn.freebsd.org: mat set sender to mat@FreeBSD.org
using -f
From: Mathieu Arnold
Date: Wed, 8 Apr 2015 11:41:19 +0000 (UTC)
To: doc-committers@freebsd.org, svn-doc-all@freebsd.org,
svn-doc-head@freebsd.org
Subject: svn commit: r46502 -
head/en_US.ISO8859-1/books/porters-handbook/makefiles
X-SVN-Group: doc-head
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
X-BeenThere: svn-doc-head@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: SVN commit messages for the doc tree for head
List-Unsubscribe: ,
List-Archive:
List-Post:
List-Help:
List-Subscribe: ,
X-List-Received-Date: Wed, 08 Apr 2015 11:41:19 -0000
Author: mat
Date: Wed Apr 8 11:41:18 2015
New Revision: 46502
URL: https://svnweb.freebsd.org/changeset/doc/46502
Log:
Reindent/rewrap chapter.
Differential Revision: https://reviews.freebsd.org/D2217
Approved by: wblock (mentor)
Sponsored by: Absolight
Modified:
head/en_US.ISO8859-1/books/porters-handbook/makefiles/chapter.xml
Modified: head/en_US.ISO8859-1/books/porters-handbook/makefiles/chapter.xml
==============================================================================
--- head/en_US.ISO8859-1/books/porters-handbook/makefiles/chapter.xml Wed Apr 8 09:16:56 2015 (r46501)
+++ head/en_US.ISO8859-1/books/porters-handbook/makefiles/chapter.xml Wed Apr 8 11:41:18 2015 (r46502)
@@ -58,8 +58,9 @@
The package name must be unique among all of the ports
- tree. Make sure that there is not already a port with the same
- PORTNAME and if there is add one of PORTNAME and if there is add one of
+ PKGNAMEPREFIX
or PKGNAMESUFFIX.
@@ -106,9 +107,9 @@
Changes in the packing list or the install-time
- behavior of the package. For example, a change to a script which
- generates initial data for the package, like &man.ssh.1; host
- keys.
+ behavior of the package. For example, a change to a
+ script which generates initial data for the package,
+ like &man.ssh.1; host keys.
@@ -121,8 +122,8 @@
Silent changes to the port distfile which have
- significant functional differences. For example, changes to the
- distfile requiring a correction to
+ significant functional differences. For example,
+ changes to the distfile requiring a correction to
distinfo with no corresponding
change to PORTVERSION, where a
diff -ru of the old and new versions
@@ -166,8 +167,9 @@
A rule of thumb is to decide whether a change
- committed to a port is something which some people would
- benefit from having. Either because of an enhancement, fix,
+ committed to a port is something which
+ some people would benefit from having.
+ Either because of an enhancement, fix,
or by virtue that the new package will actually work at
all. Then weigh that against that fact that it will cause
everyone who regularly updates their ports tree to be
@@ -177,7 +179,7 @@
People using binary packages will
never see the update if
- PORTREVISION is not bumped. Without
+ PORTREVISION is not bumped. Without
increasing PORTREVISION, the
package builders have no way to detect the change and
thus, will not rebuild the package.
@@ -215,13 +217,13 @@
the package name as described in section 0 above.
PORTEPOCH must never be decreased or
reset to zero, because that would cause comparison to a
- package from an earlier epoch to fail. For example, the package
- would not be detected as out of date. The new version
- number, 1.0,1 in the above
- example, is still numerically less than the previous version,
- 20000801, but the ,1 suffix is treated
- specially by automated tools and found to be greater than
- the implied suffix ,0 on the earlier
+ package from an earlier epoch to fail. For example, the
+ package would not be detected as out of date. The new
+ version number, 1.0,1 in the above
+ example, is still numerically less than the previous
+ version, 20000801, but the ,1 suffix is
+ treated specially by automated tools and found to be greater
+ than the implied suffix ,0 on the earlier
package.Dropping or resetting PORTEPOCH
@@ -242,8 +244,8 @@
release is made.For example, if a snapshot release is made on the date
- 20000917, and the previous version of the software was
- version 1.2, do not use
+ 20000917, and the previous version of the
+ software was version 1.2, do not use
20000917 for
PORTVERSION. The correct way is a
PORTVERSION of
@@ -398,14 +400,15 @@ PORTEPOCH= 1
version part is if the upstream distribution is really
named that way, as in the
textproc/libxml2 or
- japanese/kinput2-freewnn ports.
- Otherwise, PORTNAME cannot
+ japanese/kinput2-freewnn
+ ports. Otherwise, PORTNAME cannot
contain any version-specific information. It is quite
normal for several ports to have the same
PORTNAME, as the
- www/apache* ports do; in that case,
- different versions (and different index entries) are
- distinguished by PKGNAMEPREFIX
+ www/apache* ports do; in
+ that case, different versions (and different index
+ entries) are distinguished by
+ PKGNAMEPREFIX
and PKGNAMESUFFIX values.There is a tradition of naming
@@ -806,8 +809,8 @@ PORTEPOCH= 1
editorsGeneral editors.Specialized editors go in the section for those
- tools. For example, a mathematical-formula editor will
- go in math, and have
+ tools. For example, a mathematical-formula editor
+ will go in math, and have
editors as a second
category.
@@ -844,8 +847,10 @@ PORTEPOCH= 1
ftp
- FTP client and server utilities.
- If the port speaks both FTP and HTTP, put it
+ FTP client and server
+ utilities.
+ If the port speaks both FTP
+ and HTTP, put it
in ftp with a secondary
category of www.
@@ -1648,186 +1653,186 @@ PORTEPOCH= 1
MASTER_SITE_*
Variables
- Shortcut abbreviations are available for popular archives
- like SourceForge (SF), GNU
- (GNU), or Perl CPAN
- (CPAN). MASTER_SITES can
- use them directly:
-
- MASTER_SITES= GNU/make
-
- The older expanded format still works, but all ports
- should be converted to the compact format. The expanded
- format looks like this:
+ Shortcut abbreviations are available for popular
+ archives like SourceForge (SF), GNU
+ (GNU), or Perl CPAN
+ (CPAN). MASTER_SITES
+ can use them directly:
+
+ MASTER_SITES= GNU/make
+
+ The older expanded format still works, but all ports
+ should be converted to the compact format. The expanded
+ format looks like this:
- MASTER_SITES= ${MASTER_SITE_GNU}
+ MASTER_SITES= ${MASTER_SITE_GNU}
MASTER_SITE_SUBDIR= make
- These values and variables are defined in Mk/bsd.sites.mk.
- New entries are added often, so make sure to check the latest
- version of this file before submitting a port.
+ These values and variables are defined in Mk/bsd.sites.mk.
+ New entries are added often, so make sure to check the
+ latest version of this file before submitting a port.
-
- For any
- MASTER_SITE_FOO
- variable, the shorthand
- FOO can be
- used. For example, use:
+
+ For any
+ MASTER_SITE_FOO
+ variable, the shorthand
+ FOO can be
+ used. For example, use:
- MASTER_SITES= FOO
+ MASTER_SITES= FOO
- If MASTER_SITE_SUBDIR is needed, use
- this:
+ If MASTER_SITE_SUBDIR is needed,
+ use this:
- MASTER_SITES= FOO/bar
-
+ MASTER_SITES= FOO/bar
+ Magic MASTER_SITES Macros
- Several magic macros exist for
- popular sites with a predictable directory structure. For
- these, just use the abbreviation and the system will try to
- guess the correct subdirectory automatically. For a port
- named Stardict, of version
- 1.2.3, and hosted on SourceForge, adding
- this line:
+ Several magic macros exist for
+ popular sites with a predictable directory structure. For
+ these, just use the abbreviation and the system will try to
+ guess the correct subdirectory automatically. For a port
+ named Stardict, of version
+ 1.2.3, and hosted on SourceForge, adding
+ this line:
- MASTER_SITES= SF
+ MASTER_SITES= SF
- Will infer a subdirectory named
- /project/stardict/stardict/1.2.3. If the
- guess is incorrect, it can be overridden as follows.
+ Will infer a subdirectory named
+ /project/stardict/stardict/1.2.3. If the
+ guess is incorrect, it can be overridden as follows.
- MASTER_SITES= SF/stardict/WyabdcRealPeopleTTS/${PORTVERSION}
+ MASTER_SITES= SF/stardict/WyabdcRealPeopleTTS/${PORTVERSION}
- This can also be written as
+ This can also be written as
- MASTER_SITES= SF
+ MASTER_SITES= SF
MASTER_SITE_SUBDIR= stardict/WyabdcRealPeopleTTS/${PORTVERSION}
-
+
+ SF
+ ${PORTNAME:tl}/${PORTNAME:tl}/${PORTVERSION}
+
+
+
+
@@ -2025,7 +2030,8 @@ EXTRACT_ONLY= source.tar.gzPATCHFILESIf the port requires some additional patches that are
- available by FTP or HTTP, set PATCHFILES to
+ available by FTP or
+ HTTP, set PATCHFILES to
the names of the files and PATCH_SITES to
the URL of the directory that contains them (the format is the
same as MASTER_SITES).
@@ -2224,8 +2230,8 @@ DISTFILES= source1.tar.gz:source1 \
[a-zA-Z_][0-9a-zA-Z_]+ for
now.
- Moreover, string matching is case sensitive; that is,
- n is different from
+ Moreover, string matching is case sensitive; that
+ is, n is different from
N.However, these words cannot be used for
@@ -3373,7 +3379,7 @@ xmlcatmgr:${PORTSDIR}/textproc/xmlcatmgr
world, will have their &os; installation broken
almost immediately, with many others quickly to follow. These
can really be hard to detect. If in doubt, before making
- that change, make sure to run:
+ that change, make sure to run:
cd /usr/ports; make index. That process
can be quite slow on older machines, but it may be able to
save a large number of people, including yourself,
@@ -3431,22 +3437,23 @@ BAR_LIB_DEPENDS= libbar.so:${PORTSDIR}/f
USE_* and
WANT_*
- USE_* are set by the port
- maintainer to define software on which this port depends. A
- port that needs Firefox would set
+ USE_* are
+ set by the port maintainer to define software on which this
+ port depends. A port that needs Firefox would setUSE_FIREFOX= yes
- Some USE_* can accept version
- numbers or other parameters. For example, a port that
- requires Apache 2.2 would set
+ Some USE_*
+ can accept version numbers or other parameters. For example,
+ a port that requires Apache 2.2 would setUSE_APACHE= 22For more control over dependencies in some cases,
- WANT_* are available to more
- precisely specify what is needed. For example, consider the
- mail/squirrelmail port. This
+ WANT_* are
+ available to more precisely specify what is needed. For
+ example, consider the mail/squirrelmail port. This
port needs some PHP modules, which are listed in
USE_PHP:
@@ -3458,8 +3465,10 @@ BAR_LIB_DEPENDS= libbar.so:${PORTSDIR}/f
WANT_PHP_WEB= yes
- Available USE_* and
- WANT_* are defined in the files in
+ Available
+ USE_* and
+ WANT_* are
+ defined in the files in
/usr/ports/Mk.
@@ -3540,8 +3549,8 @@ MASTERDIR= ${.CURDIR}/../xdvi300
Info Files
- If the package needs to install GNU info files, list them
- in INFO (without the
+ If the package needs to install GNU info
+ files, list them in INFO (without the
trailing .info), one entry per document.
These files are assumed to be installed to
PREFIX/INFO_PATH. Change
@@ -3579,12 +3588,12 @@ MASTERDIR= ${.CURDIR}/../xdvi300
Background
- OPTIONS_* give the
- user installing the port a dialog showing the available
- options, and then saves those options to
+ OPTIONS_*
+ give the user installing the port a dialog showing the
+ available options, and then saves those options to
${PORT_DBDIR}/${OPTIONS_NAME}/options.
The next time the port is built, the options are
- reused. PORT_DBDIR defaults to
+ reused. PORT_DBDIR defaults to
/var/db/ports.
OPTIONS_NAME is to the port origin with
an underscore as the space separator, for example, for
@@ -3596,7 +3605,8 @@ MASTERDIR= ${.CURDIR}/../xdvi300
framework checks for
${PORT_DBDIR}/${OPTIONS_NAME}/options.
If that file does not exist, the values of
- OPTIONS_* are used, and a dialog box is
+ OPTIONS_*
+ are used, and a dialog box is
displayed where the options can be enabled or disabled.
Then options is saved and the
configured variables are used when building the port.
@@ -3708,7 +3718,9 @@ OPTIONS_GROUP_GG1= OPT9 OPT10bsd.port.options.mk.
But be aware that some variables will not work as expected
after the inclusion of bsd.port.pre.mk,
- typically some USE_* flags.
+ typically some
+ USE_*
+ flags.Simple Use of OPTIONS
@@ -3734,7 +3746,7 @@ BAR_RUN_DEPENDS= bar:${PORTSDIR}/bar/bar
CONFIGURE_ARGS+=--without-examples
.endif
- The form shown above is discouraged. The preferred
+ The form shown above is discouraged. The preferred
method is using a configure knob to really enable and
disable the feature to match the option:
@@ -3974,12 +3986,13 @@ USE_XORG= x11 xextproto xext xrandr
OPT_CONFIGURE_ENABLE
then
--enable-entry
- is appended to CONFIGURE_ARGS. When option
- OPT is not selected,
+ is appended to CONFIGURE_ARGS. When
+ option OPT is not selected,
--disable-entry
- is appended to CONFIGURE_ARGS. An optional
- argument can be specified with an =
- symbol. This argument is only appended to the
+ is appended to CONFIGURE_ARGS. An
+ optional argument can be specified with an
+ = symbol. This argument is only appended
+ to the
--enable-entry
configure option. For example:
@@ -4014,12 +4027,13 @@ CONFIGURE_ARGS+= --disable-test2
OPT_CONFIGURE_ENABLE
then
--with-entry
- is appended to CONFIGURE_ARGS. When option
- OPT is not selected,
+ is appended to CONFIGURE_ARGS. When
+ option OPT is not selected,
--without-entry
- is appended to CONFIGURE_ARGS. An optional
- argument can be specified with an =
- symbol. This argument is only appended to the
+ is appended to CONFIGURE_ARGS. An
+ optional argument can be specified with an
+ = symbol. This argument is only appended
+ to the
--with-entry
configure option. For example:
@@ -4529,20 +4543,21 @@ PORTVERSION= 1.0
that CONFLICTS_INSTALL does not match this
port's package itself. Otherwise enforcing its installation
with FORCE_PKG_REGISTER will no longer
- work. CONFLICTS_INSTALL check is done after the build
- stage and prior to the install stage.
+ work. CONFLICTS_INSTALL check is done
+ after the build stage and prior to the install stage.CONFLICTS_BUILD
- If the port cannot be built when other specific ports are already
- installed, list the other port names in
+ If the port cannot be built when other specific ports are
+ already installed, list the other port names in
CONFLICTS_BUILD. Use
shell globs like * and ?
here. Use package names, not port names or origins.
- CONFLICTS_BUILD check is done prior to the build stage. Build
- conflicts are not recorded in the resulting package.
+ CONFLICTS_BUILD check is done prior to the
+ build stage. Build conflicts are not recorded in the
+ resulting package.
@@ -4558,8 +4573,8 @@ PORTVERSION= 1.0
CONFLICTS does not match this
port's package itself. Otherwise enforcing its installation
with FORCE_PKG_REGISTER will no longer
- work. CONFLICTS check is done prior to the build stage
- and prior to the install stage.
+ work. CONFLICTS check is done prior to the
+ build stage and prior to the install stage.
@@ -4567,7 +4582,8 @@ PORTVERSION= 1.0
Installing Files
- INSTALL_* Macros
+ INSTALL_*
+ MacrosUse the macros provided in
bsd.port.mk to ensure correct modes of
@@ -4707,7 +4723,8 @@ PORTVERSION= 1.0
Additional find arguments can be
passed via the third argument to
- COPYTREE_* macros. For example, to install
+ COPYTREE_*
+ macros. For example, to install
all files from the first example except Makefiles, one can use
these commands.
From owner-svn-doc-head@FreeBSD.ORG Wed Apr 8 15:44:24 2015
Return-Path:
Delivered-To: svn-doc-head@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
[IPv6:2001:1900:2254:206a::19:1])
(using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
(No client certificate requested)
by hub.freebsd.org (Postfix) with ESMTPS id 81F0391;
Wed, 8 Apr 2015 15:44:24 +0000 (UTC)
Received: from svn.freebsd.org (svn.freebsd.org
[IPv6:2001:1900:2254:2068::e6a:0])
(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
(Client did not present a certificate)
by mx1.freebsd.org (Postfix) with ESMTPS id 62A3ABCB;
Wed, 8 Apr 2015 15:44:24 +0000 (UTC)
Received: from svn.freebsd.org ([127.0.1.70])
by svn.freebsd.org (8.14.9/8.14.9) with ESMTP id t38FiOVe082970;
Wed, 8 Apr 2015 15:44:24 GMT (envelope-from bjk@FreeBSD.org)
Received: (from bjk@localhost)
by svn.freebsd.org (8.14.9/8.14.9/Submit) id t38FiNZB082968;
Wed, 8 Apr 2015 15:44:23 GMT (envelope-from bjk@FreeBSD.org)
Message-Id: <201504081544.t38FiNZB082968@svn.freebsd.org>
X-Authentication-Warning: svn.freebsd.org: bjk set sender to bjk@FreeBSD.org
using -f
From: Benjamin Kaduk
Date: Wed, 8 Apr 2015 15:44:23 +0000 (UTC)
To: doc-committers@freebsd.org, svn-doc-all@freebsd.org,
svn-doc-head@freebsd.org
Subject: svn commit: r46503 - head/en_US.ISO8859-1/htdocs/news/status
X-SVN-Group: doc-head
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
X-BeenThere: svn-doc-head@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: SVN commit messages for the doc tree for head
List-Unsubscribe: ,
List-Archive:
List-Post:
List-Help:
List-Subscribe: ,
X-List-Received-Date: Wed, 08 Apr 2015 15:44:24 -0000
Author: bjk
Date: Wed Apr 8 15:44:23 2015
New Revision: 46503
URL: https://svnweb.freebsd.org/changeset/doc/46503
Log:
Add an empty status report file for January-March 2015
Approved by: hrs (mentor, implicit)
Added:
head/en_US.ISO8859-1/htdocs/news/status/report-2015-01-2015-03.xml (contents, props changed)
Modified:
head/en_US.ISO8859-1/htdocs/news/status/Makefile
Modified: head/en_US.ISO8859-1/htdocs/news/status/Makefile
==============================================================================
--- head/en_US.ISO8859-1/htdocs/news/status/Makefile Wed Apr 8 11:41:18 2015 (r46502)
+++ head/en_US.ISO8859-1/htdocs/news/status/Makefile Wed Apr 8 15:44:23 2015 (r46503)
@@ -68,6 +68,7 @@ XMLDOCS+= report-2014-01-2014-03
XMLDOCS+= report-2014-04-2014-06
XMLDOCS+= report-2014-07-2014-09
XMLDOCS+= report-2014-10-2014-12
+XMLDOCS+= report-2015-01-2015-03
XSLT.DEFAULT= report.xsl
Added: head/en_US.ISO8859-1/htdocs/news/status/report-2015-01-2015-03.xml
==============================================================================
--- /dev/null 00:00:00 1970 (empty, because file is newly added)
+++ head/en_US.ISO8859-1/htdocs/news/status/report-2015-01-2015-03.xml Wed Apr 8 15:44:23 2015 (r46503)
@@ -0,0 +1,86 @@
+
+
+
+
+
+
+
+ January-March
+
+ 2015
+
+
+
+ Introduction
+
+
+
This is a draft of the January–March 2015
+ status report. Please check back after it is finalized, and
+ an announcement email is sent to the &os;-Announce mailing
+ list.
+
+
+
This report covers &os;-related projects between January and
+ March 2015. This is the first of four reports planned for
+ 2015.
+
+
The first quarter of 2015... was a very busy and productive
+ time.
+
+
Thanks to all the reporters for the excellent work!
+
+
The deadline for submissions covering the period from April
+ to June 2015 is July 7th, 2015.
+
+
+
+ team
+
+ &os; Team Reports
+
+
+
+ proj
+
+ Projects
+
+
+
+ kern
+
+ Kernel
+
+
+
+ arch
+
+ Architectures
+
+
+
+ bin
+
+ Userland Programs
+
+
+
+ ports
+
+ Ports
+
+
+
+ doc
+
+ Documentation
+
+
+
+ misc
+
+ Miscellaneous
+
+
+
From owner-svn-doc-head@FreeBSD.ORG Wed Apr 8 19:05:36 2015
Return-Path:
Delivered-To: svn-doc-head@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
(using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
(No client certificate requested)
by hub.freebsd.org (Postfix) with ESMTPS id 0CD8D9C2;
Wed, 8 Apr 2015 19:05:36 +0000 (UTC)
Received: from svn.freebsd.org (svn.freebsd.org
[IPv6:2001:1900:2254:2068::e6a:0])
(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
(Client did not present a certificate)
by mx1.freebsd.org (Postfix) with ESMTPS id EB5859A4;
Wed, 8 Apr 2015 19:05:35 +0000 (UTC)
Received: from svn.freebsd.org ([127.0.1.70])
by svn.freebsd.org (8.14.9/8.14.9) with ESMTP id t38J5Z9B080846;
Wed, 8 Apr 2015 19:05:35 GMT (envelope-from wblock@FreeBSD.org)
Received: (from wblock@localhost)
by svn.freebsd.org (8.14.9/8.14.9/Submit) id t38J5ZOl080845;
Wed, 8 Apr 2015 19:05:35 GMT (envelope-from wblock@FreeBSD.org)
Message-Id: <201504081905.t38J5ZOl080845@svn.freebsd.org>
X-Authentication-Warning: svn.freebsd.org: wblock set sender to
wblock@FreeBSD.org using -f
From: Warren Block
Date: Wed, 8 Apr 2015 19:05:35 +0000 (UTC)
To: doc-committers@freebsd.org, svn-doc-all@freebsd.org,
svn-doc-head@freebsd.org
Subject: svn commit: r46504 -
head/en_US.ISO8859-1/books/porters-handbook/slow-porting
X-SVN-Group: doc-head
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
X-BeenThere: svn-doc-head@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: SVN commit messages for the doc tree for head
List-Unsubscribe: ,
List-Archive:
List-Post:
List-Help:
List-Subscribe: ,
X-List-Received-Date: Wed, 08 Apr 2015 19:05:36 -0000
Author: wblock
Date: Wed Apr 8 19:05:35 2015
New Revision: 46504
URL: https://svnweb.freebsd.org/changeset/doc/46504
Log:
Fix a typo.
Submitted by: forum user tankist02
Modified:
head/en_US.ISO8859-1/books/porters-handbook/slow-porting/chapter.xml
Modified: head/en_US.ISO8859-1/books/porters-handbook/slow-porting/chapter.xml
==============================================================================
--- head/en_US.ISO8859-1/books/porters-handbook/slow-porting/chapter.xml Wed Apr 8 15:44:23 2015 (r46503)
+++ head/en_US.ISO8859-1/books/porters-handbook/slow-porting/chapter.xml Wed Apr 8 19:05:35 2015 (r46504)
@@ -109,7 +109,7 @@
The install target is run.
- This install the package created during the
+ This installs the package created during the
package target into the host
system.
From owner-svn-doc-head@FreeBSD.ORG Wed Apr 8 21:39:41 2015
Return-Path:
Delivered-To: svn-doc-head@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
(using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
(No client certificate requested)
by hub.freebsd.org (Postfix) with ESMTPS id D773AFB0;
Wed, 8 Apr 2015 21:39:41 +0000 (UTC)
Received: from svn.freebsd.org (svn.freebsd.org
[IPv6:2001:1900:2254:2068::e6a:0])
(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
(Client did not present a certificate)
by mx1.freebsd.org (Postfix) with ESMTPS id B8878D14;
Wed, 8 Apr 2015 21:39:41 +0000 (UTC)
Received: from svn.freebsd.org ([127.0.1.70])
by svn.freebsd.org (8.14.9/8.14.9) with ESMTP id t38LdffU053933;
Wed, 8 Apr 2015 21:39:41 GMT (envelope-from mahrens@FreeBSD.org)
Received: (from mahrens@localhost)
by svn.freebsd.org (8.14.9/8.14.9/Submit) id t38LddrU053927;
Wed, 8 Apr 2015 21:39:39 GMT (envelope-from mahrens@FreeBSD.org)
Message-Id: <201504082139.t38LddrU053927@svn.freebsd.org>
X-Authentication-Warning: svn.freebsd.org: mahrens set sender to
mahrens@FreeBSD.org using -f
From: Matthew Ahrens
Date: Wed, 8 Apr 2015 21:39:39 +0000 (UTC)
To: doc-committers@freebsd.org, svn-doc-all@freebsd.org,
svn-doc-head@freebsd.org
Subject: svn commit: r46505 - 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-head@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: SVN commit messages for the doc tree for head
List-Unsubscribe: ,
List-Archive:
List-Post:
List-Help:
List-Subscribe: ,
X-List-Received-Date: Wed, 08 Apr 2015 21:39:42 -0000
Author: mahrens (src committer)
Date: Wed Apr 8 21:39:38 2015
New Revision: 46505
URL: https://svnweb.freebsd.org/changeset/doc/46505
Log:
Adding myself (mahrens) as a src/ committer, according to the committer's guide
Added:
head/share/pgpkeys/mahrens.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/news.xml
Modified: head/en_US.ISO8859-1/articles/contributors/contrib.committers.xml
==============================================================================
--- head/en_US.ISO8859-1/articles/contributors/contrib.committers.xml Wed Apr 8 19:05:35 2015 (r46504)
+++ head/en_US.ISO8859-1/articles/contributors/contrib.committers.xml Wed Apr 8 21:39:38 2015 (r46505)
@@ -15,6 +15,10 @@
+ &a.mahrens.email;
+
+
+ &a.akiyama.email;
Added: head/share/pgpkeys/mahrens.key
==============================================================================
--- /dev/null 00:00:00 1970 (empty, because file is newly added)
+++ head/share/pgpkeys/mahrens.key Wed Apr 8 21:39:38 2015 (r46505)
@@ -0,0 +1,78 @@
+
+
+
+uid Matthew Ahrens
+uid Matthew Ahrens
+uid Matthew Ahrens
+uid Matthew Ahrens
+sub 2048R/1137F565976A0587 2014-04-08 [expires: 2017-04-07]
+
+]]>
+
Modified: head/share/pgpkeys/pgpkeys-developers.xml
==============================================================================
--- head/share/pgpkeys/pgpkeys-developers.xml Wed Apr 8 19:05:35 2015 (r46504)
+++ head/share/pgpkeys/pgpkeys-developers.xml Wed Apr 8 21:39:38 2015 (r46505)
@@ -19,6 +19,11 @@
&pgpkey.eadler;
+
+ &a.mahrens.email;
+ &pgpkey.mahrens;
+
+
&a.shaun.email;
&pgpkey.shaun;
Modified: head/share/pgpkeys/pgpkeys.ent
==============================================================================
--- head/share/pgpkeys/pgpkeys.ent Wed Apr 8 19:05:35 2015 (r46504)
+++ head/share/pgpkeys/pgpkeys.ent Wed Apr 8 21:39:38 2015 (r46505)
@@ -264,6 +264,7 @@
+
Modified: head/share/xml/authors.ent
==============================================================================
--- head/share/xml/authors.ent Wed Apr 8 19:05:35 2015 (r46504)
+++ head/share/xml/authors.ent Wed Apr 8 21:39:38 2015 (r46505)
@@ -1305,6 +1305,9 @@
maho@FreeBSD.org">
+
+mahrens@FreeBSD.org">
+
makc@FreeBSD.org">
Modified: head/share/xml/news.xml
==============================================================================
--- head/share/xml/news.xml Wed Apr 8 19:05:35 2015 (r46504)
+++ head/share/xml/news.xml Wed Apr 8 21:39:38 2015 (r46505)
@@ -35,6 +35,15 @@
3
+ 31
+
+
+